Plugin with out plugin.xm or metainf.mf - eclipse-plugin

Is it possible to have a Eclipse plugin without plugin.xml or metainf.mf file ?

It might not need a plugin.xml, but a plug-in absolutely needs the MANIFEST.MF.

Related

Why Intellij Idea cannot generate a maven plugin?

In this picture, I set up a plugin tag in pom.xml in order to use the mybatis-generator-maven-plugin but unfortunately there isn't a plugin in maven projects on the right side. I wanna know what's the problem?
The mybatis-generator <plugin/> should be put outside the <pluginManagement/>.
Here's the reference question: Maven: What is pluginManagement?

How to add dependent jars to deploying plug-in

I would to like to add the dependent jars to the update site plugin project in Eclipse.
I followed
http://wiki.eclipse.org/FAQ_How_do_I_create_an_update_site_%28site.xml%29%3F
but, it does not address the above issue. How to deal with the dependent jars with deploying plugin? Anybody please help with ideas.
Thanks
I'm going to assume you are wanting to add additional Jar files to your plugin. You can do this by simply putting the Jar files into the top level directory of your plugin, and in the Classpath portion of the Runtime tab in the Plugin Manifest Editor you can specify the Jar file. This will automatically add it to the build path as well.
Some people prefer to make an extra plugin that contains nothing but external Jar files; you add the Jar files to this extra plugin the same way and then just use the Dependencies tab in the Plugin Manifest Editor to make your original plugin dependent on the Jar plugin.

Avoid javadoc and sources downloading, when using Maven ant Tasks

I'm developing with Maven Ant Tasks support. When asking the repository to download desired libraries, it also downloads javadoc and source for each library. Is there a way to only download library jars?
Actual build.xml:
<artifact:dependencies settingsFile="${maven.settingsFile}" pomRefId="projectPom"
filesetId="dependency.fileset"
sourcesFilesetId="sources.dependency.fileset"
javadocFilesetId="javadoc.dependency.fileset"
versionsId="dependency.versions">
<remoteRepository refid="remote.repository" />
</artifact:dependencies>
As far as I know the src and javadoc downloads are off by default. There should be an option in your IDE or whatever tool you use for Maven.
Are your working with Eclipse?
In Eclipse you can find the option here:
Window > Preferences > Maven
Then tick the checkboxes (or rather untick them) 'Download Artifact Sources/JavaDoc'.
That's strange. Most open source Maven modules don't have source and javadoc on the default "compile" Maven scope. Have you tried specifying a scope?
<artifact:dependencies filesetId="dependency.fileset" useScope="compile">
..
Alternatively you can also specify a "scope" attribute on each dependency.
Personally I use the ivy plugin for my Maven downloads. The same problem is solved by specifying the "default" or "compile" configuration mapping: ivy: prevent downloading sources and .txt files
Finally solved: just remove sourcesFilesetId and javadocFilesetId attributes if you don't need sources and javadoc jar libraries.

pax-run using Maven Plugin in pom.xml

How can I execute Pax-Runner tasks using a Maven Plugin, which I can specify in the pom.xml file?
i.e. I can do the following in command line using Pax-Runner (to convert a war file into an OSGi bundle)
pax-run war:file:C:/somefile.war warref:C:/somefile.properties
What should I do to make it happen in a pom.xml file?
Thanks in advance!
There is a maven plugin for pax. I've not used it, but according to the documentation it does what you need. On the usage page there's a section titled Using the Pax Plugin inside a POM that describes how to set up your project.

How do I force an Eclipse plug-in to be unpacked?

My eclipse plug-in must be unpacked.
How can I enforce the installer to unpack it?
Will it be unpacked if the jar file is simply dropped into the plugins folder?
This can be chosen when configuring the feature including the plugin. Go to the plugin list, select your plugin and check "Unpack the plug-in archive after installation".
Arguably, this property should be defined by the plugin itself. There's a bug report about that https://bugs.eclipse.org/bugs/show_bug.cgi?id=157562
regards,
Vlad
You can set the Eclipse-BundleShape value in your MANIFEST.MF file to either jar (the default) or dir. If set to dir, it is deploy unpacked.
Eclipse-BundleShape: dir
http://eclipsesource.com/blogs/2009/01/20/tip-eclipse-bundleshape