[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [riena-dev] Riena CVS clean-up & refactoring
|
Sounds good to me (i.e. nebula goes to runtime, rap goes to rap).
Kind regards,
Elias.
On Fri, Jul 16, 2010 at 5:08 AM, Campo, Christian
<Christian.Campo@xxxxxxxxxxxx> wrote:
> I think the restructuring is a good idea. (maybe others like to comment that as well).
>
> There is one point where I disagree with your proposal which is the "optional" subdirectory:
>
> 1. I think the name "optional" leaves room for interpretation and in general will make people dump everything in there which is new and has no obvious place.
>
> 2. I disagree that the Nebula ridget belongs into /optional although its in the optional ridget bundle. I think it belongs into runtime and shouldnt be in a place where it is easily judged as second class citizien. People can then in their launch config disable it as they can choose not to use navigation, communication or security.
>
> I think Riena on RAP belongs just into /rap. There will be more projects comming as we move on and RAP is platform by itself and deserves its own subdirectory. I think the bundle *.rcp" still belongs into runtime subdirectory because RCP is our major platform. As we start to adopt e4 we will then add another subdirectory /e4 where we put the Riena stuff that is e4 specific.
>
> What do you think ? And what do others think ?
>
> christian
>
>
> Am 14.07.2010 um 21:53 schrieb Elias Volanakis:
>
>> Hi list,
>>
>> I think we could remove obsolete projects and maybe refactor the CVS
>> repo, to make it easy for newcomers to get started with the source.
>> Also helpful when using git, because you get everything all at once
>> (no .psf support). Details below.
>>
>> - Delete 14 obsolete projects: http://bugs.eclipse.org/319912
>>
>> - Move different things in CVS to their own subdirectory. This will
>> make obvious what is part of the Riena Runtime / what is optional /
>> examples / release engineering. Other RT projects such as ECF, RAP and
>> equinox have a similar approach. I propose the following example:
>>
>> /org.eclipse.riena
>> /releng - releng stuff, features
>> /runtime - Riena runtime + tests
>> /examples - Example / Samples / Demo clients / Snippets
>> /optional - Optional Ridgets (nebula), Riena on RAP
>> /tooling - Riena Toolbox, Wizard Templates
>>
>> Note that refactoring the repo will require a re-checkout from all
>> people on CVS. However we have so many unrelated projects thrown
>> together that the cleanup is worth it (IMHO). And I think since we are
>> after the release it may be a good time to do this.
>>
>> Feedback?
>>
>> Cheers,
>> Elias.
>>
>> --
>> Elias Volanakis | Technical Lead | http://eclipsesource.com
>> elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | @evolanakis
>> _______________________________________________
>> riena-dev mailing list
>> riena-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/riena-dev
>
>
> -------------------------------------------------------------
> compeople AG
> Untermainanlage 8
> 60329 Frankfurt/Main
> fon: +49 (0) 69 / 27 22 18 0
> fax: +49 (0) 69 / 27 22 18 22
> web: http://www.compeople.de/
>
> Vorstand: Jürgen Wiesmaier
> Aufsichtsratsvorsitzender: Christian Glanz
>
> Sitz der Gesellschaft: Frankfurt/Main
> Handelsregister Frankfurt HRB 56759
> Ust-Ident.-Nr: DE207665352
> -------------------------------------------------------------
>
> _______________________________________________
> riena-dev mailing list
> riena-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/riena-dev
>
--
Elias Volanakis | Technical Lead | http://eclipsesource.com
elias@xxxxxxxxxxxxxxxxx | +1 503 929 5537 | @evolanakis
