You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by greenstar <jn...@gmail.com> on 2008/03/10 18:39:32 UTC
pom dependencies not found in the reactor.
Hello,
I have a situation where dependencies of type "pom" are not found in the
reactor (ie: multi-module builds). If the dependency is of type "jar", then
it is found in the reactor with no problems. What is special about "pom"
types in the reactor?
As an aside, the reason I am depending on a "pom" type is because I use this
for a bundling mechanism to group common sets of dependencies that are
included in other artifacts over and over again. We can't use the
<dependencyManagement> parent mechanism because we already use the single
inheritance for another orthogonal concern. Using pom bundles works well
except for the fact that dependencies of this type are not found in the
reactor. Am I abusing poms by using them this way? Is there a better way
to group dependencies without using the parent's <dependencyManagement>
mechanism? I could also just change the type of these bundles to type jar.
This works fine. It produces a small empty jar artifact which is fine, but
this seems a bit hackish.
Thanks for your time.
--
View this message in context: http://www.nabble.com/pom-dependencies-not-found-in-the-reactor.-tp15950904s177p15950904.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: pom dependencies not found in the reactor.
Posted by gotama <li...@bgb.net>.
There is something wrong w/ the list or Nabble. My posts were not going
through so I hit resend on Nabble. Nabble said the post was not accepted so
I don't understand why there are duplicates. Nothing went through last night
through this afternoon. I'm guessing either the list got backed up for 12+
hours and finally fired them all out, or Nabble was incorrect when it said
the post was not accepted when it really was.
I'd be interested to know if there were issues with the list or Nabble in
the past day. Sorry for the dups!
Wayne Fay wrote:
>
> Apparently Nabble is re-sending these emails repeatedly.
>
> Is "gotama" the only person using Nabble who is experiencing these
> troubles? Are other people seeing it too? Or is "gotama" simply
> hitting refresh and causing these emails to be sent over and over
> again without realizing it?
>
> Wayne
>
> On 3/10/08, gotama <li...@bgb.net> wrote:
>>
>> This problem seems similar to mine:
>> http://www.nabble.com/running-optional-ant-tasks-with-maven-antrun-plugin-td15842721s177.html
>>
>> Why is the parent pom not seeing the plugin dependencies of a required
>> jar
>> module?
>>
>>
>> greenstar wrote:
>> >
>> > Hello,
>> >
>> > I have a situation where dependencies of type "pom" are not found in
>> the
>> > reactor (ie: multi-module builds). If the dependency is of type "jar",
>> > then it is found in the reactor with no problems. What is special
>> about
>> > "pom" types in the reactor?
>> >
>> > As an aside, the reason I am depending on a "pom" type is because I use
>> > this for a bundling mechanism to group common sets of dependencies that
>> > are included in other artifacts over and over again. We can't use the
>> > <dependencyManagement> parent mechanism because we already use the
>> single
>> > inheritance for another orthogonal concern. Using pom bundles works
>> well
>> > except for the fact that dependencies of this type are not found in the
>> > reactor. Am I abusing poms by using them this way? Is there a better
>> way
>> > to group dependencies without using the parent's <dependencyManagement>
>> > mechanism? I could also just change the type of these bundles to type
>> > jar. This works fine. It produces a small empty jar artifact which is
>> > fine, but this seems a bit hackish.
>> >
>> > Thanks for your time.
>> >
>> >
>>
>> --
>> View this message in context:
>> http://www.nabble.com/pom-dependencies-not-found-in-the-reactor.-tp15950904s177p15951029.html
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>> For additional commands, e-mail: users-help@maven.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/pom-dependencies-not-found-in-the-reactor.-tp15950904s177p15970390.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: pom dependencies not found in the reactor.
Posted by Wayne Fay <wa...@gmail.com>.
Apparently Nabble is re-sending these emails repeatedly.
Is "gotama" the only person using Nabble who is experiencing these
troubles? Are other people seeing it too? Or is "gotama" simply
hitting refresh and causing these emails to be sent over and over
again without realizing it?
Wayne
On 3/10/08, gotama <li...@bgb.net> wrote:
>
> This problem seems similar to mine:
> http://www.nabble.com/running-optional-ant-tasks-with-maven-antrun-plugin-td15842721s177.html
>
> Why is the parent pom not seeing the plugin dependencies of a required jar
> module?
>
>
> greenstar wrote:
> >
> > Hello,
> >
> > I have a situation where dependencies of type "pom" are not found in the
> > reactor (ie: multi-module builds). If the dependency is of type "jar",
> > then it is found in the reactor with no problems. What is special about
> > "pom" types in the reactor?
> >
> > As an aside, the reason I am depending on a "pom" type is because I use
> > this for a bundling mechanism to group common sets of dependencies that
> > are included in other artifacts over and over again. We can't use the
> > <dependencyManagement> parent mechanism because we already use the single
> > inheritance for another orthogonal concern. Using pom bundles works well
> > except for the fact that dependencies of this type are not found in the
> > reactor. Am I abusing poms by using them this way? Is there a better way
> > to group dependencies without using the parent's <dependencyManagement>
> > mechanism? I could also just change the type of these bundles to type
> > jar. This works fine. It produces a small empty jar artifact which is
> > fine, but this seems a bit hackish.
> >
> > Thanks for your time.
> >
> >
>
> --
> View this message in context: http://www.nabble.com/pom-dependencies-not-found-in-the-reactor.-tp15950904s177p15951029.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: pom dependencies not found in the reactor.
Posted by gotama <li...@bgb.net>.
This problem seems similar to mine:
http://www.nabble.com/running-optional-ant-tasks-with-maven-antrun-plugin-td15842721s177.html
Why is the parent pom not seeing the plugin dependencies of a required jar
module?
greenstar wrote:
>
> Hello,
>
> I have a situation where dependencies of type "pom" are not found in the
> reactor (ie: multi-module builds). If the dependency is of type "jar",
> then it is found in the reactor with no problems. What is special about
> "pom" types in the reactor?
>
> As an aside, the reason I am depending on a "pom" type is because I use
> this for a bundling mechanism to group common sets of dependencies that
> are included in other artifacts over and over again. We can't use the
> <dependencyManagement> parent mechanism because we already use the single
> inheritance for another orthogonal concern. Using pom bundles works well
> except for the fact that dependencies of this type are not found in the
> reactor. Am I abusing poms by using them this way? Is there a better way
> to group dependencies without using the parent's <dependencyManagement>
> mechanism? I could also just change the type of these bundles to type
> jar. This works fine. It produces a small empty jar artifact which is
> fine, but this seems a bit hackish.
>
> Thanks for your time.
>
>
--
View this message in context: http://www.nabble.com/pom-dependencies-not-found-in-the-reactor.-tp15950904s177p15951029.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org