[
http://jira.jboss.com/jira/browse/JBIDE-1703?page=comments#action_12400146 ]
Mark Newton commented on JBIDE-1703:
------------------------------------
yes, that would seem to make sense to me.
I suppose we could look at it as follows:
JBoss Tools documentation (Seam Dev Tool Reference Guide, jBPM Tools Reference Guide
etc..) should have the
JBoss.org style by default.
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. i.e. we apply the JBoss Enterprise style to any docs
that have been modified, even if it's only one word that has been changed.
However if no changes have been made and we simply need to bundle the JBoss Tools project
documentation along with the JBoss Developer Studio docs then we should leave it with the
JBoss.org style.
Any documents that are specific to JBoss Developer Studio (Getting Started Guide,
Migration Guide etc...) as you state should have the JBoss Enterprise style by default.
This approach mirrors the approach that Max and I talked about with Community and
Enterprise JARs for the Maven repository the other week. i.e. if any community jars have
been modified (even if it's only one byte) then we give it a new version to indicate
this. Only in our case we're using styles instead of versions to indicate something
has changed.
What do you think?
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