Apache HTTP Server

Call for Participation ApacheCon North America 2011 7-11 November 2011 Westin Bayshore, Vancouver, Canada All submissions must be received by Friday, 29 April 2011 at midnight Pacific Time. ApacheCon, the official conference ... [More] , trainings, and expo of The Apache Software Foundation (ASF), heads to Vancouver, Canada, this November, with dozens of technical, business, and community-focused sessions for beginner, intermediate, and expert audiences. Now in its 11th year, the ASF develops and shepherds nearly 150 Top-Level Projects and new initiatives in the Apache Incubator and Labs. With hundreds of thousands of applications deploying ASF products and code contributions by more than 2,500 Committers from around the world, the Apache community is recognized as among the most robust, successful, and respected in Open Source. This year's ApacheCon focuses on highly-relevant, professionally-directed presentations that demonstrate specific problems and real-world solutions. We welcome proposals --from developers and users alike-- in the areas of "Apache and ...": ... Enterprise Solutions (from ActiveMQ to Axis2 to ServiceMix, OFBiz to Chemistry, the gang's all here!) ... Cloud Computing (Hadoop, Cassandra, HBase, CouchDB, and friends) ... Emerging Technologies + Innovation (Incubating projects such as Libcloud, Stonehenge, and Wookie) ... Community Leadership (mentoring and meritocracy, GSoC and related initiatives) ... Data Handling, Search + Analytics (Lucene, Solr, Mahout, OODT, Hive and friends) ... Pervasive Computing (Felix/OSGi, Tomcat, MyFaces Trinidad, and friends) ... Servers, Infrastructure + Tools (HTTP Server, SpamAssassin, Geronimo, Sling, Wicket and friends) Submissions are open to anyone with relevant expertise: ASF affiliation is not required to present at, attend, or otherwise participate in ApacheCon. Whilst we encourage submissions that the highlight the use of specific Apache solutions, we are unable to accept marketing/commercially-oriented presentations. Other proposals, such as panels, have been considered in the past; you are welcome to submit an alternate presentation, however, such sessions are accepted under exceptional circumstances. Please be as descriptive as possible, including names/bios of proposed panelists and any related details. Accepted speakers (not co-presenters) qualify for general conference admission and a minimum of two nights lodging at the conference hotel. Additional hotel nights and travel assistance are possible, depending on the number of presentations given and type of assistance needed. To submit a presentation proposal, please complete our ONLINE SUBMISSION FORM at http://na11.apachecon.com/proposals/new To be considered, proposals must be received by Friday, 29 April 2011 at midnight Pacific Time. Please email any questions regarding proposal submissions to cfp AT apachecon DOT com. Key Dates: 3 March 2011 - CFP Opens 29 April 2011 - CFP Closes 20 May-30 June 2011 - Speaker Notifications and Confirmations 7-11 November 2011 - ApacheCon NA 2011 We look forward to seeing you in Vancouver! – The ApacheCon Planning team [Less]

We are pleased to announce the 2nd Apache Retreat at Knockree in Ireland, running 13th-16th May. As part of this event, we're running a BarCamp un-conference, and we'd love for members of the Apache community at-large to join us on Saturday 14th May. ... [More] For Apache code committers: we're hoping you'll be able to join us for the whole weekend; please see the website for details on the programme for those attending the full event. For Apache software users/developers/enthusiasts: we'd love for you to come along in the day on the Saturday. We're running a BarCamp in the day, and it'll be great chance to learn more about new Apache projects, how the Apache Way leads us to develop software, as well as to talk about your current projects. More details on the event, transport details, and a link to the signup site are available from:    https://sites.google.com/site/apacheretreatknockree/ We're looking forward to seeing as many of you as possible at the BarCamp in May! -- The Apache Retreat planning team [Less]

In the near future the Infrastructure team will be implementing a change to the way we handle emails for all committers. Historically we have allowed users to choose how to handle their apache.org email. However we will be making the following ... [More] changes: Making LDAP authoritative for all mail forwarding addresses. Users will no longer be allowed to store their apache.org email locally on people.apache.org (minotaur) The Infra team will take the mail address currently held in either your .qmail or .forward file (.qmail is authoritative if they both exist) and inject this into LDAP We will no longer allow users to configure mail filtering, but you can configure your SpamAssassin threshold as per our recent blog post. We will make committers ~/.forward and ~/.qmail files read-only, there will still be at least one of these files, but it will be owned by the mail daemon user. This means that all committers will be required to forward their apache.org email to an email address outside of the foundation. We are doing this to simplify the email infrastructure, and to help reduce the current level of complexity of maintaining people.apache.org. Also, making LDAP authoritative means we can move some of the work straight out to the MXs, and thus avoid sending it through several mail servers. In the new architecture if someone emails you directly at your apache.org mail address it will only be handled by one apache.org MX. Of course, we wont delete any email you currently have on people.apache.org. Should you want to edit your LDAP record you should use https://id.apache.org to do this. [Less]

