Exactly, Tasks/tar.html and Tasks/unzip.html (which aggregates
unjar/unwar/unzip/untar) do not mention xz on master.
xz then should be a link to ../install.html#librarydependencies
Gintas
2018-01-20 18:13 GMT+01:00 Stefan Bodewig :
> On 2018-01-20, Gintautas Grigelionis wrote:
>
> > Could anybod
On 2018-01-20, Gintautas Grigelionis wrote:
> To recap, I would like ivy.xml to be one central descriptor of all
> dependencies and all artifacts (including the distribution archives) that
> are produced and published by the project. The release process should use
> that single descriptor by apply
On 2018-01-20, Gintautas Grigelionis wrote:
> Could anybody check the documentation of tar/untar regarding compression
> attributes?
Anything specific?
In master "xz" is a valid option as well, I'll just add it to the manual
pages. Is this what you've been asking?
Stefan
--
I squashed the commits and pushed the revised documentation to simplify the
code changes.
To recap, I would like ivy.xml to be one central descriptor of all
dependencies and all artifacts (including the distribution archives) that
are produced and published by the project. The release process shou
The PR is currently focused on fetch.xml, as discussed with Stefan; I did
not commit anything regarding signing yet except removing signatures as Ivy
artifacts from ivy.xml.
I am looking at what the distribution target does; should the distribution
archives be included in ivy.xml, then there's a l
A bit late to the discussion. I just finished going through the release
instructions. It's a lengthy process (understandably). Having been
involved in releases of some internal projects, I do not see anything
out the ordinary in these steps.
Coming to the artifact signing step, which is what t
While revising manual/install.html, I decided to cross-link optional
libraries and corresponding tasks.
Then I noticed that untar task does not mention xz compression as a
possible option, should I just add it?
Gintas
2018-01-13 20:07 GMT+01:00 Gintautas Grigelionis :
> Thanks for feedback. I ho
Thanks for feedback. I hope Ivy release people will comment, too. My would
to make both processes more similar and remove obsolete
tasks/dependencies/steps if necessary.
Gintas
P.S: http://ant.apache.org/manual/install.html#optionalTasks describes the
use of fetch.xml to download optional depende
On 2018-01-12, Gintautas Grigelionis wrote:
> I was looking at build files in Ivy project, and realised that Ivy was
> using Commons OpenPGP as well. It's still there in the build files,
> but it's not used in publishing/upload after signers were introduced;
> only for signing the distribution ar
BTW, the trouble with Commons OpenPGP is that it's not developed and the
only version available is using an ancient BouncyCastle.
Gintas
2018-01-12 18:30 GMT+01:00 Gintautas Grigelionis :
> I was looking at build files in Ivy project, and realised that Ivy was
> using Commons OpenPGP as well.
>
I was looking at build files in Ivy project, and realised that Ivy was
using Commons OpenPGP as well.
It's still there in the build files, but it's not used in publishing/upload
after signers were introduced;
only for signing the distribution archives. The question, naturally, is
whether it makes s
Hello,
I am proposing to rip off Maven Ant tasks (for reasons described in the
discussion to PR)
and Commons OpenPGP (correspondingly, fetch and signit for brevity). Ivy
can do all of that,
and it is already used by upload. The bonus is, using Ivy properly would
simplify project
setup in IDE and s
12 matches
Mail list logo
