Announcement Announcement Module
Collapse
No announcement yet.
Import-Package xxx.xxx could not be resolved Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • Import-Package xxx.xxx could not be resolved

    after updating from nightly ap tool build:

    the following import cannot be resolved:
    Import-Package: ent.jee.isl.entity_srvc;version="[1.0.0.0,1.0.0.0]"

    the following is the corresponding export:
    Export-Package: ent.jee.isl.entity_srvc;version="1.0.0.0"


    btw, com.ge.nbcuni.ent.jee.isl.entity_srvc;version="1.0 .0.0" is in the list when addding dependent packages but, still results in an error

    any suggestions would be appreciated

  • #2
    Import-Package xxx.xxx could not be resolved

    Todd,

    in the recent nightly build we changed the way inter-project export-import dependencies are resolved. Basically there a now to ways of making this work:

    1. Put all depending bundles into a PAR using a PAR project
    2. Use the Project preferences to specify that the importing bundle *can* depends on the exporting bundle (Project Properties -> Project References -> select the project)

    This change was required because some users had multiple projects exporting the same packages and no control over which project would be added to the classpath.

    Hope that helps.

    Christian

    Comment


    • #3
      Import-Package xxx.xxx could not be resolved

      Christian

      I'm trying the second suggestion, but for some reason it does not seem to work. I have added the project to project references, but the bundle/package still cannot be resolved. Any ideas?

      I don't want to go for PAR solution as I need to deploy the bundles independently.

      Jaro

      Comment

      Working...
      X