Yes, right another reason to bring an alternative container back into place: the Remote Container, so you can hang-in against running containers (like Karaf) and use its own provisioning scheme. Somewhere in 2.0 this has been dropped to make removing pax runner uses more stable. I don't want to pollute this thread with details on this, just that adding a small removing container should be worth doing. Mostly because on a developer machine, you usually have a real human in front that can manage a Karaf instance himself and keep it running across multiple test runs. This does not work in CI, thats where Exam currently has its strengths. Thats also where you don't have an Eclipse Workspace with exploded bundles to be supported. ;)
On Wed, Jul 27, 2011 at 12:27 AM, Achim Nierbeck <[email protected]>wrote: > I'm not sure if this works, > but for the war deployer it needs to be jardir: > this way a exploded "archive" can be used. > On the other hand if you use Karaf as server you can > also deploy an exploded jar into the deploy folder. > There is a FileInstall-Deployer takes care of it :-) > > regards, Achim > > Am 26.07.2011 23:57, schrieb Toni Menzel: > > Its currently not directly supported (if normal "urls" do not work). >> What you can try is using the "url()" option and passing a equinox string >> into it, >> so like you say: >> url("bundle:/path/to/**workspace/project/bin") >> but i'm pretty sure something in Exam will check this and probably not >> "understand". >> >> If equinox has this feature, it should be pretty simple to implement as >> its just about leaving the url identifier untouched as much as possible and >> pass it over to the osgi framework. >> >> I hope to have a look at it and either directly do it or at least give >> pointers. >> >> What would help definitely is a specific example that is known to work >> with equinox. >> >> Thanks for suggesting this one! >> Toni >> >> On Jul 26, 2011, at 9:22 PM, Harald Wellmann wrote: >> >> Does Pax Exam support exploded bundles, i.e. unpacked JARs? >>> >>> Use case: I would like to run Pax Exam tests directly from my Eclipse >>> workspace, working on workspace bundles/projects. >>> >>> AFAIK, Equinox supports URLs like bundle:/path/to/workspace/**project/bin >>> (I'm not sure about the exact syntax) for provisioning exploded bundles, so >>> I think it should be sufficient for Pax Exam and/or Pax Runner to wrap these >>> URLs in suitable options and forward them to Equinox. >>> >>> If this is not currently supported, I wouldn't mind trying to implement >>> this feature, if someone could give me some pointers where to start... >>> >>> Best regards, >>> Harald >>> >>> >>> >>> >>> ______________________________**_________________ >>> general mailing list >>> [email protected] >>> http://lists.ops4j.org/**mailman/listinfo/general<http://lists.ops4j.org/mailman/listinfo/general> >>> >> >> ______________________________**_________________ >> general mailing list >> [email protected] >> http://lists.ops4j.org/**mailman/listinfo/general<http://lists.ops4j.org/mailman/listinfo/general> >> > > > -- > -- > *Achim Nierbeck* > > > Apache Karaf<http://karaf.apache.org/**> Committer& PMC > OPS4J Pax > Web<http://wiki.ops4j.org/**display/paxweb/Pax+Web/<http://wiki.ops4j.org/display/paxweb/Pax+Web/>> > Committer& Project Lead > blog<http://notizblog.**nierbeck.de/ <http://notizblog.nierbeck.de/>> > > > > ______________________________**_________________ > general mailing list > [email protected] > http://lists.ops4j.org/**mailman/listinfo/general<http://lists.ops4j.org/mailman/listinfo/general> > -- Toni Menzel Source <http://tonimenzel.com>
_______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
