Re: maven-eclipse-plugin: pde support and OSGiManifest writer
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 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. I realise that not every use of the plugin is going to be on the user list - but it can give a gauge of sentiment. Opinions welcome. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin: pde support and OSGiManifest writer
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: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin: pde support and OSGiManifest writer
+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, Barrie Treloarbaerr...@gmail.com wrote: 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. I realise that not every use of the plugin is going to be on the user list - but it can give a gauge of sentiment. Opinions welcome. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- John Casey Developer, PMC Chair - Apache Maven (http://maven.apache.org) Blog: http://www.johnofalltrades.name/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin: pde support and OSGiManifest writer
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 maven dependencies but not both. Thanks, Steve C On 23/09/2011, at 4:01 PM, Barrie Treloar wrote: 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. I realise that not every use of the plugin is going to be on the user list - but it can give a gauge of sentiment. Opinions welcome. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin: pde support and OSGiManifest writer
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 arrangement. On the surface it looks like you're either using p2 dependencies or maven dependencies but not both. I don't suppose you have some documentation that describes your setup? For the RCP application I was building we used (the now defunct) org.codehaus.mojo:pde-maven-plugin. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin: pde support and OSGiManifest writer
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
/extension
/extensions
plugins
!-- configure the bundle plugin executed as part of the bundle
packaging type --
!-- generate an OSGI manifest --
plugin
groupIdorg.apache.felix/groupId
artifactIdmaven-bundle-plugin/artifactId
extensionstrue/extensions
configuration
manifestLocationMETA-INF/manifestLocation
instructions
_nousestrue/_nouses
Bundle-SymbolicNamecom.foobar.platform.rules.deployer.config;singleton:=true/Bundle-SymbolicName
Bundle-NameFoobar Deployer Configuration/Bundle-Name
Bundle-RequiredExecutionEnvironmentJavaSE-1.6/Bundle-RequiredExecutionEnvironment
Bundle-DocURL /
Import-Package!*/Import-Package
Private-Packagecom.foobar.platform.rules.deployer.config.*/Private-Package
Export-Package /
Bundle-Activatorcom.foobar.platform.rules.deployer.config.plugin.DeployerConfigPlugin/Bundle-Activator
Bundle-ActivationPolicylazy/Bundle-ActivationPolicy
Embed-Dependency*;scope=compile|runtime;inline=false/Embed-Dependency
Embed-Transitivetrue/Embed-Transitive
Include-Resourceplugin.xml,src/main/resources/Include-Resource
Bundle-ClassPath.,{maven-dependencies}/Bundle-ClassPath
Require-Bundleorg.eclipse.core.runtime,org.eclipse.ui,com.foobar.core,com.foobar.core.deployer.rc.config,com.axegroup.rcp.plugins.log4j,org.apache.commons.lang/Require-Bundle
Eclipse-RegisterBuddycom.foobar.core,com.axegroup.rcp.plugins.log4j/Eclipse-RegisterBuddy
/instructions
/configuration
/plugin
!-- Unpack jar dependencies into the target directory so they can
be used by the pde plugin --
plugin
artifactIdmaven-dependency-plugin/artifactId
configuration
excludeTransitivefalse/excludeTransitive
/configuration
executions
execution
idcopy-dependencies/id
goals
goalcopy-dependencies/goal
/goals
configuration
excludeScopeprovided/excludeScope
outputDirectory${basedir}/outputDirectory
overWriteReleasesfalse/overWriteReleases
overWriteSnapshotsfalse/overWriteSnapshots
overWriteIfNewertrue/overWriteIfNewer
/configuration
/execution
/executions
/plugin
!-- clean up all the dependency jars dumped in the plugin root
directory for the pde plugin --
plugin
artifactIdmaven-clean-plugin/artifactId
configuration
filesets
fileset
directory${basedir}/directory
includes
include*.jar/include
/includes
followSymlinksfalse/followSymlinks
/fileset
/filesets
/configuration
/plugin
!-- configuration for the Eclipse IDE --
plugin
artifactIdmaven-eclipse-plugin/artifactId
configuration
pdetrue/pde
useProjectReferencesfalse/useProjectReferences
classpathContainers
classpathContainerorg.eclipse.jdt.launching.JRE_CONTAINER/org.eclipse.jdt.internal.debug.ui.launcher.StandardVMType/JavaSE-1.6/classpathContainer
classpathContainerorg.eclipse.pde.core.requiredPlugins/classpathContainer
/classpathContainers
/configuration
executions
execution
idrun eclipse plugin/id
phaseprepare-package/phase
goals
goalclean/goal
goaleclipse/goal
/goals
/execution
/executions
/plugin
