nhibernate-issues

[nhibernate-issues] [JIRA] Commented: (NH-615) Change XML schema names to -2.2

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-615?page=comments#action_14254 ]
     
Sergey Koshcheyev commented on NH-615:
--------------------------------------

The problem is that 1.2 is less than 2.0 which is counter-intuitive, and using 3.0/3.2 would imply that all Hibernate 3.0/3.2 features are available in the mapping while it's not the case, so the number would be essentially random anyway.

I guess I'll go with 1.2 then.

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-615) Change XML schema names to -2.2

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-615?page=comments#action_14255 ]
     
Christian Bauer commented on NH-615:
------------------------------------

The choices are: 

a) increment version numbers: NH 1.2/DTD 2.2, NH 2.0/DTD 3.0
b) align NHibernate version numbers: NH 1.2/DTD 1.2, NH 2.0/DTD 3.0
c) align all version numbers: NH 1.2/DTD 1.2, NH 3.0/DTD 3.0



> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-615) Change XML schema names to -2.2

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-615?page=comments#action_14256 ]
     
Christian Bauer commented on NH-615:
------------------------------------

One other thing: We only incremented the Hibernate DTD version when we made breaking changes. Are you sure that the NH 1.2 schema isn't backwards compatible with NH 1.0? If you just add new stuff to it, which is ignored by NH 1.0, then you can keep the major and minor version.


> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira

[nhibernate-issues] [JIRA] Commented: (NH-615) Change XML schema names to -2.2

[NHibernate J. <mik...@us...>]

     [ http://jira.nhibernate.org/browse/NH-615?page=comments#action_14257 ]
     
Sergey Koshcheyev commented on NH-615:
--------------------------------------

Option a) was what I did.

The schema was only added to, nothing was removed. But of course a file using 1.2-specific features won't validate against the 1.0.2 schema since it doesn't permit any attributes or elements it doesn't know about.

> Change XML schema names to -2.2
> -------------------------------
>
>          Key: NH-615
>          URL: http://jira.nhibernate.org/browse/NH-615
>      Project: NHibernate
>         Type: Improvement
>   Components: Core
>     Versions: 1.2.0.Alpha1
>     Reporter: Sergey Koshcheyev
>     Assignee: Sergey Koshcheyev
>     Priority: Trivial
>      Fix For: 1.2.0.Beta2

>
> The XML schema name of nhibernate-mapping-2.0 should probably be changed to nhibernate-mapping-2.2 to reflect changes made since 1.0.2.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://jira.nhibernate.org/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira