You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by hb...@apache.org on 2018/01/03 23:06:21 UTC

[maven-default-skin] annotated tag maven-default-skin-1.1 updated (8390dc9 -> 8f67eed)

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

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


*** WARNING: tag maven-default-skin-1.1 was modified! ***

    from 8390dc9  (tag)
      to 8f67eed  (tag)
 tagging 3e7e6964e0587dc0c5806bef0da913666588baf0 (commit)
 replaces maven-default-skin-1.0
      by Hervé Boutemy
      on Wed Jan 18 20:12:17 2012 +0000

- Log -----------------------------------------------------------------
maven-default-skin-1.1 reworked after migration from aggregate svn to split git
-----------------------------------------------------------------------

 discard 4be11e4  [maven-release-plugin]  copy for tag maven-default-skin-1.1
 discard a6bd3ec  [maven-release-plugin] prepare release maven-default-skin-1.1
 discard 72c7a8a  upgrading to skins parent 6
 discard 53a5652  Now that the maven-skins parent is no longer in the parent directory, we need to specify SCM URLs for all the skins. The default values, that is used if we don't specify these URLs, are wrong.
 discard 6000d62  parent + skins versions rolled back, RC1 failed
 discard 3a814bf  Split maven-skins into two separate POMs: - one parent for all the skins called maven-skins, in a subfolder like we do for our plugins - one aggregator called maven-skins-aggregator, in the root of the project, to be used in a CI-environment
 discard e0e98cc  [maven-release-plugin] prepare for next development iteration
 discard 60a84a1  [maven-release-plugin] prepare release maven-skins-6
 discard 31cb188  rolled back the maven-skins-6 release
 discard 99c238c  [maven-release-plugin] prepare for next development iteration
 discard be14dd1  [maven-release-plugin] prepare release maven-skins-6
 discard 76319c5  allows dynamic URLs depending on the active profiles
 discard 61c2bdb  added URL for released sites
 discard f8e4542  added the RC profile to stage sites, automatically enabled enabled by release plugin
 discard 6d0aaae  Fix MSKINS-12: Internet Explorer 9 shows scrollbar on <div id=navcolumn>
 discard 2332ae1  removed now unused site configuration
 discard 2a416fa  added IT and documentation to each skin
 discard 8d07350  added IT and documentation to each skin
 discard a2b958d  fix parent version.
 discard 0d4f500  added XML Schema reference to site.xml
 discard 7bea634  new parent
 discard 88f48b5  o improved issueManagement url
 discard 8f6ce40  o ignored eclipse files
 discard 0a072f9  o fixed xsd url
 discard 95c7f3b  o ordering pom
 discard 990074f  o Let each skin choose its own banner and skin.
 discard ebff724  o Use the latest parent.
 discard 2962087  o Fixed svn:keywords
 discard 384aadb  o ignored Windows Thumbs.db
 discard 51bf9d0  [MSKINS-2] maven-theme.css invalid css
 discard 5f47d32  o Ignore IDEA files.
 discard 6daf388  o Update to a released version of the parent.
 discard d774fb0  o Add new license headers.
 discard f250523  update parent POMs
 discard 01dda33  [maven-release-plugin] prepare for next development iteration
 discard f02303e  [maven-release-plugin] prepare release maven-default-skin-1.0
 discard 6d68124  [MSITE-97] copy small icon images and related CSS
 discard 92c78c2  update pom rev
 discard 99f1ea0  ignore target
 discard c0afcf7  add resources for classic and default skins
 discard 709520c  PR: MSITE-48 create scaffolding for skin projects
     add 3506c69  PR: MSITE-48 create scaffolding for skin projects
     add 24cdc22  add resources for classic and default skins
     add e72fe42  update pom rev
     add 1c583fd  [MSITE-97] copy small icon images and related CSS
     add 312b942  [maven-release-plugin] prepare release maven-default-skin-1.0
     add 39cd2eb  [maven-release-plugin] prepare for next development iteration
     add bec6292  update parent POMs
     add b1d6b08  o Add new license headers.
     add 7c1a6ef  o Update to a released version of the parent.
     add 5668015  [MSKINS-2] maven-theme.css invalid css
     add 735793f  o Use the latest parent.
     add 07ef250  o Let each skin choose its own banner and skin.
     add 95a28fd  o ordering pom
     add cb63358  o fixed xsd url
     add 777770e  o improved issueManagement url
     add 0bb75b9  new parent
     add d9d8cb0  added XML Schema reference to site.xml
     add b2fb78d  fix parent version.
     add 19118d7  added IT and documentation to each skin
     add 874e070  added IT and documentation to each skin
     add 40c528a  removed now unused site configuration
     add 499cb59  Fix MSKINS-12: Internet Explorer 9 shows scrollbar on <div id=navcolumn>
     add 3aed41b  added the RC profile to stage sites, automatically enabled enabled by release plugin
     add 1743c96  added URL for released sites
     add 540fc84  allows dynamic URLs depending on the active profiles
     add ee48090  [maven-release-plugin] prepare release maven-skins-6
     add 25c28df  [maven-release-plugin] prepare for next development iteration
     add a58fc6c  rolled back the maven-skins-6 release
     add 74eac0b  [maven-release-plugin] prepare release maven-skins-6
     add e76243d  [maven-release-plugin] prepare for next development iteration
     add 679d661  Split maven-skins into two separate POMs: - one parent for all the skins called maven-skins, in a subfolder like we do for our plugins - one aggregator called maven-skins-aggregator, in the root of the project, to be used in a CI-environment
     add 69f56b2  parent + skins versions rolled back, RC1 failed
     add ed3df72  Now that the maven-skins parent is no longer in the parent directory, we need to specify SCM URLs for all the skins. The default values, that is used if we don't specify these URLs, are wrong.
     add 85f16a4  upgrading to skins parent 6
     add 3e7e696  [maven-release-plugin] prepare release maven-default-skin-1.1

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   (8390dc9)
            \
             N -- N -- N   refs/tags/maven-default-skin-1.1 (8f67eed)

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" <co...@maven.apache.org>'].