This Bugzilla instance is deprecated, and most Eclipse projects now use GitHub or Eclipse GitLab. Please see the deprecation plan for details.
Bug 207821 - The command ("org.eclipse.wst.server.profile/run/delete") is undefined
Summary: The command ("org.eclipse.wst.server.profile/run/delete") is undefined
Status: CLOSED FIXED
Alias: None
Product: WTP ServerTools
Classification: WebTools
Component: jst.server (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M3   Edit
Assignee: Tim deBoer CLA
QA Contact: Tim deBoer CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-29 13:45 EDT by Kaloyan Raev CLA
Modified: 2007-11-01 13:08 EDT (History)
1 user (show)

See Also:

Attachments
.log (19.82 KB, text/plain)
2007-10-29 13:45 EDT, Kaloyan Raev CLA 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Kaloyan Raev CLA 2007-10-29 13:45:03 EDT 
Created attachment 81481 [details]
.log

During the Java EE smoke test execution on the last WTP 3.0 I-build I have observed the following errors in the Error Log: 

The command ("org.eclipse.wst.server.profile") is undefined
The command ("org.eclipse.wst.server.run") is undefined
The command ("org.eclipse.wst.server.debug") is undefined

The .log file is attached for details. 

I haven't observed any functional effect of these errors. 
The errors were logged only once, but I cannot say when exactly - probably on the first time I have tried to "Run As" a Servlet.
Comment 1 Tim deBoer CLA 2007-10-29 13:53:20 EDT 
Released a fix for this last night.
Comment 2 Kaloyan Raev CLA 2007-11-01 12:07:00 EDT 
Tim, exactly the same problem occurs with the 2.0.2 smoke test candidate. 
The fix is needed there, too.
Comment 3 Kaloyan Raev CLA 2007-11-01 12:48:21 EDT 
I am sorry. I am wrong. 
It is actually bug 206810. 
I was misled by the log file.
Comment 4 Tim deBoer CLA 2007-11-01 13:08:23 EDT 
Thanks, you were worrying me that I had somehow mixed up the branches and released the new command bindings into the 2.0 stream. :)