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 alternative. Is this possible? If yes, does anyone know the steps one needs to do to get this done? Cheers Sharat Chandran "Some is not a number, Soon is not a time"
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 -diagnostics for that. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Include ANT_HOME location in "ant -version" ?
We ought to update the manual (in particular [1]) and make [2] (especially "ant -diagnostics") much more prominent. Gintas [1] https://ant.apache.org/manual/feedback.html [2] https://ant.apache.org/manual/install.html#Troubleshooting 2018-04-19 15:41 GMT+00:00 Jaikiran Pai <jai.forums2...@gmail.com>: > 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 printed from. Any > thoughts? > > [1] https://www.mail-archive.com/user@ant.apache.org/msg42757.html > > -Jaikiran > > > - > To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org > For additional commands, e-mail: dev-h...@ant.apache.org > >
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 printed from. Any thoughts? [1] https://www.mail-archive.com/user@ant.apache.org/msg42757.html -Jaikiran - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Version
On 2013-12-10, at 0:18, Stefan Bodewig bode...@apache.org 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. My concern is IDE integration which might start Ant differently and bypass Main so the static methods on Main don't work properly. Andre-John's contribution made me look at the implementation again and since the methods are static and only rely on ther version.txt file being present, I no longer see a problem. An implementation outside of Main wouldn't look any different and I highly doubt an IDE integration would remove the Main class completely. Stefan Thanks for the insight. At the same time your original comment got me thinking about class dependencies on whether it would make better architectural sense to have a class that represents the application's environment, to avoid any potential two way dependencies with Main? Andre-John - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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:08 PM, Andre-John Mas andrejohn@gmail.comwrote: 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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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 gudnabr...@gmail.com wrote: 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:08 PM, Andre-John Mas andrejohn@gmail.comwrote: 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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Version
Looks like Main.getAntVersion() is your friend. Matt On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas andrejohn@gmail.comwrote: 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 gudnabr...@gmail.com wrote: 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:08 PM, Andre-John Mas andrejohn@gmail.com wrote: 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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Version
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. André-John Sent from my phone. Envoyé depuis mon téléphone. On Dec 9, 2013, at 15:56, Matt Benson gudnabr...@gmail.com wrote: Looks like Main.getAntVersion() is your friend. Matt On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas andrejohn@gmail.comwrote: 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 gudnabr...@gmail.com wrote: 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:08 PM, Andre-John Mas andrejohn@gmail.com wrote: 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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Version
Do you have a link to that discussion? I'd be interested to catch up the context here. Thanks, Matt On Mon, Dec 9, 2013 at 3:01 PM, Andre-John Mas andrejohn@gmail.comwrote: 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. André-John Sent from my phone. Envoyé depuis mon téléphone. On Dec 9, 2013, at 15:56, Matt Benson gudnabr...@gmail.com wrote: Looks like Main.getAntVersion() is your friend. Matt On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas andrejohn@gmail.com 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 Sent from my phone. Envoyé depuis mon téléphone. On Dec 9, 2013, at 14:23, Matt Benson gudnabr...@gmail.com wrote: 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:08 PM, Andre-John Mas andrejohn@gmail.com wrote: 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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Version
Covered in this ticket: https://issues.apache.org/bugzilla/show_bug.cgi?id=55489 On 9-Dec-2013, at 17:00, Matt Benson wrote: Do you have a link to that discussion? I'd be interested to catch up the context here. Thanks, Matt On Mon, Dec 9, 2013 at 3:01 PM, Andre-John Mas andrejohn@gmail.comwrote: 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. André-John Sent from my phone. Envoyé depuis mon téléphone. On Dec 9, 2013, at 15:56, Matt Benson gudnabr...@gmail.com wrote: Looks like Main.getAntVersion() is your friend. Matt On Mon, Dec 9, 2013 at 2:50 PM, Andre-John Mas andrejohn@gmail.com 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 Sent from my phone. Envoyé depuis mon téléphone. On Dec 9, 2013, at 14:23, Matt Benson gudnabr...@gmail.com wrote: 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:08 PM, Andre-John Mas andrejohn@gmail.com wrote: 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 limited to the 'long' version. Some possibilities I am thinking of going forward: - Version class - AntRuntime class Does anyone else have suggestions or preferences as to the best way going forward? André-John Sent from my phone. Envoyé depuis mon téléphone. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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 differently and bypass Main so the static methods on Main don't work properly. Andre-John's contribution made me look at the implementation again and since the methods are static and only rely on ther version.txt file being present, I no longer see a problem. An implementation outside of Main wouldn't look any different and I highly doubt an IDE integration would remove the Main class completely. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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 Main.getVersion() both returning a long version string of them form: Apache Ant(TM) version 1.9.3alpha compiled on November 22 2013 From what I can see there is no method to get a 'short' version, unless I am not looking in the right place. If there isn't already something, would adding a Main.getShortVersion() be acceptable? Regards Andre - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Short version of the ant version string?
Hello Andre, yes, adding a Main.getShortVersion() would be acceptable. are you after a version string containing only digits and dots like what AntVersion.getVersion() is computing ? The version from version.txt sometimes has an alphabetic suffix like 1.7.0beta or 1.9.0alpha 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 string in the user-agent (Apache Ant/0.0), but using the following: getProject().getProperty(MagicNames.ANT_VERSION) or Main.getVersion() both returning a long version string of them form: Apache Ant(TM) version 1.9.3alpha compiled on November 22 2013 From what I can see there is no method to get a 'short' version, unless I am not looking in the right place. If there isn't already something, would adding a Main.getShortVersion() be acceptable? Regards Andre - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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: getProject().getProperty(MagicNames.ANT_VERSION) or Main.getVersion() both returning a long version string of them form: Apache Ant(TM) version 1.9.3alpha compiled on November 22 2013 From what I can see there is no method to get a 'short' version, unless I am not looking in the right place. You may want to look at the antversion Task which strips the alpha designators and all that. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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 versions, or do I just need to test it to see if it works? Thanks. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
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 in the changelog. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Plugins - ant version compatibility
Jesse Glick jesse.glick at 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 specific incompatibilities ought to be mentioned in the changelog. I should have qualified my question a bit better. I have a set of Ant listeners that I need to make sure works from version to version. - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
Re: Ant Plugins - ant version compatibility
On Mon, Jun 20, 2011 at 10:02 AM, Michael Nellis mrnel...@us.ibm.com wrote: Jesse Glick jesse.glick at 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 specific incompatibilities ought to be mentioned in the changelog. I should have qualified my question a bit better. I have a set of Ant listeners that I need to make sure works from version to version. These should always work with later versions. The Ant developers take backward compatibility very seriously, in preference to probably any other concern. Matt - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-mail: dev-h...@ant.apache.org
[PATCH] Expose just the Ant version String
Hi,
This is a very simple patch which will allow Tasks to determine the
version of Ant they are being run in.
This is especially useful for knowing which methods on Project are
available.
e.g.
public void log(String message, Throwable throwable, int
msgLevel) et al
are only available @since 1.7.
Cheers,
Nick Pellow
Index: src/main/org/apache/tools/ant/Main.java
===
--- src/main/org/apache/tools/ant/Main.java (revision 675106)
+++ src/main/org/apache/tools/ant/Main.java (working copy)
@@ -929,6 +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: X.Y.Z for any X,Y,Z integer values
+ * and allows a lexicographical comparison of Ant versions.
+ * @return the ant version
+ */
+public static String getVersion() {
+return version;
+}
+/**
* Returns the Ant version information, if available. Once the information
* has been loaded once, it's cached and returned from the cache on future
* calls.
@@ -949,7 +964,8 @@
StringBuffer msg = new StringBuffer();
msg.append(Apache Ant version );
-msg.append(props.getProperty(VERSION));
+version = props.getProperty(VERSION);
+msg.append(version);
msg.append( compiled on );
msg.append(props.getProperty(DATE));
antVersion = msg.toString();
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 41654] New: - 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 http://issues.apache.org/bugzilla/show_bug.cgi?id=41654. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/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 Component: Core AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] I downloaded ant 1.7.0 from http://apache.ziply.com/ant/binaries/apache-ant-1.7.0-bin.zip unzipped and tried execute: ant -version it returns: Apache Ant version 1.6.5 compiled on June 2 2005 this is misleading, I tried to download it once again, just to be sure I really installed ant 1.7.0. -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 http://issues.apache.org/bugzilla/show_bug.cgi?id=41654. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=41654 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||INVALID --- Additional Comments From [EMAIL PROTECTED] 2007-02-19 01:34 --- You need to set ANT_HOME (or unset it) -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40959] New: - ant -version returns wrong version (1.6.5)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40959. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/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: Core AssignedTo: dev@ant.apache.org ReportedBy: [EMAIL PROTECTED] -- Configure bugmail: http://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 40959] - ant -version returns wrong version (1.6.5)
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40959. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=40959 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- 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 bug, or are watching the assignee. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DO NOT REPLY [Bug 40959] - ant -version returns wrong version (1.6.5)
Hello Peter, this bug report had frightened me ... :-( Good that this is a red herring. Antoine [EMAIL PROTECTED] wrote: DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG· RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://issues.apache.org/bugzilla/show_bug.cgi?id=40959. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND· INSERTED IN THE BUG DATABASE. http://issues.apache.org/bugzilla/show_bug.cgi?id=40959 [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||WORKSFORME --- Additional Comments From [EMAIL PROTECTED] 2006-11-13 11:53 --- Tested and ant -version gives the correct result. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24435] - Trailing space on Ant-Version key in MANIFEST
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24435. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24435 Trailing space on Ant-Version key in MANIFEST [EMAIL PROTECTED] changed: What|Removed |Added Status|NEW |RESOLVED Resolution||FIXED --- Additional Comments From [EMAIL PROTECTED] 2003-11-21 15:07 --- Should be fixed in next ant 1.6 beta build - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 be Peter? I could use a new beta myself... --DD - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
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 [mailto:[EMAIL PROTECTED]
The macrodef attribute issue(s) and local issue(s) need
to be resolved first
What issues ;-) We need local, in one form or another, and just do a final
vote for the macrodef attribute, with a dead line, and tally the (binding)
votes. I'll use whatever's voted on and implemented, be it my preferred
[EMAIL PROTECTED], or @{x}, or whatever. Too few committers chimed in on this
vote
IMHO...
The sooner 1.6 gets out the door (or a beta), the better!
At least for me that is. --DD
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 24435] New: - Trailing space on Ant-Version key in MANIFEST
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT http://nagoya.apache.org/bugzilla/show_bug.cgi?id=24435. ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND INSERTED IN THE BUG DATABASE. http://nagoya.apache.org/bugzilla/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: Enhancement Priority: Other Component: Build Process AssignedTo: [EMAIL PROTECTED] ReportedBy: [EMAIL PROTECTED] When building a J2ME jar file using version 1.5.4, Ant adds a key to the MANIFEST file as follows.. Ant-Version: Apache Ant 1.5.4 The above entry ends with a SPACE charactor. This apparently is problematic for some of the mobile phone opperators. Ant uses a file called defaultmanifest.mf to store the base for producing the manifest. The problem can be fixed by altering this file. This problem appears to be in other versions of Ant also. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
DO NOT REPLY [Bug 17684] New: - Ant version 1.5.1 jar with update option behaves diff from 1.4.1
DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
http://nagoya.apache.org/bugzilla/show_bug.cgi?id=17684.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND
INSERTED IN THE BUG DATABASE.
http://nagoya.apache.org/bugzilla/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 NT/2K
Status: NEW
Severity: Normal
Priority: Other
Component: Core tasks
AssignedTo: [EMAIL PROTECTED]
ReportedBy: [EMAIL PROTECTED]
I had a task that looks like this.
target name=UpdateJarFile
jar jarfile=${JAR_DIR}/${APP_NAME}/${CLIENT_JAR_NAME}
basedir=${APP_SRC_DIR}/${CLIENT_PROJECT_NAME}/bin includes=**/*.class
update=true/
/target
I call this task as
ant inheritAll=true antfile=build.xml target=UpdateJarFile
property name=CLIENT_PROJECT_NAME
value=BuildReport/
/ant
It works fine with 1.4.1
When I try the same job with 1.5.1 it doesnot do an update. It says omitting
becacuse the target jar is updated. Is this a bug or the behaviour of jar with
upadte option has changed between 1.4.1 and 1.5.1
