I think this package is embedded from the blueprint-parser jar which is
at version 1.3.2. So the 1.3.0 version is probably correct.
At least it should be the same version as for the blueprint-core 1.4.5
bundle.
Christian
On 21.10.2015 20:53, Samuel E Bratton wrote:
The Namespaces class is a new class for this release but the
org.apache.aries.blueprint.core-1.4.5.jar MANIFEST shows the package exported as
org.apache.aries.blueprint;version="1.3.0". Doesn't that need to be raised to
1.4? Or is that happening elsewhere as part of the release process?
Thanks
--
Samuel Bratton
[email protected]
phone: (512)286-5440; TL 363-5440
-----Christian Schneider <[email protected]> wrote: -----
To: [email protected]
From: Christian Schneider
Sent by: Christian Schneider
Date: 10/21/2015 11:34AM
Subject: Re: [Vote] Release Aries blueprint parser 1.3.2 and blueprint core
1.4.5
I added the license header to Namespaces.
Do we need to fix the script to work with the new maven plugins?
Christian
On 21.10.2015 18:24, Daniel Kulp wrote:
On Oct 21, 2015, at 12:17 PM, John Ross <[email protected]> wrote:
I'm receiving the following RAT failures when running the verify
script against 1045. The last simply means that Namespaces.java needs
a license header. I'm more concerned about the bad MD5s and SHA1s. Am
I doing something wrong on my end? I have the latest KEYS file
imported.
With the latest releases of the various maven plugins, the “asc” files aren’t
deployed with MD5 and SHA1 files. Your script is checking for them but not
finding them.
Dan
--
Christian Schneider
http://www.liquid-reality.de
Open Source Architect
http://www.talend.com
