Don't call this a "super pom"! It's a parent (pom). There is only ONE Super-POM and it's part of Maven Core. Calling some other artifact a super-pom will only confuse people.
/Anders On Thu, Mar 29, 2012 at 02:47, Daivish Shah <[email protected]> wrote: > Hi, > > I am trying to use the super POM in my all of the project and seems like > PluginManagement doesn't work like this way. > > Super-Pom Project > > pom.xml > > <build> > <pluginManagement> > <plugins> > <plugin> > > > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-javadoc-plugin</artifactId> > <version>2.8.1</version> > </plugin> > </plugins> > </pluginManagement> > </build> > > > > Using Super POM in my other project as followed. > > pom.xml > > <parent> > <groupId>com.super</groupId> > <artifactId>super-pom</artifactId> > <version>0.0.1-SNAPSHOT</version> > </parent> > > <build> > <plugins> > <plugin> > > <groupId>org.apache.maven.plugins</groupId> > > <artifactId>maven-javadoc-plugin</artifactId> > > </plugin> > </plugins> > </build> > > > > When i try to use like this way compiler throws me WARNING/ERROR message > and looks like i have to apply VERSION ID again when i use any of the > plugin which is listed in my super POM Project. Which doesn't make sense to > declare PLUGIN things in my SUPER POM Project. > > > Any idea what's going on here ? Is that the way MAVEN designed or i am > doing something wrong here ? > > Thanks, > daivish. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
