Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Gary Gregory]

>From the src zip: MD5, SHA1, ASC OK.

-1 because I cannot run 'mvn clean site' not matter what version of Java I
use: 6, 7, or 8.

Users must be able to download the source zip or checkout this release tag,
apply mods and rebuild and see that they did not cause regressions or break
things.

Building with 'mvn clean site' fails with Java 6 and Maven 3.0.5 due to:

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project commons-beanutils: Execution default-site of goal
org.apache.maven.plugins:maven-site-plugin:3.4:site failed: An API
incompatibility was encountered while executing
org.apache.maven.plugins:maven-site-plugin:3.4:site:
java.lang.UnsupportedClassVersionError: japicmp/maven/JApiCmpReport :
Unsupported major.minor version 51.0

This is not a blocker but MUST be documented in the RN and site IMO.

Building with 'mvn clean site' fails with Java 8 and Maven 3.3.9 due to
doclint errors; not a blocker but MUST be documented in the RN and site IMO.

Building with 'mvn clean site' fails with Java 7 and Maven 3.0.5

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 2:30.776s
[INFO] Finished at: Wed Sep 14 22:43:23 PDT 2016
[INFO] Final Memory: 51M/526M
[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on
project commons-beanutils: Error generating
japicmp-maven-plugin:0.9.0:cmp-report: Failed to generate report: Please
provide at least one resolvable
new version using one of the configuration elements  or
. -> [Help 1]

Gary



On Wed, Sep 14, 2016 at 8:45 AM, Stian Soiland-Reyes 
wrote:

> This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)
>
>
> SVN tag:
>   https://svn.apache.org/repos/asf/commons/proper/beanutils/
> tags/BEANUTILS_1_9_3_RC2/
>
> Site:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/
>
> Javadoc:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/apidocs/index.html
>
> API changes since 1.9.2 (japicmp):
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html
>
> RAT report:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/rat-report.html
>
> Distribution files (rev 15358)
>   https://dist.apache.org/repos/dist/dev/commons/beanutils/
> BEANUTILS_1_9_3_RC2/
>
>
> Distribution files hashes (SHA1):
>
> 40b7b1639eedf91b5fad5d38e6ebec01e659048f  commons-rng-1.0-src.tar.gz
> 6296dbabde10169d6365bda99f2af6dcc191e515  commons-rng-1.0-src.zip
> a221e862c8ff970a9ca3e7fbd86c3200d1f8780a  commons-rng-1.0-bin.tar.gz
> 689b2bfbdb1856d4f47851d75762aab42057805a  commons-rng-1.0-bin.zip
>
>
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>   https://repository.apache.org/content/repositories/
> orgapachecommons-1200/
>
>
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
>
> This vote will be open for at least 72 hours, let's say
> 2016-09-19T08:00:00Z
>
> --
> 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
>
>


-- 
E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
Java Persistence with Hibernate, Second Edition

JUnit in Action, Second Edition 
Spring Batch in Action 
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory

Re: [RDF] Implementation class name style

[Peter Ansell]

JSONLD-Java switched to JsonLd, after originally using uppercased
versions, to match the terminology casing used by the final
JSON-LD-API-1.0 specification:

https://www.w3.org/TR/json-ld-api/#the-application-programming-interface

The capitalisation in the project name is just kept for posterity at this point.

If it would simplify things just to rely on the prefix, you may be
able to drop the Impl suffix without confusion.

Cheers,

Peter

On 15 September 2016 at 13:01, Stian Soiland-Reyes  wrote:
> On 13 Sep 2016 2:15 a.m., "Gary Gregory"  wrote:
>>
>> For names, I like CamelCaseEvenForAcronyms, like IbmXmlSaxParser instead
> of
>> IBMXMLSAXParser.
>
> As well :-)
>
> And I am not sure which class or package prefix to use for JSONLD-Java..
> JsonLd is what is used within its classes. And RDF4J is their official
> spelling and what is used as their class prefix.
>
> But I think at this stage we don't want to rename now say RDFTerm
> interface, so would then not JsonLdRdfTermImpl look weirder than
> JsonLdRDFTermImpl?
>
> Or not so stringent, then RDF4JRDFTerm can become RDF4JTerm :)

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

Re: [RDF] adaptation methods in RDFTermFactory

[Stian Soiland-Reyes]

You mean to add unwrap() to the implementation classes? So it would just do
a cast? But we have an operator for that in Java... :-)

If you mean to add it to RDFTermFactory as a different name/style for the
many asSomething() methods, perhaps just as the name as()?

That is how Jena does it, to hide instanceof and casting:

https://jena.apache.org/documentation/javadoc/jena/org/apache/jena/rdf/model/RDFNode.html#as-java.lang.Class-

Btw, the "factory" methods might both wrap or unwrap, e.g.
JenaRdfTermFactory.asJenaNode(rdfterm) would unwrap a JenaRDFTerm
implementation directly, but still recognise a "foreign" RDFTerm which is
instead wrapped/converted to a new JenaNode instance.

I'm still worried by an API that takes "any" class, it is not too useful if
you don't know what classes are actually supported, as you see Jena
therefore also added canAs() in addition to more specific asLiteral() and
asResource().

Perhaps Andy Seaborne have views on those kind of convenience methods? They
could be added to the RDFTerm interface with a default implementation that
just tries to cast.

On 13 Sep 2016 2:00 a.m., "Matt Sicker"  wrote:

Couldn't you do the JDBC Wrapper style interface and have a generic method
like:

 T unwrap(Class cls);

Or make more specific unwrap methods like:

 T unwrap(Class cls);

If this is for implementation-specific casts and such.

On 12 September 2016 at 19:56, Stian Soiland-Reyes  wrote:

> [[ Cross-post - prefer replies to dev@commons ]]
>
> Each of the Common RDF implementations come with a RDFTermFatory
>
> http://stain.github.io/incubator-commonsrdf/integration/org/apache/
> commons/rdf/api/RDFTermFactory.html
>
> On a classical flat classloader the implementations of this factory
> can be discovered with java.util.ServiceLoader
>
>
> So if you have say a JsonLdRDFTermFactory you can call .createTriple()
> etc - and it would be backed by that implementation. As mentioned the
> marker interfaces will allow you to later on get hold of the wrapped
> object, e.g. to do some RDFS reasoning on a Jena Model or to parse it
> to a serializer.
>
>
> But what if you already have a 'native' object, e.g. a
> org.eclipse.rdf4j.model.Statement - and you want to convert it/adapt
> it to the corresponding Commons RDF API Triple?
>
> Obviously there would not be a general interface for this (without
> using ?-generics) as each backend implementation would have different
> (so far unrelated) types - but we can at least agree on the common
> style?
>
> In
>
> http://stain.github.io/incubator-commonsrdf/integration/org/apache/
> commons/rdf/rdf4j/RDF4JTermFactory.html
>
> I suggests as*() adapter methods like:
>
>
> RDF4JQuad asQuad(org.eclipse.rdf4j.model.Statement
>
> RDF4JTriple asTriple(org.eclipse.rdf4j.model.Statement statement)
>
> RDF4JTerm asRDFTerm(org.eclipse.rdf4j.model.Value value)
>
> RDF4JDataset asRDFTermDataset(org.eclipse.rdf4j.repository.Repository
> repository)
>
> RDF4JGraph  asRDFTermGraph(org.eclipse.rdf4j.model.Model model)
>
> RDF4JGraph  asRDFTermGraph(org.eclipse.rdf4j.repository.Repository
> repository)
>
>
> but also the inverse converters:
>
> org.eclipse.rdf4j.model.Value  asValue(RDFTerm term)
>
> org.eclipse.rdf4j.model.Statement
> asStatement(TripleLike tripleLike)
>
>
> (These will unpack the wrapped value if it's an RDF4JTerm - or create
> a new RDF4J native instance if it's a "foreign" class)
>
>
> Questions:
>
>
> a) Do these adapter methods belong in the RDFTermFactory or should
> there be a new family of 'adaptor factories'? (e.g. the Jena Factory
>
>
> b) What should we call these methods?  Is as*() appropriate or should
> they more closely match the createTriple() etc methods from
> RDFTermFactory?
>
> With asSomething() I wanted to hint of adaptation - rather than
> 'convert' or 'create' - but without having to commit to adaptation
> with adapt() or wrap().
>
>
> Now sometimes the implementations use the same class name as Commons
> RDF (e.g. Quad or Graph). Code-wise this is not too hard to deal with
> (avoid importing either), but it means it can get more confusing for
> downstream API users who do auto-complete and then don't know what
> direction they are adapting.
>
>
> c) Should the adapter methods have short names (e.g. asGraph()) -
> distinguished by type polymorphism and javadocs - or more verbose to
> show which particular return-type you get? (e.g. asJenaGraph() and
> asCommonsRDFGraph()) )
>
>
> d) Do we need to rename RDFTermFactory to RDFFactory (or just RDF) ?
>
>
>
> --
> 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
>
>


