Log of /maven/plugins/trunk/pom.xml
Parent Directory
| 
Revision Log
Revision
829587 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sun Oct 25 14:45:22 2009 UTC
(4 weeks, 3 days ago)
by
bentmann
File length: 12581 byte(s)
Diff to
previous 817789
(
colored)
o Updated to maven-plugin-plugin:2.5.1
o Inherited from (staged) maven-parent:14 in preparation for release
Revision
686649 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sun Aug 17 22:01:21 2008 UTC
(15 months, 1 week ago)
by
aheritier
File length: 18755 byte(s)
Diff to
previous 684818
(
colored)
Deactivate maven-project-info-reports-plugin while we find a solution to not have a cycle with invoker - JVZ : We should probably look at scope while building up the directed graph and not worry about cycles in test dependencies.
Revision
682707 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Aug 5 13:22:01 2008 UTC
(15 months, 3 weeks ago)
by
aheritier
File length: 17889 byte(s)
Diff to
previous 682692
(
colored)
Align activation properties for integration-tests profile because we cannot setup it in the parent (see MNG-3228)
Revision
682692 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Aug 5 12:32:26 2008 UTC
(15 months, 3 weeks ago)
by
aheritier
File length: 18101 byte(s)
Diff to
previous 682211
(
colored)
Use the same activation rule for all integration-tests in plugins builds (-Dintegration-tests=true)
Revision
681840 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Fri Aug 1 21:27:36 2008 UTC
(15 months, 3 weeks ago)
by
aheritier
File length: 17893 byte(s)
Diff to
previous 681715
(
colored)
- Use maven-parent 9-SNAPSHOT
- Remove plugins definitions already set in maven-parent (clean, javadoc, plugin, resources
- Force plugin-plugin to use 2.4.2 in reporting (to be synchronized with pluginsMgt)
Revision
645820 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Apr 8 09:59:02 2008 UTC
(19 months, 2 weeks ago)
by
bentmann
File length: 9985 byte(s)
Diff to
previous 645811
(
colored)
o Locked down to maven-clean-plugin:2.2 and maven-resources-plugin:2.2 (at least until POM inherits from maven-parent:9)
Revision
638626 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Mar 18 22:51:12 2008 UTC
(20 months, 1 week ago)
by
aheritier
File length: 9393 byte(s)
Diff to
previous 638340
(
colored)
Remove maven-toolchains-plugin from modules because it relies on a version of maven not yet released.
Revision
531258 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sun Apr 22 19:30:36 2007 UTC
(2 years, 7 months ago)
by
wsmoak
File length: 6600 byte(s)
Diff to
previous 531251
(
colored)
Follow best practice by declaring maven-site-plugin version 2.0-beta-5. (Also, Velocity processing in maven-site-plugin 2.0-SNAPSHOT is causing problems by evaluating expressions in the docs.)
Revision
531251 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sun Apr 22 18:36:24 2007 UTC
(2 years, 7 months ago)
by
wsmoak
File length: 6560 byte(s)
Diff to
previous 528812
(
colored)
Configure the site plugin to stage plugin sites under /plugins/${artifactId}-${version}.
Use 'mvn site:stage-deploy' to publish docs for snapshots or to stage docs for a release.
Revision
499234 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Jan 24 03:35:53 2007 UTC
(2 years, 10 months ago)
by
brett
File length: 7962 byte(s)
Diff to
previous 494359
(
colored)
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)
Revision
494359 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Jan 9 10:30:16 2007 UTC
(2 years, 10 months ago)
by
brett
File length: 9233 byte(s)
Diff to
previous 494350
(
colored)
- move plugin-plugin out of 'reporting' for plugins. It's a required part of the site, and does not cause any issues with the reactor or site generation
- update to snapshots
Revision
491162 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sat Dec 30 03:14:55 2006 UTC
(2 years, 10 months ago)
by
brett
File length: 9291 byte(s)
Diff to
previous 490210
(
colored)
Keep what we have now, but simplify it. Verified to produce the same results as previously by using help:effective-pom.
Revision
485066 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Sat Dec 9 21:46:52 2006 UTC
(2 years, 11 months ago)
by
jvanzyl
File length: 9403 byte(s)
Diff to
previous 485060
(
colored)
o couple problems with the release profile
- the deployment is running twice
- the JavaDoc and Source JARs aren't getting signed
Revision
480591 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Nov 29 15:15:19 2006 UTC
(2 years, 11 months ago)
by
jvanzyl
File length: 6753 byte(s)
Diff to
previous 477309
(
colored)
o add a profile for processing shared resources, in this case we are talking about license files being inserted
into archives created by the JAR, JavaDoc, and Source Jar plugins.
Revision
477309 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Nov 20 20:08:46 2006 UTC
(3 years ago)
by
jdcasey
File length: 6087 byte(s)
Diff to
previous 470805
(
colored)
Changing to the maven-plugin-surrogate-parent:5-SNAPSHOT POM that works around the main maven parent-POM's use of reporting to avoid a cycle when trying to build all plugins from the parent level.
Revision
424442 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Fri Jul 21 20:19:40 2006 UTC
(3 years, 4 months ago)
by
vsiveton
File length: 6242 byte(s)
Diff to
previous 420544
(
colored)
MNG-2460: Incorrect POM inheritance for plugins
Added missing <issueManagement/> and <mailingLists/> tags in pom.xml
Revision
312827 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Oct 11 07:35:33 2005 UTC
(4 years, 1 month ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 6875 byte(s)
Diff to
previous 307294
(
colored)
Resolving: MNG-449, MNG-152, MNG-1090, MNG-1089, MNG-1122
o Removed -cpl and related command line switches for controlling use of LATEST metadata for resolving plugin versions
o Made LATEST the only metadata used to resolve plugin versions, since this is also available when releases are performed
o Added various error diagnostics for project build exceptions
o Enhanced artifact not found error diagnostics
o Removed maven-project and added maven-artifact to maven-surefire-plugin's pom
o Removed the stanza that added pluginArtifacts to the test-booter's classpath...they are already covered by the classpathElements
o Fixed ITs in connection to the removal of -cpl
o Changed the plugin manager to detect whether a plugin's artifact file has changed since the plugin container was created...if so, reload it.
o Took the projecthelp plugin out of the build until I can diagnose the problems with its build (probably tomorrow).
Revision
290221 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Sep 19 17:58:46 2005 UTC
(4 years, 2 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 6374 byte(s)
Diff to
previous 289420
(
colored)
Resolving: MNG-878, MNG-880 (again)
o Added full resolution of plugins listed in the project hierarchy
o Added better resolution of snapshots within the reactor, and resolution of ${finalName}
o Added usage of fully inherited model for release-pom.xml, to enable convergence of all POM inheritance to a single POM with no parent.
o Improved handling of SCM info in a reactored situation.
Revision
280539 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Sep 13 11:41:52 2005 UTC
(4 years, 2 months ago)
by
kenney
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 6225 byte(s)
Diff to
previous 279526
(
colored)
o Put modello-maven-plugin under dependencyManagement and chose version
1.0-alpha-5-SNAPSHOT for all so they're all the same.
o Updated modello plugin invocations in all poms to by adding execution elements
and fixing goals section to get rid of deprecated notation.
o Removed dependency on modello-core in maven-plugin-tools; it seems it
was there because maven-plugin-tools-java used StringUtils from modello -
changed that to use the plexus-utils version.
o Reversed commons-cli version back to 1.0 (brett asked me to, a few days back).
o Updated all models to use fully qualified classnames - do not assume
java.util.* is included! (it won't be anymore from modello
1.0-alpha-5-SNAPSHOT onward).
o Added some <?xml processing instructions to some models that didn't have them
- vim now recognizes these files as XML (so I get syntax highlighting :))
Revision
231230 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Aug 10 13:38:21 2005 UTC
(4 years, 3 months ago)
by
kenney
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 5720 byte(s)
Diff to
previous 227088
(
colored)
Donating maven-antrun-plugin to the Maven2 project, as discussed with Brett.
Enjoy! :-)
TODO:
o make <echo>...</echo> output visible.
o devise a way to pass on maven2 properties to <ant/>-called build.xml files.
The ant code just copies all properties from the default PropertyHandler,
however with m2 that's not possible since they are resolved/evaluated at
runtime.
Revision
227084 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Aug 2 21:34:54 2005 UTC
(4 years, 3 months ago)
by
kenney
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 5255 byte(s)
Diff to
previous 226783
(
colored)
o Put all m2 core dependencies (plexus-container-default and plexus-utils)
under dependencyManagement of m2 and maven-plugins, and removed
versions in all poms having either as a parent.
Used version 1.0.2-SNAPSHOT for plexus-utils as that was used in maven-core
and is not overridable.
o Bumped maven-archiver version to 2.0-beta-1-SNAPSHOT for maven-ear-plugin
Revision
216273 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Jul 13 21:57:57 2005 UTC
(4 years, 4 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 3819 byte(s)
Diff to
previous 216013
(
colored)
Working on: MNG-576
o Implemented plan from my comments on MNG-576 for looking up lifecycle mappings within plugins.
o Fixed subtle bug in DefaultWagonManager for verifying checksums, where the destination file was being used to verify the checksum rather than the recently download temp destination.
o Fixed the DefaultRepositoryMetadataManager.resolve(..) method to allow the locally-installed metadata to be used if it is newer than the one resolved from the repository.
o Moved the lifecycle mappings for the EJB and WAR plugins out to META-INF/plexus/components.xml in the respective plugin's src/main/resources directory. it0016 and it0017 still pass.
o Changed the distributionManagement repository for maven-plugins/pom.xml to have id of 'central-plugins' and then added a normal artifact repository definition for central-plugins to that pom, to allow locally-installed repository metadata for the plugins to be put in the right place (and these builds should have access to the central plugin repo anyway).
o Changed the DefaultPluginMappingBuilder to only warn when plugins.xml for a particular plugin group is missing.
Revision
216013 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Jul 12 20:08:21 2005 UTC
(4 years, 4 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 3546 byte(s)
Diff to
previous 209083
(
colored)
Fixing problem with using distributionManagement repository definition for download of plugins.xml metadata.
Now, in order to build a maven plugin, you need two things:
1. a repository defined in distributionManagment
2. a repository defined in <repositories/> which has the same id as the one in distributionManagement.
This is necessary, since in most cases SSH will be used in the distributionManagement definition for uploading the plugin...which means that the download of the existing plugins.xml file might not be available for users trying to run an install. SSH requires authentication information, and users (particularly those running the bootstrap) might not have this auth info.
Revision
193082 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Thu Jun 23 06:03:10 2005 UTC
(4 years, 5 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 3490 byte(s)
Diff to
previous 193080
(
colored)
Resolving: MNG-495
o Pressing [ENTER] at a plugin update prompt should result in the plugin being registered, as indicated by the prompt.
o Use CLI switch '--no-plugin-updates' to suppress usage of the plugin registry
o Use CLI switch '--update-plugins' to force updated/resolved plugin versions to be registered
o Neither of these has a short CLI option, since we're starting to run out of sensible char options for these types of things.
Revision
191533 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Mon Jun 20 18:47:58 2005 UTC
(4 years, 5 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 3718 byte(s)
Diff to
previous 189878
(
colored)
Commenting maven-eclipse-plugin and it0027...eclipse plugin is missing from injected parameters, and it0027 cannot find core-it:fork. NOTE: this is based on a mirror setup directly to ibiblio.org, since codehaus was having web problems. When codehaus is again reliable, I'll take the mirror back out and try it0027 again...
Revision
189612 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Wed Jun 8 17:54:11 2005 UTC
(4 years, 5 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 3451 byte(s)
Diff to
previous 187639
(
colored)
o Started maven-projecthelp-plugin to help with build analysis (this helped me to visualize profile stuff)
current goals:
projecthelp:active-profiles
projecthelp:effective-pom
o Added source attribute to the Profile model class in maven-model, along with code in the normalization utilities (converters from profiles.xml and settings.xml models to maven-model instances) to identify the source of a particular profile.
o Added a activeProfiles cache of the Profiles in effect for the current project, on the MavenProject class
Revision
187639 -
(
view)
(
annotate)
-
[select for diffs]
Modified
Tue Jun 7 00:37:01 2005 UTC
(4 years, 5 months ago)
by
jdcasey
Original Path:
maven/components/trunk/maven-plugins/pom.xml
File length: 3405 byte(s)
Diff to
previous 170649
(
colored)
o Removed dependency on plexus-container-artifact, using nested DefaultPlexusContainer instances instead for plugin isolation.
o Moved marmalade support dependencies out of maven-core, since they can be supported on demand now
o changed the ordering of the ant and assembly plugins, to show that the classloader (plugin param) bug is fixed.
o added a method in PluginDescriptor which is similar to o.a.m.model.Plugin.getId() (I think that's the method; it's the one that results in a key of 'g:a')
o moved wagon-ssh dependency into maven-core, since there is a new issue related to nested containers and wagons which are introduced as plugin dependencies. This should be solved using a mechanism similar to plugin-manager for wagon-manager impl in future anyway
This form allows you to request diffs between any two revisions of this file.
For each of the two "sides" of the diff,
enter a numeric revision.
