You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@karaf.apache.org by "Gavin Scott (JIRA)" <ji...@apache.org> on 2012/11/07 21:54:12 UTC
[jira] [Created] (KARAF-2005) Unable to provision blueprint non-jar
artifacts in paxexam karaf
Gavin Scott created KARAF-2005:
----------------------------------
Summary: Unable to provision blueprint non-jar artifacts in paxexam karaf
Key: KARAF-2005
URL: https://issues.apache.org/jira/browse/KARAF-2005
Project: Karaf
Issue Type: Bug
Components: karaf-tooling
Affects Versions: 2.3.0
Reporter: Gavin Scott
In karaf paxexam tests, non-jar artifacts (such as blueprint xml) cannot be deployed with non-maven urls. In this case the artifacts are copied into the karaf deploy/ directory with a .jar extension, so they do not deploy correctly. This is an example @Configuration that will not deploy the referenced blueprint.xml correctly:
{code}
@Configuration
public Option[] config()
{
return new Option[] {
karafDistributionConfiguration()
.frameworkUrl("file:/tmp/apache-karaf-2.3.0.zip")
.karafVersion("2.3.0").name("Apache Karaf"),
new UrlProvisionOption("file:/tmp/blueprint.xml"),
};
}
{/code}
A workaround is to make the url resemble a maven url. For example using "file:/tmp/xml/blueprint.xml" in the above example would work. The offending code is KarafTestContainer.createFileNameWithRandomPrefixFromUrlAtTarget().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-2005) Unable to provision non-jar artifacts
in paxexam karaf
Posted by "Gavin Scott (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin Scott updated KARAF-2005:
-------------------------------
Description:
In karaf paxexam tests, non-jar artifacts (such as blueprint xml) cannot be deployed with non-maven urls. In this case the artifacts are copied into the karaf deploy/ directory with a .jar extension, so they do not deploy correctly. This is an example @Configuration that will not deploy the referenced blueprint.xml correctly:
{code}
@Configuration
public Option[] config()
{
return new Option[] {
karafDistributionConfiguration()
.frameworkUrl("file:/tmp/apache-karaf-2.3.0.zip")
.karafVersion("2.3.0").name("Apache Karaf"),
new UrlProvisionOption("file:/tmp/blueprint.xml"),
};
}
{code}
A workaround is to make the url resemble a maven url. For example using "file:/tmp/xml/blueprint.xml" in the above example would work. The offending code is KarafTestContainer.createFileNameWithRandomPrefixFromUrlAtTarget().
was:
In karaf paxexam tests, non-jar artifacts (such as blueprint xml) cannot be deployed with non-maven urls. In this case the artifacts are copied into the karaf deploy/ directory with a .jar extension, so they do not deploy correctly. This is an example @Configuration that will not deploy the referenced blueprint.xml correctly:
{code}
@Configuration
public Option[] config()
{
return new Option[] {
karafDistributionConfiguration()
.frameworkUrl("file:/tmp/apache-karaf-2.3.0.zip")
.karafVersion("2.3.0").name("Apache Karaf"),
new UrlProvisionOption("file:/tmp/blueprint.xml"),
};
}
{/code}
A workaround is to make the url resemble a maven url. For example using "file:/tmp/xml/blueprint.xml" in the above example would work. The offending code is KarafTestContainer.createFileNameWithRandomPrefixFromUrlAtTarget().
> Unable to provision non-jar artifacts in paxexam karaf
> ------------------------------------------------------
>
> Key: KARAF-2005
> URL: https://issues.apache.org/jira/browse/KARAF-2005
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 2.3.0
> Reporter: Gavin Scott
>
> In karaf paxexam tests, non-jar artifacts (such as blueprint xml) cannot be deployed with non-maven urls. In this case the artifacts are copied into the karaf deploy/ directory with a .jar extension, so they do not deploy correctly. This is an example @Configuration that will not deploy the referenced blueprint.xml correctly:
> {code}
> @Configuration
> public Option[] config()
> {
> return new Option[] {
> karafDistributionConfiguration()
> .frameworkUrl("file:/tmp/apache-karaf-2.3.0.zip")
> .karafVersion("2.3.0").name("Apache Karaf"),
> new UrlProvisionOption("file:/tmp/blueprint.xml"),
> };
> }
> {code}
> A workaround is to make the url resemble a maven url. For example using "file:/tmp/xml/blueprint.xml" in the above example would work. The offending code is KarafTestContainer.createFileNameWithRandomPrefixFromUrlAtTarget().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Updated] (KARAF-2005) Unable to provision non-jar artifacts
in paxexam karaf
Posted by "Gavin Scott (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/KARAF-2005?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Gavin Scott updated KARAF-2005:
-------------------------------
Summary: Unable to provision non-jar artifacts in paxexam karaf (was: Unable to provision blueprint non-jar artifacts in paxexam karaf)
> Unable to provision non-jar artifacts in paxexam karaf
> ------------------------------------------------------
>
> Key: KARAF-2005
> URL: https://issues.apache.org/jira/browse/KARAF-2005
> Project: Karaf
> Issue Type: Bug
> Components: karaf-tooling
> Affects Versions: 2.3.0
> Reporter: Gavin Scott
>
> In karaf paxexam tests, non-jar artifacts (such as blueprint xml) cannot be deployed with non-maven urls. In this case the artifacts are copied into the karaf deploy/ directory with a .jar extension, so they do not deploy correctly. This is an example @Configuration that will not deploy the referenced blueprint.xml correctly:
> {code}
> @Configuration
> public Option[] config()
> {
> return new Option[] {
> karafDistributionConfiguration()
> .frameworkUrl("file:/tmp/apache-karaf-2.3.0.zip")
> .karafVersion("2.3.0").name("Apache Karaf"),
> new UrlProvisionOption("file:/tmp/blueprint.xml"),
> };
> }
> {/code}
> A workaround is to make the url resemble a maven url. For example using "file:/tmp/xml/blueprint.xml" in the above example would work. The offending code is KarafTestContainer.createFileNameWithRandomPrefixFromUrlAtTarget().
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira