most issues are dealt with or in jira now

git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@293203 13f79535-47bb-0310-9956-ffa450edef68
This commit is contained in:
Jason van Zyl 2005-10-03 01:47:18 +00:00
parent a922450b0b
commit 95282adf58

View File

@ -9,14 +9,6 @@ When you create the assembly you must manually install it in your
local repository for now in order the maven-embedder-it tests to local repository for now in order the maven-embedder-it tests to
work. jvz. work. jvz.
-- parse xml to in-memory model
Now MavenEmbedder.readProjectWithDependencies()
transitively resolve all dependencies and download them
if anything is missing.
-- we need a callback for progress indication:
download, build, etc
-- run m2 (embedded): including running building, archetypes, etc. -- run m2 (embedded): including running building, archetypes, etc.
-- introspect available plugins and their goals -- introspect available plugins and their goals
@ -34,18 +26,6 @@ work. jvz.
-- the short description (in Eclipse it can be used in Problems view) -- the short description (in Eclipse it can be used in Problems view)
-- detailed description (can be used in annotation/editors markers) -- detailed description (can be used in annotation/editors markers)
-- Need getters for MavenEmbedder properties. E.g. to retrieve default
location of the local repository
-- How to deal with the plugin registry builder whose component descriptor
container references like ${maven.home} and ${user.home}. These can be
placed in the context for plexus.
-- Would be nice to centralize the use of maven.home. Possibly have the
embedder take it in and set a system property of plexus context value.
There seems to be a tad of code duplicated in the plugin registry
builder and the settings builder.
-- What are all the settings that must be provided? Ones that can be set -- What are all the settings that must be provided? Ones that can be set
and what the default values would be if they aren't set. and what the default values would be if they aren't set.
@ -67,17 +47,8 @@ plugin registry and settings should be stored in the tool specific locations
-- local repository will be shared and default to ~/.m2/repository -- local repository will be shared and default to ~/.m2/repository
-- add a method that gives the standard lifecycle phases.
<eu> -- properties param on execute() method
<eu> -- transfet listener and loggers, system out cleanup
<eu> one more thing I need in embedder - writeModel() method
<jdcasey> you know something else that would rock for the eclipse plugin? if <jdcasey> you know something else that would rock for the eclipse plugin? if
F5 triggered a re-resolution of the poms, and recreation of the .classpath, F5 triggered a re-resolution of the poms, and recreation of the .classpath, etc.
etc.
<jdcasey> that way, if the pom was upgraded to the next version-SNAPSHOT, <jdcasey> that way, if the pom was upgraded to the next version-SNAPSHOT,
you'd get it you'd get it
<jdcasey> :) <jdcasey> :)