You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@maven.apache.org by jv...@apache.org on 2014/02/10 17:18:59 UTC
[1/2] git commit: Collapse all README files into a single markdown
file which shows up nicely on Github and is easy to read by itself in text
form.
Updated Branches:
refs/heads/master f8afa711d -> 2a0454cae
Collapse all README files into a single markdown file which shows up nicely on Github and is easy to read by itself in text form.
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/9c124e9a
Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/9c124e9a
Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/9c124e9a
Branch: refs/heads/master
Commit: 9c124e9a9ae9552369cf55ffdb478808de1585f8
Parents: f8afa71
Author: Jason van Zyl <ja...@tesla.io>
Authored: Mon Feb 10 10:52:13 2014 -0500
Committer: Jason van Zyl <ja...@tesla.io>
Committed: Mon Feb 10 10:52:13 2014 -0500
----------------------------------------------------------------------
README.bootstrap.txt | 19 -------------------
README.md | 38 ++++++++++++++++++++++++++------------
README.txt | 4 ----
3 files changed, 26 insertions(+), 35 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/maven/blob/9c124e9a/README.bootstrap.txt
----------------------------------------------------------------------
diff --git a/README.bootstrap.txt b/README.bootstrap.txt
deleted file mode 100644
index f3a0449..0000000
--- a/README.bootstrap.txt
+++ /dev/null
@@ -1,19 +0,0 @@
-BOOTSTRAPPING BASICS
------------------------
-
-You'll need:
-
-- Java 1.5
-- Ant 1.8 or later
-
-First, give Ant a location into which the completed Maven distro should be installed:
-
- export M2_HOME=$HOME/apps/maven/apache-maven-3.0-SNAPSHOT
-
-Then, run Ant:
-
- ant
-
-Once the build completes, you should have a new Maven distro ready to roll in your $M2_HOME directory!
-
-Enjoy.
http://git-wip-us.apache.org/repos/asf/maven/blob/9c124e9a/README.md
----------------------------------------------------------------------
diff --git a/README.md b/README.md
index 3f4ed4e..ab3aaf2 100644
--- a/README.md
+++ b/README.md
@@ -1,15 +1,29 @@
-Homepage
-========
-<http://maven.apache.org/>
+# Maven
-Wiki
-====
-<https://cwiki.apache.org/confluence/display/MAVEN/Index>
+Maven is available under the [The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt)
-Issue Tracker
-=============
-<http://jira.codehaus.org/browse/MNG>
+- [Maven Issue Tracker](http://jira.codehaus.org/browse/MNG)
+- [Maven Wiki](https://cwiki.apache.org/confluence/display/MAVEN/Index)
+- [Building Maven](http://maven.apache.org/guides/development/guide-building-m2.html)
+
+## Bootstrapping Basics
+
+If you want to bootstrap Maven you'll need:
+
+- Java 1.6+
+- Ant 1.8 or later
+
+First, give Ant a location into which the completed Maven distro should be installed:
+
+```
+export M2_HOME=$HOME/apps/maven/apache-maven-3.0-SNAPSHOT
+```
+
+Then, run Ant:
+
+```
+ant
+```
+
+Once the build completes, you should have a new Maven distro ready to roll in your $M2_HOME directory!
-License
-=======
-[The Apache Software License, Version 2.0](http://www.apache.org/licenses/LICENSE-2.0.txt)
http://git-wip-us.apache.org/repos/asf/maven/blob/9c124e9a/README.txt
----------------------------------------------------------------------
diff --git a/README.txt b/README.txt
deleted file mode 100644
index df3dd45..0000000
--- a/README.txt
+++ /dev/null
@@ -1,4 +0,0 @@
-See:
-
-http://maven.apache.org/guides/development/guide-building-m2.html
-
[2/2] git commit: Remove my doco file
Posted by jv...@apache.org.
Remove my doco file
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/2a0454ca
Tree: http://git-wip-us.apache.org/repos/asf/maven/tree/2a0454ca
Diff: http://git-wip-us.apache.org/repos/asf/maven/diff/2a0454ca
Branch: refs/heads/master
Commit: 2a0454caecaed95f09811f7c7ebff88024cd9bcb
Parents: 9c124e9
Author: Jason van Zyl <ja...@tesla.io>
Authored: Mon Feb 10 10:53:17 2014 -0500
Committer: Jason van Zyl <ja...@tesla.io>
Committed: Mon Feb 10 10:53:17 2014 -0500
----------------------------------------------------------------------
MavenLifecyle.md | 45 ---------------------------------------------
1 file changed, 45 deletions(-)
----------------------------------------------------------------------
http://git-wip-us.apache.org/repos/asf/maven/blob/2a0454ca/MavenLifecyle.md
----------------------------------------------------------------------
diff --git a/MavenLifecyle.md b/MavenLifecyle.md
deleted file mode 100644
index 1007dea..0000000
--- a/MavenLifecyle.md
+++ /dev/null
@@ -1,45 +0,0 @@
-Maven (DefaultMaven) : doExecute
- - add a build timestamp to the request properties
- - validateLocalRepository: validate local repository (check to make sure it exists and is writable)
- - newRepositorySession: create the RepositorySystemSession
- - AbstractLifecycleParticipant.afterSessionStart
- - event: ExecutionEvent.Type.ProjectDiscoveryStarted
- - set the RepositorySystemSession in the ProjectBuildingRequest
- - getProjectsForMavenReactor
- - this triggers the reading of all the POMs: (NOTE: this could be optimized looking at the POMs if they don't change)
- - create the ReactorReader
- - set RepositorySystemSession.setWorkspaceReader()
- - make the RepositorySystemSession readonly
- ? Can we remove all the @Deprecated methods from MavenSession (4 years, 7 months)
- ? Can we make the MavenSession read-only, do we need a way to share state better
- - AbstractLifecycleParticipant.afterProjectsRead()
- - lifecycleStarter.execute(session)
- - validateProfiles (NOTE: why does this happen at the end?)
-
-# Things to document
-- How the ClassRealms are setup at each stage
-- Having meaningful visuals for the lifecycle and stages
-- explain forked executions
-- remove aggregators, and what are they exactly
-
-# Questions
-
-? forked executions
-? aggregators
-? All the different resolvers: project, plugin, lifecycle
-? Turn if all into JSR330
-
-# Things to refactor
-
-# Isolate project dependency downloads from build execution
-- project dependencies are resolved from the mojo executor
-- separate dependency resolution from build execution, right now they are intertwined
- - if separated then a calculation can be made for the whole set of dependencies
- - make sure dependency resolution works before the build executes
- - not sure there would be much of a speed impact if one assumes the best speeds will happen when everything is downloaded and the
- conflation of these modes and the complexity it creates is not worth it
-
-- turn all to JSR330
-- use LifecycleModuleBuilder consistently instead of BuilderCommon
-- the MavenExecution is calculated in each of the builders instead of once, the implication of this is that project dependency resolution will happen in parallel which means the local repository needs to be safe, and resolution in general.
-- the weave builder uses BuilderCommon directly, should be used the same way the other builders work