Using environment in karaf-maven-plugin

I've been trying to figure out how to use the configuration element with the karaf-maven-plugin... I have 2 pax-logging configuration files in the src/main/resources/etc directory of my Maven Karaf project for building a custom distribution. One of the pax logging config files has #docker

Re: Deploy bundle using karaf maven plugin

Hi By default, the authentication (user) is disabled in Karaf standard distribution. Did you uncommment the karaf user in etc/users.properties ? Regards JB On Sat, Jan 13, 2024 at 1:17 AM jose.garn...@toshibagcs.com wrote: > > I am trying to deploy a bundle using the Karaf maven plugin

Deploy bundle using karaf maven plugin

I am trying to deploy a bundle using the Karaf maven plugin to my local karaf instance, org.apache.karaf.tooling karaf-maven-plugin features-generate-descriptor true

Re: karaf-maven-plugin and version ranges

on. > >> >>> I will keep you posted soon. > >> >>> > >> >>> Regards > >> >>> JB > >> >>> > >> >>> On Tue, Mar 22, 2022 at 5:30 PM Bengt Rodehav > wrote: > >> >>>

Re: Karaf Maven Plugin / NoFileAssignedException

Hello. For sure ! I had the problem when my maven project was configured with packaging "feature", as explained in the maven plugin documentation : no main artifact is provided, and the recent install plugin failed with this exception. Some posts said to switch to an old install version 2.5.2.

Re: Karaf Maven Plugin / NoFileAssignedException

Hi, It's not easy to answer without a trace for instance or test case. Can you share more details ? Thanks, Regards JB On Mon, Aug 8, 2022 at 9:36 AM Ephemeris Lappis wrote: > > Hello. > > I'm trying to make a POC for refactoring old projects running today on > Red-Hat Fuse, and thus using its

Re: Karaf Maven Plugin / Depedent features

r version > range property. > > Example: > https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/src/main/feature/feature.xml > > You can find the configuration of the karaf maven plugin here: > https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/pom.xml > >

Re: Karaf Maven Plugin / Depedent features

Hello. You're right, dependencies in scope "provided" are ignored (not included as bundles), useful for dependencies that are needed at build time, but are provided by features. Dependencies in scope "compile" (default), are included as expected when the plugin works. For me it works now in two

Re: Karaf Maven Plugin / Depedent features

; Now it takes the template that declares dependent features, filtering > properties values for versions, and adds bundles for dependencies as > expected. Ok. The example features I posted, where from a project with packaging jar (actually an OSGi bundle, but I use packaging jar and not

Re: Karaf Maven Plugin / Depedent features

> Ephemeris Lappis : > Hello. > I've tried using such a template, and all the elements from it are > used, with filtering to generate the result file, but maven > dependencies are not added as bundles to my feature. > It seems that using the template makes the plugin ignore bundles

Re: Karaf Maven Plugin / Depedent features

are added as expected with the matching bundles. > > > How can I add features ? I've tried putting a feature.xml file in the > > src/main/feature folder, but then the generation just copy this file > > and do not update it... > > Hm... my template.xml files are expanded the

Re: Karaf Maven Plugin / Depedent features

configuration in the pom.xml (the project has "feature" packaging): org.apache.karaf.tooling karaf-maven-plugin ${project.artifactId}-dependencies And the result (just the template with filtered values, and nothing about my own feature) : http://karaf.apache.org/xmlns/features/v1.6.0;

Re: Karaf Maven Plugin / Depedent features

feature.xml file in the > src/main/feature folder, but then the generation just copy this file > and do not update it... Hm... my template.xml files are expanded the way I expect them to be. What version of karaf-maven-plugin are you using? Here is one of my src/main/feature/feature.xml

Re: Karaf Maven Plugin / Depedent features

define feature dependencies in >> > >> > src/main/feature/features.xml >> > >> > For each feature dependency I have to define in the pom a version or >> > version range property. >> > >> > Example: >> > https://github.com/rhierlmei

Re: Karaf Maven Plugin / Depedent features

pendency I have to define in the pom a version or > version range property. > > > > Example: > > > https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/src/main/feature/feature.xml > > > > You can find the configuration of the karaf maven plugin here: > >

Re: Karaf Maven Plugin / Depedent features

adin8_karaf_demo/blob/main/src/main/feature/feature.xml > > You can find the configuration of the karaf maven plugin here: > https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/pom.xml > > This approach works, but is has the following disadvantages: > > * You can no

Re: Karaf Maven Plugin / Depedent features

the configuration of the karaf maven plugin here: https://github.com/rhierlmeier/vaadin8_karaf_demo/blob/main/pom.xml This approach works, but is has the following disadvantages: * You can not reuse feature version or version range properties with the Maven BOM mechanism (import the dependency

Karaf Maven Plugin / Depedent features

Hello. I can't find any way to add dependent features to the feature I try to generate using the maven plugin. The maven dependencies are added as expected with the matching bundles. How can I add features ? I've tried putting a feature.xml file in the src/main/feature folder, but then the

Karaf Maven Plugin / NoFileAssignedException

Hello. I'm trying to make a POC for refactoring old projects running today on Red-Hat Fuse, and thus using its Fabric8's profile system for deployment. Karaf features seem to be a good alternative, but I have some issues that are already reported about NoFileAssignedException on install

Re: karaf-maven-plugin and version ranges

22, 2022 at 5:30 PM Bengt Rodehav wrote: >> >>> > >> >>> > Did you have a chance to test this on Windows JB? >> >>> > >> >>> > /Bengt >> >>> > >> >>> > Den fre 11 mars 2022 kl 17:17 skrev

Re: karaf-maven-plugin and version ranges

:30 PM Bengt Rodehav > wrote: > >>> > > >>> > Did you have a chance to test this on Windows JB? > >>> > > >>> > /Bengt > >>> > > >>> > Den fre 11 mars 2022 kl 17:17 skrev Bengt Rodehav >: > &g

Re: karaf-maven-plugin and version ranges

;> > >>> > Did you have a chance to test this on Windows JB? >>> > >>> > /Bengt >>> > >>> > Den fre 11 mars 2022 kl 17:17 skrev Bengt Rodehav : >>> >> >>> >> OK - thanks. >>> >> >>

Re: karaf-maven-plugin and version ranges

>> > >> > /Bengt >> > >> > Den fre 11 mars 2022 kl 17:17 skrev Bengt Rodehav : >> >> >> >> OK - thanks. >> >> >> >> /Bengt >> >> >> >> Den fre 11 mars 2022 kl 15:53 skrev Jean-Ba

Re: karaf-maven-plugin and version ranges

> > Did you have a chance to test this on Windows JB? > > > > /Bengt > > > > Den fre 11 mars 2022 kl 17:17 skrev Bengt Rodehav : > >> > >> OK - thanks. > >> > >> /Bengt > >> > >> Den fre 11 mars 2022 kl 15:53 skrev J

Re: karaf-maven-plugin and version ranges

>> >> OK - thanks. >> >> /Bengt >> >> Den fre 11 mars 2022 kl 15:53 skrev Jean-Baptiste Onofré : >>> >>> Hi >>> >>> I think it’s more Karaf-maven-plugin issue/use on windows. >>> >>> We don’t have such issue o

Re: karaf-maven-plugin and version ranges

Did you have a chance to test this on Windows JB? /Bengt Den fre 11 mars 2022 kl 17:17 skrev Bengt Rodehav : > OK - thanks. > > /Bengt > > Den fre 11 mars 2022 kl 15:53 skrev Jean-Baptiste Onofré >: > >> Hi >> >> I think it’s more Karaf-maven-plugin is

Re: karaf-maven-plugin and version ranges

OK - thanks. /Bengt Den fre 11 mars 2022 kl 15:53 skrev Jean-Baptiste Onofré : > Hi > > I think it’s more Karaf-maven-plugin issue/use on windows. > > We don’t have such issue on Unix. Let me try on Windows vm. > > Regards > JB > > Le ven. 11 mars 2022 à 15:38, Be

Re: karaf-maven-plugin and version ranges

Hi I think it’s more Karaf-maven-plugin issue/use on windows. We don’t have such issue on Unix. Let me try on Windows vm. Regards JB Le ven. 11 mars 2022 à 15:38, Bengt Rodehav a écrit : > Do you think this is a Camel problem? The more I think about it I wonder > how it could eve

Re: karaf-maven-plugin and version ranges

3:56 PM Bengt Rodehav wrote: >> >>> I use Karaf 4.3.6 and I'm trying to upgrade our Camel version to the >>> latest (2.14.2). It turns out I get a problem with karaf-maven-plugin, >>> goal features-add-to-repository. >>> >>> The new Karaf feature desc

Re: karaf-maven-plugin and version ranges

ying to upgrade our Camel version to the >> latest (2.14.2). It turns out I get a problem with karaf-maven-plugin, >> goal features-add-to-repository. >> >> The new Karaf feature descriptor for Camel now starts with the following >> three lines: >> >> >> mvn:org.a

Re: karaf-maven-plugin and version ranges

Hi Bengt, I guess you are on Windows right ? Regards JB On Thu, Mar 10, 2022 at 3:56 PM Bengt Rodehav wrote: > I use Karaf 4.3.6 and I'm trying to upgrade our Camel version to the > latest (2.14.2). It turns out I get a problem with karaf-maven-plugin, > goal features-add-to-r

karaf-maven-plugin and version ranges

I use Karaf 4.3.6 and I'm trying to upgrade our Camel version to the latest (2.14.2). It turns out I get a problem with karaf-maven-plugin, goal features-add-to-repository. The new Karaf feature descriptor for Camel now starts with the following three lines: mvn:org.apache.cxf.karaf/apache-cxf

Re: karaf-maven-plugin Generate Features Destination

> Paul Fraser : > Is it possible to locate the features file outside the target directory using > the plugin? I don't know, but could you tell why do you want to put the features file outside the target directory? (maybe there is some other way of accomplishing what you want...?)

karaf-maven-plugin Generate Features Destination

Hi, Vaadin is using the karaf-maven-plugin to generate the features file and is being placed in the target directory. I cannot find a way to set a target location in the plugin docs. Is it possible to locate the features file outside the target directory using the plugin? Paul Fraser

Re: Add library to jdk9plus with karaf-maven-plugin

> Thanks! > Freeman > > On Wed, Aug 12, 2020 at 4:45 PM Guillaume Girard <mailto:ggir...@outlook.com>> wrote: > Hi all, > > I am trying to use the karaf-maven-plugin to customize a distribution and > more specifically to add bouncy castle support. > On JDK

Re: Add library to jdk9plus with karaf-maven-plugin

Hi Guillaume, Could you please fill an enhancement jira ticket for this? We can track it there. Thanks! Freeman On Wed, Aug 12, 2020 at 4:45 PM Guillaume Girard wrote: > Hi all, > > I am trying to use the karaf-maven-plugin to customize a distribution and > more specifically t

Add library to jdk9plus with karaf-maven-plugin

Hi all, I am trying to use the karaf-maven-plugin to customize a distribution and more specifically to add bouncy castle support. On JDK 8, there is no issue as additional libraries can be added to the distribution with the AssemblyMojo and specifying them like mvn:org.bouncycastle/bcmail

Re: Karaf 4.2.8, karaf-maven-plugin verify exception

>> >>> You have to check your feature XML to avoid the refresh. >>> >>> Regards >>> JB >>> >>> On 23/01/2020 17:25, Alex Soto wrote: >>>> Migrating to Karaf 4.2.8, the verify goal of the karaf-maven-plugin >>>> fails

Re: Karaf 4.2.8, karaf-maven-plugin verify exception

e to check your feature XML to avoid the refresh. >> >> Regards >> JB >> >> On 23/01/2020 17:25, Alex Soto wrote: >>> Migrating to Karaf 4.2.8, the verify goal of the karaf-maven-plugin >>> fails to validate my  feature.x

Re: Karaf 4.2.8, karaf-maven-plugin verify exception

a refresh to uninstall which is bad. > > You have to check your feature XML to avoid the refresh. > > Regards > JB > > On 23/01/2020 17:25, Alex Soto wrote: >> Migrating to Karaf 4.2.8, the verify goal of the karaf-maven-plugin >> fails to va

Re: Karaf 4.2.8, karaf-maven-plugin verify exception

The resolver is performing a refresh to uninstall which is bad. You have to check your feature XML to avoid the refresh. Regards JB On 23/01/2020 17:25, Alex Soto wrote: > Migrating to Karaf 4.2.8, the verify goal of the karaf-maven-plugin > fails to validate my  feature.xml with this exc

Re: Karaf 4.2.8, karaf-maven-plugin verify exception

installer Right before the error, Best regards, Alex soto > On Jan 23, 2020, at 11:25 AM, Alex Soto wrote: > > Migrating to Karaf 4.2.8, the verify goal of the karaf-maven-plugin fails to > validate my feature.xml with th

Karaf 4.2.8, karaf-maven-plugin verify exception

Migrating to Karaf 4.2.8, the verify goal of the karaf-maven-plugin fails to validate my feature.xml with this exception: at org.apache.karaf.tooling.VerifyMojo.verifyResolution(VerifyMojo.java:506) at org.apache.karaf.tooling.VerifyMojo.doExecute

Re: karaf-maven-plugin with static framework

version} >>> >>> >> start-level="10">mvn:org.apache.karaf.services/org.apache.karaf.services.staticcm/${project.version} >>> >>> >>> Could this be a bug? Should “static-framework” also add Activation

Re: karaf-maven-plugin with static framework

gt;>     >> >> Could this be a bug? Should “static-framework” also add Activation API >> bundle? >> >> Best regards, >> Alex soto >> >> >> >> >>> On Sep 9, 2019, at 3:40 PM, Alex Soto >> <mailto:alex.s...@envieta.com&g

Re: karaf-maven-plugin with static framework

ccm/${project.version} >>     >> >> Could this be a bug? Should “static-framework” also add Activation API >> bundle? >> >> Best regards, >> Alex soto >> >> >> >> >>> On Sep 9, 2019, at 3:40 PM, Alex Soto >> <

Re: karaf-maven-plugin with static framework

atic-framework” also add Activation API >> bundle? >> >> Best regards, >> Alex soto >> >> >> >> >>> On Sep 9, 2019, at 3:40 PM, Alex Soto >> <mailto:alex.s...@envieta.com>> wrote: >>> >>> Oracle’s JDK 1.8 Java 8 Updat

Re: karaf-maven-plugin with static framework

:alex.s...@envieta.com>> wrote: >> >> Oracle’s JDK 1.8 Java 8 Update 171 >> >> Best regards, >> Alex soto >> >> >> >> >>> On Sep 9, 2019, at 3:34 PM, Francois Papon >> <mailto:francois.pa...@openobject.fr>&

