[ https://issues.jboss.org/browse/TOOLSDOC-259?page=com.atlassian.jira.plug... ] Peter Larsen commented on TOOLSDOC-259: --------------------------------------- If I may interject - that's a strange notion. JBDS 4.1 is to be supported for almost 5 more years. 4 if we're very conservative. I cannot see how version 5 changes the fact that we have bad information for a supported release? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-259?page=com.atlassian.jira.plug... ] Peter Larsen commented on TOOLSDOC-259: --------------------------------------- Well, none of our documentation on docs.redhat.com should involve or indicate that community bits are required. It not only is counter to our subscription model and message, but also leads to customers installing the wrong bits. If the doc sources are shared I guess the change would be easy because making it for one version would fit it for others?? (I guess I may be wrong here - because I see lots of omissions and differences between versions on other tools). Referring to community bits is usually done in the appendix. It shouldn't be done elsewhere in the doc - and definitely not as the SOLE AND LONE description on how to get functionality that a customer has a paid subscription for. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-259?page=com.atlassian.jira.plug... ] Isaac Rooskov edited comment on TOOLSDOC-259 at 10/4/11 10:31 PM: ------------------------------------------------------------------ Peter, sorry if I'm wrong here, but it was my understanding that JBDS as a toolset can actually be used with Enterprise and Community bits, for instance it can be used with EAP and JBoss AS, and this is not hidden, it's actually stipulated through the available JBDS server listing when creating a new server. JBDS is only a toolset and it is my understanding that the enterprise product lead likes to see it marketed as being as versatile as possible. To such an end I can see a reason to mention both enterprise and community in the docs. We support the tools in JBDS, not what they are used with. So this is not saying that Red Hat supports Drools Guvnor (the community version) but that it supports the tooling and that tooling can be used with a range of things. I do agree with you though that the doc focus should be on enterprise over community, but I have always received push-back from the JBDS team when talking about moving away from community naming (especially since the actual GUI never mentions BRMS or anything like that but indeed does use the community naming for tools because they do not have enough resources to rename everything in the actual interface that the user sees) was (Author: irooskov): Peter, sorry if I'm wrong here, but it was my understanding that JBDS as a toolset can actually be used with Enterprise and Community bits, for instance it can be used with EAP and JBoss AS, and this is not hidden, it's actually stipulated through the available JBDS server listing when creating a new server. JBDS is only a toolset and it is my understanding that the enterprise product lead likes to see it marketed as being as versatile as possible. Do such an end I can see a reason to mention both enterprise and community in the docs. We support the tools in JBDS, not what they are used with. So this is not saying that Red Hat supports Drools Guvnor (the community version) but that it supports the tooling and that tooling can be used with a range of things. I do agree with you though that the doc focus should be on enterprise over community, but I have always recieved push-back from the JBDS team when talking about moving away from community naming (especially since the actual GUI never mentions BRMS or anything like that but indeed does use the community naming for tools because they do not have enough resources to rename everything in the actual interface that the user sees) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-259?page=com.atlassian.jira.plug... ] Isaac Rooskov commented on TOOLSDOC-259: ---------------------------------------- Thanks for the input Burr :D -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/TOOLSDOC-259?page=com.atlassian.jira.plug... ] Isaac Rooskov resolved TOOLSDOC-259. ------------------------------------ Resolution: Won't Fix Without information from the BRMS team I am unable to fix this issue. I wish there was enough time and resources for me to learn how BRMS and JBDS work together but that is not available to me, sorry. If the information needed does become available please re-open this JIRA with the information attached. Thanks, Isaac -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira