[
http://jira.codehaus.org/browse/NMAVEN-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Brett Porter updated NMAVEN-133:
--------------------------------
Fix Version/s: 0.14 (Unreleased)
> VS Addin 'Configure Maven Repository' does not work if nmaven.id is not in
> the first profile
> --------------------------------------------------------------------------------------------
>
> Key: NMAVEN-133
> URL: http://jira.codehaus.org/browse/NMAVEN-133
> Project: NMaven
> Issue Type: Bug
> Affects Versions: 0.14 (Unreleased)
> Environment: 0.14 branch + patches
> Reporter: Wendy Smoak
> Fix For: 0.14 (Unreleased)
>
>
> Depending on the contents of settings.xml, the VS Addin's "Configure Maven
> Repository" can cause Visual Studio to become unresponsive.
> If the first profile in settings.xml contains a repository with an id of
> "nmaven.id", then things seem to be fine. That profile can even have other
> repositories and/or pluginRepositories in it.
> If you add a second profile to settings.xml *above* this one, selecting
> "Configure Maven Repository" will immediately lock up Visual Studio.
--
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
