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.
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'swartask, `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.