maven-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From hbout...@apache.org
Subject [maven-parent] annotated tag maven-parent-10 updated (b0e198c -> 3725600)
Date Tue, 09 Jan 2018 00:55:50 GMT
This is an automated email from the ASF dual-hosted git repository.

hboutemy pushed a change to annotated tag maven-parent-10
in repository https://gitbox.apache.org/repos/asf/maven-parent.git.


*** WARNING: tag maven-parent-10 was modified! ***

    from b0e198c  (tag)
      to 3725600  (tag)
 tagging ceb8793edd3f9185952be7220d6d902123ddb990 (commit)
 replaces maven-parent-9
      by Hervé Boutemy
      on Tue Nov 25 23:32:34 2008 +0000

- Log -----------------------------------------------------------------
maven-parent-10 reworked after migration from aggregate svn to split git
-----------------------------------------------------------------------

 discard b970bc7  [maven-release-plugin]  copy for tag maven-parent-10
 discard abc44b7  tagbase is useless now. The release plugin automagically computes the tags
directory
 discard 65428d9  Upgrade maven-release-plugin to 2.0-beta-8
 discard 770e908  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 90908f7  Upgrade resources plugin to 2.3
 discard 857c1ba  Upgrade deploy plugin to 2.4
 discard ded56a6  Changed my role to PMC Member
 discard 013de7b  o Locked down version of cobertura-maven-plugin:2.2
 discard e5bf14d  o Updated to maven-enforcer-plugin:1.0-alpha-4
 discard 57a5911  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 505eb4c  [maven-release-plugin] prepare for next development iteration
 discard 3af599c  [maven-release-plugin] prepare release maven-parent-9
 discard 9c6df95  removed the rest of clirr
 discard 4558e79  rollback
 discard f4cb4c1  [maven-release-plugin] prepare for next development iteration
 discard 5116eac  [maven-release-plugin] prepare release maven-parent-9
 discard 872e6b8  removed clirr config (see embedded comment) and enforcer version
 discard 9e6e109  reverting release
 discard aecd94b  [maven-release-plugin] prepare for next development iteration
 discard 64d634c  [maven-release-plugin] prepare release maven-parent-9
 discard cfd7fc8  We are using javadoc plugin 2.5 for reporting
 discard a95ed91  o using latest javadoc
 discard 8c1cc00  o Changed encoding of site descriptor to UTF-8 just like used for POMs o
Unified license headers
 discard 859c676  o added maven-scm-plugin in <pluginManagement/>
 discard 48a90ce  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 3eeaf94  o Remove BOM.
 discard eed9cba  o ordered POM following our conventions
 discard a9951ac  o Switched to released maven-invoker-plugin:1.2.1
 discard 50261f6  o MPIR is used even if the reporting profile is not activated
 discard 8ffc7ae  added ogusakov to the list
 discard 6daacc1  o Used custom PMD ruleset for the reporting profile
 discard 5c48540  o Added version lock-down for maven-antrun-plugin:1.2
 discard 4fa6af5  use modello-maven-plugin  released version
 discard 8a8534c  Use 1.0-alpha-21 of modello required by the changes plugin and we have the
issue MNG-3284
 discard 7ca02e3  Merge ci and ciProfiles in a quality-ckecks profile (activated with quality-ckecks=true)
 discard cb8f172  Ask to cobertura to cleanup its files
 discard ef8f9d7  Use invoker 1.2.1-SNAPSHOT required by several plugins. Will be released
in few days
 discard ffa1826  1.0-alpha-20 of modello plugin is used by doap plugin
 discard a23f927  Use SNAPSHOT version of enforcer (will be released soon) to fix a lot of
issues
 discard 1fc2aa1  1.3.5 of plexus plugin is already used in shade plugin
 discard a00df8c  set plexus plugin version in parent
 discard b876166  Set modello plugin version to use in parent
 discard 146735a  Define enforcer and invoker versions to use (used by the war plugin)
 discard 4102e33  Ignore eclipse configuration files
 discard 7f23fe2  use source encoding configuration in more plugins
 discard feb211a  o Make breadcrumbs and the menu for "Maven Projects" inherited.
 discard 5162c87  o Update versions for reporting plugins in pluginManagement, currently commented
out. o Move clirr-maven-plugin to before the reporting plugins in pluginManagement.
 discard ee2a67d  - 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 dc7a9ce  o Locked down source file encoding to UTF-8 for build reproducibility o
Excluded generated sources from PMD checks
 discard 1498f15  Version 2.2.1 of clirr-maven-plugin was released. It solved the issue that
