;d have a happier release plugin if it had a tailored
>> abstraction. Maybe not.
>>
>> --benson
>>
>>
>>
>>
>>
>>
>> On Sat, Jun 27, 2015 at 10:14 AM, Tibor Digana
>> wrote:
>>
>> > @Benson
>> >
>> > Ex
t;
> > Excellent!
> >
> > Since you have good inside of this problem you should post a Vote with
> this
> > list of activities and I hope that others will extend it.
> >
> > As you and Robert Scholte described, the situation around
> > maven-release-plu
cholte described, the situation around
> maven-release-plugin and SCM artifacts is pathetic. I hope Jason will bring
> some inspiration to make us all more optimistic.
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/number-of-bugs-in-maven
2015-06-27 14:40 GMT+02:00 robert.patr...@oracle.com <
robert.patr...@oracle.com>:
>
> The second time, I tried to interact around someone else's problem with
> mvnDebug.cmd. No one ever responded.
>
That's not really true - people did respond, it's just that no one stood up
and put your suggest
inspiration to make us all more optimistic.
--
View this message in context:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838800.html
Sent from the Maven Developers mailing list archive at Nabble.com
Hi Robert,
On 6/27/15 2:40 PM, robert.patr...@oracle.com wrote:
I have only tried to interact a few times myself (others in my team have tried
as well).
> The first time, my team and I get a patch we submitted
>to enhance the wagon-http for SSO-protected repositories adopted
thanks to Olivie
to cover them all. Otherwise we should
> just look for them.
>
> Agree. So why not to introduce more committers.
> This still sounds to me like we do not have environment to cover the fix in
> tests on all SCM we support.
>
>
>
> --
> View this message in context:
>
I have only tried to interact a few times myself (others in my team have tried
as well). The first time, my team and I get a patch we submitted to enhance
the wagon-http for SSO-protected repositories adopted thanks to Olivier Lamy.
The second time, I tried to interact around someone else's pro
hat JRE 8 already
solved known bugs reported against in JRE7.
Maybe the same should happen with Maven, who knows. :-)
--
View this message in context:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838755.html
Sent from the Maven Developers mailing list arch
Hi Robert,
On 6/27/15 12:51 PM, robert.patr...@oracle.com wrote:
Sorry for butting in but as someone who is a staunch supporter of
> Maven within my company and its user community,
> I have to agree that the difficulty in engaging
> the Maven developers to even discuss issues
> is too high.
F
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838743.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For addi
in context:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838731.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr
proved good fix.
Otherwise I would revert the fix from HEAD.
Sounds this works, hm?
--
View this message in context:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838719.html
Sent from the Maven Developers
@rfscholte
If the plugin needs redesign, I guess M3 is the rightest milestone for that.
Everybody should accept that major version comes with breaking something but
fixing a lot as well.
--
View this message in context:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin
; Sounds this works, hm?
>
>
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838719.html
> Sent from the Maven Developers mailing list archive at Nabble.com.
>
>
ng and you know that the big fix has a side effect.
--
View this message in context:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838723.html
Sent from the Maven Developers mailing list archive at Nabb
text:
http://maven.40175.n5.nabble.com/number-of-bugs-in-maven-release-plugin-tp5838696p5838719.html
Sent from the Maven Developers mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For
Some of the issues are mine. I'm pretty sure that at some point I realised
that to get it working properly for my use case would require forking it to
a privately released version. I guess now that it's mostly or all in git,
that's feasible. The conflicting requirements across SCMs, the highly
vari
It was even worse.
When I joined this team I started working on this plugin and managed to
close half of them ( let's say from 300 back to 150 issues).
Right now there's a situation where new issues are often easy to reproduce.
The older ones are often harder to reproduce or are already fixed.
Do you know what's wrong with Jira on maven-release-plugin MRELEASE?
It's growing nearly to 200 open bugs. It looks like the community use to
fix 5 in each release. Maybe the community should start closing irrelevant
bugs which better helps concentrating on more relevant bugs.
We started this stra
20 matches
Mail list logo
