This is an automated email from the ASF dual-hosted git repository.

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


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

    from 063da7d  (tag)
      to dd33120  (tag)
 tagging 1e4d7ac6f8307826210a43ac91f0f326266efac2 (commit)
 replaces maven-parent-5
      by Hervé Boutemy
      on Sun Aug 12 06:17:58 2007 +0000

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

 discard 4d46aec  [maven-scm] copy for tag 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

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   (063da7d)
            \
             N -- N -- N   refs/tags/maven-parent-6 (dd33120)

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

Reply via email to