The spring.jar for 2.0 M4 didn't include
org.springframework.orm.hibernate*. The one for M5 does. The
spring-hibernate3.jar for M4 included Hibernate dependencies, the one
for M5 does not. Which is the correct way moving forward? Which way
will it be in 2.0 Final?
Thanks,
Matt
-
hehe, I think you have wrote to the wrong list! you have to ask Spring
guys they are the official ones
and M5 is not missing dependencies, it doesn't have pom at all!
You can vote at
http://opensource.atlassian.com/projects/spring/browse/SPR-1484
I'm opening another thread to poing Maven users
The good news is I saw Rob Harrop and Juergen using maven 2 in an
example application for spring 2 (with the jetty6 plugin etc) at the
SpringOne conference, so they are aware of it. When I asked them about
it, they said that the spring build is huge and it won't be maven2ized
over night, but th
Can't they use the work that has been done in the Mergere book?
2006/6/20, Geoffrey De Smet <[EMAIL PROTECTED]>:
The good news is I saw Rob Harrop and Juergen using maven 2 in an
example application for spring 2 (with the jetty6 plugin etc) at the
SpringOne conference, so they are aware of it.
I have put updated poms in
http://opensource.atlassian.com/projects/spring/browse/SPR-1484 so
they can add them to CVS and people can help mantaining them.
After all that work I don't think is too difficult to build it with
Maven, as you say in the book you can build 2.0-m1.
The good news is tha
Here's what the Juergen had to say:
We tried a number of different jar file arrangements and eventually went
with the all-encompassing spring.jar for 2.0 M5, as alternative to a
combination of fine-grained jars from the "modules" directory. The mock jar
is still separate, sitting alongside eith
only one required, but all the others as optional
On 6/20/06, Matt Raible <[EMAIL PROTECTED]> wrote:
Here's what the Juergen had to say:
We tried a number of different jar file arrangements and eventually went
with the all-encompassing spring.jar for 2.0 M5, as alternative to a
combination of
Do optional dependencies have any effect at all, or are they purely
descriptive? Do they play a role in dependency version resolution,
for instance if they are the "nearest" source of a dependency? Are
there issues or wiki pages regarding the design of "optional" for
Maven 2.1?
(A bit off-topic
purely informative (at least for now)
that's why I encourage people to use the small jars that are more explicit
On 6/20/06, Stephen Duncan <[EMAIL PROTECTED]> wrote:
Do optional dependencies have any effect at all, or are they purely
descriptive? Do they play a role in dependency version reso
