Maven Developer Hangout - July 10th, 2014

gistfile1.txt

# Agenda

- Any topics anyone wants to discuss
- Robert 
  Getting rid of the horrible wiki link and give the mojo author an opportunity to write their own 
  error information. Igor's idea: looking at the two exceptions and the use of the compiler where it really is just
  an error from the tool only report the error from the tool and not a stack trace.
- A standard way to skip mojos/plugins and omit them in a standard way from the execution plan
- How to test all our plugins as we change Maven?
  - I have a JSR330 branch and it lit up the Maven ITs because I have all the deprecated code removed there 
  - How can we start testing our plugins against the latest version of Maven to start looking for deprecations?
  - A possible route of:
    - Release all the plugins now with a last version that is Java 1.6 and whatever version of Maven its on
    - Make a branch for all the plugins at this level and prepare all the plugins for the future
    - Bump all plugins up to Java 1.7 and a min/max version of Maven 3.x, with enforcer rules
    - Best way to build against min Maven 3.x while checking against max Maven 3.x?
- Simple POM 5.0.0 proposal update