Your achievements

Level 1

0% to

Level 2

Tip /
Sign in

Sign in to Community

to gain points, level up, and earn exciting badges like the new
BedrockMission!

Learn more

View all

Sign in to view all badges

SOLVED

Maven build failed all of a sudden.

kevingtan
Level 3
Level 3

Hi all,

I have been building my AEM 6.0 dev site for years without any related issues as the following. I always run the build command as:

mvn -Pinstall -Pinstall-publish clean install

It basically builds the package to the author and publisher the same time. It has been working since the morning but all of a sudden it stopped working. The error is:

 

[INFO] --- content-package-maven-plugin:0.0.20:install (install-content-package) @ base-content ---

[INFO] Installing base-content (/Users/kevintan/workspace/aem60/aem-accessibility/aem/content/target/base-content-4.4.1-AS-SNAPSHOT.zip) to http://123.45.67.89:4502/crx/packmgr/service.jsp

[ERROR] Request failed: com.day.jcr.vault.packaging.PackageException: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.RepositoryException: OakName0001: Invalid namespace prefix([, stFNT, pmtm, creatorAtom, def, adhocwf, mediapro, Image, xmpPLUS, Item, dex, xml, xmp, viewerpreset, prism, crss, GIMP, pdfaSchema, xmpDM, stArea, fpoinfo, xmpMM, exif, drone-dji, xmpRights, pdfaProperty, wn_private, stEvt, Profile, bext, stMfs, GPano, jcr, ExtensisFontSense, DICOM, mix, apple-fi, cc, sv, GettyImagesGIFT, xmpBJ, wn_image_info, cq, sling, Attrib, rdf, MicrosoftPhoto, dc, vlt, crxde, lr, xmpTPg, prismusagerights, photomechanic, dam, GCreations, Container, s7sitecatalyst, xmpNote, Camera, rep, psAux, xmpGImg, MP, Device, Iptc4xmpExt, photoshop, pdfuaid, prl, mwg-rs, plus, pdfxid, panorama, xmpG, acdsee, idPriv, crop, fwr, tiff, nt, pdfaExtension, s7userdata, xsl, FA1, oak, attr, oauth, prefix0, social, crs, exifEX, album, crx, stDim, DepthMap, adobe_dam, pdfx, pdf, Iptc4xmpCore, GCamera, granite, stRef, wn_thumbnails, slingevent, illustrator]): strories (500)

 

The related pom.xml section is:

<plugin>

                        <groupId>com.day.jcr.vault</groupId>

                        <artifactId>content-package-maven-plugin</artifactId>

                        <executions>

                            <execution>

                                <id>install-content-package</id>

                                <goals>

                                    <goal>install</goal>

                                </goals>

                            </execution>

                        </execution>

</plugin>

 

Then I looked at my .m2 folder and found a few versions of com/day/jcr/vault/

content-package-maven-plugin, and changed it to 0.0.24, got the same error. Any higher version will fail immediately with a very obvious not-compatible error message. 

 

Now I am making a bit easier:

mvn clean install

And it works. So It's obvious building package to remote sites using the com.day.jcr.vault/

content-package-maven-plugin will fail. Can anyone please help? 

 

I am using Maven 3.6.2. It has been working for at least 4 years, and it works for AEM6.5, which is using version 1.0.2 of content-package-maven-plugin

 

Thanks!

 

-K

 

1 Accepted Solution
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

Hi,

can you check if you can install this package on Publish(Manual install)?

from error I can see you have some custom node namespace which are not avavilble in AEM nstance

[ERROR] Request failed: com.day.jcr.vault.packaging.PackageException: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.RepositoryException: OakName0001: Invalid namespace prefix

 

View solution in original post

2 Replies
Arun_Patidar
Correct answer by
Community Advisor
Community Advisor

Hi,

can you check if you can install this package on Publish(Manual install)?

from error I can see you have some custom node namespace which are not avavilble in AEM nstance

[ERROR] Request failed: com.day.jcr.vault.packaging.PackageException: org.apache.jackrabbit.vault.packaging.PackageException: javax.jcr.RepositoryException: OakName0001: Invalid namespace prefix

 

View solution in original post

kevingtan
Level 3
Level 3

Thanks for your advice. I actually did something silly, comment out a jsp file where it's referenced by another file.