+1
Hervé
Le mercredi 27 juin 2012 07:53:44 Benson Margulies a écrit :
> Hi,
>
> We solved 1 issues:
>
> ** Bug
> * [MSHADE-123] - 1.7 Causes failures in other plugins make
> "basedir" point to the build dir
>
>
> There are still plenty of issues left in JIRA.
>
> Staging repo:
> https://
+1
Dan
On Wednesday, June 27, 2012 07:53:44 AM Benson Margulies wrote:
> Hi,
>
> We solved 1 issues:
>
> ** Bug
> * [MSHADE-123] - 1.7 Causes failures in other plugins make
> "basedir" point to the build dir
>
>
> There are still plenty of issues left in JIRA.
>
> Staging repo:
> https
+1
2012/6/27 Benson Margulies :
> Hi,
>
> We solved 1 issues:
>
> ** Bug
> * [MSHADE-123] - 1.7 Causes failures in other plugins make
> "basedir" point to the build dir
>
>
> There are still plenty of issues left in JIRA.
>
> Staging repo:
> https://repository.apache.org/content/repositories/ma
Hi,
Yes please create an issue.
Which os are you using ?
Currently jenkins build are ok. I will add one with jdk1.7
2012/6/28 Tony Chemit :
> Hy,
>
> I try to build the project from the root maven project but I faced some
> compilation problems :
>
> in maven-plugin-tools-javadoc
> --
GitHub user anistor opened a pull request:
https://github.com/apache/maven-surefire/pull/6
SUREFIRE-879 maven-surefire-report-plugin fails some times with Concurre...
...ntModificationException when running parallel TestNG
The issue is easily fixed by atomically getting the
Oh yes good point I missed that.
I essentially work on the anno mode to be able to inherits annotations
from reactors modules and/or dependencies.
2012/6/28 Igor Fedorenko :
> What about inheritance? Other tools that may want to do something
> with the annotations?
>
> --
> Regards,
> Igor
>
>
>
Github user anistor closed the pull request at:
https://github.com/apache/maven-surefire/pull/5
-
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
On 28 June 2012 11:33, Igor Fedorenko wrote:
> What about inheritance?
+1000 inheritance is one of the reasons we moved to annotations from
javadoc tags (though I agree that plugin.xml merging could solve that
somewhat, it's messy and ties us back rather than forward
> Other tools that may want
What about inheritance? Other tools that may want to do something
with the annotations?
--
Regards,
Igor
On 12-06-28 6:06 AM, Olivier Lamy wrote:
could be better maybe.
But means 1.6 required.
Do you want to work on a branch with this change ?
2012/6/28 Milos Kleint :
why not use jdk's own a
could be better maybe.
But means 1.6 required.
Do you want to work on a branch with this change ?
2012/6/28 Milos Kleint :
> why not use jdk's own annotation processors (which get compiled by
> javac are we save ourselves an extra mojo execution)?
>
> Milos
>
> On Thu, Jun 28, 2012 at 11:50 AM, O
why not use jdk's own annotation processors (which get compiled by
javac are we save ourselves an extra mojo execution)?
Milos
On Thu, Jun 28, 2012 at 11:50 AM, Olivier Lamy wrote:
> Hi,
> We use asm to collect annotations from compiled classes (so scope compile )
> Makes sense ?
>
> 2012/6/28 M
Hi,
We use asm to collect annotations from compiled classes (so scope compile )
Makes sense ?
2012/6/28 Milos Kleint :
> Hello,
>
> I'm in the process of rewriting the nbm-maven-plugin at mojo to use
> the new annotations instead of javadoc tags. It appears to be working
> fine, but I'm wondering
Hello,
I'm in the process of rewriting the nbm-maven-plugin at mojo to use
the new annotations instead of javadoc tags. It appears to be working
fine, but I'm wondering why the retention policy is CLASS. Since it's
only used to generate the xml file, it could be turned into SOURCE and
the annotati
Thanks for help Stephen.
I implemented a prototype which follows the approach to override the default
release manager:
org.apache.maven.plugins
maven-release-plugin
2.3.2
org.sourcepit.b2
b2-releas
14 matches
Mail list logo
