Hi I'm not that I understand what it is you want to do.
When you say you don't want to specify a version, do you mean for the Site Plugin or for the skin? The skin is not configured in the pom.xml file, but rather in a site.xml file. The site.xml file are inherited in the same way as pom.xml files are. So if you want some parts of the site.xml file in all of your projects, you put that site.xml in the same place as your corporate pom.xml. On 2010-09-13 11:11, Thomas Scheffler wrote: > Hi, > > I use the maven-site-plugin with a custom skin. I do not want to specify > the version in maven project. There is no way to store the the version > in a corporate pom.xml, as properties are not heritable. So I tent to > use the "latest release" resolving mechanism of the site plugin. > Unfortunately it does not resolve against configured repositories from > the pom.xml but always against "central". > > I'm using the latest version of maven-site-plugin. Is anybody on the > list, who has a custom site skin working with several maven projects? > The best way would be to have the skin configured at one central > corporate pom and nowhere else. > > regards > > Thomas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Dennis Lundberg --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
