There are several approaches, but first I'd ask, why do you hesitate to
install the Libraries to your local repository?
I'd say its perfectly fine that projects depending on each other still have
to be compiled independently.

If you want to compile them all in one rush a parent module would have to be
created, the ones of packaging type 'pom'.
Though I'm not sure that this parent module could be configured to compile
all three modules and run the web-app in one 'mvn jetty:run' call.

Also even when a parent module is set up each module still would be
installed into the local maven repository.
So it's just a decision of how tightly the modules should be knitted
together.
The best reason for a parent module is that it allows to manage the outbound
dependencies of the modules to other libraries.
Using the <dependencyManagement> element in the parent pom allows to define
the version of the libraries that the child projects should use.

mf

2008/2/24, Martin Makundi <[EMAIL PROTECTED]>:
>
> Hi!
>
> I have the following directory- and project structure:
>
> workspace/Wicket-Quickstart-App
> workspace/UtilityLibrary1
> workspace/UtilityLibrary2
>
> * UtilityLibrary1 depends on UtilityLibrary2
> * Wicket-Quickstart-App depends on both UtilityLibrary1 and
> UtilityLibrary2
>
> They compile just ok within Eclipse, but how can I deploy the
> projects? I am at prototyping stage and thus I do not want to install
> the subproject jars into maven repository. Instead, I want to deploy
> them as a single snapshot compiled directly from the sources. Is this
> possible?
>
> If I run mvn jetty:run in Wicket-Quickstart-App root, I get the
> following build error:
>
> [ERROR] BUILD ERROR
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Failed to resolve artifact.
>
> Missing:
> ----------
> 1) MyProject:UtilityLibrary2:jar:0.0.1
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=MyProject
> -DartifactId=UtilityLibrary2 \
>           -Dversion=0.0.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:       mvn deploy:deploy-file -DgroupId=MyProject
> -DartifactId=UtilityLibrary2 \
>           -Dversion=0.0.1 -Dpackaging=jar -Dfile=/path/to/file \
>            -Durl=[url] -DrepositoryId=[id]
>
>   Path to dependency:
>         1) MyProject:Wicket-Quickstart-App:war:0.0.1
>         2) MyProject:UtilityLibrary2:jar:0.0.1
>
> 2) MyProject:UtilityLibrary1:jar:0.0.1
>
>   Try downloading the file manually from the project website.
>
>   Then, install it using the command:
>       mvn install:install-file -DgroupId=MyProject
> -DartifactId=UtilityLibrary1 \
>           -Dversion=0.0.1 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file
> there:       mvn deploy:deploy-file -DgroupId=MyProject
> -DartifactId=UtilityLibrary1 \
>           -Dversion=0.0.1 -Dpackaging=jar -Dfile=/path/to/file \
>            -Durl=[url] -DrepositoryId=[id]
>
>   Path to dependency:
>         1) MyProject:Wicket-Quickstart-App:war:0.0.1
>         2) MyProject:UtilityLibrary1:jar:0.0.1
>
> ----------
> 2 required artifacts are missing.
>
> for artifact:
>   MyProject:Wicket-Quickstart-App:war:0.0.1
>
> Does anyone have experience from a similar "set up" and could help to
> configure my pom.xml files properly?
>
> t. Martin
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>

Reply via email to