[jira] Commented: (MJAVADOC-215) warning proxyHost' is deprecated since 2.4
[ http://jira.codehaus.org/browse/MJAVADOC-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161016#action_161016 ] Jochen Hinrichsen commented on MJAVADOC-215: Same problem, same environment. I could revert to 2.4 but 2.5 has this very nice project.build.sourceEncoding feature. Ok, it's WARNING, not ERROR, but for audit issues i prefer clean build logs. > warning proxyHost' is deprecated since 2.4 > -- > > Key: MJAVADOC-215 > URL: http://jira.codehaus.org/browse/MJAVADOC-215 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5 > Environment: mvn 2.0.9 > jdk 1.5 >Reporter: Andreas Höhmann > > [WARNING] The Javadoc plugin parameter 'proxyHost' is deprecated since 2.4. > Please configure an active proxy in your settings.xml. > i dont define any proxyhost in the plugin-configuration and i have define a > proxy in my settings.xml - whats the problem? -- 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] Commented: (MJAVADOC-215) warning proxyHost' is deprecated since 2.4
[ http://jira.codehaus.org/browse/MJAVADOC-215?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=161503#action_161503 ] Jochen Hinrichsen commented on MJAVADOC-215: Tested against 2.5.1-SNAPSHOT, works. Thanks! > warning proxyHost' is deprecated since 2.4 > -- > > Key: MJAVADOC-215 > URL: http://jira.codehaus.org/browse/MJAVADOC-215 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5 > Environment: mvn 2.0.9 > jdk 1.5 >Reporter: Andreas Höhmann >Assignee: Benjamin Bentmann > Fix For: 2.5.1 > > > [WARNING] The Javadoc plugin parameter 'proxyHost' is deprecated since 2.4. > Please configure an active proxy in your settings.xml. > i dont define any proxyhost in the plugin-configuration and i have define a > proxy in my settings.xml - whats the problem? -- 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] Commented: (MNG-3685) Dependency can't be resolved but has been found in the reactor.
[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=172533#action_172533 ] Jochen Hinrichsen commented on MNG-3685: Attached a sample project. It consists of two modules, module-1 depending on module-common. Executing 'mvn release:prepare' produces: [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Module Common [INFO] Module #1 [INFO] Simple Maven Multi-Module Project [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building Simple Maven Multi-Module Project [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] Downloading: (some repo) Downloading: (more repos) [WARNING] The dependency: name.hinrichsen.jochen:module-common:jar:1 can't be resolved but has been found in the reactor. This dependency has been excluded from the plugin execution. You should rerun this mojo after executing mvn install. [INFO] [release:prepare] [INFO] [ERROR] BUILD FAILURE I tried both maven 2.0.8, 2.0.10 and 2.1.0 - same problem. I also ran the sonatype 'Definitive Guide' multi-module example in chapter 6 - same problem. Not sure if this is a release plugin or a maven issue. The proposed solution from thread http://www.mail-archive.com/us...@maven.apache.org/msg75486.html is to make the release plugin execute an 'install' lifecycle: clean install Also does not work for me. > Dependency can't be resolved but has been found in the reactor. > --- > > Key: MNG-3685 > URL: http://jira.codehaus.org/browse/MNG-3685 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Jörg Hohwiller > Fix For: 2.0.11 > > Attachments: sample-MNG-3685.tgz > > > Since I upgraded maven to 2.0.9, I get messages like the following endlessly: > Downloading: > http://m-m-m.sourceforge.net/repository/net/sf/m-m-m/mmm-util-core/1.0.2-SNAPSHOT/mmm-util-core-1.0.2-SNAPSHOT.jar > [WARNING] The dependency: net.sf.m-m-m:mmm-util-core:jar:1.0.2-SNAPSHOT can't > be resolved but has been found in the reactor. > This dependency has been excluded from the plugin execution. You should rerun > this mojo after executing mvn install. > This also happens, if someone checks out the project and does "mvn > eclipse:eclipse". The process still works but takes extraordinary long to > proceed because it scales about n^2 with n beiing the number of modules in > your reactor. > You should also take into account that "mvn install" aborts if some tests > fail. > Sorry to say so, but this behaviour of maven is absolutely inacceptable. I > hope there is a chance to fix this in the next release(s). Thanks! -- 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: (MNG-3685) Dependency can't be resolved but has been found in the reactor.
[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jochen Hinrichsen updated MNG-3685: --- Attachment: sample-MNG-3685.tgz > Dependency can't be resolved but has been found in the reactor. > --- > > Key: MNG-3685 > URL: http://jira.codehaus.org/browse/MNG-3685 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Jörg Hohwiller > Fix For: 2.0.11 > > Attachments: sample-MNG-3685.tgz > > > Since I upgraded maven to 2.0.9, I get messages like the following endlessly: > Downloading: > http://m-m-m.sourceforge.net/repository/net/sf/m-m-m/mmm-util-core/1.0.2-SNAPSHOT/mmm-util-core-1.0.2-SNAPSHOT.jar > [WARNING] The dependency: net.sf.m-m-m:mmm-util-core:jar:1.0.2-SNAPSHOT can't > be resolved but has been found in the reactor. > This dependency has been excluded from the plugin execution. You should rerun > this mojo after executing mvn install. > This also happens, if someone checks out the project and does "mvn > eclipse:eclipse". The process still works but takes extraordinary long to > proceed because it scales about n^2 with n beiing the number of modules in > your reactor. > You should also take into account that "mvn install" aborts if some tests > fail. > Sorry to say so, but this behaviour of maven is absolutely inacceptable. I > hope there is a chance to fix this in the next release(s). Thanks! -- 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] Commented: (MNG-3685) Dependency can't be resolved but has been found in the reactor.
[ http://jira.codehaus.org/browse/MNG-3685?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=175740#action_175740 ] Jochen Hinrichsen commented on MNG-3685: Any new insights regarding this issue after one month? > Dependency can't be resolved but has been found in the reactor. > --- > > Key: MNG-3685 > URL: http://jira.codehaus.org/browse/MNG-3685 > Project: Maven 2 > Issue Type: Bug >Affects Versions: 2.0.9 >Reporter: Jörg Hohwiller > Fix For: 2.0.11 > > Attachments: sample-MNG-3685.tgz > > > Since I upgraded maven to 2.0.9, I get messages like the following endlessly: > Downloading: > http://m-m-m.sourceforge.net/repository/net/sf/m-m-m/mmm-util-core/1.0.2-SNAPSHOT/mmm-util-core-1.0.2-SNAPSHOT.jar > [WARNING] The dependency: net.sf.m-m-m:mmm-util-core:jar:1.0.2-SNAPSHOT can't > be resolved but has been found in the reactor. > This dependency has been excluded from the plugin execution. You should rerun > this mojo after executing mvn install. > This also happens, if someone checks out the project and does "mvn > eclipse:eclipse". The process still works but takes extraordinary long to > proceed because it scales about n^2 with n beiing the number of modules in > your reactor. > You should also take into account that "mvn install" aborts if some tests > fail. > Sorry to say so, but this behaviour of maven is absolutely inacceptable. I > hope there is a chance to fix this in the next release(s). Thanks! -- 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
