switching to the next project???
M
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a9332007
Sent from the Maven - Users mailing list archive at Nabble.com
- install
subproject B - deploy
Should a project not go through the whole build lifecycle first before
switching to the next project???
M
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a9342521
Sent from
.
:: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: ::
::
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a9314490
Sent from
the whole build lifecycle first before
switching to the next project???
M
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a9316733
Sent from the Maven - Users mailing list archive at Nabble.com
subproject A - deploy
subproject B - install
subproject B - deploy
Should a project not go through the whole build lifecycle first before
switching to the next project???
M
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies
subproject B - deploy
Should a project not go through the whole build lifecycle first before
switching to the next project???
M
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8277154
Sent from the Maven - Users mailing list archive
???
M
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8278008
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED
On Wed, Jan 03, 2007 at 07:18:17PM -0500, Trevor Torrez spake thus:
Is it the suggested / best practice to have a subproject in a multi project
setup to declare it's dependencies on the other subprojects in the
dependency section?
Yes.
This leads to requiring some parts of the multi-project
Ok; just checking; so what is the point of having the maven-eclipse-plugin
generate dependencies on subprojects in eclipse (
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html#useProjectReferences),
since it has to get the artifacts from the repository anyway to successfully
Is it the suggested / best practice to have a subproject in a multi project
setup to declare it's dependencies on the other subprojects in the
dependency section? This leads to requiring some parts of the multi-project
to be installed to the local repository before other parts can be developed
). Or is there a better way?
--
View this message in context:
http://www.nabble.com/multi-project-interdependencies-tf2916882s177.html#a8154936
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e
11 matches
Mail list logo