[jboss-dev] pom.xml housekeeping

[Max Rydahl Andersen]

On Wed, 23 Apr 2008 12:08:51 +0200, Carlo de Wolf <cdewolf at redhat.com> wrote:

> Sacha Labourey wrote:
>> but shouldn't we reconsider this now that we have cleaned the build?
>> Furthermore, we could "externalize" this information in an external
>> project (as describe in the post), but I guess projects that are really
>> allergic to this approach could still rely on their "custom" dependency
>> set (and take the risk of being publicly bashed in case they don't
>> maintain their version up-to-date).
>>
>> Is it possible to write a scripts that tests these things (i.e. gather
>> all dependency information for the complete build, flatten that
>> information and look for multiple "PROJECT-NAME_X_Y_Z" tag that have the
>> same PROJECT_NAME part but not the same X_Y_Z part? could this be part
>> of the build process as a testsuite or anyhting like that?
>
> That's the job Maven should really do for us, but doesn't. See the 'Why
> Maven sucks (part 1)' thread.

did you look at the enforcer plugin which I referenced in that thread ?

/max