oopps.. not trunk yet. Its in
https://github.com/ops4j/org.ops4j.pax.runner/tree/feature-aether-support

Well if you want the fast release, you go from trunk. Then i will work on
1.7 with aether merged into.
Alternatively you are free to merge that branch in and test + release. But..
yeah i think pax runner was just a middle step for you, right ? (not your
main concern)

On Tue, Feb 22, 2011 at 12:41 PM, Andreas Pieber <anpie...@gmail.com> wrote:

> oh, ok, the current trunk runs fine for me :) But I've a limited
> number of use cases...
>
> Would you like to upgrade or should I give it a view?
>
> I would be very thankful if some additional user could try the latest
> snapshots with their current environments to avoid breaking them.
>
> Kind regards,
> Andreas
>
> On Tue, Feb 22, 2011 at 12:24 PM, Toni Menzel <t...@okidokiteam.com>
> wrote:
> > Regarding Runner 1.6 and its aether support: It is meant to work already
> in
> > trunk and should be included into the release.
> > But: its been a while i worked on this, i think there are more recent
> aether
> > versions we should use.
> >
> > On Tue, Feb 22, 2011 at 12:14 PM, Andreas Pieber <anpie...@gmail.com>
> wrote:
> >>
> >> Hey guys,
> >>
> >> OK, TBH I have the problem that pax-scanner's scan-feature does not
> >> support version ranges like [x,y) by now. To fix this problem I've
> >> upgraded Pax-Scanner to use the latest Karaf version. But to get this
> >> fix into pax-exam I'll also have to release pax-runner and pax-exam
> >> besides pax-scanner. So there will be quite a bunch of releases within
> >> the next days :) In detail:
> >>
> >> Pax-Scanner 1.1...
> >> ----------------------------
> >>
> >> will include the following fixes
> >>
> >> PAXSCANNER-13    UNRESOLVED      Use Apache Karaf instead of ServiceMix
> >> for
> >> features scanner
> >> PAXSCANNER-17    FIXED   Upgrade maven-bundle-plugin to 2.3.4
> >> PAXSCANNER-19    FIXED   Upgrade to pax-url 1.2.5
> >> PAXSCANNER-20    FIXED   Upgrade to swissbox 1.3.1
> >> PAXSCANNER-18    FIXED   upgrade pax-base to 1.2.2
> >> PAXSCANNER-14    FIXED   ConcurrentModificationException while stopping
> >> scanner service
> >> PAXSCANNER-11    FIXED   Make an uber bundle
> >> PAXSCANNER-12    FIXED   Make Configuration Admin packages optional
> >>
> >> in addition I would like to remove the maven translator plugin for
> >> jdk1.4 if this is ok. This release is almost finished except for a
> >> little bit fine-tuning and the upgrade to karaf-2.2 components
> >>
> >> Pax-Runner 1.6...
> >> ------------------------
> >>
> >> will include the following fixes
> >>
> >> PAXRUNNER-350    UNRESOLVED      Add support of start levels for bundles
> >> in
> >> platform definition xml
> >> PAXRUNNER-370    UNRESOLVED      Upgrade to pax-scanner 1.1.0
> >> PAXRUNNER-261    UNRESOLVED      Use multithreading to improve
> performance
> >> PAXRUNNER-359    FIXED   Support Felix 3.0.3
> >> PAXRUNNER-360    FIXED   Support gogo 0.6.1 and replace default 0.6.0
> >> with this one
> >> PAXRUNNER-367    FIXED   Use java.nio instead of java.io during URL
> >> download
> >> PAXRUNNER-354    FIXED   in generated run.sh by executors zip&script in
> >> classpath properties ';' is used as delimiter instead of ':'
> >> PAXRUNNER-358    FIXED   Error in batch files
> >> PAXRUNNER-368    FIXED   Upgrade pax-url to 1.2.5
> >> PAXRUNNER-369    FIXED   upgrade swissbox to 1.3.1
> >> PAXRUNNER-347    FIXED   A "--noLogo" option for pax-runner would be
> nice.
> >> PAXRUNNER-361    FIXED   Broken Felix 3.0.2 link file
> >> PAXRUNNER-365    FIXED   Support Apache Felix 3.0.4, 3.0.5, 3.0.6
> >> PAXRUNNER-363    FIXED   Support Equinox 3.6.1
> >> PAXRUNNER-366    FIXED   Support Knopflerfish 3.1.0
> >>
> >> Is it a problem to delay paxrunner-261 and 250 to 1.7 (since both are
> >> "only" features? In addition: How do we want to handle ather in this
> >> release? Finally, I also want to remove the maven translator plugin
> >> for jdk1.4... WDYT?
> >>
> >> Pax-Exam 1.2.4....
> >> ----------------------------
> >>
> >> will include the following fixes
> >>
> >> PAXEXAM-200      UNRESOLVED      Upgrade pax-runner to 1.6
> >> PAXEXAM-197      FIXED   In RemoteBundleContextImpl class, the bundle
> can
> >> be not installed and not found. The code raise a NPE. You must wait
> >> that the bundle is installed.
> >> PAXEXAM-198      FIXED   Upgrade maven-bundle-plugin to 2.3.4
> >> PAXEXAM-199      FIXED   upgrade swissbox to 1.3.1
> >>
> >> Ok, all of my changes are available on github. Please feel free to
> >> review and all comments/problems and/or fixes you want to include
> >> within the next 3-6 days. I really want to get those versions out
> >> shortly after karaf-2.2. Any comments are highly welcomed :)
> >>
> >> kind regards,
> >> Andreas
> >>
> >> _______________________________________________
> >> general mailing list
> >> general@lists.ops4j.org
> >> http://lists.ops4j.org/mailman/listinfo/general
> >
> >
> >
> > --
> > Toni Menzel - http://www.okidokiteam.com
> >
>



-- 
*Toni Menzel - http://www.okidokiteam.com*
_______________________________________________
general mailing list
general@lists.ops4j.org
http://lists.ops4j.org/mailman/listinfo/general

Reply via email to