Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [january-dev] Issue getting the target dependencies

Should be as simple as a build.gradle of:

version = "1.0.0"


apply plugin: 'java'

apply plugin: 'application'

apply plugin: 'eclipse'


sourceCompatibility = 1.8

targetCompatibility = 1.8


repositories {




dependencies {

    compile "org.apache.commons.math3:org.apache.commons.math3:3.2.0"


... The other dependencies added here



Then gradlew eclipse will set the project up for eclipse.



On 19 October 2017 at 12:05, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
Great, can you provide that as a PR for January, I will be happy to
test it out and get the build & deploy updated once that first step
has been done.

Jonah Graham
Kichwa Coders Ltd.

On 19 October 2017 at 12:02, Matthew Gerring <matthew.gerring@xxxxxxxxx> wrote:
> I am working on another project which uses gradlew and has a command
> "gradlew eclipse" which sets up the project dependencies for eclipse ide to
> find them.
> You have:
> apply plugin: 'eclipse'
> in build.gradle and it sets the project up to have the dependencies it
> downloads...
> Matt
> On 19 October 2017 at 11:55, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>> On 19 October 2017 at 11:49, Matthew Gerring <matthew.gerring@xxxxxxxxx>
>> wrote:
>> > Maybe having target platforms is too hard for most Java developers to be
>> > familiar?
>> I agree!
>> Using TP is not something necessary for January, but is a result of
>> the evolution of how we got here. Does someone want to pick it up and
>> move it forward? Converting January datasets to Maven (or Gradle)
>> build should not be too difficult.
>> Peter, do you have any thoughts/objections to such a move?

Back to the top