Re: Update Documentation: Including install procedure

Mike,

I went through a whole bunch of projects, making POMs as needed and 
working on generating Eclipse .classpath/.poject, deleting JARs from lib 
dirs, etc.  I am in the process of checking in, but it is very slow 
here...so will probably continue tomorrow.  CVS might be in a bit of 
flux for a bit....but we'll get that much closer to sing Maven for all 
modules.

Shash

Sasvata (Shash) Chatterjee wrote:

> Mike and Keelers!
>
> Ni Hao (You well?) from a fish out of water in Shanghai, China!!!!  
> Any Keelers here?
>
> I have been running into this same problem for over a week now, but 
> thought something was wrong with my environment.  I chased it down 
> this morning.
>
> Looks like keel-client-struts-3.0.jar includes a project.xml that 
> refers to keel-client 2.0 (latest is 2.1).  There are several other 
> project.xml(s) that refer to keel-client 2.0.   These JARs need to be 
> rebuilt and uploaded to the Keel Maven repo.  Since we are not using 
> SNAPSHOT versions right now, after that folks need to delete the Keel 
> JARs from their local Maven repo, and redownload them.
>
> Also, several of the ant.properties has the version of the module 
> different that the version in project.xml.  For instance, 
> client-struts has 2.0 in ant.properties, but 3.0 in project.xml...I 
> thought the ant.properties/project.xml were interlinked?  In any case, 
> I could not build client-struts, got a compile error on "KeelJmsC
> lient").  Looks like time for you to do a sync with CVS (assuming you 
> are able to build)  :-)
>
> I figured this out by running MavenTool in Eclipse.  A few questions, 
> Mike:
> - Looks like in tool-maven, the file/class is KeelMavenTool.  But in 
> the Maven plugin dir, it is MavenTool....what the....?
> - The checked in KeelMavenTool still refers to the maven repo as 
> hard-coded "keel-build/repository".  But looks like the version in 
> 1.2.0 of the plugin doesn't behave that way.  Do you just need to 
> check in the latest code?
> - KeelMavenTool has System.err.println messages, which did show up 
> when run under Eclipse, and was enough to track down the problem.  
> When run under Maven, Maven seems to be suppressing the stream....is 
> there a way to enable printing of System.err under Maven?
>
> Shash
>
> Michael Nash wrote:
>
>> Max:
>>
>> Are you on Maven 1.0.2? (Do a "maven -v" to see). 1.0 had a bug with
>> plugin dependencies, as far as I can see, which does exactly the below.
>>
>> Mike
>>
>> On Mon, 2005-02-21 at 13:51, Max wrote:
>>  
>>
>>> Hi Mike,
>>>
>>> I just did a fresh cvs check out of keel-build and tried your new 
>>> documented instructions. The plugin installs fine but when 
>>> performing a maven keel:maven in the example-projects/default I get 
>>> the following error:
>>>
>>> keel:maven:
>>> keel:check-environment:
>>>
>>>    [java] java.lang.IllegalArgumentException: Indirect reference to 
>>> keel-client-2.0, but this file not downloaded.
>>>    [java]      at KeelMavenTool.addDependencies(KeelMavenTool.java:510)
>>>    [java]      at 
>>> KeelMavenTool.addDependenciesFromJar(KeelMavenTool.java:389)
>>>    [java]      at KeelMavenTool.run(KeelMavenTool.java:259)
>>>    [java]      at KeelMavenTool.main(KeelMavenTool.java:86)
>>>
>>> BUILD FAILED
>>> File...... C:\Documents and 
>>> Settings\Franz\.maven\cache\maven-keel-plugin-1.2.0\plugin.jelly
>>> Element... java
>>> Line...... 144
>>> Column.... 58
>>> Java returned: 1
>>> Total time: 15 seconds
>>>
>>>   
>>
>
>
> 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