using 4.2.9 builds without problems 4.3.0 fails Am Mo., 8. März 2021 um 09:37 Uhr schrieb Matthias Leinweber < m.leinwe...@datatactics.de>:
> It becomes more and more strange. I tried to simply build the example > configuration from karaf-examples without the example application and i > still get these kind of errors. > The env does not have internet access but a private artifactory, but that > should not be a problem. I can locally build against the artifactory > without any internet connection. > Do you have any ideas? We thought if it is maybe something with the > container overlay file system? or persistentvolume? > > br, > Matthias > > Am Do., 4. März 2021 um 11:39 Uhr schrieb Matthias Leinweber < > m.leinwe...@datatactics.de>: > >> My plugin configuration looks actually like (i removed my own feature) >> >> thats my pom .. karaf bundle plgin extensions is set to true in parent pom >> >> <properties> >> <dependency.locations.enabled>false</dependency.locations.enabled> >> <getRevisionOnce>false</getRevisionOnce> >> <project.build.sourceEncoding>UTF-8</project.build.sourceEncoding> >> </properties> >> >> <build> >> <plugins> >> <plugin> >> <artifactId>maven-install-plugin</artifactId> >> <configuration> >> <skip>true</skip> >> </configuration> >> <groupId>org.apache.maven.plugins</groupId> >> </plugin> >> <plugin> >> <artifactId>karaf-maven-plugin</artifactId> >> <configuration> >> <archiveTarGz>false</archiveTarGz> >> <archiveZip>false</archiveZip> >> <bootFeatures> >> <feature>standard</feature> >> </bootFeatures> >> <installedFeatures> >> <feature>wrapper</feature> >> <feature>aries-blueprint</feature> >> <feature>shell-compat</feature> >> </installedFeatures> >> <javase>11</javase> >> <libraries /> >> <startupFeatures> >> <feature>eventadmin</feature> >> </startupFeatures> >> </configuration> >> <groupId>org.apache.karaf.tooling</groupId> >> </plugin> >> </plugins> >> <resources> >> <resource> >> <directory>src/main/resources</directory> >> <filtering>false</filtering> >> <includes> >> <include>**/*</include> >> </includes> >> </resource> >> <resource> >> <directory>src/main/filtered-resources</directory> >> <filtering>true</filtering> >> <includes> >> <include>**/*</include> >> </includes> >> </resource> >> </resources> >> </build> >> >> >> <dependencies> >> <dependency> >> <artifactId>framework</artifactId> >> <groupId>org.apache.karaf.features</groupId> >> <type>kar</type> >> </dependency> >> <dependency> >> <artifactId>standard</artifactId> >> <classifier>features</classifier> >> <groupId>org.apache.karaf.features</groupId> >> <type>xml</type> >> </dependency> >> <dependency> >> <artifactId>framework</artifactId> >> <classifier>features</classifier> >> <groupId>org.apache.karaf.features</groupId> >> <scope>runtime</scope> >> <type>xml</type> >> </dependency> >> <dependency> >> <artifactId>enterprise</artifactId> >> <classifier>features</classifier> >> <groupId>org.apache.karaf.features</groupId> >> <scope>runtime</scope> >> <type>xml</type> >> </dependency> >> >> >> </dependencies> >> >> >> </project> >> >> >> >> [INFO] Loading startup repositories >> [INFO] Resolving startup features and bundles >> [INFO] Features: framework, framework-security/4.3.0, >> service-security/4.3.0, aries-proxy/4.3.0, aries-blueprint/4.3.0, >> feature/4.3.0, jaas-boot/4.3.0, shell/4.3.0, jline/3.16.0, >> shell-compat/4.3.0, deployer/4.3.0, wrapper/4.3.0, service-wrapper/4.3.0, >> obr/4.3.0, bundle/4.3.0, config/4.3.0, diagnostic/4.3.0, instance/4.3.0, >> jaas-deployer/4.3.0, jaas/4.3.0, log/4.3.0, package/4.3.0, service/4.3.0, >> system/4.3.0, felix-httplite/0.1.6, felix-http/4.1.2, pax-web-http/7.3.9, >> http/7.3.9, pax-web-http-whiteboard/7.3.9, http-whiteboard/7.3.9, >> pax-web-war/4.3.0, war/4.3.0, kar/4.3.0, webconsole/4.3.0, ssh/4.3.0, >> management/4.3.0, scheduler/4.3.0, eventadmin/4.3.0, >> jasypt-encryption/4.3.0, scr/4.3.0, blueprint-web/4.3.0, wrap/2.6.2, >> profile/4.3.0, jolokia/1.6.2, maven/4.3.0, audit-log/4.3.0, >> documentation/4.3.0, standard/4.3.0, minimal/4.3.0 >> [INFO] Bundles: >> >> >> br, >> Matthias >> >> Am Do., 4. März 2021 um 05:44 Uhr schrieb Jean-Baptiste Onofre < >> j...@nanthrax.net>: >> >>> Do you have log feature as boot feature ? >>> >>> Don’t you try to add Aries-proxy as boot feature as well ? >>> >>> It seems to be related to startup/boot features you defined (not really >>> environment). >>> >>> Regards >>> JB >>> >>> Le 3 mars 2021 à 18:22, Matthias Leinweber <m.leinwe...@datatactics.de> >>> a écrit : >>> >>> Hello Karafers, >>> >>> i have a very strange build issue with assembly plugin. >>> I can build my package on my machine, on my machine inside a container >>> using podman as well as submitting my dockerfile to a kaniko builder. A >>> colleague of mine can also build it on his machine. With our internal >>> artifactory as well as with maven.repo.org (proxy). >>> >>> However as soon as we try to build inside our kubernetes it fails with >>> changing the dependencies somehow randomly changes the missing package >>> >>> [ERROR] Failed to execute goal >>> org.apache.karaf.tooling:karaf-maven-plugin:4.3.0:assembly >>> (default-assembly) on project rahla: Unable to build assembly: >>> org.apache.felix.resolver.reason.ReasonException: Unable to resolve root: >>> missing requirement [root] osgi.identity; osgi.identity=service-security; >>> type=karaf.feature; version=4.3.0; >>> filter:="(&(osgi.identity=service-security)(type=karaf.feature)(version>=4.3.0))" >>> [caused by: Unable to resolve service-security/4.3.0: missing requirement >>> [service-security/4.3.0] osgi.identity; osgi.identity=aries-proxy; >>> type=karaf.feature [caused by: Unable to resolve aries-proxy/4.3.0: missing >>> requirement [aries-proxy/4.3.0] osgi.identity; >>> osgi.identity=org.apache.aries.proxy; type=osgi.bundle; >>> version="[1.1.8,1.1.8]"; resolution:=mandatory [caused by: Unable to >>> resolve org.apache.aries.proxy/1.1.8: missing requirement >>> [org.apache.aries.proxy/1.1.8] osgi.wiring.package; >>> filter:="(&(osgi.wiring.package=org.slf4j)(version>=1.7.0)(!(version>=2.0.0)))"]]] >>> -> [Help 1] >>> >>> We are building inside kubernetes using maven:3.6.3-jdk-11 as build >>> image. Same which i am using locally. >>> >>> Do you have any ideas/hints how i could debug this? >>> >>> br, >>> Matthias >>> >>> >>> >> >> >> > > >
