Re: [hibernate-dev] Namespaces for DOM4J Entity Mode
by Stephen Wolke
-------- Original Message --------
> From: "Max Rydahl Andersen" <max.andersen(a)jboss.com>
> Sent: Thursday, August 17, 2006 8:37 AM
> To: smwolke(a)geistig.com, hibernate-dev(a)lists.jboss.org
> Subject: Re: [hibernate-dev] Namespaces for DOM4J Entity Mode
>
> On Thu, 17 Aug 2006 05:55:14 +0200, Stephen Wolke <smwolke(a)geistig.com>
> wrote:
>
> > Attached is a diff file with the changes against the latest trunk. I
> > also had to modify the new build script, did not include that diff, so
> > that the mapping dtd file was jar'd up and validation was done with the
> > file in jar because that is where the new namespace attribute is
> > defined. This use to happen with the old build script but does not
> > happen anymore. Is that intended???
>
> I don't see that happen.
My responses are based on the assumption we are talking about the build.xml file.
>
> Comparing the old output and the new and they are 100% identical.
Starting with revision 10269 of the build.xml
- <patternset id="jar.files">
- <include name="**/*.dtd"/>
- <include name="**/*.xml"/>
- <include name="**/*.xslt"/>
- </patternset>
<jar jarfile="${jar.path}" basedir="${classes.dir}">
<include name="org/hibernate/**/*.class"/>
- <patternset refid="jar.files"/>
......
....
</jar>
The patternset tags for the dtd files have been removed from the build file. Without the patternset tags the mapping dtd file is not included in the jar file and I would assume then that validation occurs with the dtd at :http://hibernate.sourceforge.net/hibernate-mapping-3.0.dtd instead of the one in the jar file.
>
> What did you have to change to make it "work" ?
> /max
>
> >
> > -------- Original Message --------
> >> From: "Stephen Wolke" <smwolke(a)geistig.com>
> >> Sent: Wednesday, August 16, 2006 10:37 PM
> >> To: hibernate-dev(a)lists.jboss.org
> >> Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >>
> >> In trying to get the diff files I discovered that the revision number
> >> of the trunk that I made my changes on were on 9920 and the current
> >> code is on revision 10273 so now I am in the process of migrating the
> >> changes to the newer code base. How things have changed since 9920. I
> >> will get back with the changes when I am done.
> >>
> >> Steve
> >>
> >> -------- Original Message --------
> >> > From: "Stephen Wolke" <smwolke(a)geistig.com>
> >> > Sent: Wednesday, August 16, 2006 10:06 PM
> >> > To: steve.ebersole(a)jboss.com
> >> > Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >> >
> >> > Sorry the server was unaccessible from 8:00 am to about 7:00:pm today
> >> but the file should be accessible now. I am in the process of making
> >> diff files for the files changed and will send them as an attachment if
> >> the jboss mailing list will accept them. When the mailing list was on
> >> sourceforge my message was bounced because of an attachment.
> >> >
> >> > -------- Original Message --------
> >> > > From: "Steve Ebersole" <steve.ebersole(a)jboss.com>
> >> > > Sent: Wednesday, August 16, 2006 7:59 PM
> >> > > To: smwolke(a)geistig.com
> >> > > Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >> > >
> >> > > FYI, tried to access the zip, but the server does not seem to exist.
> >> > >
> >> > > -----Original Message-----
> >> > > From: hibernate-dev-bounces(a)lists.jboss.org
> >> > > [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Stephen
> >> > > Wolke
> >> > > Sent: Monday, August 14, 2006 8:57 PM
> >> > > To: hibernate-dev(a)lists.jboss.org
> >> > > Subject: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >> > >
> >> > > All,
> >> > >
> >> > > Just wanting to make available some changes that allow for creating
> >> XML
> >> > > instances with namespaces for the DOM4j Entity mode. The namespace
> >> is
> >> > > specified in the mapping file for element nodes and does not
> >> currently
> >> > > support the property tag. Actually, I have only verified the
> >> > > class,set,many-to-one,one-to-many tags. If this feature is welcome I
> >> > > would be happy to work on debugging and making changes to get it
> >> merged
> >> > > into the code base. I just need some direction, otherwise I will
> >> keep
> >> > > moving along.
> >> > >
> >> > > The code changes are at since the message seems to get bounced with
> >> an
> >> > > attachement:
> >> > >
> >> > > http://www.geistig.com/java/hibernate-namespace-updates.zip
> >> > >
> >> > > Steve
> >> > >
> >> > >
> >> > >
> >> > > _______________________________________________
> >> > > hibernate-dev mailing list
> >> > > hibernate-dev(a)lists.jboss.org
> >> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >> >
> >> >
> >> >
> >> >
> >> > _______________________________________________
> >> > hibernate-dev mailing list
> >> > hibernate-dev(a)lists.jboss.org
> >> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >>
> >>
> >>
> >>
> >> _______________________________________________
> >> hibernate-dev mailing list
> >> hibernate-dev(a)lists.jboss.org
> >> https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
>
>
>
> --
> --
> Max Rydahl Andersen
> callto://max.rydahl.andersen
>
> Hibernate
> max(a)hibernate.org
> http://hibernate.org
>
> JBoss a division of Red Hat
> max.andersen(a)jboss.com
19 years, 7 months
RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
by Stephen Wolke
Attached is a diff file with the changes against the latest trunk. I also had to modify the new build script, did not include that diff, so that the mapping dtd file was jar'd up and validation was done with the file in jar because that is where the new namespace attribute is defined. This use to happen with the old build script but does not happen anymore. Is that intended???
-------- Original Message --------
> From: "Stephen Wolke" <smwolke(a)geistig.com>
> Sent: Wednesday, August 16, 2006 10:37 PM
> To: hibernate-dev(a)lists.jboss.org
> Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
>
> In trying to get the diff files I discovered that the revision number of the trunk that I made my changes on were on 9920 and the current code is on revision 10273 so now I am in the process of migrating the changes to the newer code base. How things have changed since 9920. I will get back with the changes when I am done.
>
> Steve
>
> -------- Original Message --------
> > From: "Stephen Wolke" <smwolke(a)geistig.com>
> > Sent: Wednesday, August 16, 2006 10:06 PM
> > To: steve.ebersole(a)jboss.com
> > Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >
> > Sorry the server was unaccessible from 8:00 am to about 7:00:pm today but the file should be accessible now. I am in the process of making diff files for the files changed and will send them as an attachment if the jboss mailing list will accept them. When the mailing list was on sourceforge my message was bounced because of an attachment.
> >
> > -------- Original Message --------
> > > From: "Steve Ebersole" <steve.ebersole(a)jboss.com>
> > > Sent: Wednesday, August 16, 2006 7:59 PM
> > > To: smwolke(a)geistig.com
> > > Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
> > >
> > > FYI, tried to access the zip, but the server does not seem to exist.
> > >
> > > -----Original Message-----
> > > From: hibernate-dev-bounces(a)lists.jboss.org
> > > [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Stephen
> > > Wolke
> > > Sent: Monday, August 14, 2006 8:57 PM
> > > To: hibernate-dev(a)lists.jboss.org
> > > Subject: [hibernate-dev] Namespaces for DOM4J Entity Mode
> > >
> > > All,
> > >
> > > Just wanting to make available some changes that allow for creating XML
> > > instances with namespaces for the DOM4j Entity mode. The namespace is
> > > specified in the mapping file for element nodes and does not currently
> > > support the property tag. Actually, I have only verified the
> > > class,set,many-to-one,one-to-many tags. If this feature is welcome I
> > > would be happy to work on debugging and making changes to get it merged
> > > into the code base. I just need some direction, otherwise I will keep
> > > moving along.
> > >
> > > The code changes are at since the message seems to get bounced with an
> > > attachement:
> > >
> > > http://www.geistig.com/java/hibernate-namespace-updates.zip
> > >
> > > Steve
> > >
> > >
> > >
> > > _______________________________________________
> > > hibernate-dev mailing list
> > > hibernate-dev(a)lists.jboss.org
> > > https://lists.jboss.org/mailman/listinfo/hibernate-dev
> >
> >
> >
> >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
19 years, 7 months
New build structure
by Max Rydahl Andersen
Hi guys,
Couple of things to document/talk about what dependencies hibernateext and
the eclipse plugins have on a hibernate distribution and on hibernate3 src
it self.
hibernateext/eclipse plugins just use hibernate distribution for the
following things:
1) being able to run ant (ant-launcher.jar etc.)
2) the shared libs (including hsqldb.jar which are in different locations
depending wether it is dist or src)
3) hibernate3.jar
4) javadoc/jdstyle.css
It uses the hibernate3 src for:
5) docbook DTD references
("../../../../../Hibernate3/doc/reference/support/docbook-dtd/docbookx.dtd"
is to be found in all the docs)
6) docbook sources to build the eclipse hibernate help file.
I've made the prepare-up-dir so it now includes #4 and everything (that I
know of) that depends seem to work fine with the prepare-up-dir.
#5 would be great to fix so all the shared doc (dtd's AND build.xml) would
be the same.
#6 I could actually see being made part of the hibernate3 core build (it
is just basically applying a set of xsl files on the docbook to get a .zip)
The best thing of course would be to make these dependencies more
explicit....
btw. hibernate-client.jar only contains bytecode.javassist should it not
also contain bytecode.cglib in case the user is running with cglib?
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
19 years, 7 months
RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
by Stephen Wolke
In trying to get the diff files I discovered that the revision number of the trunk that I made my changes on were on 9920 and the current code is on revision 10273 so now I am in the process of migrating the changes to the newer code base. How things have changed since 9920. I will get back with the changes when I am done.
Steve
-------- Original Message --------
> From: "Stephen Wolke" <smwolke(a)geistig.com>
> Sent: Wednesday, August 16, 2006 10:06 PM
> To: steve.ebersole(a)jboss.com
> Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
>
> Sorry the server was unaccessible from 8:00 am to about 7:00:pm today but the file should be accessible now. I am in the process of making diff files for the files changed and will send them as an attachment if the jboss mailing list will accept them. When the mailing list was on sourceforge my message was bounced because of an attachment.
>
> -------- Original Message --------
> > From: "Steve Ebersole" <steve.ebersole(a)jboss.com>
> > Sent: Wednesday, August 16, 2006 7:59 PM
> > To: smwolke(a)geistig.com
> > Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >
> > FYI, tried to access the zip, but the server does not seem to exist.
> >
> > -----Original Message-----
> > From: hibernate-dev-bounces(a)lists.jboss.org
> > [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Stephen
> > Wolke
> > Sent: Monday, August 14, 2006 8:57 PM
> > To: hibernate-dev(a)lists.jboss.org
> > Subject: [hibernate-dev] Namespaces for DOM4J Entity Mode
> >
> > All,
> >
> > Just wanting to make available some changes that allow for creating XML
> > instances with namespaces for the DOM4j Entity mode. The namespace is
> > specified in the mapping file for element nodes and does not currently
> > support the property tag. Actually, I have only verified the
> > class,set,many-to-one,one-to-many tags. If this feature is welcome I
> > would be happy to work on debugging and making changes to get it merged
> > into the code base. I just need some direction, otherwise I will keep
> > moving along.
> >
> > The code changes are at since the message seems to get bounced with an
> > attachement:
> >
> > http://www.geistig.com/java/hibernate-namespace-updates.zip
> >
> > Steve
> >
> >
> >
> > _______________________________________________
> > hibernate-dev mailing list
> > hibernate-dev(a)lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
>
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
19 years, 7 months
RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
by Stephen Wolke
Sorry the server was unaccessible from 8:00 am to about 7:00:pm today but the file should be accessible now. I am in the process of making diff files for the files changed and will send them as an attachment if the jboss mailing list will accept them. When the mailing list was on sourceforge my message was bounced because of an attachment.
-------- Original Message --------
> From: "Steve Ebersole" <steve.ebersole(a)jboss.com>
> Sent: Wednesday, August 16, 2006 7:59 PM
> To: smwolke(a)geistig.com
> Subject: RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
>
> FYI, tried to access the zip, but the server does not seem to exist.
>
> -----Original Message-----
> From: hibernate-dev-bounces(a)lists.jboss.org
> [mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Stephen
> Wolke
> Sent: Monday, August 14, 2006 8:57 PM
> To: hibernate-dev(a)lists.jboss.org
> Subject: [hibernate-dev] Namespaces for DOM4J Entity Mode
>
> All,
>
> Just wanting to make available some changes that allow for creating XML
> instances with namespaces for the DOM4j Entity mode. The namespace is
> specified in the mapping file for element nodes and does not currently
> support the property tag. Actually, I have only verified the
> class,set,many-to-one,one-to-many tags. If this feature is welcome I
> would be happy to work on debugging and making changes to get it merged
> into the code base. I just need some direction, otherwise I will keep
> moving along.
>
> The code changes are at since the message seems to get bounced with an
> attachement:
>
> http://www.geistig.com/java/hibernate-namespace-updates.zip
>
> Steve
>
>
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
19 years, 7 months
RE: [hibernate-dev] new build script
by Steve Ebersole
No, not really; although it could. I was trying to save the whole copy
step...
-----Original Message-----
From: Max Andersen
Sent: Wednesday, August 16, 2006 10:16 AM
To: Emmanuel Bernard; Steve Ebersole
Cc: hibernate-dev(a)lists.jboss.org
Subject: Re: [hibernate-dev] new build script
On Wed, 16 Aug 2006 15:48:59 +0200, Emmanuel Bernard
<emmanuel(a)hibernate.org> wrote:
> the javadoc copy is also needed for the directory up task, unless we
> change the HibernateExt tasks to point to the new structure
i haven't had time to look at this yet, but doesn't the new build
generate
a
dir somewhere that is just as what the distribution will be like ? That
is
basically
what we need to point at.
-max
> Steve Ebersole wrote:
>>
>> I checked in a new build script today and wanted to give everyone a
>> breakdown of the various changes.
>>
>> The biggest change is that we no longer build "a directory up". All
>> build stuff now happens within the project directory; all output
>> "artifacts" end up somewhere in the build directory. For those of
you
>> that might rely on the "directory up", I added a specific target for
>> y'all (prepare-dir-up) which prepares the directory up just as before
>> (well the hibernate jar and libs).
>>
>> The other big change had to do with the test suite. Previously, we
had
>> this broken out into two separate targets: one with instrumentation
and
>> one without. Now, we have a unified notion of running the test
suite.
>> Note that this is still a little in flux as not all
>> instrumentation-dependent tests are properly covered yet...
>>
>> Minor (for some), but I also added the capability to run the eg stuff
>> inline, meaning within the checkout dir. Run 'eg.inline' instead of
>> 'eg'.
>>
>> There are various other minor changes, but these were the big ones...
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
--
--
Max Rydahl Andersen
callto://max.rydahl.andersen
Hibernate
max(a)hibernate.org
http://hibernate.org
JBoss a division of Red Hat
max.andersen(a)jboss.com
19 years, 7 months
RE: [hibernate-dev] new build script
by Steve Ebersole
So then basically it just references it and never uses it...
-----Original Message-----
From: Emmanuel Bernard [mailto:emmanuel@hibernate.org]
Sent: Wednesday, August 16, 2006 9:58 AM
To: Steve Ebersole
Cc: hibernate-dev(a)lists.jboss.org
Subject: Re: [hibernate-dev] new build script
the ant script looks for it, if the directory is not there it fails. I
don't think it actually links javadoc though.
Steve Ebersole wrote:
> I assume it does this for linking? How does that work with a
file-based
> URL? I mean when you actually bundle? Is it just assumed that the
> separate subprojects are unzipped in the same layout as our build
dirs?
>
>
> -----Original Message-----
> From: Emmanuel Bernard [mailto:emmanuel@hibernate.org]
> Sent: Wednesday, August 16, 2006 8:49 AM
> To: Steve Ebersole
> Cc: hibernate-dev(a)lists.jboss.org
> Subject: Re: [hibernate-dev] new build script
>
> the javadoc copy is also needed for the directory up task, unless we
> change the HibernateExt tasks to point to the new structure
>
> Steve Ebersole wrote:
>
>> I checked in a new build script today and wanted to give everyone a
>> breakdown of the various changes.
>>
>> The biggest change is that we no longer build "a directory up". All
>> build stuff now happens within the project directory; all output
>> "artifacts" end up somewhere in the build directory. For those of
you
>> that might rely on the "directory up", I added a specific target for
>> y'all (prepare-dir-up) which prepares the directory up just as before
>> (well the hibernate jar and libs).
>>
>> The other big change had to do with the test suite. Previously, we
>>
> had
>
>> this broken out into two separate targets: one with instrumentation
>>
> and
>
>> one without. Now, we have a unified notion of running the test
suite.
>> Note that this is still a little in flux as not all
>> instrumentation-dependent tests are properly covered yet...
>>
>> Minor (for some), but I also added the capability to run the eg stuff
>> inline, meaning within the checkout dir. Run 'eg.inline' instead of
>> 'eg'.
>>
>> There are various other minor changes, but these were the big ones...
>>
>> _______________________________________________
>> hibernate-dev mailing list
>> hibernate-dev(a)lists.jboss.org
>> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>>
>>
>
>
19 years, 7 months
new build script
by Steve Ebersole
I checked in a new build script today and wanted to give everyone a
breakdown of the various changes.
The biggest change is that we no longer build "a directory up". All
build stuff now happens within the project directory; all output
"artifacts" end up somewhere in the build directory. For those of you
that might rely on the "directory up", I added a specific target for
y'all (prepare-dir-up) which prepares the directory up just as before
(well the hibernate jar and libs).
The other big change had to do with the test suite. Previously, we had
this broken out into two separate targets: one with instrumentation and
one without. Now, we have a unified notion of running the test suite.
Note that this is still a little in flux as not all
instrumentation-dependent tests are properly covered yet...
Minor (for some), but I also added the capability to run the eg stuff
inline, meaning within the checkout dir. Run 'eg.inline' instead of
'eg'.
There are various other minor changes, but these were the big ones...
19 years, 7 months
RE: [hibernate-dev] Namespaces for DOM4J Entity Mode
by Steve Ebersole
FYI, tried to access the zip, but the server does not seem to exist.
-----Original Message-----
From: hibernate-dev-bounces(a)lists.jboss.org
[mailto:hibernate-dev-bounces@lists.jboss.org] On Behalf Of Stephen
Wolke
Sent: Monday, August 14, 2006 8:57 PM
To: hibernate-dev(a)lists.jboss.org
Subject: [hibernate-dev] Namespaces for DOM4J Entity Mode
All,
Just wanting to make available some changes that allow for creating XML
instances with namespaces for the DOM4j Entity mode. The namespace is
specified in the mapping file for element nodes and does not currently
support the property tag. Actually, I have only verified the
class,set,many-to-one,one-to-many tags. If this feature is welcome I
would be happy to work on debugging and making changes to get it merged
into the code base. I just need some direction, otherwise I will keep
moving along.
The code changes are at since the message seems to get bounced with an
attachement:
http://www.geistig.com/java/hibernate-namespace-updates.zip
Steve
_______________________________________________
hibernate-dev mailing list
hibernate-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/hibernate-dev
19 years, 7 months
RE: [hibernate-dev] new build script
by Steve Ebersole
I assume it does this for linking? How does that work with a file-based
URL? I mean when you actually bundle? Is it just assumed that the
separate subprojects are unzipped in the same layout as our build dirs?
-----Original Message-----
From: Emmanuel Bernard [mailto:emmanuel@hibernate.org]
Sent: Wednesday, August 16, 2006 8:49 AM
To: Steve Ebersole
Cc: hibernate-dev(a)lists.jboss.org
Subject: Re: [hibernate-dev] new build script
the javadoc copy is also needed for the directory up task, unless we
change the HibernateExt tasks to point to the new structure
Steve Ebersole wrote:
>
> I checked in a new build script today and wanted to give everyone a
> breakdown of the various changes.
>
> The biggest change is that we no longer build "a directory up". All
> build stuff now happens within the project directory; all output
> "artifacts" end up somewhere in the build directory. For those of you
> that might rely on the "directory up", I added a specific target for
> y'all (prepare-dir-up) which prepares the directory up just as before
> (well the hibernate jar and libs).
>
> The other big change had to do with the test suite. Previously, we
had
> this broken out into two separate targets: one with instrumentation
and
> one without. Now, we have a unified notion of running the test suite.
> Note that this is still a little in flux as not all
> instrumentation-dependent tests are properly covered yet...
>
> Minor (for some), but I also added the capability to run the eg stuff
> inline, meaning within the checkout dir. Run 'eg.inline' instead of
> 'eg'.
>
> There are various other minor changes, but these were the big ones...
>
> _______________________________________________
> hibernate-dev mailing list
> hibernate-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/hibernate-dev
>
19 years, 7 months