[Plexus-Utils] MatchPattern(s) Improvement?

Greetings, I am using modified MatchPattern, MatchPatterns and SelectorUtils in the new Apache Rat 0.17. I had to modify them because I needed visibility to the matching patterns, and because package private made some extensions impossible. The MatchPatter and MatchPatterns classes are final so

Re: Improvement in a maven-reporting-api design

Am 2022-08-07 um 23:56 schrieb Slawomir Jaranowski: Hi, Currently Maven report plugin implements MavenReport by extending AbstractMavenReport Interface MavenReport is in maven-reporting-api Class AbstractMavenReport is in maven-reporting-impl maven-reporting-impl - has many transitive dependen

Improvement in a maven-reporting-api design

Hi, Currently Maven report plugin implements MavenReport by extending AbstractMavenReport Interface MavenReport is in maven-reporting-api Class AbstractMavenReport is in maven-reporting-impl maven-reporting-impl - has many transitive dependencies. We have also AbstractMavenReportRenderer which

Re: Releasing a Parent POM procedure - improvement

Hi, Automatically building release notes is very encouraging ... but we need some place to collect other issues than dependency updates. So when we also have issues in jira, we need a label for versions in jira to mark releases which contain resolved issues. I have not a good and easy idea how t

Re: Releasing a Parent POM procedure - improvement

On Tue, 31 May 2022 at 18:22, Slawomir Jaranowski wrote: > wt., 31 maj 2022 o 09:58 Olivier Lamy napisał(a): > > > On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski < > s.jaranow...@gmail.com> > > wrote: > > > > > Hi, > > > > > > On page Releasing A Parent POM [1] we have Call the vote template

Re: Releasing a Parent POM procedure - improvement

wt., 31 maj 2022 o 09:58 Olivier Lamy napisał(a): > On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski > wrote: > > > Hi, > > > > On page Releasing A Parent POM [1] we have Call the vote template with > > info: > > > > "In the vote, instead of providing links to JIRA, the parent POMs should > > i

Re: Releasing a Parent POM procedure - improvement

On Tue, 31 May 2022 at 02:22, Slawomir Jaranowski wrote: > Hi, > > On page Releasing A Parent POM [1] we have Call the vote template with > info: > > "In the vote, instead of providing links to JIRA, the parent POMs should > include a link to the Git changes since the last release:" > > It can be

Releasing a Parent POM procedure - improvement

Hi, On page Releasing A Parent POM [1] we have Call the vote template with info: "In the vote, instead of providing links to JIRA, the parent POMs should include a link to the Git changes since the last release:" It can be understood by someone that we don't need to create release notes in jira

[GitHub] [maven-site] cpsauer commented on pull request #249: Minor improvement to English fluency

cpsauer commented on pull request #249: URL: https://github.com/apache/maven-site/pull/249#issuecomment-887863726 Wow. That was fast. Awesome. Thanks! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to g

[GitHub] [maven-site] michael-o merged pull request #249: Minor improvement to English fluency

michael-o merged pull request #249: URL: https://github.com/apache/maven-site/pull/249 -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: dev-unsubsc

[GitHub] [maven-site] cpsauer opened a new pull request #249: Minor improvement to English fluency

cpsauer opened a new pull request #249: URL: https://github.com/apache/maven-site/pull/249 Fixed some unusual phrasing I saw while reading the docs. Goal is to leave things even better than I found them. -- This is an automated message from the Apache Git Service. To respond to the me

Proposition of improvement in maven-script-interpreter

Hi, I've created issues with some of proposition: https://issues.apache.org/jira/browse/MSHARED-910 https://issues.apache.org/jira/browse/MSHARED-911 https://issues.apache.org/jira/browse/MSHARED-914 I can do this change after your approval, and after release new version of maven-script-interpre

Re: support --resume-from improvement

o so, but that implies this > flag is broken. > This improvement will pick up either the jar or target/classes (always the > most recent of the 2) from the previous build. > > thanks, > Robert > > > https://issues.apache.org/jira/browse/MNG-4660 >

support --resume-from improvement

stall". However, with Maven 3 it is advices not to do so, but that implies this flag is broken. This improvement will pick up either the jar or target/classes (always the most recent of the 2) from the previous build. thanks, Robert  https://issues.apache.org/jira/browse/MNG-4660

Re: [maven-enforcer] 05/05: Code improvement.

> > > > +private boolean isVersion( String version ) > > +{ > > +return StringUtils.isNotEmpty( version ) && > > !StringUtils.isWhitespace( version ); > > +} > Maybe use StringUtils.isNotBlank() instead? - Eric L

Re: [maven-enforcer] 05/05: Code improvement.

Hi Robert, On 09/11/18 10:05, Robert Scholte wrote: Please rename to isValidVersion +    private boolean isVersion( String version ) Really good idea...Thanks for this ... Kind regards Karl Heinz Marbaise +    { +    return StringUtils.isNotEmpty( version ) && !StringUtils.isWhitesp

Re: [maven-enforcer] 05/05: Code improvement.

Heinz Marbaise AuthorDate: Sun Oct 7 17:33:56 2018 +0200 Code improvement. --- .../maven/plugins/enforcer/RequirePluginVersions.java | 19 ++- 1 file changed, 14 insertions(+), 5 deletions(-) diff --git a/enforcer-rules/src/main/java/org/apache/maven/plugins/enforcer

Maven Enforcer Plugin: Improvement dependency resolve during validate phase

Hi, I'm working on a multiple modules project, and encountering an issue like this one https://issues.apache.org/jira/browse/MENFORCER-168 . I dig into the implementation of the enforcer plugin, and found that EnforceMojo is bound to the def

Re: Improvement in wagon-http (use http connection pooling from ASF httpclient)

On 24/08/2011, at 6:26 PM, Olivier Lamy wrote: > Hello Folks, > I have just loaded an issue [1] regarding an improvement for wagon > http (the wagon http which use asf httpclient). > This small improvement will simply add a connection pooling mechanism > to avoid http(s) connectio

Re: Improvement in wagon-http (use http connection pooling from ASF httpclient)

nd not use a per-instance > configuration ? > > 2011/8/24 Olivier Lamy > >> Hello Folks, >> I have just loaded an issue [1] regarding an improvement for wagon >> http (the wagon http which use asf httpclient). >> This small improvement will simply add a connection

Re: Improvement in wagon-http (use http connection pooling from ASF httpclient)

+1 to set this as default why use system properties to set this flag and not use a per-instance configuration ? 2011/8/24 Olivier Lamy > Hello Folks, > I have just loaded an issue [1] regarding an improvement for wagon > http (the wagon http which use asf httpclient). > This small

Improvement in wagon-http (use http connection pooling from ASF httpclient)

Hello Folks, I have just loaded an issue [1] regarding an improvement for wagon http (the wagon http which use asf httpclient). This small improvement will simply add a connection pooling mechanism to avoid http(s) connection for artifacts requests. My first idea was to not enable it by default

Re: Repository Security Improvement

Okay, it doesn't look like this is much interest in this. I'll post a broad overview of my thoughts and see if that kicks off any other discussion and, if not, I'll just let it drop. So, currently the repository security is a bit of misnomer. Everything to date is implemented in the transport la

Re: Repository Security Improvement

I'd be interested in talking about it again, if you have time/new thoughts to share. On 4/2/11 8:34 AM, Chad La Joie wrote: Quite some time ago I was asking[1] about PGP support in Maven. And in February Brett noted[2][3] some initial thinking he had done around increasing certain security asp

Repository Security Improvement

Quite some time ago I was asking[1] about PGP support in Maven. And in February Brett noted[2][3] some initial thinking he had done around increasing certain security aspects of Maven repositories. I've come back to this topic again and have been doing some thinking on it. Is this still a topic p

Re: Re: 5 minute guide - Incorrect documentation/documentation improvement?

On Mon, May 18, 2009 at 5:17 PM, wrote: > Hi all, > > > >> Whats the JIRA ticket number? > > Ah sorry it's MNG-4164. I haven't created the patch yet (trying to keep the > wording small/simple as). > > Cheers, > Martijn > Thanks, I wanted the issue so I could watch it and maybe commit it when it

Re: Re: 5 minute guide - Incorrect documentation/documentation improvement?

Hi all, Whats the JIRA ticket number? Ah sorry it's MNG-4164. I haven't created the patch yet (trying to keep the wording small/simple as). Cheers, Martijn

Re: 5 minute guide - Incorrect documentation/documentation improvement?

On Mon, May 18, 2009 at 2:49 AM, Martijn Verburg wrote: > Hi Benjamin, > >>> http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html >>> [...] >>> 1.)  I was unable to find in SVN where this file lives, any pointers? >> >> http://svn.apache.org/repos/asf/maven/site/trunk/src/site

