> -----Original Message-----
> From: Sonnek, Ryan [mailto:[EMAIL PROTECTED]
> Sent: Friday, January 09, 2004 4:59 PM
> To: 'Maven Users List'
> Subject: RE: Mutliple source directories in project.xml
> 
> 
> Why is it a bad idea?  How is it any different than having 
> /target/docs a
> property that all plugins CAN use?  It's not "hardcoded" and 
> can be changed
> by users that want to change the location of the files.  I'm 
> not seeing how
> this is any different.  The target directory is not a 
> free-for-all where
> plugins throw crap wherever they want.
> 

Because it is not necessary to have this aspect "configurable"
There is many plugin which are generating reports and which have hardcoded
the well known location: "{maven.build.dir}/generated-xdocs"


Example: (taken from SIMIAN plugin)

<ant:simian output="${maven.build.dir}/generated-xdocs/simian.log"
                lineCount="${maven.simian.linecount}"
                failOnDuplication="${maven.simian.failonduplication}">


And report generators are extremely plugable and they just works. 
It's simply useless and not wise to make evry thing configurable. Standards
are not configurable. 
Why would anybody care about it if it has a reasonable well know location?
The contract for a report generator is simple: put generated files to
"{maven.build.dir}/generated-xdocs".
I don't know anybody who ever even tried to change this location. We just
live with it. 
I am sure the same can happen to source code generators.



If today we have 

<reports>
   <report>xx</report> 
</reports>

We can imagine 
( I personally think that one source generator per project is the maximum
and this is just an example which illustrates my way of thinking)

<javaSourceGenerators>
  <javaSourceGenrator>javacc</javaSourceGenrator>
  <javaSourceGenrator>xdoclet</javaSourceGenrator>
<javaSourceGenerators>

<byteCodeEnhancers>
  <byteCodeEnhancer>kodo</byteCodeEnhancer>
  <byteCodeEnhancer>weblogicEJBCompiler</byteCodeEnhancer>
</byteCodeEnhancers>

and dozen other categories of tools.


Michal


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

Reply via email to