[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_49852 ] Barry Kaplan commented on MNG-955: -- I agree with Rafal, direct project references is critical. And since eclipse already does not have any clean way to seperate dependency types then yes, all the libraries in a referenced project should be exported and hence available the referencing project. The eclipse plugin seems to imply that it already will do this. But this is not what I am seeing. I get only jar references via the local repository. For us, this is pretty a show-stopper. My team won't use maven if it means they can't directly navigate in eclipse. (Well, at least it means that eclipse project will need to be manually created.) There should be possible to use artifacts instead of project references in multi module projects Key: MNG-955 URL: http://jira.codehaus.org/browse/MNG-955 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Reporter: Kaare Nilsen Assignee: Edwin Punzalan Fix For: 2.0.1 Attachments: MNG-955-maven-eclipse-plugin.patch One of the fine things with maven is that one can have several modules in a project. But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact. As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse. I think this should be an option. e.g. useProjectReferencetrue/useProjectReference with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_49853 ] Barry Kaplan commented on MNG-955: -- Wait, now I'm confused. This issue seems to imply that project references will always be used if version matches. If so, I can't get this to work. There should be possible to use artifacts instead of project references in multi module projects Key: MNG-955 URL: http://jira.codehaus.org/browse/MNG-955 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Reporter: Kaare Nilsen Assignee: Edwin Punzalan Fix For: 2.0.1 Attachments: MNG-955-maven-eclipse-plugin.patch One of the fine things with maven is that one can have several modules in a project. But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact. As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse. I think this should be an option. e.g. useProjectReferencetrue/useProjectReference with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_49891 ] Kaare Nilsen commented on MNG-955: -- hia. i really don't see why we have to make this so difficult. Let ut realize that there are people out there with different requirements. I think letting the user decide using a configurationoption like the one i have proposed in the issue is the best solution. then people who think it is critically important that one could navigate between projects directly do so, and the one of us who would like to do so most of the time, but also have the need of totally decoupling the project some times, do so also. At least for this plugin then the discussion about to use references or not, the answer then simply would be.. well anyway you like it my friend ;) There should be possible to use artifacts instead of project references in multi module projects Key: MNG-955 URL: http://jira.codehaus.org/browse/MNG-955 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Reporter: Kaare Nilsen Assignee: Edwin Punzalan Fix For: 2.0.1 Attachments: MNG-955-maven-eclipse-plugin.patch One of the fine things with maven is that one can have several modules in a project. But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact. As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse. I think this should be an option. e.g. useProjectReferencetrue/useProjectReference with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_49076 ] Brett Porter commented on MNG-955: -- what are the thoughts on this patch then? Looking at it, I wonder if it might mean that both the libraries and project references get included, which would not be correct, but I'm not certain. my impression is that it should use the project reference when the versions match, but use the repository artifact if not (this is consistent with the full reactor behaviour). There should be possible to use artifacts instead of project references in multi module projects Key: MNG-955 URL: http://jira.codehaus.org/browse/MNG-955 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Reporter: Kaare Nilsen Assignee: Edwin Punzalan Fix For: 2.0.1 Attachments: MNG-955-maven-eclipse-plugin.patch One of the fine things with maven is that one can have several modules in a project. But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact. As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse. I think this should be an option. e.g. useProjectReferencetrue/useProjectReference with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_48733 ] Mark Hobson commented on MNG-955: - I also have doubts about eclipse project references - see my comments on MNG-827, which is a related issue. I think the point-and-click navigation advantage is a red herring, since strictly speaking this should be implemented via source artifacts. There should be possible to use artifacts instead of project references in multi module projects Key: MNG-955 URL: http://jira.codehaus.org/browse/MNG-955 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Reporter: Kaare Nilsen Assignee: Edwin Punzalan Fix For: 2.0 Attachments: MNG-955-maven-eclipse-plugin.patch One of the fine things with maven is that one can have several modules in a project. But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact. As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse. I think this should be an option. e.g. useProjectReferencetrue/useProjectReference with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-955) There should be possible to use artifacts instead of project references in multi module projects
[ http://jira.codehaus.org/browse/MNG-955?page=comments#action_48424 ] Rafal Krzewski commented on MNG-955: Using eclipse project references is the right thing to do in 99% cases IMO. It gives you point-and-click navigation over the up-to-date sources. You could use resource sets to limit the number of projects displayed in the navigators, or try the upcoming Mylar plugin. The option to handle the remaining 1% border cases would be nice though, M1 version has such functionality: eclipse.dependencyfalse/eclipse.dependency property on a a project's dependency item. There should be possible to use artifacts instead of project references in multi module projects Key: MNG-955 URL: http://jira.codehaus.org/browse/MNG-955 Project: Maven 2 Type: Bug Components: maven-eclipse-plugin Reporter: Kaare Nilsen Fix For: 2.0-beta-4 One of the fine things with maven is that one can have several modules in a project. But in the eclipse plugin all dependent modules in the project is added as a project reference instead of using the delivered artifact. As a result i have to have all my modules (eclipse projects) opened just to compile in eclipse. I think this should be an option. e.g. useProjectReferencetrue/useProjectReference with this set to true as default, but when false, the classpath should use a reference to the jar in local repos as all other artifacts -- 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 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
