Home » Eclipse Projects » Eclipse Platform » Why can't Eclipse Target Editor read local p2 repo? (Target Editor harmful to platform definition for Tycho bulids)
| Why can't Eclipse Target Editor read local p2 repo? [message #1237492] |
Wed, 29 January 2014 21:16  |
 Ed Gow
Messages: 8
Registered: July 2009 |
Junior Member |
|
|
I have a set of plugins that I have been using as part of my target platform in a Tycho build for several years. To do this I turn it into a local p2 repo using the FeaturesAndBundlesPublisher in my Eclipse installation, as required by Tycho. If I try to use the Eclipse Target Platform Editor to create the build.target file for my Tycho build then it fails to read the F&BP p2 repo and, adding injury to insult, deletes all of the <unit lines for that repo. Because p2 repos are basically unusable by anything except the eclipse update site tooling, this forces repeated breaking of the build.target file by that tooling every time any other site content is edited.
I've seen this same behavior on both Kepler and Indigo. I've checked that the artifacts.xml and content.xml in the p2 repo look OK. I've tried every command line switch setting that the F&BP tool offers. I posted the problem to the p2 forum here http://www.eclipse.org/forums/index.php/t/637742/ and got zero replies over the course of two weeks.
I see this as a fairly severe problem for Eclipse RCP as a platform for serious applications. Good development practice dictates 1) using a defined target platform and 2) doing continuous integration and automated headless builds. At present, Tycho seems to be the only game in town for doing automated headless production builds of RCP applications. If the Eclipse tooling not only does not support defining target platforms for Tycho builds, but actually breaks them every time it touches them, then what is a serious development organization to think?
The e4 platform is an elegant and solid base for future application development. The only real reason to not use it is, IMHO, the extremely troublesome, sometimes non functional, build tooling. For the sake of the Eclipse platform, as well as for my selfish interest in getting my own build working, can someone please help me out with this.
|
|
|
| Re: Why can't Eclipse Target Editor read local p2 repo? [message #1237738 is a reply to message #1237492] |
Thu, 30 January 2014 13:13  |
|
On 29/01/2014 22:16, Ed Gow wrote:
> I have a set of plugins that I have been using as part of my target
> platform in a Tycho build for several years. To do this I turn it into a
> local p2 repo using the FeaturesAndBundlesPublisher in my Eclipse
> installation, as required by Tycho. If I try to use the Eclipse Target
> Platform Editor to create the build.target file for my Tycho build then
> it fails to read the F&BP p2 repo and, adding injury to insult, deletes
> all of the <unit lines for that repo. Because p2 repos are basically
> unusable by anything except the eclipse update site tooling, this forces
> repeated breaking of the build.target file by that tooling every time
> any other site content is edited.
>
> I've seen this same behavior on both Kepler and Indigo. I've checked
> that the artifacts.xml and content.xml in the p2 repo look OK. I've
> tried every command line switch setting that the F&BP tool offers. I
> posted the problem to the p2 forum here
> http://www.eclipse.org/forums/index.php/t/637742/ and got zero replies
> over the course of two weeks.
> I see this as a fairly severe problem for Eclipse RCP as a platform for
> serious applications. Good development practice dictates 1) using a
> defined target platform and 2) doing continuous integration and
> automated headless builds. At present, Tycho seems to be the only game
> in town for doing automated headless production builds of RCP
> applications. If the Eclipse tooling not only does not support defining
I have experienced many problems with the Eclipse Target Platform editor
myself, and I stopped using it; if I really have to define a .target
file I almost always edit it by hand, and then load it form the Target
preference page. With that respect, can you load such target from the
Target preference page (i.e., not using the target definition editor)?
Just a small addition, I've been using for some years the "other game in
town" for headless builds: Buckminster, and I'm still using it for every
Eclipse project (and RCP product) I develop, without problems.
Hope this helps
Lorenzo
--
Lorenzo Bettini, PhD in Computer Science, DI, Univ. Torino
HOME: http://www.lorenzobettini.it
Xtext Book:
http://www.packtpub.com/implementing-domain-specific-languages-with-xtext-and-xtend/book
HOME: http://www.lorenzobettini.it
TDD Book: https://leanpub.com/tdd-buildautomation-ci
Xtext Book: https://www.packtpub.com/application-development/implementing-domain-specific-languages-xtext-and-xtend-second-edition
|
|
| | | | | |
Goto Forum:
Current Time: Thu Apr 25 13:22:56 GMT 2024
Powered by FUDForum. Page generated in 0.03309 seconds |
] 
Search
Help
Register
Login
Home
