Thanks, that's what I was missing. Cheers,
James On 01/05/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
To deploy the resulting artifact that isn't attached to the install/deploy phase, you need to attach it. You can use the build helper plugin: http://mojo.codehaus.org/build-helper-maven-plugin/howto.html If it's an assembly, you can use the attached goal from the assembly plugin. Emmanuel James Abley a écrit : > Sorry, another follow-up. > > Is there a clean way to deploy the resulting zip file into a repository? > > http://maven.apache.org/pom.html#maven_coordinates > > The specified packaging types imply that it isn't possible. > > Similarly, this indicates that the discussion is still on-going. > > http://jira.codehaus.org/browse/MNG-1683 > > Otherwise, I have a locally built zip file which I have to manually > deploy into our internal repository, which would seem to be the wrong > way to do it. > > Cheers, > > James > > > On 30/04/07, James Abley <[EMAIL PROTECTED]> wrote: >> Excellent. That's getting the WAR files into the Zip. >> >> I could then do a little tweak to rename my war files to something >> more consistent with the installation documentation I'm about to >> write! >> >> <dependencySets> >> <dependencySet> >> <includes> >> <include>webapp-A-*war</include> >> </includes> >> >> <outputFileNameMapping>someNewWarFileName.war</outputFileNameMapping> >> <outputDirectory>/</outputDirectory> >> <!-- Don't extract the war files - leave them as they are --> >> <unpack>false</unpack> >> <scope>runtime</scope> >> </dependencySet> >> <dependencySet> >> <includes> >> <include>webapp-B*war</include> >> </includes> >> >> <outputFileNameMapping>someOtherNewWarFileName.war</outputFileNameMapping> >> >> <outputDirectory>/</outputDirectory> >> <unpack>false</unpack> >> <scope>runtime</scope> >> </dependencySet> >> </dependencySets> >> >> Thanks for your help. >> >> Cheers, >> >> James >> >> On 30/04/07, Roland Asmann <[EMAIL PROTECTED]> wrote: >> > Relocate the dependencyManagement-part to the dependencies, I think >> that >> > should do the trick. >> > >> > > <dependencies /> >> > > <dependencyManagement> >> > > <dependencies> >> > > <dependency> >> > > <groupId>com.example.someGroup-A</groupId> >> > > <artifactId>webapp-A</artifactId> >> > > <type>war</type> >> > > <version>1.2</version> >> > > <scope></scope> >> > > </dependency> >> > > <dependency> >> > > <groupId>com.example.someOtherGroupId-B</groupId> >> > > <artifactId>webapp-B</artifactId> >> > > <type>war</type> >> > > <version>1.3</version> >> > > </dependency> >> > > </dependencies> >> > > </dependencyManagement> >> > >> > Should be: >> > >> > <dependencies> >> > <dependency> >> > <groupId>com.example.someGroup-A</groupId> >> > <artifactId>webapp-A</artifactId> >> > <type>war</type> >> > <version>1.2</version> >> > <scope></scope> >> > </dependency> >> > <dependency> >> > <groupId>com.example.someOtherGroupId-B</groupId> >> > <artifactId>webapp-B</artifactId> >> > <type>war</type> >> > <version>1.3</version> >> > </dependency> >> > </dependencies> >> > >> > -- >> > Roland Asmann >> > >> > CFC Informationssysteme Entwicklungsgesellschaft m.b.H >> > Bäckerstrasse 1/2/7 >> > A-1010 Wien >> > FN 266155f, Handelsgericht Wien >> > >> > Tel.: +43/1/513 88 77 - 27 >> > Fax.: +43/1/513 88 62 >> > Email: [EMAIL PROTECTED] >> > Web: www.cfc.at >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
