[jetty-dev] [jira] (JETTY-1507) System properties are not getting cleared out between runs within an aggregator
"Jan Bartel (JIRA)" <[email protected]>
| Newsgroups | gmane.comp.java.jetty.general |
|---|---|
| Message-ID | <458462777.77289.1336471144350.JavaMail.j2ee-jira@codehaus01.managed.contegix.com> |
[ https://jira.codehaus.org/browse/JETTY-1507?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=298136#comment-298136 ]
Jan Bartel commented on JETTY-1507:
-----------------------------------
The more I think about this, the less inclined I am to change the current behaviour. Consider that the SystemProperties are set as the plugin begins to execute. Any clear-down of them could not reasonably be done until jetty stops running. At that point, if we start changing the system properties, we may change the exit behaviour. For example, if a system property was set that affected the logging, perhaps resetting that would mean that an exception thrown on exit would not be logged (to the same logging framework used for the rest of the runtime).
Instead of using <systemProperties> you could instead set your system properties in jetty.xml files that are executed with each new plugin invocation - they have normal jvm semantics and thus you can set them over and over again as suits your application.
Jan
> System properties are not getting cleared out between runs within an aggregator
> -------------------------------------------------------------------------------
>
> Key: JETTY-1507
> URL: https://jira.codehaus.org/browse/JETTY-1507
> Project: Jetty
> Issue Type: Bug
> Affects Versions: 7.6.1
> Environment: Apache Maven 3.0.3 (r1075438; 2011-02-28 19:31:09+0200)
> Maven home: /java/apache/maven-3.0.3
> Java version: 1.6.0_19, vendor: Sun Microsystems Inc.
> Java home: /java/jdk1.6.0_19/jre
> Default locale: en_US, platform encoding: ISO-8859-1
> OS name: "linux", version: "2.6.36.2", arch: "i386", family: "unix"
> Reporter: Martin Todorov
> Assignee: Jan Bartel
>
> If you have an aggregator with several modules each of which launches Jetty before the tests and if you've defined <systemProperties><systemProperty...></systemProperties, the next module to start up Jetty will end up using the values from defined for the first module, even if you've defined different values for this module.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email