Ant Version

Hi, I recently made a code contribution and had the task get the version from the Main class. I appreciate this probably want the best approach and I am trying to consider options going forward. I had looked at the ant.version property, but the is only available in the project scope and also li

Re: Ant Version

Are you looking for compatibility with the version? I.e., this task will work on versions >= n? A commonly taken approach there is to use the presence of some particular class introduced in the target version, rather than fiddling with version numbers per se. HTH, Matt On Mon, Dec 9, 2013 at 1

Re: Ant Version

Hi, This was the Get Task, whereby I was getting the ant version for use in the user-agent response. I am using the value uninterpreted. André-John Sent from my phone. Envoyé depuis mon téléphone. > On Dec 9, 2013, at 14:23, Matt Benson wrote: > > Are you looking for compatibi

Re: Ant Version

Looks like Main.getAntVersion() is your friend. Matt On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas wrote: > Hi, > > This was the Get Task, whereby I was getting the ant version for use in > the user-agent response. I am using the value uninterpreted. > > André-John >

Re: Ant Version

gt; Looks like Main.getAntVersion() is your friend. > > Matt > > > On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas wrote: > >> Hi, >> >> This was the Get Task, whereby I was getting the ant version for use in >> the user-agent response. I am using the value un

Re: Ant Version

> > > On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas >wrote: > > > >> Hi, > >> > >> This was the Get Task, whereby I was getting the ant version for use in > >> the user-agent response. I am using the value uninterpreted. > >> > >> A

Re: Ant Version

voyé depuis mon téléphone. >> >>> On Dec 9, 2013, at 15:56, Matt Benson wrote: >>> >>> Looks like Main.getAntVersion() is your friend. >>> >>> Matt >>> >>> >>> On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas

Re: Ant Version

On 2013-12-09, Andre-John Mas wrote: > It is what I used and how the patch was accepted, but since I was told > it wasn't ideal I wanted to see if there were ways to deal with this > going forward. It was me who said it wasn't ideal. My concern is IDE integration which might start Ant differentl

Re: Ant Version

On 2013-12-10, at 0:18, Stefan Bodewig wrote: > On 2013-12-09, Andre-John Mas wrote: > >> It is what I used and how the patch was accepted, but since I was told >> it wasn't ideal I wanted to see if there were ways to deal with this >> going forward. > > It was me who said it wasn't ideal. M

Ant Plugins - ant version compatibility

I am investigating how to determine whether an Ant plugin, built with Ant 1.8.1, will work with Ant 1.8.2. Is there a statement that indicates that this is supported, or is there a requirement that an Ant plugin must be compiled with 1.8.2 in order to work, and will then work with past versio

Include ANT_HOME location in "ant -version" ?

In context of this[1] and many similar questions/confusion previously, I am wondering if our "ant -version" output should even include, a line in the output, the location which is used as ANT_HOME? That will probably make it clearer and easy to understand where it's being pri

Re: Ant Plugins - ant version compatibility

On 06/20/2011 09:40 AM, Michael Nellis wrote: I am investigating how to determine whether an Ant plugin, built with Ant 1.8.1, will work with Ant 1.8.2. Do you mean an Ant task? Generally it should work this (not the reverse of course), though specific incompatibilities ought to be mentioned i

Re: Ant Plugins - ant version compatibility

Jesse Glick oracle.com> writes: > > On 06/20/2011 09:40 AM, Michael Nellis wrote: > > I am investigating how to determine whether an Ant plugin, > > built with Ant 1.8.1, will work with Ant 1.8.2. > > Do you mean an Ant task? Generally it should work this (not the reverse of course), though spec

Re: Ant Plugins - ant version compatibility

On Mon, Jun 20, 2011 at 10:02 AM, Michael Nellis wrote: > Jesse Glick oracle.com> writes: >> >> On 06/20/2011 09:40 AM, Michael Nellis wrote: >> > I am investigating how to determine whether an Ant plugin, >> > built with Ant 1.8.1, will work with Ant 1.8.2. >> >> Do you mean an Ant task? General

Short version of the ant version string?

Hi, As part of my work on issue 55489, "Allow specifying of alternative user agent for the 'get' task", I need to be able to include the Ant version string in the user-agent (Apache Ant/0.0), but using the following: getProject().getProperty(MagicNames.ANT_VERSION) or Mai

Re: Include ANT_HOME location in "ant -version" ?

In context of this[1] and many similar questions/confusion previously, I > am wondering if our "ant -version" output should even include, a line in > the output, the location which is used as ANT_HOME? That will probably make > it clearer and easy to understand where it's being

Re: Include ANT_HOME location in "ant -version" ?

On 2018-04-19, Jaikiran Pai wrote: > In context of this[1] and many similar questions/confusion previously, > I am wondering if our "ant -version" output should even include, a > line in the output, the location which is used as ANT_HOME? I'd prefer -diagn

