maven/maven-plugins
John Dennis Casey 590e952f02 CHANGES
------------------------

o Factored the layout for a repository into a separate set of components in o.a.m.a.repository.layout

o Added new DefaultRepositoryLayout that uses the repo layout in http://docs.codehaus.org/pages/viewpage.action?pageId=22230 (it is not used by default until we get the repo1 conversion done)

o Added command-line switches to force legacy local-repo or new format (-a/-A, I know, but try to find something that makes more sense!)

o Added path formatting to the repository itself, which is now constructed with a ArtifactRepositoryLayout instance (since layout should be tied to the repository)

o Removed path formatting altogether from the DefaultArtifactHandlerManager.

o Changed the AbstractArtifactBasedComponent (or whatever it's called) to use the repository formatting in the path() and localPath() methods.

o Moved the plugin repo construction (still intact as a hard-coded singleton list) into the DefaultMavenProjectBuilder, where it will eventually build from POM info.

o Added a new method to build an artifact repository for a <distributionManagement/> section, if possible. This reduced the strain on mojos to construct an ArtifactRepository on demand.

o Refactored all *DeployMojo to use #project.distributionManagementArtifactRepository instead of the #settings, #component..ArtifactRepositoryFactory, ... that it used to require. This is a big simplifying step.

o Removed remote artifact repository construction from DefaultMaven, and changed the MavenSession to delegate to MavenProject for remoteArtifactRepositories, just as it does for pluginRepositories.

o Added remoteArtifactRepositories, pluginArtifactRepositories, distributionManagementArtifactRepository to MavenProject as a cache for the higher-level repos used throughout the system. This is project info, so it belongs here.

o Fixed all the tests in maven-core and maven-artifact which I broke. :)

o Dropped what is probably a big format-bomb, since the Eclipse formatter doesn't really handle 'throws Exception' wrapping the right way.

o Added MavenProject to the MavenSession constructor, since there should always be a MavenProject associated with a build, even if it's just the super-pom.

TODO:
--------------------------

- Write an integration/unit test to ensure that the new repo format works with $classifier (was: $extra) and $groupId[0]/../$groupId[n]. This is a simple adaptation of the old layout, but still needs testing.


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@163638 13f79535-47bb-0310-9956-ffa450edef68
2005-03-21 08:18:34 +00:00
..
maven-assemble-plugin make the assembly mojo work, and use field type 2005-03-21 07:59:28 +00:00
maven-clean-plugin make the detection cleaner to make it easier to clean up later 2005-03-21 04:00:46 +00:00
maven-compiler-plugin move log to AbstractPlugin, out of request. Request now contains only parameters (will move to fields) and marmalade context (can move to marmalade mojo wrapper) 2005-03-21 00:07:39 +00:00
maven-deploy-plugin CHANGES 2005-03-21 08:18:34 +00:00
maven-ejb-plugin CHANGES 2005-03-21 08:18:34 +00:00
maven-install-plugin handle POM properly 2005-03-16 01:26:32 +00:00
maven-jar-plugin CHANGES 2005-03-21 08:18:34 +00:00
maven-plugin-plugin PR: MNG-52 2005-03-15 22:31:54 +00:00
maven-pom-plugin CHANGES 2005-03-21 08:18:34 +00:00
maven-resources-plugin PR: MNG-52 2005-03-15 22:31:54 +00:00
maven-surefire-plugin PR: MNG-52 2005-03-15 22:31:54 +00:00
maven-war-plugin move log to AbstractPlugin, out of request. Request now contains only parameters (will move to fields) and marmalade context (can move to marmalade mojo wrapper) 2005-03-21 00:07:39 +00:00
.cvsignore o Setting some additional ignores. 2005-01-03 06:41:15 +00:00
pom.xml flip pom format 2005-03-10 01:35:25 +00:00