[project lombok] My eclipse doesn't start anymore with 0.9.2
1,009 views
Skip to first unread message
Maaartin
May 21, 2010, 1:59:30 AM5/21/10
to Project Lombok
I've just downloaded Lombok 0.9.2 and wanted to install it over my old
0.8.5.
I copied it into my eclipse directory and started from there, which
was wrong, since it truncated itself to length 0, most probably
because of not recognizing that the destination and source files are
the same. This is a minor issue, I can live with.
The real problem is my eclipse not starting anymore. The eclipse.ini
looks just like it was before, ending with
-javaagent:lombok.jar
-Xbootclasspath/a:lombok.jar
that's fine. I get no logfile, neither in eclipse directory, nor in
configuration, nor in workspace. I get no output to console although I
tried all the options -console, -consoleLog, and -debug (both
individually and together). I tried -cleanup as well, whatever it
does. Eclipse just exits with error code 1 and that's the only
information I can get.
Removing the javaagent line helps, so the problem is definitely
related to lombok. I'm using XP64, eclipse 3.5.0, and Java 1.6.0_13-
b03.
--
You received this message because you are subscribed to the Google
Groups group for http://projectlombok.org/
To post to this group, send email to project...@googlegroups.com
To unsubscribe from this group, send email to
project-lombo...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/project-lombok?hl=en
0.8.5.
I copied it into my eclipse directory and started from there, which
was wrong, since it truncated itself to length 0, most probably
because of not recognizing that the destination and source files are
the same. This is a minor issue, I can live with.
The real problem is my eclipse not starting anymore. The eclipse.ini
looks just like it was before, ending with
-javaagent:lombok.jar
-Xbootclasspath/a:lombok.jar
that's fine. I get no logfile, neither in eclipse directory, nor in
configuration, nor in workspace. I get no output to console although I
tried all the options -console, -consoleLog, and -debug (both
individually and together). I tried -cleanup as well, whatever it
does. Eclipse just exits with error code 1 and that's the only
information I can get.
Removing the javaagent line helps, so the problem is definitely
related to lombok. I'm using XP64, eclipse 3.5.0, and Java 1.6.0_13-
b03.
--
You received this message because you are subscribed to the Google
Groups group for http://projectlombok.org/
To post to this group, send email to project...@googlegroups.com
To unsubscribe from this group, send email to
project-lombo...@googlegroups.com
For more options, visit this group at
http://groups.google.com/group/project-lombok?hl=en
Reinier Zwitserloot
May 21, 2010, 10:04:39 AM5/21/10
to Project Lombok
It sounds like the agent loading itself is perhaps failing. There
should be eclipsec.exe or eclipsec.bat or some such, which should give
you the output. I'm guessing it'll say something along the lines of
agent not found. -console and friends don't work on windows because
unless java.exe instead of javaw.exe is used, there's no terminal to
write to. Apps can't go "Oh, hey, look, a terminal! I'll use that!"
like in linux and os x. I believe eclipsec addresses that is (and you
might ALSO have to pass in -console, I'm not sure, I don't have a
windows machine here to test this on).
If this is no help I'll fire up a virtual machine image and see if I
can reproduce what you're seeing, or if I can figure out how to make
eclipse output messages. I'm positive I've managed it before.
On May 21, 7:59 am, Maaartin <grajc...@seznam.cz> wrote:
> I've just downloaded Lombok 0.9.2 and wanted to install it over my old
> 0.8.5.
>
> I copied it into my eclipse directory and started from there, which
> was wrong, since it truncated itself to length 0, most probably
> because of not recognizing that the destination and source files are
> the same. This is a minor issue, I can live with.
>
> The real problem is my eclipse not starting anymore. The eclipse.ini
> looks just like it was before, ending with
> -javaagent:lombok.jar
> -Xbootclasspath/a:lombok.jar
> that's fine. I get no logfile, neither in eclipse directory, nor in
> configuration, nor in workspace. I get no output to console although I
> tried all the options -console, -consoleLog, and -debug (both
> individually and together). I tried -cleanup as well, whatever it
> does. Eclipse just exits with error code 1 and that's the only
> information I can get.
>
> Removing the javaagent line helps, so the problem is definitely
> related to lombok. I'm using XP64, eclipse 3.5.0, and Java 1.6.0_13-
> b03.
>
> --
> You received this message because you are subscribed to the Google
> Groups group forhttp://projectlombok.org/
should be eclipsec.exe or eclipsec.bat or some such, which should give
you the output. I'm guessing it'll say something along the lines of
agent not found. -console and friends don't work on windows because
unless java.exe instead of javaw.exe is used, there's no terminal to
write to. Apps can't go "Oh, hey, look, a terminal! I'll use that!"
like in linux and os x. I believe eclipsec addresses that is (and you
might ALSO have to pass in -console, I'm not sure, I don't have a
windows machine here to test this on).
If this is no help I'll fire up a virtual machine image and see if I
can reproduce what you're seeing, or if I can figure out how to make
eclipse output messages. I'm positive I've managed it before.
On May 21, 7:59 am, Maaartin <grajc...@seznam.cz> wrote:
> I've just downloaded Lombok 0.9.2 and wanted to install it over my old
> 0.8.5.
>
> I copied it into my eclipse directory and started from there, which
> was wrong, since it truncated itself to length 0, most probably
> because of not recognizing that the destination and source files are
> the same. This is a minor issue, I can live with.
>
> The real problem is my eclipse not starting anymore. The eclipse.ini
> looks just like it was before, ending with
> -javaagent:lombok.jar
> -Xbootclasspath/a:lombok.jar
> that's fine. I get no logfile, neither in eclipse directory, nor in
> configuration, nor in workspace. I get no output to console although I
> tried all the options -console, -consoleLog, and -debug (both
> individually and together). I tried -cleanup as well, whatever it
> does. Eclipse just exits with error code 1 and that's the only
> information I can get.
>
> Removing the javaagent line helps, so the problem is definitely
> related to lombok. I'm using XP64, eclipse 3.5.0, and Java 1.6.0_13-
> b03.
>
> --
> You received this message because you are subscribed to the Google
Maaartin
May 21, 2010, 10:41:08 AM5/21/10
to Project Lombok
On May 21, 4:04 pm, Reinier Zwitserloot <reini...@gmail.com> wrote:
> It sounds like the agent loading itself is perhaps failing. There
> should be eclipsec.exe or eclipsec.bat or some such, which should give
> you the output. I'm guessing it'll say something along the lines of
> agent not found. -console and friends don't work on windows because
> unless java.exe instead of javaw.exe is used, there's no terminal to
> write to. Apps can't go "Oh, hey, look, a terminal! I'll use that!"
> like in linux and os x. I believe eclipsec addresses that is (and you
> might ALSO have to pass in -console, I'm not sure, I don't have a
> windows machine here to test this on).
You're lucky. Unfortunately, I must use this OS-like thing. The funny
> It sounds like the agent loading itself is perhaps failing. There
> should be eclipsec.exe or eclipsec.bat or some such, which should give
> you the output. I'm guessing it'll say something along the lines of
> agent not found. -console and friends don't work on windows because
> unless java.exe instead of javaw.exe is used, there's no terminal to
> write to. Apps can't go "Oh, hey, look, a terminal! I'll use that!"
> like in linux and os x. I believe eclipsec addresses that is (and you
> might ALSO have to pass in -console, I'm not sure, I don't have a
> windows machine here to test this on).
think about eclipsec.exe: It opens a console, but it gets closed
immediately after eclipse failing to start. However, I solved the
problem: I was starting eclipse from a different directory and
lombok.jar couldn't be found. It worked before, so probably there was
an absolute path in eclipse.ini which was overwritten during
installation or something like this. I was confused since it happened
just after the installation (I have tried even the absolute path, but
I must have made a typo therein).
> If this is no help I'll fire up a virtual machine image and see if I
> can reproduce what you're seeing, or if I can figure out how to make
> eclipse output messages. I'm positive I've managed it before.
Reinier Zwitserloot
May 21, 2010, 8:50:28 PM5/21/10
to Project Lombok
The lombok installer explicitly does NOT use absolute paths because
that would mean you can't move your eclipse install around anymore.
Except on linux, where on some versions of the JDK for some reason it
didn't work without an absolute path. We did, I believe, move the
directory we normally put lombok in, and perhaps that's the
explanation here. You could try uninstalling lombok and reinstalling
it (that will actually remove the -Xbootclasspath and -agent lines
from your eclipse.ini), but if everything is in working order now,
that's great to hear.
> Groups group forhttp://projectlombok.org/
that would mean you can't move your eclipse install around anymore.
Except on linux, where on some versions of the JDK for some reason it
didn't work without an absolute path. We did, I believe, move the
directory we normally put lombok in, and perhaps that's the
explanation here. You could try uninstalling lombok and reinstalling
it (that will actually remove the -Xbootclasspath and -agent lines
from your eclipse.ini), but if everything is in working order now,
that's great to hear.
Maaartin
May 22, 2010, 10:15:30 AM5/22/10
to Project Lombok
On May 22, 2:50 am, Reinier Zwitserloot <reini...@gmail.com> wrote:
> The lombok installer explicitly does NOT use absolute paths because
> that would mean you can't move your eclipse install around anymore.
Apparently, the path is relative to the current working directory
> The lombok installer explicitly does NOT use absolute paths because
> that would mean you can't move your eclipse install around anymore.
instead of the eclipse installation directory, so no solution is
ideal. It would be nice if the path would be relative to the
installation directory, but this is something what only eclipse could
do. Getting *any* error message would be nearly as good, but I see no
way how you could do it.
> Except on linux, where on some versions of the JDK for some reason it
> didn't work without an absolute path. We did, I believe, move the
> directory we normally put lombok in, and perhaps that's the
> explanation here. You could try uninstalling lombok and reinstalling
> it (that will actually remove the -Xbootclasspath and -agent lines
> from your eclipse.ini), but if everything is in working order now,
> that's great to hear.
are some problems.
1. With "save actions" including "sort members" I get sometimes a big
mess like in
http://dl.dropbox.com/u/4971686/SaveActions.txt
2. With @Synchronized on the main method I always get a NPE, except
when the method is empty.
3. The same holds for all static methods.
4. Extract method doesn't work on any part of a method annotated with
@Synchronized.
I tried to compile lombok, and get a strange error: It fails while
looking for
E:\work\java\lombok.patcher\dist\lombok-patcher.jar
while compiling the patcher created
E:\work\java\lombok-patcher\dist\lombok.patcher.jar
The only difference is the dash vs. the dot. I can easily fix it, but
what's the proper name? Is there a description how to build and debug
lombok?
Reinier Zwitserloot
May 22, 2010, 7:22:30 PM5/22/10
to Project Lombok
The lombok.patcher.jar vs. lombok-patcher.jar is a known issue, we're
right in the middle of some major refactoring.
That particular refactoring is partly to fix problems with AST-based
eclipse scripts such as actions-on-save and refactor scripts :P
Though, @Synchronized on a main method or any other static method
definitely should not NPE. Is this NPE occurring during e.g. actions-
on-save or right away when you mark any static method as
@Synchronized?
On May 22, 4:15 pm, Maaartin <grajc...@seznam.cz> wrote:
> On May 22, 2:50 am, Reinier Zwitserloot <reini...@gmail.com> wrote:
>
> > The lombok installer explicitly does NOT use absolute paths because
> > that would mean you can't move your eclipse install around anymore.
>
> Apparently, the path is relative to the current working directory
> instead of the eclipse installation directory, so no solution is
> ideal. It would be nice if the path would be relative to the
> installation directory, but this is something what only eclipse could
> do. Getting *any* error message would be nearly as good, but I see no
> way how you could do it.
>
> > Except on linux, where on some versions of the JDK for some reason it
> > didn't work without an absolute path. We did, I believe, move the
> > directory we normally put lombok in, and perhaps that's the
> > explanation here. You could try uninstalling lombok and reinstalling
> > it (that will actually remove the -Xbootclasspath and -agent lines
> > from your eclipse.ini), but if everything is in working order now,
> > that's great to hear.
>
> Everything I use works now. I've just tried @Synchronized and there
> are some problems.
>
> 1. With "save actions" including "sort members" I get sometimes a big
> mess like inhttp://dl.dropbox.com/u/4971686/SaveActions.txt
right in the middle of some major refactoring.
That particular refactoring is partly to fix problems with AST-based
eclipse scripts such as actions-on-save and refactor scripts :P
Though, @Synchronized on a main method or any other static method
definitely should not NPE. Is this NPE occurring during e.g. actions-
on-save or right away when you mark any static method as
@Synchronized?
On May 22, 4:15 pm, Maaartin <grajc...@seznam.cz> wrote:
> On May 22, 2:50 am, Reinier Zwitserloot <reini...@gmail.com> wrote:
>
> > The lombok installer explicitly does NOT use absolute paths because
> > that would mean you can't move your eclipse install around anymore.
>
> Apparently, the path is relative to the current working directory
> instead of the eclipse installation directory, so no solution is
> ideal. It would be nice if the path would be relative to the
> installation directory, but this is something what only eclipse could
> do. Getting *any* error message would be nearly as good, but I see no
> way how you could do it.
>
> > Except on linux, where on some versions of the JDK for some reason it
> > didn't work without an absolute path. We did, I believe, move the
> > directory we normally put lombok in, and perhaps that's the
> > explanation here. You could try uninstalling lombok and reinstalling
> > it (that will actually remove the -Xbootclasspath and -agent lines
> > from your eclipse.ini), but if everything is in working order now,
> > that's great to hear.
>
> Everything I use works now. I've just tried @Synchronized and there
> are some problems.
>
> 1. With "save actions" including "sort members" I get sometimes a big
>
> 2. With @Synchronized on the main method I always get a NPE, except
> when the method is empty.
>
> 3. The same holds for all static methods.
>
> 4. Extract method doesn't work on any part of a method annotated with
> @Synchronized.
>
> I tried to compile lombok, and get a strange error: It fails while
> looking for
> E:\work\java\lombok.patcher\dist\lombok-patcher.jar
> while compiling the patcher created
> E:\work\java\lombok-patcher\dist\lombok.patcher.jar
> The only difference is the dash vs. the dot. I can easily fix it, but
> what's the proper name? Is there a description how to build and debug
> lombok?
>
> --
> You received this message because you are subscribed to the Google
> Groups group forhttp://projectlombok.org/
> 2. With @Synchronized on the main method I always get a NPE, except
> when the method is empty.
>
> 3. The same holds for all static methods.
>
> 4. Extract method doesn't work on any part of a method annotated with
> @Synchronized.
>
> I tried to compile lombok, and get a strange error: It fails while
> looking for
> E:\work\java\lombok.patcher\dist\lombok-patcher.jar
> while compiling the patcher created
> E:\work\java\lombok-patcher\dist\lombok.patcher.jar
> The only difference is the dash vs. the dot. I can easily fix it, but
> what's the proper name? Is there a description how to build and debug
> lombok?
>
> --
> You received this message because you are subscribed to the Google
Maaartin
May 23, 2010, 1:39:52 AM5/23/10
to Project Lombok
On May 23, 1:22 am, Reinier Zwitserloot <reini...@gmail.com> wrote:
> The lombok.patcher.jar vs. lombok-patcher.jar is a known issue, we're
> right in the middle of some major refactoring.
>
> That particular refactoring is partly to fix problems with AST-based
> eclipse scripts such as actions-on-save and refactor scripts :P
OK.
> The lombok.patcher.jar vs. lombok-patcher.jar is a known issue, we're
> right in the middle of some major refactoring.
>
> That particular refactoring is partly to fix problems with AST-based
> eclipse scripts such as actions-on-save and refactor scripts :P
> Though, @Synchronized on a main method or any other static method
> definitely should not NPE. Is this NPE occurring during e.g. actions-
> on-save or right away when you mark any static method as
> @Synchronized?
initialized. You find it all here:
http://dl.dropbox.com/u/4971686/100523/LombokDemo.java
http://dl.dropbox.com/u/4971686/100523/LombokDemo.class
Reply all
Reply to author
Forward
0 new messages