previously required 2.3-SNAPSHOT.
 discard b18fb9c  o using latest maven site plugin
 discard a54f10d  o used latest PMD
 discard 5ded968  fix typo
 discard 6ac808a  upgrade some plugins to last version
 discard 205e2fa  Adding clirr:check to ci and release profiles.
 discard 3a0dea2  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 0ac24c7  Change my role to PMC
 discard 9448095  o bumped to maven-remote-resources-plugin:1.0
 discard 401574c  o used Hudson as CI
 discard 0ef5de0  o bumped to maven-javadoc-plugin:2.4
 discard c0c4495  lock down versions of common reporting plugins for site reproducibility
 discard 49cea0e  commented out lock down of reporting plugins waiting for MNG-3385 to be
fixed
 discard a003bcd  lock down maven-project-info-report-plugin version for site reproducibility
 discard 02b4856  lock down versions of common reporting plugins for site reproducibility
 discard 6725283  updated MarkMail addresses as recommended
 discard 7c77f4d  o Fixed svn:keywords
 discard c103c6e  o Locked down versions of maven-clean-plugin, maven-resources-plugin and
maven-plugin-plugin
 discard c940976  o Restored alphabetical order of plugins
 discard 245b385  o Test, test, 1-2-3, is this thing on?
 discard 202be23  [maven-release-plugin] prepare for next development iteration
 discard 43e41e1  [maven-release-plugin] prepare release maven-parent-8
 discard ea3b784  o Move elements around.
 discard b1fd5d6  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 0718c9b  o bumped to maven-remote-resources-plugin:1.0-beta-2
 discard 9e1d7df  o using international date format as proposed by Dennis on dev@
 discard 97e9d56  o removed links as proposed on dev@ o removed comments
 discard b6572b2  o import from plugins/trunk/src
 discard c780a31  upgrade jar plugin version to 2.2 upgrade surefire plugin version to 2.4.2
 discard 2db1b48  o Sort developers in alphabetical order. o Add Daniel's email.
 discard 8673b7d  Now I'm a PMC Member (thought I'd checked this in a while ago)
 discard c7ff034  Removing MNG issueManagement section, as this doesn't apply to all maven
projects.
 discard 24d34c9  Adding parameterized URL and name for snapshots repository in distributionManagement,
to allow closed-system build and deploy for CI systems, etc.
 discard 4cc474a  Override the distribution url to avoid inaadvertently publishing directly
to the rsynced repo.
 discard b689b19  o added more ML archives o removed issues ML since it is not a TLP ML
 discard 67edccb  update my role
 discard 927ba20  o Remove leading garbage characters.
 discard 15762cb  just updating my email/organization/timezone profile
 discard d268016  Added myself to the list of committers
 discard fa7b7eb  upgrade to last surefire plugin version
 discard b7fe2f9  MNG-3219: Create a CLIRR/JarDiff setup for 2.0.x and 2.1.x
 discard ee301f6  o Improved readingness of POM o no code change
 discard d1d92e9  o Move nicolas to the committers section of the <developers> element.
 discard 23380dd  Hey, I'm a committer now !!
 discard 0e5e1a4  o Put back SNIPPET comments for release-plugin-configuration.
 discard d673d57  o Update to the new version of maven-site-plugin.
 discard c93c8b9  site plugin 2.0-beta-6 hasn't been released yet
 discard ba25c33  Set versions in pluginManagement and sort alphabetically
 discard e45d1ad  Upgrade plugin versions and add new plugins
 discard 5bbaa3c  Upgrade release plugin
 discard a549c28  [maven-release-plugin] prepare for next development iteration
 discard 4a2e5b8  [maven-release-plugin] prepare release maven-parent-7
 discard 2e897f6  Revert release (again)
 discard 12f6830  [maven-release-plugin] prepare release maven-parent-            <groupId>org.apache.maven.plugins</groupId>
 discard f790315  Revert release and upgrade release, source and javadoc plugin
 discard 1b99fe7  [maven-release-plugin] prepare for next development iteration
 discard 9e6f0d8  [maven-release-plugin] prepare release maven-parent-7
 discard ec772c9  Revert release and upgrade gpg plugin
 discard c3dd740  [maven-release-plugin] prepare for next development iteration
 discard 19a5f31  [maven-release-plugin] prepare release maven-parent-7
 discard be4822c  Upgrade remote resources plugin and bundle just released
 discard 202efc2  Use latest apache-jar-resource-bundle snapshot
 discard f3dcd42  test commit rights (add myself in the pom)
 discard e9e5706  o Fix link to JUnit javadocs.
 discard 059077d  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

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   (b0e198c)
            \
             N -- N -- N   refs/tags/maven-parent-10 (3725600)

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>'].

Mime
View raw message