pom file errors after SWT workspace is setup in Ubuntu using oomph

[lathapatil]

I have set up an SWT workspace on the latest version of Ubuntu Linux and am able to run the Eclipse application locally after following the steps mentioned in https://wiki.eclipse.org/SWT/Devel/Gtk/Dev_guide.

Now I'm attempting to modify the OS.java file and compile the new C code, following the steps outlined here but the Ant build scripts are no longer present in the workspace, and I'm attempting to trace the chain here

But the POM files in the workspace are having issues, and I'm wondering if it's a workspace setup problem. I haven't made any changes to the POM file.

[merks]

I don't see that error...

I think the direct parent is fine, but the <relativePath>../eclipse-platform-parent</relativePath> it doesn't like

I believe this error remains only as long as the editor is open...

The problem is that the overall pom structure assumes the repo is checked out as a submodule of

https://github.com/eclipse-platform/eclipse.platform.releng.aggregator

So it expects that eclipse-platform-parent will be a sibling of the SWT repository root location:

[lathapatil]

Closing the POM editor resolved the issue today, but that wasn't the case when I was attempting this a couple of days ago.
Thanks for the tip.

Now I am proceeding with my Maven command to compile the new C code and copy the new libraries to the appropriate fragment

/swt-master/git/eclipse.platform.swt/binaries$ mvn clean process-resources -Dnative=gtk.linux.x86_64 -DskipTests

But I am encountering errors. Could it be a proxy issue? I am unable to locate the mentioned .pom file at the specified location.

Original error: Could not transfer artifact org.eclipse.tycho:tycho-source-plugin:pom:4.0.6 from/to tycho-snapshots (https://repo.eclipse.org/content/repositories/tycho-snapshots/): HTTP proxy server authentication failed for https://repo.eclipse.org/content/repositories/tycho-snapshots/org/eclipse/tycho/tycho-source-plugin/4.0.6/tycho-source-plugin-4.0.6.pom 407 Proxy Authentication Required

When clicking on the .pom file link, I receive the following information:
Retrieval of /org/eclipse/tycho/tycho-source-plugin/4.0.6/tycho-source-plugin-4.0.6.pom from M2Repository(id=tycho-snapshots) is forbidden by repository policy SNAPSHOT.

[merks]

Tycho 4.0.6 is released so it's not present here:

https://repo.eclipse.org/content/repositories/tycho-snapshots/org/eclipse/tycho/tycho-source-plugin/

[laeubi]

@lathapatil If you are using a special maven setup you maybe need to configure the settings.xml or maybe use a different one (-s option) and configure them on CLI and in the IDE.

[lathapatil]

From eclipse.platform.swt/bundles/org.eclipse.swt/Readme.Linux.md, I understand that I can either run the Build-SWT-native-binaries-for-running-platform Maven launch configuration or the build.sh script in the binaries/org.eclipse.swt.gtk.linux.${arch}/bin/library directory.

Will running build.sh also compile changed C files and copy the new libraries (*.so files) to the appropriate fragment?

If that is the case, do I no longer need to use Maven?

[HeikoKlare]

In case you specify the argument install when executing build.sh, it will also copy the generated *.so files:

eclipse.platform.swt/bundles/org.eclipse.swt/Eclipse SWT PI/gtk/library/build.sh

Line 32 in d98c128

install - copy *.so libraries to binary repository.

The Maven build also just executes the build.sh with according arguments. In addition, it defines some environment variables but if unspecified, most (if not all) of them are also filled with reasonable values by the build.sh.

eclipse.platform.swt/binaries/pom.xml

Lines 143 to 150 in d98c128

	<exec dir="${build_dir}" executable="sh" failonerror="true">
	<arg line="build.sh"/>
	<env key="SWT_JAVA_HOME" value="${SWT_JAVA_HOME}"/>
	<env key="OUTPUT_DIR" value="${project.basedir}"/>
	<env key="GTK_VERSION" value="${gtk_version}"/>
	<env key="MODEL" value="${arch}"/>
	<arg line="install clean"/>
	</exec>

[lathapatil]

@HeikoKlare Thanks for the confirmation .
I can execute build.sh its always successful except that OUTPUT_DIR path should be updated manually from OUTPUT_DIR=../../../../../eclipse.platform.swt/bundles/org.eclipse.swt.gtk.${SWT_OS}.${SWT_ARCH} to OUTPUT_DIR=../../../../../eclipse.platform.swt/binaries/org.eclipse.swt.gtk.${SWT_OS}.${SWT_ARCH}

However, I still haven't been able to resolve or figure out how to do it using Maven. If you've already attempted to build it using Maven, could you please share the steps and commands with me?

[HeikoKlare]

I build the binaries via Maven from command line. A prerequisite for building the binaries is to have an swtBuildQualifier.txt in bundles\org.eclipse.swt\target, which is created by simply running an ordinary Maven build on the complete SWT repository (or you can probably also create it manually). Then you can execute the following within the folder of the fragment you want to build:

mvn clean process-resources -Dnative=${ws}.${os}.${arch} -DskipTests

So in your case it should be mvn clean process-resources -Dnative=gtk.linux.x86_64 -DskipTests in the org.eclipse.swt.gtk.linux.x86_64 fragment folder.

You can also find the description how to build the binaries here: #973 (comment)

I can execute build.sh its always successful except that OUTPUT_DIR path should be updated manually from OUTPUT_DIR=../../../../../eclipse.platform.swt/bundles/org.eclipse.swt.gtk.${SWT_OS}.${SWT_ARCH} to OUTPUT_DIR=../../../../../eclipse.platform.swt/binaries/org.eclipse.swt.gtk.${SWT_OS}.${SWT_ARCH}

True, the default output path is outdated. I was not probably not detected yet since the Maven build overwites it. Do you want to provide a PR to correct the path?

[lathapatil]

This really helped to resolve my issue with building SWT native binaries using the Maven approach. Thanks for the detailed steps.

A prerequisite for building the binaries is to have an swtBuildQualifier.txt in bundles\org.eclipse.swt\target, which is created by simply running an ordinary Maven build on the complete SWT repository (or you can probably also create it manually).

If this step is mandatory, then it also has to be documented somewhere.

True, the default output path is outdated. I was not probably not detected yet since the Maven build overwites it. Do you want to provide a PR to correct the path?

Sure , I can do that.