[
http://jira.jboss.com/jira/browse/JBIDE-789?page=comments#action_12373636 ]
Viacheslav Kabanovich commented on JBIDE-789:
---------------------------------------------
I mean, that it may happen that components.xml does not mention core:jbpm or other tags
that would make migration required.
If 1.2 versioned components.xml contains only tags identical in 1.2 and 2.0, then
migration is not required, and 1.2 xml may be accepted
as correct for 2.0 project.
That reasoning is still more relevant for fine-grained configuration files
(*.component.xml) which are intended to configure
user components and hence are likely to be limited to using components.xsd, which is the
same for versions 1.2 and 2.0.
seam components.xml editor seem to report errors when it
shouldn't for Seam 2
------------------------------------------------------------------------------
Key: JBIDE-789
URL:
http://jira.jboss.com/jira/browse/JBIDE-789
Project: JBoss Tools
Issue Type: Bug
Components: Seam
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Viacheslav Kabanovich
Priority: Critical
Fix For: 2.0.0.Beta4
Gavin reports:
The components.xml editor always shows errors at least with Seam2
metadata.
--
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