You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Mike Gardiner (Created) (JIRA)" <ji...@apache.org> on 2011/11/18 21:04:51 UTC
[jira] [Created] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Bug generating feature.xml when dependency has no manifest
----------------------------------------------------------
Key: KARAF-1024
URL: https://issues.apache.org/jira/browse/KARAF-1024
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 3.0.0
Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
Reporter: Mike Gardiner
Fix For: 3.0.0
When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Posted by "Mike Gardiner (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Gardiner updated KARAF-1024:
---------------------------------
Attachment: NoManifest.patch
Fixes bug when an artifact has no manifest when generating the feature.xml.
> Bug generating feature.xml when dependency has no manifest
> ----------------------------------------------------------
>
> Key: KARAF-1024
> URL: https://issues.apache.org/jira/browse/KARAF-1024
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
> Reporter: Mike Gardiner
> Fix For: 3.0.0
>
> Attachments: NoManifest.patch
>
>
> When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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] [Resolved] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-1024.
-----------------------------------------
Resolution: Fixed
Revision 1206134.
> Bug generating feature.xml when dependency has no manifest
> ----------------------------------------------------------
>
> Key: KARAF-1024
> URL: https://issues.apache.org/jira/browse/KARAF-1024
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
> Reporter: Mike Gardiner
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
> Attachments: NoManifest2.patch
>
>
> When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Posted by "Mike Gardiner (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Gardiner updated KARAF-1024:
---------------------------------
Attachment: NoManifest2.patch
Fixes the bug when there is no manifest in the artifact.
> Bug generating feature.xml when dependency has no manifest
> ----------------------------------------------------------
>
> Key: KARAF-1024
> URL: https://issues.apache.org/jira/browse/KARAF-1024
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
> Reporter: Mike Gardiner
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
> Attachments: NoManifest2.patch
>
>
> When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Posted by "Mike Gardiner (Closed) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Gardiner closed KARAF-1024.
--------------------------------
Thanks Jean.
> Bug generating feature.xml when dependency has no manifest
> ----------------------------------------------------------
>
> Key: KARAF-1024
> URL: https://issues.apache.org/jira/browse/KARAF-1024
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
> Reporter: Mike Gardiner
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
> Attachments: NoManifest2.patch
>
>
> When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Posted by "Mike Gardiner (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Mike Gardiner updated KARAF-1024:
---------------------------------
Attachment: (was: NoManifest.patch)
> Bug generating feature.xml when dependency has no manifest
> ----------------------------------------------------------
>
> Key: KARAF-1024
> URL: https://issues.apache.org/jira/browse/KARAF-1024
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
> Reporter: Mike Gardiner
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
> Attachments: NoManifest2.patch
>
>
> When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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] [Assigned] (KARAF-1024) Bug generating feature.xml when
dependency has no manifest
Posted by "Jean-Baptiste Onofré (Assigned JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-1024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-1024:
-------------------------------------------
Assignee: Jean-Baptiste Onofré
> Bug generating feature.xml when dependency has no manifest
> ----------------------------------------------------------
>
> Key: KARAF-1024
> URL: https://issues.apache.org/jira/browse/KARAF-1024
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 3.0.0
> Environment: Ubuntu 10.x, JDK6, Maven 3.0.x
> Reporter: Mike Gardiner
> Assignee: Jean-Baptiste Onofré
> Fix For: 3.0.0
>
> Attachments: NoManifest.patch
>
>
> When using the karaf-maven-plugin and during the feature generation phase if a dependency does not have a manifest the process aborts because it throws an exception thus preventing the KAR from being built. This occurs in the code that generates the wrap prefix I submitted. I have attached a patch that slightly modifies the code to just log a warning that the given artifact doesn't have a manifest and since there is not manifest make the determination that the artifact is also not a bundle since there's no manifest.
--
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