I have a 3rd party Android/java (aar file) library provided by 3rd party vendor.
I want to include it in my Gluon Netbeans development environment; and package/deploy (when target set to Android) in the final apk.
BTW - the vendor has an analogous library for IOS, and Linux (respectively). The intent is to house the libraries in the Netbeans project; and package and deploy as appropriate based on the selected target.
Is there an approach to making this work using the Netbeans based Gluon project structure?
Related
Several teams in our company use internal framework to build an Eclipse UI. This framework is composed of set of Eclipse plugins.
Our team is responsible for the develpment of this framework and we're looking for some tools that would check API breakage in the further versions of our framework.
For example, we have the following class:
package com.foo.A;
class A {
public void doSmth() {}
}
Currently in MANIFEST we and users of our plugins do not specify any versions of plugin's dependencies (always complining with the latest version).
We'd like to have some warnings from Eclipse if we change something in this class, e.g. change method signature or something else. We'd like Eclipse to suggest us to rise plugin's version in such cases.
I've read the following information about API tooling in Eclipse:
https://wiki.eclipse.org/PDE/API_Tools/User_Guide
But it seems to me that this tooling works only with Eclipse native plugins, but not with our custom developed ones.
If I'm mistaken, could anyone be so kind to explain me how to setup API tooling for our plugins?
the Eclipse API tooling works also with user bundles. What you should do is take your released framework and define it as baseline. A quick solution is to copy all your build and released to the public bundles in a folder and set the folder as Baseline:
Window - Preferences - Plug-in Development - API Baselines - [Add Baseline...]
You can have multiple Baselines if you have to patch older release versions of the framework for example. Be sure to set your API Errors/Warnings as you reqire them.
Edit: Of course you should enable API Tooling in all your bundles as described in "Configure Bundles for API Tooling" in the web page you linked!
Background
In my RCP application, I have a project that consists of a plugin and a feature, the setup is like this:
my.plugin/
META-INF/MANIFEST.MF
plugin.xml
src/
my.feature/
feature.xml
The plugin contains unversioned dependencies towards other bundles (in other features). The feature contains versioned dependencies towards other features.
In the end, I will build a RCP application as a feature-based product.
All feature dependencies can be found in a p2 repo hosted by a Nexus server (over HTTP).
Problem
The above can be built fine using Tycho and the manifest-first approach. Tycho picks up the correct target platform based on the versioned feature dependencies.
When developing, I would like to create a target platform given the specified features by reading the feature versions, so that I know that development is being done against a target platform that is compatible with the specified set of features.
What is a good way to create a target platform based on this feature dependency specification? Ideally, I think I would just like to generate the target platform automatically using the latest compatible versions, just like Tycho does.
I've used the Google Guava library for a half year now inside some small Eclipse RCP applications. Until now it's worked well with the older versions of Guava 11/12 provided inside the Eclipse Orbit p2 repositories.
In a new project I need to use Base64 encoding, but this feature only exists in Guava since version 14, which is not available inside Eclipse orbit.
I know that there is an alternative within the Apache commons, but I want to have minimal dependencies to other bundles.
I also know the bundle itself is OSGi compatible, but the classic RCP build based on features and it is a good practice to define a feature based target platform.
So does somebody know an (official) p2 repository that includes the latest guava version, or do I need to build my own feature based on the library?
I've been beating my head against a wall for about 6 months now and have not found a concise way of understanding the mechanism for developing an eclipse plugin with third-party resources.
We are attempting to develop an Eclipse ODA to ride on top of in-house Spring-based code that accesses a REST based info set.
In broad strokes - this is what I feel that we need to be able to do:
Augment our maven artifacts with Eclipse bundle information using tycho or a the felix bundle plugin.
Set up a plugin project through Eclipse for the ODA Implementation & UI.
Have Tycho generate the poms etc for the plugin.
Now here's where I get muddy. I understand that there are two approaches
Manifest-First - which is the standard mechanism for defining a plugin's dependencies
POM-First - which provides dependencies via Maven's resolution mechanisms.
I'm not entirely sure where to begin trying to start doing this as I've never worked on developing an eclipse plugin.
One of the other questions I have is, how does a developer of an eclipse plugin (maven aside) leverage already existing third-party code (i.e. Apache HttpClient 4.x)? Do they have to download the jars, dump them into a directory within the project, add to classpath, then go from there or is there a "repository" mechanism similar to what is used with ivy, maven, gradle?
Thanks in advance and I apologize if I was rambling a bit with that.
Disclaimer: Your question is very broad, so it is impossible to answer it completely. Still, I can give you some hints so that you know what to search for.
In the Eclipse universe, the primary source for libraries (in the sense of binary dependencies) are p2 repositories. However, since p2 repositories are rarely used outside of the Eclipse context, you won't e.g. find a p2 repository on the Apache HTTP Client project's download page.
To account for this problem, there is the Eclipse Orbit Project which provides libraries used by Eclipse projects in p2 repositories.
If you can't find the library or library version in the Eclipse Orbit, you may also be able to use the libraries from Maven repositories. This is for example supported by Tycho via the pomDependencies=consider mechanism.
Note however that Eclipse plug-ins can only depend on libraries which are OSGi bundles. So if the library in the Maven repository is not yet an OSGi bundle, you need to convert it to an OSGi bundle first, e.g. with the maven-bundle-plugin and the Embed-Dependency mechanism.
The best way for an Eclipse plugin to consume libraries is as OSGi bundles. You just install those bundles into your target platform and reference them in the same way as eclipse.org plugins. Some of the library providers already offer their libraries as OSGi bundles. Absent that, you can typically turn a plain library jar into an OSGi bundle simply by adding a few manifest entries.
Depending on the build system you use and whether the libraries you need are available as OSGi bundles packaged into an online p2 repository, you can reference the URL and rely on your build to download and install the bundle.
If question of choosing a build system for Eclipse plugins with dependencies is still relevant:
Today I released new gradle plugin: Wuff version 0.0.1, which (I think) completely solves the problem. It allows to build Eclipse bundles and applications as they would be "normal" Gradle projects. All OSGi woodoo is auto-generated (although customizable). All dependencies are usual maven dependencies - regardless of whether dependency is OSGi or "normal" library.
Sources and doc: https://github.com/akhikhl/wuff
I created a GWT application in eclipse using the GWT eclipse plugin. By default it created GreetingServiceAsync.java and GreetingService.java in client package. GreetingServiceImpl.java in server package.
Now I want to call a CXF webservice from GreetingServiceImpl.java. I used wsdl2java to generate java classes for my wsdl. I imported these generated class in my GWT project in eclipse and the package is "service". But it complains "javax.jws.WebMethod is not supported by Google App Engine's Java runtime environment", many more errors.
How do I get rid of this?
Only error is the problem otherwise application is running fine.
Is javax.jws.WebMethod in the GAE whitelist? If you're sure that this class is really supported in the App Engine, then in Eclipse try:
Right click your project in the Project Explorer.
Google -> App Engine Settings
Make sure Use Google App Engine is checked
Try changing the App Engine SDK to the latest rev, if the dialog shows multiple ones
I had this problem after doing Software Update; a new GAE SDK was installed and for some reason it confused the plugin. It was telling me that java.lang.String was unsupported. :-)