Sorry, it looks like the examples target is out of date so use the target in releng.target and omit steps 4-6.
From: Chang, Peter (DLSLtd,RAL,LSCI)
Sent: 19 October 2017 11:40
To: 'matthew.gerring@xxxxxxxxxxxxxx' <matthew.gerring@xxxxxxxxxxxxxx>; 'january developer discussions' <january-dev@xxxxxxxxxxx>
Subject: RE: [january-dev] Issue getting the target dependencies
As I said yesterday, if you want to use the target platform:
Start a new workspace
Clone the repo
Import the plugins
Use the example target platform
Go via Windows > Preferences, search for Target Platform
Edit the plugins to uncheck the January jars
On Behalf Of Matthew Gerring
Sent: 19 October 2017 11:28
To: january developer discussions <january-dev@xxxxxxxxxxx>
Subject: Re: [january-dev] Issue getting the target dependencies
Georgi is trying to build January itself not use it in a product.
(Maven central worked fine for adding it to our product.)
On 19 October 2017 at 11:21, Jonah Graham <jonah@xxxxxxxxxxxxxxxx> wrote:
I can probably help.
Are you intending on using Eclipse Target Platforms or Maven POMs or
some other way?
There is a bit of getting started info on
https://www.eclipse.org/january/#try but if you are using target
platforms you can follow the guide here:
If you are intending on using Maven or other similar build tools, the
bit you need in your pom.xml is available
The Example-settings.xml should be unnecessary for you as you are not
building and deploying January itself. Those settings are to be able
to upload to January's Maven Central location in that repo.
is slightly wrong, there is an extra /0 on it.
Kichwa Coders Ltd.
On 19 October 2017 at 11:09, Georgi Vasilski <jvjordanvip@xxxxxxxxxxxxxx> wrote:
> I have problems to get the plug-ins for the target in January project. Would
> anyone be able to help me with some tips how I can sort the problem out.
> I am using Eclipse Neon3 and have created a settings.xml file with my
> eclipse credentials and placed it in my .m2 folder as it said at
https://github.com/eclipse/january/wiki/Example-settings.xml link. So that
> resolved the problem with the repository, but still have zero plug-ings
> available in the target where it says that it is unable to locate
> installable unit org.eclipse.core.runtime.feature.feature.group 0.0.0 and
> unable to locate installable unit org.eclipse.equinox.laucher 0.0.0.
> I have tried the website
> I am getting the following message:
> Not Found
> We're sorry, the page or file cannot be found. Here are some reasons why:
> A file may have moved to the archives. Please contact the project members on
> their user forum.
> Your file was part of a nightly or integration build which is no longer
> there. Simply download the latest version.
> The project is uploading a new build, and this file is not there yet. Try
> again later
> january-dev mailing list
> To change your delivery options, retrieve your password, or unsubscribe from
> this list, visit
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