Re: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread Gintautas Grigelionis
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 in that JIRA, I’ll send out

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

2017-05-25 Thread twogee
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

Re: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread 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 in that JIRA, I’ll send out an update. Hopefully soon. -Jaikiran On 25-May-2017, at 5:26 PM, Nicolas Lale

Re: IVYDE-382 proposed patch

2017-05-25 Thread J Pai
Hi Alexander, Thank you for volunteering to provide this feature patch. I had a look a the repo you pointed to and read the README. It does seem to contain a good amount of work in that branch in multiple commits. To make it easier for whoever will decide about merging these to upstream ant-i

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

2017-05-25 Thread jaikiran
GitHub user jaikiran reopened a pull request: https://github.com/apache/ant-ivy/pull/20 Fix IVY-1522 The commit here contains a potential fix for the issue reported in https://issues.apache.org/jira/browse/IVY-1522. This PR also contains a test case to verify the fix. **N

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

2017-05-25 Thread jaikiran
Github user jaikiran 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 en

[GitHub] ant-ivy pull request #21: Fix IVY-1495

2017-05-25 Thread jaikiran
GitHub user jaikiran reopened a pull request: https://github.com/apache/ant-ivy/pull/21 Fix IVY-1495 The commit here is a potential fix for the issue reported in https://issues.apache.org/jira/browse/IVY-1495. The issue happens when the `ivysettings.xml` is being parsed and the `Iv

[GitHub] ant-ivy issue #21: Fix IVY-1495

2017-05-25 Thread jaikiran
Github user jaikiran commented on the issue: https://github.com/apache/ant-ivy/pull/21 Reopening this one --- 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, o

[GitHub] ant-ivy pull request #21: Fix IVY-1495

2017-05-25 Thread jaikiran
Github user jaikiran closed the pull request at: https://github.com/apache/ant-ivy/pull/21 --- 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 en

[GitHub] ant-ivy pull request #27: Fix IVY-1540

2017-05-25 Thread jaikiran
GitHub user jaikiran reopened a pull request: https://github.com/apache/ant-ivy/pull/27 Fix IVY-1540 The commit here fixes the issue reported in https://issues.apache.org/jira/browse/IVY-1540. The dependency tree task now takes into account any potential circular dependencies that

[GitHub] ant-ivy issue #27: Fix IVY-1540

2017-05-25 Thread jaikiran
Github user jaikiran commented on the issue: https://github.com/apache/ant-ivy/pull/27 Now that the transient failure fixes have been merged and the Jenkins PR jobs are working, going to reopen this to trigger a new run of Jenkins. --- If your project is set up for it, you can reply

[GitHub] ant-ivy pull request #27: Fix IVY-1540

2017-05-25 Thread jaikiran
Github user jaikiran closed the pull request at: https://github.com/apache/ant-ivy/pull/27 --- 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 en

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

2017-05-25 Thread twogee
Github user twogee commented on the issue: https://github.com/apache/ant-ivy/pull/31 Thanks for a nice summary and pointing out a paradigm that I did not investigate entirely. The essential work also included checking that all appropriate setUp() and tearDown() were public and/or nece

AW: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread jhm
+1 for asciidoc. Using xooki means using a tool only few people know ... Jan > -Ursprüngliche Nachricht- > Von: J Pai [mailto:jai.forums2...@gmail.com] > Gesendet: Donnerstag, 25. Mai 2017 14:03 > An: Ant Developers List > Betreff: Re: Ivy website - fixing a Quickstart documentation live

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

2017-05-25 Thread janmaterne
Github user janmaterne commented on the issue: https://github.com/apache/ant-ivy/pull/31 That was a lot of work (or writing/using a transformator ;) Basically it - removes the "extends TestCase" and - uses JUnit annotations - change string.indexOf()!=-1 to string.contain

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

2017-05-25 Thread twogee
GitHub user twogee opened a pull request: https://github.com/apache/ant-ivy/pull/31 Convert tests to JUnit 4, clean up code JUnit 4 has primarily two benefits, clarity through annotations and more fine grained control of failures You can merge this pull request into a Git reposito

[GitHub] ant-ivy issue #30: Fix transient test failures

2017-05-25 Thread nlalevee
Github user nlalevee commented on the issue: https://github.com/apache/ant-ivy/pull/30 I don't find the fix fully satisfying because it doesn't address the fragile static set of circularDependencyId, it might produce some side effect errors in the future. At least we should keep it mi

[GitHub] ant-ivy pull request #30: Fix transient test failures

2017-05-25 Thread asfgit
Github user asfgit closed the pull request at: https://github.com/apache/ant-ivy/pull/30 --- 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 enab

Re: Ivy documentation with asciidoc

2017-05-25 Thread Nicolas Lalevée
> Le 25 mai 2017 à 16:17, Matt Sicker a écrit : > > Merge commits always spam the commits list which, while annoying, I've > learned to mass-delete whenever it happens. ;) > > I looked at some random changes and found a couple markup typos, but > otherwise it looks like it converted well enough

Re: Ivy documentation with asciidoc

2017-05-25 Thread Matt Sicker
Merge commits always spam the commits list which, while annoying, I've learned to mass-delete whenever it happens. ;) I looked at some random changes and found a couple markup typos, but otherwise it looks like it converted well enough. I'm more familiar with the maven plugins for site management

Ivy documentation with asciidoc

2017-05-25 Thread Nicolas Lalevée
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: h

Re: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread J Pai
On 25-May-2017, at 5:26 PM, Nicolas Lalevée wrote: > By the way, the Ivy documentation is managed by an hand crafted html editor, > xooki, just is good but quite slow. I did some work some time ago (2 years > ago, time flies!) to try to migrate to asciidoc [2]. I can even see that > locally

Re: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread Nicolas Lalevée
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. Now

Re: Versioning scheme in Ivy

2017-05-25 Thread Gintautas Grigelionis
Sorry for a roundabout way of getting to the point, but wouldn't the characters used in matchers be treated in a special way, thus restricting their use in version strings? On a related theme, should Ivy support semver ranges [1]? (that would include >, <, >=, <=, =, ||, &, !, and shorthands [2] *

Re: Versioning scheme in Ivy

2017-05-25 Thread Nicolas Lalevée
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?

2017-05-25 Thread Nicolas Lalevée
Thank you very much Jaikiran for your detailed explanation. I have to admit that I don’t know the answer to which is the source of truth about the resolution report. I have also wondered why the resolve report should have to be always wrote and then read from file. I’ll try to get an answer mys

IVYDE-382 proposed patch

2017-05-25 Thread alexander . blaas
Dear Sir or Madam, as it was suggested in https://issues.apache.org/jira/browse/IVYDE-382?focusedCommentId=16018847&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-16018847, we are sending you our proposed patch for https://issues.apache.org/jira/browse/IVYDE-382. Th

Re: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread Gintautas Grigelionis
By the way... we'll need ant-ivy-site-styles , too :-) Gintas

Re: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread Gintautas Grigelionis
The files mentioned in JIRA were absent for a couple of years. If they're available, let's get them into the site repo, otherwise the css files must be adjusted. I remember there was a discussion about gitpubsub... perhaps if we understand how current svnpubsub hooks are set up, going to gitpubsub