Hmmm ... repo trouble ... might that be related to what I am experiencing?

I tried to be a good guy and brush up my qi4jing for the seminar, so yesterday 
I made a fresh clone git://dscm.ops4j.org/qi4j-tutorials.git to do some hacking 
around on my own. However, when mvn installing the "Qi4j Tutorial - Composite" 
build failed (those before that one succeeded).

I got
<terminalsnippet>
[INFO] ------------------------------------------------------------------------
[INFO] Building Qi4j Tutorial - Composite
[INFO]    task-segment: [install]
[INFO] ------------------------------------------------------------------------
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
Downloading: 
http://repository.ops4j.org/mvn-snapshots/org/openrdf/sesame/sesame-model/2.3.0/sesame-model-2.3.0.pom
Downloading: 
http://repo1.maven.org/maven2/org/openrdf/sesame/sesame-model/2.3.0/sesame-model-2.3.0.pom
Downloading: 
http://repository.ops4j.org/mvn-snapshots/org/openrdf/sesame/sesame-rio-n3/2.3.0/sesame-rio-n3-2.3.0.pom
Downloading: 
http://repo1.maven.org/maven2/org/openrdf/sesame/sesame-rio-n3/2.3.0/sesame-rio-n3-2.3.0.pom
Downloading: 
http://repository.ops4j.org/mvn-snapshots/org/openrdf/sesame/sesame-core/2.3.0/sesame-core-2.3.0.pom
Downloading: 
http://repo1.maven.org/maven2/org/openrdf/sesame/sesame-core/2.3.0/sesame-core-2.3.0.pom
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error building POM (may not be this project's POM).


Project ID: null:sesame-runtime:jar:null

Reason: Cannot find parent: org.openrdf.sesame:sesame-core for project: 
null:sesame-runtime:jar:null for project null:sesame-runtime:jar:null
</terminalsnippet>

And, by the way, my config is
<terminalsnippet>
dajob04:composites danbjlocal$ mvn -v
Maven version: 2.0.9
Java version: 1.6.0_15
OS name: "mac os x" version: "10.6.2" arch: "x86_64" Family: "mac"
</terminalsnippet>

I know you are probably all totally preoccupied today, but if someone can shed 
some light without spending too much time I would be grateful. (During the day 
I am home on parental leave with my two sons, so I will not be able to do much 
until I step on the train to go to the seminar.)


Yours

   Dan



________________________________________
Från: [email protected] [[email protected]] 
f&#246;r Edward Yakop [[email protected]]
Skickat: den 26 januari 2010 08:09
Till: niclas; qi4j-dev
Ämne: Re: [qi4j-dev] Tomorrow

Ouch!
Perhaps we should try to get nexus open source license and roll our
own nexus instance like jboss etcs.

Regards,
Edward Yakop



On Tue, Jan 26, 2010 at 14:49, Niclas Hedhman <[email protected]> wrote:
> Gang!!!!
>
> Release via Sonatype's OSS Nexus hosting is aborted!!!
>
> Sonatype requires that no other repositories are referenced in the
> POMs. All dependent artifacts must reside on Central Repository, or we
> can't be sync'd up to Central. I understand the rationale (breakage
> when dependencies move location), BUT I completely disagree with the
> solution... (A federated referral system across participating
> repositories should be the way to deal with it, but I disgress).
>
> I will try and revert everything back to using our own repository, but
> before that, I will instead generate the SDK build locally and upload
> to the site so it can be downloaded.
>
>
> Cheers
> --
> Niclas Hedhman, Software Developer
> http://www.qi4j.org - New Energy for Java
>
> I  live here; http://tinyurl.com/2qq9er
> I  work here; http://tinyurl.com/2ymelc
> I relax here; http://tinyurl.com/2cgsug
>
> _______________________________________________
> qi4j-dev mailing list
> [email protected]
> http://lists.ops4j.org/mailman/listinfo/qi4j-dev
>

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

_______________________________________________
qi4j-dev mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/qi4j-dev

Reply via email to