-
Notifications
You must be signed in to change notification settings - Fork 12
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Invalid product id #22
Comments
This is the launch config generated by lcdsl: |
This seems to be a bug in LcDsl indeed. I can reproduce it with /some/ products, but others work. From what I can tell until now there seems to be some shortcut logic that IF the product name contains dots (?), the bundle name is not prefixed to the product name, otherwise it should be prefixed with the bundle name :| You could verify this by renaming your product to just 'product' - it should then be correctly identified both by eclipse and LcDsl as |
Yes I confirm, if the product id is just |
An updated version is available from the update site (caches could take a few minutes). Could you please update and try it? Fixed version is 0.1.2.N201811231318 |
It's working now, the config is valid and I can launch it. But I noticed that I have no more content assist/auto completion for the product names. Also, but it's really a minor thing, it didn't detect automatically that the product used for the launch config needed a feature containing the |
Hi,
I tried to use lcdsl for our RCP application but I encountered an issue.
I this config
launch.lc
:Once the corresponding launch configuration is generated I check it and the select product is invalid.
![image](https://user-images.githubusercontent.com/6960133/48931846-6dd75800-ef33-11e8-82f0-2b3e8e4e1af1.png)
If I do it manually it would be:
![image](https://user-images.githubusercontent.com/6960133/48931854-8182be80-ef33-11e8-901a-3ac38cabe33f.png)
The
plugin.xml
inio.toro.coder.branding
looks like this:Am I doing something wrong or is it an issue on lcdsl side?
The text was updated successfully, but these errors were encountered: