Re: [VOTE] Retire the IvyDE Subproject

[Maarten Coene]

+1

Maarten




Op donderdag 23 november 2023 om 08:19:22 CET schreef Stefan Bodewig 
: 





I'm really sorry and embarrassed but I seem to have misunderstood the
purpose of the Attic, it is not responsible for retiring subprojects,
only for top level projects like Ant as a whole with all subprojects.

The correct process to follow is
https://ant.apache.org/processes.html#Retire%20a%20subproject%20or%20component

This is a new vote as I do not want to assume I could transfer the votes
of a different vote and repurpose them.

The actual vote:

Following our own rules I propose zo retire IvyDE.

Vote will be open for at lease 72 hours, will not end before 2023-11-26T07:30 
UTC

Sorry

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Send IvyDE to the Apache Attic

[Maarten Coene]

+1

Maarten




Op zondag 19 november 2023 om 18:40:27 CET schreef Stefan Bodewig 
: 





Hi all,

within the "Future of Ivy and IvyDE" thread[1] I started about three
months ago to me it seemed as if people wouldn't be happy if IvyDE died
but I also didn't sense there was a community willing to keep it
alive. Consequently I now call for a vote to send IvyDE to the Apache
Attic following the rules layed out in https://attic.apache.org/process.html

The attic doesn't have to be a dead-end. If there are people who want to
fork IvyDE outside of the ASF they are free to (and have always
been). Basically it would resolve the Ant PMC of the duty of oversight
over the code base.

This vote will require either three PMC members to vote +1 to pass or
alternatively less than three -1s - but I really hope we don't end up
with not getting enough votes at all. If there is any -1 by a PMC member
I'm willing to immediately cancel the vote and rediscuss.


So here is the formal vote:

I hereby propose to create a board resolution that will send IvyDE to
the Apache Attic.

This vote will stay open at least 72 hours and won't be closed before
2023-11-22 17:30 UTC - likely later.

Cheers

        Stefan

[1] https://lists.apache.org/thread/h372vt1ztd6gfmgmfkmqzrksx6fpw97g

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.14 based on RC1

[Maarten Coene]

Thanks Jaikiran!


Here is my vote: +1
Maarten




Op woensdag 16 augustus 2023 om 14:35:43 CEST schreef Jaikiran Pai 
: 





Hello everyone,

I've created RC1 release candidate for Ant 1.10.14 release:

git tag: ANT_1.10.14_RC1

    on commit: 53f19eccf49acf526415997046dca5a5135b0e8f

tarballs: https://dist.apache.org/repos/dist/dev/ant/

    revision: 63474

Maven artifacts: 
https://repository.apache.org/content/repositories/orgapacheant-1057


Apart from regular bug fixes, this 1.10.14 release has crucial changes 
around Ant's usage of Java SecurityManager. Many of you will be aware 
that Java 17 deprecated (for removal) the use of SecurityManager. Java 
18 then disallowed setting SecurityManager at runtime, by default. Ant 
internally sets a SecurityManager at runtime to prevent System.exit() 
calls from within tasks, from killing the JVM in which Ant process is 
running. In Ant 1.10.13, we tried to keep using the SecurityManager 
internally for a few more releases in Ant, to facilitate projects to use 
Ant without requiring (major) changes to their build. The workarounds we 
put in place in Ant 1.10.13 were brittle and complex and although we had 
hoped they won't break user builds, they did end up breaking several 
builds. Ultimately, these workarounds for usage of SecurityManager are 
no longer feasible or adding value.

As such, this 1.10.14 release of Ant will no longer use (or set) Java 
SecurityManager when running on Java versions 18 and higher. This has 
implications for projects using Ant. Specifically, if any of the build 
tasks (for example the "", "" or "" tasks) 
or libraries used in those tasks are calling System.exit() or 
Runtime.exit() and aren't forking a new JVM, then when running on Java 
18 and higher, they may notice that the Ant JVM process gets killed. 
Such builds are recommended to either not call 
System.exit()/Runtime.exit() or use the "fork=true" option in relevant 
tasks (wherever appropriate).

Furthermore, the usage of "" type when running on Java 18 
and higher is no longer supported. More details are available in the 
manual of that type https://dist.apache.org/repos/dist/dev/ant/manual/.

The complete set of changes in this release are noted in 
https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.14.html.

Please do give this proposed release version a try against whichever 
Java runtime versions you plan to use it against (this version requires 
a minimum of Java 8 runtime, like any other Ant 1.10.x versions). Even 
if you don't vote, if you do run into issues, please report back - it 
takes time to create Ant releases, so catching any blocker issues (like 
some of which we saw after Ant 1.10.13 was released) early will help fix 
them sooner.

This vote will be open for at least 72 hours and close no earlier than 
19th August 2023 12 PM.

-Jaikiran


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Ivy 2.5.2 Based on RC2

[Maarten Coene]

Thanks Stefan!

Here is my vote: +1
Maarten




Op donderdag 17 augustus 2023 om 18:54:01 CEST schreef Stefan Bodewig 
: 





Hi all

I've cancelled the previous vote as the NOTICE file didn't contain
2023. sorry about this. Now I've built a new release candidate for Ivy
2.5.2

Changelog:

- FIX: ivy:retrieve could fail because of a `NullPointerException` (IVY-1641)
- FIX: reading POMs may loose dependencies when multiple Maven
  dependencies only differ in `classifier` (IVY-1642)
- IMPROVEMENT: Upgrade Apache HttpClient to 4.5.13 (IVY-1644)

The release artifacts can be found at
https://dist.apache.org/repos/dist/dev/ant/ivy/ (svn revision 63486)

Maven Repo is
https://repository.apache.org/content/repositories/orgapacheant-1061/org/apache/ivy/ivy/2.5.2/

Again I have not built the update site, but we never did for 2.5.1
either and it never bothered anybody.

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

This vote will be open for 72 hours as usual, I'll close it on
2023-08-20 17:00 UTC.

Thanks

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Need Help Understanding Ivy's dependency/artifacts

[Maarten Coene]

Hi Stefan,

thanks for looking into this.
After having a quick look at the diffs and without being able to look into the 
code myself, I think I prefer your approach to solve the issue.

Maybe Jaikiran can remember more details, but I'd go for backing out the 
changes to IvyNodeUsage and push your fix.

Maarten




Op vrijdag 14 april 2023 om 12:56:00 CEST schreef Stefan Bodewig 
: 





Hi all

tldr; there is a bug report about Ivy no handling dependencies to
modules with multiple artifacts - some with classifier, but not all -
and the way I fixed this seems to work. But I have no idea whether I am
fixing it the correct way and need help by somebody understanding Ivy'
semantics - I don't.

longer story:

Over on the ivy-user list somebody reported Ivy would only resolve the
"data" classified artifact as transitive dependency of Saxon-HE where
Saxon's POM contains

    
      org.xmlresolver
      xmlresolver
      5.1.1
    
    
      org.xmlresolver
      xmlresolver
      5.1.1
      data
    

and yes, this is true for the current master branch. This is the ivy.xml
created from the POM snippet above

    
      
    

I created https://issues.apache.org/jira/browse/IVY-1642 and tried to
fix it. My understanding was that this Ivy dependency means Saxon-HE
depends on the "data" artifact and only the data artifact and the
correct solution would be to add a second artifact that matches the
"default" name/type/ext.

So I "fixed" PomModuleDescriptorBuilder to do what I believed to be the
correct translation of the POM.

When I ran the tests ResolveTest#testIvy1580 failed. The modified code
would suddenly return three artifacts as dependency not two as
expected. The non-classifier artifact was returned twice.

First of all this made me discover
https://issues.apache.org/jira/browse/IVY-1580 which, I believe,
describes the same error as the new IVY-1642.

Jaikiran fixed the problem back then with
https://github.com/apache/ant-ivy/commit/d714d9dffbaa2c91855297a7df1c5d9ddfe6d0b0
. He tackled it from a different angle, rather than changing the way POM
dependencies are translated he changed the way dependencies are resolved
by throwing in an "include everything" rule under certain
circumstances. I must admit this change is beyond my understanding of
Ivy.

Backing out his change to IvyNodeUsage fixed the test in my branch. So
maybe my change alone would be enough to resolve the problem? Or there
are two different issues at hand and each of us just fixed one part of
it?

In my branch I decided to keep the IVY-1580 change and "fix" the test by
making sure Ivy's reported dependencies don't contain any
duplicates. The result can be seen here

https://github.com/apache/ant-ivy/compare/ivy-1642

I must admit that I just don't know whether this is correct - apart from
that it fixes the bug reproducer for IVY-1642.

I'll be grateful for any insight

    Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.12 based on RC2

[Maarten Coene]

+1

Maarten






Op zondag 17 oktober 2021 09:02:30 CEST schreef Jaikiran Pai 
: 





+1.

- Used this version to build some of our internal projects.

- Checked some random manuals.

All looks fine.

-Jaikiran

On 13/10/21 11:05 am, Jaikiran Pai wrote:
> I've created a new RC2 release candidate for 1.10.12:
>
> git tag: ANT_1.10.12_RC2
>  on commit: 4b420359942dfb1221f308d08f3648712fea9f83
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>   revision: 50387
> Maven artifacts:
> https://repository.apache.org/content/repositories/orgapacheant-1052
> Snapcraft Build
>   Revision 22 in latest/candidate
>
> This vote will be open for at least 72 hours and close no earlier than 
> 16th October 2021 05:30 AM UTC.
>
> -Jaikiran
>

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.12 based on RC1

[Maarten Coene]

+1

Maarten




Op donderdag 30 september 2021 04:58:56 CEST schreef Jaikiran Pai 
: 





I've created a release candidate for 1.10.12:

git tag: ANT_1.10.12_RC1
 on commit: cb7f242aa099c069bd75e6ee4d6e50b56fd73b71
tarballs: https://dist.apache.org/repos/dist/dev/ant/
  revision: 50166
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant-1051/
Snapcraft Build
  Revision 21 in latest/candidate

This release is mainly a bug fix release and the exact changes are noted 
in 
https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.12.html. 
Of particular interest is the relatively minor bug fix in the javadoc 
task which is necessary for it to work properly in the recently released 
Java 17 version.

This vote will be open at least for 72 hours and close no earlier than 
4th October 2021 03:00 AM UTC (given that it's a weekend in the next 
couple of days, I decided to extend the voting period till Monday)


-Jaikiran



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.11 based on RC1

[Maarten Coene]

+1

Maarten






Op zaterdag 10 juli 2021 20:51:38 CEST schreef Stefan Bodewig 
: 





Hi all

I've created a release candidate for 1.10.11:

git tag: ANT_1.10.11_RC1
        on commit: 01ce0c3b1
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 48767
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1049/org/apache/ant/

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.9.16 based on RC1

[Maarten Coene]

+1

Tested on our build infrastructure, no issues found.

Maarten





Op zaterdag 10 juli 2021 20:14:36 CEST schreef Stefan Bodewig 
: 





[re-send with fixed subject, sorry]


Hi all

I've created a release candidate for 1.9.16:

git tag: ANT_1.9.16_RC1
        on commit: ea698c454
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 48766
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1049/org/apache/ant/

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache AntUnit 1.4.1 based on RC1

[Maarten Coene]

+1

Maarten




Op zaterdag 3 juli 2021 14:41:50 CEST schreef Stefan Bodewig 
: 





Hi all

I've created a release candidate for AntUnit 1.4.1:

git tag: 1_4_1_RC1
        on commit: e436acf
tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
        revision: 48645
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1048/org/apache/ant/ant-antunit/1.4.1/

This Vote will be open at least for 72 hours and close no earlier than
2021-07-06 13:00UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.10 based on RC1

[Maarten Coene]

+1

Maarten






Op maandag 12 april 2021 06:31:29 CEST schreef Jaikiran Pai 
: 





I've created a release candidate for 1.10.10:

git tag: ANT_1.10.10_RC1
 on commit: eccd0a2ceb4fa854ee9f2a95cfea10d55a485dda
tarballs: https://dist.apache.org/repos/dist/dev/ant/
  revision: 46988
Maven artifacts:
https://repository.apache.org/content/repositories/orgapacheant-1047/org/apache/ant/
Snapcraft Build
  Revision 18 in latest/candidate

This vote will be open at least for 72 hours and close no earlier than 
15th April 2021 04:30 AM UTC.


-Jaikiran


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.9 based on RC1

[Maarten Coene]

+1

I could only do some minimal testing, no issues found.

Maarten






Op zondag 27 september 2020 12:29:02 CEST schreef Stefan Bodewig 
: 





Hi all

as mentioned in my last mail the release contains a decision about
implementing Nashorn support for graal.js that hasn't been discussed
before. Please don't hesitate voting -1 if you disagree with the way I
did.

I've created a release candidate for 1.10.9:

git tag: ANT_1.10.9_RC1
        on commit: 15686e56d
tarballs: https://dist.apache.org/repos/dist/dev/ant/
          revision: 41602
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1046/org/apache/ant/
Snapcraft Build
          Revision 17 in latest/candidate

This Vote will be open at least for 72 hours and close no earlier than
2020-09-30 10:30UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Release Plans for 1.10.9

[Maarten Coene]

Yes, excellent plan! :-)


Maarten






Op maandag 21 september 2020 08:32:06 CEST schreef Jaikiran Pai 
: 





Hello Stefan,

This sounds fine to me.

-Jaikiran

On 21/09/20 12:00 pm, Stefan Bodewig wrote:
> Hi all
>
> now that Java 15 is out I'd like to cut a new 1.10 release with GraalVM
> JavaScript support baked in. For that I intend to enable full Nashorn
> compatibility and allow users to disable it with a magic property.
>
> Apart from that I don't foresee any additional changes to the master
> branch.
>
> If things go to plan I should be able to implement that by the end of
> the week/around weekend and want to cut the release candidate early next
> week if not sooner.
>
> Thoughts?
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org

>

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [DISCUSS] EOL the 1.9.x branch with the 1.9.15 release

[Maarten Coene]

Hi Stefan,

could you explain a bit more why we should EOL the 1.9.x branch?

Personally, I think it's a mistake to abondon the Java 5 support.
I think there are still projects around targetting java 5, 6 or 7 using Ant as 
build tool.

For instance, one of the reasons we are still using Ant 1.9.x is that we have 
some projects that require to run on Java 6.
Upgrading these projects to Java 8 is not yet possible, since some dependencies 
are not Java 8 compatible.
I don't know if you tried to run some junit tests on a java 6 jre with an Ant 
1.10.x release, it isn't possible, even in forked mode.

But maybe you can convince me with some good arguments :-)


Maarten




Op woensdag 20 mei 2020 13:24:12 CEST schreef Stefan Bodewig 
: 





It looks as if the vote will simply not pass because of a lack of
participation - which is certainly fine. Unless we get more binding
votes, I'll close the vote as failed soon.

Mayby we should have discussed the motion here before I created the
vote. Therefore I have created this separate thread. If you don't feel
you want to discuss the topic then please just ignore me :-)


Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.10.8 based on RC1

[Maarten Coene]

+1

Maarten




Op zondag 10 mei 2020 16:59:23 CEST schreef Stefan Bodewig 
: 





Hi all

I've created a release candidate for 1.10.8:

git tag: ANT_1.10.8_RC1
        on commit: e04bc3455
tarballs: https://dist.apache.org/repos/dist/dev/ant/
          revision: 39345
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1045/org/apache/ant/
Snapcraft Build
          Revision 15 in latest/candidate

This Vote will be open at least for 72 hours and close no earlier than
2020-05-13 15:00UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Apache Ant 1.9.15 based on RC1

[Maarten Coene]

+1

I've tested this on our build infrastructure and all went fine :)

Maarten




Op zondag 10 mei 2020 16:16:49 CEST schreef Stefan Bodewig 
: 





Hi all

I've created a release candidate for 1.9.15:

git tag: ANT_1.9.15_RC1
        on commit: a03326036
tarballs: https://dist.apache.org/repos/dist/dev/ant/
          revision: a03326036
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1044/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2020-05-13 14:30UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: issue ivy 2.5.0 rc1

[Maarten Coene]

Thanks for the report Patrick,

it seems this issue has already been fixed in git some time ago.
It should be available in an upcoming release or in a recent nightly build.


Maarten



Op donderdag 10 oktober 2019 20:24:50 CEST schreef ENJOLRAS Patrick 
: 





  


Hello,

 

Using Ivy 2.5.0 rc1 and  2.4.0, I had very often encountered a retrieve issue 
with the exception:  java.lang.UnsupportedOperationException…

 

I had debug it, it comes from 

org.apache.ivy.util.FileUtil.java

 

184 existingChild.remove(childDest);

 

To fix it

Line 174 existingChild = new 
java.util.LinkedList(Arrays.asList(children));

 

Encapsulate arraysList as linkedList to be able to apply remove(File) 
function.(ArrayList fixed size cannot apply remove(File ) on it 
=>unsupportedOperationException)

 

    If someone could do the modification or tell me how to submit 
it, it will be great.

 

Thanks.

 

Regards

 

  
  

  
  
Patrick Enjolras
DIS BPS R Engineer 
Tel.: 01 55 01 59 61

Gemalto is now part of the Thales Group.
Please note that my new email address is patrick.enjol...@thalesgroup.com
  
 
  
  

THALES

  
6, rue de la Verrerie 92190 Meudon


  
  
www.thalesgroup.com
  
  
  







  

  

  


 

 

 




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Ant 1.10.6 based on RC2

[Maarten Coene]

+1

Maarten




Op donderdag 2 mei 2019 16:16:42 CEST schreef Jaikiran Pai 
: 





Hello all,

I've created a release candidate RC2 for 1.10.6. This release contains
bug fixes as well as enhancements.

The release was generated using JDK 11 version (to include JDK9+
features/tasks). The minimal required version of Java runtime, to use
this Ant release, still remains Java 8.

Release notes:
    https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.10.6.html

git tag:
    ANT_1.10.6_RC2 on commit e4a56ec5bd155fccf176ea37a778c486ac5cb92c

tarballs:
    https://dist.apache.org/repos/dist/dev/ant/
    revision 33883

Maven artifacts:
  
https://repository.apache.org/content/repositories/orgapacheant-1038/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
5th May 2019 14:30 UTC.

-Jaikiran


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Ant 1.9.14 based on RC1

[Maarten Coene]

 Tested on our build infrastructure, no issues found.

+1Maarten

Op dinsdag 12 maart 2019 11:02:18 CET schreef Jaikiran Pai 
:  
 
 Hello all,

I've created a new release candidate for 1.9.14. This release contains
bug fixes as well as some enhancements.

Release notes:
       
 https://dist.apache.org/repos/dist/dev/ant/RELEASE-NOTES-1.9.14.html
git tag: ANT_1914_RC1
 on commit: 8ec8ecf4eb94b238b09161055e75508155040180
tarballs: https://dist.apache.org/repos/dist/dev/ant/
 revision: 32887
Maven artifacts:

https://repository.apache.org/content/repositories/orgapacheant-1036/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
15th March 2019 10:00UTC.

-Jaikiran




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

  

Re: ant-ivy git commit: Update the release notes

[Maarten Coene]

Without knowing the details of the change, one thing we should take care about 
is that older Ivy versions should still be able to read that property properly.
Maarten

   Op woensdag 29 augustus 2018 16:48:01 CEST schreef Gintautas Grigelionis 
:  
 
 I like the idea, though. One thing that should be investigated further is
places where location is obtained by getResource().getName()
AFAICS that happens in CacheResolver (deprecated), BasicResolver (where
also a Resource is constructed from location), and
DefaultRepositoryCacheManager. There's no uniformity in
Resource-implementing classes either, sometimes getName() works on an URI,
sometimes a path string.

Gintas

On Wed, 29 Aug 2018 at 08:34, Jaikiran Pai  wrote:

> More of a FYI - I'm still not convinced that my fix for this handles all
> the necessary cases (looks like the ArtifactOrigin#location gets used in
> various different ways), so I may either revert back my changes or
> decide to change it in a different way. So right now, in its current
> form, my changes aren't a fix.
>
> -Jaikiran
>
>
> On 29/08/18 11:34 AM, gin...@apache.org wrote:
> > Repository: ant-ivy
> > Updated Branches:
> >  refs/heads/master d976a4a27 -> fd81f4461
> >
> >
> > Update the release notes
> >
> > Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo
> > Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/fd81f446
> > Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/fd81f446
> > Diff: http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/fd81f446
> >
> > Branch: refs/heads/master
> > Commit: fd81f44619b05a176ecbf4ff1499d64b39251520
> > Parents: d976a4a
> > Author: Gintas Grigelionis 
> > Authored: Wed Aug 29 08:03:13 2018 +0200
> > Committer: Gintas Grigelionis 
> > Committed: Wed Aug 29 08:05:12 2018 +0200
> >
> > --
> >  asciidoc/release-notes.adoc | 3 ++-
> >  1 file changed, 2 insertions(+), 1 deletion(-)
> > --
> >
> >
> >
> http://git-wip-us.apache.org/repos/asf/ant-ivy/blob/fd81f446/asciidoc/release-notes.adoc
> > --
> > diff --git a/asciidoc/release-notes.adoc b/asciidoc/release-notes.adoc
> > index cc53bb3..efa7057 100644
> > --- a/asciidoc/release-notes.adoc
> > +++ b/asciidoc/release-notes.adoc
> > @@ -85,6 +85,7 @@ For details about the following changes, check our
> JIRA install at link:https://
> >  - FIX: Don't throw a CircularDependencyException when parsing an import
> scoped dependency in dependencyManagement section of a pom (jira:IVY-1588[])
> >  - FIX: Respect exclude regardless of resolution order (jira:IVY-1486[])
> (thanks to David Turner)
> >  - FIX: ModuleDescriptorMemoryCache didn't detect outdated entries when
> Ivy file was updated in the cache by another process
> > +- FIX: Store ArtifactOrigin's location as a URL
> >
> >  - IMPROVEMENT: Throw an IllegalStateException when retrieving the
> resolutionCacheRoot on the DefaultResolutionCacheManager if the basedir (or
> IvySettings) is not set (jira:IVY-1482[])
> >  - IMPROVEMENT: Optimization: limit the revision numbers scanned if
> revision prefix is specified (Thanks to Ernestas Vaiciukeviius)
> > @@ -181,7 +182,6 @@ Here is the list of people who have contributed
> source code and documentation up
> >  * Tobias Himstedt
> >  * Achim Huegen
> >  * Pierre Hgnestrand
> > -* Ilya
> >  * Matt Inger
> >  * Anders Jacobsson
> >  * Anders Janmyr
> > @@ -196,6 +196,7 @@ Here is the list of people who have contributed
> source code and documentation up
> >  * Sebastian Krueger
> >  * Thomas Kurpick
> >  * Costin Leau
> > +* Ilya Leoshkevich
> >  * Tat Leung
> >  * Antoine Levy-Lambert
> >  * Tony Likhite
> >
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>
  

Re: Build failed in Jenkins: Ivy-tests-ubuntu » ubuntu,JDK 1.7 (latest) #360

[Maarten Coene]

And the ModuleDescriptorMemoryCacheTest failure must be my fault.
I'll look into it later this week or next week.

Maarten

  Van: Jaikiran Pai 
 Aan: Ant Developers List  
 Verzonden: vrijdag 24 augustus 9:02 2018
 Onderwerp: Re: Build failed in Jenkins: Ivy-tests-ubuntu » ubuntu,JDK 1.7 
(latest) #360
   
More of a FYI - The URLResolverTest failures, in this list, appear to be
my fault, introduced in a commit I pushed this week. I will take a look
tonight to see what the issue there is and fix (or rollback) my changes.

-Jaikiran


On 24/08/18 12:22 PM, Apache Jenkins Server wrote:
> See 
> 
>
> Changes:
>
> [maartenc] FIX: ModuleDescriptorMemoryCache didn't detect outdated entries 
> when Ivy
>
> --
> [...truncated 32.16 KB...]
>    [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,962 sec
>    [junit] Running org.apache.ivy.ant.IvyCleanCacheTest
>    [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,552 sec
>    [junit] Running org.apache.ivy.ant.IvyConfigureTest
>    [junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,596 sec
>    [junit] Running org.apache.ivy.ant.IvyConvertPomTest
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,937 sec
>    [junit] Running org.apache.ivy.ant.IvyDeliverTest
>    [junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>4,205 sec
>    [junit] Running org.apache.ivy.ant.IvyDependencyTreeTest
>    [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,566 sec
>    [junit] Running org.apache.ivy.ant.IvyDependencyUpdateCheckerTest
>    [junit] Tests run: 14, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,926 sec
>    [junit] Running org.apache.ivy.ant.IvyFindRevisionTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,868 sec
>    [junit] Running org.apache.ivy.ant.IvyInfoRepositoryTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,778 sec
>    [junit] Running org.apache.ivy.ant.IvyInfoTest
>    [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,749 sec
>    [junit] Running org.apache.ivy.ant.IvyInstallTest
>    [junit] Tests run: 15, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>3,384 sec
>    [junit] Running org.apache.ivy.ant.IvyListModulesTest
>    [junit] Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,618 sec
>    [junit] Running org.apache.ivy.ant.IvyPostResolveTaskTest
>    [junit] Tests run: 13, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,92 sec
>    [junit] Running org.apache.ivy.ant.IvyPublishTest
>    [junit] Tests run: 22, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>4,851 sec
>    [junit] Running org.apache.ivy.ant.IvyReportTest
>    [junit] Tests run: 6, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>3,306 sec
>    [junit] Running org.apache.ivy.ant.IvyRepositoryReportTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,284 sec
>    [junit] Running org.apache.ivy.ant.IvyResolveTest
>    [junit] Tests run: 35, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
>4,11 sec
>    [junit] Running org.apache.ivy.ant.IvyResourcesTest
>    [junit] Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,492 sec
>    [junit] Running org.apache.ivy.ant.IvyRetrieveBuildFileTest
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,295 sec
>    [junit] Running org.apache.ivy.ant.IvyRetrieveTest
>    [junit] Tests run: 19, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>3,52 sec
>    [junit] Running org.apache.ivy.ant.IvyTaskTest
>    [junit] Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,524 sec
>    [junit] Running org.apache.ivy.ant.IvyVarTest
>    [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>1,602 sec
>    [junit] Running org.apache.ivy.core.NormalRelativeUrlResolverTest
>    [junit] Tests run: 7, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>0,324 sec
>    [junit] Running org.apache.ivy.core.cache.DefaultRepositoryCacheManagerTest
>    [junit] Tests run: 4, Failures: 0, Errors: 0, Skipped: 1, Time elapsed: 
>1,011 sec
>    [junit] Running org.apache.ivy.core.cache.ModuleDescriptorMemoryCacheTest
>    [junit] Tests run: 10, Failures: 0, Errors: 4, Skipped: 0, Time elapsed: 
>1,004 sec
>    [junit] Test org.apache.ivy.core.cache.ModuleDescriptorMemoryCacheTest 
>FAILED
>    [junit] Running org.apache.ivy.core.deliver.DeliverTest
>    [junit] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>2,105 sec
>    [junit] Running org.apache.ivy.core.event.IvyEventFilterTest
>    [junit] Tests run: 5, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 
>0,922 sec
>    [junit] Running 

Re: [1/2] ant git commit: The selector has a new built-in algorithm 'lastmodified' which computes a value based upon the lastmodified time of the file.

[Maarten Coene]

Thanks Gintas,it was still on my todo-list to commit this to the master branch 
as well.

Maarten

  Van: "gin...@apache.org" 
 Aan: notificati...@ant.apache.org 
 Verzonden: donderdag 26 juli 18:07 2018
 Onderwerp: [1/2] ant git commit: The  selector has a new built-in 
algorithm 'lastmodified' which computes a value based upon the lastmodified 
time of the file.
   
Repository: ant
Updated Branches:
  refs/heads/master f6919079d -> 5d8bc76b1


The  selector has a new built-in algorithm 'lastmodified' which 
computes a value based upon the lastmodified time of the file.


Project: http://git-wip-us.apache.org/repos/asf/ant/repo
Commit: http://git-wip-us.apache.org/repos/asf/ant/commit/05c88a60
Tree: http://git-wip-us.apache.org/repos/asf/ant/tree/05c88a60
Diff: http://git-wip-us.apache.org/repos/asf/ant/diff/05c88a60

Branch: refs/heads/master
Commit: 05c88a60c2f8b427f3d3d4d9fbd5f71a05c6355b
Parents: 23a5135
Author: Maarten Coene 
Authored: Wed Jul 25 13:55:48 2018 +0200
Committer: Maarten Coene 
Committed: Wed Jul 25 13:55:48 2018 +0200

--
 WHATSNEW                                        |  2 +
 manual/Types/selectors.html                    |  7 +++
 .../modifiedselector/LastModifiedAlgorithm.java | 53 
 .../modifiedselector/ModifiedSelector.java      |  6 ++-
 4 files changed, 66 insertions(+), 2 deletions(-)
--


http://git-wip-us.apache.org/repos/asf/ant/blob/05c88a60/WHATSNEW
--
diff --git a/WHATSNEW b/WHATSNEW
index 357168a..28977da 100644
--- a/WHATSNEW
+++ b/WHATSNEW
@@ -6,6 +6,8 @@ Other changes:
  * generatekey task now supports SubjectAlternativeName during key
    generation.
 
+ * the  selector has a new built-in algorithm 'lastmodified'
+  which computes a value based upon the lastmodified time of the file.
 
 Changes from Ant 1.9.12 TO Ant 1.9.13
 =

http://git-wip-us.apache.org/repos/asf/ant/blob/05c88a60/manual/Types/selectors.html
--
diff --git a/manual/Types/selectors.html b/manual/Types/selectors.html
index 402c711..c260efd 100644
--- a/manual/Types/selectors.html
+++ b/manual/Types/selectors.html
@@ -742,6 +742,7 @@
                 hashvalue - HashvalueAlgorithm 
                 digest - DigestAlgorithm 
                 checksum - ChecksumAlgorithm 
+                 lastmodified - LastModifiedAlgorithm 
            
        
         No, defaults to digest 
@@ -869,6 +870,12 @@
          
        
      
+      
+         lastmodified 
+         Uses the lastModified property of a file. No 
additional
+          configuration is required.
+        
+      
       Cache options 

      
         propertyfile 

http://git-wip-us.apache.org/repos/asf/ant/blob/05c88a60/src/main/org/apache/tools/ant/types/selectors/modifiedselector/LastModifiedAlgorithm.java
--
diff --git 
a/src/main/org/apache/tools/ant/types/selectors/modifiedselector/LastModifiedAlgorithm.java
 
b/src/main/org/apache/tools/ant/types/selectors/modifiedselector/LastModifiedAlgorithm.java
new file mode 100644
index 000..af8358a
--- /dev/null
+++ 
b/src/main/org/apache/tools/ant/types/selectors/modifiedselector/LastModifiedAlgorithm.java
@@ -0,0 +1,53 @@
+/*
+ *  Licensed to the Apache Software Foundation (ASF) under one or more
+ *  contributor license agreements.  See the NOTICE file distributed with
+ *  this work for additional information regarding copyright ownership.
+ *  The ASF licenses this file to You under the Apache License, Version 2.0
+ *  (the "License"); you may not use this file except in compliance with
+ *  the License.  You may obtain a copy of the License at
+ *
+ *      http://www.apache.org/licenses/LICENSE-2.0
+ *
+ *  Unless required by applicable law or agreed to in writing, software
+ *  distributed under the License is distributed on an "AS IS" BASIS,
+ *  WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ *  See the License for the specific language governing permissions and
+ *  limitations under the License.
+ *
+ */
+
+package org.apache.tools.ant.types.selectors.modifiedselector;
+
+import java.io.File;
+
+/**
+ * Computes a 'timestamp' of file based on the lastModified time of that file.
+ *
+ * @version 2018-07-25
+ * @since  Ant 1.10.6 and 1.9.14
+ */
+public class LastModifiedAlgorithm implements Algorithm {
+
+    /**
+    * This algorithm doesn't need any configuration.
+    * Therefore it's always valid.
+    * @return always true
+    */
+    public boolean isValid() {
+        return true;
+    }
+
+    /**
+    * Computes a 'timestamp' for a file based on the lastModified time.
+    * @param file  The file for w

Re: [VOTE] Release Ant 1.10.5 based on RC1

[Maarten Coene]

We did some minimal testing with this version in our build process.No issues 
were found.
+1
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: dinsdag 10 juli 11:55 2018
 Onderwerp: [VOTE] Release Ant 1.10.5 based on RC1
   
Hi all

I've created a new release candidate for 1.10.5 with a few bug fixes and
and the "single source executable" feature for Java11.

git tag: ANT_1.10.5_RC1
        on commit: c0848d2c6
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 28015
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1035/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-07-13 10:00UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.13 based on RC1

[Maarten Coene]

Tried this version in our build process.No issues were found.
+1
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: dinsdag 10 juli 11:56 2018
 Onderwerp: [VOTE] Release Ant 1.9.13 based on RC1
   
Hi all

I've created a new release candidate for 1.9.13 with a few bug fixes.

git tag: ANT_1.9.13_RC1
        on commit: e7a4d8683
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 28014
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1034/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-07-13 10:00UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release AntUnit 1.4 based on RC3

[Maarten Coene]

+1
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: vrijdag 22 juni 7:32 2018
 Onderwerp: [VOTE] Release AntUnit 1.4 based on RC3
   
Hi all

this is the third RC for AntUnit 1.4 with the problems Gintas identified
fixed.

tag:
    
https://git-wip-us.apache.org/repos/asf?p=ant-antlibs-antunit.git;a=tag;h=fb7a42470f8a6de50686f37519e27a068c576606

tarballs:
    https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/
    svn revision 27641

Maven artifacts:
    
https://repository.apache.org/content/repositories/orgapacheant-1033/org/apache/ant/ant-antunit/1.4/

vote will be open for 72 hours and not close before 2018-06-25 05:30 UTC.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.10.4 based on RC1

[Maarten Coene]

+1
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: dinsdag 19 juni 9:08 2018
 Onderwerp: [VOTE] Release Ant 1.10.4 based on RC1
   
Hi all

I've created a new release candidate for 1.10.4 with a bunch of bug
fixes and the "ZipSlip" adjustment.

git tag: ANT_1.10.4_RC1
        on commit: 9dc3e788b
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 27553
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1031/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-06-22 08:30UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.12 based on RC1

[Maarten Coene]

+1
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: dinsdag 19 juni 9:08 2018
 Onderwerp: [VOTE] Release Ant 1.9.12 based on RC1
   
Hi all

I've created a new release candidate for 1.9.12 with a bunch of bug
fixes and the "ZipSlip" adjustment.

git tag: ANT_1_9_12_RC1
        on commit: 6e694d820
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 27552
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1030/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-06-22 08:30UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [1/2] ant git commit: Deprecate CollectionUtils and Enumerations; reduce explicit use of Enumeration

[Maarten Coene]

Converting an Enumeration to a List just for iterating it doesn't seem 
performance and memory wise a good idea to me.
Maarten

  Van: "gin...@apache.org" 
 Aan: notificati...@ant.apache.org 
 Verzonden: woensdag 16 mei 19:13 2018
 Onderwerp: [1/2] ant git commit: Deprecate CollectionUtils and Enumerations; 
reduce explicit use of Enumeration
   
Repository: ant
Updated Branches:
  refs/heads/master ac35c0014 -> 070c3bc86


http://git-wip-us.apache.org/repos/asf/ant/blob/070c3bc8/src/main/org/apache/tools/ant/types/ZipScanner.java
--
diff --git a/src/main/org/apache/tools/ant/types/ZipScanner.java 
b/src/main/org/apache/tools/ant/types/ZipScanner.java
index a3df040..5667159 100644
--- a/src/main/org/apache/tools/ant/types/ZipScanner.java
+++ b/src/main/org/apache/tools/ant/types/ZipScanner.java
@@ -20,7 +20,7 @@ package org.apache.tools.ant.types;
 
 import java.io.File;
 import java.io.IOException;
-import java.util.Enumeration;
+import java.util.Collections;
 import java.util.Map;
 import java.util.zip.ZipException;
 
@@ -62,10 +62,7 @@ public class ZipScanner extends ArchiveScanner {
                "Only file provider resources are supported"));
 
        try (ZipFile zf = new ZipFile(srcFile, encoding)) {
-
-            Enumeration e = zf.getEntries();
-            while (e.hasMoreElements()) {
-                ZipEntry entry = e.nextElement();
+            for (ZipEntry entry : Collections.list(zf.getEntries())) {
                Resource r = new ZipResource(srcFile, encoding, entry);
                String name = entry.getName();
                if (entry.isDirectory()) {


   

ivy change

[Maarten Coene]

Hi,
I've committed a change to ModuleDescriptorMemoryCache.Where should I document 
this change? Is it 'release-notes.adoc'?

Maarten

Re: [VOTE] Ivy 2.5.0-rc1 Release

[Maarten Coene]

+1
I couldn't test the Ant tasks though as we still run Ant with Java 6.


Maarten
  Van: Nicolas Lalevée 
 Aan: Ant Developers List  
 Verzonden: donderdag 12 april 18:29 2018
 Onderwerp: [VOTE] Ivy 2.5.0-rc1 Release
   
I have built a release candidate for Ivy 2.5.0-rc1.

The git tag of this release is: 
https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/2.5.0-rc1
 

 with the sha1 887fd46f3e90016e313f7724ca259b936d30a03e

The artifacts has been published to: 
https://dist.apache.org/repos/dist/dev/ant/ivy/2.5.0-rc1 
 at revision 26310

The staging Maven repository is available there: 
https://repository.apache.org/content/repositories/orgapacheant-1026 


The Eclipse updatesite has been build there: 
https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivy-2.5.0.cr1_20180412005306
 


Do you vote for the release of these binaries?

Regards,
Nicolas


   

Re: JunitTestRunner commit

[Maarten Coene]

Thanks Stefan for your time and patience :-)I think I finally got it merged 
into the 1.9.x branch...(Where are the days where everything was so easy with 
SVN ;-))
I did a little test, and I didn't see a difference compared to 1.10.3 in the 
error output when a test has a failing static initializer.
thanks,Maarten


  Van: Stefan Bodewig <bode...@apache.org>
 Aan: dev@ant.apache.org 
 Verzonden: donderdag 5 april 8:25 2018
 Onderwerp: Re: JunitTestRunner commit
   
On 2018-04-04, Maarten Coene wrote:

> Since this is more or less my first commit to the Ant codebase, could
> someone please review my change to JunitTestRunner ?

Typo in WHATSNEW (until rather than untill).

I think the change is good, although I'm not sure whether there is a
difference in how a failure in the static initializer of a real test
class gets reported now. I.e. do I get the exact same error/failure
output from your testStaticInitializerErrorTestCase that would be
created in 1.10.3?

> And if all is ok, what is the correct way to merge this into the 1.9.x
> branch?

Personally I prefer to do it the other way around - commit to 1.9.x and
merge to master - but that's too late now. In either case, as the master
branch is evolving merge conflicts will become more prevalent over
time. Most likely you will get by with just a single conflict in
WHATSNEW that you'll need to resolve manually. Something like

git checkout 1.9.x
git cherry-pick 30c9dee9bad90e56703554d21819cec6033276dc
# most likely resolve conflict and commit
git cherry-pick 20b6163989fdf4e98d7739fca3cdf9f18a5bdc7a

should probably work. If you need any help, please ask.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [2/2] ant git commit: Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ant

[Maarten Coene]

Sorry, I have no idea what this is... should it be reverted?
(I'm a Git noob and this is something that my IntelliJ git plugin seems to have 
done).

Maarten

  Van: "maart...@apache.org" <maart...@apache.org>
 Aan: notificati...@ant.apache.org 
 Verzonden: donderdag 5 april 11:33 2018
 Onderwerp: [2/2] ant git commit: Merge branch 'master' of 
https://git-wip-us.apache.org/repos/asf/ant
   
Merge branch 'master' of https://git-wip-us.apache.org/repos/asf/ant


Project: http://git-wip-us.apache.org/repos/asf/ant/repo
Commit: http://git-wip-us.apache.org/repos/asf/ant/commit/f2459248
Tree: http://git-wip-us.apache.org/repos/asf/ant/tree/f2459248
Diff: http://git-wip-us.apache.org/repos/asf/ant/diff/f2459248

Branch: refs/heads/master
Commit: f2459248f23aa439e2c5ab642d9d9d7e6cffc933
Parents: 277906b 26c8789
Author: Maarten Coene <maart...@apache.org>
Authored: Thu Apr 5 11:32:22 2018 +0200
Committer: Maarten Coene <maart...@apache.org>
Committed: Thu Apr 5 11:32:22 2018 +0200

--
 .../org/apache/tools/ant/AntClassLoader.java    |  16 +-
 .../org/apache/tools/ant/DefaultLogger.java    |  3 +-
 .../org/apache/tools/ant/DirectoryScanner.java  |  1 +
 src/main/org/apache/tools/ant/Main.java        |  2 +-
 .../org/apache/tools/ant/PathTokenizer.java    |  6 +-
 src/main/org/apache/tools/ant/Project.java      |  8 +-
 .../org/apache/tools/ant/ProjectHelper.java    |  6 +-
 .../org/apache/tools/ant/PropertyHelper.java    |  30 ++--
 .../apache/tools/ant/RuntimeConfigurable.java  |  25 ++--
 .../tools/ant/TaskConfigurationChecker.java    |  10 +-
 src/main/org/apache/tools/ant/XmlLogger.java    |  3 +-
 .../tools/ant/attribute/BaseIfAttribute.java    |  3 +-
 .../tools/ant/filters/ClassConstants.java      |  31 ++--
 .../apache/tools/ant/filters/ConcatFilter.java  |  8 +-
 .../tools/ant/filters/ExpandProperties.java    |  4 +-
 .../apache/tools/ant/filters/HeadFilter.java    |  8 +-
 .../tools/ant/filters/LineContainsRegExp.java  |  6 +-
 .../apache/tools/ant/filters/SortFilter.java    |  5 +-
 .../tools/ant/filters/StripJavaComments.java    |  3 +-
 .../apache/tools/ant/filters/TailFilter.java    |  8 +-
 .../tools/ant/filters/util/JavaClassHelper.java |  15 +-
 .../apache/tools/ant/helper/ProjectHelper2.java | 150 ++-
 .../tools/ant/helper/ProjectHelperImpl.java    |  75 ++
 .../org/apache/tools/ant/launch/Locator.java    |  2 +-
 .../apache/tools/ant/taskdefs/AntStructure.java |  33 ++--
 .../org/apache/tools/ant/taskdefs/Concat.java  |  11 +-
 .../org/apache/tools/ant/taskdefs/Copy.java    |  14 +-
 .../org/apache/tools/ant/taskdefs/EchoXML.java  |  2 +-
 .../org/apache/tools/ant/taskdefs/Expand.java  |  23 +--
 src/main/org/apache/tools/ant/taskdefs/Get.java |  15 +-
 src/main/org/apache/tools/ant/taskdefs/Jar.java |  5 +-
 .../org/apache/tools/ant/taskdefs/Javac.java    |  6 +-
 .../org/apache/tools/ant/taskdefs/Manifest.java |  29 +---
 .../org/apache/tools/ant/taskdefs/Recorder.java |  3 +-
 .../org/apache/tools/ant/taskdefs/Replace.java  |  2 +-
 .../org/apache/tools/ant/taskdefs/Rmic.java    |  5 +-
 src/main/org/apache/tools/ant/taskdefs/Tar.java |  4 +-
 .../org/apache/tools/ant/taskdefs/UpToDate.java |  13 +-
 .../compilers/DefaultCompilerAdapter.java      |  7 +-
 .../ant/taskdefs/condition/IsReference.java    |  19 +--
 .../apache/tools/ant/taskdefs/condition/Os.java |  4 +-
 .../ant/taskdefs/cvslib/ChangeLogParser.java    |  8 +-
 .../taskdefs/launcher/VmsCommandLauncher.java  |  2 +-
 .../tools/ant/taskdefs/optional/NetRexxC.java  |  6 +-
 .../ant/taskdefs/optional/RenameExtensions.java |  1 +
 .../ant/taskdefs/optional/SchemaValidate.java  |  26 ++--
 .../taskdefs/optional/depend/AntAnalyzer.java  |  4 +-
 .../ant/taskdefs/optional/ejb/IPlanetEjbc.java  |  33 ++--
 .../taskdefs/optional/jdepend/JDependTask.java  |  2 +
 .../optional/jlink/ClassNameReader.java        |  3 +-
 .../compilers/DefaultJspCompilerAdapter.java    |  11 +-
 .../ant/taskdefs/optional/junit/JUnitTask.java  |  21 +--
 .../junit/SummaryJUnitResultFormatter.java      |  14 +-
 .../AbstractJUnitResultFormatter.java          |  4 -
 .../junitlauncher/JUnitLauncherTask.java        |  2 -
 .../LegacyPlainResultFormatter.java            |  4 +-
 .../junitlauncher/LegacyXmlResultFormatter.java |  1 -
 .../native2ascii/BuiltinNative2Ascii.java      |  18 +--
 .../tools/ant/taskdefs/optional/net/FTP.java    |  11 +-
 .../optional/net/FTPTaskMirrorImpl.java        |  3 +-
 .../ant/taskdefs/optional/ssh/SSHExec.java      |  2 +-
 .../taskdefs/optional/ssh/ScpFromMessage.java  |  4 +-
 .../optional/ssh/ScpFromMessageBySftp.java      |  6 +-
 .../apache/tools/ant/types/AbstractFileSet.java |  8 +-
 .../org/apache/tools/ant/types/Commandline.java |  19 +--
 .../apache/tools/ant/types/CommandlineJava.java |  13 +-
 .../org/apache/tools/ant/types/PropertySet.java |  3 +-
 .../ant/types/resources/PropertyResource.java  

JunitTestRunner commit

[Maarten Coene]

Hi,
Since this is more or less my first commit to the Ant codebase, could someone 
please review my change to JunitTestRunner ?And if all is ok, what is the 
correct way to merge this into the 1.9.x branch?

Maarten

Re: [VOTE] Release Ant 1.10.3 based on RC2

[Maarten Coene]

+1
I couldn't test this version though...so I only verified that it contained the 
license and other required files.

Maarten


  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: zaterdag 24 maart 13:48 2018
 Onderwerp: [VOTE] Release Ant 1.10.3 based on RC2
   
Hi all

I've created a new release candidate for 1.10.3 incorporating the doc
fix for junitlauncher:

git tag: ANT_1.10.3_RC2
        on commit: 1b9cc239e
tarballs: https://dist.apache.org/repos/dist/dev/ant/
        revision: 25934
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1025/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-03-27 13:00UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.11 based on RC1

[Maarten Coene]

+1
We tested this version in our build environment, no issues were found.
Maarten


  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: vrijdag 23 maart 18:31 2018
 Onderwerp: [VOTE] Release Ant 1.9.11 based on RC1
   
Hi all

I've created a release candidate for 1.9.11:

git tag: ANT_1_9_11_RC1
        on commit: 6f58cfd
tarballs: https://dist.apache.org/repos/dist/dev/ant/
          revision: 25910
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1120/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-03-26 17:30UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.10 based on RC1

[Maarten Coene]

+1
We did test this version in our environment, no issues were found.

Maarten


  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: zaterdag 3 februari 17:32 2018
 Onderwerp: [VOTE] Release Ant 1.9.10 based on RC1
   
Hi all

I've created a release candidate for 1.9.10:

git tag: ANT_1_9_10_RC1
        on commit: 528c94e
tarballs: https://dist.apache.org/repos/dist/dev/ant/
          revision: 24666
Maven artifacts:
        
https://repository.apache.org/content/repositories/orgapacheant-1020/org/apache/ant/

This Vote will be open at least for 72 hours and close no earlier than
2018-02-06 16:30UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: IVY-1282

[Maarten Coene]

Without looking at the JIRA issue, the 'specification' of what 'A;B' should do 
is explained here: 
http://ant.apache.org/ivy/history/latest-milestone/ivyfile/dependency.html

without a defaultconfmapping set the following should be equivalent:
A;B = A->A;B->B

Maarten

  Van: Gintautas Grigelionis 
 Aan: Ant Developers List  
 Verzonden: vrijdag 2 februari 9:55 2018
 Onderwerp: IVY-1282
   
It seems that there still are problems with conf mappings containing
whitespace around semicolon separator. The rules for using semicolon are
supposedly self-evident and are not explained anywhere AFAICS.

My understanding is that semicolon is used in situtations when different
confs have different mappings, like "A->default;B->master" or "A;B->master"
when defaultconfmapping is set. I cannot find a specification, though, what
should happen when defaultconfmapping is not set or when conf is "A;B": an
exception or semicolon interpreted as comma?

Gintas


   

Re: Ivy-2.5.0

[Maarten Coene]

The change to the URLHandler class (TimoutConstraint) is also backwards 
incompatible.The IvyIdea plugin (IntelliJ) breaks on this which contains an 
extension of AbstractURLHandler.
I didn't look into it yet, maybe it can be changed to be more backwards 
compatible?

kind regards,Maarten 

  Van: Gintautas Grigelionis 
 Aan: Ant Developers List  
 Verzonden: dinsdag 9 januari 9:45 2018
 Onderwerp: Re: Ivy-2.5.0
   
2018-01-09 7:12 GMT+00:00 Jan Matèrne (jhm) :

> > What must be done to complete the work on SVG (IVY-922/IVY-450 or resp
> > PR-55/PR-60)? If you fine with merging (eventually adjusting the
> > contents of SVG), let's do it.
>
> I added a comment on the PR.
> For short:
> - license header is missed on two files
> - improve two JavaDocs
> - test: does the fresh built Ivy use the SVG graphics?
>

I hope I addressed all points now.


>
> > Changes to alleviate IVY-1315/IVY-1419/IVY-1420/IVY-1437 should be
> > evaluated by reporters, but nobody responded because the issues are so
> > old.
> > I would rather close the issues and a open a new issue if needed. I
>
> No. It's just a matter of prioritization by us.
>
>
>
> > added test cases for every issue highlighting the specific parts of the
> > problem and I can write up separately on the design problem with
> > permitting the same attributes on different elements with recursive
> > inheritance or using the same attribute name with different semantics
> > depending on the element (perhaps in Confluence? or Github wiki?).
>
> Can't understand the problem (haven't that knowledge of Ivy).
> IVY-1315 "is related to" IVY-1420, which is resolved.
> Is IVY-1315 also resolved? Then just close that issue.
>

The problem is that the same set of attributes is allowed on both
configurations and dependencies. However, it is the attrubte values for
last element (dependencies) that are definitive -- unless they're absent.

Both configurations and dependencies can be inherited ("extended"); on top
of that, configurations allow for includes, which I guess predates
extension, and includes can have the attributes, too.

So the problem is: while ivy.xml is updated, the values of attributes may
change. Because ivy.xml is written in chunks, configurations (processed
early) may end up with different attribute values than dependencies (which
are definitive). That makes no difference when processed ivy.xml is
resolved, but might mess up subsequent extends.

Because the whole mechanism is underspecified, I tend to leave it as is
(put the final values of attributes on dependencies) rather than cache
configurations and publications until attributes on dependencies are
processed in order to guarantee that attributes have identical values for
both configurations and dependencies (or that configurations get the final
values if no attributes were present on dependencies).

I will close all issues pertaining to the attributes. When we agree on
specification, we can open a new one if needed.


> > My opinion on PR-57 is that it addresses another design problem in a
> > similarly good-enough fashion. We can handle this like Ant and have a
> > Java
> > 7 branch (2.5.x) and a Java 8+ branch with further API changes (2.6.x).
> > The question is, whether that makes 2.5.x more interesting and is worth
> > the extra work?
>
> I wouldn't create an extra branch just for that.
> I am more a fan of moving to a newer Java version after that release.
>
> I recap the PR-57:
> - multiple changes array->collection
> - all are fine expect one
> - one central public interface added one new method
>  -- no changes in semantics, but only in method declaration
> (array->collection, generics)
>  -- technically one new method and deprecating the old
> - this means breaking backwards compatibility
> - proposal is adding a 2nd interface extending the original interface and
> adding that new method
>  (could be 'inlined' in later Ivy version).
>
> I followed the mail thread https://www.mail-archive.com/
> dev@ant.apache.org/msg46002.html and found another problem
> - ModuleRules breaks BWC due the same reason (as you pointed it out).
>
> Maybe we should not include this PR into an Ivy-2.5.0 release but instead
> move Ivy-2.6.0 to Java8 and change these parts in a (IMO) right but
> backwards incompatible way.
>

PR-57 is narrowed down specificaly to the method addition in
DependencyResolver. That affects every resolver implementation; however, a
default method implementation is provided in AbstractResolver and all known
third party implementations use it.

We can kick the can down the road, but the important point is that Java
permits no arrays of generics and we must fix that.

Gintas

   

Re: Error while testing 2.5.0-SNAPSHOT

[Maarten Coene]

Jaikiran,
probably only reproducible on a Windows machine...
Maarten

  Van: Aurélien Pupier 
 Aan: Ant Developers List  
 Verzonden: maandag 25 september 13:41 2017
 Onderwerp: Re: Error while testing 2.5.0-SNAPSHOT
   
Hello Jaikiran,

Source repositories implicated are:
- Fuse Tooling: https://github.com/jbosstools/jbosstools-fuse
- Camel: https://github.com/apache/camel/tree/camel-2.19.3
- Groovy: https://github.com/groovy/groovy-core/tree/GROOVY_2_4_3

I wasn't able to build the whole chain to include latest Ivy snapshot.

To reproduce, I did:
- replace ivy jar in org.fusesource.ide.camel.model.service.impl by an Ivy
2.5.0-SNAPSHOT build
- update of org.fusesource.ide.camel.model.service.impl MANIFEST.MF to
include the correct version of added snapshot


Regards,

On Mon, Sep 25, 2017 at 9:05 AM, Jaikiran Pai 
wrote:

> Is there a source repo and steps that I can follow to build and reproduce
> this issue? My attempts so far haven't been able to reproduce this.
>
> -Jaikiran
>
>
> On 14/09/17 1:57 PM, Aurélien Pupier wrote:
>
>> Hello,
>>
>> I'm trying to test https://issues.apache.org/jira/browse/IVY-1568 using
>> latest 2.5.0-SNAPSHOT as suggested.
>>
>> Unfortunately, I got errors for non-snapshots artefacts which were working
>> with 2.4.0 version.
>> I will need to investigate more but Ivy developers might detect faster
>> than
>> me what is going wrong. Please find the whole errors that i captured here
>> . Here is
>> an
>> extract of the stacktrace which seems interesting
>>
>> red-hat-ga-repository: downloading https://maven.repository.
>> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
>> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom.sha1
>> to C:\Users\AURELI~1\AppData\Local\Temp\ivytmp8576317204837329542sha1
>> sha1 OK for https://maven.repository.redhat.com/ga/org/apache/
>> camel/camel-catalog/2.17.0.redhat-630283/camel-catalog-2.
>> 17.0.redhat-630283.pom
>> [SUCCESSFUL ] org.apache.camel#camel-catalog;2.17.0.redhat-630283!
>> camel-catalog.pom(pom.original) (139ms)
>> ERROR: HttpClientHandler: URI does not specify a valid host name:
>> file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> url=file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> WARN: io problem while parsing ivy file: https://maven.repository.
>> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
>> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom
>>  (org.apache.http.client.ClientProtocolException: URI does not specify a
>> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original)
>> org.apache.http.client.ClientProtocolException: URI does not specify a
>> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(
>> CloseableHttpClient.java:94)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(
>> CloseableHttpClient.java:82)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(
>> CloseableHttpClient.java:107)
>> at org.apache.ivy.util.url.HttpClientHandler.doGet(
>> HttpClientHandler.java:313)
>> at org.apache.ivy.util.url.HttpClientHandler.openStream(
>> HttpClientHandler.java:141)
>> at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:122)
>> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
>> parseDescriptor(PomModuleDescriptorParser.java:126)
>> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
>> parseDescriptor(PomModuleDescriptorParser.java:116)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager$
>> MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.
>> java:835)
>> at org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(
>> ModuleDescriptorMemoryCache.java:68)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(
>> DefaultRepositoryCacheManager.java:852)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.
>> cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1361)
>> at org.apache.ivy.plugins.resolver.BasicResolver.parse(
>> BasicResolver.java:536)
>> at org.apache.ivy.plugins.resolver.BasicResolver.
>> getDependency(BasicResolver.java:273)
>> at org.apache.ivy.plugins.resolver.IBiblioResolver.
>> getDependency(IBiblioResolver.java:550)
>> at org.apache.ivy.plugins.resolver.ChainResolver.
>> getDependency(ChainResolver.java:101)
>> at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:183)
>> at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
>> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
>> 

Re: Fw: [2/2] ant-ivy git commit: Merge remote-tracking branch 'origin/master'

[Maarten Coene]

I remember IntelliJ was saying something about a failed commit asking me to 
merge to the last revision.
I still don't understand why this results in 2 commits. (my knowledge of git is 
very limited as you can see)
But I guess this is ok? Or should it be reverted somehow?

Maarten

  Van: Jaikiran Pai <jai.forums2...@gmail.com>
 Aan: dev@ant.apache.org 
 Verzonden: woensdag 12 juli 17:53 2017
 Onderwerp: Re: Fw: [2/2] ant-ivy git commit: Merge remote-tracking branch 
'origin/master'
   
I'm guessing that while committing the fix for IVY-1404 you probably did 
a "git merge" against latest master of upstream, which created this 
merge commit.


-Jaikiran


On 12/07/17 1:45 PM, Maarten Coene wrote:
>
> Any idea where this commit comes from?I didn't touch any of these files as 
> far as I know...
> Maarten
>
>      
> - Doorgestuurd bericht -
>  Van: "maart...@apache.org" <maart...@apache.org>
>  Aan: notificati...@ant.apache.org
>  Verzonden: woensdag 12 juli 10:06 2017
>  Onderwerp: [2/2] ant-ivy git commit: Merge remote-tracking branch 
>'origin/master'
>    
> Merge remote-tracking branch 'origin/master'
>
>
> Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo
> Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/1a36ae09
> Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/1a36ae09
> Diff: http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/1a36ae09
>
> Branch: refs/heads/master
> Commit: 1a36ae09d2848d687895532acf46531437721692
> Parents: 585a702 dcaacf4
> Author: Maarten Coene <maart...@apache.org>
> Authored: Wed Jul 12 10:05:54 2017 +0200
> Committer: Maarten Coene <maart...@apache.org>
> Committed: Wed Jul 12 10:05:54 2017 +0200
>
> --
>  .../xml/XmlModuleDescriptorParserTest.java      | 56 
>  .../hello/test-ivy-extends-absolute.xml        | 25 +
>  .../plugins/parser/xml/foo%2Fbar/parent-ivy.xml | 27 ++
>  3 files changed, 108 insertions(+)
> --
>
>
>
>
>    


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: AW: [VOTE] IvyDE requirements

[Maarten Coene]

+1
Maarten


  Van: Jan Matèrne (jhm) 
 Aan: 'Ant Developers List'  
 Verzonden: woensdag 12 juli 6:59 2017
 Onderwerp: AW: [VOTE] IvyDE requirements
   
summa summarum +2 ;-)

Jan

> -Ursprüngliche Nachricht-
> Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com]
> Gesendet: Dienstag, 11. Juli 2017 23:24
> An: Ant Developers List
> Betreff: Re: [VOTE] IvyDE requirements
> 
> +1 on both (having suggested it previously).
> 
> Gintas
> 
> 2017-07-11 23:07 GMT+02:00 Nicolas Lalevée
> :
> 
> > We have recently voted to make Ivy require Java 1.7. I think we
> should
> > do it for IvyDE too.
> > Do you vote for it ?
> >
> >
> > And while making the build of IvyDE work again nicely, I had to
> update
> > its dependencies. Mainly, the build requires Eclipse 4.3, aka Eclipse
> > Kepler (it is not the newest one as you can see [1]). So let’s make
> it
> > official that we require at least Eclipse 4.3.
> > Do you vote for it ?
> >
> >
> > Nicolas
> >
> > [1] https://en.wikipedia.org/wiki/Eclipse_(software)#Releases <
> > https://en.wikipedia.org/wiki/Eclipse_(software)#Releases>
> >
> >


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


   

Fw: [2/2] ant-ivy git commit: Merge remote-tracking branch 'origin/master'

[Maarten Coene]

Any idea where this commit comes from?I didn't touch any of these files as far 
as I know...
Maarten


- Doorgestuurd bericht -
 Van: "maart...@apache.org" <maart...@apache.org>
 Aan: notificati...@ant.apache.org 
 Verzonden: woensdag 12 juli 10:06 2017
 Onderwerp: [2/2] ant-ivy git commit: Merge remote-tracking branch 
'origin/master'
   
Merge remote-tracking branch 'origin/master'


Project: http://git-wip-us.apache.org/repos/asf/ant-ivy/repo
Commit: http://git-wip-us.apache.org/repos/asf/ant-ivy/commit/1a36ae09
Tree: http://git-wip-us.apache.org/repos/asf/ant-ivy/tree/1a36ae09
Diff: http://git-wip-us.apache.org/repos/asf/ant-ivy/diff/1a36ae09

Branch: refs/heads/master
Commit: 1a36ae09d2848d687895532acf46531437721692
Parents: 585a702 dcaacf4
Author: Maarten Coene <maart...@apache.org>
Authored: Wed Jul 12 10:05:54 2017 +0200
Committer: Maarten Coene <maart...@apache.org>
Committed: Wed Jul 12 10:05:54 2017 +0200

--
 .../xml/XmlModuleDescriptorParserTest.java      | 56 
 .../hello/test-ivy-extends-absolute.xml        | 25 +
 .../plugins/parser/xml/foo%2Fbar/parent-ivy.xml | 27 ++
 3 files changed, 108 insertions(+)
--




   

Re: [VOTE] Release Compress Antlib 1.5 based on RC2

[Maarten Coene]

+1
Maarten


  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: dinsdag 6 juni 6:26 2017
 Onderwerp: Re: [VOTE] Release Compress Antlib 1.5 based on RC2
   
On 2017-06-01, Stefan Bodewig wrote:

> I've created a new release candidate for Compress Antlib 1.5, this time
> with working Ivy coordinates and a release date three days into the
> future.

> git tag: 1_5_RC2
>          on commit: f20847d
> tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/compress/
>          revision: 19857
> Maven artifacts:
>          
>https://repository.apache.org/content/repositories/orgapacheant-1018/org/apache/ant/ant-compress/1.5/

> This Vote will be open at least for 72 hours and close no earlier than
> 2017-06-04 17:00UTC.

Making my own vote explicit

+1

Actually, time seems to be up. Any other votes?

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [antlibs] Break Backwards Compatibility of Ivy Coordinates?

[Maarten Coene]

I don't see how Ivy could resolve the old ant-compress ivy.xml files without 
using very special artifact patterns.So my guess is that Ivy users of 
ant-compress just use the pom.xml file.

So I'd say we should fix the ivy.xml.
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: woensdag 31 mei 17:34 2017
 Onderwerp: [antlibs] Break Backwards Compatibility of Ivy Coordinates?
   
Hi all

this is an excerpt from the cancelled vote thread for the compress
antlib.

2017-05-31 16:40 GMT+02:00 Stefan Bodewig :

> I've just realized that the ivy.xml file I've published to Nexus has
> completely different coordinates from the one used in earlier
> releases. It used to be
>
>              module="ant" ...>
>        
> for 1.5 RC1 it is
>
>              module="ant-compress" ...>
>        
> and the current master branch would create
>
>              module="ant-compress"
>          

Re: [VOTE] Release Compress Antlib 1.5 based on RC1

[Maarten Coene]

No Stefan, I was just wondering if it was normal that this file didn't contain 
the release date.If the current situation is fine for you, I'll give my vote.
Maarten

  Van: Stefan Bodewig <bode...@apache.org>
 Aan: dev@ant.apache.org 
 Verzonden: woensdag 31 mei 14:39 2017
 Onderwerp: Re: [VOTE] Release Compress Antlib 1.5 based on RC1
   
Maarten, Jan

right now this only has my implicit vote. Would you be more inclined to
vote if the date was included inside the changelog? If so, I'll re-roll
the release.

Stefan

On 2017-05-31, Maarten Coene wrote:

> Why not simply  ?That is the date 
> the vote started and the binaries were built?Or perhaps you could add a few 
> days to it and make sure the vote ends at that date?

> It's just strange when reading the documentation of a released version to see 
> that it's 'unreleased' or 'during-release'...

> Maarten


>      Van: "Matèrne, Jan (RZF, Ref 410)" <jan.mate...@fv.nrw.de>
>  Aan: Ant Developers List <dev@ant.apache.org>
>  Verzonden: woensdag 31 mei 10:25 2017
>  Onderwerp: AW: [VOTE] Release Compress Antlib 1.5 based on RC1

> Maybe
> ?

> Jan

> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Mittwoch, 31. Mai 2017 09:46
> An: dev@ant.apache.org
> Betreff: Re: [VOTE] Release Compress Antlib 1.5 based on RC1

> On 2017-05-31, Maarten Coene wrote:

>> The changes.xml still contains the following line:> date="unreleased">
>> I'm not sure this should block the release, but I think it would be better 
>> to fill in the correct date.

> This is a chicken and egg problem. As long as the vote hasn't passed, I
> don't know the release date :-)

> Stefan

> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org


> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


   

Re: AW: [VOTE] Release Compress Antlib 1.5 based on RC1

[Maarten Coene]

Why not simply  ?That is the date the 
vote started and the binaries were built?Or perhaps you could add a few days to 
it and make sure the vote ends at that date?

It's just strange when reading the documentation of a released version to see 
that it's 'unreleased' or 'during-release'...

Maarten


  Van: "Matèrne, Jan (RZF, Ref 410)" <jan.mate...@fv.nrw.de>
 Aan: Ant Developers List <dev@ant.apache.org> 
 Verzonden: woensdag 31 mei 10:25 2017
 Onderwerp: AW: [VOTE] Release Compress Antlib 1.5 based on RC1
   
Maybe 
?

Jan

-Ursprüngliche Nachricht-
Von: Stefan Bodewig [mailto:bode...@apache.org] 
Gesendet: Mittwoch, 31. Mai 2017 09:46
An: dev@ant.apache.org
Betreff: Re: [VOTE] Release Compress Antlib 1.5 based on RC1

On 2017-05-31, Maarten Coene wrote:

> The changes.xml still contains the following line: date="unreleased">
> I'm not sure this should block the release, but I think it would be better to 
> fill in the correct date.

This is a chicken and egg problem. As long as the vote hasn't passed, I
don't know the release date :-)

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


   

Re: [VOTE] Increase minimum Java version for Ivy to Java7

[Maarten Coene]

Yes, but it's not because Ivy is compiled with Java 5 that you cannot run it 
with Java 7 to have TLS1.2 support.
Maarten

  Van: Gintautas Grigelionis <g.grigelio...@gmail.com>
 Aan: Ant Developers List <dev@ant.apache.org>; Maarten Coene 
<maarten_co...@yahoo.com> 
 Verzonden: vrijdag 19 mei 9:20 2017
 Onderwerp: Re: [VOTE] Increase minimum Java version for Ivy to Java7
   
Java 7 implements TLS 1.2; Ivy depends a lot more on network communications
than Ant does.
+1, but please extend the vote to the baseline of IvyDE as well.

2017-05-19 9:03 GMT+02:00 Maarten Coene <maarten_co...@yahoo.com.invalid>:

> I think we should stick to Java5 as long as Ant 1.9.x is actively
> maintained.This keeps Ivy usable for both Ant 1.9.x and Ant 1.10.x
> Or are there good reasons to increase the minimum Java version, like
> features that cannot be implemented with Java 5?
> But since I don't have the time at the moment to be more active for the
> community, I will not block any decission made.
> So my vote is -0.
> Maarten
>
>
>      Van: Jan Matèrne <j...@materne.de>
>  Aan: 'Ant Developers List' <dev@ant.apache.org>
>  Verzonden: vrijdag 19 mei 7:25 2017
>  Onderwerp: [VOTE] Increase minimum Java version for Ivy to Java7
>
> As discussed on this mailing list [1] we should increase the minimum Java
> version [2] from current (Ivy-2.4.0) Java5 to Java 7 (Ivy-2.5.0).
> Decisions whether to increase to Java8 after that release should be make
> after that release.
> According to the bylaws [3] this vote is open for one week (until
> 26.05.2017).
>
> Here is my +1
> Jan
>
> [1]
> http://mail-archives.apache.org/mod_mbox/ant-dev/201705.
> mbox/ajax/%3C87415C1
> F-5EFF-4C81-8078-0276CC21A8ED%40gmail.com%3E
> [2] http://ant.apache.org/ivy/history/latest-milestone/compatibility.html
> [3] http://ant.apache.org/bylaws.html
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>
>
>
>

   

Re: [VOTE] Increase minimum Java version for Ivy to Java7

[Maarten Coene]

I think we should stick to Java5 as long as Ant 1.9.x is actively 
maintained.This keeps Ivy usable for both Ant 1.9.x and Ant 1.10.x
Or are there good reasons to increase the minimum Java version, like features 
that cannot be implemented with Java 5?
But since I don't have the time at the moment to be more active for the 
community, I will not block any decission made.
So my vote is -0.
Maarten


  Van: Jan Matèrne 
 Aan: 'Ant Developers List'  
 Verzonden: vrijdag 19 mei 7:25 2017
 Onderwerp: [VOTE] Increase minimum Java version for Ivy to Java7
   
As discussed on this mailing list [1] we should increase the minimum Java
version [2] from current (Ivy-2.4.0) Java5 to Java 7 (Ivy-2.5.0).
Decisions whether to increase to Java8 after that release should be make
after that release.
According to the bylaws [3] this vote is open for one week (until
26.05.2017).

Here is my +1
Jan

[1]
http://mail-archives.apache.org/mod_mbox/ant-dev/201705.mbox/ajax/%3C87415C1
F-5EFF-4C81-8078-0276CC21A8ED%40gmail.com%3E
[2] http://ant.apache.org/ivy/history/latest-milestone/compatibility.html
[3] http://ant.apache.org/bylaws.html


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.10.1 based on RC1

[Maarten Coene]

I couldn't test it, but based on the content it looks ok to me
+1
Maarten

  Van: Antoine Levy Lambert 
 Aan: Ant Developers List  
 Verzonden: maandag 6 februari 1:10 2017
 Onderwerp: Re: [VOTE] Release Ant 1.10.1 based on RC1
   
+1 Antoine
> On Feb 2, 2017, at 2:33 PM, Stefan Bodewig  wrote:
> 
> Hi all
> 
> I've created a release candidate for 1.10.1:
> 
> git tag: ANT_1.10.1_RC1
>      on commit: 530e59d
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>        revision: 18086
> Maven artifacts:
>        
>https://repository.apache.org/content/repositories/orgapacheant-1013/org/apache/ant/
> 
> This Vote will be open at least for 72 hours and close no earlier than
> 2017-02-05 19:30UTC.
> 
> Cheers
> 
>      Stefan
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
> 


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


   

Re: [VOTE] Release Ant 1.9.9 based on RC1

[Maarten Coene]

We didn't find any issues while testing this RC.

+1
Maarten


  Van: Antoine Levy Lambert 
 Aan: Ant Developers List  
 Verzonden: maandag 6 februari 1:34 2017
 Onderwerp: Re: [VOTE] Release Ant 1.9.9 based on RC1
   
+ 1 
Antoine
> On Feb 2, 2017, at 2:30 PM, Stefan Bodewig  wrote:
> 
> Hi all
> 
> I've created a release candidate for 1.9.9:
> 
> git tag: ANT_199_RC1
>        on commit: d5bd3b4
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>          revision: 18085
> Maven artifacts:
>        
>https://repository.apache.org/content/repositories/orgapacheant-1012/org/apache/ant/
> 
> This Vote will be open at least for 72 hours and close no earlier than
> 2017-02-05 19:30UTC.
> 
> Cheers
> 
>        Stefan
> 
> 


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


   

Re: Thoughts on Next Release

[Maarten Coene]

Agreed.
Maarten


  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: vrijdag 13 januari 13:19 2017
 Onderwerp: Thoughts on Next Release
   
Hi all,

it looks as if the wrapper script still didn't work on Solaris 10 and
also I seem to have broken Eclipse integration. The later has already
been fixed in git, and we seem to be getting closer to fixing the
former.

IMHO we should cut new releases once both have been fixed.

Thoughts?

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.10.0 based on RC1

[Maarten Coene]

Stefan,
I couldn't test this 1.10.0 release since our buildscripts are not compatible 
with Java 8.(we have some javascript that are not compatible with the new java 
8 javascript engine)

I could only check the git tag and the binaries and they looks ok to me.So here 
is my +1 vote.
kind regards,
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: donderdag 29 december 19:56 2016
 Onderwerp: Re: [VOTE] Release Ant 1.10.0 based on RC1
   
On 2016-12-27, Stefan Bodewig wrote:

> I've created a release candidate for 1.10.0:

> git tag: ANT_1.10.0_RC1
>          on commit: ffcbcd7
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>          revision: 17588
> Maven artifacts:
>    
>https://repository.apache.org/content/repositories/orgapacheant-1011/org/apache/ant/

> This Vote will be open at least for 72 hours and close no earlier than
> 2016-12-30 7:00UTC.

Making my own vote explicit: +1

It seems christmas is a bad time for votes, I'll simply leave this (as
well the 1.9.8 vote) open for a bit longer.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.8 based on RC1

[Maarten Coene]

Sorry Stefan for the late response,

We already did some testing with the 1.9.8 and we didn't encounter any 
problems.So here is my +1.
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: donderdag 29 december 19:56 2016
 Onderwerp: Re: [VOTE] Release Ant 1.9.8 based on RC1
   
On 2016-12-25, Stefan Bodewig wrote:

> I've created a release candidate for 1.9.8:

> git tag: ANT_198_RC1
>          on commit: 0e20ef3
> tarballs: https://dist.apache.org/repos/dist/dev/ant/
>          revision: 17572
> Maven artifacts:
>      
>https://repository.apache.org/content/repositories/orgapacheant-1010/org/apache/ant/

> Given the time of the year this Vote will be open at least for 96 hours
> and close no earlier than 2016-12-29 21:00UTC.

Making my own vote explicit: +1

It seems christmas is a bad time for votes, I'll simply leave this (as
well the 1.10.0 vote) open for a bit longer.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: AW: Releasing Ant 1.9.8 (and maybe 1.10.0)?

[Maarten Coene]

Thanks Stefan,
I prefer a 1.9.8 release since we are still using Java 6 and we are suffering 
from the wrapper script issues.Personally I think the 'new feature'-set is a 
bit too small to have a 1.10.0 release, but I can follow Jan to create it 
nontheless as a signal.

Maarten


  Van: Jan Matèrne (jhm) 
 Aan: 'Ant Developers List'  
 Verzonden: dinsdag 20 december 21:17 2016
 Onderwerp: AW: Releasing Ant 1.9.8 (and maybe 1.10.0)?
   
Thanks for volunteering.
I prefer having a 1.10.0 as a signal "we have a Java8-version".

Jan

> -Ursprüngliche Nachricht-
> Von: Stefan Bodewig [mailto:bode...@apache.org]
> Gesendet: Montag, 19. Dezember 2016 15:11
> An: dev@ant.apache.org
> Betreff: Releasing Ant 1.9.8 (and maybe 1.10.0)?
> 
> Hi all
> 
> it's been eight months since the last release and we currently have
> accumulated some important improvements for Java9 and seem to have
> fixed a serious wrapper script issue for "more traditional" Unixes.
> 
> See https://github.com/apache/ant/blob/1.9.x/WHATSNEW for 1.9.8
> 
> I think that's enough to warrant a release and would volunteer to be
> the RM.
> 
> For 1.10.0 things are less clear to me. It contains all the fixes of
> 1.9.8 and apart from that I only see
> 
>  * New file selectors ,  and .
> 
>  * New task  that provides the ability to set POSIX
>    compatible permssions via NIO's PosixFilePermission
> 
>  * AntClassLoader and its subclasses register themselves as parallel
>    capable.
> 
> where  really only works on POSIXy file systems because
> that's how NIO works.
> 
> Not sure whether we want to cut the release nevertheless, if so I'd be
> willing to manage that release as well.
> 
> So what do you think?
> 
> Stefan
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional
> commands, e-mail: dev-h...@ant.apache.org



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org


   

Re: Ivy - Proposal for reviving the project and moving towards a release

[Maarten Coene]

Thanks Jaikran,
I will look at your patches, I'll try to do it this week.If possible, please 
attach a junit test as well to reproduce the problem.

About the release, the master branch already contains some fixes since the 
2.4.0 release. They are listed in the release-notes.html in the 'doc' 
directory. If we want to create a 2.4.1 release, we should merge all these 
changes (and all upcomming patches) into the 2.4.x branch as well. If we decide 
to create a 2.5.0 release, this merging isn't necessary. I wouldn't pin on an 
exact timing, we can create a release any time when we think the codebase is 
ready for it.

We also have to find a release manager. I did it in the past when we were on 
SVN, but I don't have enough GIT knowledge (and I don't have the time to look 
into it) to do a new release. 

Maarten

  Van: Jaikiran Pai 
 Aan: dev@ant.apache.org 
 Verzonden: zondag 11 december 15:22 2016
 Onderwerp: Ivy - Proposal for reviving the project and moving towards a release
   
First off, I'm not an Ivy or Ant committer. The proposal that I make 
below for an Ivy release is based on what was discussed in a recent mail 
thread about the future of Ivy 
https://www.mail-archive.com/dev@ant.apache.org/msg45078.html. There was 
a suggestion that someone from community volunteer to try and bring in 
some activity into the project and see if we can create a release after 
triaging the JIRA issues.


I have had a look at the open issues in JIRA today and decided to filter 
out issues that are open, updated since Jan 2014 and affects versions 
2.1, 2.2, 2.3 and 2.4. I decided to use this as a filter criteria to 
just select a few that I thought can be considered "active". This [1] 
returns 57 issues. I went ahead and looked at those issues today and 
have asked for more information in the JIRAs wherever relevant and have 
sent a couple of pull requests [2] [3] to fix some straightforward ones. 
I also have another PR that I opened this week to fix one other issue. 
Out of those 57 issues, many are no longer relevant or don't have enough 
details. I don't have JIRA privileges to label them, share filters or 
even assign some to myself to track them better. So I think for now, we 
can rely on that JIRA search query [1].

At this point, I think, if we can target March 2017 for releasing a 
2.4.1-Beta-1 with fixes from the list of JIRAs I think that would be a 
good start. Some of the issues noted in that JIRA are indeed important 
ones and would need some review/help in fixing them correctly, which 
essentially means, we need at least one person who has had experience 
with the Ivy code and its design details and also has the committer rights.


Does any of this look feasible? Let me know if this isn't enough to move 
things forward - I don't want to end up sending PRs and spending time on 
this if there's no way we can get to a proper release in the next few 
months.


[1] 
https://issues.apache.org/jira/browse/IVY-1553?jql=project%20%3D%20IVY%20AND%20status%20in%20(Open%2C%20%22In%20Progress%22%2C%20Reopened)%20AND%20affectedVersion%20in%20(2.1.0%2C%202.2.0%2C%202.3.0%2C%202.4.0%2C%202.4.0-RC1)%20AND%20updated%20%3E%3D%202014-01-01%20ORDER%20BY%20updated%20DESC

[2] https://github.com/apache/ant-ivy/pull/11

[3] https://github.com/apache/ant-ivy/pull/12

-Jaikiran

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: AW: Ivy - any future or is it also going to be retired?

[Maarten Coene]

Thanks Jaikiran! :-)
I'll try to review it ...
kind regards,Maarten

  Van: Jaikiran Pai 
 Aan: dev@ant.apache.org 
 Verzonden: woensdag 7 december 18:17 2016
 Onderwerp: Re: AW: Ivy - any future or is it also going to be retired?
   
Thank you. Given that there does seem to be willingness to do something 
to move things forward with the project, I have now submitted a PR for 
one of the open JIRAs https://github.com/apache/ant-ivy/pull/10 in an 
attempt to fix it.

Over the weekend, I'll see if I can come up with a list of JIRAs which 
might be worth to be included in the proposed release (whenever next it 
happens). Of course, someone who has more knowledge about the project 
can do this and I'll happily step aside from that task.

-Jaikiran

On Wednesday 07 December 2016 08:41 PM, Jan Matèrne (jhm) wrote:
>> One thing that I think is probably is a priority (based on what I have
>> been trying to attempt while helping out with Ivy patches) is that we
>> have a central system which builds this project and runs the testsuite
>> regularly against a *nix and Windows system. Is this already available
>> in the project/Ant ecosystem somewhere? Something like a Jenkins? If
>> not, is there any other option we have to make sure we really release
>> something that is reproducible?
> Apache hosts a Jenkins instance with several slaves we could use.
> We already have some Ivy jobs:
>
> https://builds.apache.org/view/All/job/Ivy/
> Build Ivy on Ubuntu
> JDK 1.6, Ubuntu
> git: Recursively update submodules
> runs: @hourly
> run: Ant (latest)
> Target: clean jar sources
> archive: build/artifact/**
>
>
> https://builds.apache.org/view/All/job/Ivy-check/
> Checks of the Ivy codebase: Findbugs, RAT - Release Auditing Tool, Checkstyle
> JDK 1.6, Ubuntu
> git: clean before checkout
> run: seems to be just run manually
> run-1: Ant (latest): findbugs checkstyle-internal
> run-2: Ant (latest): rat
> check for TODOs
>
> https://builds.apache.org/view/All/job/Ivy-tests/
> seems to be a "test-job" of mine ...
> git: clean before checkout, Recursively update submodules
> matrix: (atm only JDK1.5)
>
> https://builds.apache.org/view/All/job/Ivy-tests-matrix/
> run tests
> triggerd by stable "Ivy" job
> git: clean before checkout, Recursively update submodulesrun: Ant(latest): 
> clean test-report
>
>
>
> Jan
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Fw: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Windows #157

[Maarten Coene]

Anyone an idea why this is failing and can someone fix it?I would try to do 
this myself, but I don't have the necessary permissions on Jenkins.
regards,Maarten


 
- Doorgestuurd bericht -
 Van: Apache Jenkins Server 
 Aan: notificati...@ant.apache.org 
 Verzonden: woensdag 9 november 2:11 2016
 Onderwerp: Build failed in Jenkins: Ivy-tests » JDK 1.5 (latest),Windows #157
   
See 


Changes:

[maartenc] Fix NullPointerException in dependencytree with no dependencies

--
Started by upstream project "Ivy-tests" build number 157
originally caused by:
 Started by upstream project "Ivy" build number 527
 originally caused by:
  Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on windows-2012-2 (Windows) in workspace 

 > git rev-parse --is-inside-work-tree # timeout=10
Fetching changes from the remote Git repository
 > git config remote.origin.url 
 > https://git-wip-us.apache.org/repos/asf/ant-ivy.git # timeout=10
Cleaning workspace
 > git rev-parse --verify HEAD # timeout=10
Resetting working tree
 > git reset --hard # timeout=10
 > git clean -fdx # timeout=10
 > git submodule foreach --recursive git reset --hard # timeout=10
 > git submodule foreach --recursive git clean -fdx # timeout=10
Fetching upstream changes from 
https://git-wip-us.apache.org/repos/asf/ant-ivy.git
 > git --version # timeout=10
 > git -c core.askpass=true fetch --tags --progress 
 > https://git-wip-us.apache.org/repos/asf/ant-ivy.git 
 > +refs/heads/*:refs/remotes/origin/*
Checking out Revision 7217b9d270e31fe1e68803c8e25b0a03869f1556 
(refs/remotes/origin/master)
 > git config core.sparsecheckout # timeout=10
 > git checkout -f 7217b9d270e31fe1e68803c8e25b0a03869f1556
 > git rev-list f463013f34a5c5c61b7dba22c9ed4096fbd3b218 # timeout=10
 > git remote # timeout=10
 > git submodule init # timeout=10
 > git submodule sync # timeout=10
 > git config --get remote.origin.url # timeout=10
 > git submodule update --init --recursive
ERROR: Cannot find executable from the chosen Ant installation "Ant (latest)"
Recording test results
ERROR: Step ‘Publish JUnit test result report’ failed: No test report files 
were found. Configuration error?


   

Re: Any Solaris / HP-UX Users out here?

[Maarten Coene]

Stefan,I can help testing these changes on Solaris.

regards,Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org; u...@ant.apache.org 
 Verzonden: maandag 10 oktober 18:07 2016
 Onderwerp: Any Solaris / HP-UX Users out here?
   
Hi all

we've received several reports about the ant wrapper script of Ant 1.9.7
not working on the said systems. Most likely because some changes made
to it use sed and the printf built-in in non-portable ways.

Jeff Adamson is currently evaluating options inside of
https://github.com/apache/ant/pull/24 but we all lack access to the OSes
where problems have been reported, so what ever we do is mere guess
work. It would be good if anybody could help us with testing changes
until we've found something that works on all OSes.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.7 based on RC1

[Maarten Coene]

+1
Maarten

  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: zaterdag 9 april 12:03 2016
 Onderwerp: [VOTE] Release Ant 1.9.7 based on RC1
   
Hi all

I've created a release candidate for 1.9.7:

git tag: ANT_197_RC1
        on commit: cecbf5c
tarballs: https://dist.apache.org/repos/dist/dev/ant/
          revision: 13103
Maven artifacts:
      
https://repository.apache.org/content/repositories/orgapacheant-1009/org/apache/ant/

Vote will be open at least for 72 hours and close no earlier than 2016-04-12
10:00UTC.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



  

Re: [VOTE] Adopt Java8 as Baseline for 1.10 on master Branch

[Maarten Coene]

I'd prefer moving to Java6, since there are still companies using Java6 or 
Java7.Is Java8 really required to implement some of the new features?The more 
JDK's we support, the more people can make use of Ant!

However, since I'm not that active in the Ant development, I won't block the 
vote for this:-0
Maarten


  Van: Stefan Bodewig 
 Aan: dev@ant.apache.org 
 Verzonden: dinsdag 22 maart 13:11 2016
 Onderwerp: [VOTE] Adopt Java8 as Baseline for 1.10 on master Branch
   
Hi all

after the recent discussion, I'd like to propose the following:

* create a branch 1.9.x that we use for Java5 compatible maintenance
  releases - with Jenkins Matrix Builds, of course.

* change the version number of the master branch to 1.10.0alpha
  (-SNAPSHOT, whatever) and make Java8 the new baseline for that - with
  Gump and Jenkins Matrix Builds for Java8 (and 9 once it becomes
  available).

Please cast your votes, will be open for about three days.

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



  

Re: [VOTE] Stephen Haberman as a committer

[Maarten Coene]

+1
Maarten

  Van: Conor MacNeill 
 Aan: Ant Developers List  
 Verzonden: maandag 5 oktober 11:06 2015
 Onderwerp: [VOTE] Stephen Haberman as a committer
   
I would like to nominate Stephen Haberman as a committer. Stephen has
submitted a number of well tested patches to the Ivy codebase. I
believe adding Stephen would strengthen the committer-base,
particularly for the Ivy Sub-project.

Please vote

[ ] +1 Add Stephen as a committer
[ ] -1 Disagree
[ ] +0 - Don't care.

I will start proceedings with my +1

Thanks
Conor

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org



   

Re: [VOTE] Release Ant 1.9.5 based on RC1

[Maarten Coene]

+1
I've tested this release against several builds without any problems :)

Maarten




- Oorspronkelijk bericht -
Van: Stefan Bodewig bode...@apache.org
Aan: dev@ant.apache.org
Cc: 
Verzonden: zondag 31 mei 16:46 2015
Onderwerp: [VOTE] Release Ant 1.9.5 based on RC1

Hi all

I've created a release candidate for 1.9.5:

git tag: ANT_195_RC1
 hash: 54ac2fedd
 on commit: ea7bf28
tarballs: https://dist.apache.org/repos/dist/dev/ant/
  revision: 9181
Maven artifacts:
  
https://repository.apache.org/content/repositories/orgapacheant-1007/org/apache/ant/

Vote will be open at least for 72 hours and close no earlier than Wed
3rd June 2015.

Cheers

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [jira] (IVY-1197) OutOfMemoryError during ivy:publish

[Maarten Coene]

I'm not a fan of this proposal, I like it that Ivy doesn't has any dependencies 
when using standard resolvers.
Perhaps it could be added to the documentation that if you use the URLresolver 
for large uploads you'll have to add httpclient to the classpath?


Maarten




- Oorspronkelijk bericht -
Van: Antoine Levy Lambert anto...@gmx.de
Aan: Ant Developers List dev@ant.apache.org
Cc: 
Verzonden: donderdag 9 april 3:50 2015
Onderwerp: Re: [jira] (IVY-1197) OutOfMemoryError during ivy:publish

Also, I wonder whether we should not make the use of httpclient with ivy 
compulsory, since Loren says that the HttpUrlConnection of the JDK is always 
copying the full file into a ByteArray when authentication is performed.

That would make the code more simple.

Regards,

Antoine

On Apr 7, 2015, at 9:22 PM, Antoine Levy Lambert anto...@gmx.de wrote:

 Hi,
 
 I wonder whether we should not upgrade ivy to use the latest http client 
 library too ?
 
 Regards,
 
 Antoine
 
 On Apr 7, 2015, at 12:46 PM, Loren Kratzke (JIRA) j...@apache.org wrote:
 
 
   [ 
 https://issues.apache.org/jira/browse/IVY-1197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14483468#comment-14483468
  ] 
 
 Loren Kratzke edited comment on IVY-1197 at 4/7/15 4:45 PM:
 
 
 I would be happy to provide you with a project that will reproduce the 
 issue. I can and will do that. 
 
 Generally speaking from a high level, the utility classes are calling 
 convenience methods and writing to streams that ultimately buffer the data 
 being written. There is buffering, then more buffering, and even more 
 buffering until you have multiple copies of the entire content of the stream 
 stored in over sized buffers (because they double in size when they fill 
 up). Oddly, the twist is that the JVM hits a limit no matter how much RAM 
 you allocate. Once the buffers total more than about ~1GB (which is what 
 happens with a 100-200MB upload) the JVM refuses to allocate more buffer 
 space (even if you jack up the RAM to 20GB, no cigar). Honestly, there is no 
 benefit in buffering any of this data to begin with, it is just a side 
 effect of using high level copy methods. There is no memory ballooning at 
 all when the content is written directly to the network.
 
 I will provide a test project and note the break points where you can debug 
 and watch the process walk all the way down the isle to an OOME. I will have 
 this for you asap.
 
 
 was (Author: qphase):
 I would be happy to provide you with a project that will reproduce the 
 issue. I can and will do that. 
 
 Generally speaking from a high level, the utility classes are calling 
 convenience methods and writing to streams that ultimately buffer the data 
 being written. There is buffering, then more buffering, and even more 
 buffering until you have multiple copies of the entire content of the stream 
 stored in over sized buffers (because they double in size when they fill 
 up). Oddly, the twist is that the JVM hits a limit no matter how much RAM 
 you allocate. Once the buffers total more than about ~1GB (which is what 
 happens with a 100-200MB upload) the JVM refuses to allocate more buffer 
 space (even is you jack up the RAM to 20GB, no cigar). Honestly, there is no 
 benefit in buffering any of this data to begin with, it is just a side 
 effect of using high level copy methods. There is no memory ballooning at 
 all when the content is written directly to the network.
 
 I will provide a test project and note the break points where you can debug 
 and watch the process walk all the way down the isle to an OOME. I will have 
 this for you asap.
 
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
 For additional commands, e-mail: dev-h...@ant.apache.org

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Ivy 2.4.0 Release - take 2

[Maarten Coene]

+1

Maarten



Van: Nicolas Lalevée nicolas.lale...@hibnet.org
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: zaterdag 13 december 17:45 2014
Onderwerp: [VOTE] Ivy 2.4.0 Release - take 2


I have built a second release candidate for Ivy 2.4.0

The svn tag of this release is: 
https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=0b9db35ee7a94a719e538b04122b86cb997f3a17

The artifacts has been published to: 
https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7405

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Ivy 2.4.0

[Maarten Coene]

The style folder was included using svn:externals and is part of the ivy site:
https://svn.apache.org/repos/asf/ant/site/ivy/sources/style/

We should rebuild the release with this folder included imho.

Maarten




 Van: Jean-Louis Boudart jeanlouis.boud...@gmail.com
Aan: Ant Developers List dev@ant.apache.org; Maarten Coene 
maarten_co...@yahoo.com 
Verzonden: woensdag 12 november 10:05 2014
Onderwerp: Re: [VOTE] Release Ivy 2.4.0
 

+1 for expect the style folder

Where does this style folder is  ? Is it somewhere in SVN / GIT ?


2014-11-10 0:24 GMT+01:00 Maarten Coene maarten_co...@yahoo.com.invalid:

 Thank you for creating the release Nicolas :-)

 I've noticed that the style directory is missing in the documentation in
 apache-ivy-2.4.0-bin.zip (and probably the others too).
 This makes the documentation inside these binaries look a bit 'basic'.

 Maarten



 
  Van: Nicolas Lalevée nicolas.lale...@hibnet.org
 Aan: Ant Developers List dev@ant.apache.org
 Verzonden: zondag 9 november 17:56 2014
 Onderwerp: [VOTE] Release Ivy 2.4.0


 I have built a release candidate for Ivy 2.4.0

 The git tag of this release is:
 https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2

 The artifacts has been published to:
 https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093

 Do you vote for the release of these binaries?

 [ ] Yes
 [ ] No

 Regards,
 Nicolas


 -
 To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
 For additional commands, e-mail: dev-h...@ant.apache.org




-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/

Re: [VOTE] Release Ivy 2.4.0

[Maarten Coene]

Thank you for creating the release Nicolas :-)

I've noticed that the style directory is missing in the documentation in 
apache-ivy-2.4.0-bin.zip (and probably the others too).
This makes the documentation inside these binaries look a bit 'basic'.

Maarten




 Van: Nicolas Lalevée nicolas.lale...@hibnet.org
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: zondag 9 november 17:56 2014
Onderwerp: [VOTE] Release Ivy 2.4.0
 

I have built a release candidate for Ivy 2.4.0

The git tag of this release is: 
https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=commit;h=b7f132a46601cdecfc631052818cab7f498078d2

The artifacts has been published to: 
https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0@7093

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Regards,
Nicolas


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Release of Ivy 2.4.0

[Maarten Coene]

If I remember correctly, the 2.4.0-RC1 also introduced some other very annoying 
bugs, these fixes should be included in the 2.4.0 release as well imho.

I whish I could help you with it Nicolas, but I also have too little time which 
will be needed for the first release on git.
(In fact, my very very low activity is also caused by the fact that we are on 
git now in combination with the lack of time to learn how to use it properly)


Maarten




 Van: Nicolas Lalevée nicolas.lale...@hibnet.org
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: woensdag 15 oktober 18:31 2014
Onderwerp: Release of Ivy 2.4.0
 

The last release of Eclipse has introduced a nasty bug [2], IvyDE is impacted, 
and the fix/work-around is in Ivy [2]. I think we should get a fix out very 
soon.

And Ivy has been in RC for quite some time, I suggest we release it with also 
that fix, as the 2.4.0.

This would be the first release done from git, my free time is quite limited, 
so don’t freak if I take some time to get out a release to be voted upon.

Nicolas

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=445122
[2] https://issues.apache.org/jira/browse/IVY-1487


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: migration to git : next steps

[Maarten Coene]

I did some commit tests on Ivy and it seems ok.

Could someone also change the configuration on Jenkins?

Maarten





 Van: Stefan Bodewig bode...@apache.org
Aan: dev@ant.apache.org 
Verzonden: zondag 25 mei 20:55 2014
Onderwerp: Re: migration to git : next steps
 

On 2014-05-23, anto...@gmx.de wrote:

 Jake Farrell has finished the migration, we are asked to verify. Right
 now I am at work so cannot verify but will look during the weekend.

I had a quick look at Ant core, seems to work reasonably.

One thing though, the github mirror is now trying to track the no longer
existing tunk branch rather than the new master branch.

Stefan




-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Ant 1.9.4 (second attempt)

[Maarten Coene]

+1

Tested with a more or less complex Ant/Ivy build.

Maarten




 Van: Antoine Levy Lambert anto...@gmx.de
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: woensdag 30 april 5:46 2014
Onderwerp: [VOTE] Release Ant 1.9.4 (second attempt)
 

Hi all,

restarting the vote thread after having fixed the pom of ant-testutil and 
rebuilt

a release with many bug fixes and improvements, including the initial support 
for Java 1.9,
the possibility to run JUnit tests in multiple threads (when they are forked)
and the refactoring of Ant's own test suite which is now based on JUnit 4.

I propose to adopt the following as Ant 1.9.4

SVN tag: http://svn.apache.org/repos/asf/ant/core/tags/ANT_194/
  revision 1591180
Tarballs: https://dist.apache.org/repos/dist/dev/ant/
  revision 5204
Maven Artifacts:
  
https://repository.apache.org/content/repositories/orgapacheant-1004/org/apache/ant/

Vote will be open until Monday, May 5 due to upcoming May 1st holiday

Cheers

Antoine 

Re: AW: [VOTE] Release Ant 1.9.4 (second attempt)

[Maarten Coene]

We'll give this new version a try on our more or less complex Ant/Ivy build

Maarten





 Van: Jan Matèrne (jhm) apa...@materne.de
Aan: 'Ant Developers List' dev@ant.apache.org 
Verzonden: woensdag 30 april 9:20 2014
Onderwerp: AW: [VOTE] Release Ant 1.9.4 (second attempt)
 


So a +1 from me.

But running that version on a more complex build would be helpful (EasyAnt,
Ivy?)    


Jan

Re: [VOTE] migration to git

[Maarten Coene]

Probably because I don't know much about git, but I don't see the real 
advantage of the switch from SVN to git.
In addition, I don't have the time to help adapting the Ivy release 
process/scripts.
But I don't want to stand in the way if everyone thinks this should be done.


So, my vote is:
for Ivy: -0
for the rest: +0

Maarten




 Van: Antoine Levy Lambert anto...@gmx.de
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: maandag 28 april 5:02 2014
Onderwerp: [VOTE] migration to git
 

Hi,

Let's vote about migrating to git :

-  Ant

- Ivy 

- easyant

- Ivyde

- the antlibs

I am not including the sandbox in the thread intentionally.

The web sites will remain in svn in any event because svnpubsub is the only 
supported mechanism to maintain web sites AFAIK.

[] Yes
[] No


Let me start with my +1

Antoine



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Migrating to Git

[Maarten Coene]

I'm happy with Subversion, so for me there is no need to switch to git.

Maarten




 Van: Jean-Louis Boudart jeanlouis.boud...@gmail.com
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: maandag 14 april 8:24 2014
Onderwerp: Migrating to Git
 

HI there,

Since write git repository are accessible for a while, i suggest (as many
of you) to switch projects to git.
I know this has been discussed many times [1] but never in a dedicated
thread.

So what do you think about this ?

Are you ok to migrate :
* ant
* ivy / ivyde
* easyant
* rest of stuff (antlibs, stuff from sandbox?)


[1] http://markmail.org/message/6ik4nyueayz2fpnx
-- 
Jean Louis Boudart
Independent consultant
Apache EasyAnt commiter http://ant.apache.org/easyant/

Re: Ivy performance fix

[Maarten Coene]

Hi Josh,

yes I think we can merge this in the 2.4.0 final release, but we'll have to 
review a bit in more detail first.
However, could you create a JIRA issue containing a link to the patch?

thanks!
Maarten




 Van: Antoine Levy Lambert anto...@gmx.de
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: dinsdag 1 april 3:58 2014
Onderwerp: Re: Ivy performance fix
 

Hello Josh,

thanks for contacting the Ant/Ivy community.

I think we can work with pull requests on github, as long as we see clearly the 
diffs with the code in the svn repository we should be fine.

@Maarten, Nicolas, and others in the Ivy community, do you think we can merge 
this before building the ivy 2.4.0 final ?

Regards,

Antoine

On Mar 31, 2014, at 4:15 PM, Josh Suereth joshua.suer...@gmail.com wrote:

 So, for the sbt project we noticed significant resolution time improvements
 with the following patch:
 
 https://github.com/sbt/ivy/pull/1
 
 The reasoning:
 
 
   - A lot of artifacts being resolved use Maven's dependencyManagement
   conventions
   - Ivy appears to turn these into exact matcher rules
   - A ton of resolution time is spent filtering through these rules
   - The existing solution is O(n) for all overrides
 
 
 What the patch does:
 
 
   - Creates a key'd store for all exact matcher rules
   - When executing rules, ensure that we only traverse what we have to
   (non-exact, exact specific to our key and default).
 
 
 As I said, this represents a significant speed bump for sbt builds using
 Ivy.  All existing tests pass, and I think they cover this aspect of ivy
 pretty well, from what I could see.
 
 What's the best mechanism to submit this back?  Do you accept pull requests
 on github?
 
 Thanks!
 - Josh Suereth
  Tools Lead
   Typesafe, Inc.


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[ANNOUNCE] Apache Ivy 2.4.0-RC1 released

[Maarten Coene]

The Apache Ivy project is pleased to announce its 2.4.0-RC1 release.

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

Key features of this 2.4.0-RC1 release are
* some new Ant tasks
* improved OSGI support
* numerous bug fixes as documented in Jira and in the release notes

As a release candidate version, we strongly encourage the use of this version 
for 
testing and validation. From now on, features are frozen until final 2.4.0 
version, 
only bug fixes will be applied before 2.4.0. If no outstanding bugs are 
reported 
with this release candidate, it will promoted to 2.4.0 about three weeks after 
this
release candidate. 

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

Download the 2.4.0-RC1 release 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

Re: [ANNOUNCE] Apache Ivy 2.4.0-RC1 released

[Maarten Coene]

Should I add this release to http://ant.apache.org/index.html?
Or is that only reserved for final releases?

Maarten





 Van: Maarten Coene maarten_co...@yahoo.com
Aan: ant-dev dev@ant.apache.org 
Verzonden: dinsdag 1 april 22:43 2014
Onderwerp: [ANNOUNCE] Apache Ivy 2.4.0-RC1 released
 

The Apache Ivy project is pleased to announce its 2.4.0-RC1 release.

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

Key features of this 2.4.0-RC1 release are
* some new Ant tasks
* improved OSGI support
* numerous bug fixes as documented in Jira and in the release notes

As a release candidate version, we strongly encourage the use of this version 
for 
testing and validation. From now on, features are frozen until final 2.4.0 
version, 
only bug fixes will be applied before 2.4.0. If no outstanding bugs are 
reported 
with this release candidate, it will promoted to 2.4.0 about three weeks after 
this
release candidate. 

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

Download the 2.4.0-RC1 release 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

Re: Ivy performance fix

[Maarten Coene]

Thanks!
I'll try to have a look at it soon.

Maarten



 Van: Josh Suereth joshua.suer...@gmail.com
Aan: Ant Developers List dev@ant.apache.org; Maarten Coene 
maarten_co...@yahoo.com 
Verzonden: dinsdag 1 april 21:47 2014
Onderwerp: Re: Ivy performance fix
 


Done: https://issues.apache.org/jira/browse/IVY-1465



On Tue, Apr 1, 2014 at 3:40 PM, Josh Suereth joshua.suer...@gmail.com wrote:

Can do.  I'll have to find a jira account.



On Tue, Apr 1, 2014 at 3:36 PM, Maarten Coene maarten_co...@yahoo.com wrote:

Hi Josh,

yes I think we can merge this in the 2.4.0 final release, but we'll have to 
review a bit in more detail first.
However, could you create a JIRA issue containing a link to the patch?

thanks!
Maarten




 Van: Antoine Levy Lambert anto...@gmx.de
Aan: Ant Developers List dev@ant.apache.org
Verzonden: dinsdag 1 april 3:58 2014
Onderwerp: Re: Ivy performance fix



Hello Josh,

thanks for contacting the Ant/Ivy community.

I think we can work with pull requests on github, as long as we see clearly 
the diffs with the code in the svn repository we should be fine.

@Maarten, Nicolas, and others in the Ivy community, do you think we can merge 
this before building the ivy 2.4.0 final ?

Regards,

Antoine

On Mar 31, 2014, at 4:15 PM, Josh Suereth joshua.suer...@gmail.com wrote:

 So, for the sbt project we noticed significant resolution time improvements
 with the following patch:

 https://github.com/sbt/ivy/pull/1

 The reasoning:


   - A lot of artifacts being resolved use Maven's dependencyManagement
   conventions
   - Ivy appears to turn these into exact matcher rules
   - A ton of resolution time is spent filtering through these rules
   - The existing solution is O(n) for all overrides


 What the patch does:


   - Creates a key'd store for all exact matcher rules
   - When executing rules, ensure that we only traverse what we have to
   (non-exact, exact specific to our key and default).


 As I said, this represents a significant speed bump for sbt builds using
 Ivy.  All existing tests pass, and I think they cover this aspect of ivy
 pretty well, from what I could see.

 What's the best mechanism to submit this back?  Do you accept pull requests
 on github?

 Thanks!
 - Josh Suereth
  Tools Lead
   Typesafe, Inc.


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy tests not passing

[Maarten Coene]

Hi Josh,

The junit tests should all pass when you run them with Ant.
On what platform do you run them and what is the error you get?

Maarten





 Van: Josh Suereth joshua.suer...@gmail.com
Aan: dev@ant.apache.org 
Verzonden: vrijdag 28 maart 20:48 2014
Onderwerp: Ivy tests not passing
 

Hello Ivy Community!

I'm Josh Suereth with the sbt build tool.   We've been using Ivy for a few
years now, and have recently decided that we'd like to start contributing
back some of the usability/performance fixes we have.

I'm running into an issue though:  Failing tests.

I checked out all the docs I could find, but I don't see how to set up my
environment correctly for running tests.  Particularly:


   - IBiblioTestResolver.testErrorReport
   - Everything that hits the eclipse m2 repository or is related to OSGi


Does anyone know where I can look for more information, or does anyone else
see the same issues?

Note: I'm running off the github fork of the ivy repo.


Thanks!
- Josh

Re: [RESULT][VOTE]Apache Ivy 2.4.0-rc1

[Maarten Coene]

A short update about the release progress:

- the binaries are published and the website is updated.
- I still have to create the Eclipse plugin, I'll try to do it this weekend. 

Maarten





 Van: Maarten Coene maarten_co...@yahoo.com
Aan: ant-dev dev@ant.apache.org 
Verzonden: maandag 24 maart 23:02 2014
Onderwerp: [RESULT][VOTE]Apache Ivy 2.4.0-rc1
 

Hi all,

I'm glad to announce that the vote for the Apache Ivy 2.4.0-rc1 release has 
passed with 4 +1 votes.
I'll continue the release process during the next couple of days.

Maarten

Re: svn commit: r1553704 - /ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java

[Maarten Coene]

Maybe a bit late, but what was the reason to use a ThreadLocal here?
This gives issues when the configuration of Ivy (for instance setting a custom 
logger) is done from a different thread than the actual resolve.

Maarten




 Van: cdu...@apache.org cdu...@apache.org
Aan: notificati...@ant.apache.org 
Verzonden: vrijdag 27 december 18:40 2013
Onderwerp: svn commit: r1553704 - 
/ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java
 

Author: cduffy
Date: Fri Dec 27 17:40:20 2013
New Revision: 1553704

URL: http://svn.apache.org/r1553704
Log:
Move non-root MessageLogger instances into a thread-local stack

Logger context is inherently thread-local.

Modified:
    ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java

Modified: 
ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java
URL: 
http://svn.apache.org/viewvc/ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java?rev=1553704r1=1553703r2=1553704view=diff
==
--- ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java 
(original)
+++ ant/ivy/core/trunk/src/java/org/apache/ivy/util/MessageLoggerEngine.java 
Fri Dec 27 17:40:20 2013
@@ -34,7 +34,7 @@ import java.util.Stack;
  * /p
  */
public class MessageLoggerEngine implements MessageLogger {
-    private final Stack/*MessageLogger*/ loggerStack = new Stack();
+    private final ThreadLocal/*StackMessageLogger*/ loggerStacks = new 
ThreadLocal();
    
     private MessageLogger defaultLogger = null;

@@ -44,6 +44,15 @@ public class MessageLoggerEngine impleme

     private List errors = new ArrayList();
    
+    private Stack getLoggerStack() {
+        Stack stack = (Stack) loggerStacks.get();
+        if (stack == null) {
+            stack = new Stack();
+            loggerStacks.set(stack);
+        }
+        return stack;
+    }
+    
     public MessageLoggerEngine() {
     }

@@ -66,7 +75,7 @@ public class MessageLoggerEngine impleme
      */
     public void pushLogger(MessageLogger logger) {
         Checks.checkNotNull(logger, logger);
-        loggerStack.push(logger);
+        getLoggerStack().push(logger);
     }
    
     /**
@@ -76,8 +85,8 @@ public class MessageLoggerEngine impleme
      * /p
      */
     public void popLogger() {
-        if (!loggerStack.isEmpty()) {
-            loggerStack.pop();
+        if (!getLoggerStack().isEmpty()) {
+            getLoggerStack().pop();
         }
     }

@@ -86,10 +95,10 @@ public class MessageLoggerEngine impleme
      * @return the current logger, or the default one if there is no logger in 
the stack
      */
     public MessageLogger peekLogger() {
-        if (loggerStack.isEmpty()) {
+        if (getLoggerStack().isEmpty()) {
             return getDefaultLogger();
         }
-        return (MessageLogger) loggerStack.peek();
+        return (MessageLogger) getLoggerStack().peek();
     }

     private MessageLogger getDefaultLogger() {
@@ -130,7 +139,7 @@ public class MessageLoggerEngine impleme
    
     public void clearProblems() {
         getDefaultLogger().clearProblems();
-        for (Iterator iter = loggerStack.iterator(); iter.hasNext();) {
+        for (Iterator iter = getLoggerStack().iterator(); iter.hasNext();) {
             MessageLogger l = (MessageLogger) iter.next();
             l.clearProblems();
         }
@@ -142,7 +151,7 @@ public class MessageLoggerEngine impleme
     public void setShowProgress(boolean progress) {
         getDefaultLogger().setShowProgress(progress);
         // updates all loggers in the stack
-        for (Iterator iter = loggerStack.iterator(); iter.hasNext();) {
+        for (Iterator iter = getLoggerStack().iterator(); iter.hasNext();) {
             MessageLogger l = (MessageLogger) iter.next();
             l.setShowProgress(progress);
         }

Re: [VOTE] Apache Ivy 2.4.0-rc1 Release

[Maarten Coene]

Almost forgot to vote myself :-)

+1

Maarten





 Van: Maarten Coene maarten_co...@yahoo.com
Aan: ant-dev dev@ant.apache.org 
Verzonden: zaterdag 15 maart 23:17 2014
Onderwerp: [VOTE] Apache Ivy 2.4.0-rc1 Release
 

Hi all,

I have built Apache Ivy 2.4.0-rc1.

Here are the links:
SVN tag: https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1/
Binaries: https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0-rc1
Maven repository: 
https://repository.apache.org/content/repositories/orgapacheant-1002/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Kind regards,
Maarten Coene

[RESULT][VOTE]Apache Ivy 2.4.0-rc1

[Maarten Coene]

Hi all,

I'm glad to announce that the vote for the Apache Ivy 2.4.0-rc1 release has 
passed with 4 +1 votes.
I'll continue the release process during the next couple of days.

Maarten

Re: [VOTE] Apache Ivy 2.4.0-rc1 Release

[Maarten Coene]

Hi Stefan,

good questions. I don't know if this is intentional, but it happens to be 
implemented that way in the build files for a long time. These hasn't been 
changed, so I guess this was the same in the previous Ivy releases. Do you 
think we should change it and is this blocking for this release?

Maarten





 Van: Stefan Bodewig bode...@apache.org
Aan: dev@ant.apache.org 
Verzonden: woensdag 19 maart 6:20 2014
Onderwerp: Re: [VOTE] Apache Ivy 2.4.0-rc1 Release
 

Hi Maarten

the source tarball and the svn tag differ in zwo places:

* the whole docs subdir - the source tarball contains the processed
  documentation rather than the Xooki files

* the ivy.xml are
 different

Is this intentional?

Stefan



-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[VOTE] Apache Ivy 2.4.0-rc1 Release

[Maarten Coene]

Hi all,

I have built Apache Ivy 2.4.0-rc1.

Here are the links:
SVN tag: https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1/
Binaries: https://dist.apache.org/repos/dist/dev/ant/ivy/2.4.0-rc1
Maven repository: 
https://repository.apache.org/content/repositories/orgapacheant-1002/

Do you vote for the release of these binaries?

[ ] Yes
[ ] No

Kind regards,
Maarten Coene

Re: [VOTE] Ivy 2.4.0-rc1 Release

[Maarten Coene]

No problem Charles, 
I can finish the release for you unless there are other candidates who want to 
give it a try?

thanks,
Maarten





 Van: Charles Duffy char...@dyfis.net
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: maandag 10 maart 16:47 2014
Onderwerp: Re: [VOTE] Ivy 2.4.0-rc1 Release
 

If you could finish up, that would be very much appreciated. Whereas my
former employer allowed for some amount of Ivy work on business hours, such
is no longer the case, and my personal time has more demands than I'm
presently able to satisfy.

Thank you kindly, and please accept my apologies.



On Tue, Mar 4, 2014 at 8:46 PM, Antoine Levy Lambert anto...@gmx.de wrote:

 Charles,

 are you going to be able to finish the release ?

 Do you need some help ?

 Best regards,

 Antoine
 On Feb 25, 2014, at 8:18 AM, Antoine Levy Lambert anto...@gmx.de wrote:

  Hi,
 
  I still do not see the public GPG key of Charles under
 https://dist.apache.org/repos/dist/release/ant/KEYS
 
  I did the following checkout to create a small sandbox with this KEYS
 file in it :
 
 
 
  svn checkout --depth=files --depth=files
 https://dist.apache.org/repos/dist/release/ant/ dist-release-ant
 
  Charles, let us know if you can check in your public key there.
 
 
 
  Antoine
 
 
 
  On Feb 15, 2014, at 9:23 AM, Nicolas Lalevée nicolas.lale...@hibnet.org
 wrote:
 
  Note that the release if not accepted yet, it cannot be published.
 
  Nicolas
 
  Le 14 févr. 2014 à 14:55, Charles Duffy char...@dyfis.net a écrit :
 
  Apologies -- new job; I dropped the ball somewhat. I'll try to get
 things
  back on track this weekend.
 
 
  On Fri, Feb 14, 2014 at 1:58 AM, Jean-Louis Boudart 
  jeanlouis.boud...@gmail.com wrote:
 
  Is the release over ?
 
  I dont find it on maven central
  Le 28 janv. 2014 01:46, Charles Duffy char...@dyfis.net a écrit :
 
  The keys are actually different -- the one used by the
 currently-posted
  .asc files is associated with Indeed, Inc. I'll be resigning the
 binaries
  after verifying that their Indeed signatures are intact (and moving
 them
  to
  dist.apache.org at that time).
 
  Expect a note in this thread when that happens.
 
 
  On Mon, Jan 27, 2014 at 6:42 PM, Nicolas Lalevée 
  nicolas.lale...@hibnet.org
  wrote:
 
 
  Le 22 janv. 2014 à 00:52, Nicolas Lalevée 
 nicolas.lale...@hibnet.org
  a
  écrit :
 
  I have found some issues. The source distribution seems to miss
 some
  test files. I guess this has been the case for quite some time. And
 it
  is
  just about the tests. And it is an RC. So OK for me. And I will
 fix
  that
  soon in trunk.
 
  To avoid confusion and make things simpler, I suggest we modify the
  release process to that everything goes through the svn of
  dist.apache.org,
  and not use anymore people.apache.org. In the end, everything is
  published there.
  And I'll modify in the doc of the release process the template of
 the
  email of the vote to include a line that is referencing the svn
 tag. So
  it's more difficult to miss it, and it is helpful to do review.
 
  I have tested the staging update site: works like a charm.
 
  So LGTM.
 
  I will cast my vote as soon as I can verify the signature of the
  artifacts.
 
  You pushed some keys to the KEYS files, but it doesn't seems to be
 the
  same as the one you used to sign the proposed artifacts.
 
  My gpg is asking for the key ID 93FB868A. Did I do something wrong
 or
  the
  keys are actually different ?
 
  Nicolas
 
 
 
  Nicolas
 
  Le 21 janv. 2014 à 17:19, Charles Duffy char...@dyfis.net a
 écrit
  :
 
  FYI --
 
  A tag at
  https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.4.0-rc1now
  exists. This differs from the branch head from which the binaries
  for
  test
  were built only inasmuch as its svn:externals specify a specific
  revision
  of the documentation build tools rather than leaving their
 revision
  floating.
 
 
  On Tue, Jan 21, 2014 at 6:54 AM, Charles Duffy char...@dyfis.net
 
  wrote:
 
  Howdy --
 
  I've attempted to follow the documentation at
  http://ant.apache.org/ivy/history/trunk/dev/makerelease.html and
 
  http://ant.apache.org/ivy/ivyde/history/trunk/dev/updatesite.html(as
  included-by-reference in the former) in preparing the above. That
  said, it
  appears that I missed step 12 (and, accordingly, have a 1.4.0-rc1
  branch,
  from the present tip of which the binaries were built, but no
  associated
  tag).
 
  I'll be sure to get KEYS up-to-date. Thank you for the pointers.
 
 
  On Tue, Jan 21, 2014 at 6:26 AM, Stefan Bodewig 
  bode...@apache.org
  wrote:
 
  Hi Charles,
 
  we don't really release binaries, they are just a convenience.
  All
  that
  matters as a release is the sources.
 
  I'm not sure there is anything documenting the release process
 for
  Ivy
  but in general you create an svn tag and build source and binary
  distributions from that.
 
  What you have built now is a binary for testing and you don't
  really
  

Re: AW: Java version of Ivy/IvyDE

[Maarten Coene]

For Ivy we should stick to the same minimal JDK version as Ant. (JDK 1.5)

For IvyDE we could upgrade to the mimimal JDK version required for Eclipse. 
(JDK 1.6)


So: 

[ ] we should continue to support Java 1.4 
[X] we should make Ivy require Java 5 
[X] we should make IvyDE require Java 6

Maarten




 Van: Jan Matèrne (jhm) apa...@materne.de
Aan: 'Ant Developers List' dev@ant.apache.org 
Verzonden: maandag 2 september 15:40 2013
Onderwerp: AW: Java version of Ivy/IvyDE
 

 I would vote for supporting Java 6 and then indicating on the website
 which ant + ivy/ivyDE version combination is needed to support pre-JDK
 1.6 environments, especially given the argument about Ant requiring
 more recent JDK version.

+1
Like [1] for Ant.


  As discussed with the Java requirement of Ant, Java 5 is deprecated
 too, and I for instance cannot run it anymore on my machine. So I would
 suggest to jump directly to require Java 6.

For Ant there wasn't a vote that I am aware of.
My last information is that Ant requires 1.5 [1], but there was a discussion 
[2] of moving to 1.6.




  So what do you think ?


[ ] we should continue to support Java 1.4 
[ ] we should make Ivy and IvyDE require Java 5 
[X] we should make Ivy and IvyDE require Java 6

As Jesse pointed out in [2] the actuals IDEs are requiring newer Java versions.
IvyDE is an IDE plugin so follow that.
For Ivy go the way as Ant wanted to go (but hasnt voted yet).

Jan

[1] http://ant.apache.org/faq.html#java-version
[2] 
http://ant.1045680.n5.nabble.com/Future-of-JDK-5-support-in-Ant-td5714291.html#a5714299


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [PATCH] IVY-1436

[Maarten Coene]

Could you please attach your patch to the JIRA issue?

Thanks!
Maarten





 Van: Jerry Maloney gpjerrymalo...@gmail.com
Aan: dev@ant.apache.org 
Verzonden: woensdag 28 augustus 3:37 2013
Onderwerp: [PATCH] IVY-1436
 


This patch fixes the issue I described in 
https://issues.apache.org/jira/browse/IVY-1436 .

Thanks,

Jerry Maloney

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Release Ant 1.9.2

[Maarten Coene]

+1

Maarten





 Van: Stefan Bodewig bode...@apache.org
Aan: dev@ant.apache.org 
Verzonden: dinsdag 9 juli 13:04 2013
Onderwerp: [VOTE] Release Ant 1.9.2
 

Hi all,

a very small release with some bugfixes in addition to the workaround
for Oracle's javadoc vulnerability.

I propose to adopt the following as Ant 1.9.2

SVN tag: http://svn.apache.org/repos/asf/ant/core/tags/ANT_192/
    revision 1500831
Tarballs: https://dist.apache.org/repos/dist/dev/ant/
    revision 2394
Maven Artifacts:
    
https://repository.apache.org/content/repositories/orgapacheant-116/org/apache/ant/

Vote will be open for about 72 hours

Cheers

        Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [Ivy] Support for generic filters (and download-option) on Ivy's resolve + post resolve tasks

[Maarten Coene]

Hi Tim,

I like the idea, so a patch would be grealty appreciated.

There already exists a very old JIRA issue for this, so you can attach your 
patch to that one:
https://issues.apache.org/jira/browse/IVY-439

thanks,
Maarten




 Van: Tim Enderling t.enderl...@intershop.de
Aan: 'Ant Developers List' dev@ant.apache.org 
Verzonden: dinsdag 28 mei 12:35 2013
Onderwerp: [Ivy] Support for generic filters (and download-option) on Ivy's 
resolve + post resolve tasks
 

Hi,

we would like to use Ivy in our build and deployment process.

In order to implement this I'm missing functionality on the - already very 
versatile - Ivy resolve task: While the ResolveOptions class allows arbitrary 
filters to be set, Ivy resolve only allows to specify the type attribute, which 
will always result in an instance of ArtifactTypeFilter in the resolve options. 
I would like to use a different (custom) filter implementation here.

Unfortunately the method IvyResolve.getResolveOptions(Ivy, String[], 
IvySettings) is private, so I cannot add another filter simply through 
subclassing IvyResolve in a custom Ant task. 

I propose to make it possible to add a single implementation of 
org.apache.ivy.util.filter.Filter as nested element of IvyResolve, as well as 
IvyPostResolveTask. (A single filter would be sufficient, as we can simply 
provide compounds like the AndFilter and OrFilter.) For compatibility the type 
attribute must still be supported and either be combined with an additional 
custom filter (by logical and) or only one of them can be used. 

Filter should generally extend Ant's DataType to enable reference-handling and 
be defined as global Ant types with typedefs. (Which means the element for the 
OrFilter cannot be called simply 'or', but must be called 'orfilter', but this 
seems more plausible to me than what Ant does with conditions and file 
selectors.) This way anyone is free to add custom filters. 

For all existing implementations of org.apache.ivy.util.filter.Filter there 
should be an accompanying wrapper, that basically does the same but extends 
from Ant's DataType class. (We cannot simply change them, since this would tie 
using Filters to having Ant in the classpath.)

Another small thing is, that ResolveOption's download field cannot be set to 
false through IvyResolve. I would also like to add an attribute to that. 
(Setting download to false can theoretically be emulated by providing a 
type-attribute with a type that is guaranteed to not be used in artifact 
declarations - like type=(none), but as you would probably agree this is only 
a hack.) 

What do you think?

If you generally agree to include this in the next release, I can submit an 
according patch.

Background:
Our concrete use case for filters is that we mark platform specific artifacts 
(we publish platforms for different platforms inside the same Ivy module) with 
an extra attribute, containing the target platform. (I know that there are 
other proposed ways to solve the problem of platform specific artifacts, like 
using Ivy configurations, but just for a minute, take our solution to this as 
settled.) During resolve I only want to download those artifacts, that match 
the current platform (or are platform independent). Therefore I would like to 
use an artifact filter that can compare the value of an extra attribute with an 
expected value in a certain way.

The use case for setting the download attribute to false is to use the 
resolve task to only gain insights over the dependency graph of modules (like 
by reusing the resulting ResolveReport in a custom post resolve task), not 
wanting to fiddle with artifacts at all.

Best regards,
Tim Enderling

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Ant 1.9.1 Release

[Maarten Coene]

+1

The WHATSNEW document contains an empty section 'Changes from Ant 1.9.1 TO 
current', which is rather strange for a 1.9.1 release...
Apart from that, I didn't find any problems when running our builds with this 
new version.

Maarten





 Van: Antoine Levy Lambert anto...@gmx.de
Aan: Ant Developers List dev@ant.apache.org 
Verzonden: donderdag 16 mei 5:12 2013
Onderwerp: [VOTE] Ant 1.9.1 Release
 

Hi,

I have uploaded candidate artefacts for an ant 1.9.1 release to :
http://people.apache.org/~antoine/dist

Let's vote on releasing these.


Let's start with my own +1.

Regards,

Antoine

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Michael Clarke as a committer

[Maarten Coene]

+1

Maarten





 From: Bruce Atherton br...@callenish.com
To: dev@ant.apache.org 
Sent: Tuesday, March 12, 2013 6:03 PM
Subject: [VOTE] Michael Clarke as  a committer
 
I'd like to nominate Michael Clarke as a committer. Not only has he revamped 
our testing infrastructure to make it compatible with JUnit4, he has also 
worked on resolving older bugs in our bugzilla that touched on testing. Let's 
vote on it.

[ ] +1 to add Michael Clarke as a committer
[ ] -1 to disagree
[ ] ±0 means I don't care.


Here is my +1.

Bruce


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Ant 1.9.0 release [2nd attempt]

[Maarten Coene]

+1

Maarten





 From: Antoine Levy Lambert anto...@gmx.de
To: Ant Developers List dev@ant.apache.org 
Sent: Thursday, March 7, 2013 2:47 AM
Subject: Re: [VOTE] Ant 1.9.0 release [2nd attempt]
 
Adding that I had forgotten to put the .asc files, this is now uploaded too.


On Mar 5, 2013, at 11:16 PM, Antoine Levy Lambert wrote:

 Hi,
 
 I have uploaded candidate artifacts a second time for an ant 1.9.0 release to 
 : http://people.apache.org/~antoine/dist/ after having incorporated the 
 patches of Michael Clarke concerning JUnit.
 
 Let's vote on releasing Ant 1.9.0 a second time.
 
 Let' start with my own +1
 
 Regards,
 
 Antoine


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: [VOTE] Accept EasyAnt as a subproject - take 2

[Maarten Coene]

+1

Maarten





 From: Nicolas Lalevée nicolas.lale...@hibnet.org
To: Ant Developers List dev@ant.apache.org 
Sent: Wednesday, February 27, 2013 7:44 PM
Subject: [VOTE] Accept EasyAnt as a subproject - take 2
 
Hi,

This is the come back of the proposal of bringing EasyAnt under the umbrella of 
the Ant PMC.

There were some discussion on incubator-general about the incubating hcatalog 
project being graduated under the umbrella of the Hive PMC. I think that our 
case is more clear and more standard regarding the ASF rules, but I'll remind 
here what is at stake, so there is no misunderstanding (I include myself on the 
potentially misunderstanding people).

EasyAnt code will be brought into Ant's svn tree.
EasyAnt committers will become Ant committers but not part of the PMC (on 5 
committers, 3 are already Ant ones, and 2 are part of Ant's PMC)
The Ant PMC will be responsible for the code, the community, the next releases 
of EasyAnt.

Just like for Ivy. And I like the way it worked. Further more considering my 
path, I think it is good that there is no special right management in svn. I 
started as an IvyDE committer, I ended improving myself Ivy and Ant.

Since the last vote tentative, the activity on EasyAnt remained the same, 
somehow low but continuous, not much less than Ant developers activity. And 
lately we succeeded to get a release out.

To get yourself an opinion, here are some links:
- the EasyAnt project incubator page:
http://incubator.apache.org/projects/easyant.html
- the archive of the mailing lists
http://mail-archives.apache.org/mod_mbox/incubator-easyant-commits/
http://mail-archives.apache.org/mod_mbox/incubator-easyant-dev/
- the release
http://www.apache.org/dist/incubator/easyant

So, should we accept EasyAnt as a subproject ?
Please, cast your votes:
[ ] +1, I accept
[ ] +0, OK, but….
[ ] -1, I disapprove, because….

Nicolas


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy 2.3.x tested on Jenkins

[Maarten Coene]

Hi Nicolas,

I think we can remove this job from Jenkins again.
What do you think?

Maarten





 From: Nicolas Lalevée nicolas.lale...@hibnet.org
To: Ant Developers List dev@ant.apache.org 
Sent: Wednesday, August 22, 2012 10:56 AM
Subject: Re: Ivy 2.3.x tested on Jenkins
 
The Ivy-tests job now run on both Ubuntu and Windows:
https://builds.apache.org/pview/job/Ivy-tests/

Nicolas

Le 20 août 2012 à 23:23, Maarten Coene a écrit :

 Thanks Nicolas :-)
 I also think a build matrix for Ivy would be a good idea...
 
 Maarten
 
 
 
 
 From: Nicolas Lalevée nicolas.lale...@hibnet.org
 To: Ant Developers List dev@ant.apache.org 
 Sent: Monday, August 20, 2012 5:20 PM
 Subject: Ivy 2.3.x tested on Jenkins
 
 Since the trunk is moving a little from the 2.3.x branch, I have setup a 
 build of the Ivy test suite of the 2.3.x branch:
 https://builds.apache.org/job/Ivy-2.3-tests/
 
 Also, I have seen Maarten struggle with Unix path just like I do with Windows 
 paths :)
 I think it will be interesting to do a build matrix for Ivy, like for Ant. 
 At least to test on both ubuntu and Windows. Not sure it will be interesting 
 to test for every jvm.
 
 Nicolas
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
 For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[ANNOUNCE] Apache Ivy 2.3.0 released

[Maarten Coene]

The Apache Ivy project is pleased to announce its 2.3.0 release.

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

Key features of this 2.3.0 release are
* improved Ant support with some new Ant tasks and enhancements to existing 
tasks
* improved Maven2 compatibility
* some new resolvers
* numerous bug fixes as documented in Jira and in the release notes

In addition, experimental OSGI support has been added to the Ivy core.

You can download this 2.3.0 release at:
http://ant.apache.org/ivy/download.cgi

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

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

Regards,
Maarten Coene

Re: [VOTE] Apache Ivy 2.3.0 release

[Maarten Coene]

+1

Maarten





 From: Maarten Coene maarten_co...@yahoo.com
To: ant-dev dev@ant.apache.org 
Sent: Sunday, January 13, 2013 11:40 PM
Subject: [VOTE] Apache Ivy 2.3.0 release
 
Hi all,

I've created the binaries containing the Apache Ivy 2.3.0 release.

These binaries can be found here:
https://dist.apache.org/repos/dist/dev/ant/ivy/2.3.0/

Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapacheant-125/

Eclipse Update site is located here:
https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivy-2.3.0.final_20130110142753/

They are based on the following tag:
https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.3.0/

Do you vote for the release of these binaries?

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

kind regards,
Maarten Coene

[RESULT][VOTE] Apache Ivy 2.3.0 release

[Maarten Coene]

Hi all,

I'm pleased to announce that the vote for the Apache Ivy 2.3.0 release has 
passed.
There were 4 binding +1 votes from Antoine, Jean-Louis, Nicolas and myself.
A non-binding +1 vote has been made by Paul King


I'll continue the release process the next couple of days.

Maarten

[VOTE] Apache Ivy 2.3.0 release

[Maarten Coene]

Hi all,

I've created the binaries containing the Apache Ivy 2.3.0 release.

These binaries can be found here:
https://dist.apache.org/repos/dist/dev/ant/ivy/2.3.0/

Maven artifacts are here:
https://repository.apache.org/content/repositories/orgapacheant-125/

Eclipse Update site is located here:
https://dist.apache.org/repos/dist/dev/ant/ivyde/updatesite/ivy-2.3.0.final_20130110142753/

They are based on the following tag:
https://svn.apache.org/repos/asf/ant/ivy/core/tags/2.3.0/

Do you vote for the release of these binaries?

  [ ] +1 Release these artifacts
  [ ] +0 OK, but...
  [ ] -0 OK, but really should fix...
  [ ] -1 I oppose this release because...

kind regards,
Maarten Coene

Apache Ivy 2.3.0

[Maarten Coene]

Hi all,
 
I would like to create the Apache Ivy 2.3.0 final release somewhere next week.
It will be based on the current 2.3.x branch and will contain some bugfixes 
reported against 2.3.0-RC2.
http://svn.apache.org/viewvc/ant/ivy/core/branches/2.3.x/CHANGES.txt?view=markup
 
Any objections?
 
Maarten

Re: [RESULT][VOTE] Apache Ivy 2.3.0-RC2 release (2nd attempt)

[Maarten Coene]

Nicolas,

there was problem with the checksums, they didn't match.
I've regenerated the plugin, could you check if I din't forget anything?

At least I can install the plugin now from within Eclipse, so I guess it's ok?

thanks,
Maarten





 From: Nicolas Lalevée nicolas.lale...@hibnet.org
To: Ant Developers List dev@ant.apache.org 
Sent: Wednesday, November 14, 2012 10:56 PM
Subject: Re: [RESULT][VOTE] Apache Ivy 2.3.0-RC2 release (2nd attempt)
 

Le 14 nov. 2012 à 20:41, Maarten Coene maarten_co...@yahoo.com a écrit :

 Nicolas,
 
 can you ping me if the Eclipse update site is ready?
 If you haven't started yet, I could try to publish it myself if you want.
 
 I'm waiting for this to send the official announcement.

sorry for the delay.
done and tested.

cheers,
Nicolas

 
 Maarten
 
 
 
 
 
 From: Maarten Coene maarten_co...@yahoo.com
 To: Ant Developers List dev@ant.apache.org 
 Sent: Monday, November 12, 2012 11:09 PM
 Subject: Re: [RESULT][VOTE] Apache Ivy 2.3.0-RC2 release (2nd attempt)
 
 Thanks Nicolas,
 that would be really helpful! :-)
 
 
 Maarten
 
 
 
 
 From: Nicolas Lalevée nicolas.lale...@hibnet.org
 To: Ant Developers List dev@ant.apache.org 
 Sent: Monday, November 12, 2012 11:02 PM
 Subject: Re: [RESULT][VOTE] Apache Ivy 2.3.0-RC2 release (2nd attempt)
 
 
 Le 12 nov. 2012 à 22:49, Maarten Coene maarten_co...@yahoo.com a écrit :
 
 Hi all,
 
 I'm pleased to announce that the vote for the Apache Ivy 2.3.0-RC2 release 
 has passed.
 There were +1 votes from Nicolas, Jean-Louis, Antoine and myself.
 
 
 I'll continue the release process the next couple of days.
 
 I can help with the Eclipse update site if you want.
 
 Nicolas
 
 
 -
 To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
 For additional commands, e-mail: dev-h...@ant.apache.org


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

[ANNOUNCE] Apache Ivy 2.3.0-RC2 released

[Maarten Coene]

The Apache Ivy project is pleased to announce its 2.3.0-RC2 release.

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

Key features of this 2.3.0-RC2 release are
* improved Maven support
* numerous bug fixes as documented in Jira and in the release notes

As a release candidate version, we strongly encourage the use of this version 
for 
testing and validation. From now on, features are frozen until final 2.3.0 
version, 
only bug fixes will be applied before 2.3.0. If no outstanding bugs are 
reported 
with this release candidate, it will promoted to 2.3.0 about three weeks after 
this
release candidate. 

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

Download the 2.3.0-RC2 release 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