On 20 Apr 2007, at 14:45, Stian Soiland wrote:
Attached is a fixed version of
com.noelios.restlet.ext.jetty_6.1.pom that will allow Restlet
1.0.0 it to work with Jetty using Maven. (for unit tests, for
instance)
In particular, the version number is hard coded to 6.1.1 as the
range [6.1> did not work properly, due to the central maven
repositories not listing the 6.1 versions. (I don't know why they
don't do that)
There's a similar issue with the Apache Commons HTTP client in
com.noelios.restlet.ext.httpclient_3.1.pom. The pre-release 3.1
versions are not yet listed in the official Maven repositories,
although the specific versions are available. So revised
com.noelios.restlet.ext.httpclient_3.1.pom is attached, specifying
3.1-rc1:
<dependency>
<groupId>commons-httpclient</groupId>
<artifactId>commons-httpclient</artifactId>
<version>3.1-rc1</version>
</dependency>
depending on com.noelios.restlet.ext.simple_3.1.pom is failing with:
No versions are present in the repository for the artifact with a
range [3.1,)
simple:simple-core:jar:null
depending on com.noelios.restlet.ext.asyncweb_0.8.pom is failing with:
No versions are present in the repository for the artifact with a
range [0.8,)
org.safehaus.asyncweb:asyncweb:jar:null
The repositories don't seem to have any version at all for neither of
these artefacts.
I'm sorry for reporting all these problems, but I don't see much use
of the POM files when they are faulty and consider this bugs, and I
hope that although lots of people would like to see Maven deployed
properly to a public maven repository, there's not much point to do
so with faulty dependencies.
--
Stian Soiland, myGrid team
School of Computer Science
The University of Manchester
http://www.cs.man.ac.uk/~ssoiland/
