Re: [cbi-dev] Bundles that may be improperly/incorrectly build with Tych

[Krzysztof Daniel <kdaniel@xxxxxxxxxx>]

On Tue, 2012-07-17 at 06:32 -0400, Igor Fedorenko wrote:
> I was asked to help with #2 at end of last summer and I believe we
> made
> major progress already. 

I do not negate that :-). The fact that I'm able to build Eclipse in
less than 15 minutes from my first checkout is a big success.


I'm worried about (from the list of files in my previous emails):
* jdt updating binary jars accross the bundle boundaries (if it is not
used, then I'm fine, but the code says it is used). IMO, major
refactoring should happen here either to merge those bundles, or to
split them to avoid circular dependencies (current case: A depends B, B
is build first, A is built and updates B artifacts). [1]
* jdt compiling internal jars [2]
* custom operations which do not really have maven counterpart, like
indexing documentation (all bundles matching org.eclipse.*doc*).
* Unpacking and repacking sources embedded as zips [3]?


I think those three issues shows all the variety of problems that are
yet to be solved. If only I knew the way to solve them without reusing
callbacks by maven-ant-runner, I'd stop complaining ;-).


Just do not get me wrong - I am really interested in getting things
done, as CBI is supposed to replace eclipse-build in linuxtools. I just
believe there is no justification for heavy project refactoring. I'd
rather provide integration with customBuildCallbacks and then let people
slowly migrate to the 'get it right' approach.


[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=385154
[2]
http://git.eclipse.org/c/cbi/eclipse.jdt.ui.git/tree/org.eclipse.jdt.ui/customBuildCallbacks.xml
[3]
http://git.eclipse.org/c/cbi/rt.equinox.framework.git/tree/bundles/org.eclipse.osgi.util/customBuildCallbacks.xml
-- 
Krzysztof Daniel <kdaniel@xxxxxxxxxx>
Red Hat