I believe the original hangouts were more focused on the 4.0 POM as that
was the primary topic of discussion going on in dev@ - plotting the
course forward for Maven 4.x and beyond.
But as with everything - once you open the forum for discussion, other
things can, and invariably will come in based on who is involved in said
discussion.
Mark
On 25 Jul 2014, at 15:54, jieryn wrote:
Agree! I thought I saw Jason doing these, but recently it seems anyone
can say it is a Maven Developer Hangout.
I am confused about this most recent update.
On Thu, Jul 24, 2014 at 11:50 PM, Paul Benedict <pbened...@apache.org>
wrote:
Question about these hangouts... are they about anything related to
Maven?
I thought these were to focus on 4.0 enhancements. Perhaps I
misunderstood;
it looks this week's topics were mostly private company
infrastructure
stuff.
Cheers,
Paul
On Thu, Jul 24, 2014 at 4:35 PM, Manfred Moser <manf...@mosabuam.com>
wrote:
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
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
