For many Apache means the httpd server, when in fact this is just one
sub-project (like Ant).
So when you're looking for docs you want the HTTPD project.
Barry
Frank Arensmeier wrote:
Thank you all! You made my day.
2005-09-26 kl. 10.25 skrev Jon McLennan:
I'm sure you'll find the list you
try this link:
http://httpd.apache.org/lists.html
Barry
Frank Arensmeier wrote:
... and the address would be...? Honestly, I feel lost. I can't find a
general apache mailing list. Is httpd.apache.org a good idea? Monday
morning, what else can i say?
/frank
2005-09-26 kl. 10.00 skrev Nicolas
Hi Nicolas,
how about controlling the version number in the build?
then update the version in the source file on every build:
and then compile and use ${version} to name the jar?
Barry
Nicolas Vervelle wrote:
Hi,
In one of my Java source file, I have a line like this:
mp, in the same directory..
Barry White wrote:
Hi Aydin,
try putting the servlet (J2EE) classes in the classpath for the javac
task. The following page shows you how to do this under references (it
should look familiar):
http://ant.apache.org/manual/using.html
Barry
Aydın Toprak wr
Hi Aydin,
try putting the servlet (J2EE) classes in the classpath for the javac
task. The following page shows you how to do this under references (it
should look familiar):
http://ant.apache.org/manual/using.html
Barry
Aydın Toprak wrote:
hii everybody,
I am newbie about ant I am having
Hi Andy,
are you just trying to ensure that your sources will compile to be, say,
1.3 compliant? This was a problem that I faced for a while and I believe
it was solved on this mailing list. I thought specifying
source/target=1.3 should or would be enough but it is not - you have to
specify t
When you invoke ant with no arguments, it looks for a file called
build.xml in the working directory. So build.xml needs to come out of
common and into the working directory. The relaitive paths that you have
in the javac task are correct if the build file is up one level (working
dir).
Try t
Is your problem that you have set it to true/on and it does not seem to
be having any effect? If so have you specified debuglevel also? I was
just having a quick look at the docs for javac task:
"If set to true, the value of the debuglevel attribute determines the
command line argument."
Bar
Your build assumes that smtp.gmail.com is waiting for insecure
connections on the standard smtp port. As far as I know, for
smtp.gmail.com, you need to use port 587 with TLS enabled. Looking at
the docs you will need JavaMail in you classpath too. Try:
hi all:
I want to send a mail use ant
Have you looked at writing cutom ant tasks? It maye help to handle some
of the messier details.
Barry
Scott Bell wrote:
Problem statement:
I have a number of simple tcl scripts, and they take a set number of
params as input (argv). Usually 1-10 params. They can all run
standalone, but ha
Good point...
you also have to keep an eye over your shoulder ;)
Steve Loughran wrote:
Barry White wrote:
Hi Mark,
not really an answer to your question but two solutions to this
problem that I have used before:
- pass the variable in on the command line (ant -Dpassword:x)
that
Hi Mark,
not really an answer to your question but two solutions to this problem
that I have used before:
- pass the variable in on the command line (ant -Dpassword:x)
- use a properties file but only keep an example of the file under
version control (project.properties.example)
Barry
12 matches
Mail list logo
