Can't build spring-music application

[lexsys27]

I want run spring-music application on lattice, so I try to pack it into docker container with cloud rocket. But when I fock up in spring-music directory I got an error:

/vagrant/spring-music$ fock up
Starting the CloudFocker container...
Running Buildpacks...
Started the CloudFocker container.
Deleting the CloudFocker container...
cloudfocker-staging
Deleted container.
2015/02/16 15:53:32  Staging failed - have you added a buildpack for this type of application?

I have already installed java buildpack.

$ fock buildpacks
java-buildpack

Application was built with ./gradlew assemble

[jtuchscherer]

I am seeing the same issue with a static HTML/JS/CSS app and the static buildpack:

$ fock up
Starting the CloudFocker container...
Running Buildpacks...
Started the CloudFocker container.
Deleting the CloudFocker container...
cloudfocker-staging
Deleted container.
2015/02/20 23:09:56  Staging failed - have you added a buildpack for this type of application?

$ fock buildpacks
staticfile-buildpack

The applications has a manifest.yml that points exactly to the same buildpack and works fine on CF.

[hatofmonkeys]

Hi to both of you!

Apologies for the long absence, we've had a few huge projects to deliver. I'm anticipating spending some time on this project between now and the CF Summit. Hopefully we can get some commercial support for this at some point and it can really take off.

For Java apps - the project should work if you explode the war and enter the exploded directory, and then build. The ability to work with an unexploded artefact is being tracked here https://www.pivotaltracker.com/story/show/81888786

For the static buildpack case - I haven't yet taken a look at how that buildpack interacts with CF but I believe it will be covered by this feature https://www.pivotaltracker.com/story/show/92252158

Feel free to issue pull requests if you'd like to add the features yourselves.

Colin

[jtuchscherer]

Ah, thanks @hatofmonkeys for the pointer. Triggering the normal buildpack detection mechanism by adding a Staticfile for the staticfile-buildpack worked like a charm.

Adding support for parsing the manifest.yml for buildpack detection seems not ideal to me. The manifests are written for CF. It would be confusing to know which values from the manifest apply to cloudrocker and which will be ignored.

I would prefer a command line option, e.g.:

rock up -b https://github.com/cloudfoundry/staticfile-buildpack