Re: default build problems

I know that I installed 1.2.2 but I'll do it again in case it failed and
I didn't notice.

t

On Feb 23, 2005, at 7:12 PM, Michael Nash wrote:

> Thomas:
>
> Maybe you've done this already, but make sure you have the latest keel
> plugin: version 1.2.2
>
> You can do a maven plugin:download, then tell it artifactId
> maven-keel-plugin, groupId keel, version 1.2.2
>
> I just did a maven war here, and my war has a bunch more than it shows
> below - however, if I uninstall the Keel plugin, then my war looks
> *exactly* like yours, hence my suspicion :-)
>
> Mike
>
> On Wed, 2005-02-23 at 18:52, Thomas Duff wrote:
>>   I'm probably doing something stupid, but I can't figure it out.  I
>> started
>> with a clean slate when I switched to maven.  Everything seemed to
>> go fine.  I did the maven keel:install, no errors.  Then I changed
>> directories
>> to keel-build/example-projects/default and did maven war.  After much
>> downloading and what not, it succeeded but when I checked the war  
>> file,
>> this is all I have in it:
>>
>> (~/keel/keel-build/example-projects/default)
>> [Silver] (duff): jar tf target/default.war
>> META-INF/
>> META-INF/MANIFEST.MF
>> WEB-INF/
>> WEB-INF/classes/
>> WEB-INF/lib/
>> WEB-INF/tld/
>> WEB-INF/lib/cli-1.0.jar
>> WEB-INF/lib/comm-direct-1.0.jar
>> WEB-INF/lib/commons-beanutils-1.6.1.jar
>> WEB-INF/lib/commons-collections-3.0.jar
>> WEB-INF/lib/commons-fileupload-1.0.jar
>> WEB-INF/lib/commons-logging-1.0.4.jar
>> WEB-INF/lib/commons-validator-1.1.3.jar
>> WEB-INF/lib/concurrent-1.3.1.jar
>> WEB-INF/lib/keel-client-2.1.jar
>> WEB-INF/lib/keel-clnt-cli-1.1.jar
>> WEB-INF/lib/keel-clnt-struts-3.0.jar
>> WEB-INF/lib/keel-common-2.0.jar
>> WEB-INF/lib/oro-2.0.8.jar
>> WEB-INF/lib/struts-1.2.4.jar
>> WEB-INF/lib/xercesImpl-2.6.2.jar
>> WEB-INF/lib/xml-apis-2.0.2.jar
>> WEB-INF/lib/xmlParserAPIs-2.0.2.jar
>>
>> I got the same results yesterday, but thought it might be because  
>> things
>> were still in flux.  So today I wiped it out completely and started  
>> all
>> over
>> but got the same results.  At one point I accidently used a window  
>> that
>> still had my old KEEL_HOME variable and it built a more complete
>> war file.  Also, I'm not sure if this is supposed to be the case, but
>> the only
>> top-level directory created in $KEEL_HOME is keel-build.  None of the
>> other directories are there.  I assume that is because it is doing a
>> binary build rather than from sources....
>>
>> Any help would be greatly appreciated.  Thanks!
>>
>> tom
>> --
>> 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

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