Re: Maven: cannot run keel:maven

Mike,

Not that I didn't already ask a bunch of questions, I forgot one 
though.  I did two successive "maven war" runs, without changing any 
source, and each time it took roughly 5 minutes to go through the goal.  
I am sure there is a faster edit/build/debug cycle, question is what is 
it.  Maybe I shouldn't be using the war method, but instead use an 
expanded webapp directory?  I tried "maven webapp"  (and even "maven 
keel:webapp"), as it says in the doc., but Maven says "goal doesn't 
exist in project".  Also, if we do this, Tomcat requires manual 
configuration, right, unlike the Ant build system which used to take 
care of this?

Shash

Sasvata (Shash) Chatterjee wrote:

> Mike,
>
>>> ent ahead and checked out keel-build form CVS, which does have 
>>> module map.properties, and was able to do a "maven war".  Hoever, 
>>> default.war only has JAR files in WEB-INF/lib, but nothing else.  
>>> Just FYI.
>>>
>>> Maybe you can try defining a brand-new/different KEEL_HOME with 
>>> nothing in it, and see if it works for you?
>>>   
>>
>>
>> I'm doing some tests today installing from scratch on a "bare" machine,
>> so I'll be trying this several times, and no doubt will trip over it and
>> a few others :-)
>>
> I have the latest tool-maven (3.0) built from CVS and installed in 
> local Maven repo.  Same with the Keel Maven plugin, got 1.2.3 (what is 
> in CVS).  I did a plugin:install, and "maven -i" shows the correct 
> version.
> BTW, how do I build the keel-build JAR?
>
> When I run "maven keel:maven" it complains about the POM for 
> comm-jms-1.0 missing from the Keel remote repo.  Also, the comm-jms 
> module in CVS is empty, so I couldn't generate it locally, either.
>
> So, I ran "maven war" from my project directory. It built 
> default-1.0.war and default-1.0-uber.jar.  How do I run the Keel 
> webapp?  Putting default.war in Tomcat's webapp directory is what I 
> did, but it doesn't expand any of the JSPs. etc.  I noticed that 
> default.war includes default-1.0-uber.jar in WEB-INF/lib, and in it 
> are all the JSPs, XSLs, etc.....how are we supposed to use this 
> bundling scheme?
>
> I know you said that some of the comm-*  modules need to be split-up 
> further, but as it is, is Keel runnable when built with Maven?
>
> 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
> - Any dependency marked with a  "<war.bundle>true</war.bundle>" 
> property will *also* be copied to WEB-INF/lib.
> - What is the function of the  "<keel.server>true</keel.server>" 
> property?
> - Is there a way to specify that a JAR is *only* for the client side?
> - I think the resources definition in project.xml is used to copy 
> stuff to the webapp.  Generically, how and where do I put stuff in a 
> particular (custom) module that I want copied over to the root 
> directory of the webapp?
> - A suggestion:  now would be a good time to move away from "magic" 
> mappings in our build system.  For instance, we have src/jsp/struts 
> for Struts stuff,src/xsl/cocoon for Cocoon, src/vm/velocity Velocity, 
> etc.  which get mapped into the webapp root.  Instead, we could just 
> have a src/webapp or webroot, or whatever that would be the place to 
> put UI files for all apps, and not have the build system know about 
> specific dirs for specific types of clients.  The module author could 
> still group files by client if they so chose, just the build system 
> wouldn't know or care.  This would work much better with the various 
> WEB/J2EE IDE plugins also, for instance the Eclipse J2EE plugin puts 
> the web root files in <project>/WebContent.  If we did this, what we 
> have now would need some edits to work, but it would be relatively 
> easy to do.
>
> Shash
>
>
> 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