| Summary: | Generate source tarball for EMF as used by e4 | ||
|---|---|---|---|
| Product: | [Tools] Linux Tools | Reporter: | Andrew Overholt <overholt> |
| Component: | eclipse-build | Assignee: | Krzysztof Daniel <krzysztof.daniel> |
| Status: | RESOLVED FIXED | QA Contact: | |
| Severity: | normal | ||
| Priority: | P3 | CC: | krzysztof.daniel, swagiaal |
| Version: | unspecified | ||
| Target Milestone: | 1.0 | ||
| Hardware: | PC | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Bug Depends on: | 351712, 352903 | ||
| Bug Blocks: | 350248 | ||
|
Description
Andrew Overholt
I've put a temporary tarball up here: http://fedorapeople.org/~overholt/emfFore4-2.7.0-src.tar.bz2 We may just be able to use git snapshots (maybe even the tarballs generated from git.eclipse.org on tag pages). I put the necessary emf bundles into e4 tarball - emf got actually promoted to platform code in 4.2. http://download.eclipse.org/technology/linuxtools/eclipse-build/4.2.x/ (In reply to comment #3) > emf got actually promoted to platform code in 4.2. Do you mean that it's at the same +0 level? Good question. I had in mind the stack change, which is in 3.x: osgi + jface sdk emf and in 4.x: osgi + jface emf sdk But the fact that EMF is still +1, while the depending e4 sdk is +0 looks weird. (In reply to comment #5) > > But the fact that EMF is still +1, while the depending e4 sdk is +0 looks > weird. EMF does their build in 2 parts now. Base is +0 (has the most stable runtime core of EMF, like emf.common, emf.ecore, etc). The rest of the core is still +1 PW Thanks for the info :) |