You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Jason Grant (JIRA)" <ji...@codehaus.org> on 2005/08/07 15:45:57 UTC
[jira] Created: (MNG-709) AssemblyMojo.execute() no longer gets invoked from pom
AssemblyMojo.execute() no longer gets invoked from pom
------------------------------------------------------
Key: MNG-709
URL: http://jira.codehaus.org/browse/MNG-709
Project: Maven 2
Type: Bug
Components: maven-plugins
Versions: 2.0-beta-1
Environment: linux fedora core 3
Reporter: Jason Grant
The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
<build>
<plugins>
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-assembly-plugin</artifactId>
<configuration>
<descriptor>src/assemble/zip-source.xml</descriptor>
</configuration>
<executions>
<execution>
<!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
<!--phase>package</phase-->
<goals>
<goal>assembly</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44287 ]
John Casey commented on MNG-709:
--------------------------------
which one should win? the @execute phase="package" or the <phase>package</phase>? Since the assembly mojo declares that it needs to have the package phase completed before running, I think it would be safer to defer to the mojo developer and forget about binding it to the package phase...maybe handle it as an addendum after the package phase has been run or something...
This is vague because I'm still wrapping my brain around the problem...am I missing something?
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44315 ]
John Casey commented on MNG-709:
--------------------------------
so you're saying you would like to be able to create an assembly as part of the generate-sources phase?? I'm not sure I understand why you'd ever want to do that. I thought the premise of the assembly plugin was to repackage a completed build with it's dependencies and/or other companion files into the sort of distribution file, akin to a war or ear...is that an incorrect assumption? If you're creating an assembly during generate-sources, would it be better to separate the creation of that assembly into a separate project, then depend on that project's result?
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) AssemblyMojo.execute() no longer gets invoked from pom
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=all ]
Brett Porter updated MNG-709:
-----------------------------
Priority: Blocker (was: Major)
> AssemblyMojo.execute() no longer gets invoked from pom
> ------------------------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44587 ]
John Casey commented on MNG-709:
--------------------------------
Just modified to detect whether the current mojo (the forking mojo) exists at an earlier phase of the lifecycle than the phase it's trying to execute in the forked build...then throw a LifecycleExecutionException if this is the case.
Not sure how to improve on this currently...I'd like to print a warning and adjust the build behavior to allow execution to proceed, but I'm not entirely sure how to do this safely. I'll have to keep looking.
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) AssemblyMojo.execute() no longer gets invoked from pom
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44209 ]
John Casey commented on MNG-709:
--------------------------------
is anyone working on this? thought I saw a reference to this issue and some work being done on it via the source-attachment issue...
> AssemblyMojo.execute() no longer gets invoked from pom
> ------------------------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) AssemblyMojo.execute() no longer gets invoked from pom
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=all ]
Brett Porter updated MNG-709:
-----------------------------
Fix Version: 2.0-beta-1
> AssemblyMojo.execute() no longer gets invoked from pom
> ------------------------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=all ]
John Casey closed MNG-709:
--------------------------
Resolution: Fixed
Fork-caller is removed from the forked lifecycle, and allowed to execute after the forked lifecycle returns. This will remove any possibility of the caller being reinvoked recursively inside of forked lifecycles.
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=all ]
Brett Porter updated MNG-709:
-----------------------------
Summary: lifecycle can end up in an infinite loop (was: AssemblyMojo.execute() no longer gets invoked from pom)
the exclusion of phase was a misunderstanding, but the problem we have here is that it should be possible to bind the assembly mojo to the package phase, but also run it from the command line and get the package phase called. This is closely related to the artifact attachement bug comments.
While adding the cliOnly feature or similar will account for that, we should prevent infinite loops which was the other part of this bug. We should simply not rerun the second time, not throw an error.
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "John Casey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44637 ]
John Casey commented on MNG-709:
--------------------------------
added a warning when it actually has to remove the mojo in this way...
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "Jason Grant (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44343 ]
Jason Grant commented on MNG-709:
---------------------------------
Yes, you're right; depending on a separate dedicated project is the way to go. For some reason, I had it in my head that maven would sweep each phase across all projects before proceeding to the next phase, but's its clear that the build system cannot work like this when dependencies are catered for. My misunderstanding. Maybe I should have a go at updating the lifecycle or dependency pages to make this explicit for noobs like me. 8-)
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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-709) lifecycle can end up in an infinite loop
Posted by "Jason Grant (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-709?page=comments#action_44293 ]
Jason Grant commented on MNG-709:
---------------------------------
Would that approach allow me to specify, say, <phase>generate-sources</phase> if I wanted to create some zips for inclusion into tests, etc.?
WRT your question about anyone else working on this - I'm not game to fiddle about with classes like DefaultLifecycleExecutor just yet, so I'll work on the assembly stuff, as described in #MNG-483 and #MNG-723.
> lifecycle can end up in an infinite loop
> ----------------------------------------
>
> Key: MNG-709
> URL: http://jira.codehaus.org/browse/MNG-709
> Project: Maven 2
> Type: Bug
> Components: maven-plugins
> Versions: 2.0-beta-1
> Environment: linux fedora core 3
> Reporter: Jason Grant
> Assignee: John Casey
> Priority: Blocker
> Fix For: 2.0-beta-1
>
>
> The pom source below used to work for alpha-3 subject to the comment about phase. I just built maven2 from the trunk head, and AssemblyMojo.execute() no longer gets called. If I call it from the command-line, it works fine. Interestingly, if I uncomment the phase clause, the m2 script goes into an infinite loop.
> <build>
> <plugins>
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-assembly-plugin</artifactId>
> <configuration>
> <descriptor>src/assemble/zip-source.xml</descriptor>
> </configuration>
> <executions>
> <execution>
> <!-- Bug in alpha: phase was not defined in the mojo javadoc so we need the element below -->
> <!--phase>package</phase-->
> <goals>
> <goal>assembly</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
> </plugins>
> </build>
--
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