You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2005/10/05 02:27:11 UTC

[jira] Created: (MNG-1089) apparent race condition when installing a plugin and executing the same plugin in a single build session

apparent race condition when installing a plugin and executing the same plugin in a single build session
--------------------------------------------------------------------------------------------------------

         Key: MNG-1089
         URL: http://jira.codehaus.org/browse/MNG-1089
     Project: Maven 2
        Type: Bug
  Components: maven-plugin-plugin, maven-core  
    Versions: 2.0-beta-3    
 Reporter: John Casey
 Assigned to: John Casey 
     Fix For: 2.0-beta-4


Steps to reproduce:

go into <maven>/maven-core-it/it0013

execute:

m2 -cpl -e clean:clean install it0013:it0013

The first time around (if you have a clean local repo WRT it0013), it should simply install the plugin, and run it. HOWEVER, subsequent runs will intermittently result in an NPE in java.util.jar.JarFile. I believe this is a result of initializing the plugin container for it0013:it0013 early in the lifecycle executor in order to determine whether this mojo is an aggregator. When the install mojo completes, it will have overwritten the original artifact file used in this plugin container's classpath. I *think* this is what's causing the problem, though I can't exactly work out why it's intermittent.

At any rate, we need to address this.

-- 
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


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


[jira] Updated: (MNG-1089) apparent race condition when installing a plugin and executing the same plugin in a single build session

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1089?page=all ]

John Casey updated MNG-1089:
----------------------------

    Remaining Estimate: 2 hours
     Original Estimate: 7200

just going to implement plugin container reloading for now. This should take care of any updates to plugin (or dependency) artifacts.

> apparent race condition when installing a plugin and executing the same plugin in a single build session
> --------------------------------------------------------------------------------------------------------
>
>          Key: MNG-1089
>          URL: http://jira.codehaus.org/browse/MNG-1089
>      Project: Maven 2
>         Type: Bug
>   Components: maven-plugin-plugin, maven-core
>     Versions: 2.0-beta-3
>     Reporter: John Casey
>     Assignee: John Casey
>      Fix For: 2.0-beta-4

>
> Original Estimate: 2 hours
>         Remaining: 2 hours
>
> Steps to reproduce:
> go into <maven>/maven-core-it/it0013
> execute:
> m2 -cpl -e clean:clean install it0013:it0013
> The first time around (if you have a clean local repo WRT it0013), it should simply install the plugin, and run it. HOWEVER, subsequent runs will intermittently result in an NPE in java.util.jar.JarFile. I believe this is a result of initializing the plugin container for it0013:it0013 early in the lifecycle executor in order to determine whether this mojo is an aggregator. When the install mojo completes, it will have overwritten the original artifact file used in this plugin container's classpath. I *think* this is what's causing the problem, though I can't exactly work out why it's intermittent.
> At any rate, we need to address this.

-- 
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


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


[jira] Commented: (MNG-1089) apparent race condition when installing a plugin and executing the same plugin in a single build session

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
    [ http://jira.codehaus.org/browse/MNG-1089?page=comments#action_48262 ] 

John Casey commented on MNG-1089:
---------------------------------

discussion page on confluence here:

http://docs.codehaus.org/display/MAVEN/Building+and+Using+Plugins+From+a+Single+Maven+Session

> apparent race condition when installing a plugin and executing the same plugin in a single build session
> --------------------------------------------------------------------------------------------------------
>
>          Key: MNG-1089
>          URL: http://jira.codehaus.org/browse/MNG-1089
>      Project: Maven 2
>         Type: Bug
>   Components: maven-plugin-plugin, maven-core
>     Versions: 2.0-beta-3
>     Reporter: John Casey
>     Assignee: John Casey
>      Fix For: 2.0-beta-4

>
>
> Steps to reproduce:
> go into <maven>/maven-core-it/it0013
> execute:
> m2 -cpl -e clean:clean install it0013:it0013
> The first time around (if you have a clean local repo WRT it0013), it should simply install the plugin, and run it. HOWEVER, subsequent runs will intermittently result in an NPE in java.util.jar.JarFile. I believe this is a result of initializing the plugin container for it0013:it0013 early in the lifecycle executor in order to determine whether this mojo is an aggregator. When the install mojo completes, it will have overwritten the original artifact file used in this plugin container's classpath. I *think* this is what's causing the problem, though I can't exactly work out why it's intermittent.
> At any rate, we need to address this.

-- 
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


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


[jira] Closed: (MNG-1089) apparent race condition when installing a plugin and executing the same plugin in a single build session

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1089?page=all ]
     
John Casey closed MNG-1089:
---------------------------

    Resolution: Fixed

reloading plugin container when plugin artifact changes.

> apparent race condition when installing a plugin and executing the same plugin in a single build session
> --------------------------------------------------------------------------------------------------------
>
>          Key: MNG-1089
>          URL: http://jira.codehaus.org/browse/MNG-1089
>      Project: Maven 2
>         Type: Bug
>   Components: maven-plugin-plugin, maven-core
>     Versions: 2.0-beta-3
>     Reporter: John Casey
>     Assignee: John Casey
>      Fix For: 2.0-beta-4

>
> Original Estimate: 6 hours
>        Time Spent: 6 hours
>         Remaining: 0 minutes
>
> Steps to reproduce:
> go into <maven>/maven-core-it/it0013
> execute:
> m2 -cpl -e clean:clean install it0013:it0013
> The first time around (if you have a clean local repo WRT it0013), it should simply install the plugin, and run it. HOWEVER, subsequent runs will intermittently result in an NPE in java.util.jar.JarFile. I believe this is a result of initializing the plugin container for it0013:it0013 early in the lifecycle executor in order to determine whether this mojo is an aggregator. When the install mojo completes, it will have overwritten the original artifact file used in this plugin container's classpath. I *think* this is what's causing the problem, though I can't exactly work out why it's intermittent.
> At any rate, we need to address this.

-- 
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


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


[jira] Updated: (MNG-1089) apparent race condition when installing a plugin and executing the same plugin in a single build session

Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MNG-1089?page=all ]

John Casey updated MNG-1089:
----------------------------

    Remaining Estimate: 6 hours  (was: 2 hours)
     Original Estimate: 21600  (was: 7200)

adding time to account for design/discovery for implied plugin dependencies (implied by the packaging of a project).

> apparent race condition when installing a plugin and executing the same plugin in a single build session
> --------------------------------------------------------------------------------------------------------
>
>          Key: MNG-1089
>          URL: http://jira.codehaus.org/browse/MNG-1089
>      Project: Maven 2
>         Type: Bug
>   Components: maven-plugin-plugin, maven-core
>     Versions: 2.0-beta-3
>     Reporter: John Casey
>     Assignee: John Casey
>      Fix For: 2.0-beta-4

>
> Original Estimate: 6 hours
>         Remaining: 6 hours
>
> Steps to reproduce:
> go into <maven>/maven-core-it/it0013
> execute:
> m2 -cpl -e clean:clean install it0013:it0013
> The first time around (if you have a clean local repo WRT it0013), it should simply install the plugin, and run it. HOWEVER, subsequent runs will intermittently result in an NPE in java.util.jar.JarFile. I believe this is a result of initializing the plugin container for it0013:it0013 early in the lifecycle executor in order to determine whether this mojo is an aggregator. When the install mojo completes, it will have overwritten the original artifact file used in this plugin container's classpath. I *think* this is what's causing the problem, though I can't exactly work out why it's intermittent.
> At any rate, we need to address this.

-- 
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


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