philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550376753
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550377021
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550376789
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550376753
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
What's you analysis?
Did you inform INFRA?
If we have issues with these versions, most likely Maven users will have to.
We've seen this in the past too and I think all the time I'm been able to bring
the builds back to blue.
Disabling would be avoiding or ignoring the problem.
thanks,
Robert
On
>From my experience, if we discard this issues now, on our infrastructure,
we would need to pay more when end users start to complying that one of our
maven plugins fails randomly.
We added new java versions to early test new java versions with our
products so there will be chance that bug can be
+1
śr., 30 gru 2020, 22:23 użytkownik Michael Osipov
napisał:
> Am 2020-12-30 um 22:16 schrieb Hervé BOUTEMY:
> > Hi,
> >
> > We solved 14 issues:
> >
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12348850=Text
> >
> > Staging repo:
> >
On Wed, Dec 30, 2020 at 8:58 PM John Patrick wrote:
>
> Better to know the issues and slowly fix them then get hit with a load
> of issues blocking users.
>
We have the Linux JDK 15, and Windows JDK 16, builds for that. The
windows JDK-15 build is noise that provides no useful information.
--
+1
On Wed, Dec 30, 2020 at 9:16 PM Hervé BOUTEMY wrote:
>
> Hi,
>
> We solved 14 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12348850=Text
>
> Staging repo:
> https://repository.apache.org/content/repositories/maven-1621/
>
Am 2020-12-30 um 22:16 schrieb Hervé BOUTEMY:
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12348850=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1621/
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550329282
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,241 @@
+ --
+ Guide to Large Scale Centralized
Hi,
We solved 14 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317422=12348850=Text
Staging repo:
https://repository.apache.org/content/repositories/maven-1621/
Better to know the issues and slowly fix them then get hit with a load
of issues blocking users.
Unlike the 1st 20 years of Java where deprecated didn't really mean
anything at all... Since Java 9 the guidelines are 1 release with
deprecation warning and then things can be
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550308234
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550299955
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550285056
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
philsttr commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550285056
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
khmarbaise commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550224261
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on a change in pull request #223:
URL: https://github.com/apache/maven-site/pull/223#discussion_r550214607
##
File path: content/apt/guides/mini/guide-large-scale-centralized-deployments.apt
##
@@ -0,0 +1,230 @@
+ --
+ Guide to Large Scale Centralized
michael-o commented on pull request #223:
URL: https://github.com/apache/maven-site/pull/223#issuecomment-752641357
>
>
> @slachiewicz , since [all the other
guides](https://github.com/apache/maven-site/tree/master/content/apt/guides)
are in apt, I'd rather keep this one in apt
Well, whether or not switching off a build platform should more be a question
of: Why have we switched it on actually?
-Markus
-Ursprüngliche Nachricht-
Von: Gary Gregory [mailto:garydgreg...@gmail.com]
Gesendet: Mittwoch, 30. Dezember 2020 15:14
An: Maven Developers List
Betreff: Re:
FWIW, it might be worth switching that Java 15/16-EA build to 17-EA since
17 will be LTS.
FYI, over at Apache Commons, we've found and reported bugs in Java 15 that
have been fixed in 16-EA but that won't be back ported to 15.
Gary
On Wed, Dec 30, 2020, 08:59 Elliotte Rusty Harold
wrote:
>
The Windows JDK 15 instance in jenkins seems irredeemably flaky. It
fails more often than not for reasons that have nothing to do with the
code being tested.
As JDK 15 is not a long term support release, and has only minimal
adoption, can we simply turn off the Windows JDK 15 build?
Personally,
rfscholte commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752506877
I still consider adding the `org.apache.maven.shared.transfer.project`
package a bad choice, because it introduces a dependency on Maven.
slachiewicz closed pull request #21:
URL: https://github.com/apache/maven-artifact-transfer/pull/21
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
slachiewicz commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752469411
Do we have anywhere documented this recommendation? I think we still have on
wiki to use this artefact.
Also with this changes we can easily switch to new
rfscholte closed pull request #20:
URL: https://github.com/apache/maven-artifact-transfer/pull/20
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
rfscholte commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752454346
Sorry @slachiewicz if you've spend a lot of time on this, but I need to
close this. Once everything is using Maven 3.1+ we can simply archive
rfscholte commented on pull request #20:
URL:
https://github.com/apache/maven-artifact-transfer/pull/20#issuecomment-752440522
Please don't do this. The intention of maven-artifact-transfer is a bridge
to any Aether implementation.
yes, it's time for release: I'll do it
thank you for your great help on this one
regards,
Hervé
Le lundi 28 décembre 2020, 19:14:54 CET abra...@gmail.com a écrit :
> Hi community,
>
>
>
> Are there any plans about release of 3.2.0 version of Maven EAR Plugin?
>
>
>
> It feels like there
asfgit closed pull request #47:
URL: https://github.com/apache/maven-doxia/pull/47
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
asfgit closed pull request #48:
URL: https://github.com/apache/maven-doxia/pull/48
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
32 matches
Mail list logo
