We have the same pb. And the only easiest solution we found is to
declare inhouse repositories in pom.xml of each project, not in the
common corporate one. Like this, new checkouts are ready to go, without
configuring settings.xml
Regards,
Jérémy Soula
Nick Stolwijk a écrit :
Hi,
I've got a nice puzzle. We are making a corporate pom file with some
defaults for plugins and the stuff. Also our inhouse repository is
mentioned in there as well as our inhouse snapshot repository.
So when we have a project which has as parent this pom, we don't have
to configure all that stuff anymore. All nice and set, I've been
testing with this setup and it worked fine. Now my colleague wants to
test and check out our project, runs mvn install and maven starts
complaining that it could not find the parent project. Hmm, I've got a
nice circle, I'm looking for my parent, without the repository
configuration, because that's in my parent.
Is there a way to solve this? I thought about a profile in the
settings.xml or profiles.xml, but then you still have to change the
value everywhere when your repository changes url.
Hope someone has any experience with this.
With regards,
Nick Stolwijk
---------------------------------------------------------------------
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]
