On Fri, Sep 6, 2019 at 9:19 PM Gilles Sadowski wrote:
> 2019-09-06 16:53 UTC+02:00, Mark Thomas :
> > Hi all,
> >
> > I've looked but can't find a previous vote on this.
>
> Right; we stopped short of voting because the discussion
> didn't elicit much interest:
>https://markmail.org/message/b
2019-09-06 16:53 UTC+02:00, Mark Thomas :
> Hi all,
>
> I've looked but can't find a previous vote on this.
>
> The current logo is:
> https://apache.org/foundation/press/kit/ApacheFoundation_StyleGuide.pdf
>
> The options for the new logo are:
>
> https://issues.apache.org/jira/browse/COMMONSSITE-
2019-09-06 16:53 UTC+02:00, Mark Thomas :
> Hi all,
>
> I've looked but can't find a previous vote on this.
Right; we stopped short of voting because the discussion
didn't elicit much interest:
https://markmail.org/message/bgbzusjpfulou4pq
I thus went on making logos for the new components:
h
Here is the article that describes how to get the JavaDoc from unit tests.
https://javax0.wordpress.com/2019/09/04/keep-javadoc-up-to-date/
--
Peter Verhas
pe...@verhas.com
t: +41791542095
skype: verhas
Hello.
We, at Apache Commons, would like to know whether an Apache
project is authorized to extract graphical elements from the
foundation's logo, apply some transformation to them, and use
the result in order to compose its own logo.
Case in point is here:
https://svn.apache.org/repos/asf/c
Run:
mvn clean site -P jacoco
Then look at the generate site's JaCoCo report and make sure the new code
has as close to possible to 100% code coverage by the unit tests.
The profile might not be required but it will make sure the right thing
happens.
Gary
On Fri, Sep 6, 2019, 19:58 Mark Robert
On Fri, 6 Sep 2019 at 22:51, Gilles Sadowski wrote:
>
> Hello.
>
> Le ven. 6 sept. 2019 à 16:53, Mark Thomas a écrit :
> >
> > Hi all,
> >
> > I've looked but can't find a previous vote on this.
> >
> > The current logo is:
> > https://apache.org/foundation/press/kit/ApacheFoundation_StyleGuide.p
I might have some time over the weekend. Would you mind double checking you
recent work for code coverage.
Gary
On Fri, Sep 6, 2019, 09:07 Mark Roberts wrote:
> I'm good. From our standpoint it would be nice to make a BCEL release so
> we don't need to include a special version with our tool s
Hello.
Le ven. 6 sept. 2019 à 16:53, Mark Thomas a écrit :
>
> Hi all,
>
> I've looked but can't find a previous vote on this.
>
> The current logo is:
> https://apache.org/foundation/press/kit/ApacheFoundation_StyleGuide.pdf
>
> The options for the new logo are:
>
> https://issues.apache.org/jir
What I can do is to implement a DiffView class as a simple String key,
String leftVal and String rightVal triplet and implement a toString method
there.
We will then see if it’s relevant to add it to the lib or not
Le ven. 6 sept. 2019 à 18:31, sebb a écrit :
> [Added component prefix]
>
> On Fr
[Added component prefix]
On Fri, 6 Sep 2019 at 16:20, Nicolas BD wrote:
>
> Hi all,
>
> TL;DR : I think we should be able to add arbitrary diffs to a diff result,
> not only those related to its type fields. We could create a class allowing
> us to store a Diff as a simple "key", "val1", "val2" t
Hi all,
TL;DR : I think we should be able to add arbitrary diffs to a diff result,
not only those related to its type fields. We could create a class allowing
us to store a Diff as a simple "key", "val1", "val2" triplet
I'm new to this list and just made a small addition to one of the classes
of
On Fri, 6 Sep 2019 at 15:53, Mark Thomas wrote:
>
> Hi all,
>
> I've looked but can't find a previous vote on this.
>
> The current logo is:
> https://apache.org/foundation/press/kit/ApacheFoundation_StyleGuide.pdf
>
> The options for the new logo are:
>
> https://issues.apache.org/jira/browse/COM
Hi all,
I've looked but can't find a previous vote on this.
The current logo is:
https://apache.org/foundation/press/kit/ApacheFoundation_StyleGuide.pdf
The options for the new logo are:
https://issues.apache.org/jira/browse/COMMONSSITE-86
Of those, commons_logo.small.png is not consistent wit
On 06/09/2019 14:07, Gilles Sadowski wrote:
> Hi.
>
> Le ven. 6 sept. 2019 à 14:49, Mark Thomas a écrit :
>>
>> On 06/09/2019 13:05, Gilles Sadowski wrote:
>>> Hi.
>>>
>>> Le ven. 6 sept. 2019 à 12:17, Mark Thomas a écrit :
On 05/09/2019 21:39, Mark Thomas wrote:
>
I'm good. From our standpoint it would be nice to make a BCEL release so we
don't need to include a special version with our tool set.
Thanks,
Mark
-Original Message-
From: Gary Gregory [mailto:garydgreg...@gmail.com]
Sent: Sunday, September 1, 2019 3:25 PM
To: Commons Developers List
Hi.
Le ven. 6 sept. 2019 à 14:49, Mark Thomas a écrit :
>
> On 06/09/2019 13:05, Gilles Sadowski wrote:
> > Hi.
> >
> > Le ven. 6 sept. 2019 à 12:17, Mark Thomas a écrit :
> >>
> >> On 05/09/2019 21:39, Mark Thomas wrote:
> >>
> >>
> >>
> >>> [X] Approved - go ahead and release Commons Daemon 1
On 06/09/2019 13:05, Gilles Sadowski wrote:
> Hi.
>
> Le ven. 6 sept. 2019 à 12:17, Mark Thomas a écrit :
>>
>> On 05/09/2019 21:39, Mark Thomas wrote:
>>
>>
>>
>>> [X] Approved - go ahead and release Commons Daemon 1.2.1 RC1 as 1.2.1
>>> [ ] Broken - do not release because...
>>
>> Tested wit
[X] Approved - go ahead and release Commons Daemon 1.2.1 RC1 as 1.2.1
CheersBruno
On Friday, 6 September 2019, 8:39:19 am NZST, Mark Thomas
wrote:
A couple of regressions have been identified in the 1.2.0 release so I'd
like to get 1.2.1 released to address them. So, time for another
Hi.
Le ven. 6 sept. 2019 à 12:17, Mark Thomas a écrit :
>
> On 05/09/2019 21:39, Mark Thomas wrote:
>
>
>
> > [X] Approved - go ahead and release Commons Daemon 1.2.1 RC1 as 1.2.1
> > [ ] Broken - do not release because...
>
> Tested with a release build of Tomcat 9.0.x - all good.
>
> I did n
On 05/09/2019 21:39, Mark Thomas wrote:
> [X] Approved - go ahead and release Commons Daemon 1.2.1 RC1 as 1.2.1
> [ ] Broken - do not release because...
Tested with a release build of Tomcat 9.0.x - all good.
I did notice that the about box for prunmgr uses the old Commons logo.
I'll get tha
[This was sent to private@commons, but does not seem to have been
forwarded to the dev@ list.]
Please note the penultimate paragraph about tagging successful
releases under rel/
AFAICT, we have not been doing that, so our release tags are not
automatically protected against deletion.
We should p
22 matches
Mail list logo
