Re: [VOTE] DBCP 2.2 rc2

[Gary Gregory]

On Mar 8, 2017 5:37 AM, "Matt Sicker"  wrote:

It's been a few months now, oh wow!

I'll be working on making a commons-pool release later this week. After
that, I'll update commons-dbcp to use the new release and create rc3 for
this. I don't have access to the project where I was able to reproduce the
OSGi issues anymore (old employer), so it'll be up to the voters to find
any issues with it at that point. ;)


Ok, cool.

Gary


On 31 October 2016 at 10:26, Stian Soiland-Reyes  wrote:

> Here's an approach we used in Jena with partial success:
>
> https://github.com/apache/jena/tree/master/apache-jena-osgi/jena-osgi-test
>
> Uses PaxExam - https://ops4j1.jira.com/wiki/display/paxexam/Pax+Exam
>
>
> On 31 October 2016 at 15:22, Matt Sicker  wrote:
> > Oh, yes, rc2 is cancelled. I forgot to clean up.
> >
> > And yes, help is appreciated. I haven't had a chance to look back at
> this,
> > but one of the things we wanted to accomplish with this bug fix was to
> also
> > introduce a pattern for black box testing Commons libraries in OSGi.
> >
> > On 31 October 2016 at 10:15, Stian Soiland-Reyes 
> wrote:
> >
> >> Hi, Matt,
> >>
> >> Was this DBCP Release Candidate vote cancelled..? I noticed it is still
> in
> >>
> >> https://repository.apache.org/content/repositories/
> orgapachecommons-1196/
> >> https://dist.apache.org/repos/dist/dev/commons/dbcp/DBCP_2_2_RC2/
> >>
> >>
> >> BTW - do you need some help with
> >> https://issues.apache.org/jira/browse/DBCP-454 ?
> >>
> >> In Taverna we had as simular issue which we worked around by declaring
> >> javax.activation as part of org.osgi.framework.system.packages.extra
> >> .. not sure if that helps:
> >>
> >> https://github.com/apache/incubator-taverna-commandline/commit/
> >> d63f91eea3c15a2df56c5eb3000f7c4f8c6152d5
> >>
> >> On 9 August 2016 at 17:01, Gary Gregory  wrote:
> >> > On Tue, Aug 9, 2016 at 8:27 AM, Matt Sicker  wrote:
> >> >
> >> >> Yes, I'd like to make a decent integration test for this. This could
> >> have
> >> >> helped the original bugfix that caused this new bug, too. :)
> >> >>
> >> >
> >> > Yes, that's worth doing. Too bad it will delay DBCP, but there is a
> nice
> >> > upshot with a new reusable integration test.
> >> >
> >> > Gary
> >> >
> >> >>
> >> >> On 9 August 2016 at 10:23, Gary Gregory 
> wrote:
> >> >>
> >> >> > This is more than likely something all Commons components could
> >> benefit
> >> >> > from... I would be really nice to capture your testing in an
> >> integration
> >> >> > test we can run from Maven.
> >> >> >
> >> >> > We could put anything generic in a Commons OSGi component even if
> it
> >> only
> >> >> > has test code.
> >> >> >
> >> >> > Gary
> >> >> >
> >> >> > On Mon, Aug 8, 2016 at 10:17 AM, Matt Sicker 
> >> wrote:
> >> >> >
> >> >> > > Damn, I'm still having OSGi issues with this RC. I've reopened
> >> >> > > https://issues.apache.org/jira/browse/DBCP-454 to investigate. I
> >> may
> >> >> > need
> >> >> > > to cut an rc3, though.
> >> >> > >
> >> >> > > On 7 August 2016 at 14:03, Matt Sicker  wrote:
> >> >> > >
> >> >> > > > We have fixed quite a few bugs and added some significant
> >> >> enhancements
> >> >> > > > since DBCP 2.1.1 was released, so I would like to release DBCP
> >> 2.2.
> >> >> > > >
> >> >> > > > Changes since 2.2 rc1:
> >> >> > > > * Added a bug fix from jira that wasn't included in the
release
> >> notes
> >> >> > as
> >> >> > > > it had the wrong fix version attached.
> >> >> > > > * Fixed DBCP-454.
> >> >> > > > * Fixed scm link to point to the future DBCP_2_2 tag instead
of
> >> the
> >> >> > > > release candidate tag.
> >> >> > > > * Added link to 2.2 javadocs on sidebar.
> >> >> > > > * Various fumblings with subversion.
> >> >> > > >
> >> >> > > > DBCP 2.2 RC2 is available for review here:
> >> >> > > > https://dist.apache.org/repos/
> dist/dev/commons/dbcp/DBCP_2_
> >> 2_RC2
> >> >> > > (svn
> >> >> > > > revision 14694)
> >> >> > > >
> >> >> > > > The tag is here:
> >> >> > > > https://svn.apache.org/repos/asf/commons/proper/dbcp/tags/
> >> >> > > > DBCP_2_2_RC2/ (svn revision 1755453)
> >> >> > > > N.B. the SVN revision is required because SVN tags are not
> >> >> > immutable.
> >> >> > > >
> >> >> > > > Maven artifacts are here:
> >> >> > > > https://repository.apache.org/content/repositories/
> >> >> > > > orgapachecommons-1196/
> >> >> > > >
> >> >> > > > These are the Maven artifacts and their sha256 hashes
> >> >> > > >
> >> >> > > > 64a093b7fa2ca077b8f1cce5847308c0c89fed20fc33e499f559e00b7ba5
> 26aa
> >> >> > > > commons-dbcp2-2.2.jar
> >> >> > > > 22c3b706e8590f92688dc91399427daa3bbd35e3da0b31375d45877d2ca1
> 93f2
> >> >> > > > commons-dbcp2-2.2-javadoc.jar
> >> >> > > > 5dfe8ead3d3626d76e37f19fe26555c1caeedc071e74cacab0693bdf41c3
> 3e08
> >> >> > > > commons-dbcp2-2.2-sources.jar
> 

