[ http://jira.codehaus.org/browse/MNGECLIPSE-124?page=comments#action_74435 
] 
            
Tim Hedger commented on MNGECLIPSE-124:
---------------------------------------

Having just come across the same problem I can see where both Phillipe and 
Martin are coming from on this issue.  The plugin does work fine; you can use a 
local repository, but the problem is you have to put the settings.xml config 
file for Maven in a specific place (the location specified by the property 
${user.home}/.m2/settings.xml) before you can run the plugin in Eclipse to 
specify where you want the repository to be.  The issue from a maven 
perspective being that the master configuration for maven is in the conf 
subdirectory under the maven installation.  So if, as I do, you have your 
configuration for your repository and proxy etc in that file (e.g. 
c:\maven-2.0.4\conf\settings.xml) the Eclipse plugin doesn't look there - it 
insists that the settings.xml file in under ${user.home} - so in my case I have 
to duplicate it.  When I do that it works fine.
I think a worthwhile enhancement to the plugin would be to look for a 
settings.xml file in the conf directory under the maven installation and use 
that in preference - as maven itself does.

> Plugin fail to initialize when default maven repository folder is not 
> available
> -------------------------------------------------------------------------------
>
>                 Key: MNGECLIPSE-124
>                 URL: http://jira.codehaus.org/browse/MNGECLIPSE-124
>             Project: Maven 2.x Extension for Eclipse
>          Issue Type: Bug
>    Affects Versions: 0.0.7
>         Environment: Windows XP Professional SP2
> JSE v1.5.0-06
> Eclipse 3.2RC4
>            Reporter: Douglas WF Acheson
>         Attachments: .log
>
>
> This is this error when I try to go to the Maven2 preferences :
> Plug-in org.maven.ide.eclipse was unable to load class 
> org.maven.ide.eclipse.preferences.Maven2PreferencePage.
> As well, I an not able to associate a project with maven2 when using the RMB 
> context menu for a project .  I get a popup window with the following
> The chosen operation is not currently available

-- 
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