I realize this - the only reason I'm suggesting we deviate is that the
standard artifact name, currently, is a nodep jar. I either want to
have "no surprises" or "build time surprises" if the former cannot be
obtained. Having runtime surprises because of missing artifacts, or
version conflict or the like seems worse.
c.
On 13 Dec 2013, at 9:15, David Hoffer wrote:
It seems the most common approach is having the standard artifact name
(e.g. guice) specify in its pom the normal dependencies and then the
one
that includes them internally add -nodep suffix to that artifact name
(e.g.
guice-nodep).
Christian Gruber :: Google, Inc. :: Java Core Libraries :: Dependency
Injection
email: [email protected] :::: mobile: +1 (646) 807-9839
--
You received this message because you are subscribed to the Google Groups
"google-guice" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to [email protected].
To post to this group, send email to [email protected].
Visit this group at http://groups.google.com/group/google-guice.
For more options, visit https://groups.google.com/groups/opt_out.