Re: 5 minute guide - Incorrect documentation/documentation improvement?

Hi Benjamin, >> http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html >> [...] >> 1.)  I was unable to find in SVN where this file lives, any pointers? > > http://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/guides/getting-started/maven-in-five-minutes.apt Ah thanks,

Re: 5 minute guide - Incorrect documentation/documentation improvement?

Martijn Verburg wrote: http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html [...] 1.) I was unable to find in SVN where this file lives, any pointers? http://svn.apache.org/repos/asf/maven/site/trunk/src/site/apt/guides/getting-started/maven-in-five-minutes.apt 2.) I w

Re: 5 minute guide - Incorrect documentation/documentation improvement?

Hi all, Hopefully this isn't too much of a stupid question :). I'm attempting to make a documentation patch for the document located at: http://maven.apache.org/guides/getting-started/maven-in-five-minutes.html I've created the JIRA etc, but I have a couple of questions: 1.) I was unable to f

Re: Shade improvement: filtering

David Blevins wrote: Mauro, is it possible you can publish a new snapshot or update the perms on the metadata files? Done both. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTE

Re: Shade improvement: filtering

Mauro, is it possible you can publish a new snapshot or update the perms on the metadata files? -David On Jan 15, 2008, at 9:02 PM, David Blevins wrote: On Jan 15, 2008, at 6:47 PM, David Blevins wrote: Thanks for reviewing! On Jan 15, 2008, at 6:09 PM, Daniel Kulp wrote: David, I'm O

Re: Shade improvement: filtering

On Jan 15, 2008, at 6:47 PM, David Blevins wrote: Thanks for reviewing! On Jan 15, 2008, at 6:09 PM, Daniel Kulp wrote: David, I'm OK with you committing this except for a few minor nits: 1) Javadoc for the parameter you added. The description about the includes/excludes needs to be adde

Re: Shade improvement: filtering

Thanks for reviewing! On Jan 15, 2008, at 6:09 PM, Daniel Kulp wrote: David, I'm OK with you committing this except for a few minor nits: 1) Javadoc for the parameter you added. The description about the includes/excludes needs to be added to the javadoc for the parameter so the generat

Re: Shade improvement: filtering

David, I'm OK with you committing this except for a few minor nits: 1) Javadoc for the parameter you added. The description about the includes/excludes needs to be added to the javadoc for the parameter so the generated site has that information. 2) Code formatting isn't quite right for mav

Shade improvement: filtering

I need the ability to include/exclude classes from certain artifacts when creating the shaded jar. In OpenEJB we have a situation where one of the jars we are adding to the shaded jar contains a class also part of another jar added to the shade. The class in question truly belongs to one

Re: Improvement

Olivier already fixed it with the end time but I think it would be good to add the build def description too so users will know which build def was the latest to run Emmanuel Christophe Lechenne a écrit : Hi all, For CONTINUUM-703, I can put startTime or EndTime, I think endTime is better. w

Re: Improvement

Hi all, For CONTINUUM-703, I can put startTime or EndTime, I think endTime is better. wdyt ? 2007/10/15, olivier lamy <[EMAIL PROTECTED]>: > > Hi, > I think there are some related/similar issues to this (CONTINUUM-703, > CONTINUUM-1332). > And fixing this is not really complicated. > > Others :

RE: A simple improvement of the jar plugin

2007 4:59 PM To: dev@maven.apache.org Subject: A simple improvement of the jar plugin Hello, I would like to suggest a simple improvement of the jar plugin: a new property, specifying the artifact extension (it is now a hardcoded ".jar"). There are some cases where it would be usefu

