>>>>> Steinar Bang <[EMAIL PROTECTED]>: >>>>> Steinar Bang <[EMAIL PROTECTED]>: >> Platform: Intel Pentium M, Ubuntu Dapper, >> Sun Java 2 SDK 1.6.0_06, >> maven 2.0.4, >> maven-eclipse-plugin 2.3
[snip!] >> Ie. there is no plugin nature in .project, and .classpath still refers >> to files directly in the local maven repository. > After the parameter name correction the .project and .classpath looks > correct. But no jars are copied to a project local directory, like > the documentation says it should be. > http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html What happened, was that there was no META-INF/MANIFEST.MF in the project directories, and that I got the following warning [WARNING] The references manifest file doesn't exist, plugin dependencies will not be updated: /media/sda8/bangste/p4/depot/ccr/MAIN/com.fastsearch.ccr.repository.repositorydef/META-INF/MANIFEST.MF I created the META-INF directories, containing empty MANIFEST.MF files, and then had a bit more success. Ie. the jars weren't copied, but they were made <linkedResources> in the .project file (I'm not sure what that means wrt. creating an RCP application containing these plugin projects...?) But, of course, I'm not all there yet. Because right now, I have a bunch of META-INF/MANIFEST.MF files containing nothing but Bundle-Classpath. And I need a bit more to make these projects play as plug-ins. At least: - Bundle-Symbolic-Name - Bundle-Version Possibly: - Export-Package - Import-Package - Bundle-Activator That information is currently residing in the POMs as <manifestEntries> for maven-jar-plugin. Duplicating it manually into the MANIFEST.MF files, seems like a bad idea. Any suggestions for automating this? Thanx! - Steinar --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
