maven-m2-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Michal Maczka <mmac...@interia.pl>
Subject Re: [jira] Work started: (MNG-173) pom changes
Date Fri, 11 Mar 2005 02:30:30 GMT
Brett Porter wrote:

>Michal,
>
>I'm not responding much more to this thread as it seems to be going a little in
>circles. There is a basic misunderstanding here, so for the benefit of the whole
>list, let me try and clear it up.
>
>Versioning the POM is easier if we only make additions rather than removals
>and/or deprecations as it is backwards compatible without any work. The sensible
>thing to do then, is to make it a minimal POM. Anything that can go in plugin
>configuration should.
>That's not to say anything that can be shared shouldn't. It is being shared (eg,
>source directory). However, they'll only be introduced to the POM after careful
>consideration.
>
>They must be useful in more than one context though, and the fact that their
>value is the same must be a requirement, rather than coincidental. For example,
>the JDK requirement of compilation and runtime may be different, so are better
>specified separately.
>  
>
///I was thinking about something like:

//<project>
    <!-- standardized tags -->
    <groupId></groupId>
    ...
     <!-- those are settings which are shared among plugin and plugins 
can override them -->
     <properties>
         <jdkVersion>5<jdkVersion>
         ...
//         <groovyDevelopmentKitVersion>0.8<groovyDevelopmentKitVersion>
//         <groovySources>src/main/groovy<//groovySources//>/
/     </properties>

     <!-- plugin specific setting -->
    <plugins>
    </plugins>
//</project>/

I am also hoping to see more code reuse among plugins and see more 
standard components used in plugins.
For example jar,ear, war plugin they all need to generate manifest file.
So in place of configuring each of them sepratly - it will be nice to 
configure plexus components (like ManifestGenerator) per project and 
reuse those component in multiple plugins.
So it will be nice to have a possibility to configure component/services 
used by plugins and not just plugins.
This will also contribute to better flexibility as users could replace 
standard implementation of ManifestGenerator will their own
if they need to do something non standard.

Michal



----------------------------------------------------------------------
Portal z najlepsza wyszukiwarka! >>> http://link.interia.pl/f1861 


Mime
View raw message