sakai windows环境下已经成功部署，但当导入到ECLIPSE时就会报一万多个错误，不知道有人碰到过没有，而且2.6.2版本只有一个工程，2.5版本确实每个文件夹一个工程，望解释。

也不知道具体是什么错。是不是缺jar包什么的？
2.6.2也可以是一个目录一个工程。你看每个文件夹下面都有.project文件。如果用maven:eclipes的话，相关源代码目录已经包含到.classpath了，所以看起来就只有一个工程。

兄弟，那样我也试过了，可是还是不行，整了好多次了，也换了2.5.6版本还是不行啊

sakai windows环境下已经成功部署，但当导入到ECLIPSE时就会报一万多个错误，今天弄了一天，也没有成功，baiwenwo你的成功了没？

和楼上的问题一样，我也没找到解决方法，哪位兄弟成功了望指点

最近也在研究这个，昨天刚研究出来，安装m2eclipse插件，右击SAKAI项目，选择“Maven4MyEclipse”，选择“update project configuration“，等那么一会儿，OK，没有了。我当时更新完了还有红叉，不过关了再开就OK了。

请问如何搭建sakai oae 的开发环境啊？我运行以下代码后报错了
cd nakamura
set MAVEN_OPTS="-Xmx256m -XX:PermSize=256m"
mvn clean install
报错信息为
[ERROR] Failed to execute goal org.apache.sling:maven-launchpad-plugin:2.1.0:pr
pare-package (prepare-package-jar) on project org.sakaiproject.nakamura.app: Un
ble to find artifact. Could not find artifact org.sakaiproject.nakamura:org.sak
iproject.nakamura.ojdbc:jar:CURRENT-VERSION in maven repo (http://repo1.maven.o
g/maven2/)
[ERROR]
[ERROR] Try downloading the file manually from the project website.
[ERROR]
[ERROR] Then, install it using the command:
[ERROR] mvn install:install-file -DgroupId=org.sakaiproject.nakamura -Dartifact
d=org.sakaiproject.nakamura.ojdbc -Dversion=CURRENT-VERSION -Dpackaging=jar -Df
le=/path/to/file
[ERROR]
[ERROR] Alternatively, if you host your own repository you can deploy the file
here:
[ERROR] mvn deploy:deploy-file -DgroupId=org.sakaiproject.nakamura -DartifactId
org.sakaiproject.nakamura.ojdbc -Dversion=CURRENT-VERSION -Dpackaging=jar -Dfil
=/path/to/file -Durl=[url] -DrepositoryId=[id]
[ERROR]
[ERROR]
[ERROR] org.sakaiproject.nakamura:org.sakaiproject.nakamura.ojdbc:jar:CURRENT-V
RSION
[ERROR]
[ERROR] from the specified remote repositories:
[ERROR] maven repo (http://repo1.maven.org/maven2/, releases=true, snapshots=fa
se),
[ERROR] apache-snapshots (http://repository.apache.org/snapshots/, releases=fal
e, snapshots=true),
[ERROR] sakai-releases (http://source.sakaiproject.org/maven2/, releases=true,
napshots=false),
[ERROR] sakai-snapshots (http://source.sakaiproject.org/maven2-snapshots, relea
es=false, snapshots=true),
[ERROR] java.net (http://download.java.net/maven/2, releases=true, snapshots=fa
se),
[ERROR] modularity-releases (http://m2.modularity.net.au/releases, releases=tru
, snapshots=false),
[ERROR] modularity-snapshots (http://m2.modularity.net.au/snapshots, releases=f
lse, snapshots=true),
[ERROR] OPS4J (http://repository.ops4j.org/maven2, releases=true, snapshots=fal
e),
[ERROR] sonatype (https://oss.sonatype.org/content/repositories/releases/, rele
ses=true, snapshots=false),
[ERROR] sonatype-nexus-snapshots (https://oss.sonatype.org/content/repositories
snapshots, releases=false, snapshots=true),
[ERROR] central (http://repo.maven.apache.org/maven2, releases=true, snapshots=
alse)
[ERROR] -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e swi
ch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please re
d the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecution
xception
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the comman

[ERROR]   mvn <goals> -rfrg.sakaiproject.nakamura.app