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/02 22:25:42 UTC
[maven-install-plugin] annotated tag maven-install-plugin-2.1
updated (b50db05 -> af70930)
This is an automated email from the ASF dual-hosted git repository.
hboutemy pushed a change to annotated tag maven-install-plugin-2.1
in repository https://gitbox.apache.org/repos/asf/maven-install-plugin.git.
*** WARNING: tag maven-install-plugin-2.1 was modified! ***
from b50db05 (tag)
to af70930 (tag)
tagging 2329520b8a696e472caf4731342461fde57353bf (commit)
replaces maven-install-plugin-2.0
by Hervé Boutemy
on Wed Jan 11 22:01:38 2006 +0000
- Log -----------------------------------------------------------------
maven-install-plugin-2.1 reworked after migration from aggregate svn to split git
-----------------------------------------------------------------------
discard 5196dd8 move to correct location
discard 379798b [maven-scm] copy for tag maven-install-plugin-2.1
discard d1882c7 back to previous parent
discard 7b45918 Workaround for no primary artifact to install PR: MINSTALL-3
discard 1cc3402 Upgrade parent to 2.0.1 so that the site is deployed in the right location
discard 0424a6c -added pomFile parameter to make install-file install the jar and the customed pom at the same time.
discard d18047d move plugins
discard 83dae8f PR: MNG-1322 Submitted By: Allan Ramirez Reviewed By: John Casey
discard b091d3e PR: MNG-1279 Submitted by: Philipp Meier add missing model version to generated pom
discard 92ea8b1 PR: MNG-1279 Submitted by: Philipp Meier Reviewed by: Brett Porter ability to write a pom on install-file
discard b56c3ac cleanup some unused fields
discard 1f3c181 ignore
discard 910945b [maven-release-plugin] prepare for next development iteration
discard 58a4647 [maven-release-plugin] prepare release maven-install-plugin-2.0
discard 2723da3 update versions in plugins
discard a36b461 more error diagnostics improvements
discard e7bbbc4 PR: MNG-122 cleanup artifact metadata retrieval exceptions
discard 0b81cfd upgrade plexus utils to 1.0.4-SNAPSHOT. The group ID has changed, so add a bunch of exclusions to ensure the old is not picked up fix bugs in mboot that wasn't honoring excludes.
discard 8dff731 PR: MNG-1114 install:install-file should not run over subprojects
discard 3d139c4 PR: MNG-653 use the file assigned by the packager for installation/deployment. Error out if that isn't done.
discard d107b93 PR: MNG-644 remove use of deprecated artifact method (retain signature for backwards compat until next release of install/deploy plugins)
discard 04ce04a goal doesn't require a project
discard 2b92719 ignore release.properties and more
discard 0f8acd4 [maven-release-plugin] prepare for next development iteration
discard 9f6f1cd [maven-release-plugin] prepare release maven-install-plugin-2.0-beta-1
discard b8ea5ae update dependency and parent versions
discard eb91ec5 Resolving MNG-851. Using MavenProject.getFile() rather than constructing new. Also fixed maven-deploy-plugin with similar bug.
discard 03c8486 PR: MNG-613 make sure versions are aggregated
discard 7d862f7 PR: MNG-613 deploy snapshot information to the correct directory and fix some other minor issues
discard a718714 PR: MNG-613 changes versioning to use repository metadata
discard 1c903b9 TODOs and cleanup
discard 7d9d816 PR: MNG-596 add XSD definition to m2 poms and archetypes
discard f331916 Fix svn properties
discard 116191a Resolving:
discard d65b3c2 Update all versions to beta-1-SNAPSHOT
discard d39cbfd Resolving: MNG-495
discard f9e387f refactoring of the resolveTransitiveDependencies call. simplified by removing a bunch of duplicated code in addArtifacts - no need to merge, you have the full list. separated the original artifacts (dependency artifacts) from the resolved artifacts (getArtifacts)
discard fa31ee3 change <model> to <project> in root tag.
discard dfcdd91 PR: MNG-257
discard cecd921 o Adding support for <executions/>, which means multiple runs of the same goal/set-of-goals with different configs. o Adding @phase declarations for those mojos that seem to be part of the main build, just for completeness o Added two ITs, to test that <executions/> doesn't mess up the normal operation, and to test multi-execution for a goal.
discard f9b6aea update parent references to get access to the ci settings
discard fa51692 remove old cvs ignore files
discard 2120a1c PR: MNG-378 Only deploy the release information at the point of release
discard 882d11e Clean imports
discard e4942bf bump versions
discard efeed85 use released versions
discard ea0a132 set consistent versions
discard 527fb88 PR: MNG-338 Helpful error message for non-redistributable JARs, eg jdbc
discard e16fc2c Renamed Plugin.java, AbstractPlugin.java, PluginExecutionRe(quest|sponse) PluginExecutionException to Mojo*
discard 4c99268 o Cleaned up field-level annotation support (especially descriptor extraction, generation, and building) o Converted all "core" plugins (including maven-core-it-plugin) to use field-level annotations o Removed generation of parameter descriptors for ${/#component.* param specifications. o Added @readonly for parameters that cannot be overridden by user configuration (List override was dangerous here) o Added validation against pom-derived configuration for @readonly para [...]
discard 3a4e164 fix more references to the old package
discard abf62ff remove unnecessary maven-core dependencies
discard a600830 add more use of ${} expressions, fix problem when } was not at end
discard 82e8e4c correct problem where anything with a modified finalName was not installed/deployed
discard a884c81 improved error handling and other clean up
discard 8ee8ec5 split the plugin API and the plugin descriptor code
discard 94b46c5 release alpha-1 plugins
discard aa44861 clean up dependencies.
discard 4d2a6f1 update poms for releases
discard d617216 rewrite POM with new version on deployment
discard 826bbeb fix deploy/install os standalone POMs
discard dc287eb deploy/install POMs as a type of metadata so they are done atomically
discard a125edf change the maven group ID
discard 096a085 convert install mojo to new execute().
discard a2d74c8 handle POM properly
discard cecaa63 PR: MNG-52 change type of maven plugins to "maven-plugin" instead of plugin. This should allow other products to have different plugin types, if necessary.
discard f6d08eb flip pom format
discard 7edcb1a depedency update
discard 93dc6e9 there is no package plugin, so can't prereq on that - and prereqs are ignored now anyway.
discard b55a94d Use a correct prereq.
discard 26a316d - Make install mojo to the same model like deploy mojo - Install and deploy always pom.
discard 6d7e97b o Setting some additional ignores.
discard ca9aef5 *** empty log message ***
discard 1266213 o Adding <modelVersion> to the poms.
discard 551651b o update to account for the embedding changes made in maven-core.
discard 9d1d7f5 plugins' poms are using type = plugin
discard 4f8d844 o Fixing groupId and version tags.
discard 90dc32e fixing pacakge name
discard c00d24a adding required dependencies
discard d988766 the goal name was wrong
discard 02e4023 correcting expression
discard a6ca6cc added generic install plugin. I am not sure if this is a right way of implementing this - but I will need similar things for site plugin - so this will serve as an example for disussion how to attain arbitrary goal(s) from plugin
add 9a1ae60 added generic install plugin. I am not sure if this is a right way of implementing this - but I will need similar things for site plugin - so this will serve as an example for disussion how to attain arbitrary goal(s) from plugin
add 3b92a6a correcting expression
add e908190 the goal name was wrong
add 7f9db62 adding required dependencies
add cc58ad8 fixing pacakge name
add 5987fe6 o Fixing groupId and version tags.
add 53365e7 plugins' poms are using type = plugin
add 4f9b8d0 o update to account for the embedding changes made in maven-core.
add 75938c6 o Adding <modelVersion> to the poms.
add acf8c23 *** empty log message ***
add 089f8fb o Setting some additional ignores.
add 4e51b30 - Make install mojo to the same model like deploy mojo - Install and deploy always pom.
add 8d2aecc Use a correct prereq.
add 00695e4 there is no package plugin, so can't prereq on that - and prereqs are ignored now anyway.
add a6b4801 depedency update
add c7a2d5d flip pom format
add 020360d PR: MNG-52 change type of maven plugins to "maven-plugin" instead of plugin. This should allow other products to have different plugin types, if necessary.
add 5939033 handle POM properly
add cca250a convert install mojo to new execute().
add 8f6858a change the maven group ID
add e8a610f deploy/install POMs as a type of metadata so they are done atomically
add 4506baa fix deploy/install os standalone POMs
add a728c33 rewrite POM with new version on deployment
add 74734c0 update poms for releases
add c01acb4 clean up dependencies.
add e8338aa release alpha-1 plugins
add 2673ca4 split the plugin API and the plugin descriptor code
add 2bdac11 improved error handling and other clean up
add 88a69b6 correct problem where anything with a modified finalName was not installed/deployed
add aa0a963 add more use of ${} expressions, fix problem when } was not at end
add b03588e remove unnecessary maven-core dependencies
add 562159c fix more references to the old package
add 4c0c27f o Cleaned up field-level annotation support (especially descriptor extraction, generation, and building) o Converted all "core" plugins (including maven-core-it-plugin) to use field-level annotations o Removed generation of parameter descriptors for ${/#component.* param specifications. o Added @readonly for parameters that cannot be overridden by user configuration (List override was dangerous here) o Added validation against pom-derived configuration for @readonly para [...]
add 301542d Renamed Plugin.java, AbstractPlugin.java, PluginExecutionRe(quest|sponse) PluginExecutionException to Mojo*
add 7989576 PR: MNG-338 Helpful error message for non-redistributable JARs, eg jdbc
add 7637664 set consistent versions
add 1739c4b use released versions
add 1226b19 bump versions
add 28b1a38 Clean imports
add 4fffe8d PR: MNG-378 Only deploy the release information at the point of release
add 2d4651f remove old cvs ignore files
add a014d83 update parent references to get access to the ci settings
add 2e2f174 o Adding support for <executions/>, which means multiple runs of the same goal/set-of-goals with different configs. o Adding @phase declarations for those mojos that seem to be part of the main build, just for completeness o Added two ITs, to test that <executions/> doesn't mess up the normal operation, and to test multi-execution for a goal.
add 7066fb1 PR: MNG-257
add b80c15d change <model> to <project> in root tag.
add 321a9ec refactoring of the resolveTransitiveDependencies call. simplified by removing a bunch of duplicated code in addArtifacts - no need to merge, you have the full list. separated the original artifacts (dependency artifacts) from the resolved artifacts (getArtifacts)
add fd58aa6 Resolving: MNG-495
add a63475c Update all versions to beta-1-SNAPSHOT
add 934703e Resolving:
add 34ca1e8 PR: MNG-596 add XSD definition to m2 poms and archetypes
add c1186d2 TODOs and cleanup
add 63c6c2d PR: MNG-613 changes versioning to use repository metadata
add dfec639 PR: MNG-613 deploy snapshot information to the correct directory and fix some other minor issues
add 6c0664a PR: MNG-613 make sure versions are aggregated
add 8d222ed Resolving MNG-851. Using MavenProject.getFile() rather than constructing new. Also fixed maven-deploy-plugin with similar bug.
add 85e4a1f update dependency and parent versions
add 693c6c9 [maven-release-plugin] prepare release maven-install-plugin-2.0-beta-1
add f2f2da9 [maven-release-plugin] prepare for next development iteration
add 21741ac goal doesn't require a project
add 1e93e75 PR: MNG-644 remove use of deprecated artifact method (retain signature for backwards compat until next release of install/deploy plugins)
add 9c702fd PR: MNG-653 use the file assigned by the packager for installation/deployment. Error out if that isn't done.
add d8758e7 PR: MNG-1114 install:install-file should not run over subprojects
add 8c0a2c4 upgrade plexus utils to 1.0.4-SNAPSHOT. The group ID has changed, so add a bunch of exclusions to ensure the old is not picked up fix bugs in mboot that wasn't honoring excludes.
add 99cae8f PR: MNG-122 cleanup artifact metadata retrieval exceptions
add bb9c61a more error diagnostics improvements
add a44a887 update versions in plugins
add 26d5e7b [maven-release-plugin] prepare release maven-install-plugin-2.0
add f6b1990 [maven-release-plugin] prepare for next development iteration
add ccfb6b6 cleanup some unused fields
add b2140b4 PR: MNG-1279 Submitted by: Philipp Meier Reviewed by: Brett Porter ability to write a pom on install-file
add 5685382 PR: MNG-1279 Submitted by: Philipp Meier add missing model version to generated pom
add bb50d3b PR: MNG-1322 Submitted By: Allan Ramirez Reviewed By: John Casey
add a7c8863 -added pomFile parameter to make install-file install the jar and the customed pom at the same time.
add 444216d Upgrade parent to 2.0.1 so that the site is deployed in the right location
add 9666a2f Workaround for no primary artifact to install PR: MINSTALL-3
add 5309695 back to previous parent
add 2329520 [maven-release-plugin] prepare release maven-install-plugin-2.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 (b50db05)
\
N -- N -- N refs/tags/maven-install-plugin-2.1 (af70930)
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>'].