Snapshots resolution issue between two repositories

[Julien CARSIQUE]

Hello,

I cannot manage to fix or workaround with the following dependencies
resolution issue.
We have two Nexus instances: a public one with nightly snapshots
depending on testing conditions and an internal one with snapshots by
commits. The internal Nexus is binded on the public one.

Internal Nexus:
- snapshots (local internal repository with daily snapshots)
- public-snapshot (proxy on public Nexus with nightly snapshots)
- internal-snapshots (group of internal-snapshots and public-snapshot)

The fact is we have a deprecated version in public-snapshot
   
http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
and a *good* version in snapshots
   
http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom

Using Maven (2.0.10) resolution, I get the 20090925 version.
Using Nexus UI search, I get the same *bad* version:
   
http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
whereas the good one is available:
   
http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom

I don't understand why it takes an older one than the more recent available.
I tried re-index, empty cache, rebuild metadata, ..., on public-snapshot
and on snapshots.

Is it a known bug ? Is there some workaround ? Did I failed in some
configuration ?

Thanks,

--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
jcarsique@... | Tel: [phone]


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Tamás Cservenák]

Hi Julien,

you are right here, but this seems like a Maven issue. Nexus uses the Maven Artifact stuff (version 2.2.1 currently), and this is from there:

http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup

It seems that only build number is compared at all. This would explain why maven and also nexus behaves the same wrong way.

Thanks,

~t~

On Tue, Oct 6, 2009 at 5:10 PM, Julien CARSIQUE <jcarsique@...> wrote:

Hello,

I cannot manage to fix or workaround with the following dependencies resolution issue.
We have two Nexus instances: a public one with nightly snapshots depending on testing conditions and an internal one with snapshots by commits. The internal Nexus is binded on the public one.

Internal Nexus:
- snapshots (local internal repository with daily snapshots)
- public-snapshot (proxy on public Nexus with nightly snapshots)
- internal-snapshots (group of internal-snapshots and public-snapshot)

The fact is we have a deprecated version in public-snapshot
  http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
and a *good* version in snapshots
  http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom

Using Maven (2.0.10) resolution, I get the 20090925 version.
Using Nexus UI search, I get the same *bad* version:
  http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
whereas the good one is available:
  http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom

I don't understand why it takes an older one than the more recent available.
I tried re-index, empty cache, rebuild metadata, ..., on public-snapshot and on snapshots.

Is it a known bug ? Is there some workaround ? Did I failed in some configuration ?

Thanks,

--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
jcarsique@... | Tel: [phone]


---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Julien CARSIQUE]

After many tries,

