| Preventing double bundle start when developing plan in Eclipse tooling [message #722585] |
Tue, 06 September 2011 09:30  |
 Alexey Romanov
Messages: 263
Registered: May 2010 |
Senior Member |
|
|
Sorry for so many questions, still trying to figure things out 
According to Programmer Guide 4.3,
Quote:
Plans always get their dependencies from the VTS repository.
So if I place my plan into /pickup or deploy it into /stage from tooling, but don't add bundles to server in tooling, they aren't added to /stage, the plan can't find them and doesn't start. This is expected. However, if I do add bundles to server, they are deployed to /stage and there are two attempts to start them: from plan and from stage. How can I prevent this?
One obvious solution is to export bundles after every change and place them in /repository/usr. But this both increases turnaround time a lot and runs into my MANIFEST.MF export problem.
[Updated on: Tue, 06 September 2011 09:35] Report message to a moderator |
|
|
| Re: Preventing double bundle start when developing plan in Eclipse tooling [message #722655 is a reply to message #722585] |
Tue, 06 September 2011 12:40  |
|
Hi,
You should not manually place the bundles in /stage, you should not be using it yourself at all. If you place the bundles in one of the repositories you will get the behaviour you are after. /repository/ext or /repository/usr. I believe if the tooling is set up right it will actually do this for you as well but I don't remember the details. I think it needs to know that projects in the workspace are a part of the plan your deploying.
Chris.
------------------------------------------------
Chris Frost, Twitter @cgfrost
Springsource, a divison of VMware.
|
|
|
|
Powered by
FUDForum. Page generated in 0.02000 seconds
Search
Help
Register
Login
Home
