You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by David Jencks <da...@yahoo.com> on 2006/06/26 21:32:24 UTC
xmlbeans and maven 2
I would like to help make sure xmlbeans is represented properly in
the maven 2 repository system, partly to ease the Geronimo migration
to a maven 2 based build. Unlike a maven 1 repository, the maven 2
repo has considerable metadata about a project, including at least a
specification of the dependencies between jars. Due to some
historical accidents the metadata for xmlbeans 2.0.0 and 2.1.0 is
currently wrong. I'd like to help fix it and make sure the metadata
for xmlbeans 2.2 is correct from the start. This metadata is
contained in a pom.xml file for each released jar.
I think it would make sense to keep this metadata in the xmlbeans svn
repo inside a "maven2" folder which in turn has trunk, branches and
tags inside it: since xmlbeans isn't using a maven 2 based build the
metadata is not likely to be completely available right when a
release is available.
Before I propose particular metadata files I'd like to straighten out
some details of the dependencies between jars.
1. The main xmlbeans jar needs the stax api in a jar. IIUC this can
be provided by a jsr-173 jar distributed alongside xmlbeans. This
jar is not in any public maven 2 repository, but there is a stax-api
jar from the codehaus stax project that is available, and geronimo
has been using it for some time with no problems. The stax-api jar
seems to have at least one bug fix compared to the original api
sources. You may be able to review the changes from http://
svn.stax.codehaus.org/browse/stax/trunk/dev/src/javax/xml/stream
AFAICT all changes shown there are in the released stax-api 1.0.1
release.
For the xmlbeans pom.xml, either the xmlbeans jsr-173 jar will need
to be uploaded to the maven2 repository, together with a pom.xml for
it, or we can use the stax-api copy. Since there appear to be bug
fixes and we have been using it, I have a slight preference for the
stax-api copy, but I can try to arrange upload of the xmlbeans api
jar if it is generally preferred. Also, source for the stax-api jar
is readily available whereas I haven't found the source for the
xmlbeans jsr-173 jar.
So, which stax api jar should I use?
2. I have never used xmlpublic.jar and can't quite figure out what it
is intended for. IIUC it contains a subset of the contents of
xbean.jar. When would this be used?
3. It looks like xbean_xpath.jar can be used together with xbean.jar
in the same classloader to get xpath support. While not directly
relevant to maven, I'd like to know if this will work if xbean_xpath
is in a child classloader of the xbean jar classloader. In any case
I believe the pom.xml for xbean_xpath.jar can simply list xbean.jar
as a dependency.
4. Apparently xquery support requires saxon. Does it also require
xbean_xpath.jar? If not, does saxon provide complete xpath support
without xbean_xpath?
I'm thinking that it would be adequate to supply poms for the following:
-xbean.jar by itself, not supporting xpath or xquery
-xbean_xpath.jar + xbean.jar
-xbean.jar + saxon (this does not imply redistributing saxon, just
indicating that saxon is required to get xquery functionality)
-xbean_xpath.jar + xbean.jar + saxon.jar (unless saxon also provides
xpath functionality, see (4))
-xml_public.jar (assuming I can understand what it is for :-)
and possibly
-jsr172-1.0.jar
If the xmlbeans team can clarify these dependency issues I will work
on constructing the appropriate poms and directory structure and
submit a patch. The pom also can contain a lot of other information
such as project location, team members, svn details, etc etc which I
will try to at least rough out subject to correction.
many thanks,
david jencks
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
RE: xmlbeans and maven 2
Posted by Cezar Andrei <ce...@bea.com>.
Hi David,
I guess having the maven and maven2 poms published would be useful to
many people, do you think the files attached to XMLBEANS-277 need any
updates?
Do you know or can you point us in the right direction on how/where
those files need to be published?
Thanks,
Cezar
> -----Original Message-----
> From: David Jencks [mailto:david_jencks@yahoo.com]
> Sent: Wednesday, June 28, 2006 7:10 PM
> To: dev@xmlbeans.apache.org
> Subject: Re: xmlbeans and maven 2
>
> I've come up with some preliminary metadata and attached it to http://
> issues.apache.org/jira/browse/XMLBEANS-277
>
> I used the stax-api-1.0.1 per Tatu's recommendation.
>
> I'm working out some details with the maven 2 team and testing at
> least the plain xbean metadata. I'll try to figure out how to test
> the other metadata as well.
>
> Right now I'd appreciate if someone could review at least one of the
> poms especially the various project urls and team members.
>
> After we get this all working I'll find out more details from the
> maven team on how to actually publish this. I believe it will
> involve an xmlbeans pmc member signing the artifacts.
>
> If anyone wants to test this, unpack the jar attached to the jira in
> your local m2 repo, and copy the appropriate xmlbeans jars into the
> appropriate directories.
>
> After some consideration I realized this would be a good time to also
> change to the maven 2 style groupId of org.apache.xmlbeans rather
> than plain xmlbeans, and this will let us keep the same versions
> (2.0.0 and 2.1.0 instead of 2.0.0-1 etc).
>
> The releases of saxon available through maven2 are currently 8.5.1
> and 8.7. I assume that neither of these will work with xbean_xpath
> 2.0.0 or 2.1.0, and that 8.7 will work with 2.2.0. Has anyone tried
> to run against 8.7? How important would it be to make the 2.0.0 and
> 2.1.0 xmlbeans xpath extensions work with maven 2?
>
>
> Many thanks!
> david jencks
>
> On Jun 26, 2006, at 4:42 PM, Cezar Andrei wrote:
>
> > Hi David,
> >
> > We appreciate very much your help and involvement.
> >
> > 1. The tests we run and the releases we have are using the
jsr173-api
> > jar bundled inside the release files. The sources for this jar can
be
> > found from Jsr 173 official page:
> > http://jcp.org/aboutJava/communityprocess/final/jsr173/index.html
> > This would be the only reason to use this one, if this one can't be
> > used I guess the codehaus jar can be used instead. The changes seem
to
> > be minimal. If others have a different opinion please send it in.
> >
> > 2. xmlpublic.jar is a jar that contains the public API of XMLBeans.
> > Projects can use this jar to compile against it, to ensure backwards
> > compatibility.
> >
> > 3 and 4. To get extended xpath and xquery support in XMLBeans both
> > xbean_xpath.jar and saxon.jar need to be available to the current
> > classloader of xbean.jar.
> >
> > So the following combinations are required to work:
> > a. Compile only:
> > xmlpublic.jar + Jsr173
> > b. Runtime without xpath/xquery
> > xbean.jar + jsr173
> > c. Runtime with xpath/xquery
> > xbean.jar + jsr173 + xbean_xpath.jar + saxon.jar
> >
> >
> > Cezar
> >
> >
> >> -----Original Message-----
> >> From: David Jencks [mailto:david_jencks@yahoo.com]
> >> Sent: Monday, June 26, 2006 2:32 PM
> >> To: xmlbeans-dev@xml.apache.org
> >> Subject: xmlbeans and maven 2
> >>
> >> I would like to help make sure xmlbeans is represented properly in
> >> the maven 2 repository system, partly to ease the Geronimo
migration
> >> to a maven 2 based build. Unlike a maven 1 repository, the maven 2
> >> repo has considerable metadata about a project, including at least
a
> >> specification of the dependencies between jars. Due to some
> >> historical accidents the metadata for xmlbeans 2.0.0 and 2.1.0 is
> >> currently wrong. I'd like to help fix it and make sure the
metadata
> >> for xmlbeans 2.2 is correct from the start. This metadata is
> >> contained in a pom.xml file for each released jar.
> >>
> >> I think it would make sense to keep this metadata in the xmlbeans
svn
> >> repo inside a "maven2" folder which in turn has trunk, branches and
> >> tags inside it: since xmlbeans isn't using a maven 2 based build
the
> >> metadata is not likely to be completely available right when a
> >> release is available.
> >>
> >> Before I propose particular metadata files I'd like to straighten
out
> >> some details of the dependencies between jars.
> >>
> >> 1. The main xmlbeans jar needs the stax api in a jar. IIUC this
can
> >> be provided by a jsr-173 jar distributed alongside xmlbeans. This
> >> jar is not in any public maven 2 repository, but there is a
stax-api
> >> jar from the codehaus stax project that is available, and geronimo
> >> has been using it for some time with no problems. The stax-api
jar
> >> seems to have at least one bug fix compared to the original api
> >> sources. You may be able to review the changes from http://
> >> svn.stax.codehaus.org/browse/stax/trunk/dev/src/javax/xml/stream
> >> AFAICT all changes shown there are in the released stax-api 1.0.1
> >> release.
> >>
> >> For the xmlbeans pom.xml, either the xmlbeans jsr-173 jar will need
> >> to be uploaded to the maven2 repository, together with a pom.xml
for
> >> it, or we can use the stax-api copy. Since there appear to be bug
> >> fixes and we have been using it, I have a slight preference for the
> >> stax-api copy, but I can try to arrange upload of the xmlbeans api
> >> jar if it is generally preferred. Also, source for the stax-api
jar
> >> is readily available whereas I haven't found the source for the
> >> xmlbeans jsr-173 jar.
> >>
> >> So, which stax api jar should I use?
> >>
> >> 2. I have never used xmlpublic.jar and can't quite figure out what
it
> >> is intended for. IIUC it contains a subset of the contents of
> >> xbean.jar. When would this be used?
> >>
> >> 3. It looks like xbean_xpath.jar can be used together with
xbean.jar
> >> in the same classloader to get xpath support. While not directly
> >> relevant to maven, I'd like to know if this will work if
xbean_xpath
> >> is in a child classloader of the xbean jar classloader. In any
case
> >> I believe the pom.xml for xbean_xpath.jar can simply list xbean.jar
> >> as a dependency.
> >>
> >> 4. Apparently xquery support requires saxon. Does it also require
> >> xbean_xpath.jar? If not, does saxon provide complete xpath support
> >> without xbean_xpath?
> >>
> >> I'm thinking that it would be adequate to supply poms for the
> > following:
> >> -xbean.jar by itself, not supporting xpath or xquery
> >> -xbean_xpath.jar + xbean.jar
> >> -xbean.jar + saxon (this does not imply redistributing saxon, just
> >> indicating that saxon is required to get xquery functionality)
> >> -xbean_xpath.jar + xbean.jar + saxon.jar (unless saxon also
provides
> >> xpath functionality, see (4))
> >> -xml_public.jar (assuming I can understand what it is for :-)
> >>
> >> and possibly
> >> -jsr172-1.0.jar
> >>
> >> If the xmlbeans team can clarify these dependency issues I will
work
> >> on constructing the appropriate poms and directory structure and
> >> submit a patch. The pom also can contain a lot of other
information
> >> such as project location, team members, svn details, etc etc which
I
> >> will try to at least rough out subject to correction.
> >>
> >> many thanks,
> >> david jencks
> >>
> >>
> >>
> >>
> >>
> >>
> >>
---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
> >> For additional commands, e-mail: dev-help@xmlbeans.apache.org
> >
> >
______________________________________________________________________
> > _
> > Notice: This email message, together with any attachments, may
> > contain
> > information of BEA Systems, Inc., its subsidiaries and
> > affiliated
> > entities, that may be confidential, proprietary, copyrighted
> > and/or
> > legally privileged, and is intended solely for the use of the
> > individual
> > or entity named in this message. If you are not the intended
> > recipient,
> > and have received this message in error, please immediately return
> > this
> > by email and then delete it.
> >
> >
---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
> > For additional commands, e-mail: dev-help@xmlbeans.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: dev-help@xmlbeans.apache.org
Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
RE: xmlbeans and maven 2
Posted by Radu Preotiuc-Pietro <ra...@bea.com>.
David, it looks good.
Yes, I have tried Saxon 8.7 (in particular 8.7.3) with XmlBeans 2.2.0
and indeed it does work. I don't know if it's worth trying to make 2.0.0
and 2.1.0 work with maven2 since that would imply getting Saxon8.1.1 in
maven2 (I don't see how we can retroactively make XmlBeans 2.0.0 work
with a different Saxon version....); we can say that one needs to
upgrade to 2.2.0 if one wants maven 2.
Thanks,
Radu
-----Original Message-----
From: David Jencks [mailto:david_jencks@yahoo.com]
Sent: Wednesday, June 28, 2006 5:10 PM
To: dev@xmlbeans.apache.org
Subject: Re: xmlbeans and maven 2
I've come up with some preliminary metadata and attached it to http://
issues.apache.org/jira/browse/XMLBEANS-277
I used the stax-api-1.0.1 per Tatu's recommendation.
I'm working out some details with the maven 2 team and testing at least
the plain xbean metadata. I'll try to figure out how to test the other
metadata as well.
Right now I'd appreciate if someone could review at least one of the
poms especially the various project urls and team members.
After we get this all working I'll find out more details from the maven
team on how to actually publish this. I believe it will involve an
xmlbeans pmc member signing the artifacts.
If anyone wants to test this, unpack the jar attached to the jira in
your local m2 repo, and copy the appropriate xmlbeans jars into the
appropriate directories.
After some consideration I realized this would be a good time to also
change to the maven 2 style groupId of org.apache.xmlbeans rather than
plain xmlbeans, and this will let us keep the same versions (2.0.0 and
2.1.0 instead of 2.0.0-1 etc).
The releases of saxon available through maven2 are currently 8.5.1
and 8.7. I assume that neither of these will work with xbean_xpath
2.0.0 or 2.1.0, and that 8.7 will work with 2.2.0. Has anyone tried to
run against 8.7? How important would it be to make the 2.0.0 and 2.1.0
xmlbeans xpath extensions work with maven 2?
Many thanks!
david jencks
On Jun 26, 2006, at 4:42 PM, Cezar Andrei wrote:
> Hi David,
>
> We appreciate very much your help and involvement.
>
> 1. The tests we run and the releases we have are using the jsr173-api
> jar bundled inside the release files. The sources for this jar can be
> found from Jsr 173 official page:
> http://jcp.org/aboutJava/communityprocess/final/jsr173/index.html
> This would be the only reason to use this one, if this one can't be
> used I guess the codehaus jar can be used instead. The changes seem to
> be minimal. If others have a different opinion please send it in.
>
> 2. xmlpublic.jar is a jar that contains the public API of XMLBeans.
> Projects can use this jar to compile against it, to ensure backwards
> compatibility.
>
> 3 and 4. To get extended xpath and xquery support in XMLBeans both
> xbean_xpath.jar and saxon.jar need to be available to the current
> classloader of xbean.jar.
>
> So the following combinations are required to work:
> a. Compile only:
> xmlpublic.jar + Jsr173
> b. Runtime without xpath/xquery
> xbean.jar + jsr173
> c. Runtime with xpath/xquery
> xbean.jar + jsr173 + xbean_xpath.jar + saxon.jar
>
>
> Cezar
>
>
>> -----Original Message-----
>> From: David Jencks [mailto:david_jencks@yahoo.com]
>> Sent: Monday, June 26, 2006 2:32 PM
>> To: xmlbeans-dev@xml.apache.org
>> Subject: xmlbeans and maven 2
>>
>> I would like to help make sure xmlbeans is represented properly in
>> the maven 2 repository system, partly to ease the Geronimo migration
>> to a maven 2 based build. Unlike a maven 1 repository, the maven 2
>> repo has considerable metadata about a project, including at least a
>> specification of the dependencies between jars. Due to some
>> historical accidents the metadata for xmlbeans 2.0.0 and 2.1.0 is
>> currently wrong. I'd like to help fix it and make sure the metadata
>> for xmlbeans 2.2 is correct from the start. This metadata is
>> contained in a pom.xml file for each released jar.
>>
>> I think it would make sense to keep this metadata in the xmlbeans svn
>> repo inside a "maven2" folder which in turn has trunk, branches and
>> tags inside it: since xmlbeans isn't using a maven 2 based build the
>> metadata is not likely to be completely available right when a
>> release is available.
>>
>> Before I propose particular metadata files I'd like to straighten out
>> some details of the dependencies between jars.
>>
>> 1. The main xmlbeans jar needs the stax api in a jar. IIUC this can
>> be provided by a jsr-173 jar distributed alongside xmlbeans. This
>> jar is not in any public maven 2 repository, but there is a stax-api
>> jar from the codehaus stax project that is available, and geronimo
>> has been using it for some time with no problems. The stax-api jar
>> seems to have at least one bug fix compared to the original api
>> sources. You may be able to review the changes from http://
>> svn.stax.codehaus.org/browse/stax/trunk/dev/src/javax/xml/stream
>> AFAICT all changes shown there are in the released stax-api 1.0.1
>> release.
>>
>> For the xmlbeans pom.xml, either the xmlbeans jsr-173 jar will need
>> to be uploaded to the maven2 repository, together with a pom.xml for
>> it, or we can use the stax-api copy. Since there appear to be bug
>> fixes and we have been using it, I have a slight preference for the
>> stax-api copy, but I can try to arrange upload of the xmlbeans api
>> jar if it is generally preferred. Also, source for the stax-api jar
>> is readily available whereas I haven't found the source for the
>> xmlbeans jsr-173 jar.
>>
>> So, which stax api jar should I use?
>>
>> 2. I have never used xmlpublic.jar and can't quite figure out what it
>> is intended for. IIUC it contains a subset of the contents of
>> xbean.jar. When would this be used?
>>
>> 3. It looks like xbean_xpath.jar can be used together with xbean.jar
>> in the same classloader to get xpath support. While not directly
>> relevant to maven, I'd like to know if this will work if xbean_xpath
>> is in a child classloader of the xbean jar classloader. In any case
>> I believe the pom.xml for xbean_xpath.jar can simply list xbean.jar
>> as a dependency.
>>
>> 4. Apparently xquery support requires saxon. Does it also require
>> xbean_xpath.jar? If not, does saxon provide complete xpath support
>> without xbean_xpath?
>>
>> I'm thinking that it would be adequate to supply poms for the
> following:
>> -xbean.jar by itself, not supporting xpath or xquery -xbean_xpath.jar
>> + xbean.jar -xbean.jar + saxon (this does not imply redistributing
>> saxon, just indicating that saxon is required to get xquery
>> functionality) -xbean_xpath.jar + xbean.jar + saxon.jar (unless saxon
>> also provides xpath functionality, see (4)) -xml_public.jar (assuming
>> I can understand what it is for :-)
>>
>> and possibly
>> -jsr172-1.0.jar
>>
>> If the xmlbeans team can clarify these dependency issues I will work
>> on constructing the appropriate poms and directory structure and
>> submit a patch. The pom also can contain a lot of other information
>> such as project location, team members, svn details, etc etc which I
>> will try to at least rough out subject to correction.
>>
>> many thanks,
>> david jencks
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
>> For additional commands, e-mail: dev-help@xmlbeans.apache.org
>
> ______________________________________________________________________
> _
> Notice: This email message, together with any attachments, may
> contain
> information of BEA Systems, Inc., its subsidiaries and
> affiliated
> entities, that may be confidential, proprietary, copyrighted
> and/or
> legally privileged, and is intended solely for the use of the
> individual or entity named in this message. If you are not the
> intended recipient, and have received this message in error, please
> immediately return this by email and then delete it.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: dev-help@xmlbeans.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
Re: xmlbeans and maven 2
Posted by David Jencks <da...@yahoo.com>.
I've come up with some preliminary metadata and attached it to http://
issues.apache.org/jira/browse/XMLBEANS-277
I used the stax-api-1.0.1 per Tatu's recommendation.
I'm working out some details with the maven 2 team and testing at
least the plain xbean metadata. I'll try to figure out how to test
the other metadata as well.
Right now I'd appreciate if someone could review at least one of the
poms especially the various project urls and team members.
After we get this all working I'll find out more details from the
maven team on how to actually publish this. I believe it will
involve an xmlbeans pmc member signing the artifacts.
If anyone wants to test this, unpack the jar attached to the jira in
your local m2 repo, and copy the appropriate xmlbeans jars into the
appropriate directories.
After some consideration I realized this would be a good time to also
change to the maven 2 style groupId of org.apache.xmlbeans rather
than plain xmlbeans, and this will let us keep the same versions
(2.0.0 and 2.1.0 instead of 2.0.0-1 etc).
The releases of saxon available through maven2 are currently 8.5.1
and 8.7. I assume that neither of these will work with xbean_xpath
2.0.0 or 2.1.0, and that 8.7 will work with 2.2.0. Has anyone tried
to run against 8.7? How important would it be to make the 2.0.0 and
2.1.0 xmlbeans xpath extensions work with maven 2?
Many thanks!
david jencks
On Jun 26, 2006, at 4:42 PM, Cezar Andrei wrote:
> Hi David,
>
> We appreciate very much your help and involvement.
>
> 1. The tests we run and the releases we have are using the jsr173-api
> jar bundled inside the release files. The sources for this jar can be
> found from Jsr 173 official page:
> http://jcp.org/aboutJava/communityprocess/final/jsr173/index.html
> This would be the only reason to use this one, if this one can't be
> used I guess the codehaus jar can be used instead. The changes seem to
> be minimal. If others have a different opinion please send it in.
>
> 2. xmlpublic.jar is a jar that contains the public API of XMLBeans.
> Projects can use this jar to compile against it, to ensure backwards
> compatibility.
>
> 3 and 4. To get extended xpath and xquery support in XMLBeans both
> xbean_xpath.jar and saxon.jar need to be available to the current
> classloader of xbean.jar.
>
> So the following combinations are required to work:
> a. Compile only:
> xmlpublic.jar + Jsr173
> b. Runtime without xpath/xquery
> xbean.jar + jsr173
> c. Runtime with xpath/xquery
> xbean.jar + jsr173 + xbean_xpath.jar + saxon.jar
>
>
> Cezar
>
>
>> -----Original Message-----
>> From: David Jencks [mailto:david_jencks@yahoo.com]
>> Sent: Monday, June 26, 2006 2:32 PM
>> To: xmlbeans-dev@xml.apache.org
>> Subject: xmlbeans and maven 2
>>
>> I would like to help make sure xmlbeans is represented properly in
>> the maven 2 repository system, partly to ease the Geronimo migration
>> to a maven 2 based build. Unlike a maven 1 repository, the maven 2
>> repo has considerable metadata about a project, including at least a
>> specification of the dependencies between jars. Due to some
>> historical accidents the metadata for xmlbeans 2.0.0 and 2.1.0 is
>> currently wrong. I'd like to help fix it and make sure the metadata
>> for xmlbeans 2.2 is correct from the start. This metadata is
>> contained in a pom.xml file for each released jar.
>>
>> I think it would make sense to keep this metadata in the xmlbeans svn
>> repo inside a "maven2" folder which in turn has trunk, branches and
>> tags inside it: since xmlbeans isn't using a maven 2 based build the
>> metadata is not likely to be completely available right when a
>> release is available.
>>
>> Before I propose particular metadata files I'd like to straighten out
>> some details of the dependencies between jars.
>>
>> 1. The main xmlbeans jar needs the stax api in a jar. IIUC this can
>> be provided by a jsr-173 jar distributed alongside xmlbeans. This
>> jar is not in any public maven 2 repository, but there is a stax-api
>> jar from the codehaus stax project that is available, and geronimo
>> has been using it for some time with no problems. The stax-api jar
>> seems to have at least one bug fix compared to the original api
>> sources. You may be able to review the changes from http://
>> svn.stax.codehaus.org/browse/stax/trunk/dev/src/javax/xml/stream
>> AFAICT all changes shown there are in the released stax-api 1.0.1
>> release.
>>
>> For the xmlbeans pom.xml, either the xmlbeans jsr-173 jar will need
>> to be uploaded to the maven2 repository, together with a pom.xml for
>> it, or we can use the stax-api copy. Since there appear to be bug
>> fixes and we have been using it, I have a slight preference for the
>> stax-api copy, but I can try to arrange upload of the xmlbeans api
>> jar if it is generally preferred. Also, source for the stax-api jar
>> is readily available whereas I haven't found the source for the
>> xmlbeans jsr-173 jar.
>>
>> So, which stax api jar should I use?
>>
>> 2. I have never used xmlpublic.jar and can't quite figure out what it
>> is intended for. IIUC it contains a subset of the contents of
>> xbean.jar. When would this be used?
>>
>> 3. It looks like xbean_xpath.jar can be used together with xbean.jar
>> in the same classloader to get xpath support. While not directly
>> relevant to maven, I'd like to know if this will work if xbean_xpath
>> is in a child classloader of the xbean jar classloader. In any case
>> I believe the pom.xml for xbean_xpath.jar can simply list xbean.jar
>> as a dependency.
>>
>> 4. Apparently xquery support requires saxon. Does it also require
>> xbean_xpath.jar? If not, does saxon provide complete xpath support
>> without xbean_xpath?
>>
>> I'm thinking that it would be adequate to supply poms for the
> following:
>> -xbean.jar by itself, not supporting xpath or xquery
>> -xbean_xpath.jar + xbean.jar
>> -xbean.jar + saxon (this does not imply redistributing saxon, just
>> indicating that saxon is required to get xquery functionality)
>> -xbean_xpath.jar + xbean.jar + saxon.jar (unless saxon also provides
>> xpath functionality, see (4))
>> -xml_public.jar (assuming I can understand what it is for :-)
>>
>> and possibly
>> -jsr172-1.0.jar
>>
>> If the xmlbeans team can clarify these dependency issues I will work
>> on constructing the appropriate poms and directory structure and
>> submit a patch. The pom also can contain a lot of other information
>> such as project location, team members, svn details, etc etc which I
>> will try to at least rough out subject to correction.
>>
>> many thanks,
>> david jencks
>>
>>
>>
>>
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
>> For additional commands, e-mail: dev-help@xmlbeans.apache.org
>
> ______________________________________________________________________
> _
> Notice: This email message, together with any attachments, may
> contain
> information of BEA Systems, Inc., its subsidiaries and
> affiliated
> entities, that may be confidential, proprietary, copyrighted
> and/or
> legally privileged, and is intended solely for the use of the
> individual
> or entity named in this message. If you are not the intended
> recipient,
> and have received this message in error, please immediately return
> this
> by email and then delete it.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: dev-help@xmlbeans.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
RE: xmlbeans and maven 2
Posted by Tatu Saloranta <co...@yahoo.com>.
--- Cezar Andrei <ce...@bea.com> wrote:
> Hi David,
>
> We appreciate very much your help and involvement.
>
> 1. The tests we run and the releases we have are
> using the jsr173-api
> jar bundled inside the release files. The sources
> for this jar can be
> found from Jsr 173 official page:
>
http://jcp.org/aboutJava/communityprocess/final/jsr173/index.html
> This would be the only reason to use this one, if
> this one can't be
> used I guess the codehaus jar can be used instead.
> The changes seem to
> be minimal. If others have a different opinion
> please send it in.
Changes are minimal in the sense that there is only
one real change. Alas, the bug fixed is rather fatal
on environments it affects things (apparently on many
IBM WebSphere deployments): trying to instantiate
XMLStreamReaders will fail on a runtime exception. If
there were no fatal problems, there probably wouldn't
be 1.0.1 release in the first place.
So I would actually recommend using 1.0.1.
-+ Tatu +-
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org
RE: xmlbeans and maven 2
Posted by Cezar Andrei <ce...@bea.com>.
Hi David,
We appreciate very much your help and involvement.
1. The tests we run and the releases we have are using the jsr173-api
jar bundled inside the release files. The sources for this jar can be
found from Jsr 173 official page:
http://jcp.org/aboutJava/communityprocess/final/jsr173/index.html
This would be the only reason to use this one, if this one can't be
used I guess the codehaus jar can be used instead. The changes seem to
be minimal. If others have a different opinion please send it in.
2. xmlpublic.jar is a jar that contains the public API of XMLBeans.
Projects can use this jar to compile against it, to ensure backwards
compatibility.
3 and 4. To get extended xpath and xquery support in XMLBeans both
xbean_xpath.jar and saxon.jar need to be available to the current
classloader of xbean.jar.
So the following combinations are required to work:
a. Compile only:
xmlpublic.jar + Jsr173
b. Runtime without xpath/xquery
xbean.jar + jsr173
c. Runtime with xpath/xquery
xbean.jar + jsr173 + xbean_xpath.jar + saxon.jar
Cezar
> -----Original Message-----
> From: David Jencks [mailto:david_jencks@yahoo.com]
> Sent: Monday, June 26, 2006 2:32 PM
> To: xmlbeans-dev@xml.apache.org
> Subject: xmlbeans and maven 2
>
> I would like to help make sure xmlbeans is represented properly in
> the maven 2 repository system, partly to ease the Geronimo migration
> to a maven 2 based build. Unlike a maven 1 repository, the maven 2
> repo has considerable metadata about a project, including at least a
> specification of the dependencies between jars. Due to some
> historical accidents the metadata for xmlbeans 2.0.0 and 2.1.0 is
> currently wrong. I'd like to help fix it and make sure the metadata
> for xmlbeans 2.2 is correct from the start. This metadata is
> contained in a pom.xml file for each released jar.
>
> I think it would make sense to keep this metadata in the xmlbeans svn
> repo inside a "maven2" folder which in turn has trunk, branches and
> tags inside it: since xmlbeans isn't using a maven 2 based build the
> metadata is not likely to be completely available right when a
> release is available.
>
> Before I propose particular metadata files I'd like to straighten out
> some details of the dependencies between jars.
>
> 1. The main xmlbeans jar needs the stax api in a jar. IIUC this can
> be provided by a jsr-173 jar distributed alongside xmlbeans. This
> jar is not in any public maven 2 repository, but there is a stax-api
> jar from the codehaus stax project that is available, and geronimo
> has been using it for some time with no problems. The stax-api jar
> seems to have at least one bug fix compared to the original api
> sources. You may be able to review the changes from http://
> svn.stax.codehaus.org/browse/stax/trunk/dev/src/javax/xml/stream
> AFAICT all changes shown there are in the released stax-api 1.0.1
> release.
>
> For the xmlbeans pom.xml, either the xmlbeans jsr-173 jar will need
> to be uploaded to the maven2 repository, together with a pom.xml for
> it, or we can use the stax-api copy. Since there appear to be bug
> fixes and we have been using it, I have a slight preference for the
> stax-api copy, but I can try to arrange upload of the xmlbeans api
> jar if it is generally preferred. Also, source for the stax-api jar
> is readily available whereas I haven't found the source for the
> xmlbeans jsr-173 jar.
>
> So, which stax api jar should I use?
>
> 2. I have never used xmlpublic.jar and can't quite figure out what it
> is intended for. IIUC it contains a subset of the contents of
> xbean.jar. When would this be used?
>
> 3. It looks like xbean_xpath.jar can be used together with xbean.jar
> in the same classloader to get xpath support. While not directly
> relevant to maven, I'd like to know if this will work if xbean_xpath
> is in a child classloader of the xbean jar classloader. In any case
> I believe the pom.xml for xbean_xpath.jar can simply list xbean.jar
> as a dependency.
>
> 4. Apparently xquery support requires saxon. Does it also require
> xbean_xpath.jar? If not, does saxon provide complete xpath support
> without xbean_xpath?
>
> I'm thinking that it would be adequate to supply poms for the
following:
> -xbean.jar by itself, not supporting xpath or xquery
> -xbean_xpath.jar + xbean.jar
> -xbean.jar + saxon (this does not imply redistributing saxon, just
> indicating that saxon is required to get xquery functionality)
> -xbean_xpath.jar + xbean.jar + saxon.jar (unless saxon also provides
> xpath functionality, see (4))
> -xml_public.jar (assuming I can understand what it is for :-)
>
> and possibly
> -jsr172-1.0.jar
>
> If the xmlbeans team can clarify these dependency issues I will work
> on constructing the appropriate poms and directory structure and
> submit a patch. The pom also can contain a lot of other information
> such as project location, team members, svn details, etc etc which I
> will try to at least rough out subject to correction.
>
> many thanks,
> david jencks
>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
> For additional commands, e-mail: dev-help@xmlbeans.apache.org
_______________________________________________________________________
Notice: This email message, together with any attachments, may contain
information of BEA Systems, Inc., its subsidiaries and affiliated
entities, that may be confidential, proprietary, copyrighted and/or
legally privileged, and is intended solely for the use of the individual
or entity named in this message. If you are not the intended recipient,
and have received this message in error, please immediately return this
by email and then delete it.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org