it seems there is a misunderstanding: it's not 4 parent POMs
it's resource bundles, that are used with maven-assembly-plugin or maven-
remote-resources-plugin in Apache parent POM [1]
see https://maven.apache.org/apache-resource-bundles/index.html for some
description
Regards,
Hervé
[1] https:
Hi,
One of my long standing wishes has made it to the master branch of Maven: the
support for build/consumer pom.
With this we can finally start improving the pom without breaking the Maven eco
system.
Up until now the pom.xml has been distributed (installed/deployed) as is to
both local and r
On 22-6-2020 00:25:39, Hervé BOUTEMY wrote:
> I agree: independent release cycles means independent repositories.
in the past, we had 4 independent Maven parent POMs [1] under one unique svn
trunk, with 4 separate release cycles, many votes/hard maintenance (having a
new parent POM release for pl
Hi Robert ,
*Per the JDK 15 schedule , we are in Rampdown Phase One* *[1] *
*Please advise if you find any issues while testing the latest Early
Access builds.
*
* Schedule for JDK 15
o *2020/06/11 Rampdown Phase One*
o 2020/07/16 Rampdown Phase Two
o 2020/08/06 Initial Relea
hboutemy commented on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-647613135
> If there are accepted conventions for code commits, it would be worth
investing some time to enforce in our systems.
implementing is just one line in .asf.yaml:
elharo commented on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-647508322
Latest communication from @rfscholte was that dependency upgrades should
just happen without JIRA issues. I'm inclined to agree, but if the community
decides we must have J
michael-o edited a comment on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-647470345
I have a huge problem with these PRs: no one creates JIRA issues for these...
This is an automate
michael-o commented on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-647470345
I have a huge problem with these PRs: no one create JIRA issues for these...
This is an automated messag
olamy commented on pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32#issuecomment-647455416
OMG another spam generator
This is an automated message from the Apache Git Service.
To respond to the m
elharo opened a new pull request #32:
URL: https://github.com/apache/maven-site-plugin/pull/32
@slachiewicz Dependabot seems to be working well on the parent repos. Let's
try it here.
This is an automated message from the A
10 matches
Mail list logo