Skip to content

packaging #74

@tmackenzie

Description

@tmackenzie

At the moment building a executable war works with one limitation.

I have noticed that if there is the possibility of namespace collision for packaged files. This prevents starting the application via the executable war . I've beeb able to get around this issue by doing the following in a project's war task, `exclude "path/to/file.txt". This can only be done for files that are not needed, such as text files.

Package the war file to eliminate namespace collision modify the class path so jetty knows how to find everything.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions