[jbosstools-issues] [JBoss JIRA] (JBIDE-15209) Saxon plugin has different class to the original saxonhe-9.2.1.5 jar

[Paul Richardson (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-15209?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12790257#comment-12790257 ] 

Paul Richardson commented on JBIDE-15209:
-----------------------------------------

The source is available in [sourceforge|http://sourceforge.net/p/saxon/code/571/tree/latest9.2] BUT is actually svn revision 571. Looking at the commit history a tag for 9.2.1.5 was created but mistakenly included all the branches so was removed later and never replaced.

So, revision 571 is the maintenance release of 9.2.1.5 and is 7 commits short of the current HEAD of the branch 'latest9.2'. Now it would seem that latest9.2 is still technically only the HEAD of the branch but its last backported commit was 22/12/2010.

Questions are:
* Do we go with the source of revision 571
 ** its the replica of the published 9.2.1.5 release
 ** it lacks 7 bug fixes that may/may not have been important
* Do we go with the HEAD of latest9.2
 ** Fixes 7 issues and has remained static for 3 years now
 ** Is not available as a published release and seems will never be given versioning has moved on to 9.3, 9.4, 9.5 ...

                
> Saxon plugin has different class to the original saxonhe-9.2.1.5 jar
> --------------------------------------------------------------------
>
>                 Key: JBIDE-15209
>                 URL: https://issues.jboss.org/browse/JBIDE-15209
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: locus
>            Reporter: Paul Richardson
>
> The saxon plugin in locus has the incorrect version of saxon's source committed. Specifically, the class
> {code}
> net.sf.saxon.om.DocumentNumberAllocator
> {code}
> causes compilation problems in Teiid Designer due to a method signature change between original 9.2.1.5 versions of locus' saxon and the current one.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira