You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stephen Duncan Jr (JIRA)" <ji...@codehaus.org> on 2009/04/14 15:08:54 UTC
[jira] Created: (MECLIPSE-552) Autodiscovery of projects
dependencies in the workspace should be deactivated by default
Autodiscovery of projects dependencies in the workspace should be deactivated by default
----------------------------------------------------------------------------------------
Key: MECLIPSE-552
URL: http://jira.codehaus.org/browse/MECLIPSE-552
Project: Maven 2.x Eclipse Plugin
Issue Type: Bug
Components: Core : Dependencies resolution and build path (.classpath)
Affects Versions: 2.6
Reporter: Stephen Duncan Jr
Autodiscovery of project dependencies in the workspace doesn't work well enough to be turned on by default, and it creates surprising breakages compared to the prior behavior of the maven-eclipse-plugin. See http://www.nabble.com/maven-eclipse-plugin-2.6-project-references-td23025400.html for more details.
--
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
[jira] Updated: (MECLIPSE-552) Autodiscovery of projects
dependencies in the workspace should be deactivated by default
Posted by "Tomás Pollak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomás Pollak updated MECLIPSE-552:
----------------------------------
Attachment: MECLIPSE-552-proposed-change.patch
I am now attaching a patch with a proposed change, and its unit tests. It adds a field to the plugin called discoverWorkspaceProjects, defaults to true. If set to false, it will skip looking for the projects in the workspace.
> Autodiscovery of projects dependencies in the workspace should be deactivated by default
> ----------------------------------------------------------------------------------------
>
> Key: MECLIPSE-552
> URL: http://jira.codehaus.org/browse/MECLIPSE-552
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Affects Versions: 2.6
> Reporter: Stephen Duncan Jr
> Attachments: MECLIPSE-552-current-behaviour.patch, MECLIPSE-552-proposed-change.patch
>
>
> Autodiscovery of project dependencies in the workspace doesn't work well enough to be turned on by default, and it creates surprising breakages compared to the prior behavior of the maven-eclipse-plugin. See http://www.nabble.com/maven-eclipse-plugin-2.6-project-references-td23025400.html for more details.
--
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
[jira] Updated: (MECLIPSE-552) Autodiscovery of projects
dependencies in the workspace should be deactivated by default
Posted by "Tomás Pollak (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MECLIPSE-552?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Tomás Pollak updated MECLIPSE-552:
----------------------------------
Attachment: MECLIPSE-552-current-behaviour.patch
I am attaching a patch with test cases demonstrating how the plugin works now.
> Autodiscovery of projects dependencies in the workspace should be deactivated by default
> ----------------------------------------------------------------------------------------
>
> Key: MECLIPSE-552
> URL: http://jira.codehaus.org/browse/MECLIPSE-552
> Project: Maven 2.x Eclipse Plugin
> Issue Type: Bug
> Components: Core : Dependencies resolution and build path (.classpath)
> Affects Versions: 2.6
> Reporter: Stephen Duncan Jr
> Attachments: MECLIPSE-552-current-behaviour.patch
>
>
> Autodiscovery of project dependencies in the workspace doesn't work well enough to be turned on by default, and it creates surprising breakages compared to the prior behavior of the maven-eclipse-plugin. See http://www.nabble.com/maven-eclipse-plugin-2.6-project-references-td23025400.html for more details.
--
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