[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: ------------------------------------ {quote}This is meant to go in the upstream block when upstream data is available{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}Same reason, it's reporting the value of the property from Jenkins (or CLI).{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? (Consider what you see in the Help > About > Eclipse Config view -- it contains BOTH things set CLI / eclipse.ini and also defaults pulled from the OS/system. I think we should do that too.) Re: OS/JDK details... we should include those. It's way better to just collect it at publish time than to have to go dig up the information later if something fails which is slave config specific, or is an OS-related problem. Is it a lot of work to collect that information? Surely you can just grab the output of `uname -a;java -version` ? -- This message was sent by Atlassian JIRA (v6.3.11#6341)