[
https://jira.jboss.org/browse/JBIDE-6093?page=com.atlassian.jira.plugin.s...
]
Jeff DeLong commented on JBIDE-6093:
------------------------------------
Fitz, I am not sure I agree with you that the second issue is not a Drools / Guvnor issue.
Both the errors expressed by the validators and the BPEL archive issue are caused by the
creation of a .guvnorinfo folder with files having the same extension as the original
file, and a fix for one might fix the other and they both need to be fixed in order to use
the Eclipse Guvnor Tooling for loading arbitrary files from arbitrary projects into
Guvnor. On the other hand it might be that the second issue can be resolved by the BPEL
module assembly without any change to the .guvnorinfo naming so from that standpoint maybe
splitting them up might be better; but still link them together.
Eclipse Guvnor Tooling causes validation errors on certain file
types
----------------------------------------------------------------------
Key: JBIDE-6093
URL:
https://jira.jboss.org/browse/JBIDE-6093
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: drools
Affects Versions: 3.1.0.CR2
Environment: JBoss Tools Nightly Build - Jboss Drools Guvnor
5.1.0.v20100226213N-H20-31764
Reporter: Jeff DeLong
Assignee: Kris Verlaenen
Fix For: 3.1.x, 3.2.next
Eclipse Guvnor Tooling creates a new file with the name .filename.ext when a file is
added to Guvnor. For xml files (.xml, .xsd, .html, .bpel, etc,) and java files, this
causes the validators to report errors. E.g., "Content is not allowed in the
prolog" and "Syntax errors on tokens, delete these tokens. This is because these
files have the xml or java extension, hence the validator attempts to validate them. I
have looking at the Preferences -> Validation, but cannot see a clever way to create a
rule to exclude all files with a . at the front of the filename.
Also, Eclipse Guvnor Tooling is not able to add files to the new for Guvnor 5.1
GlobalArea.
--
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