On 3 September 2010 01:38, Barrie Treloar <baerr...@gmail.com> wrote:
> I didn't want to hijack the other thread with my questions after > reading https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html > > Caching of Artifact Resolution Errors > > Marker files are great! Is there any documentation on what they > are? The maven-eclipse-plugin has the hack I added with marker files. > Standardizing on the marker file will be the first thing I do once I > know what do use. > > Automatic Plugin Version Resolution > > Now that plugin versions are expected to be locked down in the pom > has the documentation been updated to describe how to manage the > version upgrades? > For example there was a question on the list a while ago about a > tool to check whether new versions of dependencies were available and > to provide a report. > mvn versions:display-dependency-updates > Something like that for plugins would also be needed. The benefit > mvn versions:display-plugin-updates > of not locking them down was I got the latest releases without doing > anything. > The downside was the build was not reproducible and if the new > plugin had bugs I would need to lock down the plugin to the previous > working version. > Some guidance on how to manage this lifecyle would be appreciated by > less experienced build managers. > > Plugin Repositories > "Maven 3 aims at supporting a stricter > separation between the compile/runtime/test dependencies" > > Has the > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > > Dependency Scope been modified to define "test compile" and "test > runtime"? > Without something like this dependency:analyze has false positives > with test scopes and a lot of the benefit of checking is lost. > Is this possible and on the feature list? > > Cheers > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org > For additional commands, e-mail: dev-h...@maven.apache.org > >
