[
https://issues.apache.org/jira/browse/KARAF-222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13950199#comment-13950199
]
Kurt Westerfeld commented on KARAF-222:
---------------------------------------
It may seem like a silly idea, but James was really looking for improving the
RAD experience for Karaf.
I've gotten a LOT of mileage out of simply mounting my maven output directories
directly using the felix (or is it pax-url) reference: URL mechanism. When I
do this, I rarely need to do more than simply update my bundle. I don't
deploy, and since the m2e plugin pushes java classes out to target/classes,
along with resources, I many times don't even need to change my bundle if I run
Karaf from within Eclipse. Does anyone use "reference:" ULRs with Karaf? I
only use them for manual installation of bundles, although I created Karaf
aliases to turn my distro into "dev" mode.
To me, using reference: URLs for my local bundles that I am hacking shortens
the edit/compile/debug cycle dramatically. I only wish I could build my whole
distribution with a features file that would accept reference:file: as
coordinates for the bundles, but alas the feature installer doesn't support
that. If this doesn't make sense, I can elaborate more. What I'd like to do
is build my whole distro with a -Pdev profile, which would create and expand a
customized Karaf distribution, installing my features mounted to the local
target/classes maven output directories of each of my bundles, and let it rip.
I would definitely use a karaf:run maven goal, as long as I could still debug
from within Eclipse, but many times there's issues with remote debugging, etc.
that prevents exec-ing from really improving the RAD experience.
Hope I'm making sense.
> Provide karaf:run, karaf:deploy, karaf:client Maven goals
> ---------------------------------------------------------
>
> Key: KARAF-222
> URL: https://issues.apache.org/jira/browse/KARAF-222
> Project: Karaf
> Issue Type: New Feature
> Components: karaf-tooling
> Reporter: james strachan
> Assignee: Jean-Baptiste Onofré
> Fix For: 2.4.0, 4.0.0, 2.3.5
>
> Attachments: KARAF-222-run-mojo-1.diff
>
>
> Did a quick google & couldn't see one yet - please close if there is one
> already :)
> The really nice thing about jetty:run is it watches the source code &
> target/classes dir & auto redeploys on change, so there's no deploy step -
> you just hack & compile (which your IDE or incremental compile can do - e.g.
> "mvn scala:cc").
> For added bonus would be being able to add some extra bundles, so it can be a
> RAD way to hack bundles. Maybe folks could have some integration junit tests
> automatically rerun whenever the bundle is redeployed?
--
This message was sent by Atlassian JIRA
(v6.2#6252)
