On 22 Jul 2008, Taras Lipatov wrote:
> Thanks for the info!!
>
> So I guess I have an odd-ball case with my artifacts..
> Here is the full scenario.
> I have a project with 2 modules:
>
> `-- project-parent
> |-- pom.xml
> |-- core
> | `-- pom.xml
> `-- webapp
> `-- pom
Thanks for the suggestion,
How ever, the module only seems to attach the .zip to the life-cycle for
install/deploy and it is still not resolving in the module..
so my layout is:
project-parent
- core
-webapp
module core generates: org.my.group:core-1.0.0-SNAPSHOT.zip using the
assembly plugin.
You should use the maven build-helper plugin (
http://mojo.codehaus.org/build-helper-maven-plugin) in order to attach the
zip artifact to your JAR pom so that Maven is aware of it and can build
pacefully.
Jeff MAURY
On 7/22/08, Taras Lipatov <[EMAIL PROTECTED]> wrote:
>
> Thanks for the info!!
>
Thanks for the info!!
So I guess I have an odd-ball case with my artifacts..
Here is the full scenario.
I have a project with 2 modules:
`-- project-parent
|-- pom.xml
|-- core
| `-- pom.xml
`-- webapp
`-- pom.xml
project-parent:
- packaging pom
core:
- artifact: cor
Hi!
On 21 Jul 2008, Taras Lipatov wrote:
> Does any one know,
>
> when releasing a multi-module project from the project parent..
>
> I have two modules: "core" and "webapp"
>
> "core" module is version 1.0.0-SNAPSHOT
> "webapp" has a dependency on "core:1.0.0-SNAPSHOT"
>
> When running rele
Does any one know,
when releasing a multi-module project from the project parent..
I have two modules: "core" and "webapp"
"core" module is version 1.0.0-SNAPSHOT
"webapp" has a dependency on "core:1.0.0-SNAPSHOT"
When running release:prepare...
"webapp" pom is transformed and dependency "core
