cü a écrit :
> Hello,
>
> Is it considered good practice to reference optional dependencies in BOM
> files?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
I would say yes.
My reasoning: BOM is bill of materials, ANY materials potentially needed
for a library.
Otoh, optional dependencies have to be explicitly listed by consumers (POM
consuming your library).
Hence, you will help your consumer by giving them predefined version to
use, IF they
the time you import a BOM into the `` section,
/everything/ in the BOM is optional until it is declared to be actually
used separately in the actual `` section of the POM or one
of its descendants.
Garret
On 6/17/2023 12:32 PM, Ceki Gülcü wrote:
Hello,
Is it considered good practice to refere
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
ansitive
dependency. That is: we depend on someone else's artifact (let's call
it A), which itself depends *in some circumstances* on a third
artifact (from a third source) which I'll call "B". That is: if you
never trigger a certain feature of A then it doesn't rea
ror,
>> and handle the error in a more appropriate way for your users?
>>
>> Regards,
>> Curtis
>>
>> On Thu, Jan 22, 2015 at 10:48 AM, Mark H. Wood wrote:
>>
>> I'm working on a project which has an "optional" transitive
>>> d
's artifact (let's call
it A), which itself depends *in some circumstances* on a third
artifact (from a third source) which I'll call "B". That is: if you
never trigger a certain feature of A then it doesn't really need B. A
expresses this by making B a dependency with
l call "B". That is: if you
> never trigger a certain feature of A then it doesn't really need B. A
> expresses this by making B a dependency with provided.
>
> I feel that this is an abuse of the dependency mechanism, and that
> optional dependencies should not be d
ances* on a third
artifact (from a third source) which I'll call "B". That is: if you
never trigger a certain feature of A then it doesn't really need B. A
expresses this by making B a dependency with provided.
I feel that this is an abuse of the dependency mechanism, and tha
f you
never trigger a certain feature of A then it doesn't really need B. A
expresses this by making B a dependency with provided.
I feel that this is an abuse of the dependency mechanism, and that
optional dependencies should not be declared to Maven as dependencies
at all. I think that
> any idea where his background jpg was shot?
It changes every time you refresh the page. The author also tweeted
"My blog background picture will now change regularly and draw from
the tens of thousands of photos from my trips to 63 countries so far."
So I'm afraid you'd have to ask him directly
> Date: Wed, 8 Aug 2012 07:23:00 -0400
> From: rwhee...@artifact-software.com
> To: users@maven.apache.org
> Subject: Nice article discussing optional dependencies
>
> This is a nicely illustrated and fairly concise discussion about
> handling optional dependencies.
> h
This is a nicely illustrated and fairly concise discussion about
handling optional dependencies.
http://www.axelfontaine.com/2012/08/optional-dependency-strategies-for-java.html
Enjoy
Ron
--
Ron Wheeler
President
Artifact Software Inc
email: rwhee...@artifact-software.com
skype
Is there any way to toggle which dependencies are optional, based on the
classifier?
E.g., if we have these dependencies:
A -> X, Y, Z
B -> A
When B depends on A, it transitively inherits X, Y, and Z. Now let's
suppose A produces multiple zips (different classifiers) using the assembly
plugin.
o not have it defined as
a dependency in the pom. When the test that used shale-test failed I had to
determine the failure was due to a missing dependency that was defined in
shale-test's
pom. Thus the following questions.
1) Is their a way I can include all of a dependencies optional depend
n the test that used shale-test failed I had to
determine the failure was due to a missing dependency that was defined in
shale-test's
pom. Thus the following questions.
1) Is their a way I can include all of a dependencies optional dependencies
without knowing wha
My bad, it must be Friday!!! how did i missed read that in the pom? :(
Thanks for pointing it out.
-D
On 4/27/07, Heinrich Nirschl <[EMAIL PROTECTED]> wrote:
On Fri, 2007-04-27 at 16:04 -0700, Dan Tran wrote:
> Hello, my webapp depends on commons-logging-1.1 which has a punch of
> optional j
On Fri, 2007-04-27 at 16:04 -0700, Dan Tran wrote:
> Hello, my webapp depends on commons-logging-1.1 which has a punch of
> optional jars and they are pull into my WEB-INF/lib directory
> is it a expected behavior, the optional depdendency seems to disagree with
> that
According to the commons-lo
Hello, my webapp depends on commons-logging-1.1 which has a punch of
optional jars and they are pull into my WEB-INF/lib directory
is it a expected behavior, the optional depdendency seems to disagree with
that
here is a pom to produce a the issue, makesure to create a empty
src/main/webapp/WEB
Hi,
I am presently converting our projects from maven 1.1 to maven 2.
I must say that the transitive dependencies help a lot to reduce the pom and
makes upgrades easier.
But I would like to include optional dependencies as well, without having to
explicitly include them myself in the pom.
For
have a pom file which includes dependency=A as scope=compile,
optional=true.
I would like the assembly plugin to add all optional dependencies in a
separate directory than the non-optional ones... any way to do this?
I currently have:
false
runtime
And it puts
I have a pom file which includes dependency=A as scope=compile, optional=true.
I would like the assembly plugin to add all optional dependencies in a
separate directory than the non-optional ones... any way to do this?
I currently have:
false
runtime
And it puts
Brett Porter wrote:
Create a profile, activated by the jdk, and include the dependency within it.
Thanks, read through the docs and this seems to be fine. I was missing
one feature, though, which I have filed as MNG-1910: The jdk element
should allow values like 1.4+.
Jochen
-
Optional was not the solution to his original mail (I emailed him
separately about using profiles in this instance).
I just wanted to answer your question about the use of optional.
- Brett
On 1/2/06, ir. ing. Jan Dockx <[EMAIL PROTECTED]> wrote:
> Ok, but in the original mail, Jochen talks abo
Ok, but in the original mail, Jochen talks about the requirements of his _users_, not of the developers of the main project. And users of his users need those dependencies transitively …
On 1 Jan 2006, at 23:48, Brett Porter wrote:
The optional tag is *only* for the purposes of transitive
depen
The optional tag is *only* for the purposes of transitive
dependencies. It's not really intended for use in a real Maven build.
- Brett
On 1/2/06, ir. ing. Jan Dockx <[EMAIL PROTECTED]> wrote:
> Frankly, I have no idea ;-). I knew the tag existed, but have no
> experience with it yet, although I
Create a profile, activated by the jdk, and include the dependency within it.
Cheers,
Brett
On 1/2/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> are there any recommendations on how to handle dependencies, which
> aren't always required?
>
> For example, I am using JDK 1.5 classes in
Frankly, I have no idea ;-). I knew the tag existed, but have no experience with it yet, although I do recognize your problem (see http://cvs.peopleware.be/training/maven/maven2/dependencies.html, Issues). I briefly talked with Vincent Massol during JavaPolis (hi Vincent -- nice chat), and he wasn'
ir. ing. Jan Dockx wrote:
Have you tried the tag for the dependency?
Thank you. To be honest, I wasn't aware of this tag.
Reading through the docs, I do, however, believe, that it is a partial
solution only, isn't it? I'd prefer a solution where Maven automatically
detects the presence or
Have you tried the tag for the dependency?
On 1 Jan 2006, at 14:25, Jochen Wiedmann wrote:
Hi,
are there any recommendations on how to handle dependencies, which aren't always required?
For example, I am using JDK 1.5 classes in some projects like javax.xml.Constants, or javax.xml.namespace.Q
Hi,
are there any recommendations on how to handle dependencies, which
aren't always required?
For example, I am using JDK 1.5 classes in some projects like
javax.xml.Constants, or javax.xml.namespace.QName. For JDK 1.3, and JDK
1.4 users, these are available as dependencies like
gero
true
- Brett
On 10/12/05, Dave Brondsema <[EMAIL PROTECTED]> wrote:
>
> I have a POM that declares some optional dependencies, like this:
>
>
> xerces
> xerces
> 2.0.2
>
>
>
> These are getting included as a transitive de
I have a POM that declares some optional dependencies, like this:
xerces
xerces
2.0.2
These are getting included as a transitive dependency. Am I doing
something wrong or is unimplemented?
--
Dave Brondsema
Software Developer
Cornerstone University
34 matches
Mail list logo
