Apache Maven core
Go to file
John Dennis Casey a6891c4e25 Adding resolved flag to Artifact.
This is done to counter the possibility that an artifact's file is set without the artifact actually being resolved, as in the case where the artifact is a snapshot version, but no snapshot-enabled repositories exist (think plugin resolution). This also has the beneficial side-effect of providing a more intuitive method of checking whether an artifact has been resolved (rather than artifact.getFile() != null).


git-svn-id: https://svn.apache.org/repos/asf/maven/components/trunk@226333 13f79535-47bb-0310-9956-ffa450edef68
2005-07-29 03:41:02 +00:00
benchmark PR: MNG-596 2005-07-21 13:58:42 +00:00
examples PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-1.x-integration PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-archetype PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-archiver PR: MNG-642 2005-07-27 12:48:52 +00:00
maven-artifact Adding resolved flag to Artifact. 2005-07-29 03:41:02 +00:00
maven-artifact-ant PR: MNG-249 2005-07-28 14:19:03 +00:00
maven-artifact-manager Adding resolved flag to Artifact. 2005-07-29 03:41:02 +00:00
maven-artifact-test PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-core PR: MNG-249 2005-07-28 14:19:03 +00:00
maven-core-it o Changed the it scripts to remove the $MAVEN_OPTS from the verifier launch line, so that we can remotely debug an integration test execution (rather than getting stuck on the verifier execution itself) 2005-07-29 03:07:56 +00:00
maven-core-it-plugin fix typo 2005-07-27 07:27:08 +00:00
maven-core-it-support PR: MNG-598 2005-07-26 09:04:32 +00:00
maven-core-it-verifier no latest on this, consistent with bootstrap 2005-07-27 16:24:45 +00:00
maven-mboot2 this is supposed to be preloaded to the remote repository for integration testing purposes 2005-07-22 00:08:46 +00:00
maven-meeper PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-model PR: MNG-615 2005-07-28 06:35:47 +00:00
maven-monitor PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugin-api PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugin-descriptor Working on MNG-250... 2005-07-29 03:04:38 +00:00
maven-plugin-mapping PR: MNG-598 2005-07-26 09:04:32 +00:00
maven-plugin-registry PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-plugin-tools Working on MNG-250... 2005-07-29 03:04:38 +00:00
maven-plugins PR: MNG-651 2005-07-28 12:17:45 +00:00
maven-profile PR: MNG-456 2005-07-25 09:51:12 +00:00
maven-project Adding resolved flag to Artifact. 2005-07-29 03:41:02 +00:00
maven-reporting Allow the creation of external reports. html files are now generated only by external reports and not by doxia mojo 2005-07-27 14:07:04 +00:00
maven-repository-tools PR: MNG-596 2005-07-21 13:58:42 +00:00
maven-script Working on MNG-250... 2005-07-29 03:04:38 +00:00
maven-settings o Fixing resolution of LATEST in plugin-versions, when <useLatest/> is enabled in plugin-registry.xml, or when --check-plugin-latest is specified on the command line. 2005-07-26 05:54:24 +00:00
maven-site PR: MNG-596 2005-07-21 13:58:42 +00:00
sandbox PR: MNG-596 2005-07-21 13:58:42 +00:00
README.txt o applying patch provided with: http://jira.codehaus.org/browse/MNG-499 2005-07-06 00:24:22 +00:00
ci.sh only mail about skipped run on checkout attempt to allow overlap 2005-07-28 01:17:38 +00:00
m2-bootstrap-all.bat fix in case of a non-existant local repo 2005-07-26 15:11:21 +00:00
m2-bootstrap-all.sh fix in case of a non-existant local repo 2005-07-26 15:11:21 +00:00
plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt adding my notes for implementing plugin inheritance and build profiles. delete if not needed. 2005-05-27 03:29:54 +00:00
pom.xml add license 2005-07-28 12:09:58 +00:00
upgrading-dependencies.apt some notes on changing dependencies 2004-10-23 13:28:06 +00:00

README.txt

-------------------------------------------------------------------------------
Bootstrapping Maven
-------------------------------------------------------------------------------

Set the environment variable M2_HOME pointing to the dir where you want Maven2 installed.

NOTE: presently, the directory {M2_HOME}/bin must be in your path:
set PATH=%PATH%;%M2_HOME%\bin
or
export PATH=$PATH:$M2_HOME/bin

You can set the parameters passed to the Java VM when running Maven2 bootstrap,
setting the environment variable MAVEN_OPTS, e.g.
e.g. to run in offline mode, set MAVEN_OPTS=-o

Then run m2-bootstrap-all.bat (in Windows) or m2-bootstrap-all.sh (in Unix)

NOTE: You must run these instructions from this directory!

If you are behind a firewall, you will need to let the bootstrap process know.
To do this, create a file at ~/.m2/settings.xml and paste in the XML below,
substituting your settings for those provided. You can safely skip the
username, password and nonProxyHost elements if they are not relevant to you.

<settings>
  <proxies>
    <proxy>
      <active>true</active>
      <protocol>http</protocol>
      <host>proxy.somewhere.com</host>
      <port>8080</port>
      <username>proxyuser</username>
      <password>somepassword</password>
      <nonProxyHosts>www.google.com|*.somewhere.com</nonProxyHosts>
    </proxy>
  </proxies>
</settings>