RE: [m2] The packaging for this project did not assign a file to the build artifact
Hi, Can somebody please enlighten me, how I can add build artefacts in an ant-based plugin? Can it be somewhere set in the plexus/components.xml? Currently I'm getting the error: [INFO] [deploy:deploy] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The packaging for this project did not assign a file to the build artifact [INFO] This is my components.xml: org.apache.maven.lifecycle.mapping.LifecycleMapping tigerstripe-application org.apache.maven.lifecycle.mapping.DefaultLifecycleMapping ossj.jsr264:maven-tigerstripe-plugin:tigerstripe-generate--> org.apache.maven.plugins:maven-source-plugin:2.0:jar org.apache.maven.plugins:maven-install-plugin:install org.apache.maven.plugins:maven-deploy-plugin:deploy org.apache.maven.artifact.handler.ArtifactHandler tigerstripe-application org.apache.maven.artifact.handler.DefaultArtifactHandler jar tigerstripe-application Andreas >-Original Message- >From: ext >[EMAIL PROTECTED] >e.org >[mailto:[EMAIL PROTECTED] >en.apache.org] >Sent: 28 July, 2006 07:14 >To: users@maven.apache.org >Subject: Re: [m2] The packaging for this project did not >assign a file to the build artifact > >I just read the archived mail and actually have the same problem: > >http://www.mail-archive.com/users@maven.apache.org/msg36680.html > >How to assign the build artefact in a custum plugin, that is >based on ant tasks? Is there a more elegant way? > >For me, there's also an additional tweak. I'd like to assign >not what comes out of my plugin, but I'm using the >maven-source-plugin in a subsequent step in the lifecycle and >want to deploy that. > >Any hints appreciated! > >Andreas Ebbert-Karroum > Senior Software Design Engineer - Nokia Networks Services / >Middleware > phone: +49-211-94123928, fax: +49-211-94123838 > Heltorfer Straße 1, 40472 Düsseldorf, Germany > > > > >This message is confidential. If you have received this >message in error, please delete it from your system. You >should not copy it for any purpose, or disclose its contents >to any other person. Internet communications are not secure >and therefore Nokia GmbH does not accept legal responsibility >for the contents of this message as it has been transmitted >over a public network. Thank you. > >Nokia GmbH, Nokia Networks is a German Company. Further >information about the Company is available from its principal >offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany >and from the website at http://www.nokia.com/ > > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] The packaging for this project did not assign a file to the build artifact
I just read the archived mail and actually have the same problem: http://www.mail-archive.com/users@maven.apache.org/msg36680.html How to assign the build artefact in a custum plugin, that is based on ant tasks? Is there a more elegant way? For me, there's also an additional tweak. I'd like to assign not what comes out of my plugin, but I'm using the maven-source-plugin in a subsequent step in the lifecycle and want to deploy that. Any hints appreciated! Andreas Ebbert-Karroum Senior Software Design Engineer - Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-94123838 Heltorfer Straße 1, 40472 Düsseldorf, Germany This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/
Re: [m2] The packaging for this project did not assign a file to the build artifact
SOLVED --- I made one mistake in the components.xml -- the packaging element should match the role-hint element. The ANT script task (apparently) must be used to access Maven's object model -- I have used the following code in my.build.xml file: This of course requires maven-script-beanshell, bsf and ant-apache-bsf dependencies. Is there a more elegant way? E.g. using only clean ANT syntax? Adrian. Adrian Herscu wrote: > Hi all, > > I have followed the > http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html > to add custom packaging and artifact handler to my plugin. > > In the ArtifactHandler configuration section I have defined: > war > my-type > war > my-language > false > > When binding my WAR mojo to the build lifecycle, i.e. > > com.acme:my-plugin:war > > then I get a build error with the following description: > "The packaging for this project did not assign a file to the build > artifact". > > I tried to see what happens if I bind the Maven JAR mojo, i.e. > org.apache.maven.plugins:maven-jar-plugin:jar > > and changed the ArtifactHandler configuration section to: > > jar > my-type > jar > my-language > false > > > then I get a successful build but the extension type of the installed > artifact is not ".jar" but ".my-type". Why?! > > > Please help I am stuck! > > In the lifecycle guide there is a line of Java code > [project.getArtifact().setFile( new File( "target/myFile-2.0.jar" ) );] > which must be executed by the packaging goal. I have built my mojos in > ANT -- how do I accomplish this with ANT code? (I tried the ANT's > but did not work) > > ...and TIA. > Adrian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
