Try using ${pom.parent.artifactId}
On 7/22/05, Darren Hartford <[EMAIL PROTECTED]> wrote:
> Hi Brett,
> Yup, I just installed the jpackaged version of maven1 (and after a
> little bit of tweaking to get it to work) tried this on FC2. It has the
> same results which means that at least I can rule out environmental.
>
> But, I did find it! It was in the subprojects project.xml and hopefully
> someone can point to the correct way of doing this:
>
> <groupId>${pom.groupId}_BUSINESSIMPL</groupId>
> <id>${pom.groupId}_BUSINESSIMPL</id>
> <description></description>
> <dependencies>
> <dependency>
> <groupId>${pom.groupId}</groupId>
> <artifactId>${pom.groupId}_DATA</artifactId>
> <version>${pom.currentVersion}</version>
> <type>ejb</type>
> <properties>
> <ear.bundle>true</ear.bundle>
> <cactus.bundle>true</cactus.bundle>
> </properties>
> </dependency>
>
>
>
>
> I have a master/project.xml that everything extends, and I was hoping to
> use {pom.groupId} in <groupId> as described above, but ALSO in getting a
> dependency built in a different subproject.
>
> The dependency tries to pull the LOCAL groupId instead of the
> master/project.xml since it got overridden. Is there a clean way to
> pull this off?
>
> -D
>
>
>
> > -----Original Message-----
> > From: Darren Hartford
> > Sent: Friday, July 22, 2005 10:10 AM
> > To: Maven Users List
> > Subject: [m1] obscure "Java heap memory" issue [urgent as one
> > can get for open source]
> >
> > Hey all,
> > Win2000, jdk5, tested with Maven 1.0.2 and maven 1.1-beta-1 issue:
> >
> > I have multiple projects that all work fine, but something
> > happened to only one project where I keep getting
> > "java.lang.OutOfMemoryError: Java heap space".
> >
> > Doing something as simple as 'maven -e clean' causes this
> > error, while other projects are fine. The -e produces no
> > extra output, nor does -X. MAVEN_OPTS just makes it run
> > longer until the heap space error with same output. All
> > goals on the same project all cause outofmemoryerrors.
> >
> > This project used to work fine, but then one day just keep
> > getting memory errors (I thought it was because I was running
> > a lot of apps, but even clean reboot on 1G ram/p4 still
> > happening). Not that big of a project, two ejb session beans
> > with webservices for deployment to jboss.
> >
> >
> > Any pointers on where I should look? Thanks, production
> > project that got 'stuck' because of the build tool :-(
> > -D
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Jamie Bisotti
Software Engineer
Lexmark International, Inc.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
