Hi *,
how will we solve the "version hell" in Maven repositories?
When the users search PicketLink in the Central for instance, they see 5.0.0-2013Jan16 as
the latest.
http://search.maven.org/#search%7Cga%7C1%7Cpicketlink-parent
Similar problems come if an user specifies a version range in a Maven dependency:
<dependency>
<groupId>org.picketlink</groupId>
<artifactId>picketlink-idm-impl</artifactId>
<version>[2.5,)</version>
</dependency>
Best regards,
-- josef
Too brief? Here's why!
http://emailcharter.org
----- Original Message -----
From: "Pedro Igor Silva" <psilva(a)redhat.com>
To: security-dev(a)lists.jboss.org
Sent: Monday, May 20, 2013 8:35:18 PM
Subject: [security-dev] [PicketLink] - Version 2.5.0.Beta3 Released
Hi All,
Today we released PicketLink 2.5.0.Beta3. For now on, PicketLink versions
will follow the v2.5.x series, as discussed in this list.
Documentation can be obtained from:
http://docs.jboss.org/picketlink/3/latest
Issues for this version:
https://issues.jboss.org/secure/ReleaseNote.jspa?projectId=12310923&v...
Regards.
Pedro Igor
_______________________________________________
security-dev mailing list
security-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/security-dev