Re: What will replace the @aggregator MOJO configuration?
being able to bind to the front and back of a lifecycle would be absolutely splendid +1. A simple event system which fired build events to registered listeners (plugins could register these) would go a long way. Example events could be: * Build Started * Phase Started * Goal Started * Goal Ended * Phase Ended * Build Failed * Build Complete Brian E Fox wrote: Yes it's binding the aggregator with @execute to a lifecycle that is the problem. There's nothing wrong with aggregators that are meant to perform some action from the CLI. The trouble is that everyone ends up making two goals, one @aggregator and one xxx-only goal that is without the aggregator. I know of too many instances where someone bound an aggregator executor goal to a lifecycle and ended up with n*n-1 recursive builds or other crazy behavior. What I think we need is an annotation that says execute up to this phase only if it hasn't already run essentially a minimum phase execution. There also needs to be a way to attach a plugin to execute before the lifecycle to influence things like inject dependencies and we also need a way to bind to the very end of a build for cleanup or metric collection types of things. On 12/5/08 7:59 PM, Brett Porter [EMAIL PROTECTED] wrote: On 06/12/2008, at 9:37 AM, Brian Fox wrote: There's nothing presumptive about the fact that it HAS been deprecated in trunk for quite some time now. (since it was still called 2.1-snap) Ok, you're right, when binding to the lifecycle (which admittedly we are talking about here), though not generally. Aren't the source of these problems when it is used in conjunction with @execute? (Which is probably the more problematic annotation, I was never happy with the way that was done). The aggregator is full of problems and usually leads to recursive builds when you bind it to the lifecycle. A complely new concept is needed to handle this use case. But doesn't yet exist, so perhaps a warning is more appropriate than a deprecation at this point. It does still work for the limited use cases it was designed for (such as the Nick is referring to). Cheers, Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/What-will-replace-the-%40aggregator-MOJO-configuration--tp20825520p20873221.html Sent from the Maven Developers mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Reports are down
A patch would be great! Sent from my iPhone On Dec 7, 2008, at 1:36 AM, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi, Our reports on votes are down : http://www.sonatype.org/~j2ee-hudson/reports/ https://ci.sonatype.org/view/Reports/ It's certainly a Jira upgrade which broke the xml-rpc API used in Swizzle but there was no activity on this project to fix the issue (and since april). Is there someone who know the swizzle team ? Is it useful to spend time to provide a patch ? -- .. Arnaud HERITIER 12 guidelines to boost your productivity with a Java software factory - http://tinyurl.com/56s9tw .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r724225 - /maven/mercury/trunk/pom.xml
On 08/12/2008, at 11:46 AM, [EMAIL PROTECTED] wrote: pluginManagement plugins plugin - artifactIdmaven-release-plugin/artifactId - version2.0-beta-7/version - configuration -tagBasehttps://svn.apache.org/repos/asf/maven/mercury/tags /tagBase -autoVersionSubmodulestrue/autoVersionSubmodules - /configuration -/plugin did you intend to roll this back too? Also the following commit made some code changes which didn't seem like they meant to be rolled back. - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: svn commit: r724225 - /maven/mercury/trunk/pom.xml
Thanks for catching this one, Oleg Brett Porter wrote: On 08/12/2008, at 11:46 AM, [EMAIL PROTECTED] wrote: pluginManagement plugins plugin - artifactIdmaven-release-plugin/artifactId - version2.0-beta-7/version - configuration - tagBasehttps://svn.apache.org/repos/asf/maven/mercury/tags/tagBase -autoVersionSubmodulestrue/autoVersionSubmodules - /configuration -/plugin did you intend to roll this back too? Also the following commit made some code changes which didn't seem like they meant to be rolled back. - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
{VOTE] Release Mercury 1.0.0-alpha-2
Dear All, This is the first release of Mercury with all major [mercury] functionality enabled: repository access + dependency resolution. You can try using it for resolving artifacts and then writing them into a local repo in a standalone application, event system helps to understand what is going on inside (and for how long it does that). Example of using Mercury is available in mercury-plexus unit test. More detailed discussion - http://docs.codehaus.org/display/MAVEN/Mercury Special thanks to Herve Bouteme and Benjamin Bentmann for helping to make this happen! We solved 20 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11816styleName=Htmlversion=14629 Staging repo: http://people.apache.org/~ogusakov/repos/staging Staging site: http://maven.apache.org/mercury/staging Vote open for 72 hours. Thanks, Oleg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
