Re: Ivy website - fixing a Quickstart documentation live

[J Pai]

So I got this site generation working locally (had to fix a xooki script to 
make it work with Nashorn. The attached patch includes the fix). 

At this point, I need help to commit the newly generated doc fixes to the SVN. 
I’ve attached a patch file for it and will explain what it is doing.

The changes/patch relates to _one_ of the more important issues noted in the 
JIRA https://issues.apache.org/jira/browse/IVY-1542. That JIRA lists more than 
one issue with the latest docs. However, the missing .png and .css don’t 
directly contribute to anything noticeable, so I haven’t included it in this 
patch (and probably will look into it separately). The issue that this patch 
fixes is the more important one:

> Code examples are missing. About 2/3 of the way down the page are two code 
> examples that are rendering as just a black rectangle for me. The underlying 
> html looks like it has  tags with no content.


The way these tutorial docs are generated, during the build, it triggers the 
build of quickstart examples and dumps the logs into files. The log files are 
then referred to via xooki references and the contents of those log files are 
inlined within the div tags. So I went ahead and built these tutorials on 2.4.0 
tag of Ivy project, generated those logs and then regenerated the site with 
these logs in the relevant folder. The generated documentation now has these 
output inlined correctly in the quickstart and various other docs.

The attached patch was generated with 
https://svn.apache.org/repos/asf/ant/site/ as the root of the SVN checkout. So 
whoever is applying the patch will have to cd to that directory and then apply 
it. Let me know if you run into issues or if any changes are necessary in this 
patch.

As for the other two issues noted in that JIRA, I’m planning to remove 
references to the non-existent .css and .png files and submit that as a 
separate patch.

-Jaikiran






On 26-May-2017, at 10:39 AM, J Pai  wrote:

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 Lalevée  wrote:

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 there are 
ant tasks to run to the fetch of the sources. I have found an old discussion 
[1] we had about it which should help you.

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 I 
have a commit which for some reason I didn’t pushed. If we are still 
interested, I can revive this.

Nicolas

[1] 
http://ant.1045680.n5.nabble.com/stuck-with-site-generation-issue-for-ivy-td5715758.html
 

[2] https://github.com/apache/ant-ivy/tree/xooki2asciidoc 



> Le 25 mai 2017 à 06:12, J Pai  a écrit :
> 
> What would be the process of having the live docs of Ivy project updated to 
> fix/update an issue in the documentation[1]? 
> 
> The quickstart documentation refers to certain log files that get 
> auto-generated during the doc build process. It looks like those log files 
> weren’t uploaded and are resulting in a blank text area showing up. I can run 
> the doc generation target locally (on 2.4.0 tag) and have someone upload 
> those files and see if shows up fine.
> 
> [1] https://issues.apache.org/jira/browse/IVY-1542
> 
> -Jaikiran
> -
> 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

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

[janmaterne]

Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivy/pull/31
  
Nice idea to use the old fail-Message as new method comment to document why 
the exception is expected.


---
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 #31: Convert tests to JUnit 4, clean up code

[janmaterne]

Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivy/pull/31
  
merged, thanks


---
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 pull request #31: Convert tests to JUnit 4, clean up code

[asfgit]

Github user asfgit closed the pull request at:

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


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

IVY-1485, resolve report and resolved versions

[Nicolas Lalevée]

After some digging, I found out that the resolved revisions property file is 
very old (git is awesome, even better within sourcetree). It is so old that at 
that time the xml resolve report didn’t exist. And this property file seems to 
have been created just in order to make the deliver task work [1]. And a 
comment still state this too [2]. And the purpose of the lines from 248 to 326 
are about to compute these versions and write them down, it can be extracted in 
a function without side effect.

So most probably this property file is redundant with the xml resolve report. 
But the thing is the resolve may not be produced, it is an option [3], 
defaulting to true [4].

Two options:
- continue to support the property file and correctly produce it to fix 
IVY-1485 [5].
- drop this property file, make the xml report always produced, and make the 
deliver read the report rather than the property file.

Makes sense ?

Nicolas

[1] 
https://github.com/apache/ant-ivy/commit/3081a1b16a2fcb13b7a13bf761d6a625598d0325
 

[2] 
https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveEngine.java#L247
 

[3] 
https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveEngine.java#L338
 

[4] 
https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveOptions.java#L99
 

[5] https://issues.apache.org/jira/browse/IVY-1485 

> Le 25 mai 2017 à 12:11, Nicolas Lalevée  a écrit :
> 
> 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 myself too while reading the code.
> 
> Nicolas
> 
>> Le 22 mai 2017 à 07:37, J Pai  a écrit :
>> 
>> One other thing about this issue - this is reproducible (as shown in the 
>> test case) with static revisions too and isn’t specific to any dynamic 
>> revision resolution.
>> 
>> -Jaikiran
>> On 22-May-2017, at 11:02 AM, J Pai  wrote:
>> 
>> I have had a look at that issue, this last week and I have been able to 
>> reproduce it in a simple test case[1]. I kind of understand what the issue 
>> is in there, but given my lack of knowledge of the Ivy codebase, I haven’t 
>> been able to figure how to fix this correctly. In fact, this issue is what 
>> prompted me to ask this question [2] in the dev list a day or so back, since 
>> basically comes down to those files. Here’s my understanding of the problem 
>> (backed by that test case[1] which reproduces it).
>> 
>> Imagine you have a module org:hello-world and imagine it has 2 
>> configurations conf1 and conf2. Now consider the case where this hello-world 
>> module depends on org:module1:1.0 in conf1 (a direct dependency) and on 
>> org:module2:1.0 in conf2 (a direct dependency). That translates to a module 
>> descriptor like:
>> 
>> 
>>  >module="hello-world"
>>revision="1.2.3"
>> 
>>  />
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>>  
>> 
>> 
>> Now take this one step further and consider that org:module2:1.0 (that 
>> hello-world depends on, in conf2) has a dependency of its own on 
>> org:module1:2.0. So module2’s module descriptor looks like:
>> 
>> 
>> >   module="module2"
>>   revision="1.0"
>> />
>>  
>>  
>>  
>> 
>>  
>> 
>> 
>> 
>> So ultimately, when you resolve the hello-world module, you expect it to 
>> have org:module1:1.0 as an dependency in conf1 and org:module1:2.0 as an 
>> dependency in conf2 (transitively via org:module2:1.0).
>> 
>> Does the resolve work as expected for this use case? Yes it does and the 
>> resolution pulls in the right set of dependencies in the right 
>> configurations. Internally it creates resolution report (as an xml) plus a 
>> resolution properties file for this resolution. No (obvious/apparent) issues 
>> at this point. 
>> 
>> Now, let’s say a “deliver” is triggered against this resolution, for conf1. 
>> What I would expect is, that it would deliver a file for hello-world which 
>> then has a dependency on org:module1:1.0 in conf1 (because that’s what it 
>> was correctly resolved to previously). However, the delivered file instead 
>> has a dependency on org:module1:2.0 in conf1 and I believe that’s the issue 
>> being reported in that JIRA.
>> 
>> So is this a bug in the deliver task itself? I don’t think so. So far what I 
>> have narrowed it down to is that the 

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

[asfgit]

Github user asfgit 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 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 #20: Fix IVY-1522

[nlalevee]

Github user nlalevee commented on the issue:

https://github.com/apache/ant-ivy/pull/20
  
merged. Thank both of you.


---
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 #31: Convert tests to JUnit 4, clean up code

[nlalevee]

Github user nlalevee commented on the issue:

https://github.com/apache/ant-ivy/pull/31
  
@twogee to properly add you to the list of contributors, do you confirm you 
are 
Gintautas Grigelionis ?


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

Re: IVY-1485, resolve report and resolved versions

[J Pai]

Thank you very much Nicolas for digging more into this and getting hold of 
these details. What you explain, backed by the details, makes clear sense.

I will attempt to go with this option that you suggest:

> - drop this property file, make the xml report always produced, and make the 
> deliver read the report rather than the property file.

From looking at the code and documentation, the option that decides whether to 
create the XML report seems to be an internal only option (in Ivy 2.x world) 
i.e. not exposed or documented as something that the user can fiddle with. 
That’s a good thing since removing it or fiddling with its semantics, won’t 
affect the users.

P.S: I don’t mean to step on your toes here if you were planning to work on 
this. If not, I’ll gladly try and come up with the suggested fix.

-Jaikiran


On 26-May-2017, at 2:20 PM, Nicolas Lalevée  wrote:

After some digging, I found out that the resolved revisions property file is 
very old (git is awesome, even better within sourcetree). It is so old that at 
that time the xml resolve report didn’t exist. And this property file seems to 
have been created just in order to make the deliver task work [1]. And a 
comment still state this too [2]. And the purpose of the lines from 248 to 326 
are about to compute these versions and write them down, it can be extracted in 
a function without side effect.

So most probably this property file is redundant with the xml resolve report. 
But the thing is the resolve may not be produced, it is an option [3], 
defaulting to true [4].

Two options:
- continue to support the property file and correctly produce it to fix 
IVY-1485 [5].
- drop this property file, make the xml report always produced, and make the 
deliver read the report rather than the property file.

Makes sense ?

Nicolas

