[jira] [Commented] (MTOMCAT-91) tomcat-maven-plugin hard codes INITIAL_CONTEXT

["Olivier Lamy (*$^¨%`£ JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MTOMCAT-91?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13812594#comment-13812594 ] 

Olivier Lamy (*$^¨%`£) commented on MTOMCAT-91:
-----------------------------------------------

need some changes in tomcat core.

> tomcat-maven-plugin hard codes INITIAL_CONTEXT
> ----------------------------------------------
>
>                 Key: MTOMCAT-91
>                 URL: https://issues.apache.org/jira/browse/MTOMCAT-91
>             Project: Apache Tomcat Maven Plugin
>          Issue Type: Bug
>    Affects Versions: 1.1
>            Reporter: Kennard Consulting
>             Fix For: backlog
>
>
> Hi guys,
> Thanks for a great Maven plugin in tomcat-maven-plugin. I am using it in my Open Source project and it works really well.
> I recently tried getting tomcat-maven-plugin to coexist with jetty-maven-plugin. There is a problem that appears to sit somewhere in the middle of the two projects, and requires both of you to agree on a solution :)
> Basically tomcat-maven-plugin appears to be setting INITIAL_CONTEXT at the VM level (whereas Jetty does not) and this means that Jetty ends up trying to use Tomcat's JNDI implementation. It would be great if Tomcat/Jetty could live together in a build process, so that I could run my integration tests against multiple appservers.
> Please see JETTY-1370 for an example pom.xml and an error log, and also discussion from the jetty-maven-plugin guys about what might be 'wrong'.
> Regards,
> Richard.



--
This message was sent by Atlassian JIRA
(v6.1#6144)

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org