We're getting closer:
1. Done
2. Skipped, took too long
3. Done
4. Done
So we're at #5 Check status on git-wip to gitbox migration for maven-core
and maven-integration tests
I've done my part. So Stephen, now it's up to you :)
thanks,
Robert
On Sat, 27 Jan 2018 18:52:17 +0100, Stephen Conn
Hi Sylwester,
That's what I checked yesterday (or today very very early to be more precise
:) ) before doing the release
thanks
Hervé
Le vendredi 2 février 2018, 08:32:32 CET Sylwester Lachiewicz a écrit :
> hi Herve,
>
> i’ve verifiedy checkstyle plugin configuration and you can just update
hi Herve,
i’ve verifiedy checkstyle plugin configuration and you can just update
version number.
All required changes to configuration was already commited to 31-SNAPSHOT
with a fix for https://issues.apache.org/jira/browse/MPOM-162
Sylwester
On Wed, 31 Jan 2018 at 07:54, Hervé BOUTEMY wrote:
done
Regards,
Hervé
Le mercredi 31 janvier 2018, 21:11:25 CET Robert Scholte a écrit :
> Agree, Twitter is sufficient
>
> On Wed, 31 Jan 2018 19:03:21 +0100, Manfred Moser
>
> wrote:
> > As a team we are not actively maintaining a presence on Facebook or G+
> > as far as I know so I vote for
Agree, Twitter is sufficient
On Wed, 31 Jan 2018 19:03:21 +0100, Manfred Moser
wrote:
As a team we are not actively maintaining a presence on Facebook or G+
as far as I know so I vote for removing them...
Manfred
Hervé BOUTEMY wrote on 2018-01-31 09:40:
I must confess that I don't und
As a team we are not actively maintaining a presence on Facebook or G+ as far
as I know so I vote for removing them...
Manfred
Hervé BOUTEMY wrote on 2018-01-31 09:40:
> I must confess that I don't understand G+ nor Facebook buttons result
>
> any reason not to remove them?
>
> Regards,
>
>
Hi,
On Wed, Jan 31, 2018 at 7:40 PM, Hervé BOUTEMY wrote:
> I must confess that I don't understand G+ nor Facebook buttons result
Facebook might show in your news feed that you've liked the link
(https://maven.apache.org/pom/maven). Given the fact that is not the
page where the button is locat
I must confess that I don't understand G+ nor Facebook buttons result
any reason not to remove them?
Regards,
Hervé
Le mercredi 31 janvier 2018, 10:07:06 CET Stephen Connolly a écrit :
> I like the twitter one, it's not too obtrusive. The facebook one looks
> "meh" and the G+ is similar, i.e. I
I like the twitter one, it's not too obtrusive. The facebook one looks
"meh" and the G+ is similar, i.e. I do not know what the call to action is
(what am I liking)... but "Follow @ASFMavenProject" is clear (once you see
it)
Perhaps that is an expected thing for the facebook and G+ networks and
ex
thank you Sylwester
I'm busy on many things in parallel (preparing Maven meeting at FOSDEM):
having a PR to review and merge would help me a lot, please
BTW: if someone will at FOSDEM (Brussels) this WE and wants to meet us,
discuss ideas that are not so easy to discuss from scratch on a mailing
Hi Heve,
for checkstyle plugin you must apply also configuration change - this was
described in release note for the plugin.
I’ve tested this change for maven build and works good.
Sylwester
On Wed, 31 Jan 2018 at 08:06, Hervé BOUTEMY wrote:
> thank you Andreas: this was exactly the type of fe
thank you Andreas: this was exactly the type of feedback I needed
upgrade done: now need to have a look at maven-checkstyle-plugin
I also added Twitter and Facebook buttons to the G+ as test: you can see the
result on the LATEST page [1]
feedback welcome: keep or remove some from parent POM?
Re
Since yesterday, m-pmd-p 3.9.0 is available - however, this includes a
major upgrade of PMD to 6.0.1. While all custom rulesets keep working,
the users will see a couple of deprecation warnings (the rules have been
reorganized).
I'd recommend to upgrade m-pmd-p from 3.7 -> 3.8 only.
Regards,
And
there are 2 additional plugins updates available:
[INFO] maven-checkstyle-plugin . 2.17 -> 3.0.0
[INFO] maven-pmd-plugin ... 3.7 -> 3.8
do we upgrade or not? and is this only changing the version, or does it
require more config (
one little additional opportunity:
I'll launch maven-parent POM 31 soon, so perhaps update parents before
releases. If not, please tell me and I'll upgrade Fuido skin to version 1.7
with the edit button
BTW, if anybody wants to see something in Maven parent POM 31, it's time to do
it
Regards,
Sounds good.
Robert Scholte wrote on 2018-01-27 11:51:
> Sure, I can release a 1.1.1 for the ant-tasks as well.
>
> MRESOLVER-38 is a critical/blocking issue, you probably don't want to use
> it, so my suggestions is to forget the 1.1.0 ant-tasks
>
> thanks,
> Robert
>
> On Sat, 27 Jan 2018
Sure, I can release a 1.1.1 for the ant-tasks as well.
MRESOLVER-38 is a critical/blocking issue, you probably don't want to use
it, so my suggestions is to forget the 1.1.0 ant-tasks
thanks,
Robert
On Sat, 27 Jan 2018 19:56:49 +0100, Manfred Moser
wrote:
Awesome. On the resolver releas
Awesome. On the resolver release can we make sure we release the ant task as
well (maybe even the current version first since that has never been released
yet..)
Manfred
Stephen Connolly wrote on 2018-01-27 09:52:
> Robert and I discussed on IRC...
>
> Our plan is as follows:
>
> 1. Fix http
Robert and I discussed on IRC...
Our plan is as follows:
1. Fix https://issues.apache.org/jira/browse/MRESOLVER-38
2. Check status on git-wip to gitbox migration, if maven-resolver will be
migrated during the vote, we will hold off releasing until after the
migration (so that the release artifact
19 matches
Mail list logo
