The following comment has been added to this issue:

     Author: Chad Brandon
    Created: Sat, 3 Apr 2004 10:59 PM
       Body:
I never moved to rc2 because of the fact that any plugin that was installed to the 
repository during the build process (one that was marked as a dependency in my 
project.xml) the goals weren't found and the build failed.  I filled a bug on this and 
you fixed it a week or so ago.  So I figured I would try out the latest rc3 build and 
now I'm running into this error.  

Our plugin is part of our over all project and basically this plugin is one of the 
first submodules installed into the local repository using plugin:install.  It is then 
used to build the rest of the project (other modules have it marked as a plugin 
dependency).  Our project builds itself (similar to Maven).  It would be nice to not 
have to install it first into the remote repository as a seperate step.  Why wouldn't 
you expect this to work?   

The strange thing is, that it does work if the plugin is not in the 
$MAVEN_HOME/plugins directory, but when its there (any subsequent build after the 
first), I get these build failures telling me it can't either parse the project.xml or 
the plugin.jelly of the plugin.
---------------------------------------------------------------------
View this comment:
  
http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-1219&page=comments#action_18149

---------------------------------------------------------------------
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: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

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

   Assignee: 
   Reporter: Chad Brandon

    Created: Sat, 3 Apr 2004 10:30 PM
    Updated: Sat, 3 Apr 2004 10:59 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: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to