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
Bedrock Mission!

Learn more

View all

Sign in to view all badges

[AEM Gems Webinar] Accelerating Experience Manager as a Cloud Service development with Rapid Development Environments
SOLVED

Vault Filter Not Applying

Avatar

Level 3

I am using the maven multimodule content package archetype in my project as listed here:
https://docs.adobe.com/docs/en/aem/6-0/develop/dev-tools/vlt-mavenplugin.html#multimodule-content-pa...

I changed the <version> in all three POM files from "1.0-SNAPSHOT" to "${project.version}".

The filters are included in the package when deployed to the Local environment as expected, but when deployed to the Dev and Staging environment, the filters are not there.

This did work previously when all three POMs had the "1.0-SHAPSHOT" version, but we would like to include the revision number in the content package title, hence the project.version update.

Is there anything else that I need to change?


Thanks in advance!

1 Accepted Solution

Avatar

Correct answer by
Community Advisor

Can you check in your CI environment are you overriding version or filter?
If you are using version in your child's You have to skip <version> tag in child.
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance

If this doesn't resolve this then please post your POM.xml here so that we can validate if everything is correct.

Regards,

Amit

View solution in original post

0 Replies

Avatar

Level 10

Are you saying when same is deployed in local it works as expected but when deployed in Dev or staging it didn't worked? Correct me if I am wrong.

Question: Are you deploying code manually or using some CI tools

Avatar

Level 3

Sorry, I should have specified - local is using IntelliJ; remote(dev/stage) we're using Bamboo as the CI tool.

Avatar

Level 10

When you didnt changed 1.0-SNAPSHOT" to "${project.version}".  the code was deploying correctly?

Avatar

Level 3

Yes, that's correct. When I changed the version to ${project.version} the remote deployments did not apply the filter. Could it possibly be a Bamboo setting somewhere?

Avatar

Level 10

If it works with Maven and without using Bamboo - I would think that is the issue. I like using only Maven to build OSGi and have never experienced an issue. 

Avatar

Correct answer by
Community Advisor

Can you check in your CI environment are you overriding version or filter?
If you are using version in your child's You have to skip <version> tag in child.
http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Project_Inheritance

If this doesn't resolve this then please post your POM.xml here so that we can validate if everything is correct.

Regards,

Amit