Maven's test scope only means that it needs to be on the test classpath. It would not introduce a runtime or even compile time dependency of jdo-api.jar. Optional means that if Maven can't find it, compilation should still succeed, which it wouldn't if it weren't available. Again, <scope> and <optional> are orthogonal concerns.
-Matthew Sent from mobile device. Responses brief. On Dec 9, 2010, at 1:24 AM, Andy Jefferson <[email protected]> wrote: >> You do not want to mark it as not optional since IIRC that would mean that >> anything building against jdo-api.jar would have to have ant in the >> CLASSPATH. We do not want that. > > Although maybe the "test" scope would override that requirement? > > No subsititute for actually trying it with a clean M2 repo, and > building/running a simple JDO project against it (with clean M2 repo also). > > -- > Andy > DataNucleus (http://www.datanucleus.org)
