have a better developer mode when working on the core of fabric (e.g. fabric-core) so we don't have to keep rebuilding the distro... about fabric8 HOT 9 CLOSED

+1

from fabric8.

once a fabric's created, dev:watch * works a treat; its more for fabric creation really we need this

from fabric8.

dev:watch is something that generally works even without creating fabric, isn't that enough?

from fabric8.

@iocanel thanks!

I just tried it; there's a bug I'm working on in fabric-core; tried rebuilding it, stopped the fabric container; deleted data directory, started it up, did *dev:watch *" - it doesn't recognise I've rebuilt it.
It seems ordering is important; you have to stop, clear out and restart the fabric container then do 'dev:watch *" before doing any other builds for fabric-core? Unless its just some glitch here locally?

I'd prefer a dev mode which was a little less clumsy really; as right now I'm in a constant loop of

• hack code
• try create a fabric / child containers

and if feels a bit clumsy right now. I'll try persevere with dev:watch * though; and try get in the habit of restarting & dev:watch * first before building anything.

from fabric8.

hmm - dev:watch * did spot a recompile this time of fabric-core, but not fabric-api; "dev:watch *" does seem a little unreliable unless you are doing a build after you've typed "dev:watch *"

from fabric8.

ah - dev:watch * doesn't seem to help at all for creating child containers? even when the root container correctly recognises a rebuilt fabric-core, the old one is used in the child container

from fabric8.

wonder if there's a way to enable dev:watch * to be enabled by default in the local build of fabric; so it works on startup of both a root container and children?

from fabric8.

dev:watch command is something that only works on the local container.
The closest alternative we currently have that can propagate changes cluster-wide is fabric:profile-refresh (a command that will trigger the fabric-agent to all containers using this profile, resulting in the update of recent SNAPSHOT dependencies from the local maven repo).

Maybe we could work on combining the two in such a way that whenever we use dev:watch inside fabric, instead of updating the local bundles, we bump the profile to trigger the fabric-agent like profile-refresh does).

NOTE: Regardless of how we finally implement it, we should always be aware of the fact that some utility classes are not imported/exported but embeeded to the jars as private packages. In those cases just building the jar that hosts the utility classes will not help, untill we also build the jars that embeed those (example: ZooKeeperUtils).

from fabric8.

BTW we have fabric:watch * now too - which works across containers. Not sure it helps when you need to reload fabric-core though

from fabric8.