+1
Does it really worth waste your time doing a last release?
Last real bug fix looks to be from 6yo…
On Sat, 7 Dec 2024 at 10:41 pm, Slawomir Jaranowski
wrote:
> On Sat, 7 Dec 2024 at 13:31, Elliotte Rusty Harold
> wrote:
> >
> > No objections to retiring it. However if we're going to do a fi
Semeru is based on OpenJ9 whereas Temurin builds are HotSpot based. It
depends on whether you want to test against the two different JVMs (both
pass the TCK).
Cheers,
Martijn
On Sat, 7 Dec 2024 at 10:13, Elliotte Rusty Harold
wrote:
> What's up with Java CI / build (ubuntu-latest, 17, semeru)
What's up with Java CI / build (ubuntu-latest, 17, semeru)
(pull_request)? I just had a PR flake on this due to failure to
download. Do we get anything from this we don't get from the temurin
17 builds? If not, we should remove it. Every additional build we add
to the CI increases the risk of flake
Lets start discuss about convention
https://github.com/apache/maven-site/pull/588
On Wed, 4 Dec 2024 at 19:45, Slawomir Jaranowski wrote:
>
> Hi,
>
> I'm for #2
> - simply add issues to GitHub, disable the creation of new issues in jira.
> - I know that we have many projects ... but we should do
On Fri, 6 Dec 2024 at 14:41, Sandra Parsick wrote:
>
> I asked on other channels, how Spring migrated their Jira issues. I got
> a link to their migration tool:
>
> https://github.com/rstoyanchev/jira-to-gh-issues
>
> An updated version can be found here:
> https://github.com/rwinch/jira-to-gh-iss
Hi,
We solved 58 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317222&version=12355450
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MCHANGES%20AND%20resolution%20%3D%20Unresolved%20ORDER%20BY%20priority%20
On Sat, 7 Dec 2024 at 13:31, Elliotte Rusty Harold wrote:
>
> No objections to retiring it. However if we're going to do a final
> release, let's take a couple of weeks to update it first.
I am afraid that I have to fix it to make possible to release the last
version. So will be done.
>
> On Sat
No objections to retiring it. However if we're going to do a final
release, let's take a couple of weeks to update it first.
On Sat, Dec 7, 2024 at 10:22 AM Slawomir Jaranowski
wrote:
>
> Hi,
>
> The plugin is not maintained for a long time.
> It is rational to make it retire to show the real sta
+1
Guillaume Nodet
Le sam. 7 déc. 2024 à 11:22, Slawomir Jaranowski a
écrit :
> Hi,
>
> The plugin is not maintained for a long time.
> It is rational to make it retire to show the real status of the project.
>
> Instead of this plugin we can simply use dedicated sour
+1
sob., 7 gru 2024, 11:27 użytkownik Tamás Cservenák
napisał:
> +1
>
> On Sat, Dec 7, 2024, 11:22 Slawomir Jaranowski
> wrote:
>
> > Hi,
> >
> > The plugin is not maintained for a long time.
> > It is rational to make it retire to show the real status of the project.
> >
> > Instead of this pl
+1
On Sat, Dec 7, 2024, 11:22 Slawomir Jaranowski
wrote:
> Hi,
>
> The plugin is not maintained for a long time.
> It is rational to make it retire to show the real status of the project.
>
> Instead of this plugin we can simply use dedicated source code management
> tools.
>
> https://maven.apa
Hi,
The plugin is not maintained for a long time.
It is rational to make it retire to show the real status of the project.
Instead of this plugin we can simply use dedicated source code management tools.
https://maven.apache.org/plugins/maven-patch-plugin/
https://github.com/apache/maven-patch-p
Hi,
The vote has passed with following result.
+1 Slawomir, Sylwester, Guillaume, Karlm Tamas, Olivier
I will finish the release process.
Cheers
Olivier
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional co
+1
On Fri, 6 Dec 2024 at 17:12, Konrad Windszus wrote:
>
> Hi,
>
> We solved 6 issues:
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12355261&styleName=Text
>
> There are still a couple of issues left in JIRA.
>
> Staging repo:
> https://repository.apache.org
+1
On Fri, Dec 6, 2024, 17:12 Konrad Windszus wrote:
> Hi,
>
> We solved 6 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12355261&styleName=Text
>
> There are still a couple of issues left in JIRA.
>
> Staging repo:
> https://repository.apache.org/
+1
On Wed, 4 Dec 2024 at 16:18, Olivier Lamy wrote:
>
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 3.11.2.
> We fixed 3 issues:
> https://issues.apache.org/jira/projects/MJAVADOC/versions/12355299
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2250/
>
+1
On Wed, Dec 4, 2024, 07:18 Olivier Lamy wrote:
> Hi,
> I'd like to release Apache Maven Javadoc Plugin 3.11.2.
> We fixed 3 issues:
> https://issues.apache.org/jira/projects/MJAVADOC/versions/12355299
> Staging repository:
> https://repository.apache.org/content/repositories/maven-2250/
>
> D
+1
On Fri, 6 Dec 2024 at 16:06, Guillaume Nodet wrote:
>
> I've staged a release of Maven Invoker Plugin 3.9.0
> We fixed 3 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12355445&projectId=12317525
> https://issues.apache.org/jira/projects/MINVOKER/versions/12355445
+1
On Fri, Dec 6, 2024, 16:06 Guillaume Nodet wrote:
> I've staged a release of Maven Invoker Plugin 3.9.0
> We fixed 3 issues:
>
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?version=12355445&projectId=12317525
> https://issues.apache.org/jira/projects/MINVOKER/versions/12355445
slawekjaranowski commented on PR #18:
URL:
https://github.com/apache/maven-hocon-extension/pull/18#issuecomment-2525053526
Without it we have notifications on dev list
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use t
slawekjaranowski opened a new pull request, #18:
URL: https://github.com/apache/maven-hocon-extension/pull/18
(no comment)
--
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 the specific comment.
T
21 matches
Mail list logo