Re: @threadSafe

Assuming, of course, that you use the javadoc annotation... Kristian Den 17. mai 2012 kl. 06:52 skrev Chris Graham chrisgw...@gmail.com: :-) Ta much. -Chris On Thu, May 17, 2012 at 2:27 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: yes Den 17. mai 2012 kl. 06:18 skrev

Re: @threadSafe

Um, please pardon my ignorance, but how else would you? -Chris On Thu, May 17, 2012 at 4:24 PM, Kristian Rosenvold kristian.rosenv...@zenior.no wrote: Assuming, of course, that you use the javadoc annotation... Kristian Den 17. mai 2012 kl. 06:52 skrev Chris Graham chrisgw...@gmail.com:

Re: Change of behavior with the SCM/Release Plugin?

The workaround for you is probably: checkModificationExcludes checkModificationExclude/**/pom.xml.branchcheckModificationExclude checkModificationExclude/**/pom.xml.backupcheckModificationExclude checkModificationExclude/**/pom.xml.releaseBackupcheckModificationExclude

Re: Change of behavior with the SCM/Release Plugin?

Hi Chris, I've added org.apache.maven.scm.provider.jazz.command.status.JazzStatusConsumerTest, which contains a test which should succeed according the restrictions due to SCM-674 [1] I don't know if Jazz will keep the starting slash, or if we can assume it'll always start with it (so we

Re: Maven Plugin Tools - renaming expression

I removed readonly and required as attributes of @component (both in javadoc or java 5 annotation form), since they are ignored by the descriptor generation step (see r1339666) I renamed expression to property for Java 5 annotations in r1339888. Then I tried to add property support for javadoc

[jira] Subscription: Design Best Practices

Issue Subscription Filter: Design Best Practices (25 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles https://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques