As well, Ant already has an xml format for it's properties.
See http://ant.apache.org/manual/CoreTasks/xmlproperty.html
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.multitask.com.au
Rafal Krzewski <[EMAIL PROTECTED]> wrote on 27/06
> > We also need it for documentation. Its quite common for people to ask
> > 'what property do I set to do' because there are so many
> > undocumented properties. If there was a metadata file that described
> > plugin properties, it could be used to generate the xdocs.
> There is one. It's ca
[EMAIL PROTECTED] wrote:
>>We also need it for documentation. Its quite common for people to ask
>>'what property do I set to do' because there are so many
>>undocumented properties. If there was a metadata file that described
>>plugin properties, it could be used to generate the xdocs.
>
Brian Ewins <[EMAIL PROTECTED]> wrote on 26/06/2003
06:29:09 PM:
> Michal Maczka wrote:
>
> >
> > I think we should go step further and get rid of plugin.properties
file...
> > in favour of metadata file.
> > It can look like:
> [snip]
> > BTW: We anyway need plugin metadata file which can be
is the best idea so far.
> mm
>
> > -Original Message-
> > From: Mark H. Wilkinson [mailto:[EMAIL PROTECTED]
> > Sent: Thursday, June 26, 2003 11:10 AM
> > To: Maven Developers List
> > Subject: Re: Aligning plugin artifacts with normal projects
> >
On Thu, 2003-06-26 at 01:40, [EMAIL PROTECTED] wrote:
> How would we be able to differentiate then between the properties a plugin
> exposes and those it uses for it's own purposes? The plugin plugin uses
> plugin.properties to generate docs.
Ok, it looks like we will keep both in order to make
June 2003 23:59
> > To: Maven Developers List
> > Subject: Aligning plugin artifacts with normal projects
> >
> > Hi,
> >
> > We had a quick chat in IRC about aligning plugin artifacts with normal
> > Maven Projects. By this I mean using maven.xml instead of plu
I like this idea!
mm
> -Original Message-
> From: Mark H. Wilkinson [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 11:10 AM
> To: Maven Developers List
> Subject: Re: Aligning plugin artifacts with normal projects
>
> On Wed, 2003-06-25 at 22:58, Jason
On Wed, 2003-06-25 at 22:58, Jason van Zyl wrote:
> Hi,
>
> We had a quick chat in IRC about aligning plugin artifacts with normal
> Maven Projects. By this I mean using maven.xml instead of plugin.jelly
> and the simple project.properties instead of plugin.properties.
Responses seem to be sugges
: Aligning plugin artifacts with normal projects
How would we be able to differentiate then between the properties a plugin
exposes and those it uses for it's own purposes? The plugin plugin uses
plugin.properties to generate docs.
I have exactly the same doubts.
I think we should go step fu
Michal Maczka wrote:
I think we should go step further and get rid of plugin.properties file...
in favour of metadata file.
It can look like:
[snip]
BTW: We anyway need plugin metadata file which can be used by IDEs.
Agree 100%.
We also need it for documentation. Its quite common for people to a
> -Original Message-
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
> Sent: Thursday, June 26, 2003 7:41 AM
> To: Maven Developers List
> Subject: Re: Aligning plugin artifacts with normal projects
>
> How would we be able to differentiate then between th
I could only find it on the Jelly site :)
- Brett
Ben Walding wrote:
irc.codehaus.org:6667
#maven
Probably is documented, but I have no idea where :)
Martin Skopp wrote:
--
Web Developer
f2 network ~ everything essential
02 8596 4437
---
irc.codehaus.org:6667
#maven
Probably is documented, but I have no idea where :)
Martin Skopp wrote:
On Wed, 2003-06-25 at 23:58, Jason van Zyl wrote:
We had a quick chat in IRC about aligning plugin artifacts with normal
Is there a special maven channel where you guy hang around?
Could
On Wed, 2003-06-25 at 23:58, Jason van Zyl wrote:
> We had a quick chat in IRC about aligning plugin artifacts with normal
Is there a special maven channel where you guy hang around?
Could one provide server and channelname?
Forgive me if it's somewhere documented...
Thanks
--
Martin Skopp
Rieg
How would we be able to differentiate then between the properties a plugin
exposes and those it uses for it's own purposes? The plugin plugin uses
plugin.properties to generate docs.
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Work: http://www.mult
an Zyl [mailto:[EMAIL PROTECTED]
> Sent: 25 June 2003 23:59
> To: Maven Developers List
> Subject: Aligning plugin artifacts with normal projects
>
> Hi,
>
> We had a quick chat in IRC about aligning plugin artifacts with normal
> Maven Projects. By this I mean using mav
Hi,
We had a quick chat in IRC about aligning plugin artifacts with normal
Maven Projects. By this I mean using maven.xml instead of plugin.jelly
and the simple project.properties instead of plugin.properties.
I think this alignment would make explaining plugins work as they now do
work the same
18 matches
Mail list logo
