You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ant.apache.org by Magesh Umasankar <um...@apache.org> on 2002/05/01 04:25:10 UTC
Ant 1.5 Beta1 Sneak Preview ready
Hi,
Before I make a formal announcement, I have uploaded
the beta 1 build onto
http://jakarta.apache.org/~umagesh/builds/jakarta-ant/release/v1.5Beta1
Please take a look and verify if everything looks good.
Based on your feedback, tomorrow, I will go ahead and move it
into jakarta.apache.org/builds and then, also perform
the other tasks like BugZilla version adding, announcing, etc.
At this time, I would also like to announce that
the Ant 1.6Alpha tree is available for further
commits to the main trunk. However, the patches
that you want reflected in Ant 1.5 must go against the
ANT_15_BRANCH. Bear in mind that we are in a feature
freeze as far as 1.5 Branch goes. Only bugfizes,
documentation updates/additions and testcase additions/
updates may take place on this branch - anything else
would have to be voted upon.
To start commiting against the branch, you would
first have to do a recursive cvs update based on branch
name:
cvs checkout -r ANT_15_BRANCH
This would create a working copy of the branch for you,
and any modifications to this followed by further commits
will be performed against the branch.
If you want to commit against the main tree after
having swithed to the branch environment, you would
have to update your working copy again with the main trunk
by performing a cvs update after resetting any
sticky keys.
Cheers,
Magesh
********************************************************
* Lecture: An art of transferring information from *
* the notes of lecturer to the notes of the students *
* without passing through "the minds of either". *
********************************************************
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
----- Original Message -----
From: "Darrell DeBoer" <da...@apache.org>
> Could you try it with the <style> task?
Ok, worked fine with 2.1.0 xalan.jar, but with 2.2.0 I get:
[style] DEPRECATED - xslp processor is deprecated. Use trax or xalan
instead.
[style] java.lang.NoClassDefFoundError: com/kvisco/xsl/XSLProcessor
Similar bad news with <junitreport>:
java.lang.NoClassDefFoundError: javax/xml/transform/Source
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:120)
at
org.apache.tools.ant.taskdefs.optional.junit.XalanExecutor.newInstanc
e(XalanExecutor.java:108)
at
org.apache.tools.ant.taskdefs.optional.junit.AggregateTransformer.tra
nsform(AggregateTransformer.java:188)
at
org.apache.tools.ant.taskdefs.optional.junit.XMLResultAggregator.exec
ute(XMLResultAggregator.java:173)
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Peter Donald <pe...@apache.org>.
On Tue, 7 May 2002 00:15, Darrell DeBoer wrote:
> On Mon, 6 May 2002 14:32, Michael McCallum wrote:
> > the danger is that the order of the jars depends upon the ordering of a
> > list of items from the ant/lib directory so the classes used may be
> > different on different platforms.
>
> Exactly, and it's just not great to have multiple versions of the same
> .class files in your classpath, if you can avoid it. Some of my least fun
> Java experiences have been tracking down LinkageErrors with JAXP, caused by
> different versions of JAXP classes in different places - I don't wish the
> experience on anyone. ;)
agreed.
+1 to including it by default. Though we could also offer a stripped down
version that just contained the ant jars if it is really necessary.
--
Cheers,
Peter Donald
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Darrell DeBoer <da...@apache.org>.
On Mon, 6 May 2002 14:32, Michael McCallum wrote:
> the danger is that the order of the jars depends upon the ordering of a
> list of items from the ant/lib directory so the classes used may be
> different on different platforms.
Exactly, and it's just not great to have multiple versions of the same .class
files in your classpath, if you can avoid it. Some of my least fun Java
experiences have been tracking down LinkageErrors with JAXP, caused by
different versions of JAXP classes in different places - I don't wish the
experience on anyone. ;)
--
ciao,
Daz
>
> On Monday, 06 May, 2002 16:03, Diane Holt wrote:
> > --- Darrell DeBoer <da...@apache.org> wrote:
> > > Could you try it with the <style> task?
> > > Here's what happens for me, with XalanJ - 2.3.1.
> > > 1) Clean 1.5Beta install - execute project with <style> task (myrmidon)
> > > ==> java.lang.NoClassDefFoundError:
> > > javax/xml/transform/ErrorListener
> > > 2) Copy xalan.jar into ant/lib
> > > ==> Same error
> > > 3) Copy xml-apis.jar into ant/lib
> > > ==> Success, but now we have multiple copies of JAXP classes in
> > > ant/lib, with slightly different versions. This, IMHO, is dangerous.
> >
> > That's what I did as well to get <style> to work. What about it makes it
> > dangerous? (I'm not saying it isn't -- I have no clue about any of this
> > stuff, so I'm asking what the danger actually is.)
> >
> > Diane
> >
> >
> > =====
> > (holtdl@yahoo.com)
> >
> >
> >
> > __________________________________________________
> > Do You Yahoo!?
> > Yahoo! Health - your guide to health and wellness
> > http://health.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Michael McCallum <mi...@snaphire.com>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
the danger is that the order of the jars depends upon the ordering of a list of items from the ant/lib directory
so the classes used may be different on different platforms.
On Monday, 06 May, 2002 16:03, Diane Holt wrote:
> --- Darrell DeBoer <da...@apache.org> wrote:
> > Could you try it with the <style> task?
> > Here's what happens for me, with XalanJ - 2.3.1.
> > 1) Clean 1.5Beta install - execute project with <style> task (myrmidon)
> > ==> java.lang.NoClassDefFoundError:
> > javax/xml/transform/ErrorListener
> > 2) Copy xalan.jar into ant/lib
> > ==> Same error
> > 3) Copy xml-apis.jar into ant/lib
> > ==> Success, but now we have multiple copies of JAXP classes in
> > ant/lib, with slightly different versions. This, IMHO, is dangerous.
>
> That's what I did as well to get <style> to work. What about it makes it
> dangerous? (I'm not saying it isn't -- I have no clue about any of this
> stuff, so I'm asking what the danger actually is.)
>
> Diane
>
>
> =====
> (holtdl@yahoo.com)
>
>
>
> __________________________________________________
> Do You Yahoo!?
> Yahoo! Health - your guide to health and wellness
> http://health.yahoo.com
- --
The true human being...is the meaning of the universe.
He is a dancing star.
He is the exploding singularity pregnant with infinite possibilities.
- -- David Zindell "The Broken God"
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.6 (GNU/Linux)
Comment: For info see http://www.gnupg.org
iD8DBQE81gdkiVyQAvn9zYsRAot5AJ9WZDE4Q41IdTVt3Uzh/fBdgqz/3wCfRB3H
ri/kRr+5BwYhU9dej0EBRCE=
=nzXR
-----END PGP SIGNATURE-----
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Diane Holt <ho...@yahoo.com>.
--- Darrell DeBoer <da...@apache.org> wrote:
> Could you try it with the <style> task?
> Here's what happens for me, with XalanJ - 2.3.1.
> 1) Clean 1.5Beta install - execute project with <style> task (myrmidon)
> ==> java.lang.NoClassDefFoundError:
> javax/xml/transform/ErrorListener
> 2) Copy xalan.jar into ant/lib
> ==> Same error
> 3) Copy xml-apis.jar into ant/lib
> ==> Success, but now we have multiple copies of JAXP classes in
> ant/lib, with slightly different versions. This, IMHO, is dangerous.
That's what I did as well to get <style> to work. What about it makes it
dangerous? (I'm not saying it isn't -- I have no clue about any of this
stuff, so I'm asking what the danger actually is.)
Diane
=====
(holtdl@yahoo.com)
__________________________________________________
Do You Yahoo!?
Yahoo! Health - your guide to health and wellness
http://health.yahoo.com
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Darrell DeBoer <da...@apache.org>.
On Mon, 6 May 2002 11:58, Erik Hatcher wrote:
> I certainly can't speak to all the issues with the different API
> implementations and all that, but I'm a big +1 on shipping with Xalan - it
> will make using <style> easier and also <junitreport>.
>
> Although I've got xalan.jar (v 2.1.0), xercesImpl.jar, and
> xmlParserAPIs.jar in my ANT_HOME/lib and all seems to be working fine, at
> least with <junitreport>.
>
> Erik
>
Hmmm.
Could you try it with the <style> task?
Here's what happens for me, with XalanJ - 2.3.1.
1) Clean 1.5Beta install - execute project with <style> task (myrmidon)
==> java.lang.NoClassDefFoundError: javax/xml/transform/ErrorListener
2) Copy xalan.jar into ant/lib
==> Same error
3) Copy xml-apis.jar into ant/lib
==> Success, but now we have multiple copies of JAXP classes in ant/lib,
with slightly different versions. This, IMHO, is dangerous.
4) Remove xmlParserAPIs.jar
==> Still works.
I haven't tried <junitreport>, but if it uses xalan, it should be a similar
story. Maybe earlier versions of xalan (like 2.1.0) included the JAXP files
within the xalan.jar itself. That would explain the differences between our
observed behaviour. Or maybe the JAXP transform classes are in your
classpath?
--
ciao,
Daz
> ----- Original Message -----
> From: "Darrell DeBoer" <da...@apache.org>
> To: "Ant Developers List" <an...@jakarta.apache.org>
> Sent: Sunday, May 05, 2002 9:48 PM
> Subject: Re: Ant 1.5 Beta1 Sneak Preview ready
>
> > On Thu, 2 May 2002 16:46, Stefan Bodewig wrote:
> > > On Wed, 1 May 2002, Erik Hatcher <ja...@ehatchersolutions.com>
> > >
> > > wrote:
> > > > I'm guessing we decided not to ship with Xalan - no big deal, I just
> > > > wasn't sure which way we decided.
> > >
> > > There hasn't been any veto, but I haven't seen any overwhelming
> > > support to ship Xalan either 8-)
> > >
> > > > Thanks Magesh for all the work you have and will put into this
> > > > release!!!!
> > >
> > > +1
> > >
> > > Stefan
> >
> > G'day,
> >
> > I'm tempted to say that we *should* include Xalan, or at least use the
>
> version
>
> > of JAXP from Xalan (xml-apis.jar, which is actually from the xml-commons
> > project), instead of the cut-down (parser only) version of JAXP that
> > ships with Xerces (xmlParserAPIs.jar).
> >
> > The way things are now, the process to get <style> working seems to be:
> > 1) Copy Xalan.jar into ant/lib
> > 2) Delete xmlParserAPIs.jar from ant/lib
> > 3) Copy xml-apis.jar from Xalan install into ant/lib
> >
> > I think this is confusing, and could be a support nightmare, especially
> > if people start putting xml-apis.jar and Xalan.jar in their classpath,
> > while leaving xmlParserAPIs.jar in ant/lib.
> >
> > My understanding is that there are some very minor differences between
> > the version of JAXP included in xmlParserAPIs.jar and xml-apis.jar, but
> > I'm pretty sure that the complete version that ships with Xalan will meet
> > our needs sufficiently, at least better than the incomplete version that
> > comes with Xerces. I guess the other option is to get the Xalan folks to
> > ship a "transform-only" version of JAXP, to complement the "parser-only"
> > version from Xerces (or package it up ourselves).
> >
> > Stephane was doing some research on this a while back, but I think he
> > went
>
> on
>
> > holidays? Here's the start of the thread:
> > http://marc.theaimsgroup.com/?l=xml-apache-general&m=101898418819202&w=2
> >
> > --
> > ciao,
> > Daz
> >
> > --
> > To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> > For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Erik Hatcher" <ja...@ehatchersolutions.com>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Sunday, May 05, 2002 18:58
Subject: Re: Ant 1.5 Beta1 Sneak Preview ready
> I certainly can't speak to all the issues with the different API
> implementations and all that, but I'm a big +1 on shipping with Xalan - it
> will make using <style> easier and also <junitreport>.
>
> Although I've got xalan.jar (v 2.1.0), xercesImpl.jar, and
xmlParserAPIs.jar
> in my ANT_HOME/lib and all seems to be working fine, at least with
> <junitreport>.
>
how about a 'fat distro' and a skinny 'for java1.4' distro?
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
I certainly can't speak to all the issues with the different API
implementations and all that, but I'm a big +1 on shipping with Xalan - it
will make using <style> easier and also <junitreport>.
Although I've got xalan.jar (v 2.1.0), xercesImpl.jar, and xmlParserAPIs.jar
in my ANT_HOME/lib and all seems to be working fine, at least with
<junitreport>.
Erik
----- Original Message -----
From: "Darrell DeBoer" <da...@apache.org>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Sunday, May 05, 2002 9:48 PM
Subject: Re: Ant 1.5 Beta1 Sneak Preview ready
> On Thu, 2 May 2002 16:46, Stefan Bodewig wrote:
> > On Wed, 1 May 2002, Erik Hatcher <ja...@ehatchersolutions.com>
> >
> > wrote:
> > > I'm guessing we decided not to ship with Xalan - no big deal, I just
> > > wasn't sure which way we decided.
> >
> > There hasn't been any veto, but I haven't seen any overwhelming
> > support to ship Xalan either 8-)
> >
> > > Thanks Magesh for all the work you have and will put into this
> > > release!!!!
> >
> > +1
> >
> > Stefan
>
> G'day,
>
> I'm tempted to say that we *should* include Xalan, or at least use the
version
> of JAXP from Xalan (xml-apis.jar, which is actually from the xml-commons
> project), instead of the cut-down (parser only) version of JAXP that ships
> with Xerces (xmlParserAPIs.jar).
>
> The way things are now, the process to get <style> working seems to be:
> 1) Copy Xalan.jar into ant/lib
> 2) Delete xmlParserAPIs.jar from ant/lib
> 3) Copy xml-apis.jar from Xalan install into ant/lib
>
> I think this is confusing, and could be a support nightmare, especially if
> people start putting xml-apis.jar and Xalan.jar in their classpath, while
> leaving xmlParserAPIs.jar in ant/lib.
>
> My understanding is that there are some very minor differences between the
> version of JAXP included in xmlParserAPIs.jar and xml-apis.jar, but I'm
> pretty sure that the complete version that ships with Xalan will meet our
> needs sufficiently, at least better than the incomplete version that comes
> with Xerces. I guess the other option is to get the Xalan folks to ship a
> "transform-only" version of JAXP, to complement the "parser-only" version
> from Xerces (or package it up ourselves).
>
> Stephane was doing some research on this a while back, but I think he went
on
> holidays? Here's the start of the thread:
> http://marc.theaimsgroup.com/?l=xml-apache-general&m=101898418819202&w=2
>
> --
> ciao,
> Daz
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Darrell DeBoer <da...@apache.org>.
On Thu, 2 May 2002 16:46, Stefan Bodewig wrote:
> On Wed, 1 May 2002, Erik Hatcher <ja...@ehatchersolutions.com>
>
> wrote:
> > I'm guessing we decided not to ship with Xalan - no big deal, I just
> > wasn't sure which way we decided.
>
> There hasn't been any veto, but I haven't seen any overwhelming
> support to ship Xalan either 8-)
>
> > Thanks Magesh for all the work you have and will put into this
> > release!!!!
>
> +1
>
> Stefan
G'day,
I'm tempted to say that we *should* include Xalan, or at least use the version
of JAXP from Xalan (xml-apis.jar, which is actually from the xml-commons
project), instead of the cut-down (parser only) version of JAXP that ships
with Xerces (xmlParserAPIs.jar).
The way things are now, the process to get <style> working seems to be:
1) Copy Xalan.jar into ant/lib
2) Delete xmlParserAPIs.jar from ant/lib
3) Copy xml-apis.jar from Xalan install into ant/lib
I think this is confusing, and could be a support nightmare, especially if
people start putting xml-apis.jar and Xalan.jar in their classpath, while
leaving xmlParserAPIs.jar in ant/lib.
My understanding is that there are some very minor differences between the
version of JAXP included in xmlParserAPIs.jar and xml-apis.jar, but I'm
pretty sure that the complete version that ships with Xalan will meet our
needs sufficiently, at least better than the incomplete version that comes
with Xerces. I guess the other option is to get the Xalan folks to ship a
"transform-only" version of JAXP, to complement the "parser-only" version
from Xerces (or package it up ourselves).
Stephane was doing some research on this a while back, but I think he went on
holidays? Here's the start of the thread:
http://marc.theaimsgroup.com/?l=xml-apache-general&m=101898418819202&w=2
--
ciao,
Daz
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 1 May 2002, Erik Hatcher <ja...@ehatchersolutions.com>
wrote:
> I'm guessing we decided not to ship with Xalan - no big deal, I just
> wasn't sure which way we decided.
There hasn't been any veto, but I haven't seen any overwhelming
support to ship Xalan either 8-)
> Thanks Magesh for all the work you have and will put into this
> release!!!!
+1
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Erik Hatcher <ja...@ehatchersolutions.com>.
----- Original Message -----
From: "Magesh Umasankar" <um...@apache.org>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Tuesday, April 30, 2002 10:25 PM
Subject: Ant 1.5 Beta1 Sneak Preview ready
> Hi,
> Before I make a formal announcement, I have uploaded
> the beta 1 build onto
>
> http://jakarta.apache.org/~umagesh/builds/jakarta-ant/release/v1.5Beta1
>
> Please take a look and verify if everything looks good.
> Based on your feedback, tomorrow, I will go ahead and move it
> into jakarta.apache.org/builds and then, also perform
> the other tasks like BugZilla version adding, announcing, etc.
It ran all my builds ok.
I'm guessing we decided not to ship with Xalan - no big deal, I just wasn't
sure which way we decided.
Thanks Magesh for all the work you have and will put into this release!!!!
Erik
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Peter Donald <pe...@apache.org>.
On Wed, 1 May 2002 20:33, Magesh Umasankar wrote:
> Hmm, I did respond!
> http://marc.theaimsgroup.com/?l=ant-dev&m=102018000104727&w=2
arg - sorry. My email must be messed up again.
> Add it into the beta branch...
will do - thanks.
--
Cheers,
Peter Donald
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Magesh Umasankar <um...@apache.org>.
Hmm, I did respond!
http://marc.theaimsgroup.com/?l=ant-dev&m=102018000104727&w=2
Add it into the beta branch...
********************************************************
* Lecture: An art of transferring information from *
* the notes of lecturer to the notes of the students *
* without passing through "the minds of either". *
********************************************************
----- Original Message -----
From: "Peter Donald" <pe...@apache.org>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Wednesday, May 01, 2002 6:11 AM
Subject: Re: Ant 1.5 Beta1 Sneak Preview ready
Hi,
On Wed, 1 May 2002 12:25, Magesh Umasankar wrote:
> At this time, I would also like to announce that
> the Ant 1.6Alpha tree is available for further
> commits to the main trunk. However, the patches
> that you want reflected in Ant 1.5 must go against the
> ANT_15_BRANCH. Bear in mind that we are in a feature
> freeze as far as 1.5 Branch goes. Only bugfizes,
> documentation updates/additions and testcase additions/
> updates may take place on this branch - anything else
> would have to be voted upon.
I am not sure if it got through but yesterday I sent a question whether I
should add in stuff for extension stuff given that I haven't fully tested
it.
I have attached the file that I want to add. Basically you drop this into
the
correct directory and add the following to JarLibResolver task
public void addConfiguredAnt( final AntResolver ant )
{
m_resolvers.add( ant );
}
I can drop it into branch but it may need bugfixes (going to test it
properly
tomorrow). Anyways you didn't respond last time so I haven't added it but I
think it really needs to be in there for release because it is the part of
JarLibResolver that makes it useful in projects like excalibur or commons
that contains many sub projects.
Thoughts?
--
Cheers,
Peter Donald
----------------------------------------------------------------------------
----
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Peter Donald <pe...@apache.org>.
Hi,
On Wed, 1 May 2002 12:25, Magesh Umasankar wrote:
> At this time, I would also like to announce that
> the Ant 1.6Alpha tree is available for further
> commits to the main trunk. However, the patches
> that you want reflected in Ant 1.5 must go against the
> ANT_15_BRANCH. Bear in mind that we are in a feature
> freeze as far as 1.5 Branch goes. Only bugfizes,
> documentation updates/additions and testcase additions/
> updates may take place on this branch - anything else
> would have to be voted upon.
I am not sure if it got through but yesterday I sent a question whether I
should add in stuff for extension stuff given that I haven't fully tested it.
I have attached the file that I want to add. Basically you drop this into the
correct directory and add the following to JarLibResolver task
public void addConfiguredAnt( final AntResolver ant )
{
m_resolvers.add( ant );
}
I can drop it into branch but it may need bugfixes (going to test it properly
tomorrow). Anyways you didn't respond last time so I haven't added it but I
think it really needs to be in there for release because it is the part of
JarLibResolver that makes it useful in projects like excalibur or commons
that contains many sub projects.
Thoughts?
--
Cheers,
Peter Donald
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Magesh Umasankar <um...@apache.org>.
----- Original Message -----
From: "Patrick (Gus) Heck" <pa...@olin.edu>
> Hi,
>
> I noticed that my patch to DirectoryScanner has not been applied to the
1.5
> Beta Branch. I don't think it was commited anywhere for that matter.
> So, maybe it can be added to
> the beta branch as part of a bug fix?
>
I believe Stefan Bodewig is following up on this.
Symlinks has been an BugZilla issue for a long time
now. If he considers this committable, he will
get it in, in time for the Beta 2 build, of course
assuming no other committer objects.
> Gus
>
Cheers,
Magesh
********************************************
* Ever notice how wholeheartedly we give *
* ourselves to half-baked solutions? *
********************************************
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready - DirScanner patch
Posted by "Patrick (Gus) Heck" <pa...@olin.edu>.
So I read through bug 1550 delete follows symlinks. It does look like my
patch could be used to fix this. Given the discussion there, and the definite
morass of possibilities of filesystems, the way to look at things seems (to
me) to be this:
---
1. Symlinks on linux can cause annoying, and even potentially dangerous
behavior, particularly with delete and copy type tasks. Understandably users
on these systems might want to write build files that guard against a global
delete of **/*.foo files (such as a accidental symlink to /usr that goes
unnoticed and someone being dumb and forgetting they are su root when doing a
build clean) (*shudder*). (most problems are likely to be much smaller, but
still potentially annoying)
2. Java doesn't understand symlinks very well (at all?), and the mechanisims
for identifying them absolutely in all cases are simply not available.
However, they do fall out nicely on certain file systems comparing absolute
and canonical paths. Our problem is that we don't know what filesystems are
going to be included in a FileSet and there could be more than one.
3. The only person who knows what filesystems are involved is the user who
writes the fileset. (hopefully) Thus the reasonable thing to do is to extend
the functionality that _is_ offered by Java to the user, and let him/her
apply it as needed.
---
So what I propose is to modify my current patch so rather than setting a
followLinks attribute, we set a isCanonical atribute. This can the be
propogated up to FileSet/MatchingTask and the documentation can mention it's
utility in avoiding symlinks, and mention the difficulties in using it across
samba or on case insensitive filesystems.
Sound good?
Gus
Stefan Bodewig wrote:
> On Thu, 2 May 2002, Magesh Umasankar <um...@apache.org> wrote:
>
> > would it mean changing a bunch of files?
>
> DirectoryScanner and FileSet - maybe MatchingTask.
>
> It would add a new optional followsymlinks attributes that defaulted
> to true, thus preserving the old behavior. It is rather unlikely to
> break anything. But then again, I've been the one who just said
> "let's not add new functionality between betas" ten mails ago 8-)
>
> Stefan
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Stefan Bodewig <bo...@apache.org>.
On Thu, 2 May 2002, Magesh Umasankar <um...@apache.org> wrote:
> would it mean changing a bunch of files?
DirectoryScanner and FileSet - maybe MatchingTask.
It would add a new optional followsymlinks attributes that defaulted
to true, thus preserving the old behavior. It is rather unlikely to
break anything. But then again, I've been the one who just said
"let's not add new functionality between betas" ten mails ago 8-)
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Magesh Umasankar <um...@apache.org>.
----- Original Message -----
From: "Stefan Bodewig" <bo...@apache.org>
>
> If Magesh says, it is OK to add this new functionality as it fixes a
> bug report, I will at least think about it 8-)
If it is going to help close a bug report, +1
for you to think about it - but would it mean
changing a bunch of files? If so, I am skeptical
if we want to do it for Beta 2 - perhaps for 1.6Alpha?
You make the judgement call, depending upon the
contents.
>
> Stefan
Cheers,
Magesh
****************************************************
* Doctor: A person who kills your ills by pills, *
* and then kills you with his bills. *
****************************************************
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Stefan Bodewig <bo...@apache.org>.
On Wed, 01 May 2002, Patrick Heck <pa...@olin.edu> wrote:
> I noticed that my patch to DirectoryScanner has not been applied to
> the 1.5 Beta Branch. I don't think it was commited anywhere for that
> matter.
Right, I was waiting for feedback.
If Magesh says, it is OK to add this new functionality as it fixes a
bug report, I will at least think about it 8-)
Stefan
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by "Patrick (Gus) Heck" <pa...@olin.edu>.
Hi,
I noticed that my patch to DirectoryScanner has not been applied to the 1.5
Beta Branch. I don't think it was commited anywhere for that matter. There
was some question as to whether my techniques worked consistantly across
platforms, but I did submit it before the branch was created. Since I am
writing a task for my own use that needs this functionality, I would really
like to see this included in the 1.5 release for two reasons:
The patch allowed developers to control whether or not Directory Scanner
follows symlinks (or other non-canonical paths).
1. If it is in the Beta then there is a better chance people will use it and
we will find out if it has problems on system types I don't have access to.
2. It would be much nicer if the system I am setting up on my end used ant
1.5 with my custom task rather than an Ant 1.5, apply this patch, and hope
DirectoryScanner hasn't chaged so it still works, and then use my custom
task. Basically, I don't want to have my system running on a mutated version
of Ant if I don't have to, but something standardized.
3. There was also a suggestion that the feature added to DirectoryScanner
could be propagated up to FileSet to fix a bug. So, maybe it can be added to
the beta branch as part of a bug fix?
Gus
Magesh Umasankar wrote:
> Hi,
> Before I make a formal announcement, I have uploaded
> the beta 1 build onto
>
> http://jakarta.apache.org/~umagesh/builds/jakarta-ant/release/v1.5Beta1
>
> Please take a look and verify if everything looks good.
> Based on your feedback, tomorrow, I will go ahead and move it
> into jakarta.apache.org/builds and then, also perform
> the other tasks like BugZilla version adding, announcing, etc.
>
> At this time, I would also like to announce that
> the Ant 1.6Alpha tree is available for further
> commits to the main trunk. However, the patches
> that you want reflected in Ant 1.5 must go against the
> ANT_15_BRANCH. Bear in mind that we are in a feature
> freeze as far as 1.5 Branch goes. Only bugfizes,
> documentation updates/additions and testcase additions/
> updates may take place on this branch - anything else
> would have to be voted upon.
>
> To start commiting against the branch, you would
> first have to do a recursive cvs update based on branch
> name:
>
> cvs checkout -r ANT_15_BRANCH
>
> This would create a working copy of the branch for you,
> and any modifications to this followed by further commits
> will be performed against the branch.
>
> If you want to commit against the main tree after
> having swithed to the branch environment, you would
> have to update your working copy again with the main trunk
> by performing a cvs update after resetting any
> sticky keys.
>
> Cheers,
> Magesh
>
> ********************************************************
> * Lecture: An art of transferring information from *
> * the notes of lecturer to the notes of the students *
> * without passing through "the minds of either". *
> ********************************************************
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: Ant 1.5 Beta1 Sneak Preview ready
Posted by Steve Loughran <st...@iseran.com>.
----- Original Message -----
From: "Magesh Umasankar" <um...@apache.org>
To: "Ant Developers List" <an...@jakarta.apache.org>
Sent: Tuesday, April 30, 2002 19:25
Subject: Ant 1.5 Beta1 Sneak Preview ready
>
> To start commiting against the branch, you would
> first have to do a recursive cvs update based on branch
> name:
>
> cvs checkout -r ANT_15_BRANCH
>
> This would create a working copy of the branch for you,
> and any modifications to this followed by further commits
> will be performed against the branch.
>
> If you want to commit against the main tree after
> having swithed to the branch environment, you would
> have to update your working copy again with the main trunk
> by performing a cvs update after resetting any
> sticky keys.
>
Or just grab a whole new copy in a separate dir, set up your path & ant_home
to whichever one you want
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>