I’ve merged EDGENT-251 / PR-201 which changes how Eclipse builds deal with
references to 3rd-party jars.
When you rebase and pickup commit bd71ad8 your Eclipse based Edgent runtime
builds will fail until you take the necessary action.
See EDGENT-251 for details: https://issues.apache.org/jira/bro
Now that the Gradle work is mostly completed, I would like to share my
experiences setting up my repository to use Gradle to build via the command
line and to integrate with my Eclipse development environment.
I started by re-cloning my GitHub repository to remove all of the generated
Ant-related
Queenie, thanks for the detailed sharing of your experience!
It’s great to get confirmation that everything went smoothly for someone else
:-)
— Dale
> On Oct 3, 2016, at 3:02 PM, Queenie Ma wrote:
>
> Now that the Gradle work is mostly completed, I would like to share my
> experiences settin
This is another confirmation that switching to use Gradle is a smooth
experience :-)
One thing which I noticed is that if you import Eclipse projects from the
source "General > Existing projects into Workspace", you end up importing
the scripts project from ./build/distributions/java8/scripts rath
Very impressive Dale and Queenie. I went through the instructions and
everything worked flawlessly!
Thank you Dale for all the work you have put in to transition to gradle, and
thanks Queenie for your note.
Cheers,
Susan
> On Oct 3, 2016, at 12:13 PM, Dale LaBossiere wrote:
>
> Queenie, th
