Does it exist in a maven repo?

[bbarker]

Hi,

I saw that dependency info was listed in the Readme but it wasn't clear to me if or where it has been published (I assume not in maven central unless I'm doing something very sill, which is possible).

Thanks,

[ozeebee]

Hi,
No I haven't pulished the project because it depends on other (Eclipse) libs that were not available in public repos when I created this project (a few years ago).

Now, if this is a problem for you, you may want to check the original project (which is now located here: https://github.com/coconutpalm/XScalaWT) but it's built with Maven only (no sbt).

That being said, I haven't touched this project for a while and I don't even know if it still compiles with the latest Eclipse libraries, SBT and scala version (2.11).
If you're having problems for building it, just let me know and I'll try to find some time to update/fix the build.

[bbarker]

Thanks very much for the offer to help - I'll see if I can get it to build
first, probably in the next couple of days.

On Tue, Dec 1, 2015 at 4:30 AM, ozeebee [email protected] wrote:

Hi,
No I haven't pulished the project because it depends on other (Eclipse)
libs that were not available in public repos when I created this project (a
few years ago).

Now, if this is a problem for you, you may want to check the original
project (which is now located here:
https://github.com/coconutpalm/XScalaWT) but it's built with Maven only
(no sbt).

That being said, I haven't touched this project for a while and I don't
even know if it still compiles with the latest Eclipse libraries, SBT and
scala version (2.11).
If you're having problems for building it, just let me know and I'll try
to find some time to update/fix the build.

—
Reply to this email directly or view it on GitHub
#1 (comment).

Brandon Barker
[email protected]

[bbarker]

I gave it a good try today, but I'm a bit in over my depth in understanding the (Ivy?) conflicts; I tried to use sbt's evicted and show update, but couldn't make much sense of it.

Mostly, I tried disabling some of your external dependencies just so I could open the project in IntelliJ, but I also tried updating a some of the dependencies (mainly Scala), and adding some new resolvers for SWT:

https://github.com/bbarker/ozb-xscalawt/tree/build_test

I guess the only thing there that will be of help may be the few minutes you save in googling for jface/swt resolvers.

[ozeebee]

I have tried to quickly upgrade all the tools used (scala 2.11.7 with sbt 0.13.9) but it failed just as I was afraid it would.
Now, the root problem comes from the Eclipse dependencies.
I see 3 options right now:

1. Fix the build for scala 2.11 and SBT 0.13 and stick with the current system: download and install required Eclipse jars into the local repository
2. Try to find the jars into some public repository (looks like Maven central now references a lot more than when I created the project) but we depend on third-party publishing them and I don't know if all the required jars are available (not to mention that not all versions are present)
3. Refactor the build to use a solution that ultimately fetches the dependencies from Eclipse p2 repositories. In this regard, I have found an interesting project: https://github.com/digimead/sbt-osgi-manager that could be the best solution but I haven't investigated this yet

[bbarker]

Several minor comments for option 3:

• I believe I heard about this just a couple days ago on an old
  scalawags podcast and the heroic effort it must have taken to get it
  finished.
• I've heard good things about OSGi ... but no experience with it myself.
• This would allow the project to be built, but could xscalawt then be
  published to a repo without other projects that depend on xscalawt
  going through the same hoops? I guess the only option is if the
  eclipse library dependency jars are somehow packed together with the
  xscalawt jar file. Option (1) wouldn't seem to solve this problem
  either, so perhaps (2) would be best if it works. Of course, we are
  still at the mercy of the maven repos continued existence.

In addition to maven central, did you see the other maven repos I
addded in the build.sbt? Not sure how much of what is needed was
there, but between the two, I found some versions of all the
dependencies I saw:

resolvers +=
    "SWT repo" at "http://maven-eclipse.github.io/maven"

resolvers +=
    "Jabylon" at "http://www.jabylon.org/maven"

On Thu, Dec 3, 2015 at 9:30 AM, ozeebee [email protected] wrote:

I have tried to quickly upgrade all the tools used (scala 2.11.7 with sbt
0.13.9) but it failed just as I was afraid it would.
Now, the root problem comes from the Eclipse dependencies.
I see 3 options right now:

Fix the build for scala 2.11 and SBT 0.13 and stick with the current system:
download and install required Eclipse jars into the local repository
Try to find the jars into some public repository (looks like Maven central
now references a lot more than when I created the project) but we depend on
third-party publishing them and I don't know if all the required jars are
available (not to mention that not all versions are present)
Refactor the build to use a solution that ultimately fetches the
dependencies from Eclipse p2 repositories. In this regard, I have found an
interesting project: https://github.com/digimead/sbt-osgi-manager that could
be the best solution but I haven't investigated this yet

—
Reply to this email directly or view it on GitHub.

Brandon Barker
[email protected]

[ozeebee]

I have checked your repositories, unfortunately the first one contains only SWT libs while the latter hasn't been updated since 2013.
And I haven't been able to find all the requireds libs in Maven central (ex: JFace Databinding) for a recent version of Eclipse.
I'm afraid the only viable options right now are (1: Fix the build) or (3: Investigate sbt-osgi-manager).

I'll try to fix the build for scala 2.11/sbt 0.13

[ozeebee]

Hi, I've just refreshed the project so that it's now compatible with latest scala (2.11.7) and sbt (0.13.9) versions (there are still a lot of warnings due to deprecated code but at least it compiles).
I took the opportunity to update the Eclipse dependencies and to refactor the build as well (no more dependency on 'ozb-scala-utils' project).
I recommend you to screw the old version and to clone and test the new one.
I hope you will be able to build the library;
Check also the example project

[bbarker]

Excellent! I gave it a try, and IntelliJ seems happy with it. However, the large project I'm working on currently uses Maven, and I just finished converting 5000 loc (Java) to Scala, so need to get back to doing productive work (i.e. adding features) for a few days before figuring out how to get Tycho appropriately set up. When I do, I'll try to send an example config based on your example project for other people as clueless as me - which may be just me in the future ;).