Re: suggestion/enhancement request : how to deprecate an artifact

I agree my repo should be managed a better way, but I sometimes have holidays and they're is no rule to define the groupId - artifactId. Let's take a look at ibiblio, that should be a reference. What do you thing about xml-apis/xmlParserAPIs-2.0.0.jar

cvs commit: maven-components/maven-mboot2/src/main/java MBoot.java

brett 2005/03/17 12:20:49 Modified:maven-mboot2/src/main/java MBoot.java Log: Fix NPE in later code when mavenRepoLocal was defined Revision ChangesPath 1.70 +1 -3 maven-components/maven-mboot2/src/main/java/MBoot.java Index: MBoot.java

Re: suggestion/enhancement request : how to deprecate an artifact location

>3) Moreover, you can define more than one repository with the property >maven.repo.remote. For instance, a dev repository and a production one. > > This is probably the best way to handle it. Split your repository into a "current" and "archive". Don't promote builds that require the archive (un

Re: Multiproject and branched projects

It's not a limitation, it's a feature :) Really, the reactor should fail on duplicates and have an option to allow them to both be built. But it will also require making sure the project sorting works correctly. - Brett Eric Pugh wrote: >Hi all, > >I have my project checked out as two branches

svn commit: r157954 - maven/maven-1/plugins/trunk/cruisecontrol/project.xml

Author: epugh Date: Thu Mar 17 10:08:58 2005 New Revision: 157954 URL: http://svn.apache.org/viewcvs?view=rev&rev=157954 Log: Expand on what the plugin does Modified: maven/maven-1/plugins/trunk/cruisecontrol/project.xml Modified: maven/maven-1/plugins/trunk/cruisecontrol/project.xml URL: h

[jira] Created: (MPJAVA-34) Capture Deprecation Warnings

Capture Deprecation Warnings Key: MPJAVA-34 URL: http://jira.codehaus.org/browse/MPJAVA-34 Project: maven-java-plugin Type: Improvement Versions: 1.5 Environment: This improvement is environment-agnostic Reporter: Ron Gallagh

[jira] Created: (MPECLIPSE-83) Incorrect maven.eclipse.classpath.include handling

Incorrect maven.eclipse.classpath.include handling -- Key: MPECLIPSE-83 URL: http://jira.codehaus.org/browse/MPECLIPSE-83 Project: maven-eclipse-plugin Type: Bug Versions: 1.9 Reporter: Thomas Van de Velde

RE: suggestion/enhancement request : how to deprecate an artifact location

Hi Nicolas, > I've got some difficulties managing our internal repository : as > mutliple users can update it, some artifacts are deployed on multiple > locations with != groupId. for example, java activation framework was > deployed as jaf/jar.jar, sun/activation.jar, and is also on ibiblio as >

[jira] Created: (MAVENUPLOAD-327) Upload request from Spring Web Flow 0.9.0

Upload request from Spring Web Flow 0.9.0 - Key: MAVENUPLOAD-327 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-327 Project: maven-upload-requests Type: Task Reporter: Erwin Vervaet http://users.telenet.be/ervacon/ervac

Multiproject and branched projects

Hi all, I have my project checked out as two branches. I have myproject and myproject-M4. In both, the artifactId is "myproject", however the version tags distingush between the two. However, when I attempt to run multiproject over them, it doesn't pick up the second "myproject-M4", I assume

suggestion/enhancement request : how to deprecate an artifact location

Hi guys, I've got some difficulties managing our internal repository : as mutliple users can update it, some artifacts are deployed on multiple locations with != groupId. for example, java activation framework was deployed as jaf/jar.jar, sun/activation.jar, and is also on ibiblio as activation

[jira] Created: (MPCRUISECONTROL-21) Need to be able to support two branches of the same artifact

Need to be able to support two branches of the same artifact - Key: MPCRUISECONTROL-21 URL: http://jira.codehaus.org/browse/MPCRUISECONTROL-21 Project: maven-cruisecontrol-plugin Type: New Feature Versi

[jira] Commented: (MPCRUISECONTROL-20) Local properties

[ http://jira.codehaus.org/browse/MPCRUISECONTROL-20?page=comments#action_31035 ] David Eric Pugh commented on MPCRUISECONTROL-20: This enhancement is dependent on 1.5 of SCM being released, and until it does, I am reluctant to keep pus

[jira] Commented: (MPCRUISECONTROL-18) Maven properties to control plugin

[ http://jira.codehaus.org/browse/MPCRUISECONTROL-18?page=comments#action_31034 ] David Eric Pugh commented on MPCRUISECONTROL-18: I get the port parameter, and I could buy adding the -configfile parameter. But why do you need to pass

suggestion/enhancement request : how to deprecate an artifact location

Hi guys, I've got some difficulties managing our internal repository : as mutliple users can update it, some artifacts are deployed on multiple locations with != groupId. for example, java activation framework was deployed as jaf/jar.jar, sun/activation.jar, and is also on ibiblio as activation