headers
Vlad Ureche | 7 Feb 14:46
Picon
Gravatar

Sbteclipse - skip some source entries in the Eclipse project

Hello everyone,

I have a newbie question about sbteclipse: In the project I am working on, there are Scala sources but no Java sources at all. Is there a way to configure sbteclipse not to generate project source entries for Java?
The things I tried, without success:
 - setting the javaSources in {Compile. Test} to Nil -- the setting expects a java.io.File, and will only settle for that
 - messing with the sbteclipse createSrc setting, which either selects all sources or none

Is there a way to instruct sbteclipse to skip the Java sources in the Eclipse project?

Thanks,
Vlad

Permalink | Reply | 1 comment |
headers
Alexander Baier | 8 Feb 01:56

[Emacs][scala-mode] Makefile misses "scala-mode-variables"

Hello there!

I am not quite shure, if this is the right place for me to post this, but except for the github page - which seems to be a mirror repo only - i did not find any other contact information.

So, here we go:
After running make and pointing emacs to the compiled .elc files, emacs always complained about not being able to open a scala file type, or something similar, i do not have the exact wording in mind. So i added the following line to the Makefile after line 35:

ELISP_FILES        += scala-mode-variables

After running make again, emacs stopped complaining and worked as it is supposed to do.

This is my setup:
Emacs GNU Emacs 23.4.1
Archlinux

If you need further information please do not hesitate to ask.

Permalink | Reply | 0 comments |
headers
Vlad Ureche | 8 Feb 13:18
Picon
Gravatar

Re: Sbteclipse - skip some source entries in the Eclipse project


I received a great answer to my question on the sbt mailing list, so anyone interested in this question (or a quick sbt dependency lesson), please read the thread on the sbt mailing list.

Cheers,
Vlad

On Tue, Feb 7, 2012 at 2:46 PM, Vlad Ureche <vlad.ureche-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:
Hello everyone,

I have a newbie question about sbteclipse: In the project I am working on, there are Scala sources but no Java sources at all. Is there a way to configure sbteclipse not to generate project source entries for Java?
The things I tried, without success:
 - setting the javaSources in {Compile. Test} to Nil -- the setting expects a java.io.File, and will only settle for that
 - messing with the sbteclipse createSrc setting, which either selects all sources or none

Is there a way to instruct sbteclipse to skip the Java sources in the Eclipse project?

Thanks,
Vlad


Permalink | Reply | 0 comments |
headers
Tony Sloane | 10 Feb 15:57
Picon
Gravatar

Problem with Kiama migration to Sonatype

Does anyone know who is actually doing the migration of projects from scala-tools.org to Sonatype's repository?

My com.googlecode.kiama project is published on scala-tools.org.

One of my users just reported that the

  http://scala-tools.org/repo-releases/com/googlecode

address is redirecting to 

  https://oss.sonatype.org/content/repositories/releases/com/googlecode/

which doesn't contain Kiama, so Kiama is no longer found when sbt looks for it.

I did hear from the Sonatype people about another project of mine (com.googlecode.sbt-rats) and that
appears to have been copied across to the Sonatype repo.  However, I haven't heard from them about Kiama, it
has not been copied and I don't know whether that's an oversight or whether it's just a work in progress.

So, who is actually doing it and how can I find out when things will be accessible again?  It's frustrating for
these changes to be happening magically without any clear announcements and breaking things for library users...

thanks,
Tony
Permalink | Reply | 0 comments |
headers
Doug Tangren | 10 Feb 22:44
Picon
Gravatar

scala-tools@... - 1 Message in 1 Topic



On Fri, Feb 10, 2012 at 4:34 PM, <scala-tools <at> googlegroups.com> wrote:

Group: http://groups.google.com/group/scala-tools/topics

    Tony Sloane <inkytonik-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> Feb 10 03:57PM +0100  

    Does anyone know who is actually doing the migration of projects from scala-tools.org to Sonatype's repository?
     
    My com.googlecode.kiama project is published on scala-tools.org.
     
    One of my users just reported that the
     
    http://scala-tools.org/repo-releases/com/googlecode
     
    address is redirecting to
     
    https://oss.sonatype.org/content/repositories/releases/com/googlecode/
     
    which doesn't contain Kiama, so Kiama is no longer found when sbt looks for it.
     
    I did hear from the Sonatype people about another project of mine (com.googlecode.sbt-rats) and that appears to have been copied across to the Sonatype repo. However, I haven't heard from them about Kiama, it has not been copied and I don't know whether that's an oversight or whether it's just a work in progress.
     
    So, who is actually doing it and how can I find out when things will be accessible again? It's frustrating for these changes to be happening magically without any clear announcements and breaking things for library users...
     
    thanks,
    Tony

     


I had a similar bug report with one of my scala-tools projects as well
 

    You received this message because you are subscribed to the Google Group scala-tools.
    You can post via email.
    To unsubscribe from this group, send an empty message.
    For more options, visit this group.


    Permalink | Reply | 2 comments |
    headers
    Tony Sloane | 11 Feb 09:43
    Picon
    Gravatar

    Re: Problem with Kiama migration to Sonatype

    On 10/02/2012, at 10:44 PM, Doug Tangren wrote:

    I had a similar bug report with one of my scala-tools projects as well

    The upshot seems to be that if they couldn't work out who was the maintainer of a project, they haven't moved it across since they didn't know who to contact. The result is that all of those projects are now inaccessible since scala-tools.org is redirecting to the Sonatype OSS repo. It would have been more social for the scala-tools redirect to wait until all of the projects had moved.

    Until I can find time to work out how to published to Sonatype, not difficult I presume but a time commitment I could do without right now, my library is not usable.  Not cool.

    Tony

    Permalink | Reply | 1 comment |
    headers
    Paul Phillips | 11 Feb 15:48

    Re: Re: Problem with Kiama migration to Sonatype



    On Sat, Feb 11, 2012 at 12:43 AM, Tony Sloane <inkytonik <at> gmail.com> wrote:
    It would have been more social for the scala-tools redirect to wait until all of the projects had moved.

    Based on the events leading up to this, that was the point.  No going gently into that good night for some of us.  Anyone with kids knows that kids sometimes have trouble distinguishing "good attention" and "bad attention", and so too do some of the overgrown children.

    Permalink | Reply | 0 comments |
    headers
    Kostas Kougios | 11 Feb 22:55

    can't release my project (sonatype) because of missing javadocs

    ...and can't generate javadocs since this is a scala project.

Any ideas?

Thanks,

Kostas
    Permalink | Reply | 14 comments |
    headers
    Daniel Sobral | 12 Feb 01:42
    Picon
    Gravatar

    Re: can't release my project (sonatype) because of missing javadocs

    On Sat, Feb 11, 2012 at 19:55, Kostas Kougios
<kostas.kougios@...> wrote:
> ...and can't generate javadocs since this is a scala project.

But SBT can generate javadoc jars from ScalaDocs. You can even see
such javadoc jars coming with Scala itself.

--

-- 
Daniel C. Sobral

I travel to the future all the time.
    Permalink | Reply | 13 comments |
    headers
    Daniel Sobral | 12 Feb 01:44
    Picon
    Gravatar

    Re: can't release my project (sonatype) because of missing javadocs

    Or I thought you could... Weird, I could swear they were there, but
they are not.

On Sat, Feb 11, 2012 at 22:42, Daniel Sobral <dcsobral@...> wrote:
> On Sat, Feb 11, 2012 at 19:55, Kostas Kougios
> <kostas.kougios@...> wrote:
>> ...and can't generate javadocs since this is a scala project.
>
> But SBT can generate javadoc jars from ScalaDocs. You can even see
> such javadoc jars coming with Scala itself.
>
> --
> Daniel C. Sobral
>
> I travel to the future all the time.

--

-- 
Daniel C. Sobral

I travel to the future all the time.
    Permalink | Reply | 12 comments |

    Gmane