[gatein-dev] [GateIn] Roll back revision 744 on identity & bug in jcr-core.

[Dimitri BAELI]

   Done, waiting for hudson to confirm (but hudson does not include the
pkg-* commands).
Dimitri BAELI - eXo Platform SAS


On Tue, Nov 24, 2009 at 3:56 PM, Dimitri BAELI <dbaeli at gmail.com> wrote:

>    Please use a branch of
> https://svn.jboss.org/repos/gatein/tools/packager it is here and a
> standalone module for that purpose.
>
> Dimitri BAELI - eXo Platform SAS
>
>
> On Tue, Nov 24, 2009 at 3:55 PM, Dimitri BAELI <dbaeli at gmail.com> wrote:
>
>> I'm late to commit the use of
>>     https://svn.jboss.org/repos/gatein/tools/packager  (This one seems
>> the latest, and being worked on - not used in packaging/pkg)
>>      I'm doing it now
>> Dimitri BAELI - eXo Platform SAS
>>
>>
>> On Tue, Nov 24, 2009 at 2:57 PM, Marko Strukelj <marko.strukelj at gmail.com
>> > wrote:
>>
>>>
>>> There are 2 extra things to do:
>>>
>>> 1) Separate mc-integration code in its own module, so that container
>>> module has no dependencies on mc-kernel artifacts.
>>> This will require an additional reflection style invocation in one place,
>>> but should not be a problem to do.
>>>
>>> 2) Add xml file configuration for marking certain components to use
>>> mc-interception even though they are not marked as @InterceptMC
>>> 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.
>>>
>>> I'm also working on release part of this. What's the status of exopackage
>>> ATM?
>>>
>>> http://svn.exoplatform.org/projects/utils/exopackage  (This one is
>>> actually used in portal packaging/pkg)
>>> https://svn.jboss.org/repos/gatein/portal/trunk/packaging/exopackage(???)
>>> https://svn.jboss.org/repos/gatein/tools/packager  (This one seems the
>>> latest, and being worked on - not used in packaging/pkg)
>>>
>>> I have some changes in:
>>>
>>> javascript/eXo/command/exobuild.js
>>>   - introduced --integration-test option
>>>
>>> javascript/eXo/server/JbossEar.js
>>>   - introduced jbossas specific dependencies - only if --integration-test
>>> option is on
>>>
>>> javascript/eXo/projects/Product.js
>>>   - added 'integrationTests' flag to elegantly communicate
>>> --integration-test flag from exobuild.js to JbossEar.js
>>>
>>> I'd like to make a branch so that others can try this. Where would be the
>>> best place?
>>>
>>> Cheers,
>>>
>>> - marko
>>>
>>>
>>>
>>> On Tue, Nov 24, 2009 at 1:27 PM, Julien Viet <julien at julienviet.com>wrote:
>>>
>>>> Hi Thomas,
>>>>
>>>> I discussed with Marko last night late about how to improve his work and
>>>> he agreed to proceed this way.
>>>>
>>>> cheers
>>>>
>>>> Julien
>>>>
>>>> On Nov 24, 2009, at 1:19 PM, Thomas Heute wrote:
>>>>
>>>>  See Marko's email of the 17th, can we commit this into kernel before it
>>>> gets released ?
>>>> It has been month since Marko is trying to get attention on the MC
>>>> integration with little success so far.
>>>>
>>>> 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.
>>>>
>>>> Thomas.
>>>>
>>>>
>>>
>>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/gatein-dev/attachments/20091124/4f4e1bbc/attachment-0001.html