[jira] Created: (MINVOKER-3) Invoker always returns 0 on Windows due to cmd.exe and exit /b in mvn.bat

Invoker always returns 0 on Windows due to cmd.exe and exit /b in mvn.bat - Key: MINVOKER-3 URL: http://jira.codehaus.org/browse/MINVOKER-3 Project: Maven 2.x Invoker Plugin

[jira] Commented: (NMAVEN-43) Deploy project artifacts

[ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95770 ] Evan Worley commented on NMAVEN-43: --- Shane, I haven't seen corruption but I am curious as to what could be going on. The o

[jira] Created: (MRRESOURCES-23) Introduce a parameter to define the scopes of the libraries to be included in the NOTICE licensing.

Introduce a parameter to define the scopes of the libraries to be included in the NOTICE licensing. --- Key: MRRESOURCES-23 URL: http://jira.codehaus.org/browse/MRRESO

[jira] Closed: (MJAVADOC-94) The javadoc option "-sourcetab" should be passed as "-linksourcetab"

[ http://jira.codehaus.org/browse/MJAVADOC-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-94. --- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.3 fixed > The javado

[jira] Closed: (MJAVADOC-95) Confusing and configuration options

[ http://jira.codehaus.org/browse/MJAVADOC-95?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-95. --- Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.3 It is only a Sepera

[jira] Created: (SCM-313) Check out command fails to report an error

Check out command fails to report an error -- Key: SCM-313 URL: http://jira.codehaus.org/browse/SCM-313 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-bazaar Affects Ve

[jira] Commented: (MSITE-194) xdoc's gets rendered in the HTML body, not in head

[ http://jira.codehaus.org/browse/MSITE-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95776 ] lacton commented on MSITE-194: -- The issue is in version 2.0.6 too. > xdoc's gets rendered in the HTML body, not in head > --

[jira] Created: (SCM-314) BazaarScmProviderRepository doesn't work with file URL on Windows

BazaarScmProviderRepository doesn't work with file URL on Windows - Key: SCM-314 URL: http://jira.codehaus.org/browse/SCM-314 Project: Maven SCM Issue Type: Bug Compon

[jira] Created: (MSITE-230) Spurious in generated section

Spurious in generated section --- Key: MSITE-230 URL: http://jira.codehaus.org/browse/MSITE-230 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.

[jira] Commented: (MJAVADOC-106) Dependencies with scope "runtime" or "provided" are not used in the javadoc classpath

[ http://jira.codehaus.org/browse/MJAVADOC-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95777 ] Vincent Siveton commented on MJAVADOC-106: -- Christophe, Could you provide us a test case for this? I need to inves

[jira] Commented: (NMAVEN-43) Deploy project artifacts

[ http://jira.codehaus.org/browse/NMAVEN-43?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95780 ] Shane Isbell commented on NMAVEN-43: Okay, I found the problem. During a deploy the assembly, say NMaven.Logging-0.14-200

[jira] Created: (NMAVEN-52) As Part of Life-Cycle NMaven Should Verify That All Assemblies in Local Repo Are Valid

As Part of Life-Cycle NMaven Should Verify That All Assemblies in Local Repo Are Valid -- Key: NMAVEN-52 URL: http://jira.codehaus.org/browse/NMAVEN-52 Project: NMave

[jira] Issue Comment Edited: (MNG-2872) Don't append artifactId when parent pom already has artifactId in URL

[ http://jira.codehaus.org/browse/MNG-2872?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95276 ] M. Rohrmoser edited comment on MNG-2872 at 5/13/07 1:12 PM: I ran into this one, too. despite http:

[jira] Updated: (MINSTALL-18) Bad algorithm to decide if the main artifact is to be installed or not

[ http://jira.codehaus.org/browse/MINSTALL-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MINSTALL-18: --- Fix Version/s: (was: 2.2) 2.3 > Bad algorithm to decide if the main artifac

[jira] Updated: (MINSTALL-37) Add support to force install:install to use a specific version

[ http://jira.codehaus.org/browse/MINSTALL-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MINSTALL-37: --- Fix Version/s: (was: 2.2) 2.3 > Add support to force install:install to use

[jira] Updated: (MINSTALL-30) Command Line parameter 'version' does not override pom file

[ http://jira.codehaus.org/browse/MINSTALL-30?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Carlos Sanchez updated MINSTALL-30: --- Fix Version/s: (was: 2.2) 2.3 > Command Line parameter 'version' does not o

[jira] Closed: (MINSTALL-37) Add support to force install:install to use a specific version

[ http://jira.codehaus.org/browse/MINSTALL-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox closed MINSTALL-37. - Resolution: Won't Fix The general consensus seems to be that this should not be added. > Add support to force

[jira] Commented: (MRM-329) The Reports link gives an HTTP 500

[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95787 ] Arnaud Heritier commented on MRM-329: - There's no common interface for reports data :-( We can do something like that :

[jira] Created: (MRM-338) Fix dependencies convergence between archiva projects

Fix dependencies convergence between archiva projects - Key: MRM-338 URL: http://jira.codehaus.org/browse/MRM-338 Project: Archiva Issue Type: Task Affects Versions: 1.0-alpha-1

[jira] Created: (NMAVEN-53) Creating New .NET Maven Plugins Should Not Require Adding an Entry within NMaven's net-dependencies.xml File

Creating New .NET Maven Plugins Should Not Require Adding an Entry within NMaven's net-dependencies.xml File Key: NMAVEN-53 URL: http://jira.codehaus.org/

[jira] Created: (NMAVEN-54) Support for Attaching Platform Metadata to Assemblies

Support for Attaching Platform Metadata to Assemblies - Key: NMAVEN-54 URL: http://jira.codehaus.org/browse/NMAVEN-54 Project: NMaven Issue Type: New Feature Reporter: Shane Isb

[jira] Created: (MRM-339) Roles aren't created if the repository isn't created within the web UI

Roles aren't created if the repository isn't created within the web UI -- Key: MRM-339 URL: http://jira.codehaus.org/browse/MRM-339 Project: Archiva Issue Type: Bug Affe

[jira] Closed: (MRM-338) Fix dependencies convergence between archiva projects

[ http://jira.codehaus.org/browse/MRM-338?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Arnaud Heritier closed MRM-338. --- Assignee: Arnaud Heritier Resolution: Fixed Fix Version/s: 1.0-alpha-1 All versions of depende

[jira] Commented: (MRM-329) The Reports link gives an HTTP 500

[ http://jira.codehaus.org/browse/MRM-329?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95794 ] Arnaud Heritier commented on MRM-329: - The other type used here seems to be : ArchivaArtifact > The Reports link gives an HT

[jira] Updated: (MRM-212) configure checksum policy for proxied repository

[ http://jira.codehaus.org/browse/MRM-212?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-212: Fix Version/s: 0.9 > configure checksum policy for proxied repository >

[jira] Created: (MRM-340) release:prepare fails due to missing archiva-webapp

release:prepare fails due to missing archiva-webapp --- Key: MRM-340 URL: http://jira.codehaus.org/browse/MRM-340 Project: Archiva Issue Type: Bug Components: build Affects Versio

[jira] Updated: (MRM-340) release:prepare fails due to missing archiva-applet

[ http://jira.codehaus.org/browse/MRM-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Wendy Smoak updated MRM-340: Summary: release:prepare fails due to missing archiva-applet (was: release:prepare fails due to missing archiva-web

[jira] Commented: (MRM-340) release:prepare fails due to missing archiva-applet

[ http://jira.codehaus.org/browse/MRM-340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95796 ] Arnaud Heritier commented on MRM-340: - We could add a dependency for the plugin like :

[jira] Commented: (MRM-339) Roles aren't created if the repository isn't created within the web UI

[ http://jira.codehaus.org/browse/MRM-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95797 ] Arnaud Heritier commented on MRM-339: - Same thing if I delete the database. All my repositories are created but I have no ro

[jira] Commented: (MRM-339) Roles aren't created if the repository isn't created within the web UI

[ http://jira.codehaus.org/browse/MRM-339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95798 ] Arnaud Heritier commented on MRM-339: - It can be related to this problem. I add the "Global Observer" role to guest but I ca

[jira] Commented: (MAVENUPLOAD-1532) Upload org.hibernate:hibernate-annotations:jar:3.3.0.ga to ibiblio

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1532?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95799 ] Nathan Hamblen commented on MAVENUPLOAD-1532: - This also requires hibernate-commons-annotations.jar, which h

[jira] Commented: (WAGON-82) wagon-webdav does not set http-proxy correctly

[ http://jira.codehaus.org/browse/WAGON-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95802 ] Joakim Erdfelt commented on WAGON-82: - I've considered making the protocol on wagon-webdav 'dav' (normal http) and 'davs' (

[jira] Commented: (MNG-2985) DefaultWagonManager does not safely remove TransferListeners from the wagon

[ http://jira.codehaus.org/browse/MNG-2985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95804 ] Carlos Sanchez commented on MNG-2985: - you are missing Wagonnoop class in the patch > DefaultWagonManager does not safely r

[jira] Created: (NMAVEN-55) FxCop Maven Plugin

FxCop Maven Plugin -- Key: NMAVEN-55 URL: http://jira.codehaus.org/browse/NMAVEN-55 Project: NMaven Issue Type: New Feature Reporter: Shane Isbell Priority: Minor Maven plugin for FxCop (code analysi

[jira] Commented: (NMAVEN-3) Deploy NMaven Snapshot into Repo

[ http://jira.codehaus.org/browse/NMAVEN-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95806 ] Shane Isbell commented on NMAVEN-3: --- We've finally have support for snapshots, as well as a deploy plugin for NMaven; the cap

[jira] Created: (CONTINUUM-1270) Release artifacts are missing license and notice files

Release artifacts are missing license and notice files -- Key: CONTINUUM-1270 URL: http://jira.codehaus.org/browse/CONTINUUM-1270 Project: Continuum Issue Type: Task Affects Versions: 1

[jira] Commented: (MJAR-72) Option to include source within the jar artifact

[ http://jira.codehaus.org/browse/MJAR-72?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_95807 ] Joerg Schaible commented on MJAR-72: You can simply declare the sources as resources. > Option to include source within the