[
https://issues.apache.org/activemq/browse/SMX4-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=54254#action_54254
]
Chris Custine commented on SMX4-350:
------------------------------------
WRT to the timestamps on the snapshots, we have had trouble with the snapshot
deployments from Hudson but we are working on it. I have just triggered
deployment of artifacts in Hudson and it looks like the new ones are now
available at
https://repository.apache.org/content/groups/snapshots-group/org/apache/servicemix/servicemix-smpp
> invalid manifest for servicemix-smpp 2009.01
> --------------------------------------------
>
> Key: SMX4-350
> URL: https://issues.apache.org/activemq/browse/SMX4-350
> Project: ServiceMix 4
> Issue Type: Bug
> Affects Versions: 4.1.0
> Environment: java 1.6
> Reporter: James Korotney
> Assignee: Jean-Baptiste Onofré
> Attachments: servicemix-smpp-2009.02-SNAPSHOT.jar
>
>
> Current manifest is invalid in current snapshot - not sure how it is created
> - looks automated. See version at
> https://repository.apache.org/content/groups/staging/org/apache/servicemix/servicemix-smpp/2009.01/servicemix-smpp-2009.01.jar
> Specifically, see the Require-Bundle attribute, which ends with a comma, and
> has the line broken up with whitespace at odd intervals:
> Require-Bundle: org.apache.servicemix.bundles.jaxp-ri, org.
> springframework.core, org.springframework.beans,
> org.springframework.context,
> java.util.jar.Manifest appears to pull incorrect information in java 1.6 due
> to this issue.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
