>>>>> "Tom Huybrechts" <[EMAIL PROTECTED]>: > On 12/16/06, Tom Huybrechts <[EMAIL PROTECTED]> wrote:
>> Maven needs artifacts to be single files, so they should be unpacked later. >> Take a look at this: >> http://maven.apache.org/plugins/maven-eclipse-plugin/install-plugins-mojo.html Hm... this sounds like a potentially better solution, that the maven-dependency-plugin (which as also got a reference to from you...:-) ) that we're currently using to pull the binary bundles in from a maven repository: http://maven.apache.org/plugins/maven-dependency-plugin/ Two possible issues, though: - the dependency plugin copy and copy-dependencies goals has an overWriteIfNewer setting, while the eclipse:install-plugins only has an overwrite flag, meaning "always overwrite" - the dependency plugin has the copy-dependencies goal that can be used to pull in bundles neccessary for the ones we're building Maybe I'm better off staying with the dependencies plugin. > sorry, I forgot for a moment that we we're talking about source > plugins :) still, this mojo could be expanded to also create the > source... The eclipse:install-plugins goal has the projectBuilder parameter which seems to imply that plugins can be selected to be installed as jars or directories on an individual basis. Doesn't give an actual howto to _how_ this can be accomplished though. What it says is: projectBuilder Used to retrieve the project metadata (POM) associated with each plugin dependency, to help determine whether that plugin should be installed as a jar, or expanded into a directory. I don't have a clue what to write in the POM to make bundles be installed as directories, unfortunately...:-/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
