Wendy Smoak wrote:
On 7/13/06, Brett Porter <[EMAIL PROTECTED]> wrote:
For right now, everything works, but to use the next release of the
plugin plugin, you need the next release of Maven (however, the previous
version will of course continue to work and could be branched). That is,
those livi
Wendy Smoak wrote:
On 7/13/06, Brett Porter <[EMAIL PROTECTED]> wrote:
For right now, everything works, but to use the next release of the
plugin plugin, you need the next release of Maven (however, the previous
version will of course continue to work and could be branched). That is,
those livi
On 7/13/06, Brett Porter <[EMAIL PROTECTED]> wrote:
For right now, everything works, but to use the next release of the
plugin plugin, you need the next release of Maven (however, the previous
version will of course continue to work and could be branched). That is,
those living on the edge just
There's a few things going on here:
- the plugin report uses the plugin tools, which really shouldn't be in
the Maven release cycle since they are really independant (but they are
there to make bootstrap possible without the shared SVN repo)
- the plugin descriptor generator uses the model th
2006 11:55 AM
To: Maven Developers List
Subject: Re: Plugins can't be built!
Dennis Lundberg wrote:
Brett Porter wrote:
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was
---
Hermod
-Original Message-
From: Trygve Laugstøl [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 13, 2006 11:55 AM
To: Maven Developers List
Subject: Re: Plugins can't be built!
Dennis Lundberg wrote:
> Brett Porter wrote:
>
>> This shouldn't
Dennis Lundberg wrote:
Brett Porter wrote:
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was updated to use the new tools and such. However,
it also has a prereq of maven 2.0.5, so maven
Dennis Lundberg wrote:
Brett Porter wrote:
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was updated to use the new tools and such. However,
it also has a prereq of maven 2.0.5, so maven
Brett Porter wrote:
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was updated to use the new tools and such. However, it
also has a prereq of maven 2.0.5, so maven 2.0.4 and below which gi
This shouldn't have broken - needs investigation.
A while back, we agreed to add a feature to 2.0.5 (the implementation
attribute).
The plugin plugin was updated to use the new tools and such. However, it
also has a prereq of maven 2.0.5, so maven 2.0.4 and below which give
this error should
I remember submitting patches to maven-plugin-tools-java and
maven-plugin-tools-api to reformat the plugin parameter pages... those
updates could be them.
^_^
Dennis Lundberg wrote:
I went back and checked my session to see what happened just before
things stopped working. Here's what I fo
I went back and checked my session to see what happened just before
things stopped working. Here's what I found:
Downloading:
http://svn.apache.org/maven-snapshot-repository/org/apache/maven/maven-plugin-tools-java/2.0.5-SNAPSHOT/maven-plugin-tools-java-2.0.5-20060712.135652-2.jar
10K download
Hi,
I have seen this one ... long time ago!
Can you rename/remove the folder that maps to "org.apache.maven "
groupId in your local repo, and try building again. I think its coming
from an old version of a library
Cheers,
Rahul
Dennis Lundberg wrote:
Hi all
Someone seems to have broken
Hi all
Someone seems to have broken something in the trunk. A lot of plugins
are failing in continuum. They all have similar error messages. Does
anyone know what might be wrong?
I get the same error when I try to build the plugins locally. I'm not
sure if this is true for all plugins, but t
14 matches
Mail list logo