--
Matt Sicker 

Re: [RDF] Implementation class name style

[Stian Soiland-Reyes]

On 13 Sep 2016 2:15 a.m., "Gary Gregory"  wrote:
>
> For names, I like CamelCaseEvenForAcronyms, like IbmXmlSaxParser instead
of
> IBMXMLSAXParser.

As well :-)

And I am not sure which class or package prefix to use for JSONLD-Java..
JsonLd is what is used within its classes. And RDF4J is their official
spelling and what is used as their class prefix.

But I think at this stage we don't want to rename now say RDFTerm
interface, so would then not JsonLdRdfTermImpl look weirder than
JsonLdRDFTermImpl?

Or not so stringent, then RDF4JRDFTerm can become RDF4JTerm :)

Re: [RDF] jena, rdf4j, json-ld integrations

[Stian Soiland-Reyes]

On 13 Sep 2016 5:14 a.m., "Peter Ansell"  wrote:
> Sesame-4 will not have any more releases due to the Eclipse migration,
> so you will not have a large user-base for that. Even maintaining a
> Sesame-2.8 module may not find many users, as users who are still
> using it for the near future will likely not be migrating to Java-8
> and hence won't be integrating Commons RDF as often as those who are
> already migrating to Eclipse RDF4J.

Right, I will probably just release the sesame4 as a private one-off on
GitHub, I think it would only be useful to a narrow set of users who are
"temporarily stuck" with sesame (as I am in one project I don't want to
maintain too much) but want to wriggle their way over to RDF4j via Commons
RDF, say one class/module at the time.

Thankfully rdf4j and sesame live well on the class path together! (But I
guess that could break if RDF 4J moves on to way newer dependencies)

> Developing an integration for JSONLD-Java in the same way as I have
> setup the others with their own repositories is a possibility for that
> aspect, similar to:
>
> https://github.com/jsonld-java/jsonld-java-clerezza
> https://github.com/jsonld-java/jsonld-java-rdf2go

Yes, that could be a possibility, but I think Commons is still not quite
ready for "micro" git repositories as it would complicate web site
maintenance and release processes. it's easy enough to split out the
modules with git subtree, but not if you keep developing on both sides
afterwards. :)

> However, both Jena and Sesame/RDF4J have ended up having their
> JSONLD-Java integrations moved back into their core repositories so it
> isn't the same for everyone.

Yes, I think that would be good goal, so perhaps the JSONLD-Java model
would work here as well, then it does not matter so much "how integrated"
Commons RDF gets where - Commons could still provide an empty "glue" Maven
artifact to depend on such external integrations (or just list them on the
site)

BTW, as I'm currently the sole author of the commonsrdf-rdf4j integration I
could contribute it separately to Eclipse under the EPL, if so desired.

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Stian Soiland-Reyes]

On 14 Sep 2016 3:32 p.m., "Gilles"  wrote:
> The site can, and will be fixed, "live" (as it must be done anyway for
> the link to the Javadoc, see below).

I think it's good we keep the practice of reviewing the website as part of
an RC, as otherwise it won't happen, but I would be with you that it should
not be required to cancel an RC just to fix something in src/site. However
we might need a documented routine for how to update the site independently
without spamming the site with SNAPSHOT info (e.g. a branch from the latest
release)

>> +1 mvn apache-rat:check (if using ignores from )
> I don't understand the "if" clause.
> Report is clean when generated as part of "mvn site".

Yes, I noticed. I am special in that I run the apache-rat:check target
outside (to see if it fails), but that does not pick up config within
 :)

> It was developed within the CM repository but the code was never
> released as part of CM.

Right, no point then if it has not been released before within Commons.

> Are those a mandatory part of the distribution?
> Commons Math was never released with those files.

No (hence -0, not -1), just I would prefer them in. In .md format they are
slightly less useful within the downloaded archives than on GitHub, I agree.

(In a perfect world the assembly plugin could run a markdown to text
conversion!)

> I'd rather not redo the release steps just for files that are
> meaningful only when browsing the code repository mirror at
> Github.

That is your choice as RM as long as the RC get at least +3 :)

If the front page is fixed in git, then I'll change to a +1.

Broken links on BCEL website

[Stian Soiland-Reyes]

Hi,

There were quite a few broken links on the front page of
https://commons.apache.org/proper/commons-bcel/


I fixed directly in site-SVN (and in the source-SVN) on index.html:

6.0 Download link (!)
Javadoc link
release note links


Still the menu shows two javadoc entries:

Javadoc (Latest release)
https://commons.apache.org/proper/commons-bcel/javadocs/api-release/index.html

Javadoc (SVN latest)
https://commons.apache.org/proper/commons-bcel/apidocs/index.html


Not sure why there were two links - perhaps because 6.0 took a while
to be released.



As the menu is replicated on every page I couldn't easily fix this on
every page, so the "Latest release" links are still broken.

Should I do a branch from 6.0 tag and regenerate the site?  What
should be the correct javadoc link?

Alternatively just set up a .htaccess redirect from
javadocs/api-release/ to apidocs/ ?





-- 
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

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Stian Soiland-Reyes]

On 14 September 2016 at 23:34, Gary Gregory  wrote:
> Curious: what does "Semantic Versioning: 0.0.1" mean? And that what we
> really want?

I guess you mean as in

https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html

It's showing the calculated version difference according to semantic versioning.

>From https://github.com/siom79/japicmp
> The option --semantic-versioning tells you which part of the version you have 
> to increment in order to follow semantic versioning.

So in this case beanutiols moving from 1.9.2 to 1.9.3 is compatible
with semantic versioning increase of patch version.


Here's an example where japicmp detects a minor increase (e.g. adding
classes or methods):

http://commonsrdf.incubator.apache.org/commons-rdf-api/japicmp.html


The computer is only that clever - the above example is adding methods
to the RDFTermFactory interface; socially a major version change if
third-parties are meant to (or do so anyway) implement them, but minor
if all the implementations are within the same code base.


As within Apache Commons we have agreed to generally not release
updates that break binary compatibility, so generally if japicmp says
"semantic versioning 1.0.0" (indicating a major update)  - that should
be a red flag - if it's a true major increase we would instead rename
the artifact (e.g. beanutils2);  I guess we would let it masquerade as
a minor update if it was for instance a "breaking change" in an
internal/impl class.


-- 
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

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Stian Soiland-Reyes]

On 14 September 2016 at 16:45, Stian Soiland-Reyes  wrote:
> This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)
> Distribution files hashes (SHA1):

Sorry, previous hashes were copy-pasted wrong :-(


Correct hashes (as can be verified by the dist area and Maven repo):

fb88789aa3d02619c20fe43bac00d3e3be7b7709
binaries/commons-beanutils-1.9.3-bin.tar.gz
7e5151ebd8eff7dfb1531772343a5d06dde1a964
binaries/commons-beanutils-1.9.3-bin.zip

50e47499401e5df18c6067f860cc0186ead38fe3
source/commons-beanutils-1.9.3-src.tar.gz
dd2ca3e505122e0efe9f4fb5eaf3069db6557e3b  source/commons-beanutils-1.9.3-src.zip


-- 
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

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Stian Soiland-Reyes]

I think it's from the default config of picking up earlier version, e.g. so
it would find 1.9.0.

Sorry, I sent the wrong hashes, will resend.

On 14 Sep 2016 11:34 p.m., "Gary Gregory"  wrote:

