Re: Versioning scheme in Ivy

Almost everything in Ivy is configurable, like the version matchers [1]. Ivy provide some sane default, but if some has a weird use case, he will be able to tweak thing to make it work. Nicolas [1] https://ant.apache.org/ivy/history/latest-milestone/settings/version-matchers.html

Re: Ivy - Goals for the upcoming release?

n [2] in the dev list. I can’t really think of a solution/fix for this > issue, without reading more of the current Ivy code to understand what role > these files play. > > [1] > https://github.com/jaikiran/ant-ivy/commit/529a3fa05ed5dd115bdf8046d0cf0ffe034905e0#diff-6ed8218b6bb9

Re: Ivy - Buildjobs/PreCommit

> Le 24 mai 2017 à 13:13, Jan Matèrne (jhm) a écrit : > > Not sure about this expertise because my sources were old, but I think the > github-plugin does not support matrix jobs. > https://github.com/KostyaSha/github-integration-plugin/issues/53 > > Maybe a newer plugin version would do, but I

Re: Ivy - Goals for the upcoming release?

asy to understand. Any review will be welcomed. Nicolas > Le 21 mai 2017 à 18:46, Nicolas Lalevée a écrit : > > >> 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

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, that's a Java 5 feature!) wo

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 this JIRA filter [1] to na

Re: Ivy - Buildjobs/PreCommit

> Le 20 mai 2017 à 11:18, Nicolas Lalevée a écrit : > > >> Le 20 mai 2017 à 04:45, J Pai a écrit : >> >> This pre-commit job is now almost functional. It gets triggered whenever >> there’s a PR and runs the build and tests and reports back if there are any

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 pr

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 fully familiar with the vo

Re: Ivy - Buildjobs/PreCommit

tps://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 > > -Jaikiran > > On 18-May-2

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). > Decisions whether to incr

Re: Ivy - Buildjobs/PreCommit

targets that get run via this pre commit > job to be just: > > ant clean test > > and as a start, see how it goes with the PR integration process? > > [1] https://github.com/apache/ant-ivy/pull/16 > <https://github.com/apache/ant-ivy/pull/16> > > -Jaikiran

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, SB

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. Nicola

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 style

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 a way to check if I have al

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. > > The last 'real'

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 is being correctly build

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

>> >> >> Jonathan Oulds >> Snr. Software Engineer >> McAfee >> >> -Original Message- >> From: Stefan Bodewig [mailto:bode...@apache.org] >> Sent: Wednesday, December 7, 2016 10:56 AM >> To: dev@ant.apache.org >> Subject: Re: Iv

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 case. Actually there is no

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 nothing else changes

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 real activity in ther

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 incubator. > > The last

Re: DISCUSS How to retire a subproject/component

> Le 30 nov. 2016 à 15:54, Jan Matèrne (jhm) a écrit : > > I am updating the homepage. > Before committing and make that "official" please comment: > > http://materne.de/ant/processes.html Since some of the subtitles are common between « Retire » and « Re

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 processes/todo-lists. > >

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 artifacts: > > https:

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, > particularly for the Ivy Sub

Re: Roadmap, goals, future of Ivy?

Le 23 août 2015 à 20:10, Stephen Haberman 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. > > But nothing has happe

Re: Looking to contribute

> Le 16 juil. 2015 à 14:14, Jaikiran Pai 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 found this one > h

Re: [VOTE] Release Ant 1.9.6 based on RC1

LGTM. +1 for the release Nicolas > Le 29 juin 2015 à 11:32, Stefan Bodewig 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

Re: Bug 56721 - "back quote" and "quote"

> Le 10 juin 2015 à 08:21, Jan Matèrne 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 a

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 a écrit : > > On 2015-06-09, wrote:

Re: [VOTE] Release Ant 1.9.5 based on RC1

+1 Nicolas > Le 31 mai 2015 à 16:46, Stefan Bodewig 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 > Maven ar

Re: stuck with site generation issue for ivy

Hi Antoine, Sorry I forgot to respond to your mail. The latest milestone folder used to be a external svn dependency. Since we’re using git now, I had to work around it. As my previous email about that, you need to checkout it manually, with the help of an Ant target. > svn:external have disap

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

> Le 9 avr. 2015 à 16:51, Maarten Coene 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 uploads you'll have to add http

Re: xooki to asciidoc, a proof of concept

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 a écrit > : > >> >> Le 30 déc. 2014 à 17:16, Jean-Louis Boudart > <mailto:jeanlouis.boud...@gmai

Re: [Ivy] A workspace resolver for Ant

space resolver will figure out which project is needed to build the current one, and thus trigger a build of the selected dependent project. Nicolas > > Best regards Nicolas, great to see all the work you do for ivy. > > Antoine > > > > On Jan 25, 2015, at 4:5

Re: issue with IBiblioResolverTest.testErrorReport

> Le 26 janv. 2015 à 00:56, Antoine Levy Lambert 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 > DefaultDependencyD

[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 unr

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

> Le 21 janv. 2015 à 12:10, Stefan Bodewig 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 >> Java

Re: Git workflow

> Le 11 janv. 2015 à 18:46, Stefan Bodewig 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 c

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 a > écrit : > > >> Le 7 janv. 2015 à 05:57, Stefan Bodewig a écrit : >> >>

Re: Git workflow

> Le 7 janv. 2015 à 05:57, Stefan Bodewig 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

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 o

Re: xooki to asciidoc, a proof of concept

we won’t need xooki anymore. 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 : > >> Hi, >> >> I like xooki because it manages

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 jrunscr

[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

[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 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

Re: [VOTE] Ivy 2.4.0 Release - take 2

now we have one -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 a écrit > : > > >> Le 17 déc. 2014 à 04:09,

Re: [VOTE] Ivy 2.4.0 Release - take 2

> JFrog Developer Advocate > www.jfrog.com > +972544954353 > @jbaruch <https://twitter.com/jbaruch/> > http://linkd.in/jbaruch > > On Wed, Dec 17, 2014 at 5:25 AM, Nicolas Lalevée > wrote: >> >> >>> Le 17 déc. 2014 à 04:09, Antoine Levy Lambert

Re: Develop custom Ivy parser

> Le 17 déc. 2014 à 22:25, Martin Flores 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 to a sample

Re: [VOTE] Ivy 2.4.0 Release - take 2

> Le 17 déc. 2014 à 04:09, Antoine Levy Lambert 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 expanded

[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

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 a écrit > : > > Note that the style files are also useful to edit the doc withi

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 cont

Re: [CANCELED][VOTE] Release Ivy 2.4.0

inkd.in/jbaruch > > On Tue, Dec 2, 2014 at 6:19 PM, Nicolas Lalevée > 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. J

[CANCELED][VOTE] Release Ivy 2.4.0

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. Nicolas > Le 9 nov. 2014 à 17:56, Nicolas Lalevée

[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 fo

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 a écrit : > So I have updated the release process to use git. I also made s

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 som

Re: Updating Ivy's trunk doc in the site

on servers. > > Regards, > > Antoine > On Oct 27, 2014, at 7:10 PM, Nicolas Lalevée > wrote: > >> Le 26 oct. 2014 à 20:16, Jean-Louis Boudart a >> écrit : >> >>> Would it be possible to have everything on git ? >>> Looks like there is a git

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 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 Lalevée

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 j

Re: Commit Candidates for Ivy 2.4.x

to ivy 2.3 for sbt > On Oct 26, 2014 3:30 PM, "Jean-Louis Boudart" > wrote: > >> 2014-10-26 20:19 GMT+01:00 Nicolas Lalevée : >> >>> >>> >>>>> - IVY-1465 [1] doesn’t seem to be fully finished. One part is in the >&g

Re: Updating Ivy's trunk doc in the site

pport-for-subversion-clients/ > > > > 2014-10-26 19:49 GMT+01:00 Nicolas Lalevée : > >> 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.o

Re: Commit Candidates for Ivy 2.4.x

Le 26 oct. 2014 à 20:19, Nicolas Lalevée a écrit : > > Le 26 oct. 2014 à 19:58, Jean-Louis Boudart a > écrit : > >> Hi Nicolas, >> >> My answers bellow. >> >> 2014-10-26 19:18 GMT+01:00 Nicolas Lalevée : >> >>> I have checked th

Re: Commit Candidates for Ivy 2.4.x

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

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 doc

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]

Re: Release of Ivy 2.4.0

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 >>> >>> >

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

Re: IvyDE-updatesite - fix for jenkins

Le 27 juin 2014 à 22:29, Jan Matèrne 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 tried to appli

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

unk > ans current branch ? > Le 11 juin 2014 10:00, "Nicolas Lalevée" a > écrit : > >> >> Le 10 juin 2014 à 21:29, Jan Matèrne (jhm) a écrit : >> >>> I wouldnt count myself to the Ivy team, but I prefer changing to >> trunk/branches stru

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

Le 10 juin 2014 à 21:29, Jan Matèrne (jhm) 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 Nachricht

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) a écrit : > After ivyde-updatesite (svn) this is the 2nd repo where I can't commit/push > > https://git-wip-us.apache.org/repos/asf/easyant

Re: IvyDE compiler error @ Jenkins

Le 5 juin 2014 à 07:12, Jan Matèrne (jhm) 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. > ivyde.eclipse/src/java/org/apache/ivyde/int

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 a écrit : > Hi, > > ModuleDescriptor.getExtraInfo() is deprecated but there is no indication in > the do

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 th

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 a écrit : > Hi, > > I need some help to understand a bug around classloading (nothing that > particular to Ivy). &

Re: Classloading issue

e()); >>> >>> getSession is a method which calls attemptAgentUse. >> >> It is only called is attemptAgentUse is true. In our case it is false. >> >>> Does this explain why an attempt to load AgentProxyException happens at >>> that

Re: Classloading issue

a debugger, and the class loading exception is raised on the call of SshCache.getInstance(). 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 >

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

ast work 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 : > >> Hi, >> >> ModuleDescriptor.getExtraInfo() is deprecated but there is no indication >> in the doc about wha

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. A

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 th

Re: [VOTE] Release AntUnit 1.3 based on RC1

+1 for me Nicolas Le 11 mai 2014 à 12:42, Stefan Bodewig 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) > > Maven

Re: Hoped for advantages of migrating to git

uly great moving to git. >>> >>> >>> On Wed, Apr 30, 2014 at 6:33 PM, Andre-John Mas >> wrote: >>> >>>> Could we conceive of having a GitHub project, that serves as a point for >>>> pull-requests and other community work and at the same ti

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) a écrit : > Does anyone know where (and why) the matrix build is gone? > > https://buil

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

Le 30 avr. 2014 à 05:46, Antoine Levy Lambert 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 tests in

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 a écrit : > If you don't mind some recommendations from the peanut

Re: Ivy slow resolution

Le 28 avr. 2014 à 16:36, Josh Suereth 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 a écrit : >> >>> On a whim, I implemented par

Re: Ivy slow resolution

Le 28 avr. 2014 à 13:59, Josh Suereth 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 dominates (of > course

Re: [VOTE] migration to git

Le 28 avr. 2014 à 07:29, Jan Matèrne (jhm) 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: [VOTE] migration to git

Le 28 avr. 2014 à 05:02, Antoine Levy Lambert 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 becaus

Re: Migrating to Git

Le 20 avr. 2014 à 17:34, Antoine Levy Lambert 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 also done

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 about

Re: [VOTE] Ivy 2.4.0-rc1 Release

ed 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

Re: [VOTE] Ivy 2.4.0-rc1 Release

Le 22 janv. 2014 à 00:52, Nicolas Lalevée 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 th

<    1   2   3   4   5   6   7   >