[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[eclipselink-dev] Attention: planned cut-over to use Tycho for Build.
- From: Eric Gwin <eric.gwin@xxxxxxxxxx>
- Date: Thu, 29 Sep 2011 14:54:53 -0400
- Delivered-to: email@example.com
- Organization: Oracle Corporation
- User-agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:220.127.116.11) Gecko/20110414 Lightning/1.0b2 OracleBeehiveExtension/18.104.22.168-OracleInternal ObetStats/LAFCATCAF_1294839879169-914923201 Thunderbird/3.1.10
Once again I am sending out notification of a large change in the build infrastructure for EclipseLink.
As many of you are aware, we have for several years been creating OSGi bundles to ship with Eclipse, in addition to the standard Java jars we bundle in our installer. Initially, a large hurdle had been a lack of expertise in creating OSGi bundles, another has been insuring our bundles are compatible with several OSGi platforms. To those ends we have relied on tooling to generate the OSGi manifests after the bundles were compiled.
This approach insured we maintained OSGi compliant manifests with little need for hands-on development intervention. However there were still problems with compatibility across platforms, and impact on development and testing processes. With standardized OSGi testing established we are in a position to remove the crutch of an automated tool.
To that end, I have been working on migrating to the use of Tycho to build our OSGi bundles based upon the checked-in Manifest files used by development. The initial proof-of-concept is complete, and the initial changes have been made...
The next round of changes, scheduled for October 7, will complete the switch-over to Tycho, and those changes will have several impacts upon the development team. Therefore, I have prepared a wiki to inform you of the changes you can expect, and the reasons for them. Please review, and let me know if you have any questions or concerns: