I have the RAT configuration in the indexer already, and could put it in the release profile. Another alternative is to put it in maven parent itself. There's two drawbacks: - if it's in the parent, several next releases would need to update their excludes - it only fails at the release:prepare stage, so things might be caught at the last minute (unless we have that profile on in CI).
Any thoughts? - Brett On 13/01/2011, at 12:48 AM, [email protected] wrote: > Author: bentmann > Date: Wed Jan 12 13:48:28 2011 > New Revision: 1058139 > > URL: http://svn.apache.org/viewvc?rev=1058139&view=rev > Log: > o Added license headers > > Modified: > > maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/context/ContextMemberProvider.java > > maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/context/MergedIndexingContext.java > > maven/indexer/trunk/indexer-core/src/main/java/org/apache/maven/index/context/StaticContextMemberProvider.java > > maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/ConcurrentUseTest.java > > maven/indexer/trunk/indexer-core/src/test/java/org/apache/maven/index/Nexus1911IncrementalMergedCtxTest.java -- Brett Porter [email protected] http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
