Re: [VOTE] Retire the IvyDE Subproject

> Le 23 nov. 2023 à 08:19, Stefan Bodewig a écrit : > > 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

Re: [VOTE] Send IvyDE to the Apache Attic

> Le 19 nov. 2023 à 18:39, Stefan Bodewig a écrit : > > 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.

Re: Trying my hands at an ivy-updatesite (was Re: Future of Ivy and IvyDE)

> Le 19 nov. 2023 à 18:16, Stefan Bodewig a écrit : > > On 2023-09-05, Nicolas Lalevée wrote: > >> And we tried our best to be opened on how to build and release the >> plugin and the updatesite, it is documented [2]. On my machine which >> just have Ant an

Re: Future of Ivy and IvyDE

Hi there, I used to be involved, especially in IvyDE, and as many, my build tools and my IDE changed (for the IDE I am glad, not for the build tools…). So I had no particular interest of doing any maintenance, so much that lost track of the last releases of Ivy, where I could help. Many many

Re: Java 11 Compatibility Problem

To be complete on this subject, the pack200 algorithm has been implemented to be able to resolve artifacts in an Eclipse updatesite. I don’t know how nowadays artifacts are packaged on a « p2 repository », but some documentation still exists and doesn’t contain any warnings:

Re: ant git commit: Check spelling

I might have to contribute anything in my spare time. >>> >>> Committer rights is a privilege as well as a responsibility, but this >>> behaviour is nothing but an abuse of it and no different than being a >>> troll. >>> >>> -Jaikiran >>>

Re: ant git commit: Check spelling

I have been away from the project out of boredom. Still curious, I came to read some emails. It seems things didn’t changed much: yet another unreadable commit with a log which doesn’t indicate what it actually do. > Le 9 sept. 2018 à 09:09, gin...@apache.org a écrit : > > Repository: ant >

Re: Jenkins-Builds failing

> Le 24 juil. 2018 à 08:38, Jan Matèrne (jhm) a écrit : > > "Looks like someone called 'hibou' restricted the job to themselves. (See > screenshot attached to this ticket)" > > This was a "run as hibou" configuration. > > @Nicolas: What was the reason to add that? Is it required? For some

Re: Testing IvyDE

, which is way better integrated than IvyIDEA :) > Le 15 juil. 2018 à 21:06, Nicolas Lalevée a > écrit : > > I have fixed the build, now relying on more recent dependencies. The > updatesite built by Jenkins is now up to date. > > I have started to do some test, but t

Re: Testing IvyDE

running with Java 10. I’ll try to run it with a lower Java version and redo the tests. Nicolas > Le 4 juil. 2018 à 14:01, Jaikiran Pai a écrit : > > > On 01/07/18 6:35 PM, Nicolas Lalevée wrote: >> Le 28 juin 2018 à 08:41, Jaikiran Pai a écrit : >>> >>> O

Re: [VOTE] Release Ant 1.10.5 based on RC1

+1 > Le 10 juil. 2018 à 11:55, Stefan Bodewig a écrit : > > 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:

Re: [VOTE] Release Ant 1.9.13 based on RC1

+1 > Le 10 juil. 2018 à 11:56, Stefan Bodewig a écrit : > > 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

Re: ant git commit: Unbreak tests

I have re done the revert and merge locally, and compared the diff between my local banches and the remote one. I had only diffs due to my editor automatically removing trailing space on empty lines, and I had to figure out what the status of the apt tasks (and indeed it doesn’t need to be

Testing IvyDE

Le 28 juin 2018 à 08:41, Jaikiran Pai a écrit : > > > On 27/06/18 10:12 PM, Nicolas Lalevée wrote: >> Since there is a work around (hitting refresh after resolve) and it is an >> RC, we could ship it like that and fix it later. But due to the automatic >> update

Re: FileUtils.normalize/isLeadingPath have bitten me

At my first read of the code I wondered if paths ending with slash are properly handled in every case. After more careful reading, it is seems ok. Maybe some unit tests about it would be nice, just to be sure. Then, about tackling the bug, I am on the same page as you both. It looks good to

Re: [VOTE] Release 2.3.0-rc1 of Apache IvyDE

Everything looks good apart from the bug Ross reported which I have been able to reproduce. And it seems pretty consistent, not very random. And I see no error in Eclipse’s log. I have been able to reproduce it with the Eclipse version: Version: Neon.3 Release (4.6.3) Build id: 20170314-1500 I

Re: .git(modules|attributes|ignore) files in source dists?

> Le 19 juin 2018 à 16:42, Stefan Bodewig a écrit : > > Hi all > > when I set up the build for AntUnit I realized the source tarball didn't > contain the git config files that are part of the source repo and > changed the antlibs-common module to include them (they are part of > Ant's

Re: [VOTE] Apache IvyDE 2.3.0-rc1 release

First, thank you very much Jaikiran to make this release happen. So checksum, signatures, installation, build, resolve on projects went well. But I have found a regression: global preferences cannot be saved anymore. cf https://issues.apache.org/jira/browse/IVYDE-388

Re: [VOTE] Apache IvyDE 2.3.0-rc1 release

Just a quick comment on the mirror url not working. The page is telling "The requested file or directory is not on the mirrors. » And indeed, the artifacts are not published yet to the final location, the release is not accepted yet. Nicolas > Le 14 juin 2018 à 10:19, Gintautas Grigelionis

Re: Migrating Ivy and IvyDE site to asciidoc

> Le 7 mai 2018 à 08:24, Gintautas Grigelionis <g.grigelio...@gmail.com> a > écrit : > > 2018-04-23 15:25 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > >> One page I am worried about is the main page [2]. I am not sure there are >> some sane

Re: ant git commit: Inline buildfile names, make search easier

> Le 30 avr. 2018 à 11:58, Stefan Bodewig a écrit : > > On 2018-04-30, Jaikiran Pai wrote: > >> Changes like these are random personal preferences. > > Right. > >> The fact that these are being done even after the mail discussions we >> recently had, indicates that the

Re: Migrating Ivy and IvyDE site to asciidoc

ii is working. But if pandoc can do a better job, I am all ears. At least next time I’ll probably start with that. Nicolas > > On 23 April 2018 at 08:25, Nicolas Lalevée <nicolas.lale...@hibnet.org> > wrote: > >> Hi, >> >> I would like to go forward and migrate th

Re: ivy change

> Le 23 avr. 2018 à 14:21, Maarten Coene a > écrit : > > Hi, > I've committed a change to ModuleDescriptorMemoryCache.Where should I > document this change? Is it 'release-notes.adoc’? Yes, this is the place, it is the new doc/release-notes.html. Nicolas

[Announce] Release of Apache Ivy 2.5.0-rc1

gi> More information can be found on the Ivy website: http://ant.apache.org/ivy/ <http://ant.apache.org/ivy/> Regards, Nicolas Lalevée

Re: Ant JUnit tests

> Le 20 avr. 2018 à 18:48, Gintautas Grigelionis <g.grigelio...@gmail.com> a > écrit : > > 2018-04-20 15:26 GMT+00:00 Nicolas Lalevée <nicolas.lale...@hibnet.org > <mailto:nicolas.lale...@hibnet.org>>: > >>> Le 20 avr. 2018 à 07:09, Gintautas Gri

Re: Ant JUnit tests

> Le 20 avr. 2018 à 07:09, Gintautas Grigelionis a > écrit : > > I am refactoring Ant JUnit tests with a goal to make them more > "IDE-friendly". I found several tests that are implictly dependent on > ant.home property being set. In these cases, the test should be

Re: [RESULT][VOTE] Ivy 2.5.0-rc1 Release

Binaries have been pushed, but the process to update the site still reference the old way, with a documentation managed with xooki. So I’ll need some time to create a process for asciidoc based documentation and run it. Nicolas > Le 19 avr. 2018 à 20:13, Nicolas Lalevée <nicola

[RESULT][VOTE] Ivy 2.5.0-rc1 Release

The release got 4 binding +1. The release is thus accepted. I’ll get it published then. Nicolas > Le 12 avr. 2018 à 18:29, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit > : > > I have built a release candidate for Ivy 2.5.0-rc1. > > The git tag of this releas

Re: [VOTE] Ivy 2.5.0-rc1 Release

> Le 14 avr. 2018 à 19:02, Stefan Bodewig <bode...@apache.org> a écrit : > > On 2018-04-12, Nicolas Lalevée wrote: > >> 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/as

Re: Junit Task warning about multiple versions of Ant

I have been able to make unit test which reproduces the false warning. And I have fixed the way the classloader was created. Thanks for the insights. Nicolas > Le 13 avr. 2018 à 07:38, Stefan Bodewig <bode...@apache.org> a écrit : > > On 2018-04-12, Nicolas Lalevée wrote: >

Re: Junit Task warning about multiple versions of Ant

> Le 12 avr. 2018 à 16:57, Stefan Bodewig <bode...@apache.org> a écrit : > > On 2018-04-12, Nicolas Lalevée wrote: > >> The Junit task is printing a warning if it finds multiple versions of >> Ant in the classpath of the unit tests. It seems it doesn’t do &

Re: [VOTE] Ivy 2.5.0-rc1 Release

> Le 12 avr. 2018 à 18:29, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit > : > > 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

Junit Task warning about multiple versions of Ant

The Junit task is printing a warning if it finds multiple versions of Ant in the classpath of the unit tests. It seems it doesn’t do correctly the job if the ant runtime is explicitly removed from the classpath. Here the function which checks the classpath:

Re: Mass changes to various projects under Ant umbrella - should we be doing it?

> Le 9 avr. 2018 à 20:46, Gintautas Grigelionis <g.grigelio...@gmail.com> a > écrit : > > 2018-04-09 16:48 GMT+00:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > >> I have not been reading ant-dev lately, so I cannot comment much about the >> last p

Ivy release

The last thread about a release has been stuck in the discussion about which PR, patch or Jira needed to be tackled before releasing. I suggest we just move forward with the current master. I volunteer to build a 2.5.0-rc1. Nicolas

Re: Mass changes to various projects under Ant umbrella - should we be doing it?

Le 7 avr. 2018 à 14:13, Gintautas Grigelionis a écrit : > > I sense a personal attack using broad, generalised accusations :-) > Could we please stop the inflammatory comments and be more to the point? Please don’t. Nothing is personal here. Jaikiran used « we ». Even

Re: Ivy upcoming release - where we stand

> Le 19 sept. 2017 à 06:37, Gintautas Grigelionis a > écrit : > > I would like to propose upgrading BouncyCastle to at least 1.57 [1] to > include all security and PGP/GPG related fixes. +1 Nicolas > > Gintas > > [1] https://www.bouncycastle.org/releasenotes.html

Re: Ivy upcoming release - where we stand

> Le 11 sept. 2017 à 21:45, Gintautas Grigelionis a > écrit : > > I'd like to have https://issues.apache.org/jira/browse/IVY-1420 included in > the upcoming release. Every bug is important, but I think releasing often is more important. Apart from IVY-1485 which is

Re: Ivy upcoming release - where we stand

> Le 11 sept. 2017 à 17:05, Jaikiran Pai a écrit : > > It's been a while since we have decided to revive the Ivy project and work > towards a usable release. Since then, we have fixed a good number of bugs, > added some enhancements and updated the documentation (we

Re: Ivy - Latest snapshots will now be regularly available in Apache Maven Snapshot repository

Awesome! > Le 31 août 2017 à 10:43, Jaikiran Pai a écrit : > > Starting today, we now have an Ivy Jenkins job[1] which will publish our Ivy > snapshot artifactto Apache Maven Snapshots repository[2]. This job has been > configured to run after a successfulcompletion

Re: [1/6] ant-ivy git commit: Documentation review (partly inspired by IVY-1089) [Forced Update!]

> Le 6 sept. 2017 à 08:27, Jaikiran Pai a écrit : > > IMO, we should avoid force updates to upstream repos, since it rewrites > history of the repo. Typically a force update is a sign that the local state > of a repo is not in sync with whatever is latest upstream

Re: IVY-450

Hi, Sorry for the delay, I have been less attentive to ant stuff lately. > Le 4 sept. 2017 à 10:51, Gintautas Grigelionis a > écrit : > > Changing ids is not supposed to change navigation -- if it does, then we > have a problem :-) > I was only wondering if anybody

Re: Ivy - No more support for commons-httpclient 2.x in runtime classpath?

> Le 24 juil. 2017 à 08:19, Jaikiran Pai a écrit : > > That's a a big enough reason to move to HttpComponents Client 4.x version! > I'll have that done in this release of Ivy then. +1 Nicolas > > -Jaikiran > > > On 24/07/17 11:43 AM, Stefan Bodewig wrote: >> On

[RESULT] [VOTE] IvyDE requirements

11 juil. 2017 à 23:07, Nicolas Lalevée <nicolas.lale...@hibnet.org> a > écrit : > > 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

Re: ant-ivy git commit: An asciidoctor macro to create links to Jira

I look deeper into asciidoctor and asciidoctor-ant, and I have managed to create a simple macro. It creates links to jira just by declaring the name of the issue. The Ant tasks only supports macro implemented in Java, not Ruby, even if it seems that asciidoctor itself might support them in

[VOTE] IvyDE requirements

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

Re: Build failed in Jenkins: IvyDE #320

Indeed, with the proper urls it builds, thank both of you. Nicolas > Le 11 juil. 2017 à 07:29, Jaikiran Pai <jai.forums2...@gmail.com> a écrit : > > > On 11/07/17 3:26 AM, Nicolas Lalevée wrote: >> I don’t understand what is going on. The files are there and then th

Re: Build failed in Jenkins: IvyDE #320

I don’t understand what is going on. The files are there and then they disappear… I have been able to download this file, and now it is gone. It happens several times for different files locally… I though I had finally have found a stable set of zip to download, but it seems actually not...

Re: [2/2] ant-ivy git commit: Generate automatically the copyright year in the doc

Templates updated. I used the same range as the one in the NOTICE file. Nicolas > Le 6 juil. 2017 à 12:38, Gintautas Grigelionis a > écrit : > > I put 2007 in javadoc :-) > > Gintas > > 2017-07-06 12:01 GMT+02:00 Matèrne, Jan (RZF, Ref 410) < >

Re: ant-ivy git commit: avoid generating the reports in the folder where the html of the documentation is generated

I have updated the config of the Jenkins jobs accordingly. Nicolas > Le 4 juil. 2017 à 23:59, hi...@apache.org a écrit : > > Repository: ant-ivy > Updated Branches: > refs/heads/master cd8f81d0a -> eeb79e100 > > > avoid generating the reports in the folder where the html of the >

Re: Ivy - we have now moved to asciidoc for docs

> > I’m now pick up the “Tutorials” section. > > I’ll take care of the last pages, "Reference/Introduction" and "Developper doc". Nicolas - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands,

Re: Ivy - we have now moved to asciidoc for docs

> Le 2 juil. 2017 à 07:23, Gintautas Grigelionis <g.grigelio...@gmail.com> a > écrit : > > 2017-07-01 18:56 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org > <mailto:nicolas.lale...@hibnet.org>>: > >> >>> Le 1 juil. 2017 à 15

Re: Jenkins build is back to normal : IvyDE #319

Finally. But the build of resolve visualizer has been deactivated, the Zest plugins are not properly resolved by the build. Nicolas > Le 2 juil. 2017 à 12:01, Apache Jenkins Server a > écrit : > > See

Re: Ivy - we have now moved to asciidoc for docs

> Le 1 juil. 2017 à 15:27, Gintautas Grigelionis a > écrit : > >> Probably a thing to improve are all the « since 2.x » annotations. Maybe > we can have a macro for that, which will render everywhere the same, and > which will be placed everywhere the same. Now

Re: Ivy - we have now moved to asciidoc for docs

> Le 1 juil. 2017 à 15:31, Jaikiran Pai a écrit : > > > On 29-Jun-2017, at 11:29 AM, Jaikiran Pai wrote: > > >> I’m picking up “OSGi” section next. > > I have completed and pushed the migration of “OSGi” and “Using standalone” > sections

Re: IVYDE-382 proposed patch

we can support you? > > Should we extend the official IvyDE doc by providing a more > sophisticated description about the new feature (like you suggested in > the previous mail)? > > Many greetings from Austria, > > Alexander > > Am 14.06.2017 23:56, schrieb

Re: Ivy - we have now moved to asciidoc for docs

://ant.apache.org/ivy/ >> history/master/terminology.html) >> >> Gintas >> >> 2017-06-30 18:18 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: >> >>> I have seen that you have qualified the source blocks, telling it is xml. >>> T

Re: Ivy - we have now moved to asciidoc for docs

black bold a little too much. Nicolas > Le 29 juin 2017 à 15:16, Jaikiran Pai <jai.forums2...@gmail.com> a écrit : > > > On 29-Jun-2017, at 3:58 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> > wrote: > >> >>> Le 29 juin 2017 à 07:59, Ja

Re: Ivy - we have now moved to asciidoc for docs

fulBuild/artifact/build/doc/settings.html > [2] See “Hierarchical Index” section at > https://builds.apache.org/view/A/view/Ant/job/Ivy-NightlyDistribution/lastSuccessfulBuild/artifact/build/doc/ivyfile.html > > -Jaikiran > > On 24-Jun-2017, at 7:18 PM, Nicolas Lalevée <nicol

Re: Jenkins Jobs of Ivy/IvyDE

> Le 29 juin 2017 à 07:48, Jaikiran Pai <jai.forums2...@gmail.com> a écrit : > > > On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> > wrote: > >> I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe >&g

Re: Jenkins Jobs of Ivy/IvyDE

> Dropins (or "drops" as they're called in the distributions) is what IvyDE > builds were based on all the time. I am still confounded why it worked > before and stopped working now. Yet, reading the documentation I became > convinced that the dropins must be unpacked in another location. So I

Re: Jenkins Jobs of Ivy/IvyDE

locally when dropins are unpacked in "dropins" directory, see Eclipse > documentation [1]. That's what the patch is for. I don’t have much experience with using dropins, so if you think this will help make the build more stable, you’re welcomed to open a PR. Nicolas > > Gintas &g

Re: [1/5] ant-ivy git commit: set copyright to 2017

> Le 26 juin 2017 à 08:15, Matèrne, Jan (RZF, Ref 410) > a écrit : > > Would it be better to insert the actual year to the generation process? It can certainly be done. There is some ruby code involved, so I guess this is doable. > If I remember right Stefan had

Re: Jenkins Jobs of Ivy/IvyDE

> I am sorry, my memory of what I was doing back in December is incorrect. > I guess I somehow updated > configuration/org.eclipse.equinox.simpleconfigurator/bundles.info or did > something else. > Luckily, there's a simpler way, the dropins should go into their own > special directory, which

Re: Jenkins Jobs of Ivy/IvyDE

> Le 25 juin 2017 à 16:57, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit > : > > Hi, > > I worked on the Jenkins jobs to make them work. > > There was some issues with job dependencies. Following the instructions there > [1] worked. Then didn’t

Re: Jenkins Jobs of Ivy/IvyDE

ents should go into "features" and "plugins" directories of > PDE). I have done that already. I even checked that the placed in the plugins directory have the proper OSGi metadata. It is reproductible locally if you wish to debug and suggest a fix. Nicolas > > Gintas >

Jenkins Jobs of Ivy/IvyDE

Hi, I worked on the Jenkins jobs to make them work. There was some issues with job dependencies. Following the instructions there [1] worked. I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe now the nightly is redundant. I made the Ivy-checks build work, some https

Re: Ivy - we have now moved to asciidoc for docs

> >> >> And just an idea: since there are a lot of pages, maybe we could organize a >> review at many, without useless double checks. I see 4 big parts in the doc: >> the ant tasks, the pages related to the ivy file, the pages related to the >> ivysettings, and the other pages. If 4

Re: Ivy jobs on Teamcity need reconfiguring

> Le 19 juin 2017 à 13:02, Stefan Bodewig a écrit : > > On 2017-06-19, Jaikiran Pai wrote: > >> I was reading up some docs and happened to find this page >> http://ant.apache.org/nightlies.html which lists the Ant/Ivy >> jobs. Turns out we also have Teamcity builds for Ivy

Re: Ivy - we have now moved to asciidoc for docs

> Le 19 juin 2017 à 08:30, Jan Matèrne (jhm) a écrit : > > Doc's mentioning 'how to document' must be updated. > I found http://ant.apache.org/ivy/write-doc.html Some more? This is the only page which explain xooki I know. Nicolas > > Jan > >> -Ursprüngliche

Re: Ivy - we have now moved to asciidoc for docs

> Le 19 juin 2017 à 04:52, Jaikiran Pai a écrit : > > The documentation for ant-ivy project has now been migrated to asciidoc. The > migration used a tool developed by Nicolas to migrate the xooki backed HTML > docs to asciidoc. This tool auto-generated the asciidoc

Re: Process for handling GitHub PRs and closing them

> Le 19 juin 2017 à 05:14, Jaikiran Pai a écrit : > > We have (read only) github repos which back our main ASF git repos (consider > the github ant-ivy repo which is a read-only mirror of ASF git repo). Users > submit pull requests to our github repos and the process

Re: new committer: Jaikiran Pai

Welcome Jaikiran! Thank you for your great patches. You can now apply them yourself :) Nicolas > Le 16 juin 2017 à 17:51, Jan Matèrne (jhm) a écrit : > > The Project Management Committee (PMC) for Apache Ant has invited Jaikiran > Pai to become a committer and we are

Re: IvyDE JIRA issues and changes for proposed release?

> Le 14 juin 2017 à 05:22, J Pai a écrit : > > There’s been some good progress on reviving the Ivy project (thanks Nicolas > and Jan for helping out with the reviews and merging PRs) and we seem to be > moving towards a state where the release is a possibility. The

Re: IVYDE-382 proposed patch

Hi, For some reason git apply was refusing to process the patch and was just returning an error: corrupt patch at line 1964 So I played with git commands and work with the sources available on github. I have create a branch on the ASF repo, ivyDECredentials, which has one commit which squash

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

LGTM +1 for this release Nicolas > Le 8 juin 2017 à 13:45, Stefan Bodewig a écrit : > > Hi all > > third attempt :-) > > I've created a new release candidate for Compress Antlib 1.5, this time > the source distribution should contain everything needed to build. > > git

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

-1 for me. The source didn’t build since it was missing two files, the build.properties which setup the build to use Java 7, and the ivy.xml which declares the dependencies the build is relying on. I pushed a fix to common. This is the first time use use git submodules, so I hope I have done

Re: IVY-1475 - cachefileset task and its inherent limitation

of the documentation *and* enhance > the code of this task to explicit fail with a proper error when it can’t > determine a common base directory. > Sounds good to me. Nicolas > -Jaikiran > On 02-Jun-2017, at 2:55 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> > wrote:

Re: IVY-1475 - cachefileset task and its inherent limitation

> Le 2 juin 2017 à 08:22, Jan Matèrne (jhm) a écrit : > > From a naive user point of view, it doesnt matter (to me) if I use > ivy:chachefileset or ivy:resources. > I want to specify the dependency and have a 'thing' which contains all > required jars, so I could > use

Re: Release notes for IVY-1528

done. Thanks Nicolas > Le 1 juin 2017 à 13:46, J Pai a écrit : > > The PR for this issue https://issues.apache.org/jira/browse/IVY-1528 was > merged a few days back, but I think we forgot to resolve the JIRA and include > this in the release notes. Can someone with

Re: Ivy documentation with asciidoc

ion of the logo we have is in the svn. Nicolas > > Gintas > > 2017-05-31 18:20 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org > <mailto:nicolas.lale...@hibnet.org>>: > >> >>> Le 31 mai 2017 à 17:53, J Pai <jai.forums2...@gmail.com >>>

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 17:53, J Pai <jai.forums2...@gmail.com> a écrit : > > > On 31-May-2017, at 9:02 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org > <mailto:nicolas.lale...@hibnet.org>> wrote: > > >> Le 31 mai 2017 à 15:34, J Pai <jai.forums2

Re: Ivy documentation with asciidoc

this > tool works and the fact that it isn’t breaking anything, I don’t think we > will have to maintain a separate branch to deal with this migration. > > Any thoughts? > > -Jaikiran > > On 25-May-2017, at 7:55 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> >

Re: Ivy documentation with asciidoc

e so we can compare the final result while fixing manually the asciidoc sources. Then about when to do it: I have no objection to when, as long as people are motivated to do it. Nicolas > Any thoughts? > > -Jaikiran > > On 25-May-2017, at 7:55 PM, Nicolas Lalevée &l

Re: Replace emma with jacoco?

FYI, here are the post build actions available on the Jenkins at the ASF: https://www.dropbox.com/s/zwpersrv4ydzdp5/Capture%20d%27%C3%A9cran%202017-05-29%2017.36.49.png?dl=0 It would be nice if

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

+1 Nicolas > Le 29 mai 2017 à 13:15, Jan Matèrne a écrit : > > Ivy uses Java7 from Ivy-2.5.x, so let us increase the minimum Java version > for IvyDE from 1.4 [2] to Java7, too. > > According to Eclipse Wiki [2] this will result in requiring Eclipse 4.4 > (from 2014) or

Re: PR-33: problems

> Le 29 mai 2017 à 11:46, Jan Matèrne (jhm) a écrit : > > Sounds like I would do ;) > I'll merge the PR locally and insert the delegates. > > Open is > "src/java/org/apache/ivy/osgi/util/Version.java: > the constructor removes the (IMO unneccessary) ParseException. > But

Re: PR-33: problems

> Le 29 mai 2017 à 11:35, Jan Matèrne (jhm) a écrit : > > Thanks, but I already have it done ;) > > But one point is open: > src/java/org/apache/ivy/osgi/util/Version.java: the constructor removes the > (IMO unneccessary) ParseException. But because it is a checked

Re: Ivy website - fixing a Quickstart documentation live

to issues or if any changes are necessary in this patch. >>> >>> As for the other two issues noted in that JIRA, I’m planning to remove >>> references to the non-existent .css and .png files and submit that as a >>> separate patch. >>> >>> -J

Re: build IvyDE

It has been ages since I have done a build of Eclipse, but like Gintas wrote, there is something wrong with your Eclipse install you are building against, it is missing zest. I don’t know if you have seen but there is a piece of documentation about building IvyDE there:

Re: IVY-1485, resolve report and resolved versions

s here if you were planning to work on > this. If not, I’ll gladly try and come up with the suggested fix. Please, be my guest. Nicolas > > -Jaikiran > > > On 26-May-2017, at 2:20 PM, Nicolas Lalevée <nicolas.lale...@hibnet.org> > wrote: > > After some diggin

IVY-1485, resolve report and resolved versions

s.java#L99> [5] https://issues.apache.org/jira/browse/IVY-1485 <https://issues.apache.org/jira/browse/IVY-1485> > Le 25 mai 2017 à 12:11, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit : > > Thank you very much Jaikiran for your detailed explanation. > > I

Re: Ivy documentation with asciidoc

f all the pages of the documentation. But we can imagine that we uncouple the documentation, like it is being done for the old versions of the documentation, in the « history » section, by just having a link. So yes we could some manual copy and publish to svnpubsub on release. Nicolas > >

Ivy documentation with asciidoc

I have updated the branch xooki2asciidoc. The merge generated 50 emails, which I still find weird, I would expect just one mail about the commit of the merge. I can see the current status of the transformation of the xooki source into asciidoc source and then the generated html from that here:

Re: Ivy website - fixing a Quickstart documentation live

The entire Ant site is in svn: https://svn.apache.org/repos/asf/ant/site There is a Readme.txt explaining a little bit stuff, but seems outdated since the migration to git. For Ivy and IvyDE, part of the site is built from the source for the projects. It used to be managed via svn:externals.

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?

solution > report XML instead be considered the single source of truth. Hence that > question [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-iv

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

Re: Ivy - Goals for the upcoming release?

t easy to understand. Any review will be welcomed. Nicolas > Le 21 mai 2017 à 18:46, Nicolas Lalevée <nicolas.lale...@hibnet.org> a écrit : > > >> Le 21 mai 2017 à 16:28, J Pai <jai.forums2...@gmail.com> a écrit : >> >> The past few days I’ve sent

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,

  1   2   3   4   5   6   7   >