short version:
I think I managed to extract exactly what we wanted:
https://github.com/hboutemy/maven-build-cache-extension-shallow-filtered
please review and confirm the result is ok
longer version: how was it done?
the first recipe I found is to drop old history:
git clone
+1
On the dev list should be no messages sent by robots.
czw., 23 gru 2021 o 08:19 Hervé BOUTEMY napisał(a):
> Hi,
>
> It seems that many Git repositories are configured to send issues
> notifications to dev@maven [1] instead of issues@maven [2] = the
> classical target of some Git
the usual target for scm used to be comm...@maven.apache.org?
As far as I can remember issues@ is used for Jira.
maybe if possible we could have only PR going to dev? (but no real strong
opinion on that).
I feel some pain sometimes due to duplicate notifications going to both
github and gitbox (or
>I feel some pain sometimes due to duplicate notifications going to both
github and gitbox (or maybe it's only my bad setup?)
Same here, there are a lot of duplicates...
чт, 23 дек. 2021 г. в 12:08, Olivier Lamy :
> the usual target for scm used to be comm...@maven.apache.org?
> As far as I can
michael-o merged pull request #280:
URL: https://github.com/apache/maven-site/pull/280
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail:
Ping, no one else has any opinion on this?
T
On Wed, Dec 15, 2021 at 9:26 AM Tamás Cservenák wrote:
> Howdy,
>
> I'd like to pitch a topic about maven-resolver and usage of Wagon in it.
> As IMHO, Wagon use in maven-resolver is far from optimal (is very
> suboptimal).
>
> Typical example is
+1
Enrico
Il giorno gio 23 dic 2021 alle ore 09:08 Slawomir Jaranowski <
s.jaranow...@gmail.com> ha scritto:
> +1
>
> On the dev list should be no messages sent by robots.
>
> czw., 23 gru 2021 o 08:19 Hervé BOUTEMY
> napisał(a):
>
> > Hi,
> >
> > It seems that many Git repositories are
Hi,
On 23.12.21 08:19, Hervé BOUTEMY wrote:
+1
From me.
Kind regards
Karl Heinz Marbaise
Hi,
It seems that many Git repositories are configured to send issues notifications
to dev@maven [1] instead of issues@maven [2] = the classical target of some Git
repositories and of classical Jira
Sorry I missed this interesting thread.
I completely agree with your analysis. In 2022 I don’t think anyone consume
its artifacts from another protocol than http(s) or file. It’s probably
another story for the publication and in this area wagon is still making
sense but for the resolver I don’t
dependabot[bot] opened a new pull request #56:
URL: https://github.com/apache/maven-artifact-transfer/pull/56
Bumps
[plexus-component-metadata](https://github.com/codehaus-plexus/plexus-containers)
from 2.1.0 to 2.1.1.
Release notes
Sourced from
dependabot[bot] opened a new pull request #77:
URL: https://github.com/apache/maven-doxia/pull/77
Bumps [xmlunit-matchers](https://github.com/xmlunit/xmlunit) from 2.7.0 to
2.8.4.
Release notes
Sourced from https://github.com/xmlunit/xmlunit/releases;>xmlunit-matchers's
11 matches
Mail list logo
