[jira] Commented: (MPPMD-6) Enhancement request: report by problem type

file to order entries by problems and not by files, and a JSL file to create the xdoc. > Enhancement request: report by problem type > --- > > Key: MPPMD-6 > URL: http://jira.codehaus.org/browse/MPPMD-6 > Pr

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

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: 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 >

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

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] Closed: (MPCHECKSTYLE-13) Enhancement request: report by problem type

=MPCHECKSTYLE-13 Here is an overview of the issue: - Key: MPCHECKSTYLE-13 Summary: Enhancement request: report by problem type Type: New Feature Status: Closed Priority: Minor Resolution: WON'T FIX Ori

[jira] Created: (MPPMD-6) Enhancement request: report by problem type

: - Key: MPPMD-6 Summary: Enhancement request: report by problem type Type: New Feature Status: Open Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-pmd-plugin Assignee: Jason van Zyl Reporter: Daniel

[jira] Created: (MPCHECKSTYLE-13) Enhancement request: report by problem type

: - Key: MPCHECKSTYLE-13 Summary: Enhancement request: report by problem type Type: New Feature Status: Unassigned Priority: Minor Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: maven-checkstyle-plugin Assignee

enhancement request

Hi all, I'm using maven with eclipse IDE. An interesting fonctionality of Eclipse (and much IDE may do same) is the ability to attach java sources to a jar. Using maven dependencies and maven eclipse plugin to generate classpath does not set this property. Is they're some plan to add a new entr