[
http://issues.ops4j.org/browse/PAXCONSTRUCT-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12513#action_12513
]
mcculls commented on PAXCONSTRUCT-115:
--------------------------------------
Originally the runner directory was under "target", but several users pointed
out the following use-cases which led to it being moved:
1) Upgrading bundles during development
This was raised during my first major OSGi tutorial involving pax-construct,
when I was explaining how OSGi lets you upgrade bundles without restarting.
Almost all the developers did the following:
* mvn clean install
* launch the application with "pax:provision" (alias of "pax:run")
* modify one of the bundles
* mvn clean install
* attempt to upgrade the bundle in the OSGi console
blam, the OSGi framework throws up all sorts of errors because you've just
wiped out the runner working directory (for many developers "mvn clean install"
is an instinctive reflex - you can't get them to install without clean)
2) Lack of Maven artifact caching in pax-runner
Previous releases of pax-runner do not cache downloaded artifacts in the local
Maven repository (I believe a feature request was raised for this, but I don't
know if it's been implemented). This means that if you don't have the Equinox /
Felix / KF framework artifacts in your local Maven repository, or have them
referred to in your project POMs so that Maven will cache them, then pax-runner
will (re-)download them every time you wipe the runner working directory.
For users with limited bandwidth this is a big deal - moving the pax-runner
working directory out of "target" and using the option to keep framework
bundles around between runs means you can run offline as long as your project
bundles and their dependencies are in your local Maven repository (which for
most Maven projects will be true).
For both these reasons the default "pax:run" working directory location will
remain outside of "target", but I'm not adverse to allowing users to configure
this :)
> Specify runner directory for pax:run
> ------------------------------------
>
> Key: PAXCONSTRUCT-115
> URL: http://issues.ops4j.org/browse/PAXCONSTRUCT-115
> Project: Pax Construct
> Issue Type: Improvement
> Components: maven-pax-plugin
> Affects Versions: 1.4
> Reporter: Richard Wallace
> Assignee:
>
> There is currently no way to specify the directory that runner will put the
> runner/deploy-pom.xml and runner/target/pom-transformed.xml file into. You
> can change what Pax Runner uses as its base by passing a param, but that
> still leaves a runner directory in your project root directory where it
> should be (or you should have the option of) putting it into the target
> directory.
--
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
