In the IDE and Editor Integration section of the
External Tools and Tasks page it lists an older ant
plugin for JBuilder but it doesn't list Borland
JBuilder 8 Enterprise which now supports ANT natively.
Also, GEL from www.gexperts.com also supports ANT and
isn't listed.
I didn't submit a bug on
Costin Manolache wrote:
IMHO ant should try to be a bit easier to use than XSLT.
I was playing with some examples to capture the use cases
which have been discussed for include and import with a view
to getting a/some simple models straight in my head.
I am attempting in part to explain the use
[EMAIL PROTECTED] wrote:
If macrodef attribute are to be implements as substitutions, what
should be the notation? (where x is the attribute name)
[ ] as ${x} (look like ant properties) confusion with 'real'
properties
[ ] as $(x) to close to A
[ ] as @x
I would mostly encourage this. It would seem reasonable
to be able to write tests productively use ant build files.
I am not sure how directly tied to ant (vs testing any java
program) you would need to make it to be worthwhile. I would
hope that it could be more generic.
You might want to have a
You might want to consider WebTest (webtest.canoo.com).
WebTest test scripts are like ant build scripts.
You can mix and match whatever ant tasks you want with
webtest tasks (called steps because they are actually
extend ant's Task and provide a reference to a context
which contains the state
Kev Jackson wrote:
Hi all,
This is totally off-topic, apart from in a meta-sense of Ant being an
open source project...
My favourites at the moment are:
WebTest - an Ant extension with many extension for acceptance testing (mainly)
web applications.
Groovy - a neat scripting language (which
Peter Reilly wrote:
Ruby my friend ruby
look at [rake]
Yes, Ruby is OK but if you want to contribute to the project
in a meaningful way, Groovy/Ant/Grails/WebTest is a more fun
place to be (at least in my experience) at the moment. There
is still scope for fixing things which annoy you.
[EMAIL PROTECTED] wrote:
Hello,
Has the possibility of adding multiple conditions to the target 'if' and
'unless' attributes ever been considered? Are there any reasons why this
change would be a bad idea?
I have found Groovy (and to a lesser degree other scripting
languages) to be very
[EMAIL PROTECTED] wrote:
Hello,
Has the possibility of adding multiple conditions to the target 'if' and
'unless' attributes ever been considered? Are there any reasons why this
change would be a bad idea?
I have found Groovy (and to a lesser degree other scripting
languages) to be very
Kevin Jackson wrote:
On 9/16/06, Jesse Glick [EMAIL PROTECTED] wrote:
[...]
(I'd steer away from groovy before anyone suggests it ;))
Kevin, anything in particular you don't like about Groovy?
In my experience Groovy is an excellent scripting language
and has excellent Ant support but as
Kevin Jackson wrote:
On 9/16/06, Jesse Glick [EMAIL PROTECTED] wrote:
[...]
(I'd steer away from groovy before anyone suggests it ;))
Kevin, anything in particular you don't like about Groovy?
In my experience it is an excellent scripting language and
has excellent Ant support but as
Kevin Jackson wrote:
Kevin, anything in particular you don't like about Groovy?
Hi Paul,
Nice to 'chat' to you :)
My major problem with groovy was it's instability - every time I
looked at it previously, something was mentioned as still being
unstable etc.
Yes, it has had an interesting
The Ant Team is proud to announce the first Beta release of
Apache AntUnit 1.0.
Sorry I have a question that is half Groovy and half AntUnit related.
It is also half user/half dev related. I am wanting to know the best
way to use the API (and potentially some normally internal pieces).
I was
The Ant Team is proud to announce the first Beta release of
Apache AntUnit 1.0.
I added a patch to bug 28883 (regex condition for Ant):
http://issues.apache.org/bugzilla/show_bug.cgi?id=28883
Which would allow AntUnit to have an additional assertion:
target name=testTstampFormat
tstamp
Thanks Stefan, comments and a question below.
Stefan Bodewig wrote:
On Sun, 24 Sep 2006, Paul King [EMAIL PROTECTED] wrote:
[...]
Does the Antlib.createAntlib part look like a violation of what I
should be doing from an Ant perspective?
You rely on an internal API - granted, technically
Groovy lets you run AntUnit tests (in Groovy AntBuilder syntax) and see
the results using the normal Green bar if you use Groovy's AllTestSuite.
Otherwise, just run as - ant... and point to your ant 1.7 jar files
so you don't get the built-in ant jars and you can expect output as per below:
Antoine Levy-Lambert wrote:
[...] I hope that for instance the pom of commons-bsf should itself contain js, groovy, and the other supported languages as optional runtime dependencies.
BSF doesn't contain optional jars at the moment. The project team
members are fairly new to Maven and didn't
whether
it is possible to overwrite the existing POM for 2.4.0 or whether these
additions would have to wait until the next release of bsf.
Regards,
Antoine
Paul King wrote:
Antoine Levy-Lambert wrote:
[...] I hope that for instance the pom of commons-bsf should itself
contain js, groovy
to improve things further I'll write back to the list.
Cheers, Paul.
Antoine Levy-Lambert wrote:
Original-Nachricht
Datum: Thu, 26 Oct 2006 06:06:18 +1000
Von: Paul King [EMAIL PROTECTED]
An: Ant Developers List dev@ant.apache.org
Betreff: Re: svn commit: r466627 - in /ant/core/trunk
Antoine Levy-Lambert wrote:
[...] You would like for instance to say : get bsf + groovy + jython but not
beanshell for instance.
Forgot to say: yes, this is what I would like to do.
You could have a look at two files written mainly by Steve Loughran, fetch.xml
and libraries.properties.
Peter Reilly wrote:
[...] however, having bsf.jar and js.jar in
the $ANT_HOME/lib, is a user's choice, so if they are there it is
a good assumption that the user wants to use them.
I think that Groovy has native jsr support but jruby didn't last
time I checked (though that may soon or may have
Peter Reilly wrote:
On 10/27/06, Paul King [EMAIL PROTECTED] wrote:
Peter Reilly wrote:
[...] however, having bsf.jar and js.jar in
the $ANT_HOME/lib, is a user's choice, so if they are there it is
a good assumption that the user wants to use them.
I think that Groovy has native jsr support
Stefan Bodewig wrote:
If there is enough interest we could certainly still create a 1.6
compatible branch.
From this posting I got a reply from Paul King, who explained that
similar asserts are being used in WebTest project and that he would
be interested to learn the outcome of this discussion
There is one of these in WebTest:
http://webtest.canoo.com/webtest/manual/retry.html
But it might be nice to have one outside WebTest as well.
You might want to guard against NoRetries being equal to 0
or change the code to skip the perform in that case. It
wouldn't be the usual case but
Chris Connelly wrote:
Hello,
I apologize in advance if this is the wrong forum for this question.
My organization is looking to replace some home-grown, in-house test automation
tools with open source tools where possible. I've prototyped some solutions
using Ant and AntUnit, and was
Peter Reilly wrote:
On 7/17/07, Matt Benson [EMAIL PROTECTED] wrote:
The refactoring is much bigger than the formatting
here, FYI... wanted to reassure you that I am taking
your comments to heart, Peter.
Cool!
I think perhaps we should push to remove all
checkstyle errors for ant1.8. At work,
[EMAIL PROTECTED] wrote:
Hi,
We've recently integrated Jepp (http://jepp.sourceforge.net/) into our
use of Ant via the BSF engine. This is very useful because we use Python
for scripting quite a lot and it allows Python code to be used in full
while also allowing access to Java objects.
Peter Reilly wrote:
On Tue, Mar 25, 2008 at 8:59 PM, Paul King [EMAIL PROTECTED] wrote:
[EMAIL PROTECTED] wrote:
Hi,
We've recently integrated Jepp (http://jepp.sourceforge.net/) into our
use of Ant via the BSF engine. This is very useful because we use Python
for scripting quite
If you can move straight in to Confluence 2.8, that will let you
do page ordering which helps a lot if you want to export your
site to PDF as a User Guide/PDF manual. It also seems to do
a slightly better job formatting code examples.
Cheers, Paul.
Archie Cobbs wrote:
Not sure if my vote
Not a formal vote, but just some positive feedback.
I built Groovy with 1.7.1 with no problems. Also, all
of the AntBuilder tests within the build passed fine
using 1.7.1 as did my manual testing. Looking good!
Cheers,
Paul.
Kevin Jackson wrote:
Hi all,
There is an additional folder at
If you really want to get fully up to speed quickly, I would
recommend finding yourself a book or two to read. They will
help you absorb things at a faster pace than the individual
project websites.
To cover off the Ant side of things why not try:
I don't have a vote but happy to give a non-binding +1.
The one thing that might need changing (shouldn't affect
an acceptance decision) is the rename of import to
include - this might need to be looked at given the
recent introduction in trunk of include.
Cheers, Paul.
Stefan Bodewig wrote:
Not 100% the same as what you suggest but Groovy's Grape system does some
of what you are asking for. Normally Grapes are used from within scripts,
e.g.:
@Grab('org.apache.ant:ant:1.7.1')
import org.apache.tools.ant.Main
Main.main(['-version'] as String[])
but it also has a commandline
Paul King wrote:
Not 100% the same as what you suggest but Groovy's Grape system does some
of what you are asking for. Normally Grapes are used from within scripts,
e.g.:
@Grab('org.apache.ant:ant:1.7.1')
import org.apache.tools.ant.Main
Main.main(['-version'] as String[])
but it also has
or thin wrapped with ant scripting can be
about 10 times faster for
using from command shell.
2010/1/18 Paul King pa...@asert.com.au
Paul King wrote:
Not 100% the same as what you suggest but Groovy's Grape system does some
of what you are asking for. Normally Grapes are used from within scripts
I'd probably use Groovy or whatever your favorite JVM scripting language is.
Groovy-WS is the library you would need. It uses Apache CXF under the covers.
If you have trouble getting started I can try to find one of my existing
examples that does something similar.
Cheers, Paul.
On 16/03/2010
Don't know if this helps or not:
?xml version=1.0 encoding=UTF-8?
project name=SOAP example basedir=.
property environment=env/
taskdef name=groovy classname=org.codehaus.groovy.ant.Groovy
classpath
fileset dir=${env.GROOVY_HOME}
Here's another version showing setting properties:
?xml version=1.0 encoding=UTF-8?
project name=SOAP example default=main basedir=.
property environment=env/
property name=celsius value=0/
target name=main
taskdef name=groovy classname=org.codehaus.groovy.ant.Groovy
No official vote for me but just as feedback, Ant 1.8.2 built
the latest Groovy with no problems and the (albeit humble)
AntBuilder tests all ran fine.
Cheers, Paul.
On 14/12/2010 6:59 AM, Antoine Levy-Lambert wrote:
Hi,
as announced I have built a release candidate for Ant 1.8.2.
This is
with reason:
Property skipFetch was circularly defined.
The fix was to add a default property defn but it seems
like such a behavior change in a minor update release
should warrant an entry in the WHATSNEW at least?
Cheers, Paul.
On 15/12/2010 1:48 PM, Paul King wrote:
No official vote for me
:
On 2010-12-15, Paul King wrote:
After a little more testing, one thing I did notice was an
apparent stricter treatment of property expansion.
With 1.8.1, having an arg to a forked java task like this:
arg value=-DskipFetch=${skipFetch}/
was happily ignored if skipFetch wasn't defined
On 15/12/2010 10:55 PM, Stefan Bodewig wrote:
On 2010-12-15, Paul King wrote:
This is probably enough to reproduce it:
Yes, it is, thank you Paul.
project
target name=foo
java classname=org.apache.tools.ant.launch.Launcher fork=true
classpath path=${java.class.path
I tried out the proposed artifacts with the Groovy build and test suite
(which has a bunch of ivy-related tests for downloading groovy grapes) and
also did some additional manual testing - all seemed to work as expected.
So non-binding informal +1 from me.
Cheers, Paul.
On 14/01/2013 8:40
+1 non-binding (based on running against the groovy-ant test suite)
Cheers, Paul.
On 1/06/2015 12:46 AM, Stefan Bodewig wrote:
Hi all
I've created a release candidate for 1.9.5:
git tag: ANT_195_RC1
hash: 54ac2fedd
on commit: ea7bf28
tarballs:
+1 (non-binding)
I checked the checksums and signature of the source zip.
I ran Groovy's master branch against this version including its
groovy-ant test suite.
I must admit to not having followed much recent discussion on the dev
mailing list. Just as an aside for future reference, I thought
Yep, that makes things clearer. Nice.
Cheers, Paul.
On Sat, Dec 31, 2016 at 2:50 AM, Stefan Bodewig wrote:
> On 2016-12-30, Stefan Bodewig wrote:
>
>> The README.html isn't really part of the release and we can simply
>> modify it at will at any time. Let me try to improve
The current version of Groovy has 1.6 as the minimum but is our maintenance
stream.
The upcoming next version will require 1.7 and versions with 1.8 as the
minimum are not too far away.
Ant 1.9.x is still on Java5 but Ant 1.10.x requires Java 8.
I don't think Gradle uses any Ivy classes any
On Sun, Jun 4, 2017 at 7:47 PM, Gintautas Grigelionis <
g.grigelio...@gmail.com> wrote:
> [...]
> P.S. While we're at it, in the light of the latest ASM debacle, I'm
> interested in improving Ant classloader task
[...]
Which ASM issue(s) are you referring to? Is there a link to some
+1 (non-binding)
I ran the Groovy test suite against the candidate jars and everything
passed.
There are over 100 tests related to AntBuilder and the groovy, groovyc,
groovydoc ant tasks.
Cheers, Paul.
On Tue, Jul 10, 2018 at 7:55 PM Stefan Bodewig wrote:
> Hi all
>
> I've created a new
For Groovy we use a single command but as part of push with multiple
--release options, something like:
snapcraft push --release=3.0/beta --release=beta groovy_3.0.0-beta-3_all.snap
On Thu, Sep 5, 2019 at 5:08 PM Stefan Bodewig wrote:
> On 2019-09-05, wrote:
>
> > -$ snapcraft release
+1 (non-binding)
I checked 1.10.8 with AdoptOpenJDK 11.0.6:
+ checksums and signatures for src and bin zips
+ cursory glance at LICENSE/NOTICE files seemed okay
+ ran against Groovy's test suite (GROOVY_3_0_X branch) which invokes
several hundred related tests for Groovy's Ant tasks, AntBuilder
+1 (non-binding)
* Checked signatures and hashes for zip and tar.gz src distributions.
* I also ran the Apache Groovy build against the new artifacts. The Groovy
test suite has >100 tests exercising various aspects of Ant functionality
for Groovy's AntBuilder and Groovy's various Ant tasks. There
+0 (non-binding)
I checked:
* LICENSE & NOTICE seem okay
* HASH & SIG seem okay
* I ran against the Groovy test suite which has 100+ ant-related tests and
all continue to pass (using JDK16 and the upcoming Groovy 4)
I was surprised to see binary jars in the src archives under lib/optional.
I
+1 (non-binding)
I did a casual inspection of the zip artifact including checking for
LICENSE & NOTICE files, and confirming its hash & signature.
I ran the Apache Groovy test suite against the candidate maven artifacts
for JDK 17 and 19.
Cheers, Paul.
On Wed, Aug 16, 2023 at 10:35 PM Jaikiran
Do you know if there is an issue with the "allow" class approach if
multiple projects adopt that technique? E.g. if Netbeans or Groovy
also have an allow class, will that cause a split package violation or
since it isn't really referenced except for those early JDKs, that we
should be okay? I will
Thanks for the update. We have some workarounds in the Groovy codebase too.
I'll try to tidy them up too once this has settled.
Thanks again, Paul.
On Mon, May 15, 2023 at 10:08 PM Jaikiran Pai wrote:
> Hello Paul,
>
> On 12/12/22 5:30 am, Paul King wrote:
> > Do you know if th
56 matches
Mail list logo