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

[GitHub] ant-ivy pull request #16: Fix download URL for findbugs task

Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/16 --- 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

Re: Ivy - Buildjobs/PreCommit

I just submitted a PR https://github.com/apache/ant-ivy/pull/16 which I think should fix the init-findbug task. -Jaikiran On 17-May-2017, at 6:59 PM, Nicolas Lalevée wrote: The build dedicated to check the style of Ivy is just calling: ant findbugs

[GitHub] ant-ivy pull request #16: Fix download URL for findbugs task

GitHub user jaikiran opened a pull request: https://github.com/apache/ant-ivy/pull/16 Fix download URL for findbugs task The commit here fixes the download URL used in the `init-findbugs` task, that has been failing[1] for a while due to reference to an URL that no longer works.

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.

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

AW: Ivy - Buildjobs/PreCommit

My last test result: The Jenkins job could not load Findbugs. So I have deactivated that for the moment. https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR/6/console ant-1.9.9> ant clean jar sources checkstyle-internal coverage-report resolve: BUILD FAILED /.../build.xml:184:

[GitHub] ant-ivy pull request #15: Create just-test-github-integration

GitHub user janmaterne opened a pull request: https://github.com/apache/ant-ivy/pull/15 Create just-test-github-integration You can merge this pull request into a Git repository by running: $ git pull https://github.com/janmaterne/ant-ivy patch-2 Alternatively you can review

[GitHub] ant-ivy pull request #14: Create just-test-github-integration

Github user janmaterne closed the pull request at: https://github.com/apache/ant-ivy/pull/14 --- 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

Re: Ivy - Buildjobs/PreCommit

Updated the same PR and that triggered this job https://builds.apache.org/job/Ivy-GithubPR/3/. It failed to build due to a host not being resolvable. This job ran on node called H15 https://builds.apache.org/computer/H15/ whereas the first job which had succeeded had run on

[GitHub] ant-ivy pull request #14: Create just-test-github-integration

GitHub user janmaterne opened a pull request: https://github.com/apache/ant-ivy/pull/14 Create just-test-github-integration You can merge this pull request into a Git repository by running: $ git pull https://github.com/janmaterne/ant-ivy patch-1 Alternatively you can review

AW: Ivy - Buildjobs/PreCommit

Thanks, I changed the job to run: ant clean jar sources findbugs checkstyle-internal coverage-report ant -f build-release.xml -Drat.failOnError=false rat Please try again ;) Jan > -Ursprüngliche Nachricht- > Von: J Pai [mailto:jai.forums2...@gmail.com] > Gesendet: Mittwoch, 17. Mai

[GitHub] ant-ivy issue #13: Dummy PR - Do not merge

Github user jaikiran commented on the issue: https://github.com/apache/ant-ivy/pull/13 retest this please --- 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,

Re: Ivy - Buildjobs/PreCommit

It turns out the PR you submitted was to your personal repo instead of the apache repo. I just submitted a dummy PR to apache repo https://github.com/apache/ant-ivy/pull/13 and that did indeed trigger the Jenkins job https://builds.apache.org/view/A/view/Ant/job/Ivy-GithubPR/1/ automagically

[GitHub] ant-ivy pull request #13: Dummy PR - Do not merge

GitHub user jaikiran opened a pull request: https://github.com/apache/ant-ivy/pull/13 Dummy PR - Do not merge This is just a dummy PR to test the PR integration with Jenkins jobs on Apache infra You can merge this pull request into a Git repository by running: $ git pull

Re: Ivy - Buildjobs/PreCommit

Doesn’t look like it got triggered in Jenkins. -Jaikiran On 17-May-2017, at 1:49 PM, Jan Matèrne (jhm) wrote: > I read the wiki page https://wiki.apache.org/general/PreCommitBuilds, > the Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and > had a look at some

AW: Ivy - Buildjobs/PreCommit

> I read the wiki page https://wiki.apache.org/general/PreCommitBuilds, > the Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and > had a look at some other PreCommit-jobs. > For me this works like that: > 1. The PreCommit-Admin job checks regularly on for new patches in Jira. > 2. It

Ivy - Buildjobs/PreCommit

I read the wiki page https://wiki.apache.org/general/PreCommitBuilds, the Kafka issue https://issues.apache.org/jira/browse/KAFKA-1856 and had a look at some other PreCommit-jobs. For me this works like that: 1. The PreCommit-Admin job checks regularly on for new patches in Jira. 2. It invokes the