Tibor17 opened a new pull request #482:
URL: https://github.com/apache/maven-surefire/pull/482
Following this checklist to help us incorporate your
contribution quickly and easily:
- [ ] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/SUREFIRE) filed
slawekjaranowski commented on a change in pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#discussion_r816508964
##
File path:
src/main/java/org/apache/maven/shared/invoker/MavenCommandLineBuilder.java
##
@@ -104,6 +104,8 @@ public Commandline build(
[
https://issues.apache.org/jira/browse/MSHARED-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski updated MSHARED-1041:
-
Description:
We can replace methods like:
{code:java}
public InvocationRequest
dependabot[bot] closed pull request #39:
URL: https://github.com/apache/maven-invoker/pull/39
--
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:
dependabot[bot] opened a new pull request #44:
URL: https://github.com/apache/maven-invoker/pull/44
Bumps
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
from 3.1.2 to 3.2.2.
Commits
dependabot[bot] commented on pull request #39:
URL: https://github.com/apache/maven-invoker/pull/39#issuecomment-1055015016
Superseded by #44.
--
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
Hi David
Just for clarification: we are not relying on the maven dependency plugin
at runtime. Our runtime is perfectly clear of log4j vulnerabilities.
The problem is that our security scanners are scanning gitlab runner nodes
(virtual machines on which we compile and package our application) and
dependabot[bot] opened a new pull request #14:
URL: https://github.com/apache/maven-dependency-tree/pull/14
Bumps
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
from 3.1.2 to 3.2.2.
Commits
dependabot[bot] commented on pull request #11:
URL:
https://github.com/apache/maven-dependency-tree/pull/11#issuecomment-1054770375
Superseded by #14.
--
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
dependabot[bot] closed pull request #11:
URL: https://github.com/apache/maven-dependency-tree/pull/11
--
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,
olamy commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054754133
> I'm afraid that jacoco not working in IT tests with current
configuration ... maybe I'm wrong
I will have a look but yeah it looks not
--
This is an
[
https://issues.apache.org/jira/browse/MSHARED-1041?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499210#comment-17499210
]
Michael Osipov commented on MSHARED-1041:
-
Fantastic, you read my mind. Though consider that
slawekjaranowski opened a new pull request #105:
URL: https://github.com/apache/maven-invoker-plugin/pull/105
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
slawekjaranowski commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054735362
I'm afraid that jacoco not working in IT tests with current
configuration ... maybe I'm wrong
--
This is an automated message from the Apache Git Service.
[
https://issues.apache.org/jira/browse/MINVOKER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Slawomir Jaranowski reassigned MINVOKER-298:
Assignee: Slawomir Jaranowski
> Upgrade Maven Reporting to 3.1.0
>
dependabot[bot] commented on pull request #102:
URL:
https://github.com/apache/maven-invoker-plugin/pull/102#issuecomment-1054713765
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
slawekjaranowski closed pull request #102:
URL: https://github.com/apache/maven-invoker-plugin/pull/102
--
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,
dependabot[bot] commented on pull request #101:
URL:
https://github.com/apache/maven-invoker-plugin/pull/101#issuecomment-1054713618
OK, I won't notify you again about this release, but will get in touch when
a new version is available. If you'd rather skip all updates until the next
slawekjaranowski closed pull request #101:
URL: https://github.com/apache/maven-invoker-plugin/pull/101
--
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,
Slawomir Jaranowski created MINVOKER-298:
Summary: Upgrade Maven Reporting to 3.1.0
Key: MINVOKER-298
URL: https://issues.apache.org/jira/browse/MINVOKER-298
Project: Maven Invoker Plugin
olamy commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054711444
> Agree ... surefire code is enough complexity, we should reduce complexity
not increase.
>
> Next question how to test such code with coverage all decision branch?
slawekjaranowski commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054688231
Agree ... surefire code is enough complexity, we should reduce complexity
not increase.
Next question how to test such code with coverage all decision
[
https://issues.apache.org/jira/browse/SUREFIRE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499188#comment-17499188
]
Olivier Lamy commented on SUREFIRE-2027:
It's exactly the problem. It's performance test which
olamy commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054680670
> You added one more branching and you call `throwException`.
>
> Why?
>
> It has to end up with the only one exception - `BUILD ERROR` with no other
decision
olamy commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054670812
> Your thrown exception does not make sense, because there are two types,
just notice that. If it is a `BUILD FAILURE` then it has not to fail the build
because you
Slawomir Jaranowski created MSHARED-1041:
Summary: Refactor: remove duplicate code, use addArg internally
Key: MSHARED-1041
URL: https://issues.apache.org/jira/browse/MSHARED-1041
Project:
Slawomir Jaranowski created MSHARED-1040:
Summary: Require Java 8
Key: MSHARED-1040
URL: https://issues.apache.org/jira/browse/MSHARED-1040
Project: Maven Shared Components
Issue
michael-o commented on a change in pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#discussion_r816192410
##
File path:
src/main/java/org/apache/maven/shared/invoker/MavenCommandLineBuilder.java
##
@@ -104,6 +104,8 @@ public Commandline build(
Tibor17 commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054539564
You added one more branching and you call `throwException`.
Why?
It has to end up with the only one exception - `BUILD ERROR` with no other
decision making.
Tibor17 commented on pull request #478:
URL: https://github.com/apache/maven-surefire/pull/478#issuecomment-1054523389
Your thrown exception does not make sense, because there are two types, just
notice that.
If it is a `BUILD FAILURE` then it has not to fail the build because you
Tibor Digana created SUREFIRE-2028:
--
Summary: ShadeFire is missing
org.apache.maven.surefire:common-java5
Key: SUREFIRE-2028
URL: https://issues.apache.org/jira/browse/SUREFIRE-2028
Project: Maven
[
https://issues.apache.org/jira/browse/SUREFIRE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499066#comment-17499066
]
Tibor Digana commented on SUREFIRE-2027:
It has nothing to do with functional test as you have
[
https://issues.apache.org/jira/browse/SUREFIRE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499066#comment-17499066
]
Tibor Digana edited comment on SUREFIRE-2027 at 2/28/22, 5:34 PM:
--
It
[
https://issues.apache.org/jira/browse/SUREFIRE-2027?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499065#comment-17499065
]
Tibor Digana commented on SUREFIRE-2027:
[~olamy]
It is a performance test. And these are the
slawekjaranowski commented on a change in pull request #104:
URL:
https://github.com/apache/maven-invoker-plugin/pull/104#discussion_r816106236
##
File path: src/test/java/org/apache/maven/plugins/invoker/SelectorUtilsTest.java
##
@@ -120,26 +124,45 @@ public void
[
https://issues.apache.org/jira/browse/MDEP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499051#comment-17499051
]
Cristiano Gavião edited comment on MDEP-794 at 2/28/22, 5:29 PM:
-
I'm
[
https://issues.apache.org/jira/browse/MDEP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499054#comment-17499054
]
Cristiano Gavião commented on MDEP-794:
---
[^Deps.7z]
> It is not respecting the includeScope and
[
https://issues.apache.org/jira/browse/MDEP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cristiano Gavião updated MDEP-794:
--
Attachment: Deps.7z
> It is not respecting the includeScope and excludeScope
>
[
https://issues.apache.org/jira/browse/MDEP-794?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17499051#comment-17499051
]
Cristiano Gavião commented on MDEP-794:
---
I'm attaching two simple projects.
Below is the log
[
https://issues.apache.org/jira/browse/MNG-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498904#comment-17498904
]
Michael Osipov commented on MNG-7269:
-
Does MNG-5102 cover your needs?
> Add multiple inheritance of
Juraj,
I have run this command on your reproducer and in "tmp" I cannot find
log4j versions other then 2.17.1
mvn clean install -X -Dmaven.repo.local=tmp > out.txt
Enrico
Il giorno lun 28 feb 2022 alle ore 13:52 Juraj Veverka
ha scritto:
>
> Hi David
>
> Many thanks for your email, I really
dependabot[bot] closed pull request #49:
URL: https://github.com/apache/maven-jxr/pull/49
--
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:
dependabot[bot] commented on pull request #49:
URL: https://github.com/apache/maven-jxr/pull/49#issuecomment-1054241489
Superseded by #50.
--
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
dependabot[bot] opened a new pull request #50:
URL: https://github.com/apache/maven-jxr/pull/50
Bumps
[maven-project-info-reports-plugin](https://github.com/apache/maven-project-info-reports-plugin)
from 3.1.2 to 3.2.2.
Commits
Hi David
Many thanks for your email, I really appreciate your reply. This is an
isolated example of the problem.
https://github.com/jveverka/mvn-dependency-log4j
You can find all repro steps there. In case of any questions, feel free
to contact me.
Kind regards
Juraj Veverka
On Mon, Feb 28,
Where I work we decided to address log4j vulnerabilities only for components
directly used by the application and actually performing logging.
We ignored transitive dependencies and maven plug-ins.
I’m curious about this use case from Venu though, what application would rely
on the maven
michael-o commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054222556
@slawekjaranowski Yes, retain previous ones is correct, but new ones should
be:
```
invocationRequest.addArg("-B")
invocationRequest.addArg("-Dfoo=bar")
```
[
https://issues.apache.org/jira/browse/MNG-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498882#comment-17498882
]
Nils Breunese commented on MNG-7425:
Ah, great news!
> Maven artifact downloads sometimes result in
slawekjaranowski commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054187720
I don't parse argLinie, it is pass **as-is** to shared-utils -
`Commandline#createArg().setLine(...)`,
what happens in shared-utils is hidden for invoker
--
olamy commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054181225
uhm I tend to agree parsing could be a pain for something such
```
invocationRequest.setArgLineAtEnd("-e -B clean verify -Dfile=c:\\My
Files\grhhh windows");
```
slawekjaranowski commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054171627
Now I'm also confused
Do you think about `InvocationRequest` which contains method like
`setDebug`, `setOffline` ... and so on for other Maven
michael-o commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054151604
> No problem we can use array/list of String for argLine in
`InvocationRequest` next each element will be passed as-is to
`Argument#setValue`
>
>
[
https://issues.apache.org/jira/browse/MNG-7425?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498812#comment-17498812
]
Michael Osipov commented on MNG-7425:
-
This will go away with Maven 3.9.0. Search for my participation
[
https://issues.apache.org/jira/browse/MNG-7426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498805#comment-17498805
]
Christoph Läubrich commented on MNG-7426:
-
Also it would require another ticket I think this would
Mickael Istria created MNG-7426:
---
Summary: Allow condition (like ) on mojo executions
Key: MNG-7426
URL: https://issues.apache.org/jira/browse/MNG-7426
Project: Maven
Issue Type: Improvement
slawekjaranowski commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054055061
No problem we can use array/list of String for argLine in `InvocationRequest`
next each element will be passed as-is to `Argument#setValue`
michael-o commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054035376
What a brittle pain! This will fail sooner or later. I rather prefer an
arrray.
--
This is an automated message from the Apache Git Service.
To respond to the message,
slawekjaranowski commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054033868
You provide whole additional args as String.
argLine is passed to shared-utils - `Commandline#createArg()` and finally is
parsed by
olamy commented on a change in pull request #104:
URL:
https://github.com/apache/maven-invoker-plugin/pull/104#discussion_r815683991
##
File path: src/test/java/org/apache/maven/plugins/invoker/SelectorUtilsTest.java
##
@@ -120,26 +124,45 @@ public void
michael-o commented on pull request #43:
URL: https://github.com/apache/maven-invoker/pull/43#issuecomment-1054017750
I do not fully understand how this works. Can I set args one by one as with
a list/array?
--
This is an automated message from the Apache Git Service.
To respond to the
slawekjaranowski opened a new pull request #104:
URL: https://github.com/apache/maven-invoker-plugin/pull/104
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
Hi,
Please provide more information, like plugin, mven, os version.
We also need an example project which reproduces your issue.
When we can't reproduce we can't help.
pon., 28 lut 2022 o 08:55 Jaladi, Venumadhav
napisał(a):
> Hi team,
>
> Can I expect any response? Is this the right email
[
https://issues.apache.org/jira/browse/MNG-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498754#comment-17498754
]
zosrothko commented on MNG-7269:
Michael, what do you mean by "Did you check the ticket?" I do not
[ https://issues.apache.org/jira/browse/MNG-7269 ]
zosrothko deleted comment on MNG-7269:
was (Author: zosrothko):
Not yet tested. Will do by this week?
> Add multiple inheritance of parent projects
> ---
>
[
https://issues.apache.org/jira/browse/MNG-7269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17498753#comment-17498753
]
zosrothko commented on MNG-7269:
Not yet tested. Will do by this week?
> Add multiple inheritance of
65 matches
Mail list logo
