I'm trying to port a project over to Maven. We've been developing an
enterprise application in eclipse and have the following projects:
projectname-beans (all session beans and dependent classes)
projectname-entities (all jpa entities)
projectname-lib (all remote interfaces and dto objects)
projectname-client-api (the api that clients program against using dto)
projectname-core (the ear definition)
projectname-parent (the maven parent project)
currently I have just about everything working (i think). i can build,
test, and package just fine. i can even deploy the ear to glassfish using
the glassfish plugin but this is where i'm trying to make some improvements
to the build and coming up short...
directory structure:
projectname-parent/
projectname-beans/
projectname-entities/
projectname-lib/
projectname-client-api/
projectname-core/
beans, entities, lib, client-api, core are all <modules> or parent.
I'm trying to define the glassfish plugin in the parent pom and be able to
run: projectname-parent> mvn glassfish:deploy
and have it deploy the projectname-core.ear
after succesfully deploying the ear it then tries to run the
glassfish:deploy goal on each module (client-lib, api, beans, entites) which
fails. (well, actually deploy doesn't fail - it doesn't do anything...but
glassfish:undeploy does fail. in reality, the main problem is that
glassfish plugin is running against all modules)
how can I define a plugin in the parent that does not run against each child
module?
snip of parent pom:
<!-- parent pom snippet -->
<project>
...
<build>
<plugins>
<plugin>
<groupId>org.glassfish.maven.plugin</groupId>
<artifactId>maven-glassfish-plugin</artifactId>
<version>2.1</version>
<configuration>
<glassfishDirectory>${glassfish.home}</glassfishDirectory>
<domainDirectory>${dev.domain.dir}</domainDirectory>
<autoCreate>false</autoCreate>
<echo>false</echo>
<terse>false</terse>
<interactive>false</interactive>
<user>admin</user>
<passwordFile>${dev.domain.dir}/${dev.domain.name}/dev-domain-pw-file</passwordFile>
<domain>
<name>${dev.domain.name}</name>
<adminPort>4848</adminPort>
<httpPort>8080</httpPort>
<httpsPort>8443</httpsPort>
<iiopPort>3700</iiopPort>
<jmsPort>7676</jmsPort>
</domain>
<components>
<component>
<name>${projectname.core.name}</name>
<artifact>${projectname.core.name}/${project.build.directory}/${projectname.core.name}-${project.version}.ear</artifact>
</component>
</components>
</configuration>
</plugin>
</plugins>
</build>
...
</project>
--
View this message in context:
http://www.nabble.com/Limiting-Plugin-Inheritence-tp20778618p20778618.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
