Yes. I would actually like the deploy plugin to NOT deploy a
non-SNAPSHOT artifact if it is already there.
Oleg Gusakov wrote:
I cannot imagine a use case where you would check that artifact exists
in the remote repository and then don't download it. Can you?
--
I will rewrite the test to not depend on this method. Thanks everyone
replying!
Brett Porter wrote:
Wagon is resource oriented, rather than artifact oriented - this is
more equivalent to HEAD in HTTP. I don't see a need for it in artifact
handling as it would be determined by metadata. I can't
Wagon is resource oriented, rather than artifact oriented - this is
more equivalent to HEAD in HTTP. I don't see a need for it in artifact
handling as it would be determined by metadata. I can't think of
anywhere immediately that it would be used.
I think it makes sense to remove from the i
The Maven team is pleased to announce the release of the Maven Reactor
Plugin, version 1.0.
This plugin can build a subset of interdependent projects in a reactor. It
should be useful in large reactor builds that include irrelevant stuff
you're not working on.
http://maven.apache.org/plugi
I cannot imagine a use case where you would check that artifact exists
in the remote repository and then don't download it. Can you?
Brian E. Fox wrote:
Is there never a case that you care if it's there but don't want to download
it? It seems like the efficiency is in how it's used, rather tha
Is there never a case that you care if it's there but don't want to download
it? It seems like the efficiency is in how it's used, rather than the fact that
it exists.
-Original Message-
From: Oleg Gusakov [mailto:[EMAIL PROTECTED]
Sent: Saturday, September 27, 2008 6:33 PM
To: Maven De
Result of take 2 voting:
Binding +1: Dan Fabulich, Brett Porter, Jason Van Zyl
Vote passed.
-Dan
-- Forwarded message --
Date: Tue, 23 Sep 2008 13:27:12 -0700 (PDT)
From: Dan Fabulich <[EMAIL PROTECTED]>
Reply-To: Maven Developers List
To: Maven Developers List
Subject: [VOT
+1
On 27-Sep-08, at 6:33 PM, Oleg Gusakov wrote:
wagon API has a very strange method in it: resourceExists(). And
although it is optional -
org
.apache
.maven
.integrationtests
.MavenITmng3703ExecutionProjectWithRelativePathsTest
.testForkFromReport() fails if that method is not present
wagon API has a very strange method in it: resourceExists(). And
although it is optional -
org.apache.maven.integrationtests.MavenITmng3703ExecutionProjectWithRelativePathsTest.testForkFromReport()
fails if that method is not present.
Jan and I have been weighting pro and contra of this method
+1
On 27-Sep-08, at 6:16 PM, Dan Fabulich wrote:
Just need one more +1 binding...
-Dan
-Original Message-
From: Brett Porter <[EMAIL PROTECTED]
Date: Friday, Sep 26, 2008 7:38 am
Subject: Re: [VOTE] Release maven-reactor-plugin 1.0 (take 2)
To: Reply-"Maven Developers List" To:
"
Just need one more +1 binding...
-Dan
-Original Message-
From: Brett Porter <[EMAIL PROTECTED]
Date: Friday, Sep 26, 2008 7:38 am
Subject: Re: [VOTE] Release maven-reactor-plugin 1.0 (take 2)
To: Reply-"Maven Developers List" To: "Maven
Developers List"
+1 it is working well for me
Dear Reader,
I have developed plugin in maven. when executing that
plugin, value should pass to pom.xml
from plugin. bec i need to access the value in pom.xml (property) .
Any Idea Guide Me !!
--
View this message in context:
http://www.nabble.com/Doubt-in-
12 matches
Mail list logo
