Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (nike.apache.org: domain of nigel.magnay@gmail.com
 designates 209.85.216.43 as permitted sender)
MIME-Version: 1.0
In-Reply-To: 
 <CANWgJS5zjeNQdsJg8j-_3dc+AYQfRePJ+RDqZNbzTLYbk1xdAQ@mail.gmail.com>
References: 
 <CA+nPnMx_311OdaXHXmZLYne9N+N0c-kwFp3Z3e_h_YVO5WKQ+g@mail.gmail.com>
	<25664F3F-7531-4E73-92D9-E568C04E1C6C@tesla.io>
	<CA+nPnMx7tS6UKnWLD-7DrZSsKFnHgy63mH6BodC9Hfhefqu0bQ@mail.gmail.com>
	<2F666C4F-4483-4627-9CA1-D2794977FB18@tesla.io>
	<CA+nPnMwV4V5Sg5WdByB1bNFL-XdpUykxiXPfkC2g-Q5ighbsBQ@mail.gmail.com>
	<CADVp3v-U+7K4zTcV1gM+mDJi7yet90fKAEEO+CNErV+ap1_X5Q@mail.gmail.com>
	<530D1FB4.1050407@j-hohwiller.de>
	<CA+nPnMzrbrj68EeqGJtowig3_+sbVkCaRq+fFpNfL00qHSTzQA@mail.gmail.com>
	<op.xbwphno1kdkhrr@robertscholte>
	<CANWgJS6-buOer9vver3tV_d5yyetnPsBbuwiHK4jqx8JXJCwNw@mail.gmail.com>
	<CA+nPnMzcY8X4CRX+_trcU6fCVHjw90uaTfLqQFsQfHVyT56AcA@mail.gmail.com>
	<CANWgJS7PF4TxxKoWpvcz0KRFRSEE7rO=VuR2Nf1PE_CYSaVCwA@mail.gmail.com>
	<CA+nPnMxbJ2YBnU4uFVxP8ayF3+H9MLjJwO4jku38dSWhfr36CQ@mail.gmail.com>
	<CAB63Y-c=j8tCHQD0amemQQoSaNf5CoTtR9BPfXZLqi1LwWvNoA@mail.gmail.com>
	<703E4D1F-844E-4A82-870B-FC6414F015FA@fortysix.ch>
	<CANWgJS5zjeNQdsJg8j-_3dc+AYQfRePJ+RDqZNbzTLYbk1xdAQ@mail.gmail.com>
Date: Tue, 25 Mar 2014 10:41:17 +0000
Message-ID: 
 <CAPYP83QzzykwhsJNxq_MCpRght4Zi=2d1pPo1+f+VPwWxYCpjg@mail.gmail.com>
Subject: Re: Model Version 5.0.0
From: Nigel Magnay <nigel.magnay@gmail.com>
To: Maven Developers List <dev@maven.apache.org>
Content-Type: multipart/alternative; boundary=001a1137087ceec83104f56bfd25

--001a1137087ceec83104f56bfd25
Content-Type: text/plain; charset=ISO-8859-1

On Tue, Mar 25, 2014 at 8:55 AM, Baptiste Mathus <bmathus@batmat.net> wrote:

> FWIW, I'm aware it's easily feasible to add that checksum validation in a
> plugin, but you'll still have to repeat the coordinates.
> And that very thing was my point: I don't think having to repeat those
> coordinates to add metadata is great.
>
> Not even saying this *must* go in modelVersion 5, I just wanted that debate
> to happen at least for future reference if people wonder why maven pom
> can't store that dependency metadata (DRY'ly alongside its data, I mean).
>
>
There's all sorts of other per-dependency information that would be
useful, for example - flex applications needing to store RSL deployment
paths and policy file urls.

The 'maven way' seems to be sentenced to perennially repeat yourself, and
live with the fact your plugin config and your dependency list can drift
out of sync. Or to suffer some kind of excuse of 'just specify the
dependencies you want to apply this metadata to with some kind of regular
expression (!)'.

XML even has a well-understood extension mechanism for this kind of thing.


...
<dependency security:sha1="1234567890abcdef" >
  <groupId>com.woo</groupId>
  <artifactId>yay</artifactId>
  <version>1.0</version>
  <flex:rslInfo>
      <flex:deployment-path>/blah/blah</flex:deployment-path>
      <flex:policy-file>/woo/policy.xml</flex:policy-file>
  </flex:rslInfo>
</dependency>

....
<plugins>
  <plugin>
     /// some plugin that enforces security:sha1
.... etc etc etc


If your tooling doesn't understand namespaced nodes, it's trivial to strip
them.

--001a1137087ceec83104f56bfd25--