I checked a lot, dependency looks correct to me. If i clean all project
and clean my local repository, then do jar:install on
shark-common
shark-struts
shark-taglib
shark-JNDI-users
then the target 'war' on shark-demoSite will fail telling it couldn't download
shark-viewer
If i go in shark-viewer, do a jar:install then go back to shark-demosite, the
war target is working properly. So to me the dependency is ok. I have no idea
what is wrong. I see nothing wrong in my pom, and except for the 'fail to
download shark-viewer-0.1.jar' when i didn't run jar:install in shark-viewer, i
get no error message!
any idea? Is reactor broken?
Alexandre Poitras a écrit :
>Usually when I have this kind of behaviour it is because I have made a
>typo somewhere in my poms (dependencies, modules or parent tags). From
>your output, I can't tell Maven is trying to download one of your
>project because it can't find it. Check carefully the output and see
>where the dependency resolution fails.
>
>On 3/2/06, David Delbecq <[EMAIL PROTECTED]> wrote:
>
>
>>Hello,
>>
>>maven multiproject use a reactor to do the compilation.
>>Usually, if i do a maven multiproject:install at the root, i get all
>>project compiled in the order of dependencies (a depends on b so
>>multiproject compile b before a). At least i have always seen this
>>behaviour.
>>However, today i discovered for one of my project, the reactor is
>>failing putting things in orders. Here are my subprojects with dependencies:
>>
>>shark-common
>>shark-struts depends on shark-common
>>shark-taglib depends on shark-common
>>shark-JNDI-users depends on shark-common
>>shark-demoSite depends on shark-common, shark-struts, shark-taglib,
>>shark-viewer
>>shark-viewer depends on shark-common
>>
>>They are expressed in the project.xml of each subproject with the following:
>>
>> <dependency>
>> <groupId>${pom.groupId}</groupId>
>> <artifactId>shark-common</artifactId>
>> <version>${pom.currentVersion}</version>
>> <type>jar</type>
>> </dependency>
>>
>>for shark-demoSite it's the form
>>
>> <dependency>
>> <groupId>${pom.groupId}</groupId>
>> <artifactId>shark-common</artifactId>
>> <version>${pom.currentVersion}</version>
>> <type>jar</type>
>> <properties>
>> <war.bundle>true</war.bundle>
>> </properties>
>> </dependency>
>>
>>all of the subprojects extends a root project, which itself extends a
>>master project.
>>So, for example, shark-demosite has project.xml extends ../project.xml
>>which extends ../Master/project.xml
>>
>>But when i do a multiproject:install i face this:
>>+----------------------------------------
>>| Executing multiproject:install-callback Shark-DemoSite
>>| Memory: 15M/22M
>>+----------------------------------------
>>Tentative de téléchargement de shark-viewer-0.1.jar.
>>ATTENTION: Impossible de télécharger shark-viewer-0.1.jar.
>>+----------------------------------------
>>| Executing multiproject:install-callback Shark-Viewer
>>| Memory: 9M/22M
>>+----------------------------------------
>>Shark-Viewer compiles ok and send it's .jar at the correct location. If
>>immediatly after i rerun multiproject:install, Shark-DemoSite compiles
>>and installs ok. This proves the Shark-Viewer is really building the
>>artifact Shark-DemoSite is needing. Why doesn't the reactor manage this????
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: [EMAIL PROTECTED]
>>For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>>
>>
>
>
>--
>Alexandre Poitras
>Québec, Canada
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: [EMAIL PROTECTED]
>For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
