[
https://issues.apache.org/jira/browse/SUREFIRE-1432?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17714051#comment-17714051
]
Jesse Glick commented on SUREFIRE-1432:
---
[~ste...@apache.org] how would defaulting
[
https://issues.apache.org/jira/browse/SUREFIRE-2087?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17678733#comment-17678733
]
Jesse Glick commented on SUREFIRE-2087:
---
While a full fix would of course be to rerun
[
https://issues.apache.org/jira/browse/MSHADE-323?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17599113#comment-17599113
]
Jesse Glick commented on MSHADE-323:
[
https://issues.apache.org/jira/browse/SUREFIRE-2058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17553669#comment-17553669
]
Jesse Glick commented on SUREFIRE-2058:
---
I was able to confirm that M7 fixes at least one
[
https://issues.apache.org/jira/browse/MRESOLVER-253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17527568#comment-17527568
]
Jesse Glick commented on MRESOLVER-253:
---
This sounds promising. Is
[
https://issues.apache.org/jira/browse/MCOMPILER-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17502454#comment-17502454
]
Jesse Glick commented on MCOMPILER-485:
---
Will there be some notification when the fix is
[
https://issues.apache.org/jira/browse/SUREFIRE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17468167#comment-17468167
]
Jesse Glick commented on SUREFIRE-1911:
---
Good to know that is a resolution once the problem is
[
https://issues.apache.org/jira/browse/SUREFIRE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17411203#comment-17411203
]
Jesse Glick commented on SUREFIRE-1911:
---
Struck again, this time in Jenkins core, and apparently
[
https://issues.apache.org/jira/browse/MENFORCER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385837#comment-17385837
]
Jesse Glick commented on MENFORCER-298:
---
I managed to work around that by patching
[
https://issues.apache.org/jira/browse/MENFORCER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385831#comment-17385831
]
Jesse Glick commented on MENFORCER-298:
---
My original test case still reproduces the bug in Maven
[
https://issues.apache.org/jira/browse/MNG-6380?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17385140#comment-17385140
]
Jesse Glick commented on MNG-6380:
--
Seems to work in
{code:none}
Apache Maven 3.8.2-SNAPSHOT
[
https://issues.apache.org/jira/browse/SUREFIRE-1911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17346381#comment-17346381
]
Jesse Glick commented on SUREFIRE-1911:
---
{code:none}
$ mvn dependency:tree
…
[INFO]
[
https://issues.apache.org/jira/browse/SUREFIRE-1787?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17335809#comment-17335809
]
Jesse Glick commented on SUREFIRE-1787:
---
Appears to have caused a regression: SUREFIRE-1911
>
Jesse Glick created SUREFIRE-1911:
-
Summary: Groovy-based JUnit 4 tests no longer run w/ 5 in classpath
Key: SUREFIRE-1911
URL: https://issues.apache.org/jira/browse/SUREFIRE-1911
Project: Maven
[
https://issues.apache.org/jira/browse/ARCHETYPE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17227010#comment-17227010
]
Jesse Glick commented on ARCHETYPE-539:
---
This is particular painful when a Nexus mirror is
[
https://issues.apache.org/jira/browse/MNG-6976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17219317#comment-17219317
]
Jesse Glick commented on MNG-6976:
--
A custom Logback configuration does not seem like a reasonable
[
https://issues.apache.org/jira/browse/SUREFIRE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17189572#comment-17189572
]
Jesse Glick commented on SUREFIRE-1798:
---
bq. pushing this change right now would mean that the
[
https://issues.apache.org/jira/browse/SUREFIRE-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186787#comment-17186787
]
Jesse Glick edited comment on SUREFIRE-1827 at 8/28/20, 8:08 PM:
-
[
https://issues.apache.org/jira/browse/SUREFIRE-1827?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186787#comment-17186787
]
Jesse Glick commented on SUREFIRE-1827:
---
According to {{git bisect}}, SUREFIRE-1658 is the
[
https://issues.apache.org/jira/browse/SUREFIRE-1818?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186779#comment-17186779
]
Jesse Glick commented on SUREFIRE-1818:
---
Sounds similar to SUREFIRE-1827.
> Surefire buffers
[
https://issues.apache.org/jira/browse/SUREFIRE-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17186778#comment-17186778
]
Jesse Glick commented on SUREFIRE-1798:
---
Argued before in SUREFIRE-1226.
> trimStackTrace
Jesse Glick created MNG-6976:
Summary: --no-transfer-progress variant to diagnose download issue
Key: MNG-6976
URL: https://issues.apache.org/jira/browse/MNG-6976
Project: Maven
Issue Type:
[
https://issues.apache.org/jira/browse/MDEP-667?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17007607#comment-17007607
]
Jesse Glick commented on MDEP-667:
--
I suppose
[
https://issues.apache.org/jira/browse/MDEP-667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick updated MDEP-667:
-
Summary: dependency:sources skips *-test-sources.jar by default (was:
dependency:sources skips
Jesse Glick created MDEP-667:
Summary: dependency:sources skips *--test-sources.jar by default
Key: MDEP-667
URL: https://issues.apache.org/jira/browse/MDEP-667
Project: Maven Dependency Plugin
[
https://issues.apache.org/jira/browse/MNG-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16978470#comment-16978470
]
Jesse Glick commented on MNG-6405:
--
It seems this was released in 3.6.2?
> Incorrect basedir in forked
[
https://issues.apache.org/jira/browse/MNG-6551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16739984#comment-16739984
]
Jesse Glick commented on MNG-6551:
--
The {{maven-compiler-plugin}} update is import to pick up
[
https://issues.apache.org/jira/browse/MNG-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733584#comment-16733584
]
Jesse Glick commented on MNG-6405:
--
Filed [PR 225|https://github.com/apache/maven/pull/225] with the patch
[
https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707712#comment-16707712
]
Jesse Glick commented on MENFORCER-276:
---
[~matthies] yes that makes sense. Ideally I think the
[
https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16707542#comment-16707542
]
Jesse Glick commented on MENFORCER-276:
---
[~matthies] not sure I understand. If you run the rule
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16704836#comment-16704836
]
Jesse Glick commented on SUREFIRE-1588:
---
The problem seems to have been resolved upstream if you
[
https://issues.apache.org/jira/browse/SUREFIRE-1593?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16691868#comment-16691868
]
Jesse Glick commented on SUREFIRE-1593:
---
[Final
Jesse Glick created SUREFIRE-1593:
-
Summary: 3.0.0-M1 produces invalid code sources on Windows
Key: SUREFIRE-1593
URL: https://issues.apache.org/jira/browse/SUREFIRE-1593
Project: Maven Surefire
[
https://issues.apache.org/jira/browse/MENFORCER-267?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16680229#comment-16680229
]
Jesse Glick commented on MENFORCER-267:
---
Doing this might fix MENFORCER-298 by the way. (I no
[
https://issues.apache.org/jira/browse/SUREFIRE-1588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16671777#comment-16671777
]
Jesse Glick commented on SUREFIRE-1588:
---
Building on the tip by [~cstamas] I was able to work
[
https://issues.apache.org/jira/browse/MNG-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16574196#comment-16574196
]
Jesse Glick commented on MNG-6118:
--
Came across this in a
[
https://issues.apache.org/jira/browse/MNG-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522608#comment-16522608
]
Jesse Glick commented on MNG-6405:
--
No, the bug in core remains. I was just noting that _one trigger_ for
[
https://issues.apache.org/jira/browse/MNG-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16522321#comment-16522321
]
Jesse Glick commented on MNG-6405:
--
The superpom has evidently been fixed in Maven 3.5.4, so at least now
[
https://issues.apache.org/jira/browse/MNG-6405?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16474611#comment-16474611
]
Jesse Glick commented on MNG-6405:
--
If you are using both {{flatten-maven-plugin}} and
Jesse Glick created MNG-6405:
Summary: Incorrect basedir in forked executions when using
flatten-maven-plugin with custom outputDirectory
Key: MNG-6405
URL: https://issues.apache.org/jira/browse/MNG-6405
[
https://issues.apache.org/jira/browse/MNG-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428707#comment-16428707
]
Jesse Glick commented on MNG-6066:
--
Ah, I knew about the Flatten plugin and was actually already using it
[
https://issues.apache.org/jira/browse/MNG-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428597#comment-16428597
]
Jesse Glick commented on MNG-6066:
--
Maybe something like MNG-5059 would be the best approach, so I could
[
https://issues.apache.org/jira/browse/MNG-6066?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16428589#comment-16428589
]
Jesse Glick commented on MNG-6066:
--
While the automake idiom does serve as a workaround, this nonetheless
[
https://issues.apache.org/jira/browse/MNG-6303?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16406102#comment-16406102
]
Jesse Glick commented on MNG-6303:
--
If I understand correctly there is no current or proposed feature to
[
https://issues.apache.org/jira/browse/MENFORCER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386743#comment-16386743
]
Jesse Glick commented on MENFORCER-298:
---
It is possible that my patch is also effective against
[
https://issues.apache.org/jira/browse/MENFORCER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386733#comment-16386733
]
Jesse Glick commented on MENFORCER-298:
---
I suspect the _best_ fix is to use
[
https://issues.apache.org/jira/browse/MNG-5129?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386730#comment-16386730
]
Jesse Glick commented on MNG-5129:
--
Sounds similar to MNG-4189.
> Maven struggles while resolving locked
[
https://issues.apache.org/jira/browse/MENFORCER-298?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386727#comment-16386727
]
Jesse Glick commented on MENFORCER-298:
---
Filed PR 32 with a simple proposed fix. If this is
Jesse Glick created MENFORCER-298:
-
Summary: bannedDependencies can break compilation against a
timestamped snapshot
Key: MENFORCER-298
URL: https://issues.apache.org/jira/browse/MENFORCER-298
[
https://issues.apache.org/jira/browse/MENFORCER-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386668#comment-16386668
]
Jesse Glick commented on MENFORCER-244:
---
I think you [can already do
[
https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244271#comment-16244271
]
Jesse Glick commented on MNG-6220:
--
I was directed to MNG-6296 which tracks the problem.
> Add CLI options
[
https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16244119#comment-16244119
]
Jesse Glick commented on MNG-6220:
--
The usual risks of relying on unit tests: you get what you pay for. :-/
[
https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16240636#comment-16240636
]
Jesse Glick commented on MENFORCER-276:
---
FWIW while I have not looked at this PR, I would
[
https://issues.apache.org/jira/browse/SUREFIRE-1433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16215494#comment-16215494
]
Jesse Glick commented on SUREFIRE-1433:
---
Obviously the above is not a real test. I was merely
Jesse Glick created SUREFIRE-1433:
-
Summary: rerunFailingTestsCount does not help with crashes
Key: SUREFIRE-1433
URL: https://issues.apache.org/jira/browse/SUREFIRE-1433
Project: Maven Surefire
[
https://issues.apache.org/jira/browse/SUREFIRE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16194916#comment-16194916
]
Jesse Glick commented on SUREFIRE-1226:
---
This has nothing to do with Jenkins plugins
[
https://issues.apache.org/jira/browse/MNG-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138464#comment-16138464
]
Jesse Glick commented on MNG-6274:
--
AFAIK this only applies to {{deploy}} (to a remote repository), not
[
https://issues.apache.org/jira/browse/MNG-6274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138437#comment-16138437
]
Jesse Glick commented on MNG-6274:
--
[Example question about
[
https://issues.apache.org/jira/browse/MNG-6220?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16050866#comment-16050866
]
Jesse Glick commented on MNG-6220:
--
I was surprised to find that {{TERM=dumb mvn willfail}} still prints
Jesse Glick created MENFORCER-273:
-
Summary: RequireUpperBoundDeps.excludes
Key: MENFORCER-273
URL: https://issues.apache.org/jira/browse/MENFORCER-273
Project: Maven Enforcer Plugin
Issue
Jesse Glick created MENFORCER-272:
-
Summary: Allow site generation to work
Key: MENFORCER-272
URL: https://issues.apache.org/jira/browse/MENFORCER-272
Project: Maven Enforcer Plugin
Issue
[
https://issues.apache.org/jira/browse/MENFORCER-272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick updated MENFORCER-272:
--
Flags: Patch
> Allow site generation to work
> -
>
>
[
https://issues.apache.org/jira/browse/MNG-6223?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16023504#comment-16023504
]
Jesse Glick commented on MNG-6223:
--
Was a regression of MNG-5338.
> mvn -f outputs invalid error when
[
https://issues.apache.org/jira/browse/MNG-4917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888473#comment-15888473
]
Jesse Glick commented on MNG-4917:
--
So {{activeByDefault}} does not mean what you would intuitively think
[
https://issues.apache.org/jira/browse/MNG-3229?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15888466#comment-15888466
]
Jesse Glick commented on MNG-3229:
--
Cf. MNG-4917.
> Active by default profile is ignored when another is
[
https://issues.apache.org/jira/browse/MPH-99?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15582278#comment-15582278
]
Jesse Glick commented on MPH-99:
Awkward compared to the original request—a script would be forced to create,
[
https://issues.apache.org/jira/browse/MINSTALL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15446301#comment-15446301
]
Jesse Glick commented on MINSTALL-126:
--
In my case there is no simple list of coördinates I could
[
https://issues.apache.org/jira/browse/MINSTALL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15436826#comment-15436826
]
Jesse Glick commented on MINSTALL-126:
--
[Use case from
[
https://issues.apache.org/jira/browse/SUREFIRE-1226?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15424904#comment-15424904
]
Jesse Glick commented on SUREFIRE-1226:
---
[~tibor17] I agree with [~jloc...@redhat.com]’s
[
https://issues.apache.org/jira/browse/MNG-5059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15150699#comment-15150699
]
Jesse Glick commented on MNG-5059:
--
Since it seems unlikely this will ever be worked on as a core feature,
[
https://issues.apache.org/jira/browse/MNG-5604?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14586399#comment-14586399
]
Jesse Glick commented on MNG-5604:
--
Seems to duplicate older MNG-3952 if I am not mistaken.
[
https://jira.codehaus.org/browse/SUREFIRE-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=352791#comment-352791
]
Jesse Glick commented on SUREFIRE-1061:
---
IMO this is a NetBeans bug, not a Surefire bug;
[
https://jira.codehaus.org/browse/MRELEASE-271?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=348274#comment-348274
]
Jesse Glick commented on MRELEASE-271:
--
Maven 3.1.0 still seems to be affected. Just have a
[
https://jira.codehaus.org/browse/MCOMPILER-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=344028#comment-344028
]
Jesse Glick commented on MCOMPILER-144:
---
I guess so. It would still be great for the
Jesse Glick created SUREFIRE-1067:
-
Summary: Nested causes conflated with wrapper exception
Key: SUREFIRE-1067
URL: https://jira.codehaus.org/browse/SUREFIRE-1067
Project: Maven Surefire
[
https://jira.codehaus.org/browse/MNG-4838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=331033#comment-331033
]
Jesse Glick commented on MNG-4838:
--
Seems like Wagon 2.0 with this fix was first introduced in Maven
Jesse Glick created SUREFIRE-1022:
-
Summary: system-out malformed XML
Key: SUREFIRE-1022
URL: https://jira.codehaus.org/browse/SUREFIRE-1022
Project: Maven Surefire
Issue Type: Bug
Jesse Glick created MNG-5497:
Summary: maven-metadata.xml checked if dependency expressed
snapshot range even if actual version is fixed
Key: MNG-5497
URL: https://jira.codehaus.org/browse/MNG-5497
[
https://jira.codehaus.org/browse/SUREFIRE-829?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=326485#comment-326485
]
Jesse Glick commented on SUREFIRE-829:
--
Seems wrong to me. If the authors of {{Category}}
Jesse Glick created MSHADE-147:
--
Summary: Failure to shade without explanation when signature is
invalid
Key: MSHADE-147
URL: https://jira.codehaus.org/browse/MSHADE-147
Project: Maven 2.x Shade Plugin
[
https://jira.codehaus.org/browse/MNG-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=324402#comment-324402
]
Jesse Glick commented on MNG-5075:
--
[
https://jira.codehaus.org/browse/MNG-5075?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=324403#comment-324403
]
Jesse Glick commented on MNG-5075:
--
Pull request: https://github.com/apache/maven/pull/8
[
https://jira.codehaus.org/browse/SUREFIRE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323380#comment-323380
]
Jesse Glick commented on SUREFIRE-974:
--
I filed SUREFIRE-984 to track the reporting format.
Jesse Glick created SUREFIRE-984:
Summary: Different reporting format for 3.x custom suites when
JUnit 4.7 provider enabled
Key: SUREFIRE-984
URL: https://jira.codehaus.org/browse/SUREFIRE-984
[
https://jira.codehaus.org/browse/SUREFIRE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323381#comment-323381
]
Jesse Glick commented on SUREFIRE-984:
--
By the way, the relevant sources are:
*
[
https://jira.codehaus.org/browse/SUREFIRE-984?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323381#comment-323381
]
Jesse Glick edited comment on SUREFIRE-984 at 4/8/13 9:12 AM:
--
By
[
https://jira.codehaus.org/browse/MNG-3092?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=323037#comment-323037
]
Jesse Glick commented on MNG-3092:
--
An example using Maven 3.0.5:
[
https://jira.codehaus.org/browse/SUREFIRE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick closed SUREFIRE-974.
Resolution: Won't Fix
I do not see anything Surefire could do either. I did find a simple workaround,
[
https://jira.codehaus.org/browse/SUREFIRE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322817#comment-322817
]
Jesse Glick commented on SUREFIRE-974:
--
The {{JUnit4TestAdapter}} workaround does not work
Jesse Glick created SUREFIRE-974:
Summary: Custom junit.framework.TestSuite subtypes ignored when
excludedGroups defined
Key: SUREFIRE-974
URL: https://jira.codehaus.org/browse/SUREFIRE-974
Project:
[
https://jira.codehaus.org/browse/SUREFIRE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jesse Glick updated SUREFIRE-974:
-
Attachment: SUREFIRE-974.zip
Attaching a demo project. {{mvn test}} works as expected. {{mvn -Pbug
[
https://jira.codehaus.org/browse/SUREFIRE-974?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=322102#comment-322102
]
Jesse Glick commented on SUREFIRE-974:
--
If there is a bug in JUnit itself, I cannot find it:
[
https://jira.codehaus.org/browse/MCOMPILER-66?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=321854#comment-321854
]
Jesse Glick commented on MCOMPILER-66:
--
Seems that with the 3.0 version of the plugin,
[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=321675#comment-321675
]
Jesse Glick commented on SUREFIRE-751:
--
@agudian: any progress on your examples page?
Jesse Glick created SUREFIRE-968:
Summary: Test summary line does not indicate what was being run
when using concurrency
Key: SUREFIRE-968
URL: https://jira.codehaus.org/browse/SUREFIRE-968
Project:
[
https://jira.codehaus.org/browse/SUREFIRE-751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=321682#comment-321682
]
Jesse Glick commented on SUREFIRE-751:
--
Thanks, this makes it much clearer.
[
https://jira.codehaus.org/browse/WAGON-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=321363#comment-321363
]
Jesse Glick commented on WAGON-392:
---
Some research e.g. in http://www.ietf.org/rfc/rfc2396.txt
[
https://jira.codehaus.org/browse/WAGON-392?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=321366#comment-321366
]
Jesse Glick commented on WAGON-392:
---
The problem is with the host name
[
https://jira.codehaus.org/browse/MNG-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320683#comment-320683
]
Jesse Glick commented on MNG-5443:
--
With {{-e}}:
{code:none}
java.lang.IllegalArgumentException:
[
https://jira.codehaus.org/browse/MNG-5443?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=320697#comment-320697
]
Jesse Glick commented on MNG-5443:
--
The actual host name, repo name, and group/artifactId are elided
1 - 100 of 289 matches
Mail list logo
