On Sat, Oct 28, 2017 at 5:17 PM, R0b0t1 wrote:
> Is it possible to cache compilation results? I would like to avoid
> lengthy compile times after changing one file.
What I do for these situations is have the task create an empty file
which can then be used on subsequent executions for a modtime c
On Sat, Sep 17, 2016 at 5:05 PM, Al Le wrote:
> But sometimes, after the sync, I see that dirs which do not exist on the
> share are not deleted on the local file system. Instead, just the files in
> the dirs are deleted.
>
> I still have not been able to track down when exactly it happens.
Someti
On Mar 7, 2016 7:55 AM, wrote:
>
> If you are using the same JVM and simply executing the XSL differently, I
don't see why not...
If the classpath is not identical, you could get a different transform
provider. For example, we use Saxon as our provider, overriding what is
provided in the runtime
On Mon, Sep 7, 2015 at 5:48 PM, Martin Gainty wrote:
> https://ant.apache.org/manual/Tasks/manifest.html
But you are not using that task, you are trying to define a new task:
>> > > >classname="ManifestVersion"
>> >classpath="..\build_tools.jar" />
>> >
>> > cannot find M
On Tue, Apr 28, 2015 at 8:51 AM, Alan Snyder wrote:
> Why not just postpone issuing the message until a task is attempted
> that needs the JDK?
Agreed.
But I guess it would require updating such tasks since it is likely that
such tasks today will likely just error out by not being able to load a
On Tue, Apr 28, 2015 at 12:12 AM, Jan Matèrne (jhm) wrote:
> Ant is a build tool. For some tasks (for example javac, javadoc) the tools
> from the Java _Development_ Kit are required.
> If you run with just a Java _Runtime_ Environment most of its tasks could be
> used, but not all - hence the war
On Tue, Apr 14, 2015 at 2:21 PM, Chris Barlock wrote:
> Thank you, Steve. If I make the executable="/bin/sh" and uncomment the
> protoc command, I get:
You need the -c option to /bin/sh to indicate it should execute the command
that follows on the argument list.
--ewh
--
On Tue, Apr 14, 2015 at 1:35 PM, Chris Barlock wrote:
> I have the following Ant script:
...
>
Glob expansion is a shell function, hence the error you are getting
since the file "*.proto" does not exist.
Have a look at . It supports filesets.
--ewh
---
On Tue, Mar 17, 2015 at 12:01 PM, Josh Hoff wrote:
> I guess a new question would be: how can I debug the classpath when
> building and testing?
Use the -d option to enable debug logging. You will get a ton of
output, and it is likely the output will contain information you are
interested in.
I
On Mon, Mar 16, 2015 at 7:14 PM, Josh Hoff wrote:
> I'm having an issue where the server (that I don't have control over)
> will have two junit jars in %ANT_HOME%\lib, and I'll pull one down (that
> I do want) with ivy. My tests are failing because of the two in
> %ANT_HOME%\lib conflicting with t
On Tue, Feb 17, 2015 at 2:58 PM, Jeffrey Walton wrote:
>> Use the 'encoding' attribute to the task.
...
> source="${java.source}" target="${java.target}"
> debug="true" extdirs="" includeantruntime="false"
> destdir="${out.c
On Tue, Feb 17, 2015 at 2:11 PM, Jeffrey Walton wrote:
> I'm trying to build an Android project from the command line. I'm
> getting an error during `ant release`. The error is unmappable
> character for encoding UTF-8.
Use the 'encoding' attribute to the task.
--ewh
---
On Thu, Feb 12, 2015 at 7:54 PM, Jackie Xiao wrote:
> The thing is, we need to enable customers to work with us, but we
> don’t want to share the build scripts (I know it’s weird).
Then maybe you should consider using the Ant API directly to set your
tasks and what not, or a different tool entire
On Fri, Dec 5, 2014 at 1:04 PM, Dominique Devienne wrote:
> Strange, I'd have thought the XML parser would choke before you even got to
> running something. > is one of those reserved characters in XML, that must
> be replaced with a "character entity", ">" (w/o the quotes) in this case.
No. A
On Fri, Dec 13, 2013 at 1:55 PM, I wrote:
> When using , if I have a , and the
> dirname portion of the pathname does not exist, uptodate causes a
> project build failure.
...
Nevermind. After digging through Ant source and documentation, I
realized one needs to set the erroronmissingdir="false"
Ant version: 1.8.4
When using , if I have a , and the
dirname portion of the pathname does not exist, uptodate causes a
project build failure.
For example, if the pathname is "C:\Whatever\Directory\file.txt" and
"C:\Whatever\Directory" does not exists, build failure.
There is no problem if the f
On 11/5/13, Dave Westerman wrote:
> I'm passing in an attribute that contains a value to search for in a file
> in Windows. I'm doing this:
>
> resultproperty="retcode"
> outputproperty="output">
>
>
I normally avoid using since some additional parsing is done
by Ant (or t
On Tue, Jun 18, 2013 at 11:54 AM, Bruce Atherton wrote:
> It is fairly trivial to do. In your main jar target:
>
> 1. create a temporary directory
> 2. run the unjar task
> 3. jar up your main jar, including the contents of the temporary
> directory
> 4. delete the temporary directo
I recently upgraded to Ant 1.8.4 from 1.7.1.
I have noticed a problem with how stderr and stdout is handled in 1.8
compared to 1.7.1 for the task. I have something like the
following:
...
The program normally outputs diagnostics to stderr.
I have ant invoked with the -e and -q
19 matches
Mail list logo
