OJB block clean up

[Joerg Heinicke <jh...@virbus.de>]

In the block there is a WEB-INF directory including compiled classes. 
IMO that's not ok and from what I see I think it can be removed, but 
some possible useful files could be missing afterwards: OJB.properties, 
repository.xml and repository.dtd. The rest is already in the java 
directory AFAICS.

Antonio?

Joerg

Re: OJB block clean up

[Antonio Gallardo <ag...@agsoftware.dnsalias.com>]

Joerg Heinicke dijo:
Hi Joerg:

>> Thanks for asking Joerg. The .class are there because they are already
>> "JDO enhanced". This is a special step after compiling in JDO.
>
> Yes, I read about it. But these class files are used nowhere? How will
> they get to build/webapp/samples/**?

Before it was automatically copied. I don't check it recently. Of course I
saw some changes on the build.xml and gump.xml But does not check it.

>> My problem was I don't saw where I can put the special ANT task. :-(
>
> Do you have such an Ant task? We have a directory tools/src/anttasks,
> where such things can be placed into.

Thanks for the tip. I will check this. At time when I tried to do this
nobody answer the question.

What I need is to launch a java process for JDO enhancing after compiling
the sample classes.

It this posible in our current build system without hacking it too much?

Best Regards,

Antonio Gallardo

Re: OJB block clean up

[Joerg Heinicke <jh...@virbus.de>]

On 18.11.2003 17:49, Antonio Gallardo wrote:

> Joerg Heinicke dijo:
> 
>>In the block there is a WEB-INF directory including compiled classes.
>>IMO that's not ok and from what I see I think it can be removed, but
>>some possible useful files could be missing afterwards: OJB.properties,
>>repository.xml and repository.dtd. The rest is already in the java
>>directory AFAICS.
>>
>>Antonio?
> 
> 
> Hi Joerg:
> 
> Thanks for asking Joerg. The .class are there because they are already
> "JDO enhanced". This is a special step after compiling in JDO.

Yes, I read about it. But these class files are used nowhere? How will 
they get to build/webapp/samples/**?

> Since we have no right to distribute jdo libs. I did it in this way. But
> now I thought we can check if the user has the jars in the dir and "JDO
> enhance" them only if the user has the JDO jars.
> 
> I requieres to launch a special ANT task from the JDO jar libs. If you can
> help me I can provide more info about how it might work.
> 
> My problem was I don't saw where I can put the special ANT task. :-(

Do you have such an Ant task? We have a directory tools/src/anttasks, 
where such things can be placed into.

Joerg

Re: OJB block clean up

[Antonio Gallardo <ag...@agsoftware.dnsalias.com>]

Joerg Heinicke dijo:
> In the block there is a WEB-INF directory including compiled classes.
> IMO that's not ok and from what I see I think it can be removed, but
> some possible useful files could be missing afterwards: OJB.properties,
> repository.xml and repository.dtd. The rest is already in the java
> directory AFAICS.
>
> Antonio?

Hi Joerg:

Thanks for asking Joerg. The .class are there because they are already
"JDO enhanced". This is a special step after compiling in JDO.

Since we have no right to distribute jdo libs. I did it in this way. But
now I thought we can check if the user has the jars in the dir and "JDO
enhance" them only if the user has the JDO jars.

I requieres to launch a special ANT task from the JDO jar libs. If you can
help me I can provide more info about how it might work.

My problem was I don't saw where I can put the special ANT task. :-(

Best Regards,

Antonio Gallardo