Skip to content
forked from cbeams/distyles

A tour of Spring 3 dependency injection styles, as delivered at Paris SUG, June 2010 and for Spring DI styles webinar

Notifications You must be signed in to change notification settings

romcab/distyles

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

30 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

----------------------------------------------------------
Spring DI Styles webinar companion project
----------------------------------------------------------


Introduction
------------

This project uses Git for source control (http://git-scm.com), and is hosted
at GitHub (http://github.com/cbeams/distyles).

To clone (check out) the project:

    git clone git://github.com/cbeams/distyles.git

If you don't have git installed, and would like a zip or tar of the sources:

    http://github.com/cbeams/distyles/archives/master


This project is built using Gradle (http://gradle.org).

To execute build system tasks, simply run the 'gradle wrapper' script
appropriate to your platform.  You'll notice these scripts are available in the
root of this project, meaning there is nothing for you to download or install.

    For Windows:  `gradlew.bat`
    For OSX/*nix: `gradlew`

The remainder of this document will simply refer these scripts as 'gradlew'.


Discover available tasks:
-------------------------

    gradlew --tasks
        or
    gradlew -t


Build the project:
------------------

    gradlew build

Note that 'build' includes compilation, testing, and packaging. For Maven users,
`gradlew build` is roughly equivalent to `mvn package`.

Of course, the first time you execute this task, Gradle will download all
project dependencies.


Import the project into Eclipse/STS:
------------------------------------

    gradlew eclipse

to update .classpath file with paths to the dependency jars you just downloaded
(note that .project and .springBeans files already exist).  This command will
also retrive and link dependency source jars. After this is complete, you can
import the project as follows:

    File->Import->Existing Projects Into Workspace

If using STS (http://www.springsource.com/developer/sts), you'll be glad to know
that the Spring Project Nature has already been applied for you in the .project
file, so you should have complete tooling for the Spring XML files in the
project without any extra steps.


Import the project into IntellJ IDEA:
-------------------------------------

    gradlew idea

to create .iml, .ipr, and .iws files


Run the TransferScript main():
------------------------------

    gradlew runTransferScript

About

A tour of Spring 3 dependency injection styles, as delivered at Paris SUG, June 2010 and for Spring DI styles webinar

Resources

Stars

Watchers

Forks

Packages

No packages published