You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Hubert Iwaniuk <ne...@kungfoo.pl> on 2009/04/08 15:03:16 UTC
Maven Overview Plugin version 1.4 has been released
Maven Overview Plugin version 1.4 has been released.
http://code.google.com/p/maven-overview-plugin/
Maven Overview Plugin graphs your Maven dependencies. You can use it
in plugin or report mode to generate just graph or integrate with site
generated by Maven respectively.
This release improves filtering:
http://code.google.com/p/maven-overview-plugin/issues/list?can=1&q=la...<http://code.google.com/p/maven-overview-plugin/issues/list?can=1&q=label%3AMilestone-Filtering>
You can now filter by max depth, scope and general artifact
properties, please refer to MOP documentation at
http://maven-overview-plugin.googlecode.com/svn/site/overview-mojo.html
Any questions are welcome at:
http://groups.google.com/group/maven-overview-plugin-discuss
MOP
Re: Maven Overview Plugin version 1.4 has been released
Posted by Stephen Connolly <st...@gmail.com>.
well in my case I wanted to try out the plugin first ;-)
Sent from my [rhymes with myPod] ;-)
On 9 Apr 2009, at 18:50, Dan Tran <da...@gmail.com> wrote:
> It is also interesting that we jumped on wagon of minor convention
> and forgot the praise for all the good works that developer has put
> in :-)
>
> -D
>
> On Thu, Apr 9, 2009 at 10:48 AM, Dan Tran <da...@gmail.com> wrote:
>> There is no way that we can infer enforcement this convention. If the
>> plugin belongs to a group then it is possible.
>>
>> however, personally I like name-maven-plugin since it is easy to use
>> key board to do auto complete when I have bunch of plugins to manage.
>>
>> -D
>>
>>
>>
>> On Thu, Apr 9, 2009 at 6:08 AM, Stephen Connolly
>> <st...@gmail.com> wrote:
>>> 2009/4/9 Nord, James <JN...@nds.com>
>>>
>>>>
>>>>> -----Original Message-----
>>>>> From: Rémy Sanlaville [mailto:remy.sanlaville@gmail.com]
>>>>> Sent: 09 April 2009 08:27
>>>>> To: Maven Users List
>>>>> Subject: Re: Maven Overview Plugin version 1.4 has been released
>>>>>
>>>>>>
>>>>>> as long as the plugin has its own groupId, the artifactId
>>>>> can be any thing.
>>>>>
>>>>>
>>>>> IMHO, even if the plugin has its own groupId, I agree with
>>>>> Stephen that it's better to keep the convention :
>>>>> maven-_____-plugin for o.a.m.p plugins
>>>>> _____-maven-plugin for other plugins
>>>>>
>>>>
>>>> This was news to me to. Is this documtented anywhere - prehaps
>>>> it needs to
>>>> be or made more prominent.
>>>>
>>>> The only thing I could find from google (maven plugin naming
>>>> conventions)
>>>> was the following two pages neither of which stated this
>>>> convention.
>>>>
>>>>
>>>> http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html
>>>>
>>>> <snip>In other words, when the Maven Plugin Plugin is generating
>>>> the Plugin
>>>> descriptor for your plugin and you have not explicitly set the
>>>> goalPrefix in
>>>> your project, the plugin:descriptor goal will extract the prefix
>>>> from your
>>>> plugin's artifactId when it matches the following patterns:
>>>> ${prefix}-maven-plugin, OR
>>>> maven-${prefix}-plugin
>>>> </snip>
>>>>
>>>> And
>>>>
>>>> http://maven.apache.org/guides/mini/guide-naming-conventions.html
>>>>
>>>> Which mentions nothing... It seems like although codehause
>>>> standardised
>>>> one _-maven-plugin and maven.a.o standardised on maven-__-plug-in
>>>> other
>>>> groups haven't standardised on either and they are all a mix
>>>>
>>>> e.g.
>>>> maven-jetty-plug-in (org.mortbay.jetty)
>>>
>>>
>>> except, afaik, jetty have changed from maven-jetty-plugin to
>>> jetty-maven-plugin *because* they were told (by somebody other
>>> than me) that
>>> the convention was ____-m-p for not o.a.m.p and m-____-p only for
>>> o.m.a.p
>>>
>>> See: http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
>>>
>>> *Jetty Version Information*
>>>
>>> Jetty7 - This plugin was renamed to jetty-maven-plugin to better
>>> conform to
>>> maven2 convention.
>>>
>>>
>>>
>>>>
>>>> tools-maven-plugin (org.apache.geronimo.genesis.plugins)
>>>> maven-jaxme-plug-in (org.apache.ws.jaxme)
>>>>
>>>> (also try a quick search in nexus for *-maven-plug-in and maven-*-
>>>> plug-in -
>>>> and it looks like the hourse has bolted..)
>>>>
>>>>
>>>> /James
>>>>
>>>>
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> *****************************************************************
>>>> This e-mail is confidential, the property of NDS Ltd and intended
>>>> for the
>>>> addressee only. Any dissemination, copying or distribution of
>>>> this message
>>>> or any attachments by anyone other than the intended recipient is
>>>> strictly
>>>> prohibited. If you have received this message in error, please
>>>> immediately
>>>> notify the postmaster@nds.com and destroy the original message.
>>>> Messages
>>>> sent to and from NDS may be monitored. NDS cannot guarantee any
>>>> message
>>>> delivery method is secure or error-free. Information could be
>>>> intercepted,
>>>> corrupted, lost, destroyed, arrive late or incomplete, or contain
>>>> viruses.
>>>> We do not accept responsibility for any errors or omissions in
>>>> this message
>>>> and/or attachment that arise as a result of transmission. You
>>>> should carry
>>>> out your own virus checks before opening any attachment. Any
>>>> views or
>>>> opinions presented are solely those of the author and do not
>>>> necessarily
>>>> represent those of NDS.
>>>>
>>>> To protect the environment please do not print this e-mail unless
>>>> necessary.
>>>>
>>>> NDS Limited Registered Office: One London Road, Staines,
>>>> Middlesex, TW18
>>>> 4EX, United Kingdom. A company registered in England and Wales
>>>> Registered
>>>> no. 3080780 VAT no. GB 603 8808 40-00
>>>>
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> ***
>>>> *****************************************************************
>>>>
>>>> ---
>>>> ------------------------------------------------------------------
>>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: users-help@maven.apache.org
>>>>
>>>>
>>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Overview Plugin version 1.4 has been released
Posted by Dan Tran <da...@gmail.com>.
It is also interesting that we jumped on wagon of minor convention
and forgot the praise for all the good works that developer has put
in :-)
-D
On Thu, Apr 9, 2009 at 10:48 AM, Dan Tran <da...@gmail.com> wrote:
> There is no way that we can infer enforcement this convention. If the
> plugin belongs to a group then it is possible.
>
> however, personally I like name-maven-plugin since it is easy to use
> key board to do auto complete when I have bunch of plugins to manage.
>
> -D
>
>
>
> On Thu, Apr 9, 2009 at 6:08 AM, Stephen Connolly
> <st...@gmail.com> wrote:
>> 2009/4/9 Nord, James <JN...@nds.com>
>>
>>>
>>> > -----Original Message-----
>>> > From: Rémy Sanlaville [mailto:remy.sanlaville@gmail.com]
>>> > Sent: 09 April 2009 08:27
>>> > To: Maven Users List
>>> > Subject: Re: Maven Overview Plugin version 1.4 has been released
>>> >
>>> > >
>>> > > as long as the plugin has its own groupId, the artifactId
>>> > can be any thing.
>>> >
>>> >
>>> > IMHO, even if the plugin has its own groupId, I agree with
>>> > Stephen that it's better to keep the convention :
>>> > maven-_____-plugin for o.a.m.p plugins
>>> > _____-maven-plugin for other plugins
>>> >
>>>
>>> This was news to me to. Is this documtented anywhere - prehaps it needs to
>>> be or made more prominent.
>>>
>>> The only thing I could find from google (maven plugin naming conventions)
>>> was the following two pages neither of which stated this convention.
>>>
>>>
>>> http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html
>>>
>>> <snip>In other words, when the Maven Plugin Plugin is generating the Plugin
>>> descriptor for your plugin and you have not explicitly set the goalPrefix in
>>> your project, the plugin:descriptor goal will extract the prefix from your
>>> plugin's artifactId when it matches the following patterns:
>>> ${prefix}-maven-plugin, OR
>>> maven-${prefix}-plugin
>>> </snip>
>>>
>>> And
>>>
>>> http://maven.apache.org/guides/mini/guide-naming-conventions.html
>>>
>>> Which mentions nothing... It seems like although codehause standardised
>>> one _-maven-plugin and maven.a.o standardised on maven-__-plug-in other
>>> groups haven't standardised on either and they are all a mix
>>>
>>> e.g.
>>> maven-jetty-plug-in (org.mortbay.jetty)
>>
>>
>> except, afaik, jetty have changed from maven-jetty-plugin to
>> jetty-maven-plugin *because* they were told (by somebody other than me) that
>> the convention was ____-m-p for not o.a.m.p and m-____-p only for o.m.a.p
>>
>> See: http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
>>
>> *Jetty Version Information*
>>
>> Jetty7 - This plugin was renamed to jetty-maven-plugin to better conform to
>> maven2 convention.
>>
>>
>>
>>>
>>> tools-maven-plugin (org.apache.geronimo.genesis.plugins)
>>> maven-jaxme-plug-in (org.apache.ws.jaxme)
>>>
>>> (also try a quick search in nexus for *-maven-plug-in and maven-*-plug-in -
>>> and it looks like the hourse has bolted..)
>>>
>>>
>>> /James
>>>
>>>
>>> **************************************************************************************
>>> This e-mail is confidential, the property of NDS Ltd and intended for the
>>> addressee only. Any dissemination, copying or distribution of this message
>>> or any attachments by anyone other than the intended recipient is strictly
>>> prohibited. If you have received this message in error, please immediately
>>> notify the postmaster@nds.com and destroy the original message. Messages
>>> sent to and from NDS may be monitored. NDS cannot guarantee any message
>>> delivery method is secure or error-free. Information could be intercepted,
>>> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
>>> We do not accept responsibility for any errors or omissions in this message
>>> and/or attachment that arise as a result of transmission. You should carry
>>> out your own virus checks before opening any attachment. Any views or
>>> opinions presented are solely those of the author and do not necessarily
>>> represent those of NDS.
>>>
>>> To protect the environment please do not print this e-mail unless
>>> necessary.
>>>
>>> NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18
>>> 4EX, United Kingdom. A company registered in England and Wales Registered
>>> no. 3080780 VAT no. GB 603 8808 40-00
>>>
>>> **************************************************************************************
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: users-help@maven.apache.org
>>>
>>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Overview Plugin version 1.4 has been released
Posted by Dan Tran <da...@gmail.com>.
There is no way that we can infer enforcement this convention. If the
plugin belongs to a group then it is possible.
however, personally I like name-maven-plugin since it is easy to use
key board to do auto complete when I have bunch of plugins to manage.
-D
On Thu, Apr 9, 2009 at 6:08 AM, Stephen Connolly
<st...@gmail.com> wrote:
> 2009/4/9 Nord, James <JN...@nds.com>
>
>>
>> > -----Original Message-----
>> > From: Rémy Sanlaville [mailto:remy.sanlaville@gmail.com]
>> > Sent: 09 April 2009 08:27
>> > To: Maven Users List
>> > Subject: Re: Maven Overview Plugin version 1.4 has been released
>> >
>> > >
>> > > as long as the plugin has its own groupId, the artifactId
>> > can be any thing.
>> >
>> >
>> > IMHO, even if the plugin has its own groupId, I agree with
>> > Stephen that it's better to keep the convention :
>> > maven-_____-plugin for o.a.m.p plugins
>> > _____-maven-plugin for other plugins
>> >
>>
>> This was news to me to. Is this documtented anywhere - prehaps it needs to
>> be or made more prominent.
>>
>> The only thing I could find from google (maven plugin naming conventions)
>> was the following two pages neither of which stated this convention.
>>
>>
>> http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html
>>
>> <snip>In other words, when the Maven Plugin Plugin is generating the Plugin
>> descriptor for your plugin and you have not explicitly set the goalPrefix in
>> your project, the plugin:descriptor goal will extract the prefix from your
>> plugin's artifactId when it matches the following patterns:
>> ${prefix}-maven-plugin, OR
>> maven-${prefix}-plugin
>> </snip>
>>
>> And
>>
>> http://maven.apache.org/guides/mini/guide-naming-conventions.html
>>
>> Which mentions nothing... It seems like although codehause standardised
>> one _-maven-plugin and maven.a.o standardised on maven-__-plug-in other
>> groups haven't standardised on either and they are all a mix
>>
>> e.g.
>> maven-jetty-plug-in (org.mortbay.jetty)
>
>
> except, afaik, jetty have changed from maven-jetty-plugin to
> jetty-maven-plugin *because* they were told (by somebody other than me) that
> the convention was ____-m-p for not o.a.m.p and m-____-p only for o.m.a.p
>
> See: http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
>
> *Jetty Version Information*
>
> Jetty7 - This plugin was renamed to jetty-maven-plugin to better conform to
> maven2 convention.
>
>
>
>>
>> tools-maven-plugin (org.apache.geronimo.genesis.plugins)
>> maven-jaxme-plug-in (org.apache.ws.jaxme)
>>
>> (also try a quick search in nexus for *-maven-plug-in and maven-*-plug-in -
>> and it looks like the hourse has bolted..)
>>
>>
>> /James
>>
>>
>> **************************************************************************************
>> This e-mail is confidential, the property of NDS Ltd and intended for the
>> addressee only. Any dissemination, copying or distribution of this message
>> or any attachments by anyone other than the intended recipient is strictly
>> prohibited. If you have received this message in error, please immediately
>> notify the postmaster@nds.com and destroy the original message. Messages
>> sent to and from NDS may be monitored. NDS cannot guarantee any message
>> delivery method is secure or error-free. Information could be intercepted,
>> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
>> We do not accept responsibility for any errors or omissions in this message
>> and/or attachment that arise as a result of transmission. You should carry
>> out your own virus checks before opening any attachment. Any views or
>> opinions presented are solely those of the author and do not necessarily
>> represent those of NDS.
>>
>> To protect the environment please do not print this e-mail unless
>> necessary.
>>
>> NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18
>> 4EX, United Kingdom. A company registered in England and Wales Registered
>> no. 3080780 VAT no. GB 603 8808 40-00
>>
>> **************************************************************************************
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Overview Plugin version 1.4 has been released
Posted by Stephen Connolly <st...@gmail.com>.
2009/4/9 Nord, James <JN...@nds.com>
>
> > -----Original Message-----
> > From: Rémy Sanlaville [mailto:remy.sanlaville@gmail.com]
> > Sent: 09 April 2009 08:27
> > To: Maven Users List
> > Subject: Re: Maven Overview Plugin version 1.4 has been released
> >
> > >
> > > as long as the plugin has its own groupId, the artifactId
> > can be any thing.
> >
> >
> > IMHO, even if the plugin has its own groupId, I agree with
> > Stephen that it's better to keep the convention :
> > maven-_____-plugin for o.a.m.p plugins
> > _____-maven-plugin for other plugins
> >
>
> This was news to me to. Is this documtented anywhere - prehaps it needs to
> be or made more prominent.
>
> The only thing I could find from google (maven plugin naming conventions)
> was the following two pages neither of which stated this convention.
>
>
> http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html
>
> <snip>In other words, when the Maven Plugin Plugin is generating the Plugin
> descriptor for your plugin and you have not explicitly set the goalPrefix in
> your project, the plugin:descriptor goal will extract the prefix from your
> plugin's artifactId when it matches the following patterns:
> ${prefix}-maven-plugin, OR
> maven-${prefix}-plugin
> </snip>
>
> And
>
> http://maven.apache.org/guides/mini/guide-naming-conventions.html
>
> Which mentions nothing... It seems like although codehause standardised
> one _-maven-plugin and maven.a.o standardised on maven-__-plug-in other
> groups haven't standardised on either and they are all a mix
>
> e.g.
> maven-jetty-plug-in (org.mortbay.jetty)
except, afaik, jetty have changed from maven-jetty-plugin to
jetty-maven-plugin *because* they were told (by somebody other than me) that
the convention was ____-m-p for not o.a.m.p and m-____-p only for o.m.a.p
See: http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
*Jetty Version Information*
Jetty7 - This plugin was renamed to jetty-maven-plugin to better conform to
maven2 convention.
>
> tools-maven-plugin (org.apache.geronimo.genesis.plugins)
> maven-jaxme-plug-in (org.apache.ws.jaxme)
>
> (also try a quick search in nexus for *-maven-plug-in and maven-*-plug-in -
> and it looks like the hourse has bolted..)
>
>
> /James
>
>
> **************************************************************************************
> This e-mail is confidential, the property of NDS Ltd and intended for the
> addressee only. Any dissemination, copying or distribution of this message
> or any attachments by anyone other than the intended recipient is strictly
> prohibited. If you have received this message in error, please immediately
> notify the postmaster@nds.com and destroy the original message. Messages
> sent to and from NDS may be monitored. NDS cannot guarantee any message
> delivery method is secure or error-free. Information could be intercepted,
> corrupted, lost, destroyed, arrive late or incomplete, or contain viruses.
> We do not accept responsibility for any errors or omissions in this message
> and/or attachment that arise as a result of transmission. You should carry
> out your own virus checks before opening any attachment. Any views or
> opinions presented are solely those of the author and do not necessarily
> represent those of NDS.
>
> To protect the environment please do not print this e-mail unless
> necessary.
>
> NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18
> 4EX, United Kingdom. A company registered in England and Wales Registered
> no. 3080780 VAT no. GB 603 8808 40-00
>
> **************************************************************************************
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
RE: Maven Overview Plugin version 1.4 has been released
Posted by "Nord, James" <JN...@nds.com>.
> -----Original Message-----
> From: Rémy Sanlaville [mailto:remy.sanlaville@gmail.com]
> Sent: 09 April 2009 08:27
> To: Maven Users List
> Subject: Re: Maven Overview Plugin version 1.4 has been released
>
> >
> > as long as the plugin has its own groupId, the artifactId
> can be any thing.
>
>
> IMHO, even if the plugin has its own groupId, I agree with
> Stephen that it's better to keep the convention :
> maven-_____-plugin for o.a.m.p plugins
> _____-maven-plugin for other plugins
>
This was news to me to. Is this documtented anywhere - prehaps it needs to be or made more prominent.
The only thing I could find from google (maven plugin naming conventions) was the following two pages neither of which stated this convention.
http://www.sonatype.com/books/maven-book/reference/writing-plugins-sect-plugin-prefix.html
<snip>In other words, when the Maven Plugin Plugin is generating the Plugin descriptor for your plugin and you have not explicitly set the goalPrefix in your project, the plugin:descriptor goal will extract the prefix from your plugin's artifactId when it matches the following patterns:
${prefix}-maven-plugin, OR
maven-${prefix}-plugin
</snip>
And
http://maven.apache.org/guides/mini/guide-naming-conventions.html
Which mentions nothing... It seems like although codehause standardised one _-maven-plugin and maven.a.o standardised on maven-__-plug-in other groups haven't standardised on either and they are all a mix
e.g.
maven-jetty-plug-in (org.mortbay.jetty)
tools-maven-plugin (org.apache.geronimo.genesis.plugins)
maven-jaxme-plug-in (org.apache.ws.jaxme)
(also try a quick search in nexus for *-maven-plug-in and maven-*-plug-in - and it looks like the hourse has bolted..)
/James
**************************************************************************************
This e-mail is confidential, the property of NDS Ltd and intended for the addressee only. Any dissemination, copying or distribution of this message or any attachments by anyone other than the intended recipient is strictly prohibited. If you have received this message in error, please immediately notify the postmaster@nds.com and destroy the original message. Messages sent to and from NDS may be monitored. NDS cannot guarantee any message delivery method is secure or error-free. Information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. We do not accept responsibility for any errors or omissions in this message and/or attachment that arise as a result of transmission. You should carry out your own virus checks before opening any attachment. Any views or opinions presented are solely those of the author and do not necessarily represent those of NDS.
To protect the environment please do not print this e-mail unless necessary.
NDS Limited Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales Registered no. 3080780 VAT no. GB 603 8808 40-00
**************************************************************************************
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Overview Plugin version 1.4 has been released
Posted by Rémy Sanlaville <re...@gmail.com>.
>
> as long as the plugin has its own groupId, the artifactId can be any thing.
IMHO, even if the plugin has its own groupId, I agree with Stephen that it's
better to keep the convention :
maven-_____-plugin for o.a.m.p plugins
_____-maven-plugin for other plugins
Rémy
Re: Maven Overview Plugin version 1.4 has been released
Posted by Dan Tran <da...@gmail.com>.
Stephen,
as long as the plugin has its own groupId, the artifactId can be any thing.
-D
On Wed, Apr 8, 2009 at 8:43 AM, Stephen Connolly
<st...@gmail.com> wrote:
> Ehhh,
>
> FYI, AFAIK
>
> maven-_____-plugin is reserved for o.a.m.p plugins
>
> all other plugins are supposed to use the pattern
>
> _____-maven-plugin
>
> -Stephen
>
> 2009/4/8 Hubert Iwaniuk <ne...@kungfoo.pl>
>
>> Maven Overview Plugin version 1.4 has been released.
>>
>> http://code.google.com/p/maven-overview-plugin/
>>
>> Maven Overview Plugin graphs your Maven dependencies. You can use it
>> in plugin or report mode to generate just graph or integrate with site
>> generated by Maven respectively.
>>
>> This release improves filtering:
>> http://code.google.com/p/maven-overview-plugin/issues/list?can=1&q=la...<
>> http://code.google.com/p/maven-overview-plugin/issues/list?can=1&q=label%3AMilestone-Filtering
>> >
>>
>> You can now filter by max depth, scope and general artifact
>> properties, please refer to MOP documentation at
>> http://maven-overview-plugin.googlecode.com/svn/site/overview-mojo.html
>>
>> Any questions are welcome at:
>> http://groups.google.com/group/maven-overview-plugin-discuss
>>
>> MOP
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: Maven Overview Plugin version 1.4 has been released
Posted by Stephen Connolly <st...@gmail.com>.
Ehhh,
FYI, AFAIK
maven-_____-plugin is reserved for o.a.m.p plugins
all other plugins are supposed to use the pattern
_____-maven-plugin
-Stephen
2009/4/8 Hubert Iwaniuk <ne...@kungfoo.pl>
> Maven Overview Plugin version 1.4 has been released.
>
> http://code.google.com/p/maven-overview-plugin/
>
> Maven Overview Plugin graphs your Maven dependencies. You can use it
> in plugin or report mode to generate just graph or integrate with site
> generated by Maven respectively.
>
> This release improves filtering:
> http://code.google.com/p/maven-overview-plugin/issues/list?can=1&q=la...<
> http://code.google.com/p/maven-overview-plugin/issues/list?can=1&q=label%3AMilestone-Filtering
> >
>
> You can now filter by max depth, scope and general artifact
> properties, please refer to MOP documentation at
> http://maven-overview-plugin.googlecode.com/svn/site/overview-mojo.html
>
> Any questions are welcome at:
> http://groups.google.com/group/maven-overview-plugin-discuss
>
> MOP
>