September 2010 - slf4j-dev - mailman3.qos.ch

Fwd: Any plans to update pax-logging to SLF4J >= 1.6
by Heiko Seeberger 14 Sep '10

14 Sep '10

Hi, Is SLF4J API 1.6 backwards compatible? Thanks, Heiko ---------- Forwarded message ---------- From: Toni Menzel <toni(a)okidokiteam.com> Date: Tuesday, September 14, 2010 Subject: Any plans to update pax-logging to SLF4J >= 1.6 To: Heiko Seeberger <heiko.seeberger(a)googlemail.com> Cc: General OPS4J <general(a)lists.ops4j.org> I also stumbled over this (paxlogging on slf4j 1.5) recently, so expect an upgrade if it does not break anything soon'ish.Is the slf4j 1.6 api backwards compatible ? Think so, just asking.. On Tue, Sep 14, 2010 at 11:49 AM, Heiko Seeberger <heiko.seeberger(a)googlemail.com> wrote: Hi, are there any plans to update pax-logging to SLF4J >= 1.6? Thank you! Heiko Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org _______________________________________________ general mailing list general(a)lists.ops4j.org http://lists.ops4j.org/mailman/listinfo/general -- Toni Menzel || http://okidokiteam.com -- Heiko Seeberger Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org

2 1

[Bug 198] New: Source jars should support source code attachment feature of eclipse ide in pde mode
by bugzilla-daemon＠pixie.qos.ch 09 Sep '10

09 Sep '10

http://bugzilla.slf4j.org/show_bug.cgi?id=198 Summary: Source jars should support source code attachment feature of eclipse ide in pde mode Product: SLF4J Version: unspecified Platform: All OS/Version: All Status: NEW Severity: blocker Priority: P3 Component: Core API AssignedTo: slf4j-dev(a)qos.ch ReportedBy: lenkite(a)gmail.com While source attachment works nicely outside of eclipse pde bundles with mvn eclipse:eclipse the same is currently very difficult when using the pde mode of eclipse. In the eclipse pde FAQ that it is necessary to add a header to the Manifest of the source bundle to attach it to the bundle. See http://wiki.eclipse.org/PDE/FAQ#How_do_source_attachments_for_bundles_work For slf4j-api-1.6.1-sources.jar, after adding the following 2 lines to the MANIFEST.MF Bundle-SymbolicName: slf4j.api.source Eclipse-SourceBundle: slf4j.api;version="1.6.1" ,the source was automatically attached to the bundle by eclipse. Request addition of this header by default to all source artifacts created in the maven build. An example of how this was done and fixed for Apache Camel is shown at: https://issues.apache.org/activemq/browse/CAMEL-2734 -- Configure bugmail: http://bugzilla.slf4j.org/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are the assignee for the bug.

1 0

Cross Building SLF4S against Scala versions
by Heiko Seeberger 09 Sep '10

09 Sep '10

Hi, Other than Java, Scala software must use the same Scala version for build and runtime. Because of this binary incompatibility Scala projects must be built against different Scala versions, also known as cross building. There is excellent support for cross building in SBT [1], but ASFAIK not in the Maven Scala plugin. As we will probably see Scala 2.8.1 end of this year and milestones and release candidates even earlier, this is an important issue for SLF4S. How could we deal with that? (a) Switch the whole build from Maven to SBT: Not sure if that makes sense for a +95% Java project (b) Try to only build slf4j-scala with SBT: No clue how to integrate SBT and Maven; also publishing/deploying will be an issue due to different naming strategies for artifacts [2] (c) Keep things as they are, i.e. SLF4S as a separate Scala project I hope someone comes up with a (d) ... Heiko [1] http://code.google.com/p/simple-build-tool/wiki/CrossBuild [2] http://code.google.com/p/simple-build-tool/wiki/LibraryManagement Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org

2 6

Re: [slf4j-dev] Cross Building SLF4S against Scala versions
by Heiko Seeberger 08 Sep '10

08 Sep '10

Cedrik, The approach I demonstrated will not change the project version. In the example below it is 1.0.0-SNAPSHOT and for SLF4J it could be 1.6.2 or 1.7.0 or whatever. Only the artifactID will be "enriched" by suffixing with the Scala version. This approach was introduced by the SBT build tool which is the de-facto standard in the Scala community. There is a nice feature which lets you just declare the plain artifactID and SBT will calculate the enriched one for you depending on what Scala version you build against. Therefore this is definitely the way to go. While it might maybe be possible to tweak SBT to use your approach, that's just not what Scala people are used to. Heiko On Wednesday, September 8, 2010, Cédrik LIME <2010(a)cedrik.fr> wrote: > Don't you want to name your artefact: > scala-profiles-demo-1.0-<scala_version>.jar > ? That way, maven users simply need to use the <classifier> tag in their pom's <dependency>; no need to change the SLF4J|S <version>! > > Cédrik > > > Le 08/09/2010 08:33, Heiko Seeberger a écrit : > > And here comes the solution: > http://github.com/hseeberger/scala-profiles-demo > > Run Maven twice: > 1. mvn install > 2. mvn -Pscala-2.7.7 install > > You wil get exactly what we need: > ./scala-profiles-demo_2.7.7 > ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT > ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT/maven-metadata-local.xml > ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT/scala-profiles-demo_2.7.7-1.0-SNAPSHOT.jar > ./scala-profiles-demo_2.7.7/1.0-SNAPSHOT/scala-profiles-demo_2.7.7-1.0-SNAPSHOT.pom > ./scala-profiles-demo_2.7.7/maven-metadata-local.xml > ./scala-profiles-demo_2.8.0 > ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT > ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT/maven-metadata-local.xml > ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT/scala-profiles-demo_2.8.0-1.0-SNAPSHOT.jar > ./scala-profiles-demo_2.8.0/1.0-SNAPSHOT/scala-profiles-demo_2.8.0-1.0-SNAPSHOT.pom > ./scala-profiles-demo_2.8.0/maven-metadata-local.xml > > Heiko > > -- Heiko Seeberger Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org

1 0

SLF4J goes Scala
by Heiko Seeberger 07 Sep '10

07 Sep '10

Hi, >From our private conversation: Ceki: Hello Heiko, Thank you for starting the slf4s effort. I am interested in providing logging for the Scala language. Would you be interested to have slf4s ship as part of the slf4j project? Heiko: Definitely yes! Scala support in SLF4J is ways better than "my private" project. Let's make that happen! Ceki: Great. Could we please continue this discussion on the slf4j-dev mailing list? Just post a message saying that you are interested in contributing slf4s to the slf4j project. Here we go ;-) Heiko Company: weiglewilczek.com Blog: heikoseeberger.name Follow me: twitter.com/hseeberger OSGi on Scala: scalamodules.org Lift, the simply functional web framework: liftweb.net Stambecco, highly scalable computing: stambecco.org Akka - Simpler Scalability, Fault-Tolerance, Concurrency & Remoting through Actors: akkasource.org

2 4