maven-commits mailing list archives

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

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


*** WARNING: tag apache-7 was modified! ***

    from 6882029  (tag)
      to bc1c4cb  (tag)
 tagging 2444d8c04ff0e0e2fdd1d527947e6b7d96c0b175 (commit)
 replaces apache-6
      by Hervé Boutemy
      on Sat Dec 26 12:22:23 2009 +0000

- Log -----------------------------------------------------------------
apache-7 reworked after migration from aggregate svn to split git
-----------------------------------------------------------------------

 discard ee5fe48  [maven-scm] copy for tag apache-7
 discard e621040  [maven-release-plugin] prepare release apache-7
 discard 6a75570  o Updated to maven-assembly-plugin:2.2-beta-5 o Updated to maven-deploy-plugin:2.5
o Updated to maven-jar-plugin:2.3
 discard 6171b43  o Reverted version back to 7-SNAPSHOT after cancelled release
 discard 5fd8da2  o Added note about version for maven-javadoc-plugin
 discard c4fc777  o Updated to apache-source-release-assembly-descriptor:1.0.2
 discard 1dae314  o Downgraded to maven-javadoc-plugin:2.5 as used by apache:6 to prevent
MJAVADOC-275
 discard 582e5bf  [maven-release-plugin] prepare for next development iteration
 discard 5386d9f  [maven-scm] copy for tag apache-7
 discard 702f117  [maven-release-plugin] prepare release apache-7
 discard c6db860  Adding pluginManagement entry for assembly plugin
 discard 3984e6c  updating ASF parent POM to include source-release assembly configuration,
with configurable descriptorRef (using expression ${sourceReleaseAssemblyDescriptor}). Also,
adding comments in the Maven parent POM to remove this source-release configuration once the
parent version is upgraded to 7."
 discard 3695916  o bump to latest plugins
 discard 7d554bf  o bump to latest modello
 discard 965bb14  [maven-release-plugin] prepare for next development iteration
 discard fd9baaf  [maven-release-plugin] prepare release apache-6
 discard c1cb546  move the release profile and best practices to the apache pom.
 discard edb7c3a  o Used http://maven.apache.org/xsd/* for schema location
 discard 35eb377  [maven-release-plugin] prepare for next development iteration
 discard 1b3005e  [maven-release-plugin] prepare release apache-5
 discard 1c67ff7  folders are supposed to end in / but maven always appends another / so stripping
this one.
 discard 1617e22  rollback
 discard 6c7ae1f  [maven-release-plugin] prepare for next development iteration
 discard 84bdf79  [maven-release-plugin] prepare release apache-5
 discard e222f98  remove the plugin snapshot repo
 discard 6b7f8bd  use shorter url
 discard be678db  Move the snapshot properties and repo definitions up to the asf pom for
consistency across projects. Change urls to use repository.apache.org
    omit ef3c756  o ignored IDEA files
    omit 89eae19  Ignore eclipse configuration files
    omit 7de1fd2  o Fixed svn:keywords
    omit a3e1801  [maven-release-plugin] prepare for next development iteration
    omit 760a8cb  [maven-release-plugin] prepare release apache-4
    omit d63c236  Added "The" to organization
    omit 25c8701  o applied new license headers o no change
    omit b816c6b  add SCM repo
    omit c4c1910  add logo
    omit 50a184d  o inserted a <build/> element that contains the configuration for
the remote-resources plugin that will push   licensing information into each maven build at
apache. it is currently commented out so people can look at it   before it gets turned on.
we also need to release the resource bundles.
    omit 5e393ce  move asf pom to new trunk
    omit 638b79d  o we only use snapshots in dev mode
    omit 27e7540  Use new repo paths
    omit 9398442  release version to 2
    omit 7ebd6c6  use people.apache.org instead
    omit a3f219f  others have been deployed, bumping dev version
    omit 83b135a  some elements from the components pom
    omit dc00f68  back to sequential
    omit 2aef2ab  try again
    omit cb66723  try using keyword
    omit 864b679  Apache wide POM
     add 1ec3f8b  move asf pom to new trunk
     add e0a3c09  o inserted a <build/> element that contains the configuration for
the remote-resources plugin that will push   licensing information into each maven build at
apache. it is currently commented out so people can look at it   before it gets turned on.
we also need to release the resource bundles.
     add f47b856  add logo
     add c5633b3  add SCM repo
     add 34301d5  o applied new license headers o no change
     add 2ed646d  Added "The" to organization
     add b7709ad  [maven-release-plugin] prepare release apache-4
     add 0617fc0  [maven-release-plugin] prepare for next development iteration
     add 5c8b75d  Move the snapshot properties and repo definitions up to the asf pom for
consistency across projects. Change urls to use repository.apache.org
     add 13a0014  use shorter url
     add 4a51611  remove the plugin snapshot repo
     add cf03d0f  [maven-release-plugin] prepare release apache-5
     add 8f0956c  [maven-release-plugin] prepare for next development iteration
     add 1f75dea  rollback
     add 4288a40  folders are supposed to end in / but maven always appends another / so stripping
this one.
     add f4592e2  [maven-release-plugin] prepare release apache-5
     add 66f9a4e  [maven-release-plugin] prepare for next development iteration
     add 878eab5  o Used http://maven.apache.org/xsd/* for schema location
     add b6d76ce  move the release profile and best practices to the apache pom.
     add ebf4c1c  [maven-release-plugin] prepare release apache-6
     add 4aea855  [maven-release-plugin] prepare for next development iteration
     add 49c8323  o bump to latest modello
     add c1e416d  o bump to latest plugins
     add eae5a47  updating ASF parent POM to include source-release assembly configuration,
with configurable descriptorRef (using expression ${sourceReleaseAssemblyDescriptor}). Also,
adding comments in the Maven parent POM to remove this source-release configuration once the
parent version is upgraded to 7."
     add a3e9cfe  Adding pluginManagement entry for assembly plugin
     add 28fc64f  [maven-release-plugin] prepare release apache-7
     add 6ebe070  [maven-release-plugin] prepare for next development iteration
     add 77bad19  o Downgraded to maven-javadoc-plugin:2.5 as used by apache:6 to prevent
MJAVADOC-275
     add 9ba34bb  o Updated to apache-source-release-assembly-descriptor:1.0.2
     add 092874e  o Added note about version for maven-javadoc-plugin
     add b347388  o Reverted version back to 7-SNAPSHOT after cancelled release
     add 08fd83a  o Updated to maven-assembly-plugin:2.2-beta-5 o Updated to maven-deploy-plugin:2.5
o Updated to maven-jar-plugin:2.3
     add 2444d8c  [maven-release-plugin] prepare release apache-7

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   (6882029)
            \
             N -- N -- N   refs/tags/apache-7 (bc1c4cb)

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