-
Notifications
You must be signed in to change notification settings - Fork 24
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Parametrize war name #8
Comments
wad.sh fully relies on conventions and derives the WAR name from the projects folder. IMO: artifactid == foldername == WAR name. So far there were no serious reason to deviate from this convention. Do you know any? However: making the WAR name configurable could be easily implemented -> I'm thinking about that for the next release. |
Hi @AdamBien ! I agree with convention, I think it's the best pratice. But I work in an old svn-based project where we need to checkout multiple copies of the same project. Usually my workspace has about 15 different versions of the project, and I edit/run 2-4 versions each day. It would be hard to rename directories all the time, that's why I'm asking for the feature. =D |
Now it's possible to set finalName in pom.xml for war name.
Make ThinWarNameProvider method public.
My project is located in directories like
xFulanov1.56.3
, but it always generates war files liketarget/fulano.war
. WAD fails to find my war file, giving me ajava.nio.file.NoSuchFileException: target\xFulanov1.56.3.war
error message.Is it possible to tell WAD that it should observe a different filename?
Due to business restrictions, it wouldn't be easy to rename my project directories.
The text was updated successfully, but these errors were encountered: