|
|
|
|
| Re: Contributing to the Platform/UI fails with missing org.apache.batik.i18n [message #1782432 is a reply to message #1782392] |
Fri, 23 February 2018 12:41   |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
I'm not sure how this is related to a thread about Tycho production builds versus headless provisioning of a development environment. Oomph was created to automate the setup of a development environment. It is not created to help do production builds and production builds are the not result that the development environment produces.
As an example of how Oomph ought to work for each project: before I went on my current trip, I got out my old machine (that if someone stole it I wouldn't die), deleted my "sandbox" folder and created two fresh new development environments for EMF/XSD and Oomph. In each of those development environments, there is an external tools launcher that will do a Maven Tycho build locally, producing exactly what the product build job does. This is particular convenient for both projects, because for Oomph I can test how installations are created from update sites of the latest build. For EMF, I can change the generated, do the build, install it into the IDE itself, and regenerate other models...
If the developers of the platform team actually used and maintained their setups, it would also be this trivially easy for any every contributor to duplicate what the developers are doing. But as you see, no response on the Bugzilla, and no real help here on the forum. I guess someone is hoping that I'll personally maintain all setups for all projects at Eclipse, via numerous Gerrit contributions to a plethora of repositories, as if that were scalable...
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
| Re: Contributing to the Platform/UI fails with missing org.apache.batik.i18n [message #1782511 is a reply to message #1782509] |
Sun, 25 February 2018 06:19 |
Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
Impossible is a strong word, I don't recall using it. In there past there was PDE build, but that is abandoned. There was also Buckminster, but that too is essentially abandoned. Those more closely emulated what happens in the IDE. But now there is CBI (Common Build Infrastructure) and Tycho; EMF's build was migrated from Buckminster to Tycho just last month...
In any case, no matter what you might "require"---which I pretty much replace with "desire" because it's clear that everyone else gets by without this requirement being addressed---I can assure you that no one is going to see your requirement as something in which they will invest effort, so you'll have to implement that yourself.
Without knowing what "information" Tycho needs, you assume that Oomph can generate it. Assembling the source (cloning) is not even done by Tycho, it's done by Hudson directly. Managing dependencies in Tycho is done via what's in the pom.xmls, optionally with the help of a *.target file, which Oomph can generate to match what's computed during Targlet resolution.
So while you should reasonably expect to be able to reproduce the development environment setup the developers use for development of Oxygen and Photon (so you can contribute bug fixed for example) and you should expect to be able to replicate the production builds used to produce the deliverables (so you could build you own distro with bug fixes), you are misguided if you expect CBI and Tycho will change conform to your requirement that the development IDE's builds and production builds be one and the same.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
Powered by
FUDForum. Page generated in 0.03622 seconds
] 
Search
Help
Register
Login
Home
