You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Christian Domsch (JIRA)" <ji...@codehaus.org> on 2006/08/18 15:01:48 UTC
[jira] Created: (MNG-2515) The Embedder does not work when started
from a groovy script that is started from maven 2
The Embedder does not work when started from a groovy script that is started from maven 2
-----------------------------------------------------------------------------------------
Key: MNG-2515
URL: http://jira.codehaus.org/browse/MNG-2515
Project: Maven 2
Issue Type: Bug
Components: Embedding
Affects Versions: 2.1
Environment: Windows XP, JDK 1.5, Maven 2.0.4
Reporter: Christian Domsch
Attachments: embedder-it-test.zip
The deploymentserver:changestage plugin starts a groovy script that again starts a maven 2.1-SNAPSHOT embedder. This fails due to classloading issues because the classloader for the groovy script contains a thread context classloader a s a parent. This parent classloader contains all classes from the maven 2.0.4 process that started the plugin. The embedder now fails to start because the parent classloader contains conflicting classes from 2.0.4 while the embedder is 2.1-SNAPSHOT.
The test case in the zip contains the source for the deploymentserver-mojo and the projects that this mojo should operate on. To start the test, install the mojo, and start maven in the productA project with "mvn deploymentserver:changestage". For this to work the settings.xml must contain
<pluginGroups>
<pluginGroup>innowake.lifecycle.deployment.engine.plugin</pluginGroup>
</pluginGroups>
The zip also contains the groovy jars to be copied in the local repository.
Greetings,
Christian.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MNG-2515) The Embedder does not work when started
from a groovy script that is started from maven 2
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter closed MNG-2515.
-----------------------------
Assignee: Brett Porter
Resolution: Won't Fix
Fix Version/s: (was: Reviewed Pending Version Assignment)
I expect only running the embedder for the current version of Maven, once available, will work unless you fork which can probably be handled separately
> The Embedder does not work when started from a groovy script that is started from maven 2
> -----------------------------------------------------------------------------------------
>
> Key: MNG-2515
> URL: http://jira.codehaus.org/browse/MNG-2515
> Project: Maven 2
> Issue Type: Bug
> Components: Embedding
> Affects Versions: 2.0-alpha-1
> Environment: Windows XP, JDK 1.5, Maven 2.0.4
> Reporter: Christian Domsch
> Assignee: Brett Porter
> Attachments: embedder-it-test.zip
>
>
> The deploymentserver:changestage plugin starts a groovy script that again starts a maven 2.1-SNAPSHOT embedder. This fails due to classloading issues because the classloader for the groovy script contains a thread context classloader a s a parent. This parent classloader contains all classes from the maven 2.0.4 process that started the plugin. The embedder now fails to start because the parent classloader contains conflicting classes from 2.0.4 while the embedder is 2.1-SNAPSHOT.
> The test case in the zip contains the source for the deploymentserver-mojo and the projects that this mojo should operate on. To start the test, install the mojo, and start maven in the productA project with "mvn deploymentserver:changestage". For this to work the settings.xml must contain
> <pluginGroups>
> <pluginGroup>innowake.lifecycle.deployment.engine.plugin</pluginGroup>
> </pluginGroups>
> The zip also contains the groovy jars to be copied in the local repository.
> Greetings,
> Christian.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-2515) The Embedder does not work when
started from a groovy script that is started from maven 2
Posted by "Jason van Zyl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-2515?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_88825 ]
Jason van Zyl commented on MNG-2515:
------------------------------------
So do you want to fork here? I have to experiment but I might be able to make an isolated classloader which doesn't conflict but we could easily fork from the 2.0.4 process.
> The Embedder does not work when started from a groovy script that is started from maven 2
> -----------------------------------------------------------------------------------------
>
> Key: MNG-2515
> URL: http://jira.codehaus.org/browse/MNG-2515
> Project: Maven 2
> Issue Type: Bug
> Components: Embedding
> Affects Versions: 2.1
> Environment: Windows XP, JDK 1.5, Maven 2.0.4
> Reporter: Christian Domsch
> Attachments: embedder-it-test.zip
>
>
> The deploymentserver:changestage plugin starts a groovy script that again starts a maven 2.1-SNAPSHOT embedder. This fails due to classloading issues because the classloader for the groovy script contains a thread context classloader a s a parent. This parent classloader contains all classes from the maven 2.0.4 process that started the plugin. The embedder now fails to start because the parent classloader contains conflicting classes from 2.0.4 while the embedder is 2.1-SNAPSHOT.
> The test case in the zip contains the source for the deploymentserver-mojo and the projects that this mojo should operate on. To start the test, install the mojo, and start maven in the productA project with "mvn deploymentserver:changestage". For this to work the settings.xml must contain
> <pluginGroups>
> <pluginGroup>innowake.lifecycle.deployment.engine.plugin</pluginGroup>
> </pluginGroups>
> The zip also contains the groovy jars to be copied in the local repository.
> Greetings,
> Christian.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira