I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.
On Fri, Sep 23, 2011 at 8:01 AM, Barrie Treloar baerr...@gmail.com wrote:
Does anyone actually use pde mode in maven-eclipse-plugin?
The support looks pretty
Carlos Sanchez wrote:
I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.
+1
- Jörg
-
To unsubscribe, e-mail:
+1
Having fewer partial implementations to confuse folks is always better IMO.
On 9/27/11 2:08 AM, Carlos Sanchez wrote:
I guess there wouldn't be any issue removing it adding a warning
pointing to the Felix plugin.
Osgi manifests are better handled there.
On Fri, Sep 23, 2011 at 8:01 AM,
FWIW, we're using pde mode at present.
We have a largish (~ 40 modules) framework that builds both RCP applications
and web applications.
I haven't had a chance to figure out how to integrate Tycho into this
arrangement. On the surface it looks like you're either using p2 dependencies
or
On Wed, Sep 28, 2011 at 11:40 AM, Stephen Coy st...@resolvesw.com wrote:
FWIW, we're using pde mode at present.
We have a largish (~ 40 modules) framework that builds both RCP applications
and web applications.
I haven't had a chance to figure out how to integrate Tycho into this
We're building bundles with the following build configuration:
packagingbundle/packaging
build
extensions
extension
groupIdorg.apache.felix/groupId
artifactIdorg.osgi.core/artifactId
version1.2.0/version
Does anyone actually use pde mode in maven-eclipse-plugin?
The support looks pretty basic and there are other better options like
tycho and felix for doing this stuff.
EclipseOSGiManifestWriter has been deprecated in favour of felix and I
wonder whether its worth keeping the other stuff around.
