]
Nick Boldt commented on JBIDE-12720:
------------------------------------
Assigned to Kris for comment. Bounce back to me and I can delete the contents and replace
them with a README pointing users at the new location for drools/guvnor docs.
delete ancient drools and guvnor docs from JBT SVN repo; place README
pointing at updated docs
----------------------------------------------------------------------------------------------
Key: JBIDE-12720
URL:
https://issues.jboss.org/browse/JBIDE-12720
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: drools
Affects Versions: 4.0.0.Alpha2
Reporter: Nick Boldt
Assignee: Kris Verlaenen
Fix For: 4.0.0.Alpha1-SOA, 4.0.0.Beta1
I asked of [~KrisVerlaenen] and [~ge0ffrey]:
{quote}
Do you still need the drools/guvnor doc in JBoss Tools' SVN repo? Or have you
migrated that to github?
Code's here:
https://svn.jboss.org/repos/jbosstools/trunk/drools/docs/
Also in our git-svn mirror here:
https://github.com/jbosstools/jbosstools-svn-mirror/tree/trunk/drools/docs
Looks like it hasn't changed in 10 months. We'd like to delete it from trunk (but
leave it in older branches) as part of our cleanup / git migration.
Do you need it? Can you migrate it out ASAP?
{quote}
And [~ge0ffrey] replied:
{quote}
This is the first time I hear about that svn repository. No objections of me to delete
that.
<irrelavant>We do still need our old drools svn repository (as it's the best
place to get 4.x releases code from etc), but that's a different svn
repo.</irrelavant>
Kris, can it be deleted?
---
If we want them as a separate docs, they should be under
https://github.com/droolsjbpm/droolsjbpm-tools/ as a module droolsjbpm-tools-docs
similar to
https://github.com/droolsjbpm/guvnor/ with the module guvnor-docs
But IIRC, I believe the introduction docs and/or expert docs already describe the eclipse
tooling.
http://www.jboss.org/drools/documentation
{quote}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: