Re: javac task problem in Java 6

2008-11-05 Thread Jesse Glick

Jess Holle wrote:

We've seen this before where A depends on B which /internally/ depends upon C 
and then suddenly one has to have C around to compile A.


Although this is not forbidden by the JLS (as far as I know), it does seem undesirable. If you know of particular examples which can be expressed as minimal test cases, I 
would encourage you to file bug reports for the compiler.



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[ANNOUNCE] Apache Ivy 2.0.0-rc2 released

2008-11-05 Thread Maarten Coene
Nov 4, 2008 - The Apache Ivy project is pleased to announce the
release of Ivy 2.0.0-rc2, the second release candidate for Ivy 2.0.0.

Ivy is a tool for managing (recording, tracking, resolving and
reporting) project dependencies, characterized by flexibility,
configurability, and tight integration with Apache Ant.

This is a release candidate for 2.0.0 final, meaning that no changes 
except bug fixes will occur between this release candidate and 2.0.0 final.
Problems found at this phase can be fixed in the final release, so now 
is a good time to download and use it. If no outstanding bugs are reported
in the coming weeks, this release candidate will be promoted as the 2.0.0 
final release.

Key changes in this 2.0.0-rc2 version are
* enhanced Maven2 compatibility, with several bug fixes
* 20+ bug fixes as documented in Jira and in the release notes

Issues should be reported to:
https://issues.apache.org/jira/browse/IVY

Download the 2.0.0-rc2 release files at:
http://ant.apache.org/ivy/download.cgi

More information can be found on the Ivy website:
http://ant.apache.org/ivy/

Regards,
Maarten Coene (2.0.0-rc2 release manager)



  

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: EasyAnt / vs

2008-11-05 Thread Dominique Devienne
On Wed, Nov 5, 2008 at 9:59 AM, Stefan Bodewig <[EMAIL PROTECTED]> wrote:
> IIUC EasyAnt solits the two use-cases found for  into two
> logical tasks.
>
> * you never want to override a target, you just want to reuse them: 

That's an  to me. Rename  into , and I'm +1,
even with the forced prefix (from build file or @as) to included
targets.

> * you may want to override some/most targets: 

That's the current  indeed.

> Technically  is what  is today.  ed targets
> that haven't been overwritten in the main build are known under two
> names (prefixed and not prefixed) and the depends lists of the targets
> in the -imported file are not rewritten.
>
> Targets coming from a d file only exist in their prefixed form
> and their dependencies are rewritten to include prefixes as well.
> I.e. you can not override the d target's dependencies.
>
> There has been some confusion from time to time on the user list as to
> how you can ensure you get "your" target and not an overwritten one in
> an imported file, so I think  is useful outside of EasyAnt as
> well.
>
> EasyAnt also adds an as-attribute to  where the writer of the
> importing build file can control the prefix of the d targets and
> overrules the d project's name.  This makes sense IMHO.

It does to me too :)

> I'm not totally sure whether the as-attribute would make sense for
>  as well, EasyAnt currently silently ignores it in that case.

It makes as much sense in  as it does in  to me, i.e.
to restore proper compartmentalization of the builds.

> Changes would be required to the import task as well as to
> ProjectHelper2 (the specific patch also patches AntXMLContext and
> ProjectHelper, but that may turn out to be not necessary.  It's an
> implementation detail).
>
> Opinions?

I don't think we should invent new terminology (use/extends) for
something that already exists (import) and it's natural equivalent to
use (include, which doesn't exist). The import/include difference
already exists in XSLT. It's not that import/include is *better* than
use/extends, it's that they are a fairly well known precedent,
especially given that we already have import in Ant.

What's missing from the above is the notion of TargetGroup to
implement the phase concept of EasyAnt (and Maven I guess). Although
it's possible to tack this on to Target, having a separate class to
model this would be better IMHO.

--DD

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



EasyAnt / vs

2008-11-05 Thread Stefan Bodewig
Hi,

Jean-Louis or Xavier may correct me if I'm wrong.

IIUC EasyAnt solits the two use-cases found for  into two
logical tasks.

* you never want to override a target, you just want to reuse them:
  

* you may want to override some/most targets: 

Technically  is what  is today.  ed targets
that haven't been overwritten in the main build are known under two
names (prefixed and not prefixed) and the depends lists of the targets
in the -imported file are not rewritten.

Targets coming from a d file only exist in their prefixed form
and their dependencies are rewritten to include prefixes as well.
I.e. you can not override the d target's dependencies.

There has been some confusion from time to time on the user list as to
how you can ensure you get "your" target and not an overwritten one in
an imported file, so I think  is useful outside of EasyAnt as
well.

EasyAnt also adds an as-attribute to  where the writer of the
importing build file can control the prefix of the d targets and
overrules the d project's name.  This makes sense IMHO.

I'm not totally sure whether the as-attribute would make sense for
 as well, EasyAnt currently silently ignores it in that case.

Changes would be required to the import task as well as to
ProjectHelper2 (the specific patch also patches AntXMLContext and
ProjectHelper, but that may turn out to be not necessary.  It's an
implementation detail).

Opinions?

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: javac task problem in Java 6

2008-11-05 Thread Stefan Bodewig
On Wed, 5 Nov 2008, Sergey Bondarenko <[EMAIL PROTECTED]> wrote:

> Hi Stefan!
> 
> I followed your advice and set sourcepath to "".
> 
> Compilation by javac works properly in JDK 5 and 6:
> javac -sourcepath "" -classpath b.jar A.java
> 
> Compilation by ant task works properly in JDK 5, but does not work
> in JDK 6

This is not what Ant does.  Compilation looks more like

javac -d . -sourcepath . -classpath b.jar A.java

without setting sourcepath (Ant uses srcdir as sourcepath in that
case) and

javac -d . -classpath b.jar A.java

with sourcepath="".

The problem seems to be that destdir==srcdir in your case.  If I
create a directory d and set destdir="d" then only A gets compiled (on
Java4 as well as Java5).  It seems as if Java6's javac searches the
destination directory for sources as well.

> I understand that Ant compiles classes using tools.jar, so there is
> no straight way to write the same command line.

If you set fork="true" it will use the command line, but the
in-process execution really should look the same.

Stefan

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



Re: EasyAnt project

2008-11-05 Thread Jean-Louis BOUDART
UP

Is there some news about our patch or about ProjectHelper class  / Target
class refactoring?

Jean Louis

2008/10/29 Stefan Bodewig <[EMAIL PROTECTED]>

> On Wed, 29 Oct 2008, Matt Benson <[EMAIL PROTECTED]> wrote:
>
> --- Stefan Bodewig <[EMAIL PROTECTED]> wrote:
>
> >> On Wed, 29 Oct 2008, Matt Benson
> >> <[EMAIL PROTECTED]> wrote:
>
> >> > 3.  Define an ant.project.class magic property to
> >> > easily allow the user to specify an extended Project
> >> > class to use.
> >> > 4.  EasyAnt has its own Project, Target, and Executor
> >> > implementations that know about phases.
> >>
> >> If EasyAnt used a ProjectHelper of its own, it probably could get
> >> away without a custom Project.  A custom Executor may be a good
> >> idea, though.
> >>
> >> EasyAnt would need its own wrapper script or an invocation would
> >> become cumbersome, though.
> >
> > How is a custom Project class(name) more cumbersome to
> > configure than a custom ProjectHelper?
>
> Not at all, sorry, I didn't mean to say that.  EasyAnt would need a
> wrapper anyway in order to configure Project class/ProjectHelper,
> Target class and Executor.
>
> Stefan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


Re: javac task problem in Java 6

2008-11-05 Thread Sergey Bondarenko
Hi Stefan!

I followed your advice and set sourcepath to "".

Compilation by javac works properly in JDK 5 and 6:
javac -sourcepath "" -classpath b.jar A.java

Compilation by ant task works properly in JDK 5, but does not work in JDK 6:











So there is a problem in the way Ant works with javac.
I understand that Ant compiles classes using tools.jar, so there is no
straight way to write the same command line.
But since JDK javac compiler works properly in both JDK, I suppose that
something is wrong in Ant's javac task.
Is it correct?


BTW, did you try to compile classes from javac_issue.zip that I had sent
earlier?


Regards,
Sergey Bondarenko.


2008/11/5 Stefan Bodewig <[EMAIL PROTECTED]>

> On Tue, 4 Nov 2008, Sergey Bondarenko <[EMAIL PROTECTED]> wrote:
>
> > javac -sourcepath A.java -classpath b.jar A.java
> > It works properly in both JDK 5 and 6.
>
> This is not what Ant does (and why I pointed you at sourcepath="" in
> order to get something like that.
>
> > But Ant's javac task with "includes" and "excludes" does not work
> > with JDK 6.
>
> See my response.
>
> > So I am not sure that problem is in javac compiler. It looks like
> > there is a problem in javac Ant task.  Could anybody please check
> > it?  Is there any way to look at exact javac invocation string that
> > is produced for the build script?
>
> Run Ant with -verbose.
>
> Stefan
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


Re: problem updating the ivy website

2008-11-05 Thread Xavier Hanin
On Wed, Nov 5, 2008 at 12:32 AM, Maarten Coene <[EMAIL PROTECTED]>wrote:

> I've committed the Ivy 2.0.0-rc2 website in svn:
> https://svn.apache.org/repos/asf/ant/ivy/site/target/
> When I want to update it in /www/ant.apache.org/ivy I get the following
> error:
>
> [EMAIL PROTECTED] /www/ant.apache.org/ivy]$ svn up
> svn: Can't open file 'history/trunk/settings/.svn/lock': Permission denied
>
> Xavier: can you update the site or modify the permissions?

Sorry about that, I've updated the site and the permissions, it should be in
order now.

Xavier


>
>
> regards
> Maarten
>
>
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>


-- 
Xavier Hanin - 4SH France
BordeauxJUG co leader - http://www.bordeauxjug.org/
Blogger - http://xhab.blogspot.com/
Apache Ivy Creator - http://ant.apache.org/ivy/