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 : > > > Le 31 mai 2017 à 19:47, Gintautas Grigelionis > a écrit : > > > Also, external links must be pruned and/or directed to Internet Archive > :-( > > The tutorial of yEd must be revised, version 3 has many more controls. I > > converted the odg diag

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 19:47, Gintautas Grigelionis a > écrit : > > 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/s

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

I don't see how Ivy could resolve the old ant-compress ivy.xml files without using very special artifact patterns.So my guess is that Ivy users of ant-compress just use the pom.xml file. So I'd say we should fix the ivy.xml. Maarten Van: Stefan Bodewig Aan: dev@ant.apache.org Verzonde

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 be

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 : > On 2017-05-31, Gintautas Grigelionis wrote: > > > can't you just publish new ivy.xml? > > we can't overwrite existing files in Maven Central. > > Stefan > >

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 17:53, J Pai a écrit : > > > On 31-May-2017, at 9:02 PM, Nicolas Lalevée > wrote: > > >> Le 31 mai 2017 à 15:34, J Pai a écrit : >> >> One thing I just noticed in the generated adoc files is that “external” >> links that are part of th

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

On 2017-05-31, Gintautas Grigelionis wrote: > can't you just publish new ivy.xml? we can't overwrite existing files in Maven Central. Stefan - To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org For additional commands, e-ma

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 that the ivy.xml file I've published to N

Re: Ivy documentation with asciidoc

On 31-May-2017, at 9:02 PM, Nicolas Lalevée wrote: > Le 31 mai 2017 à 15:34, J Pai a écrit : > > One thing I just noticed in the generated adoc files is that “external” links > that are part of the original xooki backed .html files are not being > generated as links in the converted adoc. T

[antlibs] Break Backwards Compatibility of Ivy Coordinates?

Hi all this is an excerpt from the cancelled vote thread for the compress antlib. 2017-05-31 16:40 GMT+02:00 Stefan Bodewig : > I've just realized that the ivy.xml file I've published to Nexus has > completely different coordinates from the one used in earlier > releases. It used to be > >

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 15:34, J Pai a écrit : > > One thing I just noticed in the generated adoc files is that “external” links > that are part of the original xooki backed .html files are not being > generated as links in the converted adoc. To see a couple of example, take a > look at this hibn

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

On 2017-05-31, Gintautas Grigelionis wrote: > Luckily, all the old poms have correct coordinates :-) They MUST be the > same in pom.xml and ivy.xml Well. Ironically the folks working on Ant libs are more familiar with Maven then with Ivy, at least I am. After re-reading the Ivy docs I fully have

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

Luckily, all the old poms have correct coordinates :-) They MUST be the same in pom.xml and ivy.xml Gintas 2017-05-31 17:09 GMT+02:00 Gintautas Grigelionis : > Hi, > > the master is correct and all previous coordinates as well as RC1 are > wrong. > > Gintas > > 2017-05-31 16:40 GMT+02:00 Stefan

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

Hi, the master is correct and all previous coordinates as well as RC1 are wrong. Gintas 2017-05-31 16:40 GMT+02:00 Stefan Bodewig : > Hi all > > I've just realized that the ivy.xml file I've published to Nexus has > completely different coordinates from the one used in earlier > releases. It us

Re: Ivy documentation with asciidoc

> Le 31 mai 2017 à 15:20, J Pai a écrit : > > I had some time today and decided to test this branch out locally. I was able > to generate the docs without any hassle. The conversion works fine which is a > great thing. > > There are certain warning about the heading/section level we use in th

[CANCEL][VOTE] Release Compress Antlib 1.5 based on RC1

Hi all I've just realized that the ivy.xml file I've published to Nexus has completely different coordinates from the one used in earlier releases. It used to be

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

No Stefan, I was just wondering if it was normal that this file didn't contain the release date.If the current situation is fine for you, I'll give my vote. Maarten Van: Stefan Bodewig Aan: dev@ant.apache.org Verzonden: woensdag 31 mei 14:39 2017 Onderwerp: Re: [VOTE] Release Compress

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 today and decided to test th

Re: Ivy documentation with asciidoc

One thing I just noticed in the generated adoc files is that “external” links that are part of the original xooki backed .html files are not being generated as links in the converted adoc. To see a couple of example, take a look at this hibnet.org/tmp/ivy-asciidoc/index.html page. The “Apache Li

Re: Ivy documentation with asciidoc