Re: [ALL][Math] git pull requests: how?

[Matt Sicker]

Found this link while trying to remember how to do this:

https://help.github.com/articles/checking-out-pull-requests-locally/

Same docs as above, just from the source. It sounds like you can't write to
a PR branch even if the author allows it, but the docs could be out of date
(it happens!).

On 2 March 2017 at 09:52, Gilles  wrote:

> On Thu, 2 Mar 2017 09:35:53 -0600, Matt Sicker wrote:
>
>> Is the different behavior caused by svn versus git mirroring?
>>
>
> The "Math" and "Numbers" projects both use git.
>
> Gilles
>
> That read-only branch feature is really cool.
>> Some of this info might be
>> useful to include in the template readme files and such for commons.
>>
>
> Since the template is the same for all git projects
>
>
>
>> On 2 March 2017 at 06:09, Gilles  wrote:
>>
>> On Thu, 2 Mar 2017 11:30:17 +, sebb wrote:
>>>
>>> This info (when validated) should be added to the Wiki:

 https://wiki.apache.org/commons/UsingGIT

 ...

 Oh, it already is there at the end


>>> Indeed, there is information there.
>>> That works:
>>>   $ git fetch github pull/72/head:fix-foo-in-bar
>>>
>>> But is it simpler to
>>>  1. remember the syntax
>>>  2. go to the GitHub site (following the link "manually" posted by
>>> the contributor on the JIRA page)
>>>  3. figure out what part of the GitHub page contains the string
>>> for replacing "fix-foo-in-bar"
>>>  4. copy/paste it in a console
>>>  5. run the above command
>>>  6. merge the branch created by the above command
>>> than have the full command posted automatically on the JIRA page,
>>> so that the committer can do everything in one go?
>>>
>>> Note that the command above is not the same as the syntax provided
>>> in the automatic posts ("fetch" vs "pull").
>>>
>>> Question is still: Why different behaviours of the GitHub mirrors?
>>> Do we want this fixed?
>>> How?
>>>
>>>
>>> Thanks,
>>> Gilles
>>>
>>>
>>>
>>> On 2 March 2017 at 10:50, Gilles  wrote:
>>>

 On Wed, 1 Mar 2017 22:51:54 -0600, Matt Sicker wrote:
