Running custom source scanners on the server
![]()
Hi guys,
I made a source code scanner the way described in https://jazz.net/wiki/bin/view/Main/ExtendDependencyParser using a similar way as I'd make an Advisor/Participant. I also put it on the server in the same way (Made the plugin, put it in a feature, then put it in a site, then built the site, and put it in the server with a reference to the feature and file in a .ini file in the server conf, then reset ccm and restarted the server)
The building of the plugin works perfectly. The problem I have however, is that the custom source code scanner doesn't show up in the source code scanners when trying to link it to a
language definition.
Am I missing something here, or doing something wrong?
Thanks,
Kristof
|
Accepted answer
![]()
Hi Kristof,
Here are the steps we used in the lab to test the scanner extension mechanism. Can you compare them and see if your procedure is the same or the equivalent? If it differs you may want to use these steps to see if it resolves your problem. From the Eclipse client: 1. Create a feature project and add the plugin to the feature.xml. 2. Create an update site project and add the feature to the site.xml. It's better to use the UI to add the feature instead of modifying the site.xml manually. 3. Open the site.xml and click on Build All. 4. Verify that your feature and plugin are generated in the update site project. 5. Export this update site project to a zip file. On the Server: 1. Go to the Admin Console and reset the server so it will reprovision on next restart. 2. Copy and extract the zip file to the <install_dir>/server/conf/ccm/sites directory. 3. Verify that in the <install_dir>/server/conf/ccm/sites directory, you have a new directory that have the following folders and files: features, plugins, site.xml. 4. Go to <install_dir>/server/conf/ccm/provision_profiles directory. 5. Make a copy of any existing ini file. 6. Edit the new ini file and change the url to point to the directory directory, and the featureid to your feature. 7. Restart the server. Kristof Van Sever selected this answer as the correct answer
Comments Hi Daniel
This is what I did, except that I put the feature folder in <install_dir>/server and had the .ini on
url=file:../PHPScanner
featureid=PHPScannerFeature
Hi Kristof,
Hi Daniel,
I made a new Plugin, exactly following the deployment the way you explained it and making sure the plugin.xml was there. It however still does not appear in the list. I uploaded a zip of the plugin's export to https://www.dropbox.com/s/jh53ffvuwuxvcvt/TestPHPScanner.zip if you'd be so kind to take a look at it
Thanks,
Kristof
Hi Kristof,
Hi Daniel,
I changed the namespace (and added the label, which I had forgotten) and it ended up in the list! So this little "hello world" works now (apart from an Unhandled event loop exception that appears in the Eclipse error log when adding the Scanner to the language definition.
Thanks a bunch for your repeated help, it's very, very, very appreciated!
|