Re: Dependencies

Thomas:

I'd start by selecting the services you want to use, for example:

If you're going to be bundling client and server in one app or webapp,
choose "comm-direct".

If you're going to want to talk to databases, select
"svc-persist-default".

If you need login/registration capabilities, "app-register".

Then you do your "maven keel:maven", and it will resolve all other
dependencies for you, pulling in everything else it needs to complete an
application.

I have a significant patch/upgrade for the build system being checked in
tonight, FYI - but it doesn't affect how the above works.

HTH!

Mike

On Tue, 2005-03-01 at 15:17, Thomas Duff wrote:
> I know in one of his recent posts Mike said that we don't
> need nearly as many dependencies now with the maven
> build system.  I'm assuming that is because it picks up the
> whole dependency hierarchy.  Anyone have any advice on
> what SHOULD be in the dependencies for a new project?
> Thanks!
> 
> t
> --
> Thomas Duff / [email protected]
> Principal Software Engineer / Global Crossing
> 
> 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