Ralph Goers wrote:

> Thanks. It does and it doesn't answer the question. I still don't have
> a clue what tags I would code to write a marmalade plugin for maven,
> let alone how to use it outside of maven. The plugin page lists a
> sample script but doesn't really describe anything. For example,
> http://maven.apache.org/maven2/developers/developing-plugins-with-marmalade.html
> shows an example with an execute tag with c:out as its child element.
> I presume that writes to the console, but I have no idea what other
> such tags are defined.

Documentation definitely needs some work, but its not the only thing.
Beanshell support is also not well documented at this point. It is one
of our areas of focus for September as we ramp up to a final release.

>
> I was hoping you could point me to the [VOTE] or [RT] thread where
> marmalade was discussed.
>
As far as the Maven community works (at least as I understand it), is
that we don't vote on every new feature. We work through issues in JIRA
and people have ample opportunity to speak up about it in advance. Major
changes to existing code would be discussed first on the list, of
course. If it is particular hairy we might discuss it in real time on
IRC and publish the logs as we did for some earlier design sessions.
Developers follow what is happening across JIRA, CVS and the lists and
have the opportunity to veto developments.

In this particular case, it was very early in the development of m2
which itself was part of a revolutionary effort rather than being on the
Maven mainline, so there was not a need for a great deal of discussion
as everything was experimental.

I don't even know what [RT] stands for, but I see people involved with
cocoon use it all the time in various lists. Maybe you can enlighten me.

I assume you are looking for further justifications for introducing
marmalade. The answer really is that my previous mail covered it. Maybe
John will have something to add.

- Brett


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to