On 8 January 2018 at 00:25, Jörg Schaible wrote:
> Am Sun, 07 Jan 2018 12:04:16 +0100 schrieb Pascal Schumacher:
>
>> Am 07.01.2018 um 11:10 schrieb Stefan Bodewig:
>>> My memory (which is old and failing frequently) claims we didn't want
>>> to put it into the parent as not all components can use
Am Sun, 07 Jan 2018 12:04:16 +0100 schrieb Pascal Schumacher:
> Am 07.01.2018 um 11:10 schrieb Stefan Bodewig:
>> My memory (which is old and failing frequently) claims we didn't want
>> to put it into the parent as not all components can use automatic
>> module names (net hasn't got a single pack
On Sun, 7 Jan 2018 20:50:51 + (UTC), ggreg...@apache.org wrote:
Repository: commons-rng
Updated Branches:
refs/heads/master 0a3149e25 -> 6cc21c16d
Update commons-parent from 42 to 43.
Change results in
$ mvn site
to fail.
Gilles
Project: http://git-wip-us.apache.org/repos/asf/com
On Sun, Jan 7, 2018 at 1:47 PM, Oliver Heger
wrote:
> Hi,
>
> Am 07.01.2018 um 21:38 schrieb ggreg...@apache.org:
> > Author: ggregory
> > Date: Sun Jan 7 20:38:53 2018
> > New Revision: 1820487
> >
> > URL: http://svn.apache.org/viewvc?rev=1820487&view=rev
> > Log:
> > Update commons-parent fro
[This announcement is only going to the dev list.]
The Apache Commons Parent team is pleased to announce the release of Apache
Commons Parent 43
The Apache Commons Parent POM provides common settings for all Apache
Commons components.
Updates plugins and generally requires Java 7.
Changes in th
This vote passes with the following appearances:
Gary Gregory: +1
Jochen Wiedmann: +1
Bruno P. Kinoshita: +1
Gilles Sadowski: +1
Oliver Heger: +1
Pascal Schumacher: +1
Sergio Fernández: +1
I will proceed with creating the git repository, and begin using COMMONSSITE as
the jira tracking location.
Might be sensible to add a note to the parent pom to say why it does
not have the feature.
On 7 January 2018 at 11:04, Pascal Schumacher wrote:
> Am 07.01.2018 um 11:10 schrieb Stefan Bodewig:
>>
>> My memory (which is old and failing frequently) claims we didn't want to
>> put it into the parent
Am 07.01.2018 um 11:10 schrieb Stefan Bodewig:
My memory (which is old and failing frequently) claims we didn't want to
put it into the parent as not all components can use automatic module
names (net hasn't got a single package root IIRC) and so wewanted to
leave it to the individual components.
On 2018-01-07, Pascal Schumacher wrote:
> Hello everybody,
> just noticed that Parent POM 43 does not seem to set the automatic
> module name in the jar manifest.
> Did I miss something you did we just forget to add the required
> maven-jar-plugin configuration?
My memory (which is old and fail
Hello everybody,
just noticed that Parent POM 43 does not seem to set the automatic
module name in the jar manifest.
Did I miss something you did we just forget to add the required
maven-jar-plugin configuration?
-Pascal
--
Thank you very much!
-Pascal
Am 06.01.2018 um 20:18 schrieb Gary Gregory:
This LAZY VOTE passes with one binding +1 VOTE from yours truly.
Gary
On Tue, Jan 2, 2018 at 1:19 PM, Gary Gregory wrote:
We have updated plugins and are now ready to use Java 9 to build sites, so
I would like to rel
11 matches
Mail list logo