[jbosstools-issues] [JBoss JIRA] (JBIDE-15190) Saxon has dependency on org.jdom (Orbit) and dom4j (not p2-fied)

Paul Richardson (JIRA) jira-events at lists.jboss.org
Fri Jul 12 08:59:22 EDT 2013


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

Paul Richardson commented on JBIDE-15190:
-----------------------------------------

Below represents the list of all packages / classes from saxon, required by Teiid Designer

Every plugin requiring saxon also depends on jdom, which is already included in the integration stack. None of the other DOM processing jars are required, including dom4j.

{code}
net.sf.saxon
net.sf.saxon.event
net.sf.saxon.evpull
net.sf.saxon.expr
net.sf.saxon.expr.PathMap
net.sf.saxon.expr
net.sf.saxon.om
net.sf.saxon.pattern
net.sf.saxon.query
net.sf.saxon.sxpath
net.sf.saxon.trace
net.sf.saxon.trans
net.sf.saxon.type
net.sf.saxon.value
{code}

{code}
net.sf.saxon.AugmentedSource
net.sf.saxon.Configuration
net.sf.saxon.event.ContentHandlerProxy
net.sf.saxon.event.PipelineConfiguration
net.sf.saxon.event.ProxyReceiver
net.sf.saxon.event.Receiver
net.sf.saxon.evpull.PullEventSource
net.sf.saxon.evpull.StaxToEventBridge
net.sf.saxon.expr.AxisExpression
net.sf.saxon.expr.ContextItemExpression
net.sf.saxon.expr.Expression
net.sf.saxon.expr.JPConverter
net.sf.saxon.expr.PathMap
net.sf.saxon.expr.PathMap.PathMapArc
net.sf.saxon.expr.PathMap.PathMapNode
net.sf.saxon.expr.PathMap.PathMapNodeSet
net.sf.saxon.expr.PathMap.PathMapRoot
net.sf.saxon.expr.RootExpression
net.sf.saxon.om.Axis
net.sf.saxon.om.AxisIterator
net.sf.saxon.om.AxisIteratorImpl
net.sf.saxon.om.DocumentInfo
net.sf.saxon.om.EmptyIterator
net.sf.saxon.om.FastStringBuffer
net.sf.saxon.om.Item
net.sf.saxon.om.Name11Checker
net.sf.saxon.om.NamePool
net.sf.saxon.om.NamespaceIterator
net.sf.saxon.om.Navigator
net.sf.saxon.om.NodeInfo
net.sf.saxon.om.QNameException
net.sf.saxon.om.SequenceIterator
net.sf.saxon.om.SiblingCountingNode
net.sf.saxon.om.SingleNodeIterator
net.sf.saxon.om.SingletonIterator
net.sf.saxon.om.StandardNames
net.sf.saxon.om.StructuredQName
net.sf.saxon.om.VirtualNode
net.sf.saxon.pattern.AnyNodeTest
net.sf.saxon.pattern.NameTest
net.sf.saxon.pattern.NodeKindTest
net.sf.saxon.pattern.NodeTest
net.sf.saxon.query.DynamicQueryContext
net.sf.saxon.query.QueryResult
net.sf.saxon.query.StaticQueryContext
net.sf.saxon.query.XQueryExpression
net.sf.saxon.sxpath.IndependentContext
net.sf.saxon.sxpath.XPathDynamicContext
net.sf.saxon.sxpath.XPathEvaluator
net.sf.saxon.sxpath.XPathExpression
net.sf.saxon.trace.ExpressionPresenter
net.sf.saxon.TransformerFactoryImpl
net.sf.saxon.trans.XPathException
net.sf.saxon.type.BuiltInAtomicType
net.sf.saxon.type.ConversionResult
net.sf.saxon.type.ItemType
net.sf.saxon.type.Type
net.sf.saxon.type.TypeHierarchy
net.sf.saxon.value.AtomicValue
net.sf.saxon.value.CalendarValue
net.sf.saxon.value.DateTimeValue
net.sf.saxon.value.DateValue
net.sf.saxon.value.DayTimeDurationValue
net.sf.saxon.value.GYearMonthValue
net.sf.saxon.value.HexBinaryValue
net.sf.saxon.value.SequenceType
net.sf.saxon.value.StringValue
net.sf.saxon.value.TimeValue
net.sf.saxon.value.UntypedAtomicValue
net.sf.saxon.value.Value
{code}
                
> Saxon has dependency on org.jdom (Orbit) and dom4j (not p2-fied)
> ----------------------------------------------------------------
>
>                 Key: JBIDE-15190
>                 URL: https://issues.jboss.org/browse/JBIDE-15190
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: locus
>            Reporter: Mickael Istria
>
> Saxon has some transitive dependencies.
> * org.jdom is part of Orbit so it's easy to provide it
> * org.dom4j is not in any p2 repo (as far as I could search), and is available in its OSGi form via Maven. It also has transitive dependencies (Jaxen and some com.sun packages)
> This makes it difficult to create a nice artifact for Saxon...

--
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


More information about the jbosstools-issues mailing list