For the Axis 1.x workstream, I'd say -1 to this. As Axis 1.x is a
released product, I am very reluctant to change a process that already
works. It may not be 100% ideal but that's the nature of the OSS beast.
It works.
When the Axis 2.x workstream launches, I'd say we can revisit this
question and see what makes the most sense based on the merits of the
individual technologies.
- James Snell
IBM Emerging Technologies
[EMAIL PROTECTED]
(877) 511-5082 (voice/fax) ** NEW NUMBER **
(700) 930-1979 (t/l) ** NEW NUMBER **
Programming Web Services With SOAP
O'Reilly & Associates, ISBN 0596000952
Have I not commanded you? Be strong and courageous.
Do not be terrified, do not be discouraged, for the Lord your
God will be with you whereever you go. - Joshua 1:9
Dan Diephouse <[EMAIL PROTECTED]>
Sent by: news <[EMAIL PROTECTED]>
03/14/2003 01:28 PM
Please respond to axis-dev
To
[EMAIL PROTECTED]
cc
bcc
Subject
Re: Axis Build System - Possible conversion to Maven
I can see I need to explain about Maven a bit more :).
I understand your worries about converting to maven. You said:
"introducing yet another technology needed to build Axis is not something
I
believe we need to do at this time."
This is exactly my point!!! Maven takes care of all these technologies
for
you!!! It will be the only technology you need once the build conversion
is
through. It automatically takes care of and downloads the dependencies.
All
you need to do is tell maven what dependencies there are in your project
file
like so:
<dependencies>
<dependency>
<id>log4j</id>
<version>1.2.6</version>
</dependency>
<dependency>
<id>jaf:activation</id>
<version>1.0.2</version>
</dependency>
<dependency>
<id>servletapi</id>
<version>2.3</version>
</dependency>
