[jira] Created: (MNG-1769) Javadoc plugin defaults to showing package private items, but should default to protected

: Bug Components: maven-javadoc-plugin Reporter: David Jackman The default access level for items shown in the Javadocs when using the Javadoc tool directly is protected (see http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#protected). However, the default access level for

[jira] Updated: (MNG-1768) excludePackageNames property doesn't work

[ http://jira.codehaus.org/browse/MNG-1768?page=all ] David Jackman updated MNG-1768: --- Attachment: MNG-1768.patch I'm attaching a patch that fixes this problem. It allows excluded package names to be separated by a space, comma, semicolon, or

[jira] Created: (MNG-1768) excludePackageNames property doesn't work

excludePackageNames property doesn't work - Key: MNG-1768 URL: http://jira.codehaus.org/browse/MNG-1768 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Reporter: David Jackman The Javadoc plugin p

[jira] Created: (MNG-1765) Overview parameter isn't having backslashes fixed before writing out to arguments

nents: maven-javadoc-plugin Reporter: David Jackman Attachments: overviewparameter.patch When using the overview parameter for the Javadoc plugin, the value (which is a path) isn't correctly converted to use forward slashes instead of backslashes. The attached patch fixes the problem.

[jira] Commented: (MNG-441) surefire plugin needs to be able to fork tests

[ http://jira.codehaus.org/browse/MNG-441?page=comments#action_51688 ] David Jackman commented on MNG-441: --- One feature of forking the tests that we're currently using in M1 is the working directory for the test process (maven.junit.dir). It'

[jira] Created: (MNG-1647) Add a parameter to install a custom pom when using install:install-file

-plugin Reporter: David Jackman Priority: Minor Right now, I can install a 3rd party artifact to my repository using install:install-file then, in a separate command, install a custom pom for that artifact using install:install-file again with packaging set to pom and the file

[jira] Created: (MNG-1646) Optional tag in project dependency doesn't work

Optional tag in project dependency doesn't work --- Key: MNG-1646 URL: http://jira.codehaus.org/browse/MNG-1646 Project: Maven 2 Type: Bug Components: maven-core Versions: 2.0 Reporter: David Jackma

[jira] Updated: (MNG-1499) Execution order is arbitrary if inheritance is involved

[ http://jira.codehaus.org/browse/MNG-1499?page=all ] David Jackman updated MNG-1499: --- Attachment: MNG-1499-b.patch After further inspection, I realized that the ModelUtils.mergePluginDefinitions method had the same problem. The second attached patch

[jira] Updated: (MNG-1499) Execution order is arbitrary if inheritance is involved

[ http://jira.codehaus.org/browse/MNG-1499?page=all ] David Jackman updated MNG-1499: --- Attachment: MNG-1499.patch The attached patch fixes this problem. Instead of keeping the list of merged plugins for parent and child in a map, it keeps the list in a

[jira] Created: (MNG-1499) Execution order is arbitrary if inheritance is involved

Execution order is arbitrary if inheritance is involved --- Key: MNG-1499 URL: http://jira.codehaus.org/browse/MNG-1499 Project: Maven 2 Type: Bug Components: maven-project Reporter: David Jackman

[jira] Created: (MNG-1465) Maven not able to find setter for MavenProjectHelper property

Maven not able to find setter for MavenProjectHelper property - Key: MNG-1465 URL: http://jira.codehaus.org/browse/MNG-1465 Project: Maven 2 Type: Bug Reporter: David Jackman This might really be a

[jira] Created: (MNG-1464) Javadoc:jar goal executes for non-Java projects

Javadoc:jar goal executes for non-Java projects --- Key: MNG-1464 URL: http://jira.codehaus.org/browse/MNG-1464 Project: Maven 2 Type: Bug Components: maven-javadoc-plugin Reporter: David Jackman Attachments

[jira] Updated: (MNG-1404) Provide informative messages when POM is invalid

[ http://jira.codehaus.org/browse/MNG-1404?page=all ] David Jackman updated MNG-1404: --- Attachment: MNG-1404.patch The current version of maven-project does output the validation errors in debug mode (using the -X parameter). However, XML parsing

[jira] Created: (MNG-1347) Maven (plexus?) doesn't recognize Mojo parameter setters defined in a base class

ement Versions: 2.0 Reporter: David Jackman Priority: Minor Create a Mojo class that extends some base class that itself defines a parameter that uses a setter. Here's an example: public class Base extends AbstractMojo { /** * @parameter property="parameter"

[jira] Created: (MNGECLIPSE-3) Cancelling from the "Create New POM" dialog doesn't revert to the disabled state

-in for Eclipse Type: Bug Reporter: David Jackman Assigned to: Eugene Kuleshov Priority: Minor >From a new Eclipse project, choose Maven2 > Enable. The "Create New POM" >dialog appears. Click cancel. A pom.xml isn't created, but the project is Maven2 enabled an

[jira] Created: (MNGECLIPSE-2) Direct dependencies marked as optional aren't included in the project build path

lipse Type: Bug Reporter: David Jackman Assigned to: Eugene Kuleshov I added dependencies to my Eclipse project, which worked fine, and the project code compiled fine. However, I added true to one of the dependencies and the M2 plugin removed the dependency from the project build path, an

[jira] Created: (MEV-150) jMock 1.0.1 POM has instead of

jMock 1.0.1 POM has instead of - Key: MEV-150 URL: http://jira.codehaus.org/browse/MEV-150 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: David Jackman -- This message is

[jira] Created: (MEV-149) commons-codec 1.3 is missing build.resources.resource.directory

commons-codec 1.3 is missing build.resources.resource.directory --- Key: MEV-149 URL: http://jira.codehaus.org/browse/MEV-149 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: David

[jira] Created: (MNG-1194) When filtering, properties defined in should be allowed as well.

: maven-resources-plugin Reporter: David Jackman It would be nice to be able to reference custom properties defined in the section of pom.xml in resources for filtering. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators

[jira] Created: (MNG-1193) When filtering, ${java.version} gets replaced with pom.version instead.

-plugin Reporter: David Jackman When filtering, the resources plugin should be using the system property value, but is getting mixed up and using the value from the pom instead. I'm told the same confusion is happening with ${pom.organization.name} getting replaced with pom.name. --

[jira] Created: (MNG-1177) Project descriptor reference does not explain the syntax for the element.

: documentation Reporter: David Jackman The Project Descriptor reference page (maven-model/maven.html) should contain information about the properties element under project. Specifically, the format for setting properties, what I can use for values (string literals only, or can I use the values

[jira] Created: (MNG-1147) Adding resources section to POM without directory element causes NullPointerException

Components: maven-resources-plugin Versions: 2.0-beta-3 Reporter: David Jackman Priority: Minor Add a resources section to a POM without a directory element (in my case I did have a filtering element, but that doesn't seem to matter). Do a build (at least to the resources:reso

[jira] Created: (MNG-1096) Error handling needs improvement

Error handling needs improvement Key: MNG-1096 URL: http://jira.codehaus.org/browse/MNG-1096 Project: Maven 2 Type: Improvement Components: maven-site-plugin Versions: 2.0-beta-2 Reporter: David Jackman I'm act

[jira] Created: (MNG-922) Allow configuring the deployment of a timedstamped artifact when using SNAPSHOT in the version

Type: New Feature Versions: 2.0-beta-1 Reporter: David Jackman This is essentially the same issue as MPARTIFACT-59, but for the Maven 2 code base. When the current version contains SNAPSHOT, every deploy creates a SNAPSHOT artifact and an artifact with a date/time. This causes a LOT

[jira] Created: (MPSCM-64) Unable to change project.xml file that contains xsd information

Unable to change project.xml file that contains xsd information --- Key: MPSCM-64 URL: http://jira.codehaus.org/browse/MPSCM-64 Project: maven-scm-plugin Type: Bug Versions: 1.4 Reporter: David

[jira] Commented: (MPSCM-37) can't change read-only project.xml

[ http://jira.codehaus.org/browse/MPSCM-37?page=comments#action_45133 ] David Jackman commented on MPSCM-37: At the very least, the scm:prepare-release goal should fail in this case. Currently, the build succeeds but it didn't really work. This

[jira] Created: (MPSCM-63) If project.xml can't be edited (e.g. read only), prepare-release goal still succeeds

: Bug Versions: 1.4.1 Reporter: David Jackman If the scm plugin can't edit the project.xml file, the prepare-release goal shows that the error happened (by showing a stack trace), but doesn't fail. It should fail with nothing changed in the source control repository. --

[jira] Created: (MPCHANGELOG-63) Add the ability to show several sets of changes

Add the ability to show several sets of changes --- Key: MPCHANGELOG-63 URL: http://jira.codehaus.org/browse/MPCHANGELOG-63 Project: maven-changelog-plugin Type: New Feature Versions: 1.7.2 Reporter: David

[jira] Updated: (MPCHANGELOG-63) Add the ability to show several sets of changes

[ http://jira.codehaus.org/browse/MPCHANGELOG-63?page=all ] David Jackman updated MPCHANGELOG-63: - Attachment: MPCHANGELOG-63.patch I've attached a patch that changes the plugin in the way I described. This patch also contains the change

[jira] Commented: (MPCHANGELOG-63) Add the ability to show several sets of changes

[ http://jira.codehaus.org/browse/MPCHANGELOG-63?page=comments#action_39195 ] David Jackman commented on MPCHANGELOG-63: -- This request is similar to MPCHANGELOG-16, but a little different. This request gives a bit more flexibility, but does

[jira] Updated: (MPCHANGELOG-61) Add ability to log based on absolute date or tag

[ http://jira.codehaus.org/browse/MPCHANGELOG-61?page=all ] David Jackman updated MPCHANGELOG-61: - Attachment: MPCHANGELOG-61.patch Attached a patch file containing the changes for this enhancement. The absolute date should work for all SCM

[jira] Created: (MPCHANGELOG-61) Add ability to log based on absolute date or tag

Add ability to log based on absolute date or tag Key: MPCHANGELOG-61 URL: http://jira.codehaus.org/browse/MPCHANGELOG-61 Project: maven-changelog-plugin Type: New Feature Versions: 1.7.2 Reporter: David

RE: Maven 2.0 Technology Preview release

Some docs on the Maven site talk about version 1.1. Is an interim 1.1 release still planned, or is everything looking forward to 2.0? Is there a projected release date for 2.0 at this time? -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, April 08, 2005 10