You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "Bob Allison (JIRA)" <ji...@codehaus.org> on 2005/08/19 16:12:08 UTC
[jira] Created: (MNG-755) Running "m2 -fae" does not use POM or reactor
Running "m2 -fae" does not use POM or reactor
---------------------------------------------
Key: MNG-755
URL: http://jira.codehaus.org/browse/MNG-755
Project: Maven 2
Type: Bug
Versions: 2.0-beta-1
Environment: SVN revision 233464 on Linux
Reporter: Bob Allison
I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
[INFO] ----------------------------------------------------------------------------
[INFO] Building Maven Default Project
[INFO] task-segment: [clean:clean, package, site:site]
[INFO] ----------------------------------------------------------------------------
even though I have a different name in the POM.
A little later, the build fails with:
[INFO] [jar:jar]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] ----------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ----------------------------------------------------------------------------
[INFO] Diagnosis: Error assembling JAR
[INFO] ----------------------------------------------------------------------------
[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.lang.NullPointerException
at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
... 16 more
which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Running "m2 -fae" does not use POM or reactor
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=all ]
Brett Porter updated MNG-755:
-----------------------------
Fix Version: 2.0-beta-1
what is the bug you are reporting here? that -fae doesn't work (ie it didn't fail at the end), or that you got a NPE in the jar building?
For the first one - try --fail-at-end. I believe that the short options don't work and will be removed before the next release
For the NPE, please report a new bug based on that (though if it is just a POM, set packaging = pom and it should work).
> Running "m2 -fae" does not use POM or reactor
> ---------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Fix For: 2.0-beta-1
>
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Remove the dysfunctional command line arguments
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=all ]
Brett Porter updated MNG-755:
-----------------------------
Assign To: Brett Porter
> Remove the dysfunctional command line arguments
> -----------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Remove the dysfunctional command line arguments
Posted by "Kenney Westerhof (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=all ]
Kenney Westerhof closed MNG-755:
--------------------------------
Assign To: Kenney Westerhof (was: Brett Porter)
Resolution: Fixed
Fixed in svn revision 279574 by using GnuParser instead of PosixParser.
> Remove the dysfunctional command line arguments
> -----------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Assignee: Kenney Westerhof
> Priority: Critical
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Remove the dysfunctional command line arguments
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=all ]
Brett Porter updated MNG-755:
-----------------------------
Remaining Estimate: 1 hour
Original Estimate: 3600
> Remove the dysfunctional command line arguments
> -----------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Assignee: Brett Porter
> Priority: Critical
> Fix For: 2.0-beta-1
>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Remove the disfunctional command line arguments
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=all ]
Brett Porter updated MNG-755:
-----------------------------
Component: maven-core
Summary: Remove the disfunctional command line arguments (was: Running "m2 -fae" does not use POM or reactor)
renaming - basically CLI doesn't support command line arguments like "-fae". It needs a one letter version. I'd prefer none at all for these, but CLI doesn't support more than one of those either. Maybe the repaired cli-1.0 will work now.
> Remove the disfunctional command line arguments
> -----------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Fix For: 2.0-beta-1
>
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Remove the dysfunctional command line arguments
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=all ]
Brett Porter updated MNG-755:
-----------------------------
Priority: Critical (was: Major)
Summary: Remove the dysfunctional command line arguments (was: Remove the disfunctional command line arguments)
> Remove the dysfunctional command line arguments
> -----------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Components: maven-core
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Priority: Critical
> Fix For: 2.0-beta-1
>
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Running "m2 -fae" does not use POM or reactor
Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=comments#action_44747 ]
Bob Allison commented on MNG-755:
---------------------------------
It looks like "m2 -fn" exhibits the same behavior.
> Running "m2 -fae" does not use POM or reactor
> ---------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
>
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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-755) Running "m2 -fae" does not use POM or reactor
Posted by "Bob Allison (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MNG-755?page=comments#action_44949 ]
Bob Allison commented on MNG-755:
---------------------------------
I wasn't sure if this was one bug or two. I did not know if the NPE was a result of using the "Default Maven Project" or something different.
Using --fail-at-end instead of -fae causes the build to use the POM in the directory rather than a default POM. I also do not get the NPE. I guess this can be closed since the whole thing was caused by using the documented but disfunctional command line options.
> Running "m2 -fae" does not use POM or reactor
> ---------------------------------------------
>
> Key: MNG-755
> URL: http://jira.codehaus.org/browse/MNG-755
> Project: Maven 2
> Type: Bug
> Versions: 2.0-beta-1
> Environment: SVN revision 233464 on Linux
> Reporter: Bob Allison
> Fix For: 2.0-beta-1
>
>
> I ran "m2 -fae clean:clean package site:site" on my top level package to clean up all targets, rebuild the artifacts, and generate a site for every project (I used -fae since I have a problem building the site in one sub-project). The banner displayed when it started processing was:
> [INFO] ----------------------------------------------------------------------------
> [INFO] Building Maven Default Project
> [INFO] task-segment: [clean:clean, package, site:site]
> [INFO] ----------------------------------------------------------------------------
> even though I have a different name in the POM.
> A little later, the build fails with:
> [INFO] [jar:jar]
> [WARNING] JAR will be empty - no content was marked for inclusion!
> [INFO] ----------------------------------------------------------------------------
> [ERROR] BUILD ERROR
> [INFO] ----------------------------------------------------------------------------
> [INFO] Diagnosis: Error assembling JAR
> [INFO] ----------------------------------------------------------------------------
> [ERROR] Cause:
> org.apache.maven.plugin.MojoExecutionException: Error assembling JAR
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:107)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:364)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:470)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:443)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:429)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:266)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:125)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:186)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:316)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: java.lang.NullPointerException
> at org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:238)
> at org.apache.maven.plugin.jar.JarMojo.execute(JarMojo.java:100)
> ... 16 more
> which is caused by not having any sources in the project (since it is a POM project). The build also did not run any of the modules.
--
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