[jira] Closed: (MAVEN-1219) Goals from plugin dependencies fail if the plugin is installed as part of the build process

[ji...@codehaus.org]

Message:

   The following issue has been closed.

   Resolver: Brett Porter
       Date: Tue, 27 Apr 2004 11:32 PM

 fixed.

Here's the catch: so I didn't break any existing behaviour, I have implemented this as a new goal.

use plugin:install-now instead of plugin:install and this should work. It will install it in the user plugin cache instead of the maven installation, and into the running instance.

If you need it to install into the global maven instance for later invocations by other users, you can use plugin:install and plugin:install-now in conjunction.
---------------------------------------------------------------------
View the issue:
  http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: MAVEN-1219
    Summary: Goals from plugin dependencies fail if the plugin is installed as part of the build process
       Type: Bug

     Status: Closed
   Priority: Major
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

    Project: maven
   Fix Fors:
             1.0-rc3
   Versions:
             1.0-rc3

   Assignee: Brett Porter
   Reporter: Chad Brandon

    Created: Sat, 3 Apr 2004 10:30 PM
    Updated: Tue, 27 Apr 2004 11:32 PM
Environment: Windows XP, JDK 1.4.2_03

Description:
I have a project consisting of multiple subprojects.  One of these subprojects includes a plugin which is built and installed via "plugin:install" during my project build.  A goal is then used from this previously installed plugin to build the rest of the project's subprojects (in other words other subprojects have a dependency on this plugin which is installed during the build process).  

Using maven-rc1 this used to be no problem, but as of yesterday (I checked out and built MAVEN-1_0_Branch) using rc3 this fails.  If the plugin doesn't already exist in the ${maven.home}/plugins directory things work fine (if I delete the plugin out before the build starts), the plugin is installed and other subprojects needing to use goal(s) from this plugin find it and the build completes successfully.  But if the plugin already exists in ${maven.home}/plugins, I'll get something like below telling me it can't parse the project.xml, when it fact that file does exist, or I sometimes get a message telling me the plugin.jelly from that plugin can't be found: 

BUILD FAILED
File...... file:/H:/Documents and Settings/Administrator/.maven/plugins/maven-multiproject-plugin-1.2/plugin.jelly
Element... maven:reactor
Line...... 202
Column.... 9
Unable to obtain goal [multiproject:install-callback] -- file:/I:/java/eclipse/andromda-all/metafacades/uml/maven.xml:17
:42: <attainGoal> Error parsing project.xml 'H:\Documents and Settings\Administrator\.maven\plugins\maven-andromda-plugi
n-3.0-SNAPSHOT\project.xml'
Total time: 23 seconds


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