[jira] Created: (MNG-2126) Snapshot plugin repositories are not searched for plugins that do not explicitly specify a snapshot version.

Snapshot plugin repositories are not searched for plugins that do not explicitly specify a snapshot version. Key: MNG-2126 URL: http://jira.codehaus.org/browse/MNG-2126

[jira] Created: (MCHECKSTYLE-33) Patch provides ability to control whether check MOJO violations cause build failure (inline with pmd:check)

Patch provides ability to control whether check MOJO violations cause build failure (inline with pmd:check) --- Key: MCHECKSTYLE-33 URL: http://jira.codehaus.org/browse/MCHECK

[jira] Created: (MNG-2086) Support writing all generated output to a different filesystem base to that of the project files (i.e. all non generated files)

Support writing all generated output to a different filesystem base to that of the project files (i.e. all non generated files) --- Key: MNG-2086 URL: http

[jira] Commented: (MRM-96) Enable the use of http proxies when mrm is restricted to browse directly over the net

[ http://jira.codehaus.org/browse/MRM-96?page=comments#action_58688 ] John Allen commented on MRM-96: --- Support NTLM HTTP proxies > Enable the use of http proxies when mrm is restricted to browse directly over > the net > --

[jira] Commented: (MNG-1931) add a reportingManagement section

[ http://jira.codehaus.org/browse/MNG-1931?page=comments#action_58533 ] John Allen commented on MNG-1931: - Any thoughts re moving this up the priority ladder? After all one of the key benefits of using maven is the reduction in duplicated configs and current

[jira] Created: (MPMD-13) Provide pmd:check (patch attached)

Provide pmd:check (patch attached) -- Key: MPMD-13 URL: http://jira.codehaus.org/browse/MPMD-13 Project: Maven 2.x Pmd Plugin Type: New Feature Reporter: John Allen Attachments: PmdViolationCheckMojo.java Attached file adds a pm

[jira] Created: (MSITE-84) Refactor of site:stage and site:site required due to new site:site modules appraoch

Refactor of site:stage and site:site required due to new site:site modules appraoch --- Key: MSITE-84 URL: http://jira.codehaus.org/browse/MSITE-84 Project: Maven 2.x Site Plugin Type: I

[jira] Updated: (MSITE-72) new non reactor populateModules SiteMojo code assumes each POM declares its own URL

[ http://jira.codehaus.org/browse/MSITE-72?page=all ] John Allen updated MSITE-72: Attachment: SiteMojo.diff > new non reactor populateModules SiteMojo code assumes each POM declares its > own URL > --

[jira] Created: (MSITE-73) new site code fails to generate banner images in projects other than site.xml owning project

new site code fails to generate banner images in projects other than site.xml owning project Key: MSITE-73 URL: http://jira.codehaus.org/browse/MSITE-73 Project: Maven 2.x Site Plug

[jira] Created: (MSITE-72) new non reactor populateModules SiteMojo code assumes each POM declares its own URL

new non reactor populateModules SiteMojo code assumes each POM declares its own URL --- Key: MSITE-72 URL: http://jira.codehaus.org/browse/MSITE-72 Project: Maven 2.x Site Plugin Type: B

[jira] Commented: (MPMD-8) PMD should generate results in formats other than html

[ http://jira.codehaus.org/browse/MPMD-8?page=comments#action_55263 ] John Allen commented on MPMD-8: --- Mike, I know it's closed, that's why I commented it, that and the fact that I didn't want my work to go to waste. But as it's now closed and not being reope

[jira] Commented: (MPMD-3) Add support for multiple RuleSets

[ http://jira.codehaus.org/browse/MPMD-3?page=comments#action_55260 ] John Allen commented on MPMD-3: --- Mike, thanks for your work on this, just a shame ive been working on it too without realising these MPMD ones were active. I would like to make one suggest

[jira] Commented: (MPMD-4) PMD should use "sensible" default rulesets

[ http://jira.codehaus.org/browse/MPMD-4?page=comments#action_55258 ] John Allen commented on MPMD-4: --- Over the weekend i took this code and MPMD-8 patches and went through the pmd:pmd and pmd:execute Mojos refactoring and aligning them with the other report

[jira] Commented: (MPMD-8) PMD should generate results in formats other than html

[ http://jira.codehaus.org/browse/MPMD-8?page=comments#action_55257 ] John Allen commented on MPMD-8: --- Over the weekend i took this code and MPMD-4 patches and went through the pmd:pmd and pmd:execute Mojos refactoring and aligning them with the other report

[jira] Commented: (MNG-1929) Plugin Goal report should indicate which fields are read only. (Patch Attached)

[ http://jira.codehaus.org/browse/MNG-1929?page=comments#action_55193 ] John Allen commented on MNG-1929: - +1 for not showing, readonly == private impl. > Plugin Goal report should indicate which fields are read only. (Patch > Attached) > --

[jira] Commented: (MNG-1943) MavenProject::getParent() returns a MavenProject that is NOT interpolated

[ http://jira.codehaus.org/browse/MNG-1943?page=comments#action_55192 ] John Allen commented on MNG-1943: - Brett, re 'a rare case', obviously my familiarity with these internal APIs and there usage is greatly limited so I will defer to your expertese but in

[jira] Created: (MSITE-71) Plugin uses NON interpolated model values (e.g URL) due to MavenProject.getParent returning non interpolated project

Plugin uses NON interpolated model values (e.g URL) due to MavenProject.getParent returning non interpolated project Key: MSITE-71 URL: http://jira.codehaus.org/b

[jira] Created: (MNG-1943) MavenProject::getParent() returns a MavenProject that is NOT interpolated

MavenProject::getParent() returns a MavenProject that is NOT interpolated - Key: MNG-1943 URL: http://jira.codehaus.org/browse/MNG-1943 Project: Maven 2 Type: Bug Reporter: John Allen Pr

[jira] Created: (MNG-1874) problems with site:stage

problems with site:stage Key: MNG-1874 URL: http://jira.codehaus.org/browse/MNG-1874 Project: Maven 2 Type: Bug Components: maven-site-plugin Versions: 2.0.2 Reporter: John Allen Fix For: 2.0.3 The patches contributed

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53654 ] John Allen commented on MNG-661: Additionall problem with new staging functionality and accessing uninterpolated parent project attributes. project.getParent() returns a project that has

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_53143 ] John Allen commented on MNG-661: re the patch, theres a bug in the SiteStageMojo::getStructure() method under windows. Windows distribution paths can start with drive prefixes and thus w

[jira] Created: (MNG-1753) support improved property based profile activation

support improved property based profile activation -- Key: MNG-1753 URL: http://jira.codehaus.org/browse/MNG-1753 Project: Maven 2 Type: New Feature Components: POM Reporter: John Allen support better profile

[jira] Commented: (MNG-1525) Allow environment variables to be referenced in pom.xml, settings.xml, etc.

[ http://jira.codehaus.org/browse/MNG-1525?page=comments#action_52783 ] John Allen commented on MNG-1525: - I guess im going to have to wait for commons-exec as the only way i know of doing this robustly is via JNI (the codeset used by cmd.exe can be any old

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52782 ] John Allen commented on MNG-661: Thanks Vincent, works a treat! I'm using the staged site not only reviewing but also for internal pre-release publications (i.e. CI build generates an i

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52746 ] John Allen commented on MNG-661: Vincent, the patch seems to be missing the new SiteStage mojo. > In parent site, automatically create link to modules sites and vice-versa > -

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_52647 ] John Allen commented on MNG-661: Hi Vincent, Yeah i think this is a more approrpiate approach, especially as its only intended for testing. So the key to the the simulate mode is that

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_52004 ] John Allen commented on MNG-1643: - brett, although i agree with you in terms of better componentisation of the design i cant think of a use case where anyone will want to make more than

[jira] Commented: (MNG-1531) add a report mojo to create a an effective pom and effective settings report (to be used in site generation)

[ http://jira.codehaus.org/browse/MNG-1531?page=comments#action_52003 ] John Allen commented on MNG-1531: - indeed regarding external publication of sensitive data but as many organisations use the maven generated project site to act as the a project's statu

[jira] Commented: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails

[ http://jira.codehaus.org/browse/MNG-1667?page=comments#action_51778 ] John Allen commented on MNG-1667: - >From build output:- [INFO] [INFO] BUILD SUCCESSFUL [INFO] ---

[jira] Created: (MNG-1667) M2_HOME is not used in the way described in README.txt and as such bootstrap build fails

M2_HOME is not used in the way described in README.txt and as such bootstrap build fails Key: MNG-1667 URL: http://jira.codehaus.org/browse/MNG-1667 Project: Maven 2 Type: Bug

[jira] Commented: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=comments#action_51763 ] John Allen commented on MNG-661: Vincent, youre right regarding the limitations of using the projects 'published' URL location for building backward and fwd refs, namely that they only w

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_51683 ] John Allen commented on MNG-1643: - Works a treat. Theres a minor change required to the download report mojo to map the custom installer formats to be refered to as exes when building th

[jira] Commented: (MNG-1643) Provide installer support like NSIS or InnoSetup

[ http://jira.codehaus.org/browse/MNG-1643?page=comments#action_51635 ] John Allen commented on MNG-1643: - Thanks for the JIRA, will review shortly (day job getting in the way...) > Provide installer support like NSIS or InnoSetup > -

[jira] Created: (MNG-1531) add a report mojo to create a an effective pom and effective settings report (to be used in site generation)

add a report mojo to create a an effective pom and effective settings report (to be used in site generation) Key: MNG-1531 URL: http://jira.codehaus.org/browse/MNG-1531

[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=all ] John Allen updated MNG-661: --- Attachment: SiteMojoPatch.txt Sigh. i got the whole distributionManagement::site::URL thing about face, taking the distro site details to reflect the projects site's URL locatio

[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=all ] John Allen updated MNG-661: --- Attachment: SiteMojoPatch.txt My bad, missed bug for leaf nodes that resulted in empty modules menu. New patch has one line difference to previous patch, namely line 791 (in pat

[jira] Updated: (MNG-661) In parent site, automatically create link to modules sites and vice-versa

[ http://jira.codehaus.org/browse/MNG-661?page=all ] John Allen updated MNG-661: --- Attachment: SiteMojoPatch.txt Patch reinstates modules support through use of reactor projects and the parsing of their distributionManagement site information. > In parent sit

[jira] Created: (MNG-1398) site report generates an 'empty' target/site/apidocs/index.html

site report generates an 'empty' target/site/apidocs/index.html --- Key: MNG-1398 URL: http://jira.codehaus.org/browse/MNG-1398 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Versions: 2

[jira] Created: (MNG-1009) Is it possible for all plugins to suport a common goal that causes the plugin to describe itself, its goals and its properties?

Is it possible for all plugins to suport a common goal that causes the plugin to describe itself, its goals and its properties? --- Key: MNG-1009 URL: http

[jira] Created: (MNG-965) Provide new javadoc:aggregate goal to perform javadoc operation on project and subprojects.

Provide new javadoc:aggregate goal to perform javadoc operation on project and subprojects. --- Key: MNG-965 URL: http://jira.codehaus.org/browse/MNG-965 Project: Maven 2 Type: I

[jira] Commented: (MNG-942) Ability to source system properties in settings.xml

[ http://jira.codehaus.org/browse/MNG-942?page=comments#action_46854 ] John Allen commented on MNG-942: > " (I'm assuming that by 'source Java System properties' you mean setting > them, like System.setProperty or -Dprop=val). " By source Java System propet

[jira] Created: (MNG-942) Ability to source system properties in settings.xml

Ability to source system properties in settings.xml --- Key: MNG-942 URL: http://jira.codehaus.org/browse/MNG-942 Project: Maven 2 Type: Wish Versions: 2.0-beta-1 Environment: Maven 2.0-beta-1 WIN XP PRO SP2 ja

[jira] Created: (MNG-941) Deletion of ~/.m2 directory prevents (re)creation of plugin-registry.xml file with java.io.FileNotFoundException

Deletion of ~/.m2 directory prevents (re)creation of plugin-registry.xml file with java.io.FileNotFoundException Key: MNG-941 URL: http://jira.codehaus.org/browse/MNG