Eclipse Community Forums: Objectteams » Create ecotj jar from command line / workspace

Home » Language IDEs » Objectteams » Create ecotj jar from command line / workspace

Create ecotj jar from command line / workspace [message #1758145]

Thu, 23 March 2017 16:30

Eclipse User

Hi Stephan,

I want to create the ecotj.jar from current head from command line or workspace. I am using Oxygen M6 and working on master.

I already found the ant script org.eclipse.jdt.core/scripts/export-ecj.xml which has an export target. When I run "ant -f export-ecj.xml export" it will create a folder ecj-export with holds ecotj.jar. However, when extracting the jar I see that it does not hold any source code.

Is there any prerequisite I did not read or found? In the how to it says everything I did. bug 507370 makes me feel that it is not so easy to fully build the jar.

Thank you very much!

[Updated on: Fri, 24 March 2017 00:48] by Moderator

Re: Create ecotj jar from command line / workspace [message #1758195 is a reply to message #1758145]

Fri, 24 March 2017 10:39

Eclipse User

Okay, got it working. The script is not general enough. On my Mac I had to change some things to make it work.

<property name="compiler.apt" value="${build.root.dir}/${jdt.compiler.apt}"/>
...
<property name="compiler.tool" value="${build.root.dir}/${jdt.compiler.tool}"/>

Where it was before

<property name="compiler.apt" value="${build.root.dir}/eclipse/${jdt.compiler.apt}"/>
...
<property name="compiler.tool" value="${build.root.dir}/eclipse/plugins/${jdt.compiler.tool}"/>

and my arguments I give to the ant script are

-Dbuild.root.dir="/Applications/Eclipse Oxygen.app/Contents/Eclipse/plugins"
-Djdt.compiler.apt="org.eclipse.jdt.compiler.apt_1.3.0.v20170110-0830.jar"
-Djdt.compiler.tool="org.eclipse.jdt.compiler.tool_1.2.0.v20161205-0823.jar"

Maybe one could further improve this in the future, as slight changes to the versions will make the build process fail.

[Updated on: Fri, 24 March 2017 10:49] by Moderator

Re: Create ecotj jar from command line / workspace [message #1758451 is a reply to message #1758195]

Tue, 28 March 2017 15:15

Eclipse User

Hi Lars,

I'm glad you figured it out.

I haven't used those files for export from the IDE in a long time.
The scripts are adjusted to the directory structure as it exists during production builds.
The good news is: those scripts are indeed used on a regular bases, so no danger for them to silently decay.

In particular on https://hudson.eclipse.org/objectteams/job/buildAndTest/ (not sure this is publically visible) you'd find links to ecotj.jar (plus the corresponding src jar) of each build.

As for the version qualifiers, those are part of the process for adopting a new base (Eclipse SDK) to build against. A jenkins job exists to extract versions from the SDK: https://hudson.eclipse.org/objectteams/job/extractVersions/ the results of which will be stored in /releng/build-scripts/build/run.properties

Since production builds are working OK in this way, I'm not planning to change anything. Hope that's OK.
Stephan

Previous Topic:	eclipse neon product does not load new weaver
Next Topic:	OTDT in Neon.3

Goto Forum:

-=] Back to Top [=-

Current Time: Wed Jul 23 14:25:48 EDT 2025

.:: Contact :: Home ::.

Breadcrumbs

Sign up to our Newsletter