[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
[eclipse-dev] Eclipse 3.0 shows Platform not defined for Wireless Apps
|
Hello group:
I have been trying to make Nokia 12 to run on Java using the Eclipse 3.0 as
an editor, following all the necessary set-up for path class, libraries etc.
I do not know why at compile time it shows an error message saying "Platform
is undefined". Funny is that everything works with Sun One?
Berns
----- Original Message -----
From: <eclipse-dev-request@xxxxxxxxxxx>
To: <eclipse-dev@xxxxxxxxxxx>
Sent: Thursday, July 29, 2004 9:00 AM
Subject: eclipse-dev digest, Vol 1 #1221 - 3 msgs
> Send eclipse-dev mailing list submissions to
> eclipse-dev@xxxxxxxxxxx
>
> To subscribe or unsubscribe via the World Wide Web, visit
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
> or, via email, send a message with subject or body 'help' to
> eclipse-dev-request@xxxxxxxxxxx
>
> You can reach the person managing the list at
> eclipse-dev-admin@xxxxxxxxxxx
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of eclipse-dev digest..."
>
>
> Today's Topics:
>
> 1. Re: JDK 1.3 support for SWT (Steve Northover)
> 2. can't able 2 launch jboss-3.2.4 using lomboz in eclipse 3.0 (mahesh
adepu)
> 3. Behavior of IWorkspace.run() (Waqas Ilyas)
>
> --__--__--
>
> Message: 1
> To: eclipse-dev@xxxxxxxxxxx
> Subject: Re: [eclipse-dev] JDK 1.3 support for SWT
> From: Steve Northover <Steve_Northover@xxxxxxxxxx>
> Date: Wed, 28 Jul 2004 12:24:07 -0400
> Reply-To: eclipse-dev@xxxxxxxxxxx
>
> This is a multipart message in MIME format.
> --=_alternative 005A191485256EDF_=
> Content-Type: text/plain; charset="US-ASCII"
>
> On Wed, 2004-07-28 at 17:08, Steve Northover wrote:
> > Do you have a specific problem under JDK 1.3 Windows? If so enter a
> > problem report. Thanks.
>
> To summarize, mouse events are not propogated under JDK Windows 1.3 but
> are correctly propogated under JDK 1.4? If this is what you are saying,
> then update the problem report. From the SWT_AWT Javadoc, it appears that
> this problem also happens under JDK 1.5 so it is possible that Sun fixed
> it for 1.4 and broke it again for 1.5. In any case, since the Javadoc
> describes a work around, it is unlikely that we can fix the problem. We
> simply don't own that side of the code.
>
> In general:
>
> Rather than reading the source, why don't you just report the problem and
> give the details? The JDK1_3 variable in the class SWT_AWT seems to be
> working around an internal AWT focus issue. It might be related to the
> problem you are seeing and it might not. If you have done research that
> proves that it is related, then indicate it in the problem report (ie.
> something like, "I set JDK1_3 to false, even though I am running on 1.3
> and it worked. The flag is therefore bogus and causing the trouble.").
> Otherwise, why bring it up at all? The names of the internal variables in
> SWT just aren't relevant.
>
> Background to the problem of "mouse events not propogated" is the fact
> that we really only support JDK 1.4 Windows and JDK 1.5 Linux. SWT_AWT
> may run under JDK 1.3 Windows, but the code is largely untested. For
> example, SWT itself (the widgets and graphics) actually runs under JDK
> 1.1.x but we don't support it or test it. This means that we may
> accidently work in configurations that are untested without officially
> supporting them. The burden of officially testing and supporting every
> combination of operating system and JDK is just too huge. We would die.
>
>
>
>
> Martin van den Bemt <mllist@xxxxxxxx>
> Sent by: eclipse-dev-admin@xxxxxxxxxxx
> 07/28/2004 11:38 AM
> Please respond to
> eclipse-dev
>
>
> To
> eclipse-dev@xxxxxxxxxxx
> cc
>
> Subject
> Re: [eclipse-dev] JDK 1.3 support for SWT
>
>
>
>
>
>
> I think it is clearly explained in my mail what the issue is.
> You say you don't support 1.3, but code says different. The issue I have
> was filed, changed by you and others and completely misunderstood,
> misread or whatever, closed, reopened by me, explaining again, again
> misunderstood and closed again.
> I said I have a problem with oranges, you made my problem about apples.
>
> So a last try, like I would have explained to my great grandmother :
> - Open the SWT_AWT.java file
> - Look at the code
> - See references the a static JDK13 variable
> - Guessing from that, it supports JDK 1.3
> - Create a new java file
> - Copy & Paste the code that is in the issue
> - Run it under jdk1.3
> - Frame0 receives mouse events, but doesn't propagate to other
> components
> - Run it under jdk1.4
> - It works.
>
> The answer I got from you says : The javadoc states "In jdk 1.5 blah
> blah" and we don't support 1.3.
>
> That leaves you with a couple of possible issues :
> 1) If you don't support jdk 1.3, you should remove 1.3 code, so you have
> less point of failures and less code to maintain.
> 2) Your javadoc is wrong and means to say jdk 1.3, which means you also
> have a bug.
> 3) Jdk 1.3 should work, so this needs fixing ?
>
> Please chose an option of what is really what you meant..
>
> Sorry about the ranting tone, maybe we are just talking different
> languages..
>
> Mvgr,
> Martin
>
> On Wed, 2004-07-28 at 17:08, Steve Northover wrote:
> > Do you have a specific problem under JDK 1.3 Windows? If so enter a
> > problem report. Thanks.
> >
> >
> >
> > Martin van den Bemt
> > <mllist@xxxxxxxx>
> > Sent by:
> > eclipse-dev-admin@xxxxxxxxxxx
> >
> > 07/27/2004 08:09 PM
> > Please respond to
> > eclipse-dev
> > To
> > eclipse-dev@xxxxxxxxxxx
> > cc
> >
> > Subject
> > [eclipse-dev] JDK
> > 1.3 support for
> > SWT
> >
> >
> >
> >
> > Maybe this is the wrong list, but at least some developers are present
> > of eclipse, that I assume know what the exact deal is.
> > I filed an issue today
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=70918
> > which talks about problems I have with the SWT_AWT class running under
> > jdk1.3, and somehow I got some answers about using jdk 1.5 and 1.3 not
> > being supported, although this particular piece of code contains some
> > specifics for JDK1.3. I got pissed of at the answers, since they
> > aren't
> > answers.
> > Also for now SWT 3.0 seem to work ok for me running on a jdk 1.3
> > (windows)
> > So maybe I can get some clear answers to my questions here :
> > - Why is jdk 1.3 not supported ? (eg OLE works great on jdk1.3)
> > - SWT_AWT.java contains code specifically for JDK 1.3 and was added
> > when
> > you guys started working on version 3, why is the code in there if it
> > is
> > not supported. Was it decided later and the was the code never removed
> > ?
> > (I assumed it needed 1.4, but since the 1.3 code was in there, I went
> > ahead anyway).
> > - Is there a link that specifies what changed to make stuff not work
> > under 1.3 ?
> >
> > I cannot make important decisions (in this case a move from jdk1.3 to
> > 1.4, which is pretty time consuming), if I see contradictions. The
> > code
> > pretends it works under 1.3, it fails, so it is bug, in my point of
> > view. If you don't want to support 1.3, code should be removed (less
> > testing, less possible errors, less code), which is a "bug" too or at
> > least a chore.
> >
> > I know you don't owe me any explanation for this of any kind (since it
> > is free code and all), but too treat an issue like that, is something
> > I
> > probably don't deserve, based on the information in the issue
> > provided.
> >
> > --
> > Mvgr,
> > Martin
> >
> > _______________________________________________
> > eclipse-dev mailing list
> > eclipse-dev@xxxxxxxxxxx
> > To change your delivery options, retrieve your password, or
> > unsubscribe from this list, visit
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
> --
> Mvgr,
> Martin
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>
> --=_alternative 005A191485256EDF_=
> Content-Type: text/html; charset="US-ASCII"
>
>
> <br><font size=2><tt><br>
> On Wed, 2004-07-28 at 17:08, Steve Northover wrote:<br>
> > Do you have a specific problem under JDK 1.3 Windows? If so
> enter a<br>
> > problem report. Thanks.</tt></font>
> <br>
> <br><font size=2 face="sans-serif">To summarize, mouse events are not
propogated
> under JDK Windows 1.3 but are correctly propogated under JDK 1.4? If
> this is what you are saying, then update the problem report. From
> the SWT_AWT Javadoc, it appears that this problem also happens under JDK
> 1.5 so it is possible that Sun fixed it for 1.4 and broke it again for
> 1.5. In any case, since the Javadoc describes a work around, it is
> unlikely that we can fix the problem. We simply don't own that side
> of the code.</font>
> <br>
> <br><font size=2 face="sans-serif">In general:</font>
> <br>
> <br><font size=2 face="sans-serif">Rather than reading the source, why
> don't you just report the problem and give the details? The JDK1_3
> variable in the class SWT_AWT seems to be working around an internal AWT
> focus issue. It might be related to the problem you are seeing and
> it might not. If you have done research that proves that it is
related,
> then indicate it in the problem report (ie. something like, "I set
> JDK1_3 to false, even though I am running on 1.3 and it worked. The
> flag is therefore bogus and causing the trouble."). Otherwise,
> why bring it up at all? The names of the internal variables in SWT
> just aren't relevant.</font>
> <br>
> <br><font size=2 face="sans-serif">Background to the problem of
"mouse
> events not propogated" is the fact that we really only support JDK
> 1.4 Windows and JDK 1.5 Linux. SWT_AWT may run under JDK 1.3
Windows,
> but the code is largely untested. For example, SWT itself (the
widgets
> and graphics) actually runs under JDK 1.1.x but we don't support it or
> test it. This means that we may accidently work in configurations
> that are untested without officially supporting them. The burden of
officially
> testing and supporting every combination of operating system and JDK is
> just too huge. We would die.</font>
> <br>
> <br>
> <br>
> <br>
> <table width=100%>
> <tr valign=top>
> <td width=40%><font size=1 face="sans-serif"><b>Martin van den Bemt
<mllist@xxxxxxxx></b>
> </font>
> <br><font size=1 face="sans-serif">Sent by:
eclipse-dev-admin@xxxxxxxxxxx</font>
> <p><font size=1 face="sans-serif">07/28/2004 11:38 AM</font>
> <table border>
> <tr valign=top>
> <td bgcolor=white>
> <div align=center><font size=1 face="sans-serif">Please respond to<br>
> eclipse-dev</font></div></table>
> <br>
> <td width=59%>
> <table width=100%>
> <tr>
> <td>
> <div align=right><font size=1 face="sans-serif">To</font></div>
> <td valign=top><font size=1
face="sans-serif">eclipse-dev@xxxxxxxxxxx</font>
> <tr>
> <td>
> <div align=right><font size=1 face="sans-serif">cc</font></div>
> <td valign=top>
> <tr>
> <td>
> <div align=right><font size=1 face="sans-serif">Subject</font></div>
> <td valign=top><font size=1 face="sans-serif">Re: [eclipse-dev] JDK 1.3
> support for SWT</font></table>
> <br>
> <table>
> <tr valign=top>
> <td>
> <td></table>
> <br></table>
> <br>
> <br>
> <br><font size=2><tt>I think it is clearly explained in my mail what the
> issue is. <br>
> You say you don't support 1.3, but code says different. The issue I
have<br>
> was filed, changed by you and others and completely misunderstood,<br>
> misread or whatever, closed, reopened by me, explaining again, again<br>
> misunderstood and closed again.<br>
> I said I have a problem with oranges, you made my problem about
apples.<br>
> <br>
> So a last try, like I would have explained to my great grandmother :<br>
> - Open the SWT_AWT.java file<br>
> - Look at the code<br>
> - See references the a static JDK13 variable<br>
> - Guessing from that, it supports JDK 1.3<br>
> - Create a new java file<br>
> - Copy & Paste the code that is in the issue<br>
> - Run it under jdk1.3<br>
> - Frame0 receives mouse events, but doesn't propagate to other<br>
> components<br>
> - Run it under jdk1.4<br>
> - It works.<br>
> <br>
> The answer I got from you says : The javadoc states "In jdk 1.5
blah<br>
> blah" and we don't support 1.3.<br>
> <br>
> That leaves you with a couple of possible issues :<br>
> 1) If you don't support jdk 1.3, you should remove 1.3 code, so you
have<br>
> less point of failures and less code to maintain.<br>
> 2) Your javadoc is wrong and means to say jdk 1.3, which means you
also<br>
> have a bug.<br>
> 3) Jdk 1.3 should work, so this needs fixing ?<br>
> <br>
> Please chose an option of what is really what you meant..<br>
> <br>
> Sorry about the ranting tone, maybe we are just talking different<br>
> languages..<br>
> <br>
> Mvgr,<br>
> Martin<br>
> <br>
> On Wed, 2004-07-28 at 17:08, Steve Northover wrote:<br>
> > Do you have a specific problem under JDK 1.3 Windows? If so
> enter a<br>
> > problem report. Thanks.<br>
> > <br>
> > <br>
> > <br>
> > Martin van den Bemt<br>
> > <mllist@xxxxxxxx><br>
> > Sent by:<br>
> > eclipse-dev-admin@xxxxxxxxxxx<br>
> > <br>
> > 07/27/2004 08:09 PM<br>
> > Please respond to<br>
> > eclipse-dev<br>
> > To<br>
> > eclipse-dev@xxxxxxxxxxx<br>
> > cc<br>
> > <br>
> > Subject<br>
> > [eclipse-dev] JDK<br>
> > 1.3 support for<br>
> > SWT<br>
> > <br>
> > <br>
> > <br>
> > <br>
> > Maybe this is the wrong list, but at least some developers are
present<br>
> > of eclipse, that I assume know what the exact deal is.<br>
> > I filed an issue today<br>
> > https://bugs.eclipse.org/bugs/show_bug.cgi?id=70918<br>
> > which talks about problems I have with the SWT_AWT class running
under<br>
> > jdk1.3, and somehow I got some answers about using jdk 1.5 and 1.3
> not<br>
> > being supported, although this particular piece of code contains
some<br>
> > specifics for JDK1.3. I got pissed of at the answers, since they<br>
> > aren't<br>
> > answers.<br>
> > Also for now SWT 3.0 seem to work ok for me running on a jdk 1.3<br>
> > (windows)<br>
> > So maybe I can get some clear answers to my questions here :<br>
> > - Why is jdk 1.3 not supported ? (eg OLE works great on jdk1.3)<br>
> > - SWT_AWT.java contains code specifically for JDK 1.3 and was
added<br>
> > when<br>
> > you guys started working on version 3, why is the code in there if
> it<br>
> > is<br>
> > not supported. Was it decided later and the was the code never
removed<br>
> > ?<br>
> > (I assumed it needed 1.4, but since the 1.3 code was in there, I
went<br>
> > ahead anyway).<br>
> > - Is there a link that specifies what changed to make stuff not
work<br>
> > under 1.3 ?<br>
> > <br>
> > I cannot make important decisions (in this case a move from jdk1.3
> to<br>
> > 1.4, which is pretty time consuming), if I see contradictions.
The<br>
> > code<br>
> > pretends it works under 1.3, it fails, so it is bug, in my point
of<br>
> > view. If you don't want to support 1.3, code should be removed
(less<br>
> > testing, less possible errors, less code), which is a "bug"
> too or at<br>
> > least a chore.<br>
> > <br>
> > I know you don't owe me any explanation for this of any kind (since
> it<br>
> > is free code and all), but too treat an issue like that, is
something<br>
> > I<br>
> > probably don't deserve, based on the information in the issue<br>
> > provided.<br>
> > <br>
> > -- <br>
> > Mvgr,<br>
> > Martin<br>
> > <br>
> > _______________________________________________<br>
> > eclipse-dev mailing list<br>
> > eclipse-dev@xxxxxxxxxxx<br>
> > To change your delivery options, retrieve your password, or<br>
> > unsubscribe from this list, visit<br>
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev<br>
> -- <br>
> Mvgr,<br>
> Martin<br>
> <br>
> _______________________________________________<br>
> eclipse-dev mailing list<br>
> eclipse-dev@xxxxxxxxxxx<br>
> To change your delivery options, retrieve your password, or unsubscribe
> from this list, visit<br>
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev<br>
> </tt></font>
> <br>
> --=_alternative 005A191485256EDF_=--
>
> --__--__--
>
> Message: 2
> Date: 29 Jul 2004 13:00:40 -0000
> From: "mahesh adepu" <maheshadepu@xxxxxxxxxxxxxx>
> To: eclipse-dev@xxxxxxxxxxx
> Subject: [eclipse-dev] can't able 2 launch jboss-3.2.4 using lomboz in
eclipse 3.0
> Reply-To: eclipse-dev@xxxxxxxxxxx
>
> This is a multipart mime message
>
>
> --Next_1091106040---0-203.199.83.28-14379
> Content-type: text/html;
> charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> <P>=0AHi frnds, <BR>=0AI am trying to integrate struts,vss,lomboz into
ecli=
> pse. <BR>=0AFor better debugging i am using lomboz plugin for jboss-3.2.4.
=
> <BR>=0ABut i can't able 2 launch jboss server in debug mode.Its giving
<BR>=
> =0Aexception like this: <BR>=0A<BR>=0AError Oct 28, 2002 15:38:43.467 J2EE
=
> Plugin internal error <BR>=0Aorg.eclipse.core.runtime.CoreException[120]:
<=
> BR>=0Ajava.net.SocketException: socket closed <BR>=0Aat
java.net.PlainSocke=
> tImpl.socketAccept(Native <BR>=0AMethod) <BR>=0Aat
java.net.PlainSocketImpl=
> .accept(Unknown <BR>=0ASource) <BR>=0Aat
java.net.ServerSocket.implAccept(U=
> nknown <BR>=0ASource) <BR>=0Aat java.net.ServerSocket.accept(Unknown
Source=
> ) <BR>=0Aat
<BR>=0Aorg.eclipse.jdi.internal.connect.SocketTransportImpl.acc=
> ept <BR>=0A(SocketTransportImpl.java:87) <BR>=0Aat
<BR>=0Aorg.eclipse.jdi.i=
> nternal.connect.SocketListeningConnectorImpl.a
<BR>=0Accept(SocketListening=
> ConnectorImpl.java:124) <BR>=0Aat
<BR>=0Aorg.eclipse.jdt.internal.launching=
> .StandardVMDebugger$Conne
<BR>=0ActRunnable.run(StandardVMDebugger.java:78)=
> <BR>=0Aat java.lang.Thread.run(Unknown Source) <BR>=0A<BR>=0A<BR>=0A<BR>=
> =0Aplz if any one has solution plz reply me ASAP to
<BR>=0Amaheshadepu@redi=
> ffmail.com <BR>=0A<BR>=0Amahesh<BR>=0A=0A</P>=0A=0A=0A<br><br>=0A<A
target=
> =3D"_blank"
HREF=3D"http://clients.rediff.com/signature/track_sig.asp";><IMG=
>
SRC=3D"http://ads.rediff.com/RealMedia/ads/adstream_nx.cgi/www.rediffmail.=
> com/inbox.htm@Bottom" BORDER=3D0 VSPACE=3D0 HSPACE=3D0></a>=0A
> --Next_1091106040---0-203.199.83.28-14379
> Content-type: text/plain;
> charset=iso-8859-1
> Content-Transfer-Encoding: quoted-printable
> Content-Disposition: inline
>
> Hi frnds, =0AI am trying to integrate struts,vss,lomboz into eclipse.
=0AFo=
> r better debugging i am using lomboz plugin for jboss-3.2.4. =0ABut i
can't=
> able 2 launch jboss server in debug mode.Its giving =0Aexception like
this=
> : =0A=0AError Oct 28, 2002 15:38:43.467 J2EE Plugin internal error
=0Aorg.e=
> clipse.core.runtime.CoreException[120]: =0Ajava.net.SocketException:
socket=
> closed =0Aat java.net.PlainSocketImpl.socketAccept(Native =0AMethod)
=0Aat=
> java.net.PlainSocketImpl.accept(Unknown =0ASource) =0Aat
java.net.ServerSo=
> cket.implAccept(Unknown =0ASource) =0Aat
java.net.ServerSocket.accept(Unkno=
> wn Source) =0Aat
=0Aorg.eclipse.jdi.internal.connect.SocketTransportImpl.ac=
> cept =0A(SocketTransportImpl.java:87) =0Aat
=0Aorg.eclipse.jdi.internal.con=
> nect.SocketListeningConnectorImpl.a
=0Accept(SocketListeningConnectorImpl.j=
> ava:124) =0Aat
=0Aorg.eclipse.jdt.internal.launching.StandardVMDebugger$Con=
> ne =0ActRunnable.run(StandardVMDebugger.java:78) =0Aat
java.lang.Thread.run=
> (Unknown Source) =0A=0A=0A=0Aplz if any one has solution plz reply me ASAP
=
> to =0Amaheshadepu@xxxxxxxxxxxxxx =0A=0Amahesh=0A=0A=0A
> --Next_1091106040---0-203.199.83.28-14379--
>
>
> --__--__--
>
> Message: 3
> From: "Waqas Ilyas" <dr_wack@xxxxxxxxxxxx>
> To: eclipse-dev@xxxxxxxxxxx
> Date: Thu, 29 Jul 2004 20:36:25 +0500
> Subject: [eclipse-dev] Behavior of IWorkspace.run()
> Reply-To: eclipse-dev@xxxxxxxxxxx
>
> This is a multi-part message in MIME format.
>
> ------=_NextPart_000_0042_01C475AB.B7D455A0
> Content-Type: text/plain;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> I want to know that when we run some actions that make changes to the =
> work space, but in the IWorkspaceRunnable.run() method that we pass onto =
> Workspace.run(). Then, how does the workspace comes to know that what =
> changes have been made to the workspace.
>
> For example i run a tool that creates a zip file of some of the =
> resources i put this action in this run method but when the method =
> returns the workspace doesnt show the zip file in the navigatro view. =
> Althought it is there in the file system. It appears if i refresh it. (I =
> am using eclipse 2.1)
>
> Do i need to perform some other tasks like create or modify the delta =
> and return it back or somehow hint the workspace as to what and where =
> the change has occured or does the workspace automatically detects all =
> the changes once the run has been called.
>
> Please help me on this i am stuck at this and i have no idea what the =
> problem could be.
>
>
> ------=_NextPart_000_0042_01C475AB.B7D455A0
> Content-Type: text/html;
> charset="iso-8859-1"
> Content-Transfer-Encoding: quoted-printable
>
> <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN">
> <HTML><HEAD>
> <META http-equiv=3DContent-Type content=3D"text/html; =
> charset=3Diso-8859-1">
> <META content=3D"MSHTML 6.00.2800.1400" name=3DGENERATOR>
> <STYLE></STYLE>
> </HEAD>
> <BODY bgColor=3D#ffffff>
> <DIV><FONT face=3DArial size=3D2>I want to know that when we run some =
> actions that=20
> make changes to the work space, but in the IWorkspaceRunnable.run() =
> method that=20
> we pass onto Workspace.run(). Then, how does the workspace comes to know =
> that=20
> what changes have been made to the workspace.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>For example i run a tool that creates a =
> zip file of=20
> some of the resources i put this action in this run method but when the =
> method=20
> returns the workspace doesnt show the zip file in the navigatro view. =
> Althought=20
> it is there in the file system. It appears if i refresh it. (I am using =
> eclipse=20
> 2.1)</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Do i need to perform some other tasks =
> like create=20
> or modify the delta and return it back or somehow hint the workspace as =
> to what=20
> and where the change has occured or does the workspace automatically =
> detects all=20
> the changes once the run has been called.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2>Please help me on this i am stuck at =
> this and i=20
> have no idea what the problem could be.</FONT></DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV>
> <DIV><FONT face=3DArial size=3D2></FONT> </DIV></BODY></HTML>
>
> ------=_NextPart_000_0042_01C475AB.B7D455A0--
>
>
>
> --__--__--
>
> _______________________________________________
> eclipse-dev mailing list
> eclipse-dev@xxxxxxxxxxx
> To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
> http://dev.eclipse.org/mailman/listinfo/eclipse-dev
>
>
> End of eclipse-dev Digest
>
