Can Workspace Mechanic be configured to load certain rules only if a given plugin or feature is installed?
For example, we have both Java and C++ developers. As it stands today, you get the option to follow both Java AND C++ guidelines in the workspace popup. Can Workspace Mechanic check if JDT and/or CDT are installed?
I do not think Workspace Mechnanic supports this out of the box. However, as it provides extension points, you may be able to build your own plugin to reach your goal. I did it once, but had to use a fragment to access internal capabilities not to reinvent the wheel.
Related
I'm starting development using OSGi but when one of my concerns is about the lack of support at development time, meaning that commonly IDEs (started using Intellij IDEA) don't use OSGi for class discovery but classpath search IDE managed (I'm in search for one that uses OSGi instead).
The main concern here is to prevent classpath issues at execution time by suing the same OSGi mechanisms at development time.
Does any IDE work this way ?
update: added link to blog post with my experience with IDEA
OSGi is a runtime technology, therefore there is no such thing as an OSGi mechanism at build time. Also bear in mind that ultimately all Java code must be compiled by a Java compiler, usually javac. The javac compiler does not use package dependencies like Import-Package, it always uses JARs or directories on the classpath.
Having said that, Bndtools uses package filtering at build time, based on the exported and private packages of the dependencies. This is a special feature of Eclipse and it does not work when you compile outside of the IDE, e.g. with Ant or Maven. However it may still be useful because if you try to use a non-exported package from another bundle you will get a problem marker with a red X in the Eclipse IDE.
IBM has this big 200+ Mb Eclipse plugin where I'm given access to everything and all functionality of Eclipse.
Is there a smaller more lightweight Eclipse plugin available that just gives access to the information a developer needs. Basically just a list of the workitems assigned to me or my team.
Yes, I can configure the big existing IBM plugin to just display that info, but then I'd still have this massive behemoth installed in my Eclipse.
I am aware of Tasktop Dev that allows me to import the workitems into my mylyn tasklist, but I'm looking for something cheaper.
No, because that plugin would have to manage work items and change sets (the list of versioned files), that is the planning and the source control part.
Plus you would need the EMF - GMF dependencies, part of the 200+ MB bundle, as described in "Tip: Installing the Rational Team Concert client into Eclipse 3.5.x".
Which is basically 75% of what the RTC plugin is (the rest being a link to the JBE: Jazz Build Engine).
i go to eclipse download website
i find Eclipse CDT - a version of eclipse that is standalone
in my standard Eclipse SDK(not cdt)
i can do this:
Help->install new software-> then i get a window popup and ask me to give the url
it looks like this:
so then you can install it
this is a separate standalone Eclipse CDT :
this is a standalone Eclipse SDK:
my question is:
1.what is the difference between separate Eclipse CDT and installing CDT plugin onto Eclipse SDK OR are they same thing?
2. what is better? is it better to use a separate Eclipse CDT or just install a plugin inside my Eclipse SDK?
thanks in advance!
Short answer: there is no important difference[1] between the two.
Longer answer: The Eclipse IDE is nothing more than a bunch of plugins that work together to create the functionality for code editing (and other things).
When you go to http://eclipse.org/downloads, you'll see a bunch of different packages. Each package provides a certain set of features, but this is no more than a convenience so that you don't have to install the vanilla SDK and then install the stuff that you really need on top of that. The php dev will not need the C++ compiler and vice-versa. But, you can install it if you want. At it's core, the same small set of plugins are re-used between all distributions.
You can compare the different distributions here: http://www.eclipse.org/downloads/compare.php
[1]: Actually, the difference is that the SDK includes source code for all features as well as the Java compiler and plugin development tools. The C++ tools do not include these.
I'm using Intellij IDEA IDE. Instead of using it's internal build and dependency management tools I prefer external tools (ant+ivy if it matters). I want IDEA be able somehow catch on the flylibraries that were retrieved by dependency manager, index them and obviously provide ide sugar (code suggesting and so on).
Is there plugin or any other solution?
I don't know about Ivy, but it already works like this with Maven. You should take a look at "IvyIDEA"; its description says.
Detect source/document/jar type ivy artifacts in dependencies and add them as such to the module
I have some basic questions in eclipse plugin development, can anyone give clarification of the following questions,
When should we have to add features in our plugin development ?
What is the difference between feature and plugin.xml ?
Regards
Mathan
As mentioned in this thread:
A plugin is the eclipse "unit of work". An OSGi bundle that supplies a classpath and can contribute to eclipse through extensions.
A fragment points to a host plugin, and anything it provides (classpath, extensions, etc) are "sucked" into the host plugin. A fragment is also a more specialized OSGi bundle.
A feature represents a versioned collection of plugins, and is used for configuration management in eclipse. They can be deployed manually or through the update manager. If you want to deploy through the update manager, then you need to use features to represent your plugins.
So if you want to manage your plugin or plugins through the update manager, a feature is in order.
You can find more in the Eclipse Help:
Feature
Features do not contain any code.
They merely describe a set of plug-ins that provide the function for the feature and information about how to update it.
Features are packaged in a feature archive file and described using a feature manifest file, feature.xml.
Plugin
While features are organized for the purposes of distributing and updating products, plug-ins are organized to facilitate the development of the product function among the product team. The development team determines when to carve up program function into a separate plug-in.
Plug-ins are packaged in a plug-in archive file and described using a plug-in manifest file, plugin.xml.