Author: nickboldt Date: 2011-05-11 12:55:52 -0400 (Wed, 11 May 2011) New Revision: 31215 Modified: branches/jbosstools-3.2.x/build/parent/pom.xml Log: replace file:// with file:/// to solve '[WARNING] Failed to access p2 repository local.composite (file://home/hudson/static_build_env/jbds/builds/staging/_composite_/3.3.indigo/), will try to use local cache. Reason: org.eclipse.equinox.p2.core.ProvisionException: URI has an authority component' Modified: branches/jbosstools-3.2.x/build/parent/pom.xml =================================================================== --- branches/jbosstools-3.2.x/build/parent/pom.xml 2011-05-11 16:55:34 UTC (rev 31214) +++ branches/jbosstools-3.2.x/build/parent/pom.xml 2011-05-11 16:55:52 UTC (rev 31215) @@ -33,20 +33,20 @@ <!-- 1a. URL of latest JBT target platform site --> <jbosstools-target-platform-repo>http://download.jboss.org/jbosstools/u... - <!-- 1b. or, use -Dtarget.platform.site=file://home/$user/trunk/build/target-platform/REPO/ --> + <!-- 1b. or, use -Dtarget.platform.site=file:///home/$user/trunk/build/target-platform/REPO/ --> <!-- Set this to a path on your own machine, or use remote URL like http://download.jboss.org/jbosstools/updates/target-platform/latest/ Can also generate a local.target file which will always point to your local repo w/o having to edit here. See local.target profile below for more information. --> - <target.platform.site>file://home/hudson/static_build_env/jbds/target-platform/e362-wtp323.target/</target.platform.site> + <target.platform.site>file:///home/hudson/static_build_env/jbds/target-platform/e362-wtp323.target/</target.platform.site> <!-- 2a. URL of latest JBT nightly staging composite site (all the components in once place) --> <jbosstools-nightly-staging-composite>http://download.jboss.org/jbossto... - <!-- 2b., or, use -Plocal.composite -Dlocal.composite=file://path/to/mirror/of/composite/staging/site/ --> - <local.composite>file://home/hudson/static_build_env/jbds/builds/staging/_composite_/3.2_stable_branch/</local.composite> + <!-- 2b., or, use -Plocal.composite -Dlocal.composite=file:///path/to/mirror/of/composite/staging/site/ --> + <local.composite>file:///home/hudson/static_build_env/jbds/builds/staging/_composite_/3.2_stable_branch/</local.composite> - <!-- 3. optionally, use -Plocal.requirements -Dlocal.requirements=file://path/to/mirror/of/composite/requirements/site --> - <local.requirements>file://qa/services/http/binaries/RHDS/updates/helios/</local.requirements> + <!-- 3. optionally, use -Plocal.requirements -Dlocal.requirements=file:///path/to/mirror/of/composite/requirements/site --> + <local.requirements>file:///qa/services/http/binaries/RHDS/updates/helios/</local.requirements> <!-- 4. published aggregate update site goes here, for consumption by QE and downstream JBDS builds --> <jbosstools.update.site>http://download.jboss.org/jbosstools/updates/ni... @@ -330,7 +330,7 @@ </profile> <!-- Time saver: to build everything from scratch from a single local repo - on Hudson cluster or on local machine. Use -Dtarget.platform.site=file://path/to/your/own/repo --> + on Hudson cluster or on local machine. Use -Dtarget.platform.site=file:///path/to/your/own/repo --> <profile> <id>helios-local-target</id> <activation> @@ -352,7 +352,7 @@ </profile> <!-- if you have a local repo mirror of the unified.site, you can use this - profile with the -Dtarget.platform.site=file://path/to/repo to resolve dependencies + profile with the -Dtarget.platform.site=file:///path/to/repo to resolve dependencies without needing to use a local.target file --> <profile> <id>local.site</id>