DO NOT REPLY [Bug 34945] ThrowableInformation has dubious Stack Trace extraction feature
https://issues.apache.org/bugzilla/show_bug.cgi?id=34945 --- Comment #4 from Prasad Gawande gawandepra...@gmail.com 2011-08-25 06:45:12 UTC --- Created attachment 27433 -- https://issues.apache.org/bugzilla/attachment.cgi?id=27433 SimpleERRdcProject -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[GUMP@vmgump]: Project logging-log4j-receivers (in module logging-log4j-receivers) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project logging-log4j-receivers has an issue affecting its community integration. This issue affects 3 projects, and has been outstanding for 17 runs. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - logging-log4j-chainsaw : Chainsaw log viewer - logging-log4j-receivers : Back-port of log4j 1.3 receivers for use with log4j 1.2. - logging-log4j-receivers-test : Back-port of log4j 1.3 receivers for use with log4j 1.2. Full details are available at: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/gump_work/build_logging-log4j-receivers_logging-log4j-receivers.html Work Name: build_logging-log4j-receivers_logging-log4j-receivers (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dproject.version=25082011 jar [Working Directory: /srv/gump/public/workspace/logging-log4j-receivers] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-25082011.jar:/srv/gump/public/workspace/logging-log4j-component/target/apache-log4j-component-25082011.jar:/srv/gump/public/workspace/logging-log4j-extras/target/apache-log4j-extras-25082011.jar:/srv/gump/packages/jms1.1/lib/jms.jar:/srv/gump/packages/apache-attic/oro-2.0.8.jar - Buildfile: /srv/gump/public/workspace/logging-log4j-receivers/build.xml BUILD FAILED Target jar does not exist in the project null. Total time: 0 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/rss.xml - Atom: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 05000625082011, vmgump.apache.org:vmgump:05000625082011 Gump E-mail Identifier (unique within run) #8. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Removing the ant junit testing
I have commented it, because it does not build on my machine (mac). But we can leave that in the pom. Any comments to the rest of my message? On Thu, Aug 25, 2011 at 5:22 AM, Curt Arnold carn...@apache.org wrote: This following patch would kill building NTEventAppender.dll which has been included in the distribution for the last couple releases (after being missing for several releases). There were several emphatic requests prior to the previous releases to also provide an x64 version of NTEventAppender which the current build process also provides. On Aug 19, 2011, at 6:14 AM, Christian Grobmeier wrote: We have discussed recently the sense of antrun doing junit test, bypassing mvn. Curt mentioned that this probably has been done because of several cleanup actions which were not made by mvn. I have attached patch below, which comments the antrun for junit. After this patch i could run mvn test and did not see a difference to the previous solution. 237 tests were running, without failures. After running it, I had one folder generated by the testing (output). With antrun I had two which were not cleaned up for some reasons, output and classes. So it looks as it would work without ant. My suggestion is as follows: - apply the patch below - mv tests/src/java to src/test/java (standard by mvn) - mv tests/resources to src/test/resources (standard by mvn) - move the test/input + witness files to src/test/resources - change the test cases to generate their output into target/test-work/output - remove the junit portions from ant buildfiles After that we should have an easier testing process. Any objections why we should not do that? The only reason I could imagine is that 1.2.x series is going to die soon. I am not sure if we should do the effort. For this question I would love to hear some opions Cheers Christian ### Eclipse Workspace Patch 1.0 #P log4j-12-trunk Index: pom.xml === --- pom.xml (revision 1159577) +++ pom.xml (working copy) @@ -100,7 +100,7 @@ workingDirectorytests/workingDirectory reportFormatplain/reportFormat forkModepertest/forkMode - skiptrue/skip + skipfalse/skip includes includeorg/apache/log4j/LevelTest.java/include includeorg/apache/log4j/PriorityTest.java/include @@ -180,6 +180,7 @@ version1.2/version executions !-- generate NTEventLogAppender.dll -- + !-- execution phaseprocess-classes/phase idntdll/id @@ -197,7 +198,9 @@ goalrun/goal /goals /execution + -- !-- create tests/output prior to test run -- + !-- execution phasetest-compile/phase idmkdir_tests_output/id @@ -239,6 +242,7 @@ goalrun/goal /goals /execution + -- !-- release builds will put SVN tags into the SCM page, this changes it back to trunk -- execution phasesite/phase - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Missing commit messages for rev 1158186 1159577, 1159583
On Thu, Aug 25, 2011 at 5:38 AM, Curt Arnold carn...@apache.org wrote: I didn't see any commit messages for these revisions which I likely means that Christian isn't subscribed to the log4j-dev list using grobme...@apache.org and the commit messages from SVN got bounced by the mailing list. I checked the status on the request for comm...@logging.apache.org and it is still open, I added a request that any configuration that would allow SVN commit messages to get through would be appreciated. I've made an attempt to add grobme...@apache.org to the log4j-dev-allow list which hopefully will should let his messages get through without sending outgoing messages. I have forwarded on of the commits in question before a while manually and then subscribed to the list with my apache email address. Besides these rvs you should have got all the other Two of the commits removed substantial sections of build.xml that are used in the Gump build which caused Gump to start failing to build extras and components as evidenced by the recent nag messages on log4j-dev. Maybe when he returns Stefan might update us on the current capabilities of Gump, but last time I visited it, it had limited abiiity with Maven, so it depended on the Ant build to provide the current nightly builds to the entire universe of code it rebuilds and tests several times a day. I've reverted the changes that removed the targets that Gump configuration depends upon. Hopefully that will eliminate the nag messages and allow Gump to build and test extras and component (and anything that depends on them again). Actually Gump does now build again with Java 1.2. I am not sure how that works without an error, because all of the components do use 1.4 features. Before reverting the commit, I would have tried to change the Gump configuration. Because it fully supports Apache Ant, Apache Maven (1.x to 3.x) (gump.apache.org) For the time being I would have preferred to leave Gump in an error state and modify the Gump config instead or disable Gump for the mini projects. It would be good to isolate whitespace changes from non-whitespace changes (or avoid whitespace only changes). One of the changes to build.xml had a decent number of indent changes (likely due to a code reformatter) in addition to some non-cosmetic changes. Reformatting the code, particularly in conjunction with actual changes, complicates code reviews in commit messages or ViewSVN. If you must reformat, reformat first, commit then make changes. http://svn.apache.org/viewvc?view=revisionrevision=1159577 http://svn.apache.org/viewvc?view=revisionrevision=1159583 http://svn.apache.org/viewvc?view=revisionrevision=1158186 Will do the next time. I didn't want to change the formatting, but it was so heavy to read, that I decided to do everything at once. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org -- http://www.grobmeier.de - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
DO NOT REPLY [Bug 51721] New: Log4j snapshots should be in the Apache Snapshot Repository
https://issues.apache.org/bugzilla/show_bug.cgi?id=51721 Bug #: 51721 Summary: Log4j snapshots should be in the Apache Snapshot Repository Product: Log4j Version: unspecified Platform: All OS/Version: All Status: NEW Severity: normal Priority: P2 Component: Other AssignedTo: log4j-dev@logging.apache.org ReportedBy: julien.p...@free.fr Classification: Unclassified Hi, I am currently having an OSGI bundle related problem with the latest release version of log4j (1.2.16) which is fixed in the latest snapshot of log4j (1.2.17-SNAPSHOT). However, this snapshot is not in the central Maven repository (because it is a snapshot). It is also less understandably not in the Apache Snapshot Repository: http://repository.apache.org/snapshots/ Possible fixes for me would be: -either to release 1.2.17 and deploy it to central, -deploy 1.2.17-SNAPSHOT to the above Apache Snapshot Repository. For now, I am stuck with using a custom compiled and deployed 1.2.17-SNAPSHOT in the 3rd party self-hosted repository of my Repository Manager. Yours sincerely, Julien -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[GUMP@vmgump]: Project logging-log4j-receivers (in module logging-log4j-receivers) failed
To whom it may engage... This is an automated request, but not an unsolicited one. For more information please visit http://gump.apache.org/nagged.html, and/or contact the folk at gene...@gump.apache.org. Project logging-log4j-receivers has an issue affecting its community integration. This issue affects 3 projects. The current state of this project is 'Failed', with reason 'Build Failed'. For reference only, the following projects are affected by this: - logging-log4j-chainsaw : Chainsaw log viewer - logging-log4j-receivers : Back-port of log4j 1.3 receivers for use with log4j 1.2. - logging-log4j-receivers-test : Back-port of log4j 1.3 receivers for use with log4j 1.2. Full details are available at: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/index.html That said, some information snippets are provided here. The following annotations (debug/informational/warning/error messages) were provided: -INFO- Failed with reason build failed -INFO- Failed to extract fallback artifacts from Gump Repository The following work was performed: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/gump_work/build_logging-log4j-receivers_logging-log4j-receivers.html Work Name: build_logging-log4j-receivers_logging-log4j-receivers (Type: Build) Work ended in a state of : Failed Elapsed: Command Line: /usr/lib/jvm/java-6-openjdk/bin/java -Djava.awt.headless=true -Dbuild.sysclasspath=only org.apache.tools.ant.Main -Dgump.merge=/srv/gump/public/gump/work/merge.xml -Dproject.version=25082011 jar [Working Directory: /srv/gump/public/workspace/logging-log4j-receivers] CLASSPATH: /usr/lib/jvm/java-6-openjdk/lib/tools.jar:/srv/gump/public/workspace/ant/dist/lib/ant.jar:/srv/gump/public/workspace/ant/dist/lib/ant-launcher.jar:/srv/gump/public/workspace/ant/dist/lib/ant-jmf.jar:/srv/gump/public/workspace/ant/dist/lib/ant-junit.jar:/srv/gump/public/workspace/ant/dist/lib/ant-swing.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-resolver.jar:/srv/gump/public/workspace/ant/dist/lib/ant-apache-xalan2.jar:/srv/gump/public/workspace/xml-commons/java/build/resolver.jar:/srv/gump/public/workspace/logging-log4j-12/dist/lib/log4j-25082011.jar:/srv/gump/public/workspace/logging-log4j-component/target/apache-log4j-component-25082011.jar:/srv/gump/public/workspace/logging-log4j-extras/target/apache-log4j-extras-25082011.jar:/srv/gump/packages/jms1.1/lib/jms.jar:/srv/gump/packages/apache-attic/oro-2.0.8.jar - Buildfile: /srv/gump/public/workspace/logging-log4j-receivers/build.xml BUILD FAILED Target jar does not exist in the project null. Total time: 0 seconds - To subscribe to this information via syndicated feeds: - RSS: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/rss.xml - Atom: http://vmgump.apache.org/gump/public/logging-log4j-receivers/logging-log4j-receivers/atom.xml == Gump Tracking Only === Produced by Apache Gump(TM) version 2.3. Gump Run 05001825082011, vmgump.apache.org:vmgump:05001825082011 Gump E-mail Identifier (unique within run) #1. -- Apache Gump http://gump.apache.org/ [Instance: vmgump] - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
[ANNOUNCEMENT} New comm...@logging.apache.org mailing list
The comm...@logging.apache.org mailing list is now accepting subscription requests at commits-subscr...@logging.apache.org. The current plan is to redirect all SVN commit messages from logging services projects to comm...@logging.apache.org and to discontinue any commit message logging to log4j-dev and the other mailing lists Sunday evening unless there are objections. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
DO NOT REPLY [Bug 34945] ThrowableInformation has dubious Stack Trace extraction feature
https://issues.apache.org/bugzilla/show_bug.cgi?id=34945 Curt Arnold carn...@apache.org changed: What|Removed |Added Status|NEEDINFO|RESOLVED Resolution||WONTFIX --- Comment #5 from Curt Arnold carn...@apache.org 2011-08-26 05:02:02 UTC --- Prasad could you file this as new bug. The original bug report was against the long abandoned log4j 1.3 branch and the current log4j 1.2.x code is quite a bit different and I'm not sure how you could be sure that you are reporting on the same bug as the original poster. I took a quick look inside the zip and there is a lot of code, but no apparent explanation of what you observed and how it differed from what you expected. It would be good to know those things, that you are observing the problem log4j 1.2.16 and any platform information (app server, OS, java version) that would allow us to reproduce the problem. Marking the original bug as WONTFIX since it relates to the abandoned log4j 1.3 branch. -- Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email --- You are receiving this mail because: --- You are the assignee for the bug. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Missing commit messages for rev 1158186 1159577, 1159583
We've supported both building with either Ant or Maven for many years, though releases have been exclusively Maven for a while. The Ant build and test scripts were necessary to build and test on JDK 1.3 and earlier (which also required an earlier version of Ant, though I forget the specific version), but that is obviously less of a concern than it was long time ago. As far as I can tell, the Ant build works and isn't hurting anyone, so I'd be inclined to keep it around at least until there is a some discussion to remove Ant as a build environment. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
Re: Missing commit messages for rev 1158186 1159577, 1159583
On Aug 26, 2011, at 12:12 AM, Curt Arnold wrote: We've supported both building with either Ant or Maven for many years, though releases have been exclusively Maven for a while. The Ant build and test scripts were necessary to build and test on JDK 1.3 and earlier (which also required an earlier version of Ant, though I forget the specific version), but that is obviously less of a concern than it was long time ago. As far as I can tell, the Ant build works and isn't hurting anyone, so I'd be inclined to keep it around at least until there is a some discussion to remove Ant as a build environment. There were also a couple of other scenarios where it was handy to have the Ant scripts around. The ant scripts allowed you to test without rebuilding which was handy to check that the jar that you built on the release platform worked on other platforms. I'm not sure how easily that can be accomplished with Maven as I think it is going to want to rebuild the jar first. Also, I recall some JVM (JRocket, Geronimo, gcj) not running Maven, but able to build and test with Ant. - To unsubscribe, e-mail: log4j-dev-unsubscr...@logging.apache.org For additional commands, e-mail: log4j-dev-h...@logging.apache.org
