On 04/03/2007, at 1:51 AM, Dennis Lundberg wrote:
Is that because maven-plugin-descriptor-2.0.5.jar is in M2_HOME/lib ?
yes
How does plugin updates work in a situation like this? Say we have
a user that is running maven 2.0.4. He/she issues "mvn -U site" on
a project that requires mave
Is that because maven-plugin-descriptor-2.0.5.jar is in M2_HOME/lib ?
How does plugin updates work in a situation like this? Say we have a
user that is running maven 2.0.4. He/she issues "mvn -U site" on a
project that requires maven-plugin-plugin-2.3, which in turn has 2.0.5
as a prerequisite
The plugin plugin wil also need a on 2.0.5, but other
than that this looks fine.
- Brett
On 03/03/2007, at 1:06 PM, Dennis Lundberg wrote:
Hi
When I was working on the site for the release plugin, something
hit me:
Where did that "@since" support for plugins go that we put into
maven 2
Dennis Lundberg wrote:
Hi
When I was working on the site for the release plugin, something hit me:
Where did that "@since" support for plugins go that we put into maven
2.0.5?
Here's an example of how this will look:
http://maven.apache.org/plugins/maven-release-plugin/rollback-mojo.html
Hi
When I was working on the site for the release plugin, something hit me:
Where did that "@since" support for plugins go that we put into maven 2.0.5?
So I dug into the code only to find that there is more work to be done
before this is usable.
First we need to get a new version of maven-pl
