- This topic has 14 replies, 3 voices, and was last updated 15 years, 6 months ago by
.
-
Posts
-
Hello,
I am attempting to take an existing RAD workspace and enhance it to work with MyEclipse Blue. My workspace contains a Web Service EAR project and WAR project, and associated client EAR and WAR projects. However, when I select my web service EAR project and choose “Enhance RAD Project” from the MyEclipse window, and give it the location of my WAS 6.1 install, I get a dialog that simply says “Migration of project failed. Reason: Could not migrate project.” The Details section simply says “The Enhancing Web project activity did not complete properly.” Is this a known issue? How can I get more information about why the operation failed?
Seeing as how this does not seem to work, is my only alternative to update my build paths manually, thus making the new project incompatible with RAD?
Thanks.
-Aaron
One more note. I am running MyEclipse Blue 7.1.1, and I notice that the help for this feature appears to be left over from release 6.5, and seems largely inapplicable. Are there plans to update the help pages as well? Thanks.
I am seeing the same error. Is there any update on this issue or should we just stay with RAD? My company is evaluating MyEclipse Blue edition to make a switch from RAD to MyEclipse, so this migration feature is the most important for us to make that final decision.
!ENTRY com.genuitec.eclipse.blue.projects 4 0 2009-03-27 12:01:44.239
!MESSAGE WebProject Capabilities Error:
!STACK 1
org.eclipse.core.runtime.CoreException: The .classpath file in <project name> must be writable in order for the web project conversion to succeed. Youll need to check the file out of your version control system or manually change it to writable to proceed.
at com.genuitec.eclipse.j2eedt.core.builder.WebProjectConverter.basicConvert(Unknown Source)
at com.genuitec.eclipse.j2eedt.core.builder.WebProjectConverter.convert(Unknown Source)
…snip…It’d be helpful if this message was displayed in the app dialog box. I shouldn’t have to dig through log files to find out what I need to do when something doesn’t work. Also, why can’t the app either automatically check out or hijack files it needs to modify, based on the clear case plugin preferences?
-Aaron
I am now seeing the following project-level errors in my workspace, post-enhancement.
– Project facet EAR 1.4 is not supported by target runtime WebSphere Application Server v6.1.
– Project facet Dynamic Web Module 2.4 is not supported by target runtime WebSphere Application Server v6.1.Those facets are part of Eclipse, aren’t they? I don’t think they should be tied to WAS… and in either event, I’m pretty sure they are both supported in WAS 6.1.
-Aaron
Can you try exporting RAD (unenhanced) project to zip and then importing it to a new MyEclipse workspace? So we can rule ClearCase out (it could’ve locked out some other files).
I tried this again, having copied the project structure to a different folder and made all the files read/write, and I did not get these errors anymore. MyEclipse must have been trying to edit a file that was still checked out.
When we will be converting projects to MyEclipse Blue from RAD, they will always be part of a ClearCase view. Is there a way to have MyEclipse Blue automatically check out or hijack the files it needs to change in order to do the conversion, instead of just failing with ambiguous errors?
If that is not an option at present, can you provide me with a list of files that MyEclipse Blue needs to change when converting, so I can document it for others so that they can successfully convert their RAD projects?
-Aaron
MyEclipse must have been trying to edit a file that was still checked out.
I meant to say, must have been trying to edit a file that was -not- checked out.
Perhaps I spoke too soon. As soon as I built my workspace, the facets errors reappeared. So it does not appear to be related to files being locked by ClearCase. Any other ideas?
I figured out how to get rid of these errors. I had to go into org.eclipse.wst.common.project.facet.core.xml in my .settings directories, and delete the offending facet (it was pretty easy to tell which one corresponded to the error). Is this something that the Enhance RAD Project functionality could be enhanced to detect and correct as part of the process?
