Comments on: Improved Target Platform Management, Eclipse Galileo Feature #3 http://eclipsesource.com/blogs/2009/06/22/eclipse-galileo-feature-top-10-list-number-3/ Eclipse Equinox OSGi Wed, 16 May 2012 08:22:45 +0000 hourly 1 http://wordpress.org/?v=3.3.2 By: Ian Bull http://eclipsesource.com/blogs/2009/06/22/eclipse-galileo-feature-top-10-list-number-3/comment-page-1/#comment-1839 Ian Bull Wed, 24 Jun 2009 16:30:56 +0000 http://eclipsesource.com/blogs/?p=1979#comment-1839 Maarte, Very good points. This feature was released right at the end of the 3.5 cycle so I would look for more exciting things around target management in Eclipse 3.6. We can't make Eclipse perfect or we would all be out of a job ;). Maarte,

Very good points. This feature was released right at the end of the 3.5 cycle so I would look for more exciting things around target management in Eclipse 3.6. We can’t make Eclipse perfect or we would all be out of a job ;) .

]]> By: Maarte Meijer http://eclipsesource.com/blogs/2009/06/22/eclipse-galileo-feature-top-10-list-number-3/comment-page-1/#comment-1824 Maarte Meijer Wed, 24 Jun 2009 04:24:31 +0000 http://eclipsesource.com/blogs/?p=1979#comment-1824 I fully agree that this is a top 3 feature but it is not complete yet! Managing libraries can be a hard and error prone process to enforce in large development teams. When you take this new target provisioning as the abstract frontend to your SCM and CI server, you can set your target to include a specific BUILT and TESTED branch and release or HEAD of some component some one else is working on, then you don't check out into your workspace, you checkout into your target. The only thing in your workspace is the code you are working on yourself, and none of the dependencies! Certainly raises the level of abstraction again! So where is the p2 target like frontend to a Bundle Integration Server so we can reduce the number of files in workspace to the ones we must work on. I fully agree that this is a top 3 feature but it is not complete yet! Managing libraries can be a hard and error prone process to enforce in large development teams. When you take this new target provisioning as the abstract frontend to your SCM and CI server, you can set your target to include a specific BUILT and TESTED branch and release or HEAD of some component some one else is working on, then you don’t check out into your workspace, you checkout into your target. The only thing in your workspace is the code you are working on yourself, and none of the dependencies!
Certainly raises the level of abstraction again!
So where is the p2 target like frontend to a Bundle Integration Server so we can reduce the number of files in workspace to the ones we must work on.

]]> By: Matthias Treitler http://eclipsesource.com/blogs/2009/06/22/eclipse-galileo-feature-top-10-list-number-3/comment-page-1/#comment-1811 Matthias Treitler Tue, 23 Jun 2009 08:36:02 +0000 http://eclipsesource.com/blogs/?p=1979#comment-1811 The enhancements sound really good. I am curious to see how these improvements will enhance the development of Eclipse RCP applications. The enhancements sound really good. I am curious to see how these improvements will enhance the development of Eclipse RCP applications.

]]>