I've produced a draft layout on the Wiki.
Comments welcome!
https://cwiki.apache.org/confluence/x/yg94Bw
On Thu, 15 Aug 2019 at 14:43, Matt Sicker wrote:
>
> The layout you propose sounds reasonable to me.
>
> On Thu, Aug 15, 2019 at 08:32, sebb wrote:
>
> > The Ruby tool and some sample output:
The Apache Commons VFS Project team is pleased to announce the release of
Apache Commons VFS Project 2.4.1-SNAPSHOT.
Apache Commons VFS is a Virtual File System library.
New features and bug fix release.
Changes in this version include:
Fixed Bugs:
o VFS-725: [Local]
org.apache.commons.vfs2.Fi
Hi all,
I've been working on the BSP tree refactor and general API cleanup for a while
now and I finally have the core and Euclidean classes complete. I have the code
in a draft PR on github [1] and I'm hoping to get as much feedback on it as I
can. Everything is in its final state from my poin
On Thu, 15 Aug 2019 at 14:50, Matt Sicker wrote:
>
> I know it’s policy, but why exactly do we have to provide checksum files
> when the asc file is a already a checksum (and most likely based on SHA256
> or 512 anyways)?
I assume because it's harder to validate a sig; the hash is better than not
I know it’s policy, but why exactly do we have to provide checksum files
when the asc file is a already a checksum (and most likely based on SHA256
or 512 anyways)?
On Thu, Aug 15, 2019 at 04:03, sebb wrote:
> I have had to fix several download pages recently because they
> referred to sha512 in
The only difference between the generated download file and my updated
one is that the generated one puts sha1 signatures on the files because
of an older version of the build plugin. I suppose I could upversion the
build plugin to ensure that I only get 256 signatures. But I think that
point w
The layout you propose sounds reasonable to me.
On Thu, Aug 15, 2019 at 08:32, sebb wrote:
> The Ruby tool and some sample output:
>
> http://svn.apache.org/repos/asf/commons/scripts/
> examples/
> pomskel.rb
>
> On Thu, 15 Aug 2019 at 14:08, sebb wrote:
> >
> > On Thu, 15 Aug 2019 at 13:06, Cl
The Ruby tool and some sample output:
http://svn.apache.org/repos/asf/commons/scripts/
examples/
pomskel.rb
On Thu, 15 Aug 2019 at 14:08, sebb wrote:
>
> On Thu, 15 Aug 2019 at 13:06, Claude Warren wrote:
> >
> > Since the POM is an XML document how about a simple XSLT that will convert
> > the
I think these issues should be sorted out. Let me know if you find any
more.]
Cheers,
-Rob
On 8/15/2019 5:57 AM, sebb wrote:
It looks like the pom has not been updated to change the SCM.
There are various other issues, e.g. download hash types.
The tag obviously cannot/must not be updated,
The download xml file is generated from the pom, so the pom must be fixed too.
On Thu, 15 Aug 2019 at 13:57, wrote:
>
> This is an automated email from the ASF dual-hosted git repository.
>
> chtompki pushed a commit to branch 1.X
> in repository https://gitbox.apache.org/repos/asf/commons-beanut
On Thu, 15 Aug 2019 at 13:06, Claude Warren wrote:
>
> Since the POM is an XML document how about a simple XSLT that will convert
> them all to the same format.
Unfortunately I don't think it's simple.
Comments on their own line apply to the following tag -- but not always.
And a comment at the
Working on this now. Thanks for the eyes.
-Rob
On 8/15/2019 5:57 AM, sebb wrote:
It looks like the pom has not been updated to change the SCM.
There are various other issues, e.g. download hash types.
The tag obviously cannot/must not be updated, so I wonder if one
approach would be to create
Since the POM is an XML document how about a simple XSLT that will convert
them all to the same format.
Alternatively an XML diff could be performed where each leaf node is
contextualized by generating the the path from the root to the leaf, the
can be sorted and a standard diff performed to deter
I think it might be useful to try to work towards standardising the
order of sections within POMs.
This will make it easier to compare them across components.
(e.g. to see why one pom works and another fails!)
And should be easier to maintain.
In particular, I would like to move the developer and
It looks like the pom has not been updated to change the SCM.
There are various other issues, e.g. download hash types.
The tag obviously cannot/must not be updated, so I wonder if one
approach would be to create a branch from the tag and build the site
from that?
Sebb.
-
Here is the link for the related bug:
https://issues.apache.org/jira/browse/MATH-1495
I have suggested two possible fixes when NaturalRanking#rank() is called on
an array of all NaNs:
1) throwing an IllegalArgumentException
2) Returning an empty array
I want to create a pull request regarding it,
I have had to fix several download pages recently because they
referred to sha512 instead of sha256.
Please would RMs double-check that the pom has the correct setting and
that the generated download_xyz.xml file corresponds with the file
names?
In future, I think the hash setting should *always*
17 matches
Mail list logo
