mvn virtual packages (auto-provides/requires)

[Mikolaj Izdebski]

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

* groupId and artifactId are upstream identifiers of the artifact.
Version is artifact version, as set by upstream.

* compatVersion is the compatibility version assigned by package
maintainer.  This is Fedora-specific.  compatVersion can differ from
version.

* extension is extension of artifact file, for example jar, war, pom,
tar.gz and so on.  If extension is omitted then it defaults to jar.

* classifier is artifact classifier.

This email describes only one feature of javapackages-tools-3.0.0.
Full release notes will be provided by Stanislav Ochotnicky in a
separate email.

-- 
Mikolaj Izdebski
IRC: mizdebsk

[Stanislav Ochotnicky]

Quoting Mikolaj Izdebski (2013-09-11 13:58:03)
>  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'll just note that any of extension, classifier and compatVersion parts can be
empty string so you can see provides such as:


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

Note that if last colon was omitted the classifier would be considered as a
version:

mvn(groupId:artifactId::version) = version

But provides/requires generators will always use the shorter version of 
mvn(groupId:artifactId:version) = version

This is good to know if you need to specify extension/classifier for some of the
scripts such as add_maven_depmap:

%add_maven_depmap gId:aId:war:version <path_to_war>

Following usage would be incorrect because last part (war) would be considered
as a version:

%add_maven_depmap gId:aId:war <path_to_war>



>  
>  * groupId and artifactId are upstream identifiers of the artifact.
>  Version is artifact version, as set by upstream.
>  
>  * compatVersion is the compatibility version assigned by package
>  maintainer.  This is Fedora-specific.  compatVersion can differ from
>  version.
>  
>  * extension is extension of artifact file, for example jar, war, pom,
>  tar.gz and so on.  If extension is omitted then it defaults to jar.
>  
>  * classifier is artifact classifier.
>  
>  This email describes only one feature of javapackages-tools-3.0.0.
>  Full release notes will be provided by Stanislav Ochotnicky in a
>  separate email.
>  
>  -- 
>  Mikolaj Izdebski
>  IRC: mizdebsk
>  --
>  java-devel mailing list
>  java-devel(a)lists.fedoraproject.org
>  https://admin.fedoraproject.org/mailman/listinfo/java-devel 
-- 
Stanislav Ochotnicky <sochotnicky(a)redhat.com&gt;
Software Engineer - Developer Experience

PGP: 7B087241
Red Hat Inc.                               http://cz.redhat.com

[Orion Poplawski]

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: [phone]
3380 Mitchell Lane                  orion(a)cora.nwra.com
Boulder, CO 80301              http://www.cora.nwra.com

[Mikolaj Izdebski]

On 09/12/2013 03:18 AM, Orion Poplawski wrote:
>  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. 
It shouldn't affect it much.  classifiers, non-jar extensions and
compatibility packages are quite rare.  groupID is usually the longest
part and it was already part of the virtual package name.

-- 
Mikolaj Izdebski
IRC: mizdebsk