On 10/26/06, Eric Redmond [EMAIL PROTECTED] wrote:
You are correct in the fact that adding an extensions element will only make
the extension available, but does not need that you need to use it. In any
case, Jeff, just add the ftp extension in the top-level build element, and
then define how
On 10/25/06, pjungwir [EMAIL PROTECTED] wrote:
Hi Jeff,
What is the benefit of loading wagon-ftp in a profile? That extensions
block doesn't per se do anything; it just makes wagon-ftp available. I guess
you're loading it for the sake of the sftp:// repository in the top-level
POM? Then why
I'm not positive, but I think that extensions block will just make
wagon-ftp available as it is needed. I think it's the maven-deploy-plugin
that does the work of picking what to send. But maybe someone with more
knowledge of multi-module builds can help?
Paul
Jeff Mutonho wrote:
On
You are correct in the fact that adding an extensions element will only make
the extension available, but does not need that you need to use it. In any
case, Jeff, just add the ftp extension in the top-level build element, and
then define how they are used (distributionManagement) in the
extensions are only valid under the main level build, not within a
profile's build. Note that the build element under profile is only a
subset of the build element under project.
Eric
On 10/25/06, Jeff Mutonho [EMAIL PROTECTED] wrote:
On 10/24/06, pjungwir [EMAIL PROTECTED] wrote:
Hi Jeff,
On 10/25/06, Eric Redmond [EMAIL PROTECTED] wrote:
extensions are only valid under the main level build, not within a
profile's build. Note that the build element under profile is only a
subset of the build element under project.
Eric
Alright.So since I have a profile , how should I do
No, you need to make a build section under the main project element -
completely unrelated to profiles. Think of it this way: profiles define how
you actually intend to build a project for a specific system, not the
mechanism by which you will upload to a remote server. At least, that's the
Hi Jeff,
What is the benefit of loading wagon-ftp in a profile? That extensions
block doesn't per se do anything; it just makes wagon-ftp available. I guess
you're loading it for the sake of the sftp:// repository in the top-level
POM? Then why not just put extensions up there, too (with no
On 10/23/06, Wayne Fay [EMAIL PROTECTED] wrote:
Fair enough, I hadn't noticed that.
I've only ever used extensions inside a plugin so I figured this
was the only valid place for it. Next time I'll have to check the
entire XSD and not assume... ;-)
In that case, I really have no idea why its
Hi Jeff,
Could you please post your whole pom, and also the version of maven you're
running?
Thanks,
Paul
Jeff Mutonho wrote:
On 10/23/06, Wayne Fay [EMAIL PROTECTED] wrote:
Fair enough, I hadn't noticed that.
I've only ever used extensions inside a plugin so I figured this
was the
Refer to the Maven XSD to see where to place extensions:
http://maven.apache.org/maven-v4_0_0.xsd
Hint: its a child node of plugin.
Wayne
On 10/23/06, Jeff Mutonho [EMAIL PROTECTED] wrote:
Hi there.
Where exactly do should I place the configuration,
extensions
extension
It appears to me from that schema that extensions is also a valid child of
build. This is where I'm using it, and it seems to work fine. Perhaps the
problem is using extensions in a module?
Paul
--
View this message in context:
Fair enough, I hadn't noticed that.
I've only ever used extensions inside a plugin so I figured this
was the only valid place for it. Next time I'll have to check the
entire XSD and not assume... ;-)
In that case, I really have no idea why its not recognized. Try moving
it under plugin just for
13 matches
Mail list logo
