[Smartfrog-support] Announcing SmartFrog 3.12.010
Steve Loughran <[email protected]> Fri, 09 Nov 2007 12:01:37 +0000
| Newsgroups | gmane.comp.java.smartfrog.user |
|---|---|
| Message-ID | <[email protected]> |
Hello Everyone!
I'm pleased to announce a new release of SmartFrog, release 3.12.010
https://sourceforge.net/project/showfiles.php?group_id=87384&package_id=108447&release_id=552931
The main changes are
-better diagnostics (we can detect duplicate smartfrog JARs on the
classpath)
-A new AntBuild component that can run complete Ant build files on
target machines.
The latter isn't included with any good documentation; this is still
ongoing. Keep an eye on
http://smartfrog.svn.sourceforge.net/viewvc/*checkout*/smartfrog/trunk/core/components/ant/doc/ant_readme.sxw
As usual, feedback and bugreps to Jira and the mailing list.
Have fun!
-Steve
Changes since last release
==========================
There have been no major changes to the core SmartFrog engine
or components since the last release. We have added some diagnostics;
any of the smartfrog commands can be called with the -diagnostics option,
which will print out diagnostic information about the environment
in which SmartFrog is running.
There is now an AntBuild component in the sf-ant package, defined in
/org/smartfrog/services/ant/components.sf . This component can run
an existing Ant build file inside a SmartFrog process, passing down
properties and collecting results. Output is passed to the SmartFrog log
infrastructure, and properties from the build can be turned into attributes
on a designated target component. Build failures can be configured to
terminate the component. If the AntBuild component is terminated mid-build,
a best-effort attempt will be made to interrupt the build; if that does not
halt the build within a specified timeout, termination can be forced.
This component enables you to integrate existing XML build files into
a SmartFrog managed deployment, potentially running a build file remotely.
Users are requested to provide feedback, to help improve the
functionality of
the component. We are particularly interested in improving termination,
failure
and reporting. We also have to complete the documentation for this
component -
please ask on the mailing list for the location in the subversion repository
of the latest documentation.
Release Notes - SmartFrog - Version 3.12.010
** Bug
* [SFOS-500] - Ant project properties arent remotely accessible
** Improvement
* [SFOS-525] - move resourceloader logic into core
* [SFOS-526] - move list operations into a central utils class
* [SFOS-530] - add support for a vector of file references in the
FileSystem class
* [SFOS-534] - Add a standard way to SmartFrogTask to let other
classes wait for a thread to finish
** New Feature
* [SFOS-499] - Add a component to run a specific build file
* [SFOS-536] - add ability to propagate the Ant properties to a
remote target
* [SFOS-537] - Add version information to SmartFrogException
* [SFOS-538] - Add diagnostics check for repeated jar file names in
classpath.
** Task
* [SFOS-497] - async Ant execution needs tests
* [SFOS-521] - Automated way to update avlEventServer in
sfinstaller.vm template file
** Sub-task
* [SFOS-522] - Add new API to sfinstaller component to read the
xmpp servername
and generate description.
--
-----------------------
Hewlett-Packard Limited
Registered Office: Cain Road, Bracknell, Berks RG12 1HN
Registered No: 690597 England
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems? Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >> http://get.splunk.com/
_______________________________________________
Smartfrog-support mailing list
Smartfrog-support-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org
https://lists.sourceforge.net/lists/listinfo/smartfrog-support
release_3.12.010.html
(text/html, 9 KB)
<html>
<head>
<title>SmartFrog 3.12.010</title>
</head>
<body>
<h1>SmartFrog 3.12.010</h1>
<p>
This is a new release of SmartFrog, the Java-based, LPGL-licensed distributed
deployment framework developed by HP Laboratories. SmartFrog enables
applications to be deployed across multiple machines, configuring different
aspects of the system so that they are all consistently configured, and managing
the life-cycle of the application as a whole. The project's home page is
<a href="http://smartfrog.org/">http://smartfrog.org/</a>
</p>
<p>
The release artifacts are available on
<a
href="https://sourceforge.net/project/showfiles.php?group_id=87384&package_id=108447&release_id=552931">
SourceForge</a>
</p>
<p>
This release is 3.12.010; built from revision 5471
of the SVN repository. This release has an extended language
with the ability to tag attributes, and includes the following items:
</p>
<ul>
<li> Core smartfrog daemon, including services to manage files, start and stop
Java and native programs.
</li>
<li> Example components and applications.
</li>
<li> Ant support: ant tasks to deploy and terminate applications from a build,
</li>
<li> Ant components: the ability to execute ant tasks in a deployment,
and run complete Ant XML build files on local or remote systems.
</li>
<li> Anubis: a partition aware tuple-space that can be used to implement fault
tolerant systems.
</li>
<li> Database: components to issue database commands, and deploy HSLDB and MySQL.
</li>
<li> JMX: the ability to configure and manage JMX components, and to manage
SmartFrog components over JMX.
</li>
<li> Logging: integration with Apache commons-logging and Log4J
</li>
<li> Networking: email, FTP, SSH, DNS support.
</li>
<li> Quartz: scheduled operations using Quartz libraries.
</li>
<li> Scripting: support for BSF-hosted scripting languages
</li>
<li> Testing: Distributed JUnit and component testing with SFUnit.
</li>
<li> WWW: deployment of WAR and EAR files to application servers. deploy-by-copy
is provided for all application servers that support, and a tomcat-specific
component can communicate with Apache Tomcat. The Jetty component can
configure and deploy individual servlets, eliminating much of the need for WAR
files themselves.
</li>
<li> XML: XML support with XOM.
</li>
<li> XMPP: Presence and messaging over Jabber.
</li>
</ul>
<h3>Packaging</h3>
<p>
This release is available as:
</p>
<ol>
<li> RPM files inside a .tar.gz file.
</li>
<li> a JAR installer.
</li>
<li>the original core smartfrog distribution as .zip and .tar.gz (deprecated)
</li>
</ol>
<p>
The RPM installation is for RPM-based Linux systems. It comprises three RPM
files, smartfrog, smartfrog-daemon and smartfrog-demo:
</p>
<table>
<tr>
<td><code>smartfrog</code></td>
<td>The core SmartFrog distribution.</td>
</tr>
<tr>
<td><code>smartfrog-daemon</code></td>
<td>The shell scripts to add the smartfrog distribution to the
path, and to run the daemon on start-up.
</td>
</tr>
<tr>
<td><code>smartfrog-demo</code></td>
<td>Example code and documentation</td>
</tr>
<tr>
<td><code>smartfrog-anubis</code></td>
<td>Anubis partition-aware "tuple space"</td>
</tr>
<tr>
<td><code>smartfrog-logging</code></td>
<td>Enhanced logging</td>
</tr>
</table>
<p>
All the JAR files are also published to a repository that is compatible with
Apache Maven and Ivy. Add
<a
href="http://smartfrog.sourceforge.net/repository">http://smartfrog.sourceforge.net/repository</a>
to your repository list to pull SmartFrog artifacts into your Ivy- or Maven- based build.
</p>
<p>
There are also SmartFrog components to retrieve artifacts from such a repository
(the Library components under /org/smartfrog/services/os/java/library.sf ),
which can be used for dynamic download of SmartFrog and other artifacts.
</p>
<h3>Security warning</h3>
<p>
Unless SmartFrog is configured with security, a running daemon
will listen on its configured port for incoming deployment requests, and deploy
the applications with the rights of the user running the daemon. When the
smartfrog-daemon RPM is installed, that means that a process running as root
will be listening on an open port for incoming deployment requests. Do not
deploy SmartFrog this way on any untrusted network, not without turning security
on and, ideally, recreating the RPMs with signed JAR files.
</p>
<h3>Building SmartFrog</h3>
<p>
SmartFrog requires Java 1.5 and Ant 1.7 to build.
</p>
<p>
The distribution does not include a source tree adequate to build the entire
system. Please follow the instructions at
<a href="http://sourceforge.net/svn/?group_id=87384">http://sourceforge.net/svn/?group_id=87384
</a>
and check out smartfrog/trunk/core from our repository.
</p>
<p>
This release was built with revision 5471 of the repository, which
is available under the SVN branch
<a href="https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.12.010">https://smartfrog.svn.sourceforge.net/svnroot/smartfrog/tags/release3.12.010</a>
</p>
<p>
We strongly encourage anyone interested in building or extending smartfrog to
get involved in the smartfrog developer mailing list, which can be found from
the sourceforge project page
<a href="http://sourceforge.net/projects/smartfrog/">
http://sourceforge.net/projects/smartfrog/</a>
</p>
<h3>Reporting Bugs</h3>
<p>
Please file all bug reports at <a
href="http://jira.smartfrog.org/">http://jira.smartfrog.org/</a>
</p>
<p>
The SmartFrog Team
</p>
<h3>Changes since last release</h3>
<p>
There have been no major changes to the core SmartFrog engine
or components since the last release. We have added some diagnostics;
any of the smartfrog commands can be called with the -diagnostics option,
which will print out diagnostic information about the environment
in which SmartFrog is running.
</p>
<p>
There is now an AntBuild component in the sf-ant package, defined in
/org/smartfrog/services/ant/components.sf . This component can run
an existing Ant build file inside a SmartFrog process, passing down
properties and collecting results. Output is passed to the SmartFrog log
infrastructure, and properties from the build can be turned into attributes
on a designated target component. Build failures can be configured to
terminate the component. If the AntBuild component is terminated mid-build,
a best-effort attempt will be made to interrupt the build; if that does not
halt the build within a specified timeout, termination can be forced.
</p>
<p>
This component enables you to integrate existing XML build files into
a SmartFrog managed deployment, potentially running a build file remotely.
Users are requested to provide feedback, to help improve the functionality of
the component. We are particularly interested in improving termination, failure
and reporting. We also have to complete the documentation for this component -
please ask on the mailing list for the location in the subversion repository
of the latest documentation.
</p>
<h3> Bug
</h3>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-500'>SFOS-500</a>] - Ant project properties arent remotely accessible
</li>
</ul>
<h3> Improvement
</h3>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-525'>SFOS-525</a>] - move resourceloader logic into core
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-526'>SFOS-526</a>] - move list operations into a central utils class
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-530'>SFOS-530</a>] - add support for a vector of file references in the FileSystem class
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-534'>SFOS-534</a>] - Add a standard way to SmartFrogTask to let other classes wait for a thread to finish
</li>
</ul>
<h3> New Feature
</h3>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-499'>SFOS-499</a>] - Add a component to run a specific build file
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-536'>SFOS-536</a>] - add ability to propagate the Ant properties to a remote target
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-537'>SFOS-537</a>] - Add version information to SmartFrogException
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-538'>SFOS-538</a>] - Add diagnostics check for repeated jar file names in classpath.
</li>
</ul>
<h3> Task
</h3>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-497'>SFOS-497</a>] - async Ant execution needs tests
</li>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-521'>SFOS-521</a>] - Automated way to update avlEventServer in sfinstaller.vm template file
</li>
</ul>
<h3> Sub-task
</h3>
<ul>
<li>[<a href='http://jira.smartfrog.org/jira/browse/SFOS-522'>SFOS-522</a>] - Add new API to sfinstaller component to read the xmpp servername and generate description.
</li>
</ul>
</body>
</html>