[PATCH] Expose just the Ant version String

+929,21 @@ private static String antVersion = null; /** + * The version string, as defined by the VERSION property in version.txt. + */ +private static String version = null; + +/** + * Returns just the ant version String. + * + * This will be generally of the form

Re: Short version of the ant version string?

a" or "1.9.0rc1". Regards, Antoine On Nov 22, 2013, at 9:18 PM, Andre-John Mas wrote: > Hi, > > As part of my work on issue 55489, "Allow specifying of alternative user > agent for the 'get' task", I need to be able to include the Ant version > s

Re: Short version of the ant version string?

On 2013-11-23, Andre-John Mas wrote: > As part of my work on issue 55489, "Allow specifying of alternative user > agent for the 'get' task", I need to be able to include the Ant version > string in the user-agent (Apache Ant/0.0), but using the following

jsch to apache mina for sshexec - Ant version 1.9.6 to 1.10.1

Hello, We use ant internally in our build systems and heavily use sshexec/scp and ssh tasks. These rely on jsch which is an external library. Now that there is Apache Mina is there a way to move away from jsch to apache mina? Jsch project is not very active, so we were looking for an alterna

DO NOT REPLY [Bug 40959] - ant -version returns wrong version (1.6.5)

SFORME --- Additional Comments From [EMAIL PROTECTED] 2006-11-13 11:53 --- Tested and ant -version gives the correct result. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the b

DO NOT REPLY [Bug 40959] New: - ant -version returns wrong version (1.6.5)

gzilla/show_bug.cgi?id=40959 Summary: ant -version returns wrong version (1.6.5) Product: Ant Version: 1.7.0RC1 Platform: Other OS/Version: other Status: NEW Severity: normal Priority: P2 Component

Re: DO NOT REPLY [Bug 40959] - ant -version returns wrong version (1.6.5)

hat|Removed |Added > > Status|NEW |RESOLVED > Resolution||WORKSFORME > > > > > --- Additional Comments From [EMAIL PROTECTED] 2006-11-1

DO NOT REPLY [Bug 41654] - "ant -version" returns wrong version for Ant 1.7.0

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT . ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bu

DO NOT REPLY [Bug 24435] - Trailing space on Ant-Version key in MANIFEST

gzilla/show_bug.cgi?id=24435 Trailing space on Ant-Version key in MANIFEST [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 41654] New: - "ant -version" returns wrong version for Ant 1.7.0

gzilla/show_bug.cgi?id=41654 Summary: "ant -version" returns wrong version for Ant 1.7.0 Product: Ant Version: 1.7.0 Platform: Other OS/Version: Linux Status: NEW Severity: major Priority: P2

DO NOT REPLY [Bug 24435] New: - Trailing space on Ant-Version key in MANIFEST

gzilla/show_bug.cgi?id=24435 Trailing space on Ant-Version key in MANIFEST Summary: Trailing space on Ant-Version key in MANIFEST Product: Ant Version: 1.5.4 Platform: PC OS/Version: Other Status: NEW Severity: Enhan

RE: DO NOT REPLY [Bug 24435] - Trailing space on Ant-Version ke y in MANIFEST

> -Original Message- > --- Additional Comments From [EMAIL PROTECTED] > Should be fixed in next ant 1.6 beta build And when would that be Peter? I could use a new beta myself... --DD - To unsubscribe, e-mail: [EMAIL P

Re: DO NOT REPLY [Bug 24435] - Trailing space on Ant-Version ke y in MANIFEST

The macrodef attribute issue(s) and local issue(s) need to be resolved first On Friday 21 November 2003 15:10, Dominique Devienne wrote: > > -Original Message- > > --- Additional Comments From [EMAIL PROTECTED] > > Should be fixed in next ant 1.6 beta build > > And when would that

RE: DO NOT REPLY [Bug 24435] - Trailing space on Ant-Version ke y in MANIFEST

> On Friday 21 November 2003 15:10, Dominique Devienne wrote: > > > -Original Message- > > > --- Additional Comments From [EMAIL PROTECTED] > > > Should be fixed in next ant 1.6 beta build > > > > And when would that be Peter? I could use a new beta myself... --DD > > From: peter reilly

DO NOT REPLY [Bug 17684] - Ant version 1.5.1 jar with update option behaves diff from 1.4.1

gzilla/show_bug.cgi?id=17684 Ant version 1.5.1 jar with update option behaves diff from 1.4.1 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RE

DO NOT REPLY [Bug 17684] New: - Ant version 1.5.1 jar with update option behaves diff from 1.4.1

gzilla/show_bug.cgi?id=17684 Ant version 1.5.1 jar with update option behaves diff from 1.4.1 Summary: Ant version 1.5.1 jar with update option behaves diff from 1.4.1 Product: Ant Version: 1.5.1 Platform: PC OS/Version: Windows