This is an automated email from the ASF dual-hosted git repository. hboutemy pushed a change to annotated tag maven-parent-15 in repository https://gitbox.apache.org/repos/asf/maven-parent.git.
*** WARNING: tag maven-parent-15 was modified! *** from 085fdde (tag) to 90bd23a (tag) tagging f297bb4dc760886e0f7f81febfe8f667fae57ce7 (commit) replaces maven-parent-14 by Hervé Boutemy on Thu Oct 29 22:35:20 2009 +0000 - Log ----------------------------------------------------------------- maven-parent-15 reworked after migration from aggregate svn to split git ----------------------------------------------------------------------- discard 7814ccd [maven-scm] copy for tag maven-parent-15 discard 89812a8 [maven-release-plugin] prepare release maven-parent-15 discard 5893ad5 o brian as chairman discard cebdb32 o bump to latest plugins discard 23624b5 [maven-release-plugin] prepare for next development iteration discard e577699 [maven-release-plugin] prepare release maven-parent-14 discard 09cab74 o Updated to (staged) apache-source-release-assembly-descriptor:1.0.1 in preparation for release discard 698a17e added javadoc links to Plexus main libraries discard b57a234 o Updated configuration for Checkstyle Plugin to load files from its classpath instead SVN discard 7a19936 adding myself to the list of committers discard c06098a [maven-release-plugin] prepare for next development iteration discard 47732a5 [maven-release-plugin] prepare release maven-parent-13 discard cc37cfa Rolling back messed up release. discard f34844f [maven-release-plugin] prepare for next development iteration discard 0b7a8b7 change groupId for source-release descriptor dependency discard 2c883de use staged version of the source-release descriptor dependency discard c2a23cf moving plugin version to pluginManagement section, outside of the profile for consistency and to allow overrides properly. discard 8255c5f Adding source-release assembly configuration. discard 7e54c38 o Synced roles with http://people.apache.org/~jim/projects.html#maven-pmc - Barrie is PMC member (cf. board report 2009-07) discard 78cb31b Add pgier as a committer discard f598319 o Synced roles with http://people.apache.org/~jim/projects.html#maven-pmc - Milos is PMC member (cf. board report 2008-04) - Deng is PMC member (cf. board report 2007-09) discard b86e798 o Restored alphabetical ordering of developers by id discard b311fbf [maven-release-plugin] prepare for next development iteration discard db9ef4b [maven-release-plugin] prepare release maven-parent-12 discard 1b333bc move the release profile and best practices to the apache pom. discard 0db6100 reverting all of this because the lag in svn breaks the release process. discard d376255 use staged parent discard 46621ed moving the release profile and other best practices to the apache pom discard 11e69a2 Upgrade maven-scm-plugin from 1.1 to 1.2 discard 80bd9cf o Removed altDeploymentRepository config for maven-deploy-plugin which has been superseded by the staging service of Nexus discard b20b228 use last maven-release-plugin version discard bb6a2e1 will change soon... discard 02a78cc o upgraded maven-site-plugin to 2.0 o upgraded modello-maven-plugin to 1.0.1 o upgraded maven-project-info-reports-plugin to 1.0.1 discard 74da752 o Used http://maven.apache.org/xsd/* for schema location discard 66fe54a Upgrade org.codehaus.mojo:taglist-maven-plugin 2.2 -> 2.3 discard aac75d2 upgrade org.apache.maven.plugins:maven-enforcer-plugin 1.0-alpha-4 -> 1.0-beta-1 discard 5719b69 o Updated to maven-plugin-plugin:2.5 discard a1bb6cd [maven-release-plugin] prepare for next development iteration discard 7a5970f [maven-release-plugin] prepare release maven-parent-11 discard 209a270 use new released version discard 88bbcad Move the snapshot properties and repo definitions up to the asf pom for consistency across projects. Change urls to use repository.apache.org discard 0812c2f Update my info. discard 8e3f0e4 o Updated my role discard 7393777 o ignored IDEA files discard 0c2e0d1 o using maven-stylus-skin release discard c1df5fc Added Petar Tahchiev to the list of committers. discard 555de5a o Updated to maven-clean-plugin:2.3 discard 618ca12 added mercury to Maven projects section discard 290f6de o using maven-stylus-skin snap due to r728944 discard d53280a upgraded Modello to 1.0-alpha-22 discard 1e4d432 [maven-release-plugin] prepare for next development iteration discard 51b61ff [maven-release-plugin] prepare release maven-parent-10 discard fa329ed tagbase is useless now. The release plugin automagically computes the tags directory discard 3a624ef Upgrade maven-release-plugin to 2.0-beta-8 discard 05b3faa o Updated to maven-antrun-plugin:1.3 o Updated to maven-docck-plugin:1.0 o Updated to maven-invoker-plugin:1.3 discard 7c38d26 Upgrade resources plugin to 2.3 discard 48d63b7 Upgrade deploy plugin to 2.4 discard c4c818a Changed my role to PMC Member discard a180cec o Locked down version of cobertura-maven-plugin:2.2 discard 5d4f617 o Updated to maven-enforcer-plugin:1.0-alpha-4 discard ba334a9 o updated to last release: apache-jar-resource-bundle:1.4 maven-plugin-plugin:2.4.3 maven-scm-plugin:1.1 plexus-maven-plugin:1.3.8 discard 3017244 [maven-release-plugin] prepare for next development iteration discard ba443d2 [maven-release-plugin] prepare release maven-parent-9 discard 8c1bcee removed the rest of clirr discard 6c3a09d rollback discard dae6843 [maven-release-plugin] prepare for next development iteration discard 2827695 [maven-release-plugin] prepare release maven-parent-9 discard c47c49b removed clirr config (see embedded comment) and enforcer version discard 4676a00 reverting release discard 63a7034 [maven-release-plugin] prepare for next development iteration discard fce246a [maven-release-plugin] prepare release maven-parent-9 discard 3bedca6 We are using javadoc plugin 2.5 for reporting discard d84fbba o using latest javadoc discard b742c9e o Changed encoding of site descriptor to UTF-8 just like used for POMs o Unified license headers discard 1f44a74 o added maven-scm-plugin in <pluginManagement/> discard 5216015 o Lock javadoc reports down to the ones we actually want (This is to prevent needless preparation of the aggregator reports which will be introduced with 2.5 and would otherwise result in build forking when individual sub projects update to latest Javadoc plugin) discard 4536c98 o Remove BOM. discard 9c8c715 o ordered POM following our conventions discard 77cf44a o Switched to released maven-invoker-plugin:1.2.1 discard 2bdabf6 o MPIR is used even if the reporting profile is not activated discard c530965 added ogusakov to the list discard 473a560 o Used custom PMD ruleset for the reporting profile discard 655d7fe o Added version lock-down for maven-antrun-plugin:1.2 discard 6fd77db use modello-maven-plugin released version discard bb30551 Use 1.0-alpha-21 of modello required by the changes plugin and we have the issue MNG-3284 discard 88d876f Merge ci and ciProfiles in a quality-ckecks profile (activated with quality-ckecks=true) discard b5762e2 Ask to cobertura to cleanup its files discard bc90a2b Use invoker 1.2.1-SNAPSHOT required by several plugins. Will be released in few days discard eeb195b 1.0-alpha-20 of modello plugin is used by doap plugin discard 1ed061c Use SNAPSHOT version of enforcer (will be released soon) to fix a lot of issues discard 6c7f74c 1.3.5 of plexus plugin is already used in shade plugin discard f2371d3 set plexus plugin version in parent discard ca180d0 Set modello plugin version to use in parent discard 63476fc Define enforcer and invoker versions to use (used by the war plugin) discard 1d9af39 Ignore eclipse configuration files discard f9ed172 use source encoding configuration in more plugins discard 848dad4 o Make breadcrumbs and the menu for "Maven Projects" inherited. discard 7fadb5f o Update versions for reporting plugins in pluginManagement, currently commented out. o Move clirr-maven-plugin to before the reporting plugins in pluginManagement. discard c888163 - Ignore settings - Add maven-docck-plugin 1.0-beta-2 in pluginsMgt - Add maven-javadoc-plugin 2.4 in pluginsMgt - Upgrade clirr-maven-plugin from 2.2.1 to 2.2.2 - Upgrade maven-project-info-reports-plugin from 2.0.1 to 2.1 discard 112059b o Locked down source file encoding to UTF-8 for build reproducibility o Excluded generated sources from PMD checks discard d9b53cc Version 2.2.1 of clirr-maven-plugin was released. It solved the issue that previously required 2.3-SNAPSHOT. discard 9ac8e7d o using latest maven site plugin discard 43cd7af o used latest PMD discard fa87ddc fix typo discard 3bae806 upgrade some plugins to last version discard a6d8063 Adding clirr:check to ci and release profiles. discard 94ffa6f Upgrading clirr plugin version (needs a release before this POM is released), so comparison artifacts will be resolved before being used...otherwise, this depends on artifacts already being in place within the local repository, which is a very bad assumption. discard 0df5d0a Change my role to PMC discard adc0321 o bumped to maven-remote-resources-plugin:1.0 discard dd69a78 o used Hudson as CI discard 1f6018f o bumped to maven-javadoc-plugin:2.4 discard 3378743 lock down versions of common reporting plugins for site reproducibility discard 4046133 commented out lock down of reporting plugins waiting for MNG-3385 to be fixed discard cae752a lock down maven-project-info-report-plugin version for site reproducibility discard 72821d1 lock down versions of common reporting plugins for site reproducibility discard 57cda22 updated MarkMail addresses as recommended discard 3366cdb o Fixed svn:keywords discard c0cfd9c o Locked down versions of maven-clean-plugin, maven-resources-plugin and maven-plugin-plugin discard b582721 o Restored alphabetical order of plugins discard d2c52b7 o Test, test, 1-2-3, is this thing on? discard 0c1878d [maven-release-plugin] prepare for next development iteration discard d083edc [maven-release-plugin] prepare release maven-parent-8 discard 3787c31 o Move elements around. discard 9645353 o Remove the name from the project element. This way the value of the name element in a projects pom.xml will be used, making it more dynamic. o Lock down the version for the skin. o Correct the date format. discard 8e13a9c o bumped to maven-remote-resources-plugin:1.0-beta-2 discard a31e968 o using international date format as proposed by Dennis on dev@ discard d5883d9 o removed links as proposed on dev@ o removed comments discard c4cc294 o import from plugins/trunk/src discard 2ba4e0c upgrade jar plugin version to 2.2 upgrade surefire plugin version to 2.4.2 discard 6510f76 o Sort developers in alphabetical order. o Add Daniel's email. discard 96e4087 Now I'm a PMC Member (thought I'd checked this in a while ago) discard 41e63a4 Removing MNG issueManagement section, as this doesn't apply to all maven projects. discard af2e6c6 Adding parameterized URL and name for snapshots repository in distributionManagement, to allow closed-system build and deploy for CI systems, etc. discard d65b720 Override the distribution url to avoid inaadvertently publishing directly to the rsynced repo. discard 3e6e455 o added more ML archives o removed issues ML since it is not a TLP ML discard 42608bf update my role discard 9135187 o Remove leading garbage characters. discard c5264ec just updating my email/organization/timezone profile discard 5b8aaf0 Added myself to the list of committers discard 862126b upgrade to last surefire plugin version discard acd0e29 MNG-3219: Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x discard 51dfba9 o Improved readingness of POM o no code change discard 66e4bcd o Move nicolas to the committers section of the <developers> element. discard 558c66c Hey, I'm a committer now !! discard 3b7693b o Put back SNIPPET comments for release-plugin-configuration. discard 51a3ca4 o Update to the new version of maven-site-plugin. discard e55ceb8 site plugin 2.0-beta-6 hasn't been released yet discard da48768 Set versions in pluginManagement and sort alphabetically discard 46fa928 Upgrade plugin versions and add new plugins discard 40feca4 Upgrade release plugin discard b872431 [maven-release-plugin] prepare for next development iteration discard 4b4b5bd [maven-release-plugin] prepare release maven-parent-7 discard efc55d6 Revert release (again) discard 9dac0ad [maven-release-plugin] prepare release maven-parent- <groupId>org.apache.maven.plugins</groupId> discard f3b1df1 Revert release and upgrade release, source and javadoc plugin discard b34a41b [maven-release-plugin] prepare for next development iteration discard 0c6f170 [maven-release-plugin] prepare release maven-parent-7 discard caab929 Revert release and upgrade gpg plugin discard 71e4ecf [maven-release-plugin] prepare for next development iteration discard 746005d [maven-release-plugin] prepare release maven-parent-7 discard 6548611 Upgrade remote resources plugin and bundle just released discard e9528ef Use latest apache-jar-resource-bundle snapshot discard a8981ce test commit rights (add myself in the pom) discard 6c74fb6 o Fix link to JUnit javadocs. discard 438b7bd test commit rights (add myself in the pom) discard 2c8a5c0 o Use the new javadocs URL for log4j. discard a1889eb o bumped to maven-remote-resources-plugin:1.0-alpha-6-SNAPSHOT due to MRRESOURCES-15 discard 12ab42e [maven-release-plugin] prepare for next development iteration discard 90981d8 [maven-release-plugin] prepare release maven-parent-6 discard 3c0672b o Update the configuration for maven-javadoc-plugin, by updating the links to Commons and Velocity who both have moved to TLP. discard f452bdf ignore target discard dcc9c77 Added maven-compiler-plugin configuration for 1.4 source and target to plugin management. discard d8e80b4 update remote resources plugin and bundle discard bc91de5 Added wsmoak to PMC and re-alphabetized list. discard 6ac64d7 o added javadoc link to Java 1.4.2 API Specification discard 1366bbb Fix xml missing tags discard 53dc166 License and notice should be in all builds, not just releases discard 5ff2b27 Configure the jar plugin to add specification and implementation entries to the manifest. discard edc699b Complete my profile discard d0b80ff a little ad for my company ;-) discard 828cb5f Use the latest release of the gpg plugin. discard 5ea2c72 Adding myself to the team list. discard 4b7134d removed the tabs discard c5b4973 MNG-1818 added all PMC and Committers. Organized by role then alpha by id for easy reference discard 8de37c9 updated my info discard 0c1f545 Add info for dkulp. discard 3ef90a9 added my info to pom. discard ec4abed Update parent discard 24f042e use the newer remote resources plugin discard 89ca87a o adding snippets that can be used in documentation discard ff54ed6 [maven-release-plugin] prepare for next development iteration discard 655d818 [maven-release-plugin] prepare release maven-parent-5 discard 6b92bb1 o just run the depoy, the site stuff should be done as part of release but separate as it pulls in so many things, can be so different and I just had it hang twice on me while doing something and I would rather have it be a separate part of the process. If the site deployment fails I don't want the release of the artifacts to fail. discard 80a9ce6 [maven-release-plugin] prepare for next development iteration discard 4bec8e6 [maven-release-plugin] prepare release maven-parent-5 discard 7a7d300 o the configuration for the release plugin can't be in the release profile itself ... duh. discard ef3cc92 o use deploy and site-deploy for the default goals discard f3f3d53 [maven-release-plugin] prepare for next development iteration discard f04170e [maven-release-plugin] prepare release maven-parent-5 discard 46416c6 git-svn-id: https://svn.apache.org/repos/asf/maven/pom/trunk/maven@502423 13f79535-47bb-0310-9956-ffa450edef68 discard 2767bb5 trying to tie up everything in the release profile discard 96cc751 [maven-release-plugin] prepare for next development iteration discard d57b98f [maven-release-plugin] prepare release maven-parent-5 discard 5197367 Added myself as a developer. discard 80cf8c7 added myself to pom discard d7f4bd8 o putting in a release profile discard 63773ab ditch the surrogate parent. It was getting out of date with everything copied from maven. Go the other way and make reporting stuff in maven optional, and retain normal inheritence. If we decide to make reporting compulsory again, it should be another parent pom between maven and the project (which the plugins won't be able to use due to the circular dependency problem) discard 7853980 o applied new license headers o no change discard 1de645e o fixed CI url discard 504b0c1 Adding myself as developer discard a054476 Test commit and added name to the list of developers. discard 1bb425a Add myself and check commit works discard 091244b put cpd-check in a ci profile discard 21926ee Add myself discard c5ec2b5 Added my timezone to the maven parent pom discard 7b44588 update location discard 53c64f7 put back the stricter rules. Your project should be made to comply before upgrading to this parent discard ad6c9b4 move maven pom to trunk discard 7583e7c [maven-release-plugin] prepare for next development iteration discard 04c5898 [maven-release-plugin] prepare release maven-parent-4 discard 78fb649 upgrade PMC members, add SCM settings for release omit e4a6113 Add Dennis omit 82e30ae disable CPD, it's pointless if the subprojects aren't yet compliant. Things need to have a working baseline to check for failures against. omit 3e9517e Update to reflect yesterday's acquision of Webify by IBM omit db6a246 Fixed start next development iteration omit 903bc5c Start next development iteration omit 8f126a2 Prepare release of version 3 omit 5244ac4 Fix commons logging api location omit 7bd3bc6 Upgrade parent omit 6687903 Added checkstyle configuration and pmd check for duplications omit d06329c release version to 2 omit 44687da use people.apache.org instead omit 0141fb9 Added more reports omit af32a4b Added surefire report to reporting omit 37f02e9 add my timezone omit 80c3198 Added reporting section omit 9d1a2e2 Added distribution site omit 437bf6a Added myself omit 1540c27 others have been deployed, bumping dev version omit 3617d71 some elements from the components pom omit 52d936d add developers omit 876c172 add maven root pom omit 3200f95 add Maven root POM add 158a552 move maven pom to trunk add cf3c004 put back the stricter rules. Your project should be made to comply before upgrading to this parent add fffe970 update location add e2a0a7a Added my timezone to the maven parent pom add 88ed392 Add myself add d2912a0 put cpd-check in a ci profile add 53e16be Add myself and check commit works add af864e4 Test commit and added name to the list of developers. add 843df10 Adding myself as developer add a4740bb o fixed CI url add fd39441 o applied new license headers o no change add c8fc072 ditch the surrogate parent. It was getting out of date with everything copied from maven. Go the other way and make reporting stuff in maven optional, and retain normal inheritence. If we decide to make reporting compulsory again, it should be another parent pom between maven and the project (which the plugins won't be able to use due to the circular dependency problem) add a19bdeb o putting in a release profile add f49c3c9 added myself to pom add aa2cb87 Added myself as a developer. add 9026a96 [maven-release-plugin] prepare release maven-parent-5 add a5da865 [maven-release-plugin] prepare for next development iteration add 937781e trying to tie up everything in the release profile add bdb3f07 git-svn-id: https://svn.apache.org/repos/asf/maven/pom/trunk@502423 13f79535-47bb-0310-9956-ffa450edef68 add 5ef89f4 [maven-release-plugin] prepare release maven-parent-5 add 6e83cd2 [maven-release-plugin] prepare for next development iteration add fada9a3 o use deploy and site-deploy for the default goals add cb9f482 o the configuration for the release plugin can't be in the release profile itself ... duh. add f2aab4c [maven-release-plugin] prepare release maven-parent-5 add e177bd6 [maven-release-plugin] prepare for next development iteration add 16fd64b o just run the depoy, the site stuff should be done as part of release but separate as it pulls in so many things, can be so different and I just had it hang twice on me while doing something and I would rather have it be a separate part of the process. If the site deployment fails I don't want the release of the artifacts to fail. add 4853641 [maven-release-plugin] prepare release maven-parent-5 add 4267e71 [maven-release-plugin] prepare for next development iteration add bd3a351 o adding snippets that can be used in documentation add 8ec76df use the newer remote resources plugin add d8a792a Update parent add 0e51796 added my info to pom. add aaab8f1 Add info for dkulp. add c937bbe updated my info add 73880b1 MNG-1818 added all PMC and Committers. Organized by role then alpha by id for easy reference add fc00bfa removed the tabs add 2181552 Adding myself to the team list. add f339a14 Use the latest release of the gpg plugin. add d1c7e0e a little ad for my company ;-) add 744491a Complete my profile add 2d34b9f Configure the jar plugin to add specification and implementation entries to the manifest. add 36dfec3 License and notice should be in all builds, not just releases add dd8591f Fix xml missing tags add d04f1d6 o added javadoc link to Java 1.4.2 API Specification add e2d7d27 Added wsmoak to PMC and re-alphabetized list. add 52d06cb update remote resources plugin and bundle add 7f4f281 Added maven-compiler-plugin configuration for 1.4 source and target to plugin management. add da0e567 o Update the configuration for maven-javadoc-plugin, by updating the links to Commons and Velocity who both have moved to TLP. add 1e4d7ac [maven-release-plugin] prepare release maven-parent-6 add 42ca9bc [maven-release-plugin] prepare for next development iteration add 7049044 o bumped to maven-remote-resources-plugin:1.0-alpha-6-SNAPSHOT due to MRRESOURCES-15 add fcf490e o Use the new javadocs URL for log4j. add 4c66e8e test commit rights (add myself in the pom) add b5c9fc0 o Fix link to JUnit javadocs. add dddedf1 test commit rights (add myself in the pom) add e159b89 Use latest apache-jar-resource-bundle snapshot add 998f80d Upgrade remote resources plugin and bundle just released add 2345bbc [maven-release-plugin] prepare release maven-parent-7 add d9d533d [maven-release-plugin] prepare for next development iteration add 47ca16f Revert release and upgrade gpg plugin add 63141f1 [maven-release-plugin] prepare release maven-parent-7 add f5b19fc [maven-release-plugin] prepare for next development iteration add e7e32ed Revert release and upgrade release, source and javadoc plugin add 2e6c58f [maven-release-plugin] prepare release maven-parent- <groupId>org.apache.maven.plugins</groupId> add 4888fd0 Revert release (again) add 10eaf16 [maven-release-plugin] prepare release maven-parent-7 add 7e4677a [maven-release-plugin] prepare for next development iteration add d7b782d Upgrade release plugin add eaec104 Upgrade plugin versions and add new plugins add 89a049d Set versions in pluginManagement and sort alphabetically add 436cb82 site plugin 2.0-beta-6 hasn't been released yet add 5fc1962 o Update to the new version of maven-site-plugin. add 6c6a583 o Put back SNIPPET comments for release-plugin-configuration. add d982a06 Hey, I'm a committer now !! add 225fc7e o Move nicolas to the committers section of the <developers> element. add 5a55cbf o Improved readingness of POM o no code change add f18769b MNG-3219: Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x add 9259dbd upgrade to last surefire plugin version add dd973c5 Added myself to the list of committers add da6440d just updating my email/organization/timezone profile add 4113379 o Remove leading garbage characters. add 7c33dc2 update my role add 1be9589 o added more ML archives o removed issues ML since it is not a TLP ML add 7c7ddb9 Override the distribution url to avoid inaadvertently publishing directly to the rsynced repo. add 43ce23c Adding parameterized URL and name for snapshots repository in distributionManagement, to allow closed-system build and deploy for CI systems, etc. add 80e5a82 Removing MNG issueManagement section, as this doesn't apply to all maven projects. add e730007 Now I'm a PMC Member (thought I'd checked this in a while ago) add 6303eb6 o Sort developers in alphabetical order. o Add Daniel's email. add 50fa9e6 upgrade jar plugin version to 2.2 upgrade surefire plugin version to 2.4.2 add 2c91509 o import from plugins/trunk/src add 2ffcaca o removed links as proposed on dev@ o removed comments add 44e0357 o using international date format as proposed by Dennis on dev@ add e550a9c o bumped to maven-remote-resources-plugin:1.0-beta-2 add 8d6acbb o Remove the name from the project element. This way the value of the name element in a projects pom.xml will be used, making it more dynamic. o Lock down the version for the skin. o Correct the date format. add df8d843 o Move elements around. add a97530b [maven-release-plugin] prepare release maven-parent-8 add 94e51ac [maven-release-plugin] prepare for next development iteration add 81f18a9 o Test, test, 1-2-3, is this thing on? add aa78d07 o Restored alphabetical order of plugins add 01c2667 o Locked down versions of maven-clean-plugin, maven-resources-plugin and maven-plugin-plugin add 4c8e4da updated MarkMail addresses as recommended add fd8a104 lock down versions of common reporting plugins for site reproducibility add 33cf679 lock down maven-project-info-report-plugin version for site reproducibility add 74e8764 commented out lock down of reporting plugins waiting for MNG-3385 to be fixed add f37240f lock down versions of common reporting plugins for site reproducibility add ac16478 o bumped to maven-javadoc-plugin:2.4 add ee4809a o used Hudson as CI add c2917c2 o bumped to maven-remote-resources-plugin:1.0 add 4bbc398 Change my role to PMC add 864dd30 Upgrading clirr plugin version (needs a release before this POM is released), so comparison artifacts will be resolved before being used...otherwise, this depends on artifacts already being in place within the local repository, which is a very bad assumption. add 419c182 Adding clirr:check to ci and release profiles. add 0debf69 upgrade some plugins to last version add eb15d43 fix typo add f18f8f4 o used latest PMD add 9d6898e o using latest maven site plugin add 2b24c45 Version 2.2.1 of clirr-maven-plugin was released. It solved the issue that previously required 2.3-SNAPSHOT. add 667e96c o Locked down source file encoding to UTF-8 for build reproducibility o Excluded generated sources from PMD checks add 8a4926e - Ignore settings - Add maven-docck-plugin 1.0-beta-2 in pluginsMgt - Add maven-javadoc-plugin 2.4 in pluginsMgt - Upgrade clirr-maven-plugin from 2.2.1 to 2.2.2 - Upgrade maven-project-info-reports-plugin from 2.0.1 to 2.1 add 17e1989 o Update versions for reporting plugins in pluginManagement, currently commented out. o Move clirr-maven-plugin to before the reporting plugins in pluginManagement. add 17057e9 o Make breadcrumbs and the menu for "Maven Projects" inherited. add 66bfb84 use source encoding configuration in more plugins add 0bf3293 Define enforcer and invoker versions to use (used by the war plugin) add 83a6023 Set modello plugin version to use in parent add 7fd31f8 set plexus plugin version in parent add 530c915 1.3.5 of plexus plugin is already used in shade plugin add 387e7e8 Use SNAPSHOT version of enforcer (will be released soon) to fix a lot of issues add 807b8b2 1.0-alpha-20 of modello plugin is used by doap plugin add 1fabc2a Use invoker 1.2.1-SNAPSHOT required by several plugins. Will be released in few days add e4833d3 Ask to cobertura to cleanup its files add 07453a6 Merge ci and ciProfiles in a quality-ckecks profile (activated with quality-ckecks=true) add 873882b Use 1.0-alpha-21 of modello required by the changes plugin and we have the issue MNG-3284 add 3341352 use modello-maven-plugin released version add 6fd683e o Added version lock-down for maven-antrun-plugin:1.2 add 3f8615d o Used custom PMD ruleset for the reporting profile add 4e9b849 added ogusakov to the list add 3cd0611 o MPIR is used even if the reporting profile is not activated add f968c4f o Switched to released maven-invoker-plugin:1.2.1 add 0f5cf0b o ordered POM following our conventions add e72cbe5 o Remove BOM. add 2aa8176 o Lock javadoc reports down to the ones we actually want (This is to prevent needless preparation of the aggregator reports which will be introduced with 2.5 and would otherwise result in build forking when individual sub projects update to latest Javadoc plugin) add 0b57afa o added maven-scm-plugin in <pluginManagement/> add 87635ab o Changed encoding of site descriptor to UTF-8 just like used for POMs o Unified license headers add 34a3a9d o using latest javadoc add 72a45ee We are using javadoc plugin 2.5 for reporting add 1f88591 [maven-release-plugin] prepare release maven-parent-9 add 8dd9a82 [maven-release-plugin] prepare for next development iteration add ea9ab2c reverting release add 7504718 removed clirr config (see embedded comment) and enforcer version add cef1efd [maven-release-plugin] prepare release maven-parent-9 add ab3132d [maven-release-plugin] prepare for next development iteration add 5bba4ba rollback add cac5a4c removed the rest of clirr add 3c4e0e2 [maven-release-plugin] prepare release maven-parent-9 add 0c2f271 [maven-release-plugin] prepare for next development iteration add 2151a8f o updated to last release: apache-jar-resource-bundle:1.4 maven-plugin-plugin:2.4.3 maven-scm-plugin:1.1 plexus-maven-plugin:1.3.8 add eb61f14 o Updated to maven-enforcer-plugin:1.0-alpha-4 add dc7b74a o Locked down version of cobertura-maven-plugin:2.2 add cb24df9 Changed my role to PMC Member add 2fca1a8 Upgrade deploy plugin to 2.4 add a1921f8 Upgrade resources plugin to 2.3 add 0c732c2 o Updated to maven-antrun-plugin:1.3 o Updated to maven-docck-plugin:1.0 o Updated to maven-invoker-plugin:1.3 add 3d00848 Upgrade maven-release-plugin to 2.0-beta-8 add e46a58a tagbase is useless now. The release plugin automagically computes the tags directory add ceb8793 [maven-release-plugin] prepare release maven-parent-10 add ea76ded [maven-release-plugin] prepare for next development iteration add 272d756 upgraded Modello to 1.0-alpha-22 add cd3433f o using maven-stylus-skin snap due to r728944 add 5f5a880 added mercury to Maven projects section add 4ed21ea o Updated to maven-clean-plugin:2.3 add e02dd47 Added Petar Tahchiev to the list of committers. add a2ad272 o using maven-stylus-skin release add f2c5d09 o Updated my role add f943035 Update my info. add ec09116 Move the snapshot properties and repo definitions up to the asf pom for consistency across projects. Change urls to use repository.apache.org add dd70e98 use new released version add ec5bff1 [maven-release-plugin] prepare release maven-parent-11 add 5932d86 [maven-release-plugin] prepare for next development iteration add 971e363 o Updated to maven-plugin-plugin:2.5 add f891e6a upgrade org.apache.maven.plugins:maven-enforcer-plugin 1.0-alpha-4 -> 1.0-beta-1 add 478a740 Upgrade org.codehaus.mojo:taglist-maven-plugin 2.2 -> 2.3 add e83b270 o Used http://maven.apache.org/xsd/* for schema location add 8ae6ef6 o upgraded maven-site-plugin to 2.0 o upgraded modello-maven-plugin to 1.0.1 o upgraded maven-project-info-reports-plugin to 1.0.1 add b2cb93d will change soon... add 7dbd6ff use last maven-release-plugin version add e707b9e o Removed altDeploymentRepository config for maven-deploy-plugin which has been superseded by the staging service of Nexus add 929ad8f Upgrade maven-scm-plugin from 1.1 to 1.2 add 7d883d4 moving the release profile and other best practices to the apache pom add dce638f use staged parent add 69e7e1d reverting all of this because the lag in svn breaks the release process. add 6d05753 move the release profile and best practices to the apache pom. add 41b3a87 [maven-release-plugin] prepare release maven-parent-12 add 4cdc227 [maven-release-plugin] prepare for next development iteration add 54d7b68 o Restored alphabetical ordering of developers by id add 883cd54 o Synced roles with http://people.apache.org/~jim/projects.html#maven-pmc - Milos is PMC member (cf. board report 2008-04) - Deng is PMC member (cf. board report 2007-09) add d85deaa Add pgier as a committer add f42a8b8 o Synced roles with http://people.apache.org/~jim/projects.html#maven-pmc - Barrie is PMC member (cf. board report 2009-07) add 20a22b2 Adding source-release assembly configuration. add fae7780 moving plugin version to pluginManagement section, outside of the profile for consistency and to allow overrides properly. add 1f7c7a6 use staged version of the source-release descriptor dependency add 837b545 change groupId for source-release descriptor dependency add 05836e3 [maven-release-plugin] prepare for next development iteration add b2ba692 Rolling back messed up release. add 60fd0c0 [maven-release-plugin] prepare release maven-parent-13 add ffd935b [maven-release-plugin] prepare for next development iteration add 72bb22a adding myself to the list of committers add 2374bb0 o Updated configuration for Checkstyle Plugin to load files from its classpath instead SVN add b4da516 added javadoc links to Plexus main libraries add 178405f o Updated to (staged) apache-source-release-assembly-descriptor:1.0.1 in preparation for release add 0db96f3 [maven-release-plugin] prepare release maven-parent-14 add 6ecd191 [maven-release-plugin] prepare for next development iteration add 2109cf8 o bump to latest plugins add 5c1eac4 o brian as chairman add f297bb4 [maven-release-plugin] prepare release maven-parent-15 This update added new revisions after undoing existing revisions. That is to say, some revisions that were in the old version of the annotated tag are not in the new version. This situation occurs when a user --force pushes a change and generates a repository containing something like this: * -- * -- B -- O -- O -- O (085fdde) \ N -- N -- N refs/tags/maven-parent-15 (90bd23a) You should already have received notification emails for all of the O revisions, and so the following emails describe only the N revisions from the common base, B. Any revisions marked "omit" are not gone; other references still refer to them. Any revisions marked "discard" are gone forever. No new revisions were added by this update. Summary of changes: -- To stop receiving notification emails like this one, please contact ['"commits@maven.apache.org" <commits@maven.apache.org>'].