Just got home and ran the tests on Win7, and they pass just fine.
Basically, if you're not too concerned with the XP failures, I have no
reason to hold back the release.
The usual checks: site, checksums, sigs all look good.
So here's my +1
Regards,
Ivan
On 8 May 2013 18:07, Christian Grobmeie
Log4php is using a google analytics account to monitor stats. If you wish,
we can add log4j to the account, but you need to add a JS code snippet to
your site template. Also, you should add a "privacy policy" page and link
to it in the footer or somewhere similiar. Example:
http://logging.apache.or
On 28 January 2013 16:14, Ralph Goers wrote:
> Please test and cast your votes.
> [] +1, release the artifacts
> [] -1, don't release because…
+1
Sigs good, hashes good, tests pass, site builds and looks good.
Regards,
Ivan
-
On 28 January 2013 02:04, Ralph Goers wrote:
> Please update and try again. I was able to get it to fail consistently on a
> Windows machine my wife has. I converted the tests to use the memory channel
> instead of the file channel and they now are working consistently for me.
I ran tests 3 t
On 27 January 2013 07:34, Ralph Goers wrote:
> This is interesting. Can you a) provide me with information on your
> hardware? The elapsed times below are even slower than my VM. Also, can
> you rerun it and modify embedded.xml and change status="warn" to
> status="debug" and change the root l
On 27 January 2013 10:16, Ivan Habunek wrote:
> I ran tests and got it to succeed once:
> http://pastebin.com/raw.php?i=2dK6bHCq
>
> And fail once:
> http://pastebin.com/raw.php?i=tXC2g4rU
Just to note, both runs were using the same version of Java
On 27 January 2013 07:34, Ralph Goers wrote:
> This is interesting. Can you a) provide me with information on your
> hardware? The elapsed times below are even slower than my VM. Also, can
> you rerun it and modify embedded.xml and change status="warn" to
> status="debug" and change the root l
On 24 January 2013 02:15, Ralph Goers wrote:
> After testing for quite a bit it appears that Flume 1.3.1 is not terminating
> some threads during shutdown and they are causing the checkpoint files to not
> be able to be deleted. I reverted to Flume 1.2.0 and the tests pass again
> for me on Wi
On 20 January 2013 22:53, Ralph Goers wrote:
>
> This is a vote to release Log4j 2.0-beta4, the sixth release of Log4j 2.0.
>
> Please test and cast your votes.
> [] +1, release the artifacts
> [] -1, don't release because…
>
Sigs and checksums are good. Site looks much nicer than before (if I
do
I think you guys should just move to git and be done with it. ;)
Ivan
On 6 December 2012 15:56, Christian Grobmeier wrote:
> Yes... and site must be rebuild.
> Thanks Paul
>
>
> On Thu, Dec 6, 2012 at 3:54 PM, Paul Benedict wrote:
>>
>> Don't forget to update any SVN URLs in the POMs.
>>
>> On
On 20 November 2012 16:09, Ralph Goers wrote:
> The only problem with that is that the pdf is generated from the same files
> as the web pages. Unfortunately, the pdf generator doesn't seem to support
> sub-navigation and I believe it makes a chapter out of every item. See
> pdf.xml.
>
> I wou
On 18 November 2012 15:24, Ralph Goers wrote:
> I was going to mention the child projects because at first I didn't notice
> you had put the project name in the page heading. Once I saw that I thought
> what you have is ok except for the missing user's guide.
I have reverted the change, so the
On 18 November 2012 01:06, Ralph Goers wrote:
> After building the site I only have one issue. Only the parent site has the
> user's guide. I would prefer that the guide be available no matter where you
> are in the site.
Oh, I was trying that out, actually didn't mean to commit that before
dis
On 17 November 2012 23:14, Olivier Lamy wrote:
> You must probably use "version named" files (ie bootstrap-2.1.0.js
> rather bootstrap.js same for css) to prevent issues with caching.
Oh, haven't thought of that. I'm not really a web person, although I
seem to be fixing a lot of webs these days.
On 17 November 2012 19:13, Gary Gregory wrote:
> Can we have a wee bit of developer docs someplace that talks about why we
> have our own copy of Bootstrap and JQuery instead of referring to them on
> the interwebs?
Well, I guess you could pull jquery from google [1], but I don't know
of any site
On 16 November 2012 20:52, Ralph Goers wrote:
> If we can release at any time I am OK with committing to trunk. If the web
> site generation will be broken in svn then please use a branch.
I have committed the initial changes. The site builds fine on my
machine (both the main one and component
On 16 November 2012 20:52, Ralph Goers wrote:
> If we can release at any time I am OK with committing to trunk. If the web
> site generation will be broken in svn then please use a branch.
OK, cool. I'll test before committing, and let you know before making
any bigger changes.
Regards,
Ivan
OK, do you want me to work in a branch and let you merge it to trunk,
or should I just commit to trunk once I get the permissions?
Regards.
Ivan
On 15 November 2012 19:39, Christian Grobmeier wrote:
> Thats pretty nice! good work!
>
> On Thu, Nov 15, 2012 at 11:00 AM, Ivan Habun
It's me again, bitching about the site, but also trying to be productive.
This is my one hour effort to apply a custom skin similar to the one
used on log4php:
http://bezdomni.net/log4j2
I think it's a big improvement. I left in the logos, like you wanted
last time we talked, just made them sligh
On 11 November 2012 20:05, Ralph Goers wrote:
> This is a vote to release Log4j 2.0-beta3, the fifth release of Log4j 2.0.
>
> Please test and cast your votes.
> [] +1, release the artifacts
> [] -1, don't release because…
I have reviewed the usual suspects (sigs, hashes, site, test),
everything
On 7 October 2012 21:46, Ralph Goers wrote:
> This is a vote to release Log4j 2.0-beta2, the fourth release of Log4j 2.0.
The remarks I made regarding the web site last time still stand.
However, this is not critical.
So sorry I didn't have the time to try and finish work on the web. I'm
busy cr
On 26 September 2012 13:39, Gary Gregory wrote:
> Incorrect!
I stand corrected. Still, it's probably not wise to have automatic XSD
validation before configuration because of performance issues. But it
would be nice to have a method which users can call and validate their
XML configuration files
On 26 September 2012 08:12, Gary Gregory wrote:
> Furthermore, if we do XML, we should deliver an XML Schema.
Having a schema is always good. But if you're tempted to do automatic
validation of config files using the schema, I suggest you don't.
I implemented automatic XSD validation in log4php
On 21 September 2012 21:50, Ralph Goers wrote:
> The only thing I would suggest is, like is done with the API, add the
> "chapter" to the beginning of each section, although I'm not really sure why
> I like that since it is obvious what chapter you are in from the sidebar.
What do you think abo
in from the sidebar.
>
> Ralph
>
> On Sep 21, 2012, at 12:21 PM, Christian Grobmeier wrote:
>
>> On Fri, Sep 21, 2012 at 9:16 PM, Ivan Habunek wrote:
>>> Ralph,
>>>
>>> How would you feel about breaking up the really long pages, e.g.
>
On 21 September 2012 21:21, Christian Grobmeier wrote:
> I see, it is always good to have a web dev in team.
> Personally I like this very much.
I'm not a web dev. Please. I'm just marginally more perceptive than
the average developer when it comes to web design. :)
> PS: as you may have noticed
Ralph,
How would you feel about breaking up the really long pages, e.g.
configuration, into smaller ones?
I've done a quick demo of how that would look (note that I've only
done configuration, not others).
http://bezdomni.net/log4j2/manual/configuration/index.html
It may require a little bit of
On 21 September 2012 21:00, Christian Grobmeier wrote:
>> Maybe it's time to try git-svn.
>
> Its fine with git-svn... if you need a starter:
> http://wiki.apache.org/logging/UsingGitWithLogging
>
> Cheers!
Thanks, just what I needed. :)
Ivan
On 21 September 2012 00:37, Ralph Goers wrote:
> I do like that the text in the sidebar doesn't seem to wrap like it does with
> the fluido skin. I'm not sure if that is just because it is wider or if it is
> wider to accommodate the text.
>
> Can you modify it to incorporate the header?
I'll g
Hi Ralph & co,
Since you mentioned you had site design issues, I tried applying the
log4php template I created to log4j2 site. Seems to work pretty well.
Check out this quick demo, especially the cool vertically fixed sidebar :D
http://bezdomni.net/log4j2/
If you're interested, I could adapt the
On 20 September 2012 22:22, Olivier Lamy wrote:
> Try:
> true
>
> See
> http://maven.apache.org/plugins/maven-changes-plugin/jira-report-mojo.html#useJql
Thanks, that was it. They could have made that the default option though. :)
Ralph, attached is a patch for your pom.xml. I bumped the versio
Well, concerning the JIRA changelog issue: it's not you, it's JIRA. I
suppose it has something to do with the recent upgrade. This is from
the log when running mvn site:
[INFO] Downloading from JIRA at:
http://issues.apache.org/jira/secure/IssueNavigator.jspa?view=rss&pid=12310790&statusIds=5&stat
32 matches
Mail list logo
