Eran,
Woden is a fairly small and simple project and the Ant build works fine. Could you please explain the benefit of using Maven?
I'd prefer to focus on completing the implementation. Perhaps we could defer Maven support until after incubation.
Arthur Ryman,
IBM Software Group, Rational Division
blog: http://ryman.eclipsedevelopersjournal.com/
phone: +1-905-413-3077, TL 969-3077
assistant: +1-905-413-2411, TL 969-2411
fax: +1-905-413-4920, TL 969-4920
mobile: +1-416-939-5063, text: [EMAIL PROTECTED]
| Eran Chinthaka <[EMAIL PROTECTED]>
06/22/2006 03:25 AM
|
|
Hi,
Yesterday I checked out (for the second time) Woden sources and thoughts
of giving some comments on that.
1. Normally the HEAD of the build should be inside the trunk folder. But
I saw the sources are inside a folder called "java". Was this
intentional? Almost all the Apache projects follow the same structure of
having the sources inside the trunk.
2. I saw test resources like wsdl files, xml files were kept inside the
test folder itself. Again from Apache WS project space, we have always
have a separate folder called "test-resources" to hold all the test
resources. Is there any reason behind putting the test sources within
the test folder itself? Don't you its better to have only the test
classes within the test folder and test resources inside the
"test-resources"?
3. I saw there were several zip files getting downloaded to get some
dependency jars. Can we not download the whole zips and only download
the dependent jars? All the dependent jars are available in maven repos.
Since I'm a maven fan, and since its better to have a maven build for
Woden, I wrote the proper maven artifacts to use maven as the additional
build system of Woden.
You can run the goals in the existing ant build file as usual except you
have to prefix your command with maven.
For example, if u were running ant dist, then now you have to run maven
run dist to run thru maven.
I didn't remove the existing ability to use ant as the build system, but
if one doesn't like to use ant (like me), he can use maven without a
problem.
I created a JIRA [1] attaching the patch.
Thanks,
Chinthaka
[1] : http://issues.apache.org/jira/browse/WODEN-36
signature.asc
Description: Binary data
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
