[
https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12718076#action_12718076
]
Delos Dai commented on GERONIMODEVTOOLS-283:
--------------------------------------------
I think it's not right behavior for refactor. Indeed, the default values of
module-id and context-root are the same as the project name. But it's not
always the case. User can change module-id or context-root into other names. So
we have to keep them independent of each other.
If possible, suggest to close this JIRA!
Thanks!
> Refactoring a Dynamic Web Project's name doesn't refactor it's artifact id &
> context root
> -----------------------------------------------------------------------------------------
>
> Key: GERONIMODEVTOOLS-283
> URL:
> https://issues.apache.org/jira/browse/GERONIMODEVTOOLS-283
> Project: Geronimo-Devtools
> Issue Type: Wish
> Components: eclipse-plugin
> Reporter: Shiva Kumar H R
> Assignee: Shiva Kumar H R
> Priority: Minor
> Fix For: 2.2.0
>
>
> When a Dynamic Web Project with name say "tt" is created, a Geronimo
> deployment plan "geronimo-web.xml" will get created with module-id as
> "default/tt-1.0.car" and context-root as "/tt".
> When this project is re-factored to say "tz", the module-id will still be the
> same "default/tt-1.0.car" (note that artifact id is not re-factored from "tt"
> to "tz"). The context-root also remains the same "/tt".
> Although this doesn't pose any problem, wouldn't it be better to refactor the
> artifact-id & context-root to match the project name?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
