Home » Language IDEs » Java Development Tools (JDT) » Refactor - rename (notice)
| Refactor - rename (notice) [message #24564] |
Thu, 15 May 2003 12:16  |
Eclipse User |
|
|
|
Hello,
I see Stanislav's sugestions for refactor - rename and try :
1) <javac target="1.1" and refactor -> rename don't work
2) recompile all with jdk 1.3.1 (and ant 1.5.3) and refactor -> rename work
Conclusion :
refactor -> rename don't work with java > 1.3.1 (and other things, maybe)
regards
Haris Peco
|
|
| | |
| Re: Refactor - rename (notice) [message #24840 is a reply to message #24728] |
Thu, 15 May 2003 12:26  |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
AFAIK, it's also Java 1.4, but maybe there is also some other older JDK
installed, which Java is first found on the execution path. - Since I'am not
before next monday again in the University, I can't say for sure which
concrete Java version there is used. - I can tell you this for sure on
monday.
Valentino
"snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
news:ba0c2s$ejv$1@rogue.oti.com...
> What java build is on University ?
> I think that eclipse recompile don't really recompile all stuff or
> that dependent from java version.
> Valentino Kyriakides wrote:
>
> > Well, at home I compile the "jdt.ui" sources with the Eclipse build in
> > compiler and Eclipse itself here runs with the Java Standard Edition
> > (build 1.4.1-b21) RFE (Java HotSpot Client VM build 1.4.1-b21, mixed
> > mode). I have NO problems with this way of compiling and afterwards
using
> > the compiled "jdt.ui" from inside a runtime-workspace.
> >
> > However, at the University computers I use the same approach, e.g.
> > importing the "jdt.ui" plugin into the workspace as an Eclipse project,
> > recompiling it and then using it inside an Eclipse runtime-workspace.
> > There it doesn't work and I always have the same behaviour that none of
> > the Rename refactorings works... STRANGE isn't it...
> >
> > Valentino
> >
> > "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
> > news:ba0630$83a$1@rogue.oti.com...
> >> Hello,
> >> I see Stanislav's sugestions for refactor - rename and try :
> >> 1) <javac target="1.1" and refactor -> rename don't work
> >> 2) recompile all with jdk 1.3.1 (and ant 1.5.3) and refactor -> rename
> > work
> >>
> >> Conclusion :
> >> refactor -> rename don't work with java > 1.3.1 (and other things,
maybe)
> >>
> >> regards
> >> Haris Peco
>
|
|
|
| Re: Refactor - rename (notice) [message #25152 is a reply to message #24840] |
Thu, 15 May 2003 16:53 |
| Eclipse User |
|
|
|
It is important which VM is ant (from ant documentation)
If ant is <= 1.3 then <javac> tag in ant is default 1.1
Please check ant, too
regards
Haris Peco
Valentino Kyriakides wrote:
> AFAIK, it's also Java 1.4, but maybe there is also some other older JDK
> installed, which Java is first found on the execution path. - Since I'am
> not before next monday again in the University, I can't say for sure which
> concrete Java version there is used. - I can tell you this for sure on
> monday.
>
> Valentino
>
> "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
> news:ba0c2s$ejv$1@rogue.oti.com...
>> What java build is on University ?
>> I think that eclipse recompile don't really recompile all stuff or
>> that dependent from java version.
>> Valentino Kyriakides wrote:
>>
>> > Well, at home I compile the "jdt.ui" sources with the Eclipse build in
>> > compiler and Eclipse itself here runs with the Java Standard Edition
>> > (build 1.4.1-b21) RFE (Java HotSpot Client VM build 1.4.1-b21, mixed
>> > mode). I have NO problems with this way of compiling and afterwards
> using
>> > the compiled "jdt.ui" from inside a runtime-workspace.
>> >
>> > However, at the University computers I use the same approach, e.g.
>> > importing the "jdt.ui" plugin into the workspace as an Eclipse project,
>> > recompiling it and then using it inside an Eclipse runtime-workspace.
>> > There it doesn't work and I always have the same behaviour that none of
>> > the Rename refactorings works... STRANGE isn't it...
>> >
>> > Valentino
>> >
>> > "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
>> > news:ba0630$83a$1@rogue.oti.com...
>> >> Hello,
>> >> I see Stanislav's sugestions for refactor - rename and try :
>> >> 1) <javac target="1.1" and refactor -> rename don't work
>> >> 2) recompile all with jdk 1.3.1 (and ant 1.5.3) and refactor -> rename
>> > work
>> >>
>> >> Conclusion :
>> >> refactor -> rename don't work with java > 1.3.1 (and other things,
> maybe)
>> >>
>> >> regards
>> >> Haris Peco
>>
|
|
|
| Re: Refactor - rename (notice) [message #25274 is a reply to message #25152] |
Thu, 15 May 2003 17:10 |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
I don't think it has something todo with ant in my case. Don't forget, I
only use the imported "jdt.ui" which comes along with Eclipse 2.1 itself and
not any cvs server version with build.xml files like you seem to use. -
Beside that, the procedure I use (as I explained before...) is always the
same on the home and University computers, with the same Eclipse version,
but the rename refactorings behave absolute different on these machines.
AFAI can see, there is nothing which can be substancially changed related to
compile settings for an imported "jdt.ui" plugin under it's project
properties. But maybe I have overseen something here...?
Valentino
"snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
news:ba0mae$o87$1@rogue.oti.com...
> It is important which VM is ant (from ant documentation)
> If ant is <= 1.3 then <javac> tag in ant is default 1.1
> Please check ant, too
>
> regards
> Haris Peco
> Valentino Kyriakides wrote:
>
> > AFAIK, it's also Java 1.4, but maybe there is also some other older JDK
> > installed, which Java is first found on the execution path. - Since I'am
> > not before next monday again in the University, I can't say for sure
which
> > concrete Java version there is used. - I can tell you this for sure on
> > monday.
> >
> > Valentino
> >
> > "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
> > news:ba0c2s$ejv$1@rogue.oti.com...
> >> What java build is on University ?
> >> I think that eclipse recompile don't really recompile all stuff or
> >> that dependent from java version.
> >> Valentino Kyriakides wrote:
> >>
> >> > Well, at home I compile the "jdt.ui" sources with the Eclipse build
in
> >> > compiler and Eclipse itself here runs with the Java Standard Edition
> >> > (build 1.4.1-b21) RFE (Java HotSpot Client VM build 1.4.1-b21, mixed
> >> > mode). I have NO problems with this way of compiling and afterwards
> > using
> >> > the compiled "jdt.ui" from inside a runtime-workspace.
> >> >
> >> > However, at the University computers I use the same approach, e.g.
> >> > importing the "jdt.ui" plugin into the workspace as an Eclipse
project,
> >> > recompiling it and then using it inside an Eclipse runtime-workspace.
> >> > There it doesn't work and I always have the same behaviour that none
of
> >> > the Rename refactorings works... STRANGE isn't it...
> >> >
> >> > Valentino
> >> >
> >> > "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
> >> > news:ba0630$83a$1@rogue.oti.com...
> >> >> Hello,
> >> >> I see Stanislav's sugestions for refactor - rename and try :
> >> >> 1) <javac target="1.1" and refactor -> rename don't work
> >> >> 2) recompile all with jdk 1.3.1 (and ant 1.5.3) and refactor ->
rename
> >> > work
> >> >>
> >> >> Conclusion :
> >> >> refactor -> rename don't work with java > 1.3.1 (and other things,
> > maybe)
> >> >>
> >> >> regards
> >> >> Haris Peco
> >>
>
|
|
|
| Re: Refactor - rename (notice) [message #25315 is a reply to message #25274] |
Thu, 15 May 2003 20:36 |
| Eclipse User |
|
|
|
If you compile jdt.ui then it is important jdk and ant if compile with ant
regards
Valentino Kyriakides wrote:
> I don't think it has something todo with ant in my case. Don't forget, I
> only use the imported "jdt.ui" which comes along with Eclipse 2.1 itself
> and not any cvs server version with build.xml files like you seem to use.
> - Beside that, the procedure I use (as I explained before...) is always
> the same on the home and University computers, with the same Eclipse
> version, but the rename refactorings behave absolute different on these
> machines.
>
> AFAI can see, there is nothing which can be substancially changed related
> to compile settings for an imported "jdt.ui" plugin under it's project
> properties. But maybe I have overseen something here...?
>
> Valentino
>
> "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
> news:ba0mae$o87$1@rogue.oti.com...
>> It is important which VM is ant (from ant documentation)
>> If ant is <= 1.3 then <javac> tag in ant is default 1.1
>> Please check ant, too
>>
>> regards
>> Haris Peco
>> Valentino Kyriakides wrote:
>>
>> > AFAIK, it's also Java 1.4, but maybe there is also some other older JDK
>> > installed, which Java is first found on the execution path. - Since
>> > I'am not before next monday again in the University, I can't say for
>> > sure
> which
>> > concrete Java version there is used. - I can tell you this for sure on
>> > monday.
>> >
>> > Valentino
>> >
>> > "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
>> > news:ba0c2s$ejv$1@rogue.oti.com...
>> >> What java build is on University ?
>> >> I think that eclipse recompile don't really recompile all stuff or
>> >> that dependent from java version.
>> >> Valentino Kyriakides wrote:
>> >>
>> >> > Well, at home I compile the "jdt.ui" sources with the Eclipse build
> in
>> >> > compiler and Eclipse itself here runs with the Java Standard Edition
>> >> > (build 1.4.1-b21) RFE (Java HotSpot Client VM build 1.4.1-b21, mixed
>> >> > mode). I have NO problems with this way of compiling and afterwards
>> > using
>> >> > the compiled "jdt.ui" from inside a runtime-workspace.
>> >> >
>> >> > However, at the University computers I use the same approach, e.g.
>> >> > importing the "jdt.ui" plugin into the workspace as an Eclipse
> project,
>> >> > recompiling it and then using it inside an Eclipse
>> >> > runtime-workspace. There it doesn't work and I always have the same
>> >> > behaviour that none
> of
>> >> > the Rename refactorings works... STRANGE isn't it...
>> >> >
>> >> > Valentino
>> >> >
>> >> > "snpe" <snpe@snpe.co.yu> schrieb im Newsbeitrag
>> >> > news:ba0630$83a$1@rogue.oti.com...
>> >> >> Hello,
>> >> >> I see Stanislav's sugestions for refactor - rename and try :
>> >> >> 1) <javac target="1.1" and refactor -> rename don't work
>> >> >> 2) recompile all with jdk 1.3.1 (and ant 1.5.3) and refactor ->
> rename
>> >> > work
>> >> >>
>> >> >> Conclusion :
>> >> >> refactor -> rename don't work with java > 1.3.1 (and other things,
>> > maybe)
>> >> >>
>> >> >> regards
>> >> >> Haris Peco
>> >>
>>
|
|
| | | |
| Re: Refactor - rename (notice) [message #26518 is a reply to message #26096] |
Fri, 16 May 2003 15:35 |
| Eclipse User |
|
|
|
Hello Stanislav,
I try this with java 1.4.1-b21 (linux).Refactor -> rename work (I cast
second fRenameJavaElement.run(selection),too ).
I try Parent,DerivedA i DerivedB, too
In eclipse with compliance 1.4 I get 'Parent.doSmth ...' (this is
bug,probably),
but from command line this is fine and print : DerivedB.doSmth ... for every
combination -source and -target (and every combination in jdk 1.3.1)
My question :
What is compliance in eclipse / (options source, target ??) ?
What options use You from commnad line with j2sdk 1.4.1 ?
What compiler use eclipse - I can change JRE, but I don't know change
compiler ?
Thanks
Haris Peco
Stanislav Bernatsky wrote:
> Hello again.
> Seems to be working for build with sun j2sdk 1.4.1_02-b06 javac; target
> "1.3"
> --begin-------------------------------------------
> ---
> org.eclipse.jdt.ui\ui\org\eclipse\jdt\ui\actions\RenameActio n.java.orig
> Thu May 15 08:42:35 2003
> +++ org.eclipse.jdt.ui\ui\org\eclipse\jdt\ui\actions\RenameActio n.java Fri
> May 16 12:16:17 2003
> @@ -113,7 +113,7 @@
>
> protected void run(IStructuredSelection selection) {
> if (fRenameJavaElement.isEnabled())
> - fRenameJavaElement.run(selection);
> +
>
((SelectionDispatchAction)fRenameJavaElement).run((IStructur edSelection)selection);
> if (fRenameResource != null && fRenameResource.isEnabled())
> fRenameResource.run(selection);
> }
> --end---------------------------------------------
>
> Best regards,
> Stanislav Bernatsky.
>
> PS. Using this patch with sun j2sdk 1.3.1_07-b02 javac; target "1.3" ends
> with other errors during runtime.
|
|
|
| Re: Refactor - rename (notice) [message #28239 is a reply to message #26518] |
Mon, 19 May 2003 04:23 |
| Eclipse User |
|
|
|
Originally posted by: sbernatsky.ukr.net
Hello.
snpe wrote:
> I try this with java 1.4.1-b21 (linux).Refactor -> rename work (I cast
> second fRenameJavaElement.run(selection),too ).
If I compile eclipse with j2sdk 1.3.1_07-b02 javac with target "1.3" I get
some errors on '.log' file but 'refactor->rename' works. For more see
below.
I'm going to add 'Thread.dumpStack()' line to
org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(ISele ction
selection) method (which is empty now) to find if call from
RenameJavaElementAction.run() dispatches there. I'll post result later and
if it will appear to be true then I'll fill a bugreport.
> I try Parent,DerivedA i DerivedB, too
> In eclipse with compliance 1.4 I get 'Parent.doSmth ...' (this is
> bug,probably),
> but from command line this is fine and print : DerivedB.doSmth ... for every
> combination -source and -target (and every combination in jdk 1.3.1)
> My question :
> What is compliance in eclipse / (options source, target ??) ?
> What options use You from commnad line with j2sdk 1.4.1 ?
> What compiler use eclipse - I can change JRE, but I don't know change
> compiler ?
I also think that a call to the 'Parent.doSmth ...' is a bug, but I don't
know whose (eclipse or compiler). ;)
As I wrote earlier I used different compilers (eclipse running on sun
j2sdk 1.3.1_07-b02 for windows, sun j2sdk 1.3.1_07-b02 for windows and sun
j2sdk 1.4.1_02-b06 for windows) with different options (for exact options
see my previous posts) and sun j2sdk 1.3.1_07-b02 for windows to run
example. In short I've got 'Parent.doSmth ...' in these cases:
a) eclipse compiler with complience level set to '1.4' and any class
compatibility option;
b) sun j2sdk 1.4.1_02-b06 compiler with any target (command line is 'javac
-target "1.3" ...' or 'javac -target "1.1" ...' no -source option).
I've used posted patch to compile eclipse with different javac's with
different options. Then I ran obtained code in different jvm's and got
results shown below in table.
buildtime jvm javac target runtime jvm result comment
1,3 1,1 1,3 ok
1,3 1,1 1,4 ok
1,3 1,3 1,3 fail some errors in '.log'
file
1,3 1,3 1,4 fail some errors in '.log'
file
1,4 1,1 1,3 ok
1,4 1,1 1,4 ok
1,4 1,3 1,3 ok
1,4 1,3 1,4 ok
1,4 1,4 1,4 ok
Best regards,
Stanislav Bernatsky.
|
|
| |
| Re: Refactor - rename (notice) [message #29083 is a reply to message #28239] |
Mon, 19 May 2003 08:29 |
| Eclipse User |
|
|
|
Hi,
Stanislav Bernatsky wrote:
> Hello.
>
> snpe wrote:
>> I try this with java 1.4.1-b21 (linux).Refactor -> rename work (I cast
>> second fRenameJavaElement.run(selection),too ).
> If I compile eclipse with j2sdk 1.3.1_07-b02 javac with target "1.3" I get
> some errors on '.log' file but 'refactor->rename' works. For more see
> below.
> I'm going to add 'Thread.dumpStack()' line to
> org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(ISele ction
> selection) method (which is empty now) to find if call from
> RenameJavaElementAction.run() dispatches there. I'll post result later and
> if it will appear to be true then I'll fill a bugreport.
>
>> I try Parent,DerivedA i DerivedB, too
>> In eclipse with compliance 1.4 I get 'Parent.doSmth ...' (this is
>> bug,probably),
>> but from command line this is fine and print : DerivedB.doSmth ... for
>> every combination -source and -target (and every combination in jdk
>> 1.3.1) My question :
>> What is compliance in eclipse / (options source, target ??) ?
>> What options use You from commnad line with j2sdk 1.4.1 ?
>> What compiler use eclipse - I can change JRE, but I don't know change
>> compiler ?
> I also think that a call to the 'Parent.doSmth ...' is a bug, but I don't
> know whose (eclipse or compiler). ;)
> As I wrote earlier I used different compilers (eclipse running on sun
> j2sdk 1.3.1_07-b02 for windows, sun j2sdk 1.3.1_07-b02 for windows and sun
> j2sdk 1.4.1_02-b06 for windows) with different options (for exact options
> see my previous posts) and sun j2sdk 1.3.1_07-b02 for windows to run
> example. In short I've got 'Parent.doSmth ...' in these cases:
> a) eclipse compiler with complience level set to '1.4' and any class
> compatibility option;
> b) sun j2sdk 1.4.1_02-b06 compiler with any target (command line is 'javac
> -target "1.3" ...' or 'javac -target "1.1" ...' no -source option).
>
> I've used posted patch to compile eclipse with different javac's with
> different options. Then I ran obtained code in different jvm's and got
> results shown below in table.
> buildtime jvm javac target runtime jvm result comment
> 1,3 1,1 1,3 ok
> 1,3 1,1 1,4 ok
> 1,3 1,3 1,3 fail some errors in '.log'
> file
> 1,3 1,3 1,4 fail some errors in '.log'
> file
> 1,4 1,1 1,3 ok
> 1,4 1,1 1,4 ok
> 1,4 1,3 1,3 ok
> 1,4 1,3 1,4 ok
> 1,4 1,4 1,4 ok
>
> Best regards,
> Stanislav Bernatsky.
I see.Eclipse have internal compiler and we can't use external compiler in
eclipse, but behavior is same with eclipse compliance 1.3-jdk 1.3.1 and
eclipse complinace 1.4- jdk 1.4.
What is correct ?
I think that eclipse's choice that use protected method in different package
is a problem.
DerivedA don't see protected method in DerivedB and maybe that is correct
Parent.doSmth("String ...) and jdk 1.3 and jdk 1.4 aren't correct, but I
don't know.
regards
Haris Peco
|
|
|
| Re: Refactor - rename (notice) [message #31604 is a reply to message #28239] |
Tue, 20 May 2003 11:29 |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
I believe Stanislav is right here! - Even I use another "jdt.ui" import
plugin project approach, I always have to setup under the
"Compiler->Compliance and Classfiles" preferences seetings for the "jdt.ui"
project a compiler compliance level of "1.3". If I set the compiler
compliance level to "1,4" for the jdt.ui project the "rename" refactorings
don't work after a compilation and run in the runtime-workspace (the used
jvm is 1.4.1_02).
So in sum up the rename refactorings from the jdt.ui don't work for me with
a compiler compliance level of "1.4" and thus only with compliance level
"1.3".
Valentino
"Stanislav Bernatsky" <sbernatsky@ukr.net> schrieb im Newsbeitrag
news:baa4ab$lot$1@rogue.oti.com...
> Hello.
>
> snpe wrote:
> > I try this with java 1.4.1-b21 (linux).Refactor -> rename work (I
cast
> > second fRenameJavaElement.run(selection),too ).
> If I compile eclipse with j2sdk 1.3.1_07-b02 javac with target "1.3" I get
> some errors on '.log' file but 'refactor->rename' works. For more see
> below.
> I'm going to add 'Thread.dumpStack()' line to
> org.eclipse.jdt.ui.actions.SelectionDispatchAction.run(ISele ction
> selection) method (which is empty now) to find if call from
> RenameJavaElementAction.run() dispatches there. I'll post result later and
> if it will appear to be true then I'll fill a bugreport.
>
> > I try Parent,DerivedA i DerivedB, too
> > In eclipse with compliance 1.4 I get 'Parent.doSmth ...' (this is
> > bug,probably),
> > but from command line this is fine and print : DerivedB.doSmth ... for
every
> > combination -source and -target (and every combination in jdk 1.3.1)
> > My question :
> > What is compliance in eclipse / (options source, target ??) ?
> > What options use You from commnad line with j2sdk 1.4.1 ?
> > What compiler use eclipse - I can change JRE, but I don't know change
> > compiler ?
> I also think that a call to the 'Parent.doSmth ...' is a bug, but I don't
> know whose (eclipse or compiler). ;)
> As I wrote earlier I used different compilers (eclipse running on sun
> j2sdk 1.3.1_07-b02 for windows, sun j2sdk 1.3.1_07-b02 for windows and sun
> j2sdk 1.4.1_02-b06 for windows) with different options (for exact options
> see my previous posts) and sun j2sdk 1.3.1_07-b02 for windows to run
> example. In short I've got 'Parent.doSmth ...' in these cases:
> a) eclipse compiler with complience level set to '1.4' and any class
> compatibility option;
> b) sun j2sdk 1.4.1_02-b06 compiler with any target (command line is 'javac
> -target "1.3" ...' or 'javac -target "1.1" ...' no -source option).
>
> I've used posted patch to compile eclipse with different javac's with
> different options. Then I ran obtained code in different jvm's and got
> results shown below in table.
> buildtime jvm javac target runtime jvm result comment
> 1,3 1,1 1,3 ok
> 1,3 1,1 1,4 ok
> 1,3 1,3 1,3 fail some errors in '.log'
> file
> 1,3 1,3 1,4 fail some errors in '.log'
> file
> 1,4 1,1 1,3 ok
> 1,4 1,1 1,4 ok
> 1,4 1,3 1,3 ok
> 1,4 1,3 1,4 ok
> 1,4 1,4 1,4 ok
>
> Best regards,
> Stanislav Bernatsky.
>
|
|
| |
| Re: Refactor - rename (notice) [message #32157 is a reply to message #25726] |
Tue, 20 May 2003 17:45 |
| Eclipse User |
|
|
|
Hello,
....
> 5) I used eclipse to compile sources and sun j2sdk 1.3.1_07-b02 to
> runtime. And for different compile options I got different output:
> a) eclipse compiler; complience level=1.3; .class compat.=1.1
>>java eclipse.a.DerivedA
>>DerivedA.doSmth(String 'TEST')
>>DerivedB.doSmth(String 'TEST')
>
> b) eclipse compiler; complience level=1.3; .class compat.=1.2
>>java eclipse.a.DerivedA
>>DerivedA.doSmth(String 'TEST')
>>DerivedB.doSmth(String 'TEST')
>
> c) eclipse compiler; complience level=1.3; .class compat.=1.3
>>java eclipse.a.DerivedA
>>DerivedA.doSmth(String 'TEST')
>>DerivedB.doSmth(String 'TEST')
>
> d) eclipse compiler; complience level=1.4; .class compat.=1.1
>>java eclipse.a.DerivedA
>>DerivedA.doSmth(String 'TEST')
>>Parent.doSmth(Object 'TEST')
>
> e) eclipse compiler; complience level=1.4; .class compat.=1.2
>>java eclipse.a.DerivedA
>>DerivedA.doSmth(String 'TEST')
>>Parent.doSmth(Object 'TEST')
>
Why not this (jdk 1.4) :
DerivedA.doSmth(String 'TEST')
Parent.doSmth(String 'TEST')
Parent.doSmth(Object 'TEST')
Is it bug in jdk 1.4, yet ?
regards
Haris Peco
|
|
|
| Re: Refactor - rename (notice) [message #32610 is a reply to message #31913] |
Tue, 20 May 2003 17:30 |
| Eclipse User |
|
|
|
Originally posted by: vkyr.nospam-ision.net
I already know, that it is a bug (see the other older rename refactoring
threads...). - Just wanted to point out (since Adam asked so before...) that
it effects you also, when you import and recompile workspace plugins from
the Eclipse SDK distribution instead of the CVS repository way via the 1.4
compiler compliance level.
Valentino
"Olivier Thomann" <Olivier_Thomann@ca.ibm.comNOSPAM> schrieb im Newsbeitrag
news:dlpkcv4jkk02klu8v3iofb38ddnkk3jd71@4ax.com...
> On Tue, 20 May 2003 17:29:14 +0200, "Valentino Kyriakides"
> <vkyr@nospam-ision.net> wrote:
> >I believe Stanislav is right here! - Even I use another "jdt.ui" import
> >plugin project approach, I always have to setup under the
> >"Compiler->Compliance and Classfiles" preferences seetings for the
"jdt.ui"
> >project a compiler compliance level of "1.3". If I set the compiler
> >compliance level to "1,4" for the jdt.ui project the "rename"
refactorings
> >don't work after a compilation and run in the runtime-workspace (the used
> >jvm is 1.4.1_02).
> >
> >So in sum up the rename refactorings from the jdt.ui don't work for me
with
> >a compiler compliance level of "1.4" and thus only with compliance level
> >"1.3".
> Look at bug https://bugs.eclipse.org/bugs/show_bug.cgi?id=37846.
> This is a bug in the JDT/UI refactoring code.
> --
> Olivier
|
|
|
| Re: Refactor - rename (notice) [message #32715 is a reply to message #32610] |
Tue, 20 May 2003 17:36 |
| Eclipse User |
|
|
|
Originally posted by: adam.kiezun.gmx.net.remove
> when you import and recompile workspace plugins from
> the Eclipse SDK distribution instead of the CVS repository way via the 1.4
> compiler compliance level.
eclipse is currently at the jdk 1.3 level
so i would not be surprised if other things were broken as well
eclipse 3.0 will be jdk1.4 (we will switch soon - afaiRemember we're waitning
for
a decent 1.4 implementation on some platforms)
a.
--
eclipse.org
|
|
|
Goto Forum:
Current Time: Sun May 11 08:21:53 EDT 2025
Powered by FUDForum. Page generated in 0.06092 seconds |
Home