> - Increment the version by 1
You might better indicate it as private branch. 

The maven versioning system supports versions like
pluginname-2.0.1-aaron-1

This way you don't get conflicts if the release is
also beeing used (which almost certain will be the
case) in a later development phase by the original
plugin vendor.

lg,
strub

--- [EMAIL PROTECTED] schrieb:

> Emmanuel Hugonnet <[EMAIL PROTECTED]>
> schrieb am 28.11.2006 
> 14:24:44:
> 
> > I have to edit the pom.xml of 
> > maven-plugin-tools-java to set the version of qdox
> to 1.6.1 and then all 
> 
> > is fine.
> 
> My solution in such a case:
> 
> - Download the source for the broken plugin
> - Fix the dependencies
> - Increment the version by 1 (i.e. 2.0.2 in this
> case).
> - Deploy the new plugin to a local repository
> 
> Now, you can use this version in your projects until
> the bug is fixed.
> 
> You might also want to add -SNAPSHOT to the version
> but then, you have to 
> make sure that you're not getting into conflicts
> with the official 
> snapshots.
> 
> If the plugin is released with the very same
> version, you have to delete 
> it manually on your side but until then, you can
> work.
> 
> How about a -PATCH version? :-)
> 
> Regards,
> 
> -- 
> Aaron Digulla
> Magazine zum Globus
> Informatik AW - Web
> Eichstrasse 23
> 8045 Zuerich
> Phone:  +41 58 455 26 20
> Fax: +41 58 455 27 28
> 
> www.globus.ch
> Mail: [EMAIL PROTECTED] 
> 
> > [EMAIL PROTECTED] a écrit :
> >  > Please post the error.
> >  >
> >  > Regards,
> >  >
> >  > 
> > It is some qdox exception. I have posted on the
> users list about my 
> > problem, in summary I have a dependency on
> maven-plugin-tools when I 
> > build my plugin, maven-plugin-tools depends on
> maven-plugin-tools-java 
> > which depends on qdox for extracting the metadata
> to plugin.xml. The 
> > problem is that I can't find a way to override
> this dependency path, 
> > since maven-plugin-tools-java is 2.0.1 it goes to
> qdox 1.5 which is not 
> > compatible with Java 1.5 so
> > I read a conversation on dev mailing list this
> summer about a similar 
> > kind of problem when trying to build maven.
> > I have checked this dependency problem on 2.04,
> 2.0.5-SNAPSHOT and 
> > 2.1-SNAPSHOT but on 2.1 I didn't try overriding
> and I didn't change my 
> pom.
> > I have attached all the log I could get, if you
> could prove me wrong and 
> 
> > give me a solution I would be more than happy :-)
> > Regards,
> > Emmanuel
> 
> 
>
---------------------------------------------------------------------
> To unsubscribe, e-mail:
> [EMAIL PROTECTED]
> For additional commands, e-mail:
> [EMAIL PROTECTED]
> 
> 



        

        
                
___________________________________________________________ 
Der frühe Vogel fängt den Wurm. Hier gelangen Sie zum neuen Yahoo! Mail: 
http://mail.yahoo.de

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to