You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by ji...@codehaus.org on 2004/09/03 14:58:08 UTC

[jira] Created: (MAVEN-1435) Plugin classpath are not overwriting project classpath.

Message:

  A new issue has been created in JIRA.

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1435

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1435
    Summary: Plugin classpath are not overwriting project classpath.
       Type: Bug

     Status: Unassigned
   Priority: Critical

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven

   Assignee: 
   Reporter: Jose Luiz

    Created: Fri, 3 Sep 2004 8:57 AM
    Updated: Fri, 3 Sep 2004 8:57 AM

Description:
My project uses picocontainer 1.1 and andromda maven plugin uses picocontainer 1.0. In plugin´s project.xml there´s a pico 1.0 depedencie declaration, but as in my project there´s a pico 1.1 declaration so I cant run it.

Okay, I´ve looked plugin code and I found:
<j:new var="pluginUtils" className="org.andromda.maven.MavenPluginUtils"/> that uses pico 1.0 and I tried to find a way to set it´s context classpath, but I could not find it (Someway like ant).

I´ve looked at project.xml and wrote "<properties><classloader>root</classloader></properties>" at pico 1.0 depedency. 
It goes perfectly... well, not so perfectly because if I run another plugin that needs pico 1.1 (like xdoclet 2.0 will soon) I got problem because when I finish to run a plugin classpath configuration does not come back to normal.

In my opinion if I write plugins depedencies should overwrite project depedencies when a plugin is running and just when its running.

I wrote a example, there is two jars on this zip, one of them is my andromda cartridge and the andromda plugin with classloader fixed.

test1 - Just run andromda plugin
test2 - Run andromda plugin and other code that uses pico 1.1.
test3 - Run a code that uses pico 1.1 and andromda plugin.

Thank´s


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MAVEN-1435) Plugin classpath are not overwriting project classpath.

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Jose Luiz (mailto:juze@mandic.com.br)
       Date: Fri, 3 Sep 2004 8:58 AM
    Comment:
test1 - Just run andromda plugin
test2 - Run andromda plugin and other code that uses pico 1.1.
test3 - Run a code that uses pico 1.1 and andromda plugin.
    Changes:
             Attachment changed to example.zip
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MAVEN-1435?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1435

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1435
    Summary: Plugin classpath are not overwriting project classpath.
       Type: Bug

     Status: Unassigned
   Priority: Critical

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven

   Assignee: 
   Reporter: Jose Luiz

    Created: Fri, 3 Sep 2004 8:57 AM
    Updated: Fri, 3 Sep 2004 8:58 AM

Description:
My project uses picocontainer 1.1 and andromda maven plugin uses picocontainer 1.0. In plugin´s project.xml there´s a pico 1.0 depedencie declaration, but as in my project there´s a pico 1.1 declaration so I cant run it.

Okay, I´ve looked plugin code and I found:
<j:new var="pluginUtils" className="org.andromda.maven.MavenPluginUtils"/> that uses pico 1.0 and I tried to find a way to set it´s context classpath, but I could not find it (Someway like ant).

I´ve looked at project.xml and wrote "<properties><classloader>root</classloader></properties>" at pico 1.0 depedency. 
It goes perfectly... well, not so perfectly because if I run another plugin that needs pico 1.1 (like xdoclet 2.0 will soon) I got problem because when I finish to run a plugin classpath configuration does not come back to normal.

In my opinion if I write plugins depedencies should overwrite project depedencies when a plugin is running and just when its running.

I wrote a example, there is two jars on this zip, one of them is my andromda cartridge and the andromda plugin with classloader fixed.

test1 - Just run andromda plugin
test2 - Run andromda plugin and other code that uses pico 1.1.
test3 - Run a code that uses pico 1.1 and andromda plugin.

Thank´s


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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

[jira] Updated: (MAVEN-1435) Plugin classpath are not overwriting project classpath.

Posted by ji...@codehaus.org.
The following issue has been updated:

    Updater: Brett Porter (mailto:brett@codehaus.org)
       Date: Tue, 21 Sep 2004 8:22 AM
    Comment:
I think this is a dupe - it requires classloader separation.
I believe we can try this in 1.1 - I've done it before, and it just requires carefully a documented break in backwards compatibility. I think the end result is worth it.
    Changes:
             Fix Version changed to 1.1
    ---------------------------------------------------------------------
For a full history of the issue, see:

  http://jira.codehaus.org/browse/MAVEN-1435?page=history

---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1435

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1435
    Summary: Plugin classpath are not overwriting project classpath.
       Type: Bug

     Status: Unassigned
   Priority: Critical

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:
             1.1

   Assignee: 
   Reporter: Jose Luiz Peleteiro

    Created: Fri, 3 Sep 2004 8:57 AM
    Updated: Tue, 21 Sep 2004 8:22 AM

Description:
My project uses picocontainer 1.1 and andromda maven plugin uses picocontainer 1.0. In plugin´s project.xml there´s a pico 1.0 depedencie declaration, but as in my project there´s a pico 1.1 declaration so I cant run it.

Okay, I´ve looked plugin code and I found:
<j:new var="pluginUtils" className="org.andromda.maven.MavenPluginUtils"/> that uses pico 1.0 and I tried to find a way to set it´s context classpath, but I could not find it (Someway like ant).

I´ve looked at project.xml and wrote "<properties><classloader>root</classloader></properties>" at pico 1.0 depedency. 
It goes perfectly... well, not so perfectly because if I run another plugin that needs pico 1.1 (like xdoclet 2.0 will soon) I got problem because when I finish to run a plugin classpath configuration does not come back to normal.

In my opinion if I write plugins depedencies should overwrite project depedencies when a plugin is running and just when its running.

I wrote a example, there is two jars on this zip, one of them is my andromda cartridge and the andromda plugin with classloader fixed.

test1 - Just run andromda plugin
test2 - Run andromda plugin and other code that uses pico 1.1.
test3 - Run a code that uses pico 1.1 and andromda plugin.

Thank´s


---------------------------------------------------------------------
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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