Re: Error while testing 2.5.0-SNAPSHOT

2017-09-25 Thread Gintautas Grigelionis 
Looks like Windows need file:/// [1]

Gintas

[1]
https://stackoverflow.com/questions/7151877/how-should-a-file-uri-corresponding-to-a-windows-path-name-look-like

2017-09-25 17:31 GMT+02:00 Maarten Coene :

> Jaikiran,
> probably only reproducible on a Windows machine...
> Maarten
>
>   Van: Aurélien Pupier 
>  Aan: Ant Developers List 
>  Verzonden: maandag 25 september 13:41 2017
>  Onderwerp: Re: Error while testing 2.5.0-SNAPSHOT
>
> Hello Jaikiran,
>
> Source repositories implicated are:
> - Fuse Tooling: https://github.com/jbosstools/jbosstools-fuse
> - Camel: https://github.com/apache/camel/tree/camel-2.19.3
> - Groovy: https://github.com/groovy/groovy-core/tree/GROOVY_2_4_3
>
> I wasn't able to build the whole chain to include latest Ivy snapshot.
>
> To reproduce, I did:
> - replace ivy jar in org.fusesource.ide.camel.model.service.impl by an Ivy
> 2.5.0-SNAPSHOT build
> - update of org.fusesource.ide.camel.model.service.impl MANIFEST.MF to
> include the correct version of added snapshot
>
>
> Regards,
>
> On Mon, Sep 25, 2017 at 9:05 AM, Jaikiran Pai 
> wrote:
>
> > Is there a source repo and steps that I can follow to build and reproduce
> > this issue? My attempts so far haven't been able to reproduce this.
> >
> > -Jaikiran
> >
> >
> > On 14/09/17 1:57 PM, Aurélien Pupier wrote:
> >
> >> Hello,
> >>
> >> I'm trying to test https://issues.apache.org/jira/browse/IVY-1568 using
> >> latest 2.5.0-SNAPSHOT as suggested.
> >>
> >> Unfortunately, I got errors for non-snapshots artefacts which were
> working
> >> with 2.4.0 version.
> >> I will need to investigate more but Ivy developers might detect faster
> >> than
> >> me what is going wrong. Please find the whole errors that i captured
> here
> >> . Here
> is
> >> an
> >> extract of the stacktrace which seems interesting
> >>
> >> red-hat-ga-repository: downloading https://maven.repository.
> >> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
> >> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom.sha1
> >> to C:\Users\AURELI~1\AppData\Local\Temp\ivytmp8576317204837329542sha1
> >> sha1 OK for https://maven.repository.redhat.com/ga/org/apache/
> >> camel/camel-catalog/2.17.0.redhat-630283/camel-catalog-2.
> >> 17.0.redhat-630283.pom
> >> [SUCCESSFUL ] org.apache.camel#camel-catalog;2.17.0.redhat-630283!
> >> camel-catalog.pom(pom.original) (139ms)
> >> ERROR: HttpClientHandler: URI does not specify a valid host name:
> >> file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
> >> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
> >> url=file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
> >> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
> >> WARN: io problem while parsing ivy file: https://maven.repository.
> >> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
> >> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom
> >>  (org.apache.http.client.ClientProtocolException: URI does not specify
> a
> >> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
> >> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original)
> >> org.apache.http.client.ClientProtocolException: URI does not specify a
> >> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
> >> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
> >> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(
> >> CloseableHttpClient.java:94)
> >> at org.apache.http.impl.client.CloseableHttpClient.execute(
> >> CloseableHttpClient.java:82)
> >> at org.apache.http.impl.client.CloseableHttpClient.execute(
> >> CloseableHttpClient.java:107)
> >> at org.apache.ivy.util.url.HttpClientHandler.doGet(
> >> HttpClientHandler.java:313)
> >> at org.apache.ivy.util.url.HttpClientHandler.openStream(
> >> HttpClientHandler.java:141)
> >> at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.
> java:122)
> >> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
> >> parseDescriptor(PomModuleDescriptorParser.java:126)
> >> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
> >> parseDescriptor(PomModuleDescriptorParser.java:116)
> >> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager$
> >> MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.
> >> java:835)
> >> at org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(
> >> ModuleDescriptorMemoryCache.java:68)
> >> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(
> >> DefaultRepositoryCacheManager.java:852)
> >> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.
> >> cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1361)
> >> at org.apache.ivy.plugins.resolver.BasicResolver.parse(
> >> BasicResolver.java:536)
> >> at org.apache.ivy.plugins.resolver.BasicResolver.
> >> getDependency(BasicResolver.java:273)
> >> at org.apache.ivy.plugins.resolver.IBiblioResolver.
> >> getDependency(IBibl

Re: Error while testing 2.5.0-SNAPSHOT

2017-09-25 Thread Maarten Coene 
Jaikiran,
probably only reproducible on a Windows machine...
Maarten

  Van: Aurélien Pupier 
 Aan: Ant Developers List  
 Verzonden: maandag 25 september 13:41 2017
 Onderwerp: Re: Error while testing 2.5.0-SNAPSHOT
   
Hello Jaikiran,

Source repositories implicated are:
- Fuse Tooling: https://github.com/jbosstools/jbosstools-fuse
- Camel: https://github.com/apache/camel/tree/camel-2.19.3
- Groovy: https://github.com/groovy/groovy-core/tree/GROOVY_2_4_3

I wasn't able to build the whole chain to include latest Ivy snapshot.

To reproduce, I did:
- replace ivy jar in org.fusesource.ide.camel.model.service.impl by an Ivy
2.5.0-SNAPSHOT build
- update of org.fusesource.ide.camel.model.service.impl MANIFEST.MF to
include the correct version of added snapshot


Regards,

On Mon, Sep 25, 2017 at 9:05 AM, Jaikiran Pai 
wrote:

> Is there a source repo and steps that I can follow to build and reproduce
> this issue? My attempts so far haven't been able to reproduce this.
>
> -Jaikiran
>
>
> On 14/09/17 1:57 PM, Aurélien Pupier wrote:
>
>> Hello,
>>
>> I'm trying to test https://issues.apache.org/jira/browse/IVY-1568 using
>> latest 2.5.0-SNAPSHOT as suggested.
>>
>> Unfortunately, I got errors for non-snapshots artefacts which were working
>> with 2.4.0 version.
>> I will need to investigate more but Ivy developers might detect faster
>> than
>> me what is going wrong. Please find the whole errors that i captured here
>> . Here is
>> an
>> extract of the stacktrace which seems interesting
>>
>> red-hat-ga-repository: downloading https://maven.repository.
>> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
>> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom.sha1
>> to C:\Users\AURELI~1\AppData\Local\Temp\ivytmp8576317204837329542sha1
>> sha1 OK for https://maven.repository.redhat.com/ga/org/apache/
>> camel/camel-catalog/2.17.0.redhat-630283/camel-catalog-2.
>> 17.0.redhat-630283.pom
>> [SUCCESSFUL ] org.apache.camel#camel-catalog;2.17.0.redhat-630283!
>> camel-catalog.pom(pom.original) (139ms)
>> ERROR: HttpClientHandler: URI does not specify a valid host name:
>> file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> url=file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> WARN: io problem while parsing ivy file: https://maven.repository.
>> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
>> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom
>>  (org.apache.http.client.ClientProtocolException: URI does not specify a
>> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original)
>> org.apache.http.client.ClientProtocolException: URI does not specify a
>> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(
>> CloseableHttpClient.java:94)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(
>> CloseableHttpClient.java:82)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(
>> CloseableHttpClient.java:107)
>> at org.apache.ivy.util.url.HttpClientHandler.doGet(
>> HttpClientHandler.java:313)
>> at org.apache.ivy.util.url.HttpClientHandler.openStream(
>> HttpClientHandler.java:141)
>> at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:122)
>> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
>> parseDescriptor(PomModuleDescriptorParser.java:126)
>> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
>> parseDescriptor(PomModuleDescriptorParser.java:116)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager$
>> MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.
>> java:835)
>> at org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(
>> ModuleDescriptorMemoryCache.java:68)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(
>> DefaultRepositoryCacheManager.java:852)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.
>> cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1361)
>> at org.apache.ivy.plugins.resolver.BasicResolver.parse(
>> BasicResolver.java:536)
>> at org.apache.ivy.plugins.resolver.BasicResolver.
>> getDependency(BasicResolver.java:273)
>> at org.apache.ivy.plugins.resolver.IBiblioResolver.
>> getDependency(IBiblioResolver.java:550)
>> at org.apache.ivy.plugins.resolver.ChainResolver.
>> getDependency(ChainResolver.java:101)
>> at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:183)
>> at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
>> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
>> ResolveEngine.java:724)
>> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependenci

Re: Ivy upcoming release - where we stand

2017-09-25 Thread Gintautas Grigelionis 
I'd rather deprecate as much as possible for 2.5.0, so that deprecated
stuff could be removed in 3.0 :-)

Gintas

2017-09-25 14:51 GMT+02:00 Jan Matèrne (jhm) :

> > I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems
> > for entire inherited configurations/dependencies blocks (and another
> > test case for that).
>
> good.
>
>
> > PR-57 breaks BC but mitigates that except for a special case. Anyway,
> > why must every release be a drop-in replacement for the previous one?
>
> It does not have to.
> With a drop-in replacement it is easier to update for the users. ;-)
> And with the upcoming 2.5.0 I would it make as easy as possible, because
> it is the first release after a long time.
>
> We could discuss major or BC-breaking changes after that. Maybe call the
> next release 3.x ...
>
>
> Jan
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>

AW: Ivy upcoming release - where we stand

2017-09-25 Thread jhm 
> I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems
> for entire inherited configurations/dependencies blocks (and another
> test case for that).

good.


> PR-57 breaks BC but mitigates that except for a special case. Anyway,
> why must every release be a drop-in replacement for the previous one?

It does not have to.
With a drop-in replacement it is easier to update for the users. ;-)
And with the upcoming 2.5.0 I would it make as easy as possible, because it is 
the first release after a long time.

We could discuss major or BC-breaking changes after that. Maybe call the next 
release 3.x ... 


Jan


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

Re: Ivy upcoming release - where we stand

2017-09-25 Thread Gintautas Grigelionis 
Sounds good.

I'm closing in on IVY-1420; it's Willem's patch + writeInheritedItems for
entire inherited configurations/dependencies blocks (and another test case
for that).

PR-57 breaks BC but mitigates that except for a special case. Anyway, why
must every release be a drop-in replacement for the previous one?

Gintas

2017-09-25 13:42 GMT+02:00 Jan Matèrne (jhm) :

> I recap the todo list before a 2.5.0 release:
>
> - https://issues.apache.org/jira/browse/IVY-1485
>   Incorrect revision of dependencies put in to delivered Ivy files
>   Status: Jaikiran wanted to focus on that (11.09.2017)
>   prio: stopper ("but it was IVY-1485 which reanimated the community")
>
> - https://issues.apache.org/jira/browse/IVY-1420
>   defaultconfmapping on  element is not written to
> delivered ivy file
>   Status: "I need about a week"
>   prio: should be included
>
> - SVG-graphics
>   Status:
>   prio: should be included, as it seems to be nearly finished (for me)
>
> - upgrading BouncyCastle
>   Status: done
>
> - IVY-1420/IVY-1437, defaultconf/defaultconfmapping/confmappingoverride
> attributes
>   "according to ivy.xsd, all three attributes can be used on both
> dependencies and configurations.
>   So, it's the documentation that must be adjusted accordingly"
>   Status: open
>   prio: maybe delay (and open a Jira ticket)
>
> - https://github.com/apache/ant-ivy/pull/60
>   use Unicode glyphs or SVG data URLs instead of bitmaps
>   Status: review required
>   prio: should be included (as part of the "svg-bulk")
>
> - https://github.com/apache/ant-ivy/pull/57
>   fix the last inconsistencies in generics
>   Status: This includes a change which breaks BC
>   prio: solve that or delay (this PR should not delay the new version in
> my opinion)
>
> - https://github.com/apache/ant-ivy/pull/55
>   use the vectorised logo
>   Status: nearly finished (missing header)
>   prio: include that as is nearly finished
>
>
> Some comments/updates?
>
>
> Jan
>
>
> > -Ursprüngliche Nachricht-
> > Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> > Gesendet: Montag, 25. September 2017 07:16
> > An: dev@ant.apache.org
> > Betreff: Re: Ivy upcoming release - where we stand
> >
> > Since the latest released version of that library is 1.58, I think we
> > should use that version, unless there's a specific reason to not use
> > it.
> > A quick compilation of Ivy with this library and checking their docs
> > for JDK compatibility suggested no issues with 1.58.
> >
> > -Jaikiran
> >
> >
> > On 19/09/17 10:07 AM, Gintautas Grigelionis wrote:
> > > I would like to propose upgrading BouncyCastle to at least 1.57 [1]
> > to
> > > include all security and PGP/GPG related fixes.
> > >
> > > Gintas
> > >
> > > [1] https://www.bouncycastle.org/releasenotes.html
> > >
> > > 2017-09-11 21:45 GMT+02:00 Gintautas Grigelionis
> > :
> > >
> > >> I'd like to have https://issues.apache.org/jira/browse/IVY-1420
> > >> included in the upcoming release.
> > >>
> > >> There were few opinions about using SVG graphics, so I'm not sure
> > >> whether the proposals could just simply be merged. It would be nice
> > >> to refresh the site for the 10th anniversary of graduation from the
> > incubator, though.
> > >>
> > >> Finally, there is a contentious issue of API change regarding the
> > use
> > >> of generics. Arrays of generics is a no-no in Java [1]. Thus, the
> > >> method in question should be deprecated. IMHO, the suggested
> > >> mitigation by providing a default implementation of the new method
> > in
> > >> terms of the old one in the abstract class is sufficient for the use
> > cases found in the wild.
> > >>
> > >> Gintas
> > >>
> > >> [1] https://docs.oracle.com/javase/tutorial/java/generics/
> > >> restrictions.html
> > >>
> > >> 2017-09-11 17:05 GMT+02:00 Jaikiran Pai :
> > >>
> > >>> It's been a while since we have decided to revive the Ivy project
> > >>> and work towards a usable release. Since then, we have fixed a good
> > >>> number of bugs, added some enhancements and updated the
> > >>> documentation (we also switched to asciidoc based docs internally).
> > >>> When we started this, the goal was to reach a certain state where
> > we
> > >>> can do a release. At this point, IMO, we are _almost_ there to do
> > >>> the release. I say almost because, there's one specific bug that I
> > >>> want to be fixed in this release -
> > >>> https://issues.apache.org/jira/browse/IVY-1485. There's been a
> > >>> discussion about what it involves and why it isn't an easy fix in
> > >>> this mailing list before. I have been working on it and as was
> > >>> expected, it's a bit complex and since it touches a critical part
> > of the code, I don't want to rush it.
> > >>>
> > >>> The past few weeks, I have been shifting between this issue and
> > >>> fixing certain other issues that have been reported in JIRA. But at
> > >>> this point, I plan to just focus on this single issue (and one
> > minor
> > >>> task involving reviewing the tutorial docs),

