WAS forceVersion for maven-install-plugin?
I'm looking at the remaining open issues in MINSTALL. This one
http://jira.codehaus.org/browse/MINSTALL-37 has had some unresolved
discussion in the past. For easy reading, please see here:
http://www.nabble.com/forceVersion-for-maven-install-plugin--
tf3341272s1
:30 PM
To: Maven Developers List
Subject: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?
I'm looking at the remaining open issues in MINSTALL. This one
http://jira.codehaus.org/browse/MINSTALL-37 has had some unresolved
discussion in the past. For easy reading, please see here
important to get feedback on
this.
Thanks
Brian
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Wednesday, May 02, 2007 8:30 PM
To: Maven Developers List
Subject: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-
plugin?
I'm looking at the remaining open
-37 WAS forceVersion for
maven-install-plugin?
I'm +1 on that one.
On 5/7/07, Brett Porter [EMAIL PROTECTED] wrote:
I thought I already replied, sorry. Anyway, it sounds like this is a
hack around the lack of ability to do something else, so I wouldn't be
in favour of it. I haven't seen anyone
:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 12:35 PM
To: Maven Developers List
Subject: Re: [VOTE] MINSTALL-37 WAS forceVersion for
maven-install-plugin?
I'm +1 on that one.
On 5/7/07, Brett Porter [EMAIL PROTECTED] wrote:
I thought I already replied, sorry. Anyway, it sounds like this is a
hack
: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?
I'm looking at the remaining open issues in MINSTALL. This one
http://jira.codehaus.org/browse/MINSTALL-37 has had some unresolved
discussion in the past. For easy reading, please see here:
http://www.nabble.com/forceVersion-for-maven
Yay forceVersion +1
--jason
-Original Message-
From: Brian E. Fox [EMAIL PROTECTED]
Date: Sun, 6 May 2007 21:54:42
To:Maven Developers List dev@maven.apache.org
Subject: [VOTE] MINSTALL-37 WAS forceVersion for maven-install-plugin?
I know many people where traveling last week
I'm looking at the remaining open issues in MINSTALL. This one
http://jira.codehaus.org/browse/MINSTALL-37 has had some unresolved
discussion in the past. For easy reading, please see here:
http://www.nabble.com/forceVersion-for-maven-install-plugin--tf3341272s1
77.html#a9292710
In summary, Jason
On May 2, 2007, at 5:30 PM, Brian E. Fox wrote:
I'm looking at the remaining open issues in MINSTALL. This one
http://jira.codehaus.org/browse/MINSTALL-37 has had some unresolved
discussion in the past. For easy reading, please see here:
http://www.nabble.com/forceVersion-for-maven-install
Its not really that close to install:install-file, since
install:install deals with attached artifacts as well as the primary
artifact. To get the same affect with install:install-file with a
project which has many attached artifacts, then you'd need to
configure an execute of
On May 2, 2007, at 7:09 PM, Brian E. Fox wrote:
Its not really that close to install:install-file, since
install:install deals with attached artifacts as well as the primary
artifact. To get the same affect with install:install-file with a
project which has many attached artifacts, then you'd
Kenny, when you get a chance I'd love to see an example of the maven-
it-plugin in action.
For now, I've just configured my projects to use install:install-
file, which appears to be working fine (at the cost of a bit more
complicated configuration).
--jason
On Mar 16, 2007, at 3:58 AM,
Ok, we've got different approaches here. I'll line them out to summarize:
Mine:
- use an integration testing plugin like maven-it-plugin to run test projects
placed in src/it/*/pom.xml against the current artifact, which is not installed
in any repository yet.
- The embedder is fed the
On Mar 16, 2007, at 3:58 AM, Kenney Westerhof wrote:
Ok, we've got different approaches here. I'll line them out to
summarize:
Mine:
- use an integration testing plugin like maven-it-plugin to run
test projects
placed in src/it/*/pom.xml against the current artifact, which is
not
Hrm... I though I replied to this mail hours ago... but looks like I
didn't...
Ok, we've got different approaches here. I'll line them out to
summarize:
I appreciate you taking the time :-)
Mine:
- use an integration testing plugin like maven-it-plugin to run
test projects
placed in
a 'forceVersion' to the
maven-install-plugin should solve this... and not introduce more
plugins to support/maintain.
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED
On Mar 15, 2007, at 2:38 AM, Kenney Westerhof wrote:
Jason Dillon wrote:
How does a test repository help? I still need to configure in my
src/it/*/pom.xml the version of the plugin I'm testing.
The latest plugin will be used, which is usually what you're testing.
If the test repository does
hardcoded plugin versions...
but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve this... and not introduce more plugins to
support/maintain.
--jason
PM
To: Maven Developers List
Subject: Re: forceVersion for maven-install-plugin?
Hrm... still no comments about this :-(
I'm going to try and whip up a patch for the maven-install-plugin to
implement this. And then hopefully someone will have a comment, or
maybe it will just get committed
they might do something along the
lines to allow src/it/**/pom.xml to not need hardcoded plugin
versions... but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve this... and not introduce more plugins
to support/maintain.
--jason
hardcoded plugin
versions... but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve this... and not introduce more plugins
to support/maintain.
--jason
it does... same thing with maven-
plug-it-plugin... both look like they might do something along the
lines to allow src/it/**/pom.xml to not need hardcoded plugin
versions... but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve
look like they might do something along
the lines to allow src/it/**/pom.xml to not need hardcoded plugin
versions... but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve this... and not introduce more
plugins to support
...
but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve this... and not introduce more plugins to
support/maintain.
--jason
-
To unsubscribe, e-mail: [EMAIL PROTECTED
they might do something along the lines
to allow src/it/**/pom.xml to not need hardcoded plugin versions...
but I really can't tell.
Anyways... I think simply adding a 'forceVersion' to the maven-
install-plugin should solve this... and not introduce more plugins to
support/maintain.
--jason
25 matches
Mail list logo
