Hi,
I am busy with migrate our codebase from Karaf 2.3.x to 4.0.4. In 2.3.x we
use Equinox as framework and we want to use Felix (5.4) in 4.0.4.
Some legacy code (bundle) with split packages use the Require-Bundle and
Bundle-ClassPath header, but it looks like the Bundle-ClassPath is ignored.
The
Hello,
why is it not possible to build the karaf source code? If I download the
src for 4.0.7 or checkout the tag and try to build karaf with mvn
-Pfastinstall I always get the output below. It seems that there are
missing dependencies on apache.commons. What do I wrong?
Regards,
Thomas
[ERROR]
Hi Thomas,
Can you try mvn clean install -DskipTests ?
Regards
JB
On 10/14/2016 01:47 PM, Thomas Termin wrote:
Hello,
why is it not possible to build the karaf source code? If I download the
src for 4.0.7 or checkout the tag and try to build karaf with mvn
-Pfastinstall I always get the outpu
What java and maven versions do you use?
Christian
On 14.10.2016 13:47, Thomas Termin wrote:
Hello,
why is it not possible to build the karaf source code? If I download
the src for 4.0.7 or checkout the tag and try to build karaf with mvn
-Pfastinstall I always get the output below. It seems
@Jean-Baptiste
mvn clean install -DskipTests results in:
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.785 s
[INFO] Finished at: 2016-10-14T14:06:08+02:00
[INFO] Final Memory: 76M/383M
[INFO]
--
Hi Thomas,
you have some "created" file without license, that's why it fails on RAT.
I just tried purging my local ~/.m2/repository/org/apache/karaf and
~/.m2/repository/commons-*
with Maven 3.3.9 and Java 8.
And it works fine.
Do you have some Maven or HTTP proxy ?
Regards
JB
On 10/14/20
Hi SvS,
I would file a bug with Felix [1] ideally with a small testcase attached.
The most likely thing is that there is some typo or other malformatting
issue. The Bundle-ClassPath is tested by the OSGi CT and Felix passes that.
So the best thing would be a small testcase to reproduce it. Then it
I just ran this with no problems.
git checkout karaf-4.0.7
mvn clean install -DskipTests
mvn -v
Apache Maven 3.2.5 (12a6b3acb947671f09b81f49094c53f426d8cea1;
2014-12-14T18:29:23+01:00)
Maven home: /home/cschneider/java/apache-maven-3.2.5
Java version: 1.8.0_92, vendor: Oracle Corporation
Java
I suggest that you actually look at the RAT output file and see of
what it complains.
On Fri, Oct 14, 2016 at 8:30 AM, Christian Schneider
wrote:
> I just ran this with no problems.
>
> git checkout karaf-4.0.7
> mvn clean install -DskipTests
>
> mvn -v
> Apache Maven 3.2.5 (12a6b3acb947671f09b81
First off all thanks for the quick responses.
@Benson
RAT complains about missing apache license header within the files:
tooling/karaf-maven-plugin/src/main/java/org/apache/karaf/tooling/utils/LocalDependency.java
jaas/modules/src/main/java/org/apache/karaf/jaas/modules/krb5/Krb5LoginModule.jav
Hi Thomas,
I don't explain:
1. Rat output is correct, but rat is executed only if you build with the
rat profile, so something like:
mvn clean install -Prat
Do you build with this profile ?
2. You can bypass the maven test (invoker) using -Dinvoker.skip:
mvn clean install -DskipTests -Dinv
By the way, the failing karaf test are excluded by default:
test-run/pom.xml
test-assembly/pom.xml
test-check-dependencies-failure/pom.xml
test-assembly-prop-edits/pom.xml
So, you are not running a "regul
The failing tests are excluded in the current master branch but not in the
karaf-4.0.x branch and not in the karaf-4.0.7 tag.
> Am 14.10.2016 um 15:29 schrieb Jean-Baptiste Onofré :
>
> By the way, the failing karaf test are excluded by default:
>
>
>
Correct for the branch. I will apply.
But anyway, they should not failed (it doesn't fail).
What's the cause ?
Regards
JB
On 10/14/2016 04:01 PM, Thomas Termin wrote:
The failing tests are excluded in the current master branch but not in the
karaf-4.0.x branch and not in the karaf-4.0.7 tag.
Karaf 3.0.6
When I run "bundle:info 222" I don't see the file location of the loaded
JAR. When I view the bundle.info file's contents in data/cache/bundle222, I
do see it (e.g. file:/path/to/file/myJar.jar). Is it planned to add this
info for the output of the "bundle:info" cmd? Or is there a r
Related issue I just noticed which was causing problems during Eclipse
debugger session (hitting wrong lines when I'm stepping through the code for
a particular bundle's class, etc.)
When I issue "update 223 file:/path/to/jar/foo.jar" I'm still seeing the mvn
repo location in the bundle 223's bund
16 matches
Mail list logo