[ 
http://jira.codehaus.org/browse/MNG-2906?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Paul Smith updated MNG-2906:
----------------------------

    Attachment: example.tar.gz

Here's a generated maven project using 2.0.6 that exhibits this sort of 
behaviour.  It was simply created as follows:

1) mvn archetype:create -DgroupId=com.foo -DartifactId=bar 
-Dversion=1.0-SNAPSHOT -Dpackaging=jar
2) Edit pom.xml, add dependency to latest jasperreports distribution
3) mvn clean package

*thud*

Paul-Smiths-Computer:/temp/bar paulsmith$ mvn clean package
[INFO] Scanning for projects...
[INFO] 
----------------------------------------------------------------------------
[INFO] Building bar
[INFO]    task-segment: [clean, package]
[INFO] 
----------------------------------------------------------------------------
[INFO] [clean:clean]
[INFO] Deleting directory /temp/bar/target
[INFO] Deleting directory /temp/bar/target/classes
[INFO] Deleting directory /temp/bar/target/test-classes
[INFO] Deleting directory /temp/bar/target/site
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.

No versions are present in the repository for the artifact with a range [2.1,)
  commons-collections:commons-collections:jar:null

from the specified remote repositories:
  central (http://repo1.maven.org/maven2)


[INFO] ------------------------------------------------------------------------
[INFO] For more information, run Maven with the -e switch
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 1 second
[INFO] Finished at: Thu Aug 23 17:46:27 EST 2007
[INFO] Final Memory: 3M/6M
[INFO] ------------------------------------------------------------------------




***********************************************************

This is regardless of using Archiva or standard central repo usage.






> version ranges don't work after a day has passed
> ------------------------------------------------
>
>                 Key: MNG-2906
>                 URL: http://jira.codehaus.org/browse/MNG-2906
>             Project: Maven 2
>          Issue Type: Bug
>          Components: Artifacts and Repositories
>            Reporter: Bill Dudney
>             Fix For: 2.1.x
>
>         Attachments: example.tar.gz, example.X.output.txt
>
>
> dependency A has a range dependency on B
> my project has a dependency on A (not directly on B)
> I build my project with a fresh clean repo (i.e. rm -rf ~/.m2/repository)
> B's latest is downloaded as expected
> the next morning I rebuild my project and I get error messages that no 
> suitable version can be found;
> No versions are present in the repository for the artifact with a range 
> [1.02b,) com.lowagie:itext-null.jar
> the particulars are jfreereports depending on [1.02b,) of lowagie.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to