[jira] Closed: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension

[ http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2831. -- > Cannot add custom artifact handler and custom lifecycle as a build extension > --

[jira] Updated: (MNG-2831) Cannot add custom artifact handler and custom lifecycle as a build extension

[ http://jira.codehaus.org/browse/MNG-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2831: --- Just running the ITs against a fix to make sure everything is ok, and then I think this one is licked. > Cannot

[jira] Issue Comment Edited: (MNG-2010) Add new lifecycle phases for IT

[ http://jira.codehaus.org/browse/MNG-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98244 ] Nelz edited comment on MNG-2010 at 6/4/07 12:17 AM: To Kenny: You convinced me. I really like the sound of

[jira] Commented: (MNG-2010) Add new lifecycle phases for IT

[ http://jira.codehaus.org/browse/MNG-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98244 ] Nelz commented on MNG-2010: --- To Kenny: You convinced me. I really like the sound of the "maven-it-plugin"... It is much less 'lite

[jira] Created: (MNG-3032) executedProject is not properly populated by @execute in reporting

executedProject is not properly populated by @execute in reporting -- Key: MNG-3032 URL: http://jira.codehaus.org/browse/MNG-3032 Project: Maven 2 Issue Type: Bug Comp

[jira] Updated: (MPPDF-60) Menu names never appear in the document

[ http://jira.codehaus.org/browse/MPPDF-60?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MPPDF-60: - Attachment: MPPDF-60-20070603-1851.patch This introduces the "chapter" level integer numbered headings

[jira] Commented: (MEV-524) Javadoc jar not uploaded correctly for digester

[ http://jira.codehaus.org/browse/MEV-524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98240 ] Henri Yandell commented on MEV-524: --- > for i in commons-*; do find $i -type f -name '*-javadoc.javadoc.jar'; done commons-conf

[jira] Work stopped: (MRM-376) Clicking an artifact in the Search Results page results to HTTP ERROR: 500

[ http://jira.codehaus.org/browse/MRM-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-376 stopped by Maria Odea Ching. > Clicking an artifact in the Search Results page results to HTTP ERROR: 500 > ---

[jira] Work started: (MRM-409) No checking of invalid poms or artifacts during repository scanning resulting to some objects not being found on the database

[ http://jira.codehaus.org/browse/MRM-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Work on MRM-409 started by Maria Odea Ching. > No checking of invalid poms or artifacts during repository scanning resulting > to some objects not being found on the database > -

[jira] Updated: (MNG-2100) v3 pom properties is already supported in v4 poms and should be converted accordingly

[ http://jira.codehaus.org/browse/MNG-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brett Porter updated MNG-2100: -- Fix Version/s: (was: 2.2) > v3 pom properties is already supported in v4 poms and should be converted > ac

[jira] Closed: (MEV-461) Missing pom for commons-logging-api-1.1

[ http://jira.codehaus.org/browse/MEV-461?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed MEV-461. - Resolution: Fixed Pom now deployed. > Missing pom for commons-logging-api-1.1 > -

[jira] Closed: (MNG-2100) v3 pom properties is already supported in v4 poms and should be converted accordingly

[ http://jira.codehaus.org/browse/MNG-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edwin Punzalan closed MNG-2100. --- Resolution: Fixed Fix Version/s: (was: 2.2.x) 2.2 > v3 pom properties is alread

[jira] Reopened: (MNG-2100) v3 pom properties is already supported in v4 poms and should be converted accordingly

[ http://jira.codehaus.org/browse/MNG-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Edwin Punzalan reopened MNG-2100: - Assignee: Edwin Punzalan > v3 pom properties is already supported in v4 poms and should be converted >

[jira] Commented: (MNG-2100) v3 pom properties is already supported in v4 poms and should be converted accordingly

[ http://jira.codehaus.org/browse/MNG-2100?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98236 ] Brett Porter commented on MNG-2100: --- Edwin wasn't a committer there until we collapsed the permissions in December so we drop

[jira] Commented: (MNG-2188) Report mojos should check canGenerateReport() when called directly

[ http://jira.codehaus.org/browse/MNG-2188?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98235 ] Brett Porter commented on MNG-2188: --- Vincent, I think your patch is correct. What the report document renderer does is irrele

[jira] Updated: (SUREFIRE-42) TestListenerInvocationHandler incorrectly assumes getName()

[ http://jira.codehaus.org/browse/SUREFIRE-42?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof updated SUREFIRE-42: - Description: I'm running test cases that extend our own custom base test case. If one of the

[jira] Updated: (SUREFIRE-61) Incorrect classpath ordering

[ http://jira.codehaus.org/browse/SUREFIRE-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof updated SUREFIRE-61: - Description: Surefire incorrectly interprets classpath ordering. Steps to reproduce: 1.

[jira] Updated: (MNG-2909) zero length files can be created for metadata

[ http://jira.codehaus.org/browse/MNG-2909?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2909: --- Description: I was getting build fails because of this: Caused by: java.io.EOFException: input contained no d

[jira] Updated: (MNG-2879) Thousands of [WARNING] Component returned which is not the same manager.

[ http://jira.codehaus.org/browse/MNG-2879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2879: --- Affects Version/s: (was: 2.0.8) 2.0.6 Fix Version/s: (was: 2.0.7)

[jira] Commented: (MNG-2261) Profiles ignored when working with non-projects (such as archetype:create)

[ http://jira.codehaus.org/browse/MNG-2261?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98220 ] Jason van Zyl commented on MNG-2261: The archetype problem is really something similar to the staging plugin problem where

[jira] Closed: (MPPDF-59) Allow configuration of line height for paragraphs

[ http://jira.codehaus.org/browse/MPPDF-59?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak closed MPPDF-59. Resolution: Won't Fix okay, okay... :) > Allow configuration of line height for paragraphs > -

[jira] Commented: (MPPDF-60) Menu names never appear in the document

[ http://jira.codehaus.org/browse/MPPDF-60?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98218 ] Wendy Smoak commented on MPPDF-60: -- Clarification: the menu name shows up in the table of contents, but is not repeated in th

[jira] Commented: (MPPDF-59) Allow configuration of line height for paragraphs

[ http://jira.codehaus.org/browse/MPPDF-59?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98217 ] Lukas Theussl commented on MPPDF-59: There are a zillion things that could be made configurable, just look at all the hard-

[jira] Created: (MPPDF-60) Menu names never appear in the document

Menu names never appear in the document --- Key: MPPDF-60 URL: http://jira.codehaus.org/browse/MPPDF-60 Project: Maven 1.x PDF Plugin Issue Type: Bug Affects Versions: 2.5.1 Reporter: Wendy

[jira] Created: (MPPDF-59) Allow configuration of line height for paragraphs

Allow configuration of line height for paragraphs - Key: MPPDF-59 URL: http://jira.codehaus.org/browse/MPPDF-59 Project: Maven 1.x PDF Plugin Issue Type: New Feature Affects Versions: 2.5.1

[jira] Commented: (MNG-2521) Using JDK 1.5+ annotations for mojos metadata

[ http://jira.codehaus.org/browse/MNG-2521?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98215 ] Yoav Landman commented on MNG-2521: --- Where can these tools be found? > Using JDK 1.5+ annotations for mojos metadata > --

[jira] Closed: (NMAVEN-68) Sandcastle Maven Plugin

[ http://jira.codehaus.org/browse/NMAVEN-68?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shane Isbell closed NMAVEN-68. -- Resolution: Won't Fix Microsoft unresponsive about whether they would be able to place the config-files and/o

[jira] Commented: (MEV-334) Stax POM points to an invalid XMLBeans dependency

[ http://jira.codehaus.org/browse/MEV-334?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98210 ] Henri Yandell commented on MEV-334: --- Carlos: Should we delete the empty directory? Otherwise I suggest we WONTFIX this as sta

[jira] Commented: (MEV-351) xmlc-xerces-2.2.7.1.jar is unnecessary and xmlc-apis.jar is required.

[ http://jira.codehaus.org/browse/MEV-351?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98209 ] Henri Yandell commented on MEV-351: --- There's an xmlc 2.3 release available now from their website. So we/you/they should just

[jira] Commented: (MEV-320) Hibernate 3.1.x POMs pull in Sun jars

[ http://jira.codehaus.org/browse/MEV-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98207 ] Henri Yandell commented on MEV-320: --- It's still this way in the latest 3.2.4.sp1 > Hibernate 3.1.x POMs pull in Sun jars > -

[jira] Closed: (MEV-33) XOM POM references xercesImpl v.2.2.1 which does not exist in repo

[ http://jira.codehaus.org/browse/MEV-33?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed MEV-33. Resolution: Fixed Now there. > XOM POM references xercesImpl v.2.2.1 which does not exist in repo >

[jira] Closed: (MEV-31) XOM POM references xmlParserAPIs v2.6.1 which is not in the repo

[ http://jira.codehaus.org/browse/MEV-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henri Yandell closed MEV-31. Resolution: Fixed Seem to be there now: http://repo1.maven.org/maven2/xerces/xmlParserAPIs/2.6.1/ > XOM POM referen

[jira] Commented: (MEV-504) Jetty 5.1.10 and 5.1.11 missing poms

[ http://jira.codehaus.org/browse/MEV-504?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98204 ] Henri Yandell commented on MEV-504: --- Asked for status on #jetty; janb is the one to talk to. > Jetty 5.1.10 and 5.1.11 missing

[jira] Commented: (MEV-461) Missing pom for commons-logging-api-1.1

[ http://jira.codehaus.org/browse/MEV-461?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98203 ] Henri Yandell commented on MEV-461: --- Pom deployed from the commons-logging-api.pom found in the commons logging trunk. Only ch

[jira] Commented: (MEV-457) Geronimo jar fails to download

[ http://jira.codehaus.org/browse/MEV-457?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98202 ] Henri Yandell commented on MEV-457: --- Touching the files doesn't seem to have worked. Will dig into this further so I can under

[jira] Commented: (MNG-2646) [PATCH] MavenProjectBuilder.buildFromRepository(...) does not support profiles

[ http://jira.codehaus.org/browse/MNG-2646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98201 ] Christian Schulte commented on MNG-2646: Can you please provide an example for having profiles supported for dependent

[jira] Commented: (MSOURCES-16) Unable to find the mojo 'org.apache.maven.plugins:maven-source-plugin:2.0.3:aggregate'

[ http://jira.codehaus.org/browse/MSOURCES-16?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98199 ] Vincent Siveton commented on MSOURCES-16: - I was unable to reproduce it on several projects like maven-2.0.x. Could

[jira] Created: (MNG-3031) Within a model duplicate dependency declarations should be considered an error and halt execution

Within a model duplicate dependency declarations should be considered an error and halt execution - Key: MNG-3031 URL: http://jira.codehaus.org/browse/MNG-3031

[jira] Updated: (MNG-2743) Dependency poms not timely merged with parents

[ http://jira.codehaus.org/browse/MNG-2743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MNG-2743: - Affects Version/s: 2.0.6 Also affects 2.0.6 per Grzegorz Kossakowski on #maven. > Dependency poms not timely mer

[jira] Commented: (MNG-2771) Provide a means of loading custom substitute components instead of default Maven components

[ http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98192 ] Kenney Westerhof commented on MNG-2771: --- I don't think this'll be available in 2.0.x, as it uses some heavily refactored

[jira] Closed: (JXR-51) Javadoc link broken for site:stage

[ http://jira.codehaus.org/browse/JXR-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed JXR-51. -- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.2 Handle the stagingDirectory for th

[jira] Commented: (MNG-2010) Add new lifecycle phases for IT

[ http://jira.codehaus.org/browse/MNG-2010?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98190 ] Kenney Westerhof commented on MNG-2010: --- I have to agree with jason and john - keep the lifecycle small. About a year ago

[jira] Closed: (WAGONSSH-57) scp prefixes remote dir with last two chars of domain name

[ http://jira.codehaus.org/browse/WAGONSSH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Nathan Coast closed WAGONSSH-57. Resolution: Cannot Reproduce missing '//' in the scp:// causing the error > scp prefixes remote dir wi

[jira] Commented: (WAGONSSH-57) scp prefixes remote dir with last two chars of domain name

[ http://jira.codehaus.org/browse/WAGONSSH-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98185 ] Nathan Coast commented on WAGONSSH-57: -- below is the distribution management config I'm using

[jira] Closed: (JXR-53) Add a link to test javadoc

[ http://jira.codehaus.org/browse/JXR-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed JXR-53. -- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.2 fixed > Add a link to test javado

[jira] Created: (JXR-53) Add a link to test javadoc

Add a link to test javadoc --- Key: JXR-53 URL: http://jira.codehaus.org/browse/JXR-53 Project: Maven JXR Issue Type: Bug Components: maven2 jxr plugin Affects Versions: 2.1 Reporter: Vincen

[jira] Closed: (JXR-52) Dont generate xref report if project has pom packaging and src/main exists

[ http://jira.codehaus.org/browse/JXR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed JXR-52. -- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.2 Fixed > Dont generate xref report

[jira] Updated: (MJAVADOC-125) Dont generate javadoc report if project has pom packaging and src/main exists

[ http://jira.codehaus.org/browse/MJAVADOC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-125: - Description: {noformat} project\ |-- pom.xml => POM packaging |-- module1\ | `-- pom.xml

[jira] Updated: (JXR-52) Dont generate xref report if project has pom packaging and src/main exists

[ http://jira.codehaus.org/browse/JXR-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated JXR-52: --- Summary: Dont generate xref report if project has pom packaging and src/main exists (was: Dont generate xref r

[jira] Commented: (NMAVEN-71) Replace various hard-coded paths with environment-aware versions

[ http://jira.codehaus.org/browse/NMAVEN-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_98174 ] Campbell Boucher-Burnet commented on NMAVEN-71: --- No, thank you Shane. I'm the application software architect for