can we work on scaling the Jira to GH Issues first before diving into all the
implications of Maven 3 vs Maven 4 compatibility topic?
I feel we launch too much large scale and critical topics in parallel
Regards,
Hervé
Le mardi 4 février 2025, 18:53:30 CET Slawomir Jaranowski a écrit :
> Hi,
>
On 2025/02/05 08:16:44 Guillaume Nodet wrote:
> Searching for infos in old issues often involves switching between github
> (for commits / PRs) and JIRAs.
> If history can be rewritten, it would clearly be a benefit.
> An example:
> * https://github.com/apache/maven-jlink-plugin/issues/499
> * h
Le mercredi 5 février 2025, 07:48:53 CET Guillaume Nodet a écrit :
> Le mer. 5 févr. 2025 à 07:36, Slawomir Jaranowski
>
> a écrit :
> > I'm still not convitient if we really need copy all issues from jira
> > to github - as I wrote many times
> >
> > - jira will be exist with us
> > - I don't b
In json, you need an empty list or object ([] or {}).
As of the duplicates:
I'll send GitHub support the list of duplicates today. They were willing to
help us clean up.
As of why the first created issues where pending, they are still
investigating that. Lessons learned: next time wait and don't
Hi,
The Project Management Committee (PMC) for Apache Maven
has invited Matthias Bünger to become a committer
and we are pleased to announce that they have accepted.
Please join us in welcoming Matthias Bünger to their new role
and responsibility in our project community.
--
Slawomir Jaranowski
Makes sense. Just let's not jump the gun. That is, don't change the
URLs and don't publish the 4.x docs at the existing URLs until Maven 4
is released. If you want to publish the docs now, you could publish
both https://maven.apache.org/plugins/maven-clean-plugin-3.x/ and
https://maven.apache.org/p
Hi,
We have some plugins in both versions for Maven 4.x and for 3.x,
probably more will be in the future.
Proposition to have 4.x documentation as in now, and add suffix -3.x
for 3.x versions, example:
https://maven.apache.org/plugins/maven-clean-plugin/ - documentation
for master branch 4.x
htt
Hi,
A little clarification on why I would like to do it ...
- try shared GitHub tools with multi-release plugin 4x and 3.x versions [1]
- do first release based on GitHub issue - to have a lesson what
should be updated in procedures [2]
- give posiility to use GitHub issues by user with more used
Howdy,
This Resolver 2.0.6 release is a bugfix release with some
improvements as well.
Maven 4.x is picking up Resolver 2.x, while Maven 3.x remains at
Resolver 1.x lineage. The two major versions, as far as client code
goes (Mojos or extensions, using Resolver API as documented), are
binary comp
The Apache Maven team is pleased to announce the release of the
Maven Resolver Ant Tasks 1.5.2
===
Site:
https://maven.apache.org/resolver-ant-tasks
Release Notes - Maven Resolver - Version ant-tasks-1.5.2
** Bug
* [MRESOLVER-668] - Don't default the scope of managed
dependencies to 'compil
Howdy,
The vote has passed with the following result:
+1: Tamas, Slawomir, Olivier, Sylwester, Arnaud
PMC quorum: reached
I will promote the source release zip file to the Apache distribution
area and the artifacts to the Maven Central repo.
Thanks
T
--
On Wed, 5 Feb 2025 at 09:55, Benjamin Marwell wrote:
>
> It should have been. You're right.
> I'll talk to infra about this.
> We also disabled jira comments to the ML for migration.
>
maybe we can put an empty value in notification ...
notifications:
...
issues:
...
https://github.com/apache
It should have been. You're right.
I'll talk to infra about this.
We also disabled jira comments to the ML for migration.
On Wed, 5 Feb 2025, 09:29 Slawomir Jaranowski,
wrote:
> One more issue ... we have many notifications on ML, like:
> https://lists.apache.org/list?iss...@maven.apache.org:l
One more issue ... we have many notifications on ML, like:
https://lists.apache.org/list?iss...@maven.apache.org:lte=1M:jira-importer
Maybe it can be possible to disable notifications during migration time.
On Tue, 4 Feb 2025 at 23:42, Elliotte Rusty Harold wrote:
>
> If you look at https://gith
Searching for infos in old issues often involves switching between github
(for commits / PRs) and JIRAs.
If history can be rewritten, it would clearly be a benefit.
An example:
* https://github.com/apache/maven-jlink-plugin/issues/499
* https://github.com/apache/maven-jlink-plugin/pull/229
It would
15 matches
Mail list logo
