Re: Ivy - Goals for the upcoming release?

> Le 21 mai 2017 à 18:34, Gintautas Grigelionis a > écrit : > > Now that Ant is upgraded, I suggest converting tests to JUnit 4 (which > requires at least Ant 1.9.5, if I'm not mistaken). I can submit a patch > pretty soon. > > Introducing generics throughout (hey,

Re: Ivy - Goals for the upcoming release?

> Le 21 mai 2017 à 16:28, J Pai a écrit : > > The past few days I’ve sent some PRs for bug fixes and some enhancements in > preparation for the proposed release of Ivy. Thanks Nicolas for reviewing > them and merging those that were good enough. > > I’ve been using

Re: Ivy - Buildjobs/PreCommit

> Le 20 mai 2017 à 11:18, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit : > > >> Le 20 mai 2017 à 04:45, J Pai <jai.forums2...@gmail.com> a écrit : >> >> This pre-commit job is now almost functional. It gets triggered whenever >> there’s

Re: Ivy - BasicURLHandler ignoring timeout during connection?

I don’t know the history of that code, it probably is older that its incubation into Apache. But from what I can read, I think that timeout was introduced but just supported by one implementation of URLHandler: the HttpClient one, HttpClientHandler. Proper support in the BasicURLHandler will

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

Ant Bylaws is a good read to understand the process https://ant.apache.org/bylaws.html Since the initial question is about Ivy only, another vote will be needed for IvyDE. Nicolas > Le 20 mai 2017 à 04:47, J Pai a écrit : > > Not

Re: Ivy - Buildjobs/PreCommit

Build-Matrix-1.9.x-Linux/ <https://builds.apache.org/view/A/view/Ant/job/Ant-Build-Matrix-1.9.x-Linux/> AFAIR, it used to be able to do on several different OS. I don’t know why they are split. And I don’t know if it is possible to do it while pulling a PR from github. Nicolas &g

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

+1 Be able to test on an old jvm will be near impossible for me. Nicolas > Le 19 mai 2017 à 07:25, Jan Matèrne a écrit : > > 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). >

Re: Ivy - Buildjobs/PreCommit

y/pull/16> > > -Jaikiran > > On 17-May-2017, at 6:59 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org > <mailto:nicolas.lale...@hibnet.org>> wrote: > > Seems to be a classpath issue where two ivy.jar are loaded. Considering the > full console log, probably

Re: Minimum Java runtime version for proposed upcoming Ivy release

I think that upgrading the requirement on the JDK is a good idea, because at least us, the maintainers, need at some point to be able to test it if there is an issue with that minimum JDK. One thing to consider is which JDK is being required in the environment Ivy is being used: Ant, Gradle,

Re: Jenkins build is back to normal : IvyDE-updatesite #787

The build was broken because Ant was requiring a JDK 8. So I have setup the build to use the latest JDK 8. > Le 17 mai 2017 à 20:31, Apache Jenkins Server a > écrit : > > See >

Re: [jira] [Resolved] (IVY-1520) Have makepom task take description from ivy-module > info > description element

FYI, the things fixed in the master in git are marked in jira « master » as « fix version », so that we can just rename it when the release is done, wether we do a 2.5.0 or 2.4.x. Here we’ll indeed do a 2.5.0, but since others jira are already marked as on « master », I changed this one.

Re: Ivy - Buildjobs/PreCommit

Seems to be a classpath issue where two ivy.jar are loaded. Considering the full console log, probably due to init-ivy called twice, a consequence of Ant not computing one unified tree of tasks to call, but a list of trees of the tasks on the command line. The build dedicated to check the

Re: Ivy+IvyDE: help wanted

> Le 16 mai 2017 à 13:11, J Pai a écrit : > > Thanks Jan for initiating this. > > On the ICLA front - I already have contributed and continue to contribute to > some other Apache projects (these days mostly via github). Do I still have to > sign the ICLA? Is there

Re: VOTE Retire IvyDE

Considering the current discussion around IvyDE and the involvement of Gintas, maybe we could cancel this vote, at least postpone it ? Nicolas > Le 5 déc. 2016 à 08:04, Jan Matèrne (jhm) a écrit : > > I start a vote for retiring IvyDE. > > The last release was in 11/2013.

IvyDE status (Was: VOTE Retire IvyDE)

I am forking the thread to not pollute the vote. > Le 7 déc. 2016 à 19:56, Gintautas Grigelionis a > écrit : > > I decided to take a quick look at the build process and it's not broken per > se, rather it's hardcoded to Eclipse SDK 3.7.1 foe Win32. You confirm the doc

Re: VOTE Retire IvyDE

> Le 7 déc. 2016 à 12:34, Gintautas Grigelionis a > écrit : > > I would prefer an agreement on status. IvyDE is dependent on Ivy and > ideally their release cycles should be synced. > Since there seem to be some changes brewing in Ivy, IvyDE could be used as > a test

Re: VOTE Retire IvyDE

+1 Nicolas > Le 6 déc. 2016 à 17:22, Stefan Bodewig a écrit : > > On 2016-12-05, Jan Matèrne (jhm) wrote: > >> I start a vote for retiring IvyDE. > > +0 > > The discussion in the "Ivy" thread makes me think we'd probably want to > update it with new Ivy releases, even if

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

> Le 6 déc. 2016 à 17:21, Stefan Bodewig a écrit : > > On 2016-12-05, Jaikiran Pai wrote: > >> I have been following the latest emails on retiring sub projects in >> Ant. I just see a proposal to retire IvyDE (the Eclipse plugin) for >> valid reasons (given the lack of any

Re: VOTE Retire EasyAnt subproject

+1 Nicolas > Le 5 déc. 2016 à 08:04, Jan Matèrne (jhm) a écrit : > > I start a vote for retiring EasyAnt and all its components: > > - core > > - buildtypes > > - plugins > > - skeletons > > - tasks > > - easyant4e > > > > We never had a real release after the

Re: DISCUSS How to retire a subproject/component

Hi, See my comments inline. > Le 25 nov. 2016 à 08:18, Jan Matèrne (jhm) a écrit : > > There aren't as many comments as I hoped to get ... > A main comment was that we also need a process of reactivating a subproject. > > So here are the updated proposals for the two

Re: [VOTE] Release Ant 1.9.7 based on RC1

+1 Nicolas > Le 9 avr. 2016 à 12:03, Stefan Bodewig a écrit : > > 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

Re: [VOTE] Stephen Haberman as a committer

+1 Nicolas > Le 5 oct. 2015 à 11:06, Conor MacNeill a écrit : > > 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, >

Re: Roadmap, goals, future of Ivy?

Le 23 août 2015 à 20:10, Stephen Haberman stephen.haber...@gmail.com a écrit : Hi Jaikiran, FWIW I've made similar complaints about inactivity on Ivy, and suggested awhile ago that Ivy needs a new group of committers/contributors who are willing/able to put the time into the project.

Re: Looking to contribute

Le 16 juil. 2015 à 14:14, Jaikiran Pai jai.forums2...@gmail.com a écrit : Hi Jean-Louis, I'm thinking of submitting via pull requests. I had a quick look at the open JIRAs and haven't yet narrowed down on my first choice yet (just to get started familiarizing myself with the code). I

Re: [VOTE] Release Ant 1.9.6 based on RC1

LGTM. +1 for the release Nicolas Le 29 juin 2015 à 11:32, Stefan Bodewig bode...@apache.org a écrit : Hi all I've created a release candidate for 1.9.6: git tag: ANT_196_RC1 hash: a143e2d3a on commit: b09976c tarballs: https://dist.apache.org/repos/dist/dev/ant/

Re: Doing a quick 1.9.5.1? (was Re: ant git commit: COMPRESS-317 ArrayIndexOutOfBoundsException in ZipArchiveEntry#getMergedFields)

I don’t much about popularity of these extra fields, but the bug seems annoying enough and the fix trivial enough to release an Ant 1.9.6 (I don’t see the need to add an extra number to the version). So +1. Nicolas Le 9 juin 2015 à 06:34, Stefan Bodewig bode...@apache.org a écrit : On

Re: Bug 56721 - back quote and quote

Le 10 juin 2015 à 08:21, Jan Matèrne j...@materne.de a écrit : https://bz.apache.org/bugzilla/show_bug.cgi?id=56721 The user was irritated by the quoting of the build sequence: Build sequence for target(s) `release' is [-set-mode-check, -set-release-mode, ... It starts with

Re: [VOTE] Release Ant 1.9.5 based on RC1

+1 Nicolas Le 31 mai 2015 à 16:46, Stefan Bodewig bode...@apache.org a écrit : 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

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

Le 9 avr. 2015 à 16:51, Maarten Coene maarten_co...@yahoo.com.INVALID a écrit : 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

Re: xooki to asciidoc, a proof of concept

are very web oriented. The first because of its layout. The second due to its form. I’m not sure what to do about them. Nicolas Le 30 déc. 2014 à 20:57, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 30 déc. 2014 à 17:16, Jean-Louis Boudart jeanlouis.boud...@gmail.com

Re: [Ivy] A workspace resolver for Ant

. Antoine On Jan 25, 2015, at 4:51 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Hi, We’ve been wondering if the workspace resolver which exists for IvyDE could be transposed to the Ant world. I think I have made a working one. And I just pushed it. The main issue

Re: issue with IBiblioResolverTest.testErrorReport

Le 26 janv. 2015 à 00:56, Antoine Levy Lambert anto...@gmx.de a écrit : Hi, when I run the ivy test suite on my computer at home, the iBiblioResolverTest.testErrorReport errors. The error happens on line 251 : ResolvedModuleRevision rmr = resolver.getDependency(new

[Ivy] A workspace resolver for Ant

Hi, We’ve been wondering if the workspace resolver which exists for IvyDE could be transposed to the Ant world. I think I have made a working one. And I just pushed it. The main issue in the design was about how Ant would be able to describe to Ivy the projects to take into account, and which

Generating EasyAnt website

Hi, I tried to fixed the issues raised by Sebb about the links in EasyAnt’s website and I got issues. I am not sure which target should be called to get things generated. The command « easyant -p » is listing the usual targets for a project with a bunch of code, but this is not helpful and

Re: ant git commit: Arrays.copyOf is Java 1.6 only

Le 21 janv. 2015 à 12:10, Stefan Bodewig bode...@apache.org a écrit : On 2015-01-21, Jan Matèrne (jhm) wrote: right, we are tied to Java1.5 http://ant.apache.org/faq.html#java-version http://www.oracle.com/technetwork/java/eol-135779.html End of public updates: Java5: Oct 2009

Re: Git workflow

Le 11 janv. 2015 à 18:46, Stefan Bodewig bode...@apache.org a écrit : On 2015-01-11, Nicolas Lalevée wrote: By the way, is there any way to close manually the pull requests in github ? The only way is to reference it in a git commit ? Probably some infra folks can since you need write

Re: Git workflow

By the way, is there any way to close manually the pull requests in github ? The only way is to reference it in a git commit ? Nicolas Le 11 janv. 2015 à 13:17, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 7 janv. 2015 à 05:57, Stefan Bodewig bode...@apache.org a écrit

Re: Git workflow

Le 7 janv. 2015 à 05:57, Stefan Bodewig bode...@apache.org a écrit : On 2015-01-07, Nicolas Lalevée wrote: For instance, to get commits from one branch to the other, I have seen two ways: via merge or via cherry-pick. Since our branches are meant to diverge à some point, I think using

Git workflow

Hi guys, I am discovering a little bit of the extends of git, and it seems there are a lot of ways to handle branches and pull requests. Maybe we should all use the same way ? For instance, to get commits from one branch to the other, I have seen two ways: via merge or via cherry-pick. Since

Re: xooki to asciidoc, a proof of concept

. The toc.json would still be there too, to be edited manually. And there would be the asciidoctor ant task to generate the .html files. Nicolas 2014-12-29 23:21 GMT+01:00 Nicolas Lalevée nicolas.lale...@hibnet.org: Hi, I like xooki because it manages well the templating of the web pages

xooki to asciidoc, a proof of concept

Hi, I like xooki because it manages well the templating of the web pages, and it manage well how to build a toc. I hate when documentation is not « browsable », like in a wiki, and xooki handle it well. But is is quite slow, generating Ivy’s documentation can takes minutes. And on macos

[RESULT][VOTE] Ivy 2.4.0 Release - take 2

Counting my own +1, we have three +1 and one -1. The vote pass. I will publish the release. Nicolas Le 22 déc. 2014 à 17:57, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : I have signed the tag: See https://git-wip-us.apache.org/repos/asf?p=ant-ivy.git;a=tag;h=refs/tags/2.4.0

[ANNOUNCE] Apache Ivy 2.4.0 Released

December 26, 2014 - The Apache Ivy project is pleased to announce its 2.4.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

Re: [VOTE] Ivy 2.4.0 Release - take 2

-1 and three +1 (including me). I’ll keep the vote open a couple of days, to be sure everyone had the time to vote. And I’ll promote the artifacts. Nicolas Le 17 déc. 2014 à 14:25, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 17 déc. 2014 à 04:09, Antoine Levy Lambert anto

Re: [VOTE] Ivy 2.4.0 Release - take 2

Le 17 déc. 2014 à 04:09, Antoine Levy Lambert anto...@gmx.de a écrit : Nicolas, Jean-Louis, what are your thoughts ? The problem reported by Stefan with the ivy.xml in the source archive must be caused by something in the build process replacing the ivy.xml of the source tree with an

Re: Develop custom Ivy parser

Le 17 déc. 2014 à 22:25, Martin Flores mflor...@gmail.com a écrit : Hi everyone, I'm about to develop to develop a custom Ivy parser but I haven't found enough information on the Ant/Ivy web sites about it. I already checkout the Ivy code but, I would like to know if someone can point me

Re: [VOTE] Ivy 2.4.0 Release - take 2

https://twitter.com/jbaruch/ http://linkd.in/jbaruch On Wed, Dec 17, 2014 at 5:25 AM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Le 17 déc. 2014 à 04:09, Antoine Levy Lambert anto...@gmx.de a écrit : Nicolas, Jean-Louis, what are your thoughts ? The problem reported by Stefan

Re: [CANCELED][VOTE] Release Ivy 2.4.0

I pushed the current style folder into git so we can go forward with the release. If we have a better process later, we will just change it. Nicolas Le 10 déc. 2014 à 10:57, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Note that the style files are also useful to edit the doc

[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

Re: [CANCELED][VOTE] Release Ivy 2.4.0

Note that the style files are also useful to edit the doc within Ivy’s code source. So this needs to be easily fetchable for contributors. Having to maintain the styles folders between the source and the site one doesn’t seem that a burden. I prefer to have the burden on committers than on

Re: [CANCELED][VOTE] Release Ivy 2.4.0

PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: It was so obvious that this release candidate should be canceled that I forgot to officially set it. Here it is. I see that the infra ticket is resolved. Jean-Louis spotted some issues with it though. But I guess we will retry very soon

[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

Re: New release process for Ivy

-notes.html See also the update release process: http://ant.apache.org/ivy/history/trunk/dev/makerelease.html I think I will actually do a release this week-end. Nicolas Le 30 oct. 2014 à 00:51, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : So I have updated the release process to use git. I

Re: Updating Ivy's trunk doc in the site

, Antoine On Oct 27, 2014, at 7:10 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Le 26 oct. 2014 à 20:16, Jean-Louis Boudart jeanlouis.boud...@gmail.com a écrit : Would it be possible to have everything on git ? Looks like there is a gitpubsub feature available[1] I don’t know

New release process for Ivy

So I have updated the release process to use git. I also made some simplification. There used to be a release branch. I don’t think we need it anymore, so I have wrote a process without it. I have pushed the doc online: http://ant.apache.org/ivy/history/trunk/dev/makerelease.html Probably some

git merge is generating a lot of mails

As you can see on the notifications list, there is a nice bunch of mails, all generated from my one commit which merged the master of Ivy into the branch 2.4. I have hard time understand the rationale. Anyone more familiar with git than me have some explanation ? Note that I am not worried, I

Re: git merge is generating a lot of mails

I just did a plain git merge, since I actually wanted both branches to join. Nicolas Le 28 oct. 2014 à 23:30, Jean-Louis Boudart jeanlouis.boud...@gmail.com a écrit : Can you tell us the command you use ? Did you used squash option? Did you rebase ? 2014-10-28 22:55 GMT+01:00 Nicolas

Re: Commit Candidates for Ivy 2.4.x

Le 26 oct. 2014 à 20:19, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 26 oct. 2014 à 19:58, Jean-Louis Boudart jeanlouis.boud...@gmail.com a écrit : Hi Nicolas, My answers bellow. 2014-10-26 19:18 GMT+01:00 Nicolas Lalevée nicolas.lale...@hibnet.org: I have checked

Re: Updating Ivy's trunk doc in the site

Nicolas Lalevée nicolas.lale...@hibnet.org: Now that the Ivy’s code source is in git, but the site is still managed in svn, how do we update the doc of Ivy trunk in the site ? How can I update this : http://ant.apache.org/ivy/history/trunk/index.html We’ll have a similar issue when we

Re: Commit Candidates for Ivy 2.4.x

had to backport that to ivy 2.3 for sbt On Oct 26, 2014 3:30 PM, Jean-Louis Boudart jeanlouis.boud...@gmail.com wrote: 2014-10-26 20:19 GMT+01:00 Nicolas Lalevée nicolas.lale...@hibnet.org: - IVY-1465 [1] doesn’t seem to be fully finished. One part is in the branch, the commit ‘3076802a

Commit Candidates for Ivy 2.4.x

I have checked the branch 2.4.x. I have put back in the branch every thing that was obvious enough. There are some that may need to be merged back too, I would need some feedback about them. - IVY-1465 [1] doesn’t seem to be fully finished. One part is in the branch, the commit ‘3076802a’ [2]

Updating Ivy's trunk doc in the site

Now that the Ivy’s code source is in git, but the site is still managed in svn, how do we update the doc of Ivy trunk in the site ? How can I update this : http://ant.apache.org/ivy/history/trunk/index.html We’ll have a similar issue when we will release, we will need to publish the released

Re: Commit Candidates for Ivy 2.4.x

Le 26 oct. 2014 à 19:58, Jean-Louis Boudart jeanlouis.boud...@gmail.com a écrit : Hi Nicolas, My answers bellow. 2014-10-26 19:18 GMT+01:00 Nicolas Lalevée nicolas.lale...@hibnet.org: I have checked the branch 2.4.x. I have put back in the branch every thing that was obvious enough

Re: Release of Ivy 2.4.0

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

Re: IvyDE-updatesite - fix for jenkins

Le 27 juin 2014 à 22:29, Jan Matèrne j...@materne.de a écrit : https://builds.apache.org/job/IvyDE-updatesite/ is broken and I think its because it tries to download the ivy.jar from the wrong location. Because I dont have write access to that svn repo, I created a patch. Please try ;) I

Re: [jira] [Commented] (INFRA-7816) Create readonly git mirror for Xooki

Le 10 juin 2014 à 21:29, Jan Matèrne (jhm) apa...@materne.de a écrit : I wouldnt count myself to the Ivy team, but I prefer changing to trunk/branches structure: * conform to other svn repos * easier setup for infra for the read only git repo +1 Nicolas Jan -Ursprüngliche

Re: IvyDE compiler error @ Jenkins

Le 5 juin 2014 à 07:12, Jan Matèrne (jhm) apa...@materne.de a écrit : https://builds.apache.org/view/A-D/view/Ant/job/IvyDE/lastBuild/consoleFull [java] [javac] 650. ERROR in /home/jenkins/jenkins-slave/workspace/IvyDE/work/eclipse/plugins/org.apache.

Re: Repository access

I couldn't commit the patch you suggested for the ivyde updatesite in svn either. It must be read only. Nicolas Le 5 juin 2014 à 07:57, Jan Matèrne (jhm) apa...@materne.de a écrit : After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push

Re: migration to git : next steps - Jenkins

About IvyDE's updatesite project, it is really just a build script. We never release it. It is a just a helper to produce the binaries associated with an Ivy or IvyDE release so they can be downloaded directly into Eclipse. And it relies on some svn:externals of Apache's dist, so it should be

Re: Ivy's ModuleDescriptor.getExtraInfo() is now deprecated

Forget about that duplicate mail, this is me being tricked by the ASF email lag. It seems to still continue to lag a lot. Nicolas Le 8 mai 2014 à 17:07, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Hi, ModuleDescriptor.getExtraInfo() is deprecated but there is no indication

Ivy's ModuleDescriptor.getExtraInfo() is now deprecated

Hi, ModuleDescriptor.getExtraInfo() is deprecated but there is no indication in the doc about what should be used then. There is getExtraInfos(), but as I look to the code, there is no data transfer between both, if if there is data in one, I cannot get the data from the other one. And since

Re: Classloading issue

r1594279 seems to fix the issue, but I still don't understand why. Any suggestion of a better fix is welcomed. Nicolas Le 11 mai 2014 à 23:41, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Hi, I need some help to understand a bug around classloading (nothing that particular to Ivy

Re: Classloading issue

(). As far as I can tell, it is the class SshCache which fails to load, but I don't understand why. Nicolas Regards, Antoine On May 11, 2014, at 5:41 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Hi, I need some help to understand a bug around classloading (nothing

Re: [VOTE] Release AntUnit 1.3 based on RC1

+1 for me Nicolas Le 11 mai 2014 à 12:42, Stefan Bodewig bode...@apache.org a écrit : Hi all, delayed because I wanted to wait for mails to arrive again. Antunit 1.3 RC1 is available for review here: https://dist.apache.org/repos/dist/dev/ant/antlibs/antunit/ (svn revision 5298)

Ivy's ModuleDescriptor.getExtraInfo() is now deprecated

Hi, ModuleDescriptor.getExtraInfo() is deprecated but there is no indication in the doc about what should be used then. There is getExtraInfos(), but as I look to the code, there is no data transfer between both, if if there is data in one, I cannot get the data from the other one. And since

Classloading issue

Hi, I need some help to understand a bug around classloading (nothing that particular to Ivy). I was looking into IVY-1471 [1] and I don't understand why it is failing that way. In the classpath there are both Ivy and Jsch, but not the optional jar related to managing the ssh agent via jsch.

Re: Ivy's ModuleDescriptor.getExtraInfo() is now deprecated

a little bit. See my commit r1593855. As far as I can tell, tests pass well. Nicolas 2014-05-11 17:07 GMT+02:00 Nicolas Lalevée nicolas.lale...@hibnet.org: Hi, ModuleDescriptor.getExtraInfo() is deprecated but there is no indication in the doc about what should be used

Re: Classloading issue

(). As far as I can tell, it is the class SshCache which fails to load, but I don't understand why. Nicolas Regards, Antoine On May 11, 2014, at 5:41 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Hi, I need some help to understand a bug around classloading (nothing

Re: Ant-Matrix-Job

Yesterday I was wondering why it didn't appeared in my Personal View, but I didn't looked into it, merly though it was a UI bug. But it seems indeed gone… Nicolas Le 5 mai 2014 à 12:35, Jan Matèrne (jhm) apa...@materne.de a écrit : Does anyone know where (and why) the matrix build is gone?

Re: Hoped for advantages of migrating to git

-requests and other community work and at the same time have a git repo at Apache that syncs with this? André-John Sent from my phone. Envoyé depuis mon téléphone. On 30 Apr 2014, at 17:33, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Even if I share some of your enthusiasm

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

Le 30 avr. 2014 à 05:46, Antoine Levy Lambert anto...@gmx.de a écrit : 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

Re: Ivy slow resolution

Le 28 avr. 2014 à 16:36, Josh Suereth joshua.suer...@gmail.com a écrit : On Mon, Apr 28, 2014 at 10:13 AM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Le 28 avr. 2014 à 13:59, Josh Suereth joshua.suer...@gmail.com a écrit : On a whim, I implemented parallel download of artifacts

Re: Hoped for advantages of migrating to git

Even if I share some of your enthusiasm with git, don't forget that git at the ASF isn't like git in github. Pull request, code review and so on is not as integrated as in github. Nicolas Le 30 avr. 2014 à 16:01, Josh Suereth joshua.suer...@gmail.com a écrit : If you don't mind some

Re: [VOTE] migration to git

Le 28 avr. 2014 à 05:02, Antoine Levy Lambert anto...@gmx.de a écrit : 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

Re: [VOTE] migration to git

Le 28 avr. 2014 à 07:29, Jan Matèrne (jhm) apa...@materne.de a écrit : Let's vote about migrating to git : - Ant +1 - Ivy +0, because I dont work on that codebase and therefore dont want to influence these committers. - easyant +0, same as for Ivy - Ivyde +0, dito

Re: Ivy slow resolution

Le 28 avr. 2014 à 13:59, Josh Suereth joshua.suer...@gmail.com a écrit : On a whim, I implemented parallel download of artifacts by hooking the downloadArtifacts method of Resolve engine. While this can potentially speed up download performance, the resolution times (getDepedencies) still

Re: Migrating to Git

Le 20 avr. 2014 à 17:34, Antoine Levy Lambert anto...@gmx.de a écrit : Hi, like Michael one of my hopes in migrating to git is that it will allow non ASF committers to create their own forks of projects and be able to keep them (or not) up to date with the master branch. I have

Re: Migrating to Git

I like git, so I like the idea. But what about the publication of the doc on the website ? Today we rely on svn:externals for the doc of each release. How would it be managed if it's migrated to git ? And I have not searched in the ASF docs, but do you have any pointer on some guidelines

Re: [VOTE] Ivy 2.4.0-rc1 Release

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 à

Re: [VOTE] Release Compress Antlib 1.4 Based on RC1

+1 Nicolas Le 21 janv. 2014 à 13:33, Stefan Bodewig bode...@apache.org a écrit : Hi all, following the Commons Compress 1.7 release I'd like to release a new version of the Antlib as well. Most importantly this adds tasks and resources for Snappy and traditional Unix .Z compress. Both

Re: [VOTE] Ivy 2.4.0-rc1 Release

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

Re: [VOTE] Ivy 2.4.0-rc1 Release

Le 22 janv. 2014 à 06:27, Stefan Bodewig bode...@apache.org a écrit : On 2014-01-22, Nicolas Lalevée wrote: 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

Re: [VOTE] Ivy 2.4.0-rc1 Release

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

Re: IvyDE's workspace resolver taking directory structure into account

Le 15 janv. 2014 à 15:37, Andrew January andrewjanu...@gmail.com a écrit : Has there been any previous discussion around optionally taking directory structure into account in IvyDE's workspace resolver? Our project structure is set up as: project-1/ project-1 util-1

Re: Proposal: Make Xooki spoof TiddlyWiki to use TiddlyFox plugin?

Le 20 janv. 2014 à 17:23, Charles Duffy char...@dyfis.net a écrit : Howdy, all -- The release process for Ivy includes using Xooki to edit the documentation before publication. Unfortunately, the code Xooki uses for saving updated files, borrowed from an early TiddlyWiki release, is no

Re: Ivy Code formatting

Le 12 janv. 2014 à 21:43, Jan Matèrne (jhm) apa...@materne.de a écrit : Maybe we could store the configuration files in the repo. E.g. Apache Camel does that in a way for multiple IDEs: https://github.com/apache/camel/tree/master/buildingtools https://github.com/apache/camel/tree/master/etc

Re: Ivy release schedule

Le 4 janv. 2014 à 14:11, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 2 janv. 2014 à 17:34, Nicolas Lalevée nicolas.lale...@hibnet.org a écrit : Le 2 janv. 2014 à 17:10, Charles Duffy char...@dyfis.net a écrit : Absolutely, then. :) I was under the impression that only

Re: Cleanup callbacks in IvyContext?

between different process. For instance what happens if a process holding a lock is killed -9, or whatever which make the jvm not even able to trigger its shutdown hooks ? Nicolas On Sat, Jan 4, 2014 at 8:06 AM, Nicolas Lalevée nicolas.lale...@hibnet.orgwrote: Le 3 janv. 2014 à 22:28

Re: Cleanup callbacks in IvyContext?

Le 9 janv. 2014 à 19:43, Charles Duffy char...@dyfis.net a écrit : On Thu, Jan 9, 2014 at 12:17 PM, Nicolas Lalevée nicolas.lale...@hibnet.org wrote: Yep, a quite hard problem to resolve. At the ant task level I don't know how you could nail it without asking the end user to call some

<    1   2   3   4   5   6   7   >