Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cbi-dev] changing package line-up

Hi Everyone,

Those are very good points about dependencies and reiterate that things are done the way they are done today for very good reasons.

I want to be clear, in case it wasn't completely  clear already, that this exercise was intended to be my own personal build & package rather than the official SDK package. This is primarily to learn & demonstrate how easy it is to do so.

I am not proposing a change to the official SDK package in this forum.

Andrew

On 12/04/2012 09:21 AM, Mickael Istria wrote:
On 12/04/2012 03:16 PM, Aleksandar Kurtakov wrote:
Lets try to keep the CBI platform build as simple as possible. I really like the idea of removing CVS but adding egit opens the door for many more circular dependencies which is not a good idea.
If someone wants to build egit/jgit together with the platform he can always create a new multimodule maven project aka:
* my-super-eclipse
    * platform-agregator-build
    * jgit
    * egit
    * mylyn
    * whatever else you want that builds using tycho

I think that's already what happens with the EPP packages: ship a "super-eclipse" for main use-cases.
I'm also +1 from removing CVS from default IDE and making it a more independent component that is not shipped by default along with SDK.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets


_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev



Back to the top