michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550452528
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
On Wed, Dec 30, 2020 at 11:38 PM Robert Scholte wrote:
>
> What's you analysis?
> Did you inform INFRA?
> If we have issues with these versions, most likely Maven users will have to.
>
The issues all seem to be in the test infrastructure, and have nothing
to do with the Maven code itself. While
Looks like the magic words are "pipeline steps". Why that isn't linked
directly from the failures and why one has to go hunting through
inobviously named menus, I don't know; but that's a Jenkins issue, not
a Maven one. I do think it would be worth revisiting our choice of CI
servers one of these
I'm not sure we're looking at the same thing.
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/null/
shows three runs of the same most recently committed code. The first
two failed flakily on different instances and passed on all other
instances. The third
Hello,
As long as we have windows builds and jdk15+ builds I guess one can reduce the
flaky combinations but it would still be interesting to see what’s the problem
is, in the pipeline steps view you see the failed step
Looks like the IT for is failing MDEP-644[1].
Elliotte, you closed this one, but I'm missing some important information in
this ticket: a link to the commit.
Now it is hard to figure out if there's a SNAPSHOT issue in play.
You see these kind of failures if branches of a SNAPSHOT dependency use
Here's one example:
https://ci-builds.apache.org/job/Maven/job/maven-box/job/maven-dependency-plugin/job/null/
There are many others. Nothing changed between the three runs. First
Windows JDK 15 failed. Then Windows JDK 7 failed. Then they all
passed. No code changes were made between the runs.
Great, thanks!
I expect that one of the other Jenkins jobs overwrites JAVA_HOME, not knowing
it effects all following jobs.
Robert
On 31-12-2020 09:24:07, Benjamin Marwell wrote:
Here you go: https://issues.apache.org/jira/browse/INFRA-21244
Already opened a week ago when Hervé tried to merge
+1
On 29-12-2020 22:53:05, Sylwester Lachiewicz wrote:
Hi,
We solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12331412=Text=12317922
Staging repo:
https://repository.apache.org/content/repositories/maven-1619/
Here you go: https://issues.apache.org/jira/browse/INFRA-21244
Already opened a week ago when Hervé tried to merge a PR and suddenly the
build failed.
Disabling JDK15 might be a valid solution if they don't react soon.
On Wed, 30 Dec 2020, 14:59 Elliotte Rusty Harold,
wrote:
> The Windows
+1
even if I could not reproduce the build because it was done with JDK 17 (EA):
what's the interest of playing with such early JDK for doing public release?
Didn't we already discuss about it before?
Regards,
Hervé
Le mardi 29 décembre 2020, 22:52:44 CET Sylwester Lachiewicz a écrit :
> Hi,
Hello all,
regarding the active work occurring for maven 4.0.0 I noticed the
introduction of a lot of new stuff around SAX parsing & filtering.
I am wondering if that means that it was decided that the input format of
maven projects will be XML forever meaning probably, among others, the end
of
Hello,
Not exactly sure what work you mean and I fully agree that using a core model
should still be the API for plugins and extensions to work with, however
specifically the consumer POM integrates with so many external ecosystems, I
would expect it to be defined in terms of XML Schema with
> Not exactly sure what work you mean
everything related to maven-xml: Build/ConsumerPomXMLFilterxxx,
Build/ConsumerModelSource and the transformer stuff.
Especially, when looking at classes like CiFriendlyXMLFilter, I would have
thought that such things could have been done elsewhere, working
Hi,
Sorry for releasing with ea version - i use it on daily basis to test all
Maven components. For future I'll be more careful.
This packages contains only files, no compiled classes so it should not be
affected by java version. My build was created from fresh git clone on
Windows 10.
How i can
I've made a recording[1] about it, which hopefully answers most questions.
Robert
[1] https://youtu.be/KDAmlNKZJto
On 31-12-2020 16:18:57, Matthieu Brouillard wrote:
> Not exactly sure what work you mean
everything related to maven-xml: Build/ConsumerPomXMLFilterxxx,
Have you tried
https://ci-builds.apache.org/blue/organizations/jenkins/Maven%2Fmaven-box%2Fmaven-dependency-plugin/detail/null/2/pipeline
?
It shows the output of the failing IT. It expects verbose information, but it
is missing.
Robert
On 31-12-2020 13:29:54, Elliotte Rusty Harold wrote:
17 matches
Mail list logo
