You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Chris Dolan (Created) (JIRA)" <ji...@apache.org> on 2011/10/06 14:42:29 UTC
[jira] [Created] (KARAF-918) pax-url prerequisites for a feature
are not respected
pax-url prerequisites for a feature are not respected
-----------------------------------------------------
Key: KARAF-918
URL: https://issues.apache.org/jira/browse/KARAF-918
Project: Karaf
Issue Type: Bug
Components: karaf-features
Affects Versions: 2.2.2
Reporter: Chris Dolan
I have a custom feature that looks roughly like this:
<feature name="..." version="${project.version}" resolver="(obr)">
<feature version="[2,3)">war</feature>
...
<bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
</feature>
This feature fails to load via featuresBoot with the following error message:
Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
The "war" feature in standard-2.2.2-features.xml has this line:
<bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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-918) pax-url prerequisites for a feature
are not respected
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-918:
---------------------------------------
Priority: Minor (was: Major)
Fix Version/s: 3.0.0
2.2.5
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-features
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.5, 3.0.0
>
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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-918) pax-url prerequisites for a feature
are not respected
Posted by "Jean-Baptiste Onofré (Resolved JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré resolved KARAF-918.
----------------------------------------
Resolution: Duplicate
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.6, 3.0.0
>
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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-918) pax-url prerequisites for a feature
are not respected
Posted by "Jean-Baptiste Onofré (Updated JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré updated KARAF-918:
---------------------------------------
Fix Version/s: (was: 2.2.5)
2.2.6
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-features
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.6, 3.0.0
>
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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-918) pax-url prerequisites for a feature are
not respected
Posted by "Jamie goodyear (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jamie goodyear closed KARAF-918.
--------------------------------
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.6, 3.0.0
>
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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] [Commented] (KARAF-918) pax-url prerequisites for a feature
are not respected
Posted by "Jean-Baptiste Onofré (Commented JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13227552#comment-13227552 ]
Jean-Baptiste Onofré commented on KARAF-918:
--------------------------------------------
KARAF-608 already address the same problem.
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-feature
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.6, 3.0.0
>
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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-918) pax-url prerequisites for a feature
are not respected
Posted by "Jean-Baptiste Onofré (Assigned JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jean-Baptiste Onofré reassigned KARAF-918:
------------------------------------------
Assignee: Jean-Baptiste Onofré
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-features
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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] [Commented] (KARAF-918) pax-url prerequisites for a feature
are not respected
Posted by "Chris Dolan (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-918?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13177714#comment-13177714 ]
Chris Dolan commented on KARAF-918:
-----------------------------------
I posted a proposal attached to KARAF-910 that would also solve this defect by adding explicit support for MalformedURLException to FeaturesServiceImpl.
https://issues.apache.org/jira/browse/KARAF-910?focusedCommentId=13177709#comment-13177709
> pax-url prerequisites for a feature are not respected
> -----------------------------------------------------
>
> Key: KARAF-918
> URL: https://issues.apache.org/jira/browse/KARAF-918
> Project: Karaf
> Issue Type: Bug
> Components: karaf-features
> Affects Versions: 2.2.2
> Reporter: Chris Dolan
> Assignee: Jean-Baptiste Onofré
> Priority: Minor
> Fix For: 2.2.6, 3.0.0
>
>
> I have a custom feature that looks roughly like this:
> <feature name="..." version="${project.version}" resolver="(obr)">
> <feature version="[2,3)">war</feature>
> ...
> <bundle start-level="90">war:mvn:org.apache.activemq/activemq-web-console/5.5.0/war?Web-ContextPath=/ServiceHost/jms-console</bundle>
> </feature>
> This feature fails to load via featuresBoot with the following error message:
> Error when installing feature avid-servicehost-jms: java.net.MalformedURLException: unknown protocol: war
> The "war" feature in standard-2.2.2-features.xml has this line:
> <bundle>mvn:org.ops4j.pax.url/pax-url-war/1.2.7</bundle>
> But that line is currently useless to my scenario. The pax-url-war bundle must be loaded before my features.xml is even validated or the error occurs. So, I'm forced to include pax-url-war in startup.properties.
> I would prefer that if the features manager encounters a malformed URL, then it should load prerequisites before throwing. This would, for example, allow us to put pax-url-wrap as an optional load instead of in startup.properties.
--
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