[jira] Commented: (SCM-13) Investigate pure Java SVN interface

[ http://jira.codehaus.org/browse/SCM-13?page=comments#action_54475 ] David Hawkins commented on SCM-13: -- I forgot to mention authentication. In order to get authentication information into the JavaSVN library, I added the ability for the svn provider to

[jira] Updated: (SCM-13) Investigate pure Java SVN interface

[ http://jira.codehaus.org/browse/SCM-13?page=all ] David Hawkins updated SCM-13: - Attachment: tmate.org.javasvn.tar.gz ch.ethz.ganymed.tar.gz SCM-13-maven-scm-api.patch > Investigate pure Java SVN interf

[jira] Updated: (SCM-13) Investigate pure Java SVN interface

[ http://jira.codehaus.org/browse/SCM-13?page=all ] David Hawkins updated SCM-13: - Attachment: SCM-13-maven-scm-manager-plexus.patch SCM-13-maven-scm-plugin.patch SCM-13-maven-scm-provider-svn.tar.gz > Investigate pure J

Re: maven-model-plugin

cheme. Any suggestions? --David - Original Message - From: "Trygve Laugstøl" <[EMAIL PROTECTED]> To: "Maven Developers List" Sent: Friday, December 16, 2005 3:29 PM Subject: Re: maven-model-plugin On Fri, 2005-12-16 at 06:56 -0600, David Hawkins wrote: I

maven-model-plugin

I created a plugin for dependency management and pom editing via the command line. My initial goal was to create a plugin which would show me a list of my dependencies and determine if any of them needed to be updated to a later version. I really couldn't find an easy way to do this for a project

[jira] Updated: (MNG-1849) maven-model Extension.hashCode() throws NPE if groupId or artifactId is null

[ http://jira.codehaus.org/browse/MNG-1849?page=all ] David Hawkins updated MNG-1849: --- Attachment: MNG-1849-maven-model.patch > maven-model Extension.hashCode() throws NPE if groupId or artifactId is n

[jira] Created: (MNG-1849) maven-model Extension.hashCode() throws NPE if groupId or artifactId is null

Reporter: David Hawkins org.apache.maven.model.Extension.hashCode() throws NullPointerException if the groupId or artifactId is null. There was null checking on version, but not on groupId or artifactId so this patch adds it. -- This message is automatically generated by JIRA. - If you

[jira] Updated: (MNG-1797) Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

[ http://jira.codehaus.org/browse/MNG-1797?page=all ] David Hawkins updated MNG-1797: --- Attachment: MNG-1797-maven-project.patch > Dependency excludes apply to every subsequent dependency, not just the one it > is declared

[jira] Created: (MNG-1797) Dependency excludes apply to every subsequent dependency, not just the one it is declared under.

Type: Bug Versions: 2.0.1 Reporter: David Hawkins If you specify ANY dependency excludes, all dependencies after that one in the pom will also exclude what you specified. They appear to be cumulative on every dependency in that they bleed over into sibling dependencies

[jira] Commented: (MNG-1696) war includes and excludes don't handle comma separated tokens (patch included)

[ http://jira.codehaus.org/browse/MNG-1696?page=comments#action_52464 ] David Hawkins commented on MNG-1696: Well I am not quite sure what else to say here. I am working with 2.0-beta-3-SNAPSHOT from http://svn.apache.org/repos/asf/maven/plugins/trunk

[jira] Commented: (MNG-1696) war includes and excludes don't handle comma separated tokens (patch included)

[ http://jira.codehaus.org/browse/MNG-1696?page=comments#action_52458 ] David Hawkins commented on MNG-1696: It was developed against repository version 349429. I just reverted my src directory, updated to the latest (350051) and patched my source with

[jira] Created: (CONTINUUM-488) Continuum will not use mirrors or alternate repositories

Reporter: David Hawkins I can't get Continuum to use a repository other than repo1.maven.org. Running mvn manually for my user works fine and fetches the dependencies from the mirror specified in settings.xml. However, when I start continuum and it attempts the build, it always tri

[jira] Updated: (MNG-1696) war includes and excludes don't handle comma separated tokens (patch included)

[ http://jira.codehaus.org/browse/MNG-1696?page=all ] David Hawkins updated MNG-1696: --- Attachment: MNG-1696-maven-war-plugin.patch > war includes and excludes don't handle comma separated tokens (patch

[jira] Created: (MNG-1696) war includes and excludes don't handle comma separated tokens (patch included)

maven-war-plugin Reporter: David Hawkins The documentation for warSourceIncludes, warSourceExcludes, dependantWarIncludes, and dependantWarExcludes all state something that they support comma delimited tokens but it simply doesn't work when a comma is specified. This patch make

[jira] Updated: (MNG-1632) mvn.bat does not properly return the exit code of the java process

[ http://jira.codehaus.org/browse/MNG-1632?page=all ] David Hawkins updated MNG-1632: --- Attachment: MNG-1632-maven-core-2.patch Sorry for taking so long to respond on this. I have created a new patch, "MNG-1632-maven-core-2.patch", which h

[jira] Updated: (MNG-1632) mvn.bat does not properly return the exit code of the java process

[ http://jira.codehaus.org/browse/MNG-1632?page=all ] David Hawkins updated MNG-1632: --- Attachment: MNG-1632-maven-core.patch > mvn.bat does not properly return the exit code of the java proc

[jira] Created: (MNG-1632) mvn.bat does not properly return the exit code of the java process

-core Reporter: David Hawkins This manifests itself when running release:perform and an error occurs in the child process. The stdout shows a build error for the child process, but a shows build success for the outer process. This is pretty confusing if you only happen to look at the last

[jira] Updated: (MNG-887) default tag to ${artifactId}-${version}

[ http://jira.codehaus.org/browse/MNG-887?page=all ] David Hawkins updated MNG-887: -- Attachment: MNG-887-maven-scm-provider-svn.patch MNG-887-maven-release-plugin.patch Changes to maven-release-plugin The user is now prompted with a default

[jira] Updated: (MNG-1556) Update to work with automatic tagBase resolution of maven-scm-provider-svn

[ http://jira.codehaus.org/browse/MNG-1556?page=all ] David Hawkins updated MNG-1556: --- Attachment: MNG-1556-maven-release-plugin.patch This patch makes the maven-release-plugin no longer specify the tagBase by default. It will now play nicely with the

[jira] Created: (MNG-1556) Update to work with automatic tagBase resolution of maven-scm-provider-svn

-plugin Versions: 2.0.1 Reporter: David Hawkins I'll take this one -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA

[jira] Updated: (MNG-1507) Merge contents of dependent wars into war being built

[ http://jira.codehaus.org/browse/MNG-1507?page=all ] David Hawkins updated MNG-1507: --- Attachment: MNG-1507-maven-war-plugin.patch > Merge contents of dependent wars into war being bu

[jira] Created: (MNG-1507) Merge contents of dependent wars into war being built

Reporter: David Hawkins We added functionality to the maven-war-plugin to copy the contents of dependent wars into the war being built. It will never overwrite existing files and has configurable includes and excludes which are applied to the files being copied. Also made a minor change in

[jira] Updated: (SCM-68) Subversion provider doesn't handle tag updates correctly

[ http://jira.codehaus.org/browse/SCM-68?page=all ] David Hawkins updated SCM-68: - Attachment: update-switch-revised.patch I found another issue regarding tags and "" empty/whitespace tags and corrected it. By doing this I did slightly