| Curious target runtime in Package Explorer [message #54848] |
Mon, 29 November 2004 15:12  |
Eclipse User |
|
|
|
Hi Newsgroup,
I just installed the last release build, and I am positivly surprised by the
step forward you made. Thanks to all developers.
Referring to the post by Dave Carlson I just can accede to the problematics
when trying to create a "New Server".
A second problem I found, which I also mentioned above
in the subject is, that my target runtime label looks like this:
%target55runtime
Do you know any reasons?
Regards Johannes Hiemer
|
|
|
|
| Re: Curious target runtime in Package Explorer [message #54956 is a reply to message #54902] |
Tue, 30 November 2004 10:44  |
| Eclipse User |
|
|
|
Hello Johannes and Tim,
I need to do more tests to reproduce, but it seems that if I have only the
Tomcat server runtime defined in preferences (I used tomcat 5.0), then I
cannot add a new server to the Servers view. Selecting the New > Server
menu in the view does nothing. However, after I also defined JBoss runtime
in the preferences using the generic server, then the New > Server action
works in the view, and I can add both Tomcat and JBoss for deployment and
testing.
Tim, was this fixed?
Dave
"Tim deBoer" <deboer@ca.ibm.com> wrote in message
news:cog279$78u$1@www.eclipse.org...
> Hi Johannes,
>
> This is just a missing string, and it should read "Tomcat v5.5 runtime".
> The
> committer & developer who dropped in the initial Tomcat v5.5 support just
> missed this string in their testing.
>
> I've already fixed it in the new Server Tools API drop, which will be
> happening at the end of this week right after the integration build.
>
>
|
|
|
|
|
|
| Re: Curious target runtime in Package Explorer [message #55382 is a reply to message #55355] |
Fri, 03 December 2004 22:05 |
| Eclipse User |
|
|
|
On Fri, 3 Dec 2004 09:43:29 +0100, Johannes Hiemer <jhiemer@web.de> wrote:
> If todays integration build works...
> A status marked with cross means that it does not work,or?
>
> Bye Johannes
>
It does mean there was some problem, but may not invalidate the whole build.
If you click on the 'x', you'll see the detailed JUnit and Compile logs, and
you can decided from that if it looks worth trying.
|
|
|
Powered by
FUDForum. Page generated in 0.03754 seconds
Home