> Curious: what does "Semantic Versioning: 0.0.1" mean? And that what we
> really want?
>
> Gary
>
> On Sep 14, 2016 8:46 AM, "Stian Soiland-Reyes"  wrote:
>
> > This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)
> >
> >
> > SVN tag:
> >   https://svn.apache.org/repos/asf/commons/proper/beanutils/
> > tags/BEANUTILS_1_9_3_RC2/
> >
> > Site:
> >   https://stain.github.io/commons-beanutils/1.9.3-rc2/
> >
> > Javadoc:
> >   https://stain.github.io/commons-beanutils/1.9.3-rc2/apidocs/index.html
> >
> > API changes since 1.9.2 (japicmp):
> >   https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html
> >
> > RAT report:
> >   https://stain.github.io/commons-beanutils/1.9.3-rc2/rat-report.html
> >
> > Distribution files (rev 15358)
> >   https://dist.apache.org/repos/dist/dev/commons/beanutils/
> > BEANUTILS_1_9_3_RC2/
> >
> >
> > Distribution files hashes (SHA1):
> >
> > 40b7b1639eedf91b5fad5d38e6ebec01e659048f  commons-rng-1.0-src.tar.gz
> > 6296dbabde10169d6365bda99f2af6dcc191e515  commons-rng-1.0-src.zip
> > a221e862c8ff970a9ca3e7fbd86c3200d1f8780a  commons-rng-1.0-bin.tar.gz
> > 689b2bfbdb1856d4f47851d75762aab42057805a  commons-rng-1.0-bin.zip
> >
> >
> > KEYS file to check signatures:
> >   http://www.apache.org/dist/commons/KEYS
> >
> > Maven artifacts:
> >   https://repository.apache.org/content/repositories/
> > orgapachecommons-1200/
> >
> >
> > [ ] +1 Release it.
> > [ ] +0 Go ahead; I don't care.
> > [ ] -0 There are a few minor glitches: ...
> > [ ] -1 No, do not release it because ...
> >
> > This vote will be open for at least 72 hours, let's say
> > 2016-09-19T08:00:00Z
> >
> > --
> > 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
> >
> >
>

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Henning Schmiedehausen]

+1 for releasing. Compiled and tested on MacOS X running Java 8.

-h

[Seems I am still a committer. Haven't been here in a while. ]


On Wed, Sep 14, 2016 at 8:45 AM, Stian Soiland-Reyes  wrote:
> This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)
>
>
> SVN tag:
>   
> https://svn.apache.org/repos/asf/commons/proper/beanutils/tags/BEANUTILS_1_9_3_RC2/
>
> Site:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/
>
> Javadoc:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/apidocs/index.html
>
> API changes since 1.9.2 (japicmp):
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html
>
> RAT report:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/rat-report.html
>
> Distribution files (rev 15358)
>   
> https://dist.apache.org/repos/dist/dev/commons/beanutils/BEANUTILS_1_9_3_RC2/
>
>
> Distribution files hashes (SHA1):
>
> 40b7b1639eedf91b5fad5d38e6ebec01e659048f  commons-rng-1.0-src.tar.gz
> 6296dbabde10169d6365bda99f2af6dcc191e515  commons-rng-1.0-src.zip
> a221e862c8ff970a9ca3e7fbd86c3200d1f8780a  commons-rng-1.0-bin.tar.gz
> 689b2bfbdb1856d4f47851d75762aab42057805a  commons-rng-1.0-bin.zip
>
>
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>   https://repository.apache.org/content/repositories/orgapachecommons-1200/
>
>
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
>
> This vote will be open for at least 72 hours, let's say 2016-09-19T08:00:00Z
>
> --
> 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
>

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

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Gary Gregory]

Curious: what does "Semantic Versioning: 0.0.1" mean? And that what we
really want?

Gary

On Sep 14, 2016 8:46 AM, "Stian Soiland-Reyes"  wrote:

> This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)
>
>
> SVN tag:
>   https://svn.apache.org/repos/asf/commons/proper/beanutils/
> tags/BEANUTILS_1_9_3_RC2/
>
> Site:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/
>
> Javadoc:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/apidocs/index.html
>
> API changes since 1.9.2 (japicmp):
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html
>
> RAT report:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/rat-report.html
>
> Distribution files (rev 15358)
>   https://dist.apache.org/repos/dist/dev/commons/beanutils/
> BEANUTILS_1_9_3_RC2/
>
>
> Distribution files hashes (SHA1):
>
> 40b7b1639eedf91b5fad5d38e6ebec01e659048f  commons-rng-1.0-src.tar.gz
> 6296dbabde10169d6365bda99f2af6dcc191e515  commons-rng-1.0-src.zip
> a221e862c8ff970a9ca3e7fbd86c3200d1f8780a  commons-rng-1.0-bin.tar.gz
> 689b2bfbdb1856d4f47851d75762aab42057805a  commons-rng-1.0-bin.zip
>
>
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>   https://repository.apache.org/content/repositories/
> orgapachecommons-1200/
>
>
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
>
> This vote will be open for at least 72 hours, let's say
> 2016-09-19T08:00:00Z
>
> --
> 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
>
>

Re: [VOTE] Release Commons BeanUtils 1.9.3 RC2

[Raviteja Lokineni]

Why do the distribution files hashes have commons-rng?

On Wed, Sep 14, 2016 at 11:45 AM, Stian Soiland-Reyes 
wrote:

> This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)
>
>
> SVN tag:
>   https://svn.apache.org/repos/asf/commons/proper/beanutils/
> tags/BEANUTILS_1_9_3_RC2/
>
> Site:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/
>
> Javadoc:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/apidocs/index.html
>
> API changes since 1.9.2 (japicmp):
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html
>
> RAT report:
>   https://stain.github.io/commons-beanutils/1.9.3-rc2/rat-report.html
>
> Distribution files (rev 15358)
>   https://dist.apache.org/repos/dist/dev/commons/beanutils/
> BEANUTILS_1_9_3_RC2/
>
>
> Distribution files hashes (SHA1):
>
> 40b7b1639eedf91b5fad5d38e6ebec01e659048f  commons-rng-1.0-src.tar.gz
> 6296dbabde10169d6365bda99f2af6dcc191e515  commons-rng-1.0-src.zip
> a221e862c8ff970a9ca3e7fbd86c3200d1f8780a  commons-rng-1.0-bin.tar.gz
> 689b2bfbdb1856d4f47851d75762aab42057805a  commons-rng-1.0-bin.zip
>
>
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>   https://repository.apache.org/content/repositories/
> orgapachecommons-1200/
>
>
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
>
> This vote will be open for at least 72 hours, let's say
> 2016-09-19T08:00:00Z
>
> --
> 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
>
>


-- 
*Raviteja Lokineni* | Business Intelligence Developer
TD Ameritrade

E: raviteja.lokin...@gmail.com

[image: View Raviteja Lokineni's profile on LinkedIn]

[VOTE] Release Commons BeanUtils 1.9.3 RC2

[Stian Soiland-Reyes]

This is a [VOTE] for releasing Apache Commons BeanUtils 1.9.3 (from RC2)


SVN tag:
  
https://svn.apache.org/repos/asf/commons/proper/beanutils/tags/BEANUTILS_1_9_3_RC2/

Site:
  https://stain.github.io/commons-beanutils/1.9.3-rc2/

Javadoc:
  https://stain.github.io/commons-beanutils/1.9.3-rc2/apidocs/index.html

API changes since 1.9.2 (japicmp):
  https://stain.github.io/commons-beanutils/1.9.3-rc2/japicmp.html

RAT report:
  https://stain.github.io/commons-beanutils/1.9.3-rc2/rat-report.html

Distribution files (rev 15358)
  https://dist.apache.org/repos/dist/dev/commons/beanutils/BEANUTILS_1_9_3_RC2/


Distribution files hashes (SHA1):

40b7b1639eedf91b5fad5d38e6ebec01e659048f  commons-rng-1.0-src.tar.gz
6296dbabde10169d6365bda99f2af6dcc191e515  commons-rng-1.0-src.zip
a221e862c8ff970a9ca3e7fbd86c3200d1f8780a  commons-rng-1.0-bin.tar.gz
689b2bfbdb1856d4f47851d75762aab42057805a  commons-rng-1.0-bin.zip


KEYS file to check signatures:
  http://www.apache.org/dist/commons/KEYS

Maven artifacts:
  https://repository.apache.org/content/repositories/orgapachecommons-1200/


[ ] +1 Release it.
[ ] +0 Go ahead; I don't care.
[ ] -0 There are a few minor glitches: ...
[ ] -1 No, do not release it because ...

This vote will be open for at least 72 hours, let's say 2016-09-19T08:00:00Z

-- 
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

Re: [VOTE][RC1] Release Commons Rng 1.0

[Emmanuel Bourg]

Hi all,

RNG is moving fast, that's nice. I got a quick look at the API and the
site, here are my comments:

- The main page (Overview) could be enhanced with a description of the
API longer than a single sentence. It could mention the motivations for
the API, the implementations supported, a sample code snippet and a link
to the user guide.

- In the Performance section of the User Guide, I'd suggest grouping the
3 tables into a single one. It might also be interesting to put the
quality results in the same table, so we can see the trade-off between
performance and quality.

- The License section of the user guide could be removed, I guess
everyone knows that Apache projects use the Apache license.

- The internal packages should be hidden from the Javadoc, otherwise
users may be tempted to directly use the classes there. This would imply
copying the documentation of the generators into the RandomSource class.

- Why isn't the UniformRandomProvider interface simply named
RandomProvider? Is there any plan to implement non uniform random
generators in the future? Will they have a different interface?

- UniformRandomProvider mimics the java.util.Random methods which is
nice. Is there any value in also implementing the nextGaussian() method
such that our API is a perfect drop-in replacement for the JDK class?

- For code relying on the java.util.Random type, it might be useful to
provide an adapter turning an UniformRandomProvider into a
java.util.Random implementation (Hipparchus has one).

- The choice of an enum for the factory class RandomSource is a bit
unusual. It is probably ok for simple RNG with a simple seed, but with
more complex implementations I find it less intuitive to use.
For example the create(RandomSource, Object Object...) method has this
snippet in its documentation:

  RandomSource.create(RandomSource.TWO_CMRES_SELECT, 26219, 6, 9)

When a user types this in its IDE, there is no type information nor
contextual documentation for the parameters expected. The user has to
know the type of the seed and the meaning of the parameters expected,
the IDE won't be able to help here (with CTRL+P and CTRL+Q in IntelliJ).

This design induces some complexity, the loss of the seed type leads to
the seed conversion mechanism (most of the util package if I understand
well).

I'd feel more comfortable with a more classic factory design, something
like:

  RandomSource.createTwoCmres()
  RandomSource.createTwoCmres(Integer seed)
  RandomSource.createTwoCmres(Integer seed, int i, int j)

or a shorter form like:

  RNG.newTwoCmres()
  RNG.newTwoCmres(int seed)
  RNG.newTwoCmres(Integer seed, int i, int j)

That will add more methods to the factory, but it'll be much more usable
in my opinion.

- I'm not convinced by the need for the convenience static methods
RandomSource.createInt/Long. If the user doesn't want to specify the
seed, he could simply use the seed-less create method. And if the random
generator requires extra parameters, he could use a null value for the
seed as a way to mean "generate one for me please":

  RandomSource.create(RandomSource.TWO_CMRES_SELECT, null, 6, 9)

- RandomSource.saveState/restoreState allows one to convert a random
generator to/from a byte array. This looks a lot like Java
serialization. Maybe the implementations supporting this feature could
be marked as Serializable, thus it would be possible to call
RandomSource.saveState only if the instance is Serializable instead of
catching the UnsupportedOperationException thrown when the feature isn't
supported.

- Why is the byte[] state encapsulated into the RandomSource.State
class? Why not using a byte array directly?


So far I'm +1 for a beta release aimed at getting more feedback on the
API, but I'm -1 for releasing the current code as 1.0.

Emmanuel Bourg


Le 11/09/2016 à 16:55, Gilles a écrit :
> Hi.
> 
> This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
> 
> Tag name:
>   RNG_1_0_RC1 (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=f8d23082607b9f2c7be7f489eb09627722440ee5
> 
> 
> Commit ID the tag points at:
>   f8d23082607b9f2c7be7f489eb09627722440ee5
> 
> Site:
>   http://home.apache.org/~erans/commons-rng-1.0-RC1-site
> 
> Distribution files:
>   https://dist.apache.org/repos/dist/dev/commons/rng/
> 
> Distribution files hashes (SHA1):
>   a221e862c8ff970a9ca3e7fbd86c3200d1f8780a commons-rng-1.0-bin.tar.gz
>   689b2bfbdb1856d4f47851d75762aab42057805a commons-rng-1.0-bin.zip
>   40b7b1639eedf91b5fad5d38e6ebec01e659048f commons-rng-1.0-src.tar.gz
>   6296dbabde10169d6365bda99f2af6dcc191e515 commons-rng-1.0-src.zip
> 
> KEYS file to check signatures:
>   http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>  
> https://repository.apache.org/content/repositories/orgapachecommons-1199/org/apache/commons/commons-rng/1.0/
> 
> 
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a 

Re: commons-rng git commit: Update release howto.

[Benedikt Ritter]

 schrieb am Mi., 14. Sep. 2016 um 16:36 Uhr:

> Repository: commons-rng
> Updated Branches:
>   refs/heads/master 6eb9a1eb1 -> 4bf4428cf
>
>
> Update release howto.
>
>
> Project: http://git-wip-us.apache.org/repos/asf/commons-rng/repo
> Commit: http://git-wip-us.apache.org/repos/asf/commons-rng/commit/4bf4428c
> Tree: http://git-wip-us.apache.org/repos/asf/commons-rng/tree/4bf4428c
> Diff: http://git-wip-us.apache.org/repos/asf/commons-rng/diff/4bf4428c
>
> Branch: refs/heads/master
> Commit: 4bf4428cf55bb5b52128a1d963fd6572805d396f
> Parents: 6eb9a1e
> Author: Gilles 
> Authored: Wed Sep 14 16:35:53 2016 +0200
> Committer: Gilles 
> Committed: Wed Sep 14 16:35:53 2016 +0200
>
> --
>  doc/release/release.howto.txt | 22 ++
>  1 file changed, 14 insertions(+), 8 deletions(-)
> --
>
>
>
> http://git-wip-us.apache.org/repos/asf/commons-rng/blob/4bf4428c/doc/release/release.howto.txt
> --
> diff --git a/doc/release/release.howto.txt b/doc/release/release.howto.txt
> index b1e1839..3cabadf 100644
> --- a/doc/release/release.howto.txt
> +++ b/doc/release/release.howto.txt
> @@ -15,7 +15,7 @@
>  # limitations under the License.
>
>  This document is meant as a step-by-step recipe to achieve the release of
> -the Commons Rng component. Note that more general instructions valid
> +the Commons RNG component. Note that more general instructions valid
>  for all components, including [rng], are available on the Apache Commons
>  main site: at "http://commons.apache.org/releases/prepare.html; and
>  "http://commons.apache.org/releases/release.html;.
> @@ -332,8 +332,14 @@ Edit the "README.html" file to contain the released
> version number.
>   $ cp ~/.m2/repository/org/apache/commons/commons-rng/1.0/*-bin.* binaries
>   $ cp ~/.m2/repository/org/apache/commons/commons-rng/1.0/*-src.* source
>   $ cp /RELEASE-NOTES.txt .
> - $ svn add README.html RELEASE-NOTES.txt binaries/* source/*
> - $ svn commit -m "Distribution files for Commons Rng v1.0 (RC1)."
> + $ svn add \
> + CONTRIBUTING.md \
> + README.md \
>

I think you only have to make sure in the src assembly descriptor, that
these files are added to the src archives.

Benedikt


> + README.html \
> + RELEASE-NOTES.txt \
> + binaries/* \
> + source/*
> + $ svn commit -m "Distribution files for Commons RNG v1.0 (RC1)."
>
>
>  (13)
> @@ -362,10 +368,10 @@ Then run these commands:
>
>  (14)
>  Call to vote by sending a message to the "dev" ML with subject
> -"[VOTE][RC1] Release Commons Rng 1.0". You can use the following example
> as
> +"[VOTE][RC1] Release Commons RNG 1.0". You can use the following example
> as
>  a starting point, replacing the URLs with the appropriate ones:
>  --
> -This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
> +This is a [VOTE] for releasing Apache Commons RNG 1.0 (from RC1).
>
>  Tag name:
>RNG_1_0_RC1 (signature can be checked from git using 'git tag -v')
> @@ -443,7 +449,7 @@ $ svnmucc -U https://dist.apache.org/repos/dist \
>mv dev/commons/rng/source/commons-rng-1.0-src.zip.asc
> release/commons/rng/source/commons-rng-1.0-src.zip.asc \
>mv dev/commons/rng/source/commons-rng-1.0-src.zip.md5
> release/commons/rng/source/commons-rng-1.0-src.zip.md5 \
>mv dev/commons/rng/source/commons-rng-1.0-src.zip.sha1
> release/commons/rng/source/commons-rng-1.0-src.zip.sha1 \
> -  -m "Release Commons Rng v1.0"
> +  -m "Release Commons RNG v1.0"
>
>
>  (18)
> @@ -557,9 +563,9 @@ You can use the following message as a template:
>  --
>  The Apache Commons Team is pleased to announce the availability of:
>
> -Apache Commons Rng 1.0
> +Apache Commons RNG 1.0
>
> -Apache Commons Rng provides Java implementations of pseudo-random
> +Apache Commons RNG provides Java implementations of pseudo-random
>  numbers generators.
>
>  The release notes can be reviewed at:
>
>

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Gary Gregory]

"I'd rather not redo the release steps just for files that are
meaningful only when browsing the code repository mirror at
Github."

I know our release process is a pain, so maybe we should see if we can
improve it. This needs a separate thread.

It's rare to release without more than one RC.

It looks pretty lame IMO if the first thing you see, our site or github, is
wrong or missing info. It could make one wonder about overall attention to
detail...

Gary

On Sep 14, 2016 7:32 AM, "Gilles"  wrote:

> On Wed, 14 Sep 2016 14:53:29 +0100, Stian Soiland-Reyes wrote:
>
>> On 14 September 2016 at 10:14, Gilles 
>> wrote:
>>
>>> This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
>>> Commit ID the tag points at:
>>>   f8d23082607b9f2c7be7f489eb09627722440ee5
>>>
>>
>> Thanks, Gilles!
>>
>> I'm afraid my vote is: -0 as the source zip is missing README.md and
>> CONTRIBUTING.md and the site is not updated.
>>
>
> The site can, and will be fixed, "live" (as it must be done anyway for
> the link to the Javadoc, see below).
>
> Everything else looks
>> good though!
>>
>>
>> Checked:
>>
>> +1 checksums
>> +1 signatures
>> +1 source zip vs tar.gz
>> +1 binaries zip vs tar.gz
>> +1 mvn apache-rat:check (if using ignores from )
>>
>
> I don't understand the "if" clause.
> Report is clean when generated as part of "mvn site".
>
> +1 maven repo matches source (on -src.tar, -src.zip)
>> +1 mvn clean install
>> +1 LICENSE/NOTICE
>> +1 javadoc
>>
>> http://home.apache.org/~erans/commons-rng-1.0-RC1-site/apidocs/index.html
>> +1 RELEASE-NOTES  (Should it mention that this was in math before?)
>>
>
> No point IMHO.
> There isn't a single file that was not significantly changed
> and most are new.
>
> It was developed within the CM repository but the code was never
> released as part of CM.
>
> -1 git tag vs source zip
>>source zip is missing README.md and CONTRIBUTING.md (and doc, which
>> I think it's correct to exclude)
>> -1 binaries vs source
>> binaries zip is missing README.md and CONTRIBUTING.md (and doc,
>> which I think it's correct to exclude)
>>
>
> Are those a mandatory part of the distribution?
> Commons Math was never released with those files.
>
> I'd rather not redo the release steps just for files that are
> meaningful only when browsing the code repository mirror at
> Github.
>
> -1 README missing from both source and bniaries
>> -1 site stlil says "There isn't any release yet" etc on front page.
>>
>
> This was noticed by Gary.
> The site is not part of the release and can be fixed anytime (which
> I'll do before the announcement).
>
> "Javadoc 1.0" link in menu is broken.
>>
>
> That is always the case; it is also to be fixed when the files are
> in their proper place (i.e. not in the RM's "~/public_html").
>
>
> Regards,
> Gilles
>
>
> Tested with
>>
>> $ mvn -v
>> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
>> 2015-11-10T16:41:47+00:00)
>> Maven home: /home/stain/software/maven
>> Java version: 1.8.0_91, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
>> Default locale: en_GB, platform encoding: UTF-8
>> OS name: "linux", version: "4.4.0-36-generic", arch: "amd64", family:
>> "unix"
>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Gilles]

On Wed, 14 Sep 2016 14:53:29 +0100, Stian Soiland-Reyes wrote:
On 14 September 2016 at 10:14, Gilles  
wrote:

This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
Commit ID the tag points at:
  f8d23082607b9f2c7be7f489eb09627722440ee5


Thanks, Gilles!

I'm afraid my vote is: -0 as the source zip is missing README.md and
CONTRIBUTING.md and the site is not updated.


The site can, and will be fixed, "live" (as it must be done anyway for
the link to the Javadoc, see below).


Everything else looks
good though!


Checked:

+1 checksums
+1 signatures
+1 source zip vs tar.gz
+1 binaries zip vs tar.gz
+1 mvn apache-rat:check (if using ignores from )


I don't understand the "if" clause.
Report is clean when generated as part of "mvn site".


+1 maven repo matches source (on -src.tar, -src.zip)
+1 mvn clean install
+1 LICENSE/NOTICE
+1 javadoc

http://home.apache.org/~erans/commons-rng-1.0-RC1-site/apidocs/index.html
+1 RELEASE-NOTES  (Should it mention that this was in math before?)


No point IMHO.
There isn't a single file that was not significantly changed
and most are new.

It was developed within the CM repository but the code was never
released as part of CM.


-1 git tag vs source zip
   source zip is missing README.md and CONTRIBUTING.md (and doc, 
which

I think it's correct to exclude)
-1 binaries vs source
binaries zip is missing README.md and CONTRIBUTING.md (and doc,
which I think it's correct to exclude)


Are those a mandatory part of the distribution?
Commons Math was never released with those files.

I'd rather not redo the release steps just for files that are
meaningful only when browsing the code repository mirror at
Github.


-1 README missing from both source and bniaries
-1 site stlil says "There isn't any release yet" etc on front page.


This was noticed by Gary.
The site is not part of the release and can be fixed anytime (which
I'll do before the announcement).


"Javadoc 1.0" link in menu is broken.


That is always the case; it is also to be fixed when the files are
in their proper place (i.e. not in the RM's "~/public_html").


Regards,
Gilles



Tested with

$ mvn -v
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /home/stain/software/maven
Java version: 1.8.0_91, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-36-generic", arch: "amd64", family: 
"unix"



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

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Stian Soiland-Reyes]

On 14 September 2016 at 10:14, Gilles  wrote:
> This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
> Commit ID the tag points at:
>   f8d23082607b9f2c7be7f489eb09627722440ee5

Thanks, Gilles!

I'm afraid my vote is: -0 as the source zip is missing README.md and
CONTRIBUTING.md and the site is not updated. Everything else looks
good though!


Checked:

+1 checksums
+1 signatures
+1 source zip vs tar.gz
+1 binaries zip vs tar.gz
+1 mvn apache-rat:check (if using ignores from )
+1 maven repo matches source (on -src.tar, -src.zip)
+1 mvn clean install
+1 LICENSE/NOTICE
+1 javadoc 
http://home.apache.org/~erans/commons-rng-1.0-RC1-site/apidocs/index.html
+1 RELEASE-NOTES  (Should it mention that this was in math before?)

-1 git tag vs source zip
   source zip is missing README.md and CONTRIBUTING.md (and doc, which
I think it's correct to exclude)
-1 binaries vs source
binaries zip is missing README.md and CONTRIBUTING.md (and doc,
which I think it's correct to exclude)
-1 README missing from both source and bniaries
-1 site stlil says "There isn't any release yet" etc on front page.
"Javadoc 1.0" link in menu is broken.


Tested with

$ mvn -v
Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5;
2015-11-10T16:41:47+00:00)
Maven home: /home/stain/software/maven
Java version: 1.8.0_91, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en_GB, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-36-generic", arch: "amd64", family: "unix"



-- 
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

Build failed in Jenkins: commons-beanutils #9

[Apache Jenkins Server]

See 

Changes:

[stain] [maven-release-plugin] prepare for next development iteration

[stain] [maven-release-plugin] prepare release BEANUTILS_1_9_3_RC2

[stain] [maven-release-plugin] prepare for next development iteration

[stain] correct pom.xml syntax

--
[...truncated 57 lines...]
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ 
commons-beanutils ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 111 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-bundle-plugin:3.0.1:manifest (bundle-manifest) @ 
commons-beanutils ---
[INFO] 
[INFO] --- animal-sniffer-maven-plugin:1.15:check (checkAPIcompatibility) @ 
commons-beanutils ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java16:1.0
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
commons-beanutils ---
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ 
commons-beanutils ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 146 source files to 

[INFO] 
:
 Some input files use or override a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 

 uses unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-surefire-plugin:2.19.1:test (default-test) @ commons-beanutils 
---
[WARNING] The parameter forkMode is deprecated since version 2.14. Use 
forkCount and reuseForks instead.

---
 T E S T S
---
Running org.apache.commons.beanutils.LazyDynaBeanTestCase
Tests run: 16, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec - in 
org.apache.commons.beanutils.LazyDynaBeanTestCase
Running org.apache.commons.beanutils.MethodUtilsTestCase
Tests run: 32, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.096 sec - in 
org.apache.commons.beanutils.MethodUtilsTestCase
Running org.apache.commons.beanutils.DynaPropertyTestCase
Tests run: 2, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.036 sec - in 
org.apache.commons.beanutils.DynaPropertyTestCase
Running org.apache.commons.beanutils.BeanPropertyValueEqualsPredicateTestCase
Tests run: 17, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.103 sec - in 
org.apache.commons.beanutils.BeanPropertyValueEqualsPredicateTestCase
Running org.apache.commons.beanutils.bugs.Jira493TestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.087 sec - in 
org.apache.commons.beanutils.bugs.Jira493TestCase
Running org.apache.commons.beanutils.bugs.Jira92TestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.086 sec - in 
org.apache.commons.beanutils.bugs.Jira92TestCase
Running org.apache.commons.beanutils.bugs.Jira349TestCase
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.072 sec - in 
org.apache.commons.beanutils.bugs.Jira349TestCase
Running org.apache.commons.beanutils.bugs.Jira157TestCase
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, 

Build failed in Jenkins: commons-beanutils » Apache Commons BeanUtils #9

[Apache Jenkins Server]

See 


Changes:

[stain] [maven-release-plugin] prepare for next development iteration

[stain] [maven-release-plugin] prepare release BEANUTILS_1_9_3_RC2

[stain] [maven-release-plugin] prepare for next development iteration

[stain] correct pom.xml syntax

--
[...truncated 27 lines...]

main:
 [copy] Copying 2 files to 

[INFO] Executed tasks
[INFO] 
[INFO] --- maven-remote-resources-plugin:1.5:process (process-resource-bundles) 
@ commons-beanutils ---
[INFO] 
[INFO] --- buildnumber-maven-plugin:1.4:create (default) @ commons-beanutils ---
[INFO] Executing: /bin/sh -c cd 
'
 && 'svn' '--non-interactive' 'info'
[INFO] Working directory: 

[INFO] Storing buildNumber: 1760709 at timestamp: 1473860447137
[INFO] Executing: /bin/sh -c cd 
'
 && 'svn' '--non-interactive' 'info'
[INFO] Working directory: 

[INFO] Storing buildScmBranch: trunk
[INFO] 
[INFO] --- maven-resources-plugin:2.7:resources (default-resources) @ 
commons-beanutils ---
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:compile (default-compile) @ 
commons-beanutils ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 111 source files to 

[INFO] 
:
 

 uses or overrides a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 Some input files use unchecked or unsafe operations.
[INFO] 
:
 Recompile with -Xlint:unchecked for details.
[INFO] 
[INFO] --- maven-bundle-plugin:3.0.1:manifest (bundle-manifest) @ 
commons-beanutils ---
[INFO] 
[INFO] --- animal-sniffer-maven-plugin:1.15:check (checkAPIcompatibility) @ 
commons-beanutils ---
[INFO] Checking unresolved references to org.codehaus.mojo.signature:java16:1.0
[INFO] 
[INFO] --- maven-resources-plugin:2.7:testResources (default-testResources) @ 
commons-beanutils ---
[INFO] Using 'iso-8859-1' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 

[INFO] Copying 2 resources to META-INF
[INFO] 
[INFO] --- maven-compiler-plugin:3.5.1:testCompile (default-testCompile) @ 
commons-beanutils ---
[INFO] Changes detected - recompiling the module!
[INFO] Compiling 146 source files to 

[INFO] 
:
 Some input files use or override a deprecated API.
[INFO] 
:
 Recompile with -Xlint:deprecation for details.
[INFO] 
:
 

 uses unchecked or unsafe operations.
[INFO] 

[GitHub] commons-codec pull request #5: Do not leak file descriptors

[SvetlinZarev]

Github user SvetlinZarev closed the pull request at:

https://github.com/apache/commons-codec/pull/5


---
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...@commons.apache.org
For additional commands, e-mail: dev-h...@commons.apache.org

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Stian Soiland-Reyes]

I'll have a go :)

On 14 September 2016 at 13:49, Gilles  wrote:
> On Wed, 14 Sep 2016 09:42:17 +, Benedikt Ritter wrote:
>>
>> Hello Gilles,
>>
>> sorry for the delay. I won't have the time to review this RC before
>> Saturday :-(
>
>
> Could someone else please provide the missing vote earlier?
>
> Regards,
> Gilles
>
>
>>
>> Benedikt
>>
>> Gilles  schrieb am Mi., 14. Sep. 2016 um
>> 11:29 Uhr:
>>
>>>
>>>
>>>  Original Message 
>>> Subject: [VOTE][RC1] Release Commons Rng 1.0
>>> Date: Sun, 11 Sep 2016 16:55:42 +0200
>>>  From: Gilles 
>>> To: Commons Developers List 
>>> Reply-To: "Commons Developers List" 
>>>
>>> Hi.
>>>
>>> This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
>>>
>>> Tag name:
>>>RNG_1_0_RC1 (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=f8d23082607b9f2c7be7f489eb09627722440ee5
>>>
>>> Commit ID the tag points at:
>>>f8d23082607b9f2c7be7f489eb09627722440ee5
>>>
>>> Site:
>>>http://home.apache.org/~erans/commons-rng-1.0-RC1-site
>>>
>>> Distribution files:
>>>https://dist.apache.org/repos/dist/dev/commons/rng/
>>>
>>> Distribution files hashes (SHA1):
>>>a221e862c8ff970a9ca3e7fbd86c3200d1f8780a commons-rng-1.0-bin.tar.gz
>>>689b2bfbdb1856d4f47851d75762aab42057805a commons-rng-1.0-bin.zip
>>>40b7b1639eedf91b5fad5d38e6ebec01e659048f commons-rng-1.0-src.tar.gz
>>>6296dbabde10169d6365bda99f2af6dcc191e515 commons-rng-1.0-src.zip
>>>
>>> KEYS file to check signatures:
>>>http://www.apache.org/dist/commons/KEYS
>>>
>>> Maven artifacts:
>>>
>>>
>>>
>>>
>>> https://repository.apache.org/content/repositories/orgapachecommons-1199/org/apache/commons/commons-rng/1.0/
>>>
>>> [ ] +1 Release it.
>>> [ ] +0 Go ahead; I don't care.
>>> [ ] -0 There are a few minor glitches: ...
>>> [ ] -1 No, do not release it because ...
>>>
>>> This vote will close in 72 hours, at 2016-09-14T15:10:00Z (this is UTC
>>> time).
>>> --
>>>
>>> Thanks,
>>> Gilles
>>>
>>>
>>>
>>>
>>> -
>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
>>> For additional commands, e-mail: dev-h...@commons.apache.org
>>>
>>>
>
>
> -
> 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

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Gilles]

On Wed, 14 Sep 2016 09:42:17 +, Benedikt Ritter wrote:

Hello Gilles,

sorry for the delay. I won't have the time to review this RC before
Saturday :-(


Could someone else please provide the missing vote earlier?

Regards,
Gilles



Benedikt

Gilles  schrieb am Mi., 14. Sep. 2016 
um

11:29 Uhr:




 Original Message 
Subject: [VOTE][RC1] Release Commons Rng 1.0
Date: Sun, 11 Sep 2016 16:55:42 +0200
 From: Gilles 
To: Commons Developers List 
Reply-To: "Commons Developers List" 

Hi.

This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).

Tag name:
   RNG_1_0_RC1 (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=f8d23082607b9f2c7be7f489eb09627722440ee5

Commit ID the tag points at:
   f8d23082607b9f2c7be7f489eb09627722440ee5

Site:
   http://home.apache.org/~erans/commons-rng-1.0-RC1-site

Distribution files:
   https://dist.apache.org/repos/dist/dev/commons/rng/

Distribution files hashes (SHA1):
   a221e862c8ff970a9ca3e7fbd86c3200d1f8780a 
commons-rng-1.0-bin.tar.gz

   689b2bfbdb1856d4f47851d75762aab42057805a commons-rng-1.0-bin.zip
   40b7b1639eedf91b5fad5d38e6ebec01e659048f 
commons-rng-1.0-src.tar.gz

   6296dbabde10169d6365bda99f2af6dcc191e515 commons-rng-1.0-src.zip

KEYS file to check signatures:
   http://www.apache.org/dist/commons/KEYS

Maven artifacts:



https://repository.apache.org/content/repositories/orgapachecommons-1199/org/apache/commons/commons-rng/1.0/

[ ] +1 Release it.
[ ] +0 Go ahead; I don't care.
[ ] -0 There are a few minor glitches: ...
[ ] -1 No, do not release it because ...

This vote will close in 72 hours, at 2016-09-14T15:10:00Z (this is 
UTC

time).
--

Thanks,
Gilles




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





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

Re: [REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Benedikt Ritter]

Hello Gilles,

sorry for the delay. I won't have the time to review this RC before
Saturday :-(

Benedikt

Gilles  schrieb am Mi., 14. Sep. 2016 um
11:29 Uhr:

>
>
>  Original Message 
> Subject: [VOTE][RC1] Release Commons Rng 1.0
> Date: Sun, 11 Sep 2016 16:55:42 +0200
>  From: Gilles 
> To: Commons Developers List 
> Reply-To: "Commons Developers List" 
>
> Hi.
>
> This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).
>
> Tag name:
>RNG_1_0_RC1 (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=f8d23082607b9f2c7be7f489eb09627722440ee5
>
> Commit ID the tag points at:
>f8d23082607b9f2c7be7f489eb09627722440ee5
>
> Site:
>http://home.apache.org/~erans/commons-rng-1.0-RC1-site
>
> Distribution files:
>https://dist.apache.org/repos/dist/dev/commons/rng/
>
> Distribution files hashes (SHA1):
>a221e862c8ff970a9ca3e7fbd86c3200d1f8780a commons-rng-1.0-bin.tar.gz
>689b2bfbdb1856d4f47851d75762aab42057805a commons-rng-1.0-bin.zip
>40b7b1639eedf91b5fad5d38e6ebec01e659048f commons-rng-1.0-src.tar.gz
>6296dbabde10169d6365bda99f2af6dcc191e515 commons-rng-1.0-src.zip
>
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS
>
> Maven artifacts:
>
>
> https://repository.apache.org/content/repositories/orgapachecommons-1199/org/apache/commons/commons-rng/1.0/
>
> [ ] +1 Release it.
> [ ] +0 Go ahead; I don't care.
> [ ] -0 There are a few minor glitches: ...
> [ ] -1 No, do not release it because ...
>
> This vote will close in 72 hours, at 2016-09-14T15:10:00Z (this is UTC
> time).
> --
>
> Thanks,
> Gilles
>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>

Re: Another BeanUtils 1.9.3 RC?

[Stian Soiland-Reyes]

OK, I'll start :-)

On 13 Sep 2016 7:34 p.m., "Gary Gregory"  wrote:

> On Tue, Sep 13, 2016 at 7:12 AM, Raviteja Lokineni <
> raviteja.lokin...@gmail.com> wrote:
>
> > I guess then we are good for release of RC, right?
> >
>
> It looks like it. :-)
>
> Gary
>
>
> >
> > On Mon, Sep 12, 2016 at 12:18 PM, Gary Gregory 
> > wrote:
> >
> > > On Mon, Sep 12, 2016 at 9:12 AM, Stian Soiland-Reyes  >
> > > wrote:
> > >
> > > > Hi,
> > > >
> > > > Sorry about the time for fixing BEANUTILS-492 - a bit of dark magic
> to
> > > > go through there inside
> > > > the bean inspectors.
> > > >
> > > > https://issues.apache.org/jira/browse/BEANUTILS-492#
> > > >
> > > >
> > > >
> > > > Now that I think it's sorted for Java 6/7/8/9 - shall I have a go at
> > > > creating a new Release Candidate for BeanUtils 1.9.3 ?
> > > >
> > >
> > > I think that was the only item holding us up.
> > >
> > > Gary
> > >
> > >
> > > >
> > > >
> > > > --
> > > > 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
> > > >
> > > >
> > >
> > >
> > > --
> > > E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> > > Java Persistence with Hibernate, Second Edition
> > > 
> > > JUnit in Action, Second Edition 
> > > Spring Batch in Action 
> > > Blog: http://garygregory.wordpress.com
> > > Home: http://garygregory.com/
> > > Tweet! http://twitter.com/GaryGregory
> > >
> >
> >
> >
> > --
> > *Raviteja Lokineni* | Business Intelligence Developer
> > TD Ameritrade
> >
> > E: raviteja.lokin...@gmail.com
> >
> > [image: View Raviteja Lokineni's profile on LinkedIn]
> > 
> >
>
>
>
> --
> E-Mail: garydgreg...@gmail.com | ggreg...@apache.org
> Java Persistence with Hibernate, Second Edition
> 
> JUnit in Action, Second Edition 
> Spring Batch in Action 
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>

[REMINDER][VOTE][RC1] Release Commons Rng 1.0

[Gilles]

 Original Message 
Subject: [VOTE][RC1] Release Commons Rng 1.0
Date: Sun, 11 Sep 2016 16:55:42 +0200
From: Gilles 
To: Commons Developers List 
Reply-To: "Commons Developers List" 

Hi.

This is a [VOTE] for releasing Apache Commons Rng 1.0 (from RC1).

Tag name:
  RNG_1_0_RC1 (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=f8d23082607b9f2c7be7f489eb09627722440ee5


Commit ID the tag points at:
  f8d23082607b9f2c7be7f489eb09627722440ee5

Site:
  http://home.apache.org/~erans/commons-rng-1.0-RC1-site

Distribution files:
  https://dist.apache.org/repos/dist/dev/commons/rng/

Distribution files hashes (SHA1):
  a221e862c8ff970a9ca3e7fbd86c3200d1f8780a commons-rng-1.0-bin.tar.gz
  689b2bfbdb1856d4f47851d75762aab42057805a commons-rng-1.0-bin.zip
  40b7b1639eedf91b5fad5d38e6ebec01e659048f commons-rng-1.0-src.tar.gz
  6296dbabde10169d6365bda99f2af6dcc191e515 commons-rng-1.0-src.zip

KEYS file to check signatures:
  http://www.apache.org/dist/commons/KEYS

Maven artifacts:
  
https://repository.apache.org/content/repositories/orgapachecommons-1199/org/apache/commons/commons-rng/1.0/


[ ] +1 Release it.
[ ] +0 Go ahead; I don't care.
[ ] -0 There are a few minor glitches: ...
[ ] -1 No, do not release it because ...

This vote will close in 72 hours, at 2016-09-14T15:10:00Z (this is UTC
time).
--

Thanks,
Gilles



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

Re: svn commit: r1760391 - in /commons/proper/beanutils/trunk/src: main/java/org/apache/commons/beanutils/PropertyUtilsBean.java test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java

[Stian Soiland-Reyes]

Yes, perhaps this tester method should be shared across the affected test
cases. Now it's kind of copied to use the particular bean class under test,
some of which were inner classes.

On 14 Sep 2016 7:23 a.m., "Benedikt Ritter"  wrote:

> Hello,
>
>  schrieb am Mo., 12. Sep. 2016 um 17:36 Uhr:
>
> > Author: stain
> > Date: Mon Sep 12 15:36:03 2016
> > New Revision: 1760391
> >
> > URL: http://svn.apache.org/viewvc?rev=1760391=rev
> > Log:
> > BEANUTILS-492: Document getPropertyType() no longer supporting List
> >
> > Added:
> >
> > commons/proper/beanutils/trunk/src/test/java/org/
> apache/commons/beanutils/bugs/Jira492TestCase.java
> > Modified:
> >
> > commons/proper/beanutils/trunk/src/main/java/org/
> apache/commons/beanutils/PropertyUtilsBean.java
> >
> > Modified:
> > commons/proper/beanutils/trunk/src/main/java/org/
> apache/commons/beanutils/PropertyUtilsBean.java
> > URL:
> > http://svn.apache.org/viewvc/commons/proper/beanutils/
> trunk/src/main/java/org/apache/commons/beanutils/
> PropertyUtilsBean.java?rev=1760391=1760390=1760391=diff
> >
> > 
> ==
> > ---
> > commons/proper/beanutils/trunk/src/main/java/org/
> apache/commons/beanutils/PropertyUtilsBean.java
> > (original)
> > +++
> > commons/proper/beanutils/trunk/src/main/java/org/
> apache/commons/beanutils/PropertyUtilsBean.java
> > Mon Sep 12 15:36:03 2016
> > @@ -1086,6 +1086,13 @@ public class PropertyUtilsBean {
> >   * of a name reference is indexed, the type of the property itself
> > will
> >   * be returned.  If the last (or only) element has no property with
> > the
> >   * specified name, null is returned.
> > + * 
> > + * If the property is an indexed property (e.g.
> > String[]),
> > + * this method will return the type of the items within that array.
> > + * Note that from Java 8 and newer, this method do not support
> > + * such index types from items within an Collection, and will
> > + * instead return the collection type (e.g. java.util.List) from the
> > + * getter mtethod.
> >   *
> >   * @param bean Bean for which a property descriptor is requested
> >   * @param name Possibly indexed and/or nested name of the property
> for
> >
> > Added:
> > commons/proper/beanutils/trunk/src/test/java/org/
> apache/commons/beanutils/bugs/Jira492TestCase.java
> > URL:
> > http://svn.apache.org/viewvc/commons/proper/beanutils/
> trunk/src/test/java/org/apache/commons/beanutils/bugs/
> Jira492TestCase.java?rev=1760391=auto
> >
> > 
> ==
> > ---
> > commons/proper/beanutils/trunk/src/test/java/org/
> apache/commons/beanutils/bugs/Jira492TestCase.java
> > (added)
> > +++
> > commons/proper/beanutils/trunk/src/test/java/org/
> apache/commons/beanutils/bugs/Jira492TestCase.java
> > Mon Sep 12 15:36:03 2016
> > @@ -0,0 +1,153 @@
> > +/*
> > + * Licensed to the Apache Software Foundation (ASF) under one or more
> > + * contributor license agreements.  See the NOTICE file distributed with
> > + * this work for additional information regarding copyright ownership.
> > + * The ASF licenses this file to You under the Apache License, Version
> 2.0
> > + * (the "License"); you may not use this file except in compliance with
> > + * the License.  You may obtain a copy of the License at
> > + *
> > + *  http://www.apache.org/licenses/LICENSE-2.0
> > + *
> > + * Unless required by applicable law or agreed to in writing, software
> > + * distributed under the License is distributed on an "AS IS" BASIS,
> > + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> > implied.
> > + * See the License for the specific language governing permissions and
> > + * limitations under the License.
> > + */
> > +package org.apache.commons.beanutils.bugs;
> > +
> > +import static org.junit.Assert.assertEquals;
> > +import static org.junit.Assert.assertTrue;
> > +
> > +import java.beans.BeanInfo;
> > +import java.beans.IndexedPropertyDescriptor;
> > +import java.beans.IntrospectionException;
> > +import java.beans.Introspector;
> > +import java.beans.PropertyDescriptor;
> > +import java.util.ArrayList;
> > +import java.util.Arrays;
> > +import java.util.List;
> > +import java.util.Map;
> > +
> > +import org.apache.commons.beanutils.BeanUtilsBean;
> > +import org.apache.commons.beanutils.PropertyUtilsBean;
> > +import org.junit.Assert;
> > +import org.junit.Before;
> > +import org.junit.Test;
> > +
> > +/**
> > + * This test verifies that although BEANUTILS-492
> > + * means {@link IndexedPropertyDescriptor}s are not
> > + * returned for properties of type {@link List}, they
> > + * can still be accessed as positional items.
> > + *
> > + */
> > +public class Jira492TestCase {
> > +
> > +   private final BeanUtilsBean beanUtils = new BeanUtilsBean();
> > +
> > +   private final PropertyUtilsBean 

Re: svn commit: r1760391 - in /commons/proper/beanutils/trunk/src: main/java/org/apache/commons/beanutils/PropertyUtilsBean.java test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java

[Benedikt Ritter]

Hello,

 schrieb am Mo., 12. Sep. 2016 um 17:36 Uhr:

> Author: stain
> Date: Mon Sep 12 15:36:03 2016
> New Revision: 1760391
>
> URL: http://svn.apache.org/viewvc?rev=1760391=rev
> Log:
> BEANUTILS-492: Document getPropertyType() no longer supporting List
>
> Added:
>
> commons/proper/beanutils/trunk/src/test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java
> Modified:
>
> commons/proper/beanutils/trunk/src/main/java/org/apache/commons/beanutils/PropertyUtilsBean.java
>
> Modified:
> commons/proper/beanutils/trunk/src/main/java/org/apache/commons/beanutils/PropertyUtilsBean.java
> URL:
> http://svn.apache.org/viewvc/commons/proper/beanutils/trunk/src/main/java/org/apache/commons/beanutils/PropertyUtilsBean.java?rev=1760391=1760390=1760391=diff
>
> ==
> ---
> commons/proper/beanutils/trunk/src/main/java/org/apache/commons/beanutils/PropertyUtilsBean.java
> (original)
> +++
> commons/proper/beanutils/trunk/src/main/java/org/apache/commons/beanutils/PropertyUtilsBean.java
> Mon Sep 12 15:36:03 2016
> @@ -1086,6 +1086,13 @@ public class PropertyUtilsBean {
>   * of a name reference is indexed, the type of the property itself
> will
>   * be returned.  If the last (or only) element has no property with
> the
>   * specified name, null is returned.
> + * 
> + * If the property is an indexed property (e.g.
> String[]),
> + * this method will return the type of the items within that array.
> + * Note that from Java 8 and newer, this method do not support
> + * such index types from items within an Collection, and will
> + * instead return the collection type (e.g. java.util.List) from the
> + * getter mtethod.
>   *
>   * @param bean Bean for which a property descriptor is requested
>   * @param name Possibly indexed and/or nested name of the property for
>
> Added:
> commons/proper/beanutils/trunk/src/test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java
> URL:
> http://svn.apache.org/viewvc/commons/proper/beanutils/trunk/src/test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java?rev=1760391=auto
>
> ==
> ---
> commons/proper/beanutils/trunk/src/test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java
> (added)
> +++
> commons/proper/beanutils/trunk/src/test/java/org/apache/commons/beanutils/bugs/Jira492TestCase.java
> Mon Sep 12 15:36:03 2016
> @@ -0,0 +1,153 @@
> +/*
> + * Licensed to the Apache Software Foundation (ASF) under one or more
> + * contributor license agreements.  See the NOTICE file distributed with
> + * this work for additional information regarding copyright ownership.
> + * The ASF licenses this file to You under the Apache License, Version 2.0
> + * (the "License"); you may not use this file except in compliance with
> + * the License.  You may obtain a copy of the License at
> + *
> + *  http://www.apache.org/licenses/LICENSE-2.0
> + *
> + * Unless required by applicable law or agreed to in writing, software
> + * distributed under the License is distributed on an "AS IS" BASIS,
> + * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
> implied.
> + * See the License for the specific language governing permissions and
> + * limitations under the License.
> + */
> +package org.apache.commons.beanutils.bugs;
> +
> +import static org.junit.Assert.assertEquals;
> +import static org.junit.Assert.assertTrue;
> +
> +import java.beans.BeanInfo;
> +import java.beans.IndexedPropertyDescriptor;
> +import java.beans.IntrospectionException;
> +import java.beans.Introspector;
> +import java.beans.PropertyDescriptor;
> +import java.util.ArrayList;
> +import java.util.Arrays;
> +import java.util.List;
> +import java.util.Map;
> +
> +import org.apache.commons.beanutils.BeanUtilsBean;
> +import org.apache.commons.beanutils.PropertyUtilsBean;
> +import org.junit.Assert;
> +import org.junit.Before;
> +import org.junit.Test;
> +
> +/**
> + * This test verifies that although BEANUTILS-492
> + * means {@link IndexedPropertyDescriptor}s are not
> + * returned for properties of type {@link List}, they
> + * can still be accessed as positional items.
> + *
> + */
> +public class Jira492TestCase {
> +
> +   private final BeanUtilsBean beanUtils = new BeanUtilsBean();
> +
> +   private final PropertyUtilsBean propertyUtils = new
> PropertyUtilsBean();
> +
> +   public static class IndexedBean {
> +   private List someList = new ArrayList();
> +   public List getSomeList() {
> +   return someList;
> +   }
> +   public void setSomeList(List someList) {
> +   this.someList = someList;
> +   }
> +   public void setSomeList(int i, String value) {
> +   someList.set(i, value);
> +   }
> +