If your parent pom is always a snapshot, your option 1) will probably work, but then you will sacrifice build reproducibility (old projects built and released with one snapshot version could in the future suddenly be built with a new parent pom - anything which might change a released build is not good).
If, however, you do releases of your parent pom, which is the recommended approach, old released projects are completely reproducible but they will in turn be stuck with an old parent pom which may suddenly contain wrong repo urls. BTW, the Sonatype book has a chapter on repo management which you may find useful: http://www.sonatype.com/book/ On Fri, Jun 6, 2008 at 4:08 PM, Rick <[EMAIL PROTECTED]> wrote: > I'm still confused on why it wouldn't be a good idea to simply put the > company repository info in a parent pom that all company projects would use? > This seems a lot cleaner and easier to setup and maintain... > > 1) If it's in a parent pom and you need to change repository urls someone > can update the parent pom and everyone should have it. If a settings.xml > file is used and anything needs to change in it (internal repo urls), you > have to contact every developer and tell them to change their settings.xml > file to reflect the new changes. > > 2) avoids having to set up any of the things mentioned so far in this > thread. (The simple 'mvn install' on their project will work without any > other modifiications or activation profiles being set.) > > Of course the user will have to first checkout the inital parent project > from version control, but this seems easier than having your team work with > a settings.xml file. > > I'm new though, so maybe I'm missing a serious drawback to this approach? > > > On Fri, Jun 6, 2008 at 4:24 AM, Timothy Reilly <[EMAIL PROTECTED]> > wrote: > >> >> Rick, >> >> A couple of other options >> If you automatically map a drive when you connect to your company lan >> you could activate the acme-company profile with a file activation. >> >> Or as Wayne says use your mvn script. >> >> For example on windows create %HOMEDRIVE%%HOMEPATH%\mavenrc_pre.bat file >> to do something like: >> >> maven_pre.bat >> >> call ping -n 1 -w 400 my_pdc_hostname >> if ERRORLEVEL > 0 GOTO end >> MAVEN_CMD_LINE_ARGS="%MAVEN_CMD_LINE_ARGS% -Dcom.acme.onthenetwork=true >> " >> :end >> >> Then use property profile activators com.acme.onthenetwork and >> !com.acme.onthenetwork >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > > > -- > Rick > -- - Jan Fredrik Wedén --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