>
>
>> Normally the GitHub email gives you the proper command to use to pull
>> the
>> PR into your local git which you can merge and push (which merges the
>> PR
>> once GitHub gets updated from apache.org).
>>
>> As for making sure that email gets sent, if it's not, file an INFRA
>> ticket
>> about it. I've never tried it, but this might work:
>>
>> git pull https://github.com/apache/commons-math/pull/55
>>
>>
>
> $ git pull https://github.com/apache/commons-math/pull/55
> remote: Not Found
> fatal: repository 'https://github.com/apache/commons-math/pull/55/'
> not
> found
>
> If you add .diff or .patch to the end of the URL, it gives you a diff
>
>> that
>> you can manually apply. The .diff URL appears to be a normal diff
>> while
>> the
>> .patch URL is the output of "git format-patch". So, if you download <
>> https://github.com/apache/commons-math/pull/55.patch> and run "git
>> apply
>> 55.patch", that'll commit it properly as if you merged the PR itself I
>> think (it'll set the commit author properly at least for proper
>> historical
>> attribution).
>>
>>
>
> Thanks, that could be a (sub-optimal) solution.
>
> Also, adding a commit message somewhere (e.g., a follow up empty commit
>
>> or
>> a changelog entry commit) containing the phrase "this closes #55" (or
>> maybe
>> just "closes #55"; it's pretty loose) is enough to close the PR, but
>> merging it should close it automatically.
>>
>>
>
> Yes, I knew that, because the notification, when it gets sent, contains
> all the information necessary to handle to request (and additionally,
> the
> JIRA issue will be updated automatically too).
>
> Hence that would be the preferred solution.
>
> I still wonder why the various Commons projects (those managed by git
> and
> having a GitHub mirror) behave differently.
>
>
> Regards,
> Gilles
>
>
> On 1 March 2017 at 17:53, Gilles  wrote:
>
>>
>> Hi.
>>
>>>
>>> How should the project be configured such that the request
>>> posted here:
>>>   https://issues.apache.org/jira/browse/MATH-1405
>>> is as easy to handle as the one posted here:
>>>   https://issues.apache.org/jira/browse/NUMBERS-4
>>> ?
>>>
>>> Thanks,
>>> Gilles
>>>
>>>
>>
>>>
>
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
> For additional commands, e-mail: dev-h...@commons.apache.org
>
>


-- 
Matt Sicker 

Re: [VOTE] DBCP 2.2 rc2

[Matt Sicker]

It's been a few months now, oh wow!

I'll be working on making a commons-pool release later this week. After
that, I'll update commons-dbcp to use the new release and create rc3 for
this. I don't have access to the project where I was able to reproduce the
OSGi issues anymore (old employer), so it'll be up to the voters to find
any issues with it at that point. ;)

On 31 October 2016 at 10:26, Stian Soiland-Reyes  wrote:

