Re: [maven-shade-plugin] TLC [WAS Re: [maven-assembly-plugin] smart(er) dependency merge]
On Thu, Jun 30, 2011 at 1:11 PM, Benson Margulies wrote: > I'll play patch monkey. Name those JIRA. :-) [1] patches the documentation to add descriptions for the resource descriptors which worked well for me. Moving on to prepare test cases and fixes for issues discovered. Robert [1] http://jira.codehaus.org/browse/MSHADE-100 - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
Re: Plugin dependencies bug
After having to disable my maven mirror for one reason or another awhile ago I now seem to be getting hit with this rather annoying bug on quite a few projects now that my ~/.m2/repository has a mix of artifacts downloaded via a mirror, and others direct. rm'ing the _maven.repositories file from ~/.m2/repository seems to work around the problem, but I'm also now hearing from people on IRC who seem to be getting tripped up with the same problem. What can I do to try and help get this problem resolved? By reading Richard's ticket the problem is inside Aether, should we raise the ticket in Aether's github issue tracker or is here good enough ( I seem to recall here being decided as the place to go when Aether was introduced ). Mark PS: For reference, the ticket was http://jira.codehaus.org/browse/MNG-5084 -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Fri, May 13, 2011 at 8:43 PM, Richard Vowles < rich...@bluetrainsoftware.com> wrote: > Hi all, > > I'm not sure of the etiquette here - but I'm struggling with an aether bug > in the easyb project - we can't release our plugin. > > I have a reproducible sample, I have debugged through down the sections of > code which seem to be at fault, but I am not confident enough about the > implications to suggest a fix. > > The bug is listed here: > > http://jira.codehaus.org/browse/MNG-5084 > > It appears I have to completely change the way that artefacts are released > (i.e. not use version ranges) to work around the bug. > > What is the proper method of progressing this? > > Thanks > Richard > > -- > --- > Richard Vowles, > Grails, Groovy, Java > Consistency is the last refuge of the unimaginative - Oscar Wilde > ph: +64275467747, linkedin, skype:rvowles > get 2Gb shared disk space in the cloud - Dropbox, its incredibly useful! - > http://tinyurl.com/cmcceh > podcast: http://www.illegalargument.com >
[ANN] Maven Release Plugin 2.2 Released
The Maven team is pleased to announce the release of the Maven Release Plugin, version 2.2 This plugin is used to release a project with Maven, saving a lot of repetitive, manual work. Releasing a project is made in two steps: prepare and perform. http://maven.apache.org/plugins/maven-release-plugin/ You should specify the version in your project's plugin configuration: org.apache.maven.plugins maven-release-plugin 2.2 Release Notes - Maven 2.x Release Plugin - Version 2.2 ** Bug * [MRELEASE-374] - Snapshot versions unusable in batch mode * [MRELEASE-622] - Creating label fails for ClearCase with message 'Unable to determine VOB for pathname ".".' * [MRELEASE-661] - Exception: String index out of range: -1 ** Improvement * [MRELEASE-591] - release:update-versions: add option to do a checkin * [MRELEASE-605] - when not pushing changes to remote git repo in 2.1, the release plugin fails on release:perform * [MRELEASE-628] - Subversion --trust-server-cert option * [MRELEASE-641] - upgrade to scm 1.5 (hg plugin insists on 'pushing') ** New Feature * [MRELEASE-159] - Support a pattern to generate the release tag * [MRELEASE-457] - Non sparse-checkout SCM support * [MRELEASE-613] - Add a parameter that tells the plugin to wait for X seconds before tagging * [MRELEASE-621] - Add a postPrepareGoals * [MRELEASE-648] - Putting SVN password in settings.xml doesn't support password encryption Enjoy, -The Maven team - To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
