osgi bundle plugin and bundle automation for dependencies

Can the apache felix "Bundle Plugin for Maven" also automate the creating of osgi bundles for project dependencies, and transitive dependencies? If it can't, is there any other tool that can, or hints people can give? Mark -

selective modules for javadocs in multi-module projects

Is there a way to selectively do javadocs for specific modules in a multi-module project? ideally I'd like to do one bit aggregate report for thse specific modules. But if necessary I'll accept the output of multiple javadocs. Thanks Mark

Re: next javadoc plugin release?

Any update when the javadoc plugin will be released? Mark Mark Proctor wrote: The Javadoc plugin is currently broken for doclet usage. I fixed the bug and carlos applied my patch, http://jira.codehaus.org/browse/MJAVADOC-115 - vincent is taking time to work on xwiki so won't be doin

Re: [hibernate-dev] docbook + maven

yes I raised that with steve, after being abused for some time, I think I eventually persuaded him to include the properties necessary for this. Mark Max Rydahl Andersen wrote: one thing is for sure, the current image location in our docbook is annoying ;( It is not relative to where the xml

next javadoc plugin release?

The Javadoc plugin is currently broken for doclet usage. I fixed the bug and carlos applied my patch, http://jira.codehaus.org/browse/MJAVADOC-115 - vincent is taking time to work on xwiki so won't be doing any plugin maintenance. Any idea when this will be released, who can do this now with vi

Re: How to use patched INTERNAL javadoc plugin

http://jira.codehaus.org/browse/MJAVADOC-115 Beers on RedHat any time you are in London :) Mark Carlos Sanchez wrote: just point to the patch and invite to some beers ;) On 3/14/07, Mark Proctor <[EMAIL PROTECTED]> wrote: The problem with another group-id is that it then cannot be se

Re: How to use patched INTERNAL javadoc plugin

use a proxy (so the maven-metadata.xml is merged) or you put your plugin under another groupId, which should be the most correct solution On 3/14/07, Mark Proctor <[EMAIL PROTECTED]> wrote: After finding a bug I'm trying to make our build system work with a patched version of the ja

How to use patched INTERNAL javadoc plugin

ilable with the following two settings: basedir file://${basedir}/repository and basedir file://${basedir}/repository This works for all the other dependencies that are local repository directory. Mark Mark Proctor wrote: I have discovered the bug, logged it

properties in settings.xml do not interpolate

Having now found this issue: http://jira.codehaus.org/browse/MJAVADOC-115 I'm back now trying to get variable interpolation done from properties in a settings file. This is my settings.xml file: default ${user.home}/dev/ydoc ${user.home}/dev/

Re: docletPath issues with javadoc plugin

I have discovered the bug, logged it and provided a fix. please fix and release asap :) http://jira.codehaus.org/browse/MJAVADOC-115 Mark Mark Proctor wrote: I'm trying to use the javadoc plugin with ydoc. If I specify the jars as artifiacts it cannot use the docletPath setting to fin

docletPath issues with javadoc plugin

I'm trying to use the javadoc plugin with ydoc. If I specify the jars as artifiacts it cannot use the docletPath setting to find the resources directory, as its one or the other: *if* ( ( docletArtifact != *null* ) && ( StringUtils.isNotEmpty( docletArtifact.getGroupId() ) )

pluginGroups in pom.xml

I'm writting a plugin that is specific to my project, I want the user to be able to call this plugin outside of the normal lifecycles. I have seen the documentation on pluginGroups, but I don't want to have to make the user go through the extra step of creating a settings.xml - is there anyway

Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2

defaults: Mark Proctor wrote: yes thought I read that in the plugin.jelly, I'm going to try 1.6 with the license for 1.7 - see if that helps. Mark Vincent Massol wrote: -Original Me

Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2

yes thought I read that in the plugin.jelly, I'm going to try 1.6 with the license for 1.7 - see if that helps. Mark Vincent Massol wrote: -Original Message- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sent: mardi 10 mai 2005 21:18 To: Maven Users List Subject: Re: Clover Plugi

Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2

I upgraded because the license ran out, no we dont fork the tests (apart from python) - but that wasn't needed before. Mark Vincent Massol wrote: Hi Mark, -Original Message- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sent: mardi 10 mai 2005 06:15 To: Maven Users List Subjec

Re: [maven 1.1] Clover Tasks not found - a solution

