Adobe AEM Maven Archetype 24 Error - java.nio.file.FileSystemException

-

Adobe AEM Maven Archetype 24 Error -java.nio.file.FileSystemException

I tried creating a Adobe AEM Archetype 24 project by using below command

mvn -B archetype:generate -D archetypeGroupId=com.adobe.aem  -D archetypeArtifactId=aem-project-archetype -D archetypeVersion=24 -D appTitle="My First Site" -D appId="myfirstsite" -D groupId="com.myfirstsite" -D aemVersion="6.5.0"


I got the below error as part of Execution:

ERROR Failed to execute goal org.apache.maven.plugins:maven-archetype-plugin:3.2.0:generate (default-cli) on project standalone-pom: java.nio.file.FileSystemException: C:\Users\user1\Documents\GitHub\myfirstsite\dispatcher\src\conf.d\enabled_vhosts\aem_author.vhost: A required privilege is not held by the client. -> [Help 1]

Solution:

Open command prompt as Administrator and run the same command it fixes the above error.


Also refer below Issue Log from Adobe Git hub for the same:

https://github.com/adobe/aem-project-archetype/issues/329



Comments

Post a Comment

Popular posts from this blog

Direct integration Approaches with the Experience Cloud Identity Service

-
Image
 1.      Purpose Below approach will help the customers use the ID service on applications that does not support 1.            No Support for Adobe Launch or SDK or VisitorApi.js 2.            No Support for Adobe Launch or SDK but support for visiotrapi.js   2.      Methodologies ECID can be extracted using below methodologies 2.1 Direct trigger of API to fetch ECID(No Support for Adobe Launch or SDK or VisitorApi.js) We can fetch the ECID by directly triggering an http get to below DCS url of adobe along with corresponding Org ID.   Example: var org_id="-----------AdobeOrg";   "https://dpm.demdex.net/id?d_visid_ver=5.2.0&d_fieldgroup=MC&d_rtbd=json&d_ver=2&d_verify=1&d_nsid=0&d_orgid="+org_id; https://dpm.demdex.net/id?d_visid_ver=[VER]&d_fieldgroup=MC&d_rtbd=json&d_ver=2&d_verify=1&d_nsid=0&d_orgid=[ORGID]&ts=[TS]   ·...
Read more

Adobe Connected Assets

-
Image
  Adobe Connected Assets     What is Connected Assets? It’s a Out of the Box functionality provided as part of adobe AEM 6.5 onwards to connect One AEM deployment instance assets to another AEM instance. So that Content Authors from one Experience Manager instance can search and utilize the Assets from another experience Manager instance Seamlessly. Architecture: Use Case: For example, if we have different AEM instance pertaining to different Line of Business in this case lets say Legal department has one AEM instance and Tax Department has one separate AEM instance.In this case either site content authors from Legal instance or Tax instance can seamlessly access the assets in other LOB seamlessly using Connected Assets Feature. Note: Asset instance (AEM instance which sources the Assets) and site instance(AEM instance which makes use of Assets from other instance for their site content) can either reside in On prem or AMS cloud or Cloud as a Service. ...
Read more