Hi,
i just want to know on what basis releases will be created...
Currently i would suggest to create a Release 1.3.2 of the
maven-enforcer-plugin...
In Jira the list
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11530version=19935
for 1.3.2 contains a number of bug fixes...
just a thought about going forward (maybe you do that already but thought I'd
mention it):
when you create an issue on
https://jira.codehaus.org/browse/MNG
there are 2 JIRA fields Testcase included and Patch Submitted.
a) this should help with filtering for quality bug reports in JIRA and
b)
Well the biggest blocker for cutting releases is getting your binding
votes...
My policy is cut releases until the PMC starts complaining that you are
cutting too many releases... ;-)
I haven't seen any of us complain about releases being too frequent
*ever*...
If you think it is ready for a
Thanks, I think it's the only sane way to try and help people.
On Jan 23, 2014, at 5:43 PM, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
Jason,
the wiki page is a really good writeup and I like the strategy to force
reporters to create a simple project which will reproduce their issue.
Karl Heinz,
you might hit MENFORCER-161[1], unless Hervé did a fix regarding the
scm-publish on this project.
Robert
[1] https://jira.codehaus.org/browse/MENFORCER-161
Op Fri, 24 Jan 2014 10:22:59 +0100 schreef Karl Heinz Marbaise
khmarba...@gmx.de:
Hi,
i just want to know on what
Maven 3.1.1 official, and all the plugin dependencies are 3.,1.1 too.
I'll trying switching to the annotations. Javadoc annotations were just for
conformity with the rest of the project.
If that doesn't work, I'll put together a cut down example.
Thanks.
William
On Thu, Jan 23, 2014 at 9:43
Karl Heinz,
one thing: MENFORCER-159 is a duplicate of MENFORCER-160 (or better it
is an alternative approach), so probably should not be mentioned.
Regards
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/ (http://osrc.dfm.io/mfriedenhagen)
Karl Heinz,
another thing: because MENFORCER-160 introduces a new interface which
is implemented by AbstractStandardEnforcerRule maybe version 1.4 would
be a better version number than 1.3.2, as it introduces a new
functionality.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
Indeed, I couldn't remember the reason for 1.4 (nor with a quick scan
through Jira), but this was it.
Robert
Op Fri, 24 Jan 2014 22:30:38 +0100 schreef Mirko Friedenhagen
mfriedenha...@gmail.com:
Karl Heinz,
another thing: because MENFORCER-160 introduces a new interface which
is
In the Android Maven Plugin we use the maven-plugin-api, which has a
transitive dependency to guava 10.0.1. Another dependency (android tools
common) pulls in 13.0.1 and things are fine so far.
However when I now upgrade to the latest version of the android tools I
get 15.0. Problem is that
Hi Robert,
Hi Mirko,
Indeed, I couldn't remember the reason for 1.4 (nor with a quick scan
through Jira), but this was it.
Thanks for the hint...
Ok. i will move the issues to 1.4 ...so new functionality is definitely
a good reason for 1.4 instead of 1.3.2 ...
So MENFORCER-160 is
This problem is specific to maven-plugin-testing-harness. You can use
any version of Guava at runtime, but test classpath is flat so you need
to use single Guava version that is compatible with all components.
Unfortunately, I don't know how to fix the problem, at least not until
Maven core is
On 24 Jan 2014, at 23:49, Igor Fedorenko i...@ifedorenko.com wrote:
This problem is specific to maven-plugin-testing-harness. You can use
any version of Guava at runtime, but test classpath is flat so you need
to use single Guava version that is compatible with all components.
Hello,
I am afraid the only documentation is in the ticket, right now. I could try
to find a place this evening and submit a patch.
Regards
Mirko
--
Sent from my mobile
On Jan 24, 2014 11:31 PM, Karl Heinz Marbaise khmarba...@gmx.de wrote:
Hi Robert,
Hi Mirko,
Indeed, I couldn't remember
14 matches
Mail list logo
