Skip to content
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

Open
lampsbr opened this issue Oct 21, 2019 · 2 comments
Open

Parametrize war name #8

lampsbr opened this issue Oct 21, 2019 · 2 comments

Comments

@lampsbr
Copy link

lampsbr commented Oct 21, 2019

My project is located in directories like xFulanov1.56.3, but it always generates war files like target/fulano.war. WAD fails to find my war file, giving me a java.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.

@AdamBien
Copy link
Owner

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.

@lampsbr
Copy link
Author

lampsbr commented Oct 28, 2019

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

mrbyte2001 added a commit to mrbyte2001/wad that referenced this issue Nov 10, 2019
Now it's possible to set finalName in pom.xml for war name.
mrbyte2001 added a commit to mrbyte2001/wad that referenced this issue Nov 10, 2019
Make ThinWarNameProvider method public.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants