How is the nopcommerce plug-in loaded in the view?
The ThemeableRazorViewEngine view rewrite engine found no relevant information and Plugins.
It depends on a version:
Plugin controllers in version 3.50 (and above) explicitly retunt a plugin view (copied to a plugin output directory).
In previous versions plugins views were embedded in plugin DLLs. And nopCommerce used embedded view engine
Related
I am using the Vaadin Plug-in for Netbeans version 1.1.0 with NetBeans 8.1 & 8.2 (as shown here. This plugin defaults to using Vaadin 7.5.9 rather than the current version of Vaadin for a new project created by choosing File > New Project > Categories (list) > Vaadin > Projects (list) > Vaadin Multi Module Project.
How does one change the Vaadin version from 7.5.9 to 7.7.3 (the latest)?
By context-clicking on the “…-ui” module in the Projects navigator in NetBeans, I accessed the Properties > Project Properties > Categories (list) > Vaadin (list item) > Vaadin Version pop-up menu.
This seemed to work. But when I do a clean-and-build on the …-parent module, I still see line items for Vaadin version 7.5.9 in the NetBeans console output.
So what is the proper way to get a Vaadin multi-module project in NetBeans 8 to use a later version of Vaadin?
You are right. Something is broken with latest Vaadin version support for projects.
Version 7.5.9 used to be the latest available version when the NetBeans plugin has been built. To be able to support latest stable versions plugin reads some URL from vaadin.com site and uses versions from there.
But apparently this is broken. New projects are created with old version.
Could you please create a ticket for that here https://github.com/vaadin/netbeans-plugin/issues ? Thanks a lot.
We are working currently on Vaadin version 8.0 and soon we will have to release new NetBeans plugin version to support it. So this issue might be fixed in this update.
Multimodule project support is not completely implemented unfortunately. That's why version is not correctly updated via project settings.
You can create an issue about this as well (though I think I already made it in our old tracker https://dev.vaadin.com/).
But back to your issue: you can fix it via editing POM file manually.
Please open POM.xml file in your root parent project and find
<properties>
section.
There is <vaadin.version>7.5.9</vaadin.version> string. Just replace 7.5.9 with required version.
Thanks and sorry for inconvenience.
i am making a java application using eclipse RCP.
i have build the project modules as separate plugin projects, now i want to link them using a main plugin project where i have the menu.i don't know how to add plugin projects to the main one.
Can anyone help me please, how to add them and make connecting the views possible ?
I am using eclipse 4 application platform for building custom ide like app, but i am still not sure what libraries i can use.
For instance i can't find some API which is responsible for maintaining projects.
Is it even possible to create project or this is just part specific for eclipse as IDE and can't be used if i am using e4 rcp?
The org.eclipse.e4.rcp, org.eclipse.emf.core and org.eclipse.emf.ecore Eclipse features list all the plugins that a pure e4 application uses.
The list includes most of the org.eclipse.core.xxx plugins but not the org.eclipse.core.resources plugin which contains the workspace code (things like IFile and IWorkspace).
So if you want projects and workspaces you would have to write you own code for that - which would not be compatible with any other Eclipse 3.x plugins.
I just installed NetBeans on my local system. I want to create a Web application but when I click on File->New Project-> The dialogue box that pops up does not give a Web option (I know one exists because I've seen it in text books). Instead I see Java, Maven, NetBeans Modules as my options. Is there a plug in that I need so that the Web option appears?
Thank you,
Elliott
It seems that you didn't download the correct download bundle.
The NetBeans download page shows an overview of all available bundles. From your description it seems that you have the JavaSE package. But you will need the JavaEE package.
As stated on the same page you can add modules:
You can add or remove packs later
using the IDE's Plugin Manager (Tools
| Plugins).
I am developing an eclipse plugin which contains a specific version of Lucene. I need to generate a search index and deploy it so that it can be read by another application which uses the same version of Lucene.
I recently upgraded eclipse to 3.4 and the search index is now not readable by the 2nd application. I see that eclipse 3.4 contains a newer version of Lucene and I am assuming that this version is used when generating the index.
How can I determine exactly which version of Lucene is being used at the time the index is generated? My plugin classpath begins with my bundled version of Lucene so I would have expected that my version should get priority.
TIA
You might want to give ClassPath Checker and ClassPath Helper a try.
You may be able that way to ascertain precisely what jar are used in your development environment, in order to compare those with jars present in your deployment environment, where Luce generates the index.
ClasPath Checker jar conflicts:
Classpath Helper Blocked (Obscured) Classes view:
Seems to work now. For those of you who are interested, this is what I had to do:
Removed the Lucene 1.4.3 jar from my plugin
Copied the old Lucene plugin from an older version of eclipse into version 3.4.
Deleted all the dependencies in the plugin.xml wizard. Now all the Lucene plugins are visible.
Selected version 1.4.xx and changed the properties to set a max version up to 1.5
Added the other plugin dependencies
Changed build path: removed old jar, added plugin dependency Lucene 1.4.3
Recalculated Run configuration. The Lucene 1.4.3 plugin was not added automatically so added it by hand.
Now when the index is generated, version 1.4.3 is loaded.
Hope this is useful to someone.
Since you're developing an Eclipse plug-in you should look into OSGi. Eclipse plug-ins are instances of OSGi bundles and OSGi has a strong model for handling dependencies and versioning between bundles.
I don't know your specific code, but if was planning to use Lucene in my plug-in I'd use OSGi's 'Import-Package' or 'Require-Bundle' functionality to express the dependency; I would not include the Lucene JAR in my plug-in. If every plug-in included their own Lucene JAR, you'd waste space, but more importantly, end up with incompatible versions (like you have).
OSGI's website is not the best place to start your OSGi journey (it's good for the OSGi specifications and Peter Kriens' blog). Better to start with something like Neil Bartlett's online book.