Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

SWT build still requires Java 11 #626

Closed
iloveeclipse opened this issue Apr 12, 2023 · 10 comments · Fixed by #633 or #978
Closed

SWT build still requires Java 11 #626

iloveeclipse opened this issue Apr 12, 2023 · 10 comments · Fixed by #633 or #978
Labels
help wanted Extra attention is needed

Comments

@iloveeclipse
Copy link
Member

iloveeclipse commented Apr 12, 2023

Nashorn JavaScript Engine was removed in Java 15, see https://openjdk.org/jeps/372

However, SWT build still uses it in ant file:
See

This has to be solved if we want to get rid of Java 11 in SWT.

Once that is done, we also can change Jenkinsfile

Beside supporting ant execution on 11, Jenkinsfile uses different JDK 11 versions also in other places, see this comment.
and following places:

iloveeclipse added a commit to iloveeclipse/eclipse.platform.swt that referenced this issue Apr 12, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See eclipse-platform#626

Fixes eclipse-platform#625
@mickaelistria
Copy link
Contributor

It's possible to use the java task instead; but we need to rework things a bit to avoid dereferencing the project in the code, but instead pass the properties we're willing to process. eg

<project default="blah">
	<target name="blah">
		<property name="tags"><![CDATA[
			a
			b
			c]]></property>
		<echo file="dummyTags.java">
			<![CDATA[
				public class lastTag { public static void main(String... args) {
					var tags = args[args.length - 1].split("\n");
					System.out.println(tags[tags.length - 1].strip());
				}}
			]]>
		</echo>
		<java fork="true" outputproperty="swt_tag" sourcefile="dummyTags.java">
			<arg value="${tags}"/>
		</java>
		<echo>${swt_tag}</echo>
	</target>
</project>

For the more complex one that sets multiple properties at once, the java block could output a key=value dictionary in a property and this property be loaded as properties in a property step.

@iloveeclipse iloveeclipse added the help wanted Extra attention is needed label Apr 12, 2023
iloveeclipse added a commit to iloveeclipse/eclipse.platform.swt that referenced this issue Apr 12, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See eclipse-platform#626

Fixes eclipse-platform#625
HannesWell pushed a commit to iloveeclipse/eclipse.platform.swt that referenced this issue Apr 12, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See eclipse-platform#626

Fixes eclipse-platform#625
@HannesWell
Copy link
Member

HannesWell commented Apr 12, 2023

My goal with #513 is to get rid of ANT as far as reasonable possible, which of course also includes to get rid of the java-script scripts in ANT tasks. For example with #613 one stage was already made ANT and javascript free. But it is a larger task I carry out step by step.

This has to be solved if we want to get rid of Java 11 in SWT.

Since these ANT/javascript script scripts are only used to perform the SWT natives build this is not completely correct. As described in #625 (comment) the Build and test stage of the SWT pipeline already uses Java-17 and we could leave the other parts at Java-11 for the moment.

iloveeclipse added a commit to iloveeclipse/eclipse.platform.swt that referenced this issue Apr 13, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See eclipse-platform#626

Fixes eclipse-platform#625
iloveeclipse added a commit that referenced this issue Apr 13, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See #626

Fixes #625
iloveeclipse added a commit to eclipse-platform/eclipse.platform.swt.binaries that referenced this issue Apr 13, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See eclipse-platform/eclipse.platform.swt#626

Fixes eclipse-platform/eclipse.platform.swt#625
iloveeclipse added a commit to eclipse-platform/eclipse.platform.swt.binaries that referenced this issue Apr 13, 2023
Note: there are still build files requiring Java 11 for execution
(Jenkinsfile and buildSWT.xml).

See eclipse-platform/eclipse.platform.swt#626

Fixes eclipse-platform/eclipse.platform.swt#625
@HannesWell
Copy link
Member

HannesWell commented Apr 13, 2023

I have analyzed in depth from which JDKs the headers are used:

  • linux.x86_64: /opt/tools/java/temurin/jdk-11/latest
  • linux.aarch64: /usr/lib/jvm/java-11-openjdk/
  • linux.ppc64le: /usr/lib/jvm/java-11-openjdk-11.0.15.0.10-3.el8.ppc64le
  • macosx.aarch64: /Library/Java/JavaVirtualMachines/temurin-17.jdk
  • macosx.x86_64: /Library/Java/JavaVirtualMachines/temurin-19.jdk
  • win32.x86_64: C:\Program Files\AdoptOpenJDK\jdk-11.0.11.9-hotspot

The mixture is coming from multiple discrepancies in the SWT-natives builds, which existed in the https://ci.eclipse.org/releng/view/SWT%20Natives jobs.

For Linux it is the expected mixture.

For Windows the environment variable from which the headers are included is name SWT_JAVA_HOME and without it defined the build.bat starts auto-searching.


CFLAGS = -O1 /WX /W4 -DNDEBUG -DUNICODE -D_UNICODE /c $(cflags) $(cvarsmt) $(CFLAGS) \
-DSWT_VERSION=$(maj_ver)$(min_ver) -DSWT_REVISION=$(rev) $(NATIVE_STATS) -DUSE_ASSEMBLER \
/I"$(SWT_JAVA_HOME)\include" /I"$(SWT_JAVA_HOME)\include\win32" /I.

For macos is it is more or less hard-coded to use JDK on the system path (as far as I understand the script):

if [ -d /System/Library/Frameworks/JavaVM.framework/Headers ]; then
export CFLAGS_JAVA_VM="-I /System/Library/Frameworks/JavaVM.framework/Headers"
else
export CFLAGS_JAVA_VM="-I $(/usr/libexec/java_home)/include -I $(/usr/libexec/java_home)/include/darwin"
fi

I downloaded the Java-17 JDKs for all of the mentioned platforms from Adoptium and compared their include folder (the one that contains the headers which are interesting for the SWT natives build. The comparison result was that for Java-17 the header files are equal per OS (linux, win, mac) regardless of the architecture. And the only difference between the OSs is a OS-specific subfolder containing the jni_md.h and jawt_md.h (and for Windows a bridge) with OS-specific content. The headers directly in the include folder are equal for all platforms.

grafik

This leads me to the conclusion that we only need one JDK respectively one set of headers per OS.

HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 13, 2023
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 13, 2023
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 16, 2023
@laeubi
Copy link
Contributor

laeubi commented Apr 16, 2023

I have already prototypes a way that is compatible with PDE/Eclipse + Tycho without the use of ANT but it would require

So if LFS is too complicated / no progress, one might probably reconsider the submodules as an intermediate solution... as soon as we have a combined repo (using whatever technique) I can try finish my prototype and open a PR... adding JDK headerfiles to the repo seems not a very good solution, even though the visible result of a headerfile should not differ between OS there is no guarantee.

@vogella
Copy link
Contributor

vogella commented Apr 19, 2023

Can this issue be closed? AFAIK SWT now requires Java 17.

@iloveeclipse
Copy link
Member Author

Can this issue be closed?

No, see bug description / comments.

AFAIK SWT now requires Java 17.

That's the point of the issue. We require Java 17 for runtime but still need Java 11 for build!

HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 22, 2023
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 23, 2023
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 24, 2023
Use headers and libs from minimal JustJ JDK and use SWT_JAVA_HOME
environment variable

Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 25, 2023
Use headers and libs from minimal JustJ JDK and use SWT_JAVA_HOME
environment variable

Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 25, 2023
Use headers and libs from minimal JustJ JDK and use SWT_JAVA_HOME
environment variable

Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 25, 2023
Use headers and libs from minimal JustJ JDK and specify the resource
location using the SWT_JAVA_HOME environment variable.
This allows to use another JDK as header/lib provider than the one
specified in the global JAVA_HOME variable.

Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 28, 2023
Use the C header files and shared native libraries from minimal JustJ
JDKs when building the SWT native binaries on specialized build
machines.

Always specify the location of the JDK providing the headers/libs using
the 'SWT_JAVA_HOME' environment variable.
This allows to use another JDK as the one specified in the global
JAVA_HOME variable.

When building the natives for the current platform via Maven set the
value of 'SWT_JAVA_HOME' to the location of the running JDK, if not set
externally.

Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 28, 2023
Use the C header files and shared native libraries from minimal JustJ
JDKs when building the SWT native binaries on specialized build
machines.

Always specify the location of the JDK providing the headers/libs using
the 'SWT_JAVA_HOME' environment variable.
This allows to use another JDK as the one specified in the global
JAVA_HOME variable.

When building the natives for the current platform via Maven set the
value of 'SWT_JAVA_HOME' to the location of the running JDK, if not set
externally.

Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Apr 28, 2023
Use the C header files and shared native libraries from minimal JustJ
JDKs when building the SWT native binaries on specialized build
machines.

Always specify the location of the JDK providing the headers/libs using
the 'SWT_JAVA_HOME' environment variable.
This allows to use another JDK as the one specified in the global
JAVA_HOME variable.

When building the natives for the current platform via Maven set the
value of 'SWT_JAVA_HOME' to the location of the running JDK, if not set
externally.

Fixes eclipse-platform#626
@HannesWell HannesWell reopened this May 2, 2023
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 12, 2024
to replace ANT tasks with JavaScript.
And stash native sources not-zipped to save the zip and unzip steps.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 12, 2024
to replace ANT tasks with JavaScript.
And stash native sources not-zipped to save the zip and unzip steps.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 12, 2024
to replace ANT tasks with JavaScript.
And stash native sources not-zipped to save the zip and unzip steps.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 12, 2024
to replace ANT tasks with JavaScript in Jenkins pipeline.
And stash native sources not-zipped to save the zip and unzip steps.

Furthermore move all remaining ANT tasks to run a native build in a
local Maven for the running platform completely to the
maven-antrun-plugin configuration.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 13, 2024
to replace ANT tasks with JavaScript in Jenkins pipeline.
And stash native sources not-zipped to save the zip and unzip steps.

Furthermore move all remaining ANT tasks to run a native build in a
local Maven for the running platform completely to the
maven-antrun-plugin configuration.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
in order to replace ANT tasks with JavaScript (which require Java-11) in
Jenkins pipeline.
Stash native sources not-zipped to save the zip and unzip steps.

Additionally move all remaining ANT tasks to run a native build in a
local Maven for the running platform completely to the
maven-antrun-plugin configuration.

Furthermore move declaration of tools to the common Jenkins pipeline
section to make them usable in all stages.
Since eclipse-platform#633
the JDK on the native-build-agent's PATH is not used anymore when
building the native binaries and thus it is not required anymore to keep
the PATH untouched.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
in order to replace ANT tasks with JavaScript (which require Java-11) in
Jenkins pipeline.
Stash native sources not-zipped to save the zip and unzip steps.

Additionally move all remaining ANT tasks to run a native build in a
local Maven for the running platform completely to the
maven-antrun-plugin configuration.

Furthermore move declaration of tools to the common Jenkins pipeline
section to make them usable in all stages.
Since eclipse-platform#633
the JDK on the native-build-agent's PATH is not used anymore when
building the native binaries and thus it is not required anymore to keep
the PATH untouched.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
in order to replace ANT tasks with JavaScript (which require Java-11) in
Jenkins pipeline.
Stash native sources not-zipped to save the zip and unzip steps.

Additionally move all remaining ANT tasks to run a native build in a
local Maven for the running platform completely to the
maven-antrun-plugin configuration.

Furthermore move declaration of tools to the common Jenkins pipeline
section to make them usable in all stages.
Since eclipse-platform#633
the JDK on the native-build-agent's PATH is not used anymore when
building the native binaries and thus it is not required anymore to keep
the PATH untouched.

Part of
- eclipse-platform#513
- eclipse-platform#626
HannesWell added a commit that referenced this issue Jan 14, 2024
in order to replace ANT tasks with JavaScript (which require Java-11) in
Jenkins pipeline.
Stash native sources not-zipped to save the zip and unzip steps.

Additionally move all remaining ANT tasks to run a native build in a
local Maven for the running platform completely to the
maven-antrun-plugin configuration.

Furthermore move declaration of tools to the common Jenkins pipeline
section to make them usable in all stages.
Since #633
the JDK on the native-build-agent's PATH is not used anymore when
building the native binaries and thus it is not required anymore to keep
the PATH untouched.

Part of
- #513
- #626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 14, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 16, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 16, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 16, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 16, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 17, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 17, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 17, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 17, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not useful anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit to HannesWell/eclipse.platform.swt that referenced this issue Jan 17, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not necessary anymore.

Part of eclipse-platform#513
Fixes eclipse-platform#626
HannesWell added a commit that referenced this issue Jan 17, 2024
This avoids the need for a Java-11 JRE to run Javascript in the pipeline
and moves the file changes and git actions into one common place, making
it simpler to understand.

Simplify the step to commit the binaries binaries by deleting all
existing native binaries in the repo before they are build and then just
committing all new, deleted and changed files.
Also skip version increment tasks that change nothing (i.e. the major-
and minor swt-version value are unchanged and thus the entire
version.txt is not updated in the automated pipeline.
Remove the 'check_fragment_libraries' task without replacement since it
is not necessary anymore.

Part of #513
Fixes #626
@HannesWell
Copy link
Member

HannesWell commented Jan 17, 2024

The build of SWT now doesn't use ANT-scripts anymore, only very few executions of the maven-antrun-plugin are left, but those don't require JavaScript and there is ot ANT script left in org.eclipse.swt.
All tasks encoded in the former scripts where either obsolete or have been migrated to Maven, the Jenkins pipeline (which uses Groovy) or to one JEP 330 single source Java script.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
help wanted Extra attention is needed
Projects
None yet
5 participants