[jira] [Updated] (MTOMCAT-170) Unable to Specify Additional Classpath for WAR Defined via "webapps" Declaration

2012-07-30 Thread Josh Harness (JIRA)

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Harness updated MTOMCAT-170:
-

Attachment: MTOMCAT-170.patch

Patch file for issue - generated from local development repo. 

> Unable to Specify Additional Classpath for WAR Defined via "webapps" 
> Declaration
> 
>
> Key: MTOMCAT-170
> URL: https://issues.apache.org/jira/browse/MTOMCAT-170
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
>Reporter: Josh Harness
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Attachments: MTOMCAT-170.patch
>
>
> I need the ability for web application defined in the "webapps" portion of 
> the plugin configuration to have the ability to use the classpath of the main 
> plugin configuration. A reasonable approach might be to allow the webapp to 
> inherit the additional classpath of the main web application config. 
> I'll apply a patch shortly for feedback/review.

--
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



[jira] [Updated] (MTOMCAT-170) Unable to Specify Additional Classpath for WAR Defined via "webapps" Declaration

2012-07-30 Thread Josh Harness (JIRA)

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Harness updated MTOMCAT-170:
-

Attachment: (was: MTOMCAT-170.patch)

> Unable to Specify Additional Classpath for WAR Defined via "webapps" 
> Declaration
> 
>
> Key: MTOMCAT-170
> URL: https://issues.apache.org/jira/browse/MTOMCAT-170
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
>Reporter: Josh Harness
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Attachments: MTOMCAT-170.patch
>
>
> I need the ability for web application defined in the "webapps" portion of 
> the plugin configuration to have the ability to use the classpath of the main 
> plugin configuration. A reasonable approach might be to allow the webapp to 
> inherit the additional classpath of the main web application config. 
> I'll apply a patch shortly for feedback/review.

--
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



[jira] [Updated] (MTOMCAT-170) Unable to Specify Additional Classpath for WAR Defined via "webapps" Declaration

2012-07-20 Thread Josh Harness (JIRA)

 [ 
https://issues.apache.org/jira/browse/MTOMCAT-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Josh Harness updated MTOMCAT-170:
-

Attachment: MTOMCAT-170.patch

Simply calls "createWebappLoader" in order to inherit the configuration of the 
main web application configuration. It would be ideal to be able to configure 
this on a case by case basis (per webapp) but this could be a reasonable start. 

> Unable to Specify Additional Classpath for WAR Defined via "webapps" 
> Declaration
> 
>
> Key: MTOMCAT-170
> URL: https://issues.apache.org/jira/browse/MTOMCAT-170
> Project: Apache Tomcat Maven Plugin
>  Issue Type: Bug
>  Components: tomcat7
>Affects Versions: 2.0
>Reporter: Josh Harness
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Attachments: MTOMCAT-170.patch
>
>
> I need the ability for web application defined in the "webapps" portion of 
> the plugin configuration to have the ability to use the classpath of the main 
> plugin configuration. A reasonable approach might be to allow the webapp to 
> inherit the additional classpath of the main web application config. 
> I'll apply a patch shortly for feedback/review.

--
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