Skip to content

Compiled rails war gives 404 errors, uncompiled works #135

Open
@joonty

Description

@joonty

Hi,

First, I just want to say that warbler is fantastic - thanks for all your work.

Unfortunately, I've been having a problem with running a compiled rails war on both Tomcat and Jetty. It's a Rails 3.2.11 app, and I've precompiled all assets and packed all gems into vendors.

Running bundle exec warble war produces a working war file, and it runs well on both Tomcat and Jetty.

Running bundle exec warble compiled war produces a war file, but the 404 page is delivered for everything except for assets.

I am using warbler 1.3.6.

If you need any more information I'm happy to supply it.

Thanks

--- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/1446631-compiled-rails-war-gives-404-errors-uncompiled-works?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F136961&utm_medium=issues&utm_source=github).

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions