[
https://issues.apache.org/jira/browse/MNG-8172?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17862983#comment-17862983
]
ASF GitHub Bot commented on MNG-8172:
-------------------------------------
michael-o commented on PR #1594:
URL: https://github.com/apache/maven/pull/1594#issuecomment-2208543807
> > 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...
I wouldn't put any effort into Doxia 1.x. Doxia 2.x is fully compatible with
Maven 3 and intended to be used with 3.6.3+. m-site-p will be available for
both Maven 3 and 4 with Doxia 2.x.
> Fix site building
> -----------------
>
> Key: MNG-8172
> URL: https://issues.apache.org/jira/browse/MNG-8172
> Project: Maven
> Issue Type: Bug
> Reporter: Guillaume Nodet
> Assignee: Guillaume Nodet
> Priority: Major
> Fix For: 4.0.0-beta-4
>
>
> Restore behaviour with MavenProject.getBasedir() == null for projects loaded
> from local repository.
> The maven-site-plugin relies on this behaviour and site building is broken if
> not.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
