Subject: FYI - Clean build test project gotcha.. - msg#00014

Previous Message by Date: click to view message preview

Maven repository issues

In doing a complete svn pull and build today (first in a while), I found that Maven (1) could not download dependancies from the repositories specified in the project.properties. This is because these have moved and Maven 1.0 does not understand http 301 redirects. My quick solution was to change the maven.repro.remote setting in the common/project.xml file(s) as follows: maven.repo.remote=http://mirrors.ibiblio.org/pub/maven/,http://people.ap ache.org/repo/m1-ibiblio-rsync-repository/ Which are the sites that you get redirected to. Another possible alternative is to follow the Maven 1 folks published solution of: maven.repo.remote=http://repo1.maven.org/maven Of course, there is another alternative for Maven 1 users. To start using the new V1.1 RC1 which understands redirects. I thought I'd ask which solution seems best before I changed any thing this core in SVN. Also, would any of these changes effect the Maven 2 build process? Greg Greg Monroe <Monroe@xxxxxxxxxx> (919)680-5050 C&IS Solutions Team Lead Duke Corporate Education, Inc. 333 Liggett St. Durham, NC 27701 Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.

Next Message by Date: click to view message preview

Re: FYI - Clean build test project gotcha..

I have not tried this yet, but if you use a new generator and an old maven 1 plugin, this will be problematic. I always use maven -D.... torque-test:clean-install-run in these situations, this will clean, build and install all torque components in the local repository and also clean and run the thest project. I'm not completely sure whether the newly build maven 1 plugin will be used in the same run, but the second run should always work. Thomas "Greg Monroe" <Greg.Monroe@xxxxxxxxxx> schrieb am 07.02.2007 19:05:59: > Just in case someone else gets caught by this... > > If you do a clean SVN pull, build, and run the test program > with Maven 1, you may get compile errors (missing Base* classes) > if you don't re-build the Maven-Plugin. > > I suspect its related to the changes that Thomas F made for > the Maven 2 plugin and modified the Maven 1 plug-in to > match. > > Not a big deal, but could be a common gotcha since the Maven 1 > plug-in hasn't been changed a lot and folks might forget this > step. > > Greg > Greg Monroe <Monroe@xxxxxxxxxx> (919)680-5050 > C&IS Solutions Team Lead > Duke Corporate Education, Inc. > 333 Liggett St. > Durham, NC 27701 > > > > > Duke CE Privacy Statement > Please be advised that this e-mail and any files transmitted with it > are confidential communication or may otherwise be privileged or > confidential and are intended solely for the individual or entity to > whom they are addressed. If you are not the intended recipient you > may not rely on the contents of this email or any attachments, and > we ask that you please not read, copy or retransmit this > communication, but reply to the sender and destroy the email, its > contents, and all copies thereof immediately. Any unauthorized > dissemination, distribution or copying of this communication is > strictly prohibited. > >

Previous Message by Thread: click to view message preview

Maven repository issues

In doing a complete svn pull and build today (first in a while), I found that Maven (1) could not download dependancies from the repositories specified in the project.properties. This is because these have moved and Maven 1.0 does not understand http 301 redirects. My quick solution was to change the maven.repro.remote setting in the common/project.xml file(s) as follows: maven.repo.remote=http://mirrors.ibiblio.org/pub/maven/,http://people.ap ache.org/repo/m1-ibiblio-rsync-repository/ Which are the sites that you get redirected to. Another possible alternative is to follow the Maven 1 folks published solution of: maven.repo.remote=http://repo1.maven.org/maven Of course, there is another alternative for Maven 1 users. To start using the new V1.1 RC1 which understands redirects. I thought I'd ask which solution seems best before I changed any thing this core in SVN. Also, would any of these changes effect the Maven 2 build process? Greg Greg Monroe <Monroe@xxxxxxxxxx> (919)680-5050 C&IS Solutions Team Lead Duke Corporate Education, Inc. 333 Liggett St. Durham, NC 27701 Duke CE Privacy Statement Please be advised that this e-mail and any files transmitted with it are confidential communication or may otherwise be privileged or confidential and are intended solely for the individual or entity to whom they are addressed. If you are not the intended recipient you may not rely on the contents of this email or any attachments, and we ask that you please not read, copy or retransmit this communication, but reply to the sender and destroy the email, its contents, and all copies thereof immediately. Any unauthorized dissemination, distribution or copying of this communication is strictly prohibited.

Next Message by Thread: click to view message preview

Re: FYI - Clean build test project gotcha..

I have not tried this yet, but if you use a new generator and an old maven 1 plugin, this will be problematic. I always use maven -D.... torque-test:clean-install-run in these situations, this will clean, build and install all torque components in the local repository and also clean and run the thest project. I'm not completely sure whether the newly build maven 1 plugin will be used in the same run, but the second run should always work. Thomas "Greg Monroe" <Greg.Monroe@xxxxxxxxxx> schrieb am 07.02.2007 19:05:59: > Just in case someone else gets caught by this... > > If you do a clean SVN pull, build, and run the test program > with Maven 1, you may get compile errors (missing Base* classes) > if you don't re-build the Maven-Plugin. > > I suspect its related to the changes that Thomas F made for > the Maven 2 plugin and modified the Maven 1 plug-in to > match. > > Not a big deal, but could be a common gotcha since the Maven 1 > plug-in hasn't been changed a lot and folks might forget this > step. > > Greg > Greg Monroe <Monroe@xxxxxxxxxx> (919)680-5050 > C&IS Solutions Team Lead > Duke Corporate Education, Inc. > 333 Liggett St. > Durham, NC 27701 > > > > > Duke CE Privacy Statement > Please be advised that this e-mail and any files transmitted with it > are confidential communication or may otherwise be privileged or > confidential and are intended solely for the individual or entity to > whom they are addressed. If you are not the intended recipient you > may not rely on the contents of this email or any attachments, and > we ask that you please not read, copy or retransmit this > communication, but reply to the sender and destroy the email, its > contents, and all copies thereof immediately. Any unauthorized > dissemination, distribution or copying of this communication is > strictly prohibited. > >