[
http://issues.ops4j.org/browse/PAXURL-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12613#action_12613
]
Anders Storsveen commented on PAXURL-61:
----------------------------------------
I actually mean that when you use pax-runner in directory scan mode (pax-run.sh
./ --autoWrap), it will create bundles out of jar files that aren't osgi
bundles. but while doing so, it will not create the correct name and version
number. This could however be worked out very often by analyzing the .jar
filename. and extracting name and version number.
> When using autoWrap all created bundles are version 0.
> ------------------------------------------------------
>
> Key: PAXURL-61
> URL: http://issues.ops4j.org/browse/PAXURL-61
> Project: Pax URL
> Issue Type: Bug
> Components: wrap
> Affects Versions: 1.0.0
> Environment: Apache Maven 2.1.0 (r755702; 2009-03-18 20:10:27+0100)
> Java version: 1.6.0_13
> Java home: /System/Library/Frameworks/JavaVM.framework/Versions/1.6.0/Home
> Default locale: no_NO, platform encoding: MacRoman
> OS name: "mac os x" version: "10.5.7" arch: "x86_64" Family: "mac"
> Reporter: Anders Storsveen
> Assignee: Alin Dreghiciu
>
> When running autoWrap from pax runner all created bundles are version 0, this
> creates problems when using bundles that need specific versions of the
> bundle. This is when pax runner is run in directory scan mode. A solution
> could be to try to read version numbers from the jar's filenames.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.ops4j.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
general mailing list
[email protected]
http://lists.ops4j.org/mailman/listinfo/general
