Ah. I thought I had done that before. I'm a bit of a maven novice, so
thanks. That fixed it.
Lee
On 5/8/2011 12:15 PM, Andrea Aime wrote:
> On Sun, May 8, 2011 at 7:23 PM, lee-verizon wrote:
>> I did run it in the root originally, and I see now that the supported
>> modules indeed have the corr
On Sun, May 8, 2011 at 7:23 PM, lee-verizon wrote:
> I did run it in the root originally, and I see now that the supported
> modules indeed have the correct dependencies, but the unsupported modules do
> not. In particular, the unsupported module I'm working on - CSV. Should I
> just do it by han
I did run it in the root originally, and I see now that the supported
modules indeed have the correct dependencies, but the unsupported
modules do not. In particular, the unsupported module I'm working on -
CSV. Should I just do it by hand, or is there a way to persuade maven
to do the unsuppo
On Sun, May 8, 2011 at 4:13 PM, lee-verizon wrote:
> I have a basic question about how projects are/should be set up in
> eclipse. I used maven eclipse:eclipse to create .project and .classpath
> files for all the projects. But I see that the .classpath files have
> cross-project dependencies done
I have a basic question about how projects are/should be set up in
eclipse. I used maven eclipse:eclipse to create .project and .classpath
files for all the projects. But I see that the .classpath files have
cross-project dependencies done using jar files rather than depending
directly on the o
