On 11/04/11 5:15 PM, Andrus Adamchik wrote:
It did find the version till now. But I guess that was Maven 2.
Maven 2 just complains less.
Also I hope that doesn't affect behavior of the released versions of the
artifacts imported by other projects.
I'm not changing the dependencies, only how maven can find them when you build.
Now it finds them in the source and we don't need to install before building.
> But I remember that you didn't like that for a reason I can't remember.
The reason was that the end user apps need to import a bunch of garbage along
the parent pom dependency chain. Now it is just a single parent POM. I still
wish we could produce self contained cayenne-server and cayenne-client
artifacts.
Just another pom, no other jars, so the garbage is limited. But since every
maven project has the same parent/child thing going on, I don't think people
will care much.
Ari
--
-------------------------->
Aristedes Maniatis
GPG fingerprint CBFB 84B4 738D 4E87 5E5C 5EFA EF6A 7D2E 3E49 102A
