I'm submitting this fasttrack for Petr Slechta, with a timeout of
08/25/2008.
Requested release binding is Minor.
Man pages are located in the case directory.
-Dan
Subject: Integrate Grails into Solaris [PSARC/2008/530 FastTrack timeout
08/25/
2008]
To: PSARC-ext at Sun.Com
Cc: Petr.Slechta at Sun.COM, Mary.Artibee at Sun.COM
Bcc: one-pager-list at sac.sfbay one-pager-log at sac.sfbay sac-bar at
sac.sfbay
Template Version: @(#)sac_nextcase 1.66 04/17/08 SMI
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Integrate Grails into Solaris
1.2. Name of Document Author/Supplier:
Author: Petr Slechta
1.3 Date of This Document:
18 August, 2008
4. Technical Description
This information is Copyright 2008 Sun Microsystems
1. Introduction
1.1. Project/Component Working Name:
Integrate Grails into Solaris
1.2. Name of Document Author/Supplier:
Author: Petr Slechta
1.3 Date of This Document:
2008-08-07
This project proposes to add the Grails framework[1] to the SFW
consolidation
for delivery on OpenSolaris.
2. Details
2.1 Background and motivation
Grails is a dynamic web application framework built on Java and Groovy,
leveraging best of breed APIs from the Java EE sphere including Spring,
Hibernate and SiteMesh. Grails brings to Java and Groovy developers
the joys of convention-based rapid development while allowing them
to leverage their existing knowledge and capitalize on the proven
and performant APIs Java developers have been using for years.
Since the release of Grails 1.0, Grails has been downloaded a staggering
186000 times averaging out to around 50000 times per month putting it up
there
with the most popular open source Java projects.
The plug-in community has grown rapidly with over 70 plug-ins being
developed
that add new features from security to RIA to web services.
Grails is mature and popular. NetBeans IDE[6] implements support
for Groovy and for Grails, so porting this into OpenSolaris may help also
with adoption of NetBeans IDE.
One of OpenSolaris[2][3] targets is to support software development
on Solaris OS. Grails will supplement the set of development tools for
OpenSola
ris.
The most recent version of Grails at the time of this writing is 1.0.3.
The product was last updated by the community on 2008-06-06. The project
and the community are active; the releases are irregular.
Typical development cycle is: (a) create the project ("grails create-app"
creates the complete directory structure for Grails project),
(b) develop the application by modification of files in project directory,
(c) run the project ("grails run-app" runs the application in embedded
Jetty we
b server),
(d) debug the project ("grails-debug run-app" runs the application and
allows t
he debuger
to be connected), (e) build the procution version ("grails war" produces
the wa
r file
that can be deployed under the production web server (Glassfish, Tomcat,
or oth
er)).
3. Interface table
3.1 Exported Interfaces
NAME STABILITY NOTES
SUNWgrails committed package name
/usr/bin/grails uncommitted startup script
/usr/bin/grails-debug uncommitted startup script
/usr/grails uncommitted root directory for Grails
installatio
ns
/usr/grails/[version]
(e.g. /usr/grails/1.0.3) uncommitted root directory of one Grails
installa
tion
GRAILS_HOME uncommitted environment variable
3.2 Imported Interfaces
NAME STABILITY NOTES
JAVA_HOME committed environment variable (widely used)
Grails require Java 1.4 or later.
4. Documentation
Simple manual pages were created to document the basic functionality of
Grails'
CLI
(grails and grails-debug commands). More help is available via Grails' CLI.
The manual pages for Grails are installed in /usr/share/man/man1.
Grails installation comes with HTML documentation (directory
/usr/grails/[version]/doc). The other sources of documentation are
Grails web pages[1] and books "Getting Started with Grails"[4] and
"The Definitive Guide to Grails"[5].
5. References
[1] http://grails.org/
[2] http://opensolaris.com
[3] http://opensolaris.org
[4] http://www.infoq.com/minibooks/grails
[5] http://www.apress.com/book/view/1590597583
[6] http://www.netbeans.org
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
sfw
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
6. Resources and Schedule
6.4. Steering Committee requested information
6.4.1. Consolidation C-team Name:
sfw
6.5. ARC review type: FastTrack
6.6. ARC Exposure: open