A simple improvement of the jar plugin

Hello, I would like to suggest a simple improvement of the jar plugin: a new property, specifying the artifact extension (it is now a hardcoded ".jar"). There are some cases where it would be useful to change it --- for example when creating a jboss microcontainer archive, which

[maven-javadoc-plugin] small suggestion/code improvement (diff included)

Hello, I've just been trying to get my head around the interaction the JavaDoc plugin when set to "aggregate" and multi-module builds... This would have saved me tons of time(svn diff on trunk version of file): Index: org/apache/maven/plugin/javadoc/AbstractJavadocMojo.java

[jira] Updated: (MSUREFIRE-57) Forking documentation improvement to help with class loader constrainst issues

[ http://jira.codehaus.org/browse/MSUREFIRE-57?page=all ] Ben Gidley updated MSUREFIRE-57: Attachment: maven-surefire-plugin-374325.patch > Forking documentation improvement to help with class loader constrainst iss

[jira] Created: (MSUREFIRE-57) Forking documentation improvement to help with class loader constrainst issues

Forking documentation improvement to help with class loader constrainst issues -- Key: MSUREFIRE-57 URL: http://jira.codehaus.org/browse/MSUREFIRE-57 Project: Maven 2.x Surefire Plugin Type

[jira] Created: (MNGECLIPSE-60) Improvement to ExecutePom Launch shortcut

Improvement to ExecutePom Launch shortcut - Key: MNGECLIPSE-60 URL: http://jira.codehaus.org/browse/MNGECLIPSE-60 Project: Maven 2.x Extension for Eclipse Type: Improvement Reporter: Dmitri Maximovich Assigned to: Dmitri

[jira] Updated: (MNG-474) performance improvement for forked lifecycles

[ http://jira.codehaus.org/browse/MNG-474?page=all ] Brett Porter updated MNG-474: - Component: Plugins and Lifecycle Design & Best Practices > performance improvement for forked lif

[jira] Updated: (MNG-474) performance improvement for forked lifecycles

[ http://jira.codehaus.org/browse/MNG-474?page=all ] Jason van Zyl updated MNG-474: -- Component: (was: Plugins and Lifecycle) Performance > performance improvement for forked lifecyc

[jira] Moved: (MSITE-52) Error handling needs improvement

[ http://jira.codehaus.org/browse/MSITE-52?page=all ] Jason van Zyl moved MNG-1096 to MSITE-52: - Version: (was: 2.0-beta-2) Fix Version: (was: 2.0 (RC)) type: Bug (was: Improvement) Component: (was: maven

[jira] Closed: (MNG-1079) error reporting for a plugin not found needs improvement

[ http://jira.codehaus.org/browse/MNG-1079?page=all ] Brett Porter closed MNG-1079: - Resolution: Fixed > error reporting for a plugin not found needs improvement > > > K

[jira] Updated: (MNG-1079) error reporting for a plugin not found needs improvement

not found needs improvement > > > Key: MNG-1079 > URL: http://jira.codehaus.org/browse/MNG-1079 > Project: Maven 2 > Type: Bug > Components: maven-core > Reporter: Brett Porter &

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

[ http://jira.codehaus.org/browse/MNG-1096?page=all ] John Casey closed MNG-1096: --- Resolution: Fixed added error diagnoser for MojoExecutionException instances. > Error handling needs improvement > > >

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

[ http://jira.codehaus.org/browse/MNG-1096?page=all ] John Casey updated MNG-1096: Remaining Estimate: 1 hour Original Estimate: 3600 add error diagnoser for report exceptions, and see where we stand > Error handling needs improvem

[jira] Updated: (MNG-1079) error reporting for a plugin not found needs improvement

[ http://jira.codehaus.org/browse/MNG-1079?page=all ] Brett Porter updated MNG-1079: -- Component: maven-core > error reporting for a plugin not found needs improvement > > > K

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

[ http://jira.codehaus.org/browse/MNG-1096?page=all ] Brett Porter updated MNG-1096: -- Fix Version: 2.0-beta-4 > Error handling needs improvement > > > Key: MNG-1096 > URL: http://jira.code

[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] Updated: (MNG-1079) error reporting for a plugin not found needs improvement

[ http://jira.codehaus.org/browse/MNG-1079?page=all ] John Casey updated MNG-1079: Complexity: Expert (was: Intermediate) Remaining Estimate: 2 hours Original Estimate: 7200 > error reporting for a plugin not found needs improvem

[jira] Created: (MNG-1079) error reporting for a plugin not found needs improvement

error reporting for a plugin not found needs improvement Key: MNG-1079 URL: http://jira.codehaus.org/browse/MNG-1079 Project: Maven 2 Type: Bug Reporter: Brett Porter Fix For: 2.0-beta-4 currently, you

[jira] Updated: (MNG-4) MavenXpp3Writer improvement

[ http://jira.codehaus.org/browse/MNG-4?page=all ] Brett Porter updated MNG-4: --- Fix Version: 2.1 > MavenXpp3Writer improvement > --- > > Key: MNG-4 > URL: http://jira.codehaus.org/browse/MNG-4 >

[jira] Updated: (MNG-4) MavenXpp3Writer improvement

[ http://jira.codehaus.org/browse/MNG-4?page=all ] Brett Porter updated MNG-4: --- Component: maven-model > MavenXpp3Writer improvement > --- > > Key: MNG-4 > URL: http://jira.codehaus.org/browse/MNG-4

[jira] Created: (MNG-474) performance improvement for forked lifecycles

performance improvement for forked lifecycles - Key: MNG-474 URL: http://jira.codehaus.org/browse/MNG-474 Project: Maven 2 Type: Improvement Components: maven-core Reporter: Brett Porter Fix For: 2.1-beta-1

[jira] Closed: (MAVEN-1608) Repository upload documentation improvement

[ http://jira.codehaus.org/browse/MAVEN-1608?page=all ] Brett Porter closed MAVEN-1608: --- Resolution: Fixed > Repository upload documentation improvement > --- > > Key: MAVEN-1608 >

[jira] Created: (MAVEN-1608) Repository upload documentation improvement

Repository upload documentation improvement --- Key: MAVEN-1608 URL: http://jira.codehaus.org/browse/MAVEN-1608 Project: maven Type: Improvement Components: documentation Reporter: Carlos Sanchez Attachments

Re: Some questions on dist plugin and proposal for improvement

a new goal to handle their format, if necessary. Sounds cool. Brett, what do you think? Sounds good for this particular issue. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PRO

RE: Some questions on dist plugin and proposal for improvement

Hi Felipe, > -Original Message- > From: Felipe Leme [mailto:[EMAIL PROTECTED] > Sent: lundi 8 novembre 2004 00:24 > To: Maven Developers List > Subject: RE: Some questions on dist plugin and proposal for improvement > > Vincent, > > On Tue, 2004-11-02 at

Re: Some questions on dist plugin and proposal for improvement

NSIS was decoupled from dist a while back. On Tue, 02 Nov 2004 22:43:41 +1100, Brett Porter <[EMAIL PROTECTED]> wrote: > Vincent Massol wrote: > > >Hi Mavens, > > > >I was browsing through the dist plugin source code and I have a few > >questions/remarks/proposal: > > > >1/ Are the following pro

RE: Some questions on dist plugin and proposal for improvement

Vincent, On Tue, 2004-11-02 at 12:04, Vincent Massol wrote: > ATM, there are 2 supported distribution types: zip and tar.gz. > ATM, they are both mandatory. Do you think they should be kept mandatory? I don't think they should be mandatory. In fact, I have already modified the plugin locally (t

RE: Some questions on dist plugin and proposal for improvement

Hi Brett, > -Original Message- > From: Brett Porter [mailto:[EMAIL PROTECTED] > Sent: mardi 2 novembre 2004 12:44 > To: Maven Developers List > Subject: Re: Some questions on dist plugin and proposal for improvement > > >Hi Mavens, > > > >I was bro

Re: Some questions on dist plugin and proposal for improvement

Vincent Massol wrote: Hi Mavens, I was browsing through the dist plugin source code and I have a few questions/remarks/proposal: 1/ Are the following properties used at all or can they be deleted: maven.dist.tar.executable=tar maven.dist.gunzip.executable=gunzip They can now be removed. 2/ Why

Some questions on dist plugin and proposal for improvement

Hi Mavens, I was browsing through the dist plugin source code and I have a few questions/remarks/proposal: 1/ Are the following properties used at all or can they be deleted: maven.dist.tar.executable=tar maven.dist.gunzip.executable=gunzip 2/ Why is there a dependency to the jar:jar goal in th

[jira] Closed: (MAVEN-1480) Improvement on repository-upload.xml

: MAVEN-1480 Summary: Improvement on repository-upload.xml Type: Improvement Status: Closed Priority: Major Resolution: FIXED Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven Components: documentation Fix Fors

[jira] Updated: (MAVEN-1480) Improvement on repository-upload.xml

: - Key: MAVEN-1480 Summary: Improvement on repository-upload.xml Type: Improvement Status: Unassigned Priority: Major Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven Components: documentation Fix Fors

[jira] Created: (MAVEN-1480) Improvement on repository-upload.xml

: MAVEN-1480 Summary: Improvement on repository-upload.xml Type: Improvement Status: Unassigned Priority: Major Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven Components: documentation Fix Fors: 1.0.1

Re: War plugin improvement

Sounds like a good idea to me. - Brett Quoting Carlos Sanchez <[EMAIL PROTECTED]>: > Hi, > > Sorry about disturbing with work in this moment of happiness ;) > > I need to make some improvements to the war plugin, at least splitting the > war:webapp in war:war-resources (to be run before tests)

War plugin improvement

Hi, Sorry about disturbing with work in this moment of happiness ;) I need to make some improvements to the war plugin, at least splitting the war:webapp in war:war-resources (to be run before tests) and war:webapp. So if anyone has any inconvenience please tell me, else I'll make them. Regards

Re: Maven2 (was Re: maven-plugin-plugin generate docs improvement)

On Wed, 2004-06-23 at 22:48, M. Sean Gilligan wrote: > >These are all good ideas, however it is probably not worth the effort at this > >point. m2's plugins are self documenting in the fashion you are talking about, > >and there is a clear direction to start pushing them in to use in maven 1 in the

RE: Maven2 (was Re: maven-plugin-plugin generate docs improvement )

> -Original Message- > From: M. Sean Gilligan [mailto:[EMAIL PROTECTED] > Sent: Thursday, June 24, 2004 4:49 AM > To: Maven Developers List > Subject: Maven2 (was Re: maven-plugin-plugin generate docs > improvement) > > > >These are all good ideas, ho

Maven2 (was Re: maven-plugin-plugin generate docs improvement)

>These are all good ideas, however it is probably not worth the effort at this >point. m2's plugins are self documenting in the fashion you are talking about, >and there is a clear direction to start pushing them in to use in maven 1 in the >near future. > Sounds cool. This leads to the following

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

script. I don't understand what you mean by "blow out the plugin.jelly script". Mixing code and documentation is generally a good idea when the documentation is minimal and closely tied to the code, two conditions which, I believe, are true in this case. Also, from Brett's post

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

;ll just blow out the plugin.jelly script. > 5) If all of the above are implemented, an undocumented properties report is > probably not necessary, but could be added as an additional mechanism for > encouraging better documentation. > As I said, I'm willing to contribute but I

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

All, These are all good ideas, however it is probably not worth the effort at this point. m2's plugins are self documenting in the fashion you are talking about, and there is a clear direction to start pushing them in to use in maven 1 in the near future. Hope this helps! Cheers, Brett Quoting

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

entation. As I said, I'm willing to contribute but I'll need help from some more experienced Maven folks. Hopefully Dion Gillard will agree this is a useful improvement (again, for the post 1.0 time-frame) and have some time to work on it. I'm not comfortable with Jelly, etc. and I do

RE: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

ditional mechanism for encouraging better documentation. As I said, I'm willing to contribute but I'll need help from some more experienced Maven folks. Hopefully Dion Gillard will agree this is a useful improvement (again, for the post 1.0 time-frame) and have some time to work on it.

Re: RE : RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Heritier Arnaud wrote: The problem is that in some plugins, the documentation of goals is very more detailled in the doc than in the plugin.jelly. In the goal's description you can't use HTML tags. For example : http://maven.apache.org/reference/plugins/dist/goals.html HTML in goal documentation

RE : RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

> the properties.xml could be generated with a more advanced > parsing and > maybe assuming all properties begin with the plugin name > followed by a '.' The problem will be to standardize the properties documentation and to parse the file. # MY DOC xxx..= > > Should synchro

Re: RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

elly, or does it? Arnaud -Message d'origine- De : Miguel Griffa [mailto:[EMAIL PROTECTED] Envoyé : mercredi 23 juin 2004 14:34 À : Maven Developers List Objet : Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17) Hi, I totally agree with this. Generating the goals.xml shuold b

RE : maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Miguel Griffa [mailto:[EMAIL PROTECTED] > Envoyé : mercredi 23 juin 2004 14:34 > À : Maven Developers List > Objet : Re: maven-plugin-plugin generate docs improvement > (MPPLUGIN-17) > > > Hi, > I totally agree with this. Generating the goals.xml > shuold be quite >

Re: maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Hi, I totally agree with this. Generating the goals.xml shuold be quite easy (a simple matter of xsl), the properties.xml may be another story... Having goals.xml generated would contribute to a more uniform documentation M. Sean Gilligan wrote: Hello Dion, et. al., I thought I'd move some

maven-plugin-plugin generate docs improvement (MPPLUGIN-17)

Hello Dion, et. al., I thought I'd move some of this (http://jira.codehaus.org/browse/MPPLUGIN-17) discussion off of JIRA and on to the dev list. (I'm not sure what the correct protocol is, so please forgive me if I'm breaking it. I also apologize if a JIRA priority of "major" seems high, I n

[jira] Closed: (MPXDOC-95) doc:jslToSite failing + escapeNameToken improvement

overview of the issue: - Key: MPXDOC-95 Summary: doc:jslToSite failing + escapeNameToken improvement Type: Bug Status: Closed Priority: Major Resolution: FIXED Original Estimate: 5 minutes Time Spent

[jira] Updated: (MPXDOC-95) doc:jslToSite failing + escapeNameToken improvement

ssue: - Key: MPXDOC-95 Summary: doc:jslToSite failing + escapeNameToken improvement Type: Bug Status: Open Priority: Major Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: m

[jira] Created: (MPXDOC-95) doc:jslToSite failing + escapeNameToken improvement

: - Key: MPXDOC-95 Summary: doc:jslToSite failing + escapeNameToken improvement Type: Bug Status: Open Priority: Major Original Estimate: 5 minutes Time Spent: Unknown Remaining: 5 minutes Project: maven-xdoc-plugin Assignee: Jason van Zyl Reporter

[jira] Created: (MNG-4) MavenXpp3Writer improvement

: - Key: MNG-4 Summary: MavenXpp3Writer improvement Type: Improvement Status: Unassigned Priority: Major Original Estimate: Unknown Time Spent: Unknown Remaining: Unknown Project: m2 Assignee: Reporter: gilles dodinet Created: Tue, 13 Apr 2004 3:33

[jira] Closed: (MAVEN-845) tasklist && xdoc plugin improvement

an overview of the issue: - Key: MAVEN-845 Summary: tasklist && xdoc plugin improvement Type: Improvement Status: Closed Priority: Minor Resolution: FIXED Time Spent: Unknown Remaining:

[jira] Updated: (MAVEN-845) tasklist && xdoc plugin improvement

ssue: http://jira.codehaus.org/secure/ViewIssue.jspa?key=MAVEN-845 Here is an overview of the issue: - Key: MAVEN-845 Summary: tasklist && xdoc plugin improvement Type: Improvement Status

[jira] Created: (MAVEN-845) tasklist && xdoc plugin improvement

: - Key: MAVEN-845 Summary: tasklist && xdoc plugin improvement Type: Improvement Status: Unassigned Priority: Minor Time Spent: Unknown Remaining: Unknown Project: maven Components: plugin-xdoc plugin-tasklist