[
https://issues.apache.org/jira/browse/MNG-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849223#comment-16849223
]
Robert Scholte edited comment on MNG-6661 at 5/28/19 6:40 AM:
--
[
https://issues.apache.org/jira/browse/MNG-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849377#comment-16849377
]
Robert Scholte commented on MNG-6661:
-
It is documented at https://maven.apache.org/ref
[
https://issues.apache.org/jira/browse/MNG-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849368#comment-16849368
]
Sergey Ponomarev commented on MNG-6661:
---
Robert, thank you for a quick reply. If this
mhus opened a new pull request #2: Fixed problems deploying karaf features to
the central repository
URL: https://github.com/apache/maven-gpg-plugin/pull/2
With the current (1.6) version it's not possible to deploy karaf features to
the central repository. The following error occurs:
[
https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849237#comment-16849237
]
Hervé Boutemy commented on MSITE-837:
-
Undertow is light?
https://repo.maven.apache.o
[
https://issues.apache.org/jira/browse/MNG-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849235#comment-16849235
]
Hudson commented on MNG-6638:
-
Build succeeded in Jenkins: Maven TLP » maven » master #211
See
[
https://issues.apache.org/jira/browse/MNG-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849236#comment-16849236
]
Hudson commented on MNG-6556:
-
Build succeeded in Jenkins: Maven TLP » maven » master #211
See
[
https://issues.apache.org/jira/browse/MNG-6556?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849226#comment-16849226
]
Hudson commented on MNG-6556:
-
Build succeeded in Jenkins: Maven TLP » maven » MNG-6638 #4
See
[
https://issues.apache.org/jira/browse/SUREFIRE-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849225#comment-16849225
]
Robert Scholte commented on SUREFIRE-1667:
--
[~sbordet] could you try my lates
[
https://issues.apache.org/jira/browse/MNG-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MNG-6661.
---
Resolution: Won't Fix
Assignee: Robert Scholte
All properties that start with $\{project. are rea
[
https://issues.apache.org/jira/browse/MNG-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed MNG-6638.
---
Resolution: Fixed
Fixed with
[d3ace78602405079d6416a63c13216568ba97995|https://gitbox.apache.org/repos
[
https://issues.apache.org/jira/browse/MNG-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6638:
Issue Type: Improvement (was: Bug)
> Prevent reparsing POMs in MavenMetadataSource
> ---
asfgit closed pull request #244: [MNG-6638] - Prevent reparsing POMs in
MavenMetadataSource
URL: https://github.com/apache/maven/pull/244
This is an automated message from the Apache Git Service.
To respond to the message, p
[
https://issues.apache.org/jira/browse/MNG-6661?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte updated MNG-6661:
Description:
I would like to improve a build speed of a big project. The project uses a lot
of IO op
Sergey Ponomarev created MNG-6661:
-
Summary: Override project.build.directory via user property
Key: MNG-6661
URL: https://issues.apache.org/jira/browse/MNG-6661
Project: Maven
Issue Type: Im
[
https://issues.apache.org/jira/browse/MNG-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6638:
Summary: Prevent reparsing POMs in MavenMetadataSource (was:
MavenMetadataSource parses POMs unneces
[
https://issues.apache.org/jira/browse/MNG-6638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov reassigned MNG-6638:
---
Assignee: Michael Osipov
> MavenMetadataSource parses POMs unnecessarily
> ---
[
https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849184#comment-16849184
]
Damien Burke commented on MSITE-837:
(y)
> use an embedded http server that is light
[
https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849181#comment-16849181
]
Michael Osipov commented on MSITE-837:
--
Undertow 2.0 requires Java 8. Do you want to
[
https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849179#comment-16849179
]
Damien Burke commented on MSITE-837:
Btw, undertow 2.0 requires Java 8 or later, so am
[
https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849177#comment-16849177
]
Damien Burke commented on MSITE-837:
Hey guys, I would like to work on this.
I have f
[
https://issues.apache.org/jira/browse/MSITE-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849177#comment-16849177
]
Damien Burke edited comment on MSITE-837 at 5/27/19 8:10 PM:
-
[
https://issues.apache.org/jira/browse/MNG-6660?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849167#comment-16849167
]
Michael Osipov commented on MNG-6660:
-
Please provide a debug logfile.
> duplicate cla
[
https://issues.apache.org/jira/browse/MNG-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849139#comment-16849139
]
Karl Heinz Marbaise edited comment on MNG-6610 at 5/27/19 7:38 PM:
--
[
https://issues.apache.org/jira/browse/MNG-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849139#comment-16849139
]
Karl Heinz Marbaise edited comment on MNG-6610 at 5/27/19 7:38 PM:
--
[
https://issues.apache.org/jira/browse/MNG-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated MNG-6596:
Fix Version/s: (was: waiting-for-feedback)
> maven should not make assumptions on the location of
[
https://issues.apache.org/jira/browse/MNG-6596?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNG-6596.
Resolution: Cannot Reproduce
Unfortunately no feedback.
> maven should not make assumptions
[
https://issues.apache.org/jira/browse/MNG-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849139#comment-16849139
]
Karl Heinz Marbaise edited comment on MNG-6610 at 5/27/19 7:08 PM:
--
[
https://issues.apache.org/jira/browse/MNG-6610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849139#comment-16849139
]
Karl Heinz Marbaise commented on MNG-6610:
--
The first thing is that you offer a fu
[
https://issues.apache.org/jira/browse/MINSTALL-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849135#comment-16849135
]
Hudson commented on MINSTALL-158:
-
Build succeeded in Jenkins: Maven TLP » maven-instal
[
https://issues.apache.org/jira/browse/MNG-6573?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849134#comment-16849134
]
Hudson commented on MNG-6573:
-
Build succeeded in Jenkins: Maven TLP » maven-install-plugin » m
[
https://issues.apache.org/jira/browse/MINSTALL-158?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849131#comment-16849131
]
Karl Heinz Marbaise commented on MINSTALL-158:
--
Done in
[c0a575481183ae15
[
https://issues.apache.org/jira/browse/MINSTALL-158?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MINSTALL-158.
Resolution: Done
> Upgrade maven-artifact-transfer to 0.11.0
> --
[
https://issues.apache.org/jira/browse/MASSEMBLY-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849125#comment-16849125
]
Hudson commented on MASSEMBLY-915:
--
Build succeeded in Jenkins: Maven TLP » maven-ass
[
https://issues.apache.org/jira/browse/MASSEMBLY-915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849119#comment-16849119
]
Karl Heinz Marbaise commented on MASSEMBLY-915:
---
Done in
[283e7c38da69c
[
https://issues.apache.org/jira/browse/MASSEMBLY-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MASSEMBLY-915.
-
Resolution: Done
> Remove integration-test-archetype
> ---
[
https://issues.apache.org/jira/browse/MCOMPILER-320?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849114#comment-16849114
]
Robert Scholte commented on MCOMPILER-320:
--
By now you should ask "How was Ed
rfscholte commented on a change in pull request #22: [MSHADE-321] - Always
respect 'createDependencyReducedPom' flag
URL: https://github.com/apache/maven-shade-plugin/pull/22#discussion_r287855274
##
File path:
src/it/MSHADE-321_respectDrpFlag/repo/org/apache/maven/its/shade/drp/a/
rfscholte commented on a change in pull request #21: Cleanup debug log handling
URL:
https://github.com/apache/maven-compiler-plugin/pull/21#discussion_r287852512
##
File path:
src/main/java/org/apache/maven/plugin/compiler/AbstractCompilerMojo.java
##
@@ -960,7 +963,7 @@
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849074#comment-16849074
]
Roman Ivanov edited comment on MCHECKSTYLE-376 at 5/27/19 4:41 PM:
---
[
https://issues.apache.org/jira/browse/MCHECKSTYLE-376?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16849074#comment-16849074
]
Roman Ivanov commented on MCHECKSTYLE-376:
--
I would recommend to release ma
oehme commented on issue #244: [MNG-6638] - Prevent reparsing POMs in
MavenMetadataSource
URL: https://github.com/apache/maven/pull/244#issuecomment-496256202
Done
This is an automated message from the Apache Git Service.
To
Luke Usherwood created MNG-6660:
---
Summary: duplicate classes error with source in the root directory
Key: MNG-6660
URL: https://issues.apache.org/jira/browse/MNG-6660
Project: Maven
Issue Type:
Tibor17 edited a comment on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496195273
> Also, it's one of the fastest fixes I've seen on GH
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496195273
> Also, it's one of the fastest fixes I've seen on GH
T
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496189783
The issue was first mentioned on [mailing
list](https://list
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496187238
> @pzygielo
> I will ask INFRA to enable it.
No ne
pzygielo edited a comment on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496184765
> What is better is to open an issue on GitHub
[
https://issues.apache.org/jira/browse/SUREFIRE-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1669.
--
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=d78bfe
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496186660
@pzygielo
I will ask INFRA to enable it. Do you have an ac
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496184765
> What is better is to open an issue on GitHub
Please
Tibor17 merged pull request #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235
This is an automa
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496176241
@pzygielo
> I don't understand that accusation.
It
Aurélien Baudet created MJAVADOC-606:
Summary: doclint fails checking references on dependencies with
scope 'provided'
Key: MJAVADOC-606
URL: https://issues.apache.org/jira/browse/MJAVADOC-606
Pro
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496137076
The CI is successful
https://builds.apache.org/job/maven-box/
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496135278
> ok, you as a user, try to be more honest and self critical.
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496130715
@pzygielo
ok, you as a user, try to be more honest and sel
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496127586
Final comment, as there is only waiting for M4 release remain
pzygielo commented on a change in pull request #235: [SUREFIRE-1669] POJO tests
do not call fixture methods setUp and tearDown and test instance are not new
between tests
URL: https://github.com/apache/maven-surefire/pull/235#discussion_r287683917
##
File path:
surefire-providers/
pzygielo commented on a change in pull request #235: [SUREFIRE-1669] POJO tests
do not call fixture methods setUp and tearDown and test instance are not new
between tests
URL: https://github.com/apache/maven-surefire/pull/235#discussion_r287683917
##
File path:
surefire-providers/
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496116288
@pzygielo
This is not our problem. It is your problem as a
Tibor17 edited a comment on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496109313
@pzygielo
Again, not talking about fields. Not talk
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496110826
Again - without your fix, if someone wants setUp/tearDown to
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496109609
in the field = somewhere in someones code
--
Tibor17 commented on issue #235: [SUREFIRE-1669] POJO tests do not call fixture
methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496109313
@pzygielo
Again, not talking about fields. Not talking abo
pzygielo commented on issue #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235#issuecomment-496107102
Just a comment - it seems your fix might be a breaking change
[
https://issues.apache.org/jira/browse/SUREFIRE-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1669:
---
Summary: POJO tests do not call fixture methods setUp and tearDown and test
instances are
Tibor17 commented on issue #234: (doc) add static modifier to signatures
URL: https://github.com/apache/maven-surefire/pull/234#issuecomment-496103165
@pzygielo
Here is a new PR #235 with the fix.
This is an automated mes
Tibor17 opened a new pull request #235: [SUREFIRE-1669] POJO tests do not call
fixture methods setUp and tearDown and test instance are not new between tests
URL: https://github.com/apache/maven-surefire/pull/235
see the Jira SUREFIRE-1669
--
[
https://issues.apache.org/jira/browse/SUREFIRE-1669?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1669:
---
Description:
* test instances are not new for each test method
* POJO tests do not call fi
70 matches
Mail list logo
