Updating the Continuous/Synergy tasks that are shipped with Ant
Hey all, I'm the build manager working a financial company in Ireland. I'd like to add some more functionality to the standard Continuous/ Synergy tasks which come with Ant. They're quite old now and could use some updating. How do I go about contributing source to the Ant project? Do I need to send svn diff's to the mailing list, or is their another preferred way? Regards, Dave -- "A lot of people are afraid of heights. Not me, I'm afraid of widths."
Re: Updating the Continuous/Synergy tasks that are shipped with Ant
Sounds good. I haven't started working on them yet, but I'd probably be enhancing the existing tasks a little (as they're still relevant) and adding one or two new tasks.I'll post back here once I have something to show. Are you also using Synergy at your workplace, or was the antlib for something else? On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote: > >Hey all, > >I'm the build manager working a financial company in Ireland. > >I'd like to add some more functionality to the standard > >Continuous/ Synergy > >tasks which come with Ant. > >They're quite old now and could use some updating. > >How do I go about contributing source to the Ant project? > >Do I need to send svn diff's to the mailing list, or is their another > >preferred way? > > I would suggest to deprecate the internal tasks and create a new antlib. > > Do you have some implementations? > I have written a new antlib for my company and I can ask for > contributing that. > > > Jan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "A lot of people are afraid of heights. Not me, I'm afraid of widths."
Re: Updating the Continuous/Synergy tasks that are shipped with Ant
Well if you'd like to send me your Antlibs, I can do some testing for you
here. We're using Synergy 6.5 SP2 (and we're planning on installing the
first post-SP2 patch next wednesday). Would that be of interest to you?
On Fri, Nov 28, 2008 at 10:39 AM, <[EMAIL PROTECTED]> wrote:
> We are using Synergy 6.5 at the moment and using it since ... mmh ... 5.1?
> 4.5?
> With 6.5 Synergy has a Java client (ok present in 6.1 also), but sadly no
> real and open "API" so these tasks wrap the command line client.
>
> As often with scm tasks a test environment for unit tests is difficult ...
>
>
> Jan
>
>
>
>
>
> initialRole=""/>
> Starts a Synergy session
>
>
> Stops a Synergy session
>
>
> Connects to a running session. ("CCM_ADDR" not set by the Java client any
> more)
>
>
>
>
> Check files out
>
>
> Check a project out
> ccm co -p ${project}-${version} -release ${release} -mod -path ${workarea}
>
>
> Reconfigure command
>
> asDefault=""/>
> Creates a new task
>
>
>
> interfacekind="info.interface"
> ip="info.ip"
> sessionid="info.session"
> user="info.user"
> computer="info.computer"/>
>
> Gets information about the current session
> [echoproperties] #Ant properties
> [echoproperties] #Mon May 22 09:46:33 CEST 2006
> [echoproperties] info.interface=Command Interface
> [echoproperties] info.user=mat
> [echoproperties] info.session=1707
> [echoproperties] info.ip=130.11.36.89
> [echoproperties] info.db=/rzf/db/skm/ccm_databases/uebungen
> [echoproperties] info.computer=nb011689
>
>
>
>
>
>
>
> Checks for a give role (task and condition)
>
>
> Stores the object version of a given file in a property. Optional default
> value if not under CM control.
>
>
>https://myJira.org/browse/
> "/>
>
> Creates a changelist by getting all completed tasks of a release. The
> result is a text or xml file with release name and task synopsis. If
> "detailed" with their documentations too. A XSL could transform that into
> HTML.
> in="${build.dir}/changes-detailed.xml"
>out="${build.dir}/changes.html"
> >
>
><javaresource name="changelist2html.xsl"/>
>
>
>
>
>
>
>
>
>
>
>
> Moving with Synergy.
>
>
>
> Checks whether an open Synergy session is available.
>
>
>
> >-Ursprüngliche Nachricht-
> >Von: Dave [mailto:[EMAIL PROTECTED]
> >Gesendet: Freitag, 28. November 2008 10:40
> >An: Ant Developers List
> >Betreff: Re: Updating the Continuous/Synergy tasks that are
> >shipped with Ant
> >
> >Sounds good. I haven't started working on them yet, but I'd probably be
> >enhancing the existing tasks a little (as they're still
> >relevant) and adding
> >one or two new tasks.I'll post back here once I have something to show.
> >Are you also using Synergy at your workplace, or was the antlib for
> >something else?
> >
> >On Fri, Nov 28, 2008 at 7:11 AM, <[EMAIL PROTECTED]> wrote:
> >
> >> >Hey all,
> >> >I'm the build manager working a financial company in Ireland.
> >> >I'd like to add some more functionality to the standard
> >> >Continuous/ Synergy
> >> >tasks which come with Ant.
> >> >They're quite old now and could use some updating.
> >> >How do I go about contributing source to the Ant project?
> >> >Do I need to send svn diff's to the mailing list, or is
> >their another
> >> >preferred way?
> >>
> >> I would suggest to deprecate the internal tasks and create a
> >new antlib.
> >>
> >> Do you have some implementations?
> >> I have written a new antlib for my company and I can ask for
> >> contributing that.
> >>
> >>
> >> Jan
> >>
> >> -
> >> To unsubscribe, e-mail: [EMAIL PROTECTED]
> >> For additional commands, e-mail: [EMAIL PROTECTED]
> >>
> >>
> >
> >
> >--
> >"A lot of people are afraid of heights. Not me, I'm afraid of widths."
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
"A lot of people are afraid of heights. Not me, I'm afraid of widths."
Re: Updating the Continuous/Synergy tasks that are shipped with Ant
I can see your point. Perhaps Apache could approach IBM about a free license
for the tool just for such a purpose.Its much better for IBM if Ant has
well-integrated Synergy support.
On Fri, Nov 28, 2008 at 12:46 PM, <[EMAIL PROTECTED]> wrote:
> What we need is an automatic unit test.
> This requires a testbed.
>
> As an AntLib for a very special scm we could live with the fact that not
> any committer has access to the scm system. But a few should have. And they
> should have a test suite so they can "click a button and get the result".
>
>
> Jan
>
> >-Ursprüngliche Nachricht-
> >Von: Dave [mailto:[EMAIL PROTECTED]
> >Gesendet: Freitag, 28. November 2008 11:48
> >An: Ant Developers List
> >Betreff: Re: Updating the Continuous/Synergy tasks that are
> >shipped with Ant
> >
> >Well if you'd like to send me your Antlibs, I can do some
> >testing for you
> >here. We're using Synergy 6.5 SP2 (and we're planning on installing the
> >first post-SP2 patch next wednesday). Would that be of interest to you?
> >
> >On Fri, Nov 28, 2008 at 10:39 AM, <[EMAIL PROTECTED]> wrote:
> >
> >> We are using Synergy 6.5 at the moment and using it since
> >... mmh ... 5.1?
> >> 4.5?
> >> With 6.5 Synergy has a Java client (ok present in 6.1 also),
> >but sadly no
> >> real and open "API" so these tasks wrap the command line client.
> >>
> >> As often with scm tasks a test environment for unit tests is
> >difficult ...
> >>
> >>
> >> Jan
> >>
> >>
> >>
> >>
> >>
> >> >uiDatabaseDir=""
> >> initialRole=""/>
> >> Starts a Synergy session
> >>
> >>
> >> Stops a Synergy session
> >>
> >>
> >> Connects to a running session. ("CCM_ADDR" not set by the
> >Java client any
> >> more)
> >>
> >>
> >>
> >>
> >> Check files out
> >>
> >>
> >> Check a project out
> >> ccm co -p ${project}-${version} -release ${release} -mod
> >-path ${workarea}
> >>
> >>
> >> Reconfigure command
> >>
> >> >> asDefault=""/>
> >> Creates a new task
> >>
> >>
> >>
> >> >> interfacekind="info.interface"
> >> ip="info.ip"
> >> sessionid="info.session"
> >> user="info.user"
> >> computer="info.computer"/>
> >>
> >> Gets information about the current session
> >> [echoproperties] #Ant properties
> >> [echoproperties] #Mon May 22 09:46:33 CEST 2006
> >> [echoproperties] info.interface=Command Interface
> >> [echoproperties] info.user=mat
> >> [echoproperties] info.session=1707
> >> [echoproperties] info.ip=130.11.36.89
> >> [echoproperties] info.db=/rzf/db/skm/ccm_databases/uebungen
> >> [echoproperties] info.computer=nb011689
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Checks for a give role (task and condition)
> >>
> >>
> >> Stores the object version of a given file in a property.
> >Optional default
> >> value if not under CM control.
> >>
> >> >detailed="">
> >> >prefix="https://myJira.org/browse/
> >> "/>
> >>
> >> Creates a changelist by getting all completed tasks of a release. The
> >> result is a text or xml file with release name and task synopsis. If
> >> "detailed" with their documentations too. A XSL could
> >transform that into
> >> HTML.
> >> >>in="${build.dir}/changes-detailed.xml"
> >>out="${build.dir}/changes.html"
> >> >
> >>
> >><javaresource name="changelist2html.xsl"/>
> >>
> >> >expression="${release.name}/${release.version}"/>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >>
> >> Moving with Synergy.
> >>
> >>
> >>
> >> Checks whether an open Synergy session is available.
> >>
> >>
> >>
> >> >-Ursprüngliche Nac
[patch] absolute filenames in s
I recently proposed a patch for this bug: http://issues.apache.org/bugzilla/show_bug.cgi?id=18128 But there hasn't been any response. Can someone take a look and tell me what you think? Attached is my personal test case, using s to delete. -- Dave Brondsema [EMAIL PROTECTED] http://www.brondsema.net - personal http://www.splike.com - programming - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
seemingly infinite loop in Project class
protected void fireMessageLogged(Project project, String message,
int priority) {
fireMessageLogged(project, message, priority);
}
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: clonevm on
Dominique Devienne wrote: From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] The new clonevm attribute on the task looked like exactly what I needed, but it seems to only clone the built in system properties and not ones specified one the commandline (e.g. ant -Dmyapp.foo=bar). I tried changing BuiltinPropertySetName to "all" didn't work. Never used clonevm, but you might be able to work around this by using a nested . --DD That works great using propertysetref's @prefix, thanks for the suggestion! signature.asc Description: OpenPGP digital signature
clonevm on
The new clonevm attribute on the task looked like exactly what I needed, but it seems to only clone the built in system properties and not ones specified one the commandline (e.g. ant -Dmyapp.foo=bar). I tried changing BuiltinPropertySetName to "all" didn't work. How can this be done? Thanks, -- Dave Brondsema : [EMAIL PROTECTED] http://www.brondsema.net : personal http://www.splike.com : programming http://csx.calvin.edu : student org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ant 1.7. Finding undefined variables
I've been writing a couple of ant build files in which I've defined quite a few variables in an included properties file. A couple of variables within the build.xml too. I keep changing them which results in undefined variables which ant ignores, spreading odd filenames all over the place. I've scratched the itch, wondered if it is of use. Idea: run a python script over any property files to find all defined variables. That generates an ant build file which can be called up from the main build file. run an ~XSL 2.0 stylesheet over the main build file, that generates another ant build file which again can be run from the main build file. Does it sound to be of use to this group? Open source. regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: ant 1.7. Finding undefined variables
2009/5/20 Dominique Devienne : > On Wed, May 20, 2009 at 1:38 PM, Dave Pawson wrote: >> I keep changing them which results in undefined variables which ant >> ignores, spreading odd filenames all over the place. > > What I used to do was use with a nested condition asserting for > some properties to be defined were indeed defined. Aborts the builds > right away if they're missing. That addresses the "Ant ignores > undefined properties" part. As to your idea, I'm not sure I'm > following, sorry. --DD Yes, that's what I generate. Except I run through the properties file and the build file to ensure I get all the (used) properties! As apposed to what I remembered to put in (and didn't change). That's the problem I was addressing, those changes and the odd properties I'd forgotten to test using regards -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: ant 1.7. Finding undefined variables
2009/5/20 Dominique Devienne : > Maybe running in verbose or debug mode and grepping for all property > related messages, especially those about not finding the property, and > convert that into a build similarly to what you did? --DD Yes Possibly. I chose Python and xslt. I gather you don't find it of use then? -- Dave Pawson XSLT XSL-FO FAQ. Docbook FAQ. http://www.dpawson.co.uk - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: ant 1.7. Finding undefined variables
2009/5/20 Dominique Devienne :
> I suggested postprocessing Ant's output as there are can hidden use of
> properties which is not easy to pick up by parsing the Ant XML file
> (they don't look like ${name} in attributes for example), and could
> thus possibly pick up info on more properties.
An example please Dominique?
But yes, for clarity, I am assuming ${name} form. ?Best practice?
regards
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
Re: ant 1.7. Finding undefined variables
2009/5/21 Dominique Devienne :
>> An example please Dominique?
>
> XML elements reading properties without the ${name} notation
>
>
>
> ...
>
> XML elements writing properties affecting the rest of the build:
>
>
>
I've not seen any of those.
Perhaps you could provide me with an example build file I can experiment with?
Below, the xslt script I'm using if you want to play
java -cp saxon9.jar:/myjava:/myjava/xercesImpl.jar
net.sf.saxon.Transform -x:org.apache.xerces.parsers.SAXParser -o $3
$1 $2 $4 $5 $6
regards
http://www.w3.org/1999/XSL/Transform";
xmlns:dp="http://www.dpawson.co.uk/ns#";
xmlns:xs="http://www.w3.org/2001/XMLSchema";
exclude-result-prefixes=" xs"
version="2.0">
http://www.dpawson.co.uk/ns#";>
This stylesheet works with an ant build file file to produce a
ant script which tests all variables within the build file
1.0
2009-05-20T11:15:12Z
DaveP
> ...
>
> In macros with params having default params (or lack thereof, what you
> try to catch), it uses @{name} to differentiate it from property using
> the ${name}. Of course the two can be combined ${...@{bar}} so
> figuring out what property could be missing would replicate the
> running behavior.
>
> These are various reasons looking for ${name} may be insufficient for
> some builds. Nonetheless I agree than looking for ${name} covers a lot
> of ground.
>
> You need to watch out for property helpers though, as
> ${toString:some-ref-id} is a fake property name converting the Java
> object (Ant datatype typically like a path) with reference id
> "some-ref-id" to a string on the fly. (undocumented feature, but
> there's an official API to add custom property helpers for
> ${helper:rest} notation.
>
>> But yes, for clarity, I am assuming ${name} form. ?Best practice?
>
> Using ${name} is how you deref properties in the XML. All I'm saying
> is that property derefs happen in the code as well, and that even
> ${name} can have a different meaning with macros and property helpers
> (the latter is not very common, but the former more so).
>
> But as I said, ${name} covers 90% of the ground, if not more. I just
> wanted to make you aware of the 10% or 5% or 1% you could be missing.
> 90+ % is a good hit rate ;-) --DD
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>
--
Dave Pawson
XSLT XSL-FO FAQ.
Docbook FAQ.
http://www.dpawson.co.uk
-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org
ant with jdk 17
Hi folks, Kind of stumped here, i am testing moving from jdk8 to 17, and have changed my 's task to have attribute target="17". When i do so, i get [javac] javac: invalid target release: 17 [javac] Usage: javac Which is emitted from javac itself. Oddly, if i run ant with -v, i get the raw javac line, and if i copy and paste that raw javac line, it seems to work fine. Anyone have idea what i'm doing wrong? I'm running in linux, all within the same console. -dave - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: ant with jdk 17
Sorry, never mind, i'm a big dummy. ant uses JAVA_HOME. On 4/19/22 12:17, Dave Brosius wrote: Hi folks, Kind of stumped here, i am testing moving from jdk8 to 17, and have changed my 's task to have attribute target="17". When i do so, i get [javac] javac: invalid target release: 17 [javac] Usage: javac Which is emitted from javac itself. Oddly, if i run ant with -v, i get the raw javac line, and if i copy and paste that raw javac line, it seems to work fine. Anyone have idea what i'm doing wrong? I'm running in linux, all within the same console. -dave - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
