You are viewing a plain text version of this content. The canonical link for it is here.
Posted to log4j-dev@logging.apache.org by Christian Grobmeier <gr...@gmail.com> on 2012/05/02 07:29:12 UTC
[VOTE] Release log4j 1.2.17
Hello,
please vote to release log4j 1.2.17.
Artifacts:
http://people.apache.org/builds/logging/repo/log4j/log4j/
Tag:
http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
Website:
http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
Please test carefully as this is my first log4j release.
[] +1, release the artifacts
[] -1, don't release because
The vote will remain open for the usual 72 hours.
Thanks,
Christian
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Ralph Goers <rg...@apache.org>.
As usual, I've been pretty busy at work and haven't had a chance to look at this. I'm going to Phoenix, AZ tomorrow to visit family through next Tuesday so I may not have time to do much between now and then.
Ralph
On May 2, 2012, at 8:39 AM, Gary Gregory <gg...@apache.org> wrote:
> Hi All,
>
> -1, mostly because of the missing bug fixed in the release notes page. Are
> there others? It would be nice to fix everything below but I realize this
> is a maintenance release and we have 2.0 coming which I hope will deal with
> these other issues, if not already done.
>
> http://people.apache.org/builds/logging/repo/log4j/log4j/ does not include
> bin and src zips (or tars if you like that) so I have to download the tag
> to test build.
>
> *Build Issues*
>
> I get these Maven warnings:
>
> [WARNING] Some problems were encountered while building the effective model
> for log4j:log4j:bundle:1.2.17
> [WARNING] 'build.plugins.plugin.version' for
> org.apache.maven.plugins:maven-resources-plugin is missing. @ line 89,
> column
> [WARNING] 'build.plugins.plugin.version' for
> org.apache.maven.plugins:
> maven-site-plugin is missing. @ line 447, column 1=
> 5
>
> I get this Maven error:
>
> [WARNING] An issue has occurred with report
> org.apache.maven.report.projectinfo.DependenciesReport, skip LinkageError
> org.c
> gerManager()Lorg/codehaus/plexus/logging/LoggerManager;, please report an
> issue to Maven dev team.
> java.lang.NoSuchMethodError:
> org.codehaus.plexus.PlexusContainer.getLoggerManager()Lorg/codehaus/plexus/=
> logging/LoggerManag
> at
> org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Depend=
> enciesReport.java:222)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport=
> .java:93)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportD=
> ocumentRenderer.java:228)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defaul=
> tSiteRenderer.java:317)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteR=
> enderer.java:134)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138=
> )
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildP=
> luginManager.java:101)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:=
> 209)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:=
> 153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:=
> 145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Lif=
> ecycleModuleBuilder.java:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Lif=
> ecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Li=
> fecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStart=
> er.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3=
> 9)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp=
> l.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.j=
> ava:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher=
> .java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
>
> I use "mvn clean site" with:
>
> Apache Maven *3.0.4* (r1232337; 2012-01-17 03:44:56-0500)
> Maven home: C:\Java\apache-maven-3.0.4\bin\..
> Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>
> With Maven 2, I cannot build at all, which is fine if it is documented:
>
> [WARNING] Removing: javadoc from forked lifecycle, to prevent recursive
> invocation.
> <snip>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.figure(Lorg/apach=
> e/maven/doxia/sink/SinkEventAttributes;)V
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.AbstractMethodError:
> org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.figure(Lorg/apach=
> e/maven/doxia/sin
> at
> org.apache.maven.plugin.issues.AbstractIssuesReportGenerator.sinkFigure(Abs=
> tractIssuesReportGenerator.java:142)
> at
> org.apache.maven.plugin.issues.AbstractIssuesReportGenerator.sinkShowTypeIc=
> on(AbstractIssuesReportGenerator.java
> at
> org.apache.maven.plugin.changes.ChangesReportGenerator.constructAction(Chan=
> gesReportGenerator.java:233)
> at
> org.apache.maven.plugin.changes.ChangesReportGenerator.constructRelease(Cha=
> ngesReportGenerator.java:538)
> at
> org.apache.maven.plugin.changes.ChangesReportGenerator.constructReleases(Ch=
> angesReportGenerator.java:495)
> at
> org.apache.maven.plugin.changes.ChangesReportGenerator.doGenerateReport(Cha=
> ngesReportGenerator.java:217)
> at
> org.apache.maven.plugin.changes.ChangesMojo.executeReport(ChangesMojo.java:=
> 321)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport=
> .java:190)
> at
> org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport=
> .java:144)
> at
> org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportD=
> ocumentRenderer.java:139)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defaul=
> tSiteRenderer.java:269)
> at
> org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteR=
> enderer.java:101)
> at
> org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
> at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100=
> )
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag=
> er.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif=
> ecycleExecutor.java:694)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl=
> e(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife=
> cycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai=
> lures(DefaultLifecycleExecutor.java:3
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def=
> aultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl=
> eExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3=
> 9)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp=
> l.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at
> org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
>
> I use "mvn clean site" with:
>
> Apache Maven *2.2.1* (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_31
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>
> - The build with M3 works aside from that. The tests pass but they are not
> invoked with "mvn site". This is odd to me because in Commons, the build
> for site calls test. It makes sense to me to fail the site build if the
> test fails. But this build does not include the same reports as Commons and
> looks to be a different beast all together.
>
> - For 2.0 we should have one build, Maven, and dump the Ant build file.
>
> *Site Issues*
>
> - Under "Release 1.2.17 - 2010-06-99", an entry is missing for
> https://issues.apache.org/bugzilla/show_bug.cgi?id=3D52913
>
> - In issue-tracking.html, the first Item should not be an "Overview" that
> we say we use Bugzilla. The most important thing on this page is the link
> to the Log4J Bugzilla page.
> I would just remove the "Overview" section, it adds no value and delays me
> getting to the information I need. If you want to keep it, make the last
> section under a different title.
>
> - In license.html, the only section should be "The Apache Software License,
> Version 2.0", the stuff before it is just boilerplate noise.
>
> - This is odd on the main page of the site, in plain text:
>
> --- Apache log4j=E2=84=A2 --- --- ---
>
> I do not get this when I download the tag and build.
>
> - The Roadmap page has a similar problem (I do not get this when I download
> the tag and build.):
>
> ------ Apache log4j 1.2 Roadmap ------ ------ ------
>
> The road map should mention Log4J 2.0 and where is can be found and the
> state it is in at this time.
>
> - Also (I do not get this when I download the tag and build.):
>
> ------ log4j 1.2 Publications ------ ------ ------
>
> - The Cross-reference Java source code looks weird because it points to
> pages instead of having links in the menu itself. I must be used to the
> Commons website generation! ;)
>
> - For 2.0 I hope we can generate the same kind of reports we do for Commons
> like FindBugs, Clirr, PMD, Changes, and so on.
>
> - For 2.0 I hope we adopt the standard Maven directory layout.
>
> - The main Javadoc page shows some packages without package level
> documentation, which is kinda lame but not a show stopper.
>
> Gary
>
>
> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com> wrote:
> Hello,
>
> please vote to release log4j 1.2.17.
>
> Artifacts:
> http://people.apache.org/builds/logging/repo/log4j/log4j/
>
> Tag:
> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>
> Website:
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>
> Please test carefully as this is my first log4j release.
>
> [] +1, release the artifacts
> [] -1, don't release because
>
>
> The vote will remain open for the usual 72 hours.
>
> Thanks,
> Christian
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
Hello again,
>> -1, mostly because of the missing bug fixed in the release notes page. Are
>> there others?
>
> 50486 is easy. It was "reopened" but I fixed it and now I closed it.
> But:
> https://issues.apache.org/bugzilla/show_bug.cgi?id=49470
> https://issues.apache.org/bugzilla/show_bug.cgi?id=43282
I have removed 43282 it seems not to be complete.
49470 looks like some kind of "release tracker issue". I closed it. We
should not create such issues, but I have left it in the list.
>> http://people.apache.org/builds/logging/repo/log4j/log4j/ does not include
>> bin and src zips (or tars if you like that) so I have to download the tag
>> to test build.
I checked: log4j-1.2.17.zip does have the sourcefiles included. Its
not separated,
but for now I would like to go on. It was so for ages, lets improve it later.
>> I use "mvn clean site" with:
>>
>> Apache Maven *2.2.1* (r801777; 2009-08-06 15:16:01-0400)
>> Java version: 1.6.0_31
>> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
>> Default locale: en_US, platform encoding: Cp1252
>> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
I have pimped the site config. Now its using site 3.1. Hopefully its
better for you now.
>> *Site Issues*
>>
>> - Under "Release 1.2.17 - 2010-06-99", an entry is missing for
>> https://issues.apache.org/bugzilla/show_bug.cgi?id=3D52913
Still not found what you mean.
>> - In issue-tracking.html, the first Item should not be an "Overview" that
>> we say we use Bugzilla. The most important thing on this page is the link
>> to the Log4J Bugzilla page.
>
>> - In license.html, the only section should be "The Apache Software License,
>> Version 2.0", the stuff before it is just boilerplate noise.
Its now standard reporting from maven.
>> - This is odd on the main page of the site, in plain text:
>>
>> --- Apache log4j=E2=84=A2 --- --- ---
Removed
>> - The Cross-reference Java source code looks weird because it points to
>> pages instead of having links in the menu itself. I must be used to the
>> Commons website generation! ;)
Got it! With standard reporting it looks better
I think I will roll out another RC now. The most important stuff
should be fixed.
Cheers
Christian
>> - The main Javadoc page shows some packages without package level
>> documentation, which is kinda lame but not a show stopper.
>
> Agreed. I would like to avoid writing it, instead using the power to
> fix what needs to be fixed and go quickly to l4j2
>
> OK... I will fix what I have marked above.
> Are you willing to help with the new assembly packages or should we
> leave that out for later?
> my goal is to make a release to learn about the release cycle. Then we
> have 2 RMs and the next version should be out quicker.
>
> Cheers
>
>>
>> Gary
>>
>>
>> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com>
>> wrote:
>>>
>>> Hello,
>>>
>>> please vote to release log4j 1.2.17.
>>>
>>> Artifacts:
>>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>>>
>>> Tag:
>>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>>>
>>> Website:
>>>
>>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>>>
>>> Please test carefully as this is my first log4j release.
>>>
>>> [] +1, release the artifacts
>>> [] -1, don't release because
>>>
>>>
>>> The vote will remain open for the usual 72 hours.
>>>
>>> Thanks,
>>> Christian
>>>
>>>
>>>
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> Spring Batch in Action: http://bit.ly/bqpbCK
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [log4j 2] build
Posted by Gary Gregory <gg...@apache.org>.
On Thu, May 3, 2012 at 8:26 AM, Ralph Goers <ra...@dslextreme.com>wrote:
>
> On May 3, 2012, at 4:51 AM, Christian Grobmeier wrote:
>
>
>
> - For 2.0 we should have one build, Maven, and dump the Ant build file.
>
>
> Not sure what 2.0 currently supports, but i think it is only maven.
> For 1.0 I would LOVE if you could help me with cleaning the build. We
> need to maintain it for a while...
> we can vote on dropping ant support for 1.x whih should make things easier.
>
>
> 2.0 uses Maven. I use Maven 3 and am not sure if Maven 2 will work. I
> modeled it after the build for Commons VFS. That doesn't mean it won't
> have its own issues. Doing a release at the ASF is complicated.
>
Good news WRT Maven vs. Ant. Did you dump Ant? Indeed WRT complicated
releases...
>
> - For 2.0 I hope we can generate the same kind of reports we do for Commons
>
> like FindBugs, Clirr, PMD, Changes, and so on.
>
>
> Yes, lets discuss this on another thread. SO far l4j2 and l4j1 are
> totally separated. 2 is a full rewrite.
>
>
> The site generates several reports that can be seen at
> http://people.apache.org/~rgoers/log4j2/
>
> For example, http://people.apache.org/~rgoers/log4j2/project-reports.html
> and
> http://people.apache.org/~rgoers/log4j2/log4j2-core/project-reports.html
>
Minor: the style for tables to sub-par:
http://people.apache.org/~rgoers/log4j2/surefire-report.html is hard to
read.
>
>
> - For 2.0 I hope we adopt the standard Maven directory layout.
>
>
> me to. for 1.x we can try to fix that stuff a little bit. I analysed
> it already, thread is somewher ein the archives.
>
>
> Yes, it uses the standard layout.
>
Great!
>
> You are both free to checkout the source and run the build. If you want to
> add more reports feel free to do so.
>
Already checked out :) I plan on helping after 1.2.17.
Gary
> I will note that on Windows the unit tests have to be run with -server
> set. I plan on adding a profile that does that automatically.
>
> Ralph
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
[log4j 2] build
Posted by Ralph Goers <ra...@dslextreme.com>.
On May 3, 2012, at 4:51 AM, Christian Grobmeier wrote:
>
>
>> - For 2.0 we should have one build, Maven, and dump the Ant build file.
>
> Not sure what 2.0 currently supports, but i think it is only maven.
> For 1.0 I would LOVE if you could help me with cleaning the build. We
> need to maintain it for a while...
> we can vote on dropping ant support for 1.x whih should make things easier.
2.0 uses Maven. I use Maven 3 and am not sure if Maven 2 will work. I modeled it after the build for Commons VFS. That doesn't mean it won't have its own issues. Doing a release at the ASF is complicated.
>
>> - For 2.0 I hope we can generate the same kind of reports we do for Commons
>> like FindBugs, Clirr, PMD, Changes, and so on.
>
> Yes, lets discuss this on another thread. SO far l4j2 and l4j1 are
> totally separated. 2 is a full rewrite.
The site generates several reports that can be seen at http://people.apache.org/~rgoers/log4j2/
For example, http://people.apache.org/~rgoers/log4j2/project-reports.html and http://people.apache.org/~rgoers/log4j2/log4j2-core/project-reports.html
>
>> - For 2.0 I hope we adopt the standard Maven directory layout.
>
> me to. for 1.x we can try to fix that stuff a little bit. I analysed
> it already, thread is somewher ein the archives.
Yes, it uses the standard layout.
You are both free to checkout the source and run the build. If you want to add more reports feel free to do so.I will note that on Windows the unit tests have to be run with -server set. I plan on adding a profile that does that automatically.
Ralph
Re: [VOTE] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
Hello Gary,
thanks for testing! Before I start commenting I want to mention it is
my first release and I don't know how exactly it was done before. Curt
(who did the past releases) did not comment so far.
> -1, mostly because of the missing bug fixed in the release notes page. Are
> there others?
I looked through changes, I am confused.
50486 is easy. It was "reopened" but I fixed it and now I closed it.
But:
https://issues.apache.org/bugzilla/show_bug.cgi?id=49470
https://issues.apache.org/bugzilla/show_bug.cgi?id=43282
I have no clue about. I had the impression everything on the changes
list is fixed, but I was wrong.
We are able to put 1.2.17 out even without these two (?) issues. My
suggestion is to drop it from changes.xml.
Other opinions?
> http://people.apache.org/builds/logging/repo/log4j/log4j/ does not include
> bin and src zips (or tars if you like that) so I have to download the tag
> to test build.
Hm, yes we can really create that.
Before it seems these are the only artifacts we have created for older releases.
> *Build Issues*
Thats the tough part. I can build on mac osx 10.6 (except windows dll)
and Ubuntu (with windows dll).
I use Java 6 and Maven 2. These are the facts. Now I am totally
confused why you get such problems as described.
So far I think M2 is the only supported buildsystem (besides ant,
which i would like to drop).
>
> With Maven 2, I cannot build at all, which is fine if it is documented:
>
> [WARNING] Removing: javadoc from forked lifecycle, to prevent recursive
> invocation.
Thats ok, at least i have this warning but it builds all well.
> <snip>
> [INFO]
> ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.figure(Lorg/apach=
> e/maven/doxia/sink/SinkEventAttributes;)V
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.AbstractMethodError:
> org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.figure(Lorg/apach=
> e/maven/doxia/sin
> at
> org.apache.maven.plugin.issues.AbstractIssuesReportGenerator.sinkFigure(Abs=
> tractIssuesReportGenerator.java:142)
Not a clue on that one.
> I use "mvn clean site" with:
>
> Apache Maven *2.2.1* (r801777; 2009-08-06 15:16:01-0400)
> Java version: 1.6.0_31
> Java home: C:\Program Files\Java\jdk1.6.0_31\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
Same as me except i use osx
> - The build with M3 works aside from that. The tests pass but they are not
> invoked with "mvn site". This is odd to me because in Commons, the build
> for site calls test. It makes sense to me to fail the site build if the
> test fails. But this build does not include the same reports as Commons and
> looks to be a different beast all together.
Actually the build is 100% hell. mvn uses ant, ant uses mvn, all have
a non standard directory layout. And of course, you need to install
some windows layer to build on *nix.
> - For 2.0 we should have one build, Maven, and dump the Ant build file.
Not sure what 2.0 currently supports, but i think it is only maven.
For 1.0 I would LOVE if you could help me with cleaning the build. We
need to maintain it for a while...
we can vote on dropping ant support for 1.x whih should make things easier.
> *Site Issues*
>
> - Under "Release 1.2.17 - 2010-06-99", an entry is missing for
> https://issues.apache.org/bugzilla/show_bug.cgi?id=3D52913
Not sure what you mean?
> - In issue-tracking.html, the first Item should not be an "Overview" that
> we say we use Bugzilla. The most important thing on this page is the link
> to the Log4J Bugzilla page.
> I would just remove the "Overview" section, it adds no value and delays me
> getting to the information I need. If you want to keep it, make the last
> section under a different title.
+1, lets remove it.
> - In license.html, the only section should be "The Apache Software License,
> Version 2.0", the stuff before it is just boilerplate noise.
+1
> - This is odd on the main page of the site, in plain text:
>
> --- Apache log4j=E2=84=A2 --- --- ---
>
> I do not get this when I download the tag and build.
It might be related because we are looking at it from svn. But I think
we can remove these lines,
I don't know what their intention is.
> - The Roadmap page has a similar problem (I do not get this when I download
> the tag and build.):
>
> ------ Apache log4j 1.2 Roadmap ------ ------ ------
>
> The road map should mention Log4J 2.0 and where is can be found and the
> state it is in at this time.
+1
> - Also (I do not get this when I download the tag and build.):
>
> ------ log4j 1.2 Publications ------ ------ ------
>
> - The Cross-reference Java source code looks weird because it points to
> pages instead of having links in the menu itself. I must be used to the
> Commons website generation! ;)
Not sure what you mean
> - For 2.0 I hope we can generate the same kind of reports we do for Commons
> like FindBugs, Clirr, PMD, Changes, and so on.
Yes, lets discuss this on another thread. SO far l4j2 and l4j1 are
totally separated. 2 is a full rewrite.
> - For 2.0 I hope we adopt the standard Maven directory layout.
me to. for 1.x we can try to fix that stuff a little bit. I analysed
it already, thread is somewher ein the archives.
> - The main Javadoc page shows some packages without package level
> documentation, which is kinda lame but not a show stopper.
Agreed. I would like to avoid writing it, instead using the power to
fix what needs to be fixed and go quickly to l4j2
OK... I will fix what I have marked above.
Are you willing to help with the new assembly packages or should we
leave that out for later?
my goal is to make a release to learn about the release cycle. Then we
have 2 RMs and the next version should be out quicker.
Cheers
>
> Gary
>
>
> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>>
>> Hello,
>>
>> please vote to release log4j 1.2.17.
>>
>> Artifacts:
>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>>
>> Website:
>>
>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>>
>> Please test carefully as this is my first log4j release.
>>
>> [] +1, release the artifacts
>> [] -1, don't release because
>>
>>
>> The vote will remain open for the usual 72 hours.
>>
>> Thanks,
>> Christian
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Gary Gregory <gg...@apache.org>.
Hi All,
-1, mostly because of the missing bug fixed in the release notes page. Are
there others? It would be nice to fix everything below but I realize this
is a maintenance release and we have 2.0 coming which I hope will deal with
these other issues, if not already done.
http://people.apache.org/builds/logging/repo/log4j/log4j/ does not include
bin and src zips (or tars if you like that) so I have to download the tag
to test build.
*Build Issues*
I get these Maven warnings:
[WARNING] Some problems were encountered while building the effective model
for log4j:log4j:bundle:1.2.17
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-resources-plugin is missing. @ line 89,
column
[WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:
maven-site-plugin is missing. @ line 447, column 1=
5
I get this Maven error:
[WARNING] An issue has occurred with report
org.apache.maven.report.projectinfo.DependenciesReport, skip LinkageError
org.c
gerManager()Lorg/codehaus/plexus/logging/LoggerManager;, please report an
issue to Maven dev team.
java.lang.NoSuchMethodError:
org.codehaus.plexus.PlexusContainer.getLoggerManager()Lorg/codehaus/plexus/=
logging/LoggerManag
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(Depend=
enciesReport.java:222)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport=
.java:93)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportD=
ocumentRenderer.java:228)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defaul=
tSiteRenderer.java:317)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteR=
enderer.java:134)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:175)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:138=
)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildP=
luginManager.java:101)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:=
209)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:=
153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:=
145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Lif=
ecycleModuleBuilder.java:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(Lif=
ecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(Li=
fecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStart=
er.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3=
9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp=
l.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.j=
ava:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher=
.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
I use "mvn clean site" with:
Apache Maven *3.0.4* (r1232337; 2012-01-17 03:44:56-0500)
Maven home: C:\Java\apache-maven-3.0.4\bin\..
Java version: 1.6.0_31, vendor: Sun Microsystems Inc.
Java home: C:\Program Files\Java\jdk1.6.0_31\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
With Maven 2, I cannot build at all, which is fine if it is documented:
[WARNING] Removing: javadoc from forked lifecycle, to prevent recursive
invocation.
<snip>
[INFO]
------------------------------------------------------------------------
[ERROR] FATAL ERROR
[INFO]
------------------------------------------------------------------------
[INFO]
org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.figure(Lorg/apach=
e/maven/doxia/sink/SinkEventAttributes;)V
[INFO]
------------------------------------------------------------------------
[INFO] Trace
java.lang.AbstractMethodError:
org.apache.maven.doxia.siterenderer.sink.SiteRendererSink.figure(Lorg/apach=
e/maven/doxia/sin
at
org.apache.maven.plugin.issues.AbstractIssuesReportGenerator.sinkFigure(Abs=
tractIssuesReportGenerator.java:142)
at
org.apache.maven.plugin.issues.AbstractIssuesReportGenerator.sinkShowTypeIc=
on(AbstractIssuesReportGenerator.java
at
org.apache.maven.plugin.changes.ChangesReportGenerator.constructAction(Chan=
gesReportGenerator.java:233)
at
org.apache.maven.plugin.changes.ChangesReportGenerator.constructRelease(Cha=
ngesReportGenerator.java:538)
at
org.apache.maven.plugin.changes.ChangesReportGenerator.constructReleases(Ch=
angesReportGenerator.java:495)
at
org.apache.maven.plugin.changes.ChangesReportGenerator.doGenerateReport(Cha=
ngesReportGenerator.java:217)
at
org.apache.maven.plugin.changes.ChangesMojo.executeReport(ChangesMojo.java:=
321)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport=
.java:190)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport=
.java:144)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportD=
ocumentRenderer.java:139)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(Defaul=
tSiteRenderer.java:269)
at
org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteR=
enderer.java:101)
at
org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:133)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:100=
)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag=
er.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif=
ecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl=
e(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife=
cycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai=
lures(DefaultLifecycleExecutor.java:3
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def=
aultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl=
eExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3=
9)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp=
l.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
I use "mvn clean site" with:
Apache Maven *2.2.1* (r801777; 2009-08-06 15:16:01-0400)
Java version: 1.6.0_31
Java home: C:\Program Files\Java\jdk1.6.0_31\jre
Default locale: en_US, platform encoding: Cp1252
OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
- The build with M3 works aside from that. The tests pass but they are not
invoked with "mvn site". This is odd to me because in Commons, the build
for site calls test. It makes sense to me to fail the site build if the
test fails. But this build does not include the same reports as Commons and
looks to be a different beast all together.
- For 2.0 we should have one build, Maven, and dump the Ant build file.
*Site Issues*
- Under "Release 1.2.17 - 2010-06-99", an entry is missing for
https://issues.apache.org/bugzilla/show_bug.cgi?id=3D52913
- In issue-tracking.html, the first Item should not be an "Overview" that
we say we use Bugzilla. The most important thing on this page is the link
to the Log4J Bugzilla page.
I would just remove the "Overview" section, it adds no value and delays me
getting to the information I need. If you want to keep it, make the last
section under a different title.
- In license.html, the only section should be "The Apache Software License,
Version 2.0", the stuff before it is just boilerplate noise.
- This is odd on the main page of the site, in plain text:
--- Apache log4j=E2=84=A2 --- --- ---
I do not get this when I download the tag and build.
- The Roadmap page has a similar problem (I do not get this when I download
the tag and build.):
------ Apache log4j 1.2 Roadmap ------ ------ ------
The road map should mention Log4J 2.0 and where is can be found and the
state it is in at this time.
- Also (I do not get this when I download the tag and build.):
------ log4j 1.2 Publications ------ ------ ------
- The Cross-reference Java source code looks weird because it points to
pages instead of having links in the menu itself. I must be used to the
Commons website generation! ;)
- For 2.0 I hope we can generate the same kind of reports we do for Commons
like FindBugs, Clirr, PMD, Changes, and so on.
- For 2.0 I hope we adopt the standard Maven directory layout.
- The main Javadoc page shows some packages without package level
documentation, which is kinda lame but not a show stopper.
Gary
On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com>wrote:
> Hello,
>
> please vote to release log4j 1.2.17.
>
> Artifacts:
> http://people.apache.org/builds/logging/repo/log4j/log4j/
>
> Tag:
> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>
> Website:
>
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>
> Please test carefully as this is my first log4j release.
>
> [] +1, release the artifacts
> [] -1, don't release because
>
>
> The vote will remain open for the usual 72 hours.
>
> Thanks,
> Christian
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
Re: [VOTE][CANCELLED] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
On Thu, May 3, 2012 at 7:05 PM, Gary Gregory <gg...@apache.org> wrote:
> The build does not work on Windows because it requires "windres", a GNU
> program. Even though I ran the build from a MS Visual Studio command line,
> the build does not apparently know how to build a Windows DLL with the
> standard Windows tools :(
>
> Does anyone know where to get a "safe" windres EXE?
wow, have not heard of that yet.
I use mingw (http://www.mingw.org/) to build. I created a vm
(virtualbox.org) with Ubuntu.
I have another option. Its requiring some effort. log4j has the
companions. We shouldnt we move out the NTEvent Appender to another
companion?
Then we are able to build log4j without platform dependency (or we
should be able)
Cheers
>
> Gary
>
> On Thu, May 3, 2012 at 10:58 AM, Christian Grobmeier <gr...@gmail.com>
> wrote:
>>
>> Hello,
>>
>> due to errors in the release notes (among others), I'll roll a new RC.
>>
>> Cheers
>> Christian
>>
>>
>> ---------- Forwarded message ----------
>> From: Christian Grobmeier <gr...@gmail.com>
>> Date: Wed, May 2, 2012 at 7:29 AM
>> Subject: [VOTE] Release log4j 1.2.17
>> To: Log4J Developers List <lo...@logging.apache.org>
>>
>>
>> Hello,
>>
>> please vote to release log4j 1.2.17.
>>
>> Artifacts:
>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>>
>> Website:
>>
>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>>
>> Please test carefully as this is my first log4j release.
>>
>> [] +1, release the artifacts
>> [] -1, don't release because
>>
>>
>> The vote will remain open for the usual 72 hours.
>>
>> Thanks,
>> Christian
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE][CANCELLED] Release log4j 1.2.17
Posted by Gary Gregory <gg...@apache.org>.
The build does not work on Windows because it requires "windres", a GNU
program. Even though I ran the build from a MS Visual Studio command line,
the build does not apparently know how to build a Windows DLL with the
standard Windows tools :(
Does anyone know where to get a "safe" windres EXE?
Gary
On Thu, May 3, 2012 at 10:58 AM, Christian Grobmeier <gr...@gmail.com>wrote:
> Hello,
>
> due to errors in the release notes (among others), I'll roll a new RC.
>
> Cheers
> Christian
>
>
> ---------- Forwarded message ----------
> From: Christian Grobmeier <gr...@gmail.com>
> Date: Wed, May 2, 2012 at 7:29 AM
> Subject: [VOTE] Release log4j 1.2.17
> To: Log4J Developers List <lo...@logging.apache.org>
>
>
> Hello,
>
> please vote to release log4j 1.2.17.
>
> Artifacts:
> http://people.apache.org/builds/logging/repo/log4j/log4j/
>
> Tag:
> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>
> Website:
>
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>
> Please test carefully as this is my first log4j release.
>
> [] +1, release the artifacts
> [] -1, don't release because
>
>
> The vote will remain open for the usual 72 hours.
>
> Thanks,
> Christian
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
[VOTE][CANCELLED] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
Hello,
due to errors in the release notes (among others), I'll roll a new RC.
Cheers
Christian
---------- Forwarded message ----------
From: Christian Grobmeier <gr...@gmail.com>
Date: Wed, May 2, 2012 at 7:29 AM
Subject: [VOTE] Release log4j 1.2.17
To: Log4J Developers List <lo...@logging.apache.org>
Hello,
please vote to release log4j 1.2.17.
Artifacts:
http://people.apache.org/builds/logging/repo/log4j/log4j/
Tag:
http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
Website:
http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
Please test carefully as this is my first log4j release.
[] +1, release the artifacts
[] -1, don't release because
The vote will remain open for the usual 72 hours.
Thanks,
Christian
--
http://www.grobmeier.de
https://www.timeandbill.de
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
On Wed, May 2, 2012 at 9:34 AM, Ralph Goers <ra...@dslextreme.com> wrote:
> How are you planning on publishing the web site? To p.a.o?
yes... the website. The current process (I followed) is to generate
the website locally and then scp it to localhost into the svn. In
other terms, the website is currently in the trunks svn. Usually we
vote and then it is "svn up"ped.
Of course this is not going to fly when we have svnpubsub (it would be
upped automatically). Therefore we need to tweak the pom.xml to deploy
it to somewhere on people.
Anyway for now this is the process - I would like to revisit it after
the release, now, that I know how it is done.
Cheers
Christian
>
> Ralph
>
> On May 1, 2012, at 10:29 PM, Christian Grobmeier wrote:
>
>> Hello,
>>
>> please vote to release log4j 1.2.17.
>>
>> Artifacts:
>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>>
>> Website:
>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>>
>> Please test carefully as this is my first log4j release.
>>
>> [] +1, release the artifacts
>> [] -1, don't release because
>>
>>
>> The vote will remain open for the usual 72 hours.
>>
>> Thanks,
>> Christian
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Ralph Goers <ra...@dslextreme.com>.
How are you planning on publishing the web site? To p.a.o?
Ralph
On May 1, 2012, at 10:29 PM, Christian Grobmeier wrote:
> Hello,
>
> please vote to release log4j 1.2.17.
>
> Artifacts:
> http://people.apache.org/builds/logging/repo/log4j/log4j/
>
> Tag:
> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>
> Website:
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>
> Please test carefully as this is my first log4j release.
>
> [] +1, release the artifacts
> [] -1, don't release because
>
>
> The vote will remain open for the usual 72 hours.
>
> Thanks,
> Christian
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
>> Can you help with the build? Its tons of to do to fix it. And I really
>> would like to get this memory leak fix out.
>
>
> I'll see if I can get the build running on Windows.
Cool.
> FYI: The next step is for the RM to send a "[VOTE][CANCEL]" email.
Yap, thanks for reminding. I actually contributed to the UsingNexus
guide and served as RM at Commons (compress), so I am not completely
noob :-)
Cheers
>
> Gary
>
>>
>>
>> Cheers
>>
>>
>> >
>> > Gary
>> >
>> >>
>> >> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier
>> >> <gr...@gmail.com>
>> >> wrote:
>> >>>
>> >>> Hello,
>> >>>
>> >>> please vote to release log4j 1.2.17.
>> >>>
>> >>> Artifacts:
>> >>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>> >>>
>> >>> Tag:
>> >>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>> >>>
>> >>> Website:
>> >>>
>> >>>
>> >>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>> >>>
>> >>> Please test carefully as this is my first log4j release.
>> >>>
>> >>> [] +1, release the artifacts
>> >>> [] -1, don't release because
>> >>>
>> >>>
>> >>> The vote will remain open for the usual 72 hours.
>> >>>
>> >>> Thanks,
>> >>> Christian
>> >>>
>> >>>
>> >>>
>> >>> --
>> >>> http://www.grobmeier.de
>> >>> https://www.timeandbill.de
>> >>>
>> >>> ---------------------------------------------------------------------
>> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>> >>>
>> >>
>> >>
>> >>
>> >> --
>> >> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> >> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> >> Spring Batch in Action: http://bit.ly/bqpbCK
>> >> Blog: http://garygregory.wordpress.com
>> >> Home: http://garygregory.com/
>> >> Tweet! http://twitter.com/GaryGregory
>> >
>> >
>> >
>> >
>> > --
>> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> > Spring Batch in Action: http://bit.ly/bqpbCK
>> > Blog: http://garygregory.wordpress.com
>> > Home: http://garygregory.com/
>> > Tweet! http://twitter.com/GaryGregory
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Gary Gregory <gg...@apache.org>.
On Thu, May 3, 2012 at 8:04 AM, Christian Grobmeier <gr...@gmail.com>wrote:
> On Thu, May 3, 2012 at 2:01 PM, Gary Gregory <gg...@apache.org> wrote:
> > There is another problem here which is process.
> >
> > This is based on my experience releasing from Commons:
> >
> > This vote should be to release "1.2.17-RC1" as "1.2.17".
> >
> > Therefore, the tag should be for 1.2.17-RC1 not 1.2.17.
> >
> > The vote email thread should be prefixed with "[VOTE]", for example
> "[VOTE]
> > Release 1.2.17-RC1"
> >
> > The following is for Commons but contains some generic info on process:
> > http://wiki.apache.org/commons/UsingNexus
>
> Yes thats all right.
>
> This is the process so far. Now I would need to to mv the tag to -RC1
> and create a new one by hand.
> Another problem: there is no real staging for the site. I mean... its
> committing everything to svn.
>
> Can you help with the build? Its tons of to do to fix it. And I really
> would like to get this memory leak fix out.
>
I'll see if I can get the build running on Windows.
FYI: The next step is for the RM to send a "[VOTE][CANCEL]" email.
Gary
>
> Cheers
>
>
> >
> > Gary
> >
> >>
> >> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <
> grobmeier@gmail.com>
> >> wrote:
> >>>
> >>> Hello,
> >>>
> >>> please vote to release log4j 1.2.17.
> >>>
> >>> Artifacts:
> >>> http://people.apache.org/builds/logging/repo/log4j/log4j/
> >>>
> >>> Tag:
> >>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
> >>>
> >>> Website:
> >>>
> >>>
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
> >>>
> >>> Please test carefully as this is my first log4j release.
> >>>
> >>> [] +1, release the artifacts
> >>> [] -1, don't release because
> >>>
> >>>
> >>> The vote will remain open for the usual 72 hours.
> >>>
> >>> Thanks,
> >>> Christian
> >>>
> >>>
> >>>
> >>> --
> >>> http://www.grobmeier.de
> >>> https://www.timeandbill.de
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> >>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
> >>>
> >>
> >>
> >>
> >> --
> >> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> >> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> >> Spring Batch in Action: http://bit.ly/bqpbCK
> >> Blog: http://garygregory.wordpress.com
> >> Home: http://garygregory.com/
> >> Tweet! http://twitter.com/GaryGregory
> >
> >
> >
> >
> > --
> > E-Mail: garydgregory@gmail.com | ggregory@apache.org
> > JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> > Spring Batch in Action: http://bit.ly/bqpbCK
> > Blog: http://garygregory.wordpress.com
> > Home: http://garygregory.com/
> > Tweet! http://twitter.com/GaryGregory
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>
Re: [VOTE] Release log4j 1.2.17
Posted by Christian Grobmeier <gr...@gmail.com>.
On Thu, May 3, 2012 at 2:01 PM, Gary Gregory <gg...@apache.org> wrote:
> There is another problem here which is process.
>
> This is based on my experience releasing from Commons:
>
> This vote should be to release "1.2.17-RC1" as "1.2.17".
>
> Therefore, the tag should be for 1.2.17-RC1 not 1.2.17.
>
> The vote email thread should be prefixed with "[VOTE]", for example "[VOTE]
> Release 1.2.17-RC1"
>
> The following is for Commons but contains some generic info on process:
> http://wiki.apache.org/commons/UsingNexus
Yes thats all right.
This is the process so far. Now I would need to to mv the tag to -RC1
and create a new one by hand.
Another problem: there is no real staging for the site. I mean... its
committing everything to svn.
Can you help with the build? Its tons of to do to fix it. And I really
would like to get this memory leak fix out.
Cheers
>
> Gary
>
>>
>> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com>
>> wrote:
>>>
>>> Hello,
>>>
>>> please vote to release log4j 1.2.17.
>>>
>>> Artifacts:
>>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>>>
>>> Tag:
>>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>>>
>>> Website:
>>>
>>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>>>
>>> Please test carefully as this is my first log4j release.
>>>
>>> [] +1, release the artifacts
>>> [] -1, don't release because
>>>
>>>
>>> The vote will remain open for the usual 72 hours.
>>>
>>> Thanks,
>>> Christian
>>>
>>>
>>>
>>> --
>>> http://www.grobmeier.de
>>> https://www.timeandbill.de
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>>
>>
>>
>>
>> --
>> E-Mail: garydgregory@gmail.com | ggregory@apache.org
>> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
>> Spring Batch in Action: http://bit.ly/bqpbCK
>> Blog: http://garygregory.wordpress.com
>> Home: http://garygregory.com/
>> Tweet! http://twitter.com/GaryGregory
>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
--
http://www.grobmeier.de
https://www.timeandbill.de
---------------------------------------------------------------------
To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
For additional commands, e-mail: log4j-dev-help@logging.apache.org
Re: [VOTE] Release log4j 1.2.17
Posted by Ralph Goers <ra...@dslextreme.com>.
Gary,
I never did that for Commons VFS as I found it to be a PITA when using Nexus. I would just keep performing the release over and over until it was right. I know the builds I've done with the release plugin didn't support an RC tag but with the maven artifacts not labeled as an RC - or if they did I have no idea how.
Ralph
On May 3, 2012, at 5:01 AM, Gary Gregory wrote:
> There is another problem here which is process.
>
> This is based on my experience releasing from Commons:
>
> This vote should be to release "1.2.17-RC1" as "1.2.17".
>
> Therefore, the tag should be for 1.2.17-RC1 not 1.2.17.
>
> The vote email thread should be prefixed with "[VOTE]", for example "[VOTE] Release 1.2.17-RC1"
>
> The following is for Commons but contains some generic info on process: http://wiki.apache.org/commons/UsingNexus
>
> Gary
>
>
> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com> wrote:
> Hello,
>
> please vote to release log4j 1.2.17.
>
> Artifacts:
> http://people.apache.org/builds/logging/repo/log4j/log4j/
>
> Tag:
> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>
> Website:
> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>
> Please test carefully as this is my first log4j release.
>
> [] +1, release the artifacts
> [] -1, don't release because
>
>
> The vote will remain open for the usual 72 hours.
>
> Thanks,
> Christian
>
>
>
> --
> http://www.grobmeier.de
> https://www.timeandbill.de
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
> Spring Batch in Action: http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
Re: [VOTE] Release log4j 1.2.17
Posted by Gary Gregory <gg...@apache.org>.
There is another problem here which is process.
This is based on my experience releasing from Commons:
This vote should be to release "1.2.17-RC1" as "1.2.17".
Therefore, the tag should be for 1.2.17-RC1 not 1.2.17.
The vote email thread should be prefixed with "[VOTE]", for example "[VOTE]
Release 1.2.17-RC1"
The following is for Commons but contains some generic info on process:
http://wiki.apache.org/commons/UsingNexus
Gary
> On Wed, May 2, 2012 at 1:29 AM, Christian Grobmeier <gr...@gmail.com>wrote:
>
>> Hello,
>>
>> please vote to release log4j 1.2.17.
>>
>> Artifacts:
>> http://people.apache.org/builds/logging/repo/log4j/log4j/
>>
>> Tag:
>> http://svn.apache.org/repos/asf/logging/log4j/tags/log4j-1.2.17/
>>
>> Website:
>>
>> http://svn.apache.org/repos/asf/logging/site/trunk/docs/log4j/1.2/index.html
>>
>> Please test carefully as this is my first log4j release.
>>
>> [] +1, release the artifacts
>> [] -1, don't release because
>>
>>
>> The vote will remain open for the usual 72 hours.
>>
>> Thanks,
>> Christian
>>
>>
>>
>> --
>> http://www.grobmeier.de
>> https://www.timeandbill.de
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: log4j-dev-unsubscribe@logging.apache.org
>> For additional commands, e-mail: log4j-dev-help@logging.apache.org
>>
>>
>
>
> --
> E-Mail: garydgregory@gmail.com | ggregory@apache.org
> JUnit in Action, 2nd Ed: <http://goog_1249600977>http://bit.ly/ECvg0
> Spring Batch in Action: <http://s.apache.org/HOq>http://bit.ly/bqpbCK
> Blog: http://garygregory.wordpress.com
> Home: http://garygregory.com/
> Tweet! http://twitter.com/GaryGregory
>
--
E-Mail: garydgregory@gmail.com | ggregory@apache.org
JUnit in Action, 2nd Ed: http://bit.ly/ECvg0
Spring Batch in Action: http://bit.ly/bqpbCK
Blog: http://garygregory.wordpress.com
Home: http://garygregory.com/
Tweet! http://twitter.com/GaryGregory <http://twitter.com/GaryGregory>