John Ormerod 11.Jun.07 05:56 AM a Web browser Toolkit 6.1 All platforms
I have a very strange situation, which I will do my best to describe.
I discovered during a long-running POC that you can have multiple portlets within a single portlet project. I am now at a point where I am redesigning and refactoring the POC code in prep for doing it 'properly'. Since most portlets use the same html themes, css files etc, it makes sense to put these into a single project.
I am rebuilding the code by a gradual process of exporting projects from the POC workspace as Project Interchange files, and importing into the new workspace.
I have already merged a couple of portlets into my 'portlets' project. However, I now have one that refuses to go!
This is the 'clockin' portlet. I have moved the code, jsps etc to the 'portlets' project; added the <portlet> def in portlet.xml. What is different is that is has dependencies on 3 of my other projects. I have added these to the Required Plug-ins section of the 'portlets' project's plugin.xml (exactly as for the clockin portlet itself).
The problem is that the 'portlets' project refuses to 'see' the dependent projects. If I look in the Build Path under Plug-in Dependencies, the dependent projects do not show up - just the one of mine that had always been there.
If I look at this in the clockin portlet project, then all of the dependent projects can be seen.
This doesn't make any sense to me. Can anyone suggest what might be causing this block?