On Fri, Apr 8, 2011 at 2:57 PM, Matt Benson wrote:
>> So yeah, I'm afraid it's by design... A proper was need
>> access to the full infoset provided by the parser, and thus require
>> deeper changes into Ant core to provide that infoset. --DD
>
> EchoXML has, I'm afraid, been a largely unsuccessf
On Fri, Apr 8, 2011 at 1:49 PM, Dominique Devienne wrote:
> On Fri, Apr 8, 2011 at 11:10 AM, Parag Doke
> wrote:
>> Notice that the "text outside the child node" appears before the child
>> node itself, though it was after the child node in the original input to
>> echoxml task.
>
> I vaguely r
Thanks, actually your suggestion led me to find that I can use a
resource using a baseResource of ${ant.file.project-name} with a relative
path of "/foo", and this works well. I too had to create a variation that
could load the same resource using a resource, but it wasn't too
hard. I'll proba
On Fri, Apr 8, 2011 at 11:10 AM, Parag Doke wrote:
> Notice that the "text outside the child node" appears before the child
> node itself, though it was after the child node in the original input to
> echoxml task.
I vaguely recall that when I wrote (Stefan is the one who
introduced it into Ant
Hi,
I'm new with dependency management and I'm trying to download primefaces. In an
ivy file I have this dependency
But the build failed with "org.primefaces#primefaces;1.0.1: configuration not
found in org.primefaces#primefaces;1.0.1: 'provided'..."
I don't understand why, because in pom f
Parag Doke schrieb am 08.04.2011 um 21:40 (+0530):
> Hello ant experts.
> I am trying to use the echoxml task in ant (1.7 / 1.8) but have
> observed a weird thing about the node text.
> Notice that the "text outside the child node" appears before the child
> node itself, though it was after the ch
Hello ant experts.
I am trying to use the echoxml task in ant (1.7 / 1.8) but have
observed a weird thing about the node text. Here is my project file
===
text inside the child node
text outside the child node
===
What I can see in the test_output.xml is:
==
On Fri, Apr 8, 2011 at 9:09 AM, Steele, Richard wrote:
> I've created a reusable set of build files using the technique I outlined at
> http://stackoverflow.com/questions/5124726/what-are-some-good-ways-to-distribute-a-common-ant-file-to-be-included-in-builds/5168745#5168745.
> This technique reli
I've created a reusable set of build files using the technique I outlined at
http://stackoverflow.com/questions/5124726/what-are-some-good-ways-to-distribute-a-common-ant-file-to-be-included-in-builds/5168745#5168745.
This technique relies heavily on Ant 1.8 importing files from the classpath
rathe
Hi Matt no need to apologize for the delay.
I have mixed feelings about re-purposing the "id" attribute to use as the
resource name. To me they're different things: I might want to use the id
for internal use and therefore want to conform to some kind of naming
convention, but I need a different
I created 51044.
Thanks,
Rich
On Tue, Apr 5, 2011 at 8:25 AM, Antoine Levy-Lambert wrote:
> On 4/1/2011 7:51 AM, Steele, Richard wrote:
>
>> As implemented it looks like expands all properties.
>> I'd
>> really like if I could embed a in it to control which
>> properties get expanded.
>>
>>
11 matches
Mail list logo