> Here's an approach we used in Jena with partial success:
>
> https://github.com/apache/jena/tree/master/apache-jena-osgi/jena-osgi-test
>
> Uses PaxExam - https://ops4j1.jira.com/wiki/display/paxexam/Pax+Exam
>
>
> On 31 October 2016 at 15:22, Matt Sicker  wrote:
> > Oh, yes, rc2 is cancelled. I forgot to clean up.
> >
> > And yes, help is appreciated. I haven't had a chance to look back at
> this,
> > but one of the things we wanted to accomplish with this bug fix was to
> also
> > introduce a pattern for black box testing Commons libraries in OSGi.
> >
> > On 31 October 2016 at 10:15, Stian Soiland-Reyes 
> wrote:
> >
> >> Hi, Matt,
> >>
> >> Was this DBCP Release Candidate vote cancelled..? I noticed it is still
> in
> >>
> >> https://repository.apache.org/content/repositories/
> orgapachecommons-1196/
> >> https://dist.apache.org/repos/dist/dev/commons/dbcp/DBCP_2_2_RC2/
> >>
> >>
> >> BTW - do you need some help with
> >> https://issues.apache.org/jira/browse/DBCP-454 ?
> >>
> >> In Taverna we had as simular issue which we worked around by declaring
> >> javax.activation as part of org.osgi.framework.system.packages.extra
> >> .. not sure if that helps:
> >>
> >> https://github.com/apache/incubator-taverna-commandline/commit/
> >> d63f91eea3c15a2df56c5eb3000f7c4f8c6152d5
> >>
> >> On 9 August 2016 at 17:01, Gary Gregory  wrote:
> >> > On Tue, Aug 9, 2016 at 8:27 AM, Matt Sicker  wrote:
> >> >
> >> >> Yes, I'd like to make a decent integration test for this. This could
> >> have
> >> >> helped the original bugfix that caused this new bug, too. :)
> >> >>
> >> >
> >> > Yes, that's worth doing. Too bad it will delay DBCP, but there is a
> nice
> >> > upshot with a new reusable integration test.
> >> >
> >> > Gary
> >> >
> >> >>
> >> >> On 9 August 2016 at 10:23, Gary Gregory 
> wrote:
> >> >>
> >> >> > This is more than likely something all Commons components could
> >> benefit
> >> >> > from... I would be really nice to capture your testing in an
> >> integration
> >> >> > test we can run from Maven.
> >> >> >
> >> >> > We could put anything generic in a Commons OSGi component even if
> it
> >> only
> >> >> > has test code.
> >> >> >
> >> >> > Gary
> >> >> >
> >> >> > On Mon, Aug 8, 2016 at 10:17 AM, Matt Sicker 
> >> wrote:
> >> >> >
> >> >> > > Damn, I'm still having OSGi issues with this RC. I've reopened
> >> >> > > https://issues.apache.org/jira/browse/DBCP-454 to investigate. I
> >> may
> >> >> > need
> >> >> > > to cut an rc3, though.
> >> >> > >
> >> >> > > On 7 August 2016 at 14:03, Matt Sicker  wrote:
> >> >> > >
> >> >> > > > We have fixed quite a few bugs and added some significant
> >> >> enhancements
> >> >> > > > since DBCP 2.1.1 was released, so I would like to release DBCP
> >> 2.2.
> >> >> > > >
> >> >> > > > Changes since 2.2 rc1:
> >> >> > > > * Added a bug fix from jira that wasn't included in the release
> >> notes
> >> >> > as
> >> >> > > > it had the wrong fix version attached.
> >> >> > > > * Fixed DBCP-454.
> >> >> > > > * Fixed scm link to point to the future DBCP_2_2 tag instead of
> >> the
> >> >> > > > release candidate tag.
> >> >> > > > * Added link to 2.2 javadocs on sidebar.
> >> >> > > > * Various fumblings with subversion.
> >> >> > > >
> >> >> > > > DBCP 2.2 RC2 is available for review here:
> >> >> > > > https://dist.apache.org/repos/
> dist/dev/commons/dbcp/DBCP_2_
> >> 2_RC2
> >> >> > > (svn
> >> >> > > > revision 14694)
> >> >> > > >
> >> >> > > > The tag is here:
> >> >> > > > https://svn.apache.org/repos/asf/commons/proper/dbcp/tags/
> >> >> > > > DBCP_2_2_RC2/ (svn revision 1755453)
> >> >> > > > N.B. the SVN revision is required because SVN tags are not
> >> >> > immutable.
> >> >> > > >
> >> >> > > > Maven artifacts are here:
> >> >> > > > https://repository.apache.org/content/repositories/
> >> >> > > > orgapachecommons-1196/
> >> >> > > >
> >> >> > > > These are the Maven artifacts and their sha256 hashes
> >> >> > > >
> >> >> > > > 64a093b7fa2ca077b8f1cce5847308c0c89fed20fc33e499f559e00b7ba5
> 26aa
> >> >> > > > commons-dbcp2-2.2.jar
> >> >> > > > 22c3b706e8590f92688dc91399427daa3bbd35e3da0b31375d45877d2ca1
> 93f2
> >> >> > > > commons-dbcp2-2.2-javadoc.jar
> >> >> > > > 5dfe8ead3d3626d76e37f19fe26555c1caeedc071e74cacab0693bdf41c3
> 3e08
> >> >> > > > commons-dbcp2-2.2-sources.jar
> >> >> > > > 32c35b92a48f179ad9de8ee3d3a8acad4baf002a4878f03174adb0d486e8
> b98c
> >> 

Build failed in Jenkins: Commons-configuration #48

[Apache Jenkins Server]

See 


Changes:

[oheger] [CONFIGURATION-653] Added @since tags.

