Hello, I use maven as build-tool and need many not mavenized equinox-bundles in an internal project (gmf, ...). Upgrading to a new version of this set of bundles is much stupid work.
struberg wrote: > > Peter, just out of curiosity: How do you decide which groupId, artifactId > and versionId you should > take for each jar? > You 'r right, the separation, of what is groupId and what is artifactId is not included in the manifest-file. For me, I decided to use the whole "Bundle-SymbolicName" for both. "Bundle-Version" is used for the maven-version. The greater problem is the dependency-version. For this, I have to deploy all needed jars together, so that the version of the previously parsed manifest-file of the needed jar is used. I know that this is not the best solution, but for the moment it works. But I don't know, if someone else would be interested in using this hack... regards, Peter -- View this message in context: http://www.nabble.com/own-plugin-without-need-for-pom.xml-tp14318109s177p14337471.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
