Hi,
sorry I couldn't make it today, though I've listened to the livestream.
One extra remark regarding the checkstyle enforcements: when I mentioned
the pre-commit-hook my idea was *not* to let that apply checkstyle, but
that it doesn't accept a commit if it doesn't follow the convention. That
way you're not forced to first have a checkstyle-error free project, but
you can make increasing progress by starting to enforce it starting from
the moment this hook is installed.
I know this is tricky, because commits contain code snippets so I'm not
sure if checkstyle is capable to verify this.
thanks Manfred for taking the lead for this talk.
Robert
Op Thu, 24 Jul 2014 23:35:46 +0200 schreef Manfred Moser
<manf...@mosabuam.com>:
Hi all!
We had another interesting and productive developer hangout today.
The following topics were discussed and raised:
- new release of progressive-organization-pom available
https://github.com/simpligility/progressive-organization-pom
- new release of Android Maven Plugin 3.9.0-rc.3
https://code.google.com/p/maven-android-plugin/
- we talked about issues with Maven plugin testing tools and Maven
verifier based tests,
Igor has a new implementation of verified based testing in the works
that supports
testing with multiple Maven versions, running IT tests as part of normal
project
(without multi module setup and/or without install of plugin, instead
using
reactor/workspace resolution, works on command line and in M2e), Android
Maven plugin
will try to migrate to that as a solution to the required refactoring
see also https://github.com/jayway/maven-android-plugin/issues/303
- Herve mentioned that he is hoping to start enforcing checkstyle as
part of the
build from the parent pom, we discussed benefits of complete reformat
in one sweep
vs gradual migration/enforcement, Herve will send update with more
details to the list,
we agreed to move forward with some sort of enforcement, potentially
with a property to
turn it for so that projects can opt out even if they update to the new
parent release
with the enforcement
- we talked about a desire to have one checkout to easily work on lots
of Maven
related projects like svn/trunks has now and how we could do that in
git, the
android repo tool as well as some other git based approaches were
mentioned
but there is no current setup, some people dont see the need for this,
others
feel its very important, users will have to come up with something
Feel free to post follow ups with what you want to mention as well
manfred
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
