[JBoss JIRA] Created: (JBRULES-568) IDE to understand new XXX.package rule package config file, and support 1 rule per file "convention" to sync with repository
4:26 p.m.
IDE to understand new XXX.package rule package config file, and support 1 rule per file
"convention" to sync with repository
----------------------------------------------------------------------------------------------------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public (Everyone can see)
Affects Versions: 3.1-m3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: 3.1-m3
package layout will be something like:
/<RulePackageName>.package
- has imports in it etc...
/Rule Name 1.rule (vanilla DRL)
/Rule Name 2.brule (uses DSL)
/XXX.dsl (used by brule file)
None of the atomic rule files will have package name, or anything other then
when/then/attributes, the IDE will have to look in to the .package file to find this out.
.drl files can work as they do now.
Let me know if this is a dupe ;)
--
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
6:38 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-568) Package configuration file for IDE
[ http://jira.jboss.com/jira/browse/JBRULES-568?page=all ]
Michael Neale updated JBRULES-568:
----------------------------------
Summary: Package configuration file for IDE (was: IDE to understand new
XXX.package rule package config file, and support 1 rule per file "convention"
to sync with repository)
Description:
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
was:
package layout will be something like:
/<RulePackageName>.package
- has imports in it etc...
/Rule Name 1.rule (vanilla DRL)
/Rule Name 2.brule (uses DSL)
/XXX.dsl (used by brule file)
None of the atomic rule files will have package name, or anything other then
when/then/attributes, the IDE will have to look in to the .package file to find this out.
.drl files can work as they do now.
Let me know if this is a dupe ;)
(slightly clarifying what this feature is about)
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 3.1-m3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: 3.1-m3
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
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
6:42 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-568) Package configuration file for IDE
[ http://jira.jboss.com/jira/browse/JBRULES-568?page=comments#action_12355075 ]
Michael Neale commented on JBRULES-568:
---------------------------------------
an example
/foo/foo.pkg
-----------------------------
package foobar
import my.class.Here
import another.class.There
global lets.all.think.Global varName
-----------------------------
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 3.1-m3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: 3.1-m3
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
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
5:59 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-568) Package configuration file for IDE
[ http://jira.jboss.com/jira/browse/JBRULES-568?page=all ]
Mark Proctor updated JBRULES-568:
---------------------------------
Fix Version/s: 4.0.0.MR4
(was: 4.0.0.MR3)
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.MR3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: 4.0.0.MR4
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
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
5:58 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-568) Package configuration file for IDE
[ http://jira.jboss.com/jira/browse/JBRULES-568?page=all ]
Mark Proctor updated JBRULES-568:
---------------------------------
Fix Version/s: FUTURE
(was: 4.0.0.GA)
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Rules
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 4.0.0.MR3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: FUTURE
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
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
3:15 p.m.
New subject: [JBoss JIRA] Updated: (JBRULES-568) Package configuration file for IDE
[ http://jira.jboss.com/jira/browse/JBRULES-568?page=all ]
Kris Verlaenen updated JBRULES-568:
-----------------------------------
Component/s: Eclipse IDE
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Eclipse IDE
Affects Versions: 4.0.0.MR3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: FUTURE
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
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
4:37 a.m.
New subject: [JBoss JIRA] Commented: (JBRULES-568) Package configuration file for IDE
[ http://jira.jboss.com/jira/browse/JBRULES-568?page=comments#action_12420048 ]
Michael Neale commented on JBRULES-568:
---------------------------------------
kris - I am using the naming convention drools.package in a folder to contain all the
config data.
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: http://jira.jboss.com/jira/browse/JBRULES-568
Project: JBoss Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Eclipse IDE
Affects Versions: 4.0.0.MR3
Reporter: Michael Neale
Assigned To: Kris Verlaenen
Fix For: FUTURE
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
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
1:02 a.m.
New subject: [JBoss JIRA] Updated: (JBRULES-568) Package configuration file for IDE
[
https://issues.jboss.org/browse/JBRULES-568?page=com.atlassian.jira.plugi...
]
Kris Verlaenen updated JBRULES-568:
-----------------------------------
Assignee: (was: Kris Verlaenen)
Package configuration file for IDE
----------------------------------
Key: JBRULES-568
URL: https://issues.jboss.org/browse/JBRULES-568
Project: Drools
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: drools-eclipse
Affects Versions: 4.0.0.MR3
Reporter: Michael Neale
Fix For: FUTURE
We need to have a new .pkg file (or .package - any file name extension will do). The
purpose of this JIRA is twofold:
1) Develop a simple eclipse forms based GUI to edit the package file
2) Modify DroolsBuilder.
The file format is basically the same as drl today - except without any rules, queries or
functions. ie just the "header" part of the rule, still plain text.
The GUI will ideally will use eclipse forms, and provide a seperate window for imports,
another for globals etc... when defining an import or a global, the Drl parser can be used
to extract the list of imports and globals (just parse it, and getGlobals, getImports) -
just a suggestion. Also, a class finder dialog would be nice (like when you pretty
ctrl+shift+t - which examines the project classpath). Of course, a text view is also
cool.
DroolsBuilder: when a package file is seen, that means that in the SAME FOLDER there will
be lots of .rule files, .drl etc.. which all get build in the context of the package file
- so the DroolsBuilder will need to be aware of this. The current parser/api can deal
with this (apparently).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4747
days inactive
6353
days old
7 comments
4 participants
participants (4)
-
Kris Verlaenen (JIRA) -
Mark Proctor (JIRA)
-
Michael Neale (JIRA)
-
Michael Neale (JIRA)