Open Source implementation of the CMIS standard widely used in Enterprise Content Management solutions, such as Adobe, Alfresco, Nuxeo, OpenText, SAP, and more. Forest Hill, MD – 23 February 2011 – The Apache Software Foundation (ASF), the ... [More] all-volunteer developers, stewards, and incubators of nearly 150 Open Source projects and initiatives, today announced that Apache Chemistry has graduated from the Apache Incubator as a Top-Level Project (TLP). This signifies that the Apache Chemistry community and products have been well-governed under the ASF's meritocratic, consensus-driven process and principles. Apache Chemistry is an Open Source implementation of the OASIS CMIS (Content Management Interoperability Services) standard. The project provides an interoperable API to CMIS repositories such as Alfresco, EMC Documentum, IBM FileNet, Microsoft SharePoint, Nuxeo, OpenText Enterprise Library Services, and other CMIS-compliant content repositories. It also provides libraries to build CMIS-compliant repository connectors. "Apache Chemistry is successfully driving adoption of the CMIS standard," said Apache Chemistry Vice President Florian Müller. "An Apache Open Source implementation of CMIS is ideal for growing a developer community around the standard, which will improve interoperability, create new tools, and foster innovation." Originally submitted to the Apache Incubator in May 2009 as a single, Java-focused project, Apache Chemistry today comprises the following sub-projects: OpenCMIS – CMIS client and server libraries for Java, as well as test tools for content repository developers and client application developers. Version 0.2 was released in January 2011; cmislib – CMIS client library for Python. Version 0.4 was released in February 2011; phpclient – CMIS client library for PHP. Already used in production, the sub-project’s first release will be made in the near future; DotCMIS – CMIS client library for .NET.  Contributed to the Apache Chemistry project in January 2011; work is underway on its initial release. Apache Chemistry is widely used in enterprise content management solutions and for CMIS implementation verification. Its flagship sub-project, OpenCMIS, is deployed in both Open Source and commercial products and solutions by Adobe, Alfresco, Metaversant, Nuxeo, OpenText, OpenWGA, and SAP, among others. "Nuxeo is very happy to see Apache Chemistry finalize its incubation phase and move forward to become a top-level Apache project", said Florent Guillaume, Director of R&D at Nuxeo. "We have supported Chemistry from the start, and we are so confident in the technology that we have included it as a core connector for the Nuxeo Enterprise Platform. Through Chemistry, many software platforms, such as Java, Python, PHP, and .NET, will be able to adopt the CMIS specification, which benefits both servers storing content documents or other assets, and the applications interacting with them." "CMIS is here, it works and it works well," said Nathan McMinn, Software Engineer at Ansell. "Having a standard interface to our content repositories makes integrating Ansell's various CMS systems with our applications much simpler. While the server support for the standard is of course essential, it is of limited value without stable client libraries. Sure, we could write our own client interface to CMIS, but with a project like Apache Chemistry there is no need. Chemistry gives us the tools we need to connect most of our major platforms (based on PHP, Python and Java) to our existing content stores, saving us time, money and headaches in the process." Supporting Standards Drives Industry Adoption Many Apache Chemistry code committers are also members of the OASIS CMIS Technical Committee. The project is community-driven, allowing for greater transparency and direct feedback during the definition and improvement process of future CMIS specifications. Two OpenCMIS sandbox projects are currently being used to implement and test new CMIS 1.1 features. "As a supporter for open source and open standards, Alfresco is pleased to have contributed resources to the Apache Chemistry project and to see it pass through the incubation phase," said John Newton, CTO and Chairman at Alfresco. "Alfresco was instrumental in driving the CMIS standard from its inception. The Apache Chemistry project will drive wider adoption of CMIS and allow developers to build new social content management applications leveraging the Alfresco open source platform." "The big benefit of CMIS for customers is that it lets them do more with content no matter where it's located across the enterprise," said Richard Anstey, Vice President of Product Management at OpenText. "With the graduation of Apache Chemistry to the top level, a number of barriers to broader CMIS adoption are being removed. This will help ensure that customers derive maximum benefit from their investment in the OpenText ECM Suite 2010, which offers CMIS support for server-to-server and server-to-client interoperability." "SAP envisions the usage of OpenCMIS as a base technology in the SAP NetWeaver® platform," said Björn Goerke, senior vice president, Technology and Innovation Platform Core, SAP. "The OASIS specification, which has been developed through co-innovation efforts, is driving forward standardization, through which our customers will be able to gain more from their existing content management systems with SAP® applications." "Apache Jackrabbit welcomes Apache Chemistry as a sibling top-level project," said Apache Jackrabbit Vice President Jukka Zitting. "We helped mentor the Chemistry community early on, and we are excited to see them reach this milestone. The success of Chemistry and CMIS is another testament to the combined strength of open source and open standards." Availability and Oversight All Apache products are released under the Apache Software License v2.0, and are overseen by a self-selected team of active contributors to the project. Upon a Project's maturity to a TLP, a Project Management Committee (PMC) is formed to guide its day-to-day operations, including community development and product releases. Apache Chemistry source code, documentation, and related resources are available at http://chemistry.apache.org/. About The Apache Software Foundation (ASF) Established in 1999, the all-volunteer Foundation oversees nearly one hundred fifty leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(3)(c) not-for-profit charity, funded by individual donations and corporate sponsors including AMD, Basis Technology, Cloudera, Facebook, Google, IBM, HP, Matt Mullenweg, Microsoft, SpringSource, and Yahoo!. For more information, visit http://www.apache.org/. "Apache" and "Apache Chemistry" are trademarks of The Apache Software Foundation. All other brands and trademarks are the property of their respective owners. # # # [Less]

Apache UIMA and Apache Hadoop Advance Data Intelligence and Semantics Capabilities of Watson Supercomputer Forest Hill, MD – 14 February 2011 – The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of ... [More] nearly 150 Open Source projects and initiatives, today announced that Apache UIMA and Apache Hadoop play key roles in the data intelligence and analytic proficiency of the IBM Watson supercomputer, playing against human champions on the TV show "Jeopardy!". Processing 80 trillion operations (teraflops) per second, Watson will access 200 million pages of content against 6 million logic rules to "understand" the nuances, meanings, and patterns in spoken human language, and compete in the trivia game show Jeopardy!. Contestants are presented with clues in the form of answers, and must phrase their responses as questions within a 5-second timeframe.  Hundreds of Apache UIMA Annotators and thousands of algorithms help Watson –which runs disconnected from the Internet– access vast databases to simultaneously comprehend clues and formulate answers. Watson then analyzes 500 gigabytes of preprocessed information to match potential meanings for the question and a potential answer to the question. Helping Watson do this is: Apache UIMA: standards-based frameworks, infrastructure and components that facilitate the analysis and annotation of an array of unstructured content (such as text, audio and video). Watson uses Apache UIMA for real-time content analytics and natural language processing, to comprehend clues, find possible answers, gather supporting evidence, score each answer, compute its confidence in each answer, and improve contextual understanding (machine learning) – all under 3 seconds. Apache Hadoop: software framework that enables data-intensive distributed applications to work with thousands of nodes and petabytes of data. A foundation of Cloud computing, Apache Hadoop enables Watson to access, sort, and process data in a massively parallel system (90+ server cluster/2,880 processor cores/16 terabytes of RAM/4 terabytes of disk storage). The Watson system uses UIMA as its principal infrastructure for component interoperability and makes extensive use of the UIMA-AS scale-out capabilities that can exploit modern, highly parallel hardware architectures. UIMA manages all work flow and communication between processes, which are spread across the cluster. Apache Hadoop manages the task of preprocessing Watson's enormous information sources by deploying UIMA pipelines as Hadoop mappers, running UIMA analytics. "The success and influence of Watson clearly shows that open source in general, and specifically open source software developed and released by the ASF, is deeply entwined in all layers and aspects of technology," said ASF President Jim Jagielski. "Apache software is part of computing and information technology DNA, forming complete or integral solutions to advanced problems, and leveraging the software under the non-restrictive Apache License allows for extremely rapid development of cutting edge technology." Watson faces off against record-breaking (human) Jeopardy champions Ken Jennings and Brad Rutter for the $1M grand prize 14-16 February 2011. 100% of Watson's winnings will be donated to charity; Rutter and Jennings have committed to donating 50% of their prizes. Availability All ASF products, including Apache UIMA and Apache Hadoop, are available to the public free of charge under the Apache Software Licence v2.0. Downloads, documentation, and related resources are available at http://www.apache.org/. About The Apache Software Foundation (ASF) Established in 1999, the all-volunteer Foundation oversees nearly one hundred fifty leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is a US 501(3)(c) not-for-profit charity, funded by individual donations and corporate sponsors including AMD, Basis Technology, Cloudera, Facebook, Google, IBM, HP, Matt Mullenweg, Microsoft, SpringSource, and Yahoo!. For more information, visit http://www.apache.org/. # # # Contact: Sally KhudairiThe Apache Software [email protected]+1 617 921 8656 [Less]

Blog Author: Vladimir Ivanov Introduction Scala Code Coverage Tool (SCCT) is a code coverage tool written in Scala and configured as SBT plugin (while integration with Maven is also possible). As for any large project, test are ... [More] vital for ESME as they gurantee that application works as expected. SCCT gathers data (after source code instrumentation phase) while tests are being run and generates user-friendly report and statistics related to test coverage of source code. Installation and configurationIntroducing SCCT support to ESME project is a matter of adding SBT plugin and consists of two steps: mixin project definition file with new trait as well as adding new repo and dependency to plugin definition file. Scala 2.8.1-compatible version of SCCT plugin is used in this article, but version for 2.7 is also available. Project File Project definition class for web project EsmeProject should mixin with ScctProject trait:import reaktor.scct.ScctProject class EsmeProject(info: ProjectInfo) extends DefaultWebProject(info) with ScctProject Plugins SCCT related configuration in plugin definition file is shown below: class Plugins(info : ProjectInfo) extends PluginDefinition(info) { ... val scctRepo = "scct-repo" at "http://mtkopone.github.com/scct/maven-repo/" lazy val scctPlugin = "reaktor" % "sbt-scct-for-2.8" % "0.1-SNAPSHOT" }    RunningTo collect test coverage data with SBT its neccessary to perform following command in SBT console: sbt> test-coverage Report files will be produced in ESME_ROOT/server/target/scala_2.8.1/coverage-report/ directory after all tests have been run. Open index.html file in your browser to see the results*. Here is a video explaining the test results. Notes Chrome browser is currently not supported. Also note that SCCT tool is still in beta. LinksMikko Koponen is the author of SCCT tool. Here is the project page on github. Here is the SCCT home page. [Less]

Apache Click 2.3.0 Release Candidate 1  is available for download. v2.3.0 contains important new features including Ajax support, Page Actions and light-weight stateful controls. In addition there are new documentation, examples and a slew other ... [More] enhancements. Click Home Roadmap and Changes - full list of new features, improvements and bug fixes Upgrade Path - please see the upgrade path when upgrading from 2.2.0 or earlier. Download Click 2.3.0-RC1 Maven bundles Live examples New features and improvement: Ajax support. Page Action support. Stateful Controls. Improve fields to only be processed if they have an incoming request parameter. This improvement streamlines dynamic forms since fields added at runtime during s POST request won't bind their values and won't be validated for that request. In subsequent requests the Field will have an incoming parameter and so will have it's value bound and validated. Another advantage is that dynamically added Fields won't have their default value overridden in the POST request they were added in. This issue has been raised by Nirmal Solanki [CLK-722]. Added automapping support for GAE with a caveat that page templates must be placed under the folders page or pages. This issue was raised by Ke Sun [CLK-639]. Added MessagesMapService interface to support pluggable messages map implementations [CLK-655]. Improved MessagesMap to be extendable and customizable [CLK-728]. Added support for loading DateField translations for month and day names from the JDK. [CLK-650]. Added support for Menus that do not have roles defined. If no roles are defined, IsUserInRoles passes a null argument to hasAccess to determine whether access is permitted to menus without roles [CLK-724].  Added support for absolute page classnames when configuring pages in click.xml. Absolute classnames aids with IDE hot-linking and is less confusing to use. [CLK-704].  Fixed escaping of control values and attributes to be XML friendly in order to support Ajax requests. Previously all HTML characters was escaped, now only the following characters are escaped: <, >, ", ', & [CLK-674].  New documentation: Added a section covering the new Behavior support. Added a chapter on Ajax, covering AjaxBehaviors, Ajax execution flow and a full example. Added a section covering the new Page Action support. New examples: Added examples showcasing the new Ajax support. See the Ajax Menu for the full list of examples. Added an example showing how to integrate a TabbedPanel, Form and Table. Added an example showing a Stateful TabbedPanel. Added an example FieldSeparator Control and example usage page [CLK-544].  Removed: Removed the ability to automatically bypass validation for Forms through JavaScript. This ability was added in 2.2.0 but raised concerns over security and was dropped for 2.3.0. If you used this feature in existing applications, please see the Upgrade path for a safe alternative to bypass validation. We apologize for the inconvenience. Deprecated: Deprecated stateful page support: Page.setStateful(). Stateful pages had the following issues: Stateful pages was introduced to make it easier to store page state across multiple HTTP requests. However developing a stateful page is very different from developing a stateless one and this lead to Click applications that are inconsistent and harder to maintain. In addition stateful page support has never been implemented consistently across the framework and some components did not work correctly. Stateful pages are very coarse grained, making it difficult to control which objects are stored in the session. Stateful pages have also introduced unnecessary complexity in the framework itself, which can now be phased out. Unfortunately there is no direct upgrade path from a stateful page. However the majority of use cases are catered for by the new stateful support in the controls: Table, Form, TabbedPanel, Field and AbstractLink. The Apache Click team [Less]

