TimSijstermans opened a new pull request #75:
URL: https://github.com/apache/maven-enforcer/pull/75
- [ x ] I hereby declare this contribution to be licenced under the [Apache
License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0)
This rule ensures that the
royvanrijn opened a new pull request #72:
URL: https://github.com/apache/maven-enforcer/pull/72
Instead of combining fields of an artifact by appending fields I've changed
this to use artifact.toString() just as the dependency:tree plugin is doing.
Following this checklist to help
asfgit closed pull request #72:
URL: https://github.com/apache/maven-enforcer/pull/72
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
michael-o commented on a change in pull request #60:
URL: https://github.com/apache/maven-shared-utils/pull/60#discussion_r462164339
##
File path:
src/test/java/org/apache/maven/shared/utils/cli/CommandLineUtilsTest.java
##
@@ -168,4 +169,25 @@ private void assertCmdLineArgs(
royvanrijn opened a new pull request #74:
URL: https://github.com/apache/maven-enforcer/pull/74
The requireUpperBoundsDeps rule already had `excludes`, now we've added
`includes` as well. When no includes are present all dependecies are included.
If specific includes are listed only these
elharo opened a new pull request #19:
URL: https://github.com/apache/maven-dependency-analyzer/pull/19
@ian-lavallee
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
elharo opened a new pull request #19:
URL: https://github.com/apache/maven-changes-plugin/pull/19
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
ian-lavallee opened a new pull request #86:
URL: https://github.com/apache/maven-dependency-plugin/pull/86
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and
TimSijstermans opened a new pull request #76:
URL: https://github.com/apache/maven-enforcer/pull/76
The issue is about the RequireSameVersion rule; it claimed transitive
dependencies were not considered.
Added ITs to verify this is no longer an issues
Following this checklist
royvanrijn commented on pull request #74:
URL: https://github.com/apache/maven-enforcer/pull/74#issuecomment-665632286
I've tried to undo a lot of reformatting, although my IDE really wants to
remove trailing spaces... which isn't a bad thing IMHO.
michael-o commented on pull request #74:
URL: https://github.com/apache/maven-enforcer/pull/74#issuecomment-665633107
Trailing spaces are fine, but not adding linebreaks.
This is an automated message from the Apache Git
royvanrijn commented on pull request #72:
URL: https://github.com/apache/maven-enforcer/pull/72#issuecomment-665553160
Absolutely, I've followed the sample from:
https://issues.apache.org/jira/browse/MENFORCER-353
This is the before:
```[WARNING]
Dependency convergence
tocchipinti opened a new pull request #77:
URL: https://github.com/apache/maven-enforcer/pull/77
Following this checklist to help us incorporate your
contribution quickly and easily:
- [x] Make sure there is a [JIRA
issue](https://issues.apache.org/jira/browse/MENFORCER) filed
michael-o commented on pull request #72:
URL: https://github.com/apache/maven-enforcer/pull/72#issuecomment-665551217
This is an automated message from the Apache Git Service.
To respond to the message, please log on to
michael-o edited a comment on pull request #74:
URL: https://github.com/apache/maven-enforcer/pull/74#issuecomment-665633107
This is an automated message from the Apache Git Service.
To respond to the message, please log on
tocchipinti commented on pull request #73:
URL: https://github.com/apache/maven-enforcer/pull/73#issuecomment-665577083
> Drop reformatting please.
Fixed the reformatting that happend
This is an automated message from
ian-lavallee commented on pull request #80:
URL:
https://github.com/apache/maven-dependency-plugin/pull/80#issuecomment-665743730
This PR needs a 1.11.3-SNAPSHOT dependency-analyzer so that the test for
compileScopedTestDependencies passes. Currently it fails because in 1.11.2 the
nywitness commented on a change in pull request #60:
URL: https://github.com/apache/maven-shared-utils/pull/60#discussion_r462115011
##
File path:
src/test/java/org/apache/maven/shared/utils/cli/CommandLineUtilsTest.java
##
@@ -168,4 +169,25 @@ private void assertCmdLineArgs(
tocchipinti opened a new pull request #73:
URL: https://github.com/apache/maven-enforcer/pull/73
[MENFORCER-349] include JavaVendor in display-info output
Added the Java Vendor to the display-info goal
This pr gets the Java Vendor using `System.getProperty( "java.vendor" )`
elharo merged pull request #19:
URL: https://github.com/apache/maven-dependency-analyzer/pull/19
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL
asfgit closed pull request #73:
URL: https://github.com/apache/maven-enforcer/pull/73
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
[
https://issues.apache.org/jira/browse/MDEP-716?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold reassigned MDEP-716:
--
Assignee: Elliotte Rusty Harold
> TestListClassesMojo logs too much
>
Elliotte Rusty Harold created MDEP-718:
--
Summary: update maven-dependency-analyzer to 1.11.2
Key: MDEP-718
URL: https://issues.apache.org/jira/browse/MDEP-718
Project: Maven Dependency Plugin
[
https://issues.apache.org/jira/browse/MDEP-645?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MDEP-645:
---
Fix Version/s: 3.1.3
> List classes in a given artifact
>
[
https://issues.apache.org/jira/browse/MDEP-709?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MDEP-709:
---
Fix Version/s: 3.1.3
> Adding maven-resolver-api to dependency plugin breaks tests
>
[
https://issues.apache.org/jira/browse/MDEP-717?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MDEP-717:
---
Fix Version/s: 3.1.3
> Set minimum supported Maven version to 3.1.1
>
[
https://issues.apache.org/jira/browse/MSHARED-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold closed MSHARED-932.
-
> Remove JMock dependency
> ---
>
> Key:
[
https://issues.apache.org/jira/browse/MSHARED-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MSHARED-932.
---
Resolution: Fixed
> Remove JMock dependency
> ---
>
>
[
https://issues.apache.org/jira/browse/MSHARED-926?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MSHARED-926:
--
Priority: Major (was: Blocker)
> Maven invoker build stuck at compiling a
[
https://issues.apache.org/jira/browse/MSHARED-926?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167336#comment-17167336
]
Elliotte Rusty Harold commented on MSHARED-926:
---
Can you explain how we might reproduce
[
https://issues.apache.org/jira/browse/MSHARED-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167332#comment-17167332
]
Hudson commented on MSHARED-932:
Build succeeded in Jenkins: Maven TLP » maven-dependency-analyzer »
[
https://issues.apache.org/jira/browse/MSHARED-932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167331#comment-17167331
]
Hudson commented on MSHARED-932:
Build succeeded in Jenkins: Maven » Maven TLP »
[
https://issues.apache.org/jira/browse/MSHARED-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold updated MSHARED-932:
--
Fix Version/s: maven-dependency-analyzer-1.11.3
> Remove JMock dependency
>
[
https://issues.apache.org/jira/browse/MSHARED-932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold reassigned MSHARED-932:
-
Assignee: Elliotte Rusty Harold
> Remove JMock dependency
>
[
https://issues.apache.org/jira/browse/MENFORCER-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167232#comment-17167232
]
Roy van Rijn commented on MENFORCER-280:
The problem originates from the dependency-tree
[
https://issues.apache.org/jira/browse/MENFORCER-280?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167221#comment-17167221
]
Roy van Rijn commented on MENFORCER-280:
Two things:
First: I'm able to reproduce this and
[
https://issues.apache.org/jira/browse/MENFORCER-357?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ali Meshkat updated MENFORCER-357:
--
Attachment: sample-pom.xml
> RequirePluginVersions not recognizing versions-from-properties
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167195#comment-17167195
]
Hudson commented on MENFORCER-349:
--
Build succeeded in Jenkins: Maven TLP » maven-enforcer » master
[
https://issues.apache.org/jira/browse/MENFORCER-357?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167193#comment-17167193
]
Ali Meshkat commented on MENFORCER-357:
---
[~jbennett2091] Could you please provide also the full
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167191#comment-17167191
]
Hudson commented on MENFORCER-349:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer »
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MENFORCER-349.
Resolution: Fixed
Fixed with
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167173#comment-17167173
]
Michael Osipov edited comment on MENFORCER-349 at 7/29/20, 12:12 PM:
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167175#comment-17167175
]
Mark Symons commented on MENFORCER-349:
---
(y) Thanks for clarification
> Include Java vendor
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167173#comment-17167173
]
Michael Osipov commented on MENFORCER-349:
--
You are confusing two JVM distribution and JVM
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167161#comment-17167161
]
Mark Symons commented on MENFORCER-349:
---
I have read [PR
[
https://issues.apache.org/jira/browse/MRESOURCES-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167155#comment-17167155
]
Dennis Lundberg commented on MRESOURCES-264:
Hi,
We have an integration test in place
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167153#comment-17167153
]
Michael Osipov commented on MENFORCER-349:
--
{{java.vendor}} will give you that information.
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167151#comment-17167151
]
Mark Symons commented on MENFORCER-349:
---
In a single sentence: when I use the {{display-info}}
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167148#comment-17167148
]
Michael Osipov commented on MENFORCER-349:
--
[~marks], I do not fully understand what you are
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167144#comment-17167144
]
Mark Symons commented on MENFORCER-349:
---
[~michael-o], I am not a dev and whilst I referenced
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MENFORCER-349:
-
Summary: Include Java vendor in display-info output (was: include Java
vendor in
[
https://issues.apache.org/jira/browse/MENFORCER-352?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167115#comment-17167115
]
Tim Occhipinti commented on MENFORCER-352:
--
Fixed in
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MENFORCER-349:
-
Summary: include Java vendor in display-info output (was: include
JavaVendor in
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MENFORCER-349:
-
Fix Version/s: 3.0.0-M4
> include JavaVendor in display-info output
>
[
https://issues.apache.org/jira/browse/MENFORCER-349?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MENFORCER-349:
Assignee: Michael Osipov
> include JavaVendor in display-info output
>
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167109#comment-17167109
]
Hudson commented on MENFORCER-353:
--
Build succeeded in Jenkins: Maven » Maven TLP » maven-enforcer »
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167108#comment-17167108
]
Hudson commented on MENFORCER-353:
--
Build failed in Jenkins: Maven TLP » maven-enforcer » master #152
[
https://issues.apache.org/jira/browse/MENFORCER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold closed MENFORCER-256.
---
> BannedDependencies does not work with wildcard strings
>
[
https://issues.apache.org/jira/browse/MENFORCER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Elliotte Rusty Harold resolved MENFORCER-256.
-
Resolution: Fixed
> BannedDependencies does not work with wildcard
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MENFORCER-353.
Resolution: Fixed
Fixed with
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MENFORCER-353:
-
Fix Version/s: (was: 3.0.0)
3.0.0-M4
> Consistently format
[
https://issues.apache.org/jira/browse/MENFORCER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167096#comment-17167096
]
Roy van Rijn edited comment on MENFORCER-256 at 7/29/20, 10:01 AM:
---
[
https://issues.apache.org/jira/browse/MENFORCER-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167096#comment-17167096
]
Roy van Rijn commented on MENFORCER-256:
I've revisted and tested this issue, with newer Maven
[
https://issues.apache.org/jira/browse/MRELEASE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167081#comment-17167081
]
Michael Osipov commented on MRELEASE-1054:
--
As far as I remember, SCM does not really support
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MENFORCER-353:
Assignee: Michael Osipov
> DependencyConvergence - should display artifact
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MENFORCER-353:
-
Summary: Consistently format artifacts same as dependency:tree (was:
[
https://issues.apache.org/jira/browse/MENFORCER-353?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MENFORCER-353:
-
Fix Version/s: 3.0.0
> DependencyConvergence - should display artifact classifier in
Joël Royer created MRESOURCES-264:
-
Summary: Parameter addDefaultExcludes with false does not copy
.gitignore
Key: MRESOURCES-264
URL: https://issues.apache.org/jira/browse/MRESOURCES-264
Project:
[
https://issues.apache.org/jira/browse/MNG-6970?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17167079#comment-17167079
]
Dennis Lundberg commented on MNG-6970:
--
If the above command fails, then I think that your Maven
michael-o commented on a change in pull request #60:
URL: https://github.com/apache/maven-shared-utils/pull/60#discussion_r461593712
##
File path:
src/test/java/org/apache/maven/shared/utils/cli/CommandLineUtilsTest.java
##
@@ -168,4 +169,25 @@ private void assertCmdLineArgs(
elharo merged pull request #2:
URL: https://github.com/apache/maven-mapping/pull/2
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
nywitness commented on pull request #60:
URL: https://github.com/apache/maven-shared-utils/pull/60#issuecomment-664713924
elharo opened a new pull request #4:
URL: https://github.com/apache/maven-mapping/pull/4
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
elharo opened a new pull request #2:
URL: https://github.com/apache/maven-mapping/pull/2
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
elharo merged pull request #3:
URL: https://github.com/apache/maven-mapping/pull/3
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
elharo opened a new pull request #3:
URL: https://github.com/apache/maven-mapping/pull/3
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
elharo merged pull request #4:
URL: https://github.com/apache/maven-mapping/pull/4
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
elharo merged pull request #1:
URL: https://github.com/apache/maven-mapping/pull/1
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
elharo opened a new pull request #1:
URL: https://github.com/apache/maven-mapping/pull/1
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
[
https://issues.apache.org/jira/browse/MRELEASE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cau Ta updated MRELEASE-1054:
-
Description:
*My project structure:*
{{parent (git scm repo parent.git)}}
{{-- git submodule A (git
[
https://issues.apache.org/jira/browse/MRELEASE-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Cau Ta updated MRELEASE-1054:
-
Description:
*My project structure:*
{{parent (git scm repo parent.git)}}
{{-- git submodule A (git
Cau Ta created MRELEASE-1054:
Summary: [Git submodule] Wrong Change on scm submodule after
release:prepare and failed on pushChange
Key: MRELEASE-1054
URL: https://issues.apache.org/jira/browse/MRELEASE-1054
[
https://issues.apache.org/jira/browse/MNGSITE-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dennis Lundberg updated MNGSITE-419:
Description:
When I released maven-shared-utils I stumbled across a couple of things in
83 matches
Mail list logo
