We still got a lot of issues open with less than 10 days to go for codefreeze on both JBDS and JBIDE jira, total over a 100.
Looking through jira reveals to me many issues that are either already fixed (but needs confirmation by assignee),
needs to be reassigned to get enough input or maybe not even relevant to be fixed.
So, please walk through your assigned issues and component area so we can have a jira with just the issues we actually need to work on.
Don't forget there are both JBIDE and JBDS.
If there are issues that are waiting for my input please assign the issues to me so I get aware of them faster.
I'll try this out when I get a build.
QA - could you try this out too ?
What do the runtime setup need to do now when creating the server
to make it use this and not a specific vm ? Just not set the vm ?
----- "Rob Stryker" <rstryker(a)redhat.com> wrote:
> I didn't add the UI to change the execution environment because my
> right now is that I set which execution environment each server type
> should have at a minimum. This filters the list of possible vm's
> This should work if you have a server automatically configured, though
> the automatically configured server should *not* reference a jre it
> cannot use. It should instead not set the vm at all and trust that the
> execution environment will find a suitable vm when one is presented.
> Details and patch in the jira. Could use some testing or at least some
> more well-defined use cases.
> FYI, the #jbosstools irc channel is now logged by echelog-1 and the
> logs are publicly available on
> including some rather funny stats.
> This allows everyone to track our public meetings and chats and we get
> a nice searchable archive.
> So more openness, but also a time to remind everyone that the
> #jbosstools irc channel is a public place so don't discuss your
> passwords or similar private things ;)