finding out the original target names in an imported project

2013-09-30 Thread Gintautas Grigelionis
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

2013-09-30 Thread Gintautas Grigelionis
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

2013-09-30 Thread Gintautas Grigelionis
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

2013-09-30 Thread Gintautas Grigelionis
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

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

2015-02-02 Thread Gintautas Grigelionis
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

Ivy extends loses defaultconfmapping

2015-04-09 Thread Gintautas Grigelionis
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: Ivy - Proposal for reviving the project and moving towards a release

2017-02-02 Thread Gintautas Grigelionis
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

2017-01-30 Thread Gintautas Grigelionis
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: VOTE Retire IvyDE

2016-12-07 Thread Gintautas Grigelionis
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

2016-12-08 Thread Gintautas Grigelionis
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: IvyDE status (Was: VOTE Retire IvyDE)

2016-12-08 Thread Gintautas Grigelionis
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: IvyDE status

2016-12-13 Thread Gintautas Grigelionis
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: VOTE Retire IvyDE

2016-12-07 Thread Gintautas Grigelionis
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: VOTE Retire IvyDE

2016-12-07 Thread Gintautas Grigelionis
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: IvyDE status

2016-12-15 Thread Gintautas Grigelionis
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

2016-12-16 Thread Gintautas Grigelionis
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 (Was: VOTE Retire IvyDE)

2016-12-11 Thread Gintautas Grigelionis
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: Ivy - any future or is it also going to be retired?

2016-12-05 Thread Gintautas Grigelionis
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

Re: Site stuff (in particular Ivy and IvyDE)

2016-12-20 Thread Gintautas Grigelionis
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: Ivy - Proposal for reviving the project and moving towards a release

2016-12-22 Thread Gintautas Grigelionis
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)

2016-12-19 Thread Gintautas Grigelionis
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: Ivy - PR-57 need inputs

2017-07-28 Thread Gintautas Grigelionis
Please see my comment on GitHub. It is a change of signature (from array to collection) in order to change the return type (from array to collection, because arrays of generics do not work), and it's based on refactoring of AbstractOSGiResolver. It is a crucial piece to getting the generics right,

Re: Ivy - PR-57 need inputs

2017-07-29 Thread Gintautas Grigelionis
only because of the lack of proper typing. In a nutshell, the mitigation I proposed looks adequate (the check in ChainResolver looks like almost an overkill). Gintas 2017-07-28 21:26 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > Sorry all, I misunderstood the problem, a

Re: Proposed changes for IVY-735 - Ability to specify timeouts

2017-07-17 Thread Gintautas Grigelionis
hem would allow > > reusing these values on whichever resolvers want to: > > > > > > > > > > > > > read-timeout=""> > > > > ... > > > > > > > > > > > > > > > > > > > > > > > > > > -Jaikiran >

Re: Ivy 2.5 and generics

2017-07-09 Thread Gintautas Grigelionis
Hi, I hope you're doing well and not (yet) on vacation :-) I just opened PR-52, which should conclude large-scale code changes and prepare the field for more focused discussion regarding the API. Gintas 2017-06-20 14:06 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > I

Re: [VOTE] IvyDE requirements

2017-07-11 Thread Gintautas Grigelionis
+1 on both (having suggested it previously). Gintas 2017-07-11 23:07 GMT+02:00 Nicolas Lalevée : > We have recently voted to make Ivy require Java 1.7. I think we should do > it for IvyDE too. > Do you vote for it ? > > > And while making the build of IvyDE work

Re: Build failed in Jenkins: IvyDE #320

2017-07-10 Thread Gintautas Grigelionis
Looks like GEF3 was archived, see http://archive.eclipse.org/tools/gef/downloads/drops/3.9.100/R201405261516/ Gintas 2017-07-10 23:56 GMT+02:00 Nicolas Lalevée : > I don’t understand what is going on. The files are there and then they > disappear… I have been able to

Re: Proposed changes for IVY-735 - Ability to specify timeouts

2017-07-14 Thread Gintautas Grigelionis
my €.02 : currently, all resolvers only have artifact patterns as child elements, so I'd rather have the timeouts as attributes that might use references, similarly to cache managers or latest strategies. That would imply a global default that may be overridden individually. Gintas 2017-07-14

Coding style: import of nested classes

2017-07-18 Thread Gintautas Grigelionis
In my last PR I tried to address inconsistencies with import of nested classes, such as Map.Entry; some classes, e.g. IvySettings ended up with foreach loops over both Entry and Map.Entry. So: should qualified names be encouraged or avoided? Gintas

Re: Opportunities for cohesion improvement and refatoring.

2017-07-20 Thread Gintautas Grigelionis
Hi João Paulo, please open a pull request on GitHub or at least provide a description of your suggested improvements. Thanks, Gintas 2017-07-20 1:56 GMT+02:00 João Paulo Lemes Machado : > Hello everyone. > > My name is João Paulo, I am a graduate student the Federal

Re: Opportunities for cohesion improvement and refatoring.

2017-07-20 Thread Gintautas Grigelionis
I looked at Project proposal [1]. I would suggest running the refactored Ant through japicmp [2] or revapi [3] and examining the binary incompatibilities. Gintas [1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61305 [2] http://siom79.github.io/japicmp/ [3] http://revapi.org/ 2017-07-20 16:41

Re: Opportunities for cohesion improvement and refatoring.

2017-07-21 Thread Gintautas Grigelionis
SubProject you are going to break the > subclass. And I don't think the tools are going to tell you as long as > you keep all existing methods. > > This is what I meant with "have to ensure you keep the existing who > calls which method semantics". > > Cheers > &

Re: Ivy - No more support for commons-httpclient 2.x in runtime classpath?

2017-07-24 Thread Gintautas Grigelionis
FYI 2.x is EOL for 11.5 years [1] Should we count each year as +1? :-) Gintas [1] http://hc.apache.org/httpclient-3.x/news.html 2017-07-24 7:53 GMT+02:00 Jan Matèrne (jhm) : > While it's fine to have such a dynamic behaviour it's hard to maintain. > On this special location

Re: Ivy - Move to symlink creation standard Java API?

2017-07-27 Thread Gintautas Grigelionis
There might be some issues with Cygwin, see Eclipse/JGit discussion [1] Gintas [1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=354367 2017-07-27 10:44 GMT+02:00 Jan Matèrne (jhm) : > If the new Java version supports the symlink creation and it's an > implementation detail

Re: Ivy - Move to symlink creation standard Java API?

2017-07-27 Thread Gintautas Grigelionis
I did a few simple tests on Windows 7 + Cygwin and NIO.2 seems to work just fine (if privilege to create symlinks is granted). +1 Gintas 2017-07-27 11:40 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > There might be some issues with Cygwin, see Eclipse/JGit disc

Re: Ivy logo as SVG

2017-07-27 Thread Gintautas Grigelionis
Devienne <ddevie...@gmail.com>: > On Thu, Jun 8, 2017 at 4:35 PM, Gintautas Grigelionis < > g.grigelio...@gmail.com> wrote: > > > https://drive.google.com/open?id=0B2mVPD7ZO6sdcDFkX1lQdHJWZVRwU > > UdSSXI1VnF3bk5xTFhF > > > I like it! --DD >

Re: Is CacheResolver relevant?

2017-07-27 Thread Gintautas Grigelionis
Perhaps another JIRA issue [1] would cast some light? [1] https://issues.apache.org/jira/browse/IVY-1227 Gintas 2017-07-27 18:10 GMT+02:00 Jaikiran Pai : > > On 27/07/17 9:34 PM, Jaikiran Pai wrote: > >> There's a JIRA[2] asking for the docs to be updated to explain

Re: Is CacheResolver relevant?

2017-07-28 Thread Gintautas Grigelionis
://github.com/sbt/sbt/issues/368 Perhaps it's worth looking into? 2017-07-28 7:44 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > Perhaps another JIRA issue [1] would cast some light? > > [1] https://issues.apache.org/jira/browse/IVY-1227 > > Gintas > > 2017-07-

Re: Reproducible JARs

2017-07-25 Thread Gintautas Grigelionis
I believe the easier way would be to diff the fileset of classes to be packed to the fileset of classes in the jar before creating a new jar. There's a tool called zipdiff that could do the trick (it may ignore timestamps, etc). That would correspond to a javac deciding on whether to recompile the

Re: Ivy - we have now moved to asciidoc for docs

2017-06-30 Thread Gintautas Grigelionis
terminology.adoc apparently has an incorrect link on line 150, configuration/statuses.html should be settings/statuses.html (I get a redirect from http://ant.apache.org/ivy/history/master/terminology.html) Gintas 2017-06-30 18:18 GMT+02:00 Nicolas Lalevée : > I have

Re: Ivy - we have now moved to asciidoc for docs

2017-07-01 Thread Gintautas Grigelionis
> Probably a thing to improve are all the « since 2.x » annotations. Maybe we can have a macro for that, which will render everywhere the same, and which will be placed everywhere the same. Now sometimes it is at the beginning of the line, sometimes at the end, sometimes above. And I find it being

Re: Ivy - we have now moved to asciidoc for docs

2017-07-01 Thread Gintautas Grigelionis
pull/49/commits> > [2] https://github.com/apache/ant-ivy/pull/50/commits < > https://github.com/apache/ant-ivy/pull/50/commits> > > > Le 1 juil. 2017 à 08:07, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > > I opened a PR (well, actually two :

Re: Ivy - we have now moved to asciidoc for docs

2017-07-01 Thread Gintautas Grigelionis
I opened a PR (well, actually two :-() to fix spelling and links that still point to configuration. Gintas 2017-06-30 18:44 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > terminology.adoc apparently has an incorrect link on line 150, > configuration/statuses

Re: [GitHub] ant-ivy pull request #48: Generics and Java 7 syntax in osgi and plugins pac...

2017-07-01 Thread Gintautas Grigelionis
I believe stackoverflow has an answer [1] Gintas [1] https://stackoverflow.com/questions/30454635/when-using-for-a-primitive-and-a-boxed-value-is-autoboxing-done-or-is-unbox 2017-07-01 15:56 GMT+02:00 jaikiran : > Github user jaikiran commented on a diff in the pull

Re: Ivy - we have now moved to asciidoc for docs

2017-07-01 Thread Gintautas Grigelionis
2017-07-01 18:56 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > > > Le 1 juil. 2017 à 15:27, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > >> Probably a thing to improve are all the « since 2.x » annotations. Maybe > > we

Re: [2/2] ant-ivy git commit: Generate automatically the copyright year in the doc

2017-07-06 Thread Gintautas Grigelionis
I believe Ivy graduated in 2007? Gintas 2017-07-06 8:10 GMT+02:00 Matèrne, Jan (RZF, Ref 410) : > AFAIK in other locations we use a range of time. > Should that be used here too? > > | Copyright 2008 - > = " " + Time.now.year.to_s + " " > |

Re: [2/2] ant-ivy git commit: Generate automatically the copyright year in the doc

2017-07-06 Thread Gintautas Grigelionis
; -Ursprüngliche Nachricht- > Von: Gintautas Grigelionis [mailto:g.grigelio...@gmail.com] > Gesendet: Donnerstag, 6. Juli 2017 10:15 > An: Ant Developers List > Betreff: Re: [2/2] ant-ivy git commit: Generate automatically the > copyright year in the doc > > I believe Ivy gradu

Hubot going berserk?

2017-04-28 Thread Gintautas Grigelionis
Hi, does anybody know why hubot deleted ant-ivy and ant-ivyde repos on GitHub and later partially restored ant-ivyde? Gintas

Re: Ivy - PR-57 need inputs

2017-07-28 Thread Gintautas Grigelionis
34 GMT+02:00 Gintautas Grigelionis <g.grigelio...@gmail.com>: > It's not a new method, it's a change of signature. The old method is still > there. If an implementation disregards the abstract class, which contains > the replacement, it would still work, right? > > Gintas > > 20

Re: Ivy - PR-57 need inputs

2017-07-28 Thread Gintautas Grigelionis
Sorry all, I misunderstood the problem, and thanks to Jaikiran and Stefan for the discussion. Third party implementations will be broken because they lack the method with the new signature unless they extend the AbstractResolver. And the AbstractResolver must work the other way around, provide a

Re: Ivy - PR-57 need inputs

2017-07-28 Thread Gintautas Grigelionis
It's not a new method, it's a change of signature. The old method is still there. If an implementation disregards the abstract class, which contains the replacement, it would still work, right? Gintas 2017-07-28 18:55 GMT+02:00 Stefan Bodewig : > On 2017-07-28, Jaikiran Pai

Re: IVY-1485

2017-08-08 Thread Gintautas Grigelionis
Great! Should I look into documentation-related issues in more detail? Gintas 2017-08-08 6:06 GMT+02:00 Jaikiran Pai <jai.forums2...@gmail.com>: > I'm looking into that JIRA. I'll assigned it to my name now. > > -Jaikiran > > > > On 06/08/17 12:52 PM, Gintautas Gri

Documentation-related issues in Jira

2017-08-22 Thread Gintautas Grigelionis
Earlier, I wrote about the amount of documentation-related issues in Jira. There are 27 of them still open [1], and some of them could be closed right away. I would be glad to help, but I have no privileges. Is there somebody who could help me? Thanks, Gintas P.S. I noticed that I misspelled my

Re: Documentation-related issues in Jira

2017-08-23 Thread Gintautas Grigelionis
Thanks, somehow I missed the pencil in my profile :-) I'll start commenting the issues. Gintas 2017-08-23 7:44 GMT+02:00 Stefan Bodewig <bode...@apache.org>: > On 2017-08-22, Gintautas Grigelionis wrote: > > > I would be glad to help, but I have no privileges. Is there some

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

2017-05-17 Thread Gintautas Grigelionis
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

2017-05-16 Thread Gintautas Grigelionis
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

Re: Ivy - we have now moved to asciidoc for docs

2017-06-20 Thread Gintautas Grigelionis
I'd happy to help later tonight, please let me know if there's some particular section that I should look into. Skimming through quickly, More Examples ( http://people.apache.org/~hibou/doc/moreexamples.html) should be adjusted. Gintas 2017-06-20 4:16 GMT+02:00 Jaikiran Pai

Re: Ivy 2.5 and generics

2017-06-20 Thread Gintautas Grigelionis
on to that for a bit and evaluate > it in some subsequent release so that we don’t do too many changes without > evaluating the kind of impact it has on the external libraries that use Ivy. > > Ultimately, I believe this will come down to a case-by-case basis. > > -Jaikiran >

Re: Ivy jobs on Teamcity need reconfiguring

2017-06-20 Thread Gintautas Grigelionis
Sorry for confusing TeamCity jobs with Jenkins jobs previously. TeamCity seems to be unhappy about the Java version *javac: invalid target release: 1.7* since it still uses JRE 1.5 Somebody who is project admin should change parameters in build configuration? Gintas

Re: Jenkins Jobs of Ivy/IvyDE

2017-06-26 Thread Gintautas Grigelionis
2017-06-26 13:54 GMT+02:00 Nicolas Lalevée <nicolas.lale...@hibnet.org>: > > > Le 26 juin 2017 à 07:46, Gintautas Grigelionis <g.grigelio...@gmail.com> > a écrit : > > > > If I understand the process correctly, Jenkins executes "ant > > prepare-jenki

Re: Jenkins Jobs of Ivy/IvyDE

2017-06-25 Thread Gintautas Grigelionis
[3]: the path looks wrong, it starts with "\:\:\" [2]: please check that unpacking of drops puts files into the correct places (the contents should go into "features" and "plugins" directories of PDE). Gintas 2017-06-25 16:57 GMT+02:00 Nicolas Lalevée : > Hi, > > I

Re: Jenkins Jobs of Ivy/IvyDE

2017-06-25 Thread Gintautas Grigelionis
2017-06-25 18:23 GMT+02:00 Nicolas Lalevée : > > [2]: please check that unpacking of drops puts files into the correct > > places (the contents should go into "features" and "plugins" directories > of > > PDE). > > I have done that already. I even checked that the

Re: Jenkins Jobs of Ivy/IvyDE

2017-06-25 Thread Gintautas Grigelionis
If I understand the process correctly, Jenkins executes "ant prepare-jenkins" first, which does not work locally any more, because the property used to figure out where to get Ivy jar from is set to an empty string. I wondered what was the reason for that change. Actually, when I look at it again,

Re: Ivy - we have now moved to asciidoc for docs

2017-06-19 Thread Gintautas Grigelionis
SVG is inlined as code, see http://people.apache.org/~hibou/doc/osgi.html Gintas 2017-06-20 0:09 GMT+02:00 Nicolas Lalevée : > > > Le 19 juin 2017 à 08:30, Jan Matèrne (jhm) a écrit : > > > > Doc's mentioning 'how to document' must be updated. > >

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

2017-05-20 Thread Gintautas Grigelionis
, 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: [VOTE] Increase minimum Java version for Ivy to Java7

2017-05-20 Thread Gintautas Grigelionis
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: Ivy - BasicURLHandler ignoring timeout during connection?

2017-05-20 Thread Gintautas Grigelionis
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

2017-05-22 Thread Gintautas Grigelionis
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

2017-05-22 Thread Gintautas Grigelionis
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 website - fixing a Quickstart documentation live

2017-05-24 Thread Gintautas Grigelionis
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: build IvyDE

2017-05-26 Thread Gintautas Grigelionis
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

2017-05-26 Thread Gintautas Grigelionis
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: Ivy website - fixing a Quickstart documentation live

2017-05-25 Thread Gintautas Grigelionis
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 - BasicURLHandler ignoring timeout during connection?

2017-05-21 Thread Gintautas Grigelionis
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 - Goals for the upcoming release?

2017-05-21 Thread Gintautas Grigelionis
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 - Goals for the upcoming release?

2017-05-21 Thread Gintautas Grigelionis
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

Replace emma with jacoco?

2017-05-28 Thread Gintautas Grigelionis
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

2017-05-28 Thread Gintautas Grigelionis
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

2017-05-28 Thread Gintautas Grigelionis
;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

Re: Replace emma with jacoco?

2017-05-29 Thread Gintautas Grigelionis
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: Replace emma with jacoco?

2017-05-29 Thread Gintautas Grigelionis
...@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?

2017-05-29 Thread Gintautas Grigelionis
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: Versioning scheme in Ivy

2017-05-25 Thread Gintautas Grigelionis
> > [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

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

Re: Ivy - BasicURLHandler ignoring timeout during connection?

2017-05-19 Thread Gintautas Grigelionis
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: Minimum Java runtime version for proposed upcoming Ivy release

2017-05-18 Thread Gintautas Grigelionis
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

2017-05-18 Thread Gintautas Grigelionis
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

Versioning scheme in Ivy

2017-05-24 Thread Gintautas Grigelionis
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: Versioning scheme in Ivy

2017-05-24 Thread Gintautas Grigelionis
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 >

Re: PR-33: problems

2017-05-29 Thread Gintautas Grigelionis
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: AW: PR-33: problems

2017-05-29 Thread Gintautas Grigelionis
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: Ivy logo as SVG

2017-06-01 Thread Gintautas Grigelionis
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: AW: Ivy logo as SVG

2017-06-02 Thread Gintautas Grigelionis
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: [antlibs] Break Backwards Compatibility of Ivy Coordinates?

2017-05-31 Thread Gintautas Grigelionis
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?

2017-05-31 Thread Gintautas Grigelionis
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: PR-41: use of fonts

2017-06-03 Thread Gintautas Grigelionis
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

2017-06-03 Thread Gintautas Grigelionis
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: Ant Contrib

2017-06-05 Thread Gintautas Grigelionis
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

Ant Contrib

2017-06-04 Thread Gintautas Grigelionis
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

  1   2   3   4   >