You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Eric Kolotyluk <er...@gmail.com> on 2012/11/23 16:30:46 UTC
Referencing a parent POM without relativePath
I am playing around with getting our Corporate POM process working
correctly, but running into problems.
I have things configured so that people need to reference it without using
<relativePath>blah</relativePath> because I want them to get it from the
repository and not from Perforce. In particular, I don't want to force
people to make their project POM dependent on some arbitrary place that the
Corporate POM is mapped from source control.
This works well if the Corporate POM is already in the local repository,
but fails completely if it is not in the local repository. Even when the
Corporate POM is in Nexus, Maven will not look there for it. Is there
something I can put in the settings.xml that will force Maven to get the
Corporate POM from Nexus?
Currently people are forced to 'seed' their local repository with the
Corporate POM, which is really a hassle.
What do other people do who have a top level or Corporate POM for all their
projects?
Cheers, Eric
Re: Referencing a parent POM without relativePath
Posted by Benson Margulies <bi...@gmail.com>.
On Fri, Nov 23, 2012 at 12:05 PM, Laird Nelson <lj...@gmail.com> wrote:
> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <bi...@gmail.com>wrote:
>
>> You just name the G/A/V and no relativePath, and Maven will download
>> just as it would a dependency.
>>
>
> Well, not exactly; if there is no <relativePath> element present, then
> Maven behaves as though <relativePath>../pom.xml</relativePath> were
> specified. If that file is a working copy that has not been refreshed from
> the SCM, then problems can ensue.
You only ever need an empty relativePath element when there is an
unwanted pom sitting in .. that you need to discourage Maven from
paying attention to.
>
> I recall that someone mentioned specifying a relative path like this:
>
> <relativePath/>
>
>
> ...and that that was the only way to force Maven to truly resolve the pom
> from the repository, but I don't know if this is in fact true.
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Laird Nelson <lj...@gmail.com>.
On Mon, Nov 26, 2012 at 3:37 PM, Curtis Rueden <ct...@wisc.edu> wrote:
> However, I still think it worth noting, since it is a related issue with
> Maven's behavior with respect to "doing the right thing" with relativePaths
Indeed. For us, implicit relative path behavior (of ../pom.xml) shows up
commonly when someone has a local ../pom.xml in their Subversion workspace
that for some reason they haven't svn updated. Then they do a build of the
./pom.xml project (i.e. the child, not the parent) and get what seems to
them to be bizarre results (i.e. that do not include the most recently
deployed-to-the-corporate-repo ../pom.xml copy but instead occur because
../pom.xml is out of date and is silently being used by Maven instead of
the (updated) Nexus/repo copy). An svn update of that ../pom.xml obviously
fixes the issue (assuming that the version deployed to the repo is the
same, of course). For this reason it seems that we would want to use
<relativePath/> throughout our system. Does that sound right?
Best,
Laird
--
http://about.me/lairdnelson
Re: Referencing a parent POM without relativePath
Posted by Curtis Rueden <ct...@wisc.edu>.
Hi Benson,
> No, that's not what this issue says. This issue deals with the case
> where there IS a ../pom.xml but it's the wrong ../pom.xml.
Indeed, my apologies.
However, I still think it worth noting, since it is a related issue with
Maven's behavior with respect to "doing the right thing" with relativePaths.
Regards,
Curtis
On Mon, Nov 26, 2012 at 2:09 PM, Benson Margulies <bi...@gmail.com>wrote:
> On Mon, Nov 26, 2012 at 11:58 AM, Curtis Rueden <ct...@wisc.edu> wrote:
> > Hi Eric & everyone,
> >
> >> I still think the <userFriendly>true</userFriendly> version of Maven
> >> would just do the right thing when there is no <relativePath/>
> >> element, and there is no ../pom.xml.
> >
> > I agree. Note that there is an issue for it already:
> >
> > http://jira.codehaus.org/browse/MNG-4687
>
> No, that's not what this issue says. This issue deals with the case
> where there IS a ../pom.xml but it's the wrong ../pom.xml.
>
> The OP here has explained that this problem was a local config error,
> the maven behavior is just as requested.
>
>
>
>
>
> >
> > Regards,
> > Curtis
> >
> >
> > On Sat, Nov 24, 2012 at 12:13 PM, Anders Hammar <an...@hammar.net>
> wrote:
> >
> >> I'd just like to echo Benson. You do not need the <relativePath/>
> element
> >> if your environment is setup correctly.
> >>
> >> /Anders
> >>
> >>
> >> On Sat, Nov 24, 2012 at 4:48 AM, Eric Kolotyluk <
> eric.kolotyluk@gmail.com
> >> >wrote:
> >>
> >> > On 2012-11-23 7:01 PM, Benson Margulies wrote:
> >> >
> >> >> On Fri, Nov 23, 2012 at 8:45 PM, Eric Kolotyluk
> >> >> <er...@gmail.com> wrote:
> >> >>
> >> >>> OK, I have added the following to our Corporate POM. Hopefully I,
> and
> >> >>> others, won't fall into this trap again.
> >> >>>
> >> >>> I still think the <userFriendly>true</**userFriendly> version of
> Maven
> >> >>> would
> >> >>> just do the right thing when there is no <relativePath/> element,
> and
> >> >>> there
> >> >>> is no ../pom.xml. I can see no value in the current Maven behavior
> of
> >> >>> throwing an error the way it does.
> >> >>>
> >> >> Eric,
> >> >>
> >> >> It does what you want. If it is not doing it for you, there's
> >> >> something wrong with your environment.
> >> >>
> >> >> None of our POMs have explicit relativePath elements, and they all
> >> >> work fine. The empty element is only needed when there *is* a
> >> >> ../pom.xml to avoid, but you are writing that you don't have one.
> >> >>
> >> >>
> >> > OK, I will play with this some more to see if I can replicate the
> problem
> >> > again.
> >> >
> >> > Cheers, Eric
> >> >
> >> >
> >> >
> >> >> Cheers, Eric
> >> >>>
> >> >>> <!--
> >> >>> No parent for this POM! This is parent of all Kodak
> projects.
> >> >>> Top Level Project POMs should reference this POM with
> >> >>>
> >> >>> <parent>
> >> >>> <groupId>com</groupId>
> >> >>> <artifactId>kodak</artifactId>
> >> >>> <version>1.0.0</version>
> >> >>> <relativePath/>
> >> >>> </parent>
> >> >>>
> >> >>> The empty <relativePath/> element is necessary because
> >> com:kodak
> >> >>> is a
> >> >>> seperate project that will never be in
> >> >>> the parent directory of your project. If <relativePath/> is
> >> >>> missing,
> >> >>> Maven will look in ../ by default, and
> >> >>> then throw an error because it cannot find ../pom.xml (and
> you
> >> >>> should
> >> >>> never have ../pom.xml).
> >> >>> -->
> >> >>>
> >> >>>
> >> >>> On 2012-11-23 12:47 PM, David Karr wrote:
> >> >>>
> >> >>>> I had also discovered the difference between the missing vs. empty
> >> >>>> "relativePath" element. Although it was initially disconcerting
> that
> >> I
> >> >>>> had
> >> >>>> to specify an empty "relativePath" element to get what I assumed
> was
> >> the
> >> >>>> most reasonable behavior, I can also see the logic of the
> alternative
> >> >>>> with
> >> >>>> the default value. I prefer to separate the notion of "parent" pom
> >> from
> >> >>>> "aggregator" pom (a pom with a list of modules), but if you use a
> >> >>>> strategy
> >> >>>> that combines them, then the default value is more likely.
> >> >>>>
> >> >>>>
> >> >>>> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
> >> >>>> <er...@gmail.com>**wrote:
> >> >>>>
> >> >>>> DOH! I retract that previous message. I forgot to open my VPN
> >> >>>>> connection
> >> >>>>> first.
> >> >>>>>
> >> >>>>> Putting <relativePath/> in the POM does work!
> >> >>>>>
> >> >>>>> So, would it be unreasonable if Maven treated the absence of the
> >> >>>>> <relativePath> element the same as <relativePath/>. That would
> make
> >> it
> >> >>>>> more
> >> >>>>> user friendly as far as I am concerned.
> >> >>>>>
> >> >>>>> Also, it was m2e that built the original project POM, and it did
> not
> >> >>>>> put
> >> >>>>> <relativePath/> in the POM.
> >> >>>>>
> >> >>>>> Cheers, Eric
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>>>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
> >> >>>>>
> >> >>>>> I tried putting <relativePath/> in my POM, but it does not fix
> >> things.
> >> >>>>>>
> >> >>>>>> <parent>
> >> >>>>>> <groupId>com</groupId>
> >> >>>>>> <artifactId>kodak</artifactId>
> >> >>>>>> <version>0.0.11-SNAPSHOT</****version>
> >> >>>>>> <relativePath/>
> >> >>>>>> </parent>
> >> >>>>>>
> >> >>>>>> I still get
> >> >>>>>>
> >> >>>>>> C:\Users\Eric\workspace\tree-****combo-box>mvn clean
> >> >>>>>> [INFO] Scanning for projects...
> >> >>>>>> Downloading:
> >> >>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
> >> >>>>>>
> >> >>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/maven-metadata.xml<ht**
> >> >>>>>> tp://repository.ca.kodak.com:**8082/nexus/content/groups/**
> >> >>>>>> public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<
> >>
> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml
> >> >
> >> >>>>>> >
> >> >>>>>> [WARNING] Could not transfer metadata
> >> >>>>>> com:kodak:0.0.11-SNAPSHOT/****maven-metadata.xml
> >> >>>>>> from/to nexus (http://repository.ca.kodak.**
> >> >>>>>>
> >> >>>>>> com:8082/nexus/content/groups/****public<http://repository.ca.**
> >> >>>>>> kodak.com:8082/nexus/content/**groups/public<
> >> http://repository.ca.kodak.com:8082/nexus/content/groups/public>
> >> >>>>>> >):
> >> >>>>>> repository.ca.kodak.com
> >> >>>>>> Downloading:
> >> >>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
> >> >>>>>>
> >> >>>>>>
> *public/com/kodak/0.0.11-****SNAPSHOT/kodak-0.0.11-****SNAPSHOT.pom<
> >> >>>>>> http://**
> >> repository.ca.kodak.com:8082/**nexus/content/groups/public/*
> >> >>>>>> *com/kodak/0.0.11-SNAPSHOT/**kodak-0.0.11-SNAPSHOT.pom<
> >>
> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom
> >> >
> >> >>>>>> >
> >> >>>>>> [ERROR] The build could not read 1 project -> [Help 1]
> >> >>>>>> [ERROR]
> >> >>>>>> [ERROR] The project
> >> >>>>>> net.kolotyluk.experiment:tree-****combo-box:0.0.1-SNAPSHOT
> >> >>>>>> (C:\Users\Eric\workspace\tree-****combo-box\pom.xml) has 1 error
> >> >>>>>> [ERROR] Non-resolvable parent POM: Could not transfer
> artifact
> >> >>>>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
> >> >>>>>> (http://repository.ca.kodak.*
> >> >>>>>>
> >> >>>>>> *com:8082/nexus/content/**groups/**public<http://**
> >> >>>>>> repository.ca.kodak.com:8082/**nexus/content/groups/public<
> >> http://repository.ca.kodak.com:8082/nexus/content/groups/public>
> >> >>>>>> >):
> >> >>>>>> repository.ca.kodak.com and 'parent.relativePath' points at no
> >> local
> >> >>>>>> POM
> >> >>>>>> @ line 9, column 11: Unknown host repository.ca.kodak.com ->
> [Help
> >> 2]
> >> >>>>>> [ERROR]
> >> >>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven
> with
> >> >>>>>> the
> >> >>>>>> -e switch.
> >> >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> >> logging.
> >> >>>>>> [ERROR]
> >> >>>>>> [ERROR] For more information about the errors and possible
> >> solutions,
> >> >>>>>> please read the following articles:
> >> >>>>>> [ERROR] [Help 1] http://cwiki.apache.org/****
> >> >>>>>> confluence/display/MAVEN/**<
> >> http://cwiki.apache.org/**confluence/display/MAVEN/**>
> >> >>>>>>
> >> >>>>>> ProjectBuildingException<http:**//cwiki.apache.org/confluence/**
> >> >>>>>> display/MAVEN/**ProjectBuildingException<
> >>
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
> >> >>>>>> >
> >> >>>>>> [ERROR] [Help 2] http://cwiki.apache.org/****
> >> >>>>>> confluence/display/MAVEN/**<
> >> http://cwiki.apache.org/**confluence/display/MAVEN/**>
> >> >>>>>>
> >> >>>>>> UnresolvableModelException<htt**p://cwiki.apache.org/**
> >> >>>>>> confluence/display/MAVEN/**UnresolvableModelException<
> >>
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> >> >
> >> >>>>>> >
> >> >>>>>>
> >> >>>>>> It looks like Maven wants to download the Corporate POM because
> it
> >> >>>>>> sees
> >> >>>>>> it in Nexus, but craps out because it does not like the Project
> POM.
> >> >>>>>> Maven
> >> >>>>>> seems pretty certain that it wants parent.relativePath to point
> to a
> >> >>>>>> local
> >> >>>>>> POM.
> >> >>>>>>
> >> >>>>>> Is there a <userFriendly>true</****userFriendly> switch I can
> turn
> >> on
> >> >>>>>> somewhere in Maven ;-)
> >> >>>>>>
> >> >>>>>> Cheers, Eric
> >> >>>>>>
> >> >>>>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
> >> >>>>>>
> >> >>>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
> >> >>>>>>> bimargulies@gmail.com>wrote:
> >> >>>>>>>
> >> >>>>>>> You just name the G/A/V and no relativePath, and Maven will
> >> >>>>>>> download
> >> >>>>>>>
> >> >>>>>>>> just as it would a dependency.
> >> >>>>>>>>
> >> >>>>>>>> Well, not exactly; if there is no <relativePath> element
> >> present,
> >> >>>>>>>> then
> >> >>>>>>>>
> >> >>>>>>> Maven behaves as though
> <relativePath>../pom.xml</****relativePath>
> >> >>>>>>> were
> >> >>>>>>> specified. If that file is a working copy that has not been
> >> >>>>>>> refreshed
> >> >>>>>>> from
> >> >>>>>>> the SCM, then problems can ensue.
> >> >>>>>>>
> >> >>>>>>> I recall that someone mentioned specifying a relative path like
> >> this:
> >> >>>>>>>
> >> >>>>>>> <relativePath/>
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>> ...and that that was the only way to force Maven to truly
> resolve
> >> the
> >> >>>>>>> pom
> >> >>>>>>> from the repository, but I don't know if this is in fact true.
> >> >>>>>>>
> >> >>>>>>> Best,
> >> >>>>>>> Laird
> >> >>>>>>>
> >> >>>>>>>
> >> >>>>>>>
> ------------------------------****----------------------------**
> >> >>>>> --**---------
> >> >>>>> To unsubscribe, e-mail:
> >> >>>>> users-unsubscribe@maven.**apac**he.org <http://apache.org><
> >> >>>>> users-unsubscribe@**maven.apache.org<
> >> users-unsubscribe@maven.apache.org>
> >> >>>>> >
> >> >>>>> For additional commands, e-mail: users-help@maven.apache.org
> >> >>>>>
> >> >>>>>
> >> >>>>>
> >> >>> ------------------------------**------------------------------**
> >> >>> ---------
> >> >>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
> >> users-unsubscribe@maven.apache.org>
> >> >>> For additional commands, e-mail: users-help@maven.apache.org
> >> >>>
> >> >>> ------------------------------**------------------------------**
> >> >> ---------
> >> >> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
> >> users-unsubscribe@maven.apache.org>
> >> >> For additional commands, e-mail: users-help@maven.apache.org
> >> >>
> >> >>
> >> >
> >> >
> ------------------------------**------------------------------**---------
> >> > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
> >> users-unsubscribe@maven.apache.org>
> >> > For additional commands, e-mail: users-help@maven.apache.org
> >> >
> >> >
> >>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Referencing a parent POM without relativePath
Posted by Benson Margulies <bi...@gmail.com>.
On Mon, Nov 26, 2012 at 11:58 AM, Curtis Rueden <ct...@wisc.edu> wrote:
> Hi Eric & everyone,
>
>> I still think the <userFriendly>true</userFriendly> version of Maven
>> would just do the right thing when there is no <relativePath/>
>> element, and there is no ../pom.xml.
>
> I agree. Note that there is an issue for it already:
>
> http://jira.codehaus.org/browse/MNG-4687
No, that's not what this issue says. This issue deals with the case
where there IS a ../pom.xml but it's the wrong ../pom.xml.
The OP here has explained that this problem was a local config error,
the maven behavior is just as requested.
>
> Regards,
> Curtis
>
>
> On Sat, Nov 24, 2012 at 12:13 PM, Anders Hammar <an...@hammar.net> wrote:
>
>> I'd just like to echo Benson. You do not need the <relativePath/> element
>> if your environment is setup correctly.
>>
>> /Anders
>>
>>
>> On Sat, Nov 24, 2012 at 4:48 AM, Eric Kolotyluk <eric.kolotyluk@gmail.com
>> >wrote:
>>
>> > On 2012-11-23 7:01 PM, Benson Margulies wrote:
>> >
>> >> On Fri, Nov 23, 2012 at 8:45 PM, Eric Kolotyluk
>> >> <er...@gmail.com> wrote:
>> >>
>> >>> OK, I have added the following to our Corporate POM. Hopefully I, and
>> >>> others, won't fall into this trap again.
>> >>>
>> >>> I still think the <userFriendly>true</**userFriendly> version of Maven
>> >>> would
>> >>> just do the right thing when there is no <relativePath/> element, and
>> >>> there
>> >>> is no ../pom.xml. I can see no value in the current Maven behavior of
>> >>> throwing an error the way it does.
>> >>>
>> >> Eric,
>> >>
>> >> It does what you want. If it is not doing it for you, there's
>> >> something wrong with your environment.
>> >>
>> >> None of our POMs have explicit relativePath elements, and they all
>> >> work fine. The empty element is only needed when there *is* a
>> >> ../pom.xml to avoid, but you are writing that you don't have one.
>> >>
>> >>
>> > OK, I will play with this some more to see if I can replicate the problem
>> > again.
>> >
>> > Cheers, Eric
>> >
>> >
>> >
>> >> Cheers, Eric
>> >>>
>> >>> <!--
>> >>> No parent for this POM! This is parent of all Kodak projects.
>> >>> Top Level Project POMs should reference this POM with
>> >>>
>> >>> <parent>
>> >>> <groupId>com</groupId>
>> >>> <artifactId>kodak</artifactId>
>> >>> <version>1.0.0</version>
>> >>> <relativePath/>
>> >>> </parent>
>> >>>
>> >>> The empty <relativePath/> element is necessary because
>> com:kodak
>> >>> is a
>> >>> seperate project that will never be in
>> >>> the parent directory of your project. If <relativePath/> is
>> >>> missing,
>> >>> Maven will look in ../ by default, and
>> >>> then throw an error because it cannot find ../pom.xml (and you
>> >>> should
>> >>> never have ../pom.xml).
>> >>> -->
>> >>>
>> >>>
>> >>> On 2012-11-23 12:47 PM, David Karr wrote:
>> >>>
>> >>>> I had also discovered the difference between the missing vs. empty
>> >>>> "relativePath" element. Although it was initially disconcerting that
>> I
>> >>>> had
>> >>>> to specify an empty "relativePath" element to get what I assumed was
>> the
>> >>>> most reasonable behavior, I can also see the logic of the alternative
>> >>>> with
>> >>>> the default value. I prefer to separate the notion of "parent" pom
>> from
>> >>>> "aggregator" pom (a pom with a list of modules), but if you use a
>> >>>> strategy
>> >>>> that combines them, then the default value is more likely.
>> >>>>
>> >>>>
>> >>>> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
>> >>>> <er...@gmail.com>**wrote:
>> >>>>
>> >>>> DOH! I retract that previous message. I forgot to open my VPN
>> >>>>> connection
>> >>>>> first.
>> >>>>>
>> >>>>> Putting <relativePath/> in the POM does work!
>> >>>>>
>> >>>>> So, would it be unreasonable if Maven treated the absence of the
>> >>>>> <relativePath> element the same as <relativePath/>. That would make
>> it
>> >>>>> more
>> >>>>> user friendly as far as I am concerned.
>> >>>>>
>> >>>>> Also, it was m2e that built the original project POM, and it did not
>> >>>>> put
>> >>>>> <relativePath/> in the POM.
>> >>>>>
>> >>>>> Cheers, Eric
>> >>>>>
>> >>>>>
>> >>>>>
>> >>>>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
>> >>>>>
>> >>>>> I tried putting <relativePath/> in my POM, but it does not fix
>> things.
>> >>>>>>
>> >>>>>> <parent>
>> >>>>>> <groupId>com</groupId>
>> >>>>>> <artifactId>kodak</artifactId>
>> >>>>>> <version>0.0.11-SNAPSHOT</****version>
>> >>>>>> <relativePath/>
>> >>>>>> </parent>
>> >>>>>>
>> >>>>>> I still get
>> >>>>>>
>> >>>>>> C:\Users\Eric\workspace\tree-****combo-box>mvn clean
>> >>>>>> [INFO] Scanning for projects...
>> >>>>>> Downloading:
>> >>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
>> >>>>>>
>> >>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/maven-metadata.xml<ht**
>> >>>>>> tp://repository.ca.kodak.com:**8082/nexus/content/groups/**
>> >>>>>> public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<
>> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml
>> >
>> >>>>>> >
>> >>>>>> [WARNING] Could not transfer metadata
>> >>>>>> com:kodak:0.0.11-SNAPSHOT/****maven-metadata.xml
>> >>>>>> from/to nexus (http://repository.ca.kodak.**
>> >>>>>>
>> >>>>>> com:8082/nexus/content/groups/****public<http://repository.ca.**
>> >>>>>> kodak.com:8082/nexus/content/**groups/public<
>> http://repository.ca.kodak.com:8082/nexus/content/groups/public>
>> >>>>>> >):
>> >>>>>> repository.ca.kodak.com
>> >>>>>> Downloading:
>> >>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
>> >>>>>>
>> >>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/kodak-0.0.11-****SNAPSHOT.pom<
>> >>>>>> http://**
>> repository.ca.kodak.com:8082/**nexus/content/groups/public/*
>> >>>>>> *com/kodak/0.0.11-SNAPSHOT/**kodak-0.0.11-SNAPSHOT.pom<
>> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom
>> >
>> >>>>>> >
>> >>>>>> [ERROR] The build could not read 1 project -> [Help 1]
>> >>>>>> [ERROR]
>> >>>>>> [ERROR] The project
>> >>>>>> net.kolotyluk.experiment:tree-****combo-box:0.0.1-SNAPSHOT
>> >>>>>> (C:\Users\Eric\workspace\tree-****combo-box\pom.xml) has 1 error
>> >>>>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>> >>>>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
>> >>>>>> (http://repository.ca.kodak.*
>> >>>>>>
>> >>>>>> *com:8082/nexus/content/**groups/**public<http://**
>> >>>>>> repository.ca.kodak.com:8082/**nexus/content/groups/public<
>> http://repository.ca.kodak.com:8082/nexus/content/groups/public>
>> >>>>>> >):
>> >>>>>> repository.ca.kodak.com and 'parent.relativePath' points at no
>> local
>> >>>>>> POM
>> >>>>>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help
>> 2]
>> >>>>>> [ERROR]
>> >>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> >>>>>> the
>> >>>>>> -e switch.
>> >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
>> logging.
>> >>>>>> [ERROR]
>> >>>>>> [ERROR] For more information about the errors and possible
>> solutions,
>> >>>>>> please read the following articles:
>> >>>>>> [ERROR] [Help 1] http://cwiki.apache.org/****
>> >>>>>> confluence/display/MAVEN/**<
>> http://cwiki.apache.org/**confluence/display/MAVEN/**>
>> >>>>>>
>> >>>>>> ProjectBuildingException<http:**//cwiki.apache.org/confluence/**
>> >>>>>> display/MAVEN/**ProjectBuildingException<
>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
>> >>>>>> >
>> >>>>>> [ERROR] [Help 2] http://cwiki.apache.org/****
>> >>>>>> confluence/display/MAVEN/**<
>> http://cwiki.apache.org/**confluence/display/MAVEN/**>
>> >>>>>>
>> >>>>>> UnresolvableModelException<htt**p://cwiki.apache.org/**
>> >>>>>> confluence/display/MAVEN/**UnresolvableModelException<
>> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>> >
>> >>>>>> >
>> >>>>>>
>> >>>>>> It looks like Maven wants to download the Corporate POM because it
>> >>>>>> sees
>> >>>>>> it in Nexus, but craps out because it does not like the Project POM.
>> >>>>>> Maven
>> >>>>>> seems pretty certain that it wants parent.relativePath to point to a
>> >>>>>> local
>> >>>>>> POM.
>> >>>>>>
>> >>>>>> Is there a <userFriendly>true</****userFriendly> switch I can turn
>> on
>> >>>>>> somewhere in Maven ;-)
>> >>>>>>
>> >>>>>> Cheers, Eric
>> >>>>>>
>> >>>>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>> >>>>>>
>> >>>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
>> >>>>>>> bimargulies@gmail.com>wrote:
>> >>>>>>>
>> >>>>>>> You just name the G/A/V and no relativePath, and Maven will
>> >>>>>>> download
>> >>>>>>>
>> >>>>>>>> just as it would a dependency.
>> >>>>>>>>
>> >>>>>>>> Well, not exactly; if there is no <relativePath> element
>> present,
>> >>>>>>>> then
>> >>>>>>>>
>> >>>>>>> Maven behaves as though <relativePath>../pom.xml</****relativePath>
>> >>>>>>> were
>> >>>>>>> specified. If that file is a working copy that has not been
>> >>>>>>> refreshed
>> >>>>>>> from
>> >>>>>>> the SCM, then problems can ensue.
>> >>>>>>>
>> >>>>>>> I recall that someone mentioned specifying a relative path like
>> this:
>> >>>>>>>
>> >>>>>>> <relativePath/>
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> ...and that that was the only way to force Maven to truly resolve
>> the
>> >>>>>>> pom
>> >>>>>>> from the repository, but I don't know if this is in fact true.
>> >>>>>>>
>> >>>>>>> Best,
>> >>>>>>> Laird
>> >>>>>>>
>> >>>>>>>
>> >>>>>>> ------------------------------****----------------------------**
>> >>>>> --**---------
>> >>>>> To unsubscribe, e-mail:
>> >>>>> users-unsubscribe@maven.**apac**he.org <http://apache.org><
>> >>>>> users-unsubscribe@**maven.apache.org<
>> users-unsubscribe@maven.apache.org>
>> >>>>> >
>> >>>>> For additional commands, e-mail: users-help@maven.apache.org
>> >>>>>
>> >>>>>
>> >>>>>
>> >>> ------------------------------**------------------------------**
>> >>> ---------
>> >>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
>> users-unsubscribe@maven.apache.org>
>> >>> For additional commands, e-mail: users-help@maven.apache.org
>> >>>
>> >>> ------------------------------**------------------------------**
>> >> ---------
>> >> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
>> users-unsubscribe@maven.apache.org>
>> >> For additional commands, e-mail: users-help@maven.apache.org
>> >>
>> >>
>> >
>> > ------------------------------**------------------------------**---------
>> > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
>> users-unsubscribe@maven.apache.org>
>> > For additional commands, e-mail: users-help@maven.apache.org
>> >
>> >
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Curtis Rueden <ct...@wisc.edu>.
Hi Eric & everyone,
> I still think the <userFriendly>true</userFriendly> version of Maven
> would just do the right thing when there is no <relativePath/>
> element, and there is no ../pom.xml.
I agree. Note that there is an issue for it already:
http://jira.codehaus.org/browse/MNG-4687
Regards,
Curtis
On Sat, Nov 24, 2012 at 12:13 PM, Anders Hammar <an...@hammar.net> wrote:
> I'd just like to echo Benson. You do not need the <relativePath/> element
> if your environment is setup correctly.
>
> /Anders
>
>
> On Sat, Nov 24, 2012 at 4:48 AM, Eric Kolotyluk <eric.kolotyluk@gmail.com
> >wrote:
>
> > On 2012-11-23 7:01 PM, Benson Margulies wrote:
> >
> >> On Fri, Nov 23, 2012 at 8:45 PM, Eric Kolotyluk
> >> <er...@gmail.com> wrote:
> >>
> >>> OK, I have added the following to our Corporate POM. Hopefully I, and
> >>> others, won't fall into this trap again.
> >>>
> >>> I still think the <userFriendly>true</**userFriendly> version of Maven
> >>> would
> >>> just do the right thing when there is no <relativePath/> element, and
> >>> there
> >>> is no ../pom.xml. I can see no value in the current Maven behavior of
> >>> throwing an error the way it does.
> >>>
> >> Eric,
> >>
> >> It does what you want. If it is not doing it for you, there's
> >> something wrong with your environment.
> >>
> >> None of our POMs have explicit relativePath elements, and they all
> >> work fine. The empty element is only needed when there *is* a
> >> ../pom.xml to avoid, but you are writing that you don't have one.
> >>
> >>
> > OK, I will play with this some more to see if I can replicate the problem
> > again.
> >
> > Cheers, Eric
> >
> >
> >
> >> Cheers, Eric
> >>>
> >>> <!--
> >>> No parent for this POM! This is parent of all Kodak projects.
> >>> Top Level Project POMs should reference this POM with
> >>>
> >>> <parent>
> >>> <groupId>com</groupId>
> >>> <artifactId>kodak</artifactId>
> >>> <version>1.0.0</version>
> >>> <relativePath/>
> >>> </parent>
> >>>
> >>> The empty <relativePath/> element is necessary because
> com:kodak
> >>> is a
> >>> seperate project that will never be in
> >>> the parent directory of your project. If <relativePath/> is
> >>> missing,
> >>> Maven will look in ../ by default, and
> >>> then throw an error because it cannot find ../pom.xml (and you
> >>> should
> >>> never have ../pom.xml).
> >>> -->
> >>>
> >>>
> >>> On 2012-11-23 12:47 PM, David Karr wrote:
> >>>
> >>>> I had also discovered the difference between the missing vs. empty
> >>>> "relativePath" element. Although it was initially disconcerting that
> I
> >>>> had
> >>>> to specify an empty "relativePath" element to get what I assumed was
> the
> >>>> most reasonable behavior, I can also see the logic of the alternative
> >>>> with
> >>>> the default value. I prefer to separate the notion of "parent" pom
> from
> >>>> "aggregator" pom (a pom with a list of modules), but if you use a
> >>>> strategy
> >>>> that combines them, then the default value is more likely.
> >>>>
> >>>>
> >>>> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
> >>>> <er...@gmail.com>**wrote:
> >>>>
> >>>> DOH! I retract that previous message. I forgot to open my VPN
> >>>>> connection
> >>>>> first.
> >>>>>
> >>>>> Putting <relativePath/> in the POM does work!
> >>>>>
> >>>>> So, would it be unreasonable if Maven treated the absence of the
> >>>>> <relativePath> element the same as <relativePath/>. That would make
> it
> >>>>> more
> >>>>> user friendly as far as I am concerned.
> >>>>>
> >>>>> Also, it was m2e that built the original project POM, and it did not
> >>>>> put
> >>>>> <relativePath/> in the POM.
> >>>>>
> >>>>> Cheers, Eric
> >>>>>
> >>>>>
> >>>>>
> >>>>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
> >>>>>
> >>>>> I tried putting <relativePath/> in my POM, but it does not fix
> things.
> >>>>>>
> >>>>>> <parent>
> >>>>>> <groupId>com</groupId>
> >>>>>> <artifactId>kodak</artifactId>
> >>>>>> <version>0.0.11-SNAPSHOT</****version>
> >>>>>> <relativePath/>
> >>>>>> </parent>
> >>>>>>
> >>>>>> I still get
> >>>>>>
> >>>>>> C:\Users\Eric\workspace\tree-****combo-box>mvn clean
> >>>>>> [INFO] Scanning for projects...
> >>>>>> Downloading:
> >>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
> >>>>>>
> >>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/maven-metadata.xml<ht**
> >>>>>> tp://repository.ca.kodak.com:**8082/nexus/content/groups/**
> >>>>>> public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<
> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml
> >
> >>>>>> >
> >>>>>> [WARNING] Could not transfer metadata
> >>>>>> com:kodak:0.0.11-SNAPSHOT/****maven-metadata.xml
> >>>>>> from/to nexus (http://repository.ca.kodak.**
> >>>>>>
> >>>>>> com:8082/nexus/content/groups/****public<http://repository.ca.**
> >>>>>> kodak.com:8082/nexus/content/**groups/public<
> http://repository.ca.kodak.com:8082/nexus/content/groups/public>
> >>>>>> >):
> >>>>>> repository.ca.kodak.com
> >>>>>> Downloading:
> >>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
> >>>>>>
> >>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/kodak-0.0.11-****SNAPSHOT.pom<
> >>>>>> http://**
> repository.ca.kodak.com:8082/**nexus/content/groups/public/*
> >>>>>> *com/kodak/0.0.11-SNAPSHOT/**kodak-0.0.11-SNAPSHOT.pom<
> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom
> >
> >>>>>> >
> >>>>>> [ERROR] The build could not read 1 project -> [Help 1]
> >>>>>> [ERROR]
> >>>>>> [ERROR] The project
> >>>>>> net.kolotyluk.experiment:tree-****combo-box:0.0.1-SNAPSHOT
> >>>>>> (C:\Users\Eric\workspace\tree-****combo-box\pom.xml) has 1 error
> >>>>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
> >>>>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
> >>>>>> (http://repository.ca.kodak.*
> >>>>>>
> >>>>>> *com:8082/nexus/content/**groups/**public<http://**
> >>>>>> repository.ca.kodak.com:8082/**nexus/content/groups/public<
> http://repository.ca.kodak.com:8082/nexus/content/groups/public>
> >>>>>> >):
> >>>>>> repository.ca.kodak.com and 'parent.relativePath' points at no
> local
> >>>>>> POM
> >>>>>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help
> 2]
> >>>>>> [ERROR]
> >>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
> >>>>>> the
> >>>>>> -e switch.
> >>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug
> logging.
> >>>>>> [ERROR]
> >>>>>> [ERROR] For more information about the errors and possible
> solutions,
> >>>>>> please read the following articles:
> >>>>>> [ERROR] [Help 1] http://cwiki.apache.org/****
> >>>>>> confluence/display/MAVEN/**<
> http://cwiki.apache.org/**confluence/display/MAVEN/**>
> >>>>>>
> >>>>>> ProjectBuildingException<http:**//cwiki.apache.org/confluence/**
> >>>>>> display/MAVEN/**ProjectBuildingException<
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
> >>>>>> >
> >>>>>> [ERROR] [Help 2] http://cwiki.apache.org/****
> >>>>>> confluence/display/MAVEN/**<
> http://cwiki.apache.org/**confluence/display/MAVEN/**>
> >>>>>>
> >>>>>> UnresolvableModelException<htt**p://cwiki.apache.org/**
> >>>>>> confluence/display/MAVEN/**UnresolvableModelException<
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
> >
> >>>>>> >
> >>>>>>
> >>>>>> It looks like Maven wants to download the Corporate POM because it
> >>>>>> sees
> >>>>>> it in Nexus, but craps out because it does not like the Project POM.
> >>>>>> Maven
> >>>>>> seems pretty certain that it wants parent.relativePath to point to a
> >>>>>> local
> >>>>>> POM.
> >>>>>>
> >>>>>> Is there a <userFriendly>true</****userFriendly> switch I can turn
> on
> >>>>>> somewhere in Maven ;-)
> >>>>>>
> >>>>>> Cheers, Eric
> >>>>>>
> >>>>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
> >>>>>>
> >>>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
> >>>>>>> bimargulies@gmail.com>wrote:
> >>>>>>>
> >>>>>>> You just name the G/A/V and no relativePath, and Maven will
> >>>>>>> download
> >>>>>>>
> >>>>>>>> just as it would a dependency.
> >>>>>>>>
> >>>>>>>> Well, not exactly; if there is no <relativePath> element
> present,
> >>>>>>>> then
> >>>>>>>>
> >>>>>>> Maven behaves as though <relativePath>../pom.xml</****relativePath>
> >>>>>>> were
> >>>>>>> specified. If that file is a working copy that has not been
> >>>>>>> refreshed
> >>>>>>> from
> >>>>>>> the SCM, then problems can ensue.
> >>>>>>>
> >>>>>>> I recall that someone mentioned specifying a relative path like
> this:
> >>>>>>>
> >>>>>>> <relativePath/>
> >>>>>>>
> >>>>>>>
> >>>>>>> ...and that that was the only way to force Maven to truly resolve
> the
> >>>>>>> pom
> >>>>>>> from the repository, but I don't know if this is in fact true.
> >>>>>>>
> >>>>>>> Best,
> >>>>>>> Laird
> >>>>>>>
> >>>>>>>
> >>>>>>> ------------------------------****----------------------------**
> >>>>> --**---------
> >>>>> To unsubscribe, e-mail:
> >>>>> users-unsubscribe@maven.**apac**he.org <http://apache.org><
> >>>>> users-unsubscribe@**maven.apache.org<
> users-unsubscribe@maven.apache.org>
> >>>>> >
> >>>>> For additional commands, e-mail: users-help@maven.apache.org
> >>>>>
> >>>>>
> >>>>>
> >>> ------------------------------**------------------------------**
> >>> ---------
> >>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
> users-unsubscribe@maven.apache.org>
> >>> For additional commands, e-mail: users-help@maven.apache.org
> >>>
> >>> ------------------------------**------------------------------**
> >> ---------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
> users-unsubscribe@maven.apache.org>
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
> >
> > ------------------------------**------------------------------**---------
> > To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<
> users-unsubscribe@maven.apache.org>
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
Re: Referencing a parent POM without relativePath
Posted by Anders Hammar <an...@hammar.net>.
I'd just like to echo Benson. You do not need the <relativePath/> element
if your environment is setup correctly.
/Anders
On Sat, Nov 24, 2012 at 4:48 AM, Eric Kolotyluk <er...@gmail.com>wrote:
> On 2012-11-23 7:01 PM, Benson Margulies wrote:
>
>> On Fri, Nov 23, 2012 at 8:45 PM, Eric Kolotyluk
>> <er...@gmail.com> wrote:
>>
>>> OK, I have added the following to our Corporate POM. Hopefully I, and
>>> others, won't fall into this trap again.
>>>
>>> I still think the <userFriendly>true</**userFriendly> version of Maven
>>> would
>>> just do the right thing when there is no <relativePath/> element, and
>>> there
>>> is no ../pom.xml. I can see no value in the current Maven behavior of
>>> throwing an error the way it does.
>>>
>> Eric,
>>
>> It does what you want. If it is not doing it for you, there's
>> something wrong with your environment.
>>
>> None of our POMs have explicit relativePath elements, and they all
>> work fine. The empty element is only needed when there *is* a
>> ../pom.xml to avoid, but you are writing that you don't have one.
>>
>>
> OK, I will play with this some more to see if I can replicate the problem
> again.
>
> Cheers, Eric
>
>
>
>> Cheers, Eric
>>>
>>> <!--
>>> No parent for this POM! This is parent of all Kodak projects.
>>> Top Level Project POMs should reference this POM with
>>>
>>> <parent>
>>> <groupId>com</groupId>
>>> <artifactId>kodak</artifactId>
>>> <version>1.0.0</version>
>>> <relativePath/>
>>> </parent>
>>>
>>> The empty <relativePath/> element is necessary because com:kodak
>>> is a
>>> seperate project that will never be in
>>> the parent directory of your project. If <relativePath/> is
>>> missing,
>>> Maven will look in ../ by default, and
>>> then throw an error because it cannot find ../pom.xml (and you
>>> should
>>> never have ../pom.xml).
>>> -->
>>>
>>>
>>> On 2012-11-23 12:47 PM, David Karr wrote:
>>>
>>>> I had also discovered the difference between the missing vs. empty
>>>> "relativePath" element. Although it was initially disconcerting that I
>>>> had
>>>> to specify an empty "relativePath" element to get what I assumed was the
>>>> most reasonable behavior, I can also see the logic of the alternative
>>>> with
>>>> the default value. I prefer to separate the notion of "parent" pom from
>>>> "aggregator" pom (a pom with a list of modules), but if you use a
>>>> strategy
>>>> that combines them, then the default value is more likely.
>>>>
>>>>
>>>> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
>>>> <er...@gmail.com>**wrote:
>>>>
>>>> DOH! I retract that previous message. I forgot to open my VPN
>>>>> connection
>>>>> first.
>>>>>
>>>>> Putting <relativePath/> in the POM does work!
>>>>>
>>>>> So, would it be unreasonable if Maven treated the absence of the
>>>>> <relativePath> element the same as <relativePath/>. That would make it
>>>>> more
>>>>> user friendly as far as I am concerned.
>>>>>
>>>>> Also, it was m2e that built the original project POM, and it did not
>>>>> put
>>>>> <relativePath/> in the POM.
>>>>>
>>>>> Cheers, Eric
>>>>>
>>>>>
>>>>>
>>>>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
>>>>>
>>>>> I tried putting <relativePath/> in my POM, but it does not fix things.
>>>>>>
>>>>>> <parent>
>>>>>> <groupId>com</groupId>
>>>>>> <artifactId>kodak</artifactId>
>>>>>> <version>0.0.11-SNAPSHOT</****version>
>>>>>> <relativePath/>
>>>>>> </parent>
>>>>>>
>>>>>> I still get
>>>>>>
>>>>>> C:\Users\Eric\workspace\tree-****combo-box>mvn clean
>>>>>> [INFO] Scanning for projects...
>>>>>> Downloading:
>>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
>>>>>>
>>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/maven-metadata.xml<ht**
>>>>>> tp://repository.ca.kodak.com:**8082/nexus/content/groups/**
>>>>>> public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml>
>>>>>> >
>>>>>> [WARNING] Could not transfer metadata
>>>>>> com:kodak:0.0.11-SNAPSHOT/****maven-metadata.xml
>>>>>> from/to nexus (http://repository.ca.kodak.**
>>>>>>
>>>>>> com:8082/nexus/content/groups/****public<http://repository.ca.**
>>>>>> kodak.com:8082/nexus/content/**groups/public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>
>>>>>> >):
>>>>>> repository.ca.kodak.com
>>>>>> Downloading:
>>>>>> http://repository.ca.kodak.****com:8082/nexus/content/groups/***
>>>>>>
>>>>>> *public/com/kodak/0.0.11-****SNAPSHOT/kodak-0.0.11-****SNAPSHOT.pom<
>>>>>> http://**repository.ca.kodak.com:8082/**nexus/content/groups/public/*
>>>>>> *com/kodak/0.0.11-SNAPSHOT/**kodak-0.0.11-SNAPSHOT.pom<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom>
>>>>>> >
>>>>>> [ERROR] The build could not read 1 project -> [Help 1]
>>>>>> [ERROR]
>>>>>> [ERROR] The project
>>>>>> net.kolotyluk.experiment:tree-****combo-box:0.0.1-SNAPSHOT
>>>>>> (C:\Users\Eric\workspace\tree-****combo-box\pom.xml) has 1 error
>>>>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>>>>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
>>>>>> (http://repository.ca.kodak.*
>>>>>>
>>>>>> *com:8082/nexus/content/**groups/**public<http://**
>>>>>> repository.ca.kodak.com:8082/**nexus/content/groups/public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>
>>>>>> >):
>>>>>> repository.ca.kodak.com and 'parent.relativePath' points at no local
>>>>>> POM
>>>>>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
>>>>>> [ERROR]
>>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>>>>>> the
>>>>>> -e switch.
>>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>>>> [ERROR]
>>>>>> [ERROR] For more information about the errors and possible solutions,
>>>>>> please read the following articles:
>>>>>> [ERROR] [Help 1] http://cwiki.apache.org/****
>>>>>> confluence/display/MAVEN/**<http://cwiki.apache.org/**confluence/display/MAVEN/**>
>>>>>>
>>>>>> ProjectBuildingException<http:**//cwiki.apache.org/confluence/**
>>>>>> display/MAVEN/**ProjectBuildingException<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
>>>>>> >
>>>>>> [ERROR] [Help 2] http://cwiki.apache.org/****
>>>>>> confluence/display/MAVEN/**<http://cwiki.apache.org/**confluence/display/MAVEN/**>
>>>>>>
>>>>>> UnresolvableModelException<htt**p://cwiki.apache.org/**
>>>>>> confluence/display/MAVEN/**UnresolvableModelException<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException>
>>>>>> >
>>>>>>
>>>>>> It looks like Maven wants to download the Corporate POM because it
>>>>>> sees
>>>>>> it in Nexus, but craps out because it does not like the Project POM.
>>>>>> Maven
>>>>>> seems pretty certain that it wants parent.relativePath to point to a
>>>>>> local
>>>>>> POM.
>>>>>>
>>>>>> Is there a <userFriendly>true</****userFriendly> switch I can turn on
>>>>>> somewhere in Maven ;-)
>>>>>>
>>>>>> Cheers, Eric
>>>>>>
>>>>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>>>>>>
>>>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
>>>>>>> bimargulies@gmail.com>wrote:
>>>>>>>
>>>>>>> You just name the G/A/V and no relativePath, and Maven will
>>>>>>> download
>>>>>>>
>>>>>>>> just as it would a dependency.
>>>>>>>>
>>>>>>>> Well, not exactly; if there is no <relativePath> element present,
>>>>>>>> then
>>>>>>>>
>>>>>>> Maven behaves as though <relativePath>../pom.xml</****relativePath>
>>>>>>> were
>>>>>>> specified. If that file is a working copy that has not been
>>>>>>> refreshed
>>>>>>> from
>>>>>>> the SCM, then problems can ensue.
>>>>>>>
>>>>>>> I recall that someone mentioned specifying a relative path like this:
>>>>>>>
>>>>>>> <relativePath/>
>>>>>>>
>>>>>>>
>>>>>>> ...and that that was the only way to force Maven to truly resolve the
>>>>>>> pom
>>>>>>> from the repository, but I don't know if this is in fact true.
>>>>>>>
>>>>>>> Best,
>>>>>>> Laird
>>>>>>>
>>>>>>>
>>>>>>> ------------------------------****----------------------------**
>>>>> --**---------
>>>>> To unsubscribe, e-mail:
>>>>> users-unsubscribe@maven.**apac**he.org <http://apache.org><
>>>>> users-unsubscribe@**maven.apache.org<us...@maven.apache.org>
>>>>> >
>>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>>
>>>>>
>>>>>
>>> ------------------------------**------------------------------**
>>> ---------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>> ------------------------------**------------------------------**
>> ---------
>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Referencing a parent POM without relativePath
Posted by Eric Kolotyluk <er...@gmail.com>.
On 2012-11-23 7:01 PM, Benson Margulies wrote:
> On Fri, Nov 23, 2012 at 8:45 PM, Eric Kolotyluk
> <er...@gmail.com> wrote:
>> OK, I have added the following to our Corporate POM. Hopefully I, and
>> others, won't fall into this trap again.
>>
>> I still think the <userFriendly>true</userFriendly> version of Maven would
>> just do the right thing when there is no <relativePath/> element, and there
>> is no ../pom.xml. I can see no value in the current Maven behavior of
>> throwing an error the way it does.
> Eric,
>
> It does what you want. If it is not doing it for you, there's
> something wrong with your environment.
>
> None of our POMs have explicit relativePath elements, and they all
> work fine. The empty element is only needed when there *is* a
> ../pom.xml to avoid, but you are writing that you don't have one.
>
OK, I will play with this some more to see if I can replicate the
problem again.
Cheers, Eric
>
>> Cheers, Eric
>>
>> <!--
>> No parent for this POM! This is parent of all Kodak projects.
>> Top Level Project POMs should reference this POM with
>>
>> <parent>
>> <groupId>com</groupId>
>> <artifactId>kodak</artifactId>
>> <version>1.0.0</version>
>> <relativePath/>
>> </parent>
>>
>> The empty <relativePath/> element is necessary because com:kodak is a
>> seperate project that will never be in
>> the parent directory of your project. If <relativePath/> is missing,
>> Maven will look in ../ by default, and
>> then throw an error because it cannot find ../pom.xml (and you should
>> never have ../pom.xml).
>> -->
>>
>>
>> On 2012-11-23 12:47 PM, David Karr wrote:
>>> I had also discovered the difference between the missing vs. empty
>>> "relativePath" element. Although it was initially disconcerting that I
>>> had
>>> to specify an empty "relativePath" element to get what I assumed was the
>>> most reasonable behavior, I can also see the logic of the alternative with
>>> the default value. I prefer to separate the notion of "parent" pom from
>>> "aggregator" pom (a pom with a list of modules), but if you use a strategy
>>> that combines them, then the default value is more likely.
>>>
>>>
>>> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
>>> <er...@gmail.com>wrote:
>>>
>>>> DOH! I retract that previous message. I forgot to open my VPN connection
>>>> first.
>>>>
>>>> Putting <relativePath/> in the POM does work!
>>>>
>>>> So, would it be unreasonable if Maven treated the absence of the
>>>> <relativePath> element the same as <relativePath/>. That would make it
>>>> more
>>>> user friendly as far as I am concerned.
>>>>
>>>> Also, it was m2e that built the original project POM, and it did not put
>>>> <relativePath/> in the POM.
>>>>
>>>> Cheers, Eric
>>>>
>>>>
>>>>
>>>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
>>>>
>>>>> I tried putting <relativePath/> in my POM, but it does not fix things.
>>>>>
>>>>> <parent>
>>>>> <groupId>com</groupId>
>>>>> <artifactId>kodak</artifactId>
>>>>> <version>0.0.11-SNAPSHOT</**version>
>>>>> <relativePath/>
>>>>> </parent>
>>>>>
>>>>> I still get
>>>>>
>>>>> C:\Users\Eric\workspace\tree-**combo-box>mvn clean
>>>>> [INFO] Scanning for projects...
>>>>> Downloading:
>>>>> http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>>>>>
>>>>> *public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml>
>>>>> [WARNING] Could not transfer metadata
>>>>> com:kodak:0.0.11-SNAPSHOT/**maven-metadata.xml
>>>>> from/to nexus (http://repository.ca.kodak.**
>>>>>
>>>>> com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>>>>> repository.ca.kodak.com
>>>>> Downloading:
>>>>> http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>>>>>
>>>>> *public/com/kodak/0.0.11-**SNAPSHOT/kodak-0.0.11-**SNAPSHOT.pom<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom>
>>>>> [ERROR] The build could not read 1 project -> [Help 1]
>>>>> [ERROR]
>>>>> [ERROR] The project
>>>>> net.kolotyluk.experiment:tree-**combo-box:0.0.1-SNAPSHOT
>>>>> (C:\Users\Eric\workspace\tree-**combo-box\pom.xml) has 1 error
>>>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>>>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
>>>>> (http://repository.ca.kodak.*
>>>>>
>>>>> *com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>>>>> repository.ca.kodak.com and 'parent.relativePath' points at no local POM
>>>>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
>>>>> [ERROR]
>>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>>>> -e switch.
>>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>>> [ERROR]
>>>>> [ERROR] For more information about the errors and possible solutions,
>>>>> please read the following articles:
>>>>> [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/**
>>>>>
>>>>> ProjectBuildingException<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
>>>>> [ERROR] [Help 2] http://cwiki.apache.org/**confluence/display/MAVEN/**
>>>>>
>>>>> UnresolvableModelException<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException>
>>>>>
>>>>> It looks like Maven wants to download the Corporate POM because it sees
>>>>> it in Nexus, but craps out because it does not like the Project POM.
>>>>> Maven
>>>>> seems pretty certain that it wants parent.relativePath to point to a
>>>>> local
>>>>> POM.
>>>>>
>>>>> Is there a <userFriendly>true</**userFriendly> switch I can turn on
>>>>> somewhere in Maven ;-)
>>>>>
>>>>> Cheers, Eric
>>>>>
>>>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>>>>>
>>>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
>>>>>> bimargulies@gmail.com>wrote:
>>>>>>
>>>>>> You just name the G/A/V and no relativePath, and Maven will download
>>>>>>> just as it would a dependency.
>>>>>>>
>>>>>>> Well, not exactly; if there is no <relativePath> element present,
>>>>>>> then
>>>>>> Maven behaves as though <relativePath>../pom.xml</**relativePath> were
>>>>>> specified. If that file is a working copy that has not been refreshed
>>>>>> from
>>>>>> the SCM, then problems can ensue.
>>>>>>
>>>>>> I recall that someone mentioned specifying a relative path like this:
>>>>>>
>>>>>> <relativePath/>
>>>>>>
>>>>>>
>>>>>> ...and that that was the only way to force Maven to truly resolve the
>>>>>> pom
>>>>>> from the repository, but I don't know if this is in fact true.
>>>>>>
>>>>>> Best,
>>>>>> Laird
>>>>>>
>>>>>>
>>>> ------------------------------**------------------------------**---------
>>>> To unsubscribe, e-mail:
>>>> users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Benson Margulies <bi...@gmail.com>.
On Fri, Nov 23, 2012 at 8:45 PM, Eric Kolotyluk
<er...@gmail.com> wrote:
> OK, I have added the following to our Corporate POM. Hopefully I, and
> others, won't fall into this trap again.
>
> I still think the <userFriendly>true</userFriendly> version of Maven would
> just do the right thing when there is no <relativePath/> element, and there
> is no ../pom.xml. I can see no value in the current Maven behavior of
> throwing an error the way it does.
Eric,
It does what you want. If it is not doing it for you, there's
something wrong with your environment.
None of our POMs have explicit relativePath elements, and they all
work fine. The empty element is only needed when there *is* a
../pom.xml to avoid, but you are writing that you don't have one.
>
> Cheers, Eric
>
> <!--
> No parent for this POM! This is parent of all Kodak projects.
> Top Level Project POMs should reference this POM with
>
> <parent>
> <groupId>com</groupId>
> <artifactId>kodak</artifactId>
> <version>1.0.0</version>
> <relativePath/>
> </parent>
>
> The empty <relativePath/> element is necessary because com:kodak is a
> seperate project that will never be in
> the parent directory of your project. If <relativePath/> is missing,
> Maven will look in ../ by default, and
> then throw an error because it cannot find ../pom.xml (and you should
> never have ../pom.xml).
> -->
>
>
> On 2012-11-23 12:47 PM, David Karr wrote:
>>
>> I had also discovered the difference between the missing vs. empty
>> "relativePath" element. Although it was initially disconcerting that I
>> had
>> to specify an empty "relativePath" element to get what I assumed was the
>> most reasonable behavior, I can also see the logic of the alternative with
>> the default value. I prefer to separate the notion of "parent" pom from
>> "aggregator" pom (a pom with a list of modules), but if you use a strategy
>> that combines them, then the default value is more likely.
>>
>>
>> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
>> <er...@gmail.com>wrote:
>>
>>> DOH! I retract that previous message. I forgot to open my VPN connection
>>> first.
>>>
>>> Putting <relativePath/> in the POM does work!
>>>
>>> So, would it be unreasonable if Maven treated the absence of the
>>> <relativePath> element the same as <relativePath/>. That would make it
>>> more
>>> user friendly as far as I am concerned.
>>>
>>> Also, it was m2e that built the original project POM, and it did not put
>>> <relativePath/> in the POM.
>>>
>>> Cheers, Eric
>>>
>>>
>>>
>>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
>>>
>>>> I tried putting <relativePath/> in my POM, but it does not fix things.
>>>>
>>>> <parent>
>>>> <groupId>com</groupId>
>>>> <artifactId>kodak</artifactId>
>>>> <version>0.0.11-SNAPSHOT</**version>
>>>> <relativePath/>
>>>> </parent>
>>>>
>>>> I still get
>>>>
>>>> C:\Users\Eric\workspace\tree-**combo-box>mvn clean
>>>> [INFO] Scanning for projects...
>>>> Downloading:
>>>> http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>>>>
>>>> *public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml>
>>>> [WARNING] Could not transfer metadata
>>>> com:kodak:0.0.11-SNAPSHOT/**maven-metadata.xml
>>>> from/to nexus (http://repository.ca.kodak.**
>>>>
>>>> com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>>>> repository.ca.kodak.com
>>>> Downloading:
>>>> http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>>>>
>>>> *public/com/kodak/0.0.11-**SNAPSHOT/kodak-0.0.11-**SNAPSHOT.pom<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom>
>>>> [ERROR] The build could not read 1 project -> [Help 1]
>>>> [ERROR]
>>>> [ERROR] The project
>>>> net.kolotyluk.experiment:tree-**combo-box:0.0.1-SNAPSHOT
>>>> (C:\Users\Eric\workspace\tree-**combo-box\pom.xml) has 1 error
>>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
>>>> (http://repository.ca.kodak.*
>>>>
>>>> *com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>>>> repository.ca.kodak.com and 'parent.relativePath' points at no local POM
>>>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
>>>> [ERROR]
>>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>>> -e switch.
>>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>>> [ERROR]
>>>> [ERROR] For more information about the errors and possible solutions,
>>>> please read the following articles:
>>>> [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/**
>>>>
>>>> ProjectBuildingException<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
>>>> [ERROR] [Help 2] http://cwiki.apache.org/**confluence/display/MAVEN/**
>>>>
>>>> UnresolvableModelException<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException>
>>>>
>>>> It looks like Maven wants to download the Corporate POM because it sees
>>>> it in Nexus, but craps out because it does not like the Project POM.
>>>> Maven
>>>> seems pretty certain that it wants parent.relativePath to point to a
>>>> local
>>>> POM.
>>>>
>>>> Is there a <userFriendly>true</**userFriendly> switch I can turn on
>>>> somewhere in Maven ;-)
>>>>
>>>> Cheers, Eric
>>>>
>>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>>>>
>>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
>>>>> bimargulies@gmail.com>wrote:
>>>>>
>>>>> You just name the G/A/V and no relativePath, and Maven will download
>>>>>>
>>>>>> just as it would a dependency.
>>>>>>
>>>>>> Well, not exactly; if there is no <relativePath> element present,
>>>>>> then
>>>>>
>>>>> Maven behaves as though <relativePath>../pom.xml</**relativePath> were
>>>>> specified. If that file is a working copy that has not been refreshed
>>>>> from
>>>>> the SCM, then problems can ensue.
>>>>>
>>>>> I recall that someone mentioned specifying a relative path like this:
>>>>>
>>>>> <relativePath/>
>>>>>
>>>>>
>>>>> ...and that that was the only way to force Maven to truly resolve the
>>>>> pom
>>>>> from the repository, but I don't know if this is in fact true.
>>>>>
>>>>> Best,
>>>>> Laird
>>>>>
>>>>>
>>> ------------------------------**------------------------------**---------
>>> To unsubscribe, e-mail:
>>> users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Eric Kolotyluk <er...@gmail.com>.
OK, I have added the following to our Corporate POM. Hopefully I, and
others, won't fall into this trap again.
I still think the <userFriendly>true</userFriendly> version of Maven
would just do the right thing when there is no <relativePath/> element,
and there is no ../pom.xml. I can see no value in the current Maven
behavior of throwing an error the way it does.
Cheers, Eric
<!--
No parent for this POM! This is parent of all Kodak projects.
Top Level Project POMs should reference this POM with
<parent>
<groupId>com</groupId>
<artifactId>kodak</artifactId>
<version>1.0.0</version>
<relativePath/>
</parent>
The empty <relativePath/> element is necessary because com:kodak
is a seperate project that will never be in
the parent directory of your project. If <relativePath/> is
missing, Maven will look in ../ by default, and
then throw an error because it cannot find ../pom.xml (and you
should never have ../pom.xml).
-->
On 2012-11-23 12:47 PM, David Karr wrote:
> I had also discovered the difference between the missing vs. empty
> "relativePath" element. Although it was initially disconcerting that I had
> to specify an empty "relativePath" element to get what I assumed was the
> most reasonable behavior, I can also see the logic of the alternative with
> the default value. I prefer to separate the notion of "parent" pom from
> "aggregator" pom (a pom with a list of modules), but if you use a strategy
> that combines them, then the default value is more likely.
>
>
> On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
> <er...@gmail.com>wrote:
>
>> DOH! I retract that previous message. I forgot to open my VPN connection
>> first.
>>
>> Putting <relativePath/> in the POM does work!
>>
>> So, would it be unreasonable if Maven treated the absence of the
>> <relativePath> element the same as <relativePath/>. That would make it more
>> user friendly as far as I am concerned.
>>
>> Also, it was m2e that built the original project POM, and it did not put
>> <relativePath/> in the POM.
>>
>> Cheers, Eric
>>
>>
>>
>> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
>>
>>> I tried putting <relativePath/> in my POM, but it does not fix things.
>>>
>>> <parent>
>>> <groupId>com</groupId>
>>> <artifactId>kodak</artifactId>
>>> <version>0.0.11-SNAPSHOT</**version>
>>> <relativePath/>
>>> </parent>
>>>
>>> I still get
>>>
>>> C:\Users\Eric\workspace\tree-**combo-box>mvn clean
>>> [INFO] Scanning for projects...
>>> Downloading: http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>>> *public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml>
>>> [WARNING] Could not transfer metadata com:kodak:0.0.11-SNAPSHOT/**maven-metadata.xml
>>> from/to nexus (http://repository.ca.kodak.**
>>> com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>>> repository.ca.kodak.com
>>> Downloading: http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>>> *public/com/kodak/0.0.11-**SNAPSHOT/kodak-0.0.11-**SNAPSHOT.pom<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom>
>>> [ERROR] The build could not read 1 project -> [Help 1]
>>> [ERROR]
>>> [ERROR] The project net.kolotyluk.experiment:tree-**combo-box:0.0.1-SNAPSHOT
>>> (C:\Users\Eric\workspace\tree-**combo-box\pom.xml) has 1 error
>>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus (http://repository.ca.kodak.*
>>> *com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>>> repository.ca.kodak.com and 'parent.relativePath' points at no local POM
>>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
>>> [ERROR]
>>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>>> -e switch.
>>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>>> [ERROR]
>>> [ERROR] For more information about the errors and possible solutions,
>>> please read the following articles:
>>> [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/**
>>> ProjectBuildingException<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
>>> [ERROR] [Help 2] http://cwiki.apache.org/**confluence/display/MAVEN/**
>>> UnresolvableModelException<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException>
>>>
>>> It looks like Maven wants to download the Corporate POM because it sees
>>> it in Nexus, but craps out because it does not like the Project POM. Maven
>>> seems pretty certain that it wants parent.relativePath to point to a local
>>> POM.
>>>
>>> Is there a <userFriendly>true</**userFriendly> switch I can turn on
>>> somewhere in Maven ;-)
>>>
>>> Cheers, Eric
>>>
>>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>>>
>>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
>>>> bimargulies@gmail.com>wrote:
>>>>
>>>> You just name the G/A/V and no relativePath, and Maven will download
>>>>> just as it would a dependency.
>>>>>
>>>>> Well, not exactly; if there is no <relativePath> element present, then
>>>> Maven behaves as though <relativePath>../pom.xml</**relativePath> were
>>>> specified. If that file is a working copy that has not been refreshed
>>>> from
>>>> the SCM, then problems can ensue.
>>>>
>>>> I recall that someone mentioned specifying a relative path like this:
>>>>
>>>> <relativePath/>
>>>>
>>>>
>>>> ...and that that was the only way to force Maven to truly resolve the pom
>>>> from the repository, but I don't know if this is in fact true.
>>>>
>>>> Best,
>>>> Laird
>>>>
>>>>
>> ------------------------------**------------------------------**---------
>> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by David Karr <da...@gmail.com>.
I had also discovered the difference between the missing vs. empty
"relativePath" element. Although it was initially disconcerting that I had
to specify an empty "relativePath" element to get what I assumed was the
most reasonable behavior, I can also see the logic of the alternative with
the default value. I prefer to separate the notion of "parent" pom from
"aggregator" pom (a pom with a list of modules), but if you use a strategy
that combines them, then the default value is more likely.
On Fri, Nov 23, 2012 at 12:34 PM, Eric Kolotyluk
<er...@gmail.com>wrote:
> DOH! I retract that previous message. I forgot to open my VPN connection
> first.
>
> Putting <relativePath/> in the POM does work!
>
> So, would it be unreasonable if Maven treated the absence of the
> <relativePath> element the same as <relativePath/>. That would make it more
> user friendly as far as I am concerned.
>
> Also, it was m2e that built the original project POM, and it did not put
> <relativePath/> in the POM.
>
> Cheers, Eric
>
>
>
> On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
>
>> I tried putting <relativePath/> in my POM, but it does not fix things.
>>
>> <parent>
>> <groupId>com</groupId>
>> <artifactId>kodak</artifactId>
>> <version>0.0.11-SNAPSHOT</**version>
>> <relativePath/>
>> </parent>
>>
>> I still get
>>
>> C:\Users\Eric\workspace\tree-**combo-box>mvn clean
>> [INFO] Scanning for projects...
>> Downloading: http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>> *public/com/kodak/0.0.11-**SNAPSHOT/maven-metadata.xml<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml>
>> [WARNING] Could not transfer metadata com:kodak:0.0.11-SNAPSHOT/**maven-metadata.xml
>> from/to nexus (http://repository.ca.kodak.**
>> com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>> repository.ca.kodak.com
>> Downloading: http://repository.ca.kodak.**com:8082/nexus/content/groups/*
>> *public/com/kodak/0.0.11-**SNAPSHOT/kodak-0.0.11-**SNAPSHOT.pom<http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom>
>> [ERROR] The build could not read 1 project -> [Help 1]
>> [ERROR]
>> [ERROR] The project net.kolotyluk.experiment:tree-**combo-box:0.0.1-SNAPSHOT
>> (C:\Users\Eric\workspace\tree-**combo-box\pom.xml) has 1 error
>> [ERROR] Non-resolvable parent POM: Could not transfer artifact
>> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus (http://repository.ca.kodak.*
>> *com:8082/nexus/content/groups/**public<http://repository.ca.kodak.com:8082/nexus/content/groups/public>):
>> repository.ca.kodak.com and 'parent.relativePath' points at no local POM
>> @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with the
>> -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1] http://cwiki.apache.org/**confluence/display/MAVEN/**
>> ProjectBuildingException<http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException>
>> [ERROR] [Help 2] http://cwiki.apache.org/**confluence/display/MAVEN/**
>> UnresolvableModelException<http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException>
>>
>> It looks like Maven wants to download the Corporate POM because it sees
>> it in Nexus, but craps out because it does not like the Project POM. Maven
>> seems pretty certain that it wants parent.relativePath to point to a local
>> POM.
>>
>> Is there a <userFriendly>true</**userFriendly> switch I can turn on
>> somewhere in Maven ;-)
>>
>> Cheers, Eric
>>
>> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>>
>>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <
>>> bimargulies@gmail.com>wrote:
>>>
>>> You just name the G/A/V and no relativePath, and Maven will download
>>>> just as it would a dependency.
>>>>
>>>> Well, not exactly; if there is no <relativePath> element present, then
>>> Maven behaves as though <relativePath>../pom.xml</**relativePath> were
>>> specified. If that file is a working copy that has not been refreshed
>>> from
>>> the SCM, then problems can ensue.
>>>
>>> I recall that someone mentioned specifying a relative path like this:
>>>
>>> <relativePath/>
>>>
>>>
>>> ...and that that was the only way to force Maven to truly resolve the pom
>>> from the repository, but I don't know if this is in fact true.
>>>
>>> Best,
>>> Laird
>>>
>>>
>>
>
> ------------------------------**------------------------------**---------
> To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org<us...@maven.apache.org>
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: Referencing a parent POM without relativePath
Posted by Eric Kolotyluk <er...@gmail.com>.
DOH! I retract that previous message. I forgot to open my VPN connection
first.
Putting <relativePath/> in the POM does work!
So, would it be unreasonable if Maven treated the absence of the
<relativePath> element the same as <relativePath/>. That would make it
more user friendly as far as I am concerned.
Also, it was m2e that built the original project POM, and it did not put
<relativePath/> in the POM.
Cheers, Eric
On 2012-11-23 12:22 PM, Eric Kolotyluk wrote:
> I tried putting <relativePath/> in my POM, but it does not fix things.
>
> <parent>
> <groupId>com</groupId>
> <artifactId>kodak</artifactId>
> <version>0.0.11-SNAPSHOT</version>
> <relativePath/>
> </parent>
>
> I still get
>
> C:\Users\Eric\workspace\tree-combo-box>mvn clean
> [INFO] Scanning for projects...
> Downloading:
> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml
> [WARNING] Could not transfer metadata
> com:kodak:0.0.11-SNAPSHOT/maven-metadata.xml from/to nexus
> (http://repository.ca.kodak.com:8082/nexus/content/groups/public):
> repository.ca.kodak.com
> Downloading:
> http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project
> net.kolotyluk.experiment:tree-combo-box:0.0.1-SNAPSHOT
> (C:\Users\Eric\workspace\tree-combo-box\pom.xml) has 1 error
> [ERROR] Non-resolvable parent POM: Could not transfer artifact
> com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
> (http://repository.ca.kodak.com:8082/nexus/content/groups/public):
> repository.ca.kodak.com and 'parent.relativePath' points at no local
> POM @ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with
> the -e switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions,
> please read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
> [ERROR] [Help 2]
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
>
> It looks like Maven wants to download the Corporate POM because it
> sees it in Nexus, but craps out because it does not like the Project
> POM. Maven seems pretty certain that it wants parent.relativePath to
> point to a local POM.
>
> Is there a <userFriendly>true</userFriendly> switch I can turn on
> somewhere in Maven ;-)
>
> Cheers, Eric
>
> On 2012-11-23 9:05 AM, Laird Nelson wrote:
>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies
>> <bi...@gmail.com>wrote:
>>
>>> You just name the G/A/V and no relativePath, and Maven will download
>>> just as it would a dependency.
>>>
>> Well, not exactly; if there is no <relativePath> element present, then
>> Maven behaves as though <relativePath>../pom.xml</relativePath> were
>> specified. If that file is a working copy that has not been
>> refreshed from
>> the SCM, then problems can ensue.
>>
>> I recall that someone mentioned specifying a relative path like this:
>>
>> <relativePath/>
>>
>>
>> ...and that that was the only way to force Maven to truly resolve the
>> pom
>> from the repository, but I don't know if this is in fact true.
>>
>> Best,
>> Laird
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Eric Kolotyluk <er...@gmail.com>.
This problem is resolved. I forgot to bring up my VPN connections, so my
local system could not see the Nexus server.
I apologize for the confusion.
Cheers, Eric
On 2012-11-23 7:02 PM, Benson Margulies wrote:
> On Fri, Nov 23, 2012 at 10:00 PM, Ron Wheeler
> <rw...@artifact-software.com> wrote:
>> On 23/11/2012 3:22 PM, Eric Kolotyluk wrote:
>>> Unknown host repository.ca.kodak.com
>> What is causing that?
> Indeed this needs to be sorted first.
>
>> --
>> Ron Wheeler
>> President
>> Artifact Software Inc
>> email: rwheeler@artifact-software.com
>> skype: ronaldmwheeler
>> phone: 866-970-2435, ext 102
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Benson Margulies <bi...@gmail.com>.
On Fri, Nov 23, 2012 at 10:00 PM, Ron Wheeler
<rw...@artifact-software.com> wrote:
> On 23/11/2012 3:22 PM, Eric Kolotyluk wrote:
>>
>> Unknown host repository.ca.kodak.com
>
> What is causing that?
Indeed this needs to be sorted first.
>
> --
> Ron Wheeler
> President
> Artifact Software Inc
> email: rwheeler@artifact-software.com
> skype: ronaldmwheeler
> phone: 866-970-2435, ext 102
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Ron Wheeler <rw...@artifact-software.com>.
On 23/11/2012 3:22 PM, Eric Kolotyluk wrote:
> Unknown host repository.ca.kodak.com
What is causing that?
--
Ron Wheeler
President
Artifact Software Inc
email: rwheeler@artifact-software.com
skype: ronaldmwheeler
phone: 866-970-2435, ext 102
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Eric Kolotyluk <er...@gmail.com>.
I tried putting <relativePath/> in my POM, but it does not fix things.
<parent>
<groupId>com</groupId>
<artifactId>kodak</artifactId>
<version>0.0.11-SNAPSHOT</version>
<relativePath/>
</parent>
I still get
C:\Users\Eric\workspace\tree-combo-box>mvn clean
[INFO] Scanning for projects...
Downloading:
http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/maven-metadata.xml
[WARNING] Could not transfer metadata
com:kodak:0.0.11-SNAPSHOT/maven-metadata.xml from/to nexus
(http://repository.ca.kodak.com:8082/nexus/content/groups/public):
repository.ca.kodak.com
Downloading:
http://repository.ca.kodak.com:8082/nexus/content/groups/public/com/kodak/0.0.11-SNAPSHOT/kodak-0.0.11-SNAPSHOT.pom
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project
net.kolotyluk.experiment:tree-combo-box:0.0.1-SNAPSHOT
(C:\Users\Eric\workspace\tree-combo-box\pom.xml) has 1 error
[ERROR] Non-resolvable parent POM: Could not transfer artifact
com:kodak:pom:0.0.11-SNAPSHOT from/to nexus
(http://repository.ca.kodak.com:8082/nexus/content/groups/public):
repository.ca.kodak.com and 'parent.relativePath' points at no local POM
@ line 9, column 11: Unknown host repository.ca.kodak.com -> [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException
It looks like Maven wants to download the Corporate POM because it sees
it in Nexus, but craps out because it does not like the Project POM.
Maven seems pretty certain that it wants parent.relativePath to point to
a local POM.
Is there a <userFriendly>true</userFriendly> switch I can turn on
somewhere in Maven ;-)
Cheers, Eric
On 2012-11-23 9:05 AM, Laird Nelson wrote:
> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <bi...@gmail.com>wrote:
>
>> You just name the G/A/V and no relativePath, and Maven will download
>> just as it would a dependency.
>>
> Well, not exactly; if there is no <relativePath> element present, then
> Maven behaves as though <relativePath>../pom.xml</relativePath> were
> specified. If that file is a working copy that has not been refreshed from
> the SCM, then problems can ensue.
>
> I recall that someone mentioned specifying a relative path like this:
>
> <relativePath/>
>
>
> ...and that that was the only way to force Maven to truly resolve the pom
> from the repository, but I don't know if this is in fact true.
>
> Best,
> Laird
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Benson Margulies <bi...@gmail.com>.
On Fri, Nov 23, 2012 at 12:11 PM, Anders Hammar <an...@hammar.net> wrote:
> Well, the corp pom should not be in the parent folder of any project. It's
> a standalone project.
Well, precisely. 99% of the time you run 'svn co', and you get a
directory in which ../pom.xml does not exist, and running mvn causes
mvn to go out to repositories. If someone has a counter-example, we
need a test case.
>
> /Anders
>
>
> On Fri, Nov 23, 2012 at 6:05 PM, Laird Nelson <lj...@gmail.com> wrote:
>
>> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <bimargulies@gmail.com
>> >wrote:
>>
>> > You just name the G/A/V and no relativePath, and Maven will download
>> > just as it would a dependency.
>> >
>>
>> Well, not exactly; if there is no <relativePath> element present, then
>> Maven behaves as though <relativePath>../pom.xml</relativePath> were
>> specified. If that file is a working copy that has not been refreshed from
>> the SCM, then problems can ensue.
>>
>> I recall that someone mentioned specifying a relative path like this:
>>
>> <relativePath/>
>>
>>
>> ...and that that was the only way to force Maven to truly resolve the pom
>> from the repository, but I don't know if this is in fact true.
>>
>> Best,
>> Laird
>>
>> --
>> http://about.me/lairdnelson
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Referencing a parent POM without relativePath
Posted by Laird Nelson <lj...@gmail.com>.
On Fri, Nov 23, 2012 at 12:11 PM, Anders Hammar <an...@hammar.net> wrote:
> Well, the corp pom should not be in the parent folder of any project. It's
> a standalone project.
>
Yes; sorry if I contributed noise--my point was only to call attention to
what the absence of <relativePath> meant, not to comment on any particular
project layout.
Best,
Laird
--
http://about.me/lairdnelson
Re: Referencing a parent POM without relativePath
Posted by Anders Hammar <an...@hammar.net>.
Well, the corp pom should not be in the parent folder of any project. It's
a standalone project.
/Anders
On Fri, Nov 23, 2012 at 6:05 PM, Laird Nelson <lj...@gmail.com> wrote:
> On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <bimargulies@gmail.com
> >wrote:
>
> > You just name the G/A/V and no relativePath, and Maven will download
> > just as it would a dependency.
> >
>
> Well, not exactly; if there is no <relativePath> element present, then
> Maven behaves as though <relativePath>../pom.xml</relativePath> were
> specified. If that file is a working copy that has not been refreshed from
> the SCM, then problems can ensue.
>
> I recall that someone mentioned specifying a relative path like this:
>
> <relativePath/>
>
>
> ...and that that was the only way to force Maven to truly resolve the pom
> from the repository, but I don't know if this is in fact true.
>
> Best,
> Laird
>
> --
> http://about.me/lairdnelson
>
Re: Referencing a parent POM without relativePath
Posted by Laird Nelson <lj...@gmail.com>.
On Fri, Nov 23, 2012 at 11:22 AM, Benson Margulies <bi...@gmail.com>wrote:
> You just name the G/A/V and no relativePath, and Maven will download
> just as it would a dependency.
>
Well, not exactly; if there is no <relativePath> element present, then
Maven behaves as though <relativePath>../pom.xml</relativePath> were
specified. If that file is a working copy that has not been refreshed from
the SCM, then problems can ensue.
I recall that someone mentioned specifying a relative path like this:
<relativePath/>
...and that that was the only way to force Maven to truly resolve the pom
from the repository, but I don't know if this is in fact true.
Best,
Laird
--
http://about.me/lairdnelson
Re: Referencing a parent POM without relativePath
Posted by Benson Margulies <bi...@gmail.com>.
Why don't you think that Maven will fish out a disconnected parent
from Nexus? Many builds all over depend on this behavior.
You just name the G/A/V and no relativePath, and Maven will download
just as it would a dependency.
If this isn't working for you we'd need more information to diagnose.
On Fri, Nov 23, 2012 at 10:30 AM, Eric Kolotyluk
<er...@gmail.com> wrote:
> I am playing around with getting our Corporate POM process working
> correctly, but running into problems.
>
> I have things configured so that people need to reference it without using
> <relativePath>blah</relativePath> because I want them to get it from the
> repository and not from Perforce. In particular, I don't want to force
> people to make their project POM dependent on some arbitrary place that the
> Corporate POM is mapped from source control.
>
> This works well if the Corporate POM is already in the local repository,
> but fails completely if it is not in the local repository. Even when the
> Corporate POM is in Nexus, Maven will not look there for it. Is there
> something I can put in the settings.xml that will force Maven to get the
> Corporate POM from Nexus?
>
> Currently people are forced to 'seed' their local repository with the
> Corporate POM, which is really a hassle.
>
> What do other people do who have a top level or Corporate POM for all their
> projects?
>
> Cheers, Eric
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org