It seems that having the site in git is possible [1]:
- have your site in a git repo
- open a INFRA Jira-Ticket
- branch "asf-site" will be published
We have 7 svn repos [2], most inactive (migrated to git), 1 active and 1 not
used for a longer time:
- antlibs, inactive repo, last change 2015, al
I'll grep through the sources and revert all changes to clone
signatures unless anybody else beats me to it.
Done
https://github.com/apache/ant/commit/2e788849136bfd75e88ce0d959810f1191d43a33
-Jaikiran
-
To unsubscribe, e-m
The ugly thing
2018-02-27 22:40 GMT+01:00 Gintautas Grigelionis :
> 2018-02-18 20:30 GMT+01:00 Stefan Bodewig :
>
>> [Personally I prefer discussion by email over discussion in github
>> issues.]
>>
>
> The beauty is that GitHub comments are echoed in mailing list, and, in
> case of PR mentioning
Github user twogee commented on the issue:
https://github.com/apache/ant-ivy/pull/63
A new version using `Deque` and providing a backwards compatible method.
Any concurrency concerns?
---
-
To unsubscribe, e-mail: d
2018-02-18 20:30 GMT+01:00 Stefan Bodewig :
> [Personally I prefer discussion by email over discussion in github
> issues.]
>
The beauty is that GitHub comments are echoed in mailing list, and, in case
of PR mentioning JIRA issues, in JIRA as well.
Gintas
2018-02-19 7:35 GMT+01:00 Stefan Bodewig :
> On 2018-02-18, Gintautas Grigelionis wrote:
>
> > 2018-02-18 20:30 GMT+01:00 Stefan Bodewig :
>
> >> On 2018-02-18, Gintautas Grigelionis wrote:
>
> >>>- https://github.com/apache/ant-ivy/pull/63 (has to do with choice
> of
> >>>generics, with a
On 2018-02-27, Gintautas Grigelionis wrote:
> More specifically, that's Ant 1.10.2 thing... so, one more regression in
> master, I suppose. 1.10.1 and 1.9.10 work fine.
> Gintas
> 2018-02-27 20:23 GMT+01:00 Gintautas Grigelionis :
>> After Ant dependency in Ivy was updated to 1.9.10, I'm gettin
Github user twogee commented on a diff in the pull request:
https://github.com/apache/ant-ivy/pull/67#discussion_r171054211
--- Diff: ivy.xml ---
@@ -61,6 +61,7 @@
+
--- End diff --
Ah, I get it... the way things wor
Github user twogee commented on a diff in the pull request:
https://github.com/apache/ant-ivy/pull/67#discussion_r171053071
--- Diff: ivy.xml ---
@@ -61,6 +61,7 @@
+
--- End diff --
Good catch, thanks. BTW, run this
More specifically, that's Ant 1.10.2 thing... so, one more regression in
master, I suppose. 1.10.1 and 1.9.10 work fine.
Gintas
2018-02-27 20:23 GMT+01:00 Gintautas Grigelionis :
> After Ant dependency in Ivy was updated to 1.9.10, I'm getting
>
> [javac] /Users/gintas/Projects/ant-ivy-asf/s
After Ant dependency in Ivy was updated to 1.9.10, I'm getting
[javac]
/Users/gintas/Projects/ant-ivy-asf/src/java/org/apache/ivy/ant/IvyCacheFileset.java:206:
error: clone() in EmptyFileSet cannot override clone() in FileSet
[javac] public Object clone() {
[javac]
Frankly, I was doubtful about the classloader change.
But, what use cases are there for java -jar ivy.jar -main ?
As I understand it, it's about resolving an artifact and lauching whatever
main class would be there in it.
So, why not bootstrapping an Ivy build in a fancy way?
But, the new classl
Github user twogee commented on the pull request:
https://github.com/apache/ant-ivy/commit/1a19f2f836cd33a25d458ed8ba9bbb3c7ce4ff96#commitcomment-27816643
Could we do release and sign in one go by adding distributions to ivy.xml
and using a separate filesystem resolver to copy and sig
On 2018-02-27, Jaikiran Pai wrote:
> The first round of this might not be publicly usable and we might have
> to redo the steps as and when we fix things in the release process. So
> maybe we should attempt an intermediate release before doing a 2.5.0.
As long as we stop before pushing anything i
No I hadn’t :) Will check it out tonight.
-Jaikiran
On Tuesday, February 27, 2018, Jan Matèrne (jhm) wrote:
> Have you seen doc/dev/makerelease.html ?
> But updating (and maybe automating) is a good idea. ;)
>
> Jan
>
> > -Ursprüngliche Nachricht-
> > Von: jaiki...@apache.org [mailto:ja
Have you seen doc/dev/makerelease.html ?
But updating (and maybe automating) is a good idea. ;)
Jan
> -Ursprüngliche Nachricht-
> Von: jaiki...@apache.org [mailto:jaiki...@apache.org]
> Gesendet: Dienstag, 27. Februar 2018 13:59
> An: notificati...@ant.apache.org
> Betreff: ant-ivy git co
- https://github.com/apache/ant-ivy/pull/67 (a one-liner; anybody
sees some side effects?)
I don't understand the issue. Is this a documented way of using Ivy or
why would anybody expect it to be possible to invoke Ant via the Ivy
jar?
Somebody was interested enough to open a JIRA issu
In order to move towards a release soon, I decided to come up with an
initial set of instructions that we might have to follow to generate the
release. Most of the instructions have been borrowed from Ant's release
process. Furthermore, the instructions are based on my checking out the
release
18 matches
Mail list logo
