[jira] Commented: (MSITE-594) release:stage does not properly compute new distroManagement.site.URL or project.URLs for projects

[ https://jira.codehaus.org/browse/MSITE-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=272022#comment-272022 ] John Allen commented on MSITE-594: -- Although it has been a while a quick re-reading of my original

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165421#action_165421 ] John Allen commented on MSITE-129: -- module != child modules list empty if modules don't use this

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165319#action_165319 ] John Allen commented on MSITE-129: -- df modules list empty if modules don't use this project as

[jira] Issue Comment Edited: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=165319#action_165319 ] John Allen edited comment on MSITE-129 at 2/12/09 12:00 PM: Module

[jira] Created: (MRELEASE-395) release:stage does not properly compute new distroManagement.site.URL or project.URLs for projects

release:stage does not properly compute new distroManagement.site.URL or project.URLs for projects -- Key: MRELEASE-395 URL:

[jira] Commented: (MSITE-358) site.xml urls are not always correct

[ http://jira.codehaus.org/browse/MSITE-358?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157108#action_157108 ] John Allen commented on MSITE-358: -- Over enthusiatsic application or resolveRelativeLinks, probably

[jira] Commented: (MSITE-163) The modules menu is not inherited if the parent project has no modules of its own

[ http://jira.codehaus.org/browse/MSITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157109#action_157109 ] John Allen commented on MSITE-163: -- Worth seeing MSHARED-83 too. The modules menu is not inherited

[jira] Commented: (MSITE-136) when inheriting site.xml the menu ref='parent' expands to a menu with links for *all* ancestors and not just the immediate parent

[ http://jira.codehaus.org/browse/MSITE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157110#action_157110 ] John Allen commented on MSITE-136: -- Patch for this is in MSHARED-83 when inheriting site.xml the

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=157111#action_157111 ] John Allen commented on MSITE-129: -- Modules should be modules and not children? Fixed in patch

[jira] Created: (MSHARED-83) populateModulesMenuItemsFromReactorProjects logic is incorrect, a module does not have to be a child

populateModulesMenuItemsFromReactorProjects logic is incorrect, a module does not have to be a child Key: MSHARED-83 URL:

[jira] Commented: (MSHARED-83) populateModulesMenuItemsFromReactorProjects logic is incorrect, a module does not have to be a child

[ http://jira.codehaus.org/browse/MSHARED-83?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155380#action_155380 ] John Allen commented on MSHARED-83: --- Having a closer look I also see that the old bug where

[jira] Updated: (MSHARED-83) populateModulesMenuItemsFromReactorProjects logic is incorrect, a module does not have to be a child

[ http://jira.codehaus.org/browse/MSHARED-83?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MSHARED-83: -- Attachment: 1.0.1-modules-patch.diff addresses the repeated parents menu items bug that results in all

[jira] Commented: (MCHANGELOG-87) Wrong svn path if artifactid != directory

[ http://jira.codehaus.org/browse/MCHANGELOG-87?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=155155#action_155155 ] John Allen commented on MCHANGELOG-87: -- there a quite a few situations where maven assumes

[jira] Created: (DOXIASITETOOLS-9) PathDescriptor fails to create proper absolute paths from relative components, as expected by DefaultDecorationModelInheritanceAssembler.convertPaths

PathDescriptor fails to create proper absolute paths from relative components, as expected by DefaultDecorationModelInheritanceAssembler.convertPaths

[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121577 ] John Allen commented on MRELEASE-261: - Subclipse plugin for Eclipse can not handle nested projects in Eclipse at all,

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121577 ] skaze edited comment on MRELEASE-261 at 1/28/08 5:35 PM: -- Subclipse plugin for Eclipse can

[jira] Issue Comment Edited: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121582 ] skaze edited comment on MSITE-129 at 1/28/08 5:50 PM: --- Yeah you're right, the assumption that a

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121582 ] John Allen commented on MSITE-129: -- Yeah you're right, the relation between module to parent should not be there. modules

[jira] Commented: (MSITE-136) when inheriting site.xml the menu ref='parent' expands to a menu with links for *all* ancestors and not just the immediate parent

[ http://jira.codehaus.org/browse/MSITE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121581 ] John Allen commented on MSITE-136: -- I ended up moving this out and making changes to attach-descriptor too, see MSITE-135

[jira] Commented: (MSITE-163) site modules menu does not inherit

[ http://jira.codehaus.org/browse/MSITE-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121580 ] John Allen commented on MSITE-163: -- This may be due to change (incorrect now in IMHO) that stated a module must inherit

[jira] Commented: (MSITE-135) inherited site.xml files are interpolated with the originating project's model values and not the consumer project's values

[ http://jira.codehaus.org/browse/MSITE-135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121579 ] John Allen commented on MSITE-135: -- In regards to the multiple parent items appearing in the final leaf site, as a quick

[jira] Commented: (MSITE-276) Links on Modules are completely broken on site:stage

[ http://jira.codehaus.org/browse/MSITE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121592 ] John Allen commented on MSITE-276: -- stage does seem to now have difficulties since beta-6 Links on Modules are completely

[jira] Commented: (MSITE-236) multi module reporting - main page doesn't show links to contained modules

[ http://jira.codehaus.org/browse/MSITE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121591 ] John Allen commented on MSITE-236: -- dup of other 'empty modules menu'? multi module reporting - main page doesn't show

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121583 ] John Allen commented on MSITE-129: -- It's not a difficult fix, detection of the modules uses reactor or filesystem and uses

[jira] Commented: (MSITE-209) populateModulesMenu() logic results in invalid modules list if projects share artifactIds

[ http://jira.codehaus.org/browse/MSITE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121586 ] John Allen commented on MSITE-209: -- This is now defunct, modules identification should no longer have any bearing on who

[jira] Commented: (MSITE-275) site:stage for multimodule project creates wrong links

[ http://jira.codehaus.org/browse/MSITE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_121587 ] John Allen commented on MSITE-275: -- We also experience this, the new relative link processing done in beta-6 doesnt work

[jira] Commented: (MINVOKER-22) Add feature to install plugin to a local repository.

[ http://jira.codehaus.org/browse/MINVOKER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118945 ] John Allen commented on MINVOKER-22: We use the maven-component-it-plugin for this but see Brett's comparison matrix

[jira] Issue Comment Edited: (MNG-3244) inherited site url not properly handling parameters

[ http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118450 ] skaze edited comment on MNG-3244 at 1/5/08 7:55 AM: - After playing with some patch some more i came

[jira] Commented: (MNG-3344) Provide new POM element to configure site directory (e.g. src/site)

[ http://jira.codehaus.org/browse/MNG-3344?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118824 ] John Allen commented on MNG-3344: - I think there are a few reporting plugins that have had to rely upon using the default

[jira] Commented: (MNG-3244) inherited site url not properly handling parameters

[ http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118450 ] John Allen commented on MNG-3244: - After playing with some patch some more i came across another problem beyond the one

[jira] Commented: (MNG-3244) inherited site url not properly handling parameters

[ http://jira.codehaus.org/browse/MNG-3244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_118289 ] John Allen commented on MNG-3244: - remember that the site distro URL and the project URL are related. If you add the

[jira] Commented: (MINVOKER-14) release maven-invoker

[ http://jira.codehaus.org/browse/MINVOKER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_116431 ] John Allen commented on MINVOKER-14: would allow us to drop local corporate version +1 release maven-invoker

[jira] Commented: (MRELEASE-230) release:prepare cannot update the version of a module in a multi-module build if you have both normal artifact and attached artifact in dependencies

[ http://jira.codehaus.org/browse/MRELEASE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113386 ] John Allen commented on MRELEASE-230: - did you develop a patch for this? release:prepare cannot update the version

[jira] Created: (MNG-3249) Profile resident POM element overrides do not effect inherited projects if the children have their own explicitly defined elements.

Profile resident POM element overrides do not effect inherited projects if the children have their own explicitly defined elements. --- Key: MNG-3249

[jira] Issue Comment Edited: (MPMD-55) The Xml pmd file isn't encode to UTF8 charset counter the charset declaration in the file header

[ http://jira.codehaus.org/browse/MPMD-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110084 ] John Allen edited comment on MPMD-55 at 10/16/07 12:53 PM: --- Just encountered this ourselves, will try

[jira] Commented: (MPMD-55) The Xml pmd file isn't encode to UTF8 charset counter the charset declaration in the file header

[ http://jira.codehaus.org/browse/MPMD-55?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_110084 ] John Allen commented on MPMD-55: Just encountered this ourselves, what's the fix? The Xml pmd file isn't encode to UTF8

[jira] Created: (MNG-3192) Properties not effective in inherited reportingpluginsplugininherited elements in child projects

Properties not effective in inherited reportingpluginsplugininherited elements in child projects Key: MNG-3192 URL: http://jira.codehaus.org/browse/MNG-3192

[jira] Commented: (MSITE-209) populateModulesMenu() logic results in invalid modules list if projects share artifactIds

[ http://jira.codehaus.org/browse/MSITE-209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_106281 ] John Allen commented on MSITE-209: -- Crazy busy at the moment but yes of course (will take some time though sorry). The

[jira] Created: (SUREFIRE-348) Proivde a surefire aggregate option for report-only mojo

Proivde a surefire aggregate option for report-only mojo Key: SUREFIRE-348 URL: http://jira.codehaus.org/browse/SUREFIRE-348 Project: Maven Surefire Issue Type: New Feature

[jira] Commented: (MSITE-245) parent filesystem site.xml is never be found

[ http://jira.codehaus.org/browse/MSITE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104922 ] John Allen commented on MSITE-245: -- I'm not sure I exactly follow you John, I've had a look at the patch and the opening

[jira] Issue Comment Edited: (MSITE-245) parent filesystem site.xml is never be found

[ http://jira.codehaus.org/browse/MSITE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104922 ] John Allen edited comment on MSITE-245 at 8/15/07 10:49 AM: I'm not sure I exactly follow you

[jira] Issue Comment Edited: (MSITE-245) parent filesystem site.xml is never be found

[ http://jira.codehaus.org/browse/MSITE-245?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104922 ] John Allen edited comment on MSITE-245 at 8/15/07 11:10 AM: I'm not sure I exactly follow you

[jira] Created: (MNG-3133) DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths

DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths - Key: MNG-3133 URL: http://jira.codehaus.org/browse/MNG-3133 Project:

[jira] Created: (MNG-3134) DefaultModelInheritence::assembleDistributionInheritence should be childPathAdjustment aware

DefaultModelInheritence::assembleDistributionInheritence should be childPathAdjustment aware Key: MNG-3134 URL: http://jira.codehaus.org/browse/MNG-3134

[jira] Issue Comment Edited: (MNG-2209) Calculation of module URLs does not match deployment

[ http://jira.codehaus.org/browse/MNG-2209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104029 ] John Allen edited comment on MNG-2209 at 8/5/07 11:27 AM: -- MNG-3134 fixes this issue was: MNG3133

[jira] Commented: (MNG-2290) Generated URLs in POMs of child modules

[ http://jira.codehaus.org/browse/MNG-2290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_104030 ] John Allen commented on MNG-2290: - This is an issue that we've been living with for ages and continues to result in hassle

[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103999 ] John Allen commented on MJAVADOC-140: - except I don't think getExecutionProject can be relied upon to always return a

[jira] Commented: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

[ http://jira.codehaus.org/browse/MJAVADOC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103594 ] John Allen commented on MJAVADOC-140: - I only saw maven-javadoc-plugin\src\it\MJAVADOC-110 under IT, do the ITs reside

[jira] Updated: (MCHANGELOG-74) Combined patch for MCHANGELOG-69, MCHANGELOG-70, MCHANGELOG-71, MCHANGELOG-72, MCHANGELOG-73

[ http://jira.codehaus.org/browse/MCHANGELOG-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-74: - Attachment: MCHANGELOG-69,70,71,72,73.patch previous patch was missing a call to sinkAuthorNames()

[jira] Updated: (MCLOVER-80) aggregate is not respecting the true module hierarchy and creates merged databases containing non-sibling data

[ http://jira.codehaus.org/browse/MCLOVER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCLOVER-80: -- Attachment: MCLOVER-80.diff it has been observed that a module hierarchy is very different to the project

[jira] Issue Comment Edited: (MCLOVER-80) aggregate is not respecting the true module hierarchy and creates merged databases containing non-sibling data

[ http://jira.codehaus.org/browse/MCLOVER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103541 ] John Allen edited comment on MCLOVER-80 at 7/29/07 6:46 AM: it has been observed that a module

[jira] Updated: (MCLOVER-80) aggregate is not respecting the true module hierarchy and creates merged databases containing non-sibling data

[ http://jira.codehaus.org/browse/MCLOVER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCLOVER-80: -- Attachment: MCLOVER-80.diff aggregate is not respecting the true module hierarchy and creates merged

[jira] Created: (MJAVADOC-140) test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool

test-javadoc run in aggregate mode does not pass correct classpath to javadoc tool -- Key: MJAVADOC-140 URL: http://jira.codehaus.org/browse/MJAVADOC-140 Project: Maven

[jira] Commented: (MJAVADOC-137) javadoc:javadoc always runs as aggregator

[ http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103491 ] John Allen commented on MJAVADOC-137: - My observation should have been that when report MOJOs are run from the site

[jira] Commented: (MCHANGELOG-71) Support a %REV% in displayFileDetailUrl in the same way we support %FILE

[ http://jira.codehaus.org/browse/MCHANGELOG-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103494 ] John Allen commented on MCHANGELOG-71: -- Looking at this further I have implemented this feature with a new parameter

[jira] Updated: (MCHANGELOG-71) Support a %REV% in displayFileDetailUrl in the same way we support %FILE

[ http://jira.codehaus.org/browse/MCHANGELOG-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-71: - Attachment: MCHANGELOG-71.patch Patch provides displayFileRevDetailUrl option that can be used to

[jira] Commented: (MCHANGELOG-72) Provide a way to make the changeset revision number used in the changelog report an active link

[ http://jira.codehaus.org/browse/MCHANGELOG-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103497 ] John Allen commented on MCHANGELOG-72: -- ps. codehaus JIRA administrator - you may wish to consider letting the

[jira] Updated: (MCHANGELOG-70) Support a URL filter that enables JIRA/bugzilla/whatever IDs quoted in SCM message to be mapped to real URLs

[ http://jira.codehaus.org/browse/MCHANGELOG-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-70: - Attachment: MCHANGELOG-70.patch Patch provides two new options: {code} /** * A pattern

[jira] Updated: (MCHANGELOG-70) Support a URL filter that enables JIRA/bugzilla/whatever IDs quoted in SCM message to be mapped to real URLs

[ http://jira.codehaus.org/browse/MCHANGELOG-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-70: - Attachment: MCHANGELOG-70.patch Mistake in the 'ticketLinkRegexPattern' default value - an extra

[jira] Updated: (MCHANGELOG-70) Support a URL filter that enables JIRA/bugzilla/whatever IDs quoted in SCM message to be mapped to real URLs

[ http://jira.codehaus.org/browse/MCHANGELOG-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-70: - Attachment: MCHANGELOG-70,71,72.patch Combined patch for MCHANGELOG-70, MCHANGELOG-71 and

[jira] Commented: (MCHANGELOG-72) Provide a way to make the changeset revision number used in the changelog report an active link

[ http://jira.codehaus.org/browse/MCHANGELOG-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103502 ] John Allen commented on MCHANGELOG-72: -- See http://jira.codehaus.org/browse/MCHANGELOG-70#action_103500 for a

[jira] Created: (MCHANGELOG-73) Print developer names in the change report for known developers and make them links to the team page.

Print developer names in the change report for known developers and make them links to the team page. - Key: MCHANGELOG-73 URL:

[jira] Updated: (MCHANGELOG-69) Print developer names regardless of whether they're listed in the POM

[ http://jira.codehaus.org/browse/MCHANGELOG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-69: - Attachment: MCHANGELOG-69,73.patch Patch against trunk, 560535. It's combined with the

[jira] Updated: (MCHANGELOG-73) Print developer names in the change report for known developers and make them links to the team page.

[ http://jira.codehaus.org/browse/MCHANGELOG-73?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-73: - Attachment: MCHANGELOG-69,73.patch Patch against trunk, 560535. It's combined with the

[jira] Updated: (MCHANGELOG-74) Combined patch for MCHANGELOG-69, MCHANGELOG-70, MCHANGELOG-71, MCHANGELOG-72, MCHANGELOG-73

[ http://jira.codehaus.org/browse/MCHANGELOG-74?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-74: - Attachment: MCHANGELOG-69,70,71,72,73.patch removed unnecessary change to ChangeLogReportTest

[jira] Created: (MCHANGELOG-74) Combined patch for MCHANGELOG-69, MCHANGELOG-70, MCHANGELOG-71, MCHANGELOG-72, MCHANGELOG-73

Combined patch for MCHANGELOG-69, MCHANGELOG-70, MCHANGELOG-71, MCHANGELOG-72, MCHANGELOG-73 Key: MCHANGELOG-74 URL: http://jira.codehaus.org/browse/MCHANGELOG-74

[jira] Updated: (MCHANGELOG-69) Print developer names regardless of whether they're listed in the POM

[ http://jira.codehaus.org/browse/MCHANGELOG-69?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-69: - Attachment: MCHANGELOG-69,73.patch fixes NPE in unit tests from a lack of valid injected developers

[jira] Updated: (MCHANGELOG-70) Support a URL filter that enables JIRA/bugzilla/whatever IDs quoted in SCM message to be mapped to real URLs

[ http://jira.codehaus.org/browse/MCHANGELOG-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-70: - Attachment: MCHANGELOG-70.patch fixes unit tests failures from NPEs due to a lack of parameter

[jira] Updated: (MCHANGELOG-71) Support a %REV% in displayFileDetailUrl in the same way we support %FILE

[ http://jira.codehaus.org/browse/MCHANGELOG-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-71: - Attachment: MCHANGELOG-71.patch changed base path of patch Support a %REV% in

[jira] Updated: (MCHANGELOG-70) Support a URL filter that enables JIRA/bugzilla/whatever IDs quoted in SCM message to be mapped to real URLs

[ http://jira.codehaus.org/browse/MCHANGELOG-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCHANGELOG-70: - Attachment: MCHANGELOG-70,71,72.patch fixes NPEs in unit tests due to a lack of injected

[jira] Created: (MJAVADOC-139) NPE out of AbstractJavadocMojo::getSourcePaths() on multimodule project using aggregate

NPE out of AbstractJavadocMojo::getSourcePaths() on multimodule project using aggregate --- Key: MJAVADOC-139 URL: http://jira.codehaus.org/browse/MJAVADOC-139

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103349 ] John Allen commented on MSITE-129: -- Matt, In regards to your structure. We are a massive information services company and

[jira] Commented: (MSITE-132) Use artefactID instead of name for directories

[ http://jira.codehaus.org/browse/MSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103350 ] John Allen commented on MSITE-132: -- Jorg, The logic of stage is fairly obvious. one is simulating the real world

[jira] Updated: (MCLOVER-80) aggregate is not respecting the true module hierarchy and creates merged databases containing non-sibling data

[ http://jira.codehaus.org/browse/MCLOVER-80?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John Allen updated MCLOVER-80: -- Attachment: MCLOVER-80.diff After discussion it appears that some people would like aggregate to include

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103404 ] John Allen commented on MSITE-129: -- Kenney, how can we go about dealing with these two cases? * A user wishes to have all

[jira] Commented: (MJAVADOC-137) javadoc:javadoc always runs as aggregator

[ http://jira.codehaus.org/browse/MJAVADOC-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103388 ] John Allen commented on MJAVADOC-137: - If you run the javadoc plugin as report then the @aggregator is ignored (see

[jira] Commented: (MSITE-132) Use artefactID instead of name for directories

[ http://jira.codehaus.org/browse/MSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103374 ] John Allen commented on MSITE-132: -- Guess I'm not explaining myself very well :) Re the name being used to create the path

[jira] Issue Comment Edited: (MNG-41) best practices: site management

[ http://jira.codehaus.org/browse/MNG-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103358 ] John Allen edited comment on MNG-41 at 7/26/07 6:54 AM: I know I've been banging this drum from day one

[jira] Commented: (MNG-367) best practices: multi-user installation

[ http://jira.codehaus.org/browse/MNG-367?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103359 ] John Allen commented on MNG-367: Re installers - We deploy our developers java environment via a nice looking NSIS installer

[jira] Commented: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI

[ http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103352 ] John Allen commented on MSITE-159: -- I think something along the lines of 'convert URLs to relative URLs where possible' is

[jira] Commented: (MNG-41) best practices: site management

[ http://jira.codehaus.org/browse/MNG-41?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103358 ] John Allen commented on MNG-41: --- I know I've been banging this drum from day one so I'm obviously off 'Maven message' in this

[jira] Created: (MCHANGELOG-71) Support a %REV% in displayFileDetailUrl in the same way we support %FILE

Support a %REV% in displayFileDetailUrl in the same way we support %FILE Key: MCHANGELOG-71 URL: http://jira.codehaus.org/browse/MCHANGELOG-71 Project: Maven 2.x Changelog

[jira] Created: (MCHANGELOG-68) testReadFile unit test timebased comparisons fail

testReadFile unit test timebased comparisons fail - Key: MCHANGELOG-68 URL: http://jira.codehaus.org/browse/MCHANGELOG-68 Project: Maven 2.x Changelog Plugin Issue Type: Bug Affects

[jira] Commented: (MSITE-132) Use artefactID instead of name for directories

[ http://jira.codehaus.org/browse/MSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103351 ] John Allen commented on MSITE-132: -- Denis, Ahh, it's only if you have no distroManagement section that it invents the path

[jira] Commented: (MSITE-177) Docs are not updated if only site.xml changed

[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102985 ] John Allen commented on MSITE-177: -- Same here, the logic is obviously broken in regards to what requires a rebuild. if

[jira] Commented: (MSITE-79) mechanism for local preview of a multiproject site tree

[ http://jira.codehaus.org/browse/MSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102990 ] John Allen commented on MSITE-79: - stage was supposed to be a peer of deploy, ie a 'deploy to local directory' function -

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103004 ] John Allen commented on MSITE-129: -- I'm curious should a site be displaying a project's modules or a project's children

[jira] Issue Comment Edited: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103004 ] John Allen edited comment on MSITE-129 at 7/23/07 12:30 PM: I'm curious should a site be

[jira] Commented: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI

[ http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103012 ] John Allen commented on MSITE-159: -- Re isnt that why you define them as absolute? Well yes but also not really, a project's

[jira] Issue Comment Edited: (MSITE-159) Absolute URI rendered as relative URI if absolute URI related to domain of POM URI

[ http://jira.codehaus.org/browse/MSITE-159?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103012 ] John Allen edited comment on MSITE-159 at 7/23/07 12:48 PM: IMHO a project.URL is supposed to

[jira] Commented: (MSITE-132) Use artefactID instead of name for directories

[ http://jira.codehaus.org/browse/MSITE-132?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103013 ] John Allen commented on MSITE-132: -- There are indeed some gotchas re the naming of artifactIds and directories in Maven.

[jira] Commented: (MSITE-236) multi module reporting - main page doesn't show links to contained modules

[ http://jira.codehaus.org/browse/MSITE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103014 ] John Allen commented on MSITE-236: -- If you mean modules menu, in the top LHS (using the default site.xml) then yes they

[jira] Commented: (MSITE-169) links to modules where not working if a modules dir is used

[ http://jira.codehaus.org/browse/MSITE-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103015 ] John Allen commented on MSITE-169: -- By default maven assumes that modules live under the parent project's directory. And

[jira] Commented: (MSITE-195) Module navigation entries point to index.html not moduleName/index.html

[ http://jira.codehaus.org/browse/MSITE-195?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_103018 ] John Allen commented on MSITE-195: -- Probably related to the way the modules have been found (ie via reactor, via filesystem

[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102667 ] John Allen commented on MRELEASE-261: - Well in that case the common directory is '/' which is probably not what you

[jira] Commented: (MSITE-136) when inheriting site.xml the menu ref='parent' expands to a menu with links for *all* ancestors and not just the immediate parent

[ http://jira.codehaus.org/browse/MSITE-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102676 ] John Allen commented on MSITE-136: -- Okay this is definitely due to the above, i.e. for every parent in the hierarchy of the

[jira] Commented: (MRELEASE-6) Multiproject Release: No check in

[ http://jira.codehaus.org/browse/MRELEASE-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102609 ] John Allen commented on MRELEASE-6: --- Dear all, we have converted release 3 plugin to work just fine with flat based

[jira] Commented: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102611 ] John Allen commented on MRELEASE-261: - Dear all, we have converted release 3 plugin to work just fine with flat based

[jira] Issue Comment Edited: (MRELEASE-261) release:prepare shouls support flat directory multimodule projects

[ http://jira.codehaus.org/browse/MRELEASE-261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102611 ] John Allen edited comment on MRELEASE-261 at 7/18/07 12:12 PM: --- Dear all, we have converted

[jira] Commented: (MDEPLOY-57) uniqueVersionfalse/uniqueVersion not honored inside profile

[ http://jira.codehaus.org/browse/MDEPLOY-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102619 ] John Allen commented on MDEPLOY-57: --- We have also seen strange things with profiles not appearing to to be active (or not

  1   2   >