commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jörg Schaible <Joerg.Schai...@Elsag-Solutions.com>
Subject RE: [logging] release status
Date Fri, 20 Jan 2006 08:50:10 GMT
Hi Simon,

Simon Kitching wrote on Friday, January 20, 2006 9:14 AM:
[snip]
> (2)
> To revisit the MANIFEST.MF file. I believe there was some
> discussion on
> this list a while ago about some attribute of the manifest that should
> be there but most projects weren't inserting. I went searching for
>   the info and found this: http://jira.codehaus.org/browse/MPJAR-51
> with a comment by a certain Robert Donkin. So I presume you
> know what to
> do with the manifest Robert? :-)

Well, there's also a comment by me :)

I've solved the specificationVersion within the javaapp plugin by using major.minor, see jelly
snippet:

        <j:set var="specificationVersion" value="${maven.javaapp.manifest.specificationVersion}"
/>
        <j:if test="${empty(specificationVersion)}">
          <u:tokenize var="versionItems" delim="." trim="true">${pom.currentVersion}</u:tokenize>
          <j:if test="${size(versionItems) > 0}">
            <j:set var="specificationVersion" value="${versionItems[0]}" />
          </j:if>
          <j:if test="${size(versionItems) > 1}">
            <j:set var="specificationVersion" value="${specificationVersion}.${versionItems[1]}"
/>
          </j:if>
        </j:if>

Since the jar plugin still does not handle this case, I am not sure, if we should add something
like this into our build.

[snip]

- Jörg

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


Mime
View raw message