Re: Releasing from multiple modules
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! >> >> >> >> >> webapp-A-*war >> >> >> someNewWarFileName.war >> / >> >> false >> runtime >> >> >> >> webapp-B*war >> >> >> someOtherNewWarFileName.war >> >> / >> false >> runtime >> >> >> >> 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. >> > >> > > >> > > >> > > >> > > >> > > com.example.someGroup-A >> > > webapp-A >> > > war >> > > 1.2 >> > > >> > > >> > > >> > > com.example.someOtherGroupId-B >> > > webapp-B >> > > war >> > > 1.3 >> > > >> > > >> > > >> > >> > Should be: >> > >> > >> > >> > com.example.someGroup-A >> > webapp-A >> > war >> > 1.2 >> > >> > >> > >> > com.example.someOtherGroupId-B >> > webapp-B >> > war >> > 1.3 >> > >> > >> > >> > -- >> > 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]
Re: Releasing from multiple modules
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! webapp-A-*war someNewWarFileName.war / false runtime webapp-B*war someOtherNewWarFileName.war / false runtime 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. > > > > > > > > > > > com.example.someGroup-A > > webapp-A > > war > > 1.2 > > > > > > > > com.example.someOtherGroupId-B > > webapp-B > > war > > 1.3 > > > > > > > > Should be: > > > > com.example.someGroup-A > webapp-A > war > 1.2 > > > > com.example.someOtherGroupId-B > webapp-B > war > 1.3 > > > > -- > 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]
Re: Releasing from multiple modules
On 5/1/07, James Abley <[EMAIL PROTECTED]> wrote: 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. see http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Releasing from multiple modules
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! webapp-A-*war someNewWarFileName.war / false runtime webapp-B*war someOtherNewWarFileName.war / false runtime 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. > > > > > > > > > > > com.example.someGroup-A > > webapp-A > > war > > 1.2 > > > > > > > > com.example.someOtherGroupId-B > > webapp-B > > war > > 1.3 > > > > > > > > Should be: > > > > com.example.someGroup-A > webapp-A > war > 1.2 > > > > com.example.someOtherGroupId-B > webapp-B > war > 1.3 > > > > -- > 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]
Re: Releasing from multiple modules
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! webapp-A-*war someNewWarFileName.war / false runtime webapp-B*war someOtherNewWarFileName.war / false runtime 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. > > > > > com.example.someGroup-A > webapp-A > war > 1.2 > > > > com.example.someOtherGroupId-B > webapp-B > war > 1.3 > > > Should be: com.example.someGroup-A webapp-A war 1.2 com.example.someOtherGroupId-B webapp-B war 1.3 -- 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]
Re: Releasing from multiple modules
Relocate the dependencyManagement-part to the dependencies, I think that should do the trick. > > > > > com.example.someGroup-A > webapp-A > war > 1.2 > > > > com.example.someOtherGroupId-B > webapp-B > war > 1.3 > > > Should be: com.example.someGroup-A webapp-A war 1.2 com.example.someOtherGroupId-B webapp-B war 1.3 -- 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]
Re: Releasing from multiple modules
Hello again. So I've gone through a release cycle for all of my modules, which was a long process, and ironed out a few cycles that had crept into the dependencies. Now I am at the stage where I have two modules that create WAR files and I have pursued my original suggestion of creating another SVN / Maven2 module to package that up. I would be happy with just a zip of some form as a first draft; I can worry about integrating it with an installer at a later date. So, I have a POM like this: http://maven.apache.org/POM/4.0.0"; xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> com.example master-pom 1 4.0.0 com.example.installer the-installer pom 1.0-SNAPSHOT My Company Platform Installer http://maven.apache.org com.example.someGroup-A webapp-A war 1.2 com.example.someOtherGroupId-B webapp-B war 1.3 maven-assembly-plugin src/main/assembly/dep.xml I have a simple assembly configuration - src/main/assembly/dep.xml: zip false / .project src/main/assembly/** target/archive-tmp/** / true runtime The two WARs are installed into our internal repository (and in my local repository), but no request is made to retrieve them. What am I missing? Cheers, James On 25/04/07, James Abley <[EMAIL PROTECTED]> wrote: Thanks for that link, that does seem very useful to know. Any comments on my suggested approach of releasing content? I'm trying to understand what Maven buys me by using the mvn release:prepare approach. Cheers, James On 25/04/07, Damien Lecan <[EMAIL PROTECTED]> wrote: > > I'm fairly new to Maven2 and haven't used it much in situations more > > complex than those described in the documentation. But now I have hit > > an issue that I haven't been able to find much documentation on this > > subject[1] > > http://docs.codehaus.org/display/MAVENUSER/How+to+handle+releases+with+multiple+SNAPSHOT+dependents > > Use version range ? > http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution > > Damien > > - > 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]
Re: Releasing from multiple modules
Thanks for that link, that does seem very useful to know. Any comments on my suggested approach of releasing content? I'm trying to understand what Maven buys me by using the mvn release:prepare approach. Cheers, James On 25/04/07, Damien Lecan <[EMAIL PROTECTED]> wrote: > I'm fairly new to Maven2 and haven't used it much in situations more > complex than those described in the documentation. But now I have hit > an issue that I haven't been able to find much documentation on this > subject[1] > http://docs.codehaus.org/display/MAVENUSER/How+to+handle+releases+with+multiple+SNAPSHOT+dependents Use version range ? http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution Damien - 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]
Re: Releasing from multiple modules
I'm fairly new to Maven2 and haven't used it much in situations more complex than those described in the documentation. But now I have hit an issue that I haven't been able to find much documentation on this subject[1] http://docs.codehaus.org/display/MAVENUSER/How+to+handle+releases+with+multiple+SNAPSHOT+dependents Use version range ? http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+and+Conflict+Resolution Damien - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
