I surely don't meet this problem, as my parent POM is not used by any
plugin (like assembly) during packaging.
So I don't have any clue but maybe to configure the assembly plugin in
the parent POM so that it's not called?
Or try to modify your project structure so that the parent POM is not
used by
Ping.
I still have this issue, and do not know where to begin to try to resolve
this...
Someone Please help
On 9/14/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime)
> [DEBUG] Retrieving parent-POM:
> org.apache.maven.wag
DEBUG] commons-cli:commons-cli:jar:1.0:runtime (selected for runtime)
[DEBUG] Retrieving parent-POM:
org.apache.maven.wagon:wagon-providers::1.0-alpha-6 for project:
null:wagon-ssh-external:jar:1.0-alpha-6 from the repository.
[DEBUG] Retrieving parent-POM: org.apache.maven.wagon:wagon::1.0-alp
This one is really killing me on the assembly part.
Any ideas anyone?
On 9/14/07, Mick Knutson <[EMAIL PROTECTED]> wrote:
>
> So what did you do with you master pom.xml for
> ../../..
>
> This seems to work except with my assembly that needs to use the filter as
> well. Then it complains about t
So what did you do with you master pom.xml for
../../..
This seems to work except with my assembly that needs to use the filter as
well. Then it complains about the master pom.xml not being able to find:
${parent.relativePath}/src/main/filters/filter-dev.properties
But besides that, this works
Hi Mick,
I personnaly had to define a different filter file regarding the
target environment, in my super POM :
...
../module1
...
...
${parent.relativePath}/src/main/filters/filter-${env}.properties
...
...
Each module defines the parent in its own
I am trying to make all my sub-modules use the same filter.properties like:
${project.root
}/src/main/filters/filter.properties
I keep getting this error:
[INFO]
[INFO] Error loading property
