+1 from me. At my work we also can only access maven central for artefacts
Am 04.10.2024 um 13:40 schrieb Niels Basjes:
Hi,
Currently the full zip file of maven is released both via the download
servers as it is published in maven central.
-
https://dlcdn.apache.org/maven/maven-3/3.9.9/binaries
good idea, why not
this will be our first project doing full automated release staging from CI
https://github.com/apache/maven-mvnd/blob/master/.github/workflows/release.yaml
(= the technical reason why pushing to classical Apache staging repository has
not been done "as usual")
Regards,
Hervé
Ok,
This sounds like consensus to me.
Shall I create a jira issue ? Or will one of you do this?
Niels
On Sat, Oct 5, 2024 at 11:14 AM Hervé Boutemy wrote:
> good idea, why not
>
> this will be our first project doing full automated release staging from CI
>
> https://github.com/apache/maven-mv
Why not, but I’m not sure how to do that.
That was the primary reason why it has never reached central. I’d like to
avoid another manual step,m, so any idea welcomed !
Guillaume Nodet
Le sam. 5 oct. 2024 à 11:16, Hervé Boutemy a écrit :
> good idea, why not
>
> this
I created this issue (so not in Jira what I initially thought was the right
place)
https://github.com/apache/maven-mvnd/issues/1159
Niels
On Sat, Oct 5, 2024 at 1:58 PM Guillaume Nodet wrote:
> Why not, but I’m not sure how to do that.
> That was the primary reason why it has never reached cent
Haven't used it yet, but seems that JReleaser could do the trick:
https://jreleaser.org/guide/latest/examples/maven/maven-central.html
On Sat, Oct 5, 2024 at 1:58 PM Guillaume Nodet wrote:
> Why not, but I’m not sure how to do that.
> That was the primary reason why it has never reached central.
The page
https://search.maven.org/artifact/org.apache.maven.plugins/maven-site-plugin
Currently shows:
Source code
https://github.com/apache/maven-site-plugin/tree/${project.scm.tag}
Does Maven Central show a broken URL due to some wrong assumption about
variable substitution or a bug in a POM?
T
