Hi, I looked for myself - otherwise i would not adress to the mailing-list or and I wouldn´t have found the JIRA issues concerning that problem... Thanx for your "hint" - but there´s nothing about "empty jar" on this page - i guess you mean "forceCreation" - but that doesn´t change the behaviour.
=> So again - is there a solution, please ? Thanx, Torsten "Stephen Connolly" <[EMAIL PROTECTED]> 09.12.2008 10:08 Bitte antworten an "Maven Users List" <[email protected]> An "Maven Users List" <[email protected]> Kopie Thema Re: Re: Build fails for an empty test-jar with maven-jar-plugin 2.2 Did you even try looking for yourself... hint: it's on this page: http://maven.apache.org/plugins/maven-jar-plugin/test-jar-mojo.html 2008/12/9 <[EMAIL PROTECTED]> > ...and what´s the parameters name and options? > > Thanx, Torsten > > > > > "Stephen Connolly" <[EMAIL PROTECTED]> > 08.12.2008 12:52 > Bitte antworten an > "Maven Users List" <[email protected]> > > > An > "Maven Users List" <[email protected]> > Kopie > > Thema > Re: Build fails for an empty test-jar with maven-jar-plugin 2.2 > > > > > > > afaik there is a parameter you can set to allow empty jars > > 2008/12/8 <[EMAIL PROTECTED]> > > > Hi, > > > > I have a parent pom.xml with packaging "pom" and some child modules in > the > > <modules> section, defining: > > > > <build> > > <plugins> > > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-jar-plugin</artifactId> > > <version>2.2</version> > > > > <configuration> > > <archive> > > <addMavenDescriptor>false</addMavenDescriptor> > > </archive> > > </configuration> > > <executions> > > <execution> > > <goals> > > <goal>test-jar</goal> > > </goals> > > </execution> > > </executions> > > </plugin> > > > > When I switch from 2.1 to 2.2 to get rid of > > http://jira.codehaus.org/browse/MJAR-30, I now get > > > > [ERROR] BUILD ERROR > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Error assembling JAR > > > > Embedded error: You must set at least one file. > > [INFO] > > ------------------------------------------------------------------------ > > [INFO] Trace > > org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling > > JAR > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583) > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499) > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478) > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) > > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) > > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) > > at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) > > 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: org.apache.maven.plugin.MojoExecutionException: Error > > assembling JAR > > at > > > > > > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:225) > > at > > > > > > org.apache.maven.plugin.jar.AbstractJarMojo.execute(AbstractJarMojo.java:237) > > at > > org.apache.maven.plugin.jar.TestJarMojo.execute(TestJarMojo.java:85) > > at > > > > > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451) > > at > > > > > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558) > > ... 16 more > > Caused by: org.codehaus.plexus.archiver.ArchiverException: You must set > at > > least one file. > > at > > > > > > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.createArchiveMain(AbstractZipArchiver.java:260) > > at > > > > > > org.codehaus.plexus.archiver.zip.AbstractZipArchiver.execute(AbstractZipArchiver.java:242) > > at > > > > > > org.codehaus.plexus.archiver.AbstractArchiver.createArchive(AbstractArchiver.java:673) > > at > > > > > > org.apache.maven.archiver.MavenArchiver.createArchive(MavenArchiver.java:421) > > at > > > > > > org.apache.maven.plugin.jar.AbstractJarMojo.createArchive(AbstractJarMojo.java:218) > > ... 20 more > > > > > > I guess this is the same issue mentioned in > > http://jira.codehaus.org/browse/MJAR-105 - except for the packaging type > > and the goal? > > Will there a fix be available, soon ? Or at least a workaround in the > > meantime ? > > > > Thanx very much, Torsten > > > >
