A quick update on Weld-OSGi. I finally managed to get all tests - plain, incontainer, etc - to pass. :-) (apart from that disabled LifeCycleTest, which I'm waiting on Mathieu to have a look) This are the latest branches I've been working on (a) Weld API: https://github.com/alesj/api/tree/osgi2 (b) AS7 OSGi: https://github.com/alesj/jboss-as/tree/osgi2 (c) Weld OSGi: https://github.com/alesj/core/tree/osgi3 @Stuart: * I would need a new AS7 CDI TCK Runner - 1.0.0.CR3

* if you could run this stuff against JEE6 TCK

Now the next question is how to get this into AS7? As it's sort of a chicken-n-egg problem. :-) We need to upgrade Weld API in AS7 + switch its impl, but to release the impl we need to test this against latest AS7. I guess if this manual setup from above (a, b, c) fully works, we could tweak/hack the release of impl (Weld Core) a bit?

> Now the next question is how to get this into AS7? > As it's sort of a chicken-n-egg problem. :-) > > We need to upgrade Weld API in AS7 + switch its impl, > but to release the impl we need to test this against latest AS7. For the AS7-dev ml ... We have Weld-OSGi impl, which needs API change, plus small impl change on top of this API in AS7 integration code. But in order to confirm everything works, we need to test this against upgraded AS7. I did this manually, and it seems to work -- all tests pass. But of course, when releasing, there should be no SNAPSHOT. I could trick Weld Core into using AS7.1.1 jars, where the AS7 running would be this modified instance, as we only need it for Arquillian API, *but* unfortunately 7.1.1 is not "Arquillian" compatible with latest AS7 upstream. Any suggestion on how to actually pull off this Weld 1.2 (with OSGi) release? -Ales _______________________________________________ jboss-as7-dev mailing list jboss-as7-dev(a)lists.jboss.org https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Wdym? That i manually fix (upgrade with new Weld bits) my 7.1.1 instance and do a Weld release? -Ales On Sep 17, 2012, at 3:59, Stuart Douglas<stuart.w.douglas(a)gmail.com> wrote: > Can't you just use the appropriate arquillian version for 7.1.1? > > Stuart > > Ales Justin wrote: >>> Now the next question is how to get this into AS7? >>> As it's sort of a chicken-n-egg problem. :-) >>> >>> We need to upgrade Weld API in AS7 + switch its impl, >>> but to release the impl we need to test this against latest AS7. >> For the AS7-dev ml ... >> >> We have Weld-OSGi impl, which needs API change, >> plus small impl change on top of this API in AS7 integration code. >> >> But in order to confirm everything works, we need to test this against upgraded AS7. >> I did this manually, and it seems to work -- all tests pass. >> But of course, when releasing, there should be no SNAPSHOT. >> >> I could trick Weld Core into using AS7.1.1 jars, where the AS7 running would be this modified instance, >> as we only need it for Arquillian API, *but* unfortunately 7.1.1 is not "Arquillian" compatible with latest AS7 upstream. >> >> Any suggestion on how to actually pull off this Weld 1.2 (with OSGi) release? >> >> -Ales >> >> >> _______________________________________________ >> jboss-as7-dev mailing list >> jboss-as7-dev(a)lists.jboss.org >> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev

Doesn't release run tests? At least, when using "mvn release:xyz", which is what I'm using. But probably not against container, as there is no -Dincontainer, right? -Ales On Sep 17, 2012, at 9:14 AM, Stuart Douglas<stuart.w.douglas(a)gmail.com> wrote: > Basically I think you will need to just have the 7.1.1 version in the pom when you release, even if it does not actually work. > Stuart > > Ales Justin wrote: >> Wdym? >> >> That i manually fix (upgrade with new Weld bits) my 7.1.1 instance and do a Weld release? >> >> -Ales >> >> On Sep 17, 2012, at 3:59, Stuart Douglas<stuart.w.douglas(a)gmail.com> wrote: >> >>> Can't you just use the appropriate arquillian version for 7.1.1? >>> >>> Stuart >>> >>> Ales Justin wrote: >>>>> Now the next question is how to get this into AS7? >>>>> As it's sort of a chicken-n-egg problem. :-) >>>>> >>>>> We need to upgrade Weld API in AS7 + switch its impl, >>>>> but to release the impl we need to test this against latest AS7. >>>> For the AS7-dev ml ... >>>> >>>> We have Weld-OSGi impl, which needs API change, >>>> plus small impl change on top of this API in AS7 integration code. >>>> >>>> But in order to confirm everything works, we need to test this against upgraded AS7. >>>> I did this manually, and it seems to work -- all tests pass. >>>> But of course, when releasing, there should be no SNAPSHOT. >>>> >>>> I could trick Weld Core into using AS7.1.1 jars, where the AS7 running would be this modified instance, >>>> as we only need it for Arquillian API, *but* unfortunately 7.1.1 is not "Arquillian" compatible with latest AS7 upstream. >>>> >>>> Any suggestion on how to actually pull off this Weld 1.2 (with OSGi) release? >>>> >>>> -Ales >>>> >>>> >>>> _______________________________________________ >>>> jboss-as7-dev mailing list >>>> jboss-as7-dev(a)lists.jboss.org >>>> https://lists.jboss.org/mailman/listinfo/jboss-as7-dev