Mailing-List: contact dev-help@systemml.incubator.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@systemml.incubator.apache.org
MIME-Version: 1.0
In-Reply-To: <0fa8474f7973d589baff09f39c3845e8@posteo.de>
References: <91461534-247D-4813-9D96-451FF729872C@capitalone.com> <0fa8474f7973d589baff09f39c3845e8@posteo.de>
From: Mike Dusenberry <dusenberrymw@gmail.com>
Date: Fri, 6 Jan 2017 17:31:29 -0800
Message-ID: <CAOE9byF6vhPUtTXdWSP_MTG66S6b++UaiKeA27pUwNoF9TDTyg@mail.gmail.com>
Subject: Re: Maven build failing
To: dev <dev@systemml.incubator.apache.org>
Content-Type: multipart/alternative; boundary=001a114bd270399e9205457719e5
archived-at: Sat, 07 Jan 2017 01:32:02 -0000

--001a114bd270399e9205457719e5
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

Hi Sandeep,

Thanks for reaching out!  The error message looks like a local Maven
issue.  In addition to the suggestion from Felix, another possibility is to
remove (or rename) your Maven cache, typically located at `~/.m2`, and then
try building again with a fresh start.

- Mike


--

Michael W. Dusenberry
GitHub: github.com/dusenberrymw
LinkedIn: linkedin.com/in/mikedusenberry

On Fri, Jan 6, 2017 at 5:26 PM, <fschueler@posteo.de> wrote:

> Hi Sandeep,
>
> it seems like you can't connect to the maven repository. Can you open the
> link to the repository in a browser? (https://repo1.maven.org/maven2/)
> Are you behind a proxy maybe?
>
> If nothing else, you can download a binary release from our website to ge=
t
> started working with SystemML: http://systemml.apache.org/download.html
> The beginners guide (http://systemml.apache.org/get-started) has another
> way of getting started if you don't need to build the source yourself.
>
> - Felix
>
>
> Am 07.01.2017 02:09 schrieb Narayanaswami, Sandeep:
>
>> Dear SystemML community,
>>
>> I attempted the following (as per the Beginners' Guide for Python
>> users<https://apache.github.io/incubator-systemml/beginners-
>> guide-python.html>):
>>
>> git checkout clone https://github.com/apache/incubator-systemml.git
>> cd incubator-systemml
>> mvn clean package -P distribution
>>
>> This resulted in:
>>
>> [INFO] Scanning for projects...
>> Downloading: https://repo1.maven.org/maven2/org/apache/apache/18/apache-
>> 18.pom
>> Downloading:
>> https://raw.github.com/niketanpansare/mavenized-jcuda/mvn-
>> repo/org/apache/apache/18/apache-18.pom
>> [ERROR] [ERROR] Some problems were encountered while processing the POMs=
:
>> [FATAL] Non-resolvable parent POM for
>> org.apache.systemml:systemml:0.12.0-incubating-SNAPSHOT: Could not
>> transfer artifact org.apache:apache:pom:18 from/to central
>> (https://repo1.maven.org/maven2): Connect to repo1.maven.org:443
>> [repo1.maven.org/151.101.32.209] failed: Operation timed out
>> (Connection timed out) and 'parent.relativePath' points at wrong local
>> POM @ line 22, column 10
>> @
>> [ERROR] The build could not read 1 project -> [Help 1]
>> [ERROR]
>> [ERROR]   The project
>> org.apache.systemml:systemml:0.12.0-incubating-SNAPSHOT
>> (/Users/ioz814/Projects/oss/incubator-systemml/pom.xml) has 1 error
>> [ERROR]     Non-resolvable parent POM for
>> org.apache.systemml:systemml:0.12.0-incubating-SNAPSHOT: Could not
>> transfer artifact org.apache:apache:pom:18 from/to central
>> (https://repo1.maven.org/maven2): Connect to repo1.maven.org:443
>> [repo1.maven.org/151.101.32.209] failed: Operation timed out
>> (Connection timed out) and 'parent.relativePath' points at wrong local
>> POM @ line 22, column 10 -> [Help 2]
>> [ERROR]
>> [ERROR] To see the full stack trace of the errors, re-run Maven with
>> the -e switch.
>> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
>> [ERROR]
>> [ERROR] For more information about the errors and possible solutions,
>> please read the following articles:
>> [ERROR] [Help 1]
>> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExceptio=
n
>> [ERROR] [Help 2]
>> http://cwiki.apache.org/confluence/display/MAVEN/Unresolvabl
>> eModelException
>>
>> I=E2=80=99d appreciate any help with resolving this issue.
>>
>> Thanks,
>> Sandeep
>> ________________________________________________________
>>
>> The information contained in this e-mail is confidential and/or
>> proprietary to Capital One and/or its affiliates and may only be used
>> solely in performance of work or services for Capital One. The
>> information transmitted herewith is intended only for use by the
>> individual or entity to which it is addressed. If the reader of this
>> message is not the intended recipient, you are hereby notified that
>> any review, retransmission, dissemination, distribution, copying or
>> other use of, or taking of any action in reliance upon this
>> information is strictly prohibited. If you have received this
>> communication in error, please contact the sender and delete the
>> material from your computer.
>>
>

--001a114bd270399e9205457719e5--