Running sculptor 'out of the box'

[greatfooty]

Guys I'm still well in the newbie class but with a couple of weeks now just playing with sculptor examples etc. I am impressed with the product and am certain it has a bright future. Also looking forward to extending it etc

Whats surprised me though is the number of problems I've had in trying to trial the product and while I think the documentation is excellent I'd suggest that some effort is given to providing new adopters with a 'stable' ie. non-snapshot version of the product with which to learn and come up to speed.

For example (as per previous posting I've had dramas with rogue dependecies in mvn repo as followintg Patrik's suggestion I've just blown away entire maven repo and done mvn install on a small app I've (sculpted as per the archetype tutorial). All looked to be going great with heaps being redownoaded etc until the build complained it was unable to find:

org.springframework.webflow:org.springframework.faces:jar:2.0.7.RELEASE

I look in mvn central and within the fornax repo but no sign of it in there - only this:

    * 2.0.0.RELEASE/
    * 2.0.1.RELEASE/
    * 2.0.2.RELEASE/
    * 2.0.3.RELEASE/
    * 2.0.4.RELEASE/
    * 2.0.5.RELEASE/
    * maven-metadata-central.xml
    * maven-metadata-central.xml.md5
    * maven-metadata-central.xml.sha1
    * maven-metadata.xml
    * maven-metadata.xml.md5
    * maven-metadata.xml.sha1

Does this mean I need to know how to grab that dependency from somewhere else??

Note there's also a few others that aren't found, including:

com.sun.faces:com.springsource.com.sun.faces:jar:1.2.0.09
org.jboss.el:com.springsource.org.jboss.el:jar:2.0.0.GA

etc

Does this mean I should be including a few other repositories on my search path or manually installing from those repos (as per the mvn error message when the build fails)? eg. maybe including a spring repo and a jboss repo ???

[Patrik Nordwall]

The intention is that the dependencies should be working out of the box.

All needed repositories are defined in generated pom.xml of -parent project.
For example org.springframework.faces-2.0.7.RELEASE.jar should be downloaded like this...
Downloading: http://repository.springsource.com/maven/bundles/release/org/springframework/webflow/org.springframework.faces/2.0.7.RELEASE/org.springframework.faces-2.0.7.RELEASE.jar
1/137K
3/137K

I think you must have something strange in your maven installation.
Note that maven looks for settings.xml in <user home>/.m2/settings.xml and in <maven home>/conf/settings.xml
It is possible to define repositories in these files, but you should NOT do that. The repositories are defined in pom.xml of the -parent project (created by sculptor archetype).

Please verify.
/Patrik

greatfooty wrote:

Guys I'm still well in the newbie class but with a couple of weeks now just playing with sculptor examples etc. I am impressed with the product and am certain it has a bright future. Also looking forward to extending it etc

Whats surprised me though is the number of problems I've had in trying to trial the product and while I think the documentation is excellent I'd suggest that some effort is given to providing new adopters with a 'stable' ie. non-snapshot version of the product with which to learn and come up to speed.

For example (as per previous posting I've had dramas with rogue dependecies in mvn repo as followintg Patrik's suggestion I've just blown away entire maven repo and done mvn install on a small app I've (sculpted as per the archetype tutorial). All looked to be going great with heaps being redownoaded etc until the build complained it was unable to find:

org.springframework.webflow:org.springframework.faces:jar:2.0.7.RELEASE

I look in mvn central and within the fornax repo but no sign of it in there - only this:

    * 2.0.0.RELEASE/
    * 2.0.1.RELEASE/
    * 2.0.2.RELEASE/
    * 2.0.3.RELEASE/
    * 2.0.4.RELEASE/
    * 2.0.5.RELEASE/
    * maven-metadata-central.xml
    * maven-metadata-central.xml.md5
    * maven-metadata-central.xml.sha1
    * maven-metadata.xml
    * maven-metadata.xml.md5
    * maven-metadata.xml.sha1

Does this mean I need to know how to grab that dependency from somewhere else??

Note there's also a few others that aren't found, including:

com.sun.faces:com.springsource.com.sun.faces:jar:1.2.0.09
org.jboss.el:com.springsource.org.jboss.el:jar:2.0.0.GA

etc

Does this mean I should be including a few other repositories on my search path or manually installing from those repos (as per the mvn error message when the build fails)? eg. maybe including a spring repo and a jboss repo ???

[greatfooty]

Many thanks for this Patrik - I'm still coming to terms with Maven and I can see now as you mention in the -parent pom the list of repos that are needed.

We had configured a Nexus repository manager during past week to try avoiding the repeated download of same artefacts by different people and nexus obviously needs know about those other repositories. I'd been naive thinking everything needed for sculptor was within maven central and fornax.

It looks to be doing mvn install all fine now - thanks again