[
https://issues.apache.org/jira/browse/EDGENT-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Dale LaBossiere resolved EDGENT-251.
------------------------------------
Resolution: Fixed
> [gradle] initial work for developing Edgent runtime with gradle in Eclipse
> --------------------------------------------------------------------------
>
> Key: EDGENT-251
> URL: https://issues.apache.org/jira/browse/EDGENT-251
> Project: Edgent
> Issue Type: Task
> Reporter: Dale LaBossiere
> Assignee: Dale LaBossiere
>
> An Eclipse-based Edgent runtime development enviroment depends on the 3rd
> party jars currently present in the Edgent repository (the Eclipse .classpath
> files present in the repository depend on them)
> Those jars will be removed, replaced by a gradle based build environment,
> when all of the pieces are in place - EDGENT-139.
> Summary: (changes in PR-201)
> - The user must run "./gradlew setupExternalJars" to satisfy the projects'
> .classpath jar references
> - Read DEVELOPMENT.md -
> https://github.com/apache/incubator-edgent/blob/master/DEVELOPMENT.md
> Removal of the 3rd party jars from our repo will be covered by a separate
> issue.
> Note: My initial experience trying to use the Buildship gradle/Eclipse
> integration came up short. The way it created/updated .classpath files
> as a result of the way dependencies are expressed in our build.gradle
> files was problematic. So, I scoped back to the approach here to get to
> the end-goal (removal of dependency of 3rd party jars in the repo) asap.
> Should revisit the buildship env later to see if things can be made to
> work.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
