+1.
The only challenge might be packaging of any library jars the tools use.
Ideally, we could avoid redundant copies of too many jars - i.e. where
tool A, tool B, and the RHQ Server itself all have a dep on the same
library jar, we could possibly have them all use the same copy of the
jar; whether this is worth the trouble depends on how much space these
redundant jars consume.
I'd also include a README.txt for each tool.
On 01/25/2011 09:10 AM, Heiko W.Rupp wrote:
Hi,
we have developer tools
- standalone plugin container (see e.g.
http://community.jboss.org/community/jopr/blog/2011/01/20/using-the-stand...
)
- plugin generator
- ??
I think those should be delivered with a RHQ release - perhaps in a new top level
directory, so that developers have
easier access to them.
WDYT?
Heiko
--
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer(a)redhat.com