[jira] (SUREFIRE-985) Some Parameterized tests are not executed (or not reported)
[
https://jira.codehaus.org/browse/SUREFIRE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323589#comment-323589
]
Nicolas Liochon commented on SUREFIRE-985:
--
That was fast! Thanks a lot. We're using a fork of the 2.11, that could explain
why we don't have the issue. The workaround is great, I'm going to try it.
> Some Parameterized tests are not executed (or not reported)
> ---
>
> Key: SUREFIRE-985
> URL: https://jira.codehaus.org/browse/SUREFIRE-985
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.14
> Environment: linux, 2 *4 cores, 32 Gb RAM (The sample does not work
> on Windows)
>Reporter: Nicolas Liochon
>Assignee: Andreas Gudian
>Priority: Critical
> Fix For: 2.15
>
>
> The test itself does nothing. The problem occurs when you have a lot of test
> classes with different categories, that's why I haven't been able to extract
> it (I suppose generating test classes would work): the report 'forgets' some
> tests.
> here is a branch I created to reproduce the issue:
> {code}
> git clone -b surefire git://github.com/nkeywal/hbase.git
> mvn clean install -D skipTests
> {code}
> There is a lot of third parties and code. Then:
> {code}
> mvn test -pl hbase-server
> {code}
> will give back a random number of test executed (from 0 to 9).
> If you specify the test name with -Dtest= the number of tests is always 9 (as
> expected).
> Building will take time, but there is a single test to execute.
> It's fragile: I tried to move the test to a difference package and the
> problem was not reproducable anymore. But I do reproduce it on a clean
> install with the branch above, and I do reproduce it all the time on our test
> suite, on different Linux machines.
>
> test code:
> {code}
> package org.apache.hadoop.hbase.regionserver;
> import java.util.*;
> @org.junit.runner.RunWith(org.junit.runners.Parameterized.class)
> @org.junit.experimental.categories.Category(org.apache.hadoop.hbase.S1Tests.class)
> public class TestSurefire {
> @org.junit.runners.Parameterized.Parameters
> public static Collection parameters() {
> ArrayList configurations = new ArrayList();
> for (int i = 1; i < 10; i++) {
> configurations.add(new Object[] { i });
> }
> return configurations;
> }
> public TestSurefire(Object o) {
> }
> @org.junit.Test
> public void testM() {
> }
> }
> {code}
> settings
> {code}
>
> maven-surefire-plugin
> 2.14
>
> true
> 2
> org.apache.hadoop.hbase.S1Tests
> true
>
>
> {code}
> Example of output:
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
> or
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Running org.apache.hadoop.hbase.regionserver.TestSurefire
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> Results :
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-985) Some Parameterized tests are not executed (or not reported)
[
https://jira.codehaus.org/browse/SUREFIRE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323594#comment-323594
]
Kristian Rosenvold commented on SUREFIRE-985:
-
@Nicolas Is there a jira that documents the reason you forked 2.11 ? I'm just
curious since I'm gathering some use-cases for version "3.0" where we try to
make more extensibility cases
> Some Parameterized tests are not executed (or not reported)
> ---
>
> Key: SUREFIRE-985
> URL: https://jira.codehaus.org/browse/SUREFIRE-985
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.14
> Environment: linux, 2 *4 cores, 32 Gb RAM (The sample does not work
> on Windows)
>Reporter: Nicolas Liochon
>Assignee: Andreas Gudian
>Priority: Critical
> Fix For: 2.15
>
>
> The test itself does nothing. The problem occurs when you have a lot of test
> classes with different categories, that's why I haven't been able to extract
> it (I suppose generating test classes would work): the report 'forgets' some
> tests.
> here is a branch I created to reproduce the issue:
> {code}
> git clone -b surefire git://github.com/nkeywal/hbase.git
> mvn clean install -D skipTests
> {code}
> There is a lot of third parties and code. Then:
> {code}
> mvn test -pl hbase-server
> {code}
> will give back a random number of test executed (from 0 to 9).
> If you specify the test name with -Dtest= the number of tests is always 9 (as
> expected).
> Building will take time, but there is a single test to execute.
> It's fragile: I tried to move the test to a difference package and the
> problem was not reproducable anymore. But I do reproduce it on a clean
> install with the branch above, and I do reproduce it all the time on our test
> suite, on different Linux machines.
>
> test code:
> {code}
> package org.apache.hadoop.hbase.regionserver;
> import java.util.*;
> @org.junit.runner.RunWith(org.junit.runners.Parameterized.class)
> @org.junit.experimental.categories.Category(org.apache.hadoop.hbase.S1Tests.class)
> public class TestSurefire {
> @org.junit.runners.Parameterized.Parameters
> public static Collection parameters() {
> ArrayList configurations = new ArrayList();
> for (int i = 1; i < 10; i++) {
> configurations.add(new Object[] { i });
> }
> return configurations;
> }
> public TestSurefire(Object o) {
> }
> @org.junit.Test
> public void testM() {
> }
> }
> {code}
> settings
> {code}
>
> maven-surefire-plugin
> 2.14
>
> true
> 2
> org.apache.hadoop.hbase.S1Tests
> true
>
>
> {code}
> Example of output:
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
> or
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Running org.apache.hadoop.hbase.regionserver.TestSurefire
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> Results :
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-985) Some Parameterized tests are not executed (or not reported)
[
https://jira.codehaus.org/browse/SUREFIRE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323609#comment-323609
]
Nicolas Liochon commented on SUREFIRE-985:
--
The full story is in HBASE-4763 and HBASE-4955, but basically it was just to
get the features we needed (categorization and parallelization) before they
were officially integrated in surefire. When I did it, I was not expecting that
going back to the official version will take more than a year :-). We're close
now, I think the last issue is SUREFIRE-969. We also patched JUnit, and as
they release a version a year we had to wait as well.
If I list my pain points, or what we did, it would be:
- all this work on categories/parallelisation, it's integrated now.
- the double path junit4 / junit47: changing some setting was going to a
totally different behavior in junit, so we discovered new bugs
- when a process dies or does not terminate, surefire does not always says
there is an issue nor kill the process. We added some ps | jstack | kill to do
that (see zombie related stuff in
https://github.com/apache/hbase/blob/trunk/dev-support/test-patch.sh).
- we added a junit listener to add some info on the context. Having the
workload of the machine, the number of threads, this kind of things, helps when
the tests don't work as expected.
- timeouts are difficult to manage. People use test timeout to workaround that
when surefire kills a process, you don't know what was executed. So they put
the timeout in the test vs. the global surefire timeout. And then if the build
machine is too slow your test suite becomes flaky.
> Some Parameterized tests are not executed (or not reported)
> ---
>
> Key: SUREFIRE-985
> URL: https://jira.codehaus.org/browse/SUREFIRE-985
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.14
> Environment: linux, 2 *4 cores, 32 Gb RAM (The sample does not work
> on Windows)
>Reporter: Nicolas Liochon
>Assignee: Andreas Gudian
>Priority: Critical
> Fix For: 2.15
>
>
> The test itself does nothing. The problem occurs when you have a lot of test
> classes with different categories, that's why I haven't been able to extract
> it (I suppose generating test classes would work): the report 'forgets' some
> tests.
> here is a branch I created to reproduce the issue:
> {code}
> git clone -b surefire git://github.com/nkeywal/hbase.git
> mvn clean install -D skipTests
> {code}
> There is a lot of third parties and code. Then:
> {code}
> mvn test -pl hbase-server
> {code}
> will give back a random number of test executed (from 0 to 9).
> If you specify the test name with -Dtest= the number of tests is always 9 (as
> expected).
> Building will take time, but there is a single test to execute.
> It's fragile: I tried to move the test to a difference package and the
> problem was not reproducable anymore. But I do reproduce it on a clean
> install with the branch above, and I do reproduce it all the time on our test
> suite, on different Linux machines.
>
> test code:
> {code}
> package org.apache.hadoop.hbase.regionserver;
> import java.util.*;
> @org.junit.runner.RunWith(org.junit.runners.Parameterized.class)
> @org.junit.experimental.categories.Category(org.apache.hadoop.hbase.S1Tests.class)
> public class TestSurefire {
> @org.junit.runners.Parameterized.Parameters
> public static Collection parameters() {
> ArrayList configurations = new ArrayList();
> for (int i = 1; i < 10; i++) {
> configurations.add(new Object[] { i });
> }
> return configurations;
> }
> public TestSurefire(Object o) {
> }
> @org.junit.Test
> public void testM() {
> }
> }
> {code}
> settings
> {code}
>
> maven-surefire-plugin
> 2.14
>
> true
> 2
> org.apache.hadoop.hbase.S1Tests
> true
>
>
> {code}
> Example of output:
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
> or
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimit
[jira] (MDEP-406) skip is ignored
H.-C. Gürsoy created MDEP-406:
-
Summary: skip is ignored
Key: MDEP-406
URL: https://jira.codehaus.org/browse/MDEP-406
Project: Maven 2.x Dependency Plugin
Issue Type: Bug
Affects Versions: 2.7
Environment: Maven 3.0.4, Dependency Plugin 2.7
Reporter: H.-C. Gürsoy
I've a build there I've to skip dependency resolution.
According to the 2.7 documentation, using the skip parameter should prevent
from running the whole plugin execution.
Call mvn with -Dmdep.skip=true or setting skip to true in the plugin
configuration with
{code}
org.apache.maven.plugins
maven-dependency-plugin
2.7
true
{code}
is allways ignored.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5466) Maven 3.0.5 doesn't send credentials for *
Justin Garrick created MNG-5466:
---
Summary: Maven 3.0.5 doesn't send credentials for
*
Key: MNG-5466
URL: https://jira.codehaus.org/browse/MNG-5466
Project: Maven 2 & 3
Issue Type: Bug
Affects Versions: 3.0.5
Environment: Win Server 2012 x64, JDK7u17 x64, Maven 3.0.5
Reporter: Justin Garrick
Attachments: bad-settings.xml, workaround-settings.xml
When {code:xml}*{code} is used to create a "mirror-any"
setup as described
[here|http://wiki.jfrog.org/confluence/display/rtf/configuring+artifacts+resolution],
Maven 3.0.5 does not send credentials. * is documented as a valid option in
the [Maven
documentation|http://maven.apache.org/guides/mini/guide-mirror-settings.html].
This seems to be a regression as this functionality worked as expected in Maven
3.0.4. Specifying a {code:xml}{code} for each {code:xml}{code}
seems to function as a temporary workaround.
See the {{bad-settings.xml}} attachment that demonstrates the problem and
{{workaround-settings.xml}} that demonstrates the workaround.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-361) Confluence: figure captions not rendered
[
https://jira.codehaus.org/browse/DOXIA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323646#comment-323646
]
Robert Scholte commented on DOXIA-361:
--
I start to understand the confusion.
{{org.apache.maven.doxia.sink.XhtmlBaseSink.figure()}} is marked as deprecated,
but {{org.apache.maven.doxia.sink.Sink.figure()}} not.
This is a weird situation, where the implementation decided to deprecate a
method from the API.
So the {{ConfluenceParser}} can call {{figure()}} unless the {{XhtmlBaseSink}}
implementation is used.
We shouldn't accept special cases.
There are 2 options: deprecate {{org.apache.maven.doxia.sink.Sink.figure()}} or
fix {{org.apache.maven.doxia.sink.XhtmlBaseSink.figure()}}. Agree?
> Confluence: figure captions not rendered
>
>
> Key: DOXIA-361
> URL: https://jira.codehaus.org/browse/DOXIA-361
> Project: Maven Doxia
> Issue Type: Bug
> Components: Module - Confluence
>Affects Versions: 1.1
>Reporter: Lukas Theussl
>Assignee: Robert Scholte
> Attachments: DOXIA-361.patch
>
>
> Figure captions seem to go into the attribute, ie they are not
> rendered in the xhtml output.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5467) intermittent "ProtocolException: The server failed to respond with a valid HTTP response"
Igor Fedorenko created MNG-5467: --- Summary: intermittent "ProtocolException: The server failed to respond with a valid HTTP response" Key: MNG-5467 URL: https://jira.codehaus.org/browse/MNG-5467 Project: Maven 2 & 3 Issue Type: Bug Affects Versions: 3.0.5 Reporter: Igor Fedorenko Building projects with maven 3.0.5 I regularly get "ProtocolException: The server failed to respond with a valid HTTP response" when resolving dependencies from repository.sonatype.org. From what I can tell this is caused by a bug in httpclient, which I reported as https://issues.apache.org/jira/browse/HTTPCLIENT-1340 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-361) Confluence: figure captions not rendered
[ https://jira.codehaus.org/browse/DOXIA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323649#comment-323649 ] Lukas Theussl commented on DOXIA-361: - Hmm, I hadn't realized that... From an objective point of view, I'd certainly go for option 2: XhtmlBaseSink.figure() should just forward to XhtmlBaseSink.figure( null ). Unfortunately, I don't remember the details but I suppose there were some backward-compat arguments to keep it the way it is, as otherwise I would not have specifically added the note linked above. > Confluence: figure captions not rendered > > > Key: DOXIA-361 > URL: https://jira.codehaus.org/browse/DOXIA-361 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence >Affects Versions: 1.1 >Reporter: Lukas Theussl >Assignee: Robert Scholte > Attachments: DOXIA-361.patch > > > Figure captions seem to go into the attribute, ie they are not > rendered in the xhtml output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-985) Some Parameterized tests are not executed (or not reported)
[
https://jira.codehaus.org/browse/SUREFIRE-985?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian closed SUREFIRE-985.
---
Resolution: Fixed
Fixed with 199c6162596b19d5b6e25cc0c3706bd657d92b1e
> Some Parameterized tests are not executed (or not reported)
> ---
>
> Key: SUREFIRE-985
> URL: https://jira.codehaus.org/browse/SUREFIRE-985
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.14
> Environment: linux, 2 *4 cores, 32 Gb RAM (The sample does not work
> on Windows)
>Reporter: Nicolas Liochon
>Assignee: Andreas Gudian
>Priority: Critical
> Fix For: 2.15
>
>
> The test itself does nothing. The problem occurs when you have a lot of test
> classes with different categories, that's why I haven't been able to extract
> it (I suppose generating test classes would work): the report 'forgets' some
> tests.
> here is a branch I created to reproduce the issue:
> {code}
> git clone -b surefire git://github.com/nkeywal/hbase.git
> mvn clean install -D skipTests
> {code}
> There is a lot of third parties and code. Then:
> {code}
> mvn test -pl hbase-server
> {code}
> will give back a random number of test executed (from 0 to 9).
> If you specify the test name with -Dtest= the number of tests is always 9 (as
> expected).
> Building will take time, but there is a single test to execute.
> It's fragile: I tried to move the test to a difference package and the
> problem was not reproducable anymore. But I do reproduce it on a clean
> install with the branch above, and I do reproduce it all the time on our test
> suite, on different Linux machines.
>
> test code:
> {code}
> package org.apache.hadoop.hbase.regionserver;
> import java.util.*;
> @org.junit.runner.RunWith(org.junit.runners.Parameterized.class)
> @org.junit.experimental.categories.Category(org.apache.hadoop.hbase.S1Tests.class)
> public class TestSurefire {
> @org.junit.runners.Parameterized.Parameters
> public static Collection parameters() {
> ArrayList configurations = new ArrayList();
> for (int i = 1; i < 10; i++) {
> configurations.add(new Object[] { i });
> }
> return configurations;
> }
> public TestSurefire(Object o) {
> }
> @org.junit.Test
> public void testM() {
> }
> }
> {code}
> settings
> {code}
>
> maven-surefire-plugin
> 2.14
>
> true
> 2
> org.apache.hadoop.hbase.S1Tests
> true
>
>
> {code}
> Example of output:
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Results :
> Tests run: 0, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
> or
> {noformat}
> ---
> T E S T S
> ---
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> parallel='none', perCoreThreadCount=true, threadCount=2,
> useUnlimitedThreads=false
> Running org.apache.hadoop.hbase.regionserver.TestSurefire
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.001 sec
> Results :
> Tests run: 3, Failures: 0, Errors: 0, Skipped: 0
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> {noformat}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian updated SUREFIRE-969: Fix Version/s: 2.15 > Log line on screen output > - > > Key: SUREFIRE-969 > URL: https://jira.codehaus.org/browse/SUREFIRE-969 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.14 >Reporter: Nicolas Liochon >Assignee: Andreas Gudian >Priority: Trivial > Fix For: 2.15 > > > parallel='none', perCoreThreadCount=true, threadCount=2, > useUnlimitedThreads=false > This log line is more for debugging, it would be great if it would be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Andreas Gudian closed SUREFIRE-969. --- Resolution: Fixed Moved it to a one-time-only printed INFO log line. > Log line on screen output > - > > Key: SUREFIRE-969 > URL: https://jira.codehaus.org/browse/SUREFIRE-969 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.14 >Reporter: Nicolas Liochon >Assignee: Andreas Gudian >Priority: Trivial > Fix For: 2.15 > > > parallel='none', perCoreThreadCount=true, threadCount=2, > useUnlimitedThreads=false > This log line is more for debugging, it would be great if it would be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-969) Log line on screen output
[ https://jira.codehaus.org/browse/SUREFIRE-969?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323653#comment-323653 ] Nicolas Liochon commented on SUREFIRE-969: -- Thanks a lot, Andreas! Do you have a date in mind for the 2.15? > Log line on screen output > - > > Key: SUREFIRE-969 > URL: https://jira.codehaus.org/browse/SUREFIRE-969 > Project: Maven Surefire > Issue Type: Bug > Components: Junit 4.7+ (parallel) support >Affects Versions: 2.14 >Reporter: Nicolas Liochon >Assignee: Andreas Gudian >Priority: Trivial > Fix For: 2.15 > > > parallel='none', perCoreThreadCount=true, threadCount=2, > useUnlimitedThreads=false > This log line is more for debugging, it would be great if it would be removed. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-834) release:prepare fails when a system property starting with dependency is given
Mirko Friedenhagen created MRELEASE-834:
---
Summary: release:prepare fails when a system property starting
with dependency is given
Key: MRELEASE-834
URL: https://jira.codehaus.org/browse/MRELEASE-834
Project: Maven 2.x Release Plugin
Issue Type: Bug
Components: prepare
Affects Versions: 2.4.1
Reporter: Mirko Friedenhagen
When invoking {{mvn release:prepare}} with a system property starting with
dependency is set, the invocation will fail:
Sample:
{{mvn -e release:prepare -DdryRun=true -Ddependency.locations.enabled=false}}
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) on
project tljunit-parent: Execution default-cli of goal
org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
index out of range: -12 -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) on
project tljunit-parent: Execution default-cli of goal
org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
index out of range: -12
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:601)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
default-cli of goal org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare
failed: String index out of range: -12
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
range: -12
at java.lang.String.substring(String.java:1911)
at
org.apache.maven.shared.release.config.ReleaseUtils.loadResolvedDependencies(ReleaseUtils.java:256)
at
org.apache.maven.shared.release.config.ReleaseUtils.copyPropertiesToReleaseDescriptor(ReleaseUtils.java:172)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:271)
at
org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
[ERROR]
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please
read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
{code}
We did set {{dependency.locations.enabled=false}} in {{MAVEN_OPTS}} to speed up
{{site}} generation. As can be seen it is sufficient to set this as system
property during invocation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-361) Confluence: figure captions not rendered
[ https://jira.codehaus.org/browse/DOXIA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated DOXIA-361: - Component/s: Module - Xhtml Fix Version/s: 2.0 We probably have to break backwards compatibility, so pushing this forward to 2.0 > Confluence: figure captions not rendered > > > Key: DOXIA-361 > URL: https://jira.codehaus.org/browse/DOXIA-361 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence, Module - Xhtml >Affects Versions: 1.1 >Reporter: Lukas Theussl >Assignee: Robert Scholte > Fix For: 2.0 > > Attachments: DOXIA-361.patch > > > Figure captions seem to go into the attribute, ie they are not > rendered in the xhtml output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-982) systemPropertyVariables does not work, but the deprecated systemProperties works correctly
[
https://jira.codehaus.org/browse/SUREFIRE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian updated SUREFIRE-982:
Description:
I use the attached snippet below. I believe the syntax is correct. When I use
the systemPropertyVariables syntax the properties are not set. When I use the
older and now deprecated approach they are set correctly. The exaxt same POM
and code. The only difference is which snippet I uncomment.
{code}
org.apache.maven.plugins
maven-surefire-plugin
container
${container}
propertiesPath
${propertiesPath}
app-properties.runtime.url
${app-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
{code}
was:
I use the attached snippet below. I believe the syntax is correct. When I use
the systemPropertyVariables syntax the properties are not set. When I use the
older and now deprecated approach they are set correctly. The exaxt same POM
and code. The only difference is which snippet I uncomment.
org.apache.maven.plugins
maven-surefire-plugin
container
${container}
propertiesPath
${propertiesPath}
app-properties.runtime.url
${app-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
> systemPropertyVariables does not work, but the deprecated systemProperties
> works correctly
> --
>
> Key: SUREFIRE-982
> URL: https://jira.codehaus.org/browse/SUREFIRE-982
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.14
> Environment: windows 7, java 7
>Reporter: Ed Ost
>Assignee: Andreas Gudian
>
> I use the attached snippet below. I believe the syntax is correct. When I
> use the systemPropertyVariables syntax the properties are not set. When I
> use the older and now deprecated approach they are set correctly. The exaxt
> same POM and code. The only difference is which snippet I uncomment.
> {code}
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
>
> container
> ${container}
>
>
> propertiesPath
> ${propertiesPath}
>
>
> app-properties.runtime.url
> ${app-properties.runtime.url}
>
>
> container-properties.runtime.url
> ${container-properties.runtime.url}
>
>
> container-properties.runtime.url
> ${container-properties.runtime.url}
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-982) systemPropertyVariables does not work, but the deprecated systemProperties works correctly
[
https://jira.codehaus.org/browse/SUREFIRE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Gudian updated SUREFIRE-982:
Description:
I use the attached snippet below. I believe the syntax is correct. When I use
the systemPropertyVariables syntax the properties are not set. When I use the
older and now deprecated approach they are set correctly. The exaxt same POM
and code. The only difference is which snippet I uncomment.
{code:xml}
org.apache.maven.plugins
maven-surefire-plugin
container
${container}
propertiesPath
${propertiesPath}
app-properties.runtime.url
${app-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
{code}
was:
I use the attached snippet below. I believe the syntax is correct. When I use
the systemPropertyVariables syntax the properties are not set. When I use the
older and now deprecated approach they are set correctly. The exaxt same POM
and code. The only difference is which snippet I uncomment.
{code}
org.apache.maven.plugins
maven-surefire-plugin
container
${container}
propertiesPath
${propertiesPath}
app-properties.runtime.url
${app-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
container-properties.runtime.url
${container-properties.runtime.url}
{code}
> systemPropertyVariables does not work, but the deprecated systemProperties
> works correctly
> --
>
> Key: SUREFIRE-982
> URL: https://jira.codehaus.org/browse/SUREFIRE-982
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.14
> Environment: windows 7, java 7
>Reporter: Ed Ost
>Assignee: Andreas Gudian
>
> I use the attached snippet below. I believe the syntax is correct. When I
> use the systemPropertyVariables syntax the properties are not set. When I
> use the older and now deprecated approach they are set correctly. The exaxt
> same POM and code. The only difference is which snippet I uncomment.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
>
> container
> ${container}
>
>
> propertiesPath
> ${propertiesPath}
>
>
> app-properties.runtime.url
> ${app-properties.runtime.url}
>
>
> container-properties.runtime.url
> ${container-properties.runtime.url}
>
>
> container-properties.runtime.url
> ${container-properties.runtime.url}
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MRELEASE-834) release:prepare fails when a system property starting with dependency is given
[
https://jira.codehaus.org/browse/MRELEASE-834?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mirko Friedenhagen updated MRELEASE-834:
Attachment: MRELEASE-834.patch
Patch with a quick fix.
> release:prepare fails when a system property starting with dependency is given
> --
>
> Key: MRELEASE-834
> URL: https://jira.codehaus.org/browse/MRELEASE-834
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
>Reporter: Mirko Friedenhagen
> Attachments: MRELEASE-834.patch
>
>
> When invoking {{mvn release:prepare}} with a system property starting with
> dependency is set, the invocation will fail:
> Sample:
> {{mvn -e release:prepare -DdryRun=true -Ddependency.locations.enabled=false}}
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) on
> project tljunit-parent: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
> index out of range: -12 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare
> (default-cli) on project tljunit-parent: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
> index out of range: -12
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
> index out of range: -12
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range: -12
> at java.lang.String.substring(String.java:1911)
> at
> org.apache.maven.shared.release.config.ReleaseUtils.loadResolvedDependencies(ReleaseUtils.java:256)
> at
> org.apache.maven.shared.release.config.ReleaseUtils.copyPropertiesToReleaseDescriptor(ReleaseUtils.java:172)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:271)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 20 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> We did set {{dependency.locations.enabled=false}} in {{MAVEN_OPTS}} to speed
> up {{site}} generation. As can be seen it is sufficient to set
[jira] (MRELEASE-834) release:prepare fails when a system property starting with dependency is given
[
https://jira.codehaus.org/browse/MRELEASE-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323656#comment-323656
]
Mirko Friedenhagen commented on MRELEASE-834:
-
And as a pull request in Github: https://github.com/apache/maven-release/pull/3
> release:prepare fails when a system property starting with dependency is given
> --
>
> Key: MRELEASE-834
> URL: https://jira.codehaus.org/browse/MRELEASE-834
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Affects Versions: 2.4.1
>Reporter: Mirko Friedenhagen
> Attachments: MRELEASE-834.patch
>
>
> When invoking {{mvn release:prepare}} with a system property starting with
> dependency is set, the invocation will fail:
> Sample:
> {{mvn -e release:prepare -DdryRun=true -Ddependency.locations.enabled=false}}
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare (default-cli) on
> project tljunit-parent: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
> index out of range: -12 -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare
> (default-cli) on project tljunit-parent: Execution default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
> index out of range: -12
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:225)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-cli of goal
> org.apache.maven.plugins:maven-release-plugin:2.4.1:prepare failed: String
> index out of range: -12
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:110)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by: java.lang.StringIndexOutOfBoundsException: String index out of
> range: -12
> at java.lang.String.substring(String.java:1911)
> at
> org.apache.maven.shared.release.config.ReleaseUtils.loadResolvedDependencies(ReleaseUtils.java:256)
> at
> org.apache.maven.shared.release.config.ReleaseUtils.copyPropertiesToReleaseDescriptor(ReleaseUtils.java:172)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.prepareRelease(PrepareReleaseMojo.java:271)
> at
> org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareReleaseMojo.java:232)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
> ... 20 more
> [ERROR]
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
> We did set {{dependency.locations.enabled=false}} in {{MAVEN_OPTS}} to
[jira] (SUREFIRE-982) systemPropertyVariables does not work, but the deprecated systemProperties works correctly
[
https://jira.codehaus.org/browse/SUREFIRE-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323657#comment-323657
]
Andreas Gudian commented on SUREFIRE-982:
-
I can't reproduce that. Could you please create a small sample project that
demonstrates the problem?
One guess that I can take: if the variables that you use are not set, then
{{systemPropertyVariables}} will produce mappings to {{null}}, while
systemProperties fills in a String with length 0. Perhaps that's what you
experience?
> systemPropertyVariables does not work, but the deprecated systemProperties
> works correctly
> --
>
> Key: SUREFIRE-982
> URL: https://jira.codehaus.org/browse/SUREFIRE-982
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.14
> Environment: windows 7, java 7
>Reporter: Ed Ost
>Assignee: Andreas Gudian
>
> I use the attached snippet below. I believe the syntax is correct. When I
> use the systemPropertyVariables syntax the properties are not set. When I
> use the older and now deprecated approach they are set correctly. The exaxt
> same POM and code. The only difference is which snippet I uncomment.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
>
>
>
> container
> ${container}
>
>
> propertiesPath
> ${propertiesPath}
>
>
> app-properties.runtime.url
> ${app-properties.runtime.url}
>
>
> container-properties.runtime.url
> ${container-properties.runtime.url}
>
>
> container-properties.runtime.url
> ${container-properties.runtime.url}
>
>
>
>
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-987) Provide user property for suiteXmlFile so that it can be passed from Maven Command line
Manmohan Veettil created SUREFIRE-987: - Summary: Provide user property for suiteXmlFile so that it can be passed from Maven Command line Key: SUREFIRE-987 URL: https://jira.codehaus.org/browse/SUREFIRE-987 Project: Maven Surefire Issue Type: Improvement Components: Maven Failsafe Plugin Affects Versions: 2.12 Environment: Mac 10.8.2 Reporter: Manmohan Veettil Can we have a way to run all the tests in a package? I know we can run all tests in a class using -Dit.test option. OR Can we define a user property for suiteXmlFiles or suiteXmlFile so that tests in multiple package can be run using maven fail-safe plugin. mvn clean install âDsuiteXmlFiles=test1.xml,test2.xml mvn clean install -DsuiteXmlFile=test1.xml Thanks, manmohanpv -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MNG-5468) Allow mojos to access the user properties
Michael Ekstrand created MNG-5468: - Summary: Allow mojos to access the user properties Key: MNG-5468 URL: https://jira.codehaus.org/browse/MNG-5468 Project: Maven 2 & 3 Issue Type: Wish Affects Versions: 3.0.4 Reporter: Michael Ekstrand There does not seem to be any way to obtain the user properties in a mojo. The mojo can get the model properties from the project, but not the user properties specified on the Maven command line. This is problematic for mojos that want to consult them for additional configuration to pass on to other things (user classes, scripts, etc.). -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (DOXIA-361) Confluence: figure captions not rendered
[ https://jira.codehaus.org/browse/DOXIA-361?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=323662#comment-323662 ] Lukas Theussl commented on DOXIA-361: - Not sure if I'm missing something but I think this issue, concerning only the confluence parser, should be fixed in 1.x. Fixing the XhtmlBaseSink should probably go into 2.0. > Confluence: figure captions not rendered > > > Key: DOXIA-361 > URL: https://jira.codehaus.org/browse/DOXIA-361 > Project: Maven Doxia > Issue Type: Bug > Components: Module - Confluence, Module - Xhtml >Affects Versions: 1.1 >Reporter: Lukas Theussl >Assignee: Robert Scholte > Fix For: 2.0 > > Attachments: DOXIA-361.patch > > > Figure captions seem to go into the attribute, ie they are not > rendered in the xhtml output. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
