Groovy is an agile dynamic language for the Java 2 Platform that has many of
the features that people like so much in languages like Python, Ruby and
Smalltalk, making them available to Java developers using a Java-like syntax.
Groovy is designed to help you get things done on the Java 2 Platform in a
quick, concise and fun way. Groovy brings the power of a scripting language
directly into the Java 2 Platform. For example:
- Shell scripting using Groovy allows the full power of the Java Platform to be
brought to bear to the task at hand.
- Groovy can be used (and indeed is already being used) as a replacement for
Java for small and medium sized applications to execute on the Java 2
Platform.
- Groovy can be used as an embedded language for dynamic business rules or
extension points utilizing the agility of Groovy and saving the cost of
redeploying applications for each change of rule (especially when the rules
are stored in a database).
- Groovy makes writing test cases for unit tests very easy.
As well as being a powerful language for scripting Java objects, Groovy can be
used as an alternative compiler to javac to generate standard Java bytecode to
be used by any Java project.
===> The following configuration options are available for groovy-2.4.21_2:
DOCS=on: Build and/or install documentation
===> Use 'make config' to modify these settings
Mk/**java.mk: Convert bsd.java.mk to USES
The following features have been added or changed:
- Instead of USE_JAVA use USES=java. This defaults to
USES=java:build,run if NO_BUILD is undefined. Else it defaults to
USES=java:run
- Instead of USE_ANT=yes use USES=java:ant which also implies
USES=java:build
- Instead of JAVA_BUILD=yes use USES=java:build. Does not imply run or
extract
- Instead of JAVA_EXTRACT=yes use USES=java:extract does not imply
build or run
- Instead of JAVA_RUN=yes use USES=java:run does not imply extract or
build
- Instead of USE_JAVA=<version> use USES=java and JAVA_VERSION=<version>
Approved by: mat (portmgr), glewis
Differential Revision: https://reviews.freebsd.org/D48201
Remove WWW entries moved into port Makefiles
Commit b7f05445c00f has added WWW entries to port Makefiles based on
WWW: lines in pkg-descr files.
This commit removes the WWW: lines of moved-over URLs from these
pkg-descr files.
Approved by: portmgr (tcberner)
Add WWW entries to port Makefiles
It has been common practice to have one or more URLs at the end of the
ports' pkg-descr files, one per line and prefixed with "WWW:". These
URLs should point at a project website or other relevant resources.
Access to these URLs required processing of the pkg-descr files, and
they have often become stale over time. If more than one such URL was
present in a pkg-descr file, only the first one was tarnsfered into
the port INDEX, but for many ports only the last line did contain the
port specific URL to further information.
There have been several proposals to make a project URL available as
a macro in the ports' Makefiles, over time.
(Only the first 15 lines of the commit message are shown above )
Clean up after java/openjdk6 and java/openjdk6-jre removal
java/openjdk6 support was removed from Mk/bsd.java.mk (r512662) and
java/openjdk6 and java/openjdk6-jre were removed from the ports tree
(r512663). Now this patch completely removes remaining stuff from the
ports tree.
PR: 241953 (exp-run)
Reviewed by: glewis
Approved by: portmgr (antoine)
Differential Revision: https://reviews.freebsd.org/D22342
Convert all :U to :tu and :L to :tl
Since FreeBSD 8.4 and FreeBSD 9.1 make(1) do support :tu and :tl as a
replacement for :U and :L (which has been marked as deprecated)
bmake which is the default on FreeBSD 10+ only support by default
:tu/:tl a hack has been added at the time to support :U and :L to ease
migration. This hack is now not necessary anymore
Note that this makes the ports tree incompatible with make(1) from
FreeBSD 8.3 or earlier
With hat: portmgr
According to the Porter's Handbook (5.12.2.3.) default options must be added to
OPTIONS_DEFINE. This policy has been implemented only recently that's why we
have many ports violating this policy.
This patch adds the default options specified in the Porter's Handbook to
OPTIONS_DEFINE where they are being used. Ports maintained by
gnome@FreeBSD.org, kde@FreeBSD.org and x11@FreeBSD.org have been excluded.
Approved by: portmgr (bapt)
- Update to version 2.0.5 [1]
- Convert to OptionsNG
- Remove tab from WWW: line
PR: ports/174510 [1]
Submitted by: Radim Kolar <hsn@sendmail.cz>
Approved by: Mitchell Smith <mjsotn@gmail.com> (maintainer)
- The proper acronym for Apache Software License 2 is really AL2
- Thanks to crees@ for generating the initial patch
PR: ports/163521
Submitted by: Pedro Giffuni <pfg apache.org>
Hat: portmgr
Exp run by: pav
Bump portrevision due to upgrade of devel/gettext.
The affected ports are the ones with gettext as a run-dependency
according to ports/INDEX-7 (5007 of them) and the ones with USE_GETTEXT
in Makefile (29 of them).
PR: ports/124340
Submitted by: edwin@
Approved by: portmgr (pav)
- Update to 1.0-jsr-06 [1]
- Set GROOVY_HOME only when not already defined
- Set JAVA_HOME when not already defined, using feature from javavmwrapper 2.2
Reported by: portscout [1]
Groovy is an agile dynamic language for the Java 2 Platform that has many of
the features that people like so much in languages like Python, Ruby and
Smalltalk, making them available to Java developers using a Java-like syntax.
Groovy is designed to help you get things done on the Java 2 Platform in a
quick, concise and fun way. Groovy brings the power of a scripting language
directly into the Java 2 Platform. For example:
- Shell scripting using Groovy allows the full power of the Java Platform to be
brought to bear to the task at hand.
- Groovy can be used (and indeed is already being used) as a replacement for
Java for small and medium sized applications to execute on the Java 2
Platform.
- Groovy can be used as an embedded language for dynamic business rules or
extension points utilizing the agility of Groovy and saving the cost of
redeploying applications for each change of rule (especially when the rules
are stored in a database).
- Groovy makes writing test cases for unit tests very easy.
As well as being a powerful language for scripting Java objects, Groovy can be
used as an alternative compiler to javac to generate standard Java bytecode to
be used by any Java project.
WWW: http://groovy.codehaus.org/
