Re: 4.2.0 karaf-assembly missing spring?

Hi Nino, the spring "old" versions moved in spring-legacy features repository. So, you have to add spring-legacy repo: mvn:org.apache.karaf.features/spring-legacy/4.2.0/xml/features Regards JB On 10/04/2018 07:50, nino martinez wael wrote: Hi when I try to use below i get this error:

4.2.0 karaf-assembly missing spring?

Hi when I try to use below i get this error: *[ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.0:assembly (default-assembly) on project ccadmin-karaf-assembly: Unable to build assembly: Could not find matching feature for spring/[3,4) -> [Help 1]* *[ERROR]* *I

Re: Assembly Issue

Hi Greg, you said 4.0.10 for Karaf version (in the Jira). It's also the Karaf maven plugin version right ? Thanks ! Regards JB On 04/10/2018 12:34 AM, Greg Logan wrote: > Filed at https://jira.apache.org/jira/browse/KARAF-5693, with attached build > logs and .properties files. > > The assembly

Re: Assembly Issue

Filed at https://jira.apache.org/jira/browse/KARAF-5693, with attached build logs and .properties files. The assembly doesn't seem to matter, although we definitely notice it more with allinone since that's the one that gets used for testing mainly! G On Mon, Apr 9, 2018 at 3:54 PM, Guillaume

Re: Assembly Issue

Fwiw, one possible suspect is the following code: https://github.com/apache/karaf/blob/master/profile/src/main/java/org/apache/karaf/profile/assembly/Builder.java#L1484-L1497 The access to the config properties are not synchronized. 2018-04-09 23:54 GMT+02:00 Guillaume Nodet :

Re: Assembly Issue

2018-04-09 23:38 GMT+02:00 Greg Logan : > Hi all, > > Building Opencast (https://github.com/opencast/opencast), our final step > is packaging into assemblies (assemblies/pom.xml). Since I haven't seen > this elsewhere it's hard to really give you a small reproducible

Re: Assembly Issue

Hi all, Building Opencast (https://github.com/opencast/opencast), our final step is packaging into assemblies (assemblies/pom.xml). Since I haven't seen this elsewhere it's hard to really give you a small reproducible test case, but at least it's part of the final steps rather than requiring a

Re: Assembly Issue

It may be a thread issue while building the assembly. Please raise a JIRA and attach what you have, a way to reproduce the issue would be helpful. Guillaume 2018-04-09 19:15 GMT+02:00 Greg Logan : > Hi all, > > We're running into an issue where rarely (1/20 or so) of

Re: karaf with Java 9/10

Hi, Yeah, some users reported that the tokenizer that extracts the JAVA_VERSION (that we test to check if it's Java 9/10 or Java 7/8) was not set. I was not able to reproduce the issue on my Windows VM. I gonna try with another VM. Regards JB On 09/04/2018 19:00, Leschke, Scott wrote: I

Re: Assembly Issue

Hi Greg, never had this issue. Can you share a test case to take a look ? Regards JB On 09/04/2018 19:15, Greg Logan wrote: Hi all, We're running into an issue where rarely (1/20 or so) of our assembly builds end up with a corrupted config.properties file - multiple libraries are missing

Assembly Issue

Hi all, We're running into an issue where rarely (1/20 or so) of our assembly builds end up with a corrupted config.properties file - multiple libraries are missing from the file and thus our code fails to start because the dependencies are missing. I took a quick look through JIRA and could not

RE: karaf with Java 9/10

I am. That's what I'm using, karaf.bat. -Original Message- From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] Sent: Monday, April 09, 2018 11:59 AM To: user@karaf.apache.org Subject: Re: karaf with Java 9/10 Hi, I guess you are on Windows ? Because the karaf.bat|karaf.sh should

Re: karaf with Java 9/10

Hi, I guess you are on Windows ? Because the karaf.bat|karaf.sh should deal with JVM version to use endorsed or not. Regards JB On 09/04/2018 18:51, Leschke, Scott wrote: */Blah..blah..…lib\endorsed is not supported. Endorsed standards and standalone APIs in modular form will be supported

karaf with Java 9/10

Blah..blah.lib\endorsed is not supported. Endorsed standards and standalone APIs in modular form will be supported in the form of upgradeable modules. Error: Could not create the JVM. Error: A fatal exception has occurred. Program will exit. Didn't see anything in the docs about this. What