can I read silence as lazy consensus to add annotation processing to the
compiler plugin?
Milos
On Mon, Jan 25, 2010 at 2:48 PM, Milos Kleint mkle...@gmail.com wrote:
Hello,
I'd like to start a discussion about how annotations are supported in maven
builds. I'm currently trying to use some
+1
On 2010-01-21 22:48, Dennis Lundberg wrote:
Hi,
We solved 2 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?version=12800styleName=HtmlprojectId=11149
There are still a couple of issues left in JIRA:
Hi,
The vote has passed with the following result :
+1 (binding): Benjamin Bentmann, Brett Porter, Dennis Lundberg
+1 (non binding): Stephen Connolly
I will promote the artifacts to the central repo.
On 2010-01-21 22:48, Dennis Lundberg wrote:
Hi,
We solved 2 issues:
I have defined a class inheriting from AbstractMojo with @goal mygoal.
So, everytime we do
$ mvn myplugin:mygoal
I want to invoke the compile goal ( $ mvn compile ) behind the scenes
and my goal getting launched only if the former was a success. Is there
an annotation / configuration in
Please read the @execute descriptor documention on this page:
http://maven.apache.org/developers/mojo-api-specification.html
Justin
On 1/30/10 1:48 PM, Kay Kay wrote:
I have defined a class inheriting from AbstractMojo with @goal mygoal.
So, everytime we do
$ mvn myplugin:mygoal
I want to
Adding this to the mojo on top, works. Thanks.
* @execute phase=compile
On 01/30/2010 11:06 AM, Justin Edelson wrote:
Please read the @execute descriptor documention on this page:
http://maven.apache.org/developers/mojo-api-specification.html
Justin
On 1/30/10 1:48 PM, Kay Kay wrote:
I
The Maven team is pleased to announce the release of the Maven Verifier
Plugin, version 1.0
This plugin is useful for integration tests - verifies the existence of
certain conditions.
http://maven.apache.org/plugins/maven-verifier-plugin/
You should specify the version in your project's plugin
Hi,
This vote is for the entire Maven Release project, which includes Maven
Release Manager and Maven Release Plugin.
We solved 30 issues:
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11144styleName=Htmlversion=15113
There are still a couple of issues left in JIRA:
are you planning on removing the duplicates from jira. I only had a
quick look, but it would seem to have a lot if dups of bugs fixed by
this release, eg MRELEASE-514 looks like it's a dup.
I'll check the binaries on Monday against my troublesome work projects
Sent from my [rhymes with
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-068/
While I could successfully release Plexus 1.5.4 using the new plugin
version, the plugin's source bundle is incomplete, causing the following
test failures
Results :
Failed tests:
Dennis Lundberg wrote:
Staging repo:
https://repository.apache.org/content/repositories/maven-068/
The new plugin *almost* solves MRELEASE-458, in that setting
updateWorkingCopyVersions=false for release:branch does result in the working
copy version being preserved at the end of the release
On 31 January 2010 10:52, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
are you planning on removing the duplicates from jira. I only had a quick
look, but it would seem to have a lot if dups of bugs fixed by this release,
eg MRELEASE-514 looks like it's a dup.
I'll check the
On 31 January 2010 11:12, Peter Janes maven.apache@peterjanes.cawrote:
The new plugin *almost* solves MRELEASE-458, in that setting
updateWorkingCopyVersions=false for release:branch does result in the
working copy version being preserved at the end of the release process.
However, the
On 30 January 2010 02:38, Jason van Zyl ja...@sonatype.com wrote:
On 2010-01-29, at 4:09 PM, nicolas de loof wrote:
could we use milestone as names in replacement for alpha, so that we
get
more early-adopter to test the (pre)release and detected regressions ?
I can understand the
14 matches
Mail list logo
