Re: Ivy logo as SVG

2017-06-01 Thread Gintautas Grigelionis
We may not be artists, but we can be aesthetes :-)
Please see an attached mockup of an Ivy report with proposed SVG icons and
let me know what you think.

Gintas

2017-06-01 16:19 GMT+02:00 Gintautas Grigelionis :

> Logo is important, especially when it ends up in every Ivy report.
> Still, if there are no other way, I'm willing to give it a try :-)
>
> Gintas
>
> 2017-06-01 15:44 GMT+02:00 Stefan Bodewig :
>
>> On 2017-06-01, Gintautas Grigelionis wrote:
>>
>> > I noticed that ASF apparently has converted a bunch of project logos to
>> > SVG. In particular, Ant has an SVG logo.
>>
>> That's not been done "by the ASF" but rather by some kind soul who did
>> the work. I'm afraid we are better coders than artists around here :-)
>>
>> Stefan
>>
>> -
>> 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

IVY-1475 - cachefileset task and its inherent limitation

2017-06-01 Thread J Pai
One of the Ivy users has pointed out to an issue in cachefileset task[1] of Ivy 
here https://issues.apache.org/jira/browse/IVY-1475.

To summarize, the cachefileset task is expected to create a Ant Fileset of the 
resolved artifacts in the cache(s). Ant Fileset requires a (single) basedir to 
work on and the Ivy cachefileset has a piece of logic which tries to determine 
a common base directory for the resolved artifacts. It’s very much possible 
that there won’t be a common base directory for artifacts if the caches have 
been configured to be on multiple different filesystem roots, as noted in that 
JIRA. So essentially, to me, it looks like this cachefileset has an inherent 
deficiency which can’t really be fixed.

The user in that JIRA notes that we can deprecate this task (and also add a 
note about this limitation) in favour of “resources” task [2] which provides a 
similar functionality but is much more flexible and doesn’t suffer this 
limitation.

Any thoughts on how we should go about this JIRA and the cachefileset task?

[1] https://ant.apache.org/ivy/history/latest-milestone/use/cachefileset.html
[2] https://ant.apache.org/ivy/history/latest-milestone/use/resources.html

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



[VOTE] Release Compress Antlib 1.5 based on RC2

2017-06-01 Thread Stefan Bodewig
Hi all

I've created a new release candidate for Compress Antlib 1.5, this time
with working Ivy coordinates and a release date three days into the
future.

git tag: 1_5_RC2
 on commit: f20847d
tarballs: https://dist.apache.org/repos/dist/dev/ant/antlibs/compress/
  revision: 19857
Maven artifacts:
  
https://repository.apache.org/content/repositories/orgapacheant-1018/org/apache/ant/ant-compress/1.5/

This Vote will be open at least for 72 hours and close no earlier than
2017-06-04 17:00UTC.

Cheers

Stefan

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



[GitHub] ant-ivy issue #36: Replace emma with jacoco

2017-06-01 Thread twogee
Github user twogee commented on the issue:

https://github.com/apache/ant-ivy/pull/36
  
Revised accordingly.


---
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 documentation with asciidoc

2017-06-01 Thread Gintautas Grigelionis
2017-06-01 15:43 GMT+02:00 Stefan Bodewig :

> On 2017-06-01, Gintautas Grigelionis wrote:
>
> > 2017-05-31 23:00 GMT+02:00 Nicolas Lalevée :
>
>
> >>> Le 31 mai 2017 à 19:47, Gintautas Grigelionis  >
> >> a écrit :
>
>
> >> Also, external links must be pruned and/or directed to Internet Archive
> >>> -(
> >>> The tutorial of yEd must be revised, version 3 has many more controls.
> I
> >>> converted the odg diagrams to svg, and started looking at Ivy
> report/yEd
> >>> screenshots. The original Ivy logo is unfortunately too low resolution
> >> for
> >>> simple tracing :-( Is this all there is?
>
> >> The only version of the logo we have is in the svn.
>
>
> > That's a pity.
>
> > A couple of related questions: Apache Incubator has changed the logo,
> > should the new logo from their press release kit be used in documentation
> > instead?
>
> Does the Ivy doc include the Incubator logo anywhere? If so, we may want
> to update it. But it can surely only be in a historical context, so
> keeping the old logo would probably be fine.


If there are no guidelines, fine. But ASF seems to have put quite an effort
in a press release kit...


> > Next, there is an "Apache Ant Group" logo that looks like the regular
> > ASF feather 
> > mirrored horisontally with the text on top of it. Is that an official
> > logo?
>
> It is. We know the ASF logo has changed in the mean time and yes, in a
> way we are expected to adjust to the new logo. Nobody is going to do
> that for us, each project is responsible for their own stuff.


If that's fine with the project (group :-), I'll try to make an SVG version
of the logo.

Gintas


Re: Ivy logo as SVG

2017-06-01 Thread Gintautas Grigelionis
Logo is important, especially when it ends up in every Ivy report.
Still, if there are no other way, I'm willing to give it a try :-)

Gintas

2017-06-01 15:44 GMT+02:00 Stefan Bodewig :

> On 2017-06-01, Gintautas Grigelionis wrote:
>
> > I noticed that ASF apparently has converted a bunch of project logos to
> > SVG. In particular, Ant has an SVG logo.
>
> That's not been done "by the ASF" but rather by some kind soul who did
> the work. I'm afraid we are better coders than artists around here :-)
>
> Stefan
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@ant.apache.org
> For additional commands, e-mail: dev-h...@ant.apache.org
>
>


Re: [antlibs] Break Backwards Compatibility of Ivy Coordinates?

2017-06-01 Thread Gintautas Grigelionis
I believe this comment

provides
a pretty good argument why coordinates must be consistent.

Gintas

2017-06-01 14:57 GMT+02:00 Gintautas Grigelionis :

> It's not a "should", it's a MUST. Ideally, pom.xml should be generated
> from ivy.xml or the other way around; at the very least, maven-ant-tasks
> should check the consistence between them, like this
>
>   
>   uri="antlib:org.apache.maven.artifact.ant"
>  classpath="${libdir}/maven-ant-tasks-2.1.3.jar"/>
> 
> The pom version is ${ivy.pom.version}
> 
>   
> 
>arg2="${ivy.pom.build.plugins[0].artifactId}"/>
> 
>   
> 
> 
>   
> 
> 
> 
>   
> 
>   
>  forcestring="true"/>
>  forcestring="true"/>
>  forcestring="true"/>
>   
> 
>   
> 
>   
>
> Gintas
>
> 2017-06-01 13:56 GMT+02:00 J Pai :
>
>> The new organization being proposed “org.apache.ant” instead of
>> “org/apache” is the right way to go IMO. It’s not just Ivy and applies to
>> Maven co-ordinates (via pom.xml) as well. Ideally, they should match with
>> each other. Using the org.apache.ant would make it fit with the groupId (in
>> Maven land) and the organization naming schemes that I have seen for all
>> the other projects out there.
>>
>> -Jaikiran
>> On 01-Jun-2017, at 2:27 AM, Maarten Coene 
>> wrote:
>>
>> I don't see how Ivy could resolve the old ant-compress ivy.xml files
>> without using very special artifact patterns.So my guess is that Ivy users
>> of ant-compress just use the pom.xml file.
>>
>> So I'd say we should fix the ivy.xml.
>> Maarten
>>
>>  Van: Stefan Bodewig 
>> Aan: dev@ant.apache.org
>> Verzonden: woensdag 31 mei 17:34 2017
>> Onderwerp: [antlibs] Break Backwards Compatibility of Ivy Coordinates?
>>
>> Hi all
>>
>> this is an excerpt from the cancelled vote thread for the compress
>> antlib.
>>
>> 2017-05-31 16:40 GMT+02:00 Stefan Bodewig :
>>
>> > I've just realized that the ivy.xml file I've published to Nexus has
>> > completely different coordinates from the one used in earlier
>> > releases. It used to be
>> >
>> > > >   module="ant" ...>
>> > > >
>> > for 1.5 RC1 it is
>> >
>> > > >   module="ant-compress" ...>
>> > > >
>> > and the current master branch would create
>> >
>> > > >   module="ant-compress"
>> >   >
>> and as Gintas points out, master is the only one that is using Ivy
>> coordinates the way they are intended to be.
>>
>> All antlibs builds except for Compress are currently in a state that
>> makes it impossible to release them without making changes and Compress
>> is "correct" after all. So now would be a good time to decide what to
>> do.
>>
>> We could violate Ivy's concepts and go back to what we've done before -
>> the first example above. This is what the two releases of Dotnet, the
>> four releases of AntUnit ant the five releases of Compress have done so
>> far.
>>
>> The other option is to fix all Antlibs to be in line with Ivy's concepts
>> (as Compress is inside master right now). This runs the risk of breaking
>> things for people who use Ivy to retrieve the Antlibs (or maybe not, if
>> they pick them up via their POMs as those have been correct) with all
>> future releases of the three Antlibs that have had releases.
>>
>> I tend to go with the second option and list it as a backwards
>> incompatible change.
>>
>> Any preferences?
>>
>> Stefan
>>
>> -
>> 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: Ivy logo as SVG

2017-06-01 Thread Stefan Bodewig
On 2017-06-01, Gintautas Grigelionis wrote:

> I noticed that ASF apparently has converted a bunch of project logos to
> SVG. In particular, Ant has an SVG logo.

That's not been done "by the ASF" but rather by some kind soul who did
the work. I'm afraid we are better coders than artists around here :-)

Stefan

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



Re: Ivy documentation with asciidoc

2017-06-01 Thread Stefan Bodewig
On 2017-06-01, Gintautas Grigelionis wrote:

> 2017-05-31 23:00 GMT+02:00 Nicolas Lalevée :


>>> Le 31 mai 2017 à 19:47, Gintautas Grigelionis 
>> a écrit :


>> Also, external links must be pruned and/or directed to Internet Archive
>>> -(
>>> The tutorial of yEd must be revised, version 3 has many more controls. I
>>> converted the odg diagrams to svg, and started looking at Ivy report/yEd
>>> screenshots. The original Ivy logo is unfortunately too low resolution
>> for
>>> simple tracing :-( Is this all there is?

>> The only version of the logo we have is in the svn.


> That's a pity.

> A couple of related questions: Apache Incubator has changed the logo,
> should the new logo from their press release kit be used in documentation
> instead?

Does the Ivy doc include the Incubator logo anywhere? If so, we may want
to update it. But it can surely only be in a historical context, so
keeping the old logo would probably be fine.

> Next, there is an "Apache Ant Group" logo that looks like the regular
> ASF feather 
> mirrored horisontally with the text on top of it. Is that an official
> logo?

It is. We know the ASF logo has changed in the mean time and yes, in a
way we are expected to adjust to the new logo. Nobody is going to do
that for us, each project is responsible for their own stuff.

Stefan

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



[GitHub] ant-ivy issue #36: Replace emma with jacoco

2017-06-01 Thread nlalevee
Github user nlalevee commented on the issue:

https://github.com/apache/ant-ivy/pull/36
  
The build-release.xml seems to be largely modified because of some space at 
the end of xml tags. Could we avoid that ? It is painful to review and seems 
useless.


---
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: [antlibs] Break Backwards Compatibility of Ivy Coordinates?

2017-06-01 Thread Gintautas Grigelionis
It's not a "should", it's a MUST. Ideally, pom.xml should be generated from
ivy.xml or the other way around; at the very least, maven-ant-tasks should
check the consistence between them, like this

  


The pom version is ${ivy.pom.version}

  

  

  


  



  

  



  

  

  

Gintas

2017-06-01 13:56 GMT+02:00 J Pai :

> The new organization being proposed “org.apache.ant” instead of
> “org/apache” is the right way to go IMO. It’s not just Ivy and applies to
> Maven co-ordinates (via pom.xml) as well. Ideally, they should match with
> each other. Using the org.apache.ant would make it fit with the groupId (in
> Maven land) and the organization naming schemes that I have seen for all
> the other projects out there.
>
> -Jaikiran
> On 01-Jun-2017, at 2:27 AM, Maarten Coene 
> wrote:
>
> I don't see how Ivy could resolve the old ant-compress ivy.xml files
> without using very special artifact patterns.So my guess is that Ivy users
> of ant-compress just use the pom.xml file.
>
> So I'd say we should fix the ivy.xml.
> Maarten
>
>  Van: Stefan Bodewig 
> Aan: dev@ant.apache.org
> Verzonden: woensdag 31 mei 17:34 2017
> Onderwerp: [antlibs] Break Backwards Compatibility of Ivy Coordinates?
>
> Hi all
>
> this is an excerpt from the cancelled vote thread for the compress
> antlib.
>
> 2017-05-31 16:40 GMT+02:00 Stefan Bodewig :
>
> > I've just realized that the ivy.xml file I've published to Nexus has
> > completely different coordinates from the one used in earlier
> > releases. It used to be
> >
> >  >   module="ant" ...>
> >  >
> > for 1.5 RC1 it is
> >
> >  >   module="ant-compress" ...>
> >  >
> > and the current master branch would create
> >
> >  >   module="ant-compress"
> >   
> and as Gintas points out, master is the only one that is using Ivy
> coordinates the way they are intended to be.
>
> All antlibs builds except for Compress are currently in a state that
> makes it impossible to release them without making changes and Compress
> is "correct" after all. So now would be a good time to decide what to
> do.
>
> We could violate Ivy's concepts and go back to what we've done before -
> the first example above. This is what the two releases of Dotnet, the
> four releases of AntUnit ant the five releases of Compress have done so
> far.
>
> The other option is to fix all Antlibs to be in line with Ivy's concepts
> (as Compress is inside master right now). This runs the risk of breaking
> things for people who use Ivy to retrieve the Antlibs (or maybe not, if
> they pick them up via their POMs as those have been correct) with all
> future releases of the three Antlibs that have had releases.
>
> I tend to go with the second option and list it as a backwards
> incompatible change.
>
> Any preferences?
>
> Stefan
>
> -
> 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 pull request #37: Don't pollute the source lib folder during ivy ret...

2017-06-01 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #27: Fix IVY-1540

2017-06-01 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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: Release notes for IVY-1528

2017-06-01 Thread J Pai
Thanks Nicolas.

-Jaikiran
On 01-Jun-2017, at 5:24 PM, Nicolas Lalevée  wrote:

done.

Thanks
Nicolas

> Le 1 juin 2017 à 13:46, J Pai  a écrit :
> 
> The PR for this issue https://issues.apache.org/jira/browse/IVY-1528 was 
> merged a few days back, but I think we forgot to resolve the JIRA and include 
> this in the release notes. Can someone with the access rights please do so?
> 
> -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



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



Re: [antlibs] Break Backwards Compatibility of Ivy Coordinates?

2017-06-01 Thread J Pai
The new organization being proposed “org.apache.ant” instead of “org/apache” is 
the right way to go IMO. It’s not just Ivy and applies to Maven co-ordinates 
(via pom.xml) as well. Ideally, they should match with each other. Using the 
org.apache.ant would make it fit with the groupId (in Maven land) and the 
organization naming schemes that I have seen for all the other projects out 
there.

-Jaikiran 
On 01-Jun-2017, at 2:27 AM, Maarten Coene  
wrote:

I don't see how Ivy could resolve the old ant-compress ivy.xml files without 
using very special artifact patterns.So my guess is that Ivy users of 
ant-compress just use the pom.xml file.

So I'd say we should fix the ivy.xml.
Maarten

 Van: Stefan Bodewig 
Aan: dev@ant.apache.org 
Verzonden: woensdag 31 mei 17:34 2017
Onderwerp: [antlibs] Break Backwards Compatibility of Ivy Coordinates?

Hi all

this is an excerpt from the cancelled vote thread for the compress
antlib.

2017-05-31 16:40 GMT+02:00 Stefan Bodewig :

> I've just realized that the ivy.xml file I've published to Nexus has
> completely different coordinates from the one used in earlier
> releases. It used to be
> 
>module="ant" ...>
>  
> for 1.5 RC1 it is
> 
>module="ant-compress" ...>
>  
> and the current master branch would create
> 
>module="ant-compress"
>   

Re: Release notes for IVY-1528

2017-06-01 Thread Nicolas Lalevée
done.

Thanks
Nicolas

> Le 1 juin 2017 à 13:46, J Pai  a écrit :
> 
> The PR for this issue https://issues.apache.org/jira/browse/IVY-1528 was 
> merged a few days back, but I think we forgot to resolve the JIRA and include 
> this in the release notes. Can someone with the access rights please do so?
> 
> -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



Release notes for IVY-1528

2017-06-01 Thread J Pai
The PR for this issue https://issues.apache.org/jira/browse/IVY-1528 was merged 
a few days back, but I think we forgot to resolve the JIRA and include this in 
the release notes. Can someone with the access rights please do so?

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



[GitHub] ant-ivy pull request #24: Fix IVY-1555

2017-06-01 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 #21: Fix IVY-1495

2017-06-01 Thread asfgit
Github user asfgit closed the pull request at:

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


---
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 logo as SVG

2017-06-01 Thread Gintautas Grigelionis
I noticed that ASF apparently has converted a bunch of project logos to
SVG. In particular, Ant has an SVG logo. Is there an official channel at
ASF (like, a branding office?) that we could use to get Ivy logo vectorized?

Gintas