|
Re: Problem building oomph [message #1780994 is a reply to message #1780979] |
Wed, 31 January 2018 06:26 |
Ed Merks Messages: 33264 Registered: July 2009 |
Senior Member |
|
|
In my local modified version of the launch configuration (to build only the Window's 64 bit stuff) I have these -Dbuild.id=Local
-Dgit.commit=Unknown
-DskipTests=true
-Denv=win64
-DDtycho.debug.resolver=true
-DGENERATE_SOURCE=true
-DX
clean
verify You are missing -DGENERATE_SOURCE=true so they're not generated and so references to source features in the site.xml can't be resolved.
Because it's now mandatory to generate source we should move this build step from a conditionally activated profile to the root of the poml.xml in /org.eclipse.oomph.parent/features/pom.xml and/org.eclipse.oomph.parent/plugins/pom.xml.
We can also use the trick I learned with converting EMF's build to Maven Tycho so that /org.eclipse.oomph.all-feature has a p2.inf with a synthetic dependency on the it's corresponding source feature:requires.0.namespace=org.eclipse.equinox.p2.iu
requires.0.name=org.eclipse.oomph.all.source.feature.group
requires.0.range=[$version$,$version$]
requires.0.greedy=true
requires.0.optional=true The advantage of this approach is that the source feature itself is not categorized in the site as something to install. Sources are really only useful in the target platform.
I've committed these changes:
http://git.eclipse.org/c/oomph/org.eclipse.oomph.git/commit/?id=361a9986cbdf6fa722945fb5b0960826d3af75cf
So if you do a pull, your Maven build should work without the -DGENERATE_SOURCE=true option.
Ed Merks
Professional Support: https://www.macromodeling.com/
|
|
|
Powered by
FUDForum. Page generated in 0.03315 seconds