Martin Cooper wrote:
>
>
>>-----Original Message-----
>>From: St�phane MOR [mailto:[EMAIL PROTECTED]]
>>Sent: Monday, September 02, 2002 9:50 AM
>>To: Turbine Maven Users List
>>Subject: Plugin Src and dest Layout (was Re: Rep:Include HTML file in
>>xdocs)
>>
>>
>>
>>
>
>[snip]
>
>
>
>>Hi,
>>
>>What about a layout guided by the plugins ?
>>By this I mean that a plugin would take its sources from
>>src/${plugin.name} and process what it has to process to
>>target/${plugin.name}.
>>
>>
>
>Personally, I'm not at all keen on this approach. The problem is that it
>ties the source tree too closely to the plugins being used. The implication
>is that if, at some point in the future, a different plugin is used to
>accomplish the same task, then my CVS repository has to change to
>accommodate this. That's a big no-no to me.
>
A plugin that accomplishes the same task as another one
could extend the previous one, or be an alias of it, so
that it shares the same "namespace" or something, and thus
the same sources. A kind of "first arrived, first served" thing.
Changing a CVS repo because we have new plugins isn't something
very viable, I agree. We can, even now, switch very easily from
a plugin to another (for instance jalopy or jrefactory, checkstyle
or PMD, etc.)
I'm not very strong on the src stuff, because this relates to
the repo and can be a pain in the ass, but as we control the
target, I believe it would be handy to know where each plugins
outputs stuff to ("dist" to target/dist, "javadoc" to
target/javadoc, "war" to target/war, etc.)
So, maybe a ${plugin.target.dir} only would be appropriate (and
handy for plugin developpers)...
I played a little with it, and it's quite natural with things like
<mkdir dir="${plugin.target.dir}">
<copy dir="foo" todir="${plugin.target.dir}"/>, etc.
My 2 cents.
St�phane
>
>--
>Martin Cooper
>
>
>
>
>>This would give something like src/xdoc, which would be
>>output to target/xdoc. Then, it would be easier for the
>>end user to know what is used to do what, and where it
>>goes to. We already have src/java and src/test.
>>
>>The plugin base for Maven is starting to get really huge,
>>and it will for sure get bigger. This way, one could know
>>what plugins are used simply looking at the dir structure.
>>
>>I know that this would need quite some important refactorings,
>>but IMO the learning curve would be much smaller.
>>
>>We could even implement some properties, like
>>plugin.src.dir -> ${maven.src.dir}/${plugin.name}
>>plugin.target.dir -> ${maven.build.dir}/${plugin.name}
>>that would be made available to the plugin (like ${plugin.dir})
>>, so that we don't have to bother where the files are taken
>>and where we may output something.
>>
>>Any thoughts ?
>>
>>Thanks,
>>St�phane
>>
>>___________________________________________________________
>>Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
>>Yahoo! Mail : http://fr.mail.yahoo.com
>>
>>--
>>To unsubscribe, e-mail:
>><mailto:[EMAIL PROTECTED]>
>>For additional commands, e-mail:
>><mailto:[EMAIL PROTECTED]>
>>
>>
>>
>>
>
>
>--
>To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
>For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
>
>
>
___________________________________________________________
Do You Yahoo!? -- Une adresse @yahoo.fr gratuite et en fran�ais !
Yahoo! Mail : http://fr.mail.yahoo.com
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
