You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Mickael Istria <mi...@redhat.com> on 2019/05/09 12:55:35 UTC
Latest snapshot build (archive, not Maven artifact)
Hi all,
I'd like to set up for Tycho an automated build that runs it's master
against latest Maven snapshots, so we could more immediately spot
incompatibility like MNG-6642.
This should be quite easy to set up as a CI job.
However, what URL can I use to get access to the current snapshot of Maven
delivery?
Thanks in advance,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
Concretely, m2e can now pretty easily test against Maven snapshot:
https://git.eclipse.org/r/142991 . This should allow m2e to detect and
report Maven issues sooner, and to adopt newer Maven shortly after release
as we can span integration effort all along the development phase instead
of starting it after the release.
It's really a kind of revolution for m2e and Maven collaboration!
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
I think an infra that wants to prevent adopters for giving feedback on
snapshots is harmful for an open-source project. Are alternatives like
Sonatype OSSRH considered for replacement?
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Olivier Lamy <ol...@apache.org>.
not sure as infra wants to avoid too much usage of r.a.o
so we will avoid noise....
On Wed, 29 May 2019 at 17:00, Mickael Istria <mi...@redhat.com> wrote:
> Thanks a lot!
> I think it would be worth a dedicated announce post on the mailing-list or
> other community channels (blog, twitter...).
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
Thanks a lot!
I think it would be worth a dedicated announce post on the mailing-list or
other community channels (blog, twitter...).
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Olivier Lamy <ol...@apache.org>.
Thanks!
merged with a small changes and everything working fine now (
https://repository.apache.org/content/repositories/snapshots/org/apache/maven/maven-core/3.6.2-SNAPSHOT/
)
enjoy your fresh snapshots of Maven :)
cheers
Olivier
On Tue, 28 May 2019 at 23:13, Mickael Istria <mi...@redhat.com> wrote:
> Ok, here is my proposal: https://github.com/apache/maven/pull/250
>
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
Ok, here is my proposal: https://github.com/apache/maven/pull/250
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Olivier Lamy <ol...@apache.org>.
On Tue, 28 May 2019 at 15:27, Mickael Istria <mi...@redhat.com> wrote:
> Why is the CI stuff in a dedicated repo and not on the main repo? Could we
> try to change it? That would make Maven more "normal" and more accessible
> in term of contribution.
> I found https://github.com/apache/maven/blob/master/Jenkinsfile in the
> main
> repo. What is the purprose of this file vs the repo you linked?
>
correct it's the file to modify for maven core build
the other one concern plugins/shared library
> Also, I see https://github.com/apache/maven-jenkins-lib/pull/1/files was
> merged a year ago and then commented out
>
> https://github.com/apache/maven-jenkins-lib/commit/317a0e9eff8b1d793141291a4b335bf9b478ccd6
> . Does anyone know what failure was happening? Was it some missing
> credentials in the settings.xml ? Unfortunately, I do not have enough
> knowledge about Apache infra to help if the issue is credentials.
>
good question and I don't remember exactly :)
make a pr for maven core and I can have a look as I still have access to
ASF Jenkins infra.
cheers
Olivier
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
Why is the CI stuff in a dedicated repo and not on the main repo? Could we
try to change it? That would make Maven more "normal" and more accessible
in term of contribution.
I found https://github.com/apache/maven/blob/master/Jenkinsfile in the main
repo. What is the purprose of this file vs the repo you linked?
Also, I see https://github.com/apache/maven-jenkins-lib/pull/1/files was
merged a year ago and then commented out
https://github.com/apache/maven-jenkins-lib/commit/317a0e9eff8b1d793141291a4b335bf9b478ccd6
. Does anyone know what failure was happening? Was it some missing
credentials in the settings.xml ? Unfortunately, I do not have enough
knowledge about Apache infra to help if the issue is credentials.
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Hervé BOUTEMY <he...@free.fr>.
PR welcome
the code is at https://github.com/apache/maven-jenkins-lib
Regards,
Hervé
Le lundi 27 mai 2019, 11:40:00 CEST Mickael Istria a écrit :
> Up!
> What's blocking for publication of snapshots from master to some snapshot
> repo? I'd gladly try to help.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
Up!
What's blocking for publication of snapshots from master to some snapshot
repo? I'd gladly try to help.
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Enrico Olivelli <eo...@gmail.com>.
Il dom 12 mag 2019, 23:01 Olivier Lamy <ol...@apache.org> ha scritto:
> +1
> definitely agree on that let's make it simple....
> simple deploy of one build with java8 and voila.
> it's snapshot and NOT a release... so we do not have to jump on every bugs
> immediately.
>
Yes
+1
Enrico
It will be already a great forward to have quick feedback from maven
> consumers....
>
>
>
>
> On Mon, 13 May 2019 at 02:43, Mickael Istria <mi...@redhat.com> wrote:
>
> > IMO, if some patch managed to get to master, it's worth being released,
> > even if IT test fail.
> > So I would make the first step being a `mvn deploy` of what[s in master,
> > before running other tests.
> > I think this would be much simpler, allow community to test some "master"
> > snapshot even if it's bugged (so community can help in resolving), and
> > would cover all use-cases I have about snapshot. And -to put it another
> > way- making complex effort to run IT tests on all OS before publishing a
> > snapshot is over-engineering.
> >
>
>
> --
> Olivier Lamy
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Olivier Lamy <ol...@apache.org>.
+1
definitely agree on that let's make it simple....
simple deploy of one build with java8 and voila.
it's snapshot and NOT a release... so we do not have to jump on every bugs
immediately.
It will be already a great forward to have quick feedback from maven
consumers....
On Mon, 13 May 2019 at 02:43, Mickael Istria <mi...@redhat.com> wrote:
> IMO, if some patch managed to get to master, it's worth being released,
> even if IT test fail.
> So I would make the first step being a `mvn deploy` of what[s in master,
> before running other tests.
> I think this would be much simpler, allow community to test some "master"
> snapshot even if it's bugged (so community can help in resolving), and
> would cover all use-cases I have about snapshot. And -to put it another
> way- making complex effort to run IT tests on all OS before publishing a
> snapshot is over-engineering.
>
--
Olivier Lamy
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
IMO, if some patch managed to get to master, it's worth being released,
even if IT test fail.
So I would make the first step being a `mvn deploy` of what[s in master,
before running other tests.
I think this would be much simpler, allow community to test some "master"
snapshot even if it's bugged (so community can help in resolving), and
would cover all use-cases I have about snapshot. And -to put it another
way- making complex effort to run IT tests on all OS before publishing a
snapshot is over-engineering.
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Amine TAYEB CHERIF <ac...@hotmail.com>.
Hello!
The Jenkins library revision can be specified in the Jenkinsfile. For exemple, we can use a specific version of ‘my-shared-library’ with tag 1.0 by putting the following line at the beginning of the Jenkinsfile:
@Library('my-shared-library@1.0') _
Regards,
Amine TAYEB CHERIF
Le 12 mai 2019 à 08:02, Adrien Lecharpentier <ad...@gmail.com>> a écrit :
You can update the librairies as much as you want, without the need to
restart the instance. The shared libraries are cloned when the build
starts.
The fear I had during the hackergarten is more about the scope of the
change. Because the shared library is implicitly loaded, it means we cannot
specify a revision to use on one particular job. So, to test the library in
a real life environment, the changes etc needs to hit the master branche.
But as soon as this is happening, all jobs we be using it. Which means, if
what we have done has the smallest issue, it can take tremendous
proportions..
Le dim. 12 mai 2019 à 07:56, Hervé BOUTEMY <he...@free.fr>> a écrit :
notice 2:
one issue we had when working on such not so trivial Jenkins library
updates
is: how to test locally before updating the production server,
particularly
when the lib is shared then updates cannot be done without server restart?
this one probably deserves some explanations/documentation on our site,
since
we have ITs for every single Maven component/plugin but nothing about this
Jenkins library
Le samedi 11 mai 2019, 22:31:48 CEST Hervé BOUTEMY a écrit :
during latest Hackergarten in Paris [1], I had the chance to have Adrien
Lecharpentier [2] with me, then I gave him my ideal: - deploy only from
master = summary of previous discussions
- don't deploy until full ITs have been run on every platform, to avoid
deploying broken artifacts - let for later the discussion about which
build
to deploy (which JDK/OS build)...
then we started to work on an implementation based on local staging [3]
during build, then wagon:merge-maven-repos once every IT on every
platform
is ok
AFAIK, the implementation is not complete, I hope we'll finish during the
next session [4]
Really, it's about doing little steps together: I hope such Hackergarten
event can happen in many places, to have people work together more
efficiently than discussing in ML, which is frustrating when it remains
at
discussion status
Regards,
Hervé
[1] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzgbnc/
[2] https://github.com/alecharp
[3]
https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/exampl
es/deploy-network-issues.html
[4] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzhblc/
Le samedi 11 mai 2019, 15:07:25 CEST Mickael Istria a écrit :
Ok, thanks I'll try that.
But I'm still not really understanding what prevents Maven from calling
'mvn deploy' on that job to push snapshots to apache Maven repo.
Anything
one can help with??
On Saturday, May 11, 2019, Sylwester Lachiewicz <sl...@gmail.com>
wrote:
Hi Mickael,
i think You can try download latest snapshot dist from our Jenkins
build
from master branch [1]
Sylwek
[1]
https://builds.apache.org/view/M-R/view/Maven/job/maven-> > >
box/job/maven/job/master/lastSuccessfulBuild/artifact/
org/apache/maven/apache-maven
czw., 9 maj 2019 o 14:55 Mickael Istria <mi...@redhat.com>>
napisał(a):
Hi all,
I'd like to set up for Tycho an automated build that runs it's
master
against latest Maven snapshots, so we could more immediately spot
incompatibility like MNG-6642.
This should be quite easy to set up as a CI job.
However, what URL can I use to get access to the current snapshot
of
Maven
delivery?
Thanks in advance,
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org<ma...@maven.apache.org>
For additional commands, e-mail: dev-help@maven.apache.org<ma...@maven.apache.org>
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Adrien Lecharpentier <ad...@gmail.com>.
You can update the librairies as much as you want, without the need to
restart the instance. The shared libraries are cloned when the build
starts.
The fear I had during the hackergarten is more about the scope of the
change. Because the shared library is implicitly loaded, it means we cannot
specify a revision to use on one particular job. So, to test the library in
a real life environment, the changes etc needs to hit the master branche.
But as soon as this is happening, all jobs we be using it. Which means, if
what we have done has the smallest issue, it can take tremendous
proportions..
Le dim. 12 mai 2019 à 07:56, Hervé BOUTEMY <he...@free.fr> a écrit :
> notice 2:
> one issue we had when working on such not so trivial Jenkins library
> updates
> is: how to test locally before updating the production server,
> particularly
> when the lib is shared then updates cannot be done without server restart?
>
> this one probably deserves some explanations/documentation on our site,
> since
> we have ITs for every single Maven component/plugin but nothing about this
> Jenkins library
>
> Le samedi 11 mai 2019, 22:31:48 CEST Hervé BOUTEMY a écrit :
> > during latest Hackergarten in Paris [1], I had the chance to have Adrien
> > Lecharpentier [2] with me, then I gave him my ideal: - deploy only from
> > master = summary of previous discussions
> > - don't deploy until full ITs have been run on every platform, to avoid
> > deploying broken artifacts - let for later the discussion about which
> build
> > to deploy (which JDK/OS build)...
> >
> > then we started to work on an implementation based on local staging [3]
> > during build, then wagon:merge-maven-repos once every IT on every
> platform
> > is ok
> >
> > AFAIK, the implementation is not complete, I hope we'll finish during the
> > next session [4]
> >
> > Really, it's about doing little steps together: I hope such Hackergarten
> > event can happen in many places, to have people work together more
> > efficiently than discussing in ML, which is frustrating when it remains
> at
> > discussion status
> >
> > Regards,
> >
> > Hervé
> >
> > [1] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzgbnc/
> >
> > [2] https://github.com/alecharp
> >
> > [3]
> >
> https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/exampl
> > es/deploy-network-issues.html
> >
> > [4] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzhblc/
> >
> > Le samedi 11 mai 2019, 15:07:25 CEST Mickael Istria a écrit :
> > > Ok, thanks I'll try that.
> > > But I'm still not really understanding what prevents Maven from calling
> > > 'mvn deploy' on that job to push snapshots to apache Maven repo.
> Anything
> > > one can help with??
> > >
> > > On Saturday, May 11, 2019, Sylwester Lachiewicz <slachiewicz@gmail.com
> >
> > >
> > > wrote:
> > > > Hi Mickael,
> > > > i think You can try download latest snapshot dist from our Jenkins
> build
> > > > from master branch [1]
> > > >
> > > > Sylwek
> > > >
> > > > [1]
> > > > https://builds.apache.org/view/M-R/view/Maven/job/maven-> > >
> box/job/maven/job/master/lastSuccessfulBuild/artifact/
> > > > org/apache/maven/apache-maven
> > > >
> > > > czw., 9 maj 2019 o 14:55 Mickael Istria <mi...@redhat.com>
> napisał(a):
> > > > > Hi all,
> > > > >
> > > > > I'd like to set up for Tycho an automated build that runs it's
> master
> > > > > against latest Maven snapshots, so we could more immediately spot
> > > > > incompatibility like MNG-6642.
> > > > > This should be quite easy to set up as a CI job.
> > > > > However, what URL can I use to get access to the current snapshot
> of
> > > >
> > > > Maven
> > > >
> > > > > delivery?
> > > > >
> > > > > Thanks in advance,
> > > > > --
> > > > > Mickael Istria
> > > > > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
> > > > > developer, for Red Hat Developers <https://developers.redhat.com/>
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Hervé BOUTEMY <he...@free.fr>.
notice 2:
one issue we had when working on such not so trivial Jenkins library updates
is: how to test locally before updating the production server, particularly
when the lib is shared then updates cannot be done without server restart?
this one probably deserves some explanations/documentation on our site, since
we have ITs for every single Maven component/plugin but nothing about this
Jenkins library
Le samedi 11 mai 2019, 22:31:48 CEST Hervé BOUTEMY a écrit :
> during latest Hackergarten in Paris [1], I had the chance to have Adrien
> Lecharpentier [2] with me, then I gave him my ideal: - deploy only from
> master = summary of previous discussions
> - don't deploy until full ITs have been run on every platform, to avoid
> deploying broken artifacts - let for later the discussion about which build
> to deploy (which JDK/OS build)...
>
> then we started to work on an implementation based on local staging [3]
> during build, then wagon:merge-maven-repos once every IT on every platform
> is ok
>
> AFAIK, the implementation is not complete, I hope we'll finish during the
> next session [4]
>
> Really, it's about doing little steps together: I hope such Hackergarten
> event can happen in many places, to have people work together more
> efficiently than discussing in ML, which is frustrating when it remains at
> discussion status
>
> Regards,
>
> Hervé
>
> [1] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzgbnc/
>
> [2] https://github.com/alecharp
>
> [3]
> https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/exampl
> es/deploy-network-issues.html
>
> [4] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzhblc/
>
> Le samedi 11 mai 2019, 15:07:25 CEST Mickael Istria a écrit :
> > Ok, thanks I'll try that.
> > But I'm still not really understanding what prevents Maven from calling
> > 'mvn deploy' on that job to push snapshots to apache Maven repo. Anything
> > one can help with??
> >
> > On Saturday, May 11, 2019, Sylwester Lachiewicz <sl...@gmail.com>
> >
> > wrote:
> > > Hi Mickael,
> > > i think You can try download latest snapshot dist from our Jenkins build
> > > from master branch [1]
> > >
> > > Sylwek
> > >
> > > [1]
> > > https://builds.apache.org/view/M-R/view/Maven/job/maven-> > > box/job/maven/job/master/lastSuccessfulBuild/artifact/
> > > org/apache/maven/apache-maven
> > >
> > > czw., 9 maj 2019 o 14:55 Mickael Istria <mi...@redhat.com> napisał(a):
> > > > Hi all,
> > > >
> > > > I'd like to set up for Tycho an automated build that runs it's master
> > > > against latest Maven snapshots, so we could more immediately spot
> > > > incompatibility like MNG-6642.
> > > > This should be quite easy to set up as a CI job.
> > > > However, what URL can I use to get access to the current snapshot of
> > >
> > > Maven
> > >
> > > > delivery?
> > > >
> > > > Thanks in advance,
> > > > --
> > > > Mickael Istria
> > > > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
> > > > developer, for Red Hat Developers <https://developers.redhat.com/>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Hervé BOUTEMY <he...@free.fr>.
during latest Hackergarten in Paris [1], I had the chance to have Adrien Lecharpentier [2] with me, then I gave him my ideal:
- deploy only from master = summary of previous discussions
- don't deploy until full ITs have been run on every platform, to avoid deploying broken artifacts
- let for later the discussion about which build to deploy (which JDK/OS build)...
then we started to work on an implementation based on local staging [3] during build, then wagon:merge-maven-repos once every IT on every platform is ok
AFAIK, the implementation is not complete, I hope we'll finish during the next session [4]
Really, it's about doing little steps together: I hope such Hackergarten event can happen in many places, to have people work together more efficiently than discussing in ML, which is frustrating when it remains at discussion status
Regards,
Hervé
[1] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzgbnc/
[2] https://github.com/alecharp
[3] https://maven.apache.org/plugins-archives/maven-deploy-plugin-LATEST/examples/deploy-network-issues.html
[4] https://www.meetup.com/fr-FR/Paris-Hackergarten/events/tvdrwpyzhblc/
Le samedi 11 mai 2019, 15:07:25 CEST Mickael Istria a écrit :
> Ok, thanks I'll try that.
> But I'm still not really understanding what prevents Maven from calling
> 'mvn deploy' on that job to push snapshots to apache Maven repo. Anything
> one can help with??
>
> On Saturday, May 11, 2019, Sylwester Lachiewicz <sl...@gmail.com>
>
> wrote:
> > Hi Mickael,
> > i think You can try download latest snapshot dist from our Jenkins build
> > from master branch [1]
> >
> > Sylwek
> >
> > [1]
> > https://builds.apache.org/view/M-R/view/Maven/job/maven-
> > box/job/maven/job/master/lastSuccessfulBuild/artifact/
> > org/apache/maven/apache-maven
> >
> > czw., 9 maj 2019 o 14:55 Mickael Istria <mi...@redhat.com> napisał(a):
> > > Hi all,
> > >
> > > I'd like to set up for Tycho an automated build that runs it's master
> > > against latest Maven snapshots, so we could more immediately spot
> > > incompatibility like MNG-6642.
> > > This should be quite easy to set up as a CI job.
> > > However, what URL can I use to get access to the current snapshot of
> >
> > Maven
> >
> > > delivery?
> > >
> > > Thanks in advance,
> > > --
> > > Mickael Istria
> > > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
> > > developer, for Red Hat Developers <https://developers.redhat.com/>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Mickael Istria <mi...@redhat.com>.
Ok, thanks I'll try that.
But I'm still not really understanding what prevents Maven from calling
'mvn deploy' on that job to push snapshots to apache Maven repo. Anything
one can help with??
On Saturday, May 11, 2019, Sylwester Lachiewicz <sl...@gmail.com>
wrote:
> Hi Mickael,
> i think You can try download latest snapshot dist from our Jenkins build
> from master branch [1]
>
> Sylwek
>
> [1]
> https://builds.apache.org/view/M-R/view/Maven/job/maven-
> box/job/maven/job/master/lastSuccessfulBuild/artifact/
> org/apache/maven/apache-maven
>
>
> czw., 9 maj 2019 o 14:55 Mickael Istria <mi...@redhat.com> napisał(a):
>
> > Hi all,
> >
> > I'd like to set up for Tycho an automated build that runs it's master
> > against latest Maven snapshots, so we could more immediately spot
> > incompatibility like MNG-6642.
> > This should be quite easy to set up as a CI job.
> > However, what URL can I use to get access to the current snapshot of
> Maven
> > delivery?
> >
> > Thanks in advance,
> > --
> > Mickael Istria
> > Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
> > developer, for Red Hat Developers <https://developers.redhat.com/>
> >
>
--
Mickael Istria
Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
developer, for Red Hat Developers <https://developers.redhat.com/>
Re: Latest snapshot build (archive, not Maven artifact)
Posted by Sylwester Lachiewicz <sl...@gmail.com>.
Hi Mickael,
i think You can try download latest snapshot dist from our Jenkins build
from master branch [1]
Sylwek
[1]
https://builds.apache.org/view/M-R/view/Maven/job/maven-box/job/maven/job/master/lastSuccessfulBuild/artifact/org/apache/maven/apache-maven
czw., 9 maj 2019 o 14:55 Mickael Istria <mi...@redhat.com> napisał(a):
> Hi all,
>
> I'd like to set up for Tycho an automated build that runs it's master
> against latest Maven snapshots, so we could more immediately spot
> incompatibility like MNG-6642.
> This should be quite easy to set up as a CI job.
> However, what URL can I use to get access to the current snapshot of Maven
> delivery?
>
> Thanks in advance,
> --
> Mickael Istria
> Eclipse IDE <https://www.eclipse.org/downloads/eclipse-packages/>
> developer, for Red Hat Developers <https://developers.redhat.com/>
>