You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Slawomir Jaranowski <s....@gmail.com> on 2023/04/13 19:35:04 UTC
[HEADS UP] ASF/Maven parent poms
Hi.
I would like to release the next version of parent poms.
ASF -
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20fixVersion%20%3D%20ASF-30
Maven -
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20fixVersion%20%3D%20MAVEN-40
With already merged changes we can start using JDK 20 for builds.
Issues to discus:
ASF:
MPOM-398 - Bump maven-help-plugin from 3.3.0 to 3.4.0 - 3.4.0 requires
Maven 3.6.3, but whole build requires 3.2.5 it is some of inconsistency for
me
MPOM-289 - Use properties to define the versions of plugins - I hope it can
be useful
MPOM-344 - we need a new release of maven-remote-resources-plugin
MPOM-394 - we need a new release of Maven Project Info Reports Plugin to
3.4.3
Maven:
MPOM-414 - newer version of spotless require JDK 11+
Please comment / discuss in jira because we many case and on ML we can
introduce a mess
--
Sławomir Jaranowski
Re: [HEADS UP] ASF/Maven parent poms
Posted by Michael Osipov <mi...@apache.org>.
I will take care of MPIR release.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] ASF/Maven parent poms
Posted by Karl Heinz Marbaise <kh...@gmx.de>.
On 13.04.23 21:35, Slawomir Jaranowski wrote:
> Hi.
>
> I would like to release the next version of parent poms.
>
> ASF -
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20fixVersion%20%3D%20ASF-30
> Maven -
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MPOM%20AND%20fixVersion%20%3D%20MAVEN-40
>
> With already merged changes we can start using JDK 20 for builds.
Great...
>
> Issues to discus:
>
> ASF:
> MPOM-398 - Bump maven-help-plugin from 3.3.0 to 3.4.0 - 3.4.0 requires
> Maven 3.6.3, but whole build requires 3.2.5 it is some of inconsistency for
> me
> MPOM-289 - Use properties to define the versions of plugins - I hope it can
> be useful
> MPOM-344 - we need a new release of maven-remote-resources-plugin
> MPOM-394 - we need a new release of Maven Project Info Reports Plugin to
> 3.4.3
>
> Maven:
> MPOM-414 - newer version of spotless require JDK 11+
We could build with JDK11 or even JDK17 and use "--release" to produce
JDK8 compatible code... ?
Kind regards
Karl Heinz Marbaise
>
>
> Please comment / discuss in jira because we many case and on ML we can
> introduce a mess
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] ASF/Maven parent poms
Posted by Herve Boutemy <hb...@apache.org>.
that's why the documentation site for parent POMs has a "History" section that provides links to diff:
https://maven.apache.org/pom-archives/asf-LATEST/#history
Regards,
Hervé
On 2023/04/14 11:09:03 Elliotte Rusty Harold wrote:
> Several of these seem like small red flags to me and while
> individually each might be manageable, put them all together and I
> vote for staying on 39 for a while longer.
>
> I'd also prefer that we complete upgrading the ~80 projects we
> maintain to Java 8, Maven 3.2.5, and parent pom 39 before we start
> moving some projects beyond that. That is, finish the work at hand
> before committing to new work.
>
> Finally, I think we need to reduce the manual labor and bureaucracy
> associated with small upgrades. Nit picking commit history and JIRA
> issues dramatically slows progress. As currently conceived, we do not
> have the resources to do the upgrades we've already promised. We
> either have to take work off the table so this can move faster or find
> more resources to do the work.
>
> Two concrete proposals for speeding up progress:
>
> 1. Ignore the commit history. PRs are the source of truth. Configure
> all repos to allow squash merges only. Anything more granular than
> that is too rarely helpful in practice to be worth the lost time.
>
> 2. Stop filing and requiring JIRA issues for dependency updates.
> Instead use maven-dependency-analyzer tooling to directly compare poms
> between releases and insert that into release notes.
>
> --
> Elliotte Rusty Harold
> elharo@ibiblio.org
>
> ---------------------------------------------------------------------
> 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: [HEADS UP] ASF/Maven parent poms
Posted by Gary Gregory <ga...@gmail.com>.
The abundance of Maven warnings is indeed annoying, but it seems like
normal growing pains while migration to new versions of plugins is in
progress ;-) which is a good thing overall IMO.
Gary
On Sat, Apr 15, 2023, 09:19 Konrad Windszus <kw...@apache.org> wrote:
> I agree with that. For me a new ASF parent release is primarily necessary
> due to the fact that using the current version leads to quite some warnings
> when used with Maven 3.9.1.
>
> On 2023/04/15 12:31:07 Slawomir Jaranowski wrote:
> > sob., 15 kwi 2023 o 12:40 Michael Osipov <mi...@apache.org>
> napisał(a):
> >
> > > Am 2023-04-14 um 13:09 schrieb Elliotte Rusty Harold:
> > > > Several of these seem like small red flags to me and while
> > > > individually each might be manageable, put them all together and I
> > > > vote for staying on 39 for a while longer.
> > > >
> > > > I'd also prefer that we complete upgrading the ~80 projects we
> > > > maintain to Java 8, Maven 3.2.5, and parent pom 39 before we start
> > > > moving some projects beyond that. That is, finish the work at hand
> > > > before committing to new work.
> > >
> > > I totally agree here. We haven't done the homework and want to start
> new
> > > topics. We should agressive retire what we do not intend to maintain or
> > > do at least a parent 39 cleanup.
> > >
> > >
> > I agree that we still have some homework to do.
> > The new version of parent is not a new topic for me, simply if we don't
> > upgrade parent in some of components to 39 we have the next version.
> > There are many situations where we bump parent by many numbers and it is
> > not bad.
> >
> > We always will have work to do, for me it is a never ending story.
> >
> > On the other hand ASF parent is not only used by the Maven project.
> > We did many works an plugins updates and should be published in AFS
> parent
> > - last was released at 2022-12-11
> >
> > When we do not publish parents regularly with incremental changes we
> cause
> > other projects to override used plugins versions.
> > So we and others manage plugin versions in many projects, not in one.
> >
> >
> > M
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > > For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> > --
> > Sławomir Jaranowski
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
Re: [HEADS UP] ASF/Maven parent poms
Posted by Konrad Windszus <kw...@apache.org>.
I agree with that. For me a new ASF parent release is primarily necessary due to the fact that using the current version leads to quite some warnings when used with Maven 3.9.1.
On 2023/04/15 12:31:07 Slawomir Jaranowski wrote:
> sob., 15 kwi 2023 o 12:40 Michael Osipov <mi...@apache.org> napisał(a):
>
> > Am 2023-04-14 um 13:09 schrieb Elliotte Rusty Harold:
> > > Several of these seem like small red flags to me and while
> > > individually each might be manageable, put them all together and I
> > > vote for staying on 39 for a while longer.
> > >
> > > I'd also prefer that we complete upgrading the ~80 projects we
> > > maintain to Java 8, Maven 3.2.5, and parent pom 39 before we start
> > > moving some projects beyond that. That is, finish the work at hand
> > > before committing to new work.
> >
> > I totally agree here. We haven't done the homework and want to start new
> > topics. We should agressive retire what we do not intend to maintain or
> > do at least a parent 39 cleanup.
> >
> >
> I agree that we still have some homework to do.
> The new version of parent is not a new topic for me, simply if we don't
> upgrade parent in some of components to 39 we have the next version.
> There are many situations where we bump parent by many numbers and it is
> not bad.
>
> We always will have work to do, for me it is a never ending story.
>
> On the other hand ASF parent is not only used by the Maven project.
> We did many works an plugins updates and should be published in AFS parent
> - last was released at 2022-12-11
>
> When we do not publish parents regularly with incremental changes we cause
> other projects to override used plugins versions.
> So we and others manage plugin versions in many projects, not in one.
>
>
> M
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> --
> Sławomir Jaranowski
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] ASF/Maven parent poms
Posted by Slawomir Jaranowski <s....@gmail.com>.
sob., 15 kwi 2023 o 12:40 Michael Osipov <mi...@apache.org> napisał(a):
> Am 2023-04-14 um 13:09 schrieb Elliotte Rusty Harold:
> > Several of these seem like small red flags to me and while
> > individually each might be manageable, put them all together and I
> > vote for staying on 39 for a while longer.
> >
> > I'd also prefer that we complete upgrading the ~80 projects we
> > maintain to Java 8, Maven 3.2.5, and parent pom 39 before we start
> > moving some projects beyond that. That is, finish the work at hand
> > before committing to new work.
>
> I totally agree here. We haven't done the homework and want to start new
> topics. We should agressive retire what we do not intend to maintain or
> do at least a parent 39 cleanup.
>
>
I agree that we still have some homework to do.
The new version of parent is not a new topic for me, simply if we don't
upgrade parent in some of components to 39 we have the next version.
There are many situations where we bump parent by many numbers and it is
not bad.
We always will have work to do, for me it is a never ending story.
On the other hand ASF parent is not only used by the Maven project.
We did many works an plugins updates and should be published in AFS parent
- last was released at 2022-12-11
When we do not publish parents regularly with incremental changes we cause
other projects to override used plugins versions.
So we and others manage plugin versions in many projects, not in one.
M
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
Sławomir Jaranowski
Re: [HEADS UP] ASF/Maven parent poms
Posted by Michael Osipov <mi...@apache.org>.
Am 2023-04-14 um 13:09 schrieb Elliotte Rusty Harold:
> Several of these seem like small red flags to me and while
> individually each might be manageable, put them all together and I
> vote for staying on 39 for a while longer.
>
> I'd also prefer that we complete upgrading the ~80 projects we
> maintain to Java 8, Maven 3.2.5, and parent pom 39 before we start
> moving some projects beyond that. That is, finish the work at hand
> before committing to new work.
I totally agree here. We haven't done the homework and want to start new
topics. We should agressive retire what we do not intend to maintain or
do at least a parent 39 cleanup.
M
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [HEADS UP] ASF/Maven parent poms
Posted by Elliotte Rusty Harold <el...@ibiblio.org>.
Several of these seem like small red flags to me and while
individually each might be manageable, put them all together and I
vote for staying on 39 for a while longer.
I'd also prefer that we complete upgrading the ~80 projects we
maintain to Java 8, Maven 3.2.5, and parent pom 39 before we start
moving some projects beyond that. That is, finish the work at hand
before committing to new work.
Finally, I think we need to reduce the manual labor and bureaucracy
associated with small upgrades. Nit picking commit history and JIRA
issues dramatically slows progress. As currently conceived, we do not
have the resources to do the upgrades we've already promised. We
either have to take work off the table so this can move faster or find
more resources to do the work.
Two concrete proposals for speeding up progress:
1. Ignore the commit history. PRs are the source of truth. Configure
all repos to allow squash merges only. Anything more granular than
that is too rarely helpful in practice to be worth the lost time.
2. Stop filing and requiring JIRA issues for dependency updates.
Instead use maven-dependency-analyzer tooling to directly compare poms
between releases and insert that into release notes.
--
Elliotte Rusty Harold
elharo@ibiblio.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org