However, that build failed. Eventually I found that the build command on hudson included profiles, so then I tried building with
this still failed with
[ERROR] Failed to execute goal org.eclipse.cbi.maven.plugins:eclipse-jarsigner-plugin:1.0.5:sign (sign) on project org.eclipse.mat.report: Could not sign artifact org.eclipse.mat:org.eclipse.mat.report:eclipse-plugin:1.5.0-SNAPSHOT: Connection to http://build.eclipse.org:31338 refused: Operation timed out -> [Help 1]
just the "compile" goal did succeed, though. I'm not sure why "install" is trying to sign the artifacts -- I just want a locally published jar. It did work after I changed the phase of the "sign" execution to "deploy", instead of "verify".
Finally, the "updatesite" & "rcp" modules failed to build with
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-antrun-plugin:1.7:run (deploy) on project org.eclipse.mat.updatesite: An Ant BuildException has occured: Directory does not exist: /home/data/httpd/download.eclipse.org/mat/snapshots/update-site
I didn't care about those modules, so I just removed it from the parent pom, but maybe there should be another fix for that too? Should the build instructions be updated, or am I doing something else wrong?
If it matters at all, I am trying to publish a jar locally because I want to access MAT from within another java program, not as a plugin at all.
thanks,
Imran