I'm trying to eclipsify a play project that I use with heroku.
I've downloaded and unzipped the play 2.1.1
According to the documentation I run this command in my project directory:
play eclipse
And I get this errors
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.scala-sbt#sbt;${{sbt.version}}: not found
::::::::::::::::::::::::::::::::::::::::::::::
I've found some answers about setting the build.propeties file but it is already set. I don't know what to do. Please help.
Thanks
Need PROJECT/project/build.properties
sbt.version=0.12.2
file content is only 1 line
refer : http://jackviers.blogspot.kr/2012/01/sbt-scalas-simple-build-tool-series.html
On Github, James Ward and Matt Raible provided a comparison application for Play! framework 2 and Grails.
If you switch betsween branches, you will find their presentation slides too.
https://github.com/jamesward/happytrails
Related
I installed Intellij IDEA 15.0.4 + Scala plugin (2.2.0) on a computer with an internet connection, created a new SBT project and all the external dependencies were added to the project:
i.stack.imgur.com/v560H.png
However, when I try to do the same thing in our issolated network (no internet) against our Artifactory server, I got the following message:
Error:Error while importing SBT project:...
http://zzz:8081/artifactory/scala_local/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.fusesource.jansi#jansi;1.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS unresolved
dependency: org.fusesource.jansi#jansi;1.11: not found Error during
sbt execution: Error retrieving required libraries (see
C:\Users....sbt\boot\update.log for complete log) Error: Could not
retrieve jansi 1.11See complete log in C:\Users....IdeaIC15\system\log\sbt.last.log
So I figured I need to get jansi 1.11 up to Artifactory (to /org/fusesource/jansi/jansi/1.11/).
After uploading jansi to Artifactory, I refreshed SBT and started getting the following message:
Error:Error while importing SBT project:Error during sbt execution: No
Scala version specified or detected
So I'm guessing it has something to do with the fact that Scala is not available in Artifactory? If that's the reason, it seems unreasonable to upload all the jars to their respective paths manually, and I couldn't "guess" the path in my many tries... So I'm pretty sure I'm doing something wrong here...
This is my build.sbt:
name := "untitled"
version := "1.0"
scalaVersion := "2.10.4"
This is my .sbt\repositories:
[repositories] local my-ivy-proxy-releases: http://zzz:8081/artifactory/scala_local/, [organization]/[module]/(scala_[scalaVersion]/)(sbt_[sbtVersion]/)[revision]/[type]s/[artifact](-[classifier]).[ext] my-maven-proxy-releases: http://zzz:8081/artifactory/scala_local/
(sorry for the layout, won't let me post more than 2 links...)
I checked some similar issues here, nothing seemed to help...
I'd appreciate your help on what I should check / read on...
Is there a way to automatically deploy all the dependencies to the correct path in Artifactory?
***EDIT:
Ok, so I removed .sbt\repositories file, invalidated the IntelliJ cache and restarted, created a new SBT project...
This didn't seem to help, also
now it seems that it doesn't recognize the build.sbt syntax anymore...
Even when I add the resolver, it completely ignores it...
I manually deleted the directories in /.sbt/boot/other/ (had jansi and scala-sbt there), and now it can't resolve jansi again, only this time it tries to connect to repo1.maven.org... :
Error:Error while importing SBT project:<br/>...<br/><pre> https://repo1.maven.org/maven2/org/fusesource/jansi/jansi/1.11/jansi-1.11.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.fusesource.jansi#jansi;1.11: not found
::::::::::::::::::::::::::::::::::::::::::::::
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS
unresolved dependency: org.fusesource.jansi#jansi;1.11: not found
Error during sbt execution: Error retrieving required libraries
(see C:\Users\...\.sbt\boot\update.log for complete log)
Error: Could not retrieve jansi 1.11
Java HotSpot(TM) 64-Bit Server VM warning: ignoring option MaxPermSize=384M; support was removed in 8.0</pre><br/>See complete log in C:\Users\...\.IdeaIC15\system\log\sbt.last.log
Thanks,
PA
We encounter a similar issue.
What finally solved the problem was removing .sbt\repository file.
Then all dependency could be resolved with the default repositories.
It is the problem of IDE you are using specially the scala plugin in it. You can get ride of this just go to the folder where the build.sbt is created. Delete the "project" folder and open cmd, run "sbt" command on the folder, a new project folder will be created. Now you can open that in IDE.
It may be that you may find some problem very first in ide, if you build the project once , all the problems will go away.
I'm using IntelliJ IDEA 13 (Community Edition) with the Scala plugin.
My initial import of an existing Scala project with a build.sbt worked fine. The library dependencies were picked up by IDEA. Additional dependencies added after the initial import were not picked up, although I had checked the auto-import option.
How can I force IDEA to reload the dependencies from build.sbt?
You can force SBT to reload changes:
Open SBT toolwindow (on the right side of IDE) and press refresh button.
If you use auto-import feature you need to save your file to force auto-refresh.
IF plugin gets 'stuck' it helps to invalidate cache (under file menu) and restart intellij.
As of 7 Dec, 2013, the issue is solved. You need to update the Scala plugin in IntelliJ IDEA (this applies to both community and ultimate editions).
This is the link to the issue opened on JetBrains developer community web site:
http://devnet.jetbrains.com/thread/451395
This may be due to a broken publication of org.jetbrains:sbt-structure:latest.integration that occurred tonight, about 4 or 5 hours ago. Given that your post is 4 hours old ...
You can see the ivy activity in idea.log (~/Library/Logs/IntelliJIdea13 or ~/Library/Logs/IdeaIC13 on OSX).
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: UNRESOLVED DEPENDENCIES ::
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn] :: org.jetbrains#sbt-structure;latest.integration: not found
[warn] ::::::::::::::::::::::::::::::::::::::::::::::
[warn]
[warn] Note: Some unresolved dependencies have extra attributes. Check that these dependencies exist with the requested attributes.
[warn] org.jetbrains:sbt-structure:latest.integration (sbtVersion=0.13, scalaVersion=2.10)
I have opened a ticket at JetBrains.
Ticket for broken plublication of sbt.jetbrains is resolved. Updating scala plugin will fix this issue
Ticket : http://devnet.jetbrains.com/thread/451395
Perhaps this working only for some kind of projects, but in my case,
on the Library side, I do in sbt: publishLocal
on the Client side where the Library goes into, I click the menu item Build -> Build (Ctrl-F9), and sometimes, when open Files or Intellisens are not yet current, I do Ctrl-Alt-Y (Menu item File -> Synchronize) to get the file reflecting the refreshed code base.
Not having to refresh all sbt projects is faster for me.
I have created a scala project with play framework 2.0.
The project compiles and runs fine both with sbt and play commands.
However, the problems started when I tried to add another play project as a dependency to my project, because I needed to reuse some of its classes.
sbt compile succeeds, but play compile/run does not.
They give me the following error:
sbt.ResolveException: unresolved dependency: name_of_old_project_play_dependency: not found
I am also not able to run the project with sbt run; whenever I do a request to the play framework, I get a null pointer exception.
Is that because both the projects are play projects and maybe there is a conflict somewhere?
Any insight would be appreciated!
Please be sure to view the play version since sbt (the build system play uses) may have different versions.
Please verify the build.properties and plugins.sbt play version.
A technique I use to solve unresolved dependencies is to check the links that sbt tries to access.
I manually try to fetch the file by visiting the failed sites. I usually discover I have a version mishap.
I am trying to get an open source project running with scala that is built using sbt.
I downloaded sbt and set it up. But when I try to run sbt from the command line, I get the following error.
:: problems summary :: :::: WARNINGS [NOT FOUND ]
commons-logging#commons-logging;1.0.4!commons-logging.jar (1ms)
==== Maven2 Local: tried
file:///Users/jeremy/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: FAILED DOWNLOADS ::
:: ^ see resolution messages for details ^ ::
::::::::::::::::::::::::::::::::::::::::::::::
:: commons-logging#commons-logging;1.0.4!commons-logging.jar
::::::::::::::::::::::::::::::::::::::::::::::
:: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS download
failed: commons-logging#commons-logging;1.0.4!commons-logging.jar
Error during sbt execution: Error retrieving required libraries (see
/Users/jeremy/sourceCode/public/scalaConsole/project/boot/update.log
for complete log) Error: Could not retrieve sbt 0.10.1
Any ideas on how I could resolve this.
I have scala 2.9.1 and sbt version 0.10.1
Thanks
It worked for me after I removed both ~/.m2/repository/commons-logging and ~/.ivy2/cache/commons-logging. If sbt founds none of this two paths it will actually try and download the commons logging package.
Sometimes maven doesn't download the files correctly and you'll only find a .pom file in the repository and no commons-logging-1.0.4.jar file. First I removed ~/.m2/repository/commons-logging. Then I downloaded the jar manually from http://search.maven.org/remotecontent?filepath=commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar and finally installed the jar using the mvn install command:
mvn install:install-file -DgroupId=commons-logging -DartifactId=commons-logging -Dversion=1.0.4 -Dpackaging=jar -Dfile=commons-logging-1.0.4.jar
Are you behind a proxy server? If so you may need to modify your sbt bat or sh script to pass along the proxy information to the JVM like so:
java -XX:MaxPermSize=96m -Xmx512m -Dhttp.proxyHost=my.proxy.server.com -Dhttp.proxyPort=1234 -jar sbt-launch-0.10.1.jar
I don't know what the root cause of the issue is. But I use a script that automatically installs and launches sbt; so I modified the script to download commons-logging before running sbt.
The sbt launcher is here: https://gist.github.com/1274530
To run sbt, save the script somewhere in your $PATH, make sure that is executable, and run it by typing sbt.
Add http://repo1.maven.org/maven to the maven.repo.remote property in your project.properties file. This will download the file from the maven2 remote repository.
Old entry:
maven.repo.remote=http://www.ibiblio.org/maven
New entry:
maven.repo.remote=http://www.ibiblio.org/maven,http://repo1.maven.org/maven
New clone from git repo, fresh install of groovy and grails. Seems to work for everyone else on my team? New to groovy and grails. Any help or general troubleshooting is appreciated.
::::::::::::::::::::::::::::::::::::::::::::::
:: UNRESOLVED DEPENDENCIES ::
::::::::::::::::::::::::::::::::::::::::::::::
:: org.grails.plugins#dynamic-jasper;0.6: not found
:: org.grails.plugins#testing;0.5: not found
:: org.grails.plugins#code-coverage;1.1.8: not found
:: org.grails.plugins#liquibase;1.9.3.3: not found
::::::::::::::::::::::::::::::::::::::::::::::
You may just need to do a grails clean - have you tried that?
Grails stores its plugins in ~/.grails; if all else fails, it might not hurt to go in and clean out that directory after doing a fresh install.