FW: Change in behaviour of karaf-maven-plugin w.r.t. dependencies for feature packaging between 4.0.x and 4.1.x
Hello, With updating to Karaf 4.1.1 I have found a change in behaviour in the karaf-maven-plugin seemingly no longer adding bundles from POM dependencies. I have put a testcase up at https://github.com/arunan-interlink/karaf-maven-plugin-features-change that demonstrates the issue. Changing the version of karaf-maven-plugin used in the top level POM shows the different behaviours in the output feature file. Has anybody else had similar issues? Has anybody else started using the 4.1.x Maven plugins and had this work? My apologies if I have missed a release note, existing issue or if this is an incorrect configuration. Regards, Arunan
RE: FW: Change in behaviour of karaf-maven-plugin w.r.t. dependencies for feature packaging between 4.0.x and 4.1.x
Hi Guillaume, Thanks for the reference, much appreciated. Looks like https://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/developer-guide/karaf-maven-plugin.adoc could do with an update at least regarding karaf:features-generate-descriptor . I would volunteer a patch but I don't know what the right updates are, sorry. And generally, thanks to everybody for Karaf, I've been using it for a year and really enjoying it. Arunan From: Guillaume Nodet [mailto:gno...@apache.org] Sent: 12 April 2017 15:49 To: user Subject: Re: FW: Change in behaviour of karaf-maven-plugin w.r.t. dependencies for feature packaging between 4.0.x and 4.1.x Didn't we discussed that on dev@ a while ago ? The thread is named "[DISCUSS] Feature package, feature generation and validation", started on 13/10/2016. IIRC, the outcome was to remove the ‘feature-generate-descriptor’ goal from the ‘feature’ packaging by default. 2017-04-12 16:36 GMT+02:00 Jean-Baptiste Onofré : Hi Arunan, let me take a look but it sounds like a bug to me. I keep you posted. Regards JB On 04/12/2017 04:25 PM, Arunan Balasubramaniam wrote: Hello, With updating to Karaf 4.1.1 I have found a change in behaviour in the karaf-maven-plugin seemingly no longer adding bundles from POM dependencies. I have put a testcase up at https://github.com/arunan-interlink/karaf-maven-plugin-features-change that demonstrates the issue. Changing the version of karaf-maven-plugin used in the top level POM shows the different behaviours in the output feature file. Has anybody else had similar issues? Has anybody else started using the 4.1.x Maven plugins and had this work? My apologies if I have missed a release note, existing issue or if this is an incorrect configuration. Regards, Arunan -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com -- Guillaume Nodet
RE: FW: Change in behaviour of karaf-maven-plugin w.r.t. dependencies for feature packaging between 4.0.x and 4.1.x
Hi, I gave it a go at https://github.com/apache/karaf/pull/293 Cheers, Arunan -Original Message- From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] Sent: 13 April 2017 09:28 To: user@karaf.apache.org Subject: Re: FW: Change in behaviour of karaf-maven-plugin w.r.t. dependencies for feature packaging between 4.0.x and 4.1.x Hi Arunan, good catch for the documentation. You can submit a pull request on the dev guide, I will merge/rebase with the current work in progress. Thanks ! Regards JB On 04/13/2017 09:49 AM, Arunan Balasubramaniam wrote: > > Hi Guillaume, > > Thanks for the reference, much appreciated. > > Looks like > https://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/developer-guide/karaf-maven-plugin.adoc > could do with an update at least regarding > karaf:features-generate-descriptor . I would volunteer a patch but I don't > know what the right updates are, sorry. > > And generally, thanks to everybody for Karaf, I've been using it for a year > and really enjoying it. > > Arunan > > > > From: Guillaume Nodet [mailto:gno...@apache.org] > Sent: 12 April 2017 15:49 > To: user > Subject: Re: FW: Change in behaviour of karaf-maven-plugin w.r.t. > dependencies for feature packaging between 4.0.x and 4.1.x > > Didn't we discussed that on dev@ a while ago ? > The thread is named "[DISCUSS] Feature package, feature generation and > validation", started on 13/10/2016. > IIRC, the outcome was to remove the ‘feature-generate-descriptor’ goal from > the ‘feature’ packaging by default. > > 2017-04-12 16:36 GMT+02:00 Jean-Baptiste Onofré : > Hi Arunan, > > let me take a look but it sounds like a bug to me. > > I keep you posted. > > Regards > JB > > > On 04/12/2017 04:25 PM, Arunan Balasubramaniam wrote: > Hello, > > With updating to Karaf 4.1.1 I have found a change in behaviour in the > karaf-maven-plugin seemingly no longer adding bundles from POM dependencies. > I have put a testcase up at > https://github.com/arunan-interlink/karaf-maven-plugin-features-change that > demonstrates the issue. Changing the version of karaf-maven-plugin used in > the top level POM shows the different behaviours in the output feature file. > > Has anybody else had similar issues? Has anybody else started using the > 4.1.x Maven plugins and had this work? > > My apologies if I have missed a release note, existing issue or if this is > an incorrect configuration. > > Regards, > Arunan > -- Jean-Baptiste Onofré jbono...@apache.org http://blog.nanthrax.net Talend - http://www.talend.com
RE: going from karaf 4.0.9 to 4.1.1 broken logging
Hi,
I had a poke at this and have got as far as
https://github.com/NetNow/org.ops4j.pax.exam2/tree/configure-karaf-logging-by-backend
which will work if your log4j2 is configured using properties within the file
etc/org.ops4j.pax.logging.cfg rather than in a different file referenced from
it. It’s not ideal but it’s equal to the previous log4j situation.
Cheers,
Arunan
From: nino martinez wael [mailto:nino.martinez.w...@gmail.com]
Sent: 01 May 2017 12:27
To: user@karaf.apache.org
Subject: Re: going from karaf 4.0.9 to 4.1.1 broken logging
nice :)
On Wed, Apr 26, 2017 at 3:37 PM, Achim Nierbeck
mailto:bcanh...@googlemail.com>> wrote:
Hi,
yeah I've already filed a bug for that in pax exam.
I think this is due to the fact that Karaf 4.1.x uses the log4j2 backend
instead of the log4j backend it previously used.
regards, Achim
[1] - https://ops4j1.jira.com/browse/PAXEXAM-815
2017-04-26 15:27 GMT+02:00 nino martinez wael
mailto:nino.martinez.w...@gmail.com>>:
Sorry for the weird subject.. In my pax exam tests I no longer have logging
when going from 4.0.9 to 4.1.1
karafDistributionConfiguration().frameworkUrl(maven().groupId("org.apache.karaf").artifactId("apache-karaf")
.type("zip").version("4.0.9"))
.unpackDirectory(new File("target/paxexam/unpack/"))
,CoreOptions.systemTimeout(36),
configureConsole().ignoreLocalConsole(),
logLevel(LogLevel.DEBUG),
something seems off..
--
Best regards / Med venlig hilsen
Nino Martinez
--
Apache Member
Apache Karaf
Software Architect / Project Manager / Scrum Master
--
Best regards / Med venlig hilsen
Nino Martinez