[GitHub] ant issue #36: Allow faking of zip entry modification times.

2017-09-25 Thread janmaterne 
Github user janmaterne commented on the issue:

https://github.com/apache/ant/pull/36
  
ant-unit-1.3 is in the repo 
(https://github.com/apache/ant/blob/master/lib/optional/ant-antunit-1.3.jar).
It seems that you use an Ant version for building this which does not 
contain this jar.

If you are building Ant itself I recommend cleaning the environment before 
(unset ANT_HOME) and bootstrap Ant by itself.


---

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

AW: Ivy upcoming release - where we stand

2017-09-25 Thread jhm 
I recap the todo list before a 2.5.0 release:

- https://issues.apache.org/jira/browse/IVY-1485
  Incorrect revision of dependencies put in to delivered Ivy files
  Status: Jaikiran wanted to focus on that (11.09.2017)
  prio: stopper ("but it was IVY-1485 which reanimated the community")

- https://issues.apache.org/jira/browse/IVY-1420
  defaultconfmapping on  element is not written to delivered 
ivy file
  Status: "I need about a week"
  prio: should be included

- SVG-graphics
  Status:
  prio: should be included, as it seems to be nearly finished (for me)

- upgrading BouncyCastle
  Status: done

- IVY-1420/IVY-1437, defaultconf/defaultconfmapping/confmappingoverride 
attributes
  "according to ivy.xsd, all three attributes can be used on both dependencies 
and configurations. 
  So, it's the documentation that must be adjusted accordingly"
  Status: open
  prio: maybe delay (and open a Jira ticket)

- https://github.com/apache/ant-ivy/pull/60
  use Unicode glyphs or SVG data URLs instead of bitmaps
  Status: review required
  prio: should be included (as part of the "svg-bulk")

- https://github.com/apache/ant-ivy/pull/57
  fix the last inconsistencies in generics
  Status: This includes a change which breaks BC
  prio: solve that or delay (this PR should not delay the new version in my 
opinion)

- https://github.com/apache/ant-ivy/pull/55
  use the vectorised logo
  Status: nearly finished (missing header)
  prio: include that as is nearly finished


Some comments/updates?


Jan


> -Ursprüngliche Nachricht-
> Von: Jaikiran Pai [mailto:jai.forums2...@gmail.com]
> Gesendet: Montag, 25. September 2017 07:16
> An: dev@ant.apache.org
> Betreff: Re: Ivy upcoming release - where we stand
> 
> Since the latest released version of that library is 1.58, I think we
> should use that version, unless there's a specific reason to not use
> it.
> A quick compilation of Ivy with this library and checking their docs
> for JDK compatibility suggested no issues with 1.58.
> 
> -Jaikiran
> 
> 
> On 19/09/17 10:07 AM, Gintautas Grigelionis wrote:
> > I would like to propose upgrading BouncyCastle to at least 1.57 [1]
> to
> > include all security and PGP/GPG related fixes.
> >
> > Gintas
> >
> > [1] https://www.bouncycastle.org/releasenotes.html
> >
> > 2017-09-11 21:45 GMT+02:00 Gintautas Grigelionis
> :
> >
> >> I'd like to have https://issues.apache.org/jira/browse/IVY-1420
> >> included in the upcoming release.
> >>
> >> There were few opinions about using SVG graphics, so I'm not sure
> >> whether the proposals could just simply be merged. It would be nice
> >> to refresh the site for the 10th anniversary of graduation from the
> incubator, though.
> >>
> >> Finally, there is a contentious issue of API change regarding the
> use
> >> of generics. Arrays of generics is a no-no in Java [1]. Thus, the
> >> method in question should be deprecated. IMHO, the suggested
> >> mitigation by providing a default implementation of the new method
> in
> >> terms of the old one in the abstract class is sufficient for the use
> cases found in the wild.
> >>
> >> Gintas
> >>
> >> [1] https://docs.oracle.com/javase/tutorial/java/generics/
> >> restrictions.html
> >>
> >> 2017-09-11 17:05 GMT+02:00 Jaikiran Pai :
> >>
> >>> It's been a while since we have decided to revive the Ivy project
> >>> and work towards a usable release. Since then, we have fixed a good
> >>> number of bugs, added some enhancements and updated the
> >>> documentation (we also switched to asciidoc based docs internally).
> >>> When we started this, the goal was to reach a certain state where
> we
> >>> can do a release. At this point, IMO, we are _almost_ there to do
> >>> the release. I say almost because, there's one specific bug that I
> >>> want to be fixed in this release -
> >>> https://issues.apache.org/jira/browse/IVY-1485. There's been a
> >>> discussion about what it involves and why it isn't an easy fix in
> >>> this mailing list before. I have been working on it and as was
> >>> expected, it's a bit complex and since it touches a critical part
> of the code, I don't want to rush it.
> >>>
> >>> The past few weeks, I have been shifting between this issue and
> >>> fixing certain other issues that have been reported in JIRA. But at
> >>> this point, I plan to just focus on this single issue (and one
> minor
> >>> task involving reviewing the tutorial docs), before I personally
> >>> consider things done for this release.
> >>>
> >>> -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



-

Re: Error while testing 2.5.0-SNAPSHOT

2017-09-25 Thread Aurélien Pupier 
Hello Jaikiran,

Source repositories implicated are:
- Fuse Tooling: https://github.com/jbosstools/jbosstools-fuse
- Camel: https://github.com/apache/camel/tree/camel-2.19.3
- Groovy: https://github.com/groovy/groovy-core/tree/GROOVY_2_4_3

I wasn't able to build the whole chain to include latest Ivy snapshot.

To reproduce, I did:
- replace ivy jar in org.fusesource.ide.camel.model.service.impl by an Ivy
2.5.0-SNAPSHOT build
- update of org.fusesource.ide.camel.model.service.impl MANIFEST.MF to
include the correct version of added snapshot


Regards,

On Mon, Sep 25, 2017 at 9:05 AM, Jaikiran Pai 
wrote:

> Is there a source repo and steps that I can follow to build and reproduce
> this issue? My attempts so far haven't been able to reproduce this.
>
> -Jaikiran
>
>
> On 14/09/17 1:57 PM, Aurélien Pupier wrote:
>
>> Hello,
>>
>> I'm trying to test https://issues.apache.org/jira/browse/IVY-1568 using
>> latest 2.5.0-SNAPSHOT as suggested.
>>
>> Unfortunately, I got errors for non-snapshots artefacts which were working
>> with 2.4.0 version.
>> I will need to investigate more but Ivy developers might detect faster
>> than
>> me what is going wrong. Please find the whole errors that i captured here
>> . Here is
>> an
>> extract of the stacktrace which seems interesting
>>
>> red-hat-ga-repository: downloading https://maven.repository.
>> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
>> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom.sha1
>> to C:\Users\AURELI~1\AppData\Local\Temp\ivytmp8576317204837329542sha1
>> sha1 OK for https://maven.repository.redhat.com/ga/org/apache/
>> camel/camel-catalog/2.17.0.redhat-630283/camel-catalog-2.
>> 17.0.redhat-630283.pom
>> [SUCCESSFUL ] org.apache.camel#camel-catalog;2.17.0.redhat-630283!
>> camel-catalog.pom(pom.original) (139ms)
>> ERROR: HttpClientHandler: URI does not specify a valid host name:
>> file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> url=file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> WARN: io problem while parsing ivy file: https://maven.repository.
>> redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
>> redhat-630283/camel-catalog-2.17.0.redhat-630283.pom
>>   (org.apache.http.client.ClientProtocolException: URI does not specify a
>> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original)
>> org.apache.http.client.ClientProtocolException: URI does not specify a
>> valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
>> apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
>> at org.apache.http.impl.client.CloseableHttpClient.determineTarget(
>> CloseableHttpClient.java:94)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(
>> CloseableHttpClient.java:82)
>> at org.apache.http.impl.client.CloseableHttpClient.execute(
>> CloseableHttpClient.java:107)
>> at org.apache.ivy.util.url.HttpClientHandler.doGet(
>> HttpClientHandler.java:313)
>> at org.apache.ivy.util.url.HttpClientHandler.openStream(
>> HttpClientHandler.java:141)
>> at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:122)
>> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
>> parseDescriptor(PomModuleDescriptorParser.java:126)
>> at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
>> parseDescriptor(PomModuleDescriptorParser.java:116)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager$
>> MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.
>> java:835)
>> at org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(
>> ModuleDescriptorMemoryCache.java:68)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(
>> DefaultRepositoryCacheManager.java:852)
>> at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.
>> cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1361)
>> at org.apache.ivy.plugins.resolver.BasicResolver.parse(
>> BasicResolver.java:536)
>> at org.apache.ivy.plugins.resolver.BasicResolver.
>> getDependency(BasicResolver.java:273)
>> at org.apache.ivy.plugins.resolver.IBiblioResolver.
>> getDependency(IBiblioResolver.java:550)
>> at org.apache.ivy.plugins.resolver.ChainResolver.
>> getDependency(ChainResolver.java:101)
>> at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:183)
>> at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
>> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
>> ResolveEngine.java:724)
>> at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(
>> ResolveEngine.java:803)
>> at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
>> ResolveEngine.java:731)
>> at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(
>> ResolveEngine.java:608)
>> at o

