headers
Julien Richard-Foy | 1 May 2012 09:56
Picon

Re: Unable to resolve a dependency previously published on my github pages

Please help!

Why is my repository not even tried? Do I need to add another piece of 
information somewhere?

Regards,
Julien
Permalink | Reply | 0 comments |
headers
Ray Racine | 1 May 2012 20:13
Picon
Gravatar

Invertability Of Local Publication And Resolution

Hi, been away for a long time.


publish-local and update (which attempts to resolve from the local repository) don't seem to share the same default pattern.  I've always worked around this by manually setting patterns but it seems a bit inefficient.

Example.

Create a tiny project Hello with build.sbt as follows: 

name := "hello"

version := "1.0"

organization := "ray"

Publish said project via publish-local.

sbt> publish-local
...
[info] published hello_2.9.1 to /home/ray/.ivy2/local/ray/hello_2.9.1/1.0/jars/hello_2.9.1.jar
[info] published ivy to /home/ray/.ivy2/local/ray/hello_2.9.1/1.0/ivys/ivy.xml
...

Now lets pretend we want to use the above published local artifact as a standard sbt dependency.

An equally simple sbt.build of a project which uses hello.jar

name := "main"

version := "1.0"

organization := "ray"

libraryDependencies += "ray" % "hello" % "1.0"

sbt> update

Resolving ray#hello;1.0 ...
[warn] module not found: ray#hello;1.0
[warn] ==== local: tried
[warn]   /home/ray/.ivy2/local/ray/hello/1.0/ivys/ivy.xml
...
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] ::          UNRESOLVED DEPENDENCIES         ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: ray#hello;1.0: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[error] {file:/tmp/p1/}default-df7991/*:update: sbt.ResolveException: unresolved dependency: ray#hello;1.0: not found

The out-of-the-box sbt local publish pattern does not match the out-of-box sbt local resolution pattern.

[info] published ivy to /home/ray/.ivy2/local/ray/hello_2.9.1/1.0/ivys/ivy.xml
[warn]       (resolving from)  /home/ray/.ivy2/local/ray/hello/1.0/ivys/ivy.xml

Can we bring the "default" local pattern for publish/resolution into alignment?


Thanks,

Ray

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/D3sTOLKCezAJ.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 3 comments |
headers
Ray Racine | 1 May 2012 20:23
Picon
Gravatar

Re: Resolver.ssh using ssk keyfile + password prompt does not work

I think what you are looking to do here is use "ssh-agent".   There is plenty of googleage on it.  In essence, you add your key to ssh-agent, for which you will prompted the key decrypt password, after that ssh-agent will provide the key as needed without the continued prompting.  This is completely an ssh suite behavior and is outside of SBT's control.



On Mon, Apr 30, 2012 at 1:30 PM, fmpwizard <fmpwizard <at> gmail.com> wrote:
Hi,

At work we have something like this on a build file:

  val cloudRepo = Resolver.ssh("work repo", ivyRepo,22)(Resolver.ivyStylePatterns) as ("ivy", Path.userHome / ".ssh" / "id_rsa") withPermissions("0755")


the idea is to connect using ssh on port 22 to the server in val ivyRepo using the username ivy  , my ssh key file.

The problem is that if my ssh key requires a password, I get a popup asking for it, no problem, I enter my password for the key, but the popup comes back again.
I think the problem is that my real user on my laptop is diego.medina, but to ssh to my server I use   ivy, like:



that works fine, but the ivy popup asks for user and password, but then I think it tries to ssh like


which of curse fails.

Does anyone have any solutions?

  Thanks

   Diego

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/80KRwNoMv-UJ.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 1 comment |
headers
Jesse C | 1 May 2012 22:39
Picon

[sbteclipse] Native libraries in classpath

So a couple of the libraries in our unmanaged lib directory have native libraries that need to be linked to them.  Easy enough to do in the eclipse project, but we're regenerating our eclipse projects fairly frequently as we add/remove dependencies or make changes to our build setup.  So it would be great to have the ability to associate a native library path with a library in the sbteclipse configuration so we don't have to manually add that each time we regenerate the project.  In the eclipse .classpath file it looks like:

        <classpathentry kind="lib" path="../project/lib/zmq.jar">
                <attributes>
                        <attribute name="org.eclipse.jdt.launching.CLASSPATH_ATTR_LIBRARY_PATH_ENTRY" value="project/src/libOther/native/linux/x64"/>
                </attributes>
        </classpathentry>

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 2 comments |
headers
ijuma | 1 May 2012 23:44
Picon

Re: Resolver.ssh using ssk keyfile + password prompt does not work

On Tuesday, 1 May 2012 19:23:42 UTC+1, Ray Racine wrote:

I think what you are looking to do here is use "ssh-agent".   There is plenty of googleage on it.  In essence, you add your key to ssh-agent, for which you will prompted the key decrypt password, after that ssh-agent will provide the key as needed without the continued prompting.  This is completely an ssh suite behavior and is outside of SBT's control.

This doesn't work with SBT since it relies on Ivy which relies on JSch which doesn't support ssh-agent (at least in its default configuration). Maven, on the other hand, does the right thing in this case.

Best,
Ismael

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/9_9s8IBd-VEJ.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 0 comments |
headers
ijuma | 1 May 2012 23:48
Picon

Re: Resolver.ssh using ssk keyfile + password prompt does not work

On Monday, 30 April 2012 18:30:28 UTC+1, fmpwizard wrote:

that works fine, but the ivy popup asks for user and password, but then I think it tries to ssh like

Coincidentally I ran into a similar issue today. In my case, the prompt worked for a dsa key but not for a rsa key. The username was the same for both and I tested that the passphrase was correct by using plain ssh. No idea what the real problem is, but SBT has always had unreliable support for SSH since it relies on Ivy. I moved away from it in the past due to that and my experiment today reinforced that belief.

Best,
Ismael

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/gpktMCvIkyMJ.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 0 comments |
headers
Miles Sabin | 2 May 2012 00:03
Gravatar

Conditionally including a source directory

Hi folks,

What's the simplest way of arranging for a source directory to be
included in the build conditional on the value of a setting?
Specifically I want to include a 2.9.x specific source directory iff
the project's scalaVersion <= 2.10.

Cheers,

Miles

--

-- 
Miles Sabin
tel: +44 7813 944 528
gtalk: miles <at> milessabin.com
skype: milessabin
g+: http://www.milessabin.com
http://twitter.com/milessabin
http://underscoreconsulting.com
http://www.chuusai.com
Permalink | Reply | 5 comments |
headers
Christian Goetze | 2 May 2012 01:14
Picon
Gravatar

Re: Invertability Of Local Publication And Resolution

would using "ray" %% "hello" % "1.0" help?

On Tue, May 1, 2012 at 11:13 AM, Ray Racine <ray.racine <at> gmail.com> wrote:
Hi, been away for a long time.

publish-local and update (which attempts to resolve from the local repository) don't seem to share the same default pattern.  I've always worked around this by manually setting patterns but it seems a bit inefficient.

Example.

Create a tiny project Hello with build.sbt as follows: 

name := "hello"

version := "1.0"

organization := "ray"

Publish said project via publish-local.

sbt> publish-local
...
[info] published hello_2.9.1 to /home/ray/.ivy2/local/ray/hello_2.9.1/1.0/jars/hello_2.9.1.jar
[info] published ivy to /home/ray/.ivy2/local/ray/hello_2.9.1/1.0/ivys/ivy.xml
...

Now lets pretend we want to use the above published local artifact as a standard sbt dependency.

An equally simple sbt.build of a project which uses hello.jar

name := "main"

version := "1.0"

organization := "ray"

libraryDependencies += "ray" % "hello" % "1.0"

sbt> update

Resolving ray#hello;1.0 ...
[warn] module not found: ray#hello;1.0
[warn] ==== local: tried
[warn]   /home/ray/.ivy2/local/ray/hello/1.0/ivys/ivy.xml
...
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] ::          UNRESOLVED DEPENDENCIES         ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: ray#hello;1.0: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[error] {file:/tmp/p1/}default-df7991/*:update: sbt.ResolveException: unresolved dependency: ray#hello;1.0: not found

The out-of-the-box sbt local publish pattern does not match the out-of-box sbt local resolution pattern.

[info] published ivy to /home/ray/.ivy2/local/ray/hello_2.9.1/1.0/ivys/ivy.xml
[warn]       (resolving from)  /home/ray/.ivy2/local/ray/hello/1.0/ivys/ivy.xml

Can we bring the "default" local pattern for publish/resolution into alignment?


Thanks,

Ray

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To view this discussion on the web visit https://groups.google.com/d/msg/simple-build-tool/-/D3sTOLKCezAJ.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 2 comments |
headers
Paul Phillips | 2 May 2012 01:29

Re: Conditionally including a source directory

Well, I don't know if it's the "simplest" way, but as I've had to do
this before, here's how I segregated some 2.10 only source such that
2.9 would still build.

    unmanagedSourceDirectories in Compile <++= (baseDirectory,
scalaVersion)((bd, sv) =>
      if (sv startsWith "2.10.") Seq(bd / "src" / "main" /
"scala-2.10") else Nil
    ),

On Tue, May 1, 2012 at 3:03 PM, Miles Sabin <miles <at> milessabin.com> wrote:
> Hi folks,
>
> What's the simplest way of arranging for a source directory to be
> included in the build conditional on the value of a setting?
> Specifically I want to include a 2.9.x specific source directory iff
> the project's scalaVersion <= 2.10.
>
> Cheers,
>
>
> Miles
>
> --
> Miles Sabin
> tel: +44 7813 944 528
> gtalk: miles <at> milessabin.com
> skype: milessabin
> g+: http://www.milessabin.com
> http://twitter.com/milessabin
> http://underscoreconsulting.com
> http://www.chuusai.com
>
> --
> You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
> To post to this group, send email to simple-build-tool <at> googlegroups.com.
> To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
> For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
>
Permalink | Reply | 4 comments |
headers
Oscar Vargas Torres | 2 May 2012 03:40
Picon

[sbtosgi] Help to build a basic bundle. Working Examples? Documentations or tutorials?

(Working on Mac OS X Lion, with JDK 1.7 from Oracle, sbt 0.11.2)

After I issue
$ sbt osgi-bundle

I keep getting a wrong MANIFEST.MF:
------->
Manifest-Version: 1.0
Bnd-LastModified: 1335919650936
Bundle-Activator: mx.umich.fie.dep.simple.gui.Activator
Bundle-ManifestVersion: 2
Bundle-Name: UMSNH.simple
Bundle-SymbolicName: UMSNH.simple
Bundle-Version: 1.0
Created-By: 1.7.0_04 (Oracle Corporation)
Import-Package: mx.umich.fie.dep.simple.gui
Include-Resource: /Users/oscarvarto/programacion/osgi/felix-simple/modul
 es/first/src/main/resources,/Users/oscarvarto/programacion/osgi/felix-s
 imple/modules/first/target/scala-2.9.1/resource_managed/main
Tool: Bnd-1.50.0
<------------

I want to export mx.umich.fie.dep.simple.gui, but cannot configure the project properly.

  •  My project's base directory is /Users/oscarvarto/programacion/osgi/felix-simple/modules/first/
    • I tried to configure sbtosgi in build.sbt with this contents:

-------------->

organization := "UMSNH"

name := "simple"

version := "1.0"

scalaVersion := "2.9.2"

libraryDependencies <+= scalaVersion { "org.scala-lang" % "scala-swing" % _ }

seq(osgiSettings: _*)

OsgiKeys.bundleActivator := Some("mx.umich.fie.dep.simple.gui.Activator")

OsgiKeys.exportPackage := Seq("mx.umich.fie.dep.simple.gui;version=\"1.0\"")

OsgiKeys.importPackage := Nil

OsgiKeys.privatePackage := Nil

<-------------------------

However, if I unjar the bundle, I get the wrong MANIFEST.MF

I also tried to write a Build.scala configuring the same options, following this post https://groups.google.com/forum/#!searchin/simple-build-tool/sbtosgi/simple-build-tool/Qfdbr2Af120/wlmHXAFPBvw, but couldn't write something that compiled properly.

Heiko Seeberger has done a great job but I need more documentation (or sadly, have to reluctantly work with java only)!! Does anybody knows a tutorial for sbtosgi? Has anyone some basic (working) example to share?

ScalaModules has a repo with examples, however, those are outdated (sbt 0.7, scala 2.8, so different sintax, etc.)...

HELP PLEASE!!!

--
You received this message because you are subscribed to the Google Groups "simple-build-tool" group.
To post to this group, send email to simple-build-tool <at> googlegroups.com.
To unsubscribe from this group, send email to simple-build-tool+unsubscribe <at> googlegroups.com.
For more options, visit this group at http://groups.google.com/group/simple-build-tool?hl=en.
Permalink | Reply | 5 comments |

Gmane