Permalink
Browse files

Adapted README and Contributors for patch

Added asflier to contributors
Updated README to incorporate changes from patches
Increased version to 0.7.0
Added notes for release 0.7.0
Increased plugin version of eclipsify used for SbtEclipsify to 0.7.0
  • Loading branch information...
1 parent 632c7eb commit d30a42b6d17c230a4159de22782ca406122f0104 @musk committed Nov 5, 2010
Showing with 14 additions and 7 deletions.
  1. +3 −4 README.md
  2. +1 −0 contributors.txt
  3. +6 −0 notes/0.7.0.markdown
  4. +3 −2 project/build.properties
  5. +1 −1 project/plugins/Plugins.scala
View
@@ -37,6 +37,8 @@ The following properties can be added to the build.properties of your project in
`plugin.project` (default: false) => if set to true the project is setup to be a plugin project (osgi projects are handled as plugin projects in eclipse). This results in the plugin dependencies container being added to .classpath and the manifest and schema builder being added to .project.
+`eclipse.project.nature` (default: scala) => the nature of the project can be either "java" or "scala". Unknown values are converted to "scala"
+
## Using the Plugin in your own project
You need to create a plugin definition in your sbt project.
The plugin definition can be any Scala class that extends PluginDefinition and is located in the plugins directory in the projects subfolder of your sbt project.
@@ -52,7 +54,7 @@ next create a file name MySbtProjectPlugins.scala and add the following text to
import sbt._
class MySbtProjectPlugins(info: ProjectInfo) extends PluginDefinition(info) {
- lazy val eclipse = "de.element34" % "sbt-eclipsify" % "0.6.0"
+ lazy val eclipse = "de.element34" % "sbt-eclipsify" % "0.7.0"
}
This will enable your project to get the plugin in order to use it you need to add it to your project defintion.
@@ -69,15 +71,12 @@ After reloading the project you should have a new action named "eclipse" which w
Now all you need to do is import the Project into your Eclipse workspace as an existing Project and everything should work.
-__Note__: The old trait SbtEclipsifyPlugin has been removed from this version.
-
## Known Issues
Crossbuilds are not supported officially but they might work (testing still pending).
## FUTURE
* Better documentation (as always :) )
* Add ability to fine tune generation
-* Support for java only projects? Does this even make sense when using sbt?
* Add ability to include directories besides those in test and main
* Add generation of subprojects like with eclipse:eclipse from maven
* Improve the test coverage (still need to figure out how to mock the sbt parts)
View
@@ -3,3 +3,4 @@ I like to thank the people that contributed to this project.
Stefan Langer
dholbrook
plalloni
+asflierl
View
@@ -0,0 +1,6 @@
+### Fixed paths bug and added pure java project support ###
+
+ * Added patch from asflierl to correct java classpath generation
+ * Added patch from asflierl to support pure Java projects
+
+Thank you asflierl for the great work
View
@@ -1,14 +1,15 @@
#Project properties
-#Wed Aug 11 22:22:42 CEST 2010
+#Fri Nov 05 17:39:53 CET 2010
project.name=sbt-eclipsify
def.scala.version=2.7.7
include.plugin=true
sbt.dependency=true
plugin.project=false
sbt.version=0.7.4
eclipse.name=Eclipsify
+eclipse.project.nature=scala
build.scala.versions=2.7.7
project.organization=de.element34
project.initialize=false
-project.version=0.6.1
+project.version=0.7.0
include.project=true
@@ -30,7 +30,7 @@
import sbt._
class SbtEclipsifyPlugin(info: ProjectInfo) extends PluginDefinition(info) {
- lazy val eclipse = "de.element34" % "sbt-eclipsify" % "0.5.4"
+ lazy val eclipse = "de.element34" % "sbt-eclipsify" % "0.7.0"
val t_repo = "t_repo" at "http://tristanhunt.com:8081/content/groups/public/"
lazy val posterous = "net.databinder" % "posterous-sbt" % "0.1.4"
}

0 comments on commit d30a42b

Please sign in to comment.