On 2008-11-14, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
> I am not sure of how are used the "Resource" in the Ant code, but it
> makes me think of the Eclipse adapters (probably a design pattern ?):
> http://www.jeffreyricker.com/papers/Eclipse-Adapters.pdf
Sounds reasonable.
> Though it chang
On 2008-11-15, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> The only workaround.I found is :
> ant -lib build/classes\;build/test-classes test
I use two -libs, but otherwise I do exactly the same.
Stefan
-
To unsubscribe, e-mai
Stefan Bodewig a écrit :
On 2008-11-14, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
I am not sure of how are used the "Resource" in the Ant code, but it
makes me think of the Eclipse adapters (probably a design pattern ?):
http://www.jeffreyricker.com/papers/Eclipse-Adapters.pdf
Sounds
On Tue, Nov 11, 2008 at 12:49 PM, Nicolas Lalevée
<[EMAIL PROTECTED]> wrote:
>
> Le 11 nov. 08 à 11:49, Scheper, Erik-Berndt a écrit :
>
>> Well, 'qxo' is definitely not me (or I would know how to reproduce
>> IVYDE-130 ;-)
>
> ok :)
>
>>
>> And I agree with your comment on IVYDE-128. Personally I
On Mon, Nov 10, 2008 at 11:15 PM, Nicolas Lalevée
<[EMAIL PROTECTED]> wrote:
> I would like to discuss about the next release of IvyDE.
>
> The last release of IvyDE was made 4 months ago, there are some important
> bug fixes that make IvyDE a lot more stable, so I think it is a good time to
> get
Hi all,
while trying to be able to write a decorator for Resource while
allowing the decorator to provide Touchable, Appendable and
FileProvider if the wrapped resource does, I took much inspiration
from Bruce and Nicolas and added the floowing method to the Resource
class
/**
* Returns
On 2008-11-17, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
> Stefan Bodewig a écrit :
>> On 2008-11-14, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
>>> But I see another solution, quite different. Probably most of the work
>>> should be done in the Resource class:
>> I thought about that, but Res
I find that Ant will output detail error information when a ill-form
build.xml is presented, even when build.xml isn’t a valid xml file. But
when I use other package to parse XML files, I can’t get detail error
message just like which Ant generate. Following is a test file, which
contains only thre
Stefan Bodewig a écrit :
On 2008-11-17, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
Stefan Bodewig a écrit :
On 2008-11-14, Nicolas Lalevée <[EMAIL PROTECTED]> wrote:
But I see another solution, quite different. Probably most of the work
should be done in the Resource clas
Ant uses a SAX parser, not a DocumentBuilder (see
javax.xml.parsers,SAXParser), this alone may explain the difference.
It will use whatever JAXP provides, but Ant ships with a pretty recent
version of Apache Xerces.
Finally, the error message you cite comes from Ant, not the parser.
If the docume
Also sax is stream based - so the first errors that
ant would see would be the fact that the first element is
not "project" the malformed xml document would
not be noticed at this stage as processing of the
document would stop.
Peter
On Mon, Nov 17, 2008 at 3:46 PM, Stefan Bodewig <[EMAIL PROT
11 matches
Mail list logo