[GitHub] ant issue #36: Allow faking of zip entry modification times.

2017-09-25 Thread GKFX 
Github user GKFX commented on the issue:

https://github.com/apache/ant/pull/36
  
@bodewig I've done that, but `ant test` fails with the output
```
-antunit-warn-location:
 [echo] AntUnit tests must be run with /home/bateman/Geek/ant/bootstrap 
(or /home/bateman/Geek/ant/dist), not /usr/share/ant. Try './build.sh 
antunit-tests' for example.

antunit-tests:

BUILD FAILED
/home/bateman/Geek/ant/build.xml:1957: Problem: failed to create task or 
type antlib:org.apache.ant.antunit:antunit
Cause: The name is undefined.
Action: Check the spelling.
Action: Check that any custom tasks/types have been declared.
Action: Check that any / declarations have taken place.
No types or tasks have been defined in this namespace yet

This appears to be an antlib declaration. 
Action: Check that the implementing library exists in one of:
-/usr/share/ant/lib
-/home/bateman/.ant/lib
-a directory added on the command line with the -lib argument
```
and I'm not quite sure how to fix that. Is the test I've written wrong?


---

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

[GitHub] ant-ivy issue #55: use the vectorised logo

2017-09-25 Thread twogee 
Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/55
  
logo.png is for CredentialsUtil; replaced by IvyLogo

CSS contains changes for `#logo` and adds `svg.icon` (somehow Firefox 
cannot read dimensions from embedded SVGs)

XSL generates HTML5 that uses xlink to reuse SVGs

IvyLogo is a one-off conversion of SVG + some manual additions (cleaned 
casts and added max icon size). Using SVG directly requires Batik, which is an 
overkill.

Here's the build.xml I used for testing Ivy report

```
















```


---

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

[GitHub] ant-ivy issue #55: use the vectorised logo

2017-09-25 Thread janmaterne 
Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivy/pull/55
  
Violations of the license header:
* ivy-lierre.svg (missing, remove the generator comment)
* IvyLogo (missing)


---

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

[GitHub] ant-ivy issue #55: use the vectorised logo

2017-09-25 Thread janmaterne 
Github user janmaterne commented on the issue:

https://github.com/apache/ant-ivy/pull/55
  
ivy-lierre.svg: 
- looks good
- havent compared, I think asciidoc/images and doc/images are the same?
- why this name? why not simply logo.svg? (ok, I see: ivy-lierre.png ...) 
But there is logo.png with same content (only smaller borders)

ivy-report.css
- seems that here is only different formatting 

ivy-report.xsl
- formatting
- changed  to 
- translated img/@art->svg//title and img/@title->svg//title
! couldnt see the content of the grafik (where is defined that 
searched/downloaded svg should be used?)

IvyLogo.java
- havent tested that generated code
- JavaDoc of the parameters of IvyLogo(int width, int height) are bad 
("ditto")
- I am thinking about the code generation ...
  a) include the flamingo task into our build and remove the generated code 
(= keep the model (svg) and the generator)
  b) just keep that generated code
  c) reuse the svg (Java reads the svg-resource and interpretes the drawing)
  Because this is one-shot we could go with b) ...



Checked out the code and the report looks fine.
But a simple ivy:report didnt work, I changed build.xml:500 to use 
explicitly the new xsl
  
Maybe my local environment ...


---

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

Re: Error while testing 2.5.0-SNAPSHOT

2017-09-25 Thread Jaikiran Pai 
Is there a source repo and steps that I can follow to build and 
reproduce this issue? My attempts so far haven't been able to reproduce 
this.


-Jaikiran


On 14/09/17 1:57 PM, Aurélien Pupier wrote:

Hello,

I'm trying to test https://issues.apache.org/jira/browse/IVY-1568 using
latest 2.5.0-SNAPSHOT as suggested.

Unfortunately, I got errors for non-snapshots artefacts which were working
with 2.4.0 version.
I will need to investigate more but Ivy developers might detect faster than
me what is going wrong. Please find the whole errors that i captured here
. Here is an
extract of the stacktrace which seems interesting

red-hat-ga-repository: downloading https://maven.repository.
redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
redhat-630283/camel-catalog-2.17.0.redhat-630283.pom.sha1
to C:\Users\AURELI~1\AppData\Local\Temp\ivytmp8576317204837329542sha1
sha1 OK for https://maven.repository.redhat.com/ga/org/apache/
camel/camel-catalog/2.17.0.redhat-630283/camel-catalog-2.
17.0.redhat-630283.pom
[SUCCESSFUL ] org.apache.camel#camel-catalog;2.17.0.redhat-630283!
camel-catalog.pom(pom.original) (139ms)
ERROR: HttpClientHandler: URI does not specify a valid host name:
file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
url=file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
WARN: io problem while parsing ivy file: https://maven.repository.
redhat.com/ga/org/apache/camel/camel-catalog/2.17.0.
redhat-630283/camel-catalog-2.17.0.redhat-630283.pom
  (org.apache.http.client.ClientProtocolException: URI does not specify a
valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original)
org.apache.http.client.ClientProtocolException: URI does not specify a
valid host name: file:/C:/Users/Aurelien%20Pupier/.groovy/grapes/org.
apache.camel/camel-catalog/ivy-2.17.0.redhat-630283.xml.original
at org.apache.http.impl.client.CloseableHttpClient.determineTarget(
CloseableHttpClient.java:94)
at org.apache.http.impl.client.CloseableHttpClient.execute(
CloseableHttpClient.java:82)
at org.apache.http.impl.client.CloseableHttpClient.execute(
CloseableHttpClient.java:107)
at org.apache.ivy.util.url.HttpClientHandler.doGet(
HttpClientHandler.java:313)
at org.apache.ivy.util.url.HttpClientHandler.openStream(
HttpClientHandler.java:141)
at org.apache.ivy.plugins.parser.m2.PomReader.(PomReader.java:122)
at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
parseDescriptor(PomModuleDescriptorParser.java:126)
at org.apache.ivy.plugins.parser.m2.PomModuleDescriptorParser.
parseDescriptor(PomModuleDescriptorParser.java:116)
at org.apache.ivy.core.cache.DefaultRepositoryCacheManager$
MyModuleDescriptorProvider.provideModule(DefaultRepositoryCacheManager.
java:835)
at org.apache.ivy.core.cache.ModuleDescriptorMemoryCache.getStale(
ModuleDescriptorMemoryCache.java:68)
at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.getStaledMd(
DefaultRepositoryCacheManager.java:852)
at org.apache.ivy.core.cache.DefaultRepositoryCacheManager.
cacheModuleDescriptor(DefaultRepositoryCacheManager.java:1361)
at org.apache.ivy.plugins.resolver.BasicResolver.parse(
BasicResolver.java:536)
at org.apache.ivy.plugins.resolver.BasicResolver.
getDependency(BasicResolver.java:273)
at org.apache.ivy.plugins.resolver.IBiblioResolver.
getDependency(IBiblioResolver.java:550)
at org.apache.ivy.plugins.resolver.ChainResolver.
getDependency(ChainResolver.java:101)
at org.apache.ivy.core.resolve.IvyNode.loadData(IvyNode.java:183)
at org.apache.ivy.core.resolve.VisitNode.loadData(VisitNode.java:284)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
ResolveEngine.java:724)
at org.apache.ivy.core.resolve.ResolveEngine.doFetchDependencies(
ResolveEngine.java:803)
at org.apache.ivy.core.resolve.ResolveEngine.fetchDependencies(
ResolveEngine.java:731)
at org.apache.ivy.core.resolve.ResolveEngine.getDependencies(
ResolveEngine.java:608)
at org.apache.ivy.core.resolve.ResolveEngine.resolve(ResolveEngine.java:252)
at org.apache.ivy.Ivy.resolve(Ivy.java:522)
at org.apache.ivy.Ivy$resolve$0.call(Unknown Source)
at groovy.grape.GrapeIvy.getDependencies(GrapeIvy.groovy:410)
at sun.reflect.GeneratedMethodAccessor71.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite$
PogoCachedMethodSite.invoke(PogoMetaMethodSite.java:169)
at org.codehaus.groovy.runtime.callsite.PogoMetaMethodSite.callCurrent(
PogoMetaMethodSite.java:59)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:571)
at groovy.grape.GrapeIvy$resolve$1.callCurrent(Unknown Source)
at groovy.grape.GrapeIvy.resolve(GrapeIvy.groovy:538)
at groovy.grape.GrapeIvy$resolve$0