Awesome! Thank you very much for the summary.
On Fri, Aug 1, 2014 at 7:56 AM, Jason van Zyl ja...@takari.io wrote:
Here's a short summary of yesterdays discussion:
---
Manfred Moser
1) Alternative verifier use in maven-android-plugin for testing. Igor
created an alternative verifier for use inside of M2E for integration
testing that allows an integration test to be run from within Eclipse
without having to install the plugin. The alternative verifier also allows
multiple invocations with different versions of Maven. So if you want to
test a plugin against 3.1.1 and 3.2.1, for example, this would be possible.
This code will be released in the next few weeks. Manfred is attempting to
remove the use of the maven-testing-harness in the maven-android-plugin
with this new technique for integration testing.
2) New repository populator that takes a set of dependency coordinates,
calculates the transitive hull and publishes them to a remote repository.
This is a tool that uses Aether. Not sure what Manfreds plans are for
releasing this or if it's already available. Manfred can speak to this as
he wishes.
Hervé Boutemy
1) Continued work on the Checkstyle setup for Maven projects. A nice way
is being developed that doesn't force conformance to all rules at once.
Rules can be selectively turned off so that adherence to the rules can be
met over time without a huge disruption. Hervé is continuing to test the
setup with various Maven projects and the current plan is to release this
new setup in about a month.
Mark Derricutt
1) Tiles plugin work is progressing and a release is planned shortly after
some repository cleanup work. The Tiles plugin is a prototype version of a
type of mixin for Maven. Some work needs to be done to sort out the proper
merging of the models, and there may be other things Mark wants to explain
but we'll likely see something soon.
Jason van Zyl
1) Work on the JSR330 branch has 4 ITs failing, but this is due to some
movement of deprecated code that I will have to revert. While doing the
JSR330 work some investigation was done on removing maven-compat and there
are some issues that need to be resolved. Trying to fully remove Plexus
with JSR330 and get rid of maven-compat is an attempt at something that
will resemble Maven 4. To make this work quite a bit of refactoring will be
required and staged releases of plugins in order not to break users. A
proposal will be sent next week on how we might proceed, but essentially
involves finding efficient ways to find use of deprecated code and provide
alternatives to the deprecated code that we are willing to support forever
more.
Thanks,
Jason
--
Jason van Zyl
Founder, Apache Maven
http://twitter.com/jvanzyl
http://twitter.com/takari_io
-
the course of true love never did run smooth ...
-- Shakespeare