I deployed again into "snapshots" without better results (still
receiving the old one from public-snapshots):
    [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for
updates from public-snapshot
    [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for
updates from internal-snapshots
    Downloading:
http://maven.in.nuxeo.com/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20090925.015004-82.pom
    61K downloaded

then, I finally deployed into "public-snapshot" and of course I got the
good artifact:
    [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for
updates from public-snapshot
    [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for
updates from internal-snapshots
    Downloading:
http://maven.nuxeo.org/public-snapshot/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20091006.153540-83.pom
    68K downloaded

Stranger is on http://maven.in.nuxeo.com/nexus/index.html#nexus-search 
where searching for nuxeo-ecm:5.2.1-SNAPSHOT gives two results:
    public-snapshot (remote)   5.2.1-SNAPSHOT ->
nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
    snapshots (local)                5.2.1-SNAPSHOT ->
nuxeo-ecm-5.2.1-*20091006*.153450-66.pom
so why the group of both return the oldest ?

PS: I use Nexus Version 1.3.6 Open Source

Thanks,

Julien CARSIQUE a écrit :

> Hello,
>
> I cannot manage to fix or workaround with the following dependencies
> resolution issue.
> We have two Nexus instances: a public one with nightly snapshots
> depending on testing conditions and an internal one with snapshots by
> commits. The internal Nexus is binded on the public one.
>
> Internal Nexus:
> - snapshots (local internal repository with daily snapshots)
> - public-snapshot (proxy on public Nexus with nightly snapshots)
> - internal-snapshots (group of internal-snapshots and public-snapshot)
>
> The fact is we have a deprecated version in public-snapshot
>    
> http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom 
>
> and a *good* version in snapshots
>    
> http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom 
>
>
> Using Maven (2.0.10) resolution, I get the 20090925 version.
> Using Nexus UI search, I get the same *bad* version:
>    
> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom 
>
> whereas the good one is available:
>    
> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom 
>
>
> I don't understand why it takes an older one than the more recent
> available.
> I tried re-index, empty cache, rebuild metadata, ..., on
> public-snapshot and on snapshots.
>
> Is it a known bug ? Is there some workaround ? Did I failed in some
> configuration ?
>
> Thanks,
>

--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform



---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Julien CARSIQUE]

Hello,

What do you mean with build number ? In a jar I would have looked for
something in the manifest... but in a pom ?

Thank you Tamás,

Tamás Cservenák a écrit :

> Hi Julien,
>
> you are right here, but this seems like a Maven issue. Nexus uses the
> Maven Artifact stuff (version 2.2.1 currently), and this is from there:
>
> http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup
>
> It seems that only build number is compared at all. This would explain
> why maven and also nexus behaves the same wrong way.
>
> Thanks,
> ~t~
>
> On Tue, Oct 6, 2009 at 5:10 PM, Julien CARSIQUE <jcarsique@...
> <mailto:jcarsique@...>> wrote:
>
>     Hello,
>
>     I cannot manage to fix or workaround with the following
>     dependencies resolution issue.
>     We have two Nexus instances: a public one with nightly snapshots
>     depending on testing conditions and an internal one with snapshots
>     by commits. The internal Nexus is binded on the public one.
>
>     Internal Nexus:
>     - snapshots (local internal repository with daily snapshots)
>     - public-snapshot (proxy on public Nexus with nightly snapshots)
>     - internal-snapshots (group of internal-snapshots and public-snapshot)
>
>     The fact is we have a deprecated version in public-snapshot
>      
>     http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>     and a *good* version in snapshots
>      
>     http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>
>     Using Maven (2.0.10) resolution, I get the 20090925 version.
>     Using Nexus UI search, I get the same *bad* version:
>      
>     http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>     whereas the good one is available:
>      
>     http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>
>     I don't understand why it takes an older one than the more recent
>     available.
>     I tried re-index, empty cache, rebuild metadata, ..., on
>     public-snapshot and on snapshots.
>
>     Is it a known bug ? Is there some workaround ? Did I failed in
>     some configuration ?
>
>     Thanks,
>
>     --
>     Julien Carsique, Nuxeo (Paris, France)
>     www.nuxeo.com <http://www.nuxeo.com> - The Open Source ECM
>     Platform - www.nuxeo.org <http://www.nuxeo.org>
>     Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>     jcarsique@... <mailto:jcarsique@...> | Tel: +33 1 40
>     33 79 87
>
>
>     ---------------------------------------------------------------------
>     To unsubscribe, e-mail: nexus-user-unsubscribe@...
>     <mailto:nexus-user-unsubscribe@...>
>     For additional commands, e-mail: nexus-user-help@...
>     <mailto:nexus-user-help@...>
>
>

--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform




---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian Fox]

Actually this was found and fixed in 1.4:
https://issues.sonatype.org/browse/NEXUS-2472

The merging will now look at the latest metadata during the merge and
serve that version back to maven. In general though having the same
snapshots in multiple repos is probably going to cause you trouble, if
you can I would recommend avoiding it. You can use routing rules to
exclude on repo for these artifacts if you choose.

On Tue, Oct 6, 2009 at 11:52 AM, Julien CARSIQUE <jcarsique@...> wrote:

> After many tries,
>
> I deployed again into "snapshots" without better results (still receiving
> the old one from public-snapshots):
>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
> from public-snapshot
>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
> from internal-snapshots
>   Downloading:
> http://maven.in.nuxeo.com/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20090925.015004-82.pom
>   61K downloaded
>
> then, I finally deployed into "public-snapshot" and of course I got the good
> artifact:
>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
> from public-snapshot
>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
> from internal-snapshots
>   Downloading:
> http://maven.nuxeo.org/public-snapshot/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20091006.153540-83.pom
>   68K downloaded
>
> Stranger is on http://maven.in.nuxeo.com/nexus/index.html#nexus-search where
> searching for nuxeo-ecm:5.2.1-SNAPSHOT gives two results:
>   public-snapshot (remote)   5.2.1-SNAPSHOT ->
> nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>   snapshots (local)                5.2.1-SNAPSHOT ->
> nuxeo-ecm-5.2.1-*20091006*.153450-66.pom
> so why the group of both return the oldest ?
>
> PS: I use Nexus Version 1.3.6 Open Source
>
> Thanks,
>
> Julien CARSIQUE a écrit :
>>
>> Hello,
>>
>> I cannot manage to fix or workaround with the following dependencies
>> resolution issue.
>> We have two Nexus instances: a public one with nightly snapshots depending
>> on testing conditions and an internal one with snapshots by commits. The
>> internal Nexus is binded on the public one.
>>
>> Internal Nexus:
>> - snapshots (local internal repository with daily snapshots)
>> - public-snapshot (proxy on public Nexus with nightly snapshots)
>> - internal-snapshots (group of internal-snapshots and public-snapshot)
>>
>> The fact is we have a deprecated version in public-snapshot
>>
>> http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>> and a *good* version in snapshots
>>
>> http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>
>> Using Maven (2.0.10) resolution, I get the 20090925 version.
>> Using Nexus UI search, I get the same *bad* version:
>>
>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>> whereas the good one is available:
>>
>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>
>> I don't understand why it takes an older one than the more recent
>> available.
>> I tried re-index, empty cache, rebuild metadata, ..., on public-snapshot
>> and on snapshots.
>>
>> Is it a known bug ? Is there some workaround ? Did I failed in some
>> configuration ?
>>
>> Thanks,
>>
>
> --
> Julien Carsique, Nuxeo (Paris, France)
> www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
> Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Julien CARSIQUE]

Ok, I saw this buildnumber and I'm more confused :)

.../groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/maven-metadata.xml
    <?xml version="1.0" encoding="UTF-8"?>
    <metadata>
      <groupId>org.nuxeo</groupId>
      <artifactId>nuxeo-ecm</artifactId>
      <version>5.2.1-SNAPSHOT</version>
      <versioning>
        <snapshot>
          <timestamp>20090925.015004</timestamp>
          <buildNumber>*82*</buildNumber>
        </snapshot>
        <lastUpdated>20091006153451</lastUpdated>
      </versioning>
    </metadata>

Bad: nuxeo-ecm-5.2.1-20090925.015004-*82*.pom
Good: nuxeo-ecm-5.2.1-20091006.153450-*66*.pom

I now can imagine a (crazy) solution : deploy multiple times into
internal until the buildnumber is always greater than in public oO
that's awful.

Thanks again.

Julien CARSIQUE a écrit :

> Hello,
>
> What do you mean with build number ? In a jar I would have looked for
> something in the manifest... but in a pom ?
>
> Thank you Tamás,
>
> Tamás Cservenák a écrit :
>> Hi Julien,
>>
>> you are right here, but this seems like a Maven issue. Nexus uses the
>> Maven Artifact stuff (version 2.2.1 currently), and this is from there:
>>
>> http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup 
>>
>>
>> It seems that only build number is compared at all. This would
>> explain why maven and also nexus behaves the same wrong way.
>>
>> Thanks,
>> ~t~
>>
>> On Tue, Oct 6, 2009 at 5:10 PM, Julien CARSIQUE <jcarsique@...
>> <mailto:jcarsique@...>> wrote:
>>
>>     Hello,
>>
>>     I cannot manage to fix or workaround with the following
>>     dependencies resolution issue.
>>     We have two Nexus instances: a public one with nightly snapshots
>>     depending on testing conditions and an internal one with snapshots
>>     by commits. The internal Nexus is binded on the public one.
>>
>>     Internal Nexus:
>>     - snapshots (local internal repository with daily snapshots)
>>     - public-snapshot (proxy on public Nexus with nightly snapshots)
>>     - internal-snapshots (group of internal-snapshots and
>> public-snapshot)
>>
>>     The fact is we have a deprecated version in public-snapshot
>>          
>> http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom 
>>
>>     and a *good* version in snapshots
>>          
>> http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom 
>>
>>
>>     Using Maven (2.0.10) resolution, I get the 20090925 version.
>>     Using Nexus UI search, I get the same *bad* version:
>>          
>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom 
>>
>>     whereas the good one is available:
>>          
>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom 
>>
>>
>>     I don't understand why it takes an older one than the more recent
>>     available.
>>     I tried re-index, empty cache, rebuild metadata, ..., on
>>     public-snapshot and on snapshots.
>>
>>     Is it a known bug ? Is there some workaround ? Did I failed in
>>     some configuration ?
>>
>>     Thanks,
>>
>>     --     Julien Carsique, Nuxeo (Paris, France)
>>     www.nuxeo.com <http://www.nuxeo.com> - The Open Source ECM
>>     Platform - www.nuxeo.org <http://www.nuxeo.org>
>>     Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>>     jcarsique@... <mailto:jcarsique@...> | Tel: +33 1 40
>>     33 79 87
>>
>>
>>    
>> ---------------------------------------------------------------------
>>     To unsubscribe, e-mail: nexus-user-unsubscribe@...
>>     <mailto:nexus-user-unsubscribe@...>
>>     For additional commands, e-mail: nexus-user-help@...
>>     <mailto:nexus-user-help@...>
>>
>>
>

--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
jcarsique@... | Tel: [phone]



---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian Fox]

See my last reply, the buildnumber isn't in play here.

On Tue, Oct 6, 2009 at 12:11 PM, Julien CARSIQUE <jcarsique@...> wrote:

> Ok, I saw this buildnumber and I'm more confused :)
>
> .../groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/maven-metadata.xml
>   <?xml version="1.0" encoding="UTF-8"?>
>   <metadata>
>     <groupId>org.nuxeo</groupId>
>     <artifactId>nuxeo-ecm</artifactId>
>     <version>5.2.1-SNAPSHOT</version>
>     <versioning>
>       <snapshot>
>         <timestamp>20090925.015004</timestamp>
>         <buildNumber>*82*</buildNumber>
>       </snapshot>
>       <lastUpdated>20091006153451</lastUpdated>
>     </versioning>
>   </metadata>
>
> Bad: nuxeo-ecm-5.2.1-20090925.015004-*82*.pom
> Good: nuxeo-ecm-5.2.1-20091006.153450-*66*.pom
>
> I now can imagine a (crazy) solution : deploy multiple times into internal
> until the buildnumber is always greater than in public oO that's awful.
>
> Thanks again.
>
> Julien CARSIQUE a écrit :
>>
>> Hello,
>>
>> What do you mean with build number ? In a jar I would have looked for
>> something in the manifest... but in a pom ?
>>
>> Thank you Tamás,
>>
>> Tamás Cservenák a écrit :
>>>
>>> Hi Julien,
>>>
>>> you are right here, but this seems like a Maven issue. Nexus uses the
>>> Maven Artifact stuff (version 2.2.1 currently), and this is from there:
>>>
>>>
>>> http://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/maven-artifact/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup
>>>
>>> It seems that only build number is compared at all. This would explain
>>> why maven and also nexus behaves the same wrong way.
>>>
>>> Thanks,
>>> ~t~
>>>
>>> On Tue, Oct 6, 2009 at 5:10 PM, Julien CARSIQUE <jcarsique@...
>>> <mailto:jcarsique@...>> wrote:
>>>
>>>    Hello,
>>>
>>>    I cannot manage to fix or workaround with the following
>>>    dependencies resolution issue.
>>>    We have two Nexus instances: a public one with nightly snapshots
>>>    depending on testing conditions and an internal one with snapshots
>>>    by commits. The internal Nexus is binded on the public one.
>>>
>>>    Internal Nexus:
>>>    - snapshots (local internal repository with daily snapshots)
>>>    - public-snapshot (proxy on public Nexus with nightly snapshots)
>>>    - internal-snapshots (group of internal-snapshots and public-snapshot)
>>>
>>>    The fact is we have a deprecated version in public-snapshot
>>>
>>> http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>>    and a *good* version in snapshots
>>>
>>> http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>>
>>>    Using Maven (2.0.10) resolution, I get the 20090925 version.
>>>    Using Nexus UI search, I get the same *bad* version:
>>>
>>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>>    whereas the good one is available:
>>>
>>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>>
>>>    I don't understand why it takes an older one than the more recent
>>>    available.
>>>    I tried re-index, empty cache, rebuild metadata, ..., on
>>>    public-snapshot and on snapshots.
>>>
>>>    Is it a known bug ? Is there some workaround ? Did I failed in
>>>    some configuration ?
>>>
>>>    Thanks,
>>>
>>>    --     Julien Carsique, Nuxeo (Paris, France)
>>>    www.nuxeo.com <http://www.nuxeo.com> - The Open Source ECM
>>>    Platform - www.nuxeo.org <http://www.nuxeo.org>
>>>    Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>>>    jcarsique@... <mailto:jcarsique@...> | Tel: +33 1 40
>>>    33 79 87
>>>
>>>
>>>    ---------------------------------------------------------------------
>>>    To unsubscribe, e-mail: nexus-user-unsubscribe@...
>>>    <mailto:nexus-user-unsubscribe@...>
>>>    For additional commands, e-mail: nexus-user-help@...
>>>    <mailto:nexus-user-help@...>
>>>
>>>
>>
>
> --
> Julien Carsique, Nuxeo (Paris, France)
> www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
> Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
> jcarsique@... | Tel: [phone]
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Julien CARSIQUE]

