org.osgi.framework.BundleException

Unresolved constraint in bundle org.springfr amework.roo.shell.jline [48]: Unable to resolve 48.0: missing requirement [48.0] package; (&(package=jline)(version>=0.9.0)(!(version>=1.0.0))) [caused by: Unab le to resolve 62.0: missing requirement [62.0] package; (package=javax.swing)]

Solutions on the web6290

  • via Spring JIRA by alosman alosman, 1 year ago
    Unresolved constraint in bundle org.springfr amework.roo.shell.jline [48]: Unable to resolve 48.0: missing requirement [48.0] package; (&(package=jline)(version>=0.9.0)(!(version>=1.0.0))) [caused by: Unab le to resolve 62.0: missing requirement [62.0] package; (package=javax.swing)]
  • via Spring JIRA by alosman alosman, 1 year ago
    Unresolved constraint in bundle org.springfr amework.roo.shell.jline [48]: Unable to resolve 48.0: missing requirement [48.0] package; (&(package=jline)(version>=0.9.0)(!(version>=1.0.0))) [caused by: Unab le to resolve 62.0: missing requirement [62.0] package; (package=javax.swing)]
  • via Spring JIRA by Martin Lippert, 1 year ago
    Unresolved constraint in bundle org.springframework.roo.shell.jline [48]: Unable to resolve 48.0: missing requirement [48.0] package; (&(package=jline)(version>=0.9.0)(!(version>=1.0.0))) [caused by: Unable to resolve 62.0: missing requirement [62.0] package; (package=javax.swing)]
  • Stack trace

    • org.osgi.framework.BundleException: Unresolved constraint in bundle org.springfr amework.roo.shell.jline [48]: Unable to resolve 48.0: missing requirement [48.0] package; (&(package=jline)(version>=0.9.0)(!(version>=1.0.0))) [caused by: Unab le to resolve 62.0: missing requirement [62.0] package; (package=javax.swing)] at org.apache.felix.framework.Felix.resolveBundle(Felix.java:3409) at org.apache.felix.framework.Felix.startBundle(Felix.java:1719) at org.apache.felix.framework.Felix.setActiveStartLevel(Felix.java:1148) at org.apache.felix.framework.StartLevelImpl.run(StartLevelImpl.java:264) at java.lang.Thread.run(Thread.java:722)

    Write tip

    You have a different solution? A short tip here would help you and many other users who saw this issue last week.

    Users with the same issue

    2 times, 5 months ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 1 year ago
    Unknown user
    Once, 11 months ago
    2 more bugmates