Benjamin Bentmann wrote:
Hypermedia like the web is all about hyperlinks
In this spirit, Wendy has just suggested to add a link for the "mail
archive", too, which I happily adopted:
General instructions on how to use the Plugin Name can be found on the
{{{usage.html}usage page}}. Some m
Wendy Smoak wrote:
Each plugin has an associated wiki page... what do you think about
adding a link to it?
Hypermedia like the web is all about hyperlinks so I am +1 on your
suggestion. As a prerequisite, I made sure all our plugins have a
corresponding wiki page by adding a stub page where
Wendy Smoak wrote:
Each plugin has an associated wiki page... what do you think about
adding a link to it?
Hypermedia like the web is all about hyperlinks so I am +1 on your
suggestion. As a prerequisite, I made sure all our plugins have a
corresponding wiki page by adding a stub page where
On Fri, Aug 22, 2008 at 2:46 AM, Benjamin Bentmann
<[EMAIL PROTECTED]> wrote:
> I would like to propose the following update (excluding typos ;-) ) to the
> index.apt template given in the Plugin Documentation Standard [0]:
Sounds good. :)
Each plugin has an associated wiki page...
Vincent Siveton wrote:
+1 late ;)
Knowing that the proposal is supported by a good amount of the community
is always nice to know ;-)
Benjamin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [
+1 late ;)
Vincent
2008/8/22 Benjamin Bentmann <[EMAIL PROTECTED]>:
> Hi,
>
> I would like to propose the following update (excluding typos ;-) ) to the
> index.apt template given in the Plugin Documentation Standard [0]:
>
>> * Usage
>>
>> General instruc
Sounds good :)
On 22/08/2008, at 7:46 PM, Benjamin Bentmann wrote:
Hi,
I would like to propose the following update (excluding typos ;-) )
to the index.apt template given in the Plugin Documentation Standard
[0]:
* Usage
General instructions on how to use the Plugin Name can be found
Nice.
As a french reader, I haven't found any typos ;-).
--
Olivier
2008/8/22 Benjamin Bentmann <[EMAIL PROTECTED]>:
> Hi,
>
> I would like to propose the following update (excluding typos ;-) ) to the
> index.apt template given in the Plugin Documentation Sta
; I would like to propose the following update (excluding typos ;-) ) to the
>> index.apt template given in the Plugin Documentation Standard [0]:
>>
>>> * Usage
>>> General instructions on how to use the Plugin Name can be found on the
>>> {{{usage.html}usage p
Like a little "howto" read this documentation. I think it's good.
+1
On 22-Aug-08, at 2:46 AM, Benjamin Bentmann wrote:
Hi,
I would like to propose the following update (excluding typos ;-) )
to the index.apt template given in the Plugin Documentation Standard
[0]:
*
Hi,
I would like to propose the following update (excluding typos ;-) ) to
the index.apt template given in the Plugin Documentation Standard [0]:
* Usage
General instructions on how to use the Plugin Name can be found on the
{{{usage.html}usage page}}. Some more
specific use cases are
Brett Porter wrote:
Hi,
Just thought I'd break this one out. This needs to be converted to a
guide - which is one of the tasks I'll list at the end.
(this is MNG-1987, btw)
* Required POM Elements
- modelVersion, version, group ID, artifact ID, packaging (required
anyway to build)
- name
-
From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, June 19,
2006 9:56 AM
To: Maven Developers List
Subject: Re: Plugin documentation standard
On 19 Jun 06, at 9:47 AM 19 Jun 06, Brett Porter wrote:
Hi,
Just thought I'd break this one out. This needs to be converted to
a guide
Boss QA
>>
>> -
>> 512-342-7840 ext 2011
>> Yahoo: ruelloehr
>> Skype: ruelloehr
>> AOL: dokoruel
>>
>> -----Original Message-----
>> From: Jason van Zyl [mailto:[EMAIL PROTECTED] Sent: Monday, June 19,
>> 2006 9
al Message-
From: Jason van Zyl [mailto:[EMAIL PROTECTED]
Sent: Monday, June 19, 2006 9:56 AM
To: Maven Developers List
Subject: Re: Plugin documentation standard
On 19 Jun 06, at 9:47 AM 19 Jun 06, Brett Porter wrote:
Hi,
Just thought I'd break this one out. This needs to be convert
Sent: Monday, June 19, 2006 9:56 AM
To: Maven Developers List
Subject: Re: Plugin documentation standard
On 19 Jun 06, at 9:47 AM 19 Jun 06, Brett Porter wrote:
> Hi,
>
> Just thought I'd break this one out. This needs to be converted to
> a guide - which is one of the task
On 20/06/2006 12:56 AM, Jason van Zyl wrote:
Make a plugin to check all these thing and plug it into the validation
phase. This is all nice to enumerate but it will only take effect when
it is easy for people to comply.
Yah, sorry, I assumed everyone knew what docck was by osmosis or
somethin
On 19 Jun 06, at 9:47 AM 19 Jun 06, Brett Porter wrote:
Hi,
Just thought I'd break this one out. This needs to be converted to
a guide - which is one of the tasks I'll list at the end.
(this is MNG-1987, btw)
* Required POM Elements
- modelVersion, version, group ID, artifact ID, packagi
Hi,
Just thought I'd break this one out. This needs to be converted to a
guide - which is one of the tasks I'll list at the end.
(this is MNG-1987, btw)
* Required POM Elements
- modelVersion, version, group ID, artifact ID, packaging (required
anyway to build)
- name
- description
- url
-
Here's some additions, sorry I missed these:
# must have link to the API docs of of additional types (eg
MavenArchiveConfiguration)
# must describe how the configuration of some elements affects others,
where applicable (for example, surefire's suiteXmlFiles disables the
includes/excludes opti
20 matches
Mail list logo
