Jump to content
We've recently updated our Privacy Statement, available here ×

mvn clean install - Error building POM


bdgregg

Recommended Posts

Having problems Building JasperServer Source Code - Following the manual for 2.0.1. I know the problem is with the settings.xml or another file in the .m2 directory but I'm not sure which setting is wrong. Please point me in the right direction. Here is the error...

 

Code:
[iNFO] Scanning for projects...
[iNFO] ------------------------------------------------------------------------
[ERROR] FATAL ERROR
[iNFO] ------------------------------------------------------------------------
[iNFO] Error building POM (may not be this project's POM).


Project ID: com.jaspersoft.jasperserver:jasperserver-export-tool-package
POM Location: /usr/local/src/jasperserver-2.0.1/jasperserver/jasperserver-export-package/pom.xml
Validation Messages:

[0] 'dependencies.dependency.artifactId' with value '${repository.database.driver.artifactId}' does not match a valid id pattern.
[1] 'dependencies.dependency.groupId' with value '${repository.database.driver.groupId}' does not match a valid id pattern.


Reason: Failed to validate POM
Link to comment
Share on other sites

  • Replies 2
  • Created
  • Last Reply

Top Posters In This Topic

Top Posters In This Topic

It looks to be a problem in the settings.xml. The settings.xml sets these two values and they are used in later parts of the build.

 

Here is what I have set for these two:

 

<repository.database.driver.groupId>mysql</repository.database.driver.groupId>

<repository.database.driver.artifactId>mysql-connector-java</repository.database.driver.artifactId>

<repository.database.driver.version>3.1.11</repository.database.driver.version>

 

So, if the build and these values are working nicely, I will end up with the mysql driver jar in the following directory:

 

<user-home>/.m2/repository/mysql/mysql-connector-java/3.1.11

 

-Tony

Link to comment
Share on other sites

Tony,

 

I had those options set.

 

But the problem seems to be resolved, added the following to settings.xml file:

<localRepository>/usr/local/maven-repo</localRepository>

 

Moved my .m2 files to another location.

 

Then used...

 

mvn -s /usr/local/.m2/settings.xml clean install

 

Works but now have another problem with sockets that I'll post separately.

 

Thanks,

Brian.

Link to comment
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now

×
×
  • Create New...