Nice :)

Nexus 1.4 isn't available for download.
Would it be possible to have a fix for Nexus 1.3.6 on NEXUS-2472 ?

We have multiple snapshots repositories because of continuous
integration and the fact the platform we develop is also a framework for
external people.
We need to publish fully tested snapshots, they are nightly snapshots
and, in case of bugs, may not be deployed for a few days. Those "public"
snapshots need to be known as stable.
In the same time, we need to publish daily snapshots for continuous
integration purpose (http://qa.nuxeo.org) so that Hudson's slaves share
build tasks. Those "internal" snapshots may be unstable: they are very
closed to the source code.
I know we could use staging or manage this with multiple repositories
and groups on the same Nexus instance, but we are also concerned with
bandwidth consumption and so need to have Nexus instances inside and
outside our network.


Thank you,
Julien


Brian Fox a écrit :

> Actually this was found and fixed in 1.4:
> https://issues.sonatype.org/browse/NEXUS-2472
>
> The merging will now look at the latest metadata during the merge and
> serve that version back to maven. In general though having the same
> snapshots in multiple repos is probably going to cause you trouble, if
> you can I would recommend avoiding it. You can use routing rules to
> exclude on repo for these artifacts if you choose.
>
> On Tue, Oct 6, 2009 at 11:52 AM, Julien CARSIQUE <jcarsique@...> wrote:
>  
>> After many tries,
>>
>> I deployed again into "snapshots" without better results (still receiving
>> the old one from public-snapshots):
>>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>> from public-snapshot
>>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>> from internal-snapshots
>>   Downloading:
>> http://maven.in.nuxeo.com/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20090925.015004-82.pom
>>   61K downloaded
>>
>> then, I finally deployed into "public-snapshot" and of course I got the good
>> artifact:
>>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>> from public-snapshot
>>   [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>> from internal-snapshots
>>   Downloading:
>> http://maven.nuxeo.org/public-snapshot/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20091006.153540-83.pom
>>   68K downloaded
>>
>> Stranger is on http://maven.in.nuxeo.com/nexus/index.html#nexus-search where
>> searching for nuxeo-ecm:5.2.1-SNAPSHOT gives two results:
>>   public-snapshot (remote)   5.2.1-SNAPSHOT ->
>> nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>   snapshots (local)                5.2.1-SNAPSHOT ->
>> nuxeo-ecm-5.2.1-*20091006*.153450-66.pom
>> so why the group of both return the oldest ?
>>
>> PS: I use Nexus Version 1.3.6 Open Source
>>
>> Thanks,
>>
>> Julien CARSIQUE a écrit :
>>    
>>> Hello,
>>>
>>> I cannot manage to fix or workaround with the following dependencies
>>> resolution issue.
>>> We have two Nexus instances: a public one with nightly snapshots depending
>>> on testing conditions and an internal one with snapshots by commits. The
>>> internal Nexus is binded on the public one.
>>>
>>> Internal Nexus:
>>> - snapshots (local internal repository with daily snapshots)
>>> - public-snapshot (proxy on public Nexus with nightly snapshots)
>>> - internal-snapshots (group of internal-snapshots and public-snapshot)
>>>
>>> The fact is we have a deprecated version in public-snapshot
>>>
>>> http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>> and a *good* version in snapshots
>>>
>>> http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>>
>>> Using Maven (2.0.10) resolution, I get the 20090925 version.
>>> Using Nexus UI search, I get the same *bad* version:
>>>
>>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>> whereas the good one is available:
>>>
>>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>>
>>> I don't understand why it takes an older one than the more recent
>>> available.
>>> I tried re-index, empty cache, rebuild metadata, ..., on public-snapshot
>>> and on snapshots.
>>>
>>> Is it a known bug ? Is there some workaround ? Did I failed in some
>>> configuration ?
>>>
>>> Thanks,
>>>
>>>      
>> --
>> Julien Carsique, Nuxeo (Paris, France)
>> www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
>> Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>> For additional commands, e-mail: nexus-user-help@...
>>
>>
>>    
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>  

--
Julien Carsique, Nuxeo (Paris, France)
www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform




---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[Brian Fox]

We are putting the final touches on 1.4 now and plan to have a release
in the next week.

On Wed, Oct 7, 2009 at 9:35 AM, Julien CARSIQUE <jcarsique@...> wrote:

> Nice :)
>
> Nexus 1.4 isn't available for download.
> Would it be possible to have a fix for Nexus 1.3.6 on NEXUS-2472 ?
>
> We have multiple snapshots repositories because of continuous integration
> and the fact the platform we develop is also a framework for external
> people.
> We need to publish fully tested snapshots, they are nightly snapshots and,
> in case of bugs, may not be deployed for a few days. Those "public"
> snapshots need to be known as stable.
> In the same time, we need to publish daily snapshots for continuous
> integration purpose (http://qa.nuxeo.org) so that Hudson's slaves share
> build tasks. Those "internal" snapshots may be unstable: they are very
> closed to the source code.
> I know we could use staging or manage this with multiple repositories and
> groups on the same Nexus instance, but we are also concerned with bandwidth
> consumption and so need to have Nexus instances inside and outside our
> network.
>
>
> Thank you,
> Julien
>
>
> Brian Fox a écrit :
>>
>> Actually this was found and fixed in 1.4:
>> https://issues.sonatype.org/browse/NEXUS-2472
>>
>> The merging will now look at the latest metadata during the merge and
>> serve that version back to maven. In general though having the same
>> snapshots in multiple repos is probably going to cause you trouble, if
>> you can I would recommend avoiding it. You can use routing rules to
>> exclude on repo for these artifacts if you choose.
>>
>> On Tue, Oct 6, 2009 at 11:52 AM, Julien CARSIQUE <jcarsique@...>
>> wrote:
>>
>>>
>>> After many tries,
>>>
>>> I deployed again into "snapshots" without better results (still receiving
>>> the old one from public-snapshots):
>>>  [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>>> from public-snapshot
>>>  [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>>> from internal-snapshots
>>>  Downloading:
>>>
>>> http://maven.in.nuxeo.com/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20090925.015004-82.pom
>>>  61K downloaded
>>>
>>> then, I finally deployed into "public-snapshot" and of course I got the
>>> good
>>> artifact:
>>>  [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>>> from public-snapshot
>>>  [INFO] snapshot org.nuxeo:nuxeo-ecm:5.2.1-SNAPSHOT: checking for updates
>>> from internal-snapshots
>>>  Downloading:
>>>
>>> http://maven.nuxeo.org/public-snapshot/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-20091006.153540-83.pom
>>>  68K downloaded
>>>
>>> Stranger is on http://maven.in.nuxeo.com/nexus/index.html#nexus-search
>>> where
>>> searching for nuxeo-ecm:5.2.1-SNAPSHOT gives two results:
>>>  public-snapshot (remote)   5.2.1-SNAPSHOT ->
>>> nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>>  snapshots (local)                5.2.1-SNAPSHOT ->
>>> nuxeo-ecm-5.2.1-*20091006*.153450-66.pom
>>> so why the group of both return the oldest ?
>>>
>>> PS: I use Nexus Version 1.3.6 Open Source
>>>
>>> Thanks,
>>>
>>> Julien CARSIQUE a écrit :
>>>
>>>>
>>>> Hello,
>>>>
>>>> I cannot manage to fix or workaround with the following dependencies
>>>> resolution issue.
>>>> We have two Nexus instances: a public one with nightly snapshots
>>>> depending
>>>> on testing conditions and an internal one with snapshots by commits. The
>>>> internal Nexus is binded on the public one.
>>>>
>>>> Internal Nexus:
>>>> - snapshots (local internal repository with daily snapshots)
>>>> - public-snapshot (proxy on public Nexus with nightly snapshots)
>>>> - internal-snapshots (group of internal-snapshots and public-snapshot)
>>>>
>>>> The fact is we have a deprecated version in public-snapshot
>>>>
>>>>
>>>> http://maven.nuxeo.org/nexus/service/local/repositories/nuxeo-snapshot/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>>> and a *good* version in snapshots
>>>>
>>>>
>>>> http://maven.in.nuxeo.com/nexus/service/local/repositories/snapshots/content/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>>>
>>>> Using Maven (2.0.10) resolution, I get the 20090925 version.
>>>> Using Nexus UI search, I get the same *bad* version:
>>>>
>>>>
>>>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20090925*.015004-82.pom
>>>> whereas the good one is available:
>>>>
>>>>
>>>> http://maven.in.nuxeo.com/nexus/content/groups/internal-snapshots/org/nuxeo/nuxeo-ecm/5.2.1-SNAPSHOT/nuxeo-ecm-5.2.1-*20091005*.190102-64.pom
>>>>
>>>> I don't understand why it takes an older one than the more recent
>>>> available.
>>>> I tried re-index, empty cache, rebuild metadata, ..., on public-snapshot
>>>> and on snapshots.
>>>>
>>>> Is it a known bug ? Is there some workaround ? Did I failed in some
>>>> configuration ?
>>>>
>>>> Thanks,
>>>>
>>>>
>>>
>>> --
>>> Julien Carsique, Nuxeo (Paris, France)
>>> www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
>>> Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>>>
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>>> For additional commands, e-mail: nexus-user-help@...
>>>
>>>
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: nexus-user-unsubscribe@...
>> For additional commands, e-mail: nexus-user-help@...
>>
>>
>
> --
> Julien Carsique, Nuxeo (Paris, France)
> www.nuxeo.com - The Open Source ECM Platform - www.nuxeo.org
> Nuxeo ECM Stack - The Java EE, scalable, standard-based ECM Platform
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: nexus-user-unsubscribe@...
> For additional commands, e-mail: nexus-user-help@...
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: nexus-user-unsubscribe@...
For additional commands, e-mail: nexus-user-help@...

[hgomez]

2009/10/7 Brian Fox <brianf@...>

We are putting the final touches on 1.4 now and plan to have a release
in the next week.

Great !