The problem I ran into with this is that targetPath is relative to the
classes directory for jar and war packing types. So if you want your xml
files to go anywhere else Maven is just going to be way too helpful and
not let you. I gave up and used an ant task for copying. If there is a
way to
This is cool - very nice!
I'm using ant for an existing project that doesn't fit the Maven 2
lifecycle, directory structure, one artifact per pom, and versioning
"coventions". But I still would like to use the Maven repository and
dependencies. Antlib for maven looks like exactly what I nee
4:04 PM, Wendy Smoak wrote:
On 7/1/07, Paul Copeland <[EMAIL PROTECTED]> wrote:
Hm - following that link (which I had seen) there is a heading named
"Packaging". So if you examine the pom there is a element
(jar, war, pom, what are the others?) which is different from the
packa
I'm still interested in whether there is a way
to find out what lifecycles are available and what phases are part of
each lkind of ifecycle - for the pom packaging type I read there is only
the install and deploy phases for instance.
On 7/1/2007 2:31 PM, Wendy Smoak wrote:
On 7/1/07, Paul C
In pom below the objective is to copy the "specialres" resources
directory from src to target.
If the section of is commented out as shown nothing
gets copied although resources:resources runs twice. The log shows that
the execution named "resource-copy" ran first.
If the comments are remo
Is there a difinitive list of built-in m2 lifecycles? Does lifecycle ==
packaging type? Also is there a way to discover the phases that a given
lifecycle processes?
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Henry -
What maven packaging type would the ant project have in this case?
What would the ant project do in each phase of the first maven build?
How would the second maven project gain access to the products of the
first ant build?
On 6/26/2007 6:08 PM, Henry Isidro wrote:
Hi Shinjan,
You
ached
I need to run javadoc and then assemble the javadoc created uisng assembly
descriptor (cmp-client-javadoc.xml).
Thanks a lot,
Shankar.
Paul Copeland wrote:
I'm generating javado
It looks like the javadoc plugin always fires up Velocity for some some
reason. The only work around I can see to the two questions below is to
use the usual antrun to run the ant javadoc task.
On 6/20/2007 10:05 AM, Paul Copeland wrote:
Any thoughts on what the "Removing: javadoc from f
ems"
we've seen on this list can be "solved" with the Assembly plugin
and/or Antrun plugin.
Wayne
On 6/20/07, Paul Copeland <[EMAIL PROTECTED]> wrote:
So that's one vote for antRun for a the totally common need to copy
files.
I am also suspecting that behavior d
So that's one vote for antRun for a the totally common need to copy files.
I am also suspecting that behavior depends on the
type although I haven't tested that theory and this doesn't
seem to be documented anywhere.
On 6/20/2007 4:33 PM, Wendy Smoak wrote:
On 6/20/07
Trying to use to copy resource files to an arbitrary
target directory. The problem is that the resource phase insists on
copying to target/classes no matter what I have for targetPath.
This is the latest attempt - unfortunately it tried to copy to
target/classes/targetResources. Even if I a
ad?
On 6/19/2007 2:10 PM, Paul Copeland wrote:
I'm generating javadoc within a webapp context. I put the
maven-javadoc-plugin:javadoc goal into the package phase rather than
in the usual the generation lifecycle. It is doing the
right thing but I get this message -
[WARNING] Removin
rsive
invocation
Then I get a bunch of velocity messages (irrelevant for javadoc AFAIK)
Why do I get the message and can I get rid of velocity since this is a
plain vanilla javadoc tool run?
TIA - Paul Copeland, Jot Object Technologies http://www.jotobject
14 matches
Mail list logo
