[jira] [Commented] (MDEP-649) dependency:resolve-plugins lacks includeParents user property
[
https://issues.apache.org/jira/browse/MDEP-649?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16971880#comment-16971880
]
Nick Stolwijk commented on MDEP-649:
I'm taking a shot at this.
Question: is it feasible to do something on [3]? I don't think changing the
default is a good idea and I think that having the same defaults for the same
options is a good idea. (Yes, that speaks against itself)
> dependency:resolve-plugins lacks includeParents user property
> -
>
> Key: MDEP-649
> URL: https://issues.apache.org/jira/browse/MDEP-649
> Project: Maven Dependency Plugin
> Issue Type: New Feature
> Components: resolve-plugins
>Affects Versions: 3.1.1
>Reporter: Dennis Schridde
>Priority: Major
>
> `dependency:resolve` has an `includeParents` user property [1] which
> `dependency:resolve-plugins` is lacking [2]. This makes it difficult to
> generate a complete list of all (JARs and) POMs required to build a project
> (with dependencies and plugins and their dependencies).
> P.S. `dependency:get` appears to have a similar shortcoming: It can resolve
> dependencies recursively (`{{transitive}}=true`, enabled by default [3]), but
> it lacks a `{{includeParents}}` user property.
> [1]:
> [https://maven.apache.org/plugins/maven-dependency-plugin/resolve-mojo.html#includeParents]
> [2]:
> [https://maven.apache.org/plugins/maven-dependency-plugin/resolve-plugins-mojo.html]
> [3]: Which BTW is inverse to the disabled-by-default `{{excludeTransitive}}`
> user property of `dependency:resolve`
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] (MCHECKSTYLE-189) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10
[ https://jira.codehaus.org/browse/MCHECKSTYLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320480#comment-320480 ] Nick Stolwijk commented on MCHECKSTYLE-189: --- I concur on you with that. It would be nicer if Checkstyle removed the functionality of the class and displayed a warning when instantiating the class. At least you can get it to work again now. > Unable to instantiate DoubleCheckedLockingCheck exception after upgrading > from version 2.9.1 to 2.10 > > > Key: MCHECKSTYLE-189 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-189 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: $ mvn -v > Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 > 07:51:28-0600) > Maven home: /Users/mheuer/bin/maven-latest > Java version: 1.6.0_37, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" >Reporter: Michael Heuer > Attachments: mcheckstyle188.tar.gz > > > After upgrading from version 3.9.1 to version 3.10 > $ mvn -e site > ... > Error during page generation: Error rendering Maven report: Failed during > checkstyle configuration: cannot initialize module TreeWalker - Unable to > instantiate DoubleCheckedLocking: Unable to instantiate > DoubleCheckedLockingCheck -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on > project dsh-midi-cytoscape3-app: Error during page generation > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page > generation > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error > rendering Maven report: Failed during checkstyle configuration > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) > at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) > ... 21 more > Caused by: org.apache.maven.reporting.MavenReportException: Failed during > checkstyle configuration > at > org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) > at > org.apache.maven.plugin.checkstyle.CheckstyleReport.executeReport(CheckstyleReport.java:339) > at > org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenRe
[jira] (MCHECKSTYLE-189) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10
[ https://jira.codehaus.org/browse/MCHECKSTYLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320477#comment-320477 ] Nick Stolwijk commented on MCHECKSTYLE-189: --- Ah, also see http://sourceforge.net/p/checkstyle/bugs/681/. It seems Checkstyle 5.6 contains a bug, that the sun_checks.xml still contains this check. Unfortunately, the sun_checks is the default for the Maven Checkstyle plugin. See http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#configLocation for how to use your own. > Unable to instantiate DoubleCheckedLockingCheck exception after upgrading > from version 2.9.1 to 2.10 > > > Key: MCHECKSTYLE-189 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-189 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: $ mvn -v > Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 > 07:51:28-0600) > Maven home: /Users/mheuer/bin/maven-latest > Java version: 1.6.0_37, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" >Reporter: Michael Heuer > Attachments: mcheckstyle188.tar.gz > > > After upgrading from version 3.9.1 to version 3.10 > $ mvn -e site > ... > Error during page generation: Error rendering Maven report: Failed during > checkstyle configuration: cannot initialize module TreeWalker - Unable to > instantiate DoubleCheckedLocking: Unable to instantiate > DoubleCheckedLockingCheck -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on > project dsh-midi-cytoscape3-app: Error during page generation > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page > generation > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error > rendering Maven report: Failed during checkstyle configuration > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) > at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) > ... 21 more > Caused by: org.apache.maven.reporting.MavenReportException: Failed during > checkstyle configuration > at > org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) > at > org.apache.ma
[jira] (MCHECKSTYLE-189) Unable to instantiate DoubleCheckedLockingCheck exception after upgrading from version 2.9.1 to 2.10
[ https://jira.codehaus.org/browse/MCHECKSTYLE-189?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=320476#comment-320476 ] Nick Stolwijk commented on MCHECKSTYLE-189: --- As you can see at https://jira.codehaus.org/browse/MCHECKSTYLE-181 Checkstyle has been upgraded to version 5.6 in the new plugin version. Unfortunately, Winrar wouldn't open your attachment, so I cannot check which checkstyle configuration you use. Could it be you have your own configuration and didn't update it to be compatible with Checkstyle 5.6? > Unable to instantiate DoubleCheckedLockingCheck exception after upgrading > from version 2.9.1 to 2.10 > > > Key: MCHECKSTYLE-189 > URL: https://jira.codehaus.org/browse/MCHECKSTYLE-189 > Project: Maven 2.x Checkstyle Plugin > Issue Type: Bug >Affects Versions: 2.10 > Environment: $ mvn -v > Apache Maven 3.0.5 (r01de14724cdef164cd33c7c8c2fe155faf9602da; 2013-02-19 > 07:51:28-0600) > Maven home: /Users/mheuer/bin/maven-latest > Java version: 1.6.0_37, vendor: Apple Inc. > Java home: /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > Default locale: en_US, platform encoding: MacRoman > OS name: "mac os x", version: "10.7.5", arch: "x86_64", family: "mac" >Reporter: Michael Heuer > Attachments: mcheckstyle188.tar.gz > > > After upgrading from version 3.9.1 to version 3.10 > $ mvn -e site > ... > Error during page generation: Error rendering Maven report: Failed during > checkstyle configuration: cannot initialize module TreeWalker - Unable to > instantiate DoubleCheckedLocking: Unable to instantiate > DoubleCheckedLockingCheck -> [Help 1] > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > goal org.apache.maven.plugins:maven-site-plugin:3.2:site (default-site) on > project dsh-midi-cytoscape3-app: Error during page generation > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84) > at > org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183) > at > org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156) > at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537) > at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:141) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at > org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290) > at org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230) > at > org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409) > at org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352) > Caused by: org.apache.maven.plugin.MojoExecutionException: Error during page > generation > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:143) > at > org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101) > at > org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209) > ... 19 more > Caused by: org.apache.maven.doxia.siterenderer.RendererException: Error > rendering Maven report: Failed during checkstyle configuration > at > org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:233) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:319) > at > org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:135) > at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175) > at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138) > ... 21 more > Caused by: org.apache.maven.reporting.MavenReportException: Failed during > checkstyle configuration > at > org.apache.maven.plugin.checkstyle.AbstractCheckstyleReport.executeReport(AbstractCheckstyleReport.java:260) > at > org.apache.m
[jira] Commented: (MPMD-109) Class name not printed in pmd:check output
[ http://jira.codehaus.org/browse/MPMD-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196397#action_196397 ] Nick Stolwijk commented on MPMD-109: I have found the problem. The pmd plugin just parsed the xml file and prints the packagename + class found in the xml file. [1] The pmd file does not contain class for rules which are above class level. [2] It is not something the pmd plugin can solve. Your rule sees the whole class as "wrong", maybe you can change your rule to see a specific line as wrong. [1] http://svn.apache.org/viewvc/maven/plugins/tags/maven-pmd-plugin-2.4/src/main/java/org/apache/maven/plugin/pmd/PmdViolationCheckMojo.java?view=markup line 89 [2] http://pmd.svn.sourceforge.net/viewvc/pmd/tags/pmd/pmd_release_4_2_2/src/net/sourceforge/pmd/RuleViolation.java?revision=6135&view=markup line 77 > Class name not printed in pmd:check output > -- > > Key: MPMD-109 > URL: http://jira.codehaus.org/browse/MPMD-109 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 2.4 >Reporter: Johan Andrén > > When we get pmd:check failures only package name and line is printed. It > would be very nice to get class name as well. > Example output: > [pmd:check] > PMD Failure: se.databyran.prosang.client.core.util.form.dialogs.13 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.gui.62 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.search.44 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.search.FinderDialog:70 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. -- 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: (MPMD-109) Class name not printed in pmd:check output
[ http://jira.codehaus.org/browse/MPMD-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196392#action_196392 ] Nick Stolwijk commented on MPMD-109: The plugin doesn't do anything else then parse the pmd.xml, but you say the classname is in there. Can you post a snippet of your pmd.xml? > Class name not printed in pmd:check output > -- > > Key: MPMD-109 > URL: http://jira.codehaus.org/browse/MPMD-109 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 2.4 >Reporter: Johan Andrén > > When we get pmd:check failures only package name and line is printed. It > would be very nice to get class name as well. > Example output: > [pmd:check] > PMD Failure: se.databyran.prosang.client.core.util.form.dialogs.13 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.gui.62 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.search.44 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.search.FinderDialog:70 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. -- 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: (MPMD-109) Class name not printed in pmd:check output
[ http://jira.codehaus.org/browse/MPMD-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=196375#action_196375 ] Nick Stolwijk commented on MPMD-109: I haven't looked at the code yet, but could it be that those warnings are from anonymous inner classes? > Class name not printed in pmd:check output > -- > > Key: MPMD-109 > URL: http://jira.codehaus.org/browse/MPMD-109 > Project: Maven 2.x PMD Plugin > Issue Type: Improvement > Components: PMD >Affects Versions: 2.4 >Reporter: Johan Andrén > > When we get pmd:check failures only package name and line is printed. It > would be very nice to get class name as well. > Example output: > [pmd:check] > PMD Failure: se.databyran.prosang.client.core.util.form.dialogs.13 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.gui.62 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.search.44 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. > PMD Failure: se.databyran.prosang.client.core.util.search.FinderDialog:70 > Rule:AutoGenerateMnemonicsRequired Priority:3 All forms and panels must have > the 'auto generate mnemonics' property set. -- 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: (MENFORCER-84) Allow rules to be configured from an external file
[ http://jira.codehaus.org/browse/MENFORCER-84?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195704#action_195704 ] Nick Stolwijk commented on MENFORCER-84: This is tricky. If the configuration is not in an artifact, released builds can start failing, because of a rules change. > Allow rules to be configured from an external file > -- > > Key: MENFORCER-84 > URL: http://jira.codehaus.org/browse/MENFORCER-84 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature > Components: Plugin >Affects Versions: 1.0-beta-1 >Reporter: Mark Hobson > > It could be handy to share enforcer rules configuration across projects > without using POM inheritance. Perhaps consider accepting an XML file that > contains the rules in addition to the current method of configuration. -- 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: (SCM-480) "mvn scm:status" doesn't show modified file
[ http://jira.codehaus.org/browse/SCM-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=195698#action_195698 ] Nick Stolwijk commented on SCM-480: --- The specifications of the output format are found in the SVN repository. http://svn.collab.net/repos/svn/tags/1.6.0/subversion/svn/schema/ > "mvn scm:status" doesn't show modified file > --- > > Key: SCM-480 > URL: http://jira.codehaus.org/browse/SCM-480 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.2 > Environment: OS X 10.5.7 > JDK 1.5 > Maven 2.1.0 > SVN 1.6.2 >Reporter: Victor Volle > Attachments: svn-consumer.patch > > > "svn status" gives > M src/main/java/de/artive/test/FooBar.java > "mvn scm:status" gives > [INFO] Scanning for projects... > [INFO] Searching repository for plugin with prefix: 'scm'. > [INFO] > > [INFO] Building test-build > [INFO]task-segment: [scm:status] (aggregator-style) > [INFO] > > [INFO] [scm:status] > [INFO] Executing: /bin/sh -c cd /Users/vivo/workspaces/eclipse-3.4/test-build > && svn --username vivo --password '*' --non-interactive status > [INFO] Working directory: /Users/vivo/workspaces/eclipse-3.4/test-build > [INFO] > > [INFO] BUILD SUCCESSFUL > [INFO] > > [INFO] Total time: 4 seconds > [INFO] Finished at: Fri Jun 26 13:01:04 CEST 2009 > [INFO] Final Memory: 15M/29M > [INFO] > > The changed file is not shown. > This wouldn't be that bad, if the the release plugin therefore would not > recognize that there still is a modified file in the workspace -- 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] Created: (MDEP-236) analyze-dep-mgt doesn't fail on version mismatches while failbuild is set
analyze-dep-mgt doesn't fail on version mismatches while failbuild is set
-
Key: MDEP-236
URL: http://jira.codehaus.org/browse/MDEP-236
Project: Maven 2.x Dependency Plugin
Issue Type: Improvement
Components: analyze
Affects Versions: 2.1, 2.0
Reporter: Nick Stolwijk
Assignee: Brian Fox
Attachments: test-artifact.tar.gz
Even if failBuild is set to true, the builds still succeeds if there is a
version mismatch.
Output with attached pom:
[INFO] [dependency:analyze-dep-mgt {execution: analyze}]
[INFO] Found Resolved Dependency / DependencyManagement mismatches:
[INFO] Dependency: junit:junit:jar
[INFO] DepMgt : 3.7.9
[INFO] Resolved: 3.8.1
[INFO]None
[INFO] [install:install {execution: default-install}]
[INFO] Installing /tmp/test-artifact/target/test-artifact-1.0-SNAPSHOT.jar to
/home/nick/.m2/repository/org/example/test/test-artifact/1.0-SNAPSHOT/test-artifact-1.0-SNAPSHOT.jar
[INFO]
[INFO] BUILD SUCCESSFUL
[INFO]
[INFO] Total time: 11 seconds
[INFO] Finished at: Tue Oct 20 13:56:19 CEST 2009
[INFO] Final Memory: 21M/39M
--
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: (MPIR-151) Unable to find the mojo 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license'
[ http://jira.codehaus.org/browse/MPIR-151?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=167913#action_167913 ] Nick Stolwijk commented on MPIR-151: See also the thread running at the user list. It is also encountered with maven 2.0.7. > Unable to find the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' > -- > > Key: MPIR-151 > URL: http://jira.codehaus.org/browse/MPIR-151 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Bug >Affects Versions: 2.1.1 > Environment: all >Reporter: Martin West > > This started happening yesterday after it downloaded a new version of the > plugin ... > Downloading: > http://mirrors.dotsrc.org/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.pom > Downloading: > http://www.ibiblio.net/pub/packages/maven2/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar > 205K downloaded > - > this realm = > app0.child-container[org.apache.maven.plugins:maven-project-info-reports-plugin] > urls[0] = > file:/var/maven2/repo/org/apache/maven/plugins/maven-project-info-reports-plugin/2.1.1/maven-project-info-reports-plugin-2.1.1.jar > urls[1] = > file:/var/maven2/repo/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar > Number of imports: 6 > import: org.codehaus.classworlds.en...@4891bb28 > import: org.codehaus.classworlds.en...@f8e44ca4 > import: org.codehaus.classworlds.en...@c51bc9e7 > import: org.codehaus.classworlds.en...@bece5185 > import: org.codehaus.classworlds.en...@3fee8e37 > import: org.codehaus.classworlds.en...@3fee19d8 > this realm = plexus.core > urls[0] = file:/opt/maven2/lib/maven-2.1.0-M1-uber.jar > Number of imports: 6 > import: org.codehaus.classworlds.en...@4891bb28 > import: org.codehaus.classworlds.en...@f8e44ca4 > import: org.codehaus.classworlds.en...@c51bc9e7 > import: org.codehaus.classworlds.en...@bece5185 > import: org.codehaus.classworlds.en...@3fee8e37 > import: org.codehaus.classworlds.en...@3fee19d8 > - > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Error getting reports from the plugin > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1': Unable to > find the mojo > 'org.apache.maven.plugins:maven-project-info-reports-plugin:2.1.1:license' in > the plugin 'org.apache.maven.plugins:maven-project-info-reports-plugin' > org.apache.maven.reporting.AbstractMavenReport -- 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: (MNGSITE-74) Maven Assembly Plugin XSD link is broken
[ http://jira.codehaus.org/browse/MNGSITE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MNGSITE-74: - Attachment: mngsite-74.patch This is against the assembly plugin, not against site. Also updated the version number of the assembly plugin in the documentation. > Maven Assembly Plugin XSD link is broken > > > Key: MNGSITE-74 > URL: http://jira.codehaus.org/browse/MNGSITE-74 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Asaf Mesika >Priority: Minor > Attachments: mngsite-74.patch > > > The link to the Maven Assembly Plugin Descriptor XSD is broken. > The link is found at the bottom of the following page: > http://maven.apache.org/plugins/maven-assembly-plugin/ > The link should be: > http://maven.apache.org/xsd/assembly-1.1.0.xsd > The current (wrong) link is: > http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd -- 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: (MNGSITE-74) Maven Assembly Plugin XSD link is broken
[ http://jira.codehaus.org/browse/MNGSITE-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=159148#action_159148 ] Nick Stolwijk commented on MNGSITE-74: -- Added to wrong project. This documentation is included in the assembly project itself. Included a patch against the assembly project. > Maven Assembly Plugin XSD link is broken > > > Key: MNGSITE-74 > URL: http://jira.codehaus.org/browse/MNGSITE-74 > Project: Maven 2 Project Web Site > Issue Type: Bug >Reporter: Asaf Mesika >Priority: Minor > > The link to the Maven Assembly Plugin Descriptor XSD is broken. > The link is found at the bottom of the following page: > http://maven.apache.org/plugins/maven-assembly-plugin/ > The link should be: > http://maven.apache.org/xsd/assembly-1.1.0.xsd > The current (wrong) link is: > http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd -- 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: (MNGSITE-75) Add scriptSourceDirectory to introduction-to-the-standard-directory-layout.html
[ http://jira.codehaus.org/browse/MNGSITE-75?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MNGSITE-75: - Attachment: mngsite-75.patch > Add scriptSourceDirectory to > introduction-to-the-standard-directory-layout.html > --- > > Key: MNGSITE-75 > URL: http://jira.codehaus.org/browse/MNGSITE-75 > Project: Maven 2 Project Web Site > Issue Type: Improvement >Reporter: Nick Stolwijk > Attachments: mngsite-75.patch > > > On http://maven.apache.org/guides/introduction/introduction-to-the-pom.html > there is a scriptSourceDirectory which is missing from > introduction-to-the-standard-directory-layout.html. > Patch will follow as soon as I have setup subversion. -- 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] Created: (MNGSITE-75) Add scriptSourceDirectory to introduction-to-the-standard-directory-layout.html
Add scriptSourceDirectory to introduction-to-the-standard-directory-layout.html --- Key: MNGSITE-75 URL: http://jira.codehaus.org/browse/MNGSITE-75 Project: Maven 2 Project Web Site Issue Type: Improvement Reporter: Nick Stolwijk On http://maven.apache.org/guides/introduction/introduction-to-the-pom.html there is a scriptSourceDirectory which is missing from introduction-to-the-standard-directory-layout.html. Patch will follow as soon as I have setup subversion. -- 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: (SCM-262) scm:tag for subversion tagging from local version of code, not directly from repository
[ http://jira.codehaus.org/browse/SCM-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=156408#action_156408 ] Nick Stolwijk commented on SCM-262: --- Wouldn't it be possible to take the revision number at start of the release and give that to svn checkout and svn copy? Noone can change a revision so you will be save. > scm:tag for subversion tagging from local version of code, not directly from > repository > --- > > Key: SCM-262 > URL: http://jira.codehaus.org/browse/SCM-262 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Reporter: Stephan Heilner > Fix For: future > > > In theory, you shouldn't tag or branch from a local and potentially different > version of the code. From what I can tell, the scm:tag imports your existing > code into a new tag. With subversion, tagging is very lightweight if you do > a 'svn copy trunk_url tag_url'. The way it currently works make sense for > other repositories such as CVS but not for subversion. -- 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] Created: (MECLIPSE-499) Improve eclipse:eclipse excludes option
Improve eclipse:eclipse excludes option --- Key: MECLIPSE-499 URL: http://jira.codehaus.org/browse/MECLIPSE-499 Project: Maven 2.x Eclipse Plugin Issue Type: Improvement Components: Core : .project Affects Versions: 2.5.1 Reporter: Nick Stolwijk The documentation don't reflect how to configure the exludes option. Please include some documentation, like List of [groupId]:[artifactId] -- 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: (ARCHETYPE-217) mvn archetype:help should not require a pom
[ http://jira.codehaus.org/browse/ARCHETYPE-217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=151514#action_151514 ] Nick Stolwijk commented on ARCHETYPE-217: - Just tested it with the trunk version and there it works. It has been fixed by updating the maven-plugin-plugin version to 2.4.3 in r703584. > mvn archetype:help should not require a pom > --- > > Key: ARCHETYPE-217 > URL: http://jira.codehaus.org/browse/ARCHETYPE-217 > Project: Maven Archetype > Issue Type: Improvement >Affects Versions: 2.0-alpha-3 > Environment: Maven version: 2.0.8 > Java version: 1.5.0_11 > OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows" >Reporter: Neil Crow >Priority: Minor > > mvn archetype:help should not require a pom. > This goal only runs successfully if issued from a directory which contains a > valid pom. > This is counter-intuitive, as mvn archetype:generate does not have this > requirement. -- 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-3752) Preparing release fails with svn client 1.5.1 and 1.5.2
[
http://jira.codehaus.org/browse/MNG-3752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=147796#action_147796
]
Nick Stolwijk commented on MNG-3752:
This is a duplicate of http://jira.codehaus.org/browse/SCM-406
> Preparing release fails with svn client 1.5.1 and 1.5.2
> ---
>
> Key: MNG-3752
> URL: http://jira.codehaus.org/browse/MNG-3752
> Project: Maven 2
> Issue Type: Bug
>Affects Versions: 2.0.9
> Environment: Maven version: 2.0.9
> Java version: 1.5.0_11
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
> Subversion command-line client, version 1.5.2
>Reporter: Borut Bolcina
>Priority: Blocker
>
> When upgraded svn client from 1.5.0-dev to 1.5.2 the _mvn release:prepare_
> fails:
> {code}[INFO] Executing: svn --non-interactive commit --file
> C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-2091962435.commit --targets
> C:\DOCUME~1\borutb\L
> OCALS~1\Temp\maven-scm-44156-targets
> [INFO] Working directory: C:\workarea\madserver-RB-1.3
> [INFO] Tagging release with the label REL-1.3.10...
> [INFO] Executing: svn --non-interactive copy --file
> C:\DOCUME~1\borutb\LOCALS~1\Temp\maven-scm-855569361.commit .
> https://svn.acme.com/repos
> itories/modules/madserver/tags/REL-1.3.10
> [INFO] Working directory: C:\workarea\madserver-RB-1.3
> [INFO]
>
> [ERROR] BUILD FAILURE
> [INFO]
>
> [INFO] Unable to tag SCM
> Provider message:
> The svn tag command failed.
> Command output:
> svn: Commit failed (details follow):
> svn: File
> '/repositories/modules/madserver/tags/REL-1.3.10/.settings/org.maven.ide.eclipse.prefs'
> already exists
> {code}
> The same happens with 1.5.1 svn client on Linux with my coworker. Installing
> 1.5.0 solves the problem. As temporary files (.commit) are deleted I can not
> give 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] Commented: (MENFORCER-37) 'noSnapshots' rule do not check version of parent
[ http://jira.codehaus.org/browse/MENFORCER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=139022#action_139022 ] Nick Stolwijk commented on MENFORCER-37: The "noSnapshots" rules is deprecated and replaced by the "RequireReleaseDeps" rule. I've attached a patch to change this rule to also check for the parent. This is turned on by default, and it is possible to turn it off. Maybe the default should be turned off, but I'll leave that to Brian. > 'noSnapshots' rule do not check version of parent > - > > Key: MENFORCER-37 > URL: http://jira.codehaus.org/browse/MENFORCER-37 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Tomasz Pik >Assignee: Brian Fox > Fix For: 1.0 > > Attachments: RequireReleaseDeps.patch > > > 'noSnapshots' is passing when parent is defined to be SNAPSHOT, IMHO parent > is also a dependency so it should be checked and rule should throw an error > if parent is a SNAPSHOT. -- 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: (MENFORCER-37) 'noSnapshots' rule do not check version of parent
[ http://jira.codehaus.org/browse/MENFORCER-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MENFORCER-37: --- Attachment: RequireReleaseDeps.patch > 'noSnapshots' rule do not check version of parent > - > > Key: MENFORCER-37 > URL: http://jira.codehaus.org/browse/MENFORCER-37 > Project: Maven 2.x Enforcer Plugin > Issue Type: Bug > Components: Standard Rules >Affects Versions: 1.0-alpha-3 >Reporter: Tomasz Pik >Assignee: Brian Fox > Fix For: 1.0 > > Attachments: RequireReleaseDeps.patch > > > 'noSnapshots' is passing when parent is defined to be SNAPSHOT, IMHO parent > is also a dependency so it should be checked and rule should throw an error > if parent is a SNAPSHOT. -- 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] Issue Comment Edited: (MENFORCER-29) Enforcer complains about its own version
[
http://jira.codehaus.org/browse/MENFORCER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138999#action_138999
]
nick_stolwijk edited comment on MENFORCER-29 at 6/19/08 6:46 AM:
-
I've tested this with maven 2.0.9 against the current trunk (r669424) and had
to change the jar plugin to version 2.2 (from 2.0.2, which could not be found)
but then the commands "mvn install" and "mvn compile -Penforce" worked
perfectly.
Not reproducible.
was (Author: nick_stolwijk):
I've tested this against the current trunk (r669424) and had to change the
jar plugin to version 2.2 (from 2.0.2, which could not be found) but then the
commands "mvn install" and "mvn compile -Penforce" worked perfectly.
Not reproducible.
> Enforcer complains about its own version
>
>
> Key: MENFORCER-29
> URL: http://jira.codehaus.org/browse/MENFORCER-29
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.0
> Environment: GNU/Linux
>Reporter: Hilco Wijbenga
>Assignee: Brian Fox
> Fix For: 1.0
>
> Attachments: pom.xml
>
>
> The attached POM uses the latest version of the Enforcer (revision 611262),
> i.e. 1.0-SNAPSHOT. I've called it 1.0-Local-1, so that's what's defined in
> the POM.
> If I use the Enforcer normally, without a profile, everything works
> beautifully. The attached POM, however, tries to use the Enforcer from a
> profile ("enforce"). If you now try something like "mvn compile -Penforce" it
> complains about its own version not being set, even though it's specified
> *twice*.
--
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: (MENFORCER-29) Enforcer complains about its own version
[
http://jira.codehaus.org/browse/MENFORCER-29?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138999#action_138999
]
Nick Stolwijk commented on MENFORCER-29:
I've tested this against the current trunk (r669424) and had to change the jar
plugin to version 2.2 (from 2.0.2, which could not be found) but then the
commands "mvn install" and "mvn compile -Penforce" worked perfectly.
Not reproducible.
> Enforcer complains about its own version
>
>
> Key: MENFORCER-29
> URL: http://jira.codehaus.org/browse/MENFORCER-29
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 1.0
> Environment: GNU/Linux
>Reporter: Hilco Wijbenga
>Assignee: Brian Fox
> Fix For: 1.0
>
> Attachments: pom.xml
>
>
> The attached POM uses the latest version of the Enforcer (revision 611262),
> i.e. 1.0-SNAPSHOT. I've called it 1.0-Local-1, so that's what's defined in
> the POM.
> If I use the Enforcer normally, without a profile, everything works
> beautifully. The attached POM, however, tries to use the Enforcer from a
> profile ("enforce"). If you now try something like "mvn compile -Penforce" it
> complains about its own version not being set, even though it's specified
> *twice*.
--
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: (MENFORCER-31) Incorrect documentation for writing a custom rule
[
http://jira.codehaus.org/browse/MENFORCER-31?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=138997#action_138997
]
Nick Stolwijk commented on MENFORCER-31:
The documentation on the site is for 1.0-SNAPSHOT, which has changed GroupId /
ArtifactId from version 1.0-alpha-2 to the current SNAPSHOT. So for the current
version (SNAPSHOT) the site is right, but for the current alpha release it is
not right.
Also the method you've mentioned are necessary in current SNAPSHOT.
> Incorrect documentation for writing a custom rule
> -
>
> Key: MENFORCER-31
> URL: http://jira.codehaus.org/browse/MENFORCER-31
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Rule API
>Affects Versions: 1.0-alpha-3
>Reporter: Ben Lidgey
>Assignee: Brian Fox
> Fix For: 1.0
>
>
> The documentation at
> http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html has
> the wrong dependencies and code examples for creating a custom rule.
> It defines
> {code:xml}
>
> org.apache.maven.enforcer
> enforcer-api
> ${api.version}
>
> {code}
> instead of
> {code:xml}
>
> org.apache.maven.shared
> maven-enforcer-rule-api
> 1.0-alpha-2
>
> {code}
> and so the code examples are incorrect because:
> # Incorrect imports:
> #* The imports are for
> #** {{org.apache.maven.enforcer.rule.api.EnforcerRule}}
> #** {{org.apache.maven.enforcer.rule.api.EnforcerRuleException}}
> #** {{org.apache.maven.enforcer.rule.api.EnforcerRuleHelper}}
> #* instead of
> #** {{org.apache.maven.shared.enforcer.rule.api.EnforcerRule}}
> #** {{org.apache.maven.shared.enforcer.rule.api.EnforcerRuleException}}
> #** {{org.apache.maven.shared.enforcer.rule.api.EnforcerRuleHelper}}.
> #* Implementing {{import org.apache.maven.enforcer.rule.api.EnforcerRule}}
> causes the custom plugin invocation to fail with an ArrayStoreException as
> the expected type is {{import
> org.apache.maven.shared.enforcer.rule.api.EnforcerRule}} instead.
> # It shows implementing {{public String getCacheId()}}, {{public boolean
> isCacheable()}}, {{public boolean isResultValid( EnforcerRule arg0 )}} which
> are no longer needed.
--
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: (ARCHETYPE-154) Can i ask when will alpha-3 released
[ http://jira.codehaus.org/browse/ARCHETYPE-154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129281#action_129281 ] Nick Stolwijk commented on ARCHETYPE-154: - And why couldn't this just be asked on the user or dev mailinglists? > Can i ask when will alpha-3 released > > > Key: ARCHETYPE-154 > URL: http://jira.codehaus.org/browse/ARCHETYPE-154 > Project: Maven Archetype > Issue Type: Wish > Components: Archetypes >Affects Versions: 2.0-alpha-2, 2.0-alpha-3 >Reporter: chenliang > > Because there is a bug[ARCHETYPE-147] in alpha-2 which make my project > cannot process. So i want to ask when will alpha-3 released. -- 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-2348) add a simple command line alias for -Dmaven.test.skip=true as I find myself typing it very very often
[ http://jira.codehaus.org/browse/MNG-2348?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=129076#action_129076 ] Nick Stolwijk commented on MNG-2348: Or just use: -DskipTests Saves another few characters. > add a simple command line alias for -Dmaven.test.skip=true as I find myself > typing it very very often > - > > Key: MNG-2348 > URL: http://jira.codehaus.org/browse/MNG-2348 > Project: Maven 2 > Issue Type: Improvement > Components: Command Line >Affects Versions: 2.0.4 >Reporter: james strachan > Fix For: 2.x > > > Could we have some simple alias on the command line to disable unit tests > just like we have maven -o for offline. > Don't much mind what it is - how about... > -nt --no-testsDisables the junit tests in this build > so to do a build without unit tests > mvn -nt install -- 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: (CONTINUUM-1680) Add functionality to remove/recreate a working copy
[ http://jira.codehaus.org/browse/CONTINUUM-1680?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_126420 ] Nick Stolwijk commented on CONTINUUM-1680: -- I know of that option, after the little discussion on the maillinglist. However, it would be nice if there was just one button to recreate it. I'd rather not to have to schedule a build with a recreate. > Add functionality to remove/recreate a working copy > --- > > Key: CONTINUUM-1680 > URL: http://jira.codehaus.org/browse/CONTINUUM-1680 > Project: Continuum > Issue Type: New Feature > Components: SCM, Web - UI >Reporter: Nick Stolwijk >Priority: Minor > > Sometimes a subversion working copy gets corrupted and can not be repaired > through the user interface. This is possible when you have a strange build > which overwrites directories or conflicting commits/build(*). It would be > nice if the User interface offered a possibility to recreate the working copy > (remove and new checkout for example). > (*) We had a directory called etc. In a few commits someone removed that > directory, another one added build code to create a file in that directory > and another person added this folder again in SVN. Continuum (or rather the > SVN under it) was a little confused and could not update. -- 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: (MPIR-85) Refactoring of dependency and dependency management report
[ http://jira.codehaus.org/browse/MPIR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MPIR-85: -- Attachment: refactor.patch Contains the Plugin, Artifact and Dependency Comparators for the refactoring, with unit tests. > Refactoring of dependency and dependency management report > -- > > Key: MPIR-85 > URL: http://jira.codehaus.org/browse/MPIR-85 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Nick Stolwijk > Attachments: comparators.patch, refactor.patch, refactor.patch > > > I've tried to refactor the code from MPIR-83 a bit, because it used a lot of > copied code. > Important improvements: > - Created a AbstractProjectInfoRenderer and AbstractDependencyRenderer. > If this patch is accepted, I want to write all the renderers out of the > inforeports in separate classes, with more code sharing. This is a start of > that. > - I changed the unit tests, because the expected and actual were reversed. > This is the case in many of the info report unit tests. > Please tell me what you think of it. I know it is only a start. -- 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: (MPIR-85) Refactoring of dependency and dependency management report
[ http://jira.codehaus.org/browse/MPIR-85?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MPIR-85: -- Attachment: comparators.patch And now the right file. ;) Added comparators and unit test for them in comparators.patch > Refactoring of dependency and dependency management report > -- > > Key: MPIR-85 > URL: http://jira.codehaus.org/browse/MPIR-85 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Improvement >Affects Versions: 2.1 >Reporter: Nick Stolwijk > Attachments: comparators.patch, refactor.patch, refactor.patch > > > I've tried to refactor the code from MPIR-83 a bit, because it used a lot of > copied code. > Important improvements: > - Created a AbstractProjectInfoRenderer and AbstractDependencyRenderer. > If this patch is accepted, I want to write all the renderers out of the > inforeports in separate classes, with more code sharing. This is a start of > that. > - I changed the unit tests, because the expected and actual were reversed. > This is the case in many of the info report unit tests. > Please tell me what you think of it. I know it is only a start. -- 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] Created: (MPIR-85) Refactoring of dependency and dependency management report
Refactoring of dependency and dependency management report -- Key: MPIR-85 URL: http://jira.codehaus.org/browse/MPIR-85 Project: Maven 2.x Project Info Reports Plugin Issue Type: Improvement Affects Versions: 2.1 Reporter: Nick Stolwijk Attachments: refactor.patch I've tried to refactor the code from MPIR-83 a bit, because it used a lot of copied code. Important improvements: - Created a AbstractProjectInfoRenderer and AbstractDependencyRenderer. If this patch is accepted, I want to write all the renderers out of the inforeports in separate classes, with more code sharing. This is a start of that. - I changed the unit tests, because the expected and actual were reversed. This is the case in many of the info report unit tests. Please tell me what you think of it. I know it is only a start. -- 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: (MENFORCER-30) RequirePluginVersions breaks when using project.parent.groupId and project.parent.version.
[
http://jira.codehaus.org/browse/MENFORCER-30?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_122047
]
Nick Stolwijk commented on MENFORCER-30:
I had already spoken to Brian about this issue and that was indeed the
solution. He only wanted it registered here, so he would not forget it. No
problem, no hurry, this is just a reminder.
> RequirePluginVersions breaks when using project.parent.groupId and
> project.parent.version.
> --
>
> Key: MENFORCER-30
> URL: http://jira.codehaus.org/browse/MENFORCER-30
> Project: Maven 2.x Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Reporter: Nick Stolwijk
>Assignee: Brian Fox
>Priority: Trivial
>
> We were using a obsolete but working child pom file, like:
> http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
>
> org.example.petstore
> petstore
> 0.2-SNAPSHOT
>
> ${project.parent.groupId}
> petstore-common
> 0.2-SNAPSHOT
> jar
> Common module
> The Common module.
>
> The rule will fail, when the child is not in the local or a remote
> repository, because ${project.parent.groupId} and org.example.petstore are
> not the same and the artifact can not be found.
--
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] Created: (ARCHETYPE-120) Webapp sample contains the wrong project layout
Webapp sample contains the wrong project layout --- Key: ARCHETYPE-120 URL: http://jira.codehaus.org/browse/ARCHETYPE-120 Project: Maven Archetype Issue Type: Improvement Components: Archetypes Reporter: Nick Stolwijk Attachments: fix-webapp-example.patch The "Creating a Webapp" example page (http://maven.apache.org/plugins/maven-archetype-plugin/examples/webapp.html) contains the wrong directory layout. (Fix included) Also, the files in the archetype plugin have no svn property svn:line-endings native set. (No fix included) -- 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: (MPIR-83) Include reports for DependencyManagement and PluginManagement
[ http://jira.codehaus.org/browse/MPIR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121758 ] Nick Stolwijk commented on MPIR-83: --- I will look what I can do. Expect some more patches, of course in new issues. :) > Include reports for DependencyManagement and PluginManagement > - > > Key: MPIR-83 > URL: http://jira.codehaus.org/browse/MPIR-83 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Nick Stolwijk >Assignee: Vincent Siveton > Fix For: 2.1 > > Attachments: management-reports.patch, management-reports.zip > > > Create a report for the DependencyManagement and PluginManagement sections of > the project. -- 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: (MPIR-83) Include reports for DependencyManagement and PluginManagement
[ http://jira.codehaus.org/browse/MPIR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121756 ] Nick Stolwijk commented on MPIR-83: --- I've got three questions: 1) Do you think a little refactoring is good, to remove the code duplication this patch introduced? 2) What do you think of the following features for the dependency management report? - Show optional - Show a transitive dependency tree, like the dependency report. - Show excluded dependencies. - Show dependency info, like the dependency report. 3) What do you think of the following features for the plugin management report? - Show configuration - Show executions +configuration - Show extensions - Show inheritance - Show dependencies > Include reports for DependencyManagement and PluginManagement > - > > Key: MPIR-83 > URL: http://jira.codehaus.org/browse/MPIR-83 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Affects Versions: 2.0.1 >Reporter: Nick Stolwijk >Assignee: Vincent Siveton > Fix For: 2.1 > > Attachments: management-reports.patch, management-reports.zip > > > Create a report for the DependencyManagement and PluginManagement sections of > the project. -- 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] Created: (MENFORCER-30) RequirePluginVersions breaks when using project.parent.groupId and project.parent.version.
RequirePluginVersions breaks when using project.parent.groupId and
project.parent.version.
--
Key: MENFORCER-30
URL: http://jira.codehaus.org/browse/MENFORCER-30
Project: Maven 2.x Enforcer Plugin
Issue Type: Bug
Components: Standard Rules
Reporter: Nick Stolwijk
Assignee: Brian Fox
Priority: Trivial
We were using a obsolete but working child pom file, like:
http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
org.example.petstore
petstore
0.2-SNAPSHOT
${project.parent.groupId}
petstore-common
0.2-SNAPSHOT
jar
Common module
The Common module.
The rule will fail, when the child is not in the local or a remote repository,
because ${project.parent.groupId} and org.example.petstore are not the same and
the artifact can not be found.
--
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: (MPIR-83) Include reports for DependencyManagement and PluginManagement
[ http://jira.codehaus.org/browse/MPIR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MPIR-83: -- Attachment: management-reports.zip Example reports > Include reports for DependencyManagement and PluginManagement > - > > Key: MPIR-83 > URL: http://jira.codehaus.org/browse/MPIR-83 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Reporter: Nick Stolwijk > Attachments: management-reports.patch, management-reports.zip > > > Create a report for the DependencyManagement and PluginManagement sections of > the project. -- 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: (MPIR-83) Include reports for DependencyManagement and PluginManagement
[ http://jira.codehaus.org/browse/MPIR-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MPIR-83: -- Attachment: management-reports.patch The attached patch includes the DependencyMangement and PluginManagement reports. I have not changed the original code, not wanted to introduce new bugs. So it is a lot of copy paste with little adjustments from the default dependencies report. Maybe some refactoring is in order to avoid code copy. The dependencyManagment report includes the dependencies from dependencyMagement, sorted by scope and ordered, just like the dependencies report. No transitive dependencies are included in the report, as of yet. The pluginManagement report includes the plugins from the pluginManagement, with groupId, artifactId and version (if specified). Also the URL of the site is included, through artifact lookup. Maybe another extension in the report could include configuration and executions. The attached example reports give an idea of the reports. > Include reports for DependencyManagement and PluginManagement > - > > Key: MPIR-83 > URL: http://jira.codehaus.org/browse/MPIR-83 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: New Feature >Reporter: Nick Stolwijk > Attachments: management-reports.patch > > > Create a report for the DependencyManagement and PluginManagement sections of > the project. -- 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] Created: (MPIR-83) Include reports for DependencyManagement and PluginManagement
Include reports for DependencyManagement and PluginManagement - Key: MPIR-83 URL: http://jira.codehaus.org/browse/MPIR-83 Project: Maven 2.x Project Info Reports Plugin Issue Type: New Feature Reporter: Nick Stolwijk Create a report for the DependencyManagement and PluginManagement sections of the project. -- 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: (MASSEMBLY-265) Run site:site if includeSiteDirectory is set to true
[ http://jira.codehaus.org/browse/MASSEMBLY-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119979 ] Nick Stolwijk commented on MASSEMBLY-265: - Duplicate of MASSEMBLY-22 > Run site:site if includeSiteDirectory is set to true > > > Key: MASSEMBLY-265 > URL: http://jira.codehaus.org/browse/MASSEMBLY-265 > Project: Maven 2.x Assembly Plugin > Issue Type: New Feature >Reporter: Michael Osipov > > running a descriptor with the above attribute set to true causes an build > failure when site has not been geneated. > Call site:site when attribute is set to true. > same fuction as calling package since package is already called by default. -- 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-3358) Require explicit plugin versions
[ http://jira.codehaus.org/browse/MNG-3358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119530 ] Nick Stolwijk commented on MNG-3358: This is exactly what the enforcer plugin can do. I don't think that Maven itself should do it. > Require explicit plugin versions > > > Key: MNG-3358 > URL: http://jira.codehaus.org/browse/MNG-3358 > Project: Maven 2 > Issue Type: Improvement > Components: Plugins and Lifecycle >Reporter: Paul Gier > > Currently plugin versions are not required in the pom which causes maven to > use the latest version of each plugin to be used when building a project. > The problem with this system is that builds can break (without any change to > the project itself) if a new version of a plugin is released. This can cause > confusion among developers because the build appears to break for no reason. > It also makes reproducing old builds to be more difficult because a newer > version of a plugin could cause some aspect of the build to be different than > when it was originally released. > SUREFIRE-61 is one example of where this happened. When surefire 2.3.1 was > released, it affected the testing of some builds because the classpath > ordering changed. > My suggestion for fixing this is to require a version for all plugins. This > is already a best practice among many maven users, but it is not enforced by > maven itself. For the default lifecycle plugins (compiler plugin, surefire > plugin, etc.) maven should tie it's version to specific default versions of > the plugins. These could then be overridden when necessary. > This change probably belongs in 2.1 since it is too big a change for 2.0.9. -- 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] Created: (MENFORCER-28) Create a rule, which fail when the upper most parent (corporate pom) is not the latest version
Create a rule, which fail when the upper most parent (corporate pom) is not the latest version -- Key: MENFORCER-28 URL: http://jira.codehaus.org/browse/MENFORCER-28 Project: Maven 2.x Enforcer Plugin Issue Type: New Feature Components: Standard Rules Reporter: Nick Stolwijk Assignee: Brian Fox Priority: Minor Basic functionality: - Should fail if the current project is a SNAPSHOT and there is a newer version of the top most (the corporate pom) artifact. (Don't fail on released versions) - Very optional (I can't find a good use case):Option to fail on released versions also. - Option to not fail on major changes. (so update from 0.9.1 -> 0.9.2 fail, from 0.9.0 to 1.0.0 don't fail) -- 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: (MCOMPILER-62) Allow multiple options to be passed to compiler for options not supported by the compiler mojo
[
http://jira.codehaus.org/browse/MCOMPILER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115165
]
Nick Stolwijk commented on MCOMPILER-62:
Then you'll get something like this:
${java.home}\lib\rt.jar
-proc:none
-implicit
In my opinion it is easier to read when there is a collection element around it.
> Allow multiple options to be passed to compiler for options not supported by
> the compiler mojo
> --
>
> Key: MCOMPILER-62
> URL: http://jira.codehaus.org/browse/MCOMPILER-62
> Project: Maven 2.x Compiler Plugin
> Issue Type: Improvement
> Environment: Maven version: 2.0.7
>Reporter: Sanjeeb Sahoo
>
> Look at the mail thread in maven user group:
> http://www.nabble.com/Not-able-to-pass-multiple-arguments-to-javac-tf4857909s177.html
> User may have to pass options to the underlying compiler that are not yet
> supported by the mojo. Current implementation of the maven-compiler-plugin
> allows user to specify only one option. Neither of the following techniques
> work:
>
>-proc:none
>-implicit
>
> or
>
> -proc:none -impicit
>
> In the first approach, only one of the compilerArgument is considered, in the
> second approach since maven quotes the argument, it ends up as a single
> argument to javac and hence becomes an invalid option.
> The best suggestion is to allow multiple compilerArgument -- may be something
> like:
>
>
>
>
--
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: (MCOMPILER-62) Allow multiple options to be passed to compiler for options not supported by the compiler mojo
[ http://jira.codehaus.org/browse/MCOMPILER-62?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_115043 ] Nick Stolwijk commented on MCOMPILER-62: To be more precise, the Plexus Compiler and more specific, the Plexus CommandLine and Shell classes quotes each argument. Maybe also a suggestion for the Maven debug statement, which ommits these quotes. (It creates an own version of the commandline and output it) Show the real arguments given to javac. I can try to create a patch for the solution. Is this the best solution? > Allow multiple options to be passed to compiler for options not supported by > the compiler mojo > -- > > Key: MCOMPILER-62 > URL: http://jira.codehaus.org/browse/MCOMPILER-62 > Project: Maven 2.x Compiler Plugin > Issue Type: Improvement > Environment: Maven version: 2.0.7 >Reporter: Sanjeeb Sahoo > > Look at the mail thread in maven user group: > http://www.nabble.com/Not-able-to-pass-multiple-arguments-to-javac-tf4857909s177.html > User may have to pass options to the underlying compiler that are not yet > supported by the mojo. Current implementation of the maven-compiler-plugin > allows user to specify only one option. Neither of the following techniques > work: > >-proc:none >-implicit > > or > > -proc:none -impicit > > In the first approach, only one of the compilerArgument is considered, in the > second approach since maven quotes the argument, it ends up as a single > argument to javac and hence becomes an invalid option. > The best suggestion is to allow multiple compilerArgument -- may be something > like: > > > > -- 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: (MPMD-59) Upgrade to PMD 4.0
[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114892 ] Nick Stolwijk commented on MPMD-59: --- The POM file for 4.1 is also in the repository. > Upgrade to PMD 4.0 > -- > > Key: MPMD-59 > URL: http://jira.codehaus.org/browse/MPMD-59 > Project: Maven 2.x PMD Plugin > Issue Type: Task >Affects Versions: 2.2 >Reporter: Ulli Hafner > Attachments: patch.txt > > > PMD 3.9 has a serious bug when trying to create a report of Java 1.5 classes > with @SuppressWarnings annotations. > Hopefully, an update would fix this bug. -- 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] Created: (MPIR-75) Typing mistake in properties file
Typing mistake in properties file - Key: MPIR-75 URL: http://jira.codehaus.org/browse/MPIR-75 Project: Maven 2.x Project Info Reports Plugin Issue Type: Bug Affects Versions: 2.0.1 Reporter: Nick Stolwijk Priority: Minor In the project-info-report.properties file I found the following entry: report.scm.webaccess.nourl = There are no online source repository listed for this project. Please check back again later. I guess this should be: There are no online source repositories Or: There is no online source repository -- 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: (MPMD-59) Upgrade to PMD 4.0
[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nick Stolwijk updated MPMD-59: -- Attachment: patch.txt I've upped the version of PMD to 4.1 and removed the special cases for Jaxen and Xom, because the new PMD-4.1 POM (not in repository yet) includes the right jaxen (1.1). Also, be very wary of xom-1.1 as it contains some outdated classes from Jaxen! > Upgrade to PMD 4.0 > -- > > Key: MPMD-59 > URL: http://jira.codehaus.org/browse/MPMD-59 > Project: Maven 2.x PMD Plugin > Issue Type: Task >Affects Versions: 2.2 >Reporter: Ulli Hafner > Attachments: patch.txt > > > PMD 3.9 has a serious bug when trying to create a report of Java 1.5 classes > with @SuppressWarnings annotations. > Hopefully, an update would fix this bug. -- 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: (MPMD-59) Upgrade to PMD 4.0
[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114363 ] Nick Stolwijk commented on MPMD-59: --- Oh, and the deployed PMD 4.1 jar file is compiled with Java 5 instead of 1.4. > Upgrade to PMD 4.0 > -- > > Key: MPMD-59 > URL: http://jira.codehaus.org/browse/MPMD-59 > Project: Maven 2.x PMD Plugin > Issue Type: Task >Affects Versions: 2.2 >Reporter: Ulli Hafner > > PMD 3.9 has a serious bug when trying to create a report of Java 1.5 classes > with @SuppressWarnings annotations. > Hopefully, an update would fix this bug. -- 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: (MPMD-59) Upgrade to PMD 4.0
[ http://jira.codehaus.org/browse/MPMD-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_114353 ] Nick Stolwijk commented on MPMD-59: --- PMD 4.1 has been released to central, but unfortunately without a pom file. Also, there isn't a lot of activity on the maven-pmd-plugin trunk lately. Is it still under development? Daniel Kulp was the main committer, is he still around? > Upgrade to PMD 4.0 > -- > > Key: MPMD-59 > URL: http://jira.codehaus.org/browse/MPMD-59 > Project: Maven 2.x PMD Plugin > Issue Type: Task >Affects Versions: 2.2 >Reporter: Ulli Hafner > > PMD 3.9 has a serious bug when trying to create a report of Java 1.5 classes > with @SuppressWarnings annotations. > Hopefully, an update would fix this bug. -- 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: (MRELEASE-251) expression in a POM cannot be updated during release:prepare
[ http://jira.codehaus.org/browse/MRELEASE-251?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113332 ] Nick Stolwijk commented on MRELEASE-251: I can reproduce it with a fresh checkout of the maven-2.0.x branch, but when I update the maven-release-plugin to 2.0-beta-8-SNAPSHOT. (Latest checkout of the release plugin) this is not reproducible. > expression in a POM cannot be updated during release:prepare > > > Key: MRELEASE-251 > URL: http://jira.codehaus.org/browse/MRELEASE-251 > Project: Maven 2.x Release Plugin > Issue Type: Bug >Affects Versions: 2.0-beta-6 >Reporter: Brett Porter >Priority: Critical > Fix For: 2.0 > > > eg. > The artifact (org.apache.maven:maven-error-diagnostics) requires a different > version (2.0.7) than what is found (2.0.7) for the expression (mavenVersion) > in the project (org.apache.maven:maven). > This is achieved by running mvn -DdryRun=true release:prepare on the > maven-2.0.x branch and selecting "2.0.7" as the release version for all, > "maven-2.0.7" as the tag and "2.0.8-SNAPSHOT" as the next version for them > all. -- 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: (MRELEASE-214) scm:tag with scmCommentPrefix
[ http://jira.codehaus.org/browse/MRELEASE-214?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110355 ] Nick Stolwijk commented on MRELEASE-214: I've tested this with a recent checkout of the plugin 2.0-beta-7-SNAPSHOT and cannot reproduce it. I've build revision 586102 of the plugin and tested it with the following configuration: org.apache.maven.plugins maven-release-plugin 2.0-beta-7-SNAPSHOT [TRAC-BLA] The [TRAC-BLA] was added to each checkin comment and also was in release.properties. Also tried it with: org.apache.maven.plugins maven-release-plugin 2.0-beta-7-SNAPSHOT and performed mvn release:prepare -DscmCommentPrefix=[TRAC-BLA], same result. I'm on a Linux machine, using Maven 2.0.7 and Java 6. > scm:tag with scmCommentPrefix > - > > Key: MRELEASE-214 > URL: http://jira.codehaus.org/browse/MRELEASE-214 > Project: Maven 2.x Release Plugin > Issue Type: Improvement > Components: scm >Affects Versions: 2.0-beta-5 > Environment: macosx >Reporter: fabio melen >Assignee: Emmanuel Venisse > Fix For: 2.0-beta-5 > > > My svn repository use a pre-commit hook in order to check the commit message > and to validate it (Trac integration). So I'd like that the scm:tag, invoked > from release:prepare, inherits the scmCommentPrefix value. > ciao > fabio -- 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] Created: (MRELEASE-171) Parameter -Darguments only allow one argument
Parameter -Darguments only allow one argument - Key: MRELEASE-171 URL: http://jira.codehaus.org/browse/MRELEASE-171 Project: Maven 2.x Release Plugin Issue Type: Bug Affects Versions: 2.0-beta-4 Environment: Ubuntu 6.10 maven 2.0.4 j2sdk1.4.2 Reporter: Nick Stolwijk I try to give some arguments when preparing a release to surefire, which is called when the mvn integration-test is being run. My commandline: mvn release:prepare -DdryRun=true -Darguments="-Dautoportaal.environment=continuum -Dmaven.test.failure.ignore=true" When I run this I see in the log: [INFO] Executing: mvn clean integration-test --no-plugin-updates -Dautoportaal.environment=continuum When I try: mvn release:prepare -DdryRun=true -Darguments="-Dautoportaal.environment=continuum" -Darugments="-Dmaven.test.failure.ignore=true" I see: [INFO] Executing: mvn clean integration-test --no-plugin-updates -Dmaven.test.failure.ignore=true It seems only one argument is passed on with the -Darguments argument. -- 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
