because of r941505
if maven-reporting-impl 2.0.4.x can use maven-reporting-api 3.0 too
Regards,
Hervé
Le mercredi 05 mai 2010, Lukas Theussl a écrit :
> why?
>
> -Lukas
>
> hbout...@apache.org wrote:
> > Author: hboutemy
> > Date: Mon May 3 20:47:38 2010
> > New Revision: 940613
> >
> > URL:
Hi there,
I have take a short look on the site and found that the JIRA Report page
in simply empty ?
http://maven.apache.org/plugins/maven-plugin-plugin/
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz Mar
moved to retired path.
2010/5/5 Jason van Zyl :
> You can just erase this repository, we're not ever going to use it.
>
> On May 4, 2010, at 10:04 PM, ol...@apache.org wrote:
>
>> Author: olamy
>> Date: Tue May 4 20:04:55 2010
>> New Revision: 941019
>>
>> URL: http://svn.apache.org/viewvc?rev=94
Kurt Zettel wrote:
The jars were in two different groups. [...] plexus versus org.codehaus.plexus.
Ah, now I got it, thanks. That's unintended and scheduled for fixing in
the next release [0].
Benjamin
[0] http://jira.codehaus.org/browse/MNG-4666
The jars were in two different groups. We are
using: plexus:plexus-log4j-logging:1.0 which imports an old version of the
plexus-container which is in the group plexus versus org.codehaus.plexus.
--
Kurt
On Wed, May 5, 2010 at 2:44 PM, Benjamin Bentmann wrote:
> Kurt Zettel wrote:
>
> I figure
Kurt Zettel wrote:
I figured it out. Turns out I had two different versions
of plexus-container-default as Maven dependencies.
This sounds strange. For one, Maven's dependency resolution ensures only
a single version per groupId:artifactId:type[:classifier] is present in
the dependency tree
I figured it out. Turns out I had two different versions
of plexus-container-default as Maven dependencies. This caused the
instanceof check in the ContextualizePhase to return false even though my
Mojo implemented Contextualizable. I corrected my pom and it is working as
expected now.
Thank yo
The Maven team is pleased to announce the release of the Maven Plugin
Tools, version 2.6.
This plugin assists authors of Maven plugins in the creation of a plugin
descriptor and documentation by scanning the plugin sources for mojo
annotations. See the plugin's site for more details:
http:
You can just erase this repository, we're not ever going to use it.
On May 4, 2010, at 10:04 PM, ol...@apache.org wrote:
> Author: olamy
> Date: Tue May 4 20:04:55 2010
> New Revision: 941019
>
> URL: http://svn.apache.org/viewvc?rev=941019&view=rev
> Log:
> add a note on the state of mercury i
On 5/05/10 10:00 PM, Benjamin Bentmann wrote:
James C. McPherson wrote:
I think it's reasonable to remove the
from the extract-assembly target. Thoughts?
No, this task should stay in place as it ensures the installation
directory actually contains the just built distribution and not some
James C. McPherson wrote:
I think it's reasonable to remove the
from the extract-assembly target. Thoughts?
No, this task should stay in place as it ensures the installation
directory actually contains the just built distribution and not some
remains from a previous build. So I'm for "Not
Brett Porter wrote:
It used to check the env var was correct before starting - I'm not sure why it
didn't in this case.
In case you refer to MNG-4352, that was applied after 2.2.1 was released.
Benjamin
-
To unsubscribe, e
Hi,
The vote has passed with the following result:
+1 (binding): Benjamin Bentmann, Vincent Siveton, John Casey, Jason van
Zyl, Hervé Boutemy, Arnaud Héritier, Lukas Theussl
+1 (non-binding): Kristian Rosenvold, Stephen Connolly
I will promote the artifacts to the central repository and cont
Hervé BOUTEMY wrote:
Le mardi 04 mai 2010, Dennis Lundberg a écrit :
Hi,
This is all great stuff, but we currently have two codebases to manage:
trunk and this branch. It would be good if refactorings like these could
wait until we have only one codebase to manage. I guess that you are not
pl
14 matches
Mail list logo
