-
Notifications
You must be signed in to change notification settings - Fork 308
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
adam-cli POM invalid: maven.build.timestamp #1004
Comments
CC @heuermh |
That expression is used in the About class here
It is repeated in the pom file as a workaround for a bug with the maven assembly plugin (I believe, would have to dig for context). I've never seen this maven error before, what version are you using? |
As an aside, why does Guacamole depend on the |
Ouch, found it, issue open since 2009. There is a workaround but I found it to be unreliable (on a different project). |
All of my downstream repos do, and I don't believe I've ever seen this error https://github.com/heuermh/adam-commands |
|
Good point, seems like we don't need it :) will remove it, but maybe still good to understand why the error was happening. |
Agreed. |
@heuermh I just cloned adam-commands, ran
|
Yeah just saw that, with [DEBUG] Skipped remote request for org.bdgenomics.adam:adam-cli_2.10:0.19.1-SNAPSHOT/maven-metadata.xml, locally installed metadata up-to-date.
[WARNING] The POM for org.bdgenomics.adam:adam-cli_2.10:jar:0.19.1-SNAPSHOT is invalid, transitive dependencies (if any) will not be available: 1 problem was encountered while building the effective model for org.bdgenomics.adam:adam-cli_2.10:0.19.1-SNAPSHOT
[ERROR] Resolving expression: '${maven.build.timestamp}': Detected the following recursive expression cycle in 'maven.build.timestamp': [maven.build.timestamp] @ |
Fixed by #1005 |
Guacamole (which depends on ADAM) is showing an error parsing the adam-cli POM; here is debug output from running
mvn -X package
there:This line seems to be the culprit.
Anyone have context on why it's there / what it's supposed to be doing?
The text was updated successfully, but these errors were encountered: