Hi, there are no objections, so I'll proceed to release this plugin. -Robert @Anders, AFAIK the jira-report should be generated. I just noticed the plugin uses 2.3 of the m-changes-p, maybe there's already a fix in 2.4
Date: Wed, 23 Feb 2011 06:32:17 +0100 From: [email protected] To: [email protected] Subject: Re: [mojo-dev] [VOTE] Release Aspectj-maven-plugin version 1.3.1 The jira report on the site [1] doesn't match the fixed issues you've linked to in jira [2]. Not a major thing, but a little bit weird. I haven't checked the code, but I assume the jira report is crafted manually instead of retrieved from jira. /Anders [1] http://mojo.codehaus.org/aspectj-maven-plugin/jira-report.html [2] http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11781&version=16118 On Tue, Feb 22, 2011 at 23:30, Robert Scholte <[email protected]> wrote: Hi, I'd like to release version 1.3.1 of the Aspectj Maven Plugin This plugin handles AspectJ usage within MavenFunctionality provided is: weaving of aspects (or existing aspects from libraries) with the test and/or main classes, weaving of pre-existing jars and ajdoc reporting. We solved 4 issues: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11781&version=16118There are still a couple of issues left in JIRA: http://jira.codehaus.org/browse/MASPECTJ#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel Staging Repositories: General: https://nexus.codehaus.org/content/groups/staging/ Exclusive: https://nexus.codehaus.org/content/repositories/orgcodehausmojo-003/ (Staging) Site: http://mojo.codehaus.org/aspectj-maven-plugin/SCM Tag: http://fisheye.codehaus.org/changelog/mojo/?cs=13660 The main reason for this bugfix-release is the fix of MASPECTJ-90, which orders the dependencies on the classpath as they should be. [ ] +1 [ ] +0 [ ] -1 The vote is open for 72 hours and will succeed by lazy consensus. Regards -Robert
