Hi!
Thanks for the explanation about how it works. Considering that I had problems running the suite
from withing the IDE, I have modified the base test to use the Jackrabbit API to import custom nodes.
Considering that there is no specification to handle custom node types, I would say that both
solutions are oke. The single difference is that the programmatic approach (the way i have modified
the base test) will allow running the suite from within the IDE.
./alex
--
.w( the_mindstorm )p.
#: Christophe Lombart changed the world a bit at a time by saying (astral date:
2/2/2006 9:35 PM) :#
For unit test, the custom node type file solution is quite easy.
of course, for real applications I see good reasons to use the API to
import the node types.
How is it working for the unit tests ? (see the maven.xml, it is
quite simple to understand) :
1/ Node types used in the unit tests are added in :
/src/test-config/repository/repository/nodetypes/custom_nodetypes.xml
2/ target/repository contains the repository for the unit test and can
clean up with " maven clean" .
3/ before starting the unit tests,
/src/test-config/repository/repository/nodetypes/custom_nodetypes.xml
is copied into target/repository/repository/nodetypes
of course, we have the same result by using the API but I didn't know
that Oliver has finished that. Up to you to choose what you want.
On 2/2/06, Oliver Kiessler <[EMAIL PROTECTED]> wrote:
> That's how I have modified the BaseTest to do ;-). Register the custom node
types using Jackrabbit
> API (before Christophe explaining how it works with Maven).
sorry about that! I didn't know... Well, both ways are possible but I
prefer solving this programmatically.... ;)
- oliver
--
Best regards,
Christophe
