AW: build IvyDE

Nope, haven't read that. My first contact to a build is always executing the build without any parameters. ;) I'll have a look, thanks. Jan > -Ursprüngliche Nachricht- > Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org] > Gesendet: Freitag, 26. Mai 2017 17:21 > An: Ant

[GitHub] ant-ivy pull request #32: A few loose bits in JUnit 4 migration

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/32 --- 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 this feature enabled and wishes so, or if the feature is

[GitHub] ant-ivy issue #32: A few loose bits in JUnit 4 migration

Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/32 Jenkins build was complete an hour ago, but status on Github is still pending... --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If

Re: Ivy website - fixing a Quickstart documentation live

There are some Ant task for asciidoctor, and it is used in the branch where there is the experiment about migrating from xooki to asciidoc: https://github.com/apache/ant-ivy/blob/xooki2asciidoc/build-release.xml#L168

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

[GitHub] ant-ivy issue #32: A few loose bits in JUnit 4 migration

Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/32 Unless I'm mistaken, `BuildFileRule` was available first in 1.9.5; `ProcessUtil` needs 1.9.4 --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] ant-ivy issue #32: A few loose bits in JUnit 4 migration

Github user nlalevee commented on the issue: https://github.com/apache/ant-ivy/pull/32 The job was configure to use the default Ant, which I don't know which is exactly. So I have changed the conf to use Ant 1.9.9 (the same version that the one declared in the ivy.xml of Ivy). A

Re: Ivy website - fixing a Quickstart documentation live

Can't you run the original Ruby asciidoc parser via JRuby, too? On 26 May 2017 at 02:06, J Pai wrote: > So I got this site generation working locally (had to fix a xooki script > to make it work with Nashorn. The attached patch includes the fix). > > At this point, I

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

build IvyDE

I tried to get the IvyDE build working. Finally I am getting a [eclipse.buildScript] Some inter-plug-in dependencies have not been satisfied. [eclipse.buildScript] Bundle org.apache.ivyde.eclipse.resolvevisualizer: [eclipse.buildScript] Missing required plug-in

[GitHub] ant-ivy issue #31: Convert tests to JUnit 4, clean up code

Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/31 I do 😃 --- 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 this feature enabled and wishes so, or if the

[GitHub] ant-ivy issue #32: A few loose bits in JUnit 4 migration

Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/32 Why is Jenkins lacking org.apache.tools.ant.util.ProcessUtil? Something wrong with Ant? --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as

[GitHub] ant-ivy pull request #32: A few loose bits in JUnit 4 migration

GitHub user twogee opened a pull request: https://github.com/apache/ant-ivy/pull/32 A few loose bits in JUnit 4 migration This adds annotations that are missing, migrates example code and fixes whitespace You can merge this pull request into a Git repository by running: $ git

Re: IVY-1485, resolve report and resolved versions

> Le 26 mai 2017 à 13:23, J Pai a écrit : > > Thank you very much Nicolas for digging more into this and getting hold of > these details. What you explain, backed by the details, makes clear sense. > > I will attempt to go with this option that you suggest: > >> -

Re: IVY-1485, resolve report and resolved versions

Thank you very much Nicolas for digging more into this and getting hold of these details. What you explain, backed by the details, makes clear sense. I will attempt to go with this option that you suggest: > - drop this property file, make the xml report always produced, and make the > deliver

[GitHub] ant-ivy issue #31: Convert tests to JUnit 4, clean up code

Github user nlalevee commented on the issue: https://github.com/apache/ant-ivy/pull/31 @twogee to properly add you to the list of contributors, do you confirm you are Gintautas Grigelionis ? --- If your project is set up for it, you can reply to this email and have your reply

[GitHub] ant-ivy issue #20: Fix IVY-1522

Github user nlalevee commented on the issue: https://github.com/apache/ant-ivy/pull/20 merged. Thank both of you. --- 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 this feature enabled and

[GitHub] ant-ivy pull request #20: Fix IVY-1522

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/20 --- 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 this feature enabled and wishes so, or if the feature is

IVY-1485, resolve report and resolved versions

After some digging, I found out that the resolved revisions property file is very old (git is awesome, even better within sourcetree). It is so old that at that time the xml resolve report didn’t exist. And this property file seems to have been created just in order to make the deliver task

[GitHub] ant-ivy pull request #31: Convert tests to JUnit 4, clean up code

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/31 --- 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 this feature enabled and wishes so, or if the feature is

[GitHub] ant-ivy issue #31: Convert tests to JUnit 4, clean up code

Github user janmaterne commented on the issue: https://github.com/apache/ant-ivy/pull/31 merged, thanks --- 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 this feature enabled and wishes so, or

[GitHub] ant-ivy issue #31: Convert tests to JUnit 4, clean up code

Github user janmaterne commented on the issue: https://github.com/apache/ant-ivy/pull/31 Nice idea to use the old fail-Message as new method comment to document why the exception is expected. --- If your project is set up for it, you can reply to this email and have your reply

Re: Ivy website - fixing a Quickstart documentation live

So I got this site generation working locally (had to fix a xooki script to make it work with Nashorn. The attached patch includes the fix). At this point, I need help to commit the newly generated doc fixes to the SVN. I’ve attached a patch file for it and will explain what it is doing. The

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

[GitHub] ant-ivy issue #31: Convert tests to JUnit 4, clean up code

Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/31 I left a few `fail()`s where multiple assertions were made; I guess that requires a custom @Rule. Also, in `FileSystemResolverTest`, I moved `finally` blocks to `tearDown()`. Strangely, that