If the dependencies are not applicable for this artifact (e.g. the pom is
not valid for it because it is generated against Maven convention) then it
should not be an artifact in the same coordinates but rather be a
different module with different GAV coordinates

On Sat, January 5, 2013 2:34 pm, Stanimir Stamenkov wrote:
> Is it true attached artifacts, that is artifacts with a non-empty
> classifier, "inherit" their dependencies from the main artifact?
> Stated otherwise - is it possible to specify different set of
> dependencies for an attached artifact such that when included in
> another project, that different set of dependencies get resolved for
> it, instead of the dependencies declared for the main artifact?
>
> It doesn't really matter for many of the commonly attached artifacts
> like "sources" and "javadoc", or the main set of dependencies is
> just fine for "classes" (of a WAR), but here are some cases it makes
> sens if the dependencies for an attached artifact could be specified
> differently from the main one:
>
> 1. "jar-with-dependencies" - an assembly packaging all required
> dependencies in the JAR, already.  In this case no dependencies
> should be resolved for such an artifact, I guess;
>
> 2. "client" - such as produced by the EJB plugin [1].  In this case
> resolving all dependencies from the main implementation is not
> desired.  Adding some runtime dependencies for the attached
> "client", not declared for the main implementation, may be desired too.
>
> So is achieving different set of dependencies possible with using
> attached artifacts vs. just different artifacts?
>
> [1]
> http://maven.apache.org/plugins/maven-ejb-plugin/examples/ejb-client-dependency.html
>
> --
> Stanimir
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to