You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@felix.apache.org by "Stuart McCulloch (Created) (JIRA)" <ji...@apache.org> on 2012/02/11 15:15:59 UTC
[jira] [Created] (FELIX-3347) Upper-case environment variables end
up in final manifest
Upper-case environment variables end up in final manifest
---------------------------------------------------------
Key: FELIX-3347
URL: https://issues.apache.org/jira/browse/FELIX-3347
Project: Felix
Issue Type: Bug
Components: Maven Bundle Plugin
Affects Versions: maven-bundle-plugin-2.3.6, maven-bundle-plugin-2.3.5
Reporter: Stuart McCulloch
Assignee: Stuart McCulloch
Priority: Blocker
On 10 Feb 2012, at 08:01, Tuomas Kiviaho wrote:
I'm having the exact same problem. Any news what might cause this. I upgraded
the bundle plugin from 2.0.1 to 2.3.6 and this started to appear.
See this thread http://www.mail-archive.com/users@felix.apache.org/msg11754.html for more discussion.
I tracked the cause down to https://issues.apache.org/jira/browse/FELIX-2449 which added the Maven session execution properties to the properties passed to bnd.
This change was needed so people could use command-line properties in bnd macros, otherwise you could get inconsistent results between Maven and bnd filtering.
Perhaps we should simply avoid adding any Maven session execution properties that start with an upper-case letter (bnd automatically copies these to the manifest).
Reminder: you can tell bnd to avoid copying entries to the manifest by listing the headers in the <_removeheaders> instruction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (FELIX-3347) Upper-case environment variables end
up in final manifest
Posted by "Stuart McCulloch (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch updated FELIX-3347:
------------------------------------
Fix Version/s: maven-bundle-plugin-2.3.7
> Upper-case environment variables end up in final manifest
> ---------------------------------------------------------
>
> Key: FELIX-3347
> URL: https://issues.apache.org/jira/browse/FELIX-3347
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.5, maven-bundle-plugin-2.3.6
> Reporter: Stuart McCulloch
> Assignee: Stuart McCulloch
> Priority: Blocker
> Fix For: maven-bundle-plugin-2.3.7
>
>
> On 10 Feb 2012, at 08:01, Tuomas Kiviaho wrote:
> I'm having the exact same problem. Any news what might cause this. I upgraded
> the bundle plugin from 2.0.1 to 2.3.6 and this started to appear.
> See this thread http://www.mail-archive.com/users@felix.apache.org/msg11754.html for more discussion.
> I tracked the cause down to https://issues.apache.org/jira/browse/FELIX-2449 which added the Maven session execution properties to the properties passed to bnd.
> This change was needed so people could use command-line properties in bnd macros, otherwise you could get inconsistent results between Maven and bnd filtering.
> Perhaps we should simply avoid adding any Maven session execution properties that start with an upper-case letter (bnd automatically copies these to the manifest).
> Reminder: you can tell bnd to avoid copying entries to the manifest by listing the headers in the <_removeheaders> instruction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (FELIX-3347) Upper-case environment variables end
up in final manifest
Posted by "Stuart McCulloch (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/FELIX-3347?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stuart McCulloch closed FELIX-3347.
-----------------------------------
Resolution: Fixed
Fixed in r1243069
> Upper-case environment variables end up in final manifest
> ---------------------------------------------------------
>
> Key: FELIX-3347
> URL: https://issues.apache.org/jira/browse/FELIX-3347
> Project: Felix
> Issue Type: Bug
> Components: Maven Bundle Plugin
> Affects Versions: maven-bundle-plugin-2.3.5, maven-bundle-plugin-2.3.6
> Reporter: Stuart McCulloch
> Assignee: Stuart McCulloch
> Priority: Blocker
> Fix For: maven-bundle-plugin-2.3.7
>
>
> On 10 Feb 2012, at 08:01, Tuomas Kiviaho wrote:
> I'm having the exact same problem. Any news what might cause this. I upgraded
> the bundle plugin from 2.0.1 to 2.3.6 and this started to appear.
> See this thread http://www.mail-archive.com/users@felix.apache.org/msg11754.html for more discussion.
> I tracked the cause down to https://issues.apache.org/jira/browse/FELIX-2449 which added the Maven session execution properties to the properties passed to bnd.
> This change was needed so people could use command-line properties in bnd macros, otherwise you could get inconsistent results between Maven and bnd filtering.
> Perhaps we should simply avoid adding any Maven session execution properties that start with an upper-case letter (bnd automatically copies these to the manifest).
> Reminder: you can tell bnd to avoid copying entries to the manifest by listing the headers in the <_removeheaders> instruction.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira