Dear all,
I am pleased to announce that the vote to release Apache log4php 2.3.0
has passed.
The following binding votes were cast:
* Christian Grobmeier +1
* Ralph Goers +1
* Ivan Habunek +1
There were no non-binding votes.
Thanks to everyone who participated. I will be publishing the release
Here is my official +1.
Regards,
Ivan
On 8 October 2012 17:56, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the first release candidate for Apache
> log4php version 2.3.0.
>
> Apache log4php 2.3.0 RC1 is available for review here:
> * http://peo
+1
I have expected some SHA1 but they are not so important if you ask me.
The new site looks great! Good job, thank you!
Best regards
On Mon, Oct 8, 2012 at 5:56 PM, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the first release candidate for Apache
> log4php v
Dear all,
It is my pleasure to announce the first release candidate for Apache
log4php version 2.3.0.
Apache log4php 2.3.0 RC1 is available for review here:
* http://people.apache.org/builds/logging/log4php/2.3.0/RC1/
The KEYS file for verifying signatures is located at:
* http
Dear all,
I am pleased to announce that the vote to release Apache log4php 2.2.1
has passed.
The following binding votes were received:
* Christian Grobmeier +1
* Ivan Habunek +1
* Curt Arnold +1
Along with the following non binding votes:
* Vladimir Gorej +1
* Florian Semm +1
* Michael Schmitz
Begin forwarded message:
> From: Curt Arnold
> Subject: Re: [VOTE] Release Apache log4php 2.2.1
> Date: February 17, 2012 10:55:49 PM CST
> To: "Logging PMC"
>
> signatures are good. Contents of zip and tar and svn tag are identical.
> NOTICE, LICENSE and lic
eciated!
> Please respond to the general/log4php-dev list - thanks!
>
> Cheers
> Christian
>
> On Wed, Feb 15, 2012 at 11:01 AM, Ivan Habunek wrote:
>> Dear all,
>>
>> It is my pleasure to announce the first release candidate for Apache
>> log4php 2.2.
re to announce the first release candidate for Apache
> log4php 2.2.1.
>
> This is a maintenance release which fixes several important bugs (see
> change log below) and features yet another update to the web site
> design.
>
> The release is available for review here:
> * h
Hi Dmitry, I'm moving your question to a new thread.
On 15 February 2012 12:28, Dmitry Perlroizen wrote:
> Hello log4php!
> Just a proposal, I hope it can be interesting...
We welcome proposals. :)
> I think it would be a good idea if socket appenders (or their layouts) would
> allow users to c
On 15/02/2012 12:01, Ivan Habunek wrote:
Dear all,
It is my pleasure to announce the first release candidate for Apache
log4php 2.2.1.
This is a maintenance release which fixes several important bugs (see
change log below) and features yet another update to the web site
design.
The release is ava
Look fine for me, so +1.
BR
Michael.
-Original Message-
From: Ivan Habunek [mailto:[email protected]]
Sent: Wednesday, February 15, 2012 11:01
To: Log4php Dev; Logging General
Subject: [VOTE] Release Apache log4php 2.2.1
Dear all,
It is my pleasure to announce the first release
Checked sigs, looked into packages, checked the site. Looks all very
good to me thus a big +1 and a huge "thank you" for the work!
Cheers
Christian
On Wed, Feb 15, 2012 at 11:01 AM, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the first release c
Here's my +1
Regards,
Ivan
On 15 February 2012 11:01, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the first release candidate for Apache
> log4php 2.2.1.
>
> This is a maintenance release which fixes several important bugs (see
> change log below
+1
Original-Nachricht
> Datum: Wed, 15 Feb 2012 11:01:19 +0100
> Von: Ivan Habunek
> An: Log4php Dev , Logging General
>
> Betreff: [VOTE] Release Apache log4php 2.2.1
> Dear all,
>
> It is my pleasure to announce the first release candidate fo
Dear all,
It is my pleasure to announce the first release candidate for Apache
log4php 2.2.1.
This is a maintenance release which fixes several important bugs (see
change log below) and features yet another update to the web site
design.
The release is available for review here:
* http
Dear all,
I am pleased to announce that the vote to release Apache log4php 2.2.0
has passed.
Binding votes:
- Christian Grobmeier +1
- Ivan Habunek +1
- Scott Deboy +1
- Stefan Bodewig +1
- Ralph Goers +1
Non-binding votes:
- Florian Semm +1
Thanks to everyone who participated. I will start
Hmm I think notice file needs to include jquery refs, yes?
If so that's probably cause to re-rool an rc.
Scott
On Dec 17, 2011, at 2:25 AM, Ivan Habunek
wrote:
On 17 December 2011 10:45, Christian Grobmeier
wrote:
Whats meant is the LICENSE file needs to contain the MIT/GPL license:
+1
On Dec 17, 2011, at 4:36 AM, Christian Grobmeier
wrote:
OK looks good to me: +1
Thanks!
On Sat, Dec 17, 2011 at 12:08 PM, Ivan Habunek
wrote:
Dear all,
It is my pleasure to announce the second release candidate for Apache
log4php version 2.2.0.
Changes since RC1 are
OK looks good to me: +1
Thanks!
On Sat, Dec 17, 2011 at 12:08 PM, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the second release candidate for Apache
> log4php version 2.2.0.
>
> Changes since RC1 are:
> * Updated LICENSE file to include jQuery licens
Am 17.12.2011 12:09, schrieb Ivan Habunek:
To start things off, here's my +1.
Best regards,
Ivan
On 17 December 2011 12:08, Ivan Habunek wrote:
Dear all,
It is my pleasure to announce the second release candidate for Apache
log4php version 2.2.0.
Changes since RC1 are:
* Updated LI
To start things off, here's my +1.
Best regards,
Ivan
On 17 December 2011 12:08, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the second release candidate for Apache
> log4php version 2.2.0.
>
> Changes since RC1 are:
> * Updated LICENSE file
Dear all,
It is my pleasure to announce the second release candidate for Apache
log4php version 2.2.0.
Changes since RC1 are:
* Updated LICENSE file to include jQuery license
* Fixed dates in NOTICE file
* Added license headers to minified js and css files
* Added (tm) to project name in
On 17 December 2011 10:45, Christian Grobmeier wrote:
> Whats meant is the LICENSE file needs to contain the MIT/GPL license:
> http://www.apache.org/dev/release.html#distributing-code-under-several-licenses
>
> I think the LICENSE must containt the license of jquery and probably
> even in the NOT
even in the NOTICE file this must be mentioned:
http://apache.org/legal/resolved.html#required-third-party-notices
Cheers
Christian
>
> [1]
> http://people.apache.org/~ihabunek/apache-log4php-2.2.0-RC1/site/js/jquery.js
>
>> Also, in the changelog, the release date: TBA, when
Hi Christian,
On 17 December 2011 08:20, Christian Grobmeier wrote:
> +1
>
> Checked the site (AMAZING work, thanks!!), the sigs, checksums etc.
>
> - we should update the NOTICE file with the next release, because
> copyright is 2004 - 2011, not 2010
> - on the the site top
ome reason. The other three are minified versions (originals
are also included in the distribution along with their respective
licenses). I was under the impression that generated files do not need
to have a licence header. Am I wrong?
[1]
http://people.apache.org/~ihabunek/apache-log4php-2.2.0-RC1/site/js
/bootstrap.min.css
>
>
> Also, in the changelog, the release date: TBA, when does that get updated?
>
> If the jquery license doesn't need to be added to the notice file, I'm +1
>
> Scott
>
>
> On Fri, Dec 16, 2011 at 11:20 PM, Christian Grobmeier
>
ry.js
src/site/resources/js/prettify.min.js
src/site/resources/css/bootstrap.min.css
Also, in the changelog, the release date: TBA, when does that get updated?
If the jquery license doesn't need to be added to the notice file, I'm +1
Scott
On Fri, Dec 16, 2011 at 11:20 PM, Christian
+1
Checked the site (AMAZING work, thanks!!), the sigs, checksums etc.
- we should update the NOTICE file with the next release, because
copyright is 2004 - 2011, not 2010
- on the the site top left in the branding bar - is it possible to add
a tm to products name? it is very prominent.
- we
Hi Ivan,
It is ok ivan, Thanks for the help and I am looking forward to join with
this project.
Glad to work with PHP :)
See you and happy release.
On Thu, Dec 15, 2011 at 7:58 PM, Ivan Habunek wrote:
> I apologise, I forgot to change the subject when replying.
>
> Please ignore
so others can
> participate, hope you don't mind.
>
> Of course, you are welcome to work on log4php. However, currently we
> do not have a road map for the next release so I can't point you to an
> exact task.
>
> Have a look at our vounteering page for some ideas of wha
Hi Buddhika,
I am forwarding this conversation to log4php dev list so others can
participate, hope you don't mind.
Of course, you are welcome to work on log4php. However, currently we
do not have a road map for the next release so I can't point you to an
exact task.
Have a l
Dear all,
It is my pleasure to announce the first release candidate for Apache
log4php version 2.2.0.
There have been many changes to the code, greatest of which is a full
rewrite of the configuration logic. The full change log is available
on the staged site (see below).
Apache log4php 2.2.0
No objections.
Thanks for the hard work so far and thanks for serving as RM.
I gladly serve as release tester :)
Cheers
Christian
On Tue, Dec 13, 2011 at 3:46 PM, Ivan Habunek wrote:
> Hi everybody,
>
> The work planned for 2.2. has been done and there are no pending
> issues left
Hi everybody,
The work planned for 2.2. has been done and there are no pending
issues left in JIRA. If nobody has any objections, I propose that we
draw the line here and release 2.2.
I propose myself as the release manager. If nobody has any complaints,
I will begin staging a release candidate
should increase the number of PHP
example configurations. A "nice to have" feature would be a switch like in
the documentation of Doctrine: [1]
I don't know if point one is important enougth to realize it for the 2.2
release, but in the coming 2.3 release it should be.
[1]:
http
e number of PHP
> example configurations. A "nice to have" feature would be a switch like in
> the documentation of Doctrine: [1]
>
>
> I don't know if point one is important enougth to realize it for the 2.2
> release, but in the coming 2.3 release it should be.
>
&g
Am 08.12.2011 09:35, schrieb Ivan Habunek:
If you have the time, there is one thing I would love some help with,
and that's the docs. I have rewritten a lot of them for this release,
trying to put more focus on the XML and PHP configuration formats, and
less on INI. If you could read throug
Thanks Ivan for sharing on list. Florian, at the ASF we say:"if it
didn't happen on list, it didn't happen".
Even when most of us are pretty inactive (like me), some of us are
still interested (like me) and probably want to lend a hand.
On topic, I would love to see a new re
Hi Florian,
I'm forwarding this to the Dev mailing list. Most other developers are
not very active at this very moment, but just to keep them in the
loop.
I think that we already have plenty new features and we could stage a
release very soon. The reason that this has not yet happened is t
up.
>
> Best regards,
> Ivan
>
>
>
>
>
>
>
>
>
> On 12 July 2011 11:17, Ivan Habunek wrote:
>> Dear all,
>>
>> I am pleased to announce that the vote to release Apache log4php 2.1.0
>> has passed.
>>
>> The following people
:
* Christian Grobmeier +1
* Scott Deboy +1
* Ivan Habunek +1
* Vladimir Gorej +1 (non binding)
* Yoav Shapira +1 (non binding)
Sorry for the mixup.
Best regards,
Ivan
On 12 July 2011 11:17, Ivan Habunek wrote:
> Dear all,
>
> I am pleased to announce that the vote to relea
Dear all,
I am pleased to announce that the vote to release Apache log4php 2.1.0
has passed.
The following people voted:
* Christian Grobmeier +1
* Vladimir Gorej +1
* Ivan Habunek +1
* Scott Deboy +1 (non binding)
Thanks to everyone who participated. I will be publishing the release
in the
wrote:
> Friendly reminder - we still need one more +1 from a PMC for this release.
> If somebody has the time to check it out, please feel free :-)
>
> Thanks in advance!
> Christian
>
> On Tue, Jun 28, 2011 at 11:35 PM, Ivan Habunek wrote:
>> Dear all,
>>
>&
Friendly reminder - we still need one more +1 from a PMC for this release.
If somebody has the time to check it out, please feel free :-)
Thanks in advance!
Christian
On Tue, Jun 28, 2011 at 11:35 PM, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the second release
I'm not going to be able to check anything this weekend. I'm all in favor of a
successful release, but I can't vote without checking.
Sorry, getting ahead of myself. I was testing the release procedure.
Removed now.
Regards,
Ivan
On 30 June 2011 15:36, Christian Grobmeier wrote:
> Hello Ivan,
>
> we need to close a vote with 3 PMCs +1s - we have 3 so far.
>
> So log4php 2.1.0 must not be available on the /dis
, Jun 28, 2011 at 11:35 PM
Subject: [VOTE] Release Apache log4php 2.1.0 (RC2)
To: Log4PHP Dev , [email protected]
Dear all,
It is my pleasure to announce the second release candidate for Apache
log4php 2.1.0.
Since we are short of PMC members at the log4php project, I would
appreciate
On 06/26/2011 12:18 PM, Ivan Habunek wrote:
Dear all,
It is my pleasure to announce the first release candidate for Apache
log4php 2.1.0.
Significant changes in this release include:
* a new logging level: trace
* a new appender: MongoDB (thanks to Vladimir Gorej)
* a plethora of
On 29.6.2011. 1:44, Scott Deboy wrote:
> Wandering through the site, the download links still show 'incubating'..
Oh, totaly forgot to increment the version number on the site. D'oh. :)
Is this a blocker in your opinion or is it ok to fix immediately after
the release?
>
Hi Ivan,
Wandering through the site, the download links still show 'incubating'..
Will report more if I find them..
Scott
On Tue, Jun 28, 2011 at 2:35 PM, Ivan Habunek wrote:
> Dear all,
>
> It is my pleasure to announce the second release candidate for Apache
> log4p
Dear all,
It is my pleasure to announce the second release candidate for Apache
log4php 2.1.0.
Since we are short of PMC members at the log4php project, I would
appreciate if other PMCs would join in so that we may pass this vote.
Fixes compared to RC1:
* included build.xml in source packages
On 27 June 2011 13:45, Christian Grobmeier wrote:
>> I agree about the site. I'll put it up ASAP.
>
> cool
The web for 2.1.0-RC1 can be found here:
http://people.apache.org/~ihabunek/apache-log4php-2.1.0-RC1/site/
The issue with the version number in api docs has been corrected.
Regards,
Ivan
r it.
> I agree about the site. I'll put it up ASAP.
cool
> BTW, I'm updating the release plan from the wiki as I go through it.
> I'm doing the changes locally, and will update the wiki when it's
> done.
Great, thanks for taking care!
Cheers
Christian
>
>
OK, I'll take care of it. Should we wait a bit to see if other PMCs
have any remarks before generating RC2?
I agree about the site. I'll put it up ASAP.
BTW, I'm updating the release plan from the wiki as I go through it.
I'm doing the changes locally, and will update the
announce the first release candidate for Apache
> log4php 2.1.0.
>
> Significant changes in this release include:
> * a new logging level: trace
> * a new appender: MongoDB (thanks to Vladimir Gorej)
> * a plethora of bugfixes and other code improvements
> * most of the site
Dear all,
It is my pleasure to announce the first release candidate for Apache
log4php 2.1.0.
Significant changes in this release include:
* a new logging level: trace
* a new appender: MongoDB (thanks to Vladimir Gorej)
* a plethora of bugfixes and other code improvements
* most of the
23 June 2011 13:05, Christian Grobmeier wrote:
> Guys,
>
> we are ready for the next release!
>
> Thanks to Ivan we have made a good progress on the latest issues.
> Anyway, Ivan, you have kindly offered yourself to serve as a release
> manager. I would like to ask you to hel
Guys,
we are ready for the next release!
Thanks to Ivan we have made a good progress on the latest issues.
Anyway, Ivan, you have kindly offered yourself to serve as a release
manager. I would like to ask you to help with this role this time,
whenever you have the time :-)
If there are others
[
https://issues.apache.org/jira/browse/LOG4PHP-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek resolved LOG4PHP-90.
-
Resolution: Fixed
> Minor release artifacts improvme
the unused incubation logo
2. CHANGELOG now points to src/changes/changes.xml and to the online changelog.
3. Renamed docs folder to apidocs.
4. Generated docs will not be included for the time being. We will consider
this when moving to doxygen (LOG4PHP-135).
> Minor release artifacts impr
[
https://issues.apache.org/jira/browse/LOG4PHP-90?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Ivan Habunek reassigned LOG4PHP-90:
---
Assignee: Ivan Habunek
> Minor release artifacts improvme
Hi Alex,
> As I understood from the mailing list archive, there were plans to release
> new tag of log4php this March.
> Apparently, it didn't happen in time, but what is the current status in this
> area?
> Is there any way I can help with this topic?
you are right, we
Hello,
As I understood from the mailing list archive, there were plans to release
new tag of log4php this March.
Apparently, it didn't happen in time, but what is the current status in this
area?
Is there any way I can help with this topic?
http://svn.apache.org/repos/asf/logging/log4j/trunk/BUILD-INFO.txt describes
the preparation of log4j 1.2.16. Some of that is applicable (the set up for
the web content) which other parts aren't.
Then there are the generic Apache Release Signing/Voting/Mirroring
requirements,
On 21 February 2011 11:58, Christian Grobmeier wrote:
> Most of them are not to difficult any objections on this list?
Looks ok to me.
> Guess we could do a new release by end of march... thoughts? I think
> its really time now.
I definitely agree. I'll try to put in
Hi,
thanks for bringing this up.
just looked through the remaining open issues in jira.
Issues we should resolve before release (* indicates patch available):
LOG4PHP-123*
LOG4PHP-128 (easy)
LOG4PHP-124
LOG4PHP-129 (I thought this one is already done? need to check in code)
LOG4PHP-90
LOG4PHP-89
Hello,
I was wondering if there's a tagged release planned for the near future?
There have been a few bugfixes recently which I'd like to take advantage
of, and unfortunately our library manager can't work off trunk
repositories.
Hello all,
we have some issues left before 2.1. But most of them already have
patches from contributors in it. I think there could be a new release
available pretty soon if some of you comitters have some time left to
help. So, how is your planning the next weeks :-) Is somebody free for
help
interest
> Official release date?
> --
>
> Key: LOG4PHP-72
> URL: https://issues.apache.org/jira/browse/LOG4PHP-72
> Project: Log4php
> Issue Type: Question
> Components: Documentation
&g
Hi,
here is the new entry for the release:
https://blogs.apache.org/preview/log4php/?previewEntry=apache_log4php_2_0_0
Its going online tomorrow lunch in Brisbane - any changes, let me know
or just edit the entry yourself.
Best regards,
Christian
Dear all,
I just created a download page and cared about mirroring the release.
Everything is in place.
Just one thing: because of the buildbot error the download page is not
deployed to the site. We need to fix buildbot or to put this manually
online. Gavin - if you have time, can you try to
Dear all,
this incubator pmc vote has passed with 3x +1 from:
antelder, gmcdonald and carnold
Thanks for voting and your help!
I will upload the release somewhen early next week.
Best regards,
Christian
-- Forwarded message --
From: Curt Arnold
Date: Sat, Dec 5, 2009 at 8:06
Minor release artifacts improvments
---
Key: LOG4PHP-90
URL: https://issues.apache.org/jira/browse/LOG4PHP-90
Project: Log4php
Issue Type: Bug
Components: Code, Documentation
Affects Versions
The log4php-dev vote was opened on Nov 27, 2009 and closed on Dec 4, 2009.
Binding +1 votes were received from Christian Grobmeier, Christian Hammers and
Curt Arnold. No other votes were received.
Christian has called for a vote on [email protected] at
http://mail-archives.apache.o
ID is: ded132f10911262256j12c0cfej21e7e5dbdcf18bf7
We kindly ask the incubator PMC to vote on our artifacts too:
[ ] +1 Yes go ahead and release the artifacts
[ ] -1 No, because...
Thanks,
Christian
-- Forwarded message --
From: Christian Grobmeier
Date: Fri, Nov 27, 2009 at 7
ID is: ded132f10911262256j12c0cfej21e7e5dbdcf18bf7
We kindly ask the incubator PMC to vote on our artifacts too:
[ ] +1 Yes go ahead and release the artifacts
[ ] -1 No, because...
Thanks,
Christian
-- Forwarded message --
From: Christian Grobmeier
Date: Fri, Nov 27, 2009 at 7
uthorization file and all three +1's are in the logging-log4php group
which is my best approximation of the PPMC membership list, so I think we have
three binding votes and we've exceeded 72 hours. I think we are good to go to
the Incubator PMC.
http://incubator.apache.org/guides/rel
Thanks Curt! I appreciate your effort and will document your installation guide
How many +1 are necessary for pushing forward?
On Thu, Dec 3, 2009 at 4:12 AM, Curt Arnold wrote:
> I was able to nearly rebuild the release which had only minor variations from
> in the generated documen
I was able to nearly rebuild the release which had only minor variations from
in the generated documentation. Every generated docfile had a "Documentation
generated by" timestamp which obviously varied. The other issue is that my
check build had a few places where classes a
Hello
+1
bye,
-christian-
Am Fri, 27 Nov 2009 07:56:11 +0100
schrieb Christian Grobmeier :
> Dear all,
>
> please vote to release the following artifacts as version 2.0.0:
>
> [ ] +1 Yes go ahead and release the artifacts
> [ ] -1 No, because...
>
> Log4PHP 2.0.0
Dear all,
please vote to release the following artifacts as version 2.0.0:
[ ] +1 Yes go ahead and release the artifacts
[ ] -1 No, because...
Log4PHP 2.0.0 artifacts are available for review here:
* http://people.apache.org/builds/logging/log4php/2.0.0/RC3/
The release plan used for the
This vote is invalid of course - i start a new one
Thanks for all comments
On Mon, Nov 23, 2009 at 7:00 AM, Christian Grobmeier
wrote:
> Dear all,
>
> please vote to release the following artifacts as version 2.0.0:
>
> [ ] +1 Yes go ahead and release the artifacts
>
Hi,
thanks Christian to making those fixes so quickly :-)
> > 3. Generated docs placed in target/site directory.
>> target is the default build directory for maven. Typically, the site
>> built with the release is placed in doc, leaving the target directory
>> avail
if my project includes its web site within a product
> > distribution?
> >
> > With few exceptions, all human-readable Apache-developed files that
> > are included within a distribution must include the header text.
> > Documentation, including web site documentation distribut
23 November 2009 4:00 PM
>> To: Log4PHP Dev
>> Subject: [VOTE] Release Log4PHP-2.0.0
>>
>> Dear all,
>>
>> please vote to release the following artifacts as version 2.0.0:
>>
>> [ ] +1 Yes go ahead and release the artifacts
>> [ ] -1 No, becau
> -Original Message-
> From: Christian Grobmeier [mailto:[email protected]]
> Sent: Monday, 23 November 2009 4:00 PM
> To: Log4PHP Dev
> Subject: [VOTE] Release Log4PHP-2.0.0
>
> Dear all,
>
> please vote to release the following artifacts as version 2.0.
> included within a distribution must include the header text. Documentation,
> including web site documentation distributed with the release, may include
> the header text within some form of metadata (such as HTML comments) or as a
> header or footer appearing in the visible docum
-
Am Mon, 23 Nov 2009 07:00:15 +0100
schrieb Christian Grobmeier :
> Dear all,
>
> please vote to release the following artifacts as version 2.0.0:
>
> [ ] +1 Yes go ahead and release the artifacts
> [ ] -1 No, because...
>
> Log4PHP 2.0.0 artifacts are available for
Dear all,
please vote to release the following artifacts as version 2.0.0:
[ ] +1 Yes go ahead and release the artifacts
[ ] -1 No, because...
Log4PHP 2.0.0 artifacts are available for review here:
* http://people.apache.org/builds/logging/log4php/2.0.0/RC2/
The release plan used for the
> Time for RC2?
Yeah, will start on it tomorrow :)
Thanks !
>
> bye,
>
> -christian-
>
> Am Thu, 19 Nov 2009 21:38:41 -0600
> schrieb Curt Arnold :
>
>> The {...@example} directive can optionally take an starting line number
>> (http://manual.phpdoc.org/HTMLSmartyConverter/HandS/phpDocumentor/t
Hello
That was a good hint. I did as you suggested and now RAT is happy.
The MDC and NDC phpdoc looks proper again, too.
Time for RC2?
bye,
-christian-
Am Thu, 19 Nov 2009 21:38:41 -0600
schrieb Curt Arnold :
> The {...@example} directive can optionally take an starting line number
> (http://
The {...@example} directive can optionally take an starting line number
(http://manual.phpdoc.org/HTMLSmartyConverter/HandS/phpDocumentor/tutorial_tags.inlineexample.pkg.html).
I've played with it with LoggerMDC.php and it would seem to allow us to add
the ASF source license header to the examp
acted them from there to be able
to automatically check them for syntax errors. But a unit test for examples
didn't turn out to be as easy as I thought.
> >> Since the generated docs could depend on the version of phpdoc
> >> installed, I think it would be good to disclose
; that I don't want a long and complex discussion about some example
> files. I even would prefer to leave the examples out from the release
> and put it on the webpage only instead. However, adding the license is
> the most pragmatic way imho.
>
> Isn't there a way to get
ver.php is 55 lines of
> non-trivial code.
I am not a legal expert but why can't we simply add all licenses to
all files we have, regardless if they contain 1 or 100 lines. I feel
that I don't want a long and complex discussion about some example
files. I even would prefer to lea
On Nov 18, 2009, at 4:44 PM, Christian Hammers wrote:
Hello Curt
Am Tue, 17 Nov 2009 22:42:45 -0600
schrieb Curt Arnold :
Running "mvn rat:check" generates a RAT (release audit tool) report
in target/rat.txt. The check fails since all the .php files in src/
examples/php and sr
Hello Curt
Am Tue, 17 Nov 2009 22:42:45 -0600
schrieb Curt Arnold :
> Running "mvn rat:check" generates a RAT (release audit tool) report
> in target/rat.txt. The check fails since all the .php files in src/
> examples/php and src/examples/resources do not have ASF Sour
ed docs could depend on the version of phpdoc installed, I
> think it would be good to disclose the environment that is used to build the
> release packages. Ideally a clean fresh installed OS on an VM with just the
> minimum installed packages.
Thats a pretty good idea. For the first sho
Running "mvn rat:check" generates a RAT (release audit tool) report in
target/rat.txt. The check fails since all the .php files in src/
examples/php and src/examples/resources do not have ASF Source
Header. src/examples/README.LICENSE explains a rationale, however
unless there h
1 - 100 of 126 matches
Mail list logo
