On 19 August 2013 13:19, James Carman wrote:
> I think you'd only see an issue building only a subproject if you had
> a fresh checkout/maven repository, but you'd have issues that way
> anyway.
Indeed, but that is a subject for a separate (long!) thread.
> The resolution of the parent pom usual
I think you'd only see an issue building only a subproject if you had
a fresh checkout/maven repository, but you'd have issues that way
anyway. The resolution of the parent pom usually occurs from the
repository by its "coordinates" (unless you use a relative path).
On Mon, Aug 19, 2013 at 8:07
On 19 August 2013 12:39, Torsten Curdt wrote:
> Probably a good idea. But does that affect building only a sub project?
All the sub-projects chain back to the shared parent pom.
> On Mon, Aug 19, 2013 at 12:56 PM, sebb wrote:
>> Would it make sense to list all the dependency versions in the par
Probably a good idea. But does that affect building only a sub project?
On Mon, Aug 19, 2013 at 12:56 PM, sebb wrote:
> Would it make sense to list all the dependency versions in the parent
> pom under dependencyManagement?
>
> Then the individual POMs would only need to list dependencies and not
Would it make sense to list all the dependency versions in the parent
pom under dependencyManagement?
Then the individual POMs would only need to list dependencies and not
their versions.
That would mean only one place to maintain the versions.
Make sense?
--
