[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... ] Mickael Istria commented on JBIDE-15135: ---------------------------------------- Here is what I'm working on about those metadata: * Merge all files in a single (JSON) file, that would include the necessary data (at least content of current build.properties and GIT_REVISION.txt) * Move this file in "buildinfo.json" just under repository, besides of content.jar/artifacts.jar * Have a mojo to generate those files * For any build, the Mojo introspects the project definition and deduces what are the upstream repositories. From them, it pulls there buildinfo.properties and includes the interesting parts in its own build.properties. With that, for any build, component or aggregate, we can use the same mojo, data is in a single file, which is together with the p2 repository. This mojo is more or less ready at https://github.com/mickaelistria/jbosstools-maven-plugins/tree/JBIDE-15135 . It can be enabled for a given eclipse-repository with {code:xml} <build> <plugins> <plugin> <groupId>org.jboss.tools.tycho-plugins</groupId> <artifactId>repository-utils</artifactId> <version>0.22.0-SNAPSHOT</version> <executions> <execution> <id>generate-full-site</id> <phase>package</phase> <goals> <goal>create-full-site</goal> </goals> </execution> </executions> </plugin> </plugins> </build> {code} Output looks like https://gist.github.com/mickaelistria/380c3602dfbfca9e436b [~nickboldt] I believe we can start adopting it from now on. Do you see other metadata to include? Should we put references to the zips in those metadata ? -- This message was sent by Atlassian JIRA (v6.3.8#6338)