[
https://issues.apache.org/jira/browse/MTOMCAT-32?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13126855#comment-13126855
]
Michael Osipov commented on MTOMCAT-32:
---------------------------------------
Steve, what is the benefit? If I look at all other pom configs like site,
deployment. All of them provider a serverId and a url.
> Allow manager url in settings.xml (via server/configuration/url)
> ----------------------------------------------------------------
>
> Key: MTOMCAT-32
> URL: https://issues.apache.org/jira/browse/MTOMCAT-32
> Project: Maven 2.x Tomcat Plugin
> Issue Type: Improvement
> Affects Versions: 1.0-beta-1
> Environment: Windows/Apache/Tomcat/Maven2/JDK1.6
> Reporter: Steve Gillam
> Priority: Minor
>
> URL for tomcat manager is a function of machine configuration (refelcted in
> maven's settings.xml) as opposed to the project settings (as reflected in
> pom.xml)
> Maven's settings.xml does support
> {server}{configuration}{url} http://localhost/manager
> {/url}{/configuration}{/server} as used by
> http://pyx4me.com/pyx4me-maven-plugins/obex-maven-plugin/
> Unfortunately, whilst not generating any errors, the tomcat plugin seems not
> to look for/use it (and defaults to http://localhost:8080/manager)
> Would be very useful if it did
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