I had some time today and decided to test this branch out locally. I was able to generate the docs without any hassle. The conversion works fine which is a great thing. There are certain warning about the heading/section level we use in the generated adoc files, for top level heading: > [ascii

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

Maarten, Jan right now this only has my implicit vote. Would you be more inclined to vote if the date was included inside the changelog? If so, I'll re-roll the release. Stefan On 2017-05-31, Maarten Coene wrote: > Why not simply ?That is the date > the vote started and the binaries were buil

Re: Problems Releaseing Antlibs

On 2017-05-31, J Pai wrote: > Just had a look at that ivysettings-nexus.xml file. You are right, > changing that file should fix it. almost. I think we are abusing the module or organization idea of ivy a little as the antlibs' artifacts all live inside the org.apache.ant groupId (in mvn speak) w

Re: Problems Releaseing Antlibs

Just had a look at that ivysettings-nexus.xml file. You are right, changing that file should fix it. -Jaikiran On 31-May-2017, at 5:43 PM, Stefan Bodewig wrote: On 2017-05-31, J Pai wrote: > These are the changes (which incorporates Gintas suggestion) that > might help get us past the upload i

Re: Problems Releaseing Antlibs

On 2017-05-31, J Pai wrote: > These are the changes (which incorporates Gintas suggestion) that > might help get us past the upload issue. I've only modified ivysettings-nexus.xml obtained from common (locally, not pushed, yet) and that seems to have done the trick. I didn't have to change prepar

Re: Problems Releaseing Antlibs

These are the changes (which incorporates Gintas suggestion) that might help get us past the upload issue. Change to ivy.xml of compress project: diff --git a/ivy.xml b/ivy.xml index eb034ac..6c5e823 100644 --- a/ivy.xml +++ b/ivy.xml @@ -18,7 +18,7 @@ --> - + value="${

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 Compress and > > do

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

Why not simply ?That is the date the vote started and the binaries were built?Or perhaps you could add a few days to it and make sure the vote ends at that date? It's just strange when reading the documentation of a released version to see that it's 'unreleased' or 'during-release'... Maarten

[GitHub] ant-ivy issue #37: Don't pollute the source lib folder during ivy retrieval ...

Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/37 Thanks, could this PR be merged? Then I'll clean up #36 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have t

Re: Problems Releaseing Antlibs

On 2017-05-31, Stefan Bodewig wrote: > I'll fix common first (and update Ivy as I go, then fix Compress and > do a test deploy that I can easily drop again. /devel/ASF/ant-antlibs-compress/common/upload.xml:40: impossible to publish artifacts for org.apache.ant#ant-compress;1.5.1: java.io.IOExce

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

Maybe ? Jan -Ursprüngliche Nachricht- Von: Stefan Bodewig [mailto:bode...@apache.org] Gesendet: Mittwoch, 31. Mai 2017 09:46 An: dev@ant.apache.org Betreff: Re: [VOTE] Release Compress Antlib 1.5 based on RC1 On 2017-05-31, Maarten Coene wrote: > The changes.xml still contains the fol

Re: Problems Releaseing Antlibs

On 2017-05-31, J Pai wrote: > I had a brief look at this project’s repo and triggered these tasks > locally. Of course, I won’t be able to test the whole upload process, > but I was able to see what’s wrong. Great! > There are 2 “projects” that need this fix. The “common” project and > the “comp

[GitHub] ant-ivy issue #36: Replace emma with jacoco

Github user jaikiran commented on the issue: https://github.com/apache/ant-ivy/pull/36 >> I found out that JUnit tests polute run.classpath by placing an empty jar in /lib, which breaks eg javadoc. Any ideas which test may do that? I believe this PR https://github.com/apache/a

[GitHub] ant-ivy pull request #37: Don't pollute the source lib folder during ivy ret...

GitHub user jaikiran opened a pull request: https://github.com/apache/ant-ivy/pull/37 Don't pollute the source lib folder during ivy retrieval in test The `IvyRetrieveBuildFileTest` triggers a Ant project build during the test case and issues a `ivy:retrieve` through the build file.

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

On 2017-05-31, Maarten Coene wrote: > The changes.xml still contains the following line: date="unreleased"> > I'm not sure this should block the release, but I think it would be better to > fill in the correct date. This is a chicken and egg problem. As long as the vote hasn't passed, I don't kn

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

The changes.xml still contains the following line: I'm not sure this should block the release, but I think it would be better to fill in the correct date. Maarten Van: Stefan Bodewig Aan: dev@ant.apache.org Verzonden: dinsdag 30 mei 20:28 2017 Onderwerp: [VOTE] Release Compress Antli