Hmm... They both have the same parent. This parent is a pom package defining all the basics for my java modules. This is the parent:
<groupId>com.mycomp.build</groupId> <artifactId>build-java</artifactId> <version>1.0-SNAPSHOT</version> <packaging>pom</packaging> And in both modules: <parent> <groupId>com.barcoview.mis.build</groupId> <artifactId>build-java</artifactId> <version>1.0-SNAPSHOT</version> </parent> How should I handle this case? I'm using the <modules/> tag, because I'm developing both modules at the same time, and I would like to call 'mvn package' on the "top"-module and the module this "top"-module depends on also gets build. I hope you understand what I'm trying to archive. regards, Wim 2005/11/18, Brett Porter <[EMAIL PROTECTED]>: > > Do they have a parent? > > I was a little confused by something you said earlier that just > clicked: you depend lang depends on logging, but you have a lang > module in logging? Module is (sort of) the inverse of a parent > relationship, which is different to a dependency. > > Maybe the dependency tree is getting confused by something in this regard. > > - Brett > > On 11/18/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > I saw that other thread, but my projects have a different artifactId: > > > > <groupId>com.mycomp.utils</groupId> > > <artifactId>utils-lang</artifactId> > > > > <groupId>com.mycomp.utils</groupId> > > <artifactId>utils-logging</artifactId> > > > > so, maybe still something else? > > > > regards, > > > > Wim > > > > > > 2005/11/18, Brett Porter <[EMAIL PROTECTED]>: > > > > > > Yes, it was discovered on another thread that its because the > > > artifactId is the same in two modules. > > > > > > - Brett > > > > > > On 11/18/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > > > Both modules are defined as 'jar', so that can't be the problem. I > can > > > > assume then that this is a bug? > > > > > > > > regards, > > > > > > > > Wim > > > > > > > > 2005/11/17, Brett Porter <[EMAIL PROTECTED]>: > > > > > > > > > > On 11/17/05, Wim Deblauwe <[EMAIL PROTECTED]> wrote: > > > > > > What does the error 'No goals needed for project - > > > > > > skipping' mean? Any clue on what goes wrong? > > > > > > > > > > Nothing was bound to the lifecycle for your packaging. Check > > > > > <packaging> is jar or something else that defines a compile or > prior > > > > > step. > > > > > > > > > > - Brett > > > > > > > > > > > --------------------------------------------------------------------- > > > > > 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] > > > > > > > > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
