@Mickael:
Please capture the list of metadata created by publish.sh in this JIRA
[1] so we have a complete set. We can later sort them into "things we
could mojo'ify" and "things we no longer need".
[1]
https://issues.jboss.org/browse/JBIDE-13835
On 10/24/2013 05:39 AM, Mickael Istria wrote:
On 10/23/2013 10:18 PM, Nick Boldt wrote:
> All that metadata, if still useful, would have to migrate to a mojo in
> order to be done at release-time instead of at build-time, if the plan
> is to trash publish.sh as the bridge between Jenkins job and resulting
> build folder.
>
+1 to create metadata in a Mojo and attach the metadata files to the
Maven artifact so they get published along with the p2 site.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <
http://www.jboss.org/tools>
My blog <
http://mickaelistria.wordpress.com> - My Tweets
<
http://twitter.com/mickaelistria>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com