[jira] [Resolved] (OLINGO-355) Maven Import of Olingo 4.0. code in Eclipse Kepler fails using M2E plugin fails

["Vikram Pancholi (JIRA)" <ji...@apache.org>]

     [ https://issues.apache.org/jira/browse/OLINGO-355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vikram Pancholi resolved OLINGO-355.
------------------------------------

    Resolution: Fixed

added a patch file to be approved for a master push

> Maven Import  of Olingo 4.0. code in Eclipse Kepler fails using M2E plugin fails 
> ---------------------------------------------------------------------------------
>
>                 Key: OLINGO-355
>                 URL: https://issues.apache.org/jira/browse/OLINGO-355
>             Project: Olingo
>          Issue Type: Bug
>          Components: odata4-server
>    Affects Versions: V4 0.1.0
>         Environment: Eclipse Kepler 
> M2E plugin antlr connector version 0.5
> Windows
>            Reporter: Vikram Pancholi
>            Priority: Trivial
>              Labels: antlr, eclipse, maven
>             Fix For: V4 0.1.0
>
>         Attachments: 0001-Olingo-255-adding-generated-source-folder-to-server-.patch
>
>   Original Estimate: 1h
>  Remaining Estimate: 1h
>
> following are the steps observed
> 1. Git clone 
> 2. Use eclipse "Import Maven project feature" with Lifecycle mapping added  as below
>   <pluginExecution>
>       <pluginExecutionFilter>
>         <groupId>org.antlr</groupId>
>         <artifactId>antlr4-maven-plugin</artifactId>
>         <goals>
>           <goal>antlr4</goal>
>         </goals>
>         <versionRange>[4.1,)</versionRange>
>       </pluginExecutionFilter>
>       <action>
>         <execute>
>           <runOnIncremental>false</runOnIncremental>
>         </execute>
>       </action>
>     </pluginExecution>
> 3. Eclipse import is successfull. But we see compilation issues in classes 
> eg org.apache.olingo.server.core.uri.parser.Parser
> 4. It appears antlr code has been generated but not added to Build path leading to compilation errors.



--
This message was sent by Atlassian JIRA
(v6.2#6252)