Hi all,
I compiled new ( and enhanced ) version of
my demo for hibernate/xdoclet/jboss
Now there are:
- 3 Entites: address, customer, country
- 1 : n relation ( customer has several addresses )
- relation address - country
you will need current CVS version of xdoclet hibernate
module to run
Message:
The following issue has been closed.
Resolver: Aslak Hellesøy
Date: Thu, 19 Dec 2002 3:37 PM
It would require too much work in the grammar, and I don't see a real benefit.
And what if the comments were intentional? Lots of warnings?
We can't baby-sit programmers who have
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED]]On Behalf Of Mathias
> Bogaert
> Sent: 20. desember 2002 05:15
> To: [EMAIL PROTECTED]
> Subject: [Xdoclet-devel] JGuru
>
>
> Guys,
>
> I received the JGuru contract. This is bullshit. Here are some terms I
> quest
Are you using Class.forName()?
not really my field - but doesn't ant have its own classloader? I'm
guessing its the same issue as using junit in ant...
cheers
dim
- Original Message -
From: "tek1" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, December 20, 2002 5:27 AM
Subjec
i've nearly finished a new castor subtask for xdoclet and part of it
actually makes a connection to the database and creates the tables for you.
however, i'm getting the below error when i execute the subtask, even
though the (postgresql) jdbc driver is on the classpath:
[ejbdoclet] (XDocletMai
Guys,
I received the JGuru contract. This is bullshit. Here are some terms I
question:
Intellectual Property
All content submitted by the contractor is the sole ownership of that
contractor; however, the contractor grants jGuru an irrevocable, lifetime,
worldw
All Ant properties should be passed down in order to allow overriding
from the master process, I would think. Is there a reason not to pass
them all down? This is how works.
Also, Sam has asked that build.sysclasspath in particular be passed
down, as this his how Gump operates by ensuring *o
Erik, what kind of property should be passed on? The build was just too
big to normally fit in a single process, that's why we start a new
instance of Ant for each module. If some properties (env.blabla?) should
be passed on then let me know which ones and how. I don't any clue how
Gump really work
Message:
A new issue has been created in JIRA.
-
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-210
Here is an overview of the issue:
That worked. I can now put this in my project.properties file:
maven.xdoclet.ejbdoclet.jboss.Version=3.0.3
where with James' previous patch, I was using this:
maven.xdoclet.ejbdoclet.jboss.0.version=3.0.3
I'm curious, though: is there any rhyme or reason as to why the version
property is
There are some Gump issues with XDoclet and overriding properties being
discussed on the ant-dev list.
Thoughts?
I haven't had a look at but we should investigate properties
being passed down somehow.
Erik
Original Message
Subject: Re: Specifying properties from the command
Just forgot to say where to get it:
http://www.pribluda.de/hibernate-test.tar.gz
regards,
=
Konstantin Priblouda ( ko5tik )Freelance Software developer
< http://www.pribluda.de > < play java games -> http://www.yook.de >
< render charts online -> http://www.pribluda.de/povray/ >
___
Message:
A new issue has been created in JIRA.
-
View the issue:
http://opensource.atlassian.com/projects/xdoclet/secure/ViewIssue.jspa?key=XDT-209
Here is an overview of the issue:
Update of
/cvsroot/xdoclet/xdoclet/modules/hibernate/src/xdoclet/modules/hibernate/resources
In directory sc8-pr-cvs1:/tmp/cvs-serv15396/src/xdoclet/modules/hibernate/resources
Modified Files:
hibernate-properties.xdt
Log Message:
fixed bag mapping
Index: hibernate-properties.xdt
=
Update of /cvsroot/xdoclet/xdoclet/modules/hibernate/src/META-INF
In directory sc8-pr-cvs1:/tmp/cvs-serv15396/src/META-INF
Modified Files:
xtags.xml
Log Message:
fixed bag mapping
Index: xtags.xml
===
RCS file: /cvsroot/xdo
Please register this as an issue in JIRA. It will get lost otherwise...
Cheers,
Aslak
- Original Message -
From: Michal Maczka <[EMAIL PROTECTED]>
Date: Thursday, December 19, 2002 1:41 pm
Subject: [Xdoclet-devel] Maven issue compilation path issue
> Hi Aslak
>
> I have one more remark
Hi Aslak
I have one more remark regarding compilation path in Maven.
In my opinion it would be even better if an update of compilation path is
separated from xdoclet target(s).
Simply if I want to start XDoclet from time to time and perform java
compilation more often.
In this case it is still re
--- tek1 <[EMAIL PROTECTED]> wrote:
> just wondering why this move was made?
Explanation is easy: since aslak & ara started to play
with maven ( and developing maven plugins etc ),
decision to tack a version number on jar files
came automatically. Maven has pretty nice dependency
handling ( and
18 matches
Mail list logo
