Re: Maven: cannot run keel:maven

Shash:

> You are right, it is default.war....I  have been looking at the Maven 
> repo too long :-).

I know what you mean - I start to see version numbers on everything
after a while :-)

> Oh...what I'd give to be there :-).  I guess something different between 
> yours and the CVS version.

I've been fixing a lot of things, and getting further behind on
checkins, sorry! Catching up this morning as best I can.

> >>Also, could you please summarize how the Maven build system 
> >>(project.xml) needs to be configured to tell what pieces of a module go 
> >>to the client and server sides?  As I understand it:
> >>- Any and all dependency JARs will go to the Keel-sever side

One other item here: I used to be using the module-properties.properties
to determine which Keel module was client side, etc. Then I realized you
can put a "properties" section in the POM. The latest MavenTool doesn't
rely on the .properties files in keel-build at all anymore. If you check
various POM's, you'll see the properties are in there.

> OK...got it.  by default, dependency is server-side.  You specify 
> keel.client to put it on the client side.  keel.client and keel.server 
> both to put it in server as well as client.

I believe that's it, yes. I really need to get all this written down -
as soon as I'm sure it works 100%, which from your report, it isn't yet!

> >Yes, I agree - simple is good! But how to avoid copying the unnecessary
> >files? Or do we care?
> >
> >  
> >
> You are right, copying unused files would be the downside.  My own 
> feeling is "don't care".  For the Keel modules, we need to package *all* 
> the UI files in the JAR anyway, since we can't tell which client user is 
> going to choose.  For users' own files, most likely they will stick to 
> one type of client anyway.   But I think  the overall simplicity  and 
> the  generality of the layout for all clients would be a big benefit, 
> and this would be a small price to pay. 

I agree. I suggest we use src/webapp, as that's the Maven default place
for webapp files to "live". CAVEAT: If in the project you actually build
the "war" from you put stuff in src/webapp, it will get toasted as part
of the build process, as that's where the stuff extracted out of the
jars gets copied. So don't do a "maven war" or a "maven war:webapp" in a
module directory!

I'll give this a try here, if it's clean I'll go ahead & check in.
Should reduce confusion even further, which is always a good thing!

Mike


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