maven-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Stevo Slavić <ssla...@gmail.com>
Subject Re: Maven 2 & 3 + Hudson + Nexus
Date Mon, 04 Oct 2010 22:49:55 GMT
When I mentioned repository policy settings, I actually meant on repository
definition in your pom.xml or settings.xml and it's update policy. By
default it's "daily". Have you tried forcing updating snapshots with "-U"
switch?

Regards,
Stevo.

On Tue, Oct 5, 2010 at 12:37 AM, Hilco Wijbenga <hilco.wijbenga@gmail.com>wrote:

> On 4 October 2010 14:57, Benjamin Bentmann <benjamin.bentmann@udo.edu>
> wrote:
> > Hilco Wijbenga wrote:
> >
> >> Any ideas how I can fix this? Any ideas as to what the problem is
> exactly?
> >
> > I personally find it helpful to start with a precise description of what
> the
> > issue actually is before trying to solve it. After all, there's a reason
> why
> > the build produces a log and even if you can't spot the relevant pieces
> in
> > there, others might be able to. So sharing the log of the failing module
> > would be a good start. And with log, I don't mean the single line that
> says
> > "[ERROR]", I mean the entire log that shows the actions taken by Maven
> that
> > eventually lead to the error and contribute to the context required to
> > understand the issue. If the log cannot be attached to the mail, using
> > pastebin.com or similar can help. Other things that are nice to know is
> the
> > directory listing of the directory in the local repo that contains the
> POM
> > in question. Last but not least, the contents of all maven-metadata-*.xml
> in
> > that directory can help to troubleshoot that issue.
>
> Here you go. I didn't see anything useful in the log files but you're
> right of course, somebody else might. I've attached the results of
> running Maven 2.2.1 (maven2.txt) and the (partial, until just after
> the successful retrieval of the problematic POM) results of running
> Maven 3.0 (RC2) (maven3.txt). (The download link to RC3 is no longer
> valid so I have not been able to try it with RC3.)
>
> I've emptied the local repository directory with the problematic POM
> file so that Maven has to redownload it. So nothing useful there. (It
> stays empty because Maven 2 doesn't download anything.)
>
> After running Maven 3, I get:
>
> hilco@centaur $ ls
> ~/.m2/repository/com/xyz/test-dependencies-pom/5-SNAPSHOT/
> _maven.repositories
> maven-metadata-all-mirror.xml
> maven-metadata-all-mirror.xml.sha1
> resolver-status.properties
> test-dependencies-pom-5-20101004.184333-6.pom
> test-dependencies-pom-5-20101004.184333-6.pom.sha1
> test-dependencies-pom-5-SNAPSHOT.pom
>
> The maven-metadata.xml that Nexus sees:
>
> <metadata>
> <groupId>com.igniteplay</groupId>
> <artifactId>test-dependencies-pom</artifactId>
> <version>5-SNAPSHOT</version>
> <versioning>
> <snapshot>
> <timestamp>20101004.184333</timestamp>
> <buildNumber>6</buildNumber>
> </snapshot>
> <lastUpdated>20101004184339</lastUpdated>
> </versioning>
> </metadata>
>
> and the directory listing that Nexus sees:
>
> maven-metadata.xml
> maven-metadata.xml.md5
> maven-metadata.xml.sha1
> test-dependencies-pom-5-20101002.073647-5.pom
> test-dependencies-pom-5-20101002.073647-5.pom.sha1
> test-dependencies-pom-5-20101004.184333-6.pom
> test-dependencies-pom-5-20101004.184333-6.pom.sha1
>
> I hope that sheds some light on things.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message