maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Moser, Christian" <...@metrohm.com>
Subject AW: Maven 3.0 doesn't download sources
Date Fri, 26 Nov 2010 07:28:53 GMT
At the moment I have no idea which tool is causing the problem. I still have problems with
artifactory 2.3.1. Just a quick question: Does artifactory 2.3.0+ supports the m3 format with
both, unique and non-unique repositories? Currently the build system is running with 2.3.1
and non-unique snapshot repositories deployed with maven 3.0 and it still doesn't download
artifact-sources neither it's downloading newer artifactory-snapshots deployed on the artifactory
if build is called with maven -U.

- Chris

-----Ursprüngliche Nachricht-----
Von: Yoav Landman [mailto:ylandman@gmail.com] 
Gesendet: Donnerstag, 25. November 2010 20:44
An: Maven Users List
Betreff: Re: Maven 3.0 doesn't download sources

Hi,

Artifactory 2.3.0+ supports the m3 format for maven-metadata.xml
for snapshot artifacts. But, if you upgraded to 2.3.x and still think there
is something wrong on the Artifactory side, better ask on the Artifactory
user list and we'll be happy to assist you there.

Thanks,

On Wed, Nov 24, 2010 at 8:34 AM, Moser, Christian <cmo@metrohm.com> wrote:

> I could imagine the culprit could be artifactory. We were forced to update
> from 2.2.2 to 2.2.3, otherwise we weren't be able to deploy with maven 3.0
> (metadata issue in Artifactory 2.2.2, deploy worked only in legacy mode). In
> the meantime just to be sure, we updated to 2.3.1. But were also required to
> change all our repositories to handle "non-unique" snapshots and to deploy
> every snapshot again. It was necessary to use "non-unique" snapshots in
> artifactory because maven was overriding newer locally installed artifacts,
> with older remote artifacts everytime we tried to install a new artifact.
>
> But regarding my two maven user list entries (Maven 3.0 doesn't download
> sources / Maven 3.0 doesn't update snapshot artifacts) it seems there are
> some metadata issues with artifactory & maven 3.0.
>
> So, the right way to go with maven 3.0 is to use repositories with unique
> (timestamped) snapshots artifacts? But this won't work with artifactory at
> least not with version 2.2.3.
>
> -thx Chris
>
> -----Ursprüngliche Nachricht-----
> Von: Brett Porter [mailto:brett@porterclan.net] Im Auftrag von Brett
> Porter
> Gesendet: Dienstag, 23. November 2010 23:14
> An: Maven Users List
> Betreff: Re: Maven 3.0 doesn't download sources
>
> There's a couple of potential things in the way you've described it:
> - Maven 3.0 does not support non-unique snapshots - you would need to use
> timestamps and rely on the repo manager to purge old versions
> - if I've misunderstood the above, the difference on timestamps is that
> Maven 3.0 will actually store separate metadata per classifier. They should
> be the same in the scenario you describe, but maybe Artifactory doesn't
> support the new metadata format and affects it in some way.
>
> HTH,
> Brett
>
> On 24/11/2010, at 3:21 AM, Stephen Connolly wrote:
>
> > Don't know what it should be but I think we may have found a possible
> > culpret.
> >
> > Check with Benjamin Bentmann, he'd know what m3 is supposed to do
> >
> > -Stephen
> >
> > On 23 November 2010 14:30, Moser, Christian <cmo@metrohm.com> wrote:
> >
> >> They are from snapshot artifacts. We use non-unique snapshots in
> >> artifactory.
> >> The sources are deployed on the same time like the compiled artifacts.
> So
> >> the timestamp should be equals, shouldn't it?
> >> If not, how could I archieve it?
> >>
> >> -Chris
> >>
> >> -----Ursprüngliche Nachricht-----
> >> Von: Stephen Connolly [mailto:stephen.alan.connolly@gmail.com]
> >> Gesendet: Dienstag, 23. November 2010 14:39
> >> An: Maven Users List
> >> Betreff: Re: Maven 3.0 doesn't download sources
> >>
> >> Are these sources of snapshots or releases?
> >>
> >> If snapshots it may be that the sources were deployed with a different
> >> timestamp, in which case the maven metadata my not be letting maven 3
> find
> >> the artifacts.
> >>
> >> IIRC Maven 3 pays more attention to the metadata, whereas Maven 2 might
> not
> >> trust it as much (but I could be wrong, my recollection is fuzzy)
> >>
> >> -Stephen
> >>
> >> On 23 November 2010 12:13, Moser, Christian <cmo@metrohm.com> wrote:
> >>
> >>> I'm unable to download artifact sources with maven 3.0 and 3.0.1-RC1
> >>> with following command.
> >>>
> >>>
> >>>
> >>> Sources classifier is: -sources (default)
> >>>
> >>>
> >>>
> >>> "mvn -U validate dependency:sources -DoverWriteSnapshots=true
> >>> -DoverWriteReleases=true"
> >>>
> >>>
> >>>
> >>>
> >>>
> >>> the artifacts with classifier -sources are available in the locale
> >>> remote-repository manager (artifactory).
> >>>
> >>>
> >>>
> >>> Is there another call to force maven to download sources?
> >>>
> >>>
> >>>
> >>> Greez Chris
> >>>
> >>>
> >>>
> >>>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: users-help@maven.apache.org
> >>
> >>
>
> --
> Brett Porter
> brett@apache.org
> http://brettporter.wordpress.com/
>
>
>
>
>
> ---------------------------------------------------------------------
> 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
>
>


-- 
Yoav
Mime
View raw message