> > Strange that there are deprecated warnings even on 1.3 ...
> > But the build works :)
>
> I'm pretty sure that the tests don't though :(
Java 1.3 ...
build ...
build test
[junit] Testcase:
testHasErrorInCase(org.apache.tools.ant.util.FileUtilsTest): FAILED
[junit] null
[junit] junit.fr
On Jan 16, 2008 8:54 AM, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> 2008/1/15, Louis Tribble <[EMAIL PROTECTED]>:
> >
> > Dominique Devienne wrote:
> > > On 1/15/08, Louis Tribble <[EMAIL PROTECTED]> wrote:
> > >
> > >> Consequently, my main comment (apologies if I missed it in the
> thread)
> >
On Jan 16, 2008 10:28 AM, Steve Loughran <[EMAIL PROTECTED]> wrote:
> Peter Reilly wrote:
>
> > I do not think we should do this.
> > As far as I know, there is no super compelling reason to make ant only
> > work on java 1.4 +,
>
>
> I was curious as it is a lot easier to do relative URLs with the
Peter Reilly wrote:
I do not think we should do this.
As far as I know, there is no super compelling reason to make ant only
work on java 1.4 +,
I was curious as it is a lot easier to do relative URLs with the
java.net.URI class, which is java 1.4+ only
java5, on the other hand
we s
I was just saying that Ant benefits/(or suffer...) from great flexibility, and
you should not change that.
Things like the declarative nature of the targets and global properties
participate to this flexibility.
The fact that you can overwrite target is also a good support for flexibility.
I
Hey,
I've been working on refactoring some code to make it easier to
implement relative resources in things like the import task.
After looking at BaseDef and AntLibDefinition, it seemed that it was a
bit backwards and AntlibDefinition should actually extend a base class
that provides basic class
On 1/16/08, Gilles Scokart <[EMAIL PROTECTED]> wrote:
> I was just saying that Ant benefits/(or suffer...) from great flexibility,
> and you should not change that. [...]
I agree with Xavier, control in large build system is a very desirable
feature, if only to force developers to talk to the buil
Thanks,
if I run:
build.sh - everything is fine.
build.sh test - run after the first build, I still get the FileNotFound
error.
For some reason FailedTests.java is never being created.
I guess I could comment out the collector for now, but that seems a
little weird.
- Jonathan
On Wed, 2008-01-1
Hi,
I have a question about the Ivy API. In IvyDE, to compute the classpath there
is:
ResolveReport r = _ivy.resolve(ivyURL, new ResolveOptions().setConfs(_confs));
all.addAll(Arrays.asList(r.getAllArtifactsReports()));
But it seems that the download reports contains also the evicted modules :
On Jan 16, 2008 4:07 PM, Nicolas Lalevée <[EMAIL PROTECTED]>
wrote:
> Hi,
>
> I have a question about the Ivy API. In IvyDE, to compute the classpath
> there
> is:
>
> ResolveReport r = _ivy.resolve(ivyURL, new
> ResolveOptions().setConfs(_confs));
> all.addAll(Arrays.asList(r.getAllArtifactsRepor
jonathan doklovic wrote:
Hey,
I've been working on refactoring some code to make it easier to
implement relative resources in things like the import task.
After looking at BaseDef and AntLibDefinition, it seemed that it was a
bit backwards and AntlibDefinition should actually extend a base clas
Well,
For now, since the relative path stuff should be going into
ResourceFactory, I'll create a new base class that simply checks for
name, classname, resource, classpath, and loadrref args and returns a
JavaResource using the ResourceFactory. I'll use this as the base for
the new import task to a
I know its been discussed before, but I'd to raise the idea again:
moving to JIRA for reporting
putting aside the main feature for end users -a better UI- what I like
about using at work is
- automatic polling of SVN and building of a change log from keywords
like SFOS-123
http://jira.sm
On 1/16/08, Steve Loughran <[EMAIL PROTECTED]> wrote:
> I know its been discussed before, but I'd to raise the idea again:
> moving to JIRA for reporting
I know it's GMail's fault, but with bugzilla threading in GMail works
most of the time, whereas it's quite broken with JIRA, and that's a
PITA I
On Jan 16, 2008 5:25 PM, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
> I know its been discussed before, but I'd to raise the idea again:
> moving to JIRA for reporting
>
> putting aside the main feature for end users -a better UI- what I like
> about using at work is
>
> - automatic polling of SV
I use gmail, and find the JIRA conversation per message a mess.
I would be -1 until this has been resolved.
Peter
On Jan 16, 2008 4:47 PM, Xavier Hanin <[EMAIL PROTECTED]> wrote:
> On Jan 16, 2008 5:25 PM, Steve Loughran <[EMAIL PROTECTED]> wrote:
>
> >
> > I know its been discussed before, but
Dominique Devienne wrote:
On 1/16/08, Gilles Scokart <[EMAIL PROTECTED]> wrote:
I was just saying that Ant benefits/(or suffer...) from great flexibility,
and you should not change that. [...]
I agree with Xavier, control in large build system is a very desirable
feature, if only to fo
I was +1 on this before, and I am +1 now, particularly since Ivy uses
it. But the objection that others have concerning threading when reading
with GMail is a fair reason for vetoing again, as happened before.
I've filed a bug report with Google on their lack of support for
observing the In-Re
Yes, I filed it too some time ago. I do not see them fixing it.
- Alexey.
On Jan 16, 2008 11:42 AM, Bruce Atherton <[EMAIL PROTECTED]> wrote:
> I was +1 on this before, and I am +1 now, particularly since Ivy uses
> it. But the objection that others have concerning threading when reading
> with
Peter Reilly wrote:
There are a woe-full amount of java 1.3 users as well..
Peter
And of 1.2 users that we abandoned during the 1.7 release. But the
thinking at that time, and I think it holds up here as well, is that if
those users are too conservative to move beyond a JVM which has now
Just a test
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Jan 17, 2008 12:19 AM, Bruce Atherton <[EMAIL PROTECTED]> wrote:
> Peter Reilly wrote:
> > There are a woe-full amount of java 1.3 users as well..
> >
> > Peter
> >
> >
>
> And of 1.2 users that we abandoned during the 1.7 release. But the
> thinking at that time, and I think it holds up here as
+1,
I found jira much more confortable, and I would like to see ant using the
same bug tracking system than ivy.
Gilles
2008/1/16, Steve Loughran <[EMAIL PROTECTED]>:
>
>
> I know its been discussed before, but I'd to raise the idea again:
> moving to JIRA for reporting
>
> putting aside the mai
23 matches
Mail list logo
