You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@xmlbeans.apache.org by Deepak Bhole <db...@redhat.com> on 2006/01/24 21:38:55 UTC

Repackaged classes during xmlbeans 2.1.0 build

Hi,

I am working on packaging xmlbeans 2.1.0 for JPackage (jpackage.org).
While building xmlbeans, I noticed that classes from two projects (jam
and piccolo) are being re-packaged, with the package structure being
changed to a org.apache.xmlbeans.* pattern.

Is there any particular reason why classes are being repackaged like
this, instead of being used with existing package names?

Thanks,
Deepak


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org

Re: Repackaged classes during xmlbeans 2.1.0 build

Posted by Deepak Bhole <db...@redhat.com>.
On Tue, 2006-01-24 at 16:44 -0800, Trevor Harmon wrote:
> On Jan 24, 2006, at 1:59 PM, Deepak Bhole wrote:
> 
> > Are xalan/xerces required during build?
> 
> I'm not sure, but I do know there are JAR files from those projects  
> that are shipped with the XMLBeans distribution (for instance,  
> resolver.jar), so I assume they're required for something. Better  
> safe than sorry...
> 
> > I don't have it in my build dir
> > and it seems to be compiling fine (atleast the default project).
> 
> Perhaps it is in your classpath somewhere?


Nope, they definitely aren't. But I see now as to why it compiled for me
without those jars. I don't run/compile the tests. The xalan/xerces jars
are in the test lib directories, so they must be used only for testing,
not building.


Cheers,
Deepak


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org

Re: Repackaged classes during xmlbeans 2.1.0 build

Posted by Trevor Harmon <tr...@vocaro.com>.
On Jan 24, 2006, at 1:59 PM, Deepak Bhole wrote:

> Are xalan/xerces required during build?

I'm not sure, but I do know there are JAR files from those projects  
that are shipped with the XMLBeans distribution (for instance,  
resolver.jar), so I assume they're required for something. Better  
safe than sorry...

> I don't have it in my build dir
> and it seems to be compiling fine (atleast the default project).

Perhaps it is in your classpath somewhere?

Trevor

Re: Repackaged classes during xmlbeans 2.1.0 build

Posted by Deepak Bhole <db...@redhat.com>.
On Tue, 2006-01-24 at 13:19 -0800, Trevor Harmon wrote:
> On Jan 24, 2006, at 12:38 PM, Deepak Bhole wrote:
> 
> > I am working on packaging xmlbeans 2.1.0 for JPackage (jpackage.org).
> > While building xmlbeans, I noticed that classes from two projects (jam
> > and piccolo) are being re-packaged, with the package structure being
> > changed to a org.apache.xmlbeans.* pattern.
> >
> > Is there any particular reason why classes are being repackaged like
> > this, instead of being used with existing package names?
> 
> I ran into the exact same confusion while trying to write a Fink  
> package description for XmlBeans. It was discussed on this list;  
> archives are here:
> 
> http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200511.mbox/% 
> 3c6E7FB378-94C0-4948-85B7-8641387B3043@vocaro.com%3e
> 
> and here:
> 
> http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200512.mbox/% 
> 3cDA4802E9-0743-443D-AB2D-70FDB43F4598@vocaro.com%3e
> 
> (The same thread is split across two links because the mail manager  
> isn't smart enough to understand that a thread might span into the  
> next month!)
> 
> Basically, the answer to your question is that XmlBeans uses modified  
> versions of JAM and Piccolo, and these are injected into xbean.jar  
> with different package names to avoid conflicts.
> 

Thanks! I searched for variations of "repackage" on the lists, but it
turned up nothing. Anyways, that answers my questions perfectly. Thanks
again.

> By the way, my Fink package description is here:
> http://sourceforge.net/tracker/download.php? 
> group_id=17203&atid=414256&file_id=163429&aid=1307707
> 
> Note that I pull in dependencies from Saxon, Xerces-J, Xalan-J, and  
> StAX, but not from JAM nor Piccolo.
> 

Are xalan/xerces required during build? I don't have it in my build dir
and it seems to be compiling fine (atleast the default project).

To anyone who may know:
Are the changes that have been made to the source for jam and piccolo
documented somewhere?

Thanks!
Deepak


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@xmlbeans.apache.org
For additional commands, e-mail: dev-help@xmlbeans.apache.org

Re: Repackaged classes during xmlbeans 2.1.0 build

Posted by Trevor Harmon <tr...@vocaro.com>.
On Jan 24, 2006, at 12:38 PM, Deepak Bhole wrote:

> I am working on packaging xmlbeans 2.1.0 for JPackage (jpackage.org).
> While building xmlbeans, I noticed that classes from two projects (jam
> and piccolo) are being re-packaged, with the package structure being
> changed to a org.apache.xmlbeans.* pattern.
>
> Is there any particular reason why classes are being repackaged like
> this, instead of being used with existing package names?

I ran into the exact same confusion while trying to write a Fink  
package description for XmlBeans. It was discussed on this list;  
archives are here:

http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200511.mbox/% 
3c6E7FB378-94C0-4948-85B7-8641387B3043@vocaro.com%3e

and here:

http://mail-archives.apache.org/mod_mbox/xmlbeans-dev/200512.mbox/% 
3cDA4802E9-0743-443D-AB2D-70FDB43F4598@vocaro.com%3e

(The same thread is split across two links because the mail manager  
isn't smart enough to understand that a thread might span into the  
next month!)

Basically, the answer to your question is that XmlBeans uses modified  
versions of JAM and Piccolo, and these are injected into xbean.jar  
with different package names to avoid conflicts.

By the way, my Fink package description is here:
http://sourceforge.net/tracker/download.php? 
group_id=17203&atid=414256&file_id=163429&aid=1307707

Note that I pull in dependencies from Saxon, Xerces-J, Xalan-J, and  
StAX, but not from JAM nor Piccolo.

Trevor