| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| Broker Toolkit 7.0.0.4 - No Deploy Option |
« View previous topic :: View next topic » |
| Author |
Message
|
| Vitor |
 Posted: Wed May 23, 2012 7:35 am Post subject: |
 |
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| lancelotlinc wrote: |
| I like you too Vitor. |
Too?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
 |
| alienartefact |
| Posted: Thu May 24, 2012 12:12 am Post subject: |
|
|
Novice
Joined: 23 May 2012
Posts: 13
Location: East Midlands, UK
|
Thank you all for you assistance. The syntax checking problem also seems to have been resolved by checking out from SVN at the msgflows level rather than at the trunk. I also notice that doing this correctly splits the Project view in my workspace into Flows and ESQLs, whereas previously they were all lumped together.
Vitor - I'm sure you must be right in that I should be able to check out at a higher level and still get a valid project. I will have to experiment with doing this when I get some time. If I discover anything useful I will post it here.
Thanks again all. |
|
| Back to top |
|
|
| Vitor |
| Posted: Thu May 24, 2012 4:56 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| alienartefact wrote: |
| Thank you all for you assistance. The syntax checking problem also seems to have been resolved by checking out from SVN at the msgflows level rather than at the trunk. I also notice that doing this correctly splits the Project view in my workspace into Flows and ESQLs, whereas previously they were all lumped together. |
So previously they didn't look like a WMB project? Which could have led to the Toolkit thinking they weren't a WMB project (with no .project file) and hence the belief that wasn't ESQL under a valid broker namespace that needed to be syntax checked?
| alienartefact wrote: |
| I'm sure you must be right in that I should be able to check out at a higher level and still get a valid project. I will have to experiment with doing this when I get some time. If I discover anything useful I will post it here. |
This is certainly not my area of excellence, but I observe that our SVN repository (like all in my recollection) doesn't have .......\msgflows & ......\ESQL branches. The lowest branch is the project, so it's trunk\PRODUCT\PROJECT with the .project & other files under that.
This may be significant. Or not.
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mqjeff |
| Posted: Thu May 24, 2012 5:07 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
The folders that contain the .project have to all be root children of the folder that is identified as the workspace.
This has nothing to do with the structure of the repository in SVN or any other source control system.
It simply and only has to do with the structure that is created when you check things out, and then the location within that structure that you identify as the workspace root.
So if you check out something like
/REPOSITORY
//TRUNK
///PRODUCT
And PRODUCT on disk then looks like
/PRODUCT
//RELEASE
///DOC
///CODE
////Project1
////Project2
////....
///RESOURCES
And Project1, Project2, etc. are all Eclipse projects with .project files as children.
Then you can point the Toolkit at PRODUCT/RELEASE/CODE as the workspace root and it should work. But if you point Toolkit at PRODUCT/RELEASE, it won't work, and if you point Toolkit at PRODUCT/RELEASE/CODE/Project1 then it won't work either.
Or you can check out /REPOSTITORY/TRUNK/PRODUCT/RELEASE/CODE into
/workspace on disk
then you can just point the Toolkit at /workspace
The above is if you are NOT using Toolkit itself to check out individual projects and link them with SVN, but are rather using something else to check files in and out.
If you ARE using Toolkit itself, it will automatically put things at the right place relative to the workspace root, but then you have to make sure to check out the right thing - the individual projects rather than anything else. And again, it doesn't matter where in the source control path the projects are, you just have to check them out individually. |
|
| Back to top |
|
|
| alienartefact |
| Posted: Wed May 30, 2012 7:16 am Post subject: |
|
|
Novice
Joined: 23 May 2012
Posts: 13
Location: East Midlands, UK
|
| mqjeff - thanks very much for the addional info. It is starting to make sense now. |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
