information into
the build for the sake of reproducibility. The timestamp is not the only
obstacle for reproducibility is it? Anyway, and if I may say so, the
idea of a fixed timestamp feels wrong.
Best regards,
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
Hi Hervé,
In my opinion, the value of should be
part of the pom.xml file and thus visible after the build. Otherwise,
how can the build be reproducible?
Or is the idea to have a *fixed* *default* timestamp for all builds?
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https
+1 (non binding)
The preceding discussion was quite insightful and informative.
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
On 2/28/2024 8:30 AM, Benjamin Marwell wrote:
> Hi Maven Devs/Users/Committers and PMC members!
>
> Afte
a version can be any Java version and only depends on
the producer of the artifact (the owner of the artifact). Obviously,
this Java version needs to be equal or higher than the "release"
version, but that is it.
Claiming that if the release version is 8, the Java version must also b
Hello Bernd,
I was unaware of the capabilities of the release flag. Thank you for
explaining.
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
On 2/25/2024 1:37 AM, Bernd Eckenfels wrote:
> It has been mentioned before, but just to add, since
Hi Tibor,
Your analysis makes sense. As SimpleLogger acts as an appender as found
in log4j/logback backends, SimpleLogger should cater for concurrent
access with some sort of synchronization. It currently does not.
Please create a jira issue for this problem.
Best regards,
--
Ceki Gülcü
On
ponse.
--
Ceki
On 3/24/2017 11:45, Robert Scholte wrote:
Hi Ceki,
the compilation-part isn't the real issue (it is acutally the easy
part), but e.g. the testing-part is.
You must ensure that surefire is also executed at least twice: once for
pre-java9 and for java9.
And what to do with oth
> target/classes/META-INF/versions/9
src/test/java-9/ -> target/test-classes/META-INF/versions/9
Thus, I would need to change little in my pom.xml files to support
MR-jars. Most of the leg work would be done by the compiler plug-in
and Maven conventions.
Comments?
--
Ceki
[1] https://githu
that SimpleLogger prints to the latest value
of System.out.
Please let me know if this may be an issue for you.
Best regards,
--
Ceki
[1] http://jira.qos.ch/browse/SLF4J-389
[2] https://github.com/qos-ch/slf4j/commit/69be5f7f9875
FYI, in the next version of logback, i.e. 2.0, we will be using JDK 1.6.
However, the logback 1.1.x series will continue to be based on JDK 1.5.
On 16.07.2013 07:06, Stephen Connolly wrote:
So what I am hearing is that until we bump core to require JDK6 (or 7) then
logback is the only runner
Apache Maven
http://twitter.com/jvanzyl
-
We know what we are, but know not what we may be.
-- Shakespeare
--
Ceki
65% of statistics are made up on the spot
--
slf4j-simple's StaticLoggerBinder) and remove temporary
reflection workaround
----
--
Ceki
65% of statistics are made up on the spot
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-m
On 17.03.2013 00:47, Jason van Zyl wrote:
If that's the case Ceki might be able to add the clearing of the logger map to
the reset method.
Ceki, would this be hard to change?
I just added a reset method to SimpleLoggerFactory. See
https://github.com/qos-ch/slf4j/commit/6dd3a60ee77a5
On 11.12.2012 21:28, Mark Struberg wrote:
> Folks, don't you see it? we cannot use logback as this is a
> LocationAwareLogger and would break all projects which use slf4j < 1.6
> and older. Please go back to the original mail from 4 month where
> Ceki himself explained it
l (which they
very likely want), then they need to have a compile scope dependency to
slf4j AND an impl.
So true. Every plugin would want to be compatible with Maven 3.1 as well
as older versions. As such, I withdraw by earlier "worse-is-better"
logging policy.
/Anders
--
Ceki
6
On 07.12.2012 18:32, Jason van Zyl wrote:
Kristian,
> I'm going to look at problem with the logging while embedding and
> Hervé wants to look at the SLF4J isolation.
>
> From what I understand in talking to Ceki, for each classloader SLF4J
> can be initialized so it a
is already loaded. Ceki might want to comment on
> how that works. If two SLF4J "systems" can run in the same JVM it may
> work. For the non-SLF4J case it's not using SLF4J, obviously, so there
> is no need to block it.
SLF4J uses an extremely simple/primitive binding (aka
emented right now.
Very nicely put.
/Anders
--
Ceki
65% of statistics are made up on the spot
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
On 04.12.2012 19:18, Jason van Zyl wrote:
> I've been talking to Ceki about configuration in SLF4J as there is
> really no way to change the log level without assuming an
> implementation. If that's the way then for embedding the user can
> change the SLF4J implementatio
that SLF4J is bound to Logback. If
not, the code should not attempt to configure logback. Basically,
Sonar should add a few lines of defensive code.
My 2c.
--
Ceki
65% of statistics are made up on the spot
-
To unsubscribe, e
On 12.10.2012 00:01, Jason van Zyl wrote:
> Ceki made some sample plugins and we'll post something tomorrow about
> some options for integration. Basically Merged vs Mixed: do we want to
> funnel everything into the the core logging backend, or let the plugin
> completely dec
Hello all,
I've created a trivial plugin which uses slf4j for logging:
https://github.com/ceki/foo-plugin
It declares a dependency on slf4j-api and slf4j-jdk14
Here are my observations:
1) when running with maven 3.0.3 the slf4j declaration is honored,
i.e. logging goes through jul (
On 11.10.2012 12:43, Mark Struberg wrote:
> ceki, really, this is perfect example why no container uses
> commons-logging anymore. Do you like to repeat these errors?
>
> I reiterate: there is a workaround by isolating this in
> ClassWorlds. It is not yet there, but ff we like to
gin imports
org.slf4j.LoggerFactory, the instance of LoggerFactory will be bound
to JUL.
I think it makes sense to study actual plugins declaring a dependency
on slf4j, instead of imagining problems which may or may not exist.
--
Ceki
6
aring an slf4j dependency and test these plugins with the upcoming
version of maven (the one using slf4j).
[1] http://marc.info/?t=11078097261&r=1&w=2
--
Ceki
65% of statistics are made up on the spot
-
To unsubscribe
ependency on an implementation does not makes sense imo. It follows
that the term "declaring a dependency on slf4j" means a dependency on
both slf4j-api as well as a binding, aka implementation.
/Anders
--
Ceki
65% of statistic
On 11.10.2012 08:37, Mark Struberg wrote:
Hi Mark,
Hi Ceki, thanks for the reply!
>> The method signatures of classes in the org.slf4j package such as?
>> Logger, LoggerFactory, Marker, MDC, etc. are the same since 2005.?
>
> No they are not. I did a diff between 1.2 and
nd-user project. We just don't know what a user defined in his
> sections...
>
> If we like to use slf4j as maven logging api and export it in the core
> classloader then we might probably face the following problematic
> spots
>
> 1.) slf4j-api <=1.5 and >=1.6 are not
gt; fundamental problems pretty early on. I'm pretty sure you know exactly
> what I mean. Others can grab the MyFaces, tomcat, OpenWebBeans,
> OpenJPA, ... lists for more info. Most time we either ended up doing
> our own logging facade or used JUL
nted. Something being used in a plugin really shouldn't be
> using those.
Exactly.
> Although Ceki is generally careful not to break compatibility, it has
> happened. For example, you cannot mix applications that use SLF4J
> 1.6.x with code that uses SLF4J 1.5.x. Likewise, L
[
http://jira.codehaus.org/browse/MAVENUPLOAD-685?page=comments#action_56079 ]
Ceki Gulcu commented on MAVENUPLOAD-685:
Carlos,
By the way, I forgot to thank you for kindly uploading the bundle files as
requested.
> Upload request for SL
[
http://jira.codehaus.org/browse/MAVENUPLOAD-685?page=comments#action_56078 ]
Ceki Gulcu commented on MAVENUPLOAD-685:
Hello Carlos,
You mean the urls of the various bundle.jar files? We do not make the bundle
files available independently of
[ http://jira.codehaus.org/browse/MAVENUPLOAD-685?page=all ]
Ceki Gulcu updated MAVENUPLOAD-685:
---
Attachment: slf4j-log4j12-1.0-rc5-bundle.jar
> Upload request for SLF4J 1.0RC5 and NLOG4J 1.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-685?page=all ]
Ceki Gulcu updated MAVENUPLOAD-685:
---
Attachment: slf4j-simple-1.0-rc5-bundle.jar
> Upload request for SLF4J 1.0RC5 and NLOG4J 1.2
[ http://jira.codehaus.org/browse/MAVENUPLOAD-685?page=all ]
Ceki Gulcu updated MAVENUPLOAD-685:
---
Attachment: slf4j-nop-1.0-rc5-bundle.jar
slf4j-log4j13-1.0-rc5-bundle.jar
slf4j-jdk14-1.0-rc5-bundle.jar
> Upload requ
Upload request for SLF4J 1.0RC5 and NLOG4J 1.2.21
--
Key: MAVENUPLOAD-685
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-685
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: jcl104
Update request for NLOG4J 1.2.19
Key: MAVENUPLOAD-622
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-622
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: nlog4j-1.2.19-bundle.jar
--
This message
[ http://jira.codehaus.org/browse/MAVENUPLOAD-621?page=all ]
Ceki Gulcu updated MAVENUPLOAD-621:
---
Attachment: slf4j-simple-1.0-rc3-bundle.jar
> Upload request for SLF4J 1.0-RC3
>
>
> Key: MAV
[ http://jira.codehaus.org/browse/MAVENUPLOAD-621?page=all ]
Ceki Gulcu updated MAVENUPLOAD-621:
---
Attachment: slf4j-nop-1.0-rc3-bundle.jar
slf4j-log4j13-1.0-rc3-bundle.jar
slf4j-log4j12-1.0-rc3-bundle.jar
> Upl
Upload request for SLF4J 1.0-RC3
Key: MAVENUPLOAD-621
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-621
Project: maven-upload-requests
Type: Bug
Reporter: Ceki Gulcu
Attachments: jcl104-over-slf4j-1.0-rc3-bundle.jar,
slf4j
[ http://jira.codehaus.org/browse/MAVENUPLOAD-613?page=all ]
Ceki Gulcu updated MAVENUPLOAD-613:
---
Attachment: slf4j-simple-1.0-rc2-bundle.jar
> Update request for SLF4J 1.0rc2
> ---
>
> Key: MAV
[ http://jira.codehaus.org/browse/MAVENUPLOAD-613?page=all ]
Ceki Gulcu updated MAVENUPLOAD-613:
---
Attachment: slf4j-nop-1.0-rc2-bundle.jar
slf4j-log4j13-1.0-rc2-bundle.jar
slf4j-log4j12-1.0-rc2-bundle.jar
> Upd
Update request for SLF4J 1.0rc2
---
Key: MAVENUPLOAD-613
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-613
Project: maven-upload-requests
Type: Wish
Reporter: Ceki Gulcu
Attachments: jcl104-over-slf4j-1.0-rc2-bundle.jar,
slf4j
[ http://jira.codehaus.org/browse/MAVENUPLOAD-597?page=all ]
Ceki Gulcu updated MAVENUPLOAD-597:
---
Attachment: slf4j-simple-1.0-rc1-bundle.jar
slf4j-nop-1.0-rc1-bundle.jar
slf4j-log4j13-1.0-rc1-bundle.jar
> Upd
Update request for SLF4J 1.0rc1
---
Key: MAVENUPLOAD-597
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-597
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: jcl104-over-slf4j-1.0-rc1-bundle.jar,
slf4j
[ http://jira.codehaus.org/browse/MAVENUPLOAD-555?page=all ]
Ceki Gulcu updated MAVENUPLOAD-555:
---
Attachment: nlog4j-1.2.18-bundle.jar
> Upload request for NLOG4J 1.2.18 and SLF4J 1.0-be
[ http://jira.codehaus.org/browse/MAVENUPLOAD-555?page=all ]
Ceki Gulcu updated MAVENUPLOAD-555:
---
Attachment: slf4j-simple-1.0-beta9-bundle.jar
slf4j-nop-1.0-beta9-bundle.jar
slf4j-log4j13-1.0-beta9-bundle.jar
> Upl
[ http://jira.codehaus.org/browse/MAVENUPLOAD-554?page=all ]
Ceki Gulcu closed MAVENUPLOAD-554:
--
Resolution: Incomplete
I mistakenly uploaded a wrong version of one of the files. Please ignore this
upload request.
> Upload request for NLO
Upload request for NLOG4J 1.2.18 and SLF4J 1.0-beta9
Key: MAVENUPLOAD-555
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-555
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: jcl104
[ http://jira.codehaus.org/browse/MAVENUPLOAD-554?page=all ]
Ceki Gulcu updated MAVENUPLOAD-554:
---
Attachment: slf4j-simple-1.0-beta9-bundle.jar
slf4j-nop-1.0-beta9-bundle.jar
slf4j-log4j-1.0-beta9-bundle.jar
> Upl
Upload request for NLOG4J 1.2.18 and SLF4J 1.0-beta9
Key: MAVENUPLOAD-554
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-554
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: jcl104
[ http://jira.codehaus.org/browse/MAVENUPLOAD-553?page=all ]
Ceki Gulcu closed MAVENUPLOAD-553:
--
Resolution: Won't Fix
SLF4J 1.0beta8 will be replaced in just a few minutes with SLF4J 1.0beta8.
There is no need to upload these files to ib
[
http://jira.codehaus.org/browse/MAVENUPLOAD-553?page=comments#action_48862 ]
Ceki Gulcu commented on MAVENUPLOAD-553:
Please hold the update. SLF4J version 1.0beta8 will be replaced with beta9 in
just a few moments.
> pload request for NLO
[ http://jira.codehaus.org/browse/MAVENUPLOAD-553?page=all ]
Ceki Gulcu updated MAVENUPLOAD-553:
---
Attachment: nlog4j-1.2.18-bundle.jar
slf4j-simple-1.0-beta8-bundle.jar
> pload request for NLOG4J 1.2.18 and SLF4J 1.0-be
pload request for NLOG4J 1.2.18 and SLF4J 1.0-beta8
---
Key: MAVENUPLOAD-553
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-553
Project: maven-upload-requests
Type: Wish
Reporter: Ceki Gulcu
Attachments: jcl104
[ http://jira.codehaus.org/browse/MAVENUPLOAD-553?page=all ]
Ceki Gulcu updated MAVENUPLOAD-553:
---
Attachment: slf4j-nop-1.0-beta8-bundle.jar
> pload request for NLOG4J 1.2.18 and SLF4J 1.0-be
[ http://jira.codehaus.org/browse/MAVENUPLOAD-503?page=all ]
Ceki Gulcu reopened MAVENUPLOAD-503:
Sorry to bug you but I noticed that the issue but the jcl104-over-slf4j files
have still not appeared at http://ibiblio.org/maven/org.slf4j/.
Is it
Upload request for "jcl104-over-slf4j"
--
Key: MAVENUPLOAD-503
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-503
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: jcl104-over-slf4j
[
http://jira.codehaus.org/browse/MAVENUPLOAD-494?page=comments#action_45616 ]
Ceki Gulcu commented on MAVENUPLOAD-494:
thank you
> Another Upload request for NLOG4J 1.2.17 and SLF4J 1.0-beta7 (replaces
> requests 492 a
[ http://jira.codehaus.org/browse/MAVENUPLOAD-494?page=all ]
Ceki Gulcu updated MAVENUPLOAD-494:
---
Attachment: nlog4j-1.2.17-bundle.jar
> Another Upload request for NLOG4J 1.2.17 and SLF4J 1.0-beta7 (replaces
> requests 492 a
: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: nlog4j-1.2.17-bundle.jar, slf4j-jdk14-1.0-beta7-bundle.jar,
slf4j-nop-1.0-beta7-bundle.jar, slf4j-simple-1.0-beta7-bundle.jar
This request supercededs requests 492 and 493. In particular, request 493
contains bundle files
[
http://jira.codehaus.org/browse/MAVENUPLOAD-493?page=comments#action_45370 ]
Ceki Gulcu commented on MAVENUPLOAD-493:
For your convenience I've added bundle files for the various slf4j jars. These
bundles include LICENSE.txt, project.xml an
[ http://jira.codehaus.org/browse/MAVENUPLOAD-493?page=all ]
Ceki Gulcu updated MAVENUPLOAD-493:
---
Attachment: slf4j-simple-1.0-beta7-bundle.jar
slf4j-simple-1.0-beta7-bundle.jar
> Upload request for NLOG4J 1.2.17 and SLF4J 1.0-be
[ http://jira.codehaus.org/browse/MAVENUPLOAD-493?page=all ]
Ceki Gulcu updated MAVENUPLOAD-493:
---
Attachment: slf4j-jdk14-1.0-beta7-bundle.jar
> Upload request for NLOG4J 1.2.17 and SLF4J 1.0-be
[ http://jira.codehaus.org/browse/MAVENUPLOAD-493?page=all ]
Ceki Gulcu updated MAVENUPLOAD-493:
---
Attachment: slf4j-nop-1.0-beta7-bundle.jar
Added slf4j-nop-1.0-beta7-bundle.jar bundle file
> Upload request for NLOG4J 1.2.17 and SLF4J 1.0-be
[
http://jira.codehaus.org/browse/MAVENUPLOAD-492?page=comments#action_45367 ]
Ceki Gulcu commented on MAVENUPLOAD-492:
Duplicate of issue 493, http://jira.codehaus.org/browse/MAVENUPLOAD-493
> Nees to upload a slf4j beta7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-493?page=all ]
Ceki Gulcu updated MAVENUPLOAD-493:
---
Attachment: nlog4j-1.2.17.jar
Added mising NLOG4J 1.2.17 jar.
> Upload request for NLOG4J 1.2.17 and SLF4J 1.0-be
Upload request for NLOG4J 1.2.17 and SLF4J 1.0-beta7
Key: MAVENUPLOAD-493
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-493
Project: maven-upload-requests
Type: Task
Reporter: Ceki Gulcu
Attachments: nlog4j
[
http://jira.codehaus.org/browse/MAVENUPLOAD-431?page=comments#action_43141 ]
Ceki Gulcu commented on MAVENUPLOAD-431:
I can confirm that the file jmxtools.jar ships with JMX 1.2 Reference
Implementation which you can download from Sun's we
69 matches
Mail list logo
