Re: [eclipse-dev] A new build is being done as we speak

[Nick_Edgar@xxxxxxx]

Please file a bug report against Platform - Ant.





"Emerson Cargnin - MSA" <emersonc@xxxxxxxxxxxxxx>
Sent by: eclipse-dev-admin@xxxxxxxxxxx
06/04/02 04:51 PM
Please respond to eclipse-dev

 
        To:     <eclipse-dev@xxxxxxxxxxx>
        cc: 
        Subject:        Re: [eclipse-dev] A new build is being done as we speak


When trying to build my program with ant inside Eclipse (M5 didn't work) 
it
gave an internal error with no message. I saw it used ant 1.4.1 and I was
using ant 1.5b1. So i set eclipse ant to use ant 1.5b1. When tring to run 
my
target I got the same error I had in M5. Anyone knows how to solve this???

Here goes the error :

ed dir: C:\eclipse\workspace\Cobranca\build\j2ee\META-INF
Created dir: C:\eclipse\workspace\Cobranca\dist
Created dir: C:\eclipse\workspace\Cobranca\build\ejb\classes
Created dir: C:\eclipse\workspace\Cobranca\build\ejb\generic-ejb
java.lang.NoClassDefFoundError: com/sun/javadoc/Doc
at java.lang.Class.getDeclaredConstructors0(Native Method)
at java.lang.Class.privateGetDeclaredConstructors(Class.java:1576)
at java.lang.Class.getConstructor0(Class.java:1748)
at java.lang.Class.getConstructor(Class.java:990)
at
org.apache.tools.ant.IntrospectionHelper.<init>(IntrospectionHelper.java:328
)
at
org.apache.tools.ant.IntrospectionHelper.getHelper(IntrospectionHelper.java:
384)
at
org.apache.tools.ant.UnknownElement.handleChildren(UnknownElement.java:206)
at
org.apache.tools.ant.UnknownElement.maybeConfigure(UnknownElement.java:122)
at org.apache.tools.ant.Task.perform(Task.java:312)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:334)
at org.apache.tools.ant.Project.executeTarget(Project.java:1216)
at org.apache.tools.ant.Project.executeTargets(Project.java:1160)
at
org.eclipse.ant.internal.core.ant.InternalAntRunner.run(InternalAntRunner.ja
va:269)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39
)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl
.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:155)
at
org.eclipse.ui.externaltools.internal.core.AntFileRunner.execute(AntFileRunn
er.java:54)
at
org.eclipse.ui.externaltools.internal.core.DefaultRunnerContext.executeRunne
r(DefaultRunnerContext.java:320)
at
org.eclipse.ui.externaltools.internal.core.DefaultRunnerContext.run(DefaultR
unnerContext.java:370)
at
org.eclipse.ui.externaltools.internal.ui.AntLaunchWizard$1.run(AntLaunchWiza
rd.java:116)
at
org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext
.java:98)
Build exception: java.lang.NoClassDefFoundError: com/sun/javadoc/Doc
----- Original Message -----
From: Sonia_Dimitrov@xxxxxxx
To: eclipse-dev@xxxxxxxxxxx
Sent: Sunday, June 02, 2002 12:42 PM
Subject: Re: [eclipse-dev] A new build is being done as we speak


I have update the build input to use this version.  A new build will be
kicked off as soon as I receive confirmation on whether or not there will 
be
a submission from swt.

-----eclipse-dev-admin@xxxxxxxxxxx wrote: -----

To: eclipse-dev@xxxxxxxxxxx
From: Nick_Edgar@xxxxxxx
Sent by: eclipse-dev-admin@xxxxxxxxxxx
Date: 06/02/2002 11:08AM
Subject: Re: [eclipse-dev] A new build is being done as we speak


Taking org.eclipse.ui from HEAD was the right decision.
I have versioned it off as v20020602, which can be used if another rebuild
is needed.

Nick

-----eclipse-dev-admin@xxxxxxxxxxx wrote: -----

To: eclipse-dev@xxxxxxxxxxx
From: Dean_Roberts@xxxxxxx
Sent by: eclipse-dev-admin@xxxxxxxxxxx
Date: 06/02/2002 08:40AM
Subject: [eclipse-dev] A new build is being done as we speak


Hi folks,

I got up this morning and found the following mail:

        A PDE contribution for their stop test bug on Linux
        A JDT UI contribution for their stop test bug

So I made the executive decision to kick another integration build.  It 
will
go up as 20020602 on the web page.  Note that from the emails that went by 
I
believe the JDTUI fix required fixes that Kai released on HEAD of
org.eclipse.ui.  This integration build is building with HEAD of
org.eclipse.ui plugin.  This is unorthodox but expedient.

This build will also rerun the failing JDTDEBUG test so we can get another
look at what is going on.

So if this build goes well I believe it will have fixes for all the 
serious
and/or stop test bugs except for:

        bug 18625  (Editor tab problem on Linux)
        bug 18629  (A GTK problem)

So this build may be an F2 candidate or may  be a good jumping off point 
to
incorporate fixes for the 2 bugs above.  Or, it may even be ignored if we
decide to promote the 06-01 build to F2.

I will not be available between 10:30 am and 11:00 pm.
Sonia may be available between 10:00 am and 5:00 pm but will not be
available after that.
I will be sending email to Kevin and John describing how to kick off a
build.

As it was yesterday by work extension is forwarded to my cell phone.

...Dean...





_______________________________________________eclipse-dev mailing
listeclipse-dev@eclipse.orghttp://dev.eclipse.org/mailman/listinfo/eclipse-d
ev_______________________________________________ eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx http://dev.eclipse.org/mailman/listinfo/eclipse-dev

_______________________________________________
eclipse-dev mailing list
eclipse-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/eclipse-dev