[
http://jira.jboss.com/jira/browse/JBIDE-1703?page=comments#action_12400162 ]
Svetlana mukhina commented on JBIDE-1703:
-----------------------------------------
1. this
"If any changes are then made to the JBoss Tools documentation in order to
'productize' it for JBoss Developer Studio then we should apply the JBoss
Enterprise style to indicate this."
is clear
but this "Only in our case we're using styles instead of versions to indicate
something has changed." is not. As I understand we change styles only if we've
made some changes that 'productize' Jboss docs as Developer Studio ones. In case
of all other changes we just leave it as is.
2. Could you plz give me an example of a guide with JBoss Enterprise style? As now these
(Getting Started Guide, Migration Guide etc...) guides actually have Exadel styles, but
you say "merging the JBoss Enterprise style with the Exadel style", so I
probably misunderstand something, as for me JBoss Enterprise style and the Exadel style
are the same now.
3. yes, I'll be good to merge best bits of the
JBoss.org default style with ones that
we have now, I could provide a list of features that we'd like to have in both
stylesheets, and then we could discuss it.
4. no, we haven't weekly meetings, but we could organize one with you, what time
suits you?
thanks
Mavenize the docbook build
--------------------------
Key: JBIDE-1703
URL:
http://jira.jboss.com/jira/browse/JBIDE-1703
Project: Tools (JBoss Tools)
Issue Type: Task
Components: Build/Releng
Reporter: Max Andersen
Assigned To: Mark Newton
Fix For: 2.1
Attachments: eclipse.xsl, pom.xml, settings.xml
Will give us the standard style + eclipse look'n'feel out of the box
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira