You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by "spencer portee (JIRA)" <ji...@codehaus.org> on 2005/10/24 16:45:11 UTC

[jira] Commented: (MNG-1256) antlib + http based repository + version range errors badly

    [ http://jira.codehaus.org/browse/MNG-1256?page=comments#action_49150 ] 

spencer portee commented on MNG-1256:
-------------------------------------

It's not a 404 page, but a 200 where the contents are a directory listing rendered as HTML.  The date in the bug above, in that html, is the date I uploaded something to my local repository.

Regarding the original bug, setting the repository to file:// and deploying there, clearing out my local repository, and then trying to resolve dependencies doesn't work.  I would expect antlib to say, "hey, the dependencies aren't in the local, let me copy them", but I get the output below.  Note, when a version doesn't exist, I get the version numbers i requested and those that exist.  This is NOT the case below, but something broken in maven2.  It's clear it can't find any version at all.

----
[INFO] artifact org.sporty:log4j: checking for updates from remote
[artifact:dependencies] An error has occurred while processing the Maven artifac
t tasks.
[artifact:dependencies]  Diagnosis:
[artifact:dependencies]
[artifact:dependencies] Unable to resolve artifact: No versions are present in t
he repository for the artifact with a range [1.2.0,1.3.0)
[artifact:dependencies]   org.sporty:log4j:null:jar
[artifact:dependencies]
[artifact:dependencies] from the specified remote repositories:
[artifact:dependencies]   remote (file://c:/developmnet/repository )
[artifact:dependencies]
[artifact:dependencies]

BUILD FAILED
C:\development\eclipse 3.0\workspace\hibernate-3\sub-projects\flip\build.xml:4:
The following error occurred while executing this line:
C:\development\eclipse 3.0\workspace\hibernate-3\common.xml:4: Unable to resolve
 artifact: No versions are present in the repository for the artifact with a ran
ge [1.2.0,1.3.0)
  org.sporty:log4j:null:jar
---

here's the maven-metadata.xml file in the log4j directory in my file:// remote repository...

--
<metadata>
  <groupId>org.sporty</groupId>
  <artifactId>log4j</artifactId>
  <version>1.2.12</version>
  <versioning>
    <versions>
      <version>1.2.12</version>
    </versions>
    <lastUpdated>20051021192921</lastUpdated>
  </versioning>
</metadata
--

antlib is severely borked.

> antlib + http based repository + version range errors badly
> -----------------------------------------------------------
>
>          Key: MNG-1256
>          URL: http://jira.codehaus.org/browse/MNG-1256
>      Project: Maven 2
>         Type: Bug
>   Components: maven-artifact-ant
>  Environment: maven 2.0 (release), antlib, ant, apache 2 webserver on windows
>     Reporter: spencer portee
>     Priority: Critical
>      Fix For: 2.0.1

>
>
> In my pom file, I have a dependency, it has no child dependencies beyond that looks like this:
>  <dependency>
>    <groupId>org.sporty</groupId>
>    <artifactId>xwork</artifactId>
>    <version>[1.0.5,1.1)</version>
>    <scope>runtime</scope>
>  </dependency>
> and use the following in my build script:
> <artifact:dependencies verbose="true" useScope="runtime" pathId="project.classpath.runtime">
>                 <artifact:pom file="pom.xml" />
>                 <artifact:remoteRepository url="${project.repository} " layout="default" />
> </artifact:dependencies>
> The variable I have above is being set right per tests 1-3.  The last test.. it gets strange.
> I deployed xwork, as an empty jar by accident, so don't be surprised there's nothing in the jar.  But the dependency downloading from the webserver breaks horribly.  I tested 4 scenarios:
> 1. If I put in my pom as my remote repository as file://c:/temp/repository and deploy to there, the above pom works flawlessly.  
> 2 & 3. If I replace the range w/ a simple: <version>1.0.5</version> and set my repository to http://sporty.org/java/repository, it downloads fine as well.  It works with the filesystem remote repository of my c:/temp... directory.
> 4. If I use the http repository AND use a range version as I originally wanted, I get an ugly error:
> C:\development\eclipse 3.0\workspace\hibernate-3\common.xml:4: Unable to resolve
>  artifact: Unable to get dependency information: Unable to read local copy of me
> tadata: Cannot read metadata from 'C:\Documents and Settings\sportee\.m2\reposit
> ory\org\sporty\xwork\maven-metadata-remote.xml': end tag name </pre> must match
> start tag name <hr> from line 11 (position: START_TAG seen ...</a>
>      11-Oct-2005 17:52    -   \n<hr></pre>... @11:11)
>   org.sporty:xwork:null:jar
> from the specified remote repositories:
>   remote (http://sporty.org/java/repository )
> Path to dependency:
>         1) org.sporty:xdoclet-xwork:jar:1.0-SNAPSHOT
> --
> The contents of the ...-remote.xml file, I see a directory listing, and not the contents of the repository file on the server. My naive guess is the repository file to look for is getting lost, or not passed, if it's in a hashmap, not being referenced properly...
> Thanks,
> -s

-- 
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


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org