On 20 October 2010 06:59, Felix Meschberger <[email protected]> wrote:
> Hi all, > > Working on FELIX-2642 I was able to get the Maven SCR Plugin also be an > Ant Task. Unlike Maven, though, Ant is not out-of-the-box able to > automatically download task (and other) dependencies from the web. FYI, you could always use the built-in "get" task to download dependencies: http://ant.apache.org/manual/Tasks/get.html not ideal, but it's what we use in the generated Ant script from the bundleplugin: http://svn.apache.org/repos/asf/felix/trunk/bundleplugin/src/main/resources/build.xml this is used in the "bundle:ant" goal to generate an Ant build for your project Yet, > for the Ant task to fully function, the QDox, ASM and our own SCR > Annotations library must be available to the task. > > The easiest thing would be to just include the QDox, ASM and our own SCR > Annotations libraries inside the maven-scr-plugin JAR file. > > What I am unsure about is, whether we should really include the > libraries with the standard maven-scr-plugin JAR file or whether we > should create anonther, Ant-specific, artifact. > > From my POV here are the pros an cons of integrating the libs with the > standard build: > > + easier build > + resolves a build time dependency problem for maven too > (the scr.annotations SNAPSHOT needs not be deployed because it > is already included in the plugin) > + no additional QDox and ASM downloads > - bigger size of the JAR file > - It would probably be impossible to upgrade the QDox or ASM > dependency for the maven-scr-plugin in a per-plugin dependencies > section > > I currently tend to just include the libraries with the standard build. > > WDYT ? > > Regards > Felix > -- Cheers, Stuart
