Hi,
When I run rexec task it fails with the error "can't connect to ".
I run it in the following way:
I also tried to run the task on other machines but it failed with the same
error.
My machine is windows 2008. The final goal is to run the task from linux
machine on a windows machine.
Any idea
Sorry, been fighting being sick...
However, I don't recall seeing mention of default values... Just the resultant
document has unwanted attributes added...
So, if this is in fact that situation...I'm confused about the posting to this
list... Have you tried to execute your XSLT outside Ant?
Hi Nicolas,
Don't you think the use case I described below makes sense?
Thanks,
Gael
> -Original Message-
> From: Marziou, Gael
> Sent: Thursday, February 12, 2009 3:20 PM
> To: ivy-u...@ant.apache.org
> Subject: RE: IvyDE 2.0.0.beta1 does not download sources nor javadocs
>
>
> >
Hi,
I'm uisng Ant 1.6. I have this target ...
For the property, 'wsdl="${basedir}/wsdl_files/Pr
What about ?
What I normally do is something like this:
That way, I can put the property file name on the command line, or
read in the default property file if it exists.
You can also override any property setting in your build.xml by simply
placing it on the command line:
So do this:
I've found the issue. The SNAPSHOT jars were corrupted. Everything works fine
now that I uploaded working jar files.
daniel.mfreitas wrote:
>
> Hello all. I'm having some issues with Ivy. I installed Artifactory and I
> have my repositories working. I can fetch the repositories by using a
> brow
Thanks for your reply. Regarding the property file directive, "",
where are you actually loading the property "PROVISIONING_SERVICE_WSDL_URL"
from the file and assigning it to a variable?
- Dave
> ---Original Message---
> From: David Weintraub
> Subject: Re: Reading a property fro
> Actually since the version 2.0-RC2, Ivy is handling the
> sources/javadoc declaration for maven pom.xml [1]. So you
> should not have any worries in getting the sources/javadoc of
> an artifact in a maven repository, even proxied.
Great, I did not know.
> Or do you mean that in your case, th
> -Original Message-
> From: Anat [mailto:anat.ba...@gmail.com]
> Sent: Wednesday, February 18, 2009 3:13 AM
> To: user@ant.apache.org
> Subject: rexec task failed with error "can't connect to..."
>
>
> Hi,
> When I run rexec task it fails with the error "can't connect to field value>"
>However, I don't recall seeing mention of default values... Just the
resultant
>document has unwanted attributes added...
>So, if this is in fact that situation...I'm confused about the posting to
this list...
>Have you tried to execute your XSLT outside Ant? If so and the result is
the same..
So, have you tried to run your XSLT outside of Ant? Be interesting to see
if you get the same results...
Ah...gotcha about xmlcatalog :)
On Wed, 18 Feb 2009, Scott Stark wrote:
However, I don't recall seeing mention of default values... Just the
resultant
document has unwanted attribu
>So, have you tried to run your XSLT outside of Ant? Be interesting to see
>if you get the same results...
>Ah...gotcha about xmlcatalog :)
Yeah, getting that to work with Saxon was more than my brain could
handle... couldn't find any good doc about it. Turned out to be easy with
Ant...
Scott
Hi all,
I am trying to publish multiple jars and not having any luck so far.
From what I've read it is possible, but I must be missing some part of
the correct configuration. We have a build that produces 5 different
jar files that are depended on by other builds, so we need to publish
them to ou
Gotcha...
Wish I could be of more help :(
On Wed, 18 Feb 2009, Scott Stark wrote:
So, have you tried to run your XSLT outside of Ant? Be interesting to see
if you get the same results...
Ah...gotcha about xmlcatalog :)
Yeah, getting that to work with Saxon was more than my brain could
Could you also tell us what's going wrong?
Do you get an error?
Maarten
- Original Message
From: Barry Pape
To: ivy-u...@ant.apache.org
Sent: Wednesday, February 18, 2009 11:33:31 PM
Subject: ivy:publish question
Hi all,
I am trying to publish multiple jars and not having any luck s
> -Original Message-
> From: Scott Stark [mailto:sst...@us.ibm.com]
> Sent: Wednesday, February 18, 2009 4:00 PM
> To: Ant Users List
> Subject: Re: Ant XSL: inserting unwanted attributes
>
>
> >So, have you tried to run your XSLT outside of Ant? Be interesting to
> see
> >if you get t
is a task as all others, therefore you can use that everywhere. If
your properties file contains 'just' properties for that generation, placing
the task just in front of the is a good idea.
Usually you have a build.properties with all properties for the build, like
java source directory, javac
17 matches
Mail list logo