Wow it's much more expensive than it was 5 years ago:
https://zeroturnaround.com/software/jrebel/buy/
https://zeroturnaround.com/software/jrebel/buy/
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-and-JRebel-tp4033487p4033489.html
Sent from the Karaf - User mailing
ok thx didn't know about dev:watch.
--
View this message in context:
http://karaf.922171.n3.nabble.com/Karaf-and-JRebel-tp4033487p4033490.html
Sent from the Karaf - User mailing list archive at Nabble.com.
Hello,
sorry for answering late, but the hawtio console has a plugin for
visualizing bundle dependencies from a package and also a service
perspective.
These blog entries describe the plugin and also give you the pointers
into the code. The hawtio rendering just uses the underlying REST
In fact if you are using maven (which I think you are), you can use
something like:
felix.fileinstall.dir = /full/path/to/your/module-project/target/
Then, when even you modify any class and it gets compiled by your ID, karaf
will reload the module.
Another open source similar to
FYI, you can do quite the same with MBeans and Jolokia (directly).
EIK is also usable in Eclipse.
Programmatically, you can use the package/wiring service (it's what
show-tree does).
Regards
JB
On 06/13/2014 08:14 AM, Andreas Gies wrote:
Hello,
sorry for answering late, but the hawtio
As an addition, you can always use Spring beans with Aries-bp, as you would
do with any other bp bean.
The only thing you cannot do without spring-dm/gemini is the use of Spring
namespaces/annotations.
I'm pretty sure it's relatively easy to bridge annotation support
configuring the right Spring
2014-06-13 10:02 GMT+02:00 Charlie Mordant cmorda...@gmail.com:
As an addition, you can always use Spring beans with Aries-bp, as you
would do with any other bp bean.
There are two big limitations in Aries that makes reusing spring beans
difficult:
* FactoryBean are not supported
* type
Can't you use Aries bean 'factory-ref' and 'init-method' to implement
factorybeans?
I knew that post processors weren't supported, but never faced the
factorybean issue (maybe I didn't dealt with it).
2014-06-13 10:14 GMT+02:00 Guillaume Nodet gno...@apache.org:
2014-06-13 10:02 GMT+02:00
Hi,
I had the same problem and I solved it by configuring the
maven-resources-plugin to copy the resources into the target/assembly
directory.
Example:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
executions
execution
