Hi Oleg,
>>> Removed all contrib related targets from the Ant build file.
>> And how am I supposed to detect build breaks in contrib code now?
>
> Just do not. I personally do not see the sky come crashing down if the
> contrib stuff is broken temporarily. Those of us who use modern IDEs
> will eventually pick up and fix the breakage.
It is the most frequent, but not the only example where I need
the contrib targets. I need them to review contrib code, I need
them to write contrib code, and I need them to run contrib code
such as your benchmark. That change has effectively locked me
out of the contrib part of our code base.
When I set out to revamp the Ant build files last year, it was
for one reason, and one reason only: to make sure that it has
_all_ the targets I expect of a decent build process, so that I
would not have to maintain a second, extended one locally. Now
you're forcing me back into that situation.
The build files were already prepared to compile contrib code in
the main module when I suggested that move last August.[1] All that
was needed is an update of a single line in module-main/build.xml
defining the base location:
<property name="comp.core.main.contr"
location="${comp.core.home}/src/contrib"/>
<!-- @@@ contrib should be moved to module-main,[...]
If you had replaced ${comp.core.home} with ${comp.core.main.home},
or waited for me to do it, everything should have worked. Instead,
you sift through the build files and rip out everything I had put
in place to make the contrib code accessible in my environment.
This change was utterly destructive. It is not urgent since I won't
be coding anytime soon, but please revert it when you find the time.
cheers,
Roland
[1] http://issues.apache.org/jira/browse/HTTPASYNC-5#action_12429272
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
