Say you have an element like this:
If you want to load that through an XMLFragment and then output it later,
the DOMElementWriter.encode() method doesn't case properly for non-printable
characters.
The quick fix for me in this case was to overload that method and add this:
case
Ok, how do I do the same thing with the war task lib directory?
need to put a reference to my union in here.
jon
On Fri, Jun 25, 2010 at 9:47 AM, Jon Stevens wrote:
> sweet. works like a charm (even though it is a bit non-intuitive). mind if
> i submit a diff to the tar docu
sweet. works like a charm (even though it is a bit non-intuitive). mind if i
submit a diff to the tar documentation page with this example?
jon
On Thu, Jun 24, 2010 at 9:10 PM, Stefan Bodewig wrote:
> On 2010-06-25, Jon Stevens wrote:
>
> > Now, I'd like to reference that Union within a ... so
On 06/25/2010 06:52 AM, jan.mate...@rzf.fin-nrw.de wrote:
Building modules in parallel.
Good luck there... these are only "modules" by fiat; they share some source and target dirs. The include/exclude definitions very likely do not form a disjoint union of
all source files, so I have no idea i
By the way, if you're interested in taking a look at my work, you can find
it here:
http://parallel-ant.googlecode.com/svn/trunk/
On 25 June 2010 11:59, Danny Yates wrote:
> Yes, I nabbed an alternative logger from a similar project :-) Basically,
> it outputs when a target starts and when it f
Yes, I nabbed an alternative logger from a similar project :-) Basically, it
outputs when a target starts and when it finishes, and for each task it
outputs [target/task] instead of just [task] so you can see what's going on.
I can't claim any responsibility for it though!
On 25 June 2010 11:48,
Added the "ignore=true" part as MAVEN_OPTS.
Building modules in parallel.
Abort stuck builds after 30 minutes and let the job fail then.
But haven't found the place for the patternset.
The job is a "Maven2-Job" and AFAIK Hudson retrieves these information only
from the poms, right?
Jan
>-U
btw - when using parallel executors the problem of parallel logging output must
be resolved ;-)
Jan
>-Ursprüngliche Nachricht-
>Von: jan.mate...@rzf.fin-nrw.de [mailto:jan.mate...@rzf.fin-nrw.de]
>Gesendet: Freitag, 25. Juni 2010 12:46
>An: dev@ant.apache.org
>Betreff: AW: [Proposal] C
Other point: we have an implementation in the sandbox
https://svn.apache.org/repos/asf/ant/sandbox/parallelexecutor
Maybe you could use some code ;-)
Jan
>-Ursprüngliche Nachricht-
>Von: Dominique Devienne [mailto:ddevie...@gmail.com]
>Gesendet: Donnerstag, 24. Juni 2010 23:12
>An: An
On 19-6-2010 20:38, Bruce Atherton wrote:
Ant supplies several tasks that require commercial software in order
to run. This is a problem because the Ant developers do not typically
have access to the commercial products required to test, maintain, and
enhance the tasks. It also means that users
On Fri, Jun 25, 2010 at 6:14 AM, Bruce Atherton wrote:
> On 19/06/2010 11:38 AM, Bruce Atherton wrote:
>>
>> 1. Should the following commercial tasks be dropped from being distributed
>> with the Ant release?
>>
>> [ ] Continuous/Synergy tasks: CCMCheckin, CCMCheckout, CCMCheckinTask,
>> CCMRec
11 matches
Mail list logo