spring roo 1.2.4中的实体插件问题
spring roo 1.2.4中的实体插件问题
提问于 2013-10-13 02:47:18
我刚刚更新到roo 1.2.4，当我尝试使用实体命令时，我得到了以下信息：
backoffice roo> entity
Command 'entity' not found (for assistance press TAB or type "hint" then hit ENTER)
Located add-on that may offer this command
1 found, sorted by rank; T = trusted developer; R = Roo 1.2 compatible
ID T R DESCRIPTION -------------------------------------------------------------
01 Y Y 1.2.0.M1 Support for the creation and management of domain entities.
--------------------------------------------------------------------------------
[HINT] use 'addon info id --searchResultId ..' to see details about a search result
[HINT] use 'addon install id --searchResultId ..' to install a specific search result, or
[HINT] use 'addon install bundle --bundleSymbolicName TAB' to install a specific add-on version
backoffice roo> addon install id --searchResultId 01
Target resource(s):
-------------------
Spring Roo - Addon - Entity (1.2.0.M1)
Required resource(s):
---------------------
Spring Roo - Support (1.2.0.RELEASE)
Deploying...done.
backoffice roo> [org.apache.felix.bundlerepository [12]] Resolver: Start error -
org.springframework.roo.addon.entity
org.apache.felix.log.LogException: org.osgi.framework.BundleException: Uses constraint violation. Unable to resolve module org.springframework.roo.addon.entity
[83.0] because it is exposed to package 'org.springframework.roo.support.util' from modules org.springframework.roo.support [68.1] and org.springframework.roo.s
upport [68.0] via two dependency chains.
Chain 1:
org.springframework.roo.addon.entity [83.0]
import: (&(package=org.springframework.roo.support.util)(version>=1.2.0)(!(version>=2.0.0)))
|
export: package=org.springframework.roo.support.util org.springframework.roo.support [68.1]
Chain 2:
org.springframework.roo.addon.entity [83.0]
import: (&(package=org.springframework.roo.classpath.customdata)(version>=1.2.0)(!(version>=2.0.0)))
|
export: package=org.springframework.roo.classpath.customdata; uses:=org.springframework.roo.support.util
org.springframework.roo.classpath [52.0]
import: (&(package=org.springframework.roo.support.util)(version>=1.2.0)(!(version>=2.0.0)))
|
export: package=org.springframework.roo.support.util org.springframework.roo.support [68.0]
at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3570)
at org.apache.felix.framework.Felix.startBundle(Felix.java:1797)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:927)
at org.apache.felix.framework.BundleImpl.start(BundleImpl.java:914)
at org.apache.felix.bundlerepository.impl.ResolverImpl.deploy(ResolverImpl.java:630)
at org.apache.felix.bundlerepository.impl.ObrCommandImpl._deploy(ObrCommandImpl.java:395)
at org.apache.felix.bundlerepository.impl.ObrCommandImpl.deploy(ObrCommandImpl.java:333)
at org.apache.felix.bundlerepository.impl.ObrCommandImpl.execute(ObrCommandImpl.java:119)
at org.apache.felix.shell.impl.Activator$ShellServiceImpl.executeCommand(Activator.java:286)
at org.springframework.roo.felix.FelixDelegator.perform(FelixDelegator.java:208)
at org.springframework.roo.felix.FelixDelegator.obrStart(FelixDelegator.java:146)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.roo.process.manager.ProcessManagerHostedExecutionStrategy$1.callback(ProcessManagerHostedExecutionStrategy.java:47)
at org.springframework.roo.process.manager.internal.DefaultProcessManager.doTransactionally(DefaultProcessManager.java:283)
at org.springframework.roo.process.manager.internal.DefaultProcessManager.execute(DefaultProcessManager.java:64)
at org.springframework.roo.process.manager.ProcessManagerHostedExecutionStrategy.execute(ProcessManagerHostedExecutionStrategy.java:44)
at org.springframework.roo.shell.AbstractShell.executeCommandImpl(AbstractShell.java:226)
at org.springframework.roo.shell.AbstractShell.executeCommand(AbstractShell.java:146)
at org.springframework.roo.addon.roobot.client.AddOnRooBotOperationsImpl.installOrUpgradeAddOn(AddOnRooBotOperationsImpl.java:478)
at org.springframework.roo.addon.roobot.client.AddOnRooBotOperationsImpl.installAddon(AddOnRooBotOperationsImpl.java:396)
at org.springframework.roo.addon.roobot.client.AddODownloaded 100% of lookup
tallAddOn(AddOnRooBotOperationsImpl.java:458)
at org.springframework.roo.addon.roobot.client.AddOnCommands.installId(AddOnCommands.java:69)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Nat
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at org.springframework.roo.process.manager.ProcessManagerHostedExecutionStrategy$1.callback(ProcessManagerHostedExecutionStrategy.java:47)
at org.springframework.roo.process.manager.internal.DefaultProcessManager.doTransactionally(DefaultProcessManager.java:283)
at org.springframework.roo.process.manager.internal.DefaultProcessManager.execute(DefaultProcessManager.java:64)
at org.springframework.roo.process.manager.ProcessManagerHostedExecutionStrategy.execute(ProcessManagerHostedExecutionStrategy.java:44)
at org.springframework.roo.shell.AbstractShell.executeCommandImpl(AbstractShell.java:226)
at org.springframework.roo.shell.AbstractShell.executeCommand(AbstractShell.java:146)
at org.springframework.roo.shell.jline.JLineShell.promptLoop(JLineShell.java:421)
at org.springframework.roo.shell.jline.JLineShell.run(JLineShell.java:539)
at java.lang.Thread.run(Unknown Source)
Successfully installed add-on: Spring Roo - Addon - Entity [version: 1.2.0.M1]
[Hint] Please consider rating this add-on with the following command:
[Hint] addon feedback bundle --bundleSymbolicName org.springframework.roo.addon.
entity --rating ... --comment "..."
backoffice roo> quit在这之后，我再也不能启动roo了。如果我删除了缓存目录，我可以启动它，但我会在相同的位置结束。
更多信息，我最近刚从1.2.3升级。在大多数情况下，我的实体都是使用DBRE创建的。我的pom.xml使用的是roo版本1.2.4.RELEASE。
有什么想法吗？
回答 2
Stack Overflow用户
发布于 2014-08-05 17:36:30
老问题，但对于Roo新用户来说，参考(相对)旧的Roo说明、教程等可能仍然是一个绊脚石。
答:语法发生了变化。entity命令现在是entity jpa命令。
抱歉:我匆忙错过了另一个问题，mvivo很好地解决了这个问题。我想补充我自己的观点，即包的目录可以--我想说应该--被删除。这样做可能会造成下载时间的损失。但是，如果在本地系统上以某种方式下载了坏东西或以某种方式损坏了下载，则新版本和后续的addon命令将快速将捆绑包目录恢复到一致的最新状态。Roo中似乎没有冗余数据结构可以不同步。当然，我还没有遇到任何问题。
我只做了一两个星期的Roo，这样的帮助可以帮我节省大量的深夜时间。不过，我要说的是，Roo似乎表现得很好。我的意思是，当我尝试我认为合理的修复方法时，情况通常会变得更好。我有时会使用另一种系统--在这种系统中，事情变得更糟，显然与你做什么无关。小袋鼠不是那样的。它相对简单，因此具有内在的健壮性。我非常佩服Roo背后的设计见解。
Stack Overflow用户
发布于 2014-08-05 17:50:30
来解决Spring Roo没有启动的问题。删除所有Spring Roo文件夹(缓存和安装)尝试使用1.2.4 (或1.2.5)版本的全新安装。
正如这里已经回答的：entity命令被重命名为entity jpa (参见Spring Roo documentation)
页面原文内容由Stack Overflow提供。腾讯云小微IT领域专用引擎提供翻译支持
原文链接：
https://stackoverflow.com/questions/19337875
复制相关文章
相似问题
腾讯云开发者
