****************************************************************************
**
** help is no longer supported. Please run 'ant -projecthelp'
**
***************************************************************************
Global settings:
java.home = ${java.home}
user.home = ${user.home}
java.class.path = ${java.class.path}
Velocity settings:
Version: ${version}
Debug: ${debug}
Optimize: ${optimize}
Deprecation: ${deprecation}
Target settings (relative to build tree root):
Velocity Source: ${build.src}
Velocity Classes: ${build.dest}
Velocity API Docs: ${build.javadoc}
Velocity Docs: ${build.docs}
Velocity Test Reports: ${build.test.reports}
********************************************************
**
** The javax.sql.Datasource class has not been found on
** your classpath. This means that your newly built
** Velocity jar will not contain the JDBC based resource
** loaders. If this is a problem, please use a JDK for
** building that contains the javax.sql.Datasource class.
**
********************************************************
********************************************************
**
** The java.util.logging.Logger class has not been found on your
** classpath. This means that your newly built Velocity jar will
** not contain JDK 1.4 compatible logging code. If this is a
** problem, please use a 1.4 or newer JDK for building.
**
********************************************************
Could not run javacc:
***********************************************************
** You have not configured your JavaCC installation
** location in the javacc.home property.
***********************************************************
Could not run javacc:
***********************************************************
**
** JavaCC 3.2 or later must be installed at ${javacc.home}.
** Ant must be at least version 1.6.x.
**
***********************************************************
***********************************************************
** Creating Parser.jj and Parser.java in source tree.
**
** Note: ASTNode files generated by jjtree are
** not generated with this task. To create new ASTNode files,
** run jjtree manually then copy the relevant files into
** the runtime/parser/node directory (deleting all other
** generated files).
**
***********************************************************
**************************************************************
** Building the examples :
** examples/app_example1 : application example
** examples/app_example2 : application example
** examples/context_example : example context implementations
** examples/logger_example : how to make an external logger
** examples/xmlapp_example : how to access XML data in a template
** examples/event_example : how to use Velocity's event handlers
**************************************************************
Deploying to ${maven.remote.repository}Deploying to Apache Maven repository
***** RELEASE INSTRUCTIONS *****
* Be sure you can answer "yes" to the following:
* Was your local code up to date and free of modifications or extra files?
* Was the version number correct in both build.properties and pom.xml?
* For a final release, the distributionManagement.site.url value
in the pom.xml should be:
scpexe://people.apache.org/www/velocity.apache.org/engine/releases/velocity-${version}
and for alpha or beta releases it should be:
scpexe://people.apache.org/www/velocity.apache.org/engine/devel/
* Do all new files have the Apache License? (use "ant rat" to double-check)
* Is ${build.src}/changes/changes.xml up to date?
Feel free to set an estimated release date for this version in that file;
it can be corrected later if the release is delayed.
* Is ${build.src}/site/apt/upgrading.apt up to date for this release?
* Is the ${velocity.dir}/README.txt up to date for this release?
* If a final release, update the "Where do I get releases?" section of
${build.dir}/xdocs/docs/index.xml
to show the latest stable version number.
* Write down the current svn revision so you don't have to look it up
later when you make the tag for this release (post-vote).
* Go to ${build.dir} and sign all the jar, zip, tar.gz and pom files
with your personal PGP key using a script like this:
#! /bin/bash
for i in *.tar.gz *.zip *jar; do
gpg --armor --output $i.asc --detach-sig $i
done
* SSH into people.apache.org and make sure that this directory exists:
${publish.dir}
* If you haven't done it before, ensure that your PGP key is appended to
/www/www.apache.org/dist/velocity/KEYS
Some instructions for that are at the top of that file.
* Call "ant publish"
* Review http://wiki.apache.org/velocity/ReleaseProcess for more details.
Could not run create distribution package:
***********************************************************
**
** In order to create a distribution package, you must be
** using Java version ${dist.required.java.version} instead
** of Java version ${java.version}
**
***********************************************************
***********************************************************
**
** Creating a distribution package. Compiling with
** Java version ${java.version}
**
***********************************************************
#######################################################
#
# Now using Anakia to transform the XML documentation
# to HTML.
#
# using project file: ${docs.project}
#
# Note: set property "docs.project" to "project.xml"
# for distribution and "project-website.xml" for
# website.
#######################################################
!!NOT READY TO PUBLISH!!
You must first execute "release" target, then sign the distribution
files with your pgp key (creating the needed '.asc'signature files).
To override this (only when uploading development snapshots not meant
for public release), add the property "release.signed=true" to your
build.properties.
You may also need to add the Jsch jar to Ant's classpath to enable the
optional 'scp' task.
Uploading distribution files from
${build.dir}
to
${username}:${password}@${publish.server}:${publish.dir}
***** RELEASE INSTRUCTIONS *****
* SSH to ${publish.server} and verify the checksums and signatures of the uploaded
files with a script like:
#!/bin/csh
foreach fn ( *.tar.gz *.zip *.jar *.pom )
echo Verifying $fn...
echo GPG signature should be "Good"
gpg --verify $fn.asc
echo MD5s should be identical
cat $fn.md5
md5 -q $fn
echo SHA1s should be identical
cat $fn.sha1
sha1 -q $fn
echo
end
* Announce the availability of an Engine ${version} test build on dev@velocity.apache.org.
* Allow a few days for people to test the test build.
* Call for a release vote on private@velocity.apache.org and dev@velocity.apache.org
* Once the release vote has passed, these files should all be copied to
/www/www.apache.org/dist/velocity/engine/${version}
and the non-dep jar, source jar, javadoc jar, pom and respective md5, sha1 and asc files should be copied into
/www/people.apache.org/repo/m2-ibiblio-rsync-repository/org/apache/velocity/velocity/${version}/
* Remove older releases of the same grade as this one (alpha, beta, final) from
/www/www.apache.org/dist/velocity/engine
* Tag the release in SVN with a command such as:
svn copy -m "Release Engine ${version}" -r [revision #] \
https://svn.apache.org/repos/asf/velocity/engine/trunk \
https://svn.apache.org/repos/asf/velocity/engine/tags/${version}
* Go to ${velocity.dir} and run "mvn site" then "mvn site:deploy"
to publish the documentation for this release on the website
* Wait a day or so for the mirrors and maven repos to sync up.
* Update the main website (velocity-site project) with the release info:
* Add this ${version} release to news.xml, download.xml, doap_engine.rdf and
the "Release status" section of index.xml
* Check those changes into SVN
* Email Henning to have him update and build the site from velocity.zones.apache.org
(or get velocity-site to work for other people besides Henning)
* Wait a few hours for the site to sync up.
* Send an announcement email from your apache.org address to all Velocity lists
and also to announce@apache.org.
* Review http://wiki.apache.org/velocity/ReleaseProcess for more details.
Could not run junit tests:
***********************************************************
**
** Ant must be at least version 1.7
**
***********************************************************
NOTE: At this time, you must add Apache RAT, Apache RAT AntTasks
Commons-Lang, Commons-Collections and Commons-CLI to Ant's lib directory
to use this.
Your RAT report is here: ${build.test.reports}/rat-report.txtWorking with FindBugs at: ${findbugs.home}Analyzing ${build.dir}/${final.name}.jar built from ${build.src}Analyzing ${build.src}...unusedcodeimportsGenerated report is at ${build.test.reports}\pmd_report.html