On Sep 25, 2012, at 7:52 AM, "Chen, Pei" <[email protected]> wrote: > What about those larger resources such as LVG or Dictionary Lookup? In my > opinion, they probably shouldn't even be versioned in the same spot as the > java srcs... Perhaps an /incr directory outside of trunk?
My suggestion (2) already addressed this. Create a separate dictionary-lookup-resources (or whatever you want to name it) module alongside dictionary-lookup. An added benefit of making the resources modules real Maven modules is that you can then write tests that test your code using the models, etc. from the resources modules. If you have them somewhere else, like "/incr", then it means your tests won't run once they're packaged in a jar file. On Sep 25, 2012, at 8:50 AM, "Bleeker, Troy C." <[email protected]> wrote: > For the best first experience, is it best to include an all-in-one package, > including the LVG and dictionary lookup, even though it will take longer to > download? If so, shouldn't they be co-located with the other resources? Well, as long as we make the resource packages real Maven modules (as I suggest above), then it's nearly trivial to write another Maven module that just aggregates the other dependencies. So no, all your resources don't need to be in the same place if the only reason you're doing that is to make an easy single-file download. On Sep 25, 2012, at 9:15 AM, "Coarr, Matt" <[email protected]> wrote: > Could we have two top level directories in svn -- main-modules and > resource-modules? I wouldn't recommend this approach. Having both code modules and resource modules at the same level makes it easier to aggregate everything into a single-file download (which I gather we'll still want at some point). On Sep 25, 2012, at 3:22 PM, "Chen, Pei" <[email protected]> wrote: > I think Brandyn and others had a reasonable suggestion to use the name > instead of location paths in those pesky descriptor xml files- Assuming > they're in the classpath (placed in src/main/resources). Awesome. Thanks! Steve
