And can someone please explain the difference in application.properties, profile.xml, and settings.xml?

---
Thank You
Mick Knutson

Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com

Washington Mutual (WAMU) (Emeryville, California)
---




From: "Mick Knutson" <[EMAIL PROTECTED]>
Reply-To: "Maven Users List" <[email protected]>
To: [email protected]
Subject: [m202] Still confused as to a solution to complex versioning
Date: Thu, 23 Feb 2006 15:10:46 -0800

I started creating a profile for my build like:
   <profile>
       <id>1.3.5_6</id>
       <properties>
           <coreVersion>1.1.4_4</coreVersion>
           <commonVersion>1.0_1</commonVersion>
           <lksmWarVersion>1.3.5_6</lksmWarVersion>
           <nytWarVersion>1.2.2_1</nytWarVersion>

           <earVersion>1.3.5_6</earVersion>
       </properties>
   </profile>


I have a master pom and ear that share the same version number (1.3.5_6) and then 5 modules that have different versions from that.
We need the ability to deploy the following:


1.3.5_6.ear contains: core-1.1.4_4, common-1.0_1, lksm-1.3.5_6.war, and nyt-1.2.2_1.war

then rollback the core version and deploy:
1.3.5_7.ear contains: core-1.1.4_3, common-1.0_2, lksm-1.3.5_7.war, and nyt-1.2.2_2.war

then include the latest of everything:
1.3.5_8.ear contains: core-1.1.4_5, common-1.0_3, lksm-1.3.5_7.war, and nyt-1.2.2_2.war


But with this, there is the issue of keeping the version numbers updated in 8 different pom's.

There must be some way to help me centralize this. Help?


---
Thank You
Mick Knutson

Sr. Java/J2EE Consultant
BASE logic, inc.
(415) 648-1804 (S.F., CA)
http://www.BASELogic.com

Washington Mutual (WAMU) (Emeryville, California)
---



---------------------------------------------------------------------
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]

Reply via email to