[
https://issues.apache.org/jira/browse/MTOMCAT-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14269476#comment-14269476
]
Srdan Srepfler commented on MTOMCAT-83:
---------------------------------------
I think we are running into this issue as well, does it mean essentially that a
forked tomcat is not getting the systemProperties passed onto it?
We are simply trying to run tomcat in the pre-integration-test-phase and
override a system configuration for the container and as it essentially needs
to run with a different configuration from the default classpath. However we
don't get the property injected into tomcat while if we pass it via the command
line as a mvn argument it works just fine. But we see this behaviour consistent
with both fork true and false so I'm not sure at this point is the entire
systemProperties problematic or our configuration.
> Support specifying arguments using a real forked JVM
> ----------------------------------------------------
>
> Key: MTOMCAT-83
> URL: https://issues.apache.org/jira/browse/MTOMCAT-83
> Project: Apache Tomcat Maven Plugin
> Issue Type: New Feature
> Affects Versions: 1.1
> Reporter: Stevo Slavic
> Fix For: backlog
>
>
> [tomcat-maven-plugin's run
> goal|http://mojo.codehaus.org/tomcat-maven-plugin/run-mojo.html] seems to
> support forking, but not specifying arguments for forked JVM. Something like
> that IMO would be useful for specifying memory options different from Maven
> build and javaagent like jacoco for coverage.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@tomcat.apache.org
For additional commands, e-mail: dev-h...@tomcat.apache.org
