You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2016/10/01 17:37:21 UTC

[jira] [Commented] (DOXIASITETOOLS-167) replace deprecated Maven 2 MavenProjectBuilder with Maven 3 ProjectBuilder

    [ https://issues.apache.org/jira/browse/DOXIASITETOOLS-167?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15538880#comment-15538880 ] 

Hudson commented on DOXIASITETOOLS-167:
---------------------------------------

SUCCESS: Integrated in Jenkins build doxia-all #297 (See [https://builds.apache.org/job/doxia-all/297/])
[DOXIASITETOOLS-166] mark DOXIASITETOOLS-167 TODO (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1763022])
* (edit) ./doxia-sitetools/doxia-integration-tools/src/main/java/org/apache/maven/doxia/tools/DefaultSiteTool.java


> replace deprecated Maven 2 MavenProjectBuilder with Maven 3 ProjectBuilder
> --------------------------------------------------------------------------
>
>                 Key: DOXIASITETOOLS-167
>                 URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-167
>             Project: Maven Doxia Sitetools
>          Issue Type: Task
>          Components: Integration Tools
>    Affects Versions: 1.7.1, 1.7.2
>            Reporter: Hervé Boutemy
>
> this will avoid issues with settings like DOXIASITETOOLS-166: the current workaround works by getting project from reactor when available, but when not available in reactor (for example because using "-N"), loading pom with MavenProjectBuilder won't properly interpolate values from settings



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)