to be imported, I would prefer
to keep it minimal and have it free of any and elements
in order to not pollute importing projects.
Is my concern warranted?
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
On 12/28/2023 7:17 PM, Tamás Cservenák wrote:
> Hej C
Hello all,
Given the javadoc generation is an important part of software projects,
maybe someone would care to comment whether the behavior described below
is expected or not?
In the meantime, happy new year to all,
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com
ior of javadoc:aggregate described above
is expected or actually a problem?
Best regards,
[1] https://www.garretwilson.com/blog/2023/06/14/improve-maven-bom-pattern
[2] https://github.com/qos-ch/slf4j/tree/branch_2.1.x
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload
.
Best regards,
ps. I did not have time to read
https://github.com/junit-team/junit5/discussions/3370
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
On 6/29/2023 7:02 PM, Mark Raynsford wrote:
> (Re-sent using correct address!)
>
> Hello!
>
On 6/17/2023 9:32 PM, Ceki Gülcü wrote:
>
> Hello,
>
> Is it considered good practice to reference optional dependencies in BOM
> files?
My question is probably silly as BOM files are reserved for declaring
artifacts a project builds itself and not for dependencies, option
Hello,
Is it considered good practice to reference optional dependencies in BOM
files?
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
-
To unsubscribe, e-mail: users-unsubscr
/JPMS modular.
This approach is a lot less painful than in-single-module testing.
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch
On 10/17/2022 1:27 PM, Martin Desruisseaux wrote:
> Le 17/10/2022 à 12:33, Olivier Lamy a écrit :
>
>> I wanted
_issue
Let me know if this merits the creation of a Jira issue.
Your feedback would be most appreciated.
--
Ceki Gülcü
Sponsoring SLF4J/logback/reload4j at https://github.com/sponsors/qos-ch--module-path
"C:\\home\\buzz\\logback\\logback-classic\\target\\classes;
C:\\Users\\buzz\\.m2\\
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ü
/org.codehaus.groovy.source.Extensions
Removing this file solves the problem at least as far as Jigsaw module
resolution is concerned. Running m-dependency-p, I see:
o.c.groovy:groovy:jar:2.4.13:compile (optional) -- module groovy (auto)
Again, thank you very much for your help,
--
Ceki
On 03.12.2017 14:06, Robert
I understand correctly m-compiler-p parses module-info.java
files before invoking javac. Really?
Best regards,
--
Ceki Gülcü
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
. Something else
is afoot here.
[1] http://tinyurl.com/nfw332
-- Lucas
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
-
To unsubscribe, e-mail: users-unsubscr
I forgot to mention that my tests were conducted using Maven 2.0.9. I will redo
the tests with Maven 2.2.0.
Ceki Gulcu wrote:
Lucas Bergman wrote:
Dennis Lundberg wrote:
That is your problem. What this does is mess the dependency-tree. It
removes commons-logging from the dependency
version 99).
In summary, there is strong evidence that common-logging 99 is not the
culprit here.
Can it be that the various dependencies, some in test scope and some
in runtime scope, are confusing Maven's dependency resolution
mechanism?
Ceki Gulcu wrote:
Lucas Bergman wrote:
Dennis Lundberg
that we wanted to release version 0.0-EMPTY, not version 99. One
could argue that releasing 0.0-EMPTY could have prevented this issue
from occurring.
- Jörg
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
am picking the first
one. (It's just a warning...)
Lobgack-classic is noticing an ambiguity and informing the user.
HTH,
--
Ceki Gülcü
Logback: The reliable, generic, fast and flexible logging framework for Java.
http://logback.qos.ch
Olivier,
Since projects A and B seem to be just artifacts, I am still wondering
why projects A and B need a configuration file for logging. If it is
for testing purposes, why not use logback-text.xml and place it under
/src/test/resources/ directory?
--
Ceki Gülcü
Logback: The reliable
On 8/15/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
The difference between the runtime and test scopes is also not very
clear to me.
Nick Veys [EMAIL PROTECTED] wrote on 17.08.2006 06:16:40:
This was already answered, but the test dependencies aren't needed for
normal runtime, so
So, this means that war and ear plug-ins reference the runtime classpath
instead of say compile or test. Correct?
Martijn Dashorst [EMAIL PROTECTED] wrote on 30.08.2006
15:37:56:
No, but maven is also used to create war, ear and other distribution
packages. These packages need those actual
Thanks!
Martijn Dashorst [EMAIL PROTECTED]
30.08.2006 16:17
Please respond to
Maven Users List users@maven.apache.org
To
Maven Users List users@maven.apache.org
cc
Subject
Re: Re: Re: Dependency scopes
Reviewed by Category
Yes, but runtime classpath !=
Nick,
I very much appreciate your response. I wish the article of reference
on subject, namely, Introduction to the Dependency Mechanism was
somewhat more precise. Perhaps the maintainers of the document could
have another look at it. Is filing a bug report appropriate?
Nick Veys [EMAIL
Mike, thank you for taking the time to respond. My question had
several parts and your response relates to the difference between
runtime scope and the test scope. I wonder if someone would care to
respond to the remaining parts.
Mike Perham [EMAIL PROTECTED] wrote on 15.08.2006 18:04:17:
Hello,
I would like to ask a question regarding dependency scopes in
Maven2. After reading the article Introduction to the Dependency
Mechanism [1], I've got several questions that may have been answered
previously. I apologize in advance if that is the case.
The said article mentions the notion
.
Is there a way to upload dependencies on ibiblio so that they are
compatible with both maven1 and maven2?
Thank you for your input,
--
Ceki Gülcü
http://ceki.blogspot.com/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
, but it :
http://www.mortbay.org/jetty/tut/logging.html
Finally, I gave the -DDEBUG and -DDEBUG_PATTERNS=net.sf.hibernate
a shot, but these too seemed to be ignored.
I get the feeling that I am clashing somehow with Jetty's own
logging. Can anyone help me unravel this?
Thanks
--David
--
Ceki Gülcü
Thank you very much, Dion.
At 08:34 PM 9/21/2003 +1000, [EMAIL PROTECTED] wrote:
It's in the documentation.
See
http://maven.apache.org/reference/plugins/xdoc/faq.html#navigation-images
--
dIon Gillard, Multitask Consulting
Blog: http://blogs.codehaus.org/people/dion/
Ceki Gülcü [EMAIL
At 10:40 PM 9/19/2003 -0400, Jason van Zyl wrote:
On Fri, 2003-09-19 at 15:37, Ceki Gülcü wrote:
Hello all,
How difficult is it to change the Maven template so that the generated
project pages contain an extra image?
For an example of what is meant please refer to:
http
27 matches
Mail list logo