[1] 
https://github.com/apache/ant-ivy/commit/3081a1b16a2fcb13b7a13bf761d6a625598d0325
 

[2] 
https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveEngine.java#L247
 

[3] 
https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveEngine.java#L338
 

[4] 
https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveOptions.java#L99
 

[5] https://issues.apache.org/jira/browse/IVY-1485 

> Le 25 mai 2017 à 12:11, Nicolas Lalevée  a écrit :
> 
> 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 myself too while reading the code.
> 
> Nicolas
> 
>> Le 22 mai 2017 à 07:37, J Pai  a écrit :
>> 
>> One other thing about this issue - this is reproducible (as shown in the 
>> test case) with static revisions too and isn’t specific to any dynamic 
>> revision resolution.
>> 
>> -Jaikiran
>> On 22-May-2017, at 11:02 AM, J Pai  wrote:
>> 
>> I have had a look at that issue, this last week and I have been able to 
>> reproduce it in a simple test case[1]. I kind of understand what the issue 
>> is in there, but given my lack of knowledge of the Ivy codebase, I haven’t 
>> been able to figure how to fix this correctly. In fact, this issue is what 
>> prompted me to ask this question [2] in the dev list a day or so back, since 
>> basically comes down to those files. Here’s my understanding of the problem 
>> (backed by that test case[1] which reproduces it).
>> 
>> Imagine you have a module org:hello-world and imagine it has 2 
>> configurations conf1 and conf2. Now consider the case where this hello-world 
>> module depends on org:module1:1.0 in conf1 (a direct dependency) and on 
>> org:module2:1.0 in conf2 (a direct dependency). That translates to a module 
>> descriptor like:
>> 
>> 
>> >   module="hello-world"
>>   revision="1.2.3"
>> 
>> />
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> Now take this one step further and consider that org:module2:1.0 (that 
>> hello-world depends on, in conf2) has a dependency of its own on 
>> org:module1:2.0. So module2’s module descriptor looks like:
>> 
>> 
>> >  module="module2"
>>  revision="1.0"
>> />
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> 
>> So ultimately, when you resolve the hello-world module, you expect it to 
>> have org:module1:1.0 as an dependency in conf1 and org:module1:2.0 as an 
>> dependency in conf2 (transitively via org:module2:1.0).
>> 
>> Does the 

Re: IVY-1485, resolve report and resolved versions

[Nicolas Lalevée]

> Le 26 mai 2017 à 13:23, J Pai  a écrit :
> 
> Thank you very much Nicolas for digging more into this and getting hold of 
> these details. What you explain, backed by the details, makes clear sense.
> 
> I will attempt to go with this option that you suggest:
> 
>> - drop this property file, make the xml report always produced, and make the 
>> deliver read the report rather than the property file.
> 
> From looking at the code and documentation, the option that decides whether 
> to create the XML report seems to be an internal only option (in Ivy 2.x 
> world) i.e. not exposed or documented as something that the user can fiddle 
> with. That’s a good thing since removing it or fiddling with its semantics, 
> won’t affect the users.

ha, ok. good then.

> P.S: I don’t mean to step on your toes here if you were planning to work on 
> this. If not, I’ll gladly try and come up with the suggested fix.

Please, be my guest.

Nicolas

