My vote: +1 (binding)
Verified:
+1 sha512 sha256
+1 asc / KEYS
+1 src zip vs tar.gz
+1 bin zip vs tar.gz vs jar
+1 src vs git (missing in src: README.md CONTRIBUTING.md;
whitespace differences in commons-daemon-1.2.0-native-src)
+1 mvn repo vs dist
+1 mvn apache-rat:ch
laude's email I see it is it's *use* that needs explanation!
The only dependencies in that code seem to be within the
org.xenei.bloomfilter.collections package which currently include use of
Jena's extended iterator classes.
This could probably be refactored, if this package is als
gt; concerns about conflicts with existing code. Duplication with of
> functionality was the main concern as I recall.
>
> Claude
>
> On Wed, Sep 11, 2019, 09:43 Stian Soiland-Reyes wrote:
>
> > On Wed, 11 Sep 2019 18:12:24 +0200, Gilles Sadowski <
> gillese...@gmail.com
ell if we include the container implementation or are they
more for disk-based collections?
--
Stian Soiland-Reyes
https://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Gary, thanks for putting together an RC and the thorough description on
how to verify releases! (perhaps some got scared.. we don't need
everyone to test everything though!)
My vote is: +1 (binding)
Checked:
[+] checksums vs *.sha512 vs VOTE email vs maven repo
[+] git tag vs commit
[*] git vs
gt;
>
> Best regards,
> Gilles
>
>
> ---------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna
On 15 Jan 2015 11:06, "Sergio Fernández" wrote:
> Therefore my proposal for Commons RDF is the following:
>
> * Commons RDF proposes an API that addresses portability issues. I'd
recommend to start form what we currently have at github which was actually
designed by committee and both Jena and Se
ns rdf api is a project that
>> principally aims to create a set of interfaces, and not host any of
>> the scalable implementations of the API. Stian Soiland-Reyes has
>> written a basic implementation, but in practice, any large dataset
>> will not load into that implementation
>> specifically to work on the relevant code, that once pull requests are
>> suggested, the discussion gets going for a few days and then falls
>> off. And eventually, once the API is stable it will fall off
>> altogether to almost zero. That last reason is the main reason for why
>> a
---
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/-0001-9842-9718
-
To
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/-0001-9842-9718
--
> instance" and return a fixed identifier for all BNode. If so the identifier
> is obviously pointless. If on the other hand one would have to assign
> identifier to all the objects the complexity of the implementation this
> would make implementations more complex both in terms of c
I hope you would still feel welcome to become an unofficial mentor
(teaching us the "Apache Commons way" perhaps) even if you haven't got the
right badges (yet). :)
Other incubator projects have also had unofficial mentors - it's a good way
into Incubator PMC.
On 29 Jan 2015 14:29, "Benedikt Ritt
elopers who are working with Semantic Web
technologies in the JVM. The initial committers are core contributors
to that community.
=== Core Developers ===
* Sergio Fernández (wikier dot apache dot org)
* Andy Seaborne (andy dot apache dot org)
* Peter Ansell (ansell dot apache dot org)
* Stian So
applications to work.
>
> Maybe we should elaborate about this in our versioning guide lines...
>
> Regards,
> Benedikt
>
>
>>
>> I am not trying to say that the system is perfect, but that is what
>> the general behaviour seems to be, even with people who
I am not speaking for Reto, but I imagined that since Reto has joined
the CommonsRDF incubator proposal, then his sandbox-code would
eventually turn into pull requests and branches on the incubator
codebase so that we can evaluate each of the differences separately.
On 19 February 2015 at 06:54,
entation but about a proof
> of-concept implementation against a SPARQL Backend as a mean to evaluate
> design decisions in the API.
>
> Cheers,
> Reto
>
> On Thu, Feb 19, 2015 at 4:01 PM, Stian Soiland-Reyes
> wrote:
>
>> I am not speaking for Reto, but I imagined that
vements like the ones staged for
> BCEL 6.0.
>
> Emmanuel Bourg
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (incubating)
http://orcid.org/000
->
com.example.api:example-api:jar:[1.0,2.0)] -> [Help 1]
> What is the evidence that a major bump causes warnings?
See above.
Note that a quick grep in my big .m2/repository didn't reveal any
dependencies on commons* that used ranges - probably because of
Commons being good
Right, just keep in mind:
For contributions, you as the committer would be responsible for the
content being IP clean, not the pull request submitter.
How do you do this from a larger contribution (e.g. 3 new classes) from a
github user known only as "msTentactle"?
If she has signed the CLA, the
I generally prefer one groupId matching the git repository somehow (e.g.
org.apache.commons.rdf), but +1 to the below and be aligned with the rest
of (modern) Commons. Also we won't have that many modules.
On 28 Mar 2015 16:51, "Gary Gregory" wrote:
> On Sat, Mar 28, 2015 at 9:40 AM, Benedikt Rit
a-page -> [Help 1]
how is the README updated now?
On 9 April 2015 at 00:53, Stian Soiland-Reyes wrote:
> Looks great! The travis is nice as it also comments on pull requests.
>
>
> .. but .. why are all the README links for homepage, JavaDoc, etc. wrong?
>
> e.g.
> https://
>>> > >>
>>>> > >> Regards,
>>>> > >> Benedikt
>>>> > >>
>>>> > >> [1] http://travis-ci.org
>>>> > >> [2] http://coveralls.io
>>>> > >> [3] https://github.com/jirutka/maven-badges
>>>> > >> [4] http://shield.io
>>>> > >> [5] https://github.com/britter/commons-lang
>>>> > >>
>>>> > >>
>>>> > >>
>>>> > >
>>>> > > -
>>>> > > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>>> > > For additional commands, e-mail: dev-h...@commons.apache.org
>>>> > >
>>>> > >
>>>> >
>>>> >
>>>> > --
>>>> > http://people.apache.org/~britter/
>>>> > http://www.systemoutprintln.de/
>>>> > http://twitter.com/BenediktRitter
>>>> > http://github.com/britter
>>>> >
>>>>
>>>>
>>>>
>>>> --
>>>> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>>>> Java Persistence with Hibernate, Second Edition
>>>> <http://www.manning.com/bauer3/>
>>>> JUnit in Action, Second Edition <http://www.manning.com/tahchiev/>
>>>> Spring Batch in Action <http://www.manning.com/templier/>
>>>> Blog: http://garygregory.wordpress.com
>>>> Home: http://garygregory.com/
>>>> Tweet! http://twitter.com/GaryGregory
>>>>
>>>
>>>
>>>
>>> --
>>> http://people.apache.org/~britter/
>>> http://www.systemoutprintln.de/
>>> http://twitter.com/BenediktRitter
>>> http://github.com/britter
>>>
>>
>>
>>
>> --
>> http://people.apache.org/~britter/
>> http://www.systemoutprintln.de/
>> http://twitter.com/BenediktRitter
>> http://github.com/britter
>>
>
>
>
> --
> http://people.apache.org/~britter/
> http://www.systemoutprintln.de/
> http://twitter.com/BenediktRitter
> http://github.com/britter
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
Changes look non-intrusive and OK for me. I would say bump the apache
super-parent as well.
Would you let us know how you checked the changes? Using the versions
plugin, or diffing the effective poms?
On 27 Aug 2015 13:47, "Bernd Eckenfels" wrote:
> Hello,
>
> I plan to release commons-parent, t
ponent has been
>> graduated?
>> > I'm fine with the KEYS file location being in the vote thread, but just
>> thought it
>> > would be worth checking.
>>
>> As I pointed in a previous thread, although we g
-rdf-jena-0.5.0
>> > commons-rdf-rdf4j-0.5.0
>> > commons-rdf-jsonld-java-0.5.0
>> > commons-rdf-integration-tests-0.5.0
>> >
>> > The Maven Staging repository can be found at:
>> >
>> > https://repository.apache.org/
til
> 2018-01-14T03:00:00Z
> (this is UTC time).
>
>
>
> Cheers,
> -Rob
>
> [1] http://apache.org/foundation/voting.html
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional co
ll/25
proposing mutator functions.
--
Stian Soiland-Reyes
The University of Manchester
http://www.esciencelab.org.uk/
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additiona
On Fri, 25 Aug 2017 19:19:58 +0100, Stian Soiland-Reyes
wrote:
> This came up also for commons rdf where we also have everything immutable,
> which I think is a good principle to keep for modern Java 8 programming.
>
> So you need a mutator function like in (4) that either r
On Mon, 12 Feb 2018 18:10:56 -0700, Gary Gregory wrote:
> On Fri, Feb 9, 2018 at 10:05 AM, Stian Soiland-Reyes
> I've not had time to review this yet but I hope to get to it sometimes this
> week.
Thanks. I'll wait for that before prepping a 1.6 RC so we get time to
decide i
t;
>>>>
>>>> Project: http://git-wip-us.apache.org/repos/asf/commons-csv/repo
>>>> Commit:
>>>> http://git-wip-us.apache.org/repos/asf/commons-csv/commit/f66a8390
>>>> Tree: http://git-wip-us.apache.org/repos/asf/commons-csv/tree/f66a8390
>>
s one out
and can just go with the cleanest code :)
On 16 February 2018 at 11:22, sebb wrote:
> On 16 February 2018 at 10:01, Stian Soiland-Reyes wrote:
>> I agree in general for .clone() on objects - and I'm trying to move
>> away from using .clone() in that Commons RDF
such comments :)
(It was also used for copying the headers, which was also String[])
--
Stian Soiland-Reyes
The University of Manchester
http://www.esciencelab.org.uk/
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail:
gets a
very clean Parser interface to implement, no abstract class needed. It
might however need to check itself that the config is complete enough
for its needs as in theory it could be a null-config with nothing set.
I'll come back to the alternative ParserBuilder interface
which guides
On Tue, 20 Feb 2018 16:49:23 +, Stian Soiland-Reyes
wrote:
> ajs6f and others who like talking about immutability and fluent APIs:
> I'll come back to the alternative ParserBuilder interface
> which guides the client caller step by step straight into a parsed file.
OK, so
che.org%3E
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
indicate that the project has yet to be fully endorsed by the ASF.
sha1 checksums:
965cbbb52946ae9ba710ab19a8fb931fbfe65e7f
apache-commons-rdf-0.3.0-incubating-src.zip
9e08b3edcc633eb07a1c303b1939a0faaebb6c1f
apache-commons-rdf-0.3.0-incubating-src.tar.gz
--
Stian Soiland-Reyes
http://orcid.org
/site target/site-content/commons-rdf-$a ;
done
cd target/site-content/
svn add commons-rdf-*
svn commit -m "submodules"
Any ideas..?
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mai
On 16 November 2016 at 11:26, Stian Soiland-Reyes wrote:
> But I could not get it to publish the submodule sites correctly.
> mvn clean package site-deploy
>
> overwrites the main site with the last module's site instead! (Do not use!)
https://maven.apache.org/plugins/
ps://github.com/apache/incubator-commonsrdf/
https://commonsrdf.incubator.apache.org/apidocs/
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additio
tion Framework"
> would help as there are other possible meanings for the acronym RDF.
> Most are unlikely to apply but the reader should not have to research this.
>
>
> On 16 November 2016 at 11:15, Stian Soiland-Reyes wrote:
>> The Apache Commons RDF team is pleased to an
OK, I'll go straight to VOTE in a couple of days to allow
dev@commonsrdf list to sync up first :)
(One questions would be how to do mailing list transition)
On 16 November 2016 at 13:30, Jochen Wiedmann wrote:
> On Wed, Nov 16, 2016 at 2:22 PM, Stian Soiland-Reyes wrote:
&g
eviewing the
> still evolving RDF4J integration, have been deferred to the future and
> they would not be easily addressed if a 1.0 release line was declared
> now.
>
> However, that isn't a reason to keep it in incubation. Good luck!
>
> Cheers,
>
> Peter
>
> On
> > return new SimpleRDF();
> > }
> >
> > Is/should a service loader be used to allow pluging in/discovering
> > implementations?
> >
> > Gary
> >
> > On Nov 16, 2016 5:22 AM, "Stian Soiland-Reyes" wrote:
> >
> > Common
6fcd39a8ee7426826e7b25e5cfe0628820;hp=b05e3e6e6acad0baeeb7e19358093232119548bb
>
> At list for the the result at target/staging looks good when executing: mvn
> clean site site:stage
>
> Please Stian, take a look to double check it.
>
> Cheers,
>
>
> On Thu, Nov 17, 2016 at 12:25 AM, Gilles
> wro
> <https://builds.apache.org/job/commons-beanutils/ws/> &&
> /home/jenkins/tools/java/latest1.6/bin/java -Xmx49M '${argLine}' -jar
> <https://builds.apache.org/job/commons-beanutils/ws/target/surefire/surefirebooter305925594730864.jar>
>
> &l
the contents of the module here:
>
> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=tree;f=commons-rng-build-tools;h=a126e20df3ed8921783b0ca4754e33f6ed6e9692;hb=refs/heads/RNG-30__sampling
>
>
>>
>> Cheers,
>> Jörg
>>
>>
>>>
>>> Regards,
>>> Benedikt
>>>
>>>
>>>>
>>>>
>>>> Regards,
>>>> Gilles
>>>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
he/commons/commons-
>> jcs-core/2.0-beta-2/
>>
>> Bye, Thomas.
>>
>>
>> -
>> To unsubscribe, e-mail: user-unsubscr...@commons.apache.org
>> For additional commands, e-mail: user-h...@commons.apache.org
>>
>>
--
Stian Soi
You can delete it, it was my attempt to test the build on different jdk
versions not already on Jenkins slaves, I think there were some oracle vs
OpenJDK issues in the last Release Candidate.
On 18 Nov 2016 10:21 pm, "Benedikt Ritter" wrote:
> Hello,
>
> we have this jenkins job that executes a
mentations, which would require use of Maven for dependencies. I
thing a second tutorial could cover that aspect.
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apac
m dev@commonsrdf:
+1 Stian Soiland-Reyes (Commons PMC binding)
+1 Benedikt Ritter (Commons PMC binding)
+1 Gary Gregory (Commons PMC binding)
Proposed component name: rdf
Proposed package name: org.apache.commons.rdf
Source code of RDF component:
https://git-wip-us.apache.org/repos/asf?p=incu
Within the assembly descriptor you can use a for the modules
you want to include.
See
https://github.com/apache/commons-jcs/blob/trunk/commons-jcs-dist/src/assembly/bin.xml
for example, here the assembly is done in a -dist submodule itself, but it
can also be done directly in the parent as long a
I think I'll tend towards agreeing with Jochen here, rather get half the
modules out early than fight ourselves with versioning workarounds if the
rest of the modules are not ready for prime time.
However I see concerns of selective "part releases" and reproducible
builds, so I would do this using
On 23 November 2016 at 13:47, Stian Soiland-Reyes wrote:
> [Note: this is the Commons PMC vote on dev@commons - there's a
> concurrent IPMC VOTE thread on general@incubator]
>
> Please VOTE on graduating Commons RDF as new component:
Thanks to everyone who voted! The results
I think Gilles' reasoning is sound for semantic versioning and releases, in
line with OSGi principles. However I think that would be better suited in a
large or enterprise project with mainly internal usersnpf the libraries
that can play along, not in Apache Commons which are making general
availab
[RDF]. (I'll send a separate
reminder about this to the dev@commonsrdf list before it closes)
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.a
ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182021&linkCode=as2&tag=garygregory-20&linkId=31ecd1f6b6d1eaf8886ac902a24de418%22
>
>
> <
http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182021
>
> Spring Batch in Action
> <
https://www.amazon.com/gp/product/1935182951/ref=as_li_tl?ie=UTF8&camp=1789&creative=9325&creativeASIN=1935182951&linkCode=%7B%7BlinkCode%7D%7D&tag=garygregory-20&linkId=%7B%7Blink_id%7D%7D%22%3ESpring%20Batch%20in%20Action
>
>
> <
http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1935182951
>
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
Stian Soiland-Reyes
http://orcid.org/-0001-9842-9718
gory-20&linkId=cadb800f39946ec62ea2b1af9fe6a2b8>
>>
>>
>> <http://ir-na.amazon-adsystem.com/e/ir?t=garygregory-20&l=am2&o=1&a=1617290459>
>> JUnit in Action, Second Edition
>>
>> <https
Yeah, that could be the better way, with a branched off commit for the
"shrunk" project with a smaller list in the parent, then no
particular flags are needed to build from the resulting tag or source repo.
I initially planned to do so within the Taverna project (before we moved to
ASF), as it co
27;Admins'), and asked INFRA
to change it to the commons notification scheme (issues@commons). I
also put Apache Commons Developers (e.g. issues@commons) as the
"Lead".
I also renamed the Jenkins build from incubator-commonsrdf to
commons-rdf (but did not change it's git repo sett
that the general rule for Commons is simplicity,
both for the user and for developers. While an unnecessary module upgrade
is not as "beautiful" as clean semantic version separations per module, it
is, I would argue, simpler to deal with for both consumers, developers and
release managers.
te:
> On Wed, Nov 30, 2016 at 1:34 AM, Stian Soiland-Reyes
> wrote:
>
>> Just a thing I noticed..
>>
>> In https://dist.apache.org/repos/dist/release/commons/commons-
>> parent/commons-parent-41/
>> and before we had a -src.tar.gz and -src.zip
>
tches: ...
> [ ] -1 No, do not release it because ...
>
> This vote will close in 72 hours, at 2016-12-03T00:00:00Z (this is UTC
> time).
> --
>
>
> Thanks,
> Gilles
>
>
> -----
> To unsubscribe, e-mail: dev-unsubscr...@commons.a
components are?
>
> thanks,
> chas
>
> > On Dec 1, 2016, at 9:15 AM, Gary Gregory wrote:
> >
> > [editing subject]
> >
> > On Thu, Dec 1, 2016 at 9:14 AM, Gary Gregory
> wrote:
> >
> >> I am canceling this VOTE to deal with the missing src f
aven ..?
On 3 Dec 2016 4:41 pm, "Gary Gregory" wrote:
So, when I run:
mvn clean deploy -Duser.name=ggregory -Prelease -Ptest-deploy
The zip and gz files are created but not signed or hashed.
Thoughts?
Gary
On Sat, Dec 3, 2016 at 2:53 AM, Stian Soiland-Reyes
wrote:
> I would
gt;> --
>> >> Matt Sicker
>> >>
>> >
>> >
>> >
>> > --
>> > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
>> > Java Persistence with Hibernate, Second Edition
>> > <https://www.amazon.com/gp/produ
That sounds like not a problem at all as RAT passes on the RC.
Just regenerate the site after releasing. (We have to verify download page
manually anyway).
(Perhaps building the site from the RC's tar-ball rather than the "dirty"
mvn tree post release is safer)
I think it would only block a rele
On 11 December 2016 at 06:11, Gilles wrote:
>> This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC6).
>> Tag name:
>> RNG_1_0_RC6 (signature can be checked from git using 'git tag -v')
>>
>> Tag URL:
>>
>>
>>
>> https://git-wip-us.apache.org/repos/asf?p=commons-rng.git;a=commit;h=4581
We had waited for Infra to do the rename/move of the commons rdf git
repository; that was just completed two days ago.
I did not republish site yet from src as half the pages would have many
broken links to the new repo; in src/site it is already updated. Sergio was
looking at ways to ensure the
I agree on not expanding too much on the roles and would favour removing
PPMC roles except for those who are listed only as emeritus.
On 17 Jan 2017 10:30 am, "Jochen Wiedmann"
wrote:
> Hi, Sergio,
>
> On Tue, Jan 17, 2017 at 8:31 AM, Sergio Fernández
> wrote:
>
> > adjusting Stian's role [1} I
Agree with Benedikt here, if it's only the .toString() that is important,
then "string" should appear in the method name; otherwise we need to do
Commons Collections style handling of anything that can be empty or not.
To support null (which isn't really "empty" but missing), perhaps just have
the
ou still have to make a such specialization,
or is that automatic?
BTW - in your approach, would it work to run the tests out of the box
from an IDE like Eclipse? I think that is quite important so Commons RDF
can be maintainable by many people in Apache Commons.
--
Stian Soiland-Reyes
U
On Mon, 30 Jan 2017 10:20:46 +, Stian Soiland-Reyes
wrote:
> BTW - in your approach, would it work to run the tests out of the box
> from an IDE like Eclipse? I think that is quite important so Commons RDF
> can be maintainable by many people in Apache Commons.
They did run out o
Modules of Text would make sense if we get larger differences of
dependencies; if it is just different functionality, subpackages within a
single module would be better.
On 30 Jan 2017 5:53 pm, "Emmanuel Bourg" wrote:
> Le 30/01/2017 à 15:16, Rob Tompkins a écrit :
>
> > I lean towards going wit
le or immutable? How should the
settings be kept? Fields, map, or what? Does it make sense with an
interface, abstract class (keeps settings) and implementations
(processess settings), or should we have a single ParserFactory class
and have a new internal interface
Do we have any GSOC2017 ideas for Apache Commons? Tag them with the label
"gsoc2017" in Jira!
Any volunteers to mentor GSOC2017 students? All committers are eligible, I
guess for Commons that is a bit special (as all ASF committers have write
access), but I guess if you have contributed before to
Adding a class with a plan to @deprecate it, something doesn't sound right.
:)
We should not be putting much effort (and future maintainability) into
adding functionality in Lang that jdk8 already (easily) can do. The point
of Lang is to complement JDK's Lang classes and friends, not to backport
w
Thanks!
Not being a mathematician I am afraid I have not been able to review the
correctness of the equation use.
Overall the addition looks good and well commented. The javadoc is a bit
sparse and could do with some more hyperlinks.
I have some code design questions you may be able to clarify:
On Mon, 08 May 2017 14:16:12 +0200, Gilles wrote:
> > Overall the addition looks good and well commented. The javadoc is a
> > bit
> > sparse and could do with some more hyperlinks.
> Strange; I thought that it was doing rather well on this point.
> Can you be more specific? [Please open a JIRA r
On Tue, 9 May 2017 13:29:21 +0100, Stian Soiland-Reyes wrote:
> I can only see this "value()" style make sense if there is also a common
> interface, perhaps DoubleFunction?
> https://docs.oracle.com/javase/8/docs/api/java/util/function/DoubleFunction.html
DoubleUnaryOpera
On Tue, 09 May 2017 14:52:09 +0200, Gilles wrote:
> [I specifically avoided "apply" so that it is free for when the
> component
> targets Java 8.]
>
> Can the "apply" method be static?
No, interface implementations can't be static (and it is not possible to
make an interface of static methods).
Agree to wait for Java 9 GA before it's general practice. Would not -1 a
release candidate with nicer Java 9 javadoc though!
With Java 8 there were many issues with javadoc checks and options
incompatible with Java 7. I I don't know if anything changes here for
Java 9, but trying to comply both
git commit --force"
+1 to include the "usual IDE suspects" (emacs ~ files anyone?) in
the .gitignore, particularly for Commons which may see many "drive by"
contributors who don't have their global gitignore perfectly set up. (I
don't even have one!)
Should we add it
Personally I am happy about source distributions accompanying the jars in
Maven Central, which are actually rebuildable as opposed to the
-source.jars.
they continue to be retrievable using Maven version mechanisms, compares to
more fragile scripts crawling archive.apache.org (dist only contains t
On 13 Aug 2017 7:43 pm, "Pascal Schumacher"
wrote:
Hello everybody,
an opinions on moving commons-launcher to dormant?
The last release is from 2007 and their have not been any bugfix or feature
addition commits since.
+1
This came up also for commons rdf where we also have everything immutable,
which I think is a good principle to keep for modern Java 8 programming.
So you need a mutator function like in (4) that either returns a new
immutable (but changed) CSVRecord; or alternatively a different
MutableCSVRecord
; executed sequentially.
>>>
>>> Cheers,
>>> Pascal
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> F
Sergio, Let me know if you are going and want to collaborate on Commons RDF
slides/demo!
(I don't think I am going this year I'm afraid. )
On 29 Jan 2016 14:01, "Sergio Fernández" wrote:
> On Fri, Jan 29, 2016 at 12:59 PM, Siegfried Göschl <
> siegfried.goes...@it20one.com> wrote:
> >
> > there
use...
>
> Thanks!
>
> Stefan
>
> -------------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (inc
ours from now, i.e. after
> 1930 GMT 05-April 2016
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this release because...
>
> Thanks!
>
> Stefan
>
> --
Right, dist is just using SVN as a convenient way to manage the
distribution tree for the download mirrors, that it is version controlled
is a nice side effect, it would not work well with Git (except possibly
with LFS) as every binary and source release of ASF since the dist repos
inception is in
e will close no sooner than 72 hours from now,
> i.e. sometime after 23:00 GMT 18 Apr 2016
>
>
> [ ] +1 Release these artifacts
> [ ] +0 OK, but...
> [ ] -0 OK, but really should fix...
> [ ] -1 I oppose this releas
+1 for the change for future releases. Being able to do svn mv (or rm) on a
single folder simplifies releasing and reduces chance of errors.
Is the -src and -bin endings already used across all of Commons? That would
be a bit more important without source/ and binaries/
(Do some have download art
sting
releases to the new layout and let the existing stay until they have been
replaced by newer versions? (This would add another 550 MB for mirrors
that don't understand symlinks)
On 18 Apr 2016 09:55, "Gilles" wrote:
> On Mon, 18 Apr 2016 09:12:16 +0100, Stian Soiland-Reyes wrote:
lack "-bin" (oh no!) - so they
could just be changed to the new pattern manually within the new
layout.
On 18 April 2016 at 10:28, Gilles wrote:
> On Mon, 18 Apr 2016 10:22:53 +0100, Stian Soiland-Reyes wrote:
>>
>> Changing download links for all existing releases (wit
olution that does not create
> new confusions.
>
> Gilles
>
>
>> Emmanuel Bourg
>>
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands,
lti-module POMs, e.g. parent
is apache-foo while submodules are
foo-bar etc.
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-uns
These downloads lack -bin / -src suffixes:
On 18 April 2016 at 10:43, Stian Soiland-Reyes wrote:
> stain@biggie:~/Downloads/912/mirrors.ukfast.co.uk/sites/ftp.apache.org$
> find . -type f | grep -v txt | grep -v -- -src.tar.gz | grep -v --
> -src.zip | grep -v -- -bin.zip
------
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/-0001-9842-9718
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org
On 18 April 2016 at 13:43, Stian Soiland-Reyes wrote:
> -1 apache-rat:check fails on
> src/main/resources/commons-xdoc-templates/download-page-body.xml and
> src/main/resources/commons-xdoc-templates/download-page-foot.xml
These are not really XML files, but templates to be insert
1 - 100 of 250 matches
Mail list logo
