Hi,
unfortunately i couldn't make it and Manfred yes i'm enjoining a really
good sunset at north sea at the end of my vacation...but i took the
recorded one...
On 7/24/14 11:35 PM, Manfred Moser 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
You have talked about testing of plugins but neither Manfred nor Igor
haven't mentioned about maven-invoker-plugin ? which gives you some of
those things....no need to make a multi-module-build out of your build etc.
What do you think about that? Is maven-invoker-plugin not an option?
Should we stop working on maven-invoker-plugin? One of the draw back
might be time it takes...but it helps a lot about working with
integration tests...
If you were talking about maven verifier based i assume you are talking
about maven-verifier from the shared components ? Or do i miss a thing?
But what is interesting running integration tests within Eclipse...of
course with some drawbacks based on
What about maven-testing-harness ?
Maybe Igor can write something about this?
- 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
Can you give some more information about the repo tool where to find?
and may be a documentation exist? It would great to know and may be to
use it...
Is it this: https://source.android.com/source/developing.html ?
Feel free to post follow ups with what you want to mention as well
Kind regards
Karl-Heinz Marbaise
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
