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

move the wildfly-maven-plugin configuration to top level so it can … #6

Merged
merged 1 commit into from
Oct 5, 2024

Conversation

liweinan
Copy link
Contributor

@liweinan liweinan commented Oct 4, 2024

…be used by multiple goals

@liweinan
Copy link
Contributor Author

liweinan commented Oct 4, 2024

@jamezp Could you please help to check this PR when you have time? I have checked it locally and it works with mvn wildly:dev or mvn wildfly:run

Copy link
Contributor

@jamezp jamezp left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. By having this outside an execution you allow goals which have the same configuration parameters to work the same. For example, dev, start, run, provision and package will all provision the same server with this configuration. In the previous configuration all goals except provision would provision a full WildFly server without the JBeret version override.

@liweinan
Copy link
Contributor Author

liweinan commented Oct 5, 2024

@jamezp Thanks for reviewing this!

@liweinan liweinan merged commit 4c3543a into jberet:main Oct 5, 2024
1 check passed
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

Successfully merging this pull request may close these issues.

2 participants