Hi,
JRE actually only supplies 1.0 of javax.annotation.
That's why the weld-feature in karaf-3.0.3 provides the bundle
mvn:javax.annotation/javax.annotation-api/1.2
You should use that bundle too, rather than modifying the version in
jre.properties.
kind regards,
Christoph
On 13/04/15 20:26,
+1
And as for third-party dependencies I think there are two possible
scenarios:
1) a library-upgrade fixes an issue that was already present in the
previous release:
-- screw it and postpone the lib-upgrade for the next-release
2) a library-upgrade causes a regression, i.e. a bug
Setting the start-level of hibernate-osgi to 100 (higher than all the
other bundles) worked for me
kind regards,
Christoph
On 2014-01-15 16:13, Dutertry Nicolas wrote:
I used version 3.3.2.GA available in Karaf 3.0.0.
I have also tested version 4.2.7 found here :
Hi,
Try adding
providerorg.apache.openjpa.persistence.PersistenceProviderImpl/provider
to your persistence-unit. I got a working setup with OpenJPA 2.3.0.
kind regards,
christoph
On 2014-01-14 12:01, Jean-Baptiste Onofré wrote:
Hi Nicolas,
could you try with OpenJPA 2.2.2 ? AFAIR it seems
The commands have been moved/renamed
osgi:list -- bundle:list
features:* -- feature:*
kind regards,
christoph
On 2013-05-09 13:58, skysw...@gmail.com wrote:
Hi,
I downloaded the karaf 3.0.0 RC1
but when I tried to run the osgi:list command the console returned
no osgi:list command. The
Hi JB,
Any update on karaf-3.0.0(.RC1)?
AFAICS the aries libs and pax-url have already been released.
regards,
christoph
On 2013-01-18 00:34, Jean-Baptiste Onofré wrote:
Hi Andrei,
A first artifact (Aries plugin) has been cut off yesterday and the vote
is in progress.
The other artifacts
Another hint:
pax-exam 2.6 requires ops4j-base 1.4 to work while pax-exam 2.4 uses
ops4j-base 1.3
Maybe you forgot to update some reference there.
regards,
christoph
On 2013-02-16 10:52, Dan Tran wrote:
your log still show you are using pax-exam 2.4
-D
On Sat, Feb 16, 2013 at 1:48 AM,
Hi Dan,
What's the start-level of your bundles?
I think I remember encountering this issue with bundles that started
before aries-stuff.
kind regards,
christoph
On 2013-02-10 23:22, Dan Tran wrote:
H JB,
I rebuild karaf-2.3.1-SNAPSHOT using aries.jpa 1.0.0 ( ie with
When using maven, you can use
bundle:watch bundle-id
or
bundle:watch *
and just call mvn install on your project. The watcher detects the
change in your local .m2 and updates the artifact.
kind regards,
christoph
On 2013-02-06 22:19, Jason wrote:
All,
This worked
Uninstall the
Some classes are loaded at runtime using reflection etc., so that the
bundle-plugin does not pick it up. Not sure why the * at the end is
missing though.
The import-list in the wiki often has to be extended depending on your
application (e.g. if you need authentication).
kind regards,
According to the homepage [1] it's actually public domain.
kind regards,
christoph
[1] http://aopalliance.sourceforge.net/
On 2013-02-03 20:13, Jean-Baptiste Onofré wrote:
AFAIR, it's a dual license.
On 02/03/2013 07:59 PM, Dan Tran wrote:
Super thanks for removing that
-D
Btw,
I think this happens mostly on clean local .m2-repos.
Here's a link to the original issue (which contains a patch)
kind regards,
christoph
On 2013-01-08 11:38, Michael Szalay wrote:
Yes, adding this
dependencyManagement
dependencies
dependency
regards,
christoph
On 22/10/12 15:33, Giacomo Coletta wrote:
The build fails because of the error and there is no target directory at
all.
2012/10/22 Christoph Gritschenberger christoph.gritschenber...@gmail.com
And is the file actually not there?
Is it nowhere in the target-directory
You need to enable resource-filtering in your maven-build. You can set
this up in your pom.xml like this:
...
build
resources
resource
directory${project.basedir}/src/main/filtered-resources/directory
filteringtrue/filtering
includes
include**/*/include
I can confirm that karaf 2.2.9 fixed our issues with jre 6u33+.
kind regards,
christoph
On 09/10/12 14:16, Achim Nierbeck wrote:
Hi Bengt,
to my knowledge Karaf 2.2.9 uses a 0.3.1 (or higher) which also
includes the corresponding Bug-Fix and therefore should work.
regards, Achim
Hi,
There seems to be some race-condition in aries there. Something similar
has been reported previously [1] [2].
I think we were able to fix it by synchronizing entity-manager-access
with synchronized-blocks
synchronized(entityManager){
entityManager.merge(...);
}
kind regards,
Hi,
I noticed that the 2.2.9-SNAPSHOT and 2.3.0-SNAPSHOT in the
apache-snapshot-repository [1] are quite outdated, although builds on
builds.apache.org were stable.
Jamie Goodyear pointed out to me in IRC that auto-deploy was turned off
as there was infra problems at the time.
Would it be
Hi,
I ran into an Error when I tried to run karaf on a Windows XP with
Oracle JRE 7u5 installed.
Error: missing `server' JVM at `C:\Programme\Java\jre7\bin\server\jvm.dll'.
Please install or use the JRE or JDK that contains these missing components.
I then discovered that the
What exactly are you trying to do?
You want to execute junit-tests that always launch a clean karaf instance?
You can do this with pax-exam [1] and pax-exam-karaf.
kind regards,
christoph
[1] http://team.ops4j.org/wiki/display/paxexam/Pax+Exam
[2]
If you just like to debug, you can enable remote-debugging in karaf by
setting the KARAF_DEBUG env-variable.
export KARAF_DEBUG=true
bin/karaf
You can then connect your debugger to port 5005.
The downside of this approach is that runtime code-editing is very limited.
Is this what you are
Hi,
We recently started using Weaving Hooks in our Project (running in
karaf-3.0.0-SNAPSHOT) and ran into a Problem:
When deploying a bundle using the deploy-directory the bundle might get
installed before the weaving hook is active. This causes the bundle to
remain unweaved.
We described the
21 matches
Mail list logo
