[
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 fea
[
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
[
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/c
[
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
[
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
[
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, bu
[
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 w
[
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
[
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 repo
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
[
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 encou
[
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 ve
[
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 i
[
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-l
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 We
[
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 t
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 : .proje
[
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
[
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
[
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
[
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
> --
[
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
[
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 (r66942
[
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,
[
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
[
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.
> ad
[
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 maillingli
[
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 u
[
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 comparator
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: Improv
[
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
so
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: Arch
[
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. :)
> Inclu
[
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 co
RequirePluginVersions breaks when using project.parent.groupId and
project.parent.version.
--
Key: MENFORCER-30
URL: http://jira.codehaus.org/browse/MENFORCER-30
[
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 PluginManagem
[
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
r
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:
[
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 s
[
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 shou
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
[
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:
[
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
Com
[
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
> -
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: Ni
[
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, bec
[
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
[
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
[
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 wh
[
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
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-
51 matches
Mail list logo