Hi,
I still consider Maven as a language independent build management tool.
In case of the enforceBytecodeVersion I think we should add an API so it
can be implemented for other packaging types as well.
Shouldn't be too hard to do so, just needs to be done.
@Stephen, which other rules do you have in mind? BanCircularDependencies?
BanDuplicateClasses?
regards,
Robert
Op Mon, 29 Sep 2014 10:36:55 +0200 schreef Stephen Connolly
<stephen.alan.conno...@gmail.com>:
Some of those look ready to move over to the standard enforcer rules:
e.g.
enforce bytecode version for one.
WDYT?
On 26 September 2014 21:31, Baptiste Mathus <bapti...@codehaus.org>
wrote:
Hi,
The Mojo team is pleased to announce the release of the Extra Enforcer
Rules version 1.0-beta-2.
Apache's Maven Enforcer Plugin is used to apply and enforce rules on
your
Maven projects.
The Enforcer plugin ships with a set of standard rules
The Mojo project hosts this project to provide extra rules which are not
part of the standard rule set.
http://mojo.codehaus.org/extra-enforcer-rules/
To get this update, simply specify the version in your project's plugin
configuration:
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.3.1</version>
<dependencies>
<dependency>
<groupId>org.codehaus.mojo</groupId>
<artifactId>extra-enforcer-rules</artifactId>
<version>1.0-beta-3</version>
</dependency>
</dependencies>
</plugin>
Release Notes :
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11062&version=19724
Bug
- [MOJO-2037] - java.lang.AssertionError: The file xyz.jar is corrupt
or invalid
Improvement
- [MOJO-1988] - Make excluding test dependencies configurable
- [MOJO-2008] - Give version of the bytecode found in a bad
dependency
Enjoy,
The Mojo team.
-- Baptiste
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email