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

Unable to build using Maven version 2.x, assuming version 3.0+ required #890

Closed
SeanRMunoz opened this issue Nov 16, 2016 · 3 comments
Closed

Comments

@SeanRMunoz
Copy link
Contributor

Attempted build using Maven version 2.2.1 and received the following error:
[see attached: compile-os4j302-maven221-error.txt]

[INFO] ------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO] ------------------------------------------------------------------------
[INFO] Error installing artifact: File /home/dorado/dev/repos/openstack4j/core/target/features.xml does not exist

Subsequent build using Maven version 3.3.9 successful. Suggest using maven-enforcer-plugin to stop/fail build if using less than Maven version 3.0?

Suggested addition to pom.xml:

<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-enforcer-plugin</artifactId>
<version>1.4.1</version>
<executions>
  <execution>
	<id>enforce-maven</id>
	<goals>
	  <goal>enforce</goal>
	</goals>
	<configuration>
	  <rules>
		<requireMavenVersion>
		  <version>3.0</version>
		  <message>Build FAILURE: Maven version 3.0+ REQUIRED!</message>
		</requireMavenVersion>
	  </rules>    
	</configuration>
  </execution>
</executions>
</plugin>

SeanRMunoz added a commit to SeanRMunoz/openstack4j that referenced this issue Nov 16, 2016
@auhlig
Copy link
Member

auhlig commented Nov 17, 2016

Hi @SeanRMunoz,
Good point.
Thanks for filing the issue and submitting the PR.

auhlig added a commit that referenced this issue Nov 19, 2016
Issue #890 - Enforce build requirement of Maven version 3.0+
@auhlig
Copy link
Member

auhlig commented Nov 19, 2016

Merged. Thanks again. Can we close this issue @SeanRMunoz ?

@SeanRMunoz
Copy link
Contributor Author

Yes @auhlig this issue #890 has been resolved. Thank you.

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

2 participants