Re: Ivy jobs on Teamcity need reconfiguring

[Stefan Bodewig]

On 2017-06-20, Nicolas Lalevée wrote:

>> Le 19 juin 2017 à 13:02, Stefan Bodewig  a écrit :

>> On 2017-06-19, Jaikiran Pai wrote:

>>> I was reading up some docs and happened to find this page
>>> http://ant.apache.org/nightlies.html which lists the Ant/Ivy
>>> jobs. Turns out we also have Teamcity builds for Ivy and they have
>>> been failing since we moved to Java 1.7[1].

>> Are we maintaining the job ourselves? Jan, have you got access to the
>> credentials?

> The credentials have been shared the 23 september 2008 on ant-private.

Ahh, found them, thanks.

I've reconfigured all Ivy jobs to use JDK 1.7 now.

>> Is this job doing anything that we couldn't do with builds.apache.org by
>> now?

> I don’t think so.

Then I'd suggest migrating them to our own infrastructure.

Stefan

-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy jobs on Teamcity need reconfiguring

[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: Ivy jobs on Teamcity need reconfiguring

[Vladislav Rassokhin]

Hi,

AFAIK Xavier Hanin has Project Administrator role for 'Apache Ivy' project
on teamcity.jetbrains.com.
Could share access with Stefan or someone else.

Also changed configuration a bit (something were left after svn -> git
migration).

2017-06-20 15:10 GMT+03:00 Nicolas Lalevée :

>
> > Le 19 juin 2017 à 13:02, Stefan Bodewig  a écrit :
> >
> > On 2017-06-19, Jaikiran Pai wrote:
> >
> >> I was reading up some docs and happened to find this page
> >> http://ant.apache.org/nightlies.html which lists the Ant/Ivy
> >> jobs. Turns out we also have Teamcity builds for Ivy and they have
> >> been failing since we moved to Java 1.7[1].
> >
> > Are we maintaining the job ourselves? Jan, have you got access to the
> > credentials?
>
> The credentials have been shared the 23 september 2008 on ant-private.
>
> > Is this job doing anything that we couldn't do with builds.apache.org by
> > now?
>
> I don’t think so.
>
> Nicolas
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Ivy jobs on Teamcity need reconfiguring

[Nicolas Lalevée]

> Le 19 juin 2017 à 13:02, Stefan Bodewig  a écrit :
> 
> On 2017-06-19, Jaikiran Pai wrote:
> 
>> I was reading up some docs and happened to find this page
>> http://ant.apache.org/nightlies.html which lists the Ant/Ivy
>> jobs. Turns out we also have Teamcity builds for Ivy and they have
>> been failing since we moved to Java 1.7[1].
> 
> Are we maintaining the job ourselves? Jan, have you got access to the
> credentials?

The credentials have been shared the 23 september 2008 on ant-private.

> Is this job doing anything that we couldn't do with builds.apache.org by
> now?

I don’t think so.

Nicolas


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

Re: Ivy 2.5 and generics

[Gintautas Grigelionis]

I left out the generification of Filter, because NoFilter is a singleton.
I'll be leaving out attribute Maps (global or local), because their values
can be Strings or Matchers (this is where the story with IvyDE started, I
was not sure what to expect from one such Map).

Anything else that is pretty unambiguous can be generified just to clear
out the room. Once that is done, the remaining cases must be thoroughly
discussed. I added binary compatibility checks to stress the point that
generification does not break binary compatibility as long as erasures stay
the same.

Gintas

2017-06-20 13:35 GMT+02:00 Jaikiran Pai :

> Gintas, can you list the exact nature of changes for some specific classes
> that you think this effort might involve? I know you already sent me some
> samples, but it would be good if the rest know what kind of changes are
> involved.
>
> Personally, my opinion on this is - if it’s internal implementation
> details that this change involves (like private fields or methods of
> certain classes), it’s fine to do that in the upcoming release. But if it’s
> more than that, then IMO, we should hold 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
>
> On 19-Jun-2017, at 10:12 AM, Gintautas Grigelionis <
> g.grigelio...@gmail.com> wrote:
>
> During a discussion about goals for Ivy 2.5, I mentioned generics [1].
> I was looking into the matter because I was investigating how IvyDE hooks
> into Ivy and I didn't quite like what I saw.
> I'd like to generify Ivy as much as possible for 2.5 (staying binary
> compatible, of course) so that decisions for the next release could be more
> informed.
>
> Should you agree, I'd finish the work with two more commits (one for core
> and one for plugins package) -- I pushed two commits already that ended up
> in PR #45.
>
> Now, I'll digress, but I believe it's worth mentioning. Apart from
> generics, there's one last thing I'd like to have in Ivy 2.5, and that's
> SVG in Ivy reports. I only heard one opinion (which was positive) about the
> non-limbless ant in vectorised Ivy logo, and no protests, so I take it as a
> silent approval :-) BTW I hope asciidoc can inline SVG in HTML, although
> some repeating icons would better be placed in CSS (as mentioned in
> comments to PR #39).
>
> [1]
> http://mail-archives.apache.org/mod_mbox/ant-dev/201705.mbox/%
> 3CCALVNWHXiZPVJmKimTB9Qxo9u6%2BNX%2Br7Kpmk3uvZvqtUxLQpekQ%
> 40mail.gmail.com%3E
>
> Gintas
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

Re: Ivy 2.5 and generics

[Jaikiran Pai]

Gintas, can you list the exact nature of changes for some specific classes that 
you think this effort might involve? I know you already sent me some samples, 
but it would be good if the rest know what kind of changes are involved.

Personally, my opinion on this is - if it’s internal implementation details 
that this change involves (like private fields or methods of certain classes), 
it’s fine to do that in the upcoming release. But if it’s more than that, then 
IMO, we should hold 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

On 19-Jun-2017, at 10:12 AM, Gintautas Grigelionis  
wrote:

During a discussion about goals for Ivy 2.5, I mentioned generics [1].
I was looking into the matter because I was investigating how IvyDE hooks
into Ivy and I didn't quite like what I saw.
I'd like to generify Ivy as much as possible for 2.5 (staying binary
compatible, of course) so that decisions for the next release could be more
informed.

Should you agree, I'd finish the work with two more commits (one for core
and one for plugins package) -- I pushed two commits already that ended up
in PR #45.

Now, I'll digress, but I believe it's worth mentioning. Apart from
generics, there's one last thing I'd like to have in Ivy 2.5, and that's
SVG in Ivy reports. I only heard one opinion (which was positive) about the
non-limbless ant in vectorised Ivy logo, and no protests, so I take it as a
silent approval :-) BTW I hope asciidoc can inline SVG in HTML, although
some repeating icons would better be placed in CSS (as mentioned in
comments to PR #39).

[1]
http://mail-archives.apache.org/mod_mbox/ant-dev/201705.mbox/%3CCALVNWHXiZPVJmKimTB9Qxo9u6%2BNX%2Br7Kpmk3uvZvqtUxLQpekQ%40mail.gmail.com%3E

Gintas


-
To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
For additional commands, e-mail: dev-h...@ant.apache.org

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

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

> >
> > On 20-Jun-2017, at 3:38 AM, Nicolas Lalevée 
> wrote:
> >
> >
> >> Le 19 juin 2017 à 04:52, Jaikiran Pai  a
> écrit :
> >>
> >> The documentation for ant-ivy project has now been migrated to
> asciidoc. The migration used a tool developed by Nicolas to migrate the
> xooki backed HTML docs to asciidoc. This tool auto-generated the asciidoc
> text and for most part no other changes were needed. However, there are
> some fixes the generated asciidoc will need which I’m doing and will
> continue to do in the coming days to fix any issues with the generated doc.
> Once the fixes are done, soon, we’ll remove the xooki backed documentation
> completely from our git repo. For now though, any new documentation or
> changes should go into the asciidoc files.
> >
> > I did a general grep about finding non translated html markup, and I
> have cleaned the ones I have found.
> > I have pushed the result here: http://people.apache.org/~hibou/doc/ <
> http://people.apache.org/~hibou/doc/>
> >
> > Probably we can start pushing it to the site, since there is section
> dedicated to the trunk version of the doc (which should be probably renamed
> master).
> > http://ant.apache.org/ivy/history/trunk/index.html <
> http://ant.apache.org/ivy/history/trunk/index.html>
> > It would be an opportunity to get an idea of what would it mean when a
> release will happen.
>
> I actually forgot to send a mail yesterday, but I setup our nightly Ivy
> job on Jenkins to publish the latest generated docs as build artifact so
> that it gives everyone a chance to view/review it. It’s here
> https://builds.apache.org/view/A/view/Ant/job/Ivy-NightlyDistribution/
> lastSuccessfulBuild/artifact/build/. We could just push it to the site
> under master but I wasn’t too sure if it’s the right time to do that or if
> we should just cleanup the rest of the issues in the doc before starting to
> push it there.
>
> >
> > And just an idea: since there are a lot of pages, maybe we could
> organize a review at many, without useless double checks. I see 4 big parts
> in the doc: the ant tasks, the pages related to the ivy file, the pages
> related to the ivysettings, and the other pages. If 4 volunteers can do a
> quick review of each page, I think we can be pretty confident that we
> didn’t leave any ugliness somewhere. The goal wouldn’t to do a fine grain
> review, but ensure that everything is readable. wdyt ?
> >
>
> Sounds a good idea. I’ll start off with the “Settings” which relates to
> the Ivy settings file.
>
> -Jaikiran
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>