Quick question: are .target specifications transitive so dependencies are resolved recursively? I was wondering about simplifying the
example target to only depend on January and junit.
From: january-dev-bounces@xxxxxxxxxxx [mailto:january-dev-bounces@xxxxxxxxxxx]
On Behalf Of Jonah Graham
Sent: 19 October 2017 13:54
To: january developer discussions <january-dev@xxxxxxxxxxx>
Subject: Re: [january-dev] Issue getting the target dependencies
This looks like an Eclipse PDE bug, unfortunately one I have seen regularly. It is not January related, but what has happened is that the cache has become corrupted. Often restarting Eclipse and/or pressing Reload and/or Update and/or deleting workspace\.metadata\.plugins\org.eclipse.pde.core
cleans up the area.
On 19 October 2017 at 12:17, Georgi Vasilski <jvjordanvip@xxxxxxxxxxxxxx> wrote:
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.
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
> On 19 October 2017 at 11:55, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
>> On 19 October 2017 at 11:49, Matthew Gerring <matthew.gerring@xxxxxxxxx>
>> > 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?
january-dev mailing list
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
This e-mail and any attachments may contain confidential, copyright and or privileged material, and are for the use of the intended addressee only. If you are not the intended addressee or an authorised recipient of the addressee please notify us of receipt by returning the e-mail and do not use, copy, retain, distribute or disclose the information in or attached to the e-mail.
Any opinions expressed within this e-mail are those of the individual and not necessarily of Diamond Light Source Ltd.
Diamond Light Source Ltd. cannot guarantee that this e-mail or any attachments are free from viruses and we cannot accept liability for any damage which you may sustain as a result of software viruses which may be transmitted in or with the message.
Diamond Light Source Limited (company no. 4375679). Registered in England and Wales with its registered office at Diamond House, Harwell Science and Innovation Campus, Didcot, Oxfordshire, OX11 0DE, United Kingdom