Deploy war type plugin dependencies with tomcat:run
---
Key: MTOMCAT-74
URL: http://jira.codehaus.org/browse/MTOMCAT-74
Project: Maven 2.x Tomcat Plugin
Issue Type: Improvement
Affects Vers
Most of the mojo-projects are starting to use a property for the maven version,
but I've noticed both ${mavenVersion} and ${maven.version}.
If you use such a property, you would always set the prerequisite of Maven for
that project too.
So I'd prefer to use ${project.prerequisite.maven}, since
I agree with Jesse on the naming...
+1 to invite Franck to join the Codehaus Mojo group
+1 to release the plugin under cxx-maven-plugin
Wayne
On Wed, Jan 12, 2011 at 10:20 AM, Jesse Farinacci wrote:
> Greetings,
>
> On Wed, Jan 12, 2011 at 6:59 AM, wrote:
>> I choose to release this plugin un
On 2011-01-12 12:21, Benjamin Bentmann wrote:
> Paul Gier wrote:
>
>> This seems like a good use case for having a property available
>> containing the current Maven version (MNG-4112). Then we could just
>> substitute something like ${maven.version} for "current".
>
> Having the javadoc links d
Greetings,
On Wed, Jan 12, 2011 at 6:59 AM, wrote:
> I choose to release this plugin under org.codehaus.mojo group id with
> artifactId
> maven-cxx-plugin
Typically, Mojo Codehaus plugins do not use the maven-xxx-plugin
format, but rather, xxx-maven-plugin.
-Jesse
--
There are 10 types of p
Hello,
So the vote has passed with the following result :
+1 : Arnaud Héritier, Julien Ponge, Matthias Wessendorf, Mark
Struberg, Olivier Lamy.
I will push the artifacts to central repo.
Thanks,
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
--
extraJvmArguments are passed verbatim
-
Key: MAPPASM-112
URL: http://jira.codehaus.org/browse/MAPPASM-112
Project: Mojo AppAssembler Plugin
Issue Type: Bug
Affects Versions: 1.1
Environment: a
Anders Hammar wrote:
I'm not PGP
guru, but I believe this is normal as the public key is not signed by a
trusted authority.
[...]
Could someone confirm that there is no issue, please?
Yes, the warning is normal.
Benjamin
-
Site doc pages refer to downlevel plugin version
Key: MFINDBUGS-130
URL: http://jira.codehaus.org/browse/MFINDBUGS-130
Project: Maven 2.x FindBugs Plugin
Issue Type: Improvement
Affects Ve
+2 too
Arnaud
On Wed, Jan 12, 2011 at 1:07 PM, nicolas de loof
wrote:
> +1 to hots the plugin as a new Mojo contrib
> +1 to invite Franck as Mojo Committer
>
> Nicolas
>
> 2011/1/12
>>
>> Hello,
>>
>> In order to complete my last work on a sonar plugin called
>> sonar-cxx-plugin. I
>> developed
+1 to hots the plugin as a new Mojo contrib
+1 to invite Franck as Mojo Committer
Nicolas
2011/1/12
> Hello,
>
> In order to complete my last work on a sonar plugin called
> sonar-cxx-plugin. I
> developed a maven plugin called maven-cxx-plugin.
>
> This plugin contains 9 mojo that achieve foll
Hello,
In order to complete my last work on a sonar plugin called sonar-cxx-plugin. I
developed a maven plugin called maven-cxx-plugin.
This plugin contains 9 mojo that achieve following phase:
1/ C++ customizable compilation phase (with CMake and make)
2/ C++ unit Test (based on xUnit)
3/ C++ st
Paul Gier wrote:
This seems like a good use case for having a property available
containing the current Maven version (MNG-4112). Then we could just
substitute something like ${maven.version} for "current".
Having the javadoc links depend on the Maven version currently used to
build is a bad
13 matches
Mail list logo
