|Re: Installation of WTP 1.5.3 from ZIP doesn't activate o.e.jem v1.2.3 [message #189961 is a reply to message #189545]
||Thu, 15 March 2007 21:25
Originally posted by: eclipse.newsgroups.javafreelancer.net|
i have essentially the same setup as the o.p. except i'm on solaris
9/sparc + i installed wtp-R-1.5.3.zip (instead of the full sdk). the other
wtp pre-reqs are the same though.
unlike the o.p. though, all my features (org.eclipse.jem.* included) are
reported as being configured properly in Help -> Software Updates ->
Manage Configuration (no red error markers for anything).
but like the o.p., when i am editing java source, the editor "[looses] its
syntax highlighting and appears as-if its treated as a regular text file".
when i go to "Window -> Preferences -> General Appearance -> Colors and
Fonts" to change stuff, the rectangular color indicator in the top r.h.
corner of the panel is white for every single item! even if i select the
color indicator and change the color, the color indicator remains white!
please, can anybody suggest a solution?
p.s. btw, does anybody know what that "Quote" button at the bottom l.h.
side of this forum's Web interface is for? it doesn't do anything in
either mozilla 1.7.13 nor msie 7!
|Re: Installation of WTP 1.5.3 from ZIP doesn't activate o.e.jem v1.2.3 [message #190008 is a reply to message #189953]
||Fri, 16 March 2007 14:12
| Darryl Miles
Registered: July 2009
Nitin Dahyabhai wrote:|
> With the JEM plugins not starting, the JSP editor itself wouldn't even
> open, but the combination you listed works fine for me with JRE
> 1.4.2_11, including the same md5sum for the jem zip. Which JRE are you
> using and are you actually on a 64-bit system?
Thanks for the reply Nitin, Yes I am on a 64bit system and using SUN JVM
$ java -version
java version "1.5.0_08"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_08-b03)
Java HotSpot(TM) 64-Bit Server VM (build 1.5.0_08-b03, mixed mode)
FYI: Eclipse will not complete its start up if you use an incorrect mix
of JVM and 32 or 64bit build of eclipse platform, this is dues to ABI
mismatch when it goes to load DLL from the Eclipse plaform. This is
because while a 64bit linux host can run 32bit programs the EXE/DLL
loader does not allow the mixing of 64 and 32bit code within the same
process. Part of the reason for this is that a 64bit CPU has a
completely different ABI which makes use of the extra general registers
in EMT64 CPU to pass the first ~4 parameters in functions calls within
registers (as opposed to 32bit which uses the stack for everything).
For clarity these are the md5sum's of where I started:
Ok I have forced a new configuration directory but kept my old workspace
to check for a problem with the configuration data. In doing this JSP
editors work correctly.
I do something slightly different with my configuration area, in that at
some point in the past I got fed up with upgrading eclipse and loosing
all my configuration settings.
This is because by default eclipse will write those configuration
settings into the executable configuration location, this being the
eclipse/configuration directory where you extracted
eclipse-SDK-3.2.2-linux-gtk-x86_64.tar.gz in my case that is
This is just not on. All personal configuration data should be
associated with the users $HOME directory (not with the shared location
where the executables are located).
So to stop this practice after installation I mark the entire eclipse
executable hierarchy as not modifiable by the userid I run eclipse as, I
run eclipse as a non-root user so "chown root.root -R /opt/eclipse" does
the trick here.
I found doing this forced the platform to start storing configuration
data in $HOME and to make sure it always used the same location after an
upgrade I give a -configuration
command line option.
I personally think that it should never write to the shared executable
location (even if the system allow it to happen) unless specifically
instructed to do so and by default it should only use the $HOME and the
workspace areas to store stuff.
So I guess in my case there is a problem with migration of the old
configuration to 1.5.3, it just does not like it and -clean does not fix
whatever it does not like.
$ ls -l /home/dlm/.eclipse
drwxrwxr-x 3 dlm dlm 4096 Jan 8 2006 org.eclipse.platform_3.1.0
drwxrwxr-x 3 dlm dlm 4096 Dec 30 2005 org.eclipse.platform_3.1.1
drwxrwxr-x 3 dlm dlm 4096 Mar 19 2006 org.eclipse.platform_3.1.2
drwxrwxr-x 5 dlm dlm 4096 Sep 22 17:41 org.eclipse.platform_3.2.0
I notice the platform version number is somehow connected with the
configuration, my problem is that the -configuration command line
directory wants the exact location which at the moment I have been using:
I actually don't want to specify this, all I really intended was to
specify that "/home/dlm/.eclipse" should be used and not
"/opt/eclipse/configuration" if it is necessary for the platform to
create org.eclipse.platform_3.2.2 then that is fine. Thats an issue I
don't want to have to manage or confront.
It would also be dandy if when first running a new version of the
platform (causing org.eclipse.platform_3.2.2 to be created, that I get a
GUI dialog to import all the configuration settings from one of the
other directories, giving a list of all previous versions it found, with
the default being the most highest version below the one we are using
now). It would be even dandier if there was an extension point which
each module owner could hook into to authorize, veto or modify
configuration directives that were being imported during this process
during that update.
Maybe I should suggest a feature enhancement for a new command line option:
Thanks for your reply knowing that it actually works for someone else
helped me isolate the problem.
Now I need to weigh up the productivity gain from upgrading to 1.5.3
over the productivity loss of loosing the entire my configuration.
Maybe I can copy a text file across manually ?
|Re: Installation of WTP 1.5.3 from ZIP doesn't activate o.e.jem v1.2.3 [message #190016 is a reply to message #189961]
||Fri, 16 March 2007 14:18
| Darryl Miles
Registered: July 2009
> but like the o.p., when i am editing java source, the editor "[looses]
> its syntax highlighting and appears as-if its treated as a regular text
"java source" ?? My post refers to "JSP Editor" which is used for
editing *.jsp files.
Please confirm if you mean *.java or *.jsp.
To verify my problem:
* Create a new DWP: New -> Project -> Web -> Dynamic Web Project
* Fill in the project name "Test", leave everything else as default.
* I found on linux there is a "I Agree" button to process, but it would
not let me press it, although my browser showed the SUN notice, I closed
the browser and clicked "I Disagree" since its the only button lit up,
but the project appear to create itself ok anyway.
* Expand the project tree for Test/WebContent
* In this directory right click and select New -> File
* For the filename use "foo.jsp"
* When the editor opens, type in "<jsp" then press Ctrl + Space (for
If the various <jsp:...> tags appear then your JSP editor is working.
Java is more fundamental and part of the base platform, so you could
only need to install eclipse-SDK-3.2.2-linux-gtk-x86_64.tar.gz to be
able to create a HelloWorld.java file and debug it.
Powered by FUDForum
. Page generated in 0.03225 seconds