[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kristian Rosenvold closed SUREFIRE-846.
---
Resolution: Fixed
Fix Version/s: 2.12.2
Assignee: Kristian Rosenvold
Fixed in r1369919. The "surefire" directory is now only left around when maven
is run with the -X option for increased logging. Thanks for the patch!
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
>Assignee: Kristian Rosenvold
> Fix For: 2.12.2
>
> Attachments: SUREFIRE-846.patch
>
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296432#comment-296432
]
Tom Vaughan commented on SUREFIRE-846:
--
But you should "More Actions->Add Vote" on this ticket to raise its profile.
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
> Attachments: SUREFIRE-846.patch
>
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296433#comment-296433
]
Martin Todorov commented on SUREFIRE-846:
-
Well, since I filed it myself, I can't vote. :)
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
> Attachments: SUREFIRE-846.patch
>
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296430#comment-296430
]
Tom Vaughan commented on SUREFIRE-846:
--
| When can we have it applied?
No idea...I'm not a contributor ;-) but I agree it is pretty annoying.
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
> Attachments: SUREFIRE-846.patch
>
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296427#comment-296427
]
Martin Todorov commented on SUREFIRE-846:
-
Excellent! The patch looks great! :)
When can we have it applied? (It's not like this is a blocker issue or
anything, but it's quite a bit annoying).
Thanks!
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
> Attachments: SUREFIRE-846.patch
>
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tom Vaughan updated SUREFIRE-846:
-
Attachment: SUREFIRE-846.patch
Attaching a proposed patch that cleans up the empty surefire directory after
each provider is executed. I used the apache commons io's "FileUtils" class to
leverage their deleteDirectory() method which I think is appropriate in this
case. If you run the patch from the root of the svn checkout (e.g. you're in
the same directory as the master pom.xml file) things should patch up nicely.
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
> Attachments: SUREFIRE-846.patch
>
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=293000#comment-293000
]
Martin Todorov commented on SUREFIRE-846:
-
Basically, it doesn't make sense to me to keep the empty directory, if the
build has succeeded. And, instead of having a bunch of surefire directories in
the target folder, they could simply be placed under the same root.
That's my suggestion.
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292999#comment-292999
]
Martin Todorov commented on SUREFIRE-846:
-
Grzegorz, if the surefire directory is empty (whether it's in target or
somewhere else), I think it should be removed upon successful tests.
Under Linux, if you want to have the target/surefire-reports path autocompleted
for you, when you hit TAB, it will currently stop at target/surefire. Clearly,
you can enter the next symbols yourself, but it wasn't like this up until
recent versions of the plugin.
The proposed structure will help keep the surefire files tidy (if you really,
must have the surefire directory after the tests).
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292998#comment-292998
]
Grzegorz Slowikowski commented on SUREFIRE-846:
---
What will you gain with the changed directories layout? You will have empty
"surefire/tmp" directory instead of "surefire". What the empty directory has to
do with console autocomplete?
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
[
https://jira.codehaus.org/browse/SUREFIRE-846?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=292990#comment-292990
]
Martin Todorov commented on SUREFIRE-846:
-
I had initially posted a question for this on stackoverflow.com
[here|http://stackoverflow.com/questions/9478695/why-is-the-maven-surefire-plugin-creating-two-surefire-directories-in-the-pro].
> Maven surefire plugin creates two surefire* directories in the
> ${project.build.directory}
> -
>
> Key: SUREFIRE-846
> URL: https://jira.codehaus.org/browse/SUREFIRE-846
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.12
> Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
>Reporter: Martin Todorov
>
> Hi,
> This is somewhere between a bug and a feature. I am filing it as per
> krosenv's suggestion.
> The Maven surefire plugin is creating two surefire* directories in the
> ${project.build.directory}:
> - surefire (empty after test executions)
> - surefire-reports (containing the output of the tests)
> I find this rather annoying. As far as I understand, the surefire directory
> is used during the testing and it contains some temporary stuff which is
> removed after the execution of the tests.
> I have tried looking up the option to remove the surefire directory, but I
> can seem to find it. The thing is -- I have other projects that don't have
> this empty directory, just the surefire-reports.
> This empty directory breaks tab autocomplete in the console which sort of
> bugs me, mainly since the directory is empty.
> In addition, this is just the test plugin, not the reporting one. There is no
> section in the project (not any parent).
> This is my surefire plugin setup:
> {code}
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.12
>
>
> **/*Abstr*Test*
>
>
>
> {code}
> If this directory is really necessary, I would like to propose the following
> options:
> 1) Make surefire use one directory:
> {code}
> - surefire
> | |- reports
> | |- tmp
> {code}
> This way things will be tidy.
> 2) Have an option for the plugin which allows you to turn on the preserving
> of this directory (I think it should be removed by default).
> Regards,
> Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (SUREFIRE-846) Maven surefire plugin creates two surefire* directories in the ${project.build.directory}
Martin Todorov created SUREFIRE-846:
---
Summary: Maven surefire plugin creates two surefire* directories
in the ${project.build.directory}
Key: SUREFIRE-846
URL: https://jira.codehaus.org/browse/SUREFIRE-846
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.12
Environment: Maven 3.0.4 ; Java 1.6.0_19 ; Linux 2.6.36.2
Reporter: Martin Todorov
Hi,
This is somewhere between a bug and a feature. I am filing it as per krosenv's
suggestion.
The Maven surefire plugin is creating two surefire* directories in the
${project.build.directory}:
- surefire (empty after test executions)
- surefire-reports (containing the output of the tests)
I find this rather annoying. As far as I understand, the surefire directory is
used during the testing and it contains some temporary stuff which is removed
after the execution of the tests.
I have tried looking up the option to remove the surefire directory, but I can
seem to find it. The thing is -- I have other projects that don't have this
empty directory, just the surefire-reports.
This empty directory breaks tab autocomplete in the console which sort of bugs
me, mainly since the directory is empty.
In addition, this is just the test plugin, not the reporting one. There is no
section in the project (not any parent).
This is my surefire plugin setup:
{code}
org.apache.maven.plugins
maven-surefire-plugin
2.12
**/*Abstr*Test*
{code}
If this directory is really necessary, I would like to propose the following
options:
1) Make surefire use one directory:
{code}
- surefire
| |- reports
| |- tmp
{code}
This way things will be tidy.
2) Have an option for the plugin which allows you to turn on the preserving of
this directory (I think it should be removed by default).
Regards,
Martin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
