It will be released to maven, but not right away.
Also it might have to be backported to the right branch.
________________________________
From: Raj [r...@apache.org]
Sent: Friday, November 14, 2014 7:52 AM
To: Zack Shoylev
Cc: dev@jclouds.apache.org
Subject: Re: References to ${jclouds.version} in MANIFEST.MF file of
openstack-neutron-1.8.1.jar
Hi Zack,
Thanks for fixing it.
This changes will be eventually in the artifact from maven central repository
right? Or Do I have to build and use it?
Thanks.
On Fri, Nov 14, 2014 at 7:04 PM, Zack Shoylev
<zack.shoy...@rackspace.com<mailto:zack.shoy...@rackspace.com>> wrote:
This should fix it
https://github.com/jclouds/jclouds-labs-openstack/pull/170
Thanks for reporting the issue!
________________________________________
From: Andrew Phillips [andr...@apache.org<mailto:andr...@apache.org>]
Sent: Friday, November 14, 2014 7:14 AM
To: dev@jclouds.apache.org<mailto:dev@jclouds.apache.org>
Cc: Raj
Subject: Re: References to ${jclouds.version} in MANIFEST.MF file of
openstack-neutron-1.8.1.jar
(moving to dev@...)
> I didn't build openstack-neutron. I just put 1.8.1 as my maven dependency
> and built my project. When I see the jar from my local repo, I found
> $Subject.
Thanks for flagging this up, Raj! I think you've found a bug in the
POM file(s) for the affected projects: the OSGi import statements
(e.g. [1]) still refer to "jclouds.version". I'm guessing that should
be "project.parent.version" or similar.
I hope one of the devs with more knowledge of the Rackspace providers
can confirm which setting is the correct one.
Are you able to work around the issue with some pre-processing for
now, or are you stuck on this?
Regards
ap
[1]
https://github.com/jclouds/jclouds-labs-openstack/blob/master/rackspace-cloudfiles/pom.xml#L45
--
Rajkumar Rajaratnam
Committer & PMC Member, Apache Stratos
Software Engineer, WSO2
