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

[Mickael Istria (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13029993#comment-13029993 ] 

Mickael Istria commented on JBIDE-15135:
----------------------------------------

{quote}When is it available? How is it made available? How do you test this offline? How does the mojo know about upstream projects, since none of the jobs are linked in Jenkins?{quote}
The mojo looks at the site referenced as "repositories" with layout type "p2" in the current reactor. Then it looks for a file ${repositoryUrl}/buildinfo.json for each referenced repository.
To test it, generate for example a site for openshift module with the mojo, so that buildinfo.json exists, then try to build central similarily, but overriding the location for openshift to local one on filesystem. You'll see the upstream block will include some data from openshift.

{quote}Why not also dump variables we know are important which are resolved from parent pom? Why only worry about CLI variables, not defaults too?{quote}
The default ones can be deduced from that parent pom so I don't believe it's necessary to repeat them here. But if you think it's important, we can have a "cliOptions" block with the current behaviour, and a resolvedMavenProperties block with the main properties.

{quote} Is it a lot of work to collect that information? {quote}
I'm not concerned about the difficulty of collecting information, but more about giving interesting and easy to read reports. Being greedy in reports makes them more difficult to read. My strategy is to put them in only if we use them regularly, not if we may need it sometimes.
But if it's a blocker for you, I'm fine with adding JVM and OS info to the report.

> Attach metadata during assembly instead of publish time
> -------------------------------------------------------
>
>                 Key: JBIDE-15135
>                 URL: https://issues.jboss.org/browse/JBIDE-15135
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: build
>            Reporter: Mickael Istria
>            Assignee: Mickael Istria
>             Fix For: 4.2.x
>
>
> In order to make it easier to deal with Nexus and to have an homogeneous way to access build metadata (commit id), it would be interesting to move creation of metadata at assembly time (same time as when we create index and so on), and put it directly into the site.
> Then whether we use Nexus or a home-made publication, we are sure that we can access metadata whenever we can access the binaries.



--
This message was sent by Atlassian JIRA
(v6.3.11#6341)