Ahhh, the sweet smell of new project growing pains!

--- Pete Carapetyan <[EMAIL PROTECTED]> wrote:
> Doug:
> 
> Addressing your concerns separately
> 1. Special Redkeel plugin dependencies
> 2. General practices regarding coding etiquette and
> standards
> 3. General problems relating to crosscutting needs
> of tools
> 
> 1. Experimenting so far with my own plugin
> development, I am discovering 
> that it works fine on just about everything beyond
> 2.0x. So I think that 
> the only real bugger we are going to have is the
> draw2d stuff (GEF?) 
> which redkeel uses. This is not about us, everyone
> that uses GEF will 
> have this problem. I bet it will be resolved
> sometime soon, just because 
> everyone else is having the same problem.
> 2. As regards the etiquette of doing the right
> thing, it was hell making 
> myself test my plugin on other eclipse versions. But
> what was 
> embarrassing is that after resisting for weeks, it
> only took a few 
> minutes of my time. So maybe we should keep
> 'encouraging' other in this 
> direction, and I bet the problems won't be so bad.
> 3. You mention below lots of 'crosscutting' concerns
> as we all need to 
> have stuff that works in each of these environments,
> and yet each has 
> different sytles and syntax. Again there are
> solutions for mitigating 
> these problems, but it may take quite a bit of
> 'encouragement'.
> Just look at all the crosscutting ways that a build
> must work
> - ant
> - eclipse
> - command line
> - cruise control
> - maven
> - within the plugin
> - unplugged from cvs
> - plugged into cvs
> - unplugged from net
> - etc, etc
> 
> Let's just try to keep our eye on the ball and keep
> swinging. If we 
> don't give up, we can probably make it all work
> together.
> 
> 
> Doug Warren wrote:
> 
> >I needed to make several library changes for
> tool-redkeel in order to run on
> >Eclipse 2.1.2.  Currently, tool-redkeel has
> hard-coded references to Eclipse
> >2.1.1 plugin paths (most of which I changed I had
> to change).  Also, I
> >changed hard-coded JAR reference for JDOM from
> D:\java\jdom-9\build\jdom.jar
> >to a JDOM_HOME variable (which on my system has
> c:\java\jdom-b9) with
> >extension for \build\jdom.jar.
> >
> >I did not commmit my changes because I thought it
> would be better that Jeff
> >make any changes to the RedKeel tool.  However, I
> think it would desirable
> >for us to use a common base for Eclipse plugins for
> Keel, if possible.
> >Currently, that would be Eclipse 2.1.2, so
> hopefully Jeff might consider
> >upgrading from Eclipse 2.1.1. to 2.1.2.
> >
> >We need to exploit Eclipse path variables and
> project redependencies.  Also,
> >it would probably be worthwhile to align Eclipse
> variables with ANT
> >properties, where possible, so we achieve some
> consistency between Eclipse
> >and ANT capabilities for common dependencies. 
> Also, we might incorporate
> >such variables/properties in the Keel preferences
> and configuration plugins
> >that Pete is working on.
> >
> >We also need to figure out the best way to address
> path evolution related to
> >dependencies since many JAR files, and now Eclipse
> plugins, have explicit
> >versions in path names.  For example, when some
> developers want to move from
> >Eclipse 2.1.1 to Eclipse 2.1.2 , currently each
> develop would have to make
> >local changes to library paths in many Keel
> projects to get Keel working
> >again.  Perhaps, we need a capability in Pete's
> configuration plugin to
> >"customize" (configure) for the developer's
> environment based on Keel
> >preferences, which are mapped to Eclipse variables
> and ANT properties.
> >
> >Doug Warren
> >
> >
> >
> >http://keelframework.org/documentation
> >Keelgroup mailing list
> >[EMAIL PROTECTED]
>
>http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com
> >
> >  
> >
> 
> 
> 
> http://keelframework.org/documentation
> Keelgroup mailing list
> [EMAIL PROTECTED]
>
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com


__________________________________
Do you Yahoo!?
Yahoo! Hotjobs: Enter the "Signing Bonus" Sweepstakes
http://hotjobs.sweepstakes.yahoo.com/signingbonus
http://keelframework.org/documentation
Keelgroup mailing list
[EMAIL PROTECTED]
http://lists.keelframework.com/listinfo.cgi/keelgroup-keelframework.com

Reply via email to