[ http://jira.codehaus.org/browse/MNGECLIPSE-164?page=comments#action_70314 
] 
            
Jimisola Laursen commented on MNGECLIPSE-164:
---------------------------------------------

My mistake I thought m2eclipse managed to add the dependency but I was too fast 
there
Even with the file in edit  mode it doesn't work. Now I get the following error:

!ENTRY org.eclipse.core.resources 4 380 2006-07-20 23:42:56.536
!MESSAGE The resource tree is locked for modifications.


> Add Dependency doesn't update pom.xml when been opened prior with the 
> Perforce Eclipse Plugin (P4WSAD)
> ------------------------------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-164
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-164
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: Bug
>          Components: POM Editor
>    Affects Versions: 0.0.9
>            Reporter: Jimisola Laursen
>         Assigned To: Eugene Kuleshov
>            Priority: Minor
>
> I am using the Perforce plugin for Eclipse aka P4WSAD (Perforce is a SCM).
> My problem is that the add dependency function doesn't work if I haven't put 
> the file in "edit mode" prior to adding a dependency.
> I don't have this problem when I use JDT, AJDT and some other plugins. 
> Perhaps m2eclipse forget to "ask the SCM" to change file to "edit mode". I am 
> not familiar with the inner working of the Eclipse platform or P4WSAD, but 
> I'll be glad to assist if I can give some more feedback.
> I'll mail the Perforce support as well and tell them to look at this bug.
> !ENTRY org.maven.ide.eclipse 4 0 2006-07-20 23:26:24.361
> !MESSAGE Unable to update POM: 
> /home/jimisola/p4clients/lt/iso/main/product/xmlrpcapi/pom.xml; Could not 
> write to read-only file: /xmlrpcapi/pom.xml.
> !STACK 1
> org.eclipse.core.internal.resources.ResourceException: Could not write to 
> read-only file: /xmlrpcapi/pom.xml.
>         at 
> org.eclipse.core.internal.localstore.FileSystemResourceManager.write(FileSystemResourceManager.java:864)
>         at 
> org.eclipse.core.internal.resources.File.internalSetContents(File.java:322)
>         at org.eclipse.core.internal.resources.File.setContents(File.java:362)
>         at org.eclipse.core.internal.resources.File.setContents(File.java:462)
>         at org.maven.ide.eclipse.Maven2Plugin$2.run(Maven2Plugin.java:303)
>         at 
> org.maven.ide.eclipse.Maven2Plugin.executeInEmbedder(Maven2Plugin.java:167)
>         at 
> org.maven.ide.eclipse.Maven2Plugin.addDependency(Maven2Plugin.java:291)
>         at 
> org.maven.ide.eclipse.actions.AddDependencyAction.run(AddDependencyAction.java:50)
>         at 
> org.eclipse.ui.internal.PluginAction.runWithEvent(PluginAction.java:254)
>         at 
> org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:539)
>         at 
> org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488)
>         at 
> org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400)
>         at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
>         at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1085)
>         at 
> org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3164)
>         at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2840)
>         at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1914)
>         at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1878)
>         at 
> org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:419)
>         at 
> org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
>         at 
> org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:95)
>         at 
> org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:78)
>         at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:92)
>         at 
> org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:68)
>         at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:400)
>         at 
> org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:177)
>         at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
>         at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
>         at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
>         at java.lang.reflect.Method.invoke(Method.java:585)
>         at org.eclipse.core.launcher.Main.invokeFramework(Main.java:336)
>         at org.eclipse.core.launcher.Main.basicRun(Main.java:280)
>         at org.eclipse.core.launcher.Main.run(Main.java:977)
>         at org.eclipse.core.launcher.Main.main(Main.java:952)
> !SUBENTRY 1 org.eclipse.core.resources 4 272 2006-07-20 23:26:24.363
> !MESSAGE Could not write to read-only file: /xmlrpcapi/pom.xml.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Reply via email to