Thanks, so I'm still missing answers to:
Why us this not just build and published as any other plugins we use ? At least while its
maturing so we don't need yet another p2 site to mirror/maintain ?
At face-to-face last year we talked about working on getting the requirements features qe
was doing that now seems part of reddeer made compatible/usable as part of normal unit
testing - any movement on that?
Reddeer seem to use log4j which is not exactly eclipse/osgi friendly - why is that ?
Why so many plugins in the git repo but just need to import reddeer.swt?
Is red deer a replacement or an addon for swt bot? The FAQ seem to indicate both?
If addon - cool, but why is it then missing features swt bot has?
Have any of this been contributed back to swtbot? I.e. we got committers on swtbot(Mikael)
so if its useful would that make more sense?
Sent from a mobile device
On 30/10/2012, at 16.29, Len DiMaggio <ldimaggi(a)redhat.com> wrote:
Hey Max,
Once again - you an inspiration - see here:
https://github.com/jboss-reddeer/reddeer/wiki/Frequently-asked-questions
;-)
-- Len
From: "Max Rydahl Andersen" <max.andersen(a)gmail.com>
To: "jbosstools-dev jbosstools-dev" <jbosstools-dev(a)lists.jboss.org>
Cc: "ldimaggi DiMaggio" <ldimaggi(a)redhat.com>, "psrna Srna"
<psrna(a)redhat.com>
Sent: Monday, October 29, 2012 2:58:52 PM
Subject: Red Deer Info?
I asked this on
https://github.com/jbosstools/jbosstools-integration-tests/pull/3 but I
assume noone saw it since the issue is closed, so repeating it here:
How is this red deer stuff going to work ? which updatesites will contain it ? I did not
realize these are actually eclipse plugins - and thus not just maven dependencies. by
reddeer being on its own the maintanence of those updatesites and releases needs to be
done fully before we should have tests depending on them, right?
I saw today there is something like
p2-reddeer.rhcloud.com/stable - what is that and why
are we publishing this way and how are this stuff supposed to be used ?
There have been no info/news on this but now alot of our tests is suddenly dependent on
this making our builds rely on something that is *not* mirrored nor communicated how to
use afaik ?
Did I miss something ? i.e. i'm still not following why we want to have separate
infrastructure for something this eclipse specific ? but first of all i'm worried
about having jbosstools code dependent on something like this very unknown reddeer.
/max
--
Len DiMaggio (ldimaggi(a)redhat.com)
JBoss by Red Hat
314 Littleton Road
Westford, MA 01886 USA
tel: 978.392.3179
cell: 781.472.9912
http://www.redhat.com
http://community.jboss.org/people/ldimaggio
<RHxJBpngthumb.png>
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev