Bug 80526 – Ebuild request: dev-java/jdtcore-3.0

• Status: RESOLVED FIXED
• Product: Gentoo Linux

[Description Karl Trygve Kalleberg (RETIRED) 2005-02-02 15:08:41 UTC]

As per thread on the mailing list.

[Comment 1 Scott Carr 2005-02-02 15:22:27 UTC]

If I created a seperate package that only builds jdtcore, could I put it on my server for inclusion in Gentoo?  I'll look over jdtcore plugin and see how easy this would be.

[Comment 2 Scott Carr 2005-02-03 21:45:42 UTC]

Created attachment 50305 [details]
jdtcore-3.0.1.ebuild (New Package)

jdtcore-3.0.1.tar.bz2 is currently stored on my server.  If you can think of a
better place to put it, let me know.  The build works as far as I can tell.

All that is in this package is the plugins/org.eclipse.jdt.core_3.0.1 folder
renamed to jdtcore-3.0.1.

[Comment 3 Karl Trygve Kalleberg (RETIRED) 2005-02-04 05:25:20 UTC]

This ebuild also suffers from a similar problem to that I mentioned in #71307:

[javac] /var/tmp/portage/jdtcore-3.0.1/work/jdtcore-3.0.1/antadapter/org/eclipse/jdt/core/CheckDebugAttributes.java:18: package org.apache.tools.ant does not exist
    [javac] import org.apache.tools.ant.BuildException;

I suspect that jdtcore must either be patched to use the regular ant directly, or we will have to include a jdtcore-specific ant in the jdtcore source tarball. 

I suggest you start with a patch setting javacFailOnError to true, and go from there: I've been fooled more than once about eclipse builds seeminly succeeding when hundreds of error messages are actually reported.

[Comment 4 Scott Carr 2005-02-04 06:58:14 UTC]

That just sucks.  Thanks for the info.  I'll work on it tonight.

[Comment 5 Scott Carr 2005-02-04 11:40:01 UTC]

Created attachment 50368 [details]
jdtcore-3.0.1.ebuild (javac fix)

I have modified the tar.bz2 to include all the dependencies for this project.
It will now use javacFailOnError by default, and I also created a new build.xml
to handle the build
of all the dependencies.

Let me know what you think.

[Comment 6 Scott Carr 2005-02-04 11:41:32 UTC]

Comment on attachment 50305 [details]
jdtcore-3.0.1.ebuild (New Package)

Obsoleting previous ebuild

[Comment 7 Karl Trygve Kalleberg (RETIRED) 2005-02-06 05:57:52 UTC]

We're getting closer. It still complains about a few missing packages: 

  [javac] /var/tmp/portage/jdtcore-3.0.1/work/jdtcore-3.0.1/model/org/eclipse/jdt/core/IJavaProject.java:21: package org.eclipse.core.resources does not exist
    [javac] import org.eclipse.core.resources.IProject;

And:

org.eclipse.core.runtime
org.eclipse.core.runtime.jobs


Yes, I redownloaded the tarball from yoursite just ~30mins ago. Excellent work so far!

[Comment 8 Scott Carr 2005-02-07 20:50:13 UTC]

Karl, can you run:

emerge jdtcore > build.log

and email it to me, or attach it.  I am not seeing any of these errors, and I
do not have anything in my classpath.

Thanks

[Comment 9 Scott Carr 2005-02-12 13:58:12 UTC]

Created attachment 51082 [details]
eclipse-jdtcore-3.0.1.ebuild

To run this, you will need to rm the previous eclipse-jdtcore-3.0.1.tar.bz2
from distfiles if it currently exists.	I had to change some pathing in the
build.xml for the ebuild to work.

[Comment 10 Karl Trygve Kalleberg (RETIRED) 2005-02-12 14:53:44 UTC]

Added to the experiemental tree.

[Comment 11 Jan Brinkmann (RETIRED) 2005-02-14 09:00:54 UTC]

reopening this one because we need jdtcore in the main tree.

[Comment 12 Scott Carr 2005-04-20 19:29:17 UTC]

How are things going on this?

Is there anything more I need to do?  Are we waiting on a number of people to say it works?

[Comment 13 Karl Trygve Kalleberg (RETIRED) 2005-09-04 11:14:09 UTC]

Inspired by this ebuild and its tarball, I have split ecj into its own package,
dev-java/eclipse-ecj. We don't have any ebuilds pending (afaik) that need the
full jdtcore, so I'm inclined to close this bug as FIXED (the derived
eclipse-ecj preempts it).

Please reopen this bug if it turns out we really need jdtcore itself.