Use ANT.
Using ANT to build OJB should work without problems on any platform.
Thomas
Charles N. Harvey III wrote:
I'm having a lot of trouble building from HEAD. Do I use maven or ant?
I get the STRANGEST error when I try to use ant. Its probably something
with
my maven/ant installation
I'm having a lot of trouble building from HEAD. Do I use maven or ant?
I get the STRANGEST error when I try to use ant. Its probably something
with
my maven/ant installation though.
Ok, so, I'm getting there. I'm starting to understand JDO a bit. I hadn't
actually looked at it before today.
Hi all,
I want to try JDO with OJB but I have some misunderstood.
I am not very clear about where to put the MetaData for the mapping ?
In the repository.xml or in the XXX.jdo ?
I look in the tutorial5 and I see that information for the mapping are
stored in the Product.jdo.
So should we put
You need both if you are using the JDORI plugin. It is annoying =(
The native JDO impl I am working on for OJB will allow you to just use
the OJB mappings as the .jdo files will only be used for (optional in
OJB but not for spec-compliant JDO) bytecode enhancement process. This
JDO impl is
Brian,
I _don't_ want to filter my queries. Can I give the native
implementation a try?
Would that be the CVS Head or would it be a different branch?
Thanks.
Charlie
Brian McCallister wrote:
You need both if you are using the JDORI plugin. It is annoying =(
The native JDO impl I am working
You will need CVS HEAD, correct -- also make sure you are comfy looking
around the sources to see what is implemented and not. I have tried to
throw OperationUnsupportedException(Not yet imeplemented!) when a
feature isn't actually implemented yet =)
This code is being actively written so it
