[
https://jira.jboss.org/browse/JBRULES-2707?page=com.atlassian.jira.plugin...
]
Mark Proctor commented on JBRULES-2707:
---------------------------------------
I'm fine with moving factconstraints into Guvnor. Davide is working on Description
Logic support for Drools and in reality the fact constraints editor should really just
author the DL aspects of the model, which the gui would consume. DL will be direct
embedded in DRL, via the Manchester Syntax.
Split up drools-guvnor into drools-guvnor-gwtclient and
drools-guvnor(-server)
------------------------------------------------------------------------------
Key: JBRULES-2707
URL:
https://jira.jboss.org/browse/JBRULES-2707
Project: Drools
Issue Type: Task
Security Level: Public(Everyone can see)
Affects Versions: 5.1.1.FINAL
Reporter: Geoffrey De Smet
Assignee: Geoffrey De Smet
Fix For: 5.2.0.M1
All classes/resources under the client/public package go to drools-guvnor-gwtclient.
The drools-guvnor-gwtclient pom.xml
- is of type war
- has only the gwt dependencies
All classes under the server package go to drools-guvnor(-server)
The drools-guvnor(-server) pom.xml
- is of type war
- has a dependency on drools-guvnor-gwtclient (= war overlay!)
- has dependencies on drools-core, drools-compiler (so on jdt too), ...
What do we do with drools-ide-common and drools-factconstraints? Split them up to, or
simply move the client package code into drools-guvnor?
Where will the drools-ide-common and drools-factconstraints GWT modules be reused,
besides in Guvnor?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira