Re: Ant Contrib

I started a new organisation on GitHub, antlibs. Currently antlibs contain 2 repos, ant-contrib and ant-http. Please let me know if you would like to join. Currently, I would appreciate some help with IfTaskTest in ant-contrib which passes with Ant + Junit but fails with Maven + Surefire.

Re: Ivy logo as SVG

Here come the links: edge analysis: https://drive.google.com/open?id=0B2mVPD7ZO6sdN0k5MmdSU0JIeDQ new logo: https://drive.google.com/open?id=0B2mVPD7ZO6sdcDFkX1lQdHJWZVRwUUdSSXI1VnF3bk5xTFhF Gintas 2017-06-08 15:21 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > I wa

Re: Ivy logo as SVG

> Gintas > > P.S. Could we please finish the PR #36? I'll look into adding Clover > separately. > > 2017-06-02 9:10 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > >> On 2017-06-02, Gintautas Grigelionis wrote: >> >> > Could we please

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

+1 FWIW Gintas 2017-06-06 9:13 GMT+02:00 Maarten Coene : > +1 > Maarten > > > Van: Stefan Bodewig > Aan: dev@ant.apache.org > Verzonden: dinsdag 6 juni 6:26 2017 > Onderwerp: Re: [VOTE] Release Compress Antlib 1.5 based on RC2 > >

Re: Ant Contrib

Thanks for the comment. IMHO, if there ever would be an Ant Contrib 2.0, it should contain at least antcallback antfetch for if (I see use cases where xmlns:if is more cumbersome :-) outofdate switch trycatch/throw switch stopwatch (for those who like adding timers in the script rather than using

Re: Ant Contrib

that was proposed 12 years ago :-) Gintas 2017-06-05 6:16 GMT+02:00 Paul King <pa...@asert.com.au>: > On Sun, Jun 4, 2017 at 7:47 PM, Gintautas Grigelionis < > g.grigelio...@gmail.com> wrote: > > > [...] > > P.S. While we're at it, in the light of the latest ASM debacle

Re: Ant Contrib

a good enough replacement for var?), that's why I asked for your opinions. The pruned version should be released as 2.0 Gintas 2017-06-05 4:25 GMT+02:00 Earl Hood <earlh...@gmail.com>: > On Sun, Jun 4, 2017 at 4:47 AM, Gintautas Grigelionis wrote: > > > I noticed that I

Ant Contrib

I noticed that Ivy has Ant Contrib as a dependency. It's a project that has been asleep for a decade, and it shows. So I decided to revive it, and the result is here: https://github.com/twogee/ant-contrib The question is, of course, is this sufficient for a 1.1 release? The next step would be a

Re: PR-41: use of fonts

ontain the original font, but can be converted to vector outlines, rasterized, or subsetted and embedded in an electronic document like a PDF or eBook. I guess we're in compliance or do we need additional legal advice? Gintas 2017-06-03 14:08 GMT+02:00 Gintautas Grigelionis <g.grigelio...@

Re: PR-41: use of fonts

This is produced by yEd and refers to the fact that it wants Helvetica to be used there. However, there are no font outlines included and the renderer is free to substitute the font if it's not available. I can remove the comments if they're confusing. BTW Linotype AG was purchased by Monotype

Re: AW: Ivy logo as SVG

atèrne (jhm)" <apa...@materne.de>: > The attachment didnt come thru. > > I think EZMLM is configured not to send attachments ;) > > > > Please open a JIRA ticket or a PR and we can discuss. > > > > > > Jan > > > > Von: Gintautas Grigelio

Re: Ivy logo as SVG

We may not be artists, but we can be aesthetes :-) Please see an attached mockup of an Ivy report with proposed SVG icons and let me know what you think. Gintas 2017-06-01 16:19 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > Logo is important, especially when it ends up

Re: Ivy documentation with asciidoc

2017-06-01 15:43 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-06-01, Gintautas Grigelionis wrote: > > > 2017-05-31 23:00 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > > > >>> Le 31 mai 2017 à 19:47, Gintautas Grigelionis

Re: Ivy logo as SVG

Logo is important, especially when it ends up in every Ivy report. Still, if there are no other way, I'm willing to give it a try :-) Gintas 2017-06-01 15:44 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-06-01, Gintautas Grigelionis wrote: > > > I noticed that

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

I believe this comment <https://github.com/ceylon/ceylon-herd/issues/262#issuecomment-194440002> provides a pretty good argument why coordinates must be consistent. Gintas 2017-06-01 14:57 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > It's not a "should&qu

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

It's not a "should", it's a MUST. Ideally, pom.xml should be generated from ivy.xml or the other way around; at the very least, maven-ant-tasks should check the consistence between them, like this The pom version is ${ivy.pom.version}

Ivy logo as SVG

I noticed that ASF apparently has converted a bunch of project logos to SVG. In particular, Ant has an SVG logo. Is there an official channel at ASF (like, a branding office?) that we could use to get Ivy logo vectorized? Gintas

Re: Ivy documentation with asciidoc

2017-05-31 23:00 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > > > Le 31 mai 2017 à 19:47, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > Also, external links must be pruned and/or directed to Internet Archive > :-( > > Th

Re: Ivy documentation with asciidoc

I looked at the documentation: both http://ant.apache.org/ivy/history/trunk/tutorial/start.html and https://ant.apache.org/ivy/history/latest-milestone/tutorial/start.html have black rectangles. Also, external links must be pruned and/or directed to Internet Archive :-( The tutorial of yEd must

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

Then option 2 is a given: errare humanum est sed in errare perseverare diabolicum :-) Gintas 2017-05-31 18:11 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-05-31, Gintautas Grigelionis wrote: > > > can't you just publish new ivy.xml? > > we can't overwrite

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

Hi, can't you just publish new ivy.xml? Gintas 2017-05-31 17:34 GMT+02:00 Stefan Bodewig : > Hi all > > this is an excerpt from the cancelled vote thread for the compress > antlib. > > 2017-05-31 16:40 GMT+02:00 Stefan Bodewig : > > > I've just realized

Re: Ivy documentation with asciidoc

Great news! How about SVG for images? I thought about tracing the Ivy logo; also, dependency graphs made with yEd can be saved in SVG. What about using fonts (eg genericons) instead of images for arrows etc? Gintas 2017-05-31 15:20 GMT+02:00 J Pai : > I had some time

Re: Problems Releaseing Antlibs

Use different pattern [orgPath] rather than [organisation] Gintas http://ant.apache.org/ivy/history/latest-milestone/concept.html 2017-05-31 11:36 GMT+02:00 Stefan Bodewig : > On 2017-05-31, Stefan Bodewig wrote: > > > I'll fix common first (and update Ivy as I go, then fix

Re: Replace emma with jacoco?

...@hotmail.com> wrote: > > > >> > >> > >> > >> > >> From: Gintautas Grigelionis <g.grigelio...@gmail.com> > >> Sent: Monday, May 29, 2017 9:50 AM > >> To: Ant Developers List > >> Sub

Re: Replace emma with jacoco?

e useful > than typical code coverage plugins. > > On 29 May 2017 at 08:55, Martin Gainty <mgai...@hotmail.com> wrote: > > > > > > > > > ____ > > From: Gintautas Grigelionis <g.grigelio...@gmail.com> > > Sen

Re: Replace emma with jacoco?

es, newsletters and other information from > sourceforge.net and its partners regarding IT services and products. I > understand that I can ... > > > WDYT of Clover? > > Martin > __ > > > > > From: Gint

Re: AW: PR-33: problems

Sorry for slow response, I'm on a trip. It does make sense to leave the exception in place only if ivy becomes opinionated about versions. I am not sure if compatibility break requires a change of major version. There are semver tools out there; maybe it's worth integrating them (redemption driven

Re: PR-33: problems

If it's acceptable I'll complement the PR addressing all the points. Gintas Den 29 maj 2017 10:13 skrev "Jan Matèrne" : I did a review of https://github.com/apache/ant-ivy/pull/33 Here are the points I have problems with, so I want

Re: Ivy website - fixing a Quickstart documentation live

;https://github.com/apache/ > ant-ivy/blob/xooki2asciidoc/asciidoc/templates/helpers.rb> > > Nicolas > > > Le 26 mai 2017 à 17:54, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > > Thanks for heads up: asciidoctorj > > <https://git

Replace emma with jacoco?

As you could understand by now, I set a goal of getting all targets in build.xml to do what they are supposed to do. Which brings us to emma, which appears no longer being developed. Do we need a vote about a replacement? Gintas

Getting checkstyle to work in build.xml

I tried to replace the current ivy:cachepath at line 578 (or so) with but that fails with [ivy:cachepath] [ivy:cachepath] :: problems summary :: [ivy:cachepath] WARNINGS [ivy:cachepath] :: [ivy:cachepath] ::

Re: Ivy website - fixing a Quickstart documentation live

Thanks for heads up: asciidoctorj , then :-) There are no Ant tasks, but maybe a javascript wrapper would do? Gintas 2017-05-26 17:26 GMT+02:00 Matt Sicker : > Can't you run the original Ruby asciidoc parser via JRuby, too? > > On

Re: build IvyDE

Did you try to run "ant hudson-prepare"? That's supposed to set up the entire environment, that is, download PDE and all dependencies (WTP, XSD, EMF, GEF and Zest) as drops, then unpack the PDE and all drops on top of that, if my understanding is correct. It also should pick up the latest Ivy

Re: Ivy website - fixing a Quickstart documentation live

asciidocs on Jython FTW :-) Gintas 2017-05-26 7:09 GMT+02:00 J Pai : > Thanks everyone for the inputs. > > I’m trying to get a proper build going locally for the site generation > (and running into issues). Once I get a proper build and the fixes to the > issues noted

Re: Versioning scheme in Ivy

> > [1] https://ant.apache.org/ivy/history/latest-milestone/ > settings/version-matchers.html <https://ant.apache.org/ivy/ > history/latest-milestone/settings/version-matchers.html> > > > > Le 24 mai 2017 à 10:22, Gintautas Grigelionis <g.grigelio...@gmail.com> >

Re: Ivy website - fixing a Quickstart documentation live

By the way... we'll need ant-ivy-site-styles , too :-) Gintas

Re: Ivy website - fixing a Quickstart documentation live

s them > online. > > We havent thought about a migrating that to git in the last few years ;) > > If these files are really required, I could upload them. > > > Jan > > > > > -Ursprüngliche Nachricht- > > Von: Gintautas Grigelionis [mailto:g.grig

Re: Ivy website - fixing a Quickstart documentation live

Is the documentation still in SVN? IVY-1542 is about site/sources/style which is shared by Ivy and IvyDE. Are there any plans about migrating this to Git and separating the source repo from publication repo? Gintas 2017-05-25 6:12 GMT+02:00 J Pai : > What would be the

Re: Versioning scheme in Ivy

Sorry, I meant to ask what may happen if special characters from range specification are used randomly in a version string? Gintas 2017-05-24 10:15 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > I was thinking about the discussion which touched upon restricted >

Versioning scheme in Ivy

I was thinking about the discussion which touched upon restricted characters in version strings. While Ivy does not place any restrictions on those strings, Ivy does support versions ranges as specified by OSGi. So, what happens if version range is used as a version string? Gintas

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

You're right, full HTTP/2 in JRE is Java 9. What I meant was AEAD crypto that was introduced in Java 8 JRE. Before that, that's another dependency on BouncyCastle. Gintas 2017-05-22 17:42 GMT+02:00 Matt Sicker : > Isn't HTTP 2.0 only in Java 9? Otherwise you need a 3rd party

Re: Buildjob: IvyDE

Admins have all rights to stay insist on closing as many CVSS 10 score holes in JRE as possible ;) Gintas 2017-05-22 21:24 GMT+02:00 Jan Matèrne (jhm) : > I changed the buildjobs for IvyDE + IvyDE-Github to use Java7(latest). > But I prefer to use the lowest Java version we

Re: Ivy - Goals for the upcoming release?

2017-05-21 19:00 GMT+02:00 Nicolas Lalevée : > > I don’t want to break your enthusiasm, but we should try to keep the API > as stable as possible. I know the API is very wide, a lot is exposed, but > we should be really careful at not breaking downside projects > I

Re: Ivy - Goals for the upcoming release?

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!) would make the code easier to read (I've seen incorrect comments of what goes

Re: Ivy - BasicURLHandler ignoring timeout during connection?

s down the line, maybe we can re-evaluate this and > consider the HttpClient libraries and their state at that time. > > -Jaikiran > On 20-May-2017, at 6:33 PM, Gintautas Grigelionis <g.grigelio...@gmail.com> > wrote: > > Looks like HttpClientHandler was added as an alternati

Re: Ivy - BasicURLHandler ignoring timeout during connection?

Looks like HttpClientHandler was added as an alternative to handle proxies with authentication by wrapping HttpClient from Commons. There is a maintenance problem because HttpClient has a major API change between version 3 (that Ivy uses currently) and 4. Perhaps it makes sense to look at

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

t. > Maarten > > Van: Gintautas Grigelionis <g.grigelio...@gmail.com> > Aan: Ant Developers List <dev@ant.apache.org>; Maarten Coene < > maarten_co...@yahoo.com> > Verzonden: vrijdag 19 mei 9:20 2017 > Onderwerp: Re: [VOTE] Increase minimum Java ver

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

, J Pai <jai.forums2...@gmail.com> a écrit : > > > > Not fully familiar with the voting process and don’t know if IvyDE will > require a voting thread of its own, but either way +1 for Java 7 for IvyDE > too. > > > > -Jaikiran > > On 19-May-2017, at 12:50 PM, Gintaut

Re: Ivy - BasicURLHandler ignoring timeout during connection?

My 2¢: timeout has only effect on doHead, in all other cases Ivy is trying the hardest it can. Just search for setTimeout :-) 2017-05-19 16:10 GMT+02:00 J Pai : > I was looking at some timing issues in test cases and noticed that the > BasicURLHandler.getURLInfo with a

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

Java 7 implements TLS 1.2; Ivy depends a lot more on network communications than Ant does. +1, but please extend the vote to the baseline of IvyDE as well. 2017-05-19 9:03 GMT+02:00 Maarten Coene : > I think we should stick to Java5 as long as Ant 1.9.x is

Re: Minimum Java runtime version for proposed upcoming Ivy release

Gradle does have an Ivy plugin which wraps Ivy 2.2.0 2017-05-18 11:26 GMT+02:00 Paul King : > The current version of Groovy has 1.6 as the minimum but is our maintenance > stream. > The upcoming next version will require 1.7 and versions with 1.8 as the > minimum are not too

Re: Minimum Java runtime version for proposed upcoming Ivy release

That's fine, IvyDE is already at Java 7/Eclipse 3.7.1; then IvyDE baseline should be bumped to Java 8/Eclipse 4.4 with the next Ivy release. Hopefully updatesite resolver could be used then. 2017-05-18 17:12 GMT+02:00 Matt Sicker : > Using 1.7 for the next release and then 1.8

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

Great! Still, the build still uses the pretty old Eclipse 3.7.1, and AFAICS the newer releases do not include drops, so some other dependency resolution mechanism will be necessary should for example we start discussing GEF 4+. 2017-05-17 20:48 GMT+02:00 Nicolas Lalevée

Re: Ivy+IvyDE: help wanted

Ivy is also a part of Groovy, through Grapes. There are quite a few forks of Ivy on GitHub, perhaps it is worth the while to solicit PRs? Meanwhile, I was asking for help/opinions about https://issues.apache.org/jira/browse/IVY-1478 (updatesite resolver) which would in turn help setting up builds

Hubot going berserk?

Hi, does anybody know why hubot deleted ant-ivy and ant-ivyde repos on GitHub and later partially restored ant-ivyde? Gintas

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

2016-12-22 20:57 GMT+01:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > Is the version number agreed upon? For IvyDE builds think the latest > version of Ivy is 2.5.0.alpha_20161213000915 > > Gintas > > > 2016-12-15 17:53 GMT+01:00 Matt Sicker <boa...@gmail.c

Ivy: updatesite resolver

I am trying to figure out how updatesite resolver works, but the documentation is somewhat lacking... For instance, http://ant.apache.org/ivy/history/trunk/osgi/osgi-mapping.html suggests using osgi attribute, which seems more logical than org="bundle" or org="package" (especially when

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

Is the version number agreed upon? For IvyDE builds think the latest version of Ivy is 2.5.0.alpha_20161213000915 Gintas 2016-12-15 17:53 GMT+01:00 Matt Sicker : > I'd definitely agree with the consistency principle. > > On 15 December 2016 at 01:38, Stefan Bodewig

Re: Site stuff (in particular Ivy and IvyDE)

svn-repo (outch). > > > Jan > > > > -Ursprüngliche Nachricht- > > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > > Gesendet: Montag, 19. Dezember 2016 14:15 > > An: Ant Developers List > > Betreff: Re: Site stuff (in particular Ivy and IvyDE

Re: Site stuff (in particular Ivy and IvyDE)

built sites and all releases for all projects (that's how IvyDE builds work, AFAICS). Gintas 2016-12-19 12:41 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2016-12-15, Gintautas Grigelionis wrote: > > >> 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bode...@apache.org>

Re: IvyDE status

One more thing: http://ant.apache.org/git.html still links to Subversion repo for IvyDE. Gintas 2016-12-15 10:13 GMT+01:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources, > ant-ivyde-site-sources

Re: IvyDE status

Great! May I suggest adding repos ant-site-sources, ant-ivy-site-sources, ant-ivyde-site-sources and ant-site (for publishing using the git workflow)? Gintas 2016-12-15 8:43 GMT+01:00 Stefan Bodewig <bode...@apache.org>: > On 2016-12-13, Gintautas Grigelionis wrote: >

Re: IvyDE status

e...@apache.org>: > On 2016-12-11, Gintautas Grigelionis wrote: > > > I have a question, too: perhaps the entire ivyde site repo could be > > converted to Git? > > The "ivyde site" is only a subdirectory of the whole of the Ant project > website. > > Back whe

Re: IvyDE status (Was: VOTE Retire IvyDE)

A short report on status (and more detailed answers to Nicholas questions): - the doc builds correctly once I clone ant-xooki repository on Github into doc/xooki; - the style clone on Github is empty; I did "wget -np -nd -r

Re: IvyDE status (Was: VOTE Retire IvyDE)

read to not pollute the vote. > > > Le 7 déc. 2016 à 19:56, Gintautas Grigelionis <g.grigelio...@gmail.com> > 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 f

Re: VOTE Retire IvyDE

Very well, how does one revive a project? Gintas 2016-12-08 21:01 GMT+01:00 Jan Matèrne (jhm) : > > Considering the current discussion around IvyDE and the involvement of > > Gintas, maybe we could cancel this vote, at least postpone it ? > > > > Nicolas > > > Yes, I agree. >

Re: VOTE Retire IvyDE

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. I would like to make the process to adapt to the build platform. Any suggestions for a reasonable Eclipse baseline? Should we target Java 8, that would be 4.5 (or

Re: VOTE Retire IvyDE

016-12-07, Gintautas Grigelionis wrote: > > > Somebody mentioned that IvyDE build process is broken and I would like to > > look into that if it could help to prevent retirement. > > That would be wonderful, regardless of whether it p

Re: VOTE Retire IvyDE

Somebody mentioned that IvyDE build process is broken and I would like to look into that if it could help to prevent retirement. Gintas 2016-12-07 10:00 GMT+01:00 Dominique Devienne : > +1 > > On Wed, Dec 7, 2016 at 8:41 AM, Jean-Louis Boudart < >

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

If you want to push Ivy, you need integrations with IDE. IMHO, IvyDE works well with Eclipse; perhaps its release cycle needs to be synced with Ivy release cycle (which is roughly biannual a this point). Is there a release plan for Ivy, by the way? When will this

Ivy extends loses defaultconfmapping

I tried to use extends tag to avoid boilerplate configurations like this ivy-module ... info organisation=a module=b extends organisation=c module=d revision=1 extendType=configurations/ /info publications ... /publications dependencies ... /dependencies /ivy-module The

Re: ERROR compile with build.sh, not read the parameters.

JUnit 4 depends in hamcrest-core Den 2 feb 2015 20:59 skrev Stefan Bodewig bode...@apache.org: On 2015-02-02, Stefan Bodewig wrote: On 2015-02-02, Rm Beer wrote: I use a source code for linux and all settings variable for shell. This line put in command shell: ./build.sh

finding out the original target names in an imported project

I have noticed (belatedly) a change in Ant API, namely, that there seems to be no way to find out what the original target names in an imported project are. Previously, original names were returned by getName() in a corresponding Target, which was consistent with getDependencies(). Now getName()

Re: finding out the original target names in an imported project

project name, so there is no way to find out what the original name is. Neither is there a simple way to correct the dependency names. Gintas 2013/9/30 Gintautas Grigelionis g.grigelio...@gmail.com I have noticed (belatedly) a change in Ant API, namely, that there seems to be no way to find

Re: finding out the original target names in an imported project

I must correct myself again... the short names are there, too, and one may use getLocation() to get rid of the doubles/correct getDependencies(). Still, the inconsistency remains... Gintas 2013/9/30 Gintautas Grigelionis g.grigelio...@gmail.com Sorry for double post, my description

Re: finding out the original target names in an imported project

But, there is one definite bug: the original name of the default target has its location set to project default=... ... line rather than the actual target name=... ... line. Gintas 2013/9/30 Gintautas Grigelionis g.grigelio...@gmail.com I must correct myself again... the short names

<    1   2   3   4