Bug 97489 - Could not create task or type of type: eclipse.refreshLocal
Summary: Could not create task or type of type: eclipse.refreshLocal
Status: NEW
Alias: None
Product: Platform
Classification: Eclipse Project
Component: Resources (show other bugs)
Version: 3.3   Edit
Hardware: PC Windows XP
: P5 enhancement (vote)
Target Milestone: ---   Edit
Assignee: Platform-Resources-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2005-05-31 10:35 EDT by Mirko J. Ploch CLA
Modified: 2019-09-06 16:08 EDT (History)
4 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Mirko J. Ploch CLA 2005-05-31 10:35:03 EDT
In Eclipse 3.1 M7 I get the error "Could not create task or type of type:
eclipse.refreshLocal" when trying to use <eclipse.refreshLocal
resource="project_name" depth="infinite"/>. It appears as a defined task in the
Ant runtime preferences.

One other thing... the table columns for the Ant runtime preference tabs
Tasks/Types/Properties always appear at a minimum width.
Comment 1 Darin Swanson CLA 2005-05-31 10:42:22 EDT
Are you running your build in the same or separate JRE (See the JRE tab for 
your Ant launch configuration)?
eclipse.refreshLocal is only available for Ant builds that occur in the same 
JRE as Eclipse. This is indicated by the Eclipse icon associated with the task 
definition in the runtime preferences.

The layout problem is fixed in Eclipse 3.1 RC1
Comment 2 Darin Swanson CLA 2005-05-31 13:06:55 EDT
If the diagnosis is incorrect please reopen with more details.
Comment 3 Mirko J. Ploch CLA 2005-05-31 14:22:42 EDT
By default Ant is setup to run in a separate JRE. I set it up as you described
to run in the same JRE and it worked. (Technically though, isn't it the same JVM
process not JRE?) Also I noticed that there is a "Refresh" tab that could be
used too. That works even if a new JVM (jre?) process is created.

Thank you!
Comment 4 Daniel Armbrust CLA 2007-07-12 16:42:03 EDT
I would like to reopen this bug as an enhancement request.  

eclipse.refreshLocal is just about completely useless in its present form, especially since the default behavior is to launch in a separate JVM.  Why can't this be added to the separate JVM environment as well when an ant build script is launched?

Also, none of the eclipse preference dialogs that show you all of these "eclipse.foo" ant tasks give you any clue that by default none of them will work.  Sticking an eclipse icon next to them really doesn't help.  It takes a web search to determine why they don't work.  Not very intuitive.

Also, what I really need is a eclipse.refreshCurrentProject task - because eclipse.refreshLocal requires you to specify a resource to refresh - and it doesn't work with a path like this: "/work/me/EclipseWorkspaces/subversion-trunk/project" - you have to provide it with just "project" - so it becomes painful to have an ant script simply refresh the current project.  I can't hardcode the project name into the ant script, since the project may be checked out under different names by different people (especially useful when checking out an older version of code, etc).



Comment 5 Darin Swanson CLA 2007-07-12 16:55:47 EDT
Thanks for your feedback Dan.

I would suggest opening a separate enhancement for the eclipse.refreshLocal task...this is provided by the platform resources team.

Is there a reason you cannot use the Refresh tab for your particular Ant build to designate the resources to refresh?
Do you have any suggestions on better indication in the preference pages?
Comment 6 Daniel Armbrust CLA 2007-07-26 11:58:20 EDT
I guess it didn't automatically add me to the CC list - whoops.

The refresh tab can work, but it is yet more steps that have to be taken every single time a project is checked out.  And it seems like it should be avoidable - I dislike manual steps.

As far as the preferences pages, if refreshLocal was made available in all cases when an ant script was run from eclipse, then there wouldn't be any need for user notification that it won't alway work.

I'll switch this request over to the resources team, hopefully it goes to the right place.
Comment 7 Eclipse Webmaster CLA 2019-09-06 16:08:39 EDT
This bug hasn't had any activity in quite some time. Maybe the problem got resolved, was a duplicate of something else, or became less pressing for some reason - or maybe it's still relevant but just hasn't been looked at yet.

If you have further information on the current state of the bug, please add it. The information can be, for example, that the problem still occurs, that you still want the feature, that more information is needed, or that the bug is (for whatever reason) no longer relevant.