> 
> -Jaikiran
> 
> 
> On 26-May-2017, at 2:20 PM, Nicolas Lalevée  
> wrote:
> 
> After some digging, I found out that the resolved revisions property file is 
> very old (git is awesome, even better within sourcetree). It is so old that 
> at that time the xml resolve report didn’t exist. And this property file 
> seems to have been created just in order to make the deliver task work [1]. 
> And a comment still state this too [2]. And the purpose of the lines from 248 
> to 326 are about to compute these versions and write them down, it can be 
> extracted in a function without side effect.
> 
> So most probably this property file is redundant with the xml resolve report. 
> But the thing is the resolve may not be produced, it is an option [3], 
> defaulting to true [4].
> 
> Two options:
> - continue to support the property file and correctly produce it to fix 
> IVY-1485 [5].
> - drop this property file, make the xml report always produced, and make the 
> deliver read the report rather than the property file.
> 
> Makes sense ?
> 
> Nicolas
> 
> [1] 
> https://github.com/apache/ant-ivy/commit/3081a1b16a2fcb13b7a13bf761d6a625598d0325
>  
> 
> [2] 
> https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveEngine.java#L247
>  
> 
> [3] 
> https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveEngine.java#L338
>  
> 
> [4] 
> https://github.com/apache/ant-ivy/blob/master/src/java/org/apache/ivy/core/resolve/ResolveOptions.java#L99
>  
> 
> [5] https://issues.apache.org/jira/browse/IVY-1485 
> 
>> Le 25 mai 2017 à 12:11, Nicolas Lalevée  a écrit 
>> :
>> 
>> 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 myself too while reading the code.
>> 
>> Nicolas
>> 
>>> Le 22 mai 2017 à 07:37, J Pai  a écrit :
>>> 
>>> One other thing about this issue - this is reproducible (as shown in the 
>>> test case) with static revisions too and isn’t specific to any dynamic 
>>> revision resolution.
>>> 
>>> -Jaikiran
>>> On 22-May-2017, at 11:02 AM, J Pai  wrote:
>>> 
>>> I have had a look at that issue, this last week and I have been able to 
>>> reproduce it in a simple test case[1]. I kind of understand what the issue 
>>> is in there, but given my lack of knowledge of the Ivy codebase, I haven’t 
>>> been able to figure how to fix this correctly. In fact, this issue is what 
>>> prompted me to ask this question [2] in the dev list a day or so back, 
>>> since basically comes down to those files. Here’s my understanding of the 
>>> problem (backed by that test case[1] which reproduces it).
>>> 
>>> Imagine you have a module org:hello-world and imagine it has 2 
>>> configurations conf1 and conf2. Now consider the case where this 
>>> hello-world module depends on org:module1:1.0 in conf1 (a direct 
>>> dependency) and on org:module2:1.0 in conf2 (a direct dependency). That 
>>> translates to a module descriptor like:
>>> 
>>> 
>>> >>  module="hello-world"
>>>  revision="1.2.3"
>>> 
>>> />
>>> 
>>>
>>>
>>> 
>>> 
>>>
>>>
>>> 
>>> 
>>> 
>>> Now take this one step further and consider that org:module2:1.0 (that 
>>> hello-world depends on, in conf2) has a dependency of its own on 
>>> org:module1:2.0. So module2’s module descriptor looks like:
>>> 
>>> 
>>> >> module="module2"
>>> revision="

[GitHub] ant-ivy pull request #32: A few loose bits in JUnit 4 migration

[twogee]

GitHub user twogee opened a pull request:

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

A few loose bits in JUnit 4 migration

This adds annotations that are missing, migrates example code and fixes 
whitespace

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/twogee/ant-ivy master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/ant-ivy/pull/32.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #32


commit fbbf092e4986635703bf9a3bfd57d4f639c86095
Author: twogee 
Date:   2017-05-26T12:00:16Z

A few loose bits in JUnit 4 migration




---
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 #32: A few loose bits in JUnit 4 migration

[twogee]

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/32
  
Why is Jenkins lacking org.apache.tools.ant.util.ProcessUtil? Something 
wrong with Ant?


---
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 #31: Convert tests to JUnit 4, clean up code

[twogee]

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/31
  
I do 😃


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

build IvyDE

[Jan Matèrne]

I tried to get the IvyDE build working.

Finally I am getting a 

 

[eclipse.buildScript] Some inter-plug-in dependencies have not been
satisfied.

[eclipse.buildScript] Bundle org.apache.ivyde.eclipse.resolvevisualizer:

[eclipse.buildScript]   Missing required plug-in
org.eclipse.zest.core_[1.2.0,2.0.0).

[eclipse.buildScript]   Missing required plug-in
org.eclipse.zest.layouts_[1.1.0,2.0.0).

 

I could download zest via "ant hudson-get-zest"

 

hudson-get-zest:

  [get] Getting:
http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drop
s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://carroll.aset.psu.edu/pub
/eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-zest-3.6.2.zip&mi
rror_id=546

  [get] To:
C:\projekte\apache-ant\ivy-ivyde\dependencies\GEF-zest-3.6.2.zip

  [get]
http://www.eclipse.org/downloads/download.php?file=/tools/gef/downloads/drop
s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://carroll.aset.psu.edu/pub
/eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-zest-3.6.2.zip&mi
rror_id=546 moved to
http://archive.eclipse.org/tools/gef/downloads/drops/3.6.2/R201102251600/GEF
-zest-3.6.2.zip

  [get] ...

 

BUILD SUCCESSFUL

Total time: 5 seconds

 

 

Some ideas?

 

 

Jan

Re: build IvyDE

