<div><br></div>There are 2 extra things to do:<div><br></div><div>1) Separate mc-integration code in its own module, so that container module has no dependencies on mc-kernel artifacts.</div><div>This will require an additional reflection style invocation in one place, but should not be a problem to do.</div>
<div><br></div><div>2) Add xml file configuration for marking certain components to use mc-interception even though they are not marked as @InterceptMC</div><div>This will allow us to externally configure to mc-intercept components that are part of exo-kernel and GateIn. We won't annotate these components in advance. Application developers who want to integrate with their existing mc-beans components will still use @InterceptMC. XML configuration will override annotations.</div>
<div><br></div><div>I'm also working on release part of this. What's the status of exopackage ATM?</div><div><br></div><div><span class="Apple-style-span" style="font-family: Verdana; font-size: 13px; "><div style="margin-top: 0px; margin-bottom: 0px; ">
<a href="http://svn.exoplatform.org/projects/utils/exopackage">http://svn.exoplatform.org/projects/utils/exopackage</a> (This one is actually used in portal packaging/pkg)</div><div style="margin-top: 0px; margin-bottom: 0px; ">
<a href="https://svn.jboss.org/repos/gatein/portal/trunk/packaging/exopackage">https://svn.jboss.org/repos/gatein/portal/trunk/packaging/exopackage</a> (???)</div><div style="margin-top: 0px; margin-bottom: 0px; "><a href="https://svn.jboss.org/repos/gatein/tools/packager">https://svn.jboss.org/repos/gatein/tools/packager</a> (This one seems the latest, and being worked on - not used in packaging/pkg)</div>
<div><br></div></span></div><div>I have some changes in:</div><div><br></div><div>javascript/eXo/command/exobuild.js</div><div> - introduced --integration-test option</div><div><br></div><div>javascript/eXo/server/JbossEar.js</div>
<div> - introduced jbossas specific dependencies - only if --integration-test option is on</div><div><br></div><div>javascript/eXo/projects/Product.js</div><div> - added 'integrationTests' flag to elegantly communicate --integration-test flag from exobuild.js to JbossEar.js</div>
<div><br></div><div>I'd like to make a branch so that others can try this. Where would be the best place?</div><div><br></div><div>Cheers,</div><div><br></div><div>- marko</div><div><br></div><div><br><br><div class="gmail_quote">
On Tue, Nov 24, 2009 at 1:27 PM, Julien Viet <span dir="ltr"><<a href="mailto:julien@julienviet.com">julien@julienviet.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex;">
<div style="word-wrap:break-word">Hi Thomas,<div><br></div><div>I discussed with Marko last night late about how to improve his work and he agreed to proceed this way.</div><div><br></div><div>cheers</div><div><br></div><font color="#888888"><div>
Julien</div></font><div><div></div><div class="h5"><div><br><div><div>On Nov 24, 2009, at 1:19 PM, Thomas Heute wrote:</div><br><blockquote type="cite"> <div text="#000000" bgcolor="#ffffff"> See Marko's email of the 17th, can we commit this into kernel before it gets released ?<br>
It has been month since Marko is trying to get attention on the MC integration with little success so far.<br> <br> Marko's changes aren't changing the way it works or interfering on lifecycle it, it just add a way to inject MC beans into eXo Kernel.<br>
<br> Thomas.<br> <br></div></blockquote></div></div></div></div></div></blockquote></div><br></div>