On 7/23/07, Luciano Resende [EMAIL PROTECTED] wrote:
Any more inputs here ?
Maybe we could stage this in two phases, for now just make all project
consistent and pointing to version2-incubating/version as
suggested on this thread. And then continue discussions on pros/cons
of having multiple
Any more inputs here ?
Maybe we could stage this in two phases, for now just make all project
consistent and pointing to version2-incubating/version as
suggested on this thread. And then continue discussions on pros/cons
of having multiple poms, one for each sub-project.
Thoughts ?
On 7/17/07,
Doing a quick search on the code, looks like we have a combination of
parent pom references in our current trunk code.
Searching for: version2-incubating/version
cts\pom.xml(24): version2-incubating/version
sca\pom.xml(25): version2-incubating/version
sca\pom.xml(160):
On 7/17/07, Simon Laws [EMAIL PROTECTED] wrote:
On 7/17/07, Luciano Resende [EMAIL PROTECTED] wrote:
Doing a quick search on the code, looks like we have a combination of
parent pom references in our current trunk code.
Searching for: version2-incubating/version
cts\pom.xml(24):
ant elder wrote:
On 7/17/07, Simon Laws [EMAIL PROTECTED] wrote:
On 7/17/07, Luciano Resende [EMAIL PROTECTED] wrote:
Doing a quick search on the code, looks like we have a combination of
parent pom references in our current trunk code.
Searching for: version2-incubating/version
+1 for each subproject to have its own.. unless we want to consciously
tie in some commonality through this between the subprojects.
- Venkat
On 7/17/07, ant elder [EMAIL PROTECTED] wrote:
On 7/17/07, Simon Laws [EMAIL PROTECTED] wrote:
On 7/17/07, Luciano Resende [EMAIL PROTECTED] wrote:
My main reason for asking the question around version, is that we have
learned from past experiences that maven does NOT work OK when you
have projects with different versions on the reactor. Today, if you
have a clean repo, and try to build from java, build is failing trying
to download some
