Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

maven aggregate don´t allow own results folder #106

Open
1 of 3 tasks
xexplorer42 opened this issue Dec 16, 2019 · 0 comments
Open
1 of 3 tasks

maven aggregate don´t allow own results folder #106

xexplorer42 opened this issue Dec 16, 2019 · 0 comments

Comments

@xexplorer42
Copy link

I'm submitting a ...

  • bug report
  • feature request
  • support request => Please do not submit support request here, see note at the top of this template.

What is the current behavior?

maven allure-maven Goal: allure:aggregate requires a result folder in the target folder, which is not configurable

Code:

Path target = Paths.get(child.getBuild().getDirectory());

It is not possible to aggregate several Maven modules if you have defined your own results folder
like this:
<resultsDirectory>${project.basedir}/allure-results</resultsDirectory>

If the current behavior is a bug, please provide the steps to reproduce and if possible a mvn allure:aggregate

What is the expected behavior?

results folder can be outside of the target folder

What is the motivation / use case for changing the behavior?

we wan´t to save the results and target is cleaned up during normal maven prozess

Please tell us about your environment:

Other information

Maven POM:

<reporting>
	<plugins>
		<plugin>
			<artifactId>maven-jxr-plugin</artifactId>
			<version>2.3</version>
			<reportSets>
				<reportSet>
					<id>aggregate</id>
					<inherited>false</inherited>
					<reports>
						<report>aggregate</report>
					</reports>
				</reportSet>
			</reportSets>
		</plugin>
		<plugin>
			<artifactId>maven-project-info-reports-plugin</artifactId>
			<version>3.0.0</version>
		</plugin>
		<plugin>
			<groupId>io.qameta.allure</groupId>
			<artifactId>allure-maven</artifactId>
			<version>${allure-maven.version}</version>
			<configuration>
				<allureDownloadUrl>https://repo.maven.apache.org/maven2/io/qameta/allure/allure-commandline/${allure.version}/allure-commandline-${allure.version}.zip</allureDownloadUrl>
				<reportVersion>2.10.0</reportVersion>
				<resultsDirectory>${project.build.directory}/allure-results/</resultsDirectory>
				<reportDirectory>${project.build.directory}/site/allure</reportDirectory>
			</configuration>
		</plugin>
	</plugins>
</reporting>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant