Closed GoogleCodeExporter closed 9 years ago
Can you include the full class path? I need to get a better idea of what was
passed
to WebAppClassLoader.addClassPath(). If you don't want to publish it, please
send me
email directly.
It occurs to me that one problem with the current design may be that the class
path
will become too long to fit on the command line; this means I should probably
introduce a temporary file used to communicate the configuration to
Bootstrap.main().
Original comment by James.Sy...@gmail.com
on 4 May 2009 at 11:45
It seems that Unix style classpath with ":" delimiters does not work. In
debugger I can see that
ProjectClassLoader(WebAppClassLoader).addClassPath(String) is using
StringTokenizer with ",;" delimiters.
Original comment by pasi.hei...@gmail.com
on 5 May 2009 at 10:09
OK, that is very helpful info.
Original comment by James.Sy...@gmail.com
on 5 May 2009 at 12:15
Issue 26 has been merged into this issue.
Original comment by James.Sy...@gmail.com
on 5 May 2009 at 12:17
Why is this issue Priority Medium? It disables unix-users to use the new plugin
version!
Original comment by phoetm...@googlemail.com
on 6 May 2009 at 8:29
this is really bad, we are all using Linux in our company and this prevents us
from
using the new version :(
Original comment by klaas.pr...@googlemail.com
on 6 May 2009 at 8:42
It's medium because I didn't think to change it. :-)
I'm planning to release a fix for this next (when a couple of free hours are
available, so it should be this week).
Original comment by James.Sy...@gmail.com
on 6 May 2009 at 10:59
I would appreciate it! We are suffering the lack of ssl-support of the old
version of
the plugin. The new support would enable us to remove a lot of
tapestry-ssl-hacks...
Original comment by phoetm...@googlemail.com
on 6 May 2009 at 11:44
Is there a way to change the title of the bug-report? I would like to see
something
bug-related. This would help finding the issue and prevent duplicate issues.
Original comment by phoetm...@googlemail.com
on 6 May 2009 at 11:45
im having the same issue here, is there a way to downgrade the version of putty
so i
can still work ?
Original comment by fefewa...@gmail.com
on 6 May 2009 at 8:11
Responding to fefewachs, comment 10:
How one removes (downgrades) is dependent upon the version of Eclipse. I tend
to
install each feature in its own extension directory, and then use link files to
add
or remove them from a particular configuration.
What version of Eclipse are using?
Original comment by James.Sy...@gmail.com
on 7 May 2009 at 12:10
[deleted comment]
[deleted comment]
Just uninstall the plugin from eclipse and than reinstall using version 1.0.1.
I did just that yesterday.
Original comment by phoetm...@googlemail.com
on 7 May 2009 at 7:13
Fixed in 1.1.1.
Original comment by James.Sy...@gmail.com
on 7 May 2009 at 12:26
Great Stuff! Jetty starts up using right path, but now i have different error
:-(
Original comment by phoetm...@googlemail.com
on 7 May 2009 at 2:34
Original issue reported on code.google.com by
sebastie...@gmail.com
on 4 May 2009 at 8:22