[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
build and update build properties.

Gintas

2017-05-26 14:53 GMT+02:00 Jan Matèrne :

> I tried to get the IvyDE build working.
>
> Finally I am getting a
>
>
>
> [eclipse.buildScript] Some inter-plug-in dependencies have not been
> satisfied.
>
> [eclipse.buildScript] Bundle org.apache.ivyde.eclipse.resolvevisualizer:
>
> [eclipse.buildScript]   Missing required plug-in
> org.eclipse.zest.core_[1.2.0,2.0.0).
>
> [eclipse.buildScript]   Missing required plug-in
> org.eclipse.zest.layouts_[1.1.0,2.0.0).
>
>
>
> I could download zest via "ant hudson-get-zest"
>
>
>
> hudson-get-zest:
>
>   [get] Getting:
> http://www.eclipse.org/downloads/download.php?file=/
> tools/gef/downloads/drop
> s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://
> carroll.aset.psu.edu/pub
> /eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-
> zest-3.6.2.zip&mi
> rror_id=546
>
>   [get] To:
> C:\projekte\apache-ant\ivy-ivyde\dependencies\GEF-zest-3.6.2.zip
>
>   [get]
> http://www.eclipse.org/downloads/download.php?file=/
> tools/gef/downloads/drop
> s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://
> carroll.aset.psu.edu/pub
> /eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-
> zest-3.6.2.zip&mi
> rror_id=546 moved to
> http://archive.eclipse.org/tools/gef/downloads/drops/3.6.
> 2/R201102251600/GEF
> -zest-3.6.2.zip
>
>   [get] ...
>
>
>
> BUILD SUCCESSFUL
>
> Total time: 5 seconds
>
>
>
>
>
> Some ideas?
>
>
>
>
>
> Jan
>
>

Re: build IvyDE

[Nicolas Lalevée]

It has been ages since I have done a build of Eclipse, but like Gintas wrote, 
there is something wrong with your Eclipse install you are building against, it 
is missing zest.
I don’t know if you have seen but there is a piece of documentation about 
building IvyDE there:
http://ant.apache.org/ivy/ivyde/history/latest-milestone/dev/build.html 


The hudson-prepare ant task is about what is described in that doc: download 
stuff and setup the baseLocation property.

Nicolas

> Le 26 mai 2017 à 16:50, Gintautas Grigelionis  a 
> écrit :
> 
> 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
> build and update build properties.
> 
> Gintas
> 
> 2017-05-26 14:53 GMT+02:00 Jan Matèrne :
> 
>> I tried to get the IvyDE build working.
>> 
>> Finally I am getting a
>> 
>> 
>> 
>> [eclipse.buildScript] Some inter-plug-in dependencies have not been
>> satisfied.
>> 
>> [eclipse.buildScript] Bundle org.apache.ivyde.eclipse.resolvevisualizer:
>> 
>> [eclipse.buildScript]   Missing required plug-in
>> org.eclipse.zest.core_[1.2.0,2.0.0).
>> 
>> [eclipse.buildScript]   Missing required plug-in
>> org.eclipse.zest.layouts_[1.1.0,2.0.0).
>> 
>> 
>> 
>> I could download zest via "ant hudson-get-zest"
>> 
>> 
>> 
>> hudson-get-zest:
>> 
>>  [get] Getting:
>> http://www.eclipse.org/downloads/download.php?file=/
>> tools/gef/downloads/drop
>> s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://
>> carroll.aset.psu.edu/pub
>> /eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-
>> zest-3.6.2.zip&mi
>> rror_id=546
>> 
>>  [get] To:
>> C:\projekte\apache-ant\ivy-ivyde\dependencies\GEF-zest-3.6.2.zip
>> 
>>  [get]
>> http://www.eclipse.org/downloads/download.php?file=/
>> tools/gef/downloads/drop
>> s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://
>> carroll.aset.psu.edu/pub
>> /eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-
>> zest-3.6.2.zip&mi
>> rror_id=546 moved to
>> http://archive.eclipse.org/tools/gef/downloads/drops/3.6.
>> 2/R201102251600/GEF
>> -zest-3.6.2.zip
>> 
>>  [get] ...
>> 
>> 
>> 
>> BUILD SUCCESSFUL
>> 
>> Total time: 5 seconds
>> 
>> 
>> 
>> 
>> 
>> Some ideas?
>> 
>> 
>> 
>> 
>> 
>> Jan
>> 
>> 

Re: Ivy website - fixing a Quickstart documentation live

[Matt Sicker]

Can't you run the original Ruby asciidoc parser via JRuby, too?

On 26 May 2017 at 02:06, J Pai  wrote:

> So I got this site generation working locally (had to fix a xooki script
> to make it work with Nashorn. The attached patch includes the fix).
>
> At this point, I need help to commit the newly generated doc fixes to the
> SVN. I’ve attached a patch file for it and will explain what it is doing.
>
> The changes/patch relates to _one_ of the more important issues noted in
> the JIRA https://issues.apache.org/jira/browse/IVY-1542. That JIRA lists
> more than one issue with the latest docs. However, the missing .png and
> .css don’t directly contribute to anything noticeable, so I haven’t
> included it in this patch (and probably will look into it separately). The
> issue that this patch fixes is the more important one:
>
> > Code examples are missing. About 2/3 of the way down the page are two
> code examples that are rendering as just a black rectangle for me. The
> underlying html looks like it has  tags with no content.
>
>
> The way these tutorial docs are generated, during the build, it triggers
> the build of quickstart examples and dumps the logs into files. The log
> files are then referred to via xooki references and the contents of those
> log files are inlined within the div tags. So I went ahead and built these
> tutorials on 2.4.0 tag of Ivy project, generated those logs and then
> regenerated the site with these logs in the relevant folder. The generated
> documentation now has these output inlined correctly in the quickstart and
> various other docs.
>
> The attached patch was generated with https://svn.apache.org/repos/
> asf/ant/site/ as the root of the SVN checkout. So whoever is applying the
> patch will have to cd to that directory and then apply it. Let me know if
> you run into issues or if any changes are necessary in this patch.
>
> As for the other two issues noted in that JIRA, I’m planning to remove
> references to the non-existent .css and .png files and submit that as a
> separate patch.
>
> -Jaikiran
>
>
>
>
>
>
>
> On 26-May-2017, at 10:39 AM, J Pai  wrote:
>
> 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 Lalevée 
> wrote:
>
> 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 there are ant tasks to run to the fetch of the sources. I have found an
> old discussion [1] we had about it which should help you.
>
> 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 I have a commit which for some reason I didn’t pushed. If
> we are still interested, I can revive this.
>
> Nicolas
>
> [1] http://ant.1045680.n5.nabble.com/stuck-with-site-
> generation-issue-for-ivy-td5715758.html  com/stuck-with-site-generation-issue-for-ivy-td5715758.html>
> [2] https://github.com/apache/ant-ivy/tree/xooki2asciidoc <
> https://github.com/apache/ant-ivy/tree/xooki2asciidoc>
>
>
> > Le 25 mai 2017 à 06:12, J Pai  a écrit :
> >
> > What would be the process of having the live docs of Ivy project updated
> to fix/update an issue in the documentation[1]?
> >
> > The quickstart documentation refers to certain log files that get
> auto-generated during the doc build process. It looks like those log files
> weren’t uploaded and are resulting in a blank text area showing up. I can
> run the doc generation target locally (on 2.4.0 tag) and have someone
> upload those files and see if shows up fine.
> >
> > [1] https://issues.apache.org/jira/browse/IVY-1542
> >
> > -Jaikiran
> > -
> > 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
>



-- 
Matt Sicker 

[GitHub] ant-ivy issue #32: A few loose bits in JUnit 4 migration

[nlalevee]

Github user nlalevee commented on the issue:

https://github.com/apache/ant-ivy/pull/32
  
The job was configure to use the default Ant, which I don't know which is 
exactly. So I have changed the conf to use Ant 1.9.9 (the same version that the 
one declared in the ivy.xml of Ivy).
A new build is coming.


---
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 #32: A few loose bits in JUnit 4 migration

[twogee]

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/32
  
Unless I'm mistaken, `BuildFileRule` was available first in 1.9.5; 
`ProcessUtil` needs 1.9.4


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

Re: Ivy website - fixing a Quickstart documentation live

[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 26 May 2017 at 02:06, J Pai  wrote:
>
> > So I got this site generation working locally (had to fix a xooki script
> > to make it work with Nashorn. The attached patch includes the fix).
> >
> > At this point, I need help to commit the newly generated doc fixes to the
> > SVN. I’ve attached a patch file for it and will explain what it is doing.
> >
> > The changes/patch relates to _one_ of the more important issues noted in
> > the JIRA https://issues.apache.org/jira/browse/IVY-1542. That JIRA lists
> > more than one issue with the latest docs. However, the missing .png and
> > .css don’t directly contribute to anything noticeable, so I haven’t
> > included it in this patch (and probably will look into it separately).
> The
> > issue that this patch fixes is the more important one:
> >
> > > Code examples are missing. About 2/3 of the way down the page are two
> > code examples that are rendering as just a black rectangle for me. The
> > underlying html looks like it has  tags with no content.
> >
> >
> > The way these tutorial docs are generated, during the build, it triggers
> > the build of quickstart examples and dumps the logs into files. The log
> > files are then referred to via xooki references and the contents of those
> > log files are inlined within the div tags. So I went ahead and built
> these
> > tutorials on 2.4.0 tag of Ivy project, generated those logs and then
> > regenerated the site with these logs in the relevant folder. The
> generated
> > documentation now has these output inlined correctly in the quickstart
> and
> > various other docs.
> >
> > The attached patch was generated with https://svn.apache.org/repos/
> > asf/ant/site/ as the root of the SVN checkout. So whoever is applying the
> > patch will have to cd to that directory and then apply it. Let me know if
> > you run into issues or if any changes are necessary in this patch.
> >
> > As for the other two issues noted in that JIRA, I’m planning to remove
> > references to the non-existent .css and .png files and submit that as a
> > separate patch.
> >
> > -Jaikiran
> >
> >
> >
> >
> >
> >
> >
> > On 26-May-2017, at 10:39 AM, J Pai  wrote:
> >
> > 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 Lalevée 
> > wrote:
> >
> > 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 there are ant tasks to run to the fetch of the sources. I have found
> an
> > old discussion [1] we had about it which should help you.
> >
> > 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 I have a commit which for some reason I didn’t pushed.
> If
> > we are still interested, I can revive this.
> >
> > Nicolas
> >
> > [1] http://ant.1045680.n5.nabble.com/stuck-with-site-
> > generation-issue-for-ivy-td5715758.html  > com/stuck-with-site-generation-issue-for-ivy-td5715758.html>
> > [2] https://github.com/apache/ant-ivy/tree/xooki2asciidoc <
> > https://github.com/apache/ant-ivy/tree/xooki2asciidoc>
> >
> >
> > > Le 25 mai 2017 à 06:12, J Pai  a écrit :
> > >
> > > What would be the process of having the live docs of Ivy project
> updated
> > to fix/update an issue in the documentation[1]?
> > >
> > > The quickstart documentation refers to certain log files that get
> > auto-generated during the doc build process. It looks like those log
> files
> > weren’t uploaded and are resulting in a blank text area showing up. I can
> > run the doc generation target locally (on 2.4.0 tag) and have someone
> > upload those files and see if shows up fine.
> > >
> > > [1] https://issues.apache.org/jira/browse/IVY-1542
> > >
> > > -Jaikiran
> > > -
> > > 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.

Re: Ivy website - fixing a Quickstart documentation live

[Nicolas Lalevée]

There are some Ant task for asciidoctor, and it is used in the branch where 
there is the experiment about migrating from xooki to asciidoc:
https://github.com/apache/ant-ivy/blob/xooki2asciidoc/build-release.xml#L168 


And it is nice because we can plug things into asciidoctor, like the management 
of the toc, just like xooki is currently doing:
https://github.com/apache/ant-ivy/blob/xooki2asciidoc/asciidoc/templates/helpers.rb
 


Nicolas
 
> Le 26 mai 2017 à 17:54, Gintautas Grigelionis  a 
> écrit :
> 
> 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 26 May 2017 at 02:06, J Pai  wrote:
>> 
>>> So I got this site generation working locally (had to fix a xooki script
>>> to make it work with Nashorn. The attached patch includes the fix).
>>> 
>>> At this point, I need help to commit the newly generated doc fixes to the
>>> SVN. I’ve attached a patch file for it and will explain what it is doing.
>>> 
>>> The changes/patch relates to _one_ of the more important issues noted in
>>> the JIRA https://issues.apache.org/jira/browse/IVY-1542. That JIRA lists
>>> more than one issue with the latest docs. However, the missing .png and
>>> .css don’t directly contribute to anything noticeable, so I haven’t
>>> included it in this patch (and probably will look into it separately).
>> The
>>> issue that this patch fixes is the more important one:
>>> 
 Code examples are missing. About 2/3 of the way down the page are two
>>> code examples that are rendering as just a black rectangle for me. The
>>> underlying html looks like it has  tags with no content.
>>> 
>>> 
>>> The way these tutorial docs are generated, during the build, it triggers
>>> the build of quickstart examples and dumps the logs into files. The log
>>> files are then referred to via xooki references and the contents of those
>>> log files are inlined within the div tags. So I went ahead and built
>> these
>>> tutorials on 2.4.0 tag of Ivy project, generated those logs and then
>>> regenerated the site with these logs in the relevant folder. The
>> generated
>>> documentation now has these output inlined correctly in the quickstart
>> and
>>> various other docs.
>>> 
>>> The attached patch was generated with https://svn.apache.org/repos/
>>> asf/ant/site/ as the root of the SVN checkout. So whoever is applying the
>>> patch will have to cd to that directory and then apply it. Let me know if
>>> you run into issues or if any changes are necessary in this patch.
>>> 
>>> As for the other two issues noted in that JIRA, I’m planning to remove
>>> references to the non-existent .css and .png files and submit that as a
>>> separate patch.
>>> 
>>> -Jaikiran
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> 
>>> On 26-May-2017, at 10:39 AM, J Pai  wrote:
>>> 
>>> 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 Lalevée 
>>> wrote:
>>> 
>>> 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 there are ant tasks to run to the fetch of the sources. I have found
>> an
>>> old discussion [1] we had about it which should help you.
>>> 
>>> 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 I have a commit which for some reason I didn’t pushed.
>> If
>>> we are still interested, I can revive this.
>>> 
>>> Nicolas
>>> 
>>> [1] http://ant.1045680.n5.nabble.com/stuck-with-site-
>>> generation-issue-for-ivy-td5715758.html >> com/stuck-with-site-generation-issue-for-ivy-td5715758.html>
>>> [2] https://github.com/apache/ant-ivy/tree/xooki2asciidoc <
>>> https://github.com/apache/ant-ivy/tree/xooki2asciidoc>
>>> 
>>> 
 Le 25 mai 2017 à 06:12, J Pai  a écrit :
 
 What would be the process of having the live docs of Ivy project
>> updated
>>> to fix/update an issue in the documentation[1]?
 
 The quickstart documentation refers to certain log files that get
>>> auto-generated during the doc build proces

[GitHub] ant-ivy issue #32: A few loose bits in JUnit 4 migration

[twogee]

Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/32
  
Jenkins build was complete an hour ago, but status on Github is still 
pending...


---
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 pull request #32: A few loose bits in JUnit 4 migration

[asfgit]

Github user asfgit closed the pull request at:

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


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

AW: build IvyDE

[jhm]

Nope, haven't read that.
My first contact to a build is always executing the build without any 
parameters. ;)

I'll have a look, thanks.


Jan

> -Ursprüngliche Nachricht-
> Von: Nicolas Lalevée [mailto:nicolas.lale...@hibnet.org]
> Gesendet: Freitag, 26. Mai 2017 17:21
> An: Ant Developers List
> Betreff: Re: build IvyDE
> 
> It has been ages since I have done a build of Eclipse, but like Gintas
> wrote, there is something wrong with your Eclipse install you are
> building against, it is missing zest.
> I don’t know if you have seen but there is a piece of documentation
> about building IvyDE there:
> http://ant.apache.org/ivy/ivyde/history/latest-milestone/dev/build.html
>  milestone/dev/build.html>
> 
> The hudson-prepare ant task is about what is described in that doc:
> download stuff and setup the baseLocation property.
> 
> Nicolas
> 
> > Le 26 mai 2017 à 16:50, Gintautas Grigelionis
>  a écrit :
> >
> > 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 build and update build properties.
> >
> > Gintas
> >
> > 2017-05-26 14:53 GMT+02:00 Jan Matèrne :
> >
> >> I tried to get the IvyDE build working.
> >>
> >> Finally I am getting a
> >>
> >>
> >>
> >> [eclipse.buildScript] Some inter-plug-in dependencies have not been
> >> satisfied.
> >>
> >> [eclipse.buildScript] Bundle
> org.apache.ivyde.eclipse.resolvevisualizer:
> >>
> >> [eclipse.buildScript]   Missing required plug-in
> >> org.eclipse.zest.core_[1.2.0,2.0.0).
> >>
> >> [eclipse.buildScript]   Missing required plug-in
> >> org.eclipse.zest.layouts_[1.1.0,2.0.0).
> >>
> >>
> >>
> >> I could download zest via "ant hudson-get-zest"
> >>
> >>
> >>
> >> hudson-get-zest:
> >>
> >>  [get] Getting:
> >> http://www.eclipse.org/downloads/download.php?file=/
> >> tools/gef/downloads/drop
> >> s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://
> >> carroll.aset.psu.edu/pub
> >> /eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-
> >> zest-3.6.2.zip&mi
> >> rror_id=546
> >>
> >>  [get] To:
> >> C:\projekte\apache-ant\ivy-ivyde\dependencies\GEF-zest-3.6.2.zip
> >>
> >>  [get]
> >> http://www.eclipse.org/downloads/download.php?file=/
> >> tools/gef/downloads/drop
> >> s/3.6.2/R201102251600/GEF-zest-3.6.2.zip&url=http://
> >> carroll.aset.psu.edu/pub
> >> /eclipse/tools/gef/downloads/drops/3.6.2/R201102251600/GEF-
> >> zest-3.6.2.zip&mi
> >> rror_id=546 moved to
> >> http://archive.eclipse.org/tools/gef/downloads/drops/3.6.
> >> 2/R201102251600/GEF
> >> -zest-3.6.2.zip
> >>
> >>  [get] ...
> >>
> >>
> >>
> >> BUILD SUCCESSFUL
> >>
> >> Total time: 5 seconds
> >>
> >>
> >>
> >>
> >>
> >> Some ideas?
> >>
> >>
> >>
> >>
> >>
> >> Jan
> >>
> >>



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