[
https://issues.jboss.org/browse/JBDS-1504?page=com.atlassian.jira.plugin....
]
Andrew Hecox commented on JBDS-1504:
------------------------------------
re: the the 404 .. no, it something much more stupid; we're working around something
that went out broken in RHEL 6.0 bits, and re-directing imprecisely to the portal based on
your browser's request for HTML content. We can clean that up so that it doesn't
hit that usage pattern.
re: product, In RHEL, we differentiate at the build system level, both for composition of
packaging and the default configuration values. I don't know if that maps exactly, but
you could either ship different plugins or change the default config to have different
backends enabled.
allow users to create cases from JBDS
-------------------------------------
Key: JBDS-1504
URL:
https://issues.jboss.org/browse/JBDS-1504
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: integration
Environment: All
Reporter: Andrew Hecox
Assignee: Max Rydahl Andersen
Fix For: 4.0.x, LATER
user-story: as a JBoss customer, I can create a case with support from JBDS so that I can
easily get help solving the problem I'm working on in my editor
notes: I think something which allowed a user to create a problem description, as well as
send any applicable files, would be a good value add to JBDS. We have a public, stable,
API for this:
https://access.redhat.com/knowledge/docs/Red_Hat_Customer_Portal/
we may deprecate some schema items in the next month or two, but otherwise it's
locked in place for the next 7+ years. This functionality presumably would only be in the
productized version, unless it was replaced with JIRA integration (or comparable)
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira