>though raising a github issue is the quickest way to communicate with folks on >hawtio Sure. I completely agree that using the Github issue list is the right place for raising an actual issue but seems somewhat awkward for asking questions.
So, even though I'm using the offline version of 1.2-M1 it keeps whining as shown below. jvm 1 | ERROR | Failed to pull from the remote git repo with credentials null. Reason: org.eclipse.jgit.api.errors.InvalidConfigurationException: No value for key remote.origin.url found in configuration jvm 1 | org.eclipse.jgit.api.errors.InvalidConfigurationException: No value for key remote.origin.url found in configuration jvm 1 | at org.eclipse.jgit.api.PullCommand.call(PullCommand.java:231) It also displays a warning on startup caused by some lower exception. Why is this? jvm 1 | INFO | Initialised an empty git configuration repo at /tmp/hawtio-6647093161915035773/config jvm 1 | WARN | Failed to startup blueprint container. org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean jvmList jvm 1 | org.osgi.service.blueprint.container.ComponentDefinitionException: Unable to intialize bean jvmList jvm 1 | at org.apache.aries.blueprint.container.BeanRecipe.runBeanProcInit(BeanRecipe.java:708) jvm 1 | at org.apache.aries.blueprint.container.BeanRecipe.internalCreate2(BeanRecipe.java:825) jvm 1 | at org.apache.aries.blueprint.container.BeanRecipe.internalCreate(BeanRecipe.java:786) jvm 1 | at org.apache.aries.blueprint.di.AbstractRecipe$1.call(AbstractRecipe.java:79) jvm 1 | at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334) jvm 1 | at java.util.concurrent.FutureTask.run(FutureTask.java:166) jvm 1 | at org.apache.aries.blueprint.di.AbstractRecipe.create(AbstractRecipe.java:88) jvm 1 | at org.apache.aries.blueprint.container.BlueprintRepository.createInstances(BlueprintRepository.java:245) jvm 1 | at org.apache.aries.blueprint.container.BlueprintRepository.createAll(BlueprintRepository.java:183) jvm 1 | at org.apache.aries.blueprint.container.BlueprintContainerImpl.instantiateEagerComponents(BlueprintContainerImpl.java:341) Thoughts on how to stop this? Thanks, Paul On Tue, Jul 2, 2013 at 5:14 AM, James Strachan <james.strac...@gmail.com> wrote: > Sorry you're having issues; though raising a github issue is the > quickest way to communicate with folks on hawtio (or bring it up here > too). Here's the current community links > http://hawt.io/community/index.html > > though we've not yet setup at google group - as so far github issues > have worked really well (much easier to keep track of and work with > than google groups so far); but if folks really really want a google > group we can spin one up; but so far we've found github issues tend to > be easier for folks to create, edit, open/close/comment on etc > > On 1 July 2013 23:18, Paul Gale <paul.n.g...@gmail.com> wrote: >> Does anyone know of if there's a dedicated mailing list for communicating >> with the committers of Hawt.IO? >> >> The only means of communication I can see are the issue list on the Github >> page and some IRC channel, neither of which are particularly useful. >> >> It seems a lot has changed with the latest download to the extent that it >> has issues working with ActiveMQ 5.8.0 without Karaf. 'Blueprint' >> exceptions all over the place. > > > > -- > James > ------- > Red Hat > > Email: jstra...@redhat.com > Web: http://fusesource.com > Twitter: jstrachan, fusenews > Blog: http://macstrac.blogspot.com/ > > Open Source Integration
