Sure, looks like the change over to the nicer manifest writer omitted the call to mkdirs for the target location.
Log an issue and I'll schedule it for 2.5.1 (the vote for 2.5.0 is already in progress) On 23 Jun 2014 00:48, "Mark Derricutt" <[email protected]> wrote: > On 16 Jun 2014, at 22:14, Stuart McCulloch wrote: > > bnd 2.3.0, and it would >> be great if people could perform some early smoke testing on the current >> snapshot before we stage the next release. >> > > In the one project I bumped to this I'm seeing the following: > > [ERROR] Error trying to write Manifest to file /Users/amrk/IdeaProjects/ > securemx/smx3/com.smxemail.rest/target/classes/META-INF/MANIFEST.MF > java.io.FileNotFoundException: /Users/amrk/IdeaProjects/ > securemx/smx3/com.smxemail.rest/target/classes/META-INF/MANIFEST.MF (No > such file or directory) > at java.io.FileOutputStream.open(Native Method) > at java.io.FileOutputStream.<init>(FileOutputStream.java:206) > at java.io.FileOutputStream.<init>(FileOutputStream.java:156) > at org.apache.felix.bundleplugin.BundlePlugin.execute( > BundlePlugin.java:431) > at org.apache.felix.bundleplugin.BundlePlugin.execute( > BundlePlugin.java:291) > at org.apache.felix.bundleplugin.BundlePlugin.execute( > BundlePlugin.java:282) > at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo( > DefaultBuildPluginManager.java:132) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute( > MojoExecutor.java:208) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute( > MojoExecutor.java:153) > at org.apache.maven.lifecycle.internal.MojoExecutor.execute( > MojoExecutor.java:145) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > buildProject(LifecycleModuleBuilder.java:116) > at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder. > buildProject(LifecycleModuleBuilder.java:80) > at org.apache.maven.lifecycle.internal.builder.singlethreaded. > SingleThreadedBuilder.build(SingleThreadedBuilder.java:51) > at org.apache.maven.lifecycle.internal.LifecycleStarter. > execute(LifecycleStarter.java:120) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:347) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:154) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:213) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:157) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke( > NativeMethodAccessorImpl.java:57) > at sun.reflect.DelegatingMethodAccessorImpl.invoke( > DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:491) > at org.codehaus.plexus.classworlds.launcher.Launcher. > launchEnhanced(Launcher.java:289) > at org.codehaus.plexus.classworlds.launcher.Launcher. > launch(Launcher.java:229) > at org.codehaus.plexus.classworlds.launcher.Launcher. > mainWithExitCode(Launcher.java:415) > at org.codehaus.plexus.classworlds.launcher.Launcher. > main(Launcher.java:356) > > After a "clean install" the target/classes/META-INF directory doesn't > exist - shall I raise this in JIRA somewhere? > > Mark > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
