Sometimes the best way to see if something is actually still used /
needed is to move it and see who screams. :)
Asking in advance often leads to replies like "oh, just leave it, this
is a bad time for churn"... like every time I've pushed to move a
project or two to github. :P
Anyway, if you want them back in the root, fine. I Just did a few `svn
move` commands to move them, so reverting those commits should be safe.
But I have to ask... why are you so attached to code that we don't
publish? Surely if it's not healthy enough to be pushed to jboss.org
part of JBT, it's not worth keeping? And if you'd happily have me delete
it, then why should I put it back?
On 11/25/2011 08:04 AM, Max Rydahl Andersen wrote:
On Nov 24, 2011, at 23:28, Nick Boldt wrote:
> FYI, I've moved a few things out of the root and into a new child folder
> called "DEPRECATED" because I'm fairly certain we don't need them
> more (we don't build or publish them, or they've moved upstream).
come on! why are you doing such rearranging without at least warning/confirming first ?
labs, profiler and working set were all fine, they build fine and you can import and use
them as is.
Makes no sense to move them - if they aren't needed *delete* them.
But these are and were fine at their place. Except the drools one which always been
If stuff needs to be moved around lets do it in a *sensible* way - not this abrupt
Putting stuff in big capital letters is really not useful!
> Note that the only piece of drools we still actively maintain is a bot
> test . All the rest of drools is entirely upstream.
> One thing I wasn't 100% sure about was the docs associated w/ these
> projects, particularly drools. Isaac: do we own the docs , or are
> they also upstream?
>  http://anonsvn.jboss.org/repos/jbosstools/trunk/DEPRECATED/drools/docs/
Another reason why this move shouldn't have happened.
Could you please revert these back ?
I would do it myself but the changes seem to have been done over multiple commits so not
sure what sideffects it will have to just revert those commits ?
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio