+1 to strict with an option to override to lax in the config closure. --b ___________________________ Brian M. Carr Senior Software Engineer Identity Management, ITS Applications University of Texas at Austin V: 512-232-6419 F: 512-471-5746 [email protected]
On Nov 10, 2011, at 1:42 PM, Daz DeBoer wrote: > > > On 10 November 2011 12:13, Uwe Bessle <[email protected]> wrote: > * Many companies will have standards, but not all. But on every place there > is at least one exception from the rule. > * If you migrate from one world without repository manager and without > metadata descriptor to a new world using both, than there will be a longer > time, where you have both things in parallel. Again a mixed scenario > > just my 0.02 cent > > Uwe > > PS: we have a mixed scenario with 10% ivy.xml 20% pom.xml and 70% no metadata > at all. > > Are you talking about a single repository (ie with a single root URL)? I'm > not surprised that many companies have a variety of repositories with > different meta-data formats. > > The question is that if we have a defined Maven repository, should we > magically work if a pom file is missing (or maybe misnamed) for a module? > I'm also talking about what the default behaviour should be: should we > default to being lax and slower, or strict and faster and tell people to > switch on a flag for "lax mode"? > > Thanks for the input. It's good to get feedback from a variety of > organisations. > -- > Darrell (Daz) DeBoer > Principal Engineer, Gradleware > http://www.gradleware.com >
smime.p7s
Description: S/MIME cryptographic signature
