"thomas.diesler(a)jboss.com" wrote :
| Anyhow, the MC framework needs to work in AS and the OSGi examples must run in AS.
This is not something you can do in an Eclipse unit test.
|
| It'd be good if you could trigger the integration tests as part of your normal
commit routine.
|
Although I understand and support this,
this is not always possible - see my latest commits.
For me in order to move fwd, I need to work on Kernel 2.2.x,
which is not yet in AS, and will only be available for AS6.
The same will probably go for Adrian's work on CL's LifeCycle / Resolver.
I guess this requires some automation on whether it even makes sense to run tests on AS.
e.g. libs compatibility
Since in this case you cannot solve the problem with a simple lib change,
as the changes affect the stuff beyond encapsulated MC projects.
e.g. ControllerContext::ungetTarget --> AS' JMX + MC int
View the original post :
http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4266720#...
Reply to the post :
http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...