You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ranger.apache.org by "Nigel Jones (JIRA)" <ji...@apache.org> on 2017/02/02 16:20:51 UTC

[jira] [Commented] (RANGER-1186) Ranger Source: eclipse

    [ https://issues.apache.org/jira/browse/RANGER-1186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15850109#comment-15850109 ] 

Nigel Jones commented on RANGER-1186:
-------------------------------------

A quick update on my attempt to get eclipse running more cleanly. Via https://github.com/mojohaus/build-helper-maven-plugin/issues/43 I can see that after testing prerelease, simply updating pom.xml with a new version for the build helper plugin, along with taking the eclipse quick-fix to pull in lifecycle mappers (a normal technique) will fix the errors relating to that plugin

<plugin>
                    <groupId>org.codehaus.mojo</groupId>
                    <artifactId>build-helper-maven-plugin</artifactId>
                    <version>3.0.0</version>
                </plugin>

Then we're left with plugins that are yet to become m2e compatible - see referenced defects for that discussion. I opted to force their tasks to run during build. This felt the most appropriate rather than ignore - since this might not find issues introduced whilst coding.

For this I added some entries to plugin management. It may not be perfect, but it's a starting point, resulting in what seems like a clean (no error) eclipse environment

              <!--This plugin's configuration is used to store Eclipse m2e settings only. It has no influence on the Maven build itself.-->
                <plugin>
                	<groupId>org.eclipse.m2e</groupId>
                	<artifactId>lifecycle-mapping</artifactId>
                	<version>1.0.0</version>
                	<configuration>
                		<lifecycleMappingMetadata>
                			<pluginExecutions>
                				<pluginExecution>
                					<pluginExecutionFilter>
                						<groupId>
                							org.apache.maven.plugins
                						</groupId>
                						<artifactId>
                							maven-antrun-plugin
                						</artifactId>
                						<versionRange>
                							[1.7,)
                						</versionRange>
                						<goals>
                							<goal>run</goal>
                						</goals>
                					</pluginExecutionFilter>
                					<action>
                						<execute></execute>
                					</action>
                				</pluginExecution>
                				<pluginExecution>
                					<pluginExecutionFilter>
                						<groupId>
                							org.codehaus.mojo
                						</groupId>
                						<artifactId>
                							native-maven-plugin
                						</artifactId>
                						<versionRange>
                							[1.0-alpha-8,)
                						</versionRange>
                						<goals>
                							<goal>compile</goal>
                						</goals>
                					</pluginExecutionFilter>
                					<action>
                						<execute></execute>
                					</action>
                				</pluginExecution>
                				<pluginExecution>
                					<pluginExecutionFilter>
                						<groupId>
                							org.codehaus.mojo
                						</groupId>
                						<artifactId>
                							native-maven-plugin
                						</artifactId>
                						<versionRange>
                							[1.0-alpha-8,)
                						</versionRange>
                						<goals>
                							<goal>initialize</goal>

                							<goal>link</goal>
                							<goal>unzipinc</goal>
                						</goals>
                					</pluginExecutionFilter>
                					<action>
                						<execute></execute>
                					</action>
                				</pluginExecution>
                			</pluginExecutions>
                		</lifecycleMappingMetadata>
                	</configuration>
                </plugin>

I can do a patch of those changes if someone would like to fix/commit?
Is this a reasonable change?
I think it's low risk as it mostly only affects m2e configuration. The only change to the real build is the move to 3.0 on the build helper plugin

> Ranger Source: eclipse
> ----------------------
>
>                 Key: RANGER-1186
>                 URL: https://issues.apache.org/jira/browse/RANGER-1186
>             Project: Ranger
>          Issue Type: Bug
>          Components: documentation
>    Affects Versions: Ranger
>         Environment: eclipse neon, ubuntu 16.10
>            Reporter: Nigel Jones
>            Assignee: Pradeep Agrawal
>         Attachments: RANGER-1186_Ranger_Source_Eclipse.pdf, ranger_me0.PNG, ranger_me1.PNG
>
>
> I can happily build ranger in my Ubuntu 16.10 environment with
>  - open jdk 1.8.0_102
>  - maven 3.3.9
> I also have eclipse neon installed in this environment
> The build/setup instructions at http://ranger.apache.org/quick_start_guide.html have minimal instructions for eclipse.
> I imported the top level ranger directory using the m2e plugin as provided in neon.
> This failed with numerous errors
> Is anyone actively building with eclipse? If so can we update the website with current setup information?
> If not I'll use this JIRA to record the issues & hope to address them & update the docs ;-)
> Screenshots to follow



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)