Committers, The Infrastructure Team has just enabled a new feature to control your SpamAssassin Threshold for your apache.org account. The default score for user delivery has always remained at 10, but with this new feature you can lower that ... [More] score to anything you want. Many people with older accounts will probably prefer a lower score, like 5, which is the default for all apache mailing lists. To lower your score login to id.apache.org and change your 'SpamAssassin Threshold (asf-sascore)' attribute to your desired level. Don't forget to supply the form with your LDAP password. Enjoy. [Less]

Open Source Platform for Building Installable Internet Applications Makes Building GUI Applications Even Easier Forest Hill, MD – 19 January 2011 – The Apache Software Foundation (ASF), the all-volunteer developers, stewards, and incubators of ... [More] nearly 150 Open Source projects and initiatives, today announced Apache Pivot 2.0, the full-featured, Open Source platform for building installable Internet applications (IIAs). Apache Pivot provides a professional-grade foundation for easily building and deploying sophisticated and engaging GUI applications that can be downloaded and installed like traditional desktop or mobile applications. Apache Pivot combines the enhanced productivity and usability features of a modern user interface toolkit with the power of Java or any other JVM-compatible language, such as JavaScript, Groovy, or Scala. "With Pivot, developers use the languages, tools, and APIs they already know, thereby reducing technology sprawl and streamlining solution technology stacks," said Greg Brown, Vice President of Apache Pivot. "It's a truly open solution for creating visually rich, highly functional desktop or Web-based applications." Apache Pivot is used in hundreds of applications across numerous industries, including retail, software, financial services, manufacturing, aerospace, and education, among others. Many of these applications have been developed for international use as well, as one of the key benefits of using Apache Pivot is ease of localization. Apache Pivot 2.0 features a number of significant enhancements that include: - Dynamic data binding – properties of target elements are automatically updated whenever a source value changes; - Support for named styles – CSS-like style classes are supported, including both typed and untyped style selectors; - Support for SVG images in addition to standard bitmap-based images (such as JPEG, PNG, or GIF) - Overhauled TextArea component – includes word navigation. undo/redo, and improved cut/paste behavior; - Additional color schemes optimized for a variety of popular desktop environments; - Serializer events – applications can now be notified as structured content such as JSON, XML, or CSV is read from an input stream; - Eclipse launcher – an Eclipse plugin helps simplify creating launch configurations for Pivot applications. Oversight and Availability Apache Pivot is available under the Apache Software License v2.0, and is overseen by a Project Management Committee (PMC), who guide its day-to-day operations, including community development and product releases. Apache Pivot 2.0 downloads, documentation, and related resources are available at http://pivot.apache.org/. About The Apache Software Foundation (ASF) Established in 1999, the all-volunteer Foundation oversees nearly one hundred fifty leading Open Source projects, including Apache HTTP Server — the world's most popular Web server software. Through the ASF's meritocratic process known as "The Apache Way," more than 300 individual Members and 2,500 Committers successfully collaborate to develop freely available enterprise-grade software, benefiting millions of users worldwide: thousands of software solutions are distributed under the Apache License; and the community actively participates in ASF mailing lists, mentoring initiatives, and ApacheCon, the Foundation's official user conference, trainings, and expo. The ASF is funded by individual donations and corporate sponsors including AMD, Basis Technology, Cloudera, Facebook, Google, IBM, HP, Matt Mullenweg, Microsoft, SpringSource, and Yahoo!. For more information, visit http://www.apache.org/. # # # [Less]

