Re: Jenkins Jobs of Ivy/IvyDE

[Jaikiran Pai]

I have now disabled the nightly job[1] and added a note to the job's 
description stating that the latest binaries can be obtained from the other Ivy 
job[2]. 


[1] https://builds.apache.org/job/Ivy-NightlyDistribution/
[2] https://builds.apache.org/job/Ivy/lastSuccessfulBuild/

-Jaikiran
On 29-Jun-2017, at 11:18 AM, Jaikiran Pai  wrote:


On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée  wrote:

> I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
> now the nightly is redundant.


I think yes, the nightly job is now probably redundant - which is fine, we can 
always direct users to this new job for the latest snapshots. The only way this 
job differs from the nightly one now is that the nightly one currently 
publishes the latest (site) docs too. I guess that’s not a big thing since we 
will soon be publishing the latest site docs live on the Ant site (under the 
“master” section).

-Jaikiran


-
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

[Jaikiran Pai]

On 29-Jun-2017, at 3:58 PM, Nicolas Lalevée  wrote:

> 
>> Le 29 juin 2017 à 07:59, Jaikiran Pai  a écrit :
>> 
>> A quick update on this one - I finished off the “settings” sections last 
>> week. There is only one pending item that I’m trying to address in that 
>> section. The “Settings” page[1] has a “Settings File Structure” section 
>> which tries to represent the Ivy settings XML file structure as a tree. We 
>> have a similar one, one place else too (in Ivy file page). We use a source 
>> code block to represent it. However, Asciidoc source code blocks are 
>> rendered literally, so it won’t show up the links (as you’ll see in that 
>> page[1] currently). For the Ivy page, I used “lists” to render the structure 
>> and that was “good enough"[2]. However, I can’t use the same here since 
>> Asciidoc (backed by asciidoctor generator) allows a max list depth of 5 
>> which means that any nested elements that exceed that depth won’t be 
>> rendered correctly as a tree. The settings file structure goes beyond that 
>> depth limit so it doesn’t work out well here.
>> 
>> Ultimately, we either have to remove that section (there’s already a “Child 
>> elements” section which _almost_ conveys the same thing) or come up with a 
>> custom asciidoc “tree” kind of block element to render this. Any thoughts?
> 
> If I count correctly, there are 6 levels. So could we just remove the root 
> element from the tree so we save one level ? The root would be just printed 
> as some text. Could it then display correctly ?
> 

That suggestion actually worked well. I went ahead and did that change and 
regenerated the latest “master” site. It looks good 
http://ant.apache.org/ivy/history/master/settings.html.

-Jaikiran



-
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

[Nicolas Lalevée]

> Le 29 juin 2017 à 07:59, Jaikiran Pai  a écrit :
> 
> A quick update on this one - I finished off the “settings” sections last 
> week. There is only one pending item that I’m trying to address in that 
> section. The “Settings” page[1] has a “Settings File Structure” section which 
> tries to represent the Ivy settings XML file structure as a tree. We have a 
> similar one, one place else too (in Ivy file page). We use a source code 
> block to represent it. However, Asciidoc source code blocks are rendered 
> literally, so it won’t show up the links (as you’ll see in that page[1] 
> currently). For the Ivy page, I used “lists” to render the structure and that 
> was “good enough"[2]. However, I can’t use the same here since Asciidoc 
> (backed by asciidoctor generator) allows a max list depth of 5 which means 
> that any nested elements that exceed that depth won’t be rendered correctly 
> as a tree. The settings file structure goes beyond that depth limit so it 
> doesn’t work out well here.
> 
> Ultimately, we either have to remove that section (there’s already a “Child 
> elements” section which _almost_ conveys the same thing) or come up with a 
> custom asciidoc “tree” kind of block element to render this. Any thoughts?

If I count correctly, there are 6 levels. So could we just remove the root 
element from the tree so we save one level ? The root would be just printed as 
some text. Could it then display correctly ?
If it is too weird, let’s remove that section; the tree is shown in the toc so 
I guess it is OK.

> By the way, I consider the settings section to be “done” in terms of 
> migration. If anyone however notices any discrepancies while doing a quick 
> review of the rendered pages, feel free to drop a mail.
> 
> I’m picking up “OSGi” section next.

And I have done the Ivy files, I’ll review the Ant Tasks section now.

Nicolas

> 
> [1] 
> https://builds.apache.org/view/A/view/Ant/job/Ivy-NightlyDistribution/lastSuccessfulBuild/artifact/build/doc/settings.html
> [2] See “Hierarchical Index” section at 
> https://builds.apache.org/view/A/view/Ant/job/Ivy-NightlyDistribution/lastSuccessfulBuild/artifact/build/doc/ivyfile.html
> 
> -Jaikiran
> 
> On 24-Jun-2017, at 7:18 PM, Nicolas Lalevée  
> wrote:
> 
>> 
>>> 
>>> 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.
> 
> Great. I’ll take care of « Ivy Files ».
> 
> Nicolas
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
> 
> 
> 
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
> 


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

Re: Jenkins Jobs of Ivy/IvyDE

[Nicolas Lalevée]

> Le 29 juin 2017 à 07:48, Jaikiran Pai  a écrit :
> 
> 
> On 25-Jun-2017, at 8:27 PM, Nicolas Lalevée  
> wrote:
> 
>> I have made the Ivy Job also build the snapshot-bin, like the nightly. Maybe 
>> now the nightly is redundant.
> 
> 
> I think yes, the nightly job is now probably redundant - which is fine, we 
> can always direct users to this new job for the latest snapshots. The only 
> way this job differs from the nightly one now is that the nightly one 
> currently publishes the latest (site) docs too. I guess that’s not a big 
> thing since we will soon be publishing the latest site docs live on the Ant 
> site (under the “master” section).

I have done that. For some reason it took a very long time to get actually 
published, but it is there now:
http://ant.apache.org/ivy/history/master/index.html 


I have also update the doc about the site:
http://svn.apache.org/repos/asf/ant/site/README.txt 


Nicolas

[GitHub] ant-ivy pull request #45: Generics + foreach loops and Java 7 in util (excep...

[twogee]

Github user twogee closed the pull request at:

https://github.com/apache/ant-ivy/pull/45


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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

[GitHub] ant-ivy issue #45: Generics + foreach loops and Java 7 in util (except Filte...

[twogee]

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/45
  
I'll put japicmp into a separate PR


---
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 enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---

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