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

[WFMP-208]: dev mode deployment runtime name is not configurable. #342

Closed
wants to merge 1 commit into from

Conversation

ehsavoie
Copy link
Contributor

  • Adding a new 'name' parameter with the same property as for the package mojo.

Jira: https://issues.redhat.com/browse/WFMP-208

plugin/src/main/java/org/wildfly/plugin/dev/DevMojo.java Outdated Show resolved Hide resolved
*
* When the deployment is copied to the server, it is renamed with this name.
*/
@Parameter(property = PropertyNames.DEPLOYMENT_NAME)
Copy link
Member

Choose a reason for hiding this comment

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

I'm on my phone so it's hard to see, but if the run goal has this field, we should remove it from there. Or just move this field into the DevMojo.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

yes it has but not the StartMojo also the RunMojo has runtimeName which is deperecated in the PackageServerMojo

Copy link
Contributor Author

Choose a reason for hiding this comment

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

@jamezp I don't see the point of adding this field to the 'parent' class AbstractServerStartMojo and it doesn't make sense in the context of StartMojo. So I don't think we should 'move' it out :)

* Adding a new 'name' parameter with the same property as for the
  package mojo.

Jira: https://issues.redhat.com/browse/WFMP-208

Signed-off-by: Emmanuel Hugonnet <ehugonne@redhat.com>
Copy link
Member

@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 like it has formatting issues.

@jamezp
Copy link
Member

jamezp commented Jun 28, 2023

Replaces by #350 to get this change into the next release.

@jamezp jamezp closed this Jun 28, 2023
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