Apache ESME has an integration with Apache Ant. It is now possible to send messages to Apache ESME that describe the progress of your build steps. This is especially useful when Apache ESME is being used in development projects where individual ... [More] developers can be made aware of the status of various-build related actions. For example, a development team could be informed that a build is broken or if it is successful.   Setup Install Apache Ant Install Apache Maven Download the Apache Commons packages "Codec" and Logger. We also need Apache "Httpclient" . Please note that we are currently using the legacy 3.1 version of the HTTP Client.  Check-out the ESME java client: https://svn.apache.org/repos/asf/esme/trunk/esme-java-client Perform a maven build in this directory with the following command "mvn compile package -Dmaven.test.skip=true" . This will create a jar file "esme-rest-api-0.1.jar" in the target directory.  Create lib directory and copy "rest-api-0.1-SNAPSHOT.jar", "commons-codec-1.2.jar", "commons-httpclient-3.1.jar" and "commons-logging-1.1.1.jar" into this directory.  Create src directory and copy the "EsmeAntTask.java" file to this directory Change the build.xml file to point to the appropriate directories Change the token in the "esme" target in the build.xml file to a correct token. Change the proxy in the "esme" target in the build.xml file to a correct proxy. call ant dist esme to test the application Here is what the result looks like: Note: We wrote a version of this blog two years ago on our old blog. I've updated it and added an image plus more details.  Build.xml <project name="EsmeViaAnt" default="dist" basedir="."> <!-- set global properties for this build --> <property name="src" location="src"/> <property name="build" location="build"/> <property name="dist" location="dist"/> <path id="project.class.path"> <pathelement path="./dist/lib/EsmeViaAnt.jar:./lib/esme-rest-api-0.1.jar:./lib/commons-codec-1.4.jar:./lib/commons-logging-1.1.1.jar:./lib/commons-httpclient-3.1.jar"/> </path> <target name="init"> <!-- Create the time stamp --> <tstamp/> <!-- Create the build directory structure used by compile --> <mkdir dir="${build}"/> </target> <target name="compile" depends="init" description="compile the source " > <!-- Compile the java code from ${src} into ${build} --> <javac srcdir="${src}" destdir="${build}"> <classpath refid="project.class.path"/> </javac> </target> <target name="dist" depends="compile" description="generate the distribution" > <!-- Create the distribution directory --> <mkdir dir="${dist}/lib"/> <!-- Put everything in ${build} into the jar file --> <jar jarfile="${dist}/lib/EsmeViaAnt.jar" basedir="${build}"/> </target> <target name="esme" description="Send Esme" > <java fork="true" classname="EsmeAntTask"> <arg value="http://esmecloudserverapache.dickhirsch.staxapps.net/api"/> <arg value="31EL0R0M15NTD2LSOS0BKC5Y0P5JOVAZ6"/> <arg value="myproxy:81"/> <arg value="A message from the ant build process"/> <classpath> <pathelement path="./dist/lib/EsmeViaAnt.jar:./lib/esme-rest-api-0.1.jar:./lib/commons-codec-1.4.jar:./lib/commons-logging-1.1.1.jar:./lib/commons-httpclient-3.1.jar"/> </classpath> </java> </target> </project> EsmeAntTask java classimport org.apache.esme.api.EsmeRestApi; import org.apache.esme.model.Message; public class EsmeAntTask { public static void main (String[] args) { String apiUrl; String authToken; String localProxy; String message; EsmeRestApi esme; apiUrl = args[0]; authToken = args[1]; localProxy = args[2]; message = args[3]; try { esme = new EsmeRestApi(apiUrl); if ((localProxy != null) && !("".equals(localProxy))) { // Split proxyHost:port into two parts String[] proxy = localProxy.split(":"); esme.setProxy(proxy[0], Integer.parseInt(proxy[1])); } esme.login(authToken); Message esmeMsg = new Message(); esmeMsg.setBody(message); String[] tags = new String[1]; tags[0] = "Ant Task"; esmeMsg.setTags(tags); esmeMsg.setSource("Ant"); esme.sendMsg(esmeMsg); } catch (Exception e) {} } }   [Less]