[ANN] Apache Maven Reporting Exec 2.0.0-M14 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M14. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M14 ** Dependency upgrade * [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3 * [MSHARED-1404] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M15 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M15. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M15 ** Dependency upgrade * [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3 * [MSHARED-1397] - Bump org.apache.maven:maven-archiver from 3.6.1 to 3.6.2 * [MSHARED-1402] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M12. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M12 ** Dependency upgrade * [MSHARED-1392] - Upgrade to Parent 42 and Maven 3.6.3 * [MSHARED-1396] - Upgrade to Doxia 2.0.0-M11 * [MSHARED-1399] - Upgrade to Doxia 2.0.0-M12 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M13 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M13. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M13 ** Task * [MSHARED-1387] - Clean up dependencies ** Dependency upgrade * [MSHARED-1362] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M14 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M14. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M14 ** Dependency upgrade * [MSHARED-1348] - Upgrade plugins and components (in ITs) * [MSHARED-1361] - Upgrade plugins and components (in ITs) (2) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M11. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M11 ** Dependency upgrade * [MSHARED-1379] - Upgrade to Doxia 2.0.0-M10 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M10. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M10 ** Task * [MSHARED-1326] - Improve (documentation on) MavenReport interface/AbstractMavenReport class ** Dependency upgrade * [MSHARED-1349] - Upgrade to Doxia 2.0.0-M9 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M13 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M13. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M13 ** Improvement * [MSHARED-1327] - Change default value of output directory in AbstractMavenReport * [MSHARED-1343] - Make parameter outputDirectory read/write in AbstractMavenReport ** Dependency upgrade * [MSHARED-1342] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M12. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M12 ** Improvement * [MSHARED-1329] - Add field to MavenReportExecution whether it is user-defined or autodetected ** Dependency upgrade * [MSHARED-1334] - Upgrade to Parent 41 * [MSHARED-1335] - Upgrade to Maven Reporting API 4.0.0-M9 * [MSHARED-1337] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M12 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M12. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M12 ** Improvement * [MSHARED-1328] - Consistently log when skipping report goal execution ** Task * [MSHARED-1326] - Improve MavenReport interface/AbstractMavenReport class API ** Dependency upgrade * [MSHARED-1334] - Upgrade to Parent 41 * [MSHARED-1335] - Upgrade to Maven Reporting API 4.0.0-M9 * [MSHARED-1336] - Upgrade to Doxia Sitetools 2.0.0-M16 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M9. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M9 ** Task * [MSHARED-1326] - Improve (documentation on) MavenReport interface/AbstractMavenReport class ** Dependency upgrade * [MSHARED-1334] - Upgrade to Parent 41 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M11. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M11 ** Dependency upgrade * [MSHARED-1322] - Upgrade to Doxia 2.0.0-M8 * [MSHARED-1323] - Upgrade to Maven Reporting API 4.0.0-M8 * [MSHARED-1324] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M8. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M8 ** Dependency upgrade * [MSHARED-1316] - Upgrade to Parent 40 * [MSHARED-1317] - Upgrade to Doxia 2.0.0-M8 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M11 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M11. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M11 ** Improvement * [MSHARED-1314] - mark execute() final to avoid users extending reporting-impl implementation ** Dependency upgrade * [MSHARED-1318] - Upgrade to Doxia 2.0.0-M8 * [MSHARED-1319] - Upgrade to Doxia Sitetools 2.0.0-M13 * [MSHARED-1320] - Upgrade to Maven Reporting API 4.0.0-M8 * [MSHARED-1321] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M10. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M10 ** Bug * [MSHARED-1298] - Missing site report should be detected ** Dependency upgrade * [MSHARED-1310] - Upgrade to Parent 40 * [MSHARED-1311] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M10 released
The Apache Maven team is pleased to announce the release of the Maven
Reporting Impl version 4.0.0-M10.
https://maven.apache.org/shared/maven-reporting-impl/
Release Notes - Maven Shared Components - Version
maven-reporting-impl-4.0.0-M10
** Improvement
* [MSHARED-1295] - Have ${project.build.outputTimestamp} injected
as @Parameter
** Dependency upgrade
* [MSHARED-1308] - Upgrade to Parent 40
* [MSHARED-1309] - Upgrade to Doxia Sitetools 2.0.0-M12
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M9. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M9 ** Dependency upgrade * [MSHARED-1281] - Upgrade to Doxia 2.0.0-M7 * [MSHARED-1282] - Upgrade plugins and components (in ITs) * [MSHARED-1283] - Upgrade to Maven Reporting API 4.0.0-M7/Maven Reporting Impl 4.0.0-M9 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M9 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M9. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M9 ** Bug * [MSHARED-1275] - MavenReport#canGenerateReport() is invoked twice ** Dependency upgrade * [MSHARED-1277] - Upgrade plugins and components (in ITs) * [MSHARED-1278] - Upgrade to Doxia 2.0.0-M7 * [MSHARED-1279] - Upgrade to Maven Reporting API 4.0.0-M7 * [MSHARED-1280] - Upgrade to Doxia Sitetools 2.0.0-M11 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M7. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M7 ** Improvement * [MSHARED-193] - API change: let MavenReportRenderer#render() throw an exception * [MSHARED-1032] - API change: let MavenReport#canGenerateReport() throw an exception ** Dependency upgrade * [MSHARED-1276] - Upgrade to Doxia 2.0.0-M7 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M8. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M8 ** Dependency upgrade * [MSHARED-1245] - Upgrade to Doxia Sitetools 2.0.0-M10 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M8 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M8. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M8 ** Dependency upgrade * [MSHARED-1246] - Upgrade components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M7. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M7 ** Improvement * [MSHARED-1232] - Properly populate DocumentRenderingContext#generator when run in standalone mode ** Dependency upgrade * [MSHARED-1233] - Upgrade to Doxia Sitetools 2.0.0-M8 * [MSHARED-1234] - Upgrade to Maven Reporting API 4.0.0-M6 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M7 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M7. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M7 ** Improvement * [MSHARED-1236] - Supply execution id of caller (Maven Site Plugin) to MavenReportExecutorRequest ** Dependency upgrade * [MSHARED-1235] - Upgrade to Maven Reporting API 4.0.0-M6 * [MSHARED-1241] - Upgrade plugins and components in ITs * [MSHARED-1242] - Upgrade to Doxia Sitetools 2.0.0-M8 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M6. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M6 ** Task * [MSHARED-1231] - Remove unused default-report.xml file Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M6. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M6 ** Dependency upgrade * [MSHARED-1222] - Upgrade to Doxia Sitetools 2.0.0-M7 * [MSHARED-1223] - Upgrade to Maven Reporting Impl 4.0.0-M6 in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M6 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M6. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M6 ** Dependency upgrade * [MSHARED-1221] - Upgrade to Doxia Sitetools 2.0.0-M7 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M5 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M5. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M5 ** Dependency upgrade * [MSHARED-1209] - Upgrade plugins and components * [MSHARED-1210] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M6 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M5 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M5. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M5 ** Task * [MSHARED-1207] - Deprecate MavenReportExecutorRequest#localRepository ** Dependency upgrade * [MSHARED-1208] - Upgrade plugins and components (in ITs) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M5 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M5. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M5 ** Dependency upgrade * [MSHARED-1206] - Upgrade to Doxia 2.0.0-M6 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M4 released
The Apache Maven team is pleased to announce the release of the Maven
Reporting Impl version 4.0.0-M4.
https://maven.apache.org/shared/maven-reporting-impl/
Release Notes - Maven Shared Components - Version
maven-reporting-impl-4.0.0-M4
** New Feature
* [MSHARED-1168] - Add support for markup output
* [MSHARED-1185] - Introduce
AbstractMavenReportRenderer#verbatimSource()
** Improvement
* [MSHARED-480] - Use maven-site-plugin's site.xml to use site's
skin instead of default when run as mojo
* [MSHARED-1174] - Don't wrap elements in anchors
* [MSHARED-1181] - Populate SiteRenderingContext#getPublishDate()
with ${project.build.outputTimestamp}
* [MSHARED-1182] - Drop incorrect usage of SinkEventAttributeSet#BOXED
* [MSHARED-1183] - Don't pass implied args to
AbstractMavenReportRenderer#startTable()
* [MSHARED-1184] - Drop unnecessary use of type attribute with
JavaScript
** Dependency upgrade
* [MSHARED-1186] - Upgrade Parent to 39
* [MSHARED-1187] - Upgrade to Doxia 2.0.0-M5
* [MSHARED-1188] - Upgrade to Maven Reporting API 4.0.0-M4
* [MSHARED-1189] - Upgrade plugins and components in ITs
* [MSHARED-1194] - Upgrade to Doxia Sitetools 2.0.0-M5
Enjoy,
-The Apache Maven team
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M4 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M4. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M4 ** Task * [MSHARED-1193] - Remove Maven 2 compat code ** Dependency upgrade * [MSHARED-1180] - Upgrade Parent to 39 * [MSHARED-1190] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M5 * [MSHARED-1191] - Upgrade Maven Reporting API to 4.0.0-M4 * [MSHARED-1192] - Upgrade plugins in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M4 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M4. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M4 ** Dependency upgrade * [MSHARED-1177] - Upgrade to Maven Parent 39 * [MSHARED-1178] - Upgrade to Doxia 2.0.0-M5 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M3 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M3. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M3 ** Improvement * [MSHARED-1106] - Improve and simplify section handling ** Dependency upgrade * [MSHARED-1133] - Switch to JUnit 5 and drop junit-addons * [MSHARED-1160] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 * [MSHARED-1162] - Upgrade Plexus Utils to 3.5.0 * [MSHARED-1165] - Upgrade plugins and components in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M3 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M3. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M3 ** Dependency upgrade * [MSHARED-1163] - Upgrade Maven Reporting API to 4.0.0-M3 * [MSHARED-1164] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M4 * [MSHARED-1166] - Upgrade Plexus Utils to 3.5.0 * [MSHARED-1167] - Upgrade plugins in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M3 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M3. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M3 ** Task * [MSHARED-1159] - Require locale to be not null ** Dependency upgrade * [MSHARED-1161] - Upgrade Doxia to 2.0.0-M4 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 3.2.0 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 3.2.0. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-3.2.0 ** Improvement * [MSHARED-1099] - Render with a skin when report is run in standalone mode ** Dependency upgrade * [MSHARED-1120] - Upgrade Maven Reporting API to 3.1.1 * [MSHARED-1121] - Upgrade plugins and components in project and ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 3.1.1 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 3.1.1. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-3.1.1 ** Task * [MSHARED-1118] - Restore binary compat for MavenReport (partially revert MSHARED-1024) Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M2 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M2. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M2 ** Task * [MSHARED-1105] - Replace Plexus Annotations with JSR 330 and upgrade relevant dependencies ** Dependency upgrade * [MSHARED-1100] - Upgrade Maven Parent to 36 * [MSHARED-1101] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M3 * [MSHARED-1102] - Upgrade plugins and components in ITs * [MSHARED-1103] - Upgrade Maven Reporting API to 4.0.0-M2 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M2 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M2. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M2 ** New Feature * [MSHARED-390] - Add startSection method AbstractMavenReportRenderer where anchor != name ** Improvement * [MSHARED-1099] - Render with a skin when report is run in standalone mode ** Dependency upgrade * [MSHARED-1093] - Upgrade Maven Parent to 36 * [MSHARED-1094] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M3 * [MSHARED-1095] - Upgrade plugins and components in ITs * [MSHARED-1096] - Upgrade Maven Reporting API to 4.0.0-M2 * [MSHARED-1097] - Update dependencies Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API 4.0.0-M2 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M2. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M2 ** Dependency upgrade * [MSHARED-1091] - Upgrade Maven Parent to 36 and Maven to 3.2.5 * [MSHARED-1092] - Upgrade to Doxia 2.0.0-M3 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 2.0.0-M1 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 2.0.0-M1. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-2.0.0-M1 ** Task * [MSHARED-1060] - Upgrade to Java 8 * [MSHARED-1061] - Replace Plexus Logger with SLF4J * [MSHARED-1064] - Reintroduce org.codehaus.doxia.sink.Sink ** Dependency upgrade * [MSHARED-1062] - Upgrade Maven Reporting API to 4.0.0-M1 * [MSHARED-1063] - Upgrade to Doxia Sitetools to 2.0.0-M2 * [MSHARED-1065] - Upgrade plugins and components in UTs and ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl 4.0.0-M1 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 4.0.0-M1. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-4.0.0-M1 ** Task * [MSHARED-1055] - Upgrade to Java 8 ** Dependency upgrade * [MSHARED-1056] - Upgrade to Maven 3.2.5 * [MSHARED-1057] - Upgrade to Doxia/Doxia Sitetools to 2.0.0-M2 * [MSHARED-1058] - Upgrade components * [MSHARED-1059] - Upgrade Maven Reporting API to 4.0.0-M1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API version 4.0.0-M1 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 4.0.0-M1. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-4.0.0-M1 ** Dependency upgrade * [MSHARED-1052] - Upgrade to Java 8 * [MSHARED-1053] - Upgrade Doxia to 2.0.0-M2 * [MSHARED-1054] - Upgrade plugins Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec version 1.6.0 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Exec version 1.6.0. https://maven.apache.org/shared/maven-reporting-exec/ Release Notes - Maven Shared Components - Version maven-reporting-exec-1.6.0 ** Bug * [MSHARED-927] - javadoc failing with JDK 8 ** Task * [MSHARED-1029] - Update component (requires Maven 3.2.5+) ** Dependency upgrade * [MSHARED-1025] - Upgrade Doxia Sitetools to 1.11.1 * [MSHARED-1026] - Upgrade Maven Reporting API to 3.1.0 * [MSHARED-1034] - Upgrade plugins and components in ITs Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Impl version 3.1.0 released
The Apache Maven team is pleased to announce the release of the Maven Reporting Impl version 3.1.0. https://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl-3.1.0 ** Improvement * [MSHARED-813] - Require Java 7 * [MSHARED-879] - make build Reproducible ** Dependency upgrade * [MSHARED-956] - Set minimum supported Maven version to 3.1.0 * [MSHARED-1027] - Update Doxia to 1.11.1 and Doxia Sitetools to 1.11.1 * [MSHARED-1028] - Upgrade Maven Reporting API to 3.1.0 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting API version 3.1.0 released
The Apache Maven team is pleased to announce the release of the Maven Reporting API version 3.1.0. https://maven.apache.org/shared/maven-reporting-api/ Release Notes - Maven Shared Components - Version maven-reporting-api-3.1.0 ** Improvement * [MSHARED-812] - Require Java 7 * [MSHARED-879] - make build Reproducible ** Task * [MSHARED-1024] - Replace deprecated code ** Dependency upgrade * [MSHARED-844] - Upgrade to Doxia 1.11.1 Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Exec 1.5.1 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Reporting Exec, version 1.5.1 This component provides an API to prepare report plugins execution with Maven 3. https://maven.apache.org/shared/maven-reporting-exec/ You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-reporting-exec/download.cgi Release Notes - Maven Shared Components - Version maven-reporting-exec-1.5.1 ** Bug * [MSHARED-923] - upgrade maven-shade-plugin to 3.2.4 to get Reproducible Build * [MSHARED-924] - fix Xpp3DomUtils shading relocation * [MSHARED-921] - NoSuchMethodError: 'Xpp3Dom.getInputLocation()' with Maven versions < 3.6.1 ** Improvement * [MSHARED-814] - Require Java 7 * [MSHARED-879] - make build Reproducible ** Task * [MSHARED-663] - mark ReportPlugin and ReportSet package private Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Reporting Executor 1.4 Released
The Maven team is pleased to announce the release of the Apache Maven Reporting Executor, version 1.4 Classes to manage report plugin executions with Maven 3. https://maven.apache.org/shared/maven-reporting-exec/ You should specify the version in your project's dependency configuration: org.apache.maven.shared maven-reporting-exec 1.4 Release Notes - Apache Maven Reporting Executor - Version 1.4 Bug * [MSHARED-616] Dependencies inside pluginManagement are not taken into account in reporting Improvement * [MSHARED-647] display what reports are added automatically when no reportSet is defined * [MSHARED-628] support maven-model ReportPlugin in addition to local copy Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Reporting Impl Version 3.0.0 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Reporting Implementation 3.0.0 https://maven.apache.org/shared/maven-reporting-impl/ You should specify the version in your project: org.apache.maven.reporting maven-reporting-impl 3.0.0 You can download the appropriate sources etc. from the download page: https://maven.apache.org/shared/maven-reporting-impl/download.cgi Release Notes Maven Reporting Impl 3.0.0 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922=12332979 Bugs: * [MSHARED-392] - AbstractMavenReportRenderer#applyPattern(String) chokes on some specific input and produces useless segments * [MSHARED-489] - AbstractMavenReportRenderer#linkPatternedText ignores name if href is invalid * [MSHARED-608] - Remove index.html-adding block in AbstractMavenReportRenderer#getValidHref() Improvements: * [MSHARED-430] - Update JDK requirement to 1.6 / upgrade Maven Core dependencies to 3.0 * [MSHARED-582] - Upgrade maven-shared-components parent to version 30 * [MSHARED-583] - Make three digit version number * [MSHARED-642] - Upgrade to maven-shared-utils 3.2.0 Tasks: * [MSHARED-606] - Upgrade to Commons Validator 1.5.1 * [MSHARED-609] - Partially revert MSHARED-429 * [MSHARED-611] - Drop any href validation and pass as-is * [MSHARED-612] - Upgrade to Doxia 1.7 * [MSHARED-613] - Upgrade to Doxia Sitetools 1.7.4 * [MSHARED-614] - Upgrade to Maven Shared Utils 3.1.0 Wish: * [MSHARED-488] - Make input source file encoding default to platform encoding Enjos, -The Apache Maven team Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Reporting Implementation version 2.3
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Reporting Implementation, version 2.3 This component provides abstract classes to manage report generation, which can be run both: - as part of a site generation, as a maven-reporting-api's MavenReport, - or as a direct standalone goal invocation, as a maven-plugin-api's Mojo http://maven.apache.org/shared/maven-reporting-impl/ You should specify the dependency in your project's dependency configuration: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-reporting-impl/artifactId version2.3/version /dependency Release Notes - Maven Shared Components - Version maven-reporting-impl-2.3 ** Sub-task * [MSHARED-240] - Port maven-reporting-impl to maven-shared-utils ** Bug * [MSHARED-328] - use @parameter default-value instead of @parameter expression in sample * [MSHARED-346] - missing properties usually set by m-site-p (outputEncoding, ...) ** Improvement * [MSHARED-348] - support reporting encoding configuration when used as goal ** New Feature * [MSHARED-347] - use plugin-tools java 5 annotations to avoid fields copy/paste when implementing Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: File lock problem in custom Maven Reporting Plugin
Hi Olivier,
I've created a JIRA issue here
http://jira.codehaus.org/browse/MSHARED-269with two project used to
reproduce the problem.
Thanks for the help guys,
Baptiste
2012/12/19 Olivier Lamy ol...@apache.org
Can you create a jira entry with a sample ?
2012/12/18 Baptiste Gaillard baptiste.gaill...@gomoob.com:
Hi and thanks for the response,
My Mojo already overwrites the isExternalReport() function and returns
true
into it.
To deep a little more I've tried to debug the execution of the Mojo when
running a 'mvn site' command using that Mojo.
It seems that the function 'executeReport' associated to a reporting Mojo
is called before 'isExternalReport' is used.
The 'execute' method associated to the 'AbstractMavenReport' (I'm using
'maven-reporting-impl' version 2.2) class contains the following lines
:
Writer writer = null;
try
{
File outputDirectory = new File( getOutputDirectory() );
String filename = getOutputName() + .html;
Locale locale = Locale.getDefault();
SiteRenderingContext siteContext = new
SiteRenderingContext();
siteContext.setDecoration( new DecorationModel() );
siteContext.setTemplateName(
org/apache/maven/doxia/siterenderer/resources/default-site.vm );
siteContext.setLocale( locale );
RenderingContext context = new RenderingContext(
outputDirectory, filename );
SiteRendererSink sink = new SiteRendererSink( context );
generate( sink, null, locale );
...
The 'generate' function then calls the reporting mojo 'executeReport'
function, so I think my locking problems comes from one of the following
calls :
- 'new RenderingContext'
- 'new SiteRendererSink'
Do you have any other ideas ?
Perhaps I should post this message on the developer Mailing List, my
problems seems to be linked to what Maven (or the 'maven-reporting-impl
plugin executes internally ?
Thanks,
Baptiste
2012/12/16 Robert Scholte rfscho...@apache.org
This is probably what you need:
from org.apache.maven.reporting.**MavenReport.isExternalReport()
/**
* An external report is a report which calls a third party program
which generates some reports too.
* A good example is javadoc tool.
*
* @return tttrue/tt if this report is external, ttfalse/tt
otherwise.
* Default should be ttfalse/tt.
*/
boolean isExternalReport();
Op Tue, 11 Dec 2012 23:42:43 +0100 schreef Baptiste Gaillard
baptiste.gaill...@gomoob.com**:
Hi, I'm currently creating a new Maven Reporting Plugin which
integrate an
external tool used to generate a Javascript documentation in my Maven
Web
Site.
My report Mojo is very simple and is declared using :
/**
* @goal jsduck
* @phase site
*/
public class JSDuckReportMojo extends AbstractMavenReport {
...
}
I encounter a file locking problem (i.e already opened elsewhere and
not
closed) at the beginning of my 'executeReport' method :
*
protected void executeReport(Locale locale) throws
MavenReportException {
// JSDuck creates an 'index.html' file itself and crashes if one
file
with this name already exist
File jsduckIndex = new File(target/site/jsduck/**index.html);
if (jsduckIndex.exists() !jsduckIndex.delete()) {
throw new MavenReportException(Fail to delete the previously
generated index.html !
);
}
// Use a document generator which absolutly need to have an empty
target directory
...
}
*
The tool I'm integrating is called 'jsduck' and absolutely needs to
have
an
empty target directory to work, its root index file is called
'index.html'.
So I've also implemented the 'getOutputName' function :
public String getOutputName() {
return jsduck/index;
}
But, the file 'target/site/jsduck/index.**html' has already been
created
automagically by Maven.
In the 'executeReport' this file is there, empty and locked !
So, I can't delete this 'index.html' file and let JSDuck create itself
:-(
Is it normal that Maven locks this 'index.html' file (because it has
been
declared in the 'getOutputName()' ) ?
How can I unlock this file inside the 'executeReport' function to let
JSDuck generate my documentation ?
I've already tried to debug the 'AbstractMavenReport' class and only
found
a 'PrintWriter' attached to the 'Sink' (in the 'execute' method) which
could cause this locking problem.
Calling the 'close' method at the beginning of the 'executeReport'
method
seems to have no effect...
Thanks for you help,
Baptiste
--**--**-
To unsubscribe, e-mail: users-unsubscribe@maven.**apache.org
users-unsubscr...@maven.apache.org
For additional commands, e
Re: File lock problem in custom Maven Reporting Plugin
Can you create a jira entry with a sample ?
2012/12/18 Baptiste Gaillard baptiste.gaill...@gomoob.com:
Hi and thanks for the response,
My Mojo already overwrites the isExternalReport() function and returns true
into it.
To deep a little more I've tried to debug the execution of the Mojo when
running a 'mvn site' command using that Mojo.
It seems that the function 'executeReport' associated to a reporting Mojo
is called before 'isExternalReport' is used.
The 'execute' method associated to the 'AbstractMavenReport' (I'm using
'maven-reporting-impl' version 2.2) class contains the following lines :
Writer writer = null;
try
{
File outputDirectory = new File( getOutputDirectory() );
String filename = getOutputName() + .html;
Locale locale = Locale.getDefault();
SiteRenderingContext siteContext = new SiteRenderingContext();
siteContext.setDecoration( new DecorationModel() );
siteContext.setTemplateName(
org/apache/maven/doxia/siterenderer/resources/default-site.vm );
siteContext.setLocale( locale );
RenderingContext context = new RenderingContext(
outputDirectory, filename );
SiteRendererSink sink = new SiteRendererSink( context );
generate( sink, null, locale );
...
The 'generate' function then calls the reporting mojo 'executeReport'
function, so I think my locking problems comes from one of the following
calls :
- 'new RenderingContext'
- 'new SiteRendererSink'
Do you have any other ideas ?
Perhaps I should post this message on the developer Mailing List, my
problems seems to be linked to what Maven (or the 'maven-reporting-impl
plugin executes internally ?
Thanks,
Baptiste
2012/12/16 Robert Scholte rfscho...@apache.org
This is probably what you need:
from org.apache.maven.reporting.**MavenReport.isExternalReport()
/**
* An external report is a report which calls a third party program
which generates some reports too.
* A good example is javadoc tool.
*
* @return tttrue/tt if this report is external, ttfalse/tt
otherwise.
* Default should be ttfalse/tt.
*/
boolean isExternalReport();
Op Tue, 11 Dec 2012 23:42:43 +0100 schreef Baptiste Gaillard
baptiste.gaill...@gomoob.com**:
Hi, I'm currently creating a new Maven Reporting Plugin which integrate an
external tool used to generate a Javascript documentation in my Maven Web
Site.
My report Mojo is very simple and is declared using :
/**
* @goal jsduck
* @phase site
*/
public class JSDuckReportMojo extends AbstractMavenReport {
...
}
I encounter a file locking problem (i.e already opened elsewhere and not
closed) at the beginning of my 'executeReport' method :
*
protected void executeReport(Locale locale) throws MavenReportException {
// JSDuck creates an 'index.html' file itself and crashes if one file
with this name already exist
File jsduckIndex = new File(target/site/jsduck/**index.html);
if (jsduckIndex.exists() !jsduckIndex.delete()) {
throw new MavenReportException(Fail to delete the previously
generated index.html !
);
}
// Use a document generator which absolutly need to have an empty
target directory
...
}
*
The tool I'm integrating is called 'jsduck' and absolutely needs to have
an
empty target directory to work, its root index file is called
'index.html'.
So I've also implemented the 'getOutputName' function :
public String getOutputName() {
return jsduck/index;
}
But, the file 'target/site/jsduck/index.**html' has already been created
automagically by Maven.
In the 'executeReport' this file is there, empty and locked !
So, I can't delete this 'index.html' file and let JSDuck create itself :-(
Is it normal that Maven locks this 'index.html' file (because it has been
declared in the 'getOutputName()' ) ?
How can I unlock this file inside the 'executeReport' function to let
JSDuck generate my documentation ?
I've already tried to debug the 'AbstractMavenReport' class and only found
a 'PrintWriter' attached to the 'Sink' (in the 'execute' method) which
could cause this locking problem.
Calling the 'close' method at the beginning of the 'executeReport' method
seems to have no effect...
Thanks for you help,
Baptiste
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
*Baptiste GAILLARD*
*Mobile : +33(6) 85 12 81 26 http://+33%286%29%2085%2012%2081%2026%20/*
*Mail :* *baptiste.gaill...@gomoob.com*
*http://www.gomoob.com*
*
*
**
*
*
--
Olivier Lamy
Talend: http://coders.talend.com
http://twitter.com/olamy | http://linkedin.com/in/olamy
Re: File lock problem in custom Maven Reporting Plugin
Hi and thanks for the response,
My Mojo already overwrites the isExternalReport() function and returns true
into it.
To deep a little more I've tried to debug the execution of the Mojo when
running a 'mvn site' command using that Mojo.
It seems that the function 'executeReport' associated to a reporting Mojo
is called before 'isExternalReport' is used.
The 'execute' method associated to the 'AbstractMavenReport' (I'm using
'maven-reporting-impl' version 2.2) class contains the following lines :
Writer writer = null;
try
{
File outputDirectory = new File( getOutputDirectory() );
String filename = getOutputName() + .html;
Locale locale = Locale.getDefault();
SiteRenderingContext siteContext = new SiteRenderingContext();
siteContext.setDecoration( new DecorationModel() );
siteContext.setTemplateName(
org/apache/maven/doxia/siterenderer/resources/default-site.vm );
siteContext.setLocale( locale );
RenderingContext context = new RenderingContext(
outputDirectory, filename );
SiteRendererSink sink = new SiteRendererSink( context );
generate( sink, null, locale );
...
The 'generate' function then calls the reporting mojo 'executeReport'
function, so I think my locking problems comes from one of the following
calls :
- 'new RenderingContext'
- 'new SiteRendererSink'
Do you have any other ideas ?
Perhaps I should post this message on the developer Mailing List, my
problems seems to be linked to what Maven (or the 'maven-reporting-impl
plugin executes internally ?
Thanks,
Baptiste
2012/12/16 Robert Scholte rfscho...@apache.org
This is probably what you need:
from org.apache.maven.reporting.**MavenReport.isExternalReport()
/**
* An external report is a report which calls a third party program
which generates some reports too.
* A good example is javadoc tool.
*
* @return tttrue/tt if this report is external, ttfalse/tt
otherwise.
* Default should be ttfalse/tt.
*/
boolean isExternalReport();
Op Tue, 11 Dec 2012 23:42:43 +0100 schreef Baptiste Gaillard
baptiste.gaill...@gomoob.com**:
Hi, I'm currently creating a new Maven Reporting Plugin which integrate an
external tool used to generate a Javascript documentation in my Maven Web
Site.
My report Mojo is very simple and is declared using :
/**
* @goal jsduck
* @phase site
*/
public class JSDuckReportMojo extends AbstractMavenReport {
...
}
I encounter a file locking problem (i.e already opened elsewhere and not
closed) at the beginning of my 'executeReport' method :
*
protected void executeReport(Locale locale) throws MavenReportException {
// JSDuck creates an 'index.html' file itself and crashes if one file
with this name already exist
File jsduckIndex = new File(target/site/jsduck/**index.html);
if (jsduckIndex.exists() !jsduckIndex.delete()) {
throw new MavenReportException(Fail to delete the previously
generated index.html !
);
}
// Use a document generator which absolutly need to have an empty
target directory
...
}
*
The tool I'm integrating is called 'jsduck' and absolutely needs to have
an
empty target directory to work, its root index file is called
'index.html'.
So I've also implemented the 'getOutputName' function :
public String getOutputName() {
return jsduck/index;
}
But, the file 'target/site/jsduck/index.**html' has already been created
automagically by Maven.
In the 'executeReport' this file is there, empty and locked !
So, I can't delete this 'index.html' file and let JSDuck create itself :-(
Is it normal that Maven locks this 'index.html' file (because it has been
declared in the 'getOutputName()' ) ?
How can I unlock this file inside the 'executeReport' function to let
JSDuck generate my documentation ?
I've already tried to debug the 'AbstractMavenReport' class and only found
a 'PrintWriter' attached to the 'Sink' (in the 'execute' method) which
could cause this locking problem.
Calling the 'close' method at the beginning of the 'executeReport' method
seems to have no effect...
Thanks for you help,
Baptiste
--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
*Baptiste GAILLARD*
*Mobile : +33(6) 85 12 81 26 http://+33%286%29%2085%2012%2081%2026%20/*
*Mail :* *baptiste.gaill...@gomoob.com*
*http://www.gomoob.com*
*
*
**
*
*
Re: File lock problem in custom Maven Reporting Plugin
This is probably what you need:
from org.apache.maven.reporting.MavenReport.isExternalReport()
/**
* An external report is a report which calls a third party program
which generates some reports too.
* A good example is javadoc tool.
*
* @return tttrue/tt if this report is external, ttfalse/tt
otherwise.
* Default should be ttfalse/tt.
*/
boolean isExternalReport();
Op Tue, 11 Dec 2012 23:42:43 +0100 schreef Baptiste Gaillard
baptiste.gaill...@gomoob.com:
Hi, I'm currently creating a new Maven Reporting Plugin which integrate
an
external tool used to generate a Javascript documentation in my Maven Web
Site.
My report Mojo is very simple and is declared using :
/**
* @goal jsduck
* @phase site
*/
public class JSDuckReportMojo extends AbstractMavenReport {
...
}
I encounter a file locking problem (i.e already opened elsewhere and not
closed) at the beginning of my 'executeReport' method :
*
protected void executeReport(Locale locale) throws MavenReportException {
// JSDuck creates an 'index.html' file itself and crashes if one file
with this name already exist
File jsduckIndex = new File(target/site/jsduck/index.html);
if (jsduckIndex.exists() !jsduckIndex.delete()) {
throw new MavenReportException(Fail to delete the previously
generated index.html !
);
}
// Use a document generator which absolutly need to have an empty
target directory
...
}
*
The tool I'm integrating is called 'jsduck' and absolutely needs to have
an
empty target directory to work, its root index file is called
'index.html'.
So I've also implemented the 'getOutputName' function :
public String getOutputName() {
return jsduck/index;
}
But, the file 'target/site/jsduck/index.html' has already been created
automagically by Maven.
In the 'executeReport' this file is there, empty and locked !
So, I can't delete this 'index.html' file and let JSDuck create itself
:-(
Is it normal that Maven locks this 'index.html' file (because it has been
declared in the 'getOutputName()' ) ?
How can I unlock this file inside the 'executeReport' function to let
JSDuck generate my documentation ?
I've already tried to debug the 'AbstractMavenReport' class and only
found
a 'PrintWriter' attached to the 'Sink' (in the 'execute' method) which
could cause this locking problem.
Calling the 'close' method at the beginning of the 'executeReport' method
seems to have no effect...
Thanks for you help,
Baptiste
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
File lock problem in custom Maven Reporting Plugin
Hi, I'm currently creating a new Maven Reporting Plugin which integrate an
external tool used to generate a Javascript documentation in my Maven Web
Site.
My report Mojo is very simple and is declared using :
/**
* @goal jsduck
* @phase site
*/
public class JSDuckReportMojo extends AbstractMavenReport {
...
}
I encounter a file locking problem (i.e already opened elsewhere and not
closed) at the beginning of my 'executeReport' method :
*
protected void executeReport(Locale locale) throws MavenReportException {
// JSDuck creates an 'index.html' file itself and crashes if one file
with this name already exist
File jsduckIndex = new File(target/site/jsduck/index.html);
if (jsduckIndex.exists() !jsduckIndex.delete()) {
throw new MavenReportException(Fail to delete the previously
generated index.html !
);
}
// Use a document generator which absolutly need to have an empty
target directory
...
}
*
The tool I'm integrating is called 'jsduck' and absolutely needs to have an
empty target directory to work, its root index file is called 'index.html'.
So I've also implemented the 'getOutputName' function :
public String getOutputName() {
return jsduck/index;
}
But, the file 'target/site/jsduck/index.html' has already been created
automagically by Maven.
In the 'executeReport' this file is there, empty and locked !
So, I can't delete this 'index.html' file and let JSDuck create itself :-(
Is it normal that Maven locks this 'index.html' file (because it has been
declared in the 'getOutputName()' ) ?
How can I unlock this file inside the 'executeReport' function to let
JSDuck generate my documentation ?
I've already tried to debug the 'AbstractMavenReport' class and only found
a 'PrintWriter' attached to the 'Sink' (in the 'execute' method) which
could cause this locking problem.
Calling the 'close' method at the beginning of the 'executeReport' method
seems to have no effect...
Thanks for you help,
Baptiste
[ANN] Maven Reporting Executor 1.0.2 Released
The Maven team is pleased to announce the release of the Maven Reporting Executor, version 1.0.2 Classes to manage report plugin executions with Maven 3. http://maven.apache.org/shared/maven-reporting-exec You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-reporting-exec/artifactId version1.0.2/version /dependency Release Notes - Maven Reporting Executor - Version 1.0.2 Bug * [MSHARED-219] Maven3 LinkageError in maven report Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Implementation 2.2 Released
The Maven team is pleased to announce the release of the Maven Reporting Implementation, version 2.2 Abstract classes to manage report generation. http://maven.apache.org/shared/maven-reporting-impl You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.shared/groupId artifactIdmaven-reporting-impl/artifactId version2.2/version /dependency Release Notes - Maven Reporting Implementation - Version 2.2 Bug * [MSHARED-105] StringIndexOutOfBoundsException in AbstractMavenReportRenderer.applyPattern Improvement * [MSHARED-222] Update the dependency on commons-validator * [MSHARED-204] AbstractMavenReport should check isExternalReport() before trying to output a Doxia document Task * [MSHARED-159] remove [WARNING] Deprecated API called - not org.apache.maven.doxia.sink.Sink instance and no SinkFactory available. Please update this plugin. Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Exec 1.0.1 Released
The Maven team is pleased to announce the release of the Maven Reporting Exec, version 1.0.1 This component contains classes to manage report plugin executions with Maven 3. http://maven.apache.org/shared/maven-reporting-exec/ You should specify the version in your project's configuration: dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-exec/artifactId version1.0.1/version /dependency Release Notes - Maven Shared Components - Version maven-reporting-exec-1.0.1 ** Bug * [MSHARED-201] - order of reports is not preserved Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven reporting plugins do not execute if a unit test failure occurs
Using the latest version (2.6) of maven-surefire-report-plugin in the reporting section of Maven 2.2.1 does not execute if there is a unit test failure. I can't get any of the plugins in the reporting section of Maven to execute if there is a unit test failure. I found that I can set maven.test.failure.ignore=true here - http://jira.codehaus.org/browse/SUREFIRE-247 The problem to this approach is now our hudson builds are successful even if there are unit test failures. I tried to set the reporting plugin maven-surefire-report-plugin to run with the build plugins on a phase but I can't figure out how to get this to work. Is this a valid approach? How can I get the Maven reporting plugins to execute if a unit test failure occurs? Vincen Collins
Maven reporting plugins do not execute if a unit test failure occurs
Using the latest version (2.6) of maven-surefire-report-plugin in the reporting section of Maven 2.2.1 does not execute if there is a unit test failure. I can't get any of the plugins in the reporting section of Maven to execute if there is a unit test failure. I found that I can set maven.test.failure.ignore=true here - http://jira.codehaus.org/browse/SUREFIRE-247 The problem to this approach is now our hudson builds are successful even if there are unit test failures. I tried to set the reporting plugin maven-surefire-report-plugin to run with the build plugins on a phase but I can't figure out how to get this to work. Is this a valid approach? How can I get the Maven reporting plugins to execute if a unit test failure occurs? Vincen Collins
[ANN] Maven Reporting API version 3.0 and Maven Reporting Implementation 2.0.5 + 2.1 Released
The Maven team is pleased to announce the release of the Maven Reporting API version 3.0 and Maven Reporting Implementation 2.0.5 + 2.1. Maven Reporting API version 3.0 is the reporting API version decoupled from Maven core version: every reporting plugin should update its dependency to this version. http://maven.apache.org/shared/maven-reporting-api http://maven.apache.org/shared/maven-reporting-impl Release Notes - Maven Shared Components - Version maven-reporting-api 3.0 ** Improvement * [MSHARED-149] - add MavenMultiPageReport to maven-reporting-api Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.5 ** Improvement * [MSHARED-151] - upgrade maven-reporting-api to 3.0 (decoupled from Maven core version) ** Task * [MSHARED-152] - change svn branch to maven-reporting-impl-2.0.x Release Notes - Maven Shared Components - Version maven-reporting-impl 2.1 ** Bug * [MSHARED-120] - No single report generated with latest maven-reporting- impl ** Improvement * [MSHARED-151] - upgrade maven-reporting-api to 3.0 (decoupled from Maven core version) ** Task * [MSHARED-107] - Update to Doxia 1.1.1 * [MSHARED-119] - Review the Doxia Sink calls Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Impl 2.0.4.3 Released
The Maven team is pleased to announce the release of the Maven Reporting Impl, version 2.0.4.3. This shared component contains abstract classes to manage report generation.. http://maven.apache.org/shared/maven-reporting-impl/ Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.4.3 ** Bug * [MSHARED-120] - No single report generated with latest maven-reporting-impl Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Reporting Implementation 2.0.4.2 Released
EJ Ciramella wrote: Woah - a four digit build number? Is this now supported in maven 2 (wrt ranges and such)? Don't know. I was just following the versioning scheme used in the last release. -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Fri 7/24/2009 2:54 AM To: annou...@maven.apache.org; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Reporting Implementation 2.0.4.2 Released The Maven team is pleased to announce the release of the Maven Reporting Implementation, version 2.0.4.2 This shared component contains abstract classes to manage report generation. http://maven.apache.org/shared/maven-reporting-impl/ You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-impl/artifactId version2.0.4.2/version /dependency Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.4.2 ** Improvement * [MSHARED-108] - Add an ASF-compliant source release assembly ** Task * [MSHARED-106] - Update to Doxia 1.0 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Implementation 2.0.4.2 Released
The Maven team is pleased to announce the release of the Maven Reporting Implementation, version 2.0.4.2 This shared component contains abstract classes to manage report generation. http://maven.apache.org/shared/maven-reporting-impl/ You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-impl/artifactId version2.0.4.2/version /dependency Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.4.2 ** Improvement * [MSHARED-108] - Add an ASF-compliant source release assembly ** Task * [MSHARED-106] - Update to Doxia 1.0 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: [ANN] Maven Reporting Implementation 2.0.4.2 Released
Woah - a four digit build number? Is this now supported in maven 2 (wrt ranges and such)? -Original Message- From: Dennis Lundberg [mailto:denn...@apache.org] Sent: Fri 7/24/2009 2:54 AM To: annou...@maven.apache.org; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Reporting Implementation 2.0.4.2 Released The Maven team is pleased to announce the release of the Maven Reporting Implementation, version 2.0.4.2 This shared component contains abstract classes to manage report generation. http://maven.apache.org/shared/maven-reporting-impl/ You should specify the version in your project's dependency configuration: dependency groupIdorg.apache.maven.reporting/groupId artifactIdmaven-reporting-impl/artifactId version2.0.4.2/version /dependency Release Notes - Maven Shared Components - Version maven-reporting-impl 2.0.4.2 ** Improvement * [MSHARED-108] - Add an ASF-compliant source release assembly ** Task * [MSHARED-106] - Update to Doxia 1.0 Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven reporting
For example, the version of a plugin can be overridden but the configuration for the plugin isn't? EJ Ciramella wrote: OY - gotcha. Some maven 2 things work such that any configuration in a child pom overwrites what's in a parent, just not in the reporting stanzas? H. Thank you! -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Friday, February 27, 2009 4:10 PM To: Maven Users List Subject: Re: Maven reporting Most plugins have a skip option, ie. pmd [1] and checkstyle [2]. You can configure the report inside your own pom with the skip option enabled. If the plugin you are targetting doesn't have, please submit a feature request. It isn't hard to build in. Hth, [1] http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#skip [2] http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#skip Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Feb 27, 2009 at 10:04 PM, EJ Ciramella ecirame...@upromise.com wrote: We have a standard corp type pom that defines a list of reports that should be run/generated as part of every site build. In a project that has this corp pom listed as a parent, I'd like to NOT run a few of those reports. Is there a way to exclude/override which reports are run? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven reporting
but the first version of a plugin used in a reactor is the one that gets used, so if the parent is part of the same reactor, *and* gets built first, your override of the version in the child will be ignored Sent from my [rhymes with myPod] ;-) On 1 Mar 2009, at 19:59, Rusty Wright rusty.wri...@gmail.com wrote: For example, the version of a plugin can be overridden but the configuration for the plugin isn't? EJ Ciramella wrote: OY - gotcha. Some maven 2 things work such that any configuration in a child pom overwrites what's in a parent, just not in the reporting stanzas? H. Thank you! -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Friday, February 27, 2009 4:10 PM To: Maven Users List Subject: Re: Maven reporting Most plugins have a skip option, ie. pmd [1] and checkstyle [2]. You can configure the report inside your own pom with the skip option enabled. If the plugin you are targetting doesn't have, please submit a feature request. It isn't hard to build in. Hth, [1] http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#skip [2] http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#skip Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Feb 27, 2009 at 10:04 PM, EJ Ciramella ecirame...@upromise.com wrote: We have a standard corp type pom that defines a list of reports that should be run/generated as part of every site build. In a project that has this corp pom listed as a parent, I'd like to NOT run a few of those reports. Is there a way to exclude/ override which reports are run? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven reporting
We have a standard corp type pom that defines a list of reports that should be run/generated as part of every site build. In a project that has this corp pom listed as a parent, I'd like to NOT run a few of those reports. Is there a way to exclude/override which reports are run?
Re: Maven reporting
Most plugins have a skip option, ie. pmd [1] and checkstyle [2]. You can configure the report inside your own pom with the skip option enabled. If the plugin you are targetting doesn't have, please submit a feature request. It isn't hard to build in. Hth, [1] http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#skip [2] http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#skip Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Feb 27, 2009 at 10:04 PM, EJ Ciramella ecirame...@upromise.com wrote: We have a standard corp type pom that defines a list of reports that should be run/generated as part of every site build. In a project that has this corp pom listed as a parent, I'd like to NOT run a few of those reports. Is there a way to exclude/override which reports are run? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven reporting
OY - gotcha. Some maven 2 things work such that any configuration in a child pom overwrites what's in a parent, just not in the reporting stanzas? H. Thank you! -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Friday, February 27, 2009 4:10 PM To: Maven Users List Subject: Re: Maven reporting Most plugins have a skip option, ie. pmd [1] and checkstyle [2]. You can configure the report inside your own pom with the skip option enabled. If the plugin you are targetting doesn't have, please submit a feature request. It isn't hard to build in. Hth, [1] http://maven.apache.org/plugins/maven-pmd-plugin/pmd-mojo.html#skip [2] http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#skip Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Fri, Feb 27, 2009 at 10:04 PM, EJ Ciramella ecirame...@upromise.com wrote: We have a standard corp type pom that defines a list of reports that should be run/generated as part of every site build. In a project that has this corp pom listed as a parent, I'd like to NOT run a few of those reports. Is there a way to exclude/override which reports are run? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Reporting Impl 2.0.4.1 Released
The reporting implementation is used to render site reports. This release fixes an incompatibility with newer doxia implementations. This has just one change from 2.0.4: http://jira.codehaus.org/browse/MNG-3476 --The Maven Team
RE: Maven Reporting - DashBoard-Maven-Plugin
Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Reporting - DashBoard-Maven-Plugin
Hi all, as described in dashboard documentation : http://mojo.codehaus.org/dashboard-maven-plugin/ you must add this in your pom.xml or settings.xml to use properly the dashboard plugin: pluginRepositories pluginRepository idCodehaus Snapshots/id url http://snapshots.repository.codehaus.org//url /pluginRepository /pluginRepositories But even if this configuration is well done, Maven doesn't recognize the mvn dashboard-report:dashboard command. and to work fine, you must run mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command instead of mvn dashboard-report:dashboard. See : http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html or http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html or http://jira.codehaus.org/browse/MOJO-899 In the project's beginning, i decided to modify the goal prefix to dashboard-report instead of the default's one by adding in the pom.xml of the dashboard plugin : ... build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixdashboard-report/goalPrefix /configuration /plugin ... /plugins ... /build I think it's The Maven resolution problem of dashboard-report. Maven does not resolve properly the plugin prefix. it's for that : mvn dashboard-report:dashboard doesn't work correctly. For the next release , i will post a vote to users@maven.apache.org and [EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the default's one which works fine. After that, you will have to modify the goal prefix in your command line or Continuum goals to use the dashboard report : from dashboard-report:dashboard to dashboard:dashboard or from dashboard-report:persist to dashboard:persist Best Regards David Vicente SrinivasN wrote: I did... the second command never worked... it complains that it cannot find the dashboard-report plugin. I even set up the repository as mentioned and it downloaded while generating site... but the second command doesn't work. Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 10:00 AM To: Maven Users List Subject: Re: Maven Reporting - DashBoard-Maven-Plugin Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: Maven Reporting - DashBoard-Maven-Plugin
Hi all, as described in dashboard documentation : http://mojo.codehaus.org/dashboard-maven-plugin/ you must add this in your pom.xml or settings.xml to use properly the dashboard plugin: pluginRepositories pluginRepository idCodehaus Snapshots/id url http://snapshots.repository.codehaus.org//url /pluginRepository /pluginRepositories But even if this configuration is well done, Maven doesn't recognize the mvn dashboard-report:dashboard command. and to work fine, you must run mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard command instead of mvn dashboard-report:dashboard. See : http://www.nabble.com/Make-a-Codehaus-plugin-works-on-a-local-configuration-tf4297606s177.html or http://www.nabble.com/Multimodule-code-coverage-report-tf4511339s177.html or http://jira.codehaus.org/browse/MOJO-899 In the project's beginning, i decided to modify the goal prefix to dashboard-report instead of the default's one by adding in the pom.xml of the dashboard plugin : ... build plugins plugin artifactIdmaven-plugin-plugin/artifactId configuration goalPrefixdashboard-report/goalPrefix /configuration /plugin ... /plugins ... /build I think it's The Maven resolution problem of dashboard-report. Maven does not resolve properly the plugin prefix. it's for that : mvn dashboard-report:dashboard doesn't work correctly. For the next release , i will post a vote to users@maven.apache.org and [EMAIL PROTECTED] mailing lists to delete this goalPrefix and let the default's one which works fine. After that, you will have to modify the goal prefix in your command line or Continuum goals to use the dashboard report : from dashboard-report:dashboard to dashboard:dashboard or from dashboard-report:persist to dashboard:persist Best Regards David Vicente SrinivasN wrote: I did... the second command never worked... it complains that it cannot find the dashboard-report plugin. I even set up the repository as mentioned and it downloaded while generating site... but the second command doesn't work. Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 10:00 AM To: Maven Users List Subject: Re: Maven Reporting - DashBoard-Maven-Plugin Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED
RE: Maven Reporting - DashBoard-Maven-Plugin
Try: mvn org.codehaus.mojo:dashboard-maven-plugin:1.0-SNAPSHOT:dashboard or whatever version you're using. With regards, Nick Stolwijk -Original Message- From: Nagesh, Srinivas (IS Consultant) [mailto:[EMAIL PROTECTED] Sent: Thu 2/7/2008 4:03 PM To: Maven Users List Subject: RE: Maven Reporting - DashBoard-Maven-Plugin I did... the second command never worked... it complains that it cannot find the dashboard-report plugin. I even set up the repository as mentioned and it downloaded while generating site... but the second command doesn't work. Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 10:00 AM To: Maven Users List Subject: Re: Maven Reporting - DashBoard-Maven-Plugin Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Reporting - DashBoard-Maven-Plugin
I did... the second command never worked... it complains that it cannot find the dashboard-report plugin. I even set up the repository as mentioned and it downloaded while generating site... but the second command doesn't work. Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 10:00 AM To: Maven Users List Subject: Re: Maven Reporting - DashBoard-Maven-Plugin Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Reporting - DashBoard-Maven-Plugin
Quote: To generate the site and the correct dashboard report, you must run the dashboard report plugin in 2 passes : # mvn site # mvn dashboard-report:dashboard You should execute these two commands on the command line. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi Stefan, Thanks for your response. As you mentioned I am looking for a common report.When I try using the dashboard-maven-plugin, I ran into the following problem I went to http://mojo.codehaus.org/dashboard-maven-plugin/usage.html 1. Placed the dashboard plugin at the very end of the reporting tag. 2. Ran Maven Site. This actually generated the report before the findbugs plugin is executed. Shouldnt it supposed to run it at the last when all the other plugins have finished generating their reports? 3. Also as mentioned in the site above, what does this mean? add the dashboard report item in the left menu. Would you happen to have a working example of the dashboard-maven-plugin? Thanks Srinivas x3126 -Original Message- From: VUB Stefan Seidel [mailto:[EMAIL PROTECTED] Sent: Thursday, February 07, 2008 2:46 AM To: Maven Users List Subject: Re: Maven Reporting Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Reporting
Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini
Re: Maven Reporting
Hi, you may consolidate single reports for all modules (like Javadoc, JXR, ...) using the aggregate feature of these reports. The question is, what do you really want to do? Your modules have different names for example, how do you consolidate that? If you are looking for a common report on JUnit tests, Checkstyle, Findbugs etc. have a look at the dashboard-maven-plugin. regards, Stefan Nagesh, Srinivas (IS Consultant) wrote: Hi All, I have a multi-project setup in maven -- Proj -- pom.xml -- Reporting -- Proj1 -- pom.xml -- Proj2 -- pom.xml When I specify reporting in the parent pom, the reports are generated in the respective children projects. I would like to know if there is a feature to create a consolidated report of the sub project (Proj1 Proj2)? Thanks Srini -- best regards, Stefan Seidel software developer VUB Printmedia GmbH Chopinstraße 4 D-04103 Leipzig Germany tel.+49 (341) 9 60 50 07 fax.+49 (341) 9 60 50 92 mail. [EMAIL PROTECTED] web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Reporting Plugin's
Hello. When JavaNCSS encounters a project which has no source code files, it renders the summary site to have all 0's for its entries. For example, if I have nine projects which have source code files in their src and one which does not, the summary page shows all 0's. Please advise on how to make sure that the JavaNCSS data for relevant projects is shown and that data for irrelevant projects is not shown. Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Maven Reporting Plugin's
Many plugins have a skip configuration. Check the docs to see if NCSS has such a config, and if not, file an RFE for it to be added and/or add it yourself. Not certain, but this would probably solve your problems. Wayne On 10/11/07, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Hello. When JavaNCSS encounters a project which has no source code files, it renders the summary site to have all 0's for its entries. For example, if I have nine projects which have source code files in their src and one which does not, the summary page shows all 0's. Please advise on how to make sure that the JavaNCSS data for relevant projects is shown and that data for irrelevant projects is not shown. Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1
Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
maven-reporting-impl with version 2.0.1).
The following stack trace (not full) :
ause the requirement
ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing
Mojo field :
/**
* @component
* @required
* @readonly
*/
I have updated my pom to use maven-reporting-api and
maven-reporting-impl with version 2.0.1.
The second update generate the trouble. I need to revert it to 2.0.
Do I miss something ?
- Olivier
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
**
Ce message electronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci apres le message ), sont confidentiels et
destines exclusivement a l'usage de la personne a laquelle ils sont adresses.
Si vous avez recu ce message par erreur, merci de le renvoyer a son emetteur
et de le detruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressement autorisees de ce
message, sont interdites.
**
Re: [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1
doxia is now in org.apache.maven.doxia
Olivier Lamy a écrit :
Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
maven-reporting-impl with version 2.0.1).
The following stack trace (not full) :
ause the requirement
ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing
Mojo field :
/**
* @component
* @required
* @readonly
*/
I have updated my pom to use maven-reporting-api and
maven-reporting-impl with version 2.0.1.
The second update generate the trouble. I need to revert it to 2.0.
Do I miss something ?
- Olivier
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s). If
you have received this message in error please send it back to the sender and delete it.
Unauthorized publication, use, dissemination or disclosure of this message, either in
whole or in part is strictly prohibited.
**
Ce message electronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci apres le message ), sont confidentiels et destines exclusivement a l'usage de la personne a laquelle ils sont adresses. Si vous avez recu ce message par erreur, merci de le renvoyer a son emetteur et de le detruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressement autorisees de ce message, sont interdites.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1
Can you explain more ?
Because my mojo report needs to extends
org.apache.maven.reporting.AbstractMavenReport
This contains the abstract method :
org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()
That's why my mojo field is :
/**
* @component
* @required
* @readonly
*/
private SiteRenderer siteRenderer;
I implements the simple method :
/**
* @see
org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
*/
protected SiteRenderer getSiteRenderer()
{
return siteRenderer;
}
I have certainly miss something in the mojo's field configuration or in
the getSiteRenderer implementation ??
Thanks,
- Olivier
-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 décembre 2005 16:17
À : Maven Users List
Objet : Re: [m2.0.1] trouble with mojo report with maven-reporting-impl
with version 2.0.1
doxia is now in org.apache.maven.doxia
Olivier Lamy a écrit :
Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
maven-reporting-impl with version 2.0.1). The following stack trace
(not full) : ause the requirement
ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing
Mojo field :
/**
* @component
* @required
* @readonly
*/
I have updated my pom to use maven-reporting-api and
maven-reporting-impl with version 2.0.1. The second update generate
the trouble. I need to revert it to 2.0. Do I miss something ?
- Olivier
This e-mail, any attachments and the information contained therein
(this message) are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.
**
Ce message electronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci apres le message ), sont
confidentiels et destines exclusivement a l'usage de la personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressement autorisees de ce message, sont
interdites.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1
Can you try to remove your getSiteRenderer method and change package of
SiteRenderer in your import?
Emmanuel
Olivier Lamy a écrit :
Can you explain more ?
Because my mojo report needs to extends
org.apache.maven.reporting.AbstractMavenReport
This contains the abstract method :
org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()
That's why my mojo field is :
/**
* @component
* @required
* @readonly
*/
private SiteRenderer siteRenderer;
I implements the simple method :
/**
* @see
org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
*/
protected SiteRenderer getSiteRenderer()
{
return siteRenderer;
}
I have certainly miss something in the mojo's field configuration or in
the getSiteRenderer implementation ??
Thanks,
- Olivier
-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 décembre 2005 16:17
À : Maven Users List
Objet : Re: [m2.0.1] trouble with mojo report with maven-reporting-impl
with version 2.0.1
doxia is now in org.apache.maven.doxia
Olivier Lamy a écrit :
Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
maven-reporting-impl with version 2.0.1). The following stack trace
(not full) : ause the requirement
ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing
Mojo field :
/**
* @component
* @required
* @readonly
*/
I have updated my pom to use maven-reporting-api and
maven-reporting-impl with version 2.0.1. The second update generate
the trouble. I need to revert it to 2.0. Do I miss something ?
- Olivier
This e-mail, any attachments and the information contained therein
(this message) are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please send
it back to the sender and delete it. Unauthorized publication, use,
dissemination or disclosure of this message, either in whole or in part
is strictly prohibited.
**
Ce message electronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci apres le message ), sont
confidentiels et destines exclusivement a l'usage de la personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous quelque
forme que se soit non expressement autorisees de ce message, sont
interdites.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE : RE : [m2.0.1] trouble with mojo report with maven-reporting-impl with version 2.0.1
I can't remove it.
Because it's an abstract method in
org.apache.maven.reporting.AbstractMavenReport and I need to extend it
to made a mojo report.
- Olivier
-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 décembre 2005 16:59
À : Maven Users List
Objet : Re: RE : [m2.0.1] trouble with mojo report with
maven-reporting-impl with version 2.0.1
Can you try to remove your getSiteRenderer method and change package of
SiteRenderer in your import?
Emmanuel
Olivier Lamy a écrit :
Can you explain more ?
Because my mojo report needs to extends
org.apache.maven.reporting.AbstractMavenReport
This contains the abstract method :
org.codehaus.doxia.site.renderer.SiteRenderer getSiteRenderer()
That's why my mojo field is :
/**
* @component
* @required
* @readonly
*/
private SiteRenderer siteRenderer;
I implements the simple method :
/**
* @see
org.apache.maven.reporting.AbstractMavenReport#getSiteRenderer()
*/
protected SiteRenderer getSiteRenderer()
{
return siteRenderer;
}
I have certainly miss something in the mojo's field configuration or
in the getSiteRenderer implementation ??
Thanks,
- Olivier
-Message d'origine-
De : Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Envoyé : mardi 13 décembre 2005 16:17
À : Maven Users List
Objet : Re: [m2.0.1] trouble with mojo report with
maven-reporting-impl
with version 2.0.1
doxia is now in org.apache.maven.doxia
Olivier Lamy a écrit :
Hi,
A reporting mojo worked with 2.0 now failed with 2.0.1 (by updating
maven-reporting-impl with version 2.0.1). The following stack trace
(not full) : ause the requirement
ComponentRequirement{role='org.codehaus.doxia.site.renderer.SiteRend
rer', roleHint='null', fieldName='siteRenderer'} was missing
Mojo field :
/**
* @component
* @required
* @readonly
*/
I have updated my pom to use maven-reporting-api and
maven-reporting-impl with version 2.0.1. The second update generate
the trouble. I need to revert it to 2.0. Do I miss something ?
- Olivier
This e-mail, any attachments and the information contained therein
(this message) are confidential and intended solely for the use of
the addressee(s). If you have received this message in error please
send it back to the sender and delete it. Unauthorized publication,
use, dissemination or disclosure of this message, either in whole or
in part is strictly prohibited.
**
Ce message electronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci apres le message ), sont
confidentiels et destines exclusivement a l'usage de la personne a
laquelle ils sont adresses. Si vous avez recu ce message par erreur,
merci de le renvoyer a son emetteur et de le detruire. Toutes
diffusion, publication, totale ou partielle ou divulgation sous
quelque forme que se soit non expressement autorisees de ce message,
sont interdites.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
**
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après le message ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
**
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
