问题与实体插件1.2.4
我刚刚更新到1.2.4袋鼠,并试图使用实体命令时,我得到如下:问题与实体插件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
在此之后,我无法启动袋鼠了。如果我删除缓存目录,我可以启动它,但我最终会在同一个地方。
更多信息,我刚刚从1.2.3升级。大多数情况下,我的实体是使用DBRE创建的。我的pom.xml使用的是roo 1.2.4.RELEASE版本。
任何想法?
回答:
老问题,但它仍然是新的Roo的用户指的是(相对)老袋鼠的说明,教程的可能的绊脚石,等
答:语法发生了变化。 entity
命令现在是entity jpa
命令。
对不起:在匆忙我错过了其他的问题,这是深受mvivo处理。我会加我自己的意见,包目录是一个可以 - 我说应该 - 删除。这样做可能会在下载时造成一定的损失。布尔如果坏的东西莫名其妙地被下载或下载莫名其妙地被破坏本地系统,新版本,并随后插件命令在束目录将很快恢复到一致的,最新的最新状态。 Roo冗余数据结构中似乎没有可能不同步的内容。当然,我还没有遇到任何。
我已经做袋鼠只有一两个星期,并帮助诸如这些将有救了我大量的深夜时间。不过,我会说,Roo似乎表现得很好。我的意思是,当我尝试在我看来,合理的解决方法通常会变得更好。我偶尔会与其他类型的系统合作 - 显然情况变得更糟的是显然不管你做什么。 Roo不是那样的。这是相对简单的,因此,固有的强大。我非常赞赏Roo背后的设计见解。
回答:
为了解决Spring Roo的问题并未开始。删除所有Spring Roo文件夹(缓存和安装)尝试使用1.2.4(或1.2.5)版本的全新安装。
前面已经回答了这里:entity
命令被重命名为entity jpa
(见Spring Roo documentation)
以上是 问题与实体插件1.2.4 的全部内容, 来源链接: utcz.com/qa/266190.html