Benjamin Bentmann 88216c6532 o Re-introduced distinction between user properties and system properties. We have use cases like interpolation and SUREFIRE-121 where we would like to handle user-specified props specially so a single properties soup is not up to the job. However, I opted not to follow the approach from 2.x where we also collect both system properties and user properties in a combined set called execution properties. Code that embeds Maven and programmatically creates an execution request should be not required to assemble such a mixed properties instance, it would enable bad behavior from Maven by subtle API misuse. Also, for things like the lifecycle participant that wants to inject properties, it should be cristal clear whether it injects a user or a system property, the semantics of something like getExecutionProperties().setProperty() would be unclear however. ... git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@796900 13f79535-47bb-0310-9956-ffa450edef68		2009-07-22 22:43:05 +00:00
..
src	o Re-introduced distinction between user properties and system properties. We have use cases like interpolation and SUREFIRE-121 where we would like to handle user-specified props specially so a single properties soup is not up to the job. However, I opted not to follow the approach from 2.x where we also collect both system properties and user properties in a combined set called execution properties. Code that embeds Maven and programmatically creates an execution request should be not required to assemble such a mixed properties instance, it would enable bad behavior from Maven by subtle API misuse. Also, for things like the lifecycle participant that wants to inject properties, it should be cristal clear whether it injects a user or a system property, the semantics of something like getExecutionProperties().setProperty() would be unclear however.	2009-07-22 22:43:05 +00:00
lifecycle-executor.txt	o taking into account the common case where configuration is specified for many goal in a single configuration element which needs to be accounted for.	2009-05-04 13:09:06 +00:00
plugin-manager.txt	o separated the sorter out of the reactor manager in preparation for making the reactor just an implementation of a local repository. shouldn't be tangled with sorting, that should be done before anything starts	2009-03-28 18:24:05 +00:00
pom.xml	o working on fixing the problem in the MavenTest where the remote repositories are not being set and causing the test to fail	2009-07-21 22:28:54 +00:00
project-builder.txt	o disable the tests in the bootstrap so ben and i can go all the way through to the embedder	2009-05-04 15:32:10 +00:00