Community
Participate
Working Groups
Build Identifier: 3.6M7 -- Version: 3.6.0 Build id: I20100429-1549 This changed from 3.6M6 to 3.6M7. It seems like a bug to me. Maybe, it is the intended behavior. When I run a PDE product build (also happens with feature build, Eclipse tries to access http://download.eclipse.org/eclipse/updates/3.6/p2.index. Being behind a proxy server, I see the errors below. I can remove the errors by setting the proxy configuration in Eclipse. But, the real issue is that I want my build to be reproducible. I don't want PDE to access anything from the network that I did not specify. If the build is dependent on a network resource that changes; then, the build will not be reproducible. Why does the build access download.eclipse.org? How can I stop this? Here are the messages: [eclipse.brand.p2.artifacts] May 9, 2010 12:22:34 AM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry [eclipse.brand.p2.artifacts] INFO: I/O exception (java.net.ConnectException) caught when processing request: Connection timed out: connect [eclipse.brand.p2.artifacts] May 9, 2010 12:22:34 AM org.apache.commons.httpclient.HttpMethodDirector executeWithRetry [eclipse.brand.p2.artifacts] INFO: Retrying request [eclipse.brand.p2.artifacts] !SESSION 2010-05-09 00:15:58.373 ----------------------------------------------- [eclipse.brand.p2.artifacts] eclipse.buildId=I20100429-1549 [eclipse.brand.p2.artifacts] java.version=1.6.0_18 [eclipse.brand.p2.artifacts] java.vendor=Sun Microsystems Inc. [eclipse.brand.p2.artifacts] BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US [eclipse.brand.p2.artifacts] Framework arguments: -application org.eclipse.ant.core.antRunner -buildfile .../productBuild.xml -Dbuilder=.../config -Dproduct=.../core.product -DbuildDirectory=.../bld -DbaseLocation=.../eclipse -DpluginPath=.../addons/eclipse [eclipse.brand.p2.artifacts] Command-line arguments: -os win32 -ws win32 -arch x86 -application org.eclipse.ant.core.antRunner -buildfile .../org.eclipse.pde.build_3.6.0.v20100428/scripts/productBuild/productBuild.xml -Dbuilder=.../config -Dproduct=.../core.product -DbuildDirectory=.../bld -DbaseLocation=.../cache/eclipse -DpluginPath=.../addons/eclipse -consoleLog [eclipse.brand.p2.artifacts] [eclipse.brand.p2.artifacts] !ENTRY org.eclipse.equinox.p2.repository 2 0 2010-05-09 00:22:55.326 [eclipse.brand.p2.artifacts] !MESSAGE Connection to http://download.eclipse.org/eclipse/updates/3.6/p2.index failed on Connection timed out: connect. Retry attempt 0 started [eclipse.brand.p2.artifacts] !STACK 0 [eclipse.brand.p2.artifacts] java.net.ConnectException: Connection timed out: connect Reproducible: Always Steps to Reproduce: 1. Run Eclipse on a computer than cannot access http://download.eclipse.org 2. Run a PDE product build 3. See "Connection to http://download.eclipse.org/eclipse/updates/3.6/p2.index failed on Connection timed out: connect. Retry attempt 0 started"
I suspect this is bug 312687. The "repo2runnable" task mentioned there is used during the product build by "eclipse.brand.p2.artifacts". As well as any feature build defining the "repoBaseLocation" property to transform repositories for the build. Please try a RC1 candidate, I20100513-0800 or newer *** This bug has been marked as a duplicate of bug 312687 ***
