Re: Finding the right Maven dependencies

Aha! I didn;t see the maven eclipse:generate-classpath option :-). Works 
great now.

Thanks for the help Shash,

Max

> Max,
>
> Just to make sure, your apps/services don't need the 2nd level of 
> dependencies, look in CVS at any of the apps to se what dependencies 
> they typically have.  Only your project needs the second level of 
> dependencies, and for that use "maven keel:maven".
>
> Once you get your app/service or your project building under 
> command-line Maven, do a "maven eclipse" and Maven will generate the 
> correct .classpath/.project for Eclipse, so you can import the project 
> in Eclipse.  If you already have the project imported in Eclipse, do 
> "maven eclipse:generate-classpath" after modifying dependencies in 
> project.xml, and do a Refresh on the project in Eclipse.
>
> HTH,
> Shash
>
>> Hi Shash,
>>
>> Thanks for the info. I am using Eclipse to do my development 
>> particularly for all it's niceties. That's why I was looking for the 
>> dependencies. From what I can see eclipse does not have the same 
>> "automagic" feature to pull in the required dependencies. I have 
>> tried mevenide but that does not suggest the second level of 
>> dependencies.
>>
>> In my case I am writing a app- module and have included keel-common, 
>> keel-core and keel-container. StandardLogEnabledModel depends in turn 
>> on org.apache.avalon.framework.configuration.Configurable. Any ideas 
>> on how do I get eclipse to add automatically this to my classpath 
>> without adding the entire maven repository?
>>
>> Thanks,
>> Max
>>
>>> Max,
>>>
>>> I am not sure there is such a way, but you don't need it either.  
>>> Look in example-projects/hoj/project.xml, I have tried to list the 
>>> minimal dependencies for that project.  List your own modules, the 
>>> Keel app-* modules you need, the Keel svc-* modules you need, 
>>> specify one or more clnt-*, and one comm-* module.  The other 
>>> dependencies, like keel-common, keel-container, keel-core and 3rd 
>>> party JARs required by any of your primary dependencies, will be 
>>> pulled in automagically by the "maven keel:maven"  goal.  This works 
>>> in a project.
>>>
>>> If you are writing a svc-* or app-* module, start with only 
>>> keel-common, keel-core and keel-container plus the custom 
>>> dependencies you need for the implementation that you are writing 
>>> (which you as the author would know).
>>>
>>> StandardLogEnabledModel lives in keel-container, I believe.
>>>
>>> HTH,
>>> Shash
>>>
>>>> Hi,
>>>>
>>>> Not knowing the keel framework that well, is there a way that I can 
>>>> find which classes are packaged into which jar file dependency? Can 
>>>> I tell this somehow from the javadoc for a keel class?
>>>>
>>>> For example, if I use the keel class StandardLogEnabledModel which 
>>>> dependency do I add to my POM?
>>>>
>>>> Thanks,
>>>> Max
>>>> http://keelframework.org/documentation.shtml
>>>> Keelgroup mailing list
>>>> [email protected]
>>>> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com 
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> http://keelframework.org/documentation.shtml
>>> Keelgroup mailing list
>>> [email protected]
>>> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>>>
>>>
>>>
>>
>> http://keelframework.org/documentation.shtml
>> Keelgroup mailing list
>> [email protected]
>> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>
>
>
>
> http://keelframework.org/documentation.shtml
> Keelgroup mailing list
> [email protected]
> http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
>
>
>

http://keelframework.org/documentation.shtml
Keelgroup mailing list
[email protected]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com