|
|
|
| Re: Oomph headless [message #1781236 is a reply to message #1781233] |
Sun, 04 February 2018 05:49   |
 Ed Merks
Messages: 33140
Registered: July 2009 |
Senior Member |
|
|
No project at Eclipse does a build that replicates their workspace development environment. The development environment uses JDT to compile the sources in the workspace against the binaries in the target platform, the build job uses Maven POMs to determine what to build and uses javac to compile Java sources. So no project ever guarantees that their development environment creates exactly the same artifacts as their build job because it definitely doesn't. But if things are well designed, you can replicate the build job locally with the External Tools Configurations that launches a Maven Tycho build. That will do quite a bit more things than you do in your development environment, e.g., it builds bundle jars, whereas JDT just populates the bin folder, and it typically builds an update site, which you don't generally need at development time, and on a real build server, it signs the jars.
An important driver for Tycho builds is often the *.target file, which in the case of Oomph (and with Targlets in general), we generate a *.target as a side effect of resolving the target platform. So that ensures that the build job compiles against what we're also using in our development environment.
It makes no sense to generate a build from the setup. The build is driven by what's in the POMs and that's not determined by the setup description. The m2e project supports POM generation for projects in the development workspace.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03206 seconds
] 
Search
Help
Register
Login
Home