--
[...truncated 36.19 KB...]
AU
src/main/java/org/apache/commons/configuration2/builder/combined/MultiFileBuilderParametersImpl.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/ConfigurationDeclaration.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/ReloadingMultiFileConfigurationBuilder.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/MultiFileBuilderProperties.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/CombinedConfigurationBuilder.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/package-info.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/BaseConfigurationBuilderProvider.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/FileExtensionConfigurationBuilderProvider.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/MultiWrapDynaBean.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/MultiWrapDynaClass.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/ConfigurationBuilderProvider.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/MultiFileConfigurationBuilder.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/CombinedConfigurationBuilderProvider.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/CombinedBuilderParametersImpl.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/CombinedBuilderProperties.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/MultiFileConfigurationBuilderProvider.java
AU
src/main/java/org/apache/commons/configuration2/builder/combined/ReloadingCombinedConfigurationBuilder.java
AU
src/main/java/org/apache/commons/configuration2/builder/EventListenerProvider.java
AU
src/main/java/org/apache/commons/configuration2/builder/HierarchicalBuilderProperties.java
AU
src/main/java/org/apache/commons/configuration2/builder/CopyObjectDefaultHandler.java
AU
src/main/java/org/apache/commons/configuration2/builder/ConfigurationBuilderResultCreatedEvent.java
AU
src/main/java/org/apache/commons/configuration2/builder/XMLBuilderParametersImpl.java
AU
src/main/java/org/apache/commons/configuration2/builder/ConfigurationBuilder.java
AU
src/main/java/org/apache/commons/configuration2/builder/ConfigurationBuilderEvent.java
AU
src/main/java/org/apache/commons/configuration2/builder/BasicConfigurationBuilder.java
AU
src/main/java/org/apache/commons/configuration2/builder/DatabaseBuilderParametersImpl.java
AU
src/main/java/org/apache/commons/configuration2/builder/XMLBuilderProperties.java
AUsrc/main/java/org/apache/commons/configuration2/INIConfiguration.java
AU
src/main/java/org/apache/commons/configuration2/CombinedConfiguration.java
AU
src/main/java/org/apache/commons/configuration2/HierarchicalConfigurationXMLReader.java
AU
src/main/java/org/apache/commons/configuration2/ConfigurationXMLReader.java
A src/main/java/org/apache/commons/configuration2/interpol
AU
src/main/java/org/apache/commons/configuration2/interpol/DummyLookup.java
AU
src/main/java/org/apache/commons/configuration2/interpol/ExprLookup.java
AUsrc/main/java/org/apache/commons/configuration2/interpol/Lookup.java
AU
src/main/java/org/apache/commons/configuration2/interpol/ConfigurationInterpolator.java
AU
src/main/java/org/apache/commons/configuration2/interpol/SystemPropertiesLookup.java
AU
src/main/java/org/apache/commons/configuration2/interpol/EnvironmentLookup.java
AU
src/main/java/org/apache/commons/configuration2/interpol/DefaultLookups.java
AU
src/main/java/org/apache/commons/configuration2/interpol/ConstantLookup.java
AU
src/main/java/org/apache/commons/configuration2/interpol/InterpolatorSpecification.java
AU
src/main/java/org/apache/commons/configuration2/interpol/package-info.java
AU
src/main/java/org/apache/commons/configuration2/SystemConfiguration.java
AU
src/main/java/org/apache/commons/configuration2/PrefixedKeysIterator.java
AUsrc/main/java/org/apache/commons/configuration2/JNDIConfiguration.java
A src/main/java/org/apache/commons/configuration2/resolver
AU
src/main/java/org/apache/commons/configuration2/resolver/EntityResolverSupport.java
AU
src/main/java/org/apache/commons/configuration2/resolver/CatalogResolver.java
AU
src/main/java/org/apache/commons/configuration2/resolver/DefaultEntityResolver.java

[lang][crypto] LANG-1145 evaluate JVM architecture

[Bruno P. Kinoshita]

Hi all,

We have a pull request [1][2] for adding code that detects the JVM 
architecture. The user has a valid use case for his code, and we have similar 
code in Apache Spark [3] and Apache Commons Crypto [4].

As this is going into [lang], another Commons component, I thought maybe there 
could be some synergy between Crypto and Lang? I believe crypto has no 
dependencies right now, but maybe it would be worth adding a dep + shade, so 
that we have a single place to maintain this list of OS architectures.

Thoughts?

Bruno


[1] https://github.com/apache/commons-lang/pull/231
[2] https://issues.apache.org/jira/browse/LANG-1145

[3] 
https://github.com/apache/spark/blob/master/core/src/main/scala/org/apache/spark/util/SizeEstimator.scala

[4] 
https://github.com/apache/commons-crypto/blob/master/src/main/java/org/apache/commons/crypto/OsInfo.java

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

Build failed in Jenkins: Commons-configuration #47

[Apache Jenkins Server]

See 

--
Started by an SCM change
[EnvInject] - Loading node environment variables.
Building remotely on ubuntu-us1 (ubuntu) in workspace 

Updating http://svn.apache.org/repos/asf/commons/proper/configuration/trunk at 
revision '2017-03-07T21:03:58.380 +'
A 
src/main/java/org/apache/commons/configuration2/builder/INIBuilderProperties.java
A 
src/main/java/org/apache/commons/configuration2/builder/fluent/INIBuilderParameters.java
U 
src/main/java/org/apache/commons/configuration2/builder/fluent/Parameters.java
A 
src/main/java/org/apache/commons/configuration2/builder/INIBuilderParametersImpl.java
U src/main/java/org/apache/commons/configuration2/INIConfiguration.java
U 
src/main/java/org/apache/commons/configuration2/ConfigurationUtils.java
U 
src/main/java/org/apache/commons/configuration2/ConfigurationConverter.java
U 
src/main/java/org/apache/commons/configuration2/plist/PropertyListConfiguration.java
U 
src/main/java/org/apache/commons/configuration2/plist/XMLPropertyListConfiguration.java
U src/changes/changes.xml
U 
src/test/java/org/apache/commons/configuration2/TestINIConfiguration.java
U 
src/test/java/org/apache/commons/configuration2/ConfigurationAssert.java
At revision 1785887

Parsing POMs
Established TCP socket on 55944
maven33-agent.jar already up to date
maven33-interceptor.jar already up to date
maven3-interceptor-commons.jar already up to date
[Commons-configuration] $ /home/jenkins/tools/java/latest1.6/bin/java -Xmx2g 
-Xms256m -cp 
/home/jenkins/jenkins-slave/maven33-agent.jar:/home/jenkins/tools/maven/latest3/boot/plexus-classworlds-2.5.2.jar:/home/jenkins/tools/maven/latest3/conf/logging
 jenkins.maven3.agent.Maven33Main /home/jenkins/tools/maven/latest3/ 
/home/jenkins/jenkins-slave/slave.jar 
/home/jenkins/jenkins-slave/maven33-interceptor.jar 
/home/jenkins/jenkins-slave/maven3-interceptor-commons.jar 55944
Native maven support requires Java 1.7 or later, but this Maven is using 
/usr/local/asfpackages/java/jdk1.6.0_45-64/jre
Please use the freestyle project.
ERROR: Failed to launch Maven. Exit code = 1


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

Re: [VOTE] Release Commons Text 1.0 based on RC1

[Oliver Heger]

Hi,

build works fine with Java 1.7 and 1.8 on Windows 10, also the site
build with Java 1.8. Artifacts and site look good.

I did not find any other problems than already reported (wrong version
in release notes and one missing license header in RAT report). One
minor point: Shouldn't the 1.0 release appear under Release History?

The wrong version in the release notes is indeed annoying, but I do not
think that this is sufficient to block the release.

So +1

Oliver

Am 06.03.2017 um 14:25 schrieb Rob Tompkins:
> Hello all,
> 
> This is a [VOTE] for releasing Apache Commons Text 1.0 (from RC1).
> 
> Tag name:
>commons-text-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-text.git;a=commit;h=
> e38039a3da2244741f5d33ab1b05bdee51c53c3e
> 
> Commit ID the tag points at:
>e38039a3da2244741f5d33ab1b05bdee51c53c3e
> 
> Site:
>http://home.apache.org/~chtompki/commons-text-1.0-RC1
> 
> Distribution files (committed at revision 18567):
>https://dist.apache.org/repos/dist/dev/commons/text/
> 
> Distribution files hashes (SHA1):
>commons-text-1.0-bin.tar.gz
>(SHA: a6eb41fd426d876669cc6799afd7435d97285229)
>commons-text-1.0-bin.zip
>(SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
>commons-text-1.0-src.tar.gz
>(SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
>commons-text-1.0-src.zip
>(SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)
> 
> These are the Maven artifacts and their hashes:
>commons-text-1.0-javadoc.jar
>(SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
>commons-text-1.0-sources.jar
>(SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
>commons-text-1.0-test-sources.jar
>(SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
>commons-text-1.0-tests.jar
>(SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
>commons-text-1.0.jar
>(SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
>commons-text-1.0.pom
>(SHA1: 7220d033f589194704533680c76c6a74cabe6d57)
> 
> KEYS file to check signatures:
>http://www.apache.org/dist/commons/KEYS
> 
> Maven artifacts:
>https://repository.apache.org/content/repositories/orgapachecommons-1239
> 
> Please select one of the following options[1]:
>   [ ] +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 at least 72 hours, i.e. until
> 2017-03-09T14: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 commands, e-mail: dev-h...@commons.apache.org

Re: Google Summer of Code 2017 Mentor Registration

[Matt Sicker]

Depending on the library, I could be available to mentor. As long as it
doesn't require a lot of domain knowledge that I don't have of course. :)

On 7 March 2017 at 08:52, Stian Soiland-Reyes  wrote:

> 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 any of the Commons
> components that should be sufficient.
>
> GSOC is a good way to engage with fresh developers, and the ideas can be
> both new/experimental features or incremental improvements and refactoring;
> although I will admit the first type of ideas often gets more interest.
>
> Apache Commons can be a good target for GSOC students as most of our
> components are independent and easy to get started with.
>
> -- Forwarded message --
> From: "Ulrich Stärk" 
> Date: 6 Mar 2017 7:39 pm
> Subject: Google Summer of Code 2017 Mentor Registration
> To: 
> Cc: "d...@community.apache.org" 
>
> Dear PMCs,
>
> I'm happy to announce that the ASF has made it onto the list of accepted
> organizations for
> Google Summer of Code 2017! [1,2]
>
> It is now time for mentors to sign up, so please pass this email on to your
> community and
> podlings. If you aren’t already subscribed to ment...@community.apache.org
> you should do so now else
> you might miss important information.
>
> Mentor signup requires two steps: mentor signup in Google's system [3] and
> PMC acknowledgement.
>
> If you want to mentor a project in this year's SoC you will have to
>
> 1. Be an Apache committer.
> 2. Request an acknowledgement from the PMC for which you want to mentor
> projects. Use the below
> template and *do not forget to copy ment...@community.apache.org*. We will
> use the email adress you
> indicate to send the invite to be a mentor for Apache.
>
> PMCs, read carefully please.
>
> We request that each mentor is acknowledged by a PMC member. This is to
> ensure the mentor is in good
> standing with the community. When you receive a request for
> acknowledgement, please ACK it and cc
> ment...@community.apache.org
>
> Lastly, it is not yet too late to record your ideas in Jira (see my
> previous emails for details).
> Students will now begin to explore ideas so if you haven’t already done so,
> record your ideas
> immediately!
>
> Cheers,
>
> Uli
>
> mentor request email template:
> 
> to: private@.apache.org
> cc: ment...@community.apache.org
> subject: GSoC 2017 mentor request for 
>
>  PMC,
>
> please acknowledge my request to become a mentor for Google Summer of Code
> 2017 projects for Apache
> .
>
> I would like to receive the mentor invite to 
>
> 
>
> 
>
> [1] https://summerofcode.withgoogle.com/organizations/
> [2] https://summerofcode.withgoogle.com/organizations/5416945173135360/
> [3] https://summerofcode.withgoogle.com/
>
> -
> To unsubscribe, e-mail: dev-unsubscr...@community.apache.org
> For additional commands, e-mail: dev-h...@community.apache.org
>



-- 
Matt Sicker 

Fwd: Google Summer of Code 2017 Mentor Registration

[Stian Soiland-Reyes]

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 any of the Commons
components that should be sufficient.

GSOC is a good way to engage with fresh developers, and the ideas can be
both new/experimental features or incremental improvements and refactoring;
although I will admit the first type of ideas often gets more interest.

Apache Commons can be a good target for GSOC students as most of our
components are independent and easy to get started with.

-- Forwarded message --
From: "Ulrich Stärk" 
Date: 6 Mar 2017 7:39 pm
Subject: Google Summer of Code 2017 Mentor Registration
To: 
Cc: "d...@community.apache.org" 

Dear PMCs,

I'm happy to announce that the ASF has made it onto the list of accepted
organizations for
Google Summer of Code 2017! [1,2]

It is now time for mentors to sign up, so please pass this email on to your
community and
podlings. If you aren’t already subscribed to ment...@community.apache.org
you should do so now else
you might miss important information.

Mentor signup requires two steps: mentor signup in Google's system [3] and
PMC acknowledgement.

If you want to mentor a project in this year's SoC you will have to

1. Be an Apache committer.
2. Request an acknowledgement from the PMC for which you want to mentor
projects. Use the below
template and *do not forget to copy ment...@community.apache.org*. We will
use the email adress you
indicate to send the invite to be a mentor for Apache.

PMCs, read carefully please.

We request that each mentor is acknowledged by a PMC member. This is to
ensure the mentor is in good
standing with the community. When you receive a request for
acknowledgement, please ACK it and cc
ment...@community.apache.org

Lastly, it is not yet too late to record your ideas in Jira (see my
previous emails for details).
Students will now begin to explore ideas so if you haven’t already done so,
record your ideas
immediately!

Cheers,

Uli

mentor request email template:

to: private@.apache.org
cc: ment...@community.apache.org
subject: GSoC 2017 mentor request for 

 PMC,

please acknowledge my request to become a mentor for Google Summer of Code
2017 projects for Apache
.

I would like to receive the mentor invite to 





[1] https://summerofcode.withgoogle.com/organizations/
[2] https://summerofcode.withgoogle.com/organizations/5416945173135360/
[3] https://summerofcode.withgoogle.com/

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

Re: [VOTE] Release Commons Text 1.0 based on RC1

[Bruno P. Kinoshita]

[ X ] +1 Release it.

Builds OK on 

Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
2015-11-11T05:41:47+13:00)
Maven home: /opt/maven
Java version: 1.8.0_121, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-oracle/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "4.4.0-64-generic", arch: "amd64", family: "unix"

No major issues in the reports, signatures match, successfully generated the 
site locally.

Minor issues, non blockers I think:

* On the front page of the web site, the link to Sonar is broken

* RAT report in my computer is complaining about 
src/site/resources/release-notes/RELEASE-NOTES-1.0-beta-1.txt, but this file 
will be probably be removed during the release

* Few Tags (TODO/FIXME/etc) in the Tag List report, but I believe they are 
coming from classes migrated from [lang], so it should be fine for 1.0 release

* JIRA links for unresolved and patch needed issues are broken for me too, 
returning 50x error, but probably due to the query generated by the plugin?

* RELEASE-NOTES.txt in the dist site is mentioning the -beta release a few 
times where it should be 1.0 I think

Thanks Rob!
Bruno


- Original Message -
From: Rob Tompkins 
To: Commons Developers List 
Sent: Tuesday, 7 March 2017 2:07 AM
Subject: [VOTE] Release Commons Text 1.0 based on RC1

Hello all,

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

Tag name:
   commons-text-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-text.git;a=commit;h=e38039a3da2244741f5d33ab1b05bdee51c53c3e

Commit ID the tag points at:
   e38039a3da2244741f5d33ab1b05bdee51c53c3e

Site:
  http://home.apache.org/~chtompki/commons-text-1.0-RC1

Distribution files (committed at revision 18567):
  https://dist.apache.org/repos/dist/dev/commons/text/

Distribution files hashes (SHA1):
   commons-text-1.0-bin.tar.gz
   (SHA: a6eb41fd426d876669cc6799afd7435d97285229)
   commons-text-1.0-bin.zip
   (SHA1: 72e732a38f41aa7934a4a9834451f0a2f368dd4e)
   commons-text-1.0-src.tar.gz
   (SHA1: 83a57a925cc551bf2e6e38be12eec953820212b9)
   commons-text-1.0-src.zip
   (SHA1: d838bb107bcdbe58bba0525f8fd7341a2b40)

These are the Maven artifacts and their hashes:
   commons-text-1.0-javadoc.jar
   (SHA1: 0e904fc88c8e6cc615e53c5c8246705f8e3d8d25)
   commons-text-1.0-sources.jar
   (SHA1: 53a622edbc40f345d7015345524ace2536a8dffc)
   commons-text-1.0-test-sources.jar
   (SHA1: baabd28e90e8f7a8765b76c8882bee058a956116)
   commons-text-1.0-tests.jar
   (SHA1: adf8d0638132df9e23a4a0416741dc1c3d6be664)
   commons-text-1.0.jar
   (SHA1: 71413afd09c3ca8b3a796bc2375ef154b0afa814)
   commons-text-1.0.pom
   (SHA1: 7220d033f589194704533680c76c6a74cabe6d57)

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

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

Please select one of the following options[1]:
  [ ] +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 at least 72 hours, i.e. until 
2017-03-09T14: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 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