Re: [cf-dev] Problem for building californium following pom.xml changes

["Hudalla Kai (INST/ESY)" <Kai.Hudalla@xxxxxxxxxxxx>]

Yes, that was a silly thing to do to put the definition of the eclipse snapshot repo into the top most parent POM which can only be downloaded from the eclipse snapshot repository ;-)

I agree that it should be sufficient to add that definition "one level lower" to Californium's five modules' POM files to work around that problem.

Are you going to do that, Matthias?

Regards,
Kai


> -----Original Message-----
> From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx] On
> Behalf Of Kovatsch Matthias
> Sent: Wednesday, September 30, 2015 9:35 PM
> To: Californium (Cf) developer discussions
> Subject: Re: [cf-dev] Problem for building californium following
> pom.xml changes
> 
> Hi Mathieu
> 
> Thanks for raising this!
> I just checked and noticed that the snapshot repo is missing in the
> module POMs. Since snapshots will never be available on Maven Central,
> we have to duplicate this info again.
> 
> Kai, can you confirm this? (Since I just adapted the scandium-parent
> for the new californium-parent ;) )
> 
> Ciao
> Matthias
> 
> > -----Original Message-----
> > From: cf-dev-bounces@xxxxxxxxxxx [mailto:cf-dev-bounces@xxxxxxxxxxx]
> > On Behalf Of Mathieu Goessens
> > Sent: Wednesday, 30 September 2015 19:47
> > To: cf-dev@xxxxxxxxxxx
> > Subject: [cf-dev] Problem for building californium following pom.xml
> > changes
> >
> > Hi folks,
> >
> > I just pulled the last version of californium from github.
> >
> > I now have a problem when trying to build it:
> >
> >
> >
> > californium$ mvn clean install
> > [INFO] Scanning for projects...
> > [ERROR] The build could not read 1 project -> [Help 1] [ERROR]
> > [ERROR]   The project
> > org.eclipse.californium:californium-parent:1.0.0-SNAPSHOT
> > (/tmp/californium.core/pom.xml) has 1 error
> > [ERROR]     Non-resolvable parent POM: Could not find artifact
> > org.eclipse.californium:parent:pom:1.0.0-SNAPSHOT and
> 'parent.relativePath'
> > points at wrong local POM @ line 8, column 10 -> [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/ProjectBuildingExcept
> > ion
> > [ERROR] [Help 2]
> >
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelExce
> > pti
> > on
> > californium$
> >
> >
> >
> > How to reproduce ?
> >
> > [$ rm ~/.m2/repository] # this will flush the local maven repository;
> > maybe needed if you already have
> > https://github.com/eclipse/californium/
> > $ cd /tmp/
> > $ git clone https://github.com/eclipse/californium.core/
> > $ cd californium.core
> > $ mvn clean install
> >
> >
> >
> > How to fix it locally ?
> >
> > $ cd /tmp/
> > $ git clone https://github.com/eclipse/californium/
> > $ cd californium
> > $ mvn clean install
> > $ cd /tmp
> > $ git clone https://github.com/eclipse/californium.core/$
> > $ cd californium.core
> > $ mvn clean install
> >
> >
> >
> > How to fix it for everybody ?
> >
> > I am not a maven guru, but it looks that
> > https://github.com/eclipse/californium/pom.xml needs to be included
> > for building californium.core and submodules. Something missing in
> > californium.core's pom ? the reference to this californium/pom.xml or
> > the repository it should be available in ?
> >
> > Thanks in advance,
> >
> > Best,
> >
> > --
> > Mathieu Goessens
> > Research Engineer
> > Telecom-Bretagne
> >
> >
> 
> _______________________________________________
> cf-dev mailing list
> cf-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit https://dev.eclipse.org/mailman/listinfo/cf-dev