-
Notifications
You must be signed in to change notification settings - Fork 130
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
WINDUP-329 Bundle settings.xml and a build script #300
WINDUP-329 Bundle settings.xml and a build script #300
Conversation
Merged build triggered. |
Merged build started. |
I think that I like the idea of doing this. However, I noticed that it doesn't appear to do a priming build (-Dskiptests). Perhaps that just needs to be in the documentation? |
Merged build finished. Test FAILed. |
retest |
Merged build triggered. |
Merged build started. |
Merged build finished. Test PASSed. |
Test PASSed. |
Merged build triggered. |
Merged build started. |
1c43249
to
ba94879
Compare
I've added the README.txt, and the Linux script determines the need for a priming build automatically. |
Merged build triggered. |
b3ba2f7
to
bf85d9e
Compare
Merged build triggered. |
Merged build finished. Test FAILed. |
Test FAILed. Failed Tests: 3org.jboss.windup.graph:windup-graph-tests: 3Test FAILed. |
Merged build started. |
bf85d9e
to
19881ec
Compare
Merged build triggered. |
Merged build finished. Test PASSed. |
Test PASSed. |
Merged build started. |
Merged build finished. Test PASSed. |
Test PASSed. |
Merged build started. |
This is ready to review, not sure why the test was triggered again. |
Merged build finished. Test FAILed. |
Test FAILed. Failed Tests: 2org.jboss.windup.config:windup-config-tests: 2Test FAILed. |
WINDUP-329 Bundle settings.xml and a build script
It's more convenient for the user to get the source and run build/build.sh than to follow build instructions and change files manually. There's no manual intervention needed if we make it so.
It will also make tests and CI more convenient - no need to create/edit local settings.xml.
This is how WildFly has it.
Alternatively, we could add the repo to pom.xml - just like JBoss Developer Framework has it now.