[
https://issues.apache.org/jira/browse/KARAF-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13431693#comment-13431693
]
Michael Prieß commented on KARAF-1692:
--------------------------------------
There are different behaviors between linux and windows. It's possible to
reproduce the problem described by lars with a exploded war under windows. For
testing I used this war http://mirrors.jenkins-ci.org/war/latest/jenkins.war.
Seems like the path used in the Parser class is not correct under windows.
Under linux the path looks fine, but the bundle cannot be generated. But this
is maybe another problem which should also occur under windows after fixing the
path.
org.ops4j.pax.url.wrap.internal.Parser
*Linux Path:*
jardir:/home/mpriess/Arbeitsfläche/apache-karaf-2.2.8/deploy/jenkins.war$Bundle-SymbolicName=jenkins.war&Bundle-Version=0.0.0
*Windows Path:*
jardir:C:\\Users\\mpriess\\Downloads\\apache-karaf-2.2.8\\apache-karaf-2.2.8\\deploy\\jenkins.war$Bundle-SymbolicName=C:\\Users\\xonix\\Downloads\\apache-karaf-2.2.8\\apache-karaf&Bundle-Version=2.2.8.deployjenkins"
> Deployment of unpacked WAR does not work
> ----------------------------------------
>
> Key: KARAF-1692
> URL: https://issues.apache.org/jira/browse/KARAF-1692
> Project: Karaf
> Issue Type: Bug
> Components: karaf-core
> Affects Versions: 2.2.8
> Environment: Karaf 2.2.8 on Windows
> Reporter: Lars-Erik Helander
> Assignee: Achim Nierbeck
>
> A WAR that deploys properly when put into the deploy directory, is not
> deployable as an unpacked WAR (WAR content put into a folder with .war
> extension) in the deploy directory.
--
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
