[
https://issues.jboss.org/browse/WELD-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12614921#comment-12614921
]
Dan Allen commented on WELD-869:
--------------------------------
The transformation from the token ${parsedVersion.osgiVersion} to
${parsedVersion (osgiVersion}) is an artifact of the log formatter.
To make it more clear, if the manifest attribute were set properly, such as:
Specification-Version: 1.1.1.Final
Then the log output would appear as:
WELD-000900 1.1.1 (Final)
Other projects appear to use the maven-buildhelper-plugin to set the
parsedVersion.osgiVersion:
{code:xml}
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>build-helper-maven-plugin</artifactId>
<version>1.5</version>
<executions>
<execution>
<id>set-osgi-version</id>
<phase>verify</phase>
<goals>
<goal>parse-version</goal>
</goals>
</execution>
</executions>
</plugin>
{code}
That may be all we need.
> Weld OSGi bundle reports version as ${parsedVersion.osgiVersion}
> ----------------------------------------------------------------
>
> Key: WELD-869
> URL: https://issues.jboss.org/browse/WELD-869
> Project: Weld
> Issue Type: Bug
> Components: OSGi support
> Affects Versions: 1.1.0.Final
> Reporter: Dan Allen
> Priority: Minor
>
> When Weld starts on GlassFish, it reports it's version as:
> WELD-000900 ${parsedVersion (osgiVersion})
> The version is read from the MANIFEST.MF, which has this line:
> Specification-Version: ${parsedVersion.osgiVersion}
> The replacement doesn't seem to be working properly in the osgi build.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
weld-issues mailing list
weld-issues@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/weld-issues
