Hi Laird,
Laird Nelson wrote:
> On Fri, Dec 3, 2010 at 9:36 AM, Yanko, Curtis wrote:
>
>> We only declare dependencies as items in our
>> Parent POMs and then declare *versionless* dependencies in each app so
>> they are explicit and comprehensible without having to go look somewhere
>> else (
On 03/12/2010 11:12 AM, Laird Nelson wrote:
On Fri, Dec 3, 2010 at 9:36 AM, Yanko, Curtis wrote:
We only declare dependencies as items in our
Parent POMs and then declare *versionless* dependencies in each app so
they are explicit and comprehensible without having to go look somewhere
else (
On Fri, Dec 3, 2010 at 9:36 AM, Yanko, Curtis wrote:
> We only declare dependencies as items in our
> Parent POMs and then declare *versionless* dependencies in each app so
> they are explicit and comprehensible without having to go look somewhere
> else (except for versioning which is all in on
How is this an override? You have declared two different things
(different artifactId). But... This is why we don't declare dependencies
in Parent POMs ( I see someone else beat me to the Super POM
clarification).
We only declare dependencies as items in our
Parent POMs and then declare *versionl
FIrst, don't use the name "super pom". In the Maven world, there is one pom
called the super pom and it is the pom all other poms inherits implicitly.
It's part of Maven core. DOn't use that name for anything else as it will
cause confusion. What you have is a parent pom.
Regarding your question.
Hi John,
there is such a thing as dependency exclusions, that might help you in this:
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html
cheers,
Phh
On Fri, Dec 3, 2010 at 1:14 AM, asdas adasads
wrote:
> Hi,
>
> My project has two pom's. One is
