felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Guillaume Nodet <gno...@gmail.com>
Subject Re: [Karaf] Moving Karaf svn into Felix
Date Fri, 24 Apr 2009 13:57:29 GMT
Currently, each subproject has its own lifecycle, but they share the
same trunk / tags.
I.e. when you release a subproject, you don't release everything, but
just copy the subproject subtree into the main tags tree.  It works
and does not imply that you have to release everything at the same
time.

FWIW, I remember talking with the maven guys and they were considering
to change the way the have organized the plugins (they currently also
share the same trunk/tags) to use separate trunk/tags/branches for
each plugin.

Anyway, I think this is a different debate and both can work.  I think
it might be better to follow the existing conventions in Felix for
Karaf, and reconsider using a separate svn tree for each subproject if
the need arise.


On Fri, Apr 24, 2009 at 15:48, Alex Karasulu <akarasulu@gmail.com> wrote:
> According to svn convention anything that releases on it's own needs it's
> own trunk/tags/branches structure.  Do we intended to have Karaf released
> with felix everytime?  Should a need to release Karaf require us to release
> Felix?  Perhaps Karaf should have it's own release schedule.  Like if there
> is a critical bug that forces an immediate release in Karaf should not force
> an unnecessary release of Felix.  We might need to reconsider our svn
> structure to make subprojects more nimble without inconveniencing other
> subprojects.
>
> Just some thoughts.
>
> Regards.
>
> On Fri, Apr 24, 2009 at 6:02 AM, Karl Pauls <karlpauls@gmail.com> wrote:
>
>> I think I'd prefer to only move your trunk to felix/trunk/karaf and
>> start from there.
>>
>> regards,
>>
>> Karl
>>
>> On Fri, Apr 24, 2009 at 11:28 AM, Guillaume Nodet <gnodet@gmail.com>
>> wrote:
>> > That was the main question.  Moving the whole trunk/tags/branches
>> > allows to keep the release tags, but moving only trunk would be more
>> > inlined with the current felix structure.  Not sure about the release
>> > tags in this case (i guess we can leave those in smx and just not
>> > import them).
>> >
>> > On Fri, Apr 24, 2009 at 09:38, Karl Pauls <karlpauls@gmail.com> wrote:
>> >> On Fri, Apr 24, 2009 at 9:26 AM, Guillaume Nodet <gnodet@gmail.com>
>> wrote:
>> >>> I'd like to start moving the ServiceMix Kernel code into Felix now.
>> >>> Given the size of the code base, I think it would be better to just
>> >>> move the tree into its own top level svn structure.
>> >>> I'd like to run the following command:
>> >>>
>> >>>    svn cp https://svn.apache.org/repos/asf/servicemix/smx4/kernel
>> >>> https://svn.apache.org/repos/asf/felix/karaf
>> >>
>> >> That should be .../felix/trunk/karaf no? I think it would be confusing
>> >> to put it along-side the trunk...
>> >>
>> >> regards,
>> >>
>> >> Karl
>> >>
>> >>> Any objections in doing that ?
>> >>>
>> >>> Next steps will include creating a JIRA project and moving all the
>> >>> issues into it (with a KARAF id), then the confluence space.
>> >>>
>> >>> --
>> >>> Cheers,
>> >>> Guillaume Nodet
>> >>> ------------------------
>> >>> Blog: http://gnodet.blogspot.com/
>> >>> ------------------------
>> >>> Open Source SOA
>> >>> http://fusesource.com
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> Karl Pauls
>> >> karlpauls@gmail.com
>> >>
>> >
>> >
>> >
>> > --
>> > Cheers,
>> > Guillaume Nodet
>> > ------------------------
>> > Blog: http://gnodet.blogspot.com/
>> > ------------------------
>> > Open Source SOA
>> > http://fusesource.com
>> >
>>
>>
>>
>> --
>> Karl Pauls
>> karlpauls@gmail.com
>>
>
>
>
> --
> Alex Karasulu
> My Blog :: http://www.jroller.com/akarasulu/
> Apache Directory Server :: http://directory.apache.org
> Apache MINA :: http://mina.apache.org
>



-- 
Cheers,
Guillaume Nodet
------------------------
Blog: http://gnodet.blogspot.com/
------------------------
Open Source SOA
http://fusesource.com

Mime
View raw message