Announcements: SBI 1.5.0 GA Released

[jeremyg484]

Well, typically you shouldn't need to build spring-flex-core yourself at all, unless you are trying to make changes to it. I would expect the more common case to be only importing and building the Test Drive, as that's the one we try to ensure works out-of-the-box.

That said, if you really do need to build spring-flex-core, then the easiest thing to do is go one level up (to the main spring-flex directory) and execute 'mvn install' from there. This will ensure the parent POM gets published to your local repo as well.

Alternatively, you can just point to the Spring milestones maven repo in your settings.xml.

[MikeOliverAZ]

The only reason I was building spring-flex-core was so that I could use it as a reference from other projects, and I had a similar problem after importing the testdrive sample.

I don't know what you mean by, "then the easiest thing to do is go one level up (to the main spring-flex directory)" as in the -dist, the spring-flex-core is in a directory all by itself and no pom in the directory above it anyplace.

I am trying to do mvn install in the samples/spring-flex-testdrive/

It does look like it is synching the M2_REPO so perhaps that will do the trick.

[jeremyg484]

I don't know what you mean by, "then the easiest thing to do is go one level up (to the main spring-flex directory)" as in the -dist, the spring-flex-core is in a directory all by itself and no pom in the directory above it anyplace.

Ahh right, sorry, I said that without actually looking at the distro. In that case you would either need to build from SVN, or point to the Spring milestones repo so that it will pull the parent pom.

[MikeOliverAZ]

Jeremy,

Added...

<repository>
<id>org.springframework.maven.milestone</id>
<name>Maven Central Compatible Spring Milestone Repository</name>
<url>http:// maven.springframework.org/milestone</url>
</repository>

to the spring-flex-core/pom.xml in STS and that triggered the maven synch, then I did a Maven Install in the "Run As" and it did its thing.

I guess my question is, why doesn't the distro have this in the pom already? Isn't that the only place to get the proper dependencies? I know that when it goes into production the milestones will be removed, but when you go into production release why not remove this from the pom on the final distro?

[jeremyg484]

See the top post for the release info for Spring BlazeDS Integration 1.5.0 GA.