i'm all for the creation of a JBoss Tools
Orbit project in which we can add content after review that can
be shared
and properly versioned.
* Consider a small independent P2 update site that is built manually and locally at first then move
to automation when that is working
yes, sounds cool - create it as a standalone github project and we can go to set that up.
Questions for getting started:
* The hosting location for this P2 update site. Do I / Is it possible to have access to
download.jboss.org to upload such a site?
yes - I don't see a problem for that - we just need to figure out the rules/conventions for how this JBoss Tools Orbit should work.
i.e. it would be anything but eclipse plugins. The jars can't modify overall system state (i.e. versions of jboss-modules or was it logging changed system behavior that might be good for one plugin but terrible for others).
But yes, Definitely a big +1 for creation of a JBoss Tools Orbit kind of repo.