Re: [Springframework-developer] http://sourceforge.net/projects/spring-rich-c is now on-line

[Eric P. <eri...@ea...>]

Keith,

In order to be able to run the run target from the build.xml in  
spring-richclient/samples/petclinic
I had to make the following changes:

1) in <workspace>/spring-richclient/samples/petclinic/build.properties

project.package=org.springframework.rcp.samples.petclinic
into
project.package=org.springframework.richclient.samples.petclinic

AND

spring-rcp.dir=../../
into
spring-rcp.dir=../..

2) in <workspace>/spring-richclient/samples/petclinic/build.xml

     	<fileset dir="${spring-rcp.dist.dir}">
    			<include name="spring-rcp.jar"/>
     	</fileset>

into

     	<fileset dir="${spring-rcp.dist.dir}">
    			<include name="spring-richclient.jar"/>
     	</fileset>


-- Eric.


On Sat, 10 Jul 2004 03:58:57 -0400, Keith Donald <kd...@cs...>  
wrote:

> Spring Rich Client's new home is now officially on-line at
> http://sourceforge.net/projects/spring-rich-c!
>
> The module and eclipse project name is "spring-richclient".
>
> Unfortunately, sourceforge unix names are limited to 15 characters, so I
> went with "spring-rich-c" for the _internal_ project unix name.
>
> -----
> 	As an aside, I decided not to go with our familiar "spring-rcp" as
> the internal name for the following reason:
> 	- The 'rcp' acronym gets confused and often associated with
> eclipse's "rich client platform"; Spring rich client's focus is on the
> enterprise 'thick client' app space, not so much IDE-type apps.  So we  
> want
> to clearly differentiate ourselves from a platform like eclipse or  
> netbeans
> (while there is some overlap, we don't aim to compete with them; probably
> the project we are mostly closely aligned with in terms of goals/focus is
> the very new JDNC initiative launched by Sun, our main differentiator  
> being
> we're nicely integrated with the rest of Spring & follow a similar
> programming model...)
>
> -----
>
> Project distributables are prefixed with spring-richclient, for example
> spring-richclient.jar and spring-richclient-resources.jar.
>
> All code should be checked in, compiling, and ready to
> use/evolve/review/critique/play with.
>
> All project dependencies are now stored in the repository; this means  
> you no
> longer need to checkout core spring or the spring sandbox to build
> spring-richclient.
>
> I've completed the aforementioned package rename from
> "org.springframework.rcp" to "org.springframework.richclient" - again, I
> apologize for the inconvenience (thankfully this should only happen once,
> and much better to get it right now.)
>
> Keith (me), Ben, Jim, and Scott are added in as developers.  You should  
> be
> able to commit now.
>
> Good times!
>
>
>
> -------------------------------------------------------
> This SF.Net email sponsored by Black Hat Briefings & Training.
> Attend Black Hat Briefings & Training, Las Vegas July 24-29 -
> digital self defense, top technical experts, no vendor pitches,
> unmatched networking opportunities. Visit www.blackhat.com
> _______________________________________________
> Springframework-developer mailing list
> Spr...@li...
> https://lists.sourceforge.net/lists/listinfo/springframework-developer



-- 
Nothing is particulary hard if you divide it into small jobs. (Henry Ford)