You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by solo turn <so...@gmail.com> on 2005/07/20 15:32:34 UTC
dependecy management, shared libraries should not be in a war/ear
hi,
how shared libraries are handled by the maven dependency management,
with respect to the following areas:
* compile:
seems to be perfect
* eclipse (create an eclipse project referencing libraries)
not sure, but works
* install (build a war, ear)
i have no idea how to declare a dependency as
"shared library" so it does not get included in the deliverable
could you please explain how you specify "shared libraries" in the pom
file, so they do not get inlcuded when building a war? maybe on
http://maven.apache.org/maven2/dependencies.html.
-solo
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management,
shared libraries should not be in a war/ear
Posted by Kris Bravo <kr...@corridor-software.us>.
I prefer 4) with the logged warnings. With 2) you potentially create more
significant runtime problems.
If, however, you decide to go with 2), a file included in an obvious
location (i.e., WEB-INF/lib/runtime.txt) listing the dropped dependencies
would help with the troubleshooting sessions.
Kris
> Jason van Zyl wrote:
>
>>>2) scope in end POM always wins
>>>
>>>
>>To me this would seem to be the most obvious the user.
>>
>>
> I agree, given the current use of dependencies.
>
>>
>>
>>>4) keep it as is (where you can use <dependencyManagement /> to force
>>>the appropriate scope)
>>>
>>>
>>Wouldn't that be a little inconvenient and unintuitive to have to create
>>the <depMan/> element to control the scope of a single dependency.
>>
>>
> Yes, it is inconvenient.
>
> A couple of problems with (2):
> - it changes the behaviour of a dependency contextually when it is
> acting in transitive mode vs. final POM. This may not be a big deal.
> - it could hide changes that cause breakages.
>
> Consider this scenario:
> A (a webapp) depends on B (which currently has no dependencies).
> A depends on commons-collections as a test dependency.
> B later adds commons-collections as a compile time dependency.
>
> Under (4), commons-collections becomes a compile time dependency for A
> and gets included in the webapp, allowing B to function.
> Under (2), C-C remains a test dependency for A and gets omitted from the
> webapp, causing B to fail at runtime with a ClassNotFoundException.
>
> Of course, we'd be warning something to the effect of "Dependency scope
> test commons-collections hides a definition of compile on B", but if
> that is actually what you wanted to do, doesn't that get annoying? I
> guess we recommend using depMgmt there to avoid the warning.
>
> I guess another option is to use (4) and instead of requiring a depMgmt
> entry, have a <force>true</force> flag on a dependency?
>
> What do others prefer? I guess of all this, I think (2) with the warning
> might be the best solution.
>
> - Brett
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by Brett Porter <br...@apache.org>.
Jason van Zyl wrote:
>>2) scope in end POM always wins
>>
>>
>To me this would seem to be the most obvious the user.
>
>
I agree, given the current use of dependencies.
>
>
>>4) keep it as is (where you can use <dependencyManagement /> to force
>>the appropriate scope)
>>
>>
>Wouldn't that be a little inconvenient and unintuitive to have to create
>the <depMan/> element to control the scope of a single dependency.
>
>
Yes, it is inconvenient.
A couple of problems with (2):
- it changes the behaviour of a dependency contextually when it is
acting in transitive mode vs. final POM. This may not be a big deal.
- it could hide changes that cause breakages.
Consider this scenario:
A (a webapp) depends on B (which currently has no dependencies).
A depends on commons-collections as a test dependency.
B later adds commons-collections as a compile time dependency.
Under (4), commons-collections becomes a compile time dependency for A
and gets included in the webapp, allowing B to function.
Under (2), C-C remains a test dependency for A and gets omitted from the
webapp, causing B to fail at runtime with a ClassNotFoundException.
Of course, we'd be warning something to the effect of "Dependency scope
test commons-collections hides a definition of compile on B", but if
that is actually what you wanted to do, doesn't that get annoying? I
guess we recommend using depMgmt there to avoid the warning.
I guess another option is to use (4) and instead of requiring a depMgmt
entry, have a <force>true</force> flag on a dependency?
What do others prefer? I guess of all this, I think (2) with the warning
might be the best solution.
- Brett
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a
war/ear
Posted by Jason van Zyl <ja...@maven.org>.
On Mon, 2005-07-25 at 08:18 +1000, Brett Porter wrote:
> What this is is another dependency with a more inclusive scope down the
> chain.
>
> While the behaviour is correct, it is not intuitive. Anyone have a
> preferred option?
>
> 1) Log a warning when a higher priority scope is found in the chain
> 2) scope in end POM always wins
> 3) same as 2, but only when it is "provided"
> 4) keep it as is (where you can use <dependencyManagement /> to force
> the appropriate scope)
>
> I'm in favour of doing (1) regardless.
+1
> If that isn't obvious enough we
> can do (2)
To me this would seem to be the most obvious the user.
> , but my preference remains to be (4).
Wouldn't that be a little inconvenient and unintuitive to have to create
the <depMan/> element to control the scope of a single dependency.
> - Brett
>
> Stephane Nicoll wrote:
>
> >On 7/23/05, solo turn <so...@gmail.com> wrote:
> >
> >>somehow i do not understand that, i tried:
> >>
> >> <dependencies>
> >> <dependency>
> >> ...
> >> <scope>provided</scope>
> >> </dependency>
> >>
> >>and it still includes it into the war. is this a bug in the war
> >>plugin?
> >
> >
> >I don't think so. I have also seen strange behavior with the
> >dependencies's scope. The war plugin takes the dependency if it's
> >neither test, nor provided. Put m2 in debug mode with the -X flag to
> >see more details.
> >
> >Namely, JUnit with scope test is included in an EAR file even if it
> >should not be. I suspect the scope to be 'null' in both cases. I'll
> >check Jira and file a new bug if necessary (but I need to check this
> >first).
> >
> >Cheers,
> >Stéphane
> >
> >
> >if i make a type, like "prod" instead of "provided", it still
> >
> >>works and packs it into the war.
> >>
> >>-solo
> >>
> >>On 7/20/05, Brett Porter <br...@apache.org> wrote:
> >>
>
> > see "provided" on that page.
> >
> > solo turn wrote:
> >
> > >hi,
> >
> > >how shared libraries are handled by the maven dependency management,
> > >with respect to the following areas:
> > >* compile:
> > >seems to be perfect
> > >* eclipse (create an eclipse project referencing libraries)
> > >not sure, but works
> > >* install (build a war, ear)
> > >i have no idea how to declare a dependency as
> > >"shared library" so it does not get included in the deliverable
> >
> > >could you please explain how you specify "shared libraries" in the pom
> > >file, so they do not get inlcuded when building a war? maybe on
> > >http://maven.apache.org/maven2/dependencies.html.
> >
> > >-solo
> >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
jvz.
Jason van Zyl
jason at maven.org
http://maven.apache.org
Simplex sigillum veri. (Simplicity is the seal of truth.)
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by Brett Porter <br...@apache.org>.
What this is is another dependency with a more inclusive scope down the
chain.
While the behaviour is correct, it is not intuitive. Anyone have a
preferred option?
1) Log a warning when a higher priority scope is found in the chain
2) scope in end POM always wins
3) same as 2, but only when it is "provided"
4) keep it as is (where you can use <dependencyManagement /> to force
the appropriate scope)
I'm in favour of doing (1) regardless. If that isn't obvious enough we
can do (2), but my preference remains to be (4).
- Brett
Stephane Nicoll wrote:
>On 7/23/05, solo turn <so...@gmail.com> wrote:
>
>>somehow i do not understand that, i tried:
>>
>> <dependencies>
>> <dependency>
>> ...
>> <scope>provided</scope>
>> </dependency>
>>
>>and it still includes it into the war. is this a bug in the war
>>plugin?
>
>
>I don't think so. I have also seen strange behavior with the
>dependencies's scope. The war plugin takes the dependency if it's
>neither test, nor provided. Put m2 in debug mode with the -X flag to
>see more details.
>
>Namely, JUnit with scope test is included in an EAR file even if it
>should not be. I suspect the scope to be 'null' in both cases. I'll
>check Jira and file a new bug if necessary (but I need to check this
>first).
>
>Cheers,
>Stéphane
>
>
>if i make a type, like "prod" instead of "provided", it still
>
>>works and packs it into the war.
>>
>>-solo
>>
>>On 7/20/05, Brett Porter <br...@apache.org> wrote:
>>
> see "provided" on that page.
>
> solo turn wrote:
>
> >hi,
>
> >how shared libraries are handled by the maven dependency management,
> >with respect to the following areas:
> >* compile:
> >seems to be perfect
> >* eclipse (create an eclipse project referencing libraries)
> >not sure, but works
> >* install (build a war, ear)
> >i have no idea how to declare a dependency as
> >"shared library" so it does not get included in the deliverable
>
> >could you please explain how you specify "shared libraries" in the pom
> >file, so they do not get inlcuded when building a war? maybe on
> >http://maven.apache.org/maven2/dependencies.html.
>
> >-solo
>
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by Stephane Nicoll <st...@gmail.com>.
On 7/23/05, solo turn <so...@gmail.com> wrote:
> somehow i do not understand that, i tried:
>
> <dependencies>
> <dependency>
> ...
> <scope>provided</scope>
> </dependency>
>
> and it still includes it into the war. is this a bug in the war
> plugin?
I don't think so. I have also seen strange behavior with the
dependencies's scope. The war plugin takes the dependency if it's
neither test, nor provided. Put m2 in debug mode with the -X flag to
see more details.
Namely, JUnit with scope test is included in an EAR file even if it
should not be. I suspect the scope to be 'null' in both cases. I'll
check Jira and file a new bug if necessary (but I need to check this
first).
Cheers,
Stéphane
if i make a type, like "prod" instead of "provided", it still
> works and packs it into the war.
>
> -solo
>
> On 7/20/05, Brett Porter <br...@apache.org> wrote:
> > -----BEGIN PGP SIGNED MESSAGE-----
> > Hash: SHA1
> >
> > see "provided" on that page.
> >
> > solo turn wrote:
> >
> > >hi,
> > >
> > >how shared libraries are handled by the maven dependency management,
> > >with respect to the following areas:
> > >* compile:
> > > seems to be perfect
> > >* eclipse (create an eclipse project referencing libraries)
> > > not sure, but works
> > >* install (build a war, ear)
> > > i have no idea how to declare a dependency as
> > > "shared library" so it does not get included in the deliverable
> > >
> > >could you please explain how you specify "shared libraries" in the pom
> > >file, so they do not get inlcuded when building a war? maybe on
> > >http://maven.apache.org/maven2/dependencies.html.
> > >
> > >-solo
> > >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >For additional commands, e-mail: dev-help@maven.apache.org
> > >
> > >
> >
> > -----BEGIN PGP SIGNATURE-----
> > Version: GnuPG v1.4.0 (Cygwin)
> > Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
> >
> > iD8DBQFC3lLVOb5RoQhMkRMRAhs7AJ9mIBPPpk6G+ifAjB80ESr74HbGRwCgvcIj
> > YO4YuaTw/IWTGglwIaTsXx8=
> > =wgPw
> > -----END PGP SIGNATURE-----
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
.::You're welcome ::.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by solo turn <so...@gmail.com>.
somehow i do not understand that, i tried:
<dependencies>
<dependency>
...
<scope>provided</scope>
</dependency>
and it still includes it into the war. is this a bug in the war
plugin? if i make a type, like "prod" instead of "provided", it still
works and packs it into the war.
-solo
On 7/20/05, Brett Porter <br...@apache.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> see "provided" on that page.
>
> solo turn wrote:
>
> >hi,
> >
> >how shared libraries are handled by the maven dependency management,
> >with respect to the following areas:
> >* compile:
> > seems to be perfect
> >* eclipse (create an eclipse project referencing libraries)
> > not sure, but works
> >* install (build a war, ear)
> > i have no idea how to declare a dependency as
> > "shared library" so it does not get included in the deliverable
> >
> >could you please explain how you specify "shared libraries" in the pom
> >file, so they do not get inlcuded when building a war? maybe on
> >http://maven.apache.org/maven2/dependencies.html.
> >
> >-solo
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (Cygwin)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFC3lLVOb5RoQhMkRMRAhs7AJ9mIBPPpk6G+ifAjB80ESr74HbGRwCgvcIj
> YO4YuaTw/IWTGglwIaTsXx8=
> =wgPw
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by solo turn <so...@gmail.com>.
hi brett,
i agree for your case, that transitivity is not a must. but i do not
think it would harm (except you probably end up auto-downloading
additional libraries you do would not need for compilation).
maybe the reason for why i like it shoul be transitive is, that i
still hope dependency mechanism could be extendet to support shared
libraries. i consider beeing independent of foreign products jar-file
policy (deletions, additions, renames) a big advantage. usually this
is elegantly solved with a shared "library", containing a few files.
may i use java itself as an example:
java13-shared-lib:
* jre/lib/i18n.jar
* jre/lib/sunrsasign.jar
* jre/lib/javaplugin.jar
* jre/lib/rt.jar
java14-shared-lib (there are some renames, some additions):
* jre/lib/sunrsasign.jar
* jre/lib/plugin.jar
* jre/lib/rt.jar
* jre/lib/jsse.jar
* jre/lib/charsets.jar
* jre/lib/jce.jar
* jre/lib/ext/dnsns.jar
* jre/lib/ext/sunjce_provider.jar
* jre/lib/ext/ldapsec.jar
* jre/lib/ext/localedata.jar
java15-shared-lib:
* mostly the same, but ldapsec missing, and sunpkcs11 added
what we try to do is just include ONE dependency in the pom:
java-shared-lib, v 1.4.2, provided (no jar attached to that one).
what we expect m2 to do then if we build a war:
* use all the jars depending on that dependency for compiling
(i.e. transitive becomes a must)
* deliver no jar, as it is provided at the target as shared library
if we later switch to jdk-1.5, we just change the version number of
that one dependency to 1.5.0, and everything works as before. if our
code does not compile and we want to take back the upgrade, we can
easily change the version number back. with the current mechanism we
end up turning the whole pom upside down.
a similar configuration does exist in a lot of products, like servlet
and jsp api (tomcat split a single jar in v4.x to two jars in 5.x).
-solo.
On 7/21/05, Brett Porter <br...@apache.org> wrote:
> only the "provided" scope dependencies are not transitive, as they are
> designed for placing in an end POM.
>
> Consider servlet API: when you depend on it in your WAR, scope =
> provided as it is used for compilation but is provided at runtime by the
> container.
>
> Now if a library uses servlet API, provided doesn't make sense as the
> library doesn't know its runtime context. This is why provided is not
> transitive. The library would declare it as compile in this case, and a
> WAR would then restate it as "provided" using dependency management.
>
> Do others agree this is the expected behaviour?
>
> Cheers,
> Brett
>
> solo turn wrote:
>
> >but this is not transitive? i.e. you define a shared library in idea,
> >eclipse, etc. with a name, containing one or more jars. if you do that
> >in a pom by specifying a dependency to a library, which depends on 2
> >or more jars, how do these jars get into the compile classpath?
> >
> >On 7/20/05, Brett Porter <br...@apache.org> wrote:
> >
>
> > see "provided" on that page.
> >
> > solo turn wrote:
> >
> > >hi,
> >
> > >how shared libraries are handled by the maven dependency management,
> > >with respect to the following areas:
> > >* compile:
> > >seems to be perfect
> > >* eclipse (create an eclipse project referencing libraries)
> > >not sure, but works
> > >* install (build a war, ear)
> > >i have no idea how to declare a dependency as
> > >"shared library" so it does not get included in the deliverable
> >
> > >could you please explain how you specify "shared libraries" in the pom
> > >file, so they do not get inlcuded when building a war? maybe on
> > >http://maven.apache.org/maven2/dependencies.html.
> >
> > >-solo
> >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by solo turn <so...@gmail.com>.
can it be that the dependency mechanism is still incomplete? i'd like
to be independent of foreign products jar-file policy. this is solved
with a shared library. may i use java itself as an example, even if i
know its in the path automatically:
java13-shared-lib:
* jre/lib/i18n.jar
* jre/lib/i18n.jar
* jre/lib/i18n.jar
* jre/lib/i18n.jar
java14-shared-lib:
java15-shared-lib:
On 7/21/05, Brett Porter <br...@apache.org> wrote:
> only the "provided" scope dependencies are not transitive, as they are
> designed for placing in an end POM.
>
> Consider servlet API: when you depend on it in your WAR, scope =
> provided as it is used for compilation but is provided at runtime by the
> container.
>
> Now if a library uses servlet API, provided doesn't make sense as the
> library doesn't know its runtime context. This is why provided is not
> transitive. The library would declare it as compile in this case, and a
> WAR would then restate it as "provided" using dependency management.
>
> Do others agree this is the expected behaviour?
>
> Cheers,
> Brett
>
> solo turn wrote:
>
> >but this is not transitive? i.e. you define a shared library in idea,
> >eclipse, etc. with a name, containing one or more jars. if you do that
> >in a pom by specifying a dependency to a library, which depends on 2
> >or more jars, how do these jars get into the compile classpath?
> >
> >On 7/20/05, Brett Porter <br...@apache.org> wrote:
> >
>
> > see "provided" on that page.
> >
> > solo turn wrote:
> >
> > >hi,
> >
> > >how shared libraries are handled by the maven dependency management,
> > >with respect to the following areas:
> > >* compile:
> > >seems to be perfect
> > >* eclipse (create an eclipse project referencing libraries)
> > >not sure, but works
> > >* install (build a war, ear)
> > >i have no idea how to declare a dependency as
> > >"shared library" so it does not get included in the deliverable
> >
> > >could you please explain how you specify "shared libraries" in the pom
> > >file, so they do not get inlcuded when building a war? maybe on
> > >http://maven.apache.org/maven2/dependencies.html.
> >
> > >-solo
> >
> > >---------------------------------------------------------------------
> > >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by Brett Porter <br...@apache.org>.
only the "provided" scope dependencies are not transitive, as they are
designed for placing in an end POM.
Consider servlet API: when you depend on it in your WAR, scope =
provided as it is used for compilation but is provided at runtime by the
container.
Now if a library uses servlet API, provided doesn't make sense as the
library doesn't know its runtime context. This is why provided is not
transitive. The library would declare it as compile in this case, and a
WAR would then restate it as "provided" using dependency management.
Do others agree this is the expected behaviour?
Cheers,
Brett
solo turn wrote:
>but this is not transitive? i.e. you define a shared library in idea,
>eclipse, etc. with a name, containing one or more jars. if you do that
>in a pom by specifying a dependency to a library, which depends on 2
>or more jars, how do these jars get into the compile classpath?
>
>On 7/20/05, Brett Porter <br...@apache.org> wrote:
>
> see "provided" on that page.
>
> solo turn wrote:
>
> >hi,
>
> >how shared libraries are handled by the maven dependency management,
> >with respect to the following areas:
> >* compile:
> >seems to be perfect
> >* eclipse (create an eclipse project referencing libraries)
> >not sure, but works
> >* install (build a war, ear)
> >i have no idea how to declare a dependency as
> >"shared library" so it does not get included in the deliverable
>
> >could you please explain how you specify "shared libraries" in the pom
> >file, so they do not get inlcuded when building a war? maybe on
> >http://maven.apache.org/maven2/dependencies.html.
>
> >-solo
>
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by solo turn <so...@gmail.com>.
but this is not transitive? i.e. you define a shared library in idea,
eclipse, etc. with a name, containing one or more jars. if you do that
in a pom by specifying a dependency to a library, which depends on 2
or more jars, how do these jars get into the compile classpath?
On 7/20/05, Brett Porter <br...@apache.org> wrote:
> -----BEGIN PGP SIGNED MESSAGE-----
> Hash: SHA1
>
> see "provided" on that page.
>
> solo turn wrote:
>
> >hi,
> >
> >how shared libraries are handled by the maven dependency management,
> >with respect to the following areas:
> >* compile:
> > seems to be perfect
> >* eclipse (create an eclipse project referencing libraries)
> > not sure, but works
> >* install (build a war, ear)
> > i have no idea how to declare a dependency as
> > "shared library" so it does not get included in the deliverable
> >
> >could you please explain how you specify "shared libraries" in the pom
> >file, so they do not get inlcuded when building a war? maybe on
> >http://maven.apache.org/maven2/dependencies.html.
> >
> >-solo
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >For additional commands, e-mail: dev-help@maven.apache.org
> >
> >
>
> -----BEGIN PGP SIGNATURE-----
> Version: GnuPG v1.4.0 (Cygwin)
> Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
>
> iD8DBQFC3lLVOb5RoQhMkRMRAhs7AJ9mIBPPpk6G+ifAjB80ESr74HbGRwCgvcIj
> YO4YuaTw/IWTGglwIaTsXx8=
> =wgPw
> -----END PGP SIGNATURE-----
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: dependecy management, shared libraries should not be in a war/ear
Posted by Brett Porter <br...@apache.org>.
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
see "provided" on that page.
solo turn wrote:
>hi,
>
>how shared libraries are handled by the maven dependency management,
>with respect to the following areas:
>* compile:
> seems to be perfect
>* eclipse (create an eclipse project referencing libraries)
> not sure, but works
>* install (build a war, ear)
> i have no idea how to declare a dependency as
> "shared library" so it does not get included in the deliverable
>
>could you please explain how you specify "shared libraries" in the pom
>file, so they do not get inlcuded when building a war? maybe on
>http://maven.apache.org/maven2/dependencies.html.
>
>-solo
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>For additional commands, e-mail: dev-help@maven.apache.org
>
>
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.0 (Cygwin)
Comment: Using GnuPG with Thunderbird - http://enigmail.mozdev.org
iD8DBQFC3lLVOb5RoQhMkRMRAhs7AJ9mIBPPpk6G+ifAjB80ESr74HbGRwCgvcIj
YO4YuaTw/IWTGglwIaTsXx8=
=wgPw
-----END PGP SIGNATURE-----
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org