[[1;31mERROR[m] [ERROR] Some problems were encountered while processing the POMs:
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.cq:core.wcm.components.core:jar -> version 2.16.4 vs ${core.wcm.components.version} @ com.adobe.aem.itc.efs:itc-efs:1.0.0-SNAPSHOT, C:\ITC-Anil-3Feb\itc-efs\pom.xml, line 715, column 25
[ERROR] Unknown packaging: content-package @ line 35, column 17
[WARNING] 'dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.cq:core.wcm.components.core:jar -> duplicate declaration of version (?) @ line 154, column 21
[WARNING] 'build.plugins.plugin.version' for org.apache.felix:maven-bundle-plugin is missing. @ line 37, column 21
[WARNING] 'dependencyManagement.dependencies.dependency.(groupId:artifactId:type:classifier)' must be unique: com.adobe.cq:core.wcm.components.core:jar -> version 2.16.4 vs ${core.wcm.components.version} @ line 715, column 25
@
[ERROR] The build could not read 1 project -> [1m[Help 1][m
[ERROR]
[ERROR] The project com.adobe.aem.itc.efs:itc-efs.all:1.0.0-SNAPSHOT (C:\ITC-Anil-3Feb\itc-efs\all\pom.xml) has 1 error
[ERROR] Unknown packaging: content-package @ line 35, column 17
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the [1m-e[m switch.
[ERROR] Re-run Maven using the [1m-X[m switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [1m[Help 1][m http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException
Solved! Go to Solution.
Views
Replies
Total Likes
The filevault-package-maven-plugin plugin does not provide this packaging anymore (the content-package-maven-plugin did, which was used before).
Just switch the packaging to "zip", and it should work.
@Anilkumar208 This blog gives some possible root causes and a related solution for this kind of issue-
https://blogs.perficient.com/2016/09/20/maven-build-failure-unknown-packaging-content-package/
Also, check if the dependency is added multiple times.
@Manu_Mathew_ thanks for sharing the blog I have all the requirements mentioned in the blog, but it not working.
@Anilkumar208 Did also you try searching for `core.wcm.components.version` on the project directory if there are duplicate dependencies? Can you also run it with debug switch -X and share the same?
@Anilkumar208 Can you share the pom.xml file
<!--
| Copyright 2019 Adobe Systems Incorporated
|
| Licensed under the Apache License, Version 2.0 (the "License");
| you may not use this file except in compliance with the License.
| You may obtain a copy of the License at
|
| http://www.apache.org/licenses/LICENSE-2.0
|
| Unless required by applicable law or agreed to in writing, software
| distributed under the License is distributed on an "AS IS" BASIS,
| WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
| See the License for the specific language governing permissions and
| limitations under the License.
-->
<project xmlns="http://maven.apache.org/POM/4.0.0"
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd">
<modelVersion>4.0.0</modelVersion>
<!-- ====================================================================== -->
<!-- P A R E N T P R O J E C T D E S C R I P T I O N -->
<!-- ====================================================================== -->
<parent>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs</artifactId>
<version>1.0.0-SNAPSHOT</version>
<relativePath>../pom.xml</relativePath>
</parent>
<!-- ====================================================================== -->
<!-- P R O J E C T D E S C R I P T I O N -->
<!-- ====================================================================== -->
<artifactId>itc-efs.all</artifactId>
<packaging>content-package</packaging>
<name>ITCEFS Sites Project - All</name>
<description>All content package for ITCEFS Sites Project</description>
<!-- ====================================================================== -->
<!-- B U I L D D E F I N I T I O N -->
<!-- ====================================================================== -->
<build>
<pluginManagement>
<plugins>
<!-- ====================================================================== -->
<!-- V A U L T P A C K A G E P L U G I N S -->
<!-- ====================================================================== -->
<plugin>
<groupId>org.apache.jackrabbit</groupId>
<artifactId>filevault-package-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<group>com.adobe.aem.itc.efs</group>
<packageType>container</packageType>
<!-- skip sub package validation for now as some vendor packages like CIF apps will not pass -->
<skipSubPackageValidation>true</skipSubPackageValidation>
<embeddeds>
<embedded>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.ui.apps</artifactId>
<type>zip</type>
<target>/apps/itcefs-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.core</artifactId>
<target>/apps/itcefs-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.ui.content</artifactId>
<type>zip</type>
<target>/apps/itcefs-packages/content/install</target>
</embedded>
<embedded>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.ui.config</artifactId>
<type>zip</type>
<target>/apps/itcefs-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.content</artifactId>
<type>zip</type>
<target>/apps/itcefs-vendor-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.core</artifactId>
<target>/apps/itcefs-vendor-packages/application/install</target>
</embedded>
<embedded>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.config</artifactId>
<type>zip</type>
<target>/apps/itcefs-vendor-packages/application/install</target>
</embedded>
</embeddeds>
</configuration>
</plugin>
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<extensions>true</extensions>
<configuration>
<verbose>true</verbose>
<failOnError>true</failOnError>
</configuration>
</plugin>
<plugin>
<artifactId>maven-clean-plugin</artifactId>
<executions>
<execution>
<id>auto-clean</id>
<phase>initialize</phase>
<goals>
<goal>clean</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</pluginManagement>
</build>
<!-- ====================================================================== -->
<!-- P R O F I L E S -->
<!-- ====================================================================== -->
<profiles>
<profile>
<id>autoInstallSinglePackage</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<executions>
<execution>
<id>install-package</id>
<goals>
<goal>install</goal>
</goals>
<configuration>
<targetURL>http://${aem.host}:${aem.port}/crx/packmgr/service.jsp</targetURL>
<failOnError>true</failOnError>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
<profile>
<id>autoInstallSinglePackagePublish</id>
<activation>
<activeByDefault>false</activeByDefault>
</activation>
<build>
<plugins>
<plugin>
<groupId>com.day.jcr.vault</groupId>
<artifactId>content-package-maven-plugin</artifactId>
<executions>
<execution>
<id>install-package-publish</id>
<goals>
<goal>install</goal>
</goals>
<configuration>
<targetURL>http://${aem.publish.host}:${aem.publish.port}/crx/packmgr/service.jsp</targetURL>
<failOnError>true</failOnError>
</configuration>
</execution>
</executions>
</plugin>
</plugins>
</build>
</profile>
</profiles>
<!-- ====================================================================== -->
<!-- D E P E N D E N C I E S -->
<!-- ====================================================================== -->
<dependencies>
<dependency>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.ui.apps</artifactId>
<version>${project.version}</version>
<type>zip</type>
</dependency>
<dependency>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.ui.content</artifactId>
<version>${project.version}</version>
<type>zip</type>
</dependency>
<dependency>
<groupId>com.adobe.aem.itc.efs</groupId>
<artifactId>itc-efs.ui.config</artifactId>
<version>${project.version}</version>
<type>zip</type>
</dependency>
<dependency>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.content</artifactId>
<type>zip</type>
</dependency>
<dependency>
<groupId>com.adobe.cq</groupId>
<artifactId>core.wcm.components.config</artifactId>
<type>zip</type>
</dependency>
</dependencies>
</project>
@Anilkumar208 On seeing the pom.xml file from 'all' module seems fine. But we might need to check that project structure how it was created. Main issue is on the package name line 35.
[ERROR] Unknown packaging: content-package @ line 35, column 17
The filevault-package-maven-plugin plugin does not provide this packaging anymore (the content-package-maven-plugin did, which was used before).
Just switch the packaging to "zip", and it should work.
Views
Likes
Replies
Views
Likes
Replies