Re: mvn virtual packages (auto-provides/requires)

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On 09/11/2013 05:58 AM, Mikolaj Izdebski wrote:
Java Packages Tools version 3.0.0 has recently been pushed to rawhide.
Since this version virtual packages generated automatically for Maven
artifacts (aka auto-provides) were extended slightly.  In this email I
will describe briefly the new format of virtual package names.

All Maven virtual package names used to be in format:

mvn(groupId:artifactId) = version

This has recently been extended to four different forms:

mvn(groupId:artifactId) = version
mvn(groupId:artifactId:compatVersion) = version
mvn(groupId:artifactId:extension:compatVersion) = version
mvn(groupId:artifactId:extension:classifier:compatVersion) = version


I'm sure this is great. I wonder how much of an impact it will have on the size of the primary yum metadata.


--
Orion Poplawski
Technical Manager                     303-415-9701 x222
NWRA/CoRA Division                    FAX: 303-415-9702
3380 Mitchell Lane                  orion@xxxxxxxxxxxxx
Boulder, CO 80301              http://www.cora.nwra.com
--
java-devel mailing list
java-devel@xxxxxxxxxxxxxxxxxxxxxxx
https://admin.fedoraproject.org/mailman/listinfo/java-devel





[Index of Archives]     [Red Users]     [Fedora Desktop]     [Fedora SELinux]     [Big List of Linux Books]     [Yosemite News]     [KDE Users]

  Powered by Linux