I haven't opened it yet as I still have to separate out functionality,
and write up some info for the site report.  Already have the
integration test done.

I just quit my job and have two weeks off until I start my next, last
day, yay!  So really good news for you!

I expect to have this split out and the site info done this week.

If you can't wait I released it for my (old) companies use on my
website ( http://www.e-hoffman.org/released/repo )
Sites are under repo as well

Not heavily documented but, if you include that location and add this
to your pom, you get the goodness.

     <plugin>
        <groupId>org.apache.maven.plugins</groupId>
        <artifactId>maven-enforcer-plugin</artifactId>
        <version>1.0-beta-1</version>
        <dependencies>
          <dependency>
            <groupId>org.apache.maven.enforcer.rules</groupId>
            <artifactId>maven-enforce-releasability</artifactId>
            <version>1.0.0</version>
          </dependency>
        </dependencies>
        <executions>
          <execution>
            <id>enforce</id>
            <configuration>
              <rules>
                <myCustomRule
implementation="org.apache.maven.enforcer.rule.DependencyRule">

<enforceNoSnapshotsOnRelease>false</enforceNoSnapshotsOnRelease>

<enforceDependencyConvergence>true</enforceDependencyConvergence>
                </myCustomRule>
              </rules>
            </configuration>
            <goals>
              <goal>enforce</goal>
            </goals>
          </execution>
        </executions>
      </plugin>


Or you can wait on me, and then a dev with commit rights to get in to
maven proper.

Cheers,

Rex

On Wed, Sep 8, 2010 at 4:26 AM, Mark Hobson <[email protected]> wrote:
> Were any issues raised to track the progress of these new rules?  I'm
> particularly interested in this one:
>
>> 2) Maven should have the option of forcing developers to ensure
>> dependencies converge rather than relying on the "closest to the top"
>> rule it uses by default.  In large projects this can be problematic.
>
> Cheers,
>
> Mark
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to