harmony-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ivan Volosyuk" <ivan.volos...@gmail.com>
Subject Re: svn commit: r416738 - /incubator/harmony/enhanced/drlvm/trunk/vm/vmcore/src/init/bootclasspath.properties
Date Thu, 29 Jun 2006 09:33:59 GMT
On 6/29/06, Geir Magnusson Jr <geir@pobox.com> wrote:
> Ivan Volosyuk wrote:
> > Geir,
> >
> > I am working on the patch. There is almost no problem, except that
> > DRLVM builds its own modified version of eclipse plugin. The plugin
> > requires eclipse for its build.
> > I see that the same plugin exists in
> > enhanced/tools/eclipse/org.apache.harmony.eclipse.jdt.launching.
> > I think:
> >  - all modifications to the plugin should go to this directory.
> >  - drlvm should not build eclipse plugin itself, it should be built
> > as part of tools.
> >
> > Correct?
> I think so.  let me ask... why do we *need* the eclipse plugin to build,
> and even more important, why must it be modified?

The purpose of modifications was AFAIK to make it compactible with the
name of main executable: 'ij.exe'. It looks that there were also a few
bug fixes.

As for building, the tools package seems not to have own build system.
The plugin is quite useful for complex testing scenarious: start
eclipse, create and run java project from it. So, the question would
be, how one could build plugin from tools package? I'm also thinking
about snapshot releases of the tools.

Btw, I've already created the patch (H-698) removing eclipse build
dependency for drlvm. Eclipse compiler (from classlib's depends) can
still be used:
export CLASSPATH=..somewhere../classlib/depends/jars/ecj...jar
build.sh -Dbuild.compiler=org.eclipse.jdt.core.JDTCompilerAdapter

Intel Middleware Products Division

Terms of use : http://incubator.apache.org/harmony/mailing.html
To unsubscribe, e-mail: harmony-dev-unsubscribe@incubator.apache.org
For additional commands, e-mail: harmony-dev-help@incubator.apache.org

View raw message