To: Maven Users List
Subject: [IMPORTANT] Maven 2 Plugin Auto-Versioning Considered Dangerous
Hi everyone,
I wanted to send out a quick email to let everyone know about some
discussion that's been taking place on the developers' list regarding
plugin
versions. In trying to release the 2.2
Did you file a jira issue for this? If your assembly broke, then I'm
assuming there was some behavior change from 2.1 - 2.2-beta-1 that got you
in trouble...I think that even if we're not going to fix it, we should have
some doco for it...
So, would you file a JIRA for this?
Thanks,
john
On
On 4/15/07, John Casey [EMAIL PROTECTED] wrote:
Did you file a jira issue for this? If your assembly broke, then I'm
assuming there was some behavior change from 2.1 - 2.2-beta-1 that got you
in trouble...I think that even if we're not going to fix it, we should have
some doco for it...
So,
On 4/11/07, John Casey [EMAIL PROTECTED] wrote:
snip
I'm sure many people have hit this plugin-versioning problem before...
snip
The first time this has really bit me in the rear is when the assembly
plugin 2.2-beta-1 hit central, and my formerly working assembly went
all to hell. Almost like
:[EMAIL PROTECTED]
Sent: den 11 april 2007 18:19
To: Maven Users List
Subject: [IMPORTANT] Maven 2 Plugin Auto-Versioning Considered Dangerous
Hi everyone,
I wanted to send out a quick email to let everyone know about some
discussion that's been taking place on the developers' list regarding plugin
reproducibility.
Peter
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: den 11 april 2007 18:19
To: Maven Users List
Subject: [IMPORTANT] Maven 2 Plugin Auto-Versioning Considered Dangerous
Hi everyone,
I wanted to send out a quick email to let everyone know about
PROTECTED]
Sent: Thursday, April 12, 2007 3:14 AM
To: Maven Users List
Subject: Re: [IMPORTANT] Maven 2 Plugin Auto-Versioning Considered
Dangerous
That makes a lot of sense.
On 4/12/07, Peter Nilsson [EMAIL PROTECTED] wrote:
The auto-resolver is a pain when using Maven in a corporate
environment
: Thierry Lach [mailto:[EMAIL PROTECTED]
Sent: Thursday, April 12, 2007 3:14 AM
To: Maven Users List
Subject: Re: [IMPORTANT] Maven 2 Plugin Auto-Versioning Considered
Dangerous
That makes a lot of sense.
On 4/12/07, Peter Nilsson [EMAIL PROTECTED] wrote:
The auto-resolver is a pain when using Maven
Hi everyone,
I wanted to send out a quick email to let everyone know about some
discussion that's been taking place on the developers' list regarding plugin
versions. In trying to release the 2.2-beta-1 version of the assembly
plugin, it became apparent that this version fixes some bugs in the
I agree, automatic resolution of plugin versions is dangerous and you
must use versions if you want reproducible builds. it's easy to add
them to your parent pom in the pluginManagement section
On 4/11/07, John Casey [EMAIL PROTECTED] wrote:
Hi everyone,
I wanted to send out a quick email to
Don't forget you use a lot more plugins than you think. Who specifies
versions for resources; compiler, surefire, install, deploy, clean,
... ?
Maybe we need a plugin that can rewrite your POMs to specify versions
for all the plugins that are used ?
Tom
On 4/11/07, Carlos Sanchez [EMAIL
I think that sort of plugin would be a great idea. For the plugins in the
standard packaging lifecycles (to which you're referring, I believe), I
still think that Maven should force you to supply a version for each one. It
might make sense to have a version-set dependency or artifact that you can
Don't forget you use a lot more plugins than you think. Who specifies
versions for resources; compiler, surefire, install, deploy, clean, ...
?
Maybe we need a plugin that can rewrite your POMs to specify versions
for all the plugins that are used ?
I agree entirely. While the automatic
I would think most corporate users have run into this already.. I know we
have :) I've been saying people still need to know and understand which
plugins and versions they are using and why, even if Maven makes it nice and
automated. Sorry for OT, but since you mentioned - what's going on with
The assembly plugin release goes to an rsync-staging repository before it's
shunted on to repo1. It usually takes a couple hours to make it all the way
out into the open.
I'm sure many people have hit this plugin-versioning problem before, and I
know that versioning everything is a huge pain in
Two more ideas:
- Versioned lifecycles. Let a version of a lifecycle map to versions
of each of its plugins. Allow users to override these by specifying
explicit versions for the plugins. If you don't specify a version for
the packaging, you get the old behaviour.
- Have the
please move development discussions to maven-dev, there's already a
thread about it there.
On 4/11/07, Tom Huybrechts [EMAIL PROTECTED] wrote:
Two more ideas:
- Versioned lifecycles. Let a version of a lifecycle map to versions
of each of its plugins. Allow users to override these by specifying
On 4/12/07, John Casey [EMAIL PROTECTED] wrote:
Here's an example:
[del]
Having created this project with its assembly descriptor, but WITHOUT A
VERSION IN THE ASSEMBLY PLUGIN DECLARATION, I commit my project. Now, some
time later, after the next version of the assembly plugin fixes this bug,
18 matches
Mail list logo
