Results 1 to 6 of 6

Thread: constant "Updating bundle class container for project"

Hybrid View

  1. #1
    Join Date
    Jul 2006
    Posts
    17

    Default constant "Updating bundle class container for project"

    I created a maven project with a couple of modules.
    Module A depends on module B.

    Eclipse keeps going back and forth between "Updating bundle class container for project" A and B. This is with the Spring DM classpath container disabled. I'm only using the maven classpath container.

    If I remove the OSGI Bundle Project Nature, this goes away.

  2. #2
    Join Date
    Jul 2006
    Posts
    17

    Default

    I see that the PDE nature is enabled for the project. Is it supposed to be or not?

  3. #3
    Join Date
    Aug 2004
    Location
    Duesseldorf, Germany
    Posts
    1,210

    Default

    kryptolus,

    the PDE nature should not be enabled on those projects. Would you be able to zip up the projects (or a stripped down version) and attach that to JIRA. I can then try to reproduce this issue.

    Thanks for your effort.

    Christian
    Christian Dupuis
    SpringSource, a division of VMware
    Lead, SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/cdupuis

  4. #4
    Join Date
    Jul 2006
    Posts
    17

    Default

    Quote Originally Posted by Christian Dupuis View Post
    kryptolus,

    the PDE nature should not be enabled on those projects. Would you be able to zip up the projects (or a stripped down version) and attach that to JIRA. I can then try to reproduce this issue.

    Thanks for your effort.

    Christian
    I'll try to disable the PDE nature first and if that doesn't work I'll try to get you the project. I used the spring-osgi-bundle archetype to create the project and I believe I ended up with PDE enabled.

  5. #5
    Join Date
    Aug 2004
    Location
    Duesseldorf, Germany
    Posts
    1,210

    Default

    kryptolus,

    I looked at your sample projects in the meantime and could reproduce and fix the problem. The two projects essentially created a cycle dependency importing each others exports, which was most likely caused by the fact that both projects used the sample internal packages names and exported those projects but also imported them.

    Exporting and importing own packages is very common when using BND or the Felix Maven plugin.

    Anyway I fixed that in the tools and it will be available in the next version.

    Thanks for taking time to file a JIRA.

    STS-57: Constant "updating bundle classpath" between two projects
    https://issuetracker.springsource.com/browse/STS-57

    Christian
    Christian Dupuis
    SpringSource, a division of VMware
    Lead, SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/cdupuis

  6. #6
    Join Date
    Jul 2006
    Posts
    17

    Default

    Thank you

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •