[jbosstools-issues] [JBoss JIRA] (JBIDE-15135) Attach metadata during assembly instead of publish time

[ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-15135: ------------------------------------ I don't think we need zip file references for two reasons: a) they were originally added because we didn't have Eclipse-SourceReferences in the MANIFEST.MF files, and needed a way to collect all the upstream sources b) they have generic names (rather than timestamped/buildID'd) so they're not really useful UNLESS the zips themselves are colocated in the build folder, which we no longer need. As to the included metadata, we need: * build details (re: the server/VM config, JDK version/paths, etc.), eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-openshift_... * build log (only useful when things go wrong and access to Jenkins is slow/impossible, so not strictly REQUIRED, only helpful) * git revs for upstream sources, eg., http://download.jboss.org/jbosstools/builds/stable/4.1.2.Final.core/2014-... In trying to use the above locally, I've realized 3 things: a) you need to use <version>0.22.1-SNAPSHOT</version> as 0.22.0-SNAPSHOT is no longer available in Nexus or in your fork b) you need to run a build of something like jbosstools-build-sites/aggregate/site/pom.xml with -DtychoVersion=0.22.0, as repository-utils now depends on on that c) you need to build with JDK8, or get: {code} [ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site (generate-full-site) on project org.jboss.tools.site.core: Execution generate-full-site of goal org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site failed: An API incompatibility was encountered while executing org.jboss.tools.tycho-plugins:repository-utils:0.22.1-SNAPSHOT:create-full-site: java.lang.UnsupportedClassVersionError: org/json/JSONObject : Unsupported major.minor version 52.0 {code} So, I inserted the above block into jbosstools-build-sites/aggregate/site/pom.xml (and fixed the version to be 0.22.1-SNAPSHOT), then: {code} $➔ mvn --version Java HotSpot(TM) 64-Bit Server VM warning: ignoring option PermSize=128m; support was removed in 8.0 Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=256m; support was removed in 8.0 Apache Maven 3.1.1 (0728685237757ffbf44136acec0402957f723d9a; 2013-09-17 11:22:22-0400) Maven home: /opt/maven3 Java version: 1.8.0, vendor: Oracle Corporation Java home: /opt/jdk1.8.0/jre Default locale: en_US, platform encoding: UTF-8 OS name: "linux", version: "3.17.4-200.fc20.x86_64", arch: "amd64", family: "unix" $➔ mvn clean install -DtychoVersion=0.22.0{code} Results: {code:title=aggregate/site/target/fullSite/all/repo/buildInfo.json} { "upstream": {}, "properties": {}, "timestamp": 1419265316379, "revision": { "HEAD": "89898db85f9e38972360c42782247f0e2b7304b0", "knownReferences": [{ "ref": "JBIDE-18869", "name": "nickboldt", "url": "git@github.com:nickboldt/jbosstools-build-sites.git" }] } } {code} Should there be something in upstream and properties? What about details about the OS & JDK version? -- This message was sent by Atlassian JIRA (v6.3.11#6341)