You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@oozie.apache.org by "Hadoop QA (JIRA)" <ji...@apache.org> on 2011/09/08 06:49:09 UTC
[jira] [Created] (OOZIE-204) GH-246: Move build to use Maven 3, fix
issues in POMs
GH-246: Move build to use Maven 3, fix issues in POMs
-----------------------------------------------------
Key: OOZIE-204
URL: https://issues.apache.org/jira/browse/OOZIE-204
Project: Oozie
Issue Type: Bug
Reporter: Hadoop QA
Maven 3 is faster and it provides better error reporting.
Some documentation reports, dependencies, are broken and with Maven 2 it stops working in (what it seems) non-deterministic ways.
Move report definitions into the generateDocs profile to ensure no docs generation happens unless it is been activated.
Add a profile to include Hadoop JARs in the WAR (this was available via parameterization but parameterization is gone).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Closed] (OOZIE-204) GH-246: Move build to use Maven 3, fix
issues in POMs
Posted by "Roman Shaposhnik (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Roman Shaposhnik closed OOZIE-204.
----------------------------------
Resolution: Fixed
> GH-246: Move build to use Maven 3, fix issues in POMs
> -----------------------------------------------------
>
> Key: OOZIE-204
> URL: https://issues.apache.org/jira/browse/OOZIE-204
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Maven 3 is faster and it provides better error reporting.
> Some documentation reports, dependencies, are broken and with Maven 2 it stops working in (what it seems) non-deterministic ways.
> Move report definitions into the generateDocs profile to ensure no docs generation happens unless it is been activated.
> Add a profile to include Hadoop JARs in the WAR (this was available via parameterization but parameterization is gone).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] [Commented] (OOZIE-204) GH-246: Move build to use Maven 3,
fix issues in POMs
Posted by "Hadoop QA (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/OOZIE-204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13099886#comment-13099886 ]
Hadoop QA commented on OOZIE-204:
---------------------------------
tucu00 remarked:
Closed by daec997c2932e65b5e16599bdbe7d3dc2894019a Move build to use Maven 3, fix issues in POMs
Maven 3 is faster and it provides better error reporting.
Some documentation reports, dependencies, are broken and with Maven 2 it stops working in (what it seems) non-deterministic ways.
Moved report definitions into the generateDocs profile to ensure no docs generation happens unless it is been activated.
Added a profile to include Hadoop JARs in the WAR (this was available via parameterization but parameterization is gone).
Made all plugins to use pluginManagment.
Added enforcer plugin to ensure Maven 3 is being used, else fails.
> GH-246: Move build to use Maven 3, fix issues in POMs
> -----------------------------------------------------
>
> Key: OOZIE-204
> URL: https://issues.apache.org/jira/browse/OOZIE-204
> Project: Oozie
> Issue Type: Bug
> Reporter: Hadoop QA
>
> Maven 3 is faster and it provides better error reporting.
> Some documentation reports, dependencies, are broken and with Maven 2 it stops working in (what it seems) non-deterministic ways.
> Move report definitions into the generateDocs profile to ensure no docs generation happens unless it is been activated.
> Add a profile to include Hadoop JARs in the WAR (this was available via parameterization but parameterization is gone).
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira