gnodet commented on PR #1594: URL: https://github.com/apache/maven/pull/1594#issuecomment-2208381221
> > > Big question is now: Should the components in m-site-p rewritten to make things right? (for both Maven 3 and 4) > > > > > > Doxia 2.x can be used on Maven 3, right ? So if we fix it there, it may be sufficient, assuming we somehow force Maven 4 users to use m-site-p 4.x. Though I suppose once the work is done on Doxia 2.x, porting it to Doxia 1.x should not be too difficult... > > Given [apache/maven-doxia-sitetools#161](https://github.com/apache/maven-doxia-sitetools/pull/161), I assume the code does not build projects from local repository anymore. I need to check if m-site-p 4.x works correctly on Maven 4.0.0-beta-3 or not. It does not, because the new `DefaultSiteTools` relies on `MavenProject.getParent()` which returns a `MavenProject` with `getBasedir() == null` when the parent has been loaded from the local repository. We may want to change some semantics on the longer term, but for now, I don't think there's an easy way to work around the situation. I think we should use this PR to restore the behaviour for next 4.x release. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
