[
https://issues.apache.org/jira/browse/MNG-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MNG-7306.
-
Assignee: Olivier Lamy
Resolution: Won't Fix
noise or please explain why it's an improvement
> Make
[
https://issues.apache.org/jira/browse/MNG-7307?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MNG-7307.
-
Resolution: Won't Fix
noise
> Make final var when its possible maven-builder-support.
> --
[
https://issues.apache.org/jira/browse/MNG-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17429003#comment-17429003
]
Sylwester Lachiewicz commented on MNG-7308:
---
maven-compact is deprecated and shou
[
https://issues.apache.org/jira/browse/MNG-7308?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz closed MNG-7308.
-
Resolution: Won't Fix
> Make var when its possible maven-compat
> -
Arturo Bernal created MNG-7308:
--
Summary: Make var when its possible maven-compat
Key: MNG-7308
URL: https://issues.apache.org/jira/browse/MNG-7308
Project: Maven
Issue Type: Sub-task
[
https://issues.apache.org/jira/browse/MNG-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428995#comment-17428995
]
Sylwester Lachiewicz commented on MNG-7217:
---
MNG-6069 and https://github.com/apac
Arturo Bernal created MNG-7307:
--
Summary: Make final var when its possible maven-builder-support.
Key: MNG-7307
URL: https://issues.apache.org/jira/browse/MNG-7307
Project: Maven
Issue Type: Sub
Arturo Bernal created MNG-7306:
--
Summary: Make final var maven-artifact
Key: MNG-7306
URL: https://issues.apache.org/jira/browse/MNG-7306
Project: Maven
Issue Type: Improvement
Repor
[
https://issues.apache.org/jira/browse/MNG-7306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Arturo Bernal updated MNG-7306:
---
Parent: MNG-7286
Issue Type: Sub-task (was: Improvement)
> Make final var maven-artifact
> ---
[
https://issues.apache.org/jira/browse/MPLUGIN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MPLUGIN-377:
Fix Version/s: 3.6.2
> Drop use of legacy APIs
> ---
>
>
[
https://issues.apache.org/jira/browse/MPLUGIN-376?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák updated MPLUGIN-376:
Fix Version/s: 3.6.2
> Drop use of legacy dependencies
> ---
>
[
https://issues.apache.org/jira/browse/MPLUGIN-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tamás Cservenák moved MNG-7305 to MPLUGIN-377:
--
Key: MPLUGIN-377 (was: MNG-7305)
Project: Maven Plugin Tools
Tamás Cservenák created MNG-7305:
Summary: Drop use of legacy APIs
Key: MNG-7305
URL: https://issues.apache.org/jira/browse/MNG-7305
Project: Maven
Issue Type: Task
Reporter: Tamá
Tamás Cservenák created MPLUGIN-376:
---
Summary: Drop use of legacy dependencies
Key: MPLUGIN-376
URL: https://issues.apache.org/jira/browse/MPLUGIN-376
Project: Maven Plugin Tools
Issue Type
Tamás Cservenák created MPOM-272:
Summary: Remove legacy from doxia parent depMgmg
Key: MPOM-272
URL: https://issues.apache.org/jira/browse/MPOM-272
Project: Maven POMs
Issue Type: Task
Tamás Cservenák created MPOM-271:
Summary: Create helper profile to "ban legacy"
Key: MPOM-271
URL: https://issues.apache.org/jira/browse/MPOM-271
Project: Maven POMs
Issue Type: Task
Tamás Cservenák created MPOM-270:
Summary: Fix enforcer use
Key: MPOM-270
URL: https://issues.apache.org/jira/browse/MPOM-270
Project: Maven POMs
Issue Type: Task
Reporter: Tamás
[
https://issues.apache.org/jira/browse/MNG-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428986#comment-17428986
]
Michael Osipov commented on MNG-7193:
-
I have a very lengthly chat with [~rfscholte] ab
[
https://issues.apache.org/jira/browse/MNG-7193?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428984#comment-17428984
]
Michael Osipov commented on MNG-7193:
-
No parsing, but supplying. You have {{MAVEN_OPTS
[
https://issues.apache.org/jira/browse/MRESOLVER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428980#comment-17428980
]
Michael Osipov commented on MRESOLVER-218:
--
What else do you have in mind for
[
https://issues.apache.org/jira/browse/MNG-7217?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428978#comment-17428978
]
Michael Osipov commented on MNG-7217:
-
bq. [~michael-o], it seems to me that the approa
[
https://issues.apache.org/jira/browse/MNG-7103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7103:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0
> Make generic VersionScheme a com
[
https://issues.apache.org/jira/browse/MNG-7279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7279:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0
> Drop PluginParameterExpressionEv
[
https://issues.apache.org/jira/browse/MNG-7278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7278:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0
> Drop use of Plexus Logger in Mav
[
https://issues.apache.org/jira/browse/MNG-7055?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7055:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0
> Using MINSTALL/DEPLOY 3.0.0-M1+
[
https://issues.apache.org/jira/browse/MNG-6898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6898:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0
> Convert DefaultLifecyclePluginAn
[
https://issues.apache.org/jira/browse/MNG-7294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-7294:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0
> Refactor MavenSession#getPluginC
[
https://issues.apache.org/jira/browse/MNG-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6389.
---
> Move the toolchains model to a separate artifactId
> --
>
[
https://issues.apache.org/jira/browse/MNG-6389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6389:
Fix Version/s: (was: 4.0.x-candidate)
4.0.0-alpha-1
4.0.0
>
Arturo Bernal created MNG-7304:
--
Summary: Use try-with-resources Statement
Key: MNG-7304
URL: https://issues.apache.org/jira/browse/MNG-7304
Project: Maven
Issue Type: Sub-task
Repor
[
https://issues.apache.org/jira/browse/MRESOLVER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428869#comment-17428869
]
Michael Osipov commented on MRESOLVER-218:
--
Theoritically you should have the
[
https://issues.apache.org/jira/browse/MRESOLVER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428869#comment-17428869
]
Michael Osipov edited comment on MRESOLVER-218 at 10/14/21, 3:27 PM:
---
cstamas commented on pull request #42:
URL: https://github.com/apache/maven-plugin-tools/pull/42#issuecomment-943357166
I am for it, but for now at least this PR aligns tests in this project, does
not mix junit3 and junit4 anymore...
--
This is an automated message from the Apache Git Se
gnodet commented on pull request #42:
URL: https://github.com/apache/maven-plugin-tools/pull/42#issuecomment-943350125
I wonder if we should switch to junit 5 rather than going to junit 4. It
has been out for 4 years now. I've done such a migration a few times, so I can
work on it when t
cstamas opened a new pull request #42:
URL: https://github.com/apache/maven-plugin-tools/pull/42
Plugin used a lot of legacy code, misused Mojo test case
and used old Junit 3.x TestCase, and missed some
dependencies (junit mostly).
---
Project cleaned up locally with help
cstamas merged pull request #41:
URL: https://github.com/apache/maven-plugin-tools/pull/41
--
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.
To unsubscribe, e-mail: issues-
cstamas edited a comment on pull request #37:
URL: https://github.com/apache/maven-plugin-tools/pull/37#issuecomment-943244503
Changes coming from master: added `-P run-its` as ITs were NOT executed
before (and they would fail IMHO).
IT failure reason is ancient projects in ITs: Thi
cstamas commented on pull request #37:
URL: https://github.com/apache/maven-plugin-tools/pull/37#issuecomment-943244503
Changes coming from master: added `-P run-its` as ITs were NOT executed
before (and they would fail IMHO). Reason is ancient projects in ITs. This PR
ITs passes when this
cstamas opened a new pull request #41:
URL: https://github.com/apache/maven-plugin-tools/pull/41
They used ancient maven API and expect things to be
on classpath, that is not the case anymore.
Changed fixed mvn version to param, and added maven-core
as dependency as the class is
cstamas opened a new pull request #34:
URL: https://github.com/apache/maven-parent/pull/34
Remove legacy drop doxia (plexus shim is "drop in"
replacement), and define at TLP the
p-u, plexus shim as well as downstream
these are most probably used, is easier
to align along these.
[
https://issues.apache.org/jira/browse/MRESOLVER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428730#comment-17428730
]
Tamás Cservenák commented on MRESOLVER-218:
---
Yes, it would cover that one as
[
https://issues.apache.org/jira/browse/MRESOLVER-218?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17428727#comment-17428727
]
Michael Osipov commented on MRESOLVER-218:
--
Uuh, what problems are you trying
Tamás Cservenák created MRESOLVER-218:
-
Summary: More granular control from where "file checksums" is
coming
Key: MRESOLVER-218
URL: https://issues.apache.org/jira/browse/MRESOLVER-218
Project: Ma
Tamás Cservenák created MRESOLVER-217:
-
Summary: Allow extra "sources" for Artifact decoration
Key: MRESOLVER-217
URL: https://issues.apache.org/jira/browse/MRESOLVER-217
Project: Maven Resolver
cstamas opened a new pull request #33:
URL: https://github.com/apache/maven-parent/pull/33
A "helper" profile that is meant to help for downstream projects
to ensure they are not depending on anything legacy, so to say
that they are future-proof.
--
This is an automated message from
cstamas opened a new pull request #32:
URL: https://github.com/apache/maven-parent/pull/32
Enforcer as is causes that downstream in case of update
POM must completely redefine plugin, thus, loosing all
the benefits of parent POM pluginMgmt.
Move plugin definition to pluginMgmt i
cstamas merged pull request #38:
URL: https://github.com/apache/maven-plugin-tools/pull/38
--
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.
To unsubscribe, e-mail: issues-
rfscholte commented on pull request #580:
URL: https://github.com/apache/maven/pull/580#issuecomment-943070478
I'm fine with these proposed changes, but we must discuss the reachitecture
of maven-wrapper on the dev-mailinglist!
--
This is an automated message from the Apache Git Service.
48 matches
Mail list logo