On 2010-05-14, Jesse Glick wrote:
> Would be much easier to manage (and possibly more friendly to IDEs) if
> classes were split into several physical source roots.
I'm not a fan of such a source file set up but wouldn't block it either.
> I would also like a clear explanation of what ant-nodeps
Bruce Atherton wrote:
>
> Just to be clear on point 3:
>
>> 3. Produce the contents of one JAR in the distribution.
>
> That is just to bundle the contents of all the ant-*.jar files
> together into a single ant.jar file, right? Or are you suggesting that
> we release two packages with each release
Hi,
The Apache Software Foundation is organizing an Apache Conference North
America 2010
(ApacheCon NA 2010) [1].
I am forwarding the following message from our Travel Assistance Committee
Antoine
[1] http://na.apachecon.com/c/acna2010/
--
On 15/05/2010 11:34 AM, Bruce Atherton wrote:
Anyway, my point is that if we go for one big jar and include
fetch.xml behaviour in the standard build, then we don't need to break
the source directories apart.
Sorry, I realized that I was conflating the distribution with working
with the sourc
I'm not sure that directly answer your question, but in the trunk of
antunit, there is a tool to plug antunit script into the eclipse (or any
other IDE) Junit runner. That way, you can use your favorite java debugger
to debug antunit script.
But still, your project need to have all the ant depend
