You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@olingo.apache.org by David Ventimiglia <dv...@gmail.com> on 2014/12/10 06:13:14 UTC
Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Hi!
I cloned the git repo for olingo v2 and tried to build it using Maven (more
precisely, Maven2) using the instructions here:
http://olingo.apache.org/doc/odata2/maven.html
And got a not-altogether-unfamiliar Maven error:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve dependencies for one or more projects in the
reactor. Reason: Unable to get dependency information: Unable to read the
metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
find parent: org.eclipse.jetty:jetty-parent for project:
null:jetty-project:pom:7.5.4.v20111024 for project
null:jetty-project:pom:7.5.4.v20111024
org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
from the specified remote repositories:
apache.snapshots (http://repository.apache.org/snapshots),
central (http://repo1.maven.org/maven2),
oss.sonatype.org (https://oss.sonatype.org/content/groups/staging)
Path to dependency:
1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
/home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
Before going off on a yak-shaving adventure tracking down dependencies,
I'll just ask here, Is there's an easy known fix for this? Thanks!
Cheers,
David
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
Very good, Michael. You might consider updating the web site to indicate
that people should use Maven 3 when building Olingo v2. I'd be happy to
help with things like that.
Warm regards,
David
On Thu, Dec 11, 2014 at 9:17 PM, Bolz, Michael <mi...@sap.com> wrote:
>
> Hi David,
>
> the problem was a malformed/corrupted Jetty pom file.
> Because of this Maven couldn’t resolve the transitive dependencies from
> Jetty which than fails the build.
>
> I can not say why this was malformed or how it get into your local repo.
> But I guess it happen through your first attempt with Maven 2.
>
> Nevertheless main thing is now it works ;o)
>
> Kind regards,
> Michael
>
> On 11 Dec 2014, at 21:29, David Ventimiglia <dv...@gmail.com> wrote:
>
> Hi Michael,
>
> Deleting the jetty components from the .m2 directory and then compiling
> again worked. Olingo v2 built fine. Can you explain to me *why* it
> worked? Thanks!
>
> Warm regards,
> David
>
> On Thu, Dec 11, 2014 at 10:53 AM, David Ventimiglia <dv...@gmail.com>
> wrote:
>
>> Hi Michael,
>>
>> Here you go.
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2/odata2-lib/odata-testutil$
>> mvn dependency:tree
>> [INFO] Scanning for projects...
>> [WARNING]
>> [WARNING] Some problems were encountered while building the effective
>> model for org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
>> must be unique: org.mockito:mockito-all:jar -> duplicate declaration of
>> version ${mockito.version} @ line 109, column 17
>> [WARNING]
>> [WARNING] It is highly recommended to fix these problems because they
>> threaten the stability of your build.
>> [WARNING]
>> [WARNING] For this reason, future Maven versions might no longer support
>> building such malformed projects.
>> [WARNING]
>> [INFO]
>>
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Building olingo-odata2-testutil 2.0.2-SNAPSHOT
>> [INFO]
>> ------------------------------------------------------------------------
>> [WARNING] The POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>> is invalid, transitive dependencies (if any) will not be available, enable
>> debug logging for more details
>> [WARNING] The POM for org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024
>> is invalid, transitive dependencies (if any) will not be available, enable
>> debug logging for more details
>> [INFO]
>> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
>> olingo-odata2-testutil ---
>> [WARNING] Invalid POM for
>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
>> dependencies (if any) will not be available, enable debug logging for more
>> details
>> [WARNING] Invalid POM for
>> org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024, transitive dependencies
>> (if any) will not be available, enable debug logging for more details
>> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
>> [INFO] +-
>> org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
>> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
>> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
>> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
>> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
>> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
>> [INFO] | | +-
>> org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
>> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
>> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
>> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
>> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
>> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
>> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
>> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
>> [INFO] +- log4j:log4j:jar:1.2.17:compile
>> [INFO] +- junit:junit:jar:4.10:compile
>> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
>> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
>> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
>> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
>> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
>> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
>> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
>> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 3.382s
>> [INFO] Finished at: Thu Dec 11 10:48:07 PST 2014
>> [INFO] Final Memory: 11M/155M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> Please not that I'm experiencing the same build problems on two
>> completely separate machines, one at home and one at work. The machines
>> are different, but what they share in common is that they're both running
>> up-to-date Ubuntu
>> 14.04 LTS.
>>
>> I'll delete the jetty components from the .m2 directory and report back
>> in a separate email. If that fails, I'll change the root pom.xml and
>> report back in a third email.
>>
>> Warm regards,
>> David
>>
>> On Thu, Dec 11, 2014 at 5:15 AM, Bolz, Michael <mi...@sap.com>
>> wrote:
>>
>>> Hi David,
>>>
>>> can you please go into the folder 'odata2-lib/odata-testutil', run 'mvn
>>> dependency:tree' and share the result.
>>>
>>> Normally it should resolve the Jetty dependencies (see my result below)
>>> which are actual necessary for building the testutils.
>>> IMHO it look like the downloaded Jetty POM on your system is 'malformd'.
>>> An workaround could be to delete it and re-run maven (best way is to
>>> delete the whole jetty artifacts from your local Maven repo ->
>>> "/home/dventimi/.m2/repository/org/eclipse/jetty/").
>>> If this not solve the issue you could try to (temporary) upgrade to
>>> newest Jetty 7.x version (7.6.16.v20140903) by setting it in the pom.xml in
>>> the project root (<jetty.version>7.6.16.v20140903</jetty.version>).
>>>
>>> Kind regards,
>>> Michael
>>>
>>> [INFO]
>>> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
>>> olingo-odata2-testutil ---
>>> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
>>> [INFO] +-
>>> org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
>>> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
>>> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
>>> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
>>> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
>>> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
>>> [INFO] | | +-
>>> org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
>>> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
>>> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
>>> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
>>> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
>>> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
>>> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
>>> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
>>> [INFO] +- log4j:log4j:jar:1.2.17:compile
>>> [INFO] +- junit:junit:jar:4.10:compile
>>> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
>>> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
>>> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
>>> [INFO] | \- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:compile
>>> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
>>> [INFO] | +- javax.servlet:servlet-api:jar:2.5:compile
>>> [INFO] | +-
>>> org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:compile
>>> [INFO] | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:compile
>>> [INFO] | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:compile
>>> [INFO] | \-
>>> org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:compile
>>> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
>>> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
>>> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
>>> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] BUILD SUCCESS
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Total time: 20.586s
>>> [INFO] Finished at: Thu Dec 11 14:04:02 CET 2014
>>> [INFO] Final Memory: 11M/245M
>>> [INFO]
>>> ------------------------------------------------------------------------
>>>
>>> On 11 Dec 2014, at 13:16, David Ventimiglia <dv...@gmail.com> wrote:
>>>
>>> As you wish.
>>>
>>> Warm regards,
>>> David
>>>
>>> On Wed, Dec 10, 2014 at 10:14 PM, Bolz, Michael <mi...@sap.com>
>>> wrote:
>>>
>>>> Hi David,
>>>>
>>>> It seems that there are still some strange problems with Maven.
>>>> The project can not build because of missing “javax.*” classes because
>>>> Maven can not resolve the transitive dependency from Jetty (see below).
>>>>
>>>> > [WARNING] Invalid POM for
>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
>>>> dependencies (if any) will not be available, enable debug logging for more
>>>> details
>>>> > TestServer.java:[25,25] error: package javax.servlet.http does not
>>>> exist
>>>>
>>>> Can you please do another build with Maven and activated debug logging:
>>>> “mvn clean install -X” and send the log again ;o)
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>> On 10 Dec 2014, at 21:36, David Ventimiglia <dv...@gmail.com> wrote:
>>>>
>>>> Here you go,
>>>>
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>>>> update-alternatives --config mvn
>>>> [sudo] password for dventimiglia:
>>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>>
>>>> Selection Path Priority Status
>>>> ------------------------------------------------------------
>>>> * 0 /usr/share/maven2/bin/mvn 200 auto mode
>>>> 1 /usr/share/maven/bin/mvn 150 manual mode
>>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>>
>>>> Press enter to keep the current choice[*], or type selection number: 1
>>>> update-alternatives: using /usr/share/maven/bin/mvn to provide
>>>> /usr/bin/mvn (mvn) in manual mode
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>>> Apache Maven 3.0.5
>>>> Maven home: /usr/share/maven
>>>> Java version: 1.7.0_65, vendor: Oracle Corporation
>>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family:
>>>> "unix"
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>>>> install > olingo.log
>>>>
>>>> Looks like it may the same problem with Jetty.
>>>> Cheers,
>>>> David
>>>>
>>>> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mi...@apache.org> wrote:
>>>>
>>>>> Hi David,
>>>>>
>>>>> Perhaps I have misunderstood your last mail but after a look into the
>>>>> log and your information in the mail it is the same problem as before.
>>>>> You try to build with Maven 2 which seems to be incompatible with
>>>>> Jetty 7.5.4 (not supported POM version 4.0.0).
>>>>>
>>>>> If possible can you please try with Maven 3 and give feedback ;o)
>>>>>
>>>>> Kind regards,
>>>>> Michael
>>>>>
>>>>>
>>>>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dv...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi Michael,
>>>>>
>>>>> We'll do another round of email, after which I'll create a ticket.
>>>>>
>>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>>>>>> update-alternatives --config mvn
>>>>>> [sudo] password for dventimiglia:
>>>>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>>>>
>>>>>> Selection Path Priority Status
>>>>>> ------------------------------------------------------------
>>>>>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>>>>>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>>>>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>>>>
>>>>>> Press enter to keep the current choice[*], or type selection number: 0
>>>>>> update-alternatives: using /usr/share/maven2/bin/mvn to provide
>>>>>> /usr/bin/mvn (mvn) in auto mode
>>>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn
>>>>>> -version
>>>>>> Apache Maven 2.2.1 (rdebian-14)
>>>>>> Java version: 1.7.0_65
>>>>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family:
>>>>>> "unix"
>>>>>>
>>>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>>>>>> install > olingo.log
>>>>>>
>>>>>
>>>>> I've attached the log file. Like I said, beyond this I'd be happy to
>>>>> create a ticket, and happy to work on it.
>>>>>
>>>>> Warm regards,
>>>>> David
>>>>>
>>>>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mi...@apache.org>wrote:
>>>>>
>>>>>> Hi David,
>>>>>>
>>>>>> Can you please attach the Maven log with the compilations errors.
>>>>>> Another question which Java version and runtime implementation
>>>>>> (OpenJDK?) do you use?
>>>>>>
>>>>>> Perhaps it would be better to create an JIRA issue (
>>>>>> https://issues.apache.org/jira/browse/OLINGO) for the problem you
>>>>>> have found.
>>>>>> Especially if we don’t get it fixed within the next mails ;o)
>>>>>>
>>>>>> Kind regards,
>>>>>> Michael
>>>>>>
>>>>>>
>>>>>>
>>>>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I
>>>>>> switch to Maven 3.0.5 I get a very different set of compilation errors.
>>>>>> Also, I just tried it again on a different machine, though the same OS
>>>>>> (Ubuntu 14.0.4). Again, the steps are:
>>>>>>
>>>>>> 1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>>>>>> 2. cd olingo-odata2
>>>>>> 3. mvn clean install
>>>>>>
>>>>>> Warm regards,
>>>>>> David
>>>>>>
>>>>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com>
>>>>>> wrote:
>>>>>>
>>>>>>> Hi,
>>>>>>>
>>>>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>>>>> See comment in Introduction (
>>>>>>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
>>>>>>> > You will need to use maven 3 from jetty-7.5.3 release going
>>>>>>> forwards.
>>>>>>>
>>>>>>> On a first glance I did not find a workaround.
>>>>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>>>>
>>>>>>> Kind regards,
>>>>>>> Michael
>>>>>>>
>>>>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com>
>>>>>>> wrote:
>>>>>>>
>>>>>>> Hi!
>>>>>>>
>>>>>>> I cloned the git repo for olingo v2 and tried to build it using
>>>>>>> Maven (more precisely, Maven2) using the instructions here:
>>>>>>>
>>>>>>> http://olingo.apache.org/doc/odata2/maven.html
>>>>>>>
>>>>>>> And got a not-altogether-unfamiliar Maven error:
>>>>>>>
>>>>>>> [ERROR] BUILD ERROR
>>>>>>> [INFO]
>>>>>>> ------------------------------------------------------------------------
>>>>>>> [INFO] Failed to resolve dependencies for one or more projects in
>>>>>>> the reactor. Reason: Unable to get dependency information: Unable to read
>>>>>>> the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar':
>>>>>>> Cannot find parent: org.eclipse.jetty:jetty-parent for project:
>>>>>>> null:jetty-project:pom:7.5.4.v20111024 for project
>>>>>>> null:jetty-project:pom:7.5.4.v20111024
>>>>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>>>>
>>>>>>> from the specified remote repositories:
>>>>>>> apache.snapshots (http://repository.apache.org/snapshots),
>>>>>>> central (http://repo1.maven.org/maven2),
>>>>>>> oss.sonatype.org(https://oss.sonatype.org/content/groups/staging)
>>>>>>>
>>>>>>> Path to dependency:
>>>>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
>>>>>>> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>>>>
>>>>>>>
>>>>>>> Before going off on a yak-shaving adventure tracking down
>>>>>>> dependencies, I'll just ask here, Is there's an easy known fix for this?
>>>>>>> Thanks!
>>>>>>>
>>>>>>> Cheers,
>>>>>>> David
>>>>>>>
>>>>>>>
>>>>>>>
>>>>>>
>>>>>
>>>> <olingo.log>
>>>>
>>>>
>>>>
>>> <olingo.log.gz>
>>>
>>>
>>>
>>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move
to olingo-dev)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi David,
the problem was a malformed/corrupted Jetty pom file.
Because of this Maven couldn’t resolve the transitive dependencies from Jetty which than fails the build.
I can not say why this was malformed or how it get into your local repo.
But I guess it happen through your first attempt with Maven 2.
Nevertheless main thing is now it works ;o)
Kind regards,
Michael
> On 11 Dec 2014, at 21:29, David Ventimiglia <dv...@gmail.com> wrote:
>
> Hi Michael,
>
> Deleting the jetty components from the .m2 directory and then compiling again worked. Olingo v2 built fine. Can you explain to me why it worked? Thanks!
>
> Warm regards,
> David
>
> On Thu, Dec 11, 2014 at 10:53 AM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
> Hi Michael,
>
> Here you go.
>
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2/odata2-lib/odata-testutil$ mvn dependency:tree
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective model for org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: org.mockito:mockito-all:jar -> duplicate declaration of version ${mockito.version} @ line 109, column 17
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
> [WARNING]
> [INFO]
> [INFO] ------------------------------------------------------------------------
> [INFO] Building olingo-odata2-testutil 2.0.2-SNAPSHOT
> [INFO] ------------------------------------------------------------------------
> [WARNING] The POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
> [WARNING] The POM for org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ olingo-odata2-testutil ---
> [WARNING] Invalid POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive dependencies (if any) will not be available, enable debug logging for more details
> [WARNING] Invalid POM for org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024, transitive dependencies (if any) will not be available, enable debug logging for more details
> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
> [INFO] +- org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
> [INFO] | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
> [INFO] +- log4j:log4j:jar:1.2.17:compile
> [INFO] +- junit:junit:jar:4.10:compile
> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 3.382s
> [INFO] Finished at: Thu Dec 11 10:48:07 PST 2014
> [INFO] Final Memory: 11M/155M
> [INFO] ------------------------------------------------------------------------
>
> Please not that I'm experiencing the same build problems on two completely separate machines, one at home and one at work. The machines are different, but what they share in common is that they're both running up-to-date Ubuntu
> 14.04 LTS.
>
> I'll delete the jetty components from the .m2 directory and report back in a separate email. If that fails, I'll change the root pom.xml and report back in a third email.
>
> Warm regards,
> David
>
> On Thu, Dec 11, 2014 at 5:15 AM, Bolz, Michael <michael.bolz@sap.com <ma...@sap.com>> wrote:
> Hi David,
>
> can you please go into the folder 'odata2-lib/odata-testutil', run 'mvn dependency:tree' and share the result.
>
> Normally it should resolve the Jetty dependencies (see my result below) which are actual necessary for building the testutils.
> IMHO it look like the downloaded Jetty POM on your system is 'malformd'.
> An workaround could be to delete it and re-run maven (best way is to delete the whole jetty artifacts from your local Maven repo -> "/home/dventimi/.m2/repository/org/eclipse/jetty/").
> If this not solve the issue you could try to (temporary) upgrade to newest Jetty 7.x version (7.6.16.v20140903) by setting it in the pom.xml in the project root (<jetty.version>7.6.16.v20140903</jetty.version>).
>
> Kind regards,
> Michael
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ olingo-odata2-testutil ---
> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
> [INFO] +- org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
> [INFO] | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
> [INFO] +- log4j:log4j:jar:1.2.17:compile
> [INFO] +- junit:junit:jar:4.10:compile
> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:compile
> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
> [INFO] | +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] | +- org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:compile
> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
> [INFO] ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO] ------------------------------------------------------------------------
> [INFO] Total time: 20.586s
> [INFO] Finished at: Thu Dec 11 14:04:02 CET 2014
> [INFO] Final Memory: 11M/245M
> [INFO] ------------------------------------------------------------------------
>
>> On 11 Dec 2014, at 13:16, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>
>> As you wish.
>>
>> Warm regards,
>> David
>>
>> On Wed, Dec 10, 2014 at 10:14 PM, Bolz, Michael <michael.bolz@sap.com <ma...@sap.com>> wrote:
>> Hi David,
>>
>> It seems that there are still some strange problems with Maven.
>> The project can not build because of missing “javax.*” classes because Maven can not resolve the transitive dependency from Jetty (see below).
>>
>> > [WARNING] Invalid POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive dependencies (if any) will not be available, enable debug logging for more details
>> > TestServer.java:[25,25] error: package javax.servlet.http does not exist
>>
>> Can you please do another build with Maven and activated debug logging: “mvn clean install -X” and send the log again ;o)
>>
>> Kind regards,
>> Michael
>>
>>> On 10 Dec 2014, at 21:36, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Here you go,
>>>
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
>>> [sudo] password for dventimiglia:
>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>
>>> Selection Path Priority Status
>>> ------------------------------------------------------------
>>> * 0 /usr/share/maven2/bin/mvn 200 auto mode
>>> 1 /usr/share/maven/bin/mvn 150 manual mode
>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>
>>> Press enter to keep the current choice[*], or type selection number: 1
>>> update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn (mvn) in manual mode
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>> Apache Maven 3.0.5
>>> Maven home: /usr/share/maven
>>> Java version: 1.7.0_65, vendor: Oracle Corporation
>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family: "unix"
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>>>
>>> Looks like it may the same problem with Jetty.
>>> Cheers,
>>> David
>>>
>>> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mibo@apache.org <ma...@apache.org>> wrote:
>>> Hi David,
>>>
>>> Perhaps I have misunderstood your last mail but after a look into the log and your information in the mail it is the same problem as before.
>>> You try to build with Maven 2 which seems to be incompatible with Jetty 7.5.4 (not supported POM version 4.0.0).
>>>
>>> If possible can you please try with Maven 3 and give feedback ;o)
>>>
>>> Kind regards,
>>> Michael
>>>
>>>
>>>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> We'll do another round of email, after which I'll create a ticket.
>>>>
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
>>>> [sudo] password for dventimiglia:
>>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>>
>>>> Selection Path Priority Status
>>>> ------------------------------------------------------------
>>>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>>>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>>
>>>> Press enter to keep the current choice[*], or type selection number: 0
>>>> update-alternatives: using /usr/share/maven2/bin/mvn to provide /usr/bin/mvn (mvn) in auto mode
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>>> Apache Maven 2.2.1 (rdebian-14)
>>>> Java version: 1.7.0_65
>>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family: "unix"
>>>>
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>>>>
>>>> I've attached the log file. Like I said, beyond this I'd be happy to create a ticket, and happy to work on it.
>>>>
>>>> Warm regards,
>>>> David
>>>>
>>>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mibo@apache.org <ma...@apache.org>>wrote:
>>>> Hi David,
>>>>
>>>> Can you please attach the Maven log with the compilations errors.
>>>> Another question which Java version and runtime implementation (OpenJDK?) do you use?
>>>>
>>>> Perhaps it would be better to create an JIRA issue (https://issues.apache.org/jira/browse/OLINGO <https://issues.apache.org/jira/browse/OLINGO>) for the problem you have found.
>>>> Especially if we don’t get it fixed within the next mails ;o)
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>>
>>>>
>>>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I switch to Maven 3.0.5 I get a very different set of compilation errors. Also, I just tried it again on a different machine, though the same OS (Ubuntu 14.0.4). Again, the steps are:
>>>>> git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2 <https://git-wip-us.apache.org/repos/asf/olingo-odata2>
>>>>> cd olingo-odata2
>>>>> mvn clean install
>>>>> Warm regards,
>>>>> David
>>>>>
>>>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <michael.bolz@sap.com <ma...@sap.com>>wrote:
>>>>> Hi,
>>>>>
>>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>>> See comment in Introduction (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin <http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin>).
>>>>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>>>
>>>>> On a first glance I did not find a workaround.
>>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>>
>>>>> Kind regards,
>>>>> Michael
>>>>>
>>>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>>>>
>>>>>> Hi!
>>>>>>
>>>>>> I cloned the git repo for olingo v2 and tried to build it using Maven (more precisely, Maven2) using the instructions here:
>>>>>>
>>>>>> http://olingo.apache.org/doc/odata2/maven.html <http://olingo.apache.org/doc/odata2/maven.html>
>>>>>>
>>>>>> And got a not-altogether-unfamiliar Maven error:
>>>>>>
>>>>>> [ERROR] BUILD ERROR
>>>>>> [INFO] ------------------------------------------------------------------------
>>>>>> [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information: Unable to read the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot find parent: org.eclipse.jetty:jetty-parent for project: null:jetty-project:pom:7.5.4.v20111024 for project null:jetty-project:pom:7.5.4.v20111024
>>>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>>>
>>>>>> from the specified remote repositories:
>>>>>> apache.snapshots (http://repository.apache.org/snapshots <http://repository.apache.org/snapshots>),
>>>>>> central (http://repo1.maven.org/maven2 <http://repo1.maven.org/maven2>),
>>>>>> oss.sonatype.org <http://oss.sonatype.org/>(https://oss.sonatype.org/content/groups/staging <https://oss.sonatype.org/content/groups/staging>)
>>>>>>
>>>>>> Path to dependency:
>>>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>>>
>>>>>>
>>>>>>
>>>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>>>
>>>>>>
>>>>>> Before going off on a yak-shaving adventure tracking down dependencies, I'll just ask here, Is there's an easy known fix for this? Thanks!
>>>>>>
>>>>>> Cheers,
>>>>>> David
>>>>>
>>>>>
>>>>
>>>
>>> <olingo.log>
>>
>>
>> <olingo.log.gz>
>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
Hi Michael,
Deleting the jetty components from the .m2 directory and then compiling
again worked. Olingo v2 built fine. Can you explain to me *why* it
worked? Thanks!
Warm regards,
David
On Thu, Dec 11, 2014 at 10:53 AM, David Ventimiglia <dv...@gmail.com>
wrote:
> Hi Michael,
>
> Here you go.
>
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2/odata2-lib/odata-testutil$
> mvn dependency:tree
> [INFO] Scanning for projects...
> [WARNING]
> [WARNING] Some problems were encountered while building the effective
> model for org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
> [WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
> must be unique: org.mockito:mockito-all:jar -> duplicate declaration of
> version ${mockito.version} @ line 109, column 17
> [WARNING]
> [WARNING] It is highly recommended to fix these problems because they
> threaten the stability of your build.
> [WARNING]
> [WARNING] For this reason, future Maven versions might no longer support
> building such malformed projects.
> [WARNING]
> [INFO]
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Building olingo-odata2-testutil 2.0.2-SNAPSHOT
> [INFO]
> ------------------------------------------------------------------------
> [WARNING] The POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
> is invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
> [WARNING] The POM for org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024
> is invalid, transitive dependencies (if any) will not be available, enable
> debug logging for more details
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
> olingo-odata2-testutil ---
> [WARNING] Invalid POM for
> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> [WARNING] Invalid POM for
> org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024, transitive dependencies
> (if any) will not be available, enable debug logging for more details
> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
> [INFO] +-
> org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
> [INFO] | | +-
> org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
> [INFO] +- log4j:log4j:jar:1.2.17:compile
> [INFO] +- junit:junit:jar:4.10:compile
> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 3.382s
> [INFO] Finished at: Thu Dec 11 10:48:07 PST 2014
> [INFO] Final Memory: 11M/155M
> [INFO]
> ------------------------------------------------------------------------
>
> Please not that I'm experiencing the same build problems on two completely
> separate machines, one at home and one at work. The machines are
> different, but what they share in common is that they're both running
> up-to-date Ubuntu
> 14.04 LTS.
>
> I'll delete the jetty components from the .m2 directory and report back in
> a separate email. If that fails, I'll change the root pom.xml and report
> back in a third email.
>
> Warm regards,
> David
>
> On Thu, Dec 11, 2014 at 5:15 AM, Bolz, Michael <mi...@sap.com>
> wrote:
>
>> Hi David,
>>
>> can you please go into the folder 'odata2-lib/odata-testutil', run 'mvn
>> dependency:tree' and share the result.
>>
>> Normally it should resolve the Jetty dependencies (see my result below)
>> which are actual necessary for building the testutils.
>> IMHO it look like the downloaded Jetty POM on your system is 'malformd'.
>> An workaround could be to delete it and re-run maven (best way is to
>> delete the whole jetty artifacts from your local Maven repo ->
>> "/home/dventimi/.m2/repository/org/eclipse/jetty/").
>> If this not solve the issue you could try to (temporary) upgrade to
>> newest Jetty 7.x version (7.6.16.v20140903) by setting it in the pom.xml in
>> the project root (<jetty.version>7.6.16.v20140903</jetty.version>).
>>
>> Kind regards,
>> Michael
>>
>> [INFO]
>> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
>> olingo-odata2-testutil ---
>> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
>> [INFO] +-
>> org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
>> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
>> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
>> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
>> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
>> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
>> [INFO] | | +-
>> org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
>> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
>> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
>> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
>> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
>> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
>> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
>> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
>> [INFO] +- log4j:log4j:jar:1.2.17:compile
>> [INFO] +- junit:junit:jar:4.10:compile
>> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
>> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
>> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
>> [INFO] | \- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:compile
>> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
>> [INFO] | +- javax.servlet:servlet-api:jar:2.5:compile
>> [INFO] | +-
>> org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:compile
>> [INFO] | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:compile
>> [INFO] | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:compile
>> [INFO] | \-
>> org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:compile
>> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
>> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
>> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
>> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] BUILD SUCCESS
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Total time: 20.586s
>> [INFO] Finished at: Thu Dec 11 14:04:02 CET 2014
>> [INFO] Final Memory: 11M/245M
>> [INFO]
>> ------------------------------------------------------------------------
>>
>> On 11 Dec 2014, at 13:16, David Ventimiglia <dv...@gmail.com> wrote:
>>
>> As you wish.
>>
>> Warm regards,
>> David
>>
>> On Wed, Dec 10, 2014 at 10:14 PM, Bolz, Michael <mi...@sap.com>
>> wrote:
>>
>>> Hi David,
>>>
>>> It seems that there are still some strange problems with Maven.
>>> The project can not build because of missing “javax.*” classes because
>>> Maven can not resolve the transitive dependency from Jetty (see below).
>>>
>>> > [WARNING] Invalid POM for
>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
>>> dependencies (if any) will not be available, enable debug logging for more
>>> details
>>> > TestServer.java:[25,25] error: package javax.servlet.http does not
>>> exist
>>>
>>> Can you please do another build with Maven and activated debug logging:
>>> “mvn clean install -X” and send the log again ;o)
>>>
>>> Kind regards,
>>> Michael
>>>
>>> On 10 Dec 2014, at 21:36, David Ventimiglia <dv...@gmail.com> wrote:
>>>
>>> Here you go,
>>>
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>>> update-alternatives --config mvn
>>> [sudo] password for dventimiglia:
>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>
>>> Selection Path Priority Status
>>> ------------------------------------------------------------
>>> * 0 /usr/share/maven2/bin/mvn 200 auto mode
>>> 1 /usr/share/maven/bin/mvn 150 manual mode
>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>
>>> Press enter to keep the current choice[*], or type selection number: 1
>>> update-alternatives: using /usr/share/maven/bin/mvn to provide
>>> /usr/bin/mvn (mvn) in manual mode
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>> Apache Maven 3.0.5
>>> Maven home: /usr/share/maven
>>> Java version: 1.7.0_65, vendor: Oracle Corporation
>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family:
>>> "unix"
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>>> install > olingo.log
>>>
>>> Looks like it may the same problem with Jetty.
>>> Cheers,
>>> David
>>>
>>> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mi...@apache.org> wrote:
>>>
>>>> Hi David,
>>>>
>>>> Perhaps I have misunderstood your last mail but after a look into the
>>>> log and your information in the mail it is the same problem as before.
>>>> You try to build with Maven 2 which seems to be incompatible with Jetty
>>>> 7.5.4 (not supported POM version 4.0.0).
>>>>
>>>> If possible can you please try with Maven 3 and give feedback ;o)
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>>
>>>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dv...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi Michael,
>>>>
>>>> We'll do another round of email, after which I'll create a ticket.
>>>>
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>>>>> update-alternatives --config mvn
>>>>> [sudo] password for dventimiglia:
>>>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>>>
>>>>> Selection Path Priority Status
>>>>> ------------------------------------------------------------
>>>>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>>>>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>>>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>>>
>>>>> Press enter to keep the current choice[*], or type selection number: 0
>>>>> update-alternatives: using /usr/share/maven2/bin/mvn to provide
>>>>> /usr/bin/mvn (mvn) in auto mode
>>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>>>> Apache Maven 2.2.1 (rdebian-14)
>>>>> Java version: 1.7.0_65
>>>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>>>> Default locale: en_US, platform encoding: UTF-8
>>>>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family:
>>>>> "unix"
>>>>>
>>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>>>>> install > olingo.log
>>>>>
>>>>
>>>> I've attached the log file. Like I said, beyond this I'd be happy to
>>>> create a ticket, and happy to work on it.
>>>>
>>>> Warm regards,
>>>> David
>>>>
>>>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mi...@apache.org>wrote:
>>>>
>>>>> Hi David,
>>>>>
>>>>> Can you please attach the Maven log with the compilations errors.
>>>>> Another question which Java version and runtime implementation
>>>>> (OpenJDK?) do you use?
>>>>>
>>>>> Perhaps it would be better to create an JIRA issue (
>>>>> https://issues.apache.org/jira/browse/OLINGO) for the problem you
>>>>> have found.
>>>>> Especially if we don’t get it fixed within the next mails ;o)
>>>>>
>>>>> Kind regards,
>>>>> Michael
>>>>>
>>>>>
>>>>>
>>>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi,
>>>>>
>>>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I
>>>>> switch to Maven 3.0.5 I get a very different set of compilation errors.
>>>>> Also, I just tried it again on a different machine, though the same OS
>>>>> (Ubuntu 14.0.4). Again, the steps are:
>>>>>
>>>>> 1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>>>>> 2. cd olingo-odata2
>>>>> 3. mvn clean install
>>>>>
>>>>> Warm regards,
>>>>> David
>>>>>
>>>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com>
>>>>> wrote:
>>>>>
>>>>>> Hi,
>>>>>>
>>>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>>>> See comment in Introduction (
>>>>>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
>>>>>> > You will need to use maven 3 from jetty-7.5.3 release going
>>>>>> forwards.
>>>>>>
>>>>>> On a first glance I did not find a workaround.
>>>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>>>
>>>>>> Kind regards,
>>>>>> Michael
>>>>>>
>>>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com>
>>>>>> wrote:
>>>>>>
>>>>>> Hi!
>>>>>>
>>>>>> I cloned the git repo for olingo v2 and tried to build it using Maven
>>>>>> (more precisely, Maven2) using the instructions here:
>>>>>>
>>>>>> http://olingo.apache.org/doc/odata2/maven.html
>>>>>>
>>>>>> And got a not-altogether-unfamiliar Maven error:
>>>>>>
>>>>>> [ERROR] BUILD ERROR
>>>>>> [INFO]
>>>>>> ------------------------------------------------------------------------
>>>>>> [INFO] Failed to resolve dependencies for one or more projects in the
>>>>>> reactor. Reason: Unable to get dependency information: Unable to read the
>>>>>> metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
>>>>>> find parent: org.eclipse.jetty:jetty-parent for project:
>>>>>> null:jetty-project:pom:7.5.4.v20111024 for project
>>>>>> null:jetty-project:pom:7.5.4.v20111024
>>>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>>>
>>>>>> from the specified remote repositories:
>>>>>> apache.snapshots (http://repository.apache.org/snapshots),
>>>>>> central (http://repo1.maven.org/maven2),
>>>>>> oss.sonatype.org(https://oss.sonatype.org/content/groups/staging)
>>>>>>
>>>>>> Path to dependency:
>>>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>>>
>>>>>>
>>>>>>
>>>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
>>>>>> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>>>
>>>>>>
>>>>>> Before going off on a yak-shaving adventure tracking down
>>>>>> dependencies, I'll just ask here, Is there's an easy known fix for this?
>>>>>> Thanks!
>>>>>>
>>>>>> Cheers,
>>>>>> David
>>>>>>
>>>>>>
>>>>>>
>>>>>
>>>>
>>> <olingo.log>
>>>
>>>
>>>
>> <olingo.log.gz>
>>
>>
>>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
Hi Michael,
Here you go.
dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2/odata2-lib/odata-testutil$
mvn dependency:tree
[INFO] Scanning for projects...
[WARNING]
[WARNING] Some problems were encountered while building the effective model
for org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)'
must be unique: org.mockito:mockito-all:jar -> duplicate declaration of
version ${mockito.version} @ line 109, column 17
[WARNING]
[WARNING] It is highly recommended to fix these problems because they
threaten the stability of your build.
[WARNING]
[WARNING] For this reason, future Maven versions might no longer support
building such malformed projects.
[WARNING]
[INFO]
[INFO]
------------------------------------------------------------------------
[INFO] Building olingo-odata2-testutil 2.0.2-SNAPSHOT
[INFO]
------------------------------------------------------------------------
[WARNING] The POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
is invalid, transitive dependencies (if any) will not be available, enable
debug logging for more details
[WARNING] The POM for org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024 is
invalid, transitive dependencies (if any) will not be available, enable
debug logging for more details
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
olingo-odata2-testutil ---
[WARNING] Invalid POM for
org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
dependencies (if any) will not be available, enable debug logging for more
details
[WARNING] Invalid POM for
org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024, transitive dependencies
(if any) will not be available, enable debug logging for more details
[INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
[INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
[INFO] +-
org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
[INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
[INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
[INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
[INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
[INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
[INFO] | | +-
org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
[INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
[INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
[INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
[INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
[INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
[INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
[INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
[INFO] +- log4j:log4j:jar:1.2.17:compile
[INFO] +- junit:junit:jar:4.10:compile
[INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
[INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
[INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
[INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
[INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
[INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] | \- commons-codec:commons-codec:jar:1.6:compile
[INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 3.382s
[INFO] Finished at: Thu Dec 11 10:48:07 PST 2014
[INFO] Final Memory: 11M/155M
[INFO]
------------------------------------------------------------------------
Please not that I'm experiencing the same build problems on two completely
separate machines, one at home and one at work. The machines are
different, but what they share in common is that they're both running
up-to-date Ubuntu
14.04 LTS.
I'll delete the jetty components from the .m2 directory and report back in
a separate email. If that fails, I'll change the root pom.xml and report
back in a third email.
Warm regards,
David
On Thu, Dec 11, 2014 at 5:15 AM, Bolz, Michael <mi...@sap.com> wrote:
> Hi David,
>
> can you please go into the folder 'odata2-lib/odata-testutil', run 'mvn
> dependency:tree' and share the result.
>
> Normally it should resolve the Jetty dependencies (see my result below)
> which are actual necessary for building the testutils.
> IMHO it look like the downloaded Jetty POM on your system is 'malformd'.
> An workaround could be to delete it and re-run maven (best way is to
> delete the whole jetty artifacts from your local Maven repo ->
> "/home/dventimi/.m2/repository/org/eclipse/jetty/").
> If this not solve the issue you could try to (temporary) upgrade to newest
> Jetty 7.x version (7.6.16.v20140903) by setting it in the pom.xml in the
> project root (<jetty.version>7.6.16.v20140903</jetty.version>).
>
> Kind regards,
> Michael
>
> [INFO]
> [INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @
> olingo-odata2-testutil ---
> [INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
> [INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
> [INFO] +-
> org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
> [INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
> [INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
> [INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
> [INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
> [INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
> [INFO] | | +-
> org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
> [INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
> [INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
> [INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
> [INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
> [INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
> [INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
> [INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
> [INFO] +- log4j:log4j:jar:1.2.17:compile
> [INFO] +- junit:junit:jar:4.10:compile
> [INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
> [INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
> [INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:compile
> [INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
> [INFO] | +- javax.servlet:servlet-api:jar:2.5:compile
> [INFO] | +-
> org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:compile
> [INFO] | \- org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:compile
> [INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
> [INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
> [INFO] | \- commons-codec:commons-codec:jar:1.6:compile
> [INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESS
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 20.586s
> [INFO] Finished at: Thu Dec 11 14:04:02 CET 2014
> [INFO] Final Memory: 11M/245M
> [INFO]
> ------------------------------------------------------------------------
>
> On 11 Dec 2014, at 13:16, David Ventimiglia <dv...@gmail.com> wrote:
>
> As you wish.
>
> Warm regards,
> David
>
> On Wed, Dec 10, 2014 at 10:14 PM, Bolz, Michael <mi...@sap.com>
> wrote:
>
>> Hi David,
>>
>> It seems that there are still some strange problems with Maven.
>> The project can not build because of missing “javax.*” classes because
>> Maven can not resolve the transitive dependency from Jetty (see below).
>>
>> > [WARNING] Invalid POM for
>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
>> dependencies (if any) will not be available, enable debug logging for more
>> details
>> > TestServer.java:[25,25] error: package javax.servlet.http does not exist
>>
>> Can you please do another build with Maven and activated debug logging:
>> “mvn clean install -X” and send the log again ;o)
>>
>> Kind regards,
>> Michael
>>
>> On 10 Dec 2014, at 21:36, David Ventimiglia <dv...@gmail.com> wrote:
>>
>> Here you go,
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>> update-alternatives --config mvn
>> [sudo] password for dventimiglia:
>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>
>> Selection Path Priority Status
>> ------------------------------------------------------------
>> * 0 /usr/share/maven2/bin/mvn 200 auto mode
>> 1 /usr/share/maven/bin/mvn 150 manual mode
>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>
>> Press enter to keep the current choice[*], or type selection number: 1
>> update-alternatives: using /usr/share/maven/bin/mvn to provide
>> /usr/bin/mvn (mvn) in manual mode
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>> Apache Maven 3.0.5
>> Maven home: /usr/share/maven
>> Java version: 1.7.0_65, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family:
>> "unix"
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>> install > olingo.log
>>
>> Looks like it may the same problem with Jetty.
>> Cheers,
>> David
>>
>> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mi...@apache.org> wrote:
>>
>>> Hi David,
>>>
>>> Perhaps I have misunderstood your last mail but after a look into the
>>> log and your information in the mail it is the same problem as before.
>>> You try to build with Maven 2 which seems to be incompatible with Jetty
>>> 7.5.4 (not supported POM version 4.0.0).
>>>
>>> If possible can you please try with Maven 3 and give feedback ;o)
>>>
>>> Kind regards,
>>> Michael
>>>
>>>
>>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dv...@gmail.com>
>>> wrote:
>>>
>>> Hi Michael,
>>>
>>> We'll do another round of email, after which I'll create a ticket.
>>>
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>>>> update-alternatives --config mvn
>>>> [sudo] password for dventimiglia:
>>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>>
>>>> Selection Path Priority Status
>>>> ------------------------------------------------------------
>>>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>>>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>>
>>>> Press enter to keep the current choice[*], or type selection number: 0
>>>> update-alternatives: using /usr/share/maven2/bin/mvn to provide
>>>> /usr/bin/mvn (mvn) in auto mode
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>>> Apache Maven 2.2.1 (rdebian-14)
>>>> Java version: 1.7.0_65
>>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>>> Default locale: en_US, platform encoding: UTF-8
>>>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family:
>>>> "unix"
>>>>
>>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>>>> install > olingo.log
>>>>
>>>
>>> I've attached the log file. Like I said, beyond this I'd be happy to
>>> create a ticket, and happy to work on it.
>>>
>>> Warm regards,
>>> David
>>>
>>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mi...@apache.org>wrote:
>>>
>>>> Hi David,
>>>>
>>>> Can you please attach the Maven log with the compilations errors.
>>>> Another question which Java version and runtime implementation
>>>> (OpenJDK?) do you use?
>>>>
>>>> Perhaps it would be better to create an JIRA issue (
>>>> https://issues.apache.org/jira/browse/OLINGO) for the problem you have
>>>> found.
>>>> Especially if we don’t get it fixed within the next mails ;o)
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>>
>>>>
>>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I
>>>> switch to Maven 3.0.5 I get a very different set of compilation errors.
>>>> Also, I just tried it again on a different machine, though the same OS
>>>> (Ubuntu 14.0.4). Again, the steps are:
>>>>
>>>> 1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>>>> 2. cd olingo-odata2
>>>> 3. mvn clean install
>>>>
>>>> Warm regards,
>>>> David
>>>>
>>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com>
>>>> wrote:
>>>>
>>>>> Hi,
>>>>>
>>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>>> See comment in Introduction (
>>>>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
>>>>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>>>
>>>>> On a first glance I did not find a workaround.
>>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>>
>>>>> Kind regards,
>>>>> Michael
>>>>>
>>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com>
>>>>> wrote:
>>>>>
>>>>> Hi!
>>>>>
>>>>> I cloned the git repo for olingo v2 and tried to build it using Maven
>>>>> (more precisely, Maven2) using the instructions here:
>>>>>
>>>>> http://olingo.apache.org/doc/odata2/maven.html
>>>>>
>>>>> And got a not-altogether-unfamiliar Maven error:
>>>>>
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO]
>>>>> ------------------------------------------------------------------------
>>>>> [INFO] Failed to resolve dependencies for one or more projects in the
>>>>> reactor. Reason: Unable to get dependency information: Unable to read the
>>>>> metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
>>>>> find parent: org.eclipse.jetty:jetty-parent for project:
>>>>> null:jetty-project:pom:7.5.4.v20111024 for project
>>>>> null:jetty-project:pom:7.5.4.v20111024
>>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>>
>>>>> from the specified remote repositories:
>>>>> apache.snapshots (http://repository.apache.org/snapshots),
>>>>> central (http://repo1.maven.org/maven2),
>>>>> oss.sonatype.org(https://oss.sonatype.org/content/groups/staging)
>>>>>
>>>>> Path to dependency:
>>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>>
>>>>>
>>>>>
>>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
>>>>> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>>
>>>>>
>>>>> Before going off on a yak-shaving adventure tracking down
>>>>> dependencies, I'll just ask here, Is there's an easy known fix for this?
>>>>> Thanks!
>>>>>
>>>>> Cheers,
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>
>>>
>> <olingo.log>
>>
>>
>>
> <olingo.log.gz>
>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move
to olingo-dev)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi David,
can you please go into the folder 'odata2-lib/odata-testutil', run 'mvn dependency:tree' and share the result.
Normally it should resolve the Jetty dependencies (see my result below) which are actual necessary for building the testutils.
IMHO it look like the downloaded Jetty POM on your system is 'malformd'.
An workaround could be to delete it and re-run maven (best way is to delete the whole jetty artifacts from your local Maven repo -> "/home/dventimi/.m2/repository/org/eclipse/jetty/").
If this not solve the issue you could try to (temporary) upgrade to newest Jetty 7.x version (7.6.16.v20140903) by setting it in the pom.xml in the project root (<jetty.version>7.6.16.v20140903</jetty.version>).
Kind regards,
Michael
[INFO]
[INFO] --- maven-dependency-plugin:2.1:tree (default-cli) @ olingo-odata2-testutil ---
[INFO] org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
[INFO] +- org.apache.olingo:olingo-odata2-api:jar:2.0.2-SNAPSHOT:compile
[INFO] +- org.apache.olingo:olingo-odata2-api-annotation:jar:2.0.2-SNAPSHOT:compile
[INFO] +- org.apache.cxf:cxf-rt-frontend-jaxrs:jar:2.7.10:compile
[INFO] | +- org.apache.cxf:cxf-api:jar:2.7.10:compile
[INFO] | | +- org.codehaus.woodstox:woodstox-core-asl:jar:4.2.0:compile
[INFO] | | | \- org.codehaus.woodstox:stax2-api:jar:3.1.1:compile
[INFO] | | +- org.apache.ws.xmlschema:xmlschema-core:jar:2.1.0:compile
[INFO] | | +- org.apache.geronimo.specs:geronimo-javamail_1.4_spec:jar:1.7.1:compile
[INFO] | | \- wsdl4j:wsdl4j:jar:1.6.3:compile
[INFO] | +- org.apache.cxf:cxf-rt-core:jar:2.7.10:compile
[INFO] | | \- com.sun.xml.bind:jaxb-impl:jar:2.2.6:compile
[INFO] | +- javax.ws.rs:javax.ws.rs-api:jar:2.0-m10:compile
[INFO] | +- org.apache.cxf:cxf-rt-bindings-xml:jar:2.7.10:compile
[INFO] | \- org.apache.cxf:cxf-rt-transports-http:jar:2.7.10:compile
[INFO] +- org.slf4j:slf4j-api:jar:1.7.1:compile
[INFO] +- log4j:log4j:jar:1.2.17:compile
[INFO] +- junit:junit:jar:4.10:compile
[INFO] | \- org.hamcrest:hamcrest-core:jar:1.1:compile
[INFO] +- org.mockito:mockito-all:jar:1.9.0:compile
[INFO] +- org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024:compile
[INFO] | \- org.eclipse.jetty:jetty-security:jar:7.5.4.v20111024:compile
[INFO] +- org.eclipse.jetty:jetty-server:jar:7.5.4.v20111024:compile
[INFO] | +- javax.servlet:servlet-api:jar:2.5:compile
[INFO] | +- org.eclipse.jetty:jetty-continuation:jar:7.5.4.v20111024:compile
[INFO] | \- org.eclipse.jetty:jetty-http:jar:7.5.4.v20111024:compile
[INFO] | \- org.eclipse.jetty:jetty-io:jar:7.5.4.v20111024:compile
[INFO] | \- org.eclipse.jetty:jetty-util:jar:7.5.4.v20111024:compile
[INFO] +- org.apache.httpcomponents:httpclient:jar:4.2.3:compile
[INFO] | +- commons-logging:commons-logging:jar:1.1.1:compile
[INFO] | \- commons-codec:commons-codec:jar:1.6:compile
[INFO] \- org.apache.httpcomponents:httpcore:jar:4.2.3:compile
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 20.586s
[INFO] Finished at: Thu Dec 11 14:04:02 CET 2014
[INFO] Final Memory: 11M/245M
[INFO] ------------------------------------------------------------------------
> On 11 Dec 2014, at 13:16, David Ventimiglia <dv...@gmail.com> wrote:
>
> As you wish.
>
> Warm regards,
> David
>
> On Wed, Dec 10, 2014 at 10:14 PM, Bolz, Michael <michael.bolz@sap.com <ma...@sap.com>> wrote:
> Hi David,
>
> It seems that there are still some strange problems with Maven.
> The project can not build because of missing “javax.*” classes because Maven can not resolve the transitive dependency from Jetty (see below).
>
> > [WARNING] Invalid POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive dependencies (if any) will not be available, enable debug logging for more details
> > TestServer.java:[25,25] error: package javax.servlet.http does not exist
>
> Can you please do another build with Maven and activated debug logging: “mvn clean install -X” and send the log again ;o)
>
> Kind regards,
> Michael
>
>> On 10 Dec 2014, at 21:36, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>
>> Here you go,
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
>> [sudo] password for dventimiglia:
>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>
>> Selection Path Priority Status
>> ------------------------------------------------------------
>> * 0 /usr/share/maven2/bin/mvn 200 auto mode
>> 1 /usr/share/maven/bin/mvn 150 manual mode
>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>
>> Press enter to keep the current choice[*], or type selection number: 1
>> update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn (mvn) in manual mode
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>> Apache Maven 3.0.5
>> Maven home: /usr/share/maven
>> Java version: 1.7.0_65, vendor: Oracle Corporation
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family: "unix"
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>>
>> Looks like it may the same problem with Jetty.
>> Cheers,
>> David
>>
>> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mibo@apache.org <ma...@apache.org>> wrote:
>> Hi David,
>>
>> Perhaps I have misunderstood your last mail but after a look into the log and your information in the mail it is the same problem as before.
>> You try to build with Maven 2 which seems to be incompatible with Jetty 7.5.4 (not supported POM version 4.0.0).
>>
>> If possible can you please try with Maven 3 and give feedback ;o)
>>
>> Kind regards,
>> Michael
>>
>>
>>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi Michael,
>>>
>>> We'll do another round of email, after which I'll create a ticket.
>>>
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
>>> [sudo] password for dventimiglia:
>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>
>>> Selection Path Priority Status
>>> ------------------------------------------------------------
>>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>
>>> Press enter to keep the current choice[*], or type selection number: 0
>>> update-alternatives: using /usr/share/maven2/bin/mvn to provide /usr/bin/mvn (mvn) in auto mode
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>> Apache Maven 2.2.1 (rdebian-14)
>>> Java version: 1.7.0_65
>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family: "unix"
>>>
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>>>
>>> I've attached the log file. Like I said, beyond this I'd be happy to create a ticket, and happy to work on it.
>>>
>>> Warm regards,
>>> David
>>>
>>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mibo@apache.org <ma...@apache.org>>wrote:
>>> Hi David,
>>>
>>> Can you please attach the Maven log with the compilations errors.
>>> Another question which Java version and runtime implementation (OpenJDK?) do you use?
>>>
>>> Perhaps it would be better to create an JIRA issue (https://issues.apache.org/jira/browse/OLINGO <https://issues.apache.org/jira/browse/OLINGO>) for the problem you have found.
>>> Especially if we don’t get it fixed within the next mails ;o)
>>>
>>> Kind regards,
>>> Michael
>>>
>>>
>>>
>>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi,
>>>>
>>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I switch to Maven 3.0.5 I get a very different set of compilation errors. Also, I just tried it again on a different machine, though the same OS (Ubuntu 14.0.4). Again, the steps are:
>>>> git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2 <https://git-wip-us.apache.org/repos/asf/olingo-odata2>
>>>> cd olingo-odata2
>>>> mvn clean install
>>>> Warm regards,
>>>> David
>>>>
>>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <michael.bolz@sap.com <ma...@sap.com>>wrote:
>>>> Hi,
>>>>
>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>> See comment in Introduction (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin <http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin>).
>>>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>>
>>>> On a first glance I did not find a workaround.
>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>>>
>>>>> Hi!
>>>>>
>>>>> I cloned the git repo for olingo v2 and tried to build it using Maven (more precisely, Maven2) using the instructions here:
>>>>>
>>>>> http://olingo.apache.org/doc/odata2/maven.html <http://olingo.apache.org/doc/odata2/maven.html>
>>>>>
>>>>> And got a not-altogether-unfamiliar Maven error:
>>>>>
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO] ------------------------------------------------------------------------
>>>>> [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information: Unable to read the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot find parent: org.eclipse.jetty:jetty-parent for project: null:jetty-project:pom:7.5.4.v20111024 for project null:jetty-project:pom:7.5.4.v20111024
>>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>>
>>>>> from the specified remote repositories:
>>>>> apache.snapshots (http://repository.apache.org/snapshots <http://repository.apache.org/snapshots>),
>>>>> central (http://repo1.maven.org/maven2 <http://repo1.maven.org/maven2>),
>>>>> oss.sonatype.org <http://oss.sonatype.org/>(https://oss.sonatype.org/content/groups/staging <https://oss.sonatype.org/content/groups/staging>)
>>>>>
>>>>> Path to dependency:
>>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>>
>>>>>
>>>>>
>>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>>
>>>>>
>>>>> Before going off on a yak-shaving adventure tracking down dependencies, I'll just ask here, Is there's an easy known fix for this? Thanks!
>>>>>
>>>>> Cheers,
>>>>> David
>>>>
>>>>
>>>
>>
>> <olingo.log>
>
>
> <olingo.log.gz>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
As you wish.
Warm regards,
David
On Wed, Dec 10, 2014 at 10:14 PM, Bolz, Michael <mi...@sap.com>
wrote:
> Hi David,
>
> It seems that there are still some strange problems with Maven.
> The project can not build because of missing “javax.*” classes because
> Maven can not resolve the transitive dependency from Jetty (see below).
>
> > [WARNING] Invalid POM for
> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive
> dependencies (if any) will not be available, enable debug logging for more
> details
> > TestServer.java:[25,25] error: package javax.servlet.http does not exist
>
> Can you please do another build with Maven and activated debug logging:
> “mvn clean install -X” and send the log again ;o)
>
> Kind regards,
> Michael
>
> On 10 Dec 2014, at 21:36, David Ventimiglia <dv...@gmail.com> wrote:
>
> Here you go,
>
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
> update-alternatives --config mvn
> [sudo] password for dventimiglia:
> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>
> Selection Path Priority Status
> ------------------------------------------------------------
> * 0 /usr/share/maven2/bin/mvn 200 auto mode
> 1 /usr/share/maven/bin/mvn 150 manual mode
> 2 /usr/share/maven2/bin/mvn 200 manual mode
>
> Press enter to keep the current choice[*], or type selection number: 1
> update-alternatives: using /usr/share/maven/bin/mvn to provide
> /usr/bin/mvn (mvn) in manual mode
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
> Apache Maven 3.0.5
> Maven home: /usr/share/maven
> Java version: 1.7.0_65, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family:
> "unix"
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
> install > olingo.log
>
> Looks like it may the same problem with Jetty.
> Cheers,
> David
>
> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mi...@apache.org> wrote:
>
>> Hi David,
>>
>> Perhaps I have misunderstood your last mail but after a look into the log
>> and your information in the mail it is the same problem as before.
>> You try to build with Maven 2 which seems to be incompatible with Jetty
>> 7.5.4 (not supported POM version 4.0.0).
>>
>> If possible can you please try with Maven 3 and give feedback ;o)
>>
>> Kind regards,
>> Michael
>>
>>
>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dv...@gmail.com>
>> wrote:
>>
>> Hi Michael,
>>
>> We'll do another round of email, after which I'll create a ticket.
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>>> update-alternatives --config mvn
>>> [sudo] password for dventimiglia:
>>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>>
>>> Selection Path Priority Status
>>> ------------------------------------------------------------
>>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>>
>>> Press enter to keep the current choice[*], or type selection number: 0
>>> update-alternatives: using /usr/share/maven2/bin/mvn to provide
>>> /usr/bin/mvn (mvn) in auto mode
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>>> Apache Maven 2.2.1 (rdebian-14)
>>> Java version: 1.7.0_65
>>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>>> Default locale: en_US, platform encoding: UTF-8
>>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family:
>>> "unix"
>>>
>>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>>> install > olingo.log
>>>
>>
>> I've attached the log file. Like I said, beyond this I'd be happy to
>> create a ticket, and happy to work on it.
>>
>> Warm regards,
>> David
>>
>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mi...@apache.org>wrote:
>>
>>> Hi David,
>>>
>>> Can you please attach the Maven log with the compilations errors.
>>> Another question which Java version and runtime implementation
>>> (OpenJDK?) do you use?
>>>
>>> Perhaps it would be better to create an JIRA issue (
>>> https://issues.apache.org/jira/browse/OLINGO) for the problem you have
>>> found.
>>> Especially if we don’t get it fixed within the next mails ;o)
>>>
>>> Kind regards,
>>> Michael
>>>
>>>
>>>
>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com>
>>> wrote:
>>>
>>> Hi,
>>>
>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I
>>> switch to Maven 3.0.5 I get a very different set of compilation errors.
>>> Also, I just tried it again on a different machine, though the same OS
>>> (Ubuntu 14.0.4). Again, the steps are:
>>>
>>> 1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>>> 2. cd olingo-odata2
>>> 3. mvn clean install
>>>
>>> Warm regards,
>>> David
>>>
>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com>
>>> wrote:
>>>
>>>> Hi,
>>>>
>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>> See comment in Introduction (
>>>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
>>>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>>
>>>> On a first glance I did not find a workaround.
>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com>
>>>> wrote:
>>>>
>>>> Hi!
>>>>
>>>> I cloned the git repo for olingo v2 and tried to build it using Maven
>>>> (more precisely, Maven2) using the instructions here:
>>>>
>>>> http://olingo.apache.org/doc/odata2/maven.html
>>>>
>>>> And got a not-altogether-unfamiliar Maven error:
>>>>
>>>> [ERROR] BUILD ERROR
>>>> [INFO]
>>>> ------------------------------------------------------------------------
>>>> [INFO] Failed to resolve dependencies for one or more projects in the
>>>> reactor. Reason: Unable to get dependency information: Unable to read the
>>>> metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
>>>> find parent: org.eclipse.jetty:jetty-parent for project:
>>>> null:jetty-project:pom:7.5.4.v20111024 for project
>>>> null:jetty-project:pom:7.5.4.v20111024
>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>
>>>> from the specified remote repositories:
>>>> apache.snapshots (http://repository.apache.org/snapshots),
>>>> central (http://repo1.maven.org/maven2),
>>>> oss.sonatype.org(https://oss.sonatype.org/content/groups/staging)
>>>>
>>>> Path to dependency:
>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>
>>>>
>>>>
>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
>>>> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>
>>>>
>>>> Before going off on a yak-shaving adventure tracking down
>>>> dependencies, I'll just ask here, Is there's an easy known fix for this?
>>>> Thanks!
>>>>
>>>> Cheers,
>>>> David
>>>>
>>>>
>>>>
>>>
>>
> <olingo.log>
>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move
to olingo-dev)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi David,
It seems that there are still some strange problems with Maven.
The project can not build because of missing “javax.*” classes because Maven can not resolve the transitive dependency from Jetty (see below).
> [WARNING] Invalid POM for org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024, transitive dependencies (if any) will not be available, enable debug logging for more details
> TestServer.java:[25,25] error: package javax.servlet.http does not exist
Can you please do another build with Maven and activated debug logging: “mvn clean install -X” and send the log again ;o)
Kind regards,
Michael
> On 10 Dec 2014, at 21:36, David Ventimiglia <dv...@gmail.com> wrote:
>
> Here you go,
>
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
> [sudo] password for dventimiglia:
> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>
> Selection Path Priority Status
> ------------------------------------------------------------
> * 0 /usr/share/maven2/bin/mvn 200 auto mode
> 1 /usr/share/maven/bin/mvn 150 manual mode
> 2 /usr/share/maven2/bin/mvn 200 manual mode
>
> Press enter to keep the current choice[*], or type selection number: 1
> update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn (mvn) in manual mode
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
> Apache Maven 3.0.5
> Maven home: /usr/share/maven
> Java version: 1.7.0_65, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family: "unix"
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>
> Looks like it may the same problem with Jetty.
> Cheers,
> David
>
> On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mibo@apache.org <ma...@apache.org>> wrote:
> Hi David,
>
> Perhaps I have misunderstood your last mail but after a look into the log and your information in the mail it is the same problem as before.
> You try to build with Maven 2 which seems to be incompatible with Jetty 7.5.4 (not supported POM version 4.0.0).
>
> If possible can you please try with Maven 3 and give feedback ;o)
>
> Kind regards,
> Michael
>
>
>> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>
>> Hi Michael,
>>
>> We'll do another round of email, after which I'll create a ticket.
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
>> [sudo] password for dventimiglia:
>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>
>> Selection Path Priority Status
>> ------------------------------------------------------------
>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>
>> Press enter to keep the current choice[*], or type selection number: 0
>> update-alternatives: using /usr/share/maven2/bin/mvn to provide /usr/bin/mvn (mvn) in auto mode
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>> Apache Maven 2.2.1 (rdebian-14)
>> Java version: 1.7.0_65
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family: "unix"
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>>
>> I've attached the log file. Like I said, beyond this I'd be happy to create a ticket, and happy to work on it.
>>
>> Warm regards,
>> David
>>
>> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mibo@apache.org <ma...@apache.org>>wrote:
>> Hi David,
>>
>> Can you please attach the Maven log with the compilations errors.
>> Another question which Java version and runtime implementation (OpenJDK?) do you use?
>>
>> Perhaps it would be better to create an JIRA issue (https://issues.apache.org/jira/browse/OLINGO <https://issues.apache.org/jira/browse/OLINGO>) for the problem you have found.
>> Especially if we don’t get it fixed within the next mails ;o)
>>
>> Kind regards,
>> Michael
>>
>>
>>
>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>
>>> Hi,
>>>
>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I switch to Maven 3.0.5 I get a very different set of compilation errors. Also, I just tried it again on a different machine, though the same OS (Ubuntu 14.0.4). Again, the steps are:
>>> git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2 <https://git-wip-us.apache.org/repos/asf/olingo-odata2>
>>> cd olingo-odata2
>>> mvn clean install
>>> Warm regards,
>>> David
>>>
>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <michael.bolz@sap.com <ma...@sap.com>>wrote:
>>> Hi,
>>>
>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>> See comment in Introduction (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin <http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin>).
>>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>
>>> On a first glance I did not find a workaround.
>>> It is perhaps possible that you upgrade to Maven 3?
>>>
>>> Kind regards,
>>> Michael
>>>
>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dventimi@gmail.com <ma...@gmail.com>> wrote:
>>>>
>>>> Hi!
>>>>
>>>> I cloned the git repo for olingo v2 and tried to build it using Maven (more precisely, Maven2) using the instructions here:
>>>>
>>>> http://olingo.apache.org/doc/odata2/maven.html <http://olingo.apache.org/doc/odata2/maven.html>
>>>>
>>>> And got a not-altogether-unfamiliar Maven error:
>>>>
>>>> [ERROR] BUILD ERROR
>>>> [INFO] ------------------------------------------------------------------------
>>>> [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information: Unable to read the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot find parent: org.eclipse.jetty:jetty-parent for project: null:jetty-project:pom:7.5.4.v20111024 for project null:jetty-project:pom:7.5.4.v20111024
>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>
>>>> from the specified remote repositories:
>>>> apache.snapshots (http://repository.apache.org/snapshots <http://repository.apache.org/snapshots>),
>>>> central (http://repo1.maven.org/maven2 <http://repo1.maven.org/maven2>),
>>>> oss.sonatype.org <http://oss.sonatype.org/>(https://oss.sonatype.org/content/groups/staging <https://oss.sonatype.org/content/groups/staging>)
>>>>
>>>> Path to dependency:
>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>
>>>>
>>>>
>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>
>>>>
>>>> Before going off on a yak-shaving adventure tracking down dependencies, I'll just ask here, Is there's an easy known fix for this? Thanks!
>>>>
>>>> Cheers,
>>>> David
>>>
>>>
>>
>
> <olingo.log>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
Here you go,
dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
update-alternatives --config mvn
[sudo] password for dventimiglia:
There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
Selection Path Priority Status
------------------------------------------------------------
* 0 /usr/share/maven2/bin/mvn 200 auto mode
1 /usr/share/maven/bin/mvn 150 manual mode
2 /usr/share/maven2/bin/mvn 200 manual mode
Press enter to keep the current choice[*], or type selection number: 1
update-alternatives: using /usr/share/maven/bin/mvn to provide /usr/bin/mvn
(mvn) in manual mode
dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
Apache Maven 3.0.5
Maven home: /usr/share/maven
Java version: 1.7.0_65, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "3.13.0-40-generic", arch: "amd64", family:
"unix"
dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install
> olingo.log
Looks like it may the same problem with Jetty.
Cheers,
David
On Wed, Dec 10, 2014 at 11:52 AM, Mibo <mi...@apache.org> wrote:
> Hi David,
>
> Perhaps I have misunderstood your last mail but after a look into the log
> and your information in the mail it is the same problem as before.
> You try to build with Maven 2 which seems to be incompatible with Jetty
> 7.5.4 (not supported POM version 4.0.0).
>
> If possible can you please try with Maven 3 and give feedback ;o)
>
> Kind regards,
> Michael
>
>
> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dv...@gmail.com>
> wrote:
>
> Hi Michael,
>
> We'll do another round of email, after which I'll create a ticket.
>
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
>> update-alternatives --config mvn
>> [sudo] password for dventimiglia:
>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>
>> Selection Path Priority Status
>> ------------------------------------------------------------
>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>
>> Press enter to keep the current choice[*], or type selection number: 0
>> update-alternatives: using /usr/share/maven2/bin/mvn to provide
>> /usr/bin/mvn (mvn) in auto mode
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>> Apache Maven 2.2.1 (rdebian-14)
>> Java version: 1.7.0_65
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family: "unix"
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
>> install > olingo.log
>>
>
> I've attached the log file. Like I said, beyond this I'd be happy to
> create a ticket, and happy to work on it.
>
> Warm regards,
> David
>
> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mi...@apache.org>wrote:
>
>> Hi David,
>>
>> Can you please attach the Maven log with the compilations errors.
>> Another question which Java version and runtime implementation (OpenJDK?)
>> do you use?
>>
>> Perhaps it would be better to create an JIRA issue (
>> https://issues.apache.org/jira/browse/OLINGO) for the problem you have
>> found.
>> Especially if we don’t get it fixed within the next mails ;o)
>>
>> Kind regards,
>> Michael
>>
>>
>>
>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com>
>> wrote:
>>
>> Hi,
>>
>> To be precise, I'm using Maven 2.2.1 and getting this error. When I
>> switch to Maven 3.0.5 I get a very different set of compilation errors.
>> Also, I just tried it again on a different machine, though the same OS
>> (Ubuntu 14.0.4). Again, the steps are:
>>
>> 1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>> 2. cd olingo-odata2
>> 3. mvn clean install
>>
>> Warm regards,
>> David
>>
>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com>
>> wrote:
>>
>>> Hi,
>>>
>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>> See comment in Introduction (
>>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
>>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>
>>> On a first glance I did not find a workaround.
>>> It is perhaps possible that you upgrade to Maven 3?
>>>
>>> Kind regards,
>>> Michael
>>>
>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com> wrote:
>>>
>>> Hi!
>>>
>>> I cloned the git repo for olingo v2 and tried to build it using Maven
>>> (more precisely, Maven2) using the instructions here:
>>>
>>> http://olingo.apache.org/doc/odata2/maven.html
>>>
>>> And got a not-altogether-unfamiliar Maven error:
>>>
>>> [ERROR] BUILD ERROR
>>> [INFO]
>>> ------------------------------------------------------------------------
>>> [INFO] Failed to resolve dependencies for one or more projects in the
>>> reactor. Reason: Unable to get dependency information: Unable to read the
>>> metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
>>> find parent: org.eclipse.jetty:jetty-parent for project:
>>> null:jetty-project:pom:7.5.4.v20111024 for project
>>> null:jetty-project:pom:7.5.4.v20111024
>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>
>>> from the specified remote repositories:
>>> apache.snapshots (http://repository.apache.org/snapshots),
>>> central (http://repo1.maven.org/maven2),
>>> oss.sonatype.org(https://oss.sonatype.org/content/groups/staging)
>>>
>>> Path to dependency:
>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>
>>>
>>>
>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
>>> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>
>>>
>>> Before going off on a yak-shaving adventure tracking down
>>> dependencies, I'll just ask here, Is there's an easy known fix for this?
>>> Thanks!
>>>
>>> Cheers,
>>> David
>>>
>>>
>>>
>>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by Mibo <mi...@apache.org>.
Hi David,
Perhaps I have misunderstood your last mail but after a look into the log and your information in the mail it is the same problem as before.
You try to build with Maven 2 which seems to be incompatible with Jetty 7.5.4 (not supported POM version 4.0.0).
If possible can you please try with Maven 3 and give feedback ;o)
Kind regards,
Michael
> On Dec 10, 2014, at 8:41 PM, David Ventimiglia <dv...@gmail.com> wrote:
>
>
> Hi Michael,
>
>
> We'll do another round of email, after which I'll create a ticket.
>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo update-alternatives --config mvn
>> [sudo] password for dventimiglia:
>> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>>
>> Selection Path Priority Status
>> ------------------------------------------------------------
>> 0 /usr/share/maven2/bin/mvn 200 auto mode
>> * 1 /usr/share/maven/bin/mvn 150 manual mode
>> 2 /usr/share/maven2/bin/mvn 200 manual mode
>>
>> Press enter to keep the current choice[*], or type selection number: 0
>> update-alternatives: using /usr/share/maven2/bin/mvn to provide /usr/bin/mvn (mvn) in auto mode
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
>> Apache Maven 2.2.1 (rdebian-14)
>> Java version: 1.7.0_65
>> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
>> Default locale: en_US, platform encoding: UTF-8
>> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family: "unix"
>>
>> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean install > olingo.log
>>
>
> I've attached the log file. Like I said, beyond this I'd be happy to create a ticket, and happy to work on it.
>
>
> Warm regards,
> David
>
>
> On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mibo@apache.org
>>wrote:
>>
>> Hi David,
>>
>>
>> Can you please attach the Maven log with the compilations errors.
>> Another question which Java version and runtime implementation (OpenJDK?) do you use?
>>
>>
>> Perhaps it would be better to create an JIRA issue (https://issues.apache.org/jira/browse/OLINGO
>> ) for the problem you have found.
>> Especially if we don’t get it fixed within the next mails ;o)
>>
>>
>> Kind regards,
>> Michael
>>
>>
>>
>>
>>
>>
>>
>>> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dventimi@gmail.com
>>>> wrote:
>>>
>>>
>>> Hi,
>>>
>>> To be precise, I'm using Maven 2.2.1 and getting this error. When I switch to Maven 3.0.5 I get a very different set of compilation errors. Also, I just tried it again on a different machine, though the same OS (Ubuntu 14.0.4). Again, the steps are:
>>> git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>>>
>>> cd olingo-odata2
>>> mvn clean install
>>>
>>>
>>>
>>> Warm regards,
>>> David
>>>
>>>
>>>
>>>
>>>
>>> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <michael.bolz@sap.com
>>>>wrote:
>>>
>>>
>>>> Hi,
>>>>
>>>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>>>> See comment in Introduction (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin
>>>> ).
>>>>> You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>>>
>>>>
>>>> On a first glance I did not find a workaround.
>>>> It is perhaps possible that you upgrade to Maven 3?
>>>>
>>>>
>>>> Kind regards,
>>>> Michael
>>>>
>>>>
>>>>
>>>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dventimi@gmail.com
>>>>>> wrote:
>>>>>
>>>>>
>>>>>
>>>>> Hi!
>>>>>
>>>>>
>>>>> I cloned the git repo for olingo v2 and tried to build it using Maven (more precisely, Maven2) using the instructions here:
>>>>>
>>>>> http://olingo.apache.org/doc/odata2/maven.html
>>>>>
>>>>>
>>>>>
>>>>> And got a not-altogether-unfamiliar Maven error:
>>>>>
>>>>>
>>>>>
>>>>> [ERROR] BUILD ERROR
>>>>> [INFO] ------------------------------------------------------------------------
>>>>> [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information: Unable to read the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot find parent: org.eclipse.jetty:jetty-parent for project: null:jetty-project:pom:7.5.4.v20111024 for project null:jetty-project:pom:7.5.4.v20111024
>>>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>>>
>>>>> from the specified remote repositories:
>>>>> apache.snapshots (http://repository.apache.org/snapshots
>>>>> ),
>>>>> central (http://repo1.maven.org/maven2
>>>>> ),
>>>>>
>>>>>
>>>>> oss.sonatype.org
>>>>> (https://oss.sonatype.org/content/groups/staging
>>>>> )
>>>>>
>>>>> Path to dependency:
>>>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>>>
>>>>>
>>>>>
>>>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>>>
>>>>>
>>>>>
>>>>> Before going off on a yak-shaving adventure tracking down dependencies, I'll just ask here, Is there's an easy known fix for this? Thanks!
>>>>>
>>>>> Cheers,
>>>>> David
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>
>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
Hi Michael,
We'll do another round of email, after which I'll create a ticket.
dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ sudo
> update-alternatives --config mvn
> [sudo] password for dventimiglia:
> There are 2 choices for the alternative mvn (providing /usr/bin/mvn).
>
> Selection Path Priority Status
> ------------------------------------------------------------
> 0 /usr/share/maven2/bin/mvn 200 auto mode
> * 1 /usr/share/maven/bin/mvn 150 manual mode
> 2 /usr/share/maven2/bin/mvn 200 manual mode
>
> Press enter to keep the current choice[*], or type selection number: 0
> update-alternatives: using /usr/share/maven2/bin/mvn to provide
> /usr/bin/mvn (mvn) in auto mode
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn -version
> Apache Maven 2.2.1 (rdebian-14)
> Java version: 1.7.0_65
> Java home: /usr/lib/jvm/java-7-openjdk-amd64/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux" version: "3.13.0-40-generic" arch: "amd64" Family: "unix"
>
> dventimiglia@dventimi-ThinkPad-T410:~/work/olingo-odata2$ mvn clean
> install > olingo.log
>
I've attached the log file. Like I said, beyond this I'd be happy to
create a ticket, and happy to work on it.
Warm regards,
David
On Wed, Dec 10, 2014 at 10:37 AM, Mibo <mi...@apache.org> wrote:
> Hi David,
>
> Can you please attach the Maven log with the compilations errors.
> Another question which Java version and runtime implementation (OpenJDK?)
> do you use?
>
> Perhaps it would be better to create an JIRA issue (
> https://issues.apache.org/jira/browse/OLINGO) for the problem you have
> found.
> Especially if we don’t get it fixed within the next mails ;o)
>
> Kind regards,
> Michael
>
>
>
> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com>
> wrote:
>
> Hi,
>
> To be precise, I'm using Maven 2.2.1 and getting this error. When I
> switch to Maven 3.0.5 I get a very different set of compilation errors.
> Also, I just tried it again on a different machine, though the same OS
> (Ubuntu 14.0.4). Again, the steps are:
>
> 1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
> 2. cd olingo-odata2
> 3. mvn clean install
>
> Warm regards,
> David
>
> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com>wrote:
>
>> Hi,
>>
>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>> See comment in Introduction (
>> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
>> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>
>> On a first glance I did not find a workaround.
>> It is perhaps possible that you upgrade to Maven 3?
>>
>> Kind regards,
>> Michael
>>
>> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com> wrote:
>>
>> Hi!
>>
>> I cloned the git repo for olingo v2 and tried to build it using Maven
>> (more precisely, Maven2) using the instructions here:
>>
>> http://olingo.apache.org/doc/odata2/maven.html
>>
>> And got a not-altogether-unfamiliar Maven error:
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>> ------------------------------------------------------------------------
>> [INFO] Failed to resolve dependencies for one or more projects in the
>> reactor. Reason: Unable to get dependency information: Unable to read the
>> metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
>> find parent: org.eclipse.jetty:jetty-parent for project:
>> null:jetty-project:pom:7.5.4.v20111024 for project
>> null:jetty-project:pom:7.5.4.v20111024
>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>
>> from the specified remote repositories:
>> apache.snapshots (http://repository.apache.org/snapshots),
>> central (http://repo1.maven.org/maven2),
>> oss.sonatype.org(https://oss.sonatype.org/content/groups/staging)
>>
>> Path to dependency:
>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>
>>
>>
>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
>> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>
>>
>> Before going off on a yak-shaving adventure tracking down dependencies,
>> I'll just ask here, Is there's an easy known fix for this? Thanks!
>>
>> Cheers,
>> David
>>
>>
>>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by Mibo <mi...@apache.org>.
Hi David,
Can you please attach the Maven log with the compilations errors.
Another question which Java version and runtime implementation (OpenJDK?) do you use?
Perhaps it would be better to create an JIRA issue (https://issues.apache.org/jira/browse/OLINGO) for the problem you have found.
Especially if we don’t get it fixed within the next mails ;o)
Kind regards,
Michael
> On Dec 10, 2014, at 5:58 PM, David Ventimiglia <dv...@gmail.com> wrote:
>
>
> Hi,
>
> To be precise, I'm using Maven 2.2.1 and getting this error. When I switch to Maven 3.0.5 I get a very different set of compilation errors. Also, I just tried it again on a different machine, though the same OS (Ubuntu 14.0.4). Again, the steps are:
> git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
>
> cd olingo-odata2
> mvn clean install
>
>
>
> Warm regards,
> David
>
>
>
> On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <michael.bolz@sap.com
>>wrote:
>> Hi,
>>
>> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
>> See comment in Introduction (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin
>> ).
>>> You will need to use maven 3 from jetty-7.5.3 release going forwards.
>>
>>
>> On a first glance I did not find a workaround.
>> It is perhaps possible that you upgrade to Maven 3?
>>
>>
>> Kind regards,
>> Michael
>>
>>> On 10 Dec 2014, at 06:13, David Ventimiglia <dventimi@gmail.com
>>>> wrote:
>>>
>>> Hi!
>>>
>>>
>>> I cloned the git repo for olingo v2 and tried to build it using Maven (more precisely, Maven2) using the instructions here:
>>>
>>> http://olingo.apache.org/doc/odata2/maven.html
>>>
>>>
>>>
>>> And got a not-altogether-unfamiliar Maven error:
>>>
>>> [ERROR] BUILD ERROR
>>> [INFO] ------------------------------------------------------------------------
>>> [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information: Unable to read the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot find parent: org.eclipse.jetty:jetty-parent for project: null:jetty-project:pom:7.5.4.v20111024 for project null:jetty-project:pom:7.5.4.v20111024
>>> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>>>
>>> from the specified remote repositories:
>>> apache.snapshots (http://repository.apache.org/snapshots
>>> ),
>>> central (http://repo1.maven.org/maven2
>>> ),
>>> oss.sonatype.org
>>> (https://oss.sonatype.org/content/groups/staging
>>> )
>>>
>>> Path to dependency:
>>> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>>>
>>>
>>>
>>> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>>>
>>>
>>>
>>> Before going off on a yak-shaving adventure tracking down dependencies, I'll just ask here, Is there's an easy known fix for this? Thanks!
>>>
>>> Cheers,
>>> David
>>>
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move to olingo-dev)
Posted by David Ventimiglia <dv...@gmail.com>.
Hi,
To be precise, I'm using Maven 2.2.1 and getting this error. When I switch
to Maven 3.0.5 I get a very different set of compilation errors. Also, I
just tried it again on a different machine, though the same OS (Ubuntu
14.0.4). Again, the steps are:
1. git clone https://git-wip-us.apache.org/repos/asf/olingo-odata2
2. cd olingo-odata2
3. mvn clean install
Warm regards,
David
On Tue, Dec 9, 2014 at 9:48 PM, Bolz, Michael <mi...@sap.com> wrote:
> Hi,
>
> it seems that Jetty > 7.5.3 is not compatible with Maven 2.
> See comment in Introduction (
> http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin).
> > You will need to use maven 3 from jetty-7.5.3 release going forwards.
>
> On a first glance I did not find a workaround.
> It is perhaps possible that you upgrade to Maven 3?
>
> Kind regards,
> Michael
>
> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com> wrote:
>
> Hi!
>
> I cloned the git repo for olingo v2 and tried to build it using Maven
> (more precisely, Maven2) using the instructions here:
>
> http://olingo.apache.org/doc/odata2/maven.html
>
> And got a not-altogether-unfamiliar Maven error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve dependencies for one or more projects in the
> reactor. Reason: Unable to get dependency information: Unable to read the
> metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot
> find parent: org.eclipse.jetty:jetty-parent for project:
> null:jetty-project:pom:7.5.4.v20111024 for project
> null:jetty-project:pom:7.5.4.v20111024
> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>
> from the specified remote repositories:
> apache.snapshots (http://repository.apache.org/snapshots),
> central (http://repo1.maven.org/maven2),
> oss.sonatype.org (https://oss.sonatype.org/content/groups/staging)
>
> Path to dependency:
> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>
>
>
> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at
> /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>
>
> Before going off on a yak-shaving adventure tracking down dependencies,
> I'll just ask here, Is there's an easy known fix for this? Thanks!
>
> Cheers,
> David
>
>
>
Re: Olingo v2 Maven build error (starting w/ olingo-user, may move
to olingo-dev)
Posted by "Bolz, Michael" <mi...@sap.com>.
Hi,
it seems that Jetty > 7.5.3 is not compatible with Maven 2.
See comment in Introduction (http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin <http://wiki.eclipse.org/Jetty/Feature/Jetty_Maven_Plugin>).
> You will need to use maven 3 from jetty-7.5.3 release going forwards.
On a first glance I did not find a workaround.
It is perhaps possible that you upgrade to Maven 3?
Kind regards,
Michael
> On 10 Dec 2014, at 06:13, David Ventimiglia <dv...@gmail.com> wrote:
>
> Hi!
>
> I cloned the git repo for olingo v2 and tried to build it using Maven (more precisely, Maven2) using the instructions here:
>
> http://olingo.apache.org/doc/odata2/maven.html <http://olingo.apache.org/doc/odata2/maven.html>
>
> And got a not-altogether-unfamiliar Maven error:
>
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Failed to resolve dependencies for one or more projects in the reactor. Reason: Unable to get dependency information: Unable to read the metadata file for artifact 'org.eclipse.jetty:jetty-servlet:jar': Cannot find parent: org.eclipse.jetty:jetty-parent for project: null:jetty-project:pom:7.5.4.v20111024 for project null:jetty-project:pom:7.5.4.v20111024
> org.eclipse.jetty:jetty-servlet:jar:7.5.4.v20111024
>
> from the specified remote repositories:
> apache.snapshots (http://repository.apache.org/snapshots <http://repository.apache.org/snapshots>),
> central (http://repo1.maven.org/maven2 <http://repo1.maven.org/maven2>),
> oss.sonatype.org <http://oss.sonatype.org/> (https://oss.sonatype.org/content/groups/staging <https://oss.sonatype.org/content/groups/staging>)
>
> Path to dependency:
> 1) org.apache.olingo:olingo-odata2-testutil:jar:2.0.2-SNAPSHOT
>
>
>
> Not a v4.0.0 POM. for project org.eclipse.jetty:jetty-parent at /home/dventimi/.m2/repository/org/eclipse/jetty/jetty-parent/19/jetty-parent-19.pom
>
>
> Before going off on a yak-shaving adventure tracking down dependencies, I'll just ask here, Is there's an easy known fix for this? Thanks!
>
> Cheers,
> David