1. because release reads the xml into memory, modifies a bunch of stuff and rewrites it. This is the cause of a bunch of jiras because formatting, comments, etc are removed. 2. Can't 3. You can use a dependencyManagement section in a common pom. Then in the child poms, you don't specify the version and maven will find it in the depmgt section.
Also, you currently need to have svn command line installed for release to work. That would be the source of 'svn' is not recognized as an internal or external command. Release is nice for simple cases when it works, but I'm not able to use it for a bunch of reasons. I looked at the code to see if I could fix some, but it's pretty complicated with all the things it actually does. -----Original Message----- From: Mick Knutson [mailto:[EMAIL PROTECTED] Sent: Monday, February 27, 2006 7:46 PM To: [email protected] Subject: Re: [m202] 'svn' is not recognized as an internal or external command Importance: High OK, I changed my ':' to '|' in my scn declaration. I ran the validate, and everything was good. However, what my goal was to get scn|svn working so that i could release develpment builds. So I was forced to rename all my modules to ${app.version}-SNAPSHOT to get it to work. Then, all hell is breaking loose. I have added a ./profiles.xml to contain my verion parameters like: <profile> <id>local_furlm2</id> <properties> <target.server>local</target.server> <!--=============================--> <furl.version>1.3.5_7-SNAPSHOT</furl.version> <!--=============================--> <common.version>1.0_1-SNAPSHOT</common.version> <core.version>1.1.4_4-SNAPSHOT</core.version> <looksmart.version>1.3.5_7-SNAPSHOT</looksmart.version> <nyt.version>1.2.2_1-SNAPSHOT</nyt.version> </properties> </profile> Then I make my actual declarations in my pom.xml like this: <dependency> <groupId>com.furl.common</groupId> <artifactId>common-jar</artifactId> <version>${common.version}</version> <type>jar</type> </dependency> <dependency> <groupId>com.furl.common</groupId> <artifactId>common-managers</artifactId> <version>${common.version}</version> <type>jar</type> </dependency> ...etc.... But, when I run mvn release:prepare, everyone of my pom.sml's are completely modified. They are re-formatted, contain duplicate blocks of code and ${furl.version} is truncated to ${furl 1. why is my code modifed? 2. How can I stop it? 2b. If I can't, how can I centralize my build version numbers so that I can have a single profile that contains the combination matrix of artifacts inside my deliverable? --- 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: "dan tran" <[EMAIL PROTECTED]> >Reply-To: "Maven Users List" <[email protected]> >To: "Maven Users List" <[email protected]> >Subject: Re: [m202] 'svn' is not recognized as an internal or external >command >Date: Mon, 27 Feb 2006 15:28:46 -0800 > >try mvn validate > > >curious, why do you want to attach scm:checkout to validate phase? > >-Dan > > >On 2/27/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > I don't use Maven SCM at this point, so I can't help you here. > > > > Perhaps someone else who is using SVN in a similar manner can supply > > their pom.xml? > > > > Wayne > > > > > > On 2/27/06, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > Thanks, that got me a little closer, but now I have something new. > > > > > > Here is my plugin: > > > <plugin> > > > <groupId>org.apache.maven.plugins</groupId> > > > <artifactId>maven-scm-plugin</artifactId> > > > <version>1.0-beta-2</version> > > > > > > <configuration> > > > <debug>true></debug> > > > <username>${svn.username}</username> > > > <password>${svn.password}</password> > > > <excludes>*.class</excludes> > > > <includes>*.java</includes> > > > > > > </configuration> > > > > > > <!-- This should be only used in the > > > dev/integration > > servers > > > profile. > > > <executions> > > > <execution> > > > <id>scm</id> > > > <phase>validate</phase> > > > <goals> > > > <goal>checkout</goal> > > > </goals> > > > <inherited>true</inherited> > > > <configuration> > > > <debug>true></debug> > > > <password>${svn.password}</password> > > > <excludes>*.class</excludes> > > > <includes>*.java</includes> > > > <workingDirectory>furlm2</workingDirectory> > > > <username>${svn.username}</username> > > > > > > > > > <connectionUrl>${svn.connectionUrl}</connectionUrl> > > > </configuration> > > > </execution> > > > </executions>--> > > > </plugin> > > > > > > > > > > > > > > > C:\opt\furl\furlm2>mvn svn:checkout -e > > > + Error stacktraces are turned on. > > > [INFO] Scanning for projects... > > > [INFO] Searching repository for plugin with prefix: 'svn'. > > > [INFO] > > > > > >----------------------------------------------------------------------- >----- > > > [ERROR] BUILD ERROR > > > [INFO] > > > > > >----------------------------------------------------------------------- >----- > > > [INFO] The plugin 'org.apache.maven.plugins:maven-svn-plugin' does > > > not > > exist > > > or no valid version could be found [INFO] > > > > > >----------------------------------------------------------------------- >----- > > > [INFO] Trace > > > org.apache.maven.lifecycle.LifecycleExecutionException: The plugin > > > 'org.apache.maven.plugins:maven-svn-plugin' does not exist or no > > > valid version could be found > > > > -------------------------------------------------------------------- > > - 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]