Re: karaf-maven-plugin with static framework

org <mailto:fpa...@apache.org> >> Le 09/09/2019 à 19:05, Alex Soto a écrit : >>> Hello, >>> >>> I am trying to build a custom distribution using karaf-maven-plugin with >>> Karaf version 4.2.6. To keep it to a minus, I have removed my feature, >

Re: karaf-maven-plugin with static framework

...@apache.org> > Le 09/09/2019 à 19:05, Alex Soto a écrit : >> Hello, >> >> I am trying to build a custom distribution using karaf-maven-plugin with >> Karaf version 4.2.6. To keep it to a minus, I have removed my feature, >> leaving only the following:

Re: karaf-maven-plugin with static framework

Hi Alex, Wich JDK are you using when building the custom distribution? regards, François fpa...@apache.org Le 09/09/2019 à 19:05, Alex Soto a écrit : > Hello,  > > I am trying to build a custom distribution using karaf-maven-plugin > with Karaf version 4.2.6. To keep it to a m

karaf-maven-plugin with static framework

Hello, I am trying to build a custom distribution using karaf-maven-plugin with Karaf version 4.2.6. To keep it to a minus, I have removed my feature, leaving only the following: static-framework 1.8 static true static Still, I get the following error: Unable to build assembly

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

ovided to only include that dependency > but > > not of it's transitive dependencies in the feature.xml > > Yup, but I didn't want to touch their dependencies if I could avoid it. > > > 3. The karaf maven plugin has an option to excludeArtifactId (look in the > > docs of

PostgreSQL JDBC driver now has a karaf feature attached (Was: How to make karaf-maven-plugin exclude some compile depencies when building a feature?)

> Steinar Bang : > The PR is here if anyone would like to take a look at it: > https://github.com/pgjdbc/pgjdbc/pull/1554 The PR was merged to pgjdbc master, so when the next release of pgjdbc is done, it should be possible to use the attached feature: 1. From a maven dependency in a

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

>>>>> Jean-Baptiste Onofré : > you can blacklist or you can exclude artifacts. Right. I tried using blacklisting in the karaf-maven-plugin documentation, but that didn't work as I expected it to. I looked for something like the exclusion of artifacts in the karaf-maven-pl

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

d to only include that dependency but > not of it's transitive dependencies in the feature.xml Yup, but I didn't want to touch their dependencies if I could avoid it. > 3. The karaf maven plugin has an option to excludeArtifactId (look in the > docs of the karaf site) Right. Something like this

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

Hi, you can blacklist or you can exclude artifacts. You can also use a different scope than compile, or use a features.xml "template". Regards JB On 31/08/2019 00:52, Steinar Bang wrote: > Is it possible to make karaf-maven-plugin exclude some dependencies with > compile?

Re: How to make karaf-maven-plugin exclude some compile depencies when building a feature?

in the feature.xml 3. The karaf maven plugin has an option to excludeArtifactId (look in the docs of the karaf site) 4. If you really have to, you can blacklist a bundle using the karaf maven plugin, but that would be a last resort IMHO. I would use one of the first 2 options primarily. Also, you

How to make karaf-maven-plugin exclude some compile depencies when building a feature?

Is it possible to make karaf-maven-plugin exclude some dependencies with compile? I'm trying to create a pull request to fix this issue https://github.com/pgjdbc/pgjdbc/issues/1552 and the PostgreSQL JDBC driver pulls in and includes two dependencies, that I would like to not pull

Re: karaf-maven-plugin doesn't fail on feature name typo

Hi Lukasz, FYI, I created https://issues.apache.org/jira/browse/KARAF-6320 about this. The problem is about the pattern matching (it's possible to use regex to select features). If the pattern doesn't match, we don't do anything as it could be matched by another pattern. I will improve this.

Re: karaf-maven-plugin doesn't fail on feature name typo

Hi, Agree, it should be improved. Let me create the Jira and fix that. Thanks Regards JB On 05/06/2019 11:26, lechlukasz wrote: > mvn karaf:verify doesn't fail when referring non-existing features. > > It is inconsistent, because if I give non-existing bootRepository, the mvn > verify will

Re: karaf-maven-plugin doesn't fail on feature name typo

mvn karaf:verify doesn't fail when referring non-existing features. It is inconsistent, because if I give non-existing bootRepository, the mvn verify will fail, however the non-existing bootFeature will be silently ignored. -- Sent from:

Re: karaf-maven-plugin doesn't fail on feature name typo

Hi, Do you use karaf:verify on your features ? Regards JB On 04/06/2019 16:37, Lukasz Lech wrote: > Hello, > >   > > I’ve noticed that the container built with maven-karaf-plugin (4.2.4) >  “doesn’t work” without any error message. > > After the inspection I’ve noticed that one of my

karaf-maven-plugin doesn't fail on feature name typo

Hello, I've noticed that the container built with maven-karaf-plugin (4.2.4) "doesn't work" without any error message. After the inspection I've noticed that one of my features is not installed. The name of the feature was misspelled. The problem is, that maven build has not failed. It looks

Re: karaf-maven-plugin: creating Docker image doesn't work for Windows

/groups/snapshots-group, default, > snapshots), ops4j.sonatype.snapshots.deploy > (https://oss.sonatype.org/content/repositories/ops4j-snapshots/, default, > snapshots), apache.snapshots (https://repository.apache.org/snapshots, > default, snapshots)] > [DEBUG] Repositories (plugins) : [thirdparty > (https://nexus-intern.mgmt.conrad24.c

Re: karaf-maven-plugin: creating Docker image doesn't work for Windows

eases > (https://nexus-intern.mgmt.conrad24.com/nexus/content/groups/public, default, > releases+snapshots), apache-snapshots > (http://repository.apache.org/content/groups/snapshots-group, default, > snapshots), ops4j.sonatype.snapshots.deploy > (https://oss.sonatype.org/content/reposit

RE: karaf-maven-plugin: creating Docker image doesn't work for Windows

worlds.launcher.Launcher.launchEnhanced (Launcher.java:289) at org.codehaus.plexus.classworlds.launcher.Launcher.launch (Launcher.java:229) at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode (Launcher.java:415) at org.codehaus.plexus.classworlds.launcher.Launcher.

Re: karaf-maven-plugin: creating Docker image doesn't work for Windows

ilto:j...@nanthrax.net] >> Sent: Sonntag, 5. Mai 2019 11:47 >> To: user@karaf.apache.org >> Subject: Re: karaf-maven-plugin: creating Docker image doesn't work for >> Windows >> >> Hi >> >> docker is in your path ? >> >> The karaf:docke

RE: karaf-maven-plugin: creating Docker image doesn't work for Windows

age- > From: Jean-Baptiste Onofré [mailto:j...@nanthrax.net] > Sent: Sonntag, 5. Mai 2019 11:47 > To: user@karaf.apache.org > Subject: Re: karaf-maven-plugin: creating Docker image doesn't work for > Windows > > Hi > > docker is in your path ? > > The karaf:do

Re: karaf-maven-plugin: creating Docker image doesn't work for Windows

ample ." > "docker run --name karaf-docker-example -p 8181:8181 -d karaf-docker-example" > > Any ideas what can be the reason of code 9 by karaf-maven-plugin? > > Regards, > Andrei. > As a recipient of an email from Talend, your contact personal data will be on

karaf-maven-plugin: creating Docker image doesn't work for Windows

Hi, I have a problem to build Docker image using karaf-maven-plugin under Windows: Command "start mvn clean install -Pdocker" under Windows always returns following error: " [ERROR] Failed to execute goal org.apache.karaf.tooling:karaf-maven-plugin:4.2.5 :docker (docker-image) o

Re: karaf-maven-plugin in 4.2.2 installs zip twice

;> installed/deployed twice. >> >> This new behaviour is related to a change >> in >> karaf\tooling\karaf-maven-plugin\src\main\java\org\apache\karaf\tooling\ArchiveMojo.java >> >> This happens when installing a simple/unchanged >> karaf-assembly-ar

Re: karaf-maven-plugin in 4.2.2 installs zip twice

: > Hi, > > starting from 4.2.2, the zip-compressed assemblies get > installed/deployed twice.  > > This new behaviour is related to a change > in  > karaf\tooling\karaf-maven-plugin\src\main\java\org\apache\karaf\tooling\ArchiveMojo.java > > This happens when install

karaf-maven-plugin in 4.2.2 installs zip twice

Hi, starting from 4.2.2, the zip-compressed assemblies get installed/deployed twice.  This new behaviour is related to a change in  karaf\tooling\karaf-maven-plugin\src\main\java\org\apache\karaf\tooling\ArchiveMojo.java This happens when installing a simple/unchanged karaf-assembly-archetype

Re: karaf-maven-plugin verify - ignore missing blueprint references

t;open" feature, meaning that the feature expects some resources at runtime, not yet defined in the features repository. The verify goal is more designed for "close" features. If there's no way to you to provide at least one feature (in the karaf-maven-plugin configuration), then, maybe,

Re: karaf-maven-plugin verify - ignore missing blueprint references

ontaining a bundle providing > this service. However, you have several service implementations > available and it's the user who decide the one he wants at runtime. > > Correct ? > > Regards > JB > > On 29/11/2018 04:23, Jesse White wrote: >> Hi, >> >>

Re: karaf-maven-plugin verify - ignore missing blueprint references

the one he wants at runtime. Correct ? Regards JB On 29/11/2018 04:23, Jesse White wrote: > Hi, > > We're currently leveraging the verify goal of the karaf-maven-plugin to > validate our feature definitions but we're having trouble using it to > test features that: > 1) I

karaf-maven-plugin verify - ignore missing blueprint references

Hi, We're currently leveraging the verify goal of the karaf-maven-plugin to validate our feature definitions but we're having trouble using it to test features that: 1) Import services via Blueprint 2) Do not explicitly depend on an implementation in the feature definition For example

Re: karaf-maven-plugin version 4.2.2?

8 21:41, Alex Soto wrote: >> I am starting to upgrade Karaf to version 4.2.2, plugin >> /karaf-maven-plugin /is missing: >> I get error: >> >> >> Could not find artifact >> org.apache.karaf.tooling:karaf-maven-plugin:jar:4.2.2 in >> central (https:/

Re: karaf-maven-plugin version 4.2.2?

Hi Alex, 4.2.2 is not yet released. The vote is scheduled for next week, so hopefully, it could be available on Central in 2 weeks. Regards JB On 21/11/2018 21:41, Alex Soto wrote: > I am starting to upgrade Karaf to version 4.2.2,  plugin >  /karaf-maven-plugin /is missing: > I

Re: karaf-maven-plugin version 4.2.2?

Hi Alex, FYI, Karaf 4.2.2 isn't released yet, should be available in coming weeks. Cheers Freeman － Freeman(Yue) Fang Red Hat, Inc. > On Nov 22, 2018, at 4:41 AM, Alex Soto wrote: > > I am starting to upgrade Karaf to version 4.2.2, plugin karaf-maven-plugin >

karaf-maven-plugin version 4.2.2?

I am starting to upgrade Karaf to version 4.2.2, plugin karaf-maven-plugin is missing: I get error: Could not find artifact org.apache.karaf.tooling:karaf-maven-plugin:jar:4.2.2 in central (https://repo.maven.apache.org/maven2) @ Was this renamed or moved somewhere else? Best

Re: 4.1.5 and Karaf Maven Plugin

execution in jenkins with an environment variable pointing to the generated settings.xml (-Dorg.ops4j.pax.url.mvn.settings=$M_SETTINGS) and now the Karaf plugin works fine in our Jenkins build. Of course I could be wrong about the above, but after 4.1.4 the karaf maven plugin definitely stopped

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

By the way, you can take a look on the contribution guide: http://karaf.apache.org/community.html Regards JB On 18/06/2018 18:01, Chris N. wrote: > Done! > https://issues.apache.org/jira/browse/KARAF-5788 > > > I have already an

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

Hi, thanks ! You can create a PR on github. Regards JB On 18/06/2018 18:01, Chris N. wrote: > Done! > https://issues.apache.org/jira/browse/KARAF-5788 > > > I have already an implementation, how can I participate? > > Christian > > > >

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

Done! https://issues.apache.org/jira/browse/KARAF-5788 I have already an implementation, how can I participate? Christian -- Sent from: http://karaf.922171.n3.nabble.com/Karaf-User-f930749.html

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

pass this behaviour? > > > org.apache.karaf.tooling > karaf-maven-plugin > true > > features-generate-descriptor > > > true >

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

Thank Jean-Baptiste for your response! Is it possible to add a plugin configuration property "useRawVersion" (default to false) to bypass this behaviour? org.apache.karaf.tooling karaf-maven-plugin

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

Hi Chris, it's normal IMHO: 2.0.0-SNAPSHOT is not a valid OSGi version. 2.0.0.SNAPSHOT is. As the feature resolver is an OSGi resolver, it deals with OSGi version format. So, if you want to use 2.0.0-SNAPSHOT, then, you have to write the features XML by hand, else, the output looks good to me.

Re: karaf-maven-plugin generates feature descriptor with bad snaphot version

Hello, The VersionCleaner .clean() used in the Feature

karaf-maven-plugin generates feature descriptor with bad snaphot version

Hello, I'm using the karaf-maven-plugin to generate feature descriptors but I discover that if the related bundle has a SNAPSHOT version, for example "2.0.0-SNAPSHOT" then the feature generated has a version like "2.0.0.SNAPSHOT" (take note of the dot instead of

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

> > > > > > Actually if I read this part, it does seem > > that the kar > > > > goal should do what > > > > > I want. But I am missing the part where the > > kar plugin ad

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

does seem > that the kar > >     >         goal should do what > >     >         >     I want. But I am missing the part where the > kar plugin add > >     >         the bundles to > >     >         >     the kar repo.. > >     >       

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

> the kar repo.. > > > > > > > > > > > > https://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/user-guide/kar.adoc > > < > https://github.com/apache/karaf/blob/master/manual/src

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

: > Hi, > > I am also having the same issue (with v.4.1.2). > > Here is the workaround I use to build an "offline" kar having all the > bundles of the dependent features. I mix the usage of 2 goals: > > > > > >     org.apache.karaf.tooling &

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

Hi, I am also having the same issue (with v.4.1.2). Here is the workaround I use to build an "offline" kar having all the bundles of the dependent features. I mix the usage of 2 goals: org.apache.karaf.tooling karaf-maven-plugin true

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

raf/blob/master/manual/src/main/asciidoc/user-guide/kar.adoc > > <https://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/user-guide/kar.adoc> > >          > <https://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/user-guide/kar.adoc > > <https://githu

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

; > > > > > https://github.com/apache/karaf/blob/master/manual/src/ > main/asciidoc/user-guide/kar.adoc > > <https://github.com/apache/karaf/blob/master/manual/src/ > main/asciidoc/user-guide/kar.adoc> > > > > > >

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

ttps://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/user-guide/kar.adoc > > <https://github.com/apache/karaf/blob/master/manual/src/main/asciidoc/user-guide/kar.adoc> > > > > > >             Maven > > > >     Apache Karaf provide

Re: karaf-maven-plugin 4.2.0 "FAT" kar?

; bundles to > > the kar repo.. > > > > https://github.com/apache/karaf/blob/master/manual/src/ > main/asciidoc/user-guide/kar.adoc > > > > > > Maven > > > > Apache Karaf provides a Maven plugin: |karaf-maven-plugin|. >

  1   2   3   4   >