[jira] [Reopened] (MRESOLVER-10) New class 'TransitiveDependencyManager' supporting transitive dependency management.
[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy reopened MRESOLVER-10:
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
>
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> The {{ClassicDependencyManager}} ignores the dependency management from
> transitive dependencies to maintain backwards compatibility with Maven 2. The
> {{TransitiveDependencyManager}} will correctly use that dependency management
> (it could also be named {{DefaultDependencyManager}}).
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MRESOLVER-10) New class 'TransitiveDependencyManager' supporting transitive dependency management.
[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy closed MRESOLVER-10.
--
Resolution: Fixed
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
>
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> The {{ClassicDependencyManager}} ignores the dependency management from
> transitive dependencies to maintain backwards compatibility with Maven 2,
> then Maven 3 (objective when extracting Aether was to keep compatibility).
> The new {{TransitiveDependencyManager}} will use that dependency management:
> this new behaviour is expected to be a better choice.
> It could also be named {{DefaultDependencyManager}}, once it is integrated
> into Maven core (version to be defined) as default new behaviour = a
> behaviour that is more predictible/logical, but that will break some
> previously working builds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MRESOLVER-10) New class 'TransitiveDependencyManager' supporting transitive dependency management.
[
https://issues.apache.org/jira/browse/MRESOLVER-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MRESOLVER-10:
---
Description:
The {{ClassicDependencyManager}} ignores the dependency management from
transitive dependencies to maintain backwards compatibility with Maven 2, then
Maven 3 (objective when extracting Aether was to keep compatibility).
The new {{TransitiveDependencyManager}} will use that dependency management:
this new behaviour is expected to be a better choice.
It could also be named {{DefaultDependencyManager}}, once it is integrated into
Maven core (version to be defined) as default new behaviour = a behaviour that
is more predictible/logical, but that will break some previously working builds.
was:
The {{ClassicDependencyManager}} ignores the dependency management from
transitive dependencies to maintain backwards compatibility with Maven 2. The
{{TransitiveDependencyManager}} will correctly use that dependency management
(it could also be named {{DefaultDependencyManager}}).
> New class 'TransitiveDependencyManager' supporting transitive dependency
> management.
>
>
> Key: MRESOLVER-10
> URL: https://issues.apache.org/jira/browse/MRESOLVER-10
> Project: Maven Resolver
> Issue Type: New Feature
> Components: resolver
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: Maven Artifact Resolver 1.2.0
>
>
> The {{ClassicDependencyManager}} ignores the dependency management from
> transitive dependencies to maintain backwards compatibility with Maven 2,
> then Maven 3 (objective when extracting Aether was to keep compatibility).
> The new {{TransitiveDependencyManager}} will use that dependency management:
> this new behaviour is expected to be a better choice.
> It could also be named {{DefaultDependencyManager}}, once it is integrated
> into Maven core (version to be defined) as default new behaviour = a
> behaviour that is more predictible/logical, but that will break some
> previously working builds.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #49 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/49/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 06580630a3b09143770fd8eeda6c86f70a016f4d)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
)
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #45 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/45/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 14bff2c5c5a0729e39f7d0fc62ed733222c90a18)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
)
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #48 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/48/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev bbffde98fdf3c46d7698c300ca074ed980fa921e)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
)
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #44 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/44/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 9fef375bb0947bdc8ae5ca1ffe5b69d3fd31a4ab)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
)
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #47 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/47/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 80f2fd6375ad5311031929c1bbaf87aa42a3c53a)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
)
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #42 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/42/])
[MNG-6135] Maven plugins are not dependencies, they should be resolved
(schulte: rev ead960adbc28b7e191449e2712ca9766cf0ec96c)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java
* (edit) maven-core/src/main/java/org/apache/maven/RepositoryUtils.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java
)
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6135:
---
Description:
Due to a bug in the Maven resolver, plugin and core extensions were resolved
incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
Ironically, this fix breaks some plugins because direct {{test}} dependencies
now take precedence over transitive {{compile}} one...
was:
Due to a bug in the Maven resolver, plugin and core extensions were resolved
incorrectly. The direct {{test}} and {{provided}} dependencies were ignored.
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756112#comment-15756112
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:39 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1450 (See
[https://builds.apache.org/job/maven-3.x/1450/])
[MNG-6135] Maven plugins are not dependencies, they should be resolved
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/ead960adbc28b7e191449e2712ca9766cf0ec96c)
* (edit) maven-core/src/main/java/org/apache/maven/RepositoryUtils.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1450 (See
[https://builds.apache.org/job/maven-3.x/1450/])
[MNG-6135] Maven plugins are not dependencies, they should be resolved
(schulte: rev ead960adbc28b7e191449e2712ca9766cf0ec96c)
* (edit) maven-core/src/main/java/org/apache/maven/RepositoryUtils.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756277#comment-15756277
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:40 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1452 (See
[https://builds.apache.org/job/maven-3.x/1452/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/9fef375bb0947bdc8ae5ca1ffe5b69d3fd31a4ab)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1452 (See
[https://builds.apache.org/job/maven-3.x/1452/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 9fef375bb0947bdc8ae5ca1ffe5b69d3fd31a4ab)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758103#comment-15758103
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:40 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1456 (See
[https://builds.apache.org/job/maven-3.x/1456/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/80f2fd6375ad5311031929c1bbaf87aa42a3c53a)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1456 (See
[https://builds.apache.org/job/maven-3.x/1456/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 80f2fd6375ad5311031929c1bbaf87aa42a3c53a)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/PlexusUtilsInjector.java
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/WagonExcluder.java
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 286c7ffba1696053274c5da6cad4336f678fceee)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756466#comment-15756466
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:40 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1453 (See
[https://builds.apache.org/job/maven-3.x/1453/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/14bff2c5c5a0729e39f7d0fc62ed733222c90a18)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1453 (See
[https://builds.apache.org/job/maven-3.x/1453/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 14bff2c5c5a0729e39f7d0fc62ed733222c90a18)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15756217#comment-15756217
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:40 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1451 (See
[https://builds.apache.org/job/maven-3.x/1451/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/15a947faeca03c74505605c290e821b0d7a59dc3)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1451 (See
[https://builds.apache.org/job/maven-3.x/1451/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 15a947faeca03c74505605c290e821b0d7a59dc3)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15766068#comment-15766068
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:41 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1466 (See
[https://builds.apache.org/job/maven-3.x/1466/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/e8a0af6e649b21a8fd5f7d59ef8b559ed39fcf16)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1466 (See
[https://builds.apache.org/job/maven-3.x/1466/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev e8a0af6e649b21a8fd5f7d59ef8b559ed39fcf16)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758251#comment-15758251
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:41 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1459 (See
[https://builds.apache.org/job/maven-3.x/1459/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/06580630a3b09143770fd8eeda6c86f70a016f4d)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1459 (See
[https://builds.apache.org/job/maven-3.x/1459/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev 06580630a3b09143770fd8eeda6c86f70a016f4d)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6135) Maven plugins and core extensions are not dependencies, they should be resolved the same way as projects.
[
https://issues.apache.org/jira/browse/MNG-6135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15758160#comment-15758160
]
Hervé Boutemy edited comment on MNG-6135 at 12/26/16 1:40 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1457 (See
[https://builds.apache.org/job/maven-3.x/1457/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev
http://git-wip-us.apache.org/repos/asf/maven/commit/bbffde98fdf3c46d7698c300ca074ed980fa921e)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1457 (See
[https://builds.apache.org/job/maven-3.x/1457/])
[MNG-6135] Maven plugins and core extensions are not dependencies, they
(schulte: rev bbffde98fdf3c46d7698c300ca074ed980fa921e)
* (edit)
maven-core/src/main/java/org/apache/maven/plugin/internal/DefaultPluginDependenciesResolver.java
> Maven plugins and core extensions are not dependencies, they should be
> resolved the same way as projects.
> -
>
> Key: MNG-6135
> URL: https://issues.apache.org/jira/browse/MNG-6135
> Project: Maven
> Issue Type: Bug
>Reporter: Christian Schulte
>Assignee: Christian Schulte
>Priority: Critical
> Fix For: 3.4.0
>
>
> Due to a bug in the Maven resolver, plugin and core extensions were resolved
> incorrectly: the direct {{test}} and {{provided}} dependencies were ignored.
> Ironically, this fix breaks some plugins because direct {{test}} dependencies
> now take precedence over transitive {{compile}} one...
>
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MWAR-200) Filtering resource don't work as expected
[
https://issues.apache.org/jira/browse/MWAR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MWAR-200:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-plugins #7819 (See
[https://builds.apache.org/job/maven-plugins/7819/])
[MWAR-200] Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2.
(schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1775963])
* (edit)
maven-war-plugin/src/main/resources-filtered/META-INF/plexus/components.xml
)
> Filtering resource don't work as expected
> -
>
> Key: MWAR-200
> URL: https://issues.apache.org/jira/browse/MWAR-200
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.1-alpha-1, 2.1-beta-1
> Environment: windows and unix
>Reporter: hugo lassiege
> Attachments: toto.txt
>
>
> Hi,
> I try to use maven war plugin and cargo however I have a problem with
> maven-war-plugin and the filtering.
> I tried with 2.1-beta-1 and alpha1
> My configuration for the maven-war-plugin is the following :
> {code:xml}
>
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1-beta-1
>
>
>
>
> ${basedir}/src/main/webapp/META-INF
> true
>
> context.xml
>
> META-INF/
>
>
>
>
> {code}
> My goal is to filter the context.xml to modify the name of the datasource
> My context.xml unfiltered is :
> {code:xml}
>
>
>factory="org.apache.commons.dbcp.BasicDataSourceFactory"
> type="javax.sql.DataSource"
> driverClassName="${connection.driver_class}"
> url="${connection.url}" username="${connection.username}"
> password="${connection.password}" maxActive="50" maxIdle="2"
> maxWait="1" />
>
> {code}
> I use mvn clean install to launch the build
> In DEBUG mode I have :
> {code}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-war-plugin:2.1-alpha-1:war' -->
> [DEBUG] (f) addDefaultSpecificationEntries = true
> [DEBUG] (f) addDefaultImplementationEntries = true
> [DEBUG] (s) manifest =
> org.apache.maven.archiver.ManifestConfiguration@1d50fd2
> [DEBUG] (f) archive =
> org.apache.maven.archiver.MavenArchiveConfiguration@101ac1c
> [DEBUG] (s) archiveClasses = true
> [DEBUG] (s) cacheFile =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\war\work\webapp-cache.xml
> [DEBUG] (s) classesDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\classes
> [DEBUG] (s) filters = []
> [DEBUG] (f) outputDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target
> [DEBUG] (f) primaryArtifact = true
> [DEBUG] (s) project = MavenProject:
> fr.sgf.wit:webintake-security-integration:3.5.0-alpha3-SNAPSHOT @
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\pom.xml
> [DEBUG] (s) useCache = true
> [DEBUG] (f) warName = webintake-security-integration-3.5.0-alpha3-SNAPSHOT
> [DEBUG] (s) warSourceDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\src\main\webapp
> [DEBUG] (s) directory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF
> [DEBUG] (s) filtering = true
> [DEBUG] (s) includes = [context.xml]
> [DEBUG] (s) targetPath = META-INF/
> [DEBUG] (s) webResources = [Resource {targetPath: META-INF/, filtering:
> true, FileSet {directory:
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF,
> PatternSet [includes: {context.xml}, excludes: {}]}}]
> [DEBUG] (s) webappDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT
> [DEBUG] (s) workDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\war\work
> [DEBUG] -- end configuration --
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[webintake-security-integration] in
> [E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT]
> [INFO] Processing war project
> [INFO] Copy webapp
> webResources[E:\Developpement\checkout\webintakeTrunk\webintake-secur
[jira] [Issue Comment Deleted] (MWAR-200) Filtering resource don't work as expected
[
https://issues.apache.org/jira/browse/MWAR-200?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MWAR-200:
---
Comment: was deleted
(was: [~schulte77], does it solve this issue?)
> Filtering resource don't work as expected
> -
>
> Key: MWAR-200
> URL: https://issues.apache.org/jira/browse/MWAR-200
> Project: Maven WAR Plugin
> Issue Type: Bug
> Components: filtering
>Affects Versions: 2.1-alpha-1, 2.1-beta-1
> Environment: windows and unix
>Reporter: hugo lassiege
> Attachments: toto.txt
>
>
> Hi,
> I try to use maven war plugin and cargo however I have a problem with
> maven-war-plugin and the filtering.
> I tried with 2.1-beta-1 and alpha1
> My configuration for the maven-war-plugin is the following :
> {code:xml}
>
>
> org.apache.maven.plugins
> maven-war-plugin
> 2.1-beta-1
>
>
>
>
> ${basedir}/src/main/webapp/META-INF
> true
>
> context.xml
>
> META-INF/
>
>
>
>
> {code}
> My goal is to filter the context.xml to modify the name of the datasource
> My context.xml unfiltered is :
> {code:xml}
>
>
>factory="org.apache.commons.dbcp.BasicDataSourceFactory"
> type="javax.sql.DataSource"
> driverClassName="${connection.driver_class}"
> url="${connection.url}" username="${connection.username}"
> password="${connection.password}" maxActive="50" maxIdle="2"
> maxWait="1" />
>
> {code}
> I use mvn clean install to launch the build
> In DEBUG mode I have :
> {code}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-war-plugin:2.1-alpha-1:war' -->
> [DEBUG] (f) addDefaultSpecificationEntries = true
> [DEBUG] (f) addDefaultImplementationEntries = true
> [DEBUG] (s) manifest =
> org.apache.maven.archiver.ManifestConfiguration@1d50fd2
> [DEBUG] (f) archive =
> org.apache.maven.archiver.MavenArchiveConfiguration@101ac1c
> [DEBUG] (s) archiveClasses = true
> [DEBUG] (s) cacheFile =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\war\work\webapp-cache.xml
> [DEBUG] (s) classesDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\classes
> [DEBUG] (s) filters = []
> [DEBUG] (f) outputDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target
> [DEBUG] (f) primaryArtifact = true
> [DEBUG] (s) project = MavenProject:
> fr.sgf.wit:webintake-security-integration:3.5.0-alpha3-SNAPSHOT @
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\pom.xml
> [DEBUG] (s) useCache = true
> [DEBUG] (f) warName = webintake-security-integration-3.5.0-alpha3-SNAPSHOT
> [DEBUG] (s) warSourceDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\src\main\webapp
> [DEBUG] (s) directory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF
> [DEBUG] (s) filtering = true
> [DEBUG] (s) includes = [context.xml]
> [DEBUG] (s) targetPath = META-INF/
> [DEBUG] (s) webResources = [Resource {targetPath: META-INF/, filtering:
> true, FileSet {directory:
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF,
> PatternSet [includes: {context.xml}, excludes: {}]}}]
> [DEBUG] (s) webappDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT
> [DEBUG] (s) workDirectory =
> E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\war\work
> [DEBUG] -- end configuration --
> [INFO] [war:war]
> [INFO] Packaging webapp
> [INFO] Assembling webapp[webintake-security-integration] in
> [E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT]
> [INFO] Processing war project
> [INFO] Copy webapp
> webResources[E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration/src/main/webapp/META-INF]
>
> to[E:\Developpement\checkout\webintakeTrunk\webintake-security\webintake-security-integration\target\webintake-security-integration-3.5.0-alpha3-SNAPSHOT]
> [DEBUG] + META-INF/\context.xml has been copied.
> [DEBUG] + META-INF/context.xm
[jira] [Commented] (MWAR-400) Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2.
[ https://issues.apache.org/jira/browse/MWAR-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778359#comment-15778359 ] Hervé Boutemy commented on MWAR-400: SUCCESS: Integrated in Jenkins build maven-plugins #7819 (See [https://builds.apache.org/job/maven-plugins/7819/]) [MWAR-400] Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2. (schulte: [http://svn.apache.org/viewvc/?view=rev&rev=1775963]) * (edit) maven-war-plugin/src/main/resources-filtered/META-INF/plexus/components.xml > Upgrade the WAR lifecycle to use the maven-resources-plugin 3.0.2. > -- > > Key: MWAR-400 > URL: https://issues.apache.org/jira/browse/MWAR-400 > Project: Maven WAR Plugin > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Blocker > Fix For: next-release > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6127: --- Comment: was deleted (was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #22 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/22/]) [MNG-6127] Fix plugin execution configuration interference (schulte: rev http://git-wip-us.apache.org/repos/asf/maven/commit/70653f3e46f7779e10a71517e7da8ac4d004c0bd) * (edit) maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java ) > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Christian Schulte > Fix For: 3.4.0 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692504#comment-15692504 ] Hervé Boutemy edited comment on MNG-6127 at 12/26/16 1:46 PM: -- SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #22 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/22/]) [MNG-6127] Fix plugin execution configuration interference (schulte: rev http://git-wip-us.apache.org/repos/asf/maven/commit/70653f3e46f7779e10a71517e7da8ac4d004c0bd) * (edit) maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java was (Author: hudson): SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #22 (See [https://builds.apache.org/job/maven-3.x%20Jigsaw/22/]) [MNG-6127] Fix plugin execution configuration interference (schulte: rev 70653f3e46f7779e10a71517e7da8ac4d004c0bd) * (edit) maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Christian Schulte > Fix For: 3.4.0 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15692517#comment-15692517 ] Hervé Boutemy edited comment on MNG-6127 at 12/26/16 1:47 PM: -- SUCCESS: Integrated in Jenkins build maven-3.x #1423 (See [https://builds.apache.org/job/maven-3.x/1423/]) [MNG-6127] Fix plugin execution configuration interference (schulte: rev http://git-wip-us.apache.org/repos/asf/maven/commit/70653f3e46f7779e10a71517e7da8ac4d004c0bd) * (edit) maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java was (Author: hudson): SUCCESS: Integrated in Jenkins build maven-3.x #1423 (See [https://builds.apache.org/job/maven-3.x/1423/]) [MNG-6127] Fix plugin execution configuration interference (schulte: rev 70653f3e46f7779e10a71517e7da8ac4d004c0bd) * (edit) maven-core/src/main/java/org/apache/maven/lifecycle/internal/DefaultLifecyclePluginAnalyzer.java > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Christian Schulte > Fix For: 3.4.0 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1316) MVN 3.1.0 minimum in build time
Tibor Digana created SUREFIRE-1316:
--
Summary: MVN 3.1.0 minimum in build time
Key: SUREFIRE-1316
URL: https://issues.apache.org/jira/browse/SUREFIRE-1316
Project: Maven Surefire
Issue Type: Task
Reporter: Tibor Digana
Assignee: Tibor Digana
Fix For: 2.19.2
The build still does not crash with MVN 3.0.x but the logs are hard to read.
Due to the Maven 3.0.x reports console messages on a new line like this:
{quote}
info
Message on new line.
{quote}
project starts using Maven 3.1.x in build time.
The users still can use MVN 3.0.x in runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SUREFIRE-1317) Refactoring
Tibor Digana created SUREFIRE-1317: -- Summary: Refactoring Key: SUREFIRE-1317 URL: https://issues.apache.org/jira/browse/SUREFIRE-1317 Project: Maven Surefire Issue Type: Improvement Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1318) Upgrade JaCoCo Version to 0.7.8
Tibor Digana created SUREFIRE-1318: -- Summary: Upgrade JaCoCo Version to 0.7.8 Key: SUREFIRE-1318 URL: https://issues.apache.org/jira/browse/SUREFIRE-1318 Project: Maven Surefire Issue Type: Task Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1270) Upgrade JaCoCo Version to 0.7.7
[ https://issues.apache.org/jira/browse/SUREFIRE-1270?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1270: --- Issue Type: Task (was: Improvement) > Upgrade JaCoCo Version to 0.7.7 > --- > > Key: SUREFIRE-1270 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1270 > Project: Maven Surefire > Issue Type: Task > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (SUREFIRE-1318) Upgrade JaCoCo Version to 0.7.8
[ https://issues.apache.org/jira/browse/SUREFIRE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana updated SUREFIRE-1318: --- Component/s: Maven Surefire Report Plugin Maven Surefire Plugin Maven Failsafe Plugin > Upgrade JaCoCo Version to 0.7.8 > --- > > Key: SUREFIRE-1318 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1318 > Project: Maven Surefire > Issue Type: Task > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1319) Upgrade RAT Plugin Version to 0.12
Tibor Digana created SUREFIRE-1319: -- Summary: Upgrade RAT Plugin Version to 0.12 Key: SUREFIRE-1319 URL: https://issues.apache.org/jira/browse/SUREFIRE-1319 Project: Maven Surefire Issue Type: Task Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1320) Upgrade Sniffer Plugin Version to 1.15
Tibor Digana created SUREFIRE-1320: -- Summary: Upgrade Sniffer Plugin Version to 1.15 Key: SUREFIRE-1320 URL: https://issues.apache.org/jira/browse/SUREFIRE-1320 Project: Maven Surefire Issue Type: Task Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1321) Integration tests should be cleaned up before running. Add goal=clean in maven-invoker-plugin.
Tibor Digana created SUREFIRE-1321: -- Summary: Integration tests should be cleaned up before running. Add goal=clean in maven-invoker-plugin. Key: SUREFIRE-1321 URL: https://issues.apache.org/jira/browse/SUREFIRE-1321 Project: Maven Surefire Issue Type: Task Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1322) Surefire and Failsafe should dump critical errors in dump file and console
Tibor Digana created SUREFIRE-1322: -- Summary: Surefire and Failsafe should dump critical errors in dump file and console Key: SUREFIRE-1322 URL: https://issues.apache.org/jira/browse/SUREFIRE-1322 Project: Maven Surefire Issue Type: Bug Reporter: Tibor Digana Assignee: Tibor Digana Fix For: 2.19.2 Both plugins, Surefire and Failsafe, dump stack trace and error messages and lost commands in dump file or in console: [date]-jvmRun[N].dump, [date].dumpstream and [date]-jvmRun[N].dumpstream IN previous versions the plugins threw exceptions like, MojoExecutionException and MojoFailureException, but the user could not see any message of error which killed the plugin internally. Since now this is possible and the user can see the dump files in target target/failsafe-reports and target/surefire-reports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6115) Add Jansi native library search path to our start scripts
[
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6115:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #11 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/11/])
[MNG-6115] Add Jansi native library search path to our start scripts (michaelo:
rev 3d4cd94450e167953c40028eaf1c71ce7a7cafc7)
* (edit) apache-maven/src/bin/mvn.cmd
* (edit) apache-maven/src/bin/mvn
)
> Add Jansi native library search path to our start scripts
> -
>
> Key: MNG-6115
> URL: https://issues.apache.org/jira/browse/MNG-6115
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build, Command Line
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
>
> By default Jansi extracts the native, shared library to temp which results in
> unnecessary file I/O and a huge amount of temp files when Maven is run very
> often. One can avoid that by adding
> {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib}} to the start script. The user
> has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the
> overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Comment Edited] (MNG-6115) Add Jansi native library search path to our start scripts
[
https://issues.apache.org/jira/browse/MNG-6115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15662060#comment-15662060
]
Hervé Boutemy edited comment on MNG-6115 at 12/26/16 3:10 PM:
--
SUCCESS: Integrated in Jenkins build maven-3.x #1412 (See
[https://builds.apache.org/job/maven-3.x/1412/])
[MNG-6115] Add Jansi native library search path to our start scripts (michaelo:
rev
http://git-wip-us.apache.org/repos/asf/maven/3d4cd94450e167953c40028eaf1c71ce7a7cafc7)
* (edit) apache-maven/src/bin/mvn
* (edit) apache-maven/src/bin/mvn.cmd
was (Author: hudson):
SUCCESS: Integrated in Jenkins build maven-3.x #1412 (See
[https://builds.apache.org/job/maven-3.x/1412/])
[MNG-6115] Add Jansi native library search path to our start scripts (michaelo:
rev 3d4cd94450e167953c40028eaf1c71ce7a7cafc7)
* (edit) apache-maven/src/bin/mvn
* (edit) apache-maven/src/bin/mvn.cmd
> Add Jansi native library search path to our start scripts
> -
>
> Key: MNG-6115
> URL: https://issues.apache.org/jira/browse/MNG-6115
> Project: Maven
> Issue Type: Improvement
> Components: Bootstrap & Build, Command Line
>Affects Versions: 3.4.0
>Reporter: Michael Osipov
>Assignee: Michael Osipov
> Fix For: 3.4.0
>
>
> By default Jansi extracts the native, shared library to temp which results in
> unnecessary file I/O and a huge amount of temp files when Maven is run very
> often. One can avoid that by adding
> {{-Dlibrary.jansi.path=$\{MAVEN_HOME\}/lib}} to the start script. The user
> has to copy the {{libjansi.so}} or {{jansi.dll}} once and will avoid the
> overhead.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Issue Comment Deleted] (MNG-6117) ${session.parallel} not correctly set
[
https://issues.apache.org/jira/browse/MNG-6117?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6117:
---
Comment: was deleted
(was: SUCCESS: Integrated in Jenkins build maven-3.x Jigsaw #13 (See
[https://builds.apache.org/job/maven-3.x%20Jigsaw/13/])
[MNG-6117] ${session.parallel} not correctly set (gboue: rev
dfb4a7b7f4225bc32385da139679e189a2aeb79a)
* (edit)
maven-core/src/main/java/org/apache/maven/lifecycle/internal/builder/multithreaded/MultiThreadedBuilder.java
)
> ${session.parallel} not correctly set
> -
>
> Key: MNG-6117
> URL: https://issues.apache.org/jira/browse/MNG-6117
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.3.9
>Reporter: Richard Raumberger
>Assignee: Guillaume Boué
> Fix For: 3.4.0
>
>
> Running {{mvn help:evaluate -T 3}} and resolving the property
> {{session.parallel}} returns {{true}} when run with Maven 3.0.5.
> When running it with 3.3.9, this property resolves to {{false}}.
> {code}
> mvn help:evaluate -T 3
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the MultiThreadedBuilder implementation with a thread count of 3
> [INFO]
> [INFO]
>
> [INFO] Building Maven Stub Project (No POM) 1
> [INFO]
>
> [INFO]
> [INFO] --- maven-help-plugin:2.2:evaluate (default-cli) @ standalone-pom ---
> [INFO] No artifact parameter specified, using
> 'org.apache.maven:standalone-pom:pom:1' as project.
> [INFO] Enter the Maven expression i.e. ${project.groupId} or 0 to exit?:
> ${session.parallel}
> [INFO]
> false
> {code}
> E.g. Surefire
> [relies|https://github.com/apache/maven-surefire/blob/fb9b699e27dae905393a5bc4d5c6ae39606c3172/maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java#L658]
> on this property, to check whether Maven is running in parallel mode, as
> mentioned in the comments of
> [SUREFIRE-1301|https://issues.apache.org/jira/browse/SUREFIRE-1301].
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (SUREFIRE-1323) Java 1.6 for improved XML parser needed in SUREFIRE-1322
Tibor Digana created SUREFIRE-1323: -- Summary: Java 1.6 for improved XML parser needed in SUREFIRE-1322 Key: SUREFIRE-1323 URL: https://issues.apache.org/jira/browse/SUREFIRE-1323 Project: Maven Surefire Issue Type: Bug Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven Surefire Report Plugin Reporter: Tibor Digana Assignee: Tibor Digana The Failsafe plugins used parser which threw exception in verification goal. This exception was expected to have a message from a stacktrace stored in failsafe-summary.xml. It was impossible to separate exception message from stack trace line because DOM parser did not split the test having new lines and therefore it looked like one big text. Therefore we use JAXB introduced in Java 1.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1316) MVN 3.1.0 minimum in build time
[
https://issues.apache.org/jira/browse/SUREFIRE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1316.
--
Resolution: Fixed
https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=137029531f22e65cb9bb841aa62ca859441b0b14
> MVN 3.1.0 minimum in build time
> ---
>
> Key: SUREFIRE-1316
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1316
> Project: Maven Surefire
> Issue Type: Task
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> The build still does not crash with MVN 3.0.x but the logs are hard to read.
> Due to the Maven 3.0.x reports console messages on a new line like this:
> {quote}
> info
> Message on new line.
> {quote}
> project starts using Maven 3.1.x in build time.
> The users still can use MVN 3.0.x in runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1317) Refactoring
[ https://issues.apache.org/jira/browse/SUREFIRE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1317. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=0d90d9755c3308aaa328a948ce7e14011f426453 > Refactoring > --- > > Key: SUREFIRE-1317 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1317 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1318) Upgrade JaCoCo Version to 0.7.8
[ https://issues.apache.org/jira/browse/SUREFIRE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1318. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=738976c4d7546d91b624435f806d6820e4025f0b > Upgrade JaCoCo Version to 0.7.8 > --- > > Key: SUREFIRE-1318 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1318 > Project: Maven Surefire > Issue Type: Task > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1319) Upgrade RAT Plugin Version to 0.12
[ https://issues.apache.org/jira/browse/SUREFIRE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1319. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=614f12c62c803d85f4cc48ad850d9055547d12fa > Upgrade RAT Plugin Version to 0.12 > -- > > Key: SUREFIRE-1319 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1319 > Project: Maven Surefire > Issue Type: Task >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1321) Integration tests should be cleaned up before running. Add goal=clean in maven-invoker-plugin.
[ https://issues.apache.org/jira/browse/SUREFIRE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1321. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=99978af43be70e29f2f74c39b888c2ef9b98cd20 > Integration tests should be cleaned up before running. Add goal=clean in > maven-invoker-plugin. > -- > > Key: SUREFIRE-1321 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1321 > Project: Maven Surefire > Issue Type: Task >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1320) Upgrade Sniffer Plugin Version to 1.15
[ https://issues.apache.org/jira/browse/SUREFIRE-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1320. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=37d99af1c19f2bdd56f10f73155c4947a09b8764 > Upgrade Sniffer Plugin Version to 1.15 > -- > > Key: SUREFIRE-1320 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1320 > Project: Maven Surefire > Issue Type: Task >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1322) Surefire and Failsafe should dump critical errors in dump file and console
[ https://issues.apache.org/jira/browse/SUREFIRE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1322. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9964119f3a238223e50b0bd6e813ea8dc03f910d > Surefire and Failsafe should dump critical errors in dump file and console > -- > > Key: SUREFIRE-1322 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1322 > Project: Maven Surefire > Issue Type: Bug >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > > Both plugins, Surefire and Failsafe, dump stack trace and error messages and > lost commands in dump file or in console: > [date]-jvmRun[N].dump, > [date].dumpstream and > [date]-jvmRun[N].dumpstream > IN previous versions the plugins threw exceptions like, > MojoExecutionException and MojoFailureException, but the user could not see > any message of error which killed the plugin internally. > Since now this is possible and the user can see the dump files in target > target/failsafe-reports and target/surefire-reports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (SUREFIRE-1323) Java 1.6 for improved XML parser needed in SUREFIRE-1322
[ https://issues.apache.org/jira/browse/SUREFIRE-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tibor Digana closed SUREFIRE-1323. -- Resolution: Fixed https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9964119f3a238223e50b0bd6e813ea8dc03f910d > Java 1.6 for improved XML parser needed in SUREFIRE-1322 > > > Key: SUREFIRE-1323 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1323 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > > The Failsafe plugins used parser which threw exception in verification goal. > This exception was expected to have a message from a stacktrace stored in > failsafe-summary.xml. It was impossible to separate exception message from > stack trace line because DOM parser did not split the test having new lines > and therefore it looked like one big text. > Therefore we use JAXB introduced in Java 1.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Comment Edited] (SUREFIRE-1322) Surefire and Failsafe should dump critical errors in dump file and console
[ https://issues.apache.org/jira/browse/SUREFIRE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778518#comment-15778518 ] Tibor Digana edited comment on SUREFIRE-1322 at 12/26/16 3:33 PM: -- https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=303cc8acdaf677bee9751da94de16e07083febb7 was (Author: tibor17): https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=9964119f3a238223e50b0bd6e813ea8dc03f910d > Surefire and Failsafe should dump critical errors in dump file and console > -- > > Key: SUREFIRE-1322 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1322 > Project: Maven Surefire > Issue Type: Bug >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > > Both plugins, Surefire and Failsafe, dump stack trace and error messages and > lost commands in dump file or in console: > [date]-jvmRun[N].dump, > [date].dumpstream and > [date]-jvmRun[N].dumpstream > IN previous versions the plugins threw exceptions like, > MojoExecutionException and MojoFailureException, but the user could not see > any message of error which killed the plugin internally. > Since now this is possible and the user can see the dump files in target > target/failsafe-reports and target/surefire-reports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1316) MVN 3.1.0 minimum in build time
[
https://issues.apache.org/jira/browse/SUREFIRE-1316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778583#comment-15778583
]
Hudson commented on SUREFIRE-1316:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See
[https://builds.apache.org/job/maven-surefire/1656/])
[SUREFIRE-1316] MVN 3.1.0 minimum in build time (tibor17:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=137029531f22e65cb9bb841aa62ca859441b0b14])
* (edit) pom.xml
> MVN 3.1.0 minimum in build time
> ---
>
> Key: SUREFIRE-1316
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1316
> Project: Maven Surefire
> Issue Type: Task
>Reporter: Tibor Digana
>Assignee: Tibor Digana
> Fix For: 2.19.2
>
>
> The build still does not crash with MVN 3.0.x but the logs are hard to read.
> Due to the Maven 3.0.x reports console messages on a new line like this:
> {quote}
> info
> Message on new line.
> {quote}
> project starts using Maven 3.1.x in build time.
> The users still can use MVN 3.0.x in runtime.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1317) Refactoring
[ https://issues.apache.org/jira/browse/SUREFIRE-1317?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778581#comment-15778581 ] Hudson commented on SUREFIRE-1317: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1317] Refactoring (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=0d90d9755c3308aaa328a948ce7e14011f426453]) * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/TestSetRunListener.java * (edit) surefire-booter/src/main/java/org/apache/maven/surefire/booter/SystemPropertyManager.java * (edit) surefire-api/src/main/java/org/apache/maven/surefire/util/internal/StringUtils.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/AbstractSurefireMojo.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/BooterSerializer.java > Refactoring > --- > > Key: SUREFIRE-1317 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1317 > Project: Maven Surefire > Issue Type: Improvement > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1320) Upgrade Sniffer Plugin Version to 1.15
[ https://issues.apache.org/jira/browse/SUREFIRE-1320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778586#comment-15778586 ] Hudson commented on SUREFIRE-1320: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1320] Upgrade Sniffer Plugin Version to 1.15 (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=37d99af1c19f2bdd56f10f73155c4947a09b8764]) * (edit) pom.xml > Upgrade Sniffer Plugin Version to 1.15 > -- > > Key: SUREFIRE-1320 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1320 > Project: Maven Surefire > Issue Type: Task >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1319) Upgrade RAT Plugin Version to 0.12
[ https://issues.apache.org/jira/browse/SUREFIRE-1319?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778580#comment-15778580 ] Hudson commented on SUREFIRE-1319: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1319] Upgrade RAT Plugin Version to 0.12 (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=614f12c62c803d85f4cc48ad850d9055547d12fa]) * (edit) pom.xml > Upgrade RAT Plugin Version to 0.12 > -- > > Key: SUREFIRE-1319 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1319 > Project: Maven Surefire > Issue Type: Task >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1323) Java 1.6 for improved XML parser needed in SUREFIRE-1322
[ https://issues.apache.org/jira/browse/SUREFIRE-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778585#comment-15778585 ] Hudson commented on SUREFIRE-1323: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1323] Java 1.6 for improved XML parser needed in SUREFIRE-1322 (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=9964119f3a238223e50b0bd6e813ea8dc03f910d]) * (edit) pom.xml > Java 1.6 for improved XML parser needed in SUREFIRE-1322 > > > Key: SUREFIRE-1323 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1323 > Project: Maven Surefire > Issue Type: Bug > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > > The Failsafe plugins used parser which threw exception in verification goal. > This exception was expected to have a message from a stacktrace stored in > failsafe-summary.xml. It was impossible to separate exception message from > stack trace line because DOM parser did not split the test having new lines > and therefore it looked like one big text. > Therefore we use JAXB introduced in Java 1.6. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1318) Upgrade JaCoCo Version to 0.7.8
[ https://issues.apache.org/jira/browse/SUREFIRE-1318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778582#comment-15778582 ] Hudson commented on SUREFIRE-1318: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1318] Upgrade JaCoCo Version to 0.7.8 (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=738976c4d7546d91b624435f806d6820e4025f0b]) * (edit) pom.xml > Upgrade JaCoCo Version to 0.7.8 > --- > > Key: SUREFIRE-1318 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1318 > Project: Maven Surefire > Issue Type: Task > Components: Maven Failsafe Plugin, Maven Surefire Plugin, Maven > Surefire Report Plugin >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1321) Integration tests should be cleaned up before running. Add goal=clean in maven-invoker-plugin.
[ https://issues.apache.org/jira/browse/SUREFIRE-1321?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778587#comment-15778587 ] Hudson commented on SUREFIRE-1321: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1321] Integration tests should be cleaned up before running. (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=99978af43be70e29f2f74c39b888c2ef9b98cd20]) * (edit) maven-failsafe-plugin/pom.xml > Integration tests should be cleaned up before running. Add goal=clean in > maven-invoker-plugin. > -- > > Key: SUREFIRE-1321 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1321 > Project: Maven Surefire > Issue Type: Task >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1322) Surefire and Failsafe should dump critical errors in dump file and console
[ https://issues.apache.org/jira/browse/SUREFIRE-1322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778584#comment-15778584 ] Hudson commented on SUREFIRE-1322: -- SUCCESS: Integrated in Jenkins build maven-surefire #1656 (See [https://builds.apache.org/job/maven-surefire/1656/]) [SUREFIRE-1323] Java 1.6 for improved XML parser needed in SUREFIRE-1322 (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=9964119f3a238223e50b0bd6e813ea8dc03f910d]) * (edit) pom.xml [SUREFIRE-1322] Surefire and Failsafe should dump critical errors in (tibor17: [http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=303cc8acdaf677bee9751da94de16e07083febb7]) * (add) maven-failsafe-plugin/src/test/java/org/apache/maven/plugin/failsafe/RunResultTest.java * (edit) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/VerifyMojo.java * (add) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/xmlsummary/FailsafeSummary.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/ForkClient.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/ForkStarter.java * (add) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/booterclient/output/LostCommandsDumpSingleton.java * (add) maven-failsafe-plugin/src/test/resources/org/apache/maven/plugin/failsafe/failsafe-summary.xml * (add) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/xmlsummary/ErrorType.java * (add) maven-surefire-plugin/src/site/resources/xsd/failsafe-summary.xsd * (edit) surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/fixture/OutputValidator.java * (add) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/xmlsummary/ObjectFactory.java * (edit) surefire-api/src/test/java/org/apache/maven/surefire/suite/RunResultTest.java * (edit) maven-surefire-plugin/src/site/apt/developing.apt.vm * (edit) surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire141PluggableProvidersIT.java * (add) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/xmlsummary/JAXB.java * (edit) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/IntegrationTestMojo.java * (edit) surefire-api/src/main/java/org/apache/maven/surefire/booter/CommandReader.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/SurefireHelper.java * (add) surefire-api/src/main/java/org/apache/maven/surefire/util/internal/DumpFileUtils.java * (edit) maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java * (add) maven-surefire-plugin/src/site/resources/xsd/bindings.xml * (edit) surefire-api/src/main/java/org/apache/maven/surefire/suite/RunResult.java * (edit) maven-surefire-plugin/src/site/apt/index.apt.vm * (add) maven-failsafe-plugin/src/main/java/org/apache/maven/plugin/failsafe/xmlsummary/FailsafeSummaryXmlUtils.java * (edit) maven-surefire-plugin/src/site/apt/examples/shutdown.apt.vm * (edit) surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/CheckTestNgExecuteErrorIT.java * (edit) surefire-booter/src/main/java/org/apache/maven/surefire/booter/ForkedBooter.java * (add) maven-failsafe-plugin/src/test/java/org/apache/maven/plugin/failsafe/MarshallerUnmarshallerTest.java * (edit) maven-surefire-plugin/src/site/fml/faq.fml > Surefire and Failsafe should dump critical errors in dump file and console > -- > > Key: SUREFIRE-1322 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1322 > Project: Maven Surefire > Issue Type: Bug >Reporter: Tibor Digana >Assignee: Tibor Digana > Fix For: 2.19.2 > > > Both plugins, Surefire and Failsafe, dump stack trace and error messages and > lost commands in dump file or in console: > [date]-jvmRun[N].dump, > [date].dumpstream and > [date]-jvmRun[N].dumpstream > IN previous versions the plugins threw exceptions like, > MojoExecutionException and MojoFailureException, but the user could not see > any message of error which killed the plugin internally. > Since now this is possible and the user can see the dump files in target > target/failsafe-reports and target/surefire-reports. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1315) Fix stylistic errors in DefaultReporterFactory
[
https://issues.apache.org/jira/browse/SUREFIRE-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778662#comment-15778662
]
Michael Osipov commented on SUREFIRE-1315:
--
Subsequent refinement with
[bd75bac320301db3fc4d8aec5b431f4d10171eb9|https://git-wip-us.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=bd75bac320301db3fc4d8aec5b431f4d10171eb9].
> Fix stylistic errors in DefaultReporterFactory
> --
>
> Key: SUREFIRE-1315
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1315
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.19.1
>Reporter: Abdysamat Mamutov
>Assignee: Michael Osipov
>Priority: Minor
> Labels: easyfix
> Fix For: 2.19.2
>
>
> I'm using maven from CLI:
> {quote}
> mvn --version
> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> 2015-04-22T17:57:37+06:00)
> Maven home: /usr/lib/maven/3.3.3
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-38-generic", arch: "amd64", family: "unix"
> {quote}
> When some unit test fails, mvn shows following message:
> {quote}
> Results :
> Tests in error:
> ...
> {quote}
> I think this message should be {quote}Errors in tests:{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (MNG-6140) update documentation's dependency graph with resolver & resolver-provider
Hervé Boutemy created MNG-6140: -- Summary: update documentation's dependency graph with resolver & resolver-provider Key: MNG-6140 URL: https://issues.apache.org/jira/browse/MNG-6140 Project: Maven Issue Type: Task Components: Documentation: General Reporter: Hervé Boutemy -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1315) Fix stylistic errors in DefaultReporterFactory
[
https://issues.apache.org/jira/browse/SUREFIRE-1315?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778725#comment-15778725
]
Hudson commented on SUREFIRE-1315:
--
SUCCESS: Integrated in Jenkins build maven-surefire #1657 (See
[https://builds.apache.org/job/maven-surefire/1657/])
[SUREFIRE-1315] Fix stylistic errors in DefaultReporterFactory (michaelo:
[http://git-wip-us.apache.org/repos/asf/?p=maven-surefire.git&a=commit&h=bd75bac320301db3fc4d8aec5b431f4d10171eb9])
* (edit) maven-surefire-plugin/src/site/markdown/newerrorsummary.md
* (edit)
maven-surefire-common/src/test/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactoryTest.java
* (edit)
maven-surefire-common/src/main/java/org/apache/maven/plugin/surefire/report/DefaultReporterFactory.java
* (edit)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/JUnit4RerunFailingTestsIT.java
* (edit)
surefire-integration-tests/src/test/java/org/apache/maven/surefire/its/jiras/Surefire1146RerunFailedAndParameterized.java
> Fix stylistic errors in DefaultReporterFactory
> --
>
> Key: SUREFIRE-1315
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1315
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.19.1
>Reporter: Abdysamat Mamutov
>Assignee: Michael Osipov
>Priority: Minor
> Labels: easyfix
> Fix For: 2.19.2
>
>
> I'm using maven from CLI:
> {quote}
> mvn --version
> Apache Maven 3.3.3 (7994120775791599e205a5524ec3e0dfe41d4a06;
> 2015-04-22T17:57:37+06:00)
> Maven home: /usr/lib/maven/3.3.3
> Java version: 1.8.0_91, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-oracle/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.4.0-38-generic", arch: "amd64", family: "unix"
> {quote}
> When some unit test fails, mvn shows following message:
> {quote}
> Results :
> Tests in error:
> ...
> {quote}
> I think this message should be {quote}Errors in tests:{quote}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MNG-6140) update documentation's dependency graph with resolver & resolver-provider
[ https://issues.apache.org/jira/browse/MNG-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6140: --- Fix Version/s: 3.4.0 > update documentation's dependency graph with resolver & resolver-provider > - > > Key: MNG-6140 > URL: https://issues.apache.org/jira/browse/MNG-6140 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Hervé Boutemy > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6140) update documentation's dependency graph with resolver + resolver-provider + slf4j-provider
[ https://issues.apache.org/jira/browse/MNG-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6140: --- Summary: update documentation's dependency graph with resolver + resolver-provider + slf4j-provider (was: update documentation's dependency graph with resolver & resolver-provider) > update documentation's dependency graph with resolver + resolver-provider + > slf4j-provider > -- > > Key: MNG-6140 > URL: https://issues.apache.org/jira/browse/MNG-6140 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Hervé Boutemy > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6140) update documentation's dependency graph with resolver + resolver-provider + slf4j-provider
[ https://issues.apache.org/jira/browse/MNG-6140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15778779#comment-15778779 ] Hudson commented on MNG-6140: - SUCCESS: Integrated in Jenkins build maven-3.x #1475 (See [https://builds.apache.org/job/maven-3.x/1475/]) MNG-6140 renamed aether to resolver, added slf4j-provider (hboutemy: [http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=08eed622d6a852bdf5d05f18b64a982ab823e2d2]) * (edit) src/site/xdoc/index.xml * (edit) src/site/resources/images/maven-deps.png * (edit) src/site/xdoc/maven-deps.odg > update documentation's dependency graph with resolver + resolver-provider + > slf4j-provider > -- > > Key: MNG-6140 > URL: https://issues.apache.org/jira/browse/MNG-6140 > Project: Maven > Issue Type: Task > Components: Documentation: General >Reporter: Hervé Boutemy > Fix For: 3.4.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MWAR-257) Remove deprecation of dependentWarExcludes, since there is no alternative on global level
[ https://issues.apache.org/jira/browse/MWAR-257?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779281#comment-15779281 ] ASF GitHub Bot commented on MWAR-257: - GitHub user michaldo opened a pull request: https://github.com/apache/maven-plugins/pull/102 MWAR-257 Remove deprecation of dependentWarExcludes, since there is no alternative on global level Revert "[MWAR-367] Overlay removes /META-INF/context.xml" This reverts commit cb254e434a40b7ff58c936abbb3f823029a0e466. You can merge this pull request into a Git repository by running: $ git pull https://github.com/michaldo/maven-plugins trunk Alternatively you can review and apply these changes as the patch at: https://github.com/apache/maven-plugins/pull/102.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #102 commit c75d0ef5c1dce43e680a122f03a9e7ed47985da2 Author: michal Date: 2016-12-26T18:32:21Z MWAR-257 Remove deprecation of dependentWarExcludes, since there is no alternative on global level Revert "[MWAR-367] Overlay removes /META-INF/context.xml" This reverts commit cb254e434a40b7ff58c936abbb3f823029a0e466. > Remove deprecation of dependentWarExcludes, since there is no alternative on > global level > - > > Key: MWAR-257 > URL: https://issues.apache.org/jira/browse/MWAR-257 > Project: Maven WAR Plugin > Issue Type: Bug > Components: overlay >Affects Versions: 2.1.1 >Reporter: dool >Assignee: Michael Osipov > > Hello, > DependentWarExcludes is marked as deprecated. Documentation says to use > / instead. > But it seems to me that it is not possible to get the same behaviour with > / as in this case we have to provide groupIds and > artifactIds. > Maybe this behaviour could be reproduced when setting both groupId and > artifactId to * as below : > > > > * > * > **/* > > > > > By the way, I found this, by looking for a way to disable overlay. The > workaround I thought was configuring your plugin to exclude every files when > overlaying. > I think it would be nice to have a configuration parameter for that. > Many thanks, > Dool -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MSHARED-604) Honor none default localRepository
Dan Tran created MSHARED-604: Summary: Honor none default localRepository Key: MSHARED-604 URL: https://issues.apache.org/jira/browse/MSHARED-604 Project: Maven Shared Components Issue Type: Bug Components: maven-aritfact-transfer Affects Versions: maven-artifact-transfer-0.9.0 Reporter: Dan Tran ArtifactResolver ignores localRepository settings in the request ProjectBuildingRequest. It always use the default location when maven starts Use case: I have a use case to resolve a maven artifact with local repo is under maven 'target' directory maven-compat does work my case. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (SUREFIRE-1309) Clarify %regex
[
https://issues.apache.org/jira/browse/SUREFIRE-1309?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15779839#comment-15779839
]
ASF GitHub Bot commented on SUREFIRE-1309:
--
GitHub user sverhagen opened a pull request:
https://github.com/apache/maven-surefire/pull/138
SUREFIRE-1309: Clarifying use of regular expressions for inclusion/exclusion
Added clarification to site examples, as discussed in
[SUREFIRE-1309](https://issues.apache.org/jira/browse/SUREFIRE-1309).
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/sverhagen/maven-surefire SUREFIRE-1309
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/maven-surefire/pull/138.patch
To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:
This closes #138
commit 85d7af0bfca1268e62f0902ec70f22370cd3dcf6
Author: Sander Verhagen
Date: 2016-12-27T07:39:56Z
SUREFIRE-1309: Clarifying use of regular expressions for inclusion/exclusion
> Clarify %regex
> --
>
> Key: SUREFIRE-1309
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1309
> Project: Maven Surefire
> Issue Type: Documentation
>Affects Versions: 2.19.1
> Environment: Probably any environment
>Reporter: Sander Verhagen
>Assignee: Tibor Digana
>
> It would be good to clarify the {{%regex ...}} feature:
> 1. While it is said to be regular expression, it really is a {{regular
> expression + ".class"}} kind of thing. This does not work (while it is proper
> regex):
> {noformat}.+\.class{noformat} The following works (while it is not proper
> regex): {noformat}.+.class{noformat}
> 2. Clarify that one is supposed to match slashes between packages and class
> name, not periods. The following [current
> documentation|http://maven.apache.org/components/surefire/maven-surefire-plugin/examples/inclusion-exclusion.html]
> doesn't clarify that by just using "{{.*}}":
> {noformat}!%regex[pkg.*Slow.*.class]{noformat}
> 3. Clarify what the expectations are in terms of escaping characters
> I just spend literally ten hours figuring out a complex regex, going into
> TeamCity (which by itself complicated the troubleshooting for me), and the
> documentation could have saved my butt, here.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
