artifactory & maven 3.0 - metadata problem

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

artifactory & maven 3.0 - metadata problem

onmomo

Hi

 

For several days, I’m stuck with a problem. I not really sure if artifactory 2.3.1 is fully compatible with maven 3.0 and it’s new modified metadata system.

 

Does artifactory 2.3.0+ supports the m3 format with both, unique and non-unique repositories? Currently our build system is running with 2.3.1 and non-unique snapshot repositories deployed with maven 3.0. Maven doesn't download artifact-sources neither it's downloading newer artifactory-snapshots jars deployed on the artifactory if build is called with maven -U.

 

Originally we were forced to change our repositories from unique to non-unique (version 2.2.3), because maven was constantly overriding never locally installed artifacts with older remote artifacts on artifactory (perhaps because of this bug: https://issues.jfrog.org/jira/browse/RTFACT-3390). Now with non-unique repos, we’ve the problem that maven 3.0 only updates artifacts if they don’t exist in the local repository. Ff they exist but are older, only maven-metadata-REPO-ID.xml file get’s updated with the correct value in <lastUpdated/>, but the .jar archive and –sources .jar still remains outdated.

 

For example:

 

<?xml version="1.0" encoding="UTF-8"?>

<metadata>

  <groupId>mnet</groupId>

  <artifactId>comp-devadapterfactory</artifactId>

  <version>4.0.0-SNAPSHOT</version>

  <versioning>

    <snapshot>

      <buildNumber>1</buildNumber>

    </snapshot>

    <lastUpdated>20101126062036</lastUpdated>

  </versioning>

</metadata>

 

 I noticed from the maven mailing list that maven 3.0 doesn’t support non-timestamped snapshots and got a new classifier entry, if I look at the maven file which was created by maven after deployment it shows:

 

<?xml version="1.0" encoding="UTF-8"?>

<metadata modelVersion="1.1.0">

  <groupId>mnet</groupId>

  <artifactId>comp-devadapterfactory</artifactId>

  <version>4.0.0-SNAPSHOT</version>

  <versioning>

    <snapshot>

      <timestamp>20101126.062035</timestamp>

      <buildNumber>2</buildNumber>

    </snapshot>

    <lastUpdated>20101126062035</lastUpdated>

    <snapshotVersions>

      <snapshotVersion>

        <extension>jar</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

      <snapshotVersion>

        <extension>pom</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

      <snapshotVersion>

        <classifier>sources</classifier>

        <extension>jar</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

    </snapshotVersions>

  </versioning>

</metadata>

 

Does Artifactory really support this? At least it seems that the metadata created by non-unique snapshots are faulty.

 

So before I change all repositories back to unique and redeploy everything on my live-system, I really want to be sure the maven 3.0 metadata is fully compatible with artifatory 2.3.1.

Currently we use the work-around which includes to clean local repository before an update and download sources via m2-eclipse or netbeans 6.9.1. Then the sources are also being downloaded, probably because of the maven 2.x embedder.

 

 

Greets Christian

 

Reply | Threaded
Open this post in threaded view
|

Re: artifactory & maven 3.0 - metadata problem

elig
Hi Christian,

Artifactory 2.3.0+ supports the m3 format for maven-metadata.xml
for snapshots  and artifacts with classifiers as sources.

We reproduced your scenario however, this is not an Artifactory issue, Maven 3 simply doesn't support the non-unique SNAPSHOT format.
You should change policy to unique or deployer in order to resolve your snapshots.


HTH,
Eli
The Artifactory team
  

On Fri, Nov 26, 2010 at 11:58 AM, cmo <[hidden email]> wrote:

Hi

 

For several days, I’m stuck with a problem. I not really sure if artifactory 2.3.1 is fully compatible with maven 3.0 and it’s new modified metadata system.

 

Does artifactory 2.3.0+ supports the m3 format with both, unique and non-unique repositories? Currently our build system is running with 2.3.1 and non-unique snapshot repositories deployed with maven 3.0. Maven doesn't download artifact-sources neither it's downloading newer artifactory-snapshots jars deployed on the artifactory if build is called with maven -U.

 

Originally we were forced to change our repositories from unique to non-unique (version 2.2.3), because maven was constantly overriding never locally installed artifacts with older remote artifacts on artifactory (perhaps because of this bug: https://issues.jfrog.org/jira/browse/RTFACT-3390). Now with non-unique repos, we’ve the problem that maven 3.0 only updates artifacts if they don’t exist in the local repository. Ff they exist but are older, only maven-metadata-REPO-ID.xml file get’s updated with the correct value in <lastUpdated/>, but the .jar archive and –sources .jar still remains outdated.

 

For example:

 

<?xml version="1.0" encoding="UTF-8"?>

<metadata>

  <groupId>mnet</groupId>

  <artifactId>comp-devadapterfactory</artifactId>

  <version>4.0.0-SNAPSHOT</version>

  <versioning>

    <snapshot>

      <buildNumber>1</buildNumber>

    </snapshot>

    <lastUpdated>20101126062036</lastUpdated>

  </versioning>

</metadata>

 

 I noticed from the maven mailing list that maven 3.0 doesn’t support non-timestamped snapshots and got a new classifier entry, if I look at the maven file which was created by maven after deployment it shows:

 

<?xml version="1.0" encoding="UTF-8"?>

<metadata modelVersion="1.1.0">

  <groupId>mnet</groupId>

  <artifactId>comp-devadapterfactory</artifactId>

  <version>4.0.0-SNAPSHOT</version>

  <versioning>

    <snapshot>

      <timestamp>20101126.062035</timestamp>

      <buildNumber>2</buildNumber>

    </snapshot>

    <lastUpdated>20101126062035</lastUpdated>

    <snapshotVersions>

      <snapshotVersion>

        <extension>jar</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

      <snapshotVersion>

        <extension>pom</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

      <snapshotVersion>

        <classifier>sources</classifier>

        <extension>jar</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

    </snapshotVersions>

  </versioning>

</metadata>

 

Does Artifactory really support this? At least it seems that the metadata created by non-unique snapshots are faulty.

 

So before I change all repositories back to unique and redeploy everything on my live-system, I really want to be sure the maven 3.0 metadata is fully compatible with artifatory 2.3.1.

Currently we use the work-around which includes to clean local repository before an update and download sources via m2-eclipse or netbeans 6.9.1. Then the sources are also being downloaded, probably because of the maven 2.x embedder.

 

 

Greets Christian

 



View this message in context: artifactory & maven 3.0 - metadata problem
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users



------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users
Reply | Threaded
Open this post in threaded view
|

AW: artifactory &amp; maven 3.0 - metadata problem

onmomo

Hi Eli

 

Thank you for your answer. I changed the snapshot repository policy to unique, it did the trick!

 

>Maven 3 simply doesn't support the non-unique SNAPSHOT format.

 

I would recommend that you post this information in boldface in the artifactory guide because the guide advises strongly against using unique policies..

 

BTW: Artifactory 2.2.3 doesn’t support maven 3 with unique policies

 

Regards,

Christian

 

 

Von: Eli Givoni [via Artifactory] [mailto:[hidden email]]
Gesendet: Sonntag, 28. November 2010 10:53
An: Moser, Christian
Betreff: Re: artifactory &amp; maven 3.0 - metadata problem

 

Hi Christian,

Artifactory 2.3.0+ supports the m3 format for maven-metadata.xml
for snapshots  and artifacts with classifiers as sources.

We reproduced your scenario however, this is not an Artifactory issue, Maven 3 simply doesn't support the non-unique SNAPSHOT format.
You should change policy to unique or deployer in order to resolve your snapshots.


HTH,
Eli
The Artifactory team
  

On Fri, Nov 26, 2010 at 11:58 AM, cmo <[hidden email]> wrote:

Hi

 

For several days, I’m stuck with a problem. I not really sure if artifactory 2.3.1 is fully compatible with maven 3.0 and it’s new modified metadata system.

 

Does artifactory 2.3.0+ supports the m3 format with both, unique and non-unique repositories? Currently our build system is running with 2.3.1 and non-unique snapshot repositories deployed with maven 3.0. Maven doesn't download artifact-sources neither it's downloading newer artifactory-snapshots jars deployed on the artifactory if build is called with maven -U.

 

Originally we were forced to change our repositories from unique to non-unique (version 2.2.3), because maven was constantly overriding never locally installed artifacts with older remote artifacts on artifactory (perhaps because of this bug: https://issues.jfrog.org/jira/browse/RTFACT-3390). Now with non-unique repos, we’ve the problem that maven 3.0 only updates artifacts if they don’t exist in the local repository. Ff they exist but are older, only maven-metadata-REPO-ID.xml file get’s updated with the correct value in <lastUpdated/>, but the .jar archive and –sources .jar still remains outdated.

 

For example:

 

<?xml version="1.0" encoding="UTF-8"?>

<metadata>

  <groupId>mnet</groupId>

  <artifactId>comp-devadapterfactory</artifactId>

  <version>4.0.0-SNAPSHOT</version>

  <versioning>

    <snapshot>

      <buildNumber>1</buildNumber>

    </snapshot>

    <lastUpdated>20101126062036</lastUpdated>

  </versioning>

</metadata>

 

 I noticed from the maven mailing list that maven 3.0 doesn’t support non-timestamped snapshots and got a new classifier entry, if I look at the maven file which was created by maven after deployment it shows:

 

<?xml version="1.0" encoding="UTF-8"?>

<metadata modelVersion="1.1.0">

  <groupId>mnet</groupId>

  <artifactId>comp-devadapterfactory</artifactId>

  <version>4.0.0-SNAPSHOT</version>

  <versioning>

    <snapshot>

      <timestamp>20101126.062035</timestamp>

      <buildNumber>2</buildNumber>

    </snapshot>

    <lastUpdated>20101126062035</lastUpdated>

    <snapshotVersions>

      <snapshotVersion>

        <extension>jar</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

      <snapshotVersion>

        <extension>pom</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

      <snapshotVersion>

        <classifier>sources</classifier>

        <extension>jar</extension>

        <value>4.0.0-20101126.062035-2</value>

        <updated>20101126062035</updated>

      </snapshotVersion>

    </snapshotVersions>

  </versioning>

</metadata>

 

Does Artifactory really support this? At least it seems that the metadata created by non-unique snapshots are faulty.

 

So before I change all repositories back to unique and redeploy everything on my live-system, I really want to be sure the maven 3.0 metadata is fully compatible with artifatory 2.3.1.

Currently we use the work-around which includes to clean local repository before an update and download sources via m2-eclipse or netbeans 6.9.1. Then the sources are also being downloaded, probably because of the maven 2.x embedder.

 

 

Greets Christian

 

 


View this message in context: artifactory & maven 3.0 - metadata problem
Sent from the Artifactory - Users mailing list archive at Nabble.com.

------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users

 


------------------------------------------------------------------------------
Increase Visibility of Your 3D Game App & Earn a Chance To Win $500!
Tap into the largest installed PC base & get more eyes on your game by
optimizing for Intel(R) Graphics Technology. Get started today with the
Intel(R) Software Partner Program. Five $500 cash prizes are up for grabs.
http://p.sf.net/sfu/intelisp-dev2dev
_______________________________________________
Artifactory-users mailing list
[hidden email]
https://lists.sourceforge.net/lists/listinfo/artifactory-users


View message @ http://forums.jfrog.org/artifactory-maven-3-0-metadata-problem-tp5776632p5781332.html
To start a new topic under Artifactory - Users, email [hidden email]
To unsubscribe from Artifactory - Users, click here.