Hi Hervé, Thanks very much for your help, that was the problem. I knew this problem existed for SCM urls, but I don't know why I assumed that project urls would not be affected.
I'm excited for MNG-5951, because that will reduce the boilerplate necessary to interact with GitHub and other git-based repositories. Many thanks, Elliot On Fri, Mar 11, 2016 at 2:50 AM, Hervé BOUTEMY <[email protected]> wrote: > yes, it is expected behaviour: see "inheritance assembly" step of model > builder [1] > > in your case, your config cause artifactId to be added twice: one on > project.url and one on site.url before ${project.url} is interpolated > > You should just not use ${project.url} in distributionManagement/site: > that's > what is causing you the issue > > > > Notice: this strategy (adding artifactId) was perfect for a good number of > years, when sites were deployed to filesystems: with sites deployed to > git, it > is known that it does not fit this case, and you're not the first to > complain > (without really understanding why "it does not work as expected" on your > case: > the important part here is *on your case*, because this git case is what > cause > some new requirements that did not exist before) > > I have prepared a new feature for (future) Maven 3.4.0 in MNG-5951 [2] > This will give attributes to disable artifactId addition on fields that > have > this url inheritance feature > > > HTH > > Regards, > > Hervé > > > [1] http://maven.apache.org/ref/3-LATEST/maven-model-builder/ > > [2] https://issues.apache.org/jira/browse/MNG-5951 > > Le jeudi 10 mars 2016 09:29:09 Elliot Metsger a écrit : > > Hi, > > > > I'm using the Maven site plugin with a multi-module build. The generated > > site is going to be deployed to GitHub, so I'm only using the Maven site > > plugin to generate and stage content locally, not deploy. > > > > I have a placeholder distributionManagement/site element in my POM so > that > > site:stage can generate links between the modules of my site. However, > my > > child modules are getting inexplicable values for their site url: > > > > Parent module distributionManagement/site (${project.url} = > > http://dataconservancy.github.io/package-ingest): > > > > <distributionManagement> > > <site> > > <id>github</id> > > <name>GitHub Pages Website</name> > > <url>${project.url}</url> > > </site> > > </distributionManagement> > > > > Parent module, help:effective-pom: > > <distributionManagement> > > <site> > > <id>github</id> > > <name>GitHub Pages Website</name> > > <url>http://dataconservancy.github.io/package-ingest</url> > > </site> > > </distributionManagement> > > > > So far, so good. However, the child module's > > distributionManagement/site/url is not what I expected. Notice that the > > child module name 'package-ingest-api' is repeated twice in the url: > > > > Child module, help:effective-pom (project url = > > http://dataconservancy.github.io/package-ingest/package-ingest-api/) > > <distributionManagement> > > <site> > > <id>github</id> > > <name>GitHub Pages Website</name> > > <url> > > > http://dataconservancy.github.io/package-ingest/package-ingest-api/package-i > > ngest-api </url> > > </site> > > </distributionManagement> > > > > Is this expected behavior? > > > > Thanks, > > Elliot > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