ls-smf/target/ first? It seems that the java compile of the first project did not recompile anything as if there was nothing to recompile: java:compile: [echo] Compiling to D:\java\drools-2.0\drools-smf/target/clover/classes -Original Message- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sen

Re: [maven 1.1] Clover Tasks not found - a solution

maven 1.1? latest I can find is 1.0.2? Anyway using maven 1.0.2 I wasn't getting that error but changed those lines you said anyway, still no good :( I have included the output below. Notice I've excluded all but two modules from mutliproject, no matter what modules I use to build I get the same

Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2

Proctor wrote: Ignore this, got it working, was a missing goal in a sub project. Mark Mark Proctor wrote: I'm trying to do clover multiproject build with maven 1.0.2 and clover plugin 1.7. This use to work but with the upgrade to 1.7 I noticed it is now broken, not sure if its 1.7 or a change i

Re: Clover Plugin 1.7 and multiproject on Maven 1.0.2

Ignore this, got it working, was a missing goal in a sub project. Mark Mark Proctor wrote: I'm trying to do clover multiproject build with maven 1.0.2 and clover plugin 1.7. This use to work but with the upgrade to 1.7 I noticed it is now broken, not sure if its 1.7 or a change in our

Clover Plugin 1.7 and multiproject on Maven 1.0.2

I'm trying to do clover multiproject build with maven 1.0.2 and clover plugin 1.7. This use to work but with the upgrade to 1.7 I noticed it is now broken, not sure if its 1.7 or a change in our code. Everything compiles and runs fine, each project reports that it is updating the same database but

Re: automated plugin update

rt: plugin:download-artifact: ... ... Mark Mark Proctor wrote: sorry thats Mark Proctor wrote: Thanks to bretts help I now have it working with: Mark Carlos Sanchez wrote: Hi, That was my suggestion, but

Re: automated plugin update

sorry thats Mark Proctor wrote: Thanks to bretts help I now have it working with: Mark Carlos Sanchez wrote: Hi, That was my suggestion, but due to bug MAVEN-1427 I think it's not possible. Re

Re: automated plugin update

lossg -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Tuesday, October 12, 2004 11:00 PM To: Maven Users List Subject: Re: automated plugin update how about declaring it as a project dependency with plugin? Cheers, Brett On Tue, 12 Oct 2004 20:48:39 +0200, Mark Proctor &l

automated plugin update

I'm trying to make sure out application automatically upates maven to plugin aspectj 3.2 but I've found my current solution to be error prone - producing cache problems. Anyone have a robust solution? ${droolsAspects

Re: optional aspects

://jira.codehaus.org/browse/MPASPECTJ If you need help, don't hesitate on asking me. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 7:18 PM To: Maven Users List; [

Re: optional aspects

y} in ant:sourceroots as normal. Mark Carlos Sanchez wrote: Feel free to CCing your findings to me. -Original Message- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 5:54 PM To: Maven Users List Subject: Re: optional aspects Just tried testing the plugin with the code c

Re: optional aspects

be happy to add it to the plugin. Regards Carlos Sanchez A Coruña, Spain Oness Project http://oness.sourceforge.net -Original Message- From: Mark Proctor [mailto:[EMAIL PROTECTED] Sent: Friday, July 30, 2004 4:29 PM To: Maven Users List Subject: optional aspects We are building up a suit

optional aspects

We are building up a suite of aspects with aspectj to help with testing/debugging. We want to be able to choose which aspects are weaved at compile time with property settings, is this possible? I was hoping I could do: maven.aspectj.sourceRootCopyFilter=**/drools/Trace.java, **/drools/Trace/Me

hooks

Whats the best way to create "hooks". By this I mean something on the lines of a taglib having a dummy which is called when something happens. A user in an another taglib can have their called when that dummy is called. Better yet would there be a way to stack this - maybe add the to an

Re: cvs, svn

I've just double checked - SVN provides java bindings via jni, as well as perl and python bindings. Mark Mark Proctor wrote: I'm using Subversion (SVN) and find it vastly simpler to use, especially with directory reorganisations. the TortoiseSVN client for windows is very nice, t

Re: cvs, svn

I'm using Subversion (SVN) and find it vastly simpler to use, especially with directory reorganisations. the TortoiseSVN client for windows is very nice, there is an eclipse plugin, that works well too. I use the Apache webdav without any problems. ViewCVS (head) now has support for SVN too. T