I'm currently in a desperate situation right now, I already tried dropping the JAR file into both the "plugins" folder I created inside the "dropins" directory and also into the other "plugins" folder that was already created. I add the "-clean" option into the target of the eclipse shortcut and then I start eclipse. I go to the "plug-ins" section and try searching my plugin, but it does not appear.
I am using Eclipse Jee Neon and this is the JAR plugin I am attempting to use. Can anyone help me resolve this?
https://mvnrepository.com/artifact/org.codehaus.mojo/exec-maven-plugin/1.5.0
Related
I have a web source code includes two folders: META-INF and WEB-INF directory is structured as:
WhatJobs
|META-INF
|WEB-INF
|application
|classes
|framework
|lib
|resources
|web.xml
how I can load project in NetBean. Please help me.
Netbeans will need project property file by reading which, netbeans will be able to understand what type of project is. So either netbeans will check for the nbproject folder where in project.properties file will reside or it should be eclipse project where in netbeans can read eclipse project property file.
Your provided structure will not work.
If you want your project in netbeans, then you can create new project and copy paste files according to your requirement in that new project.
If I have a Maven project, and someone is going to load the project by opening the pom.xml file in IntelliJ, is there anything I can put in the file or elsewhere in the project that will load project-specific coding styles into the IDE?
Not by importing from a pom only. What you can do is add some IntelliJ files to the source code management tool. Idea saves its project specific code styles into /.idea/codeStyleSettings.xml - it may just picks it up after you imported the project via maven/pom.xml. I think it does not hurt to add a few other files too. Here is my .gitignore for intellij 13.1.5:
target/
# intellij settings files:
.idea/artifacts/
.idea/dictionaries/
.idea/copyright/
.idea/inspectionProfiles
.idea/libraries/
.idea/scopes/
.idea/compiler.xml
.idea/uiDesigner.xml
.idea/vcs.xml
.idea/rebel_project.xml
.idea/dataSources.ids
.idea/workspace.xml
Everything else is under version control. (some developers dont like that - I know - just wanted to mention it)
I need to make some modifications to the Subclipse Eclipse svn plugin. To do so, I need to connect to a specific Oracle database, but my code keeps dying on this line:
Class.forName("oracle.jdbc.OracleDriver");
With (surprise) :
ClassNotFoundException
I've added the ojdbc.jar to the build path of my project
(org.tigris.subversion.subclipse.core, the project that tries to connect to the database)
This works fine in a regular project, just not with the Subclipse plugin, so it's not being deployed I guess.
I do have it checked in this menu:
Configure Build Path -> Order and Export
Any idea what I'm doing wrong?
Copy the jar to the plugin directory.
Open the file "META-INF/MANIFEST.MF" in the plugin project directory, switch to
the "runtime" tab, and then click "add" button the the "class-path"
section to select the driver jar file.
I received a new version of a plugin of a project I work in collaboration with other people.I copied it over the old version in the /plugin directory. Eclispe (3.7.2 on Win7) ignored the plugin (don’t show up in the Help/About Eclipse/Installed Plugins). I put the old version back (I put an “_old” at the end of the .jar file) and it worked again but the plugin’s command in the menu appeared with a “%” character at the beginning. After some more copying of old/new version in the /plugin directory, even the old plugin won’t install. I put back an acient original version of the plugin, but still not working. It just stop suddenly working. I checked my permissions on the /plugin directory, started Eclipse as an administrator, but no success.
Thanks.
First of all you should put both versions in plugins directory only if they have different versions in plugin.xml definitions but even in this case only one of them probably will be active i.e. will add its contributions to Eclipse. You should use copy/paste actions to provide additionals to Eclipse carefully, plugins and features directories are not supposed for manual usage. To manage your plugins easily follow the dropins directory usage. For now the best you can do is to remove all versions of your custom plugin and run Eclipse to the clean workbench.
Using NetBeans 7.1.2.
When editing pages with NetBeans as per the procedure explained below, the IDE offers only autocompletion for <jsp:...> tags:
This is how I have created the NetBeans project and the jsp (though it isn't archetype specific, nor the issue has anything to do with opencms): I have created a maven project with the OpenCms-Module archetype
mvn archetype:generate -DarchetypeCatalog=http://bp-cms-commons.sourceforge.net/m2repo
The archetype creates a maven project with jar packaging.
After that, I have added a jsp under src/main/opencms/modules/blahblah/templates.
And then I have added the taglibs.standard dependency to the project, to try to provide NetBeans with the corresponding tlds.
After several hours trying to get this working, I found this reported and closed bug that hinted me into the right direction:
Added src/main/webapp directory Edit 1: There is autocompletion only for jstl tags if the files are inside src/main/webapp. Workaround in linux (not sure if windows links will work): Create a symlink:
ln -s opencms/ src/main/webapp from the project root folder
Change maven project packaging to war (Project properties -> General -> Packaging)
(Notice that neither the #taglib directive nor the taglibs.standard dependency are necessary.)
If the Web Pages entry does not appear under your project (in the projects view), you may need to restart NetBeans. Now you'll have full autocompletion (only) under src/main/webapp! :-)
Edit 2
Unfortunately, if under version control, NetBeans sees the symlink as a new directory, and all files under it, as new files :-( This is very inconvenient, because to access the IDE integrated version control functionality, you still need to open the original resource.