Vault Filter Not Applying | Community
Skip to main content
G
Gunars_V
Level 3
February 24, 2016
Solved

Vault Filter Not Applying

  • February 24, 2016
  • 6 replies
  • 2084 views

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-package-archetype

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!

This post is no longer active and is closed to new replies. Need help? Start a new post to ask your question.
Best answer by Amit_Kumar

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

6 replies

edubey
edubey
Level 10
February 24, 2016

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

G
Gunars_VAuthor
Level 3
February 24, 2016

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

edubey
edubey
Level 10
February 25, 2016

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

G
Gunars_VAuthor
Level 3
February 25, 2016

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?

smacdonald2008
smacdonald2008
Level 10
February 25, 2016

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. 

Amit_Kumar
Amit_KumarAccepted solution
Level 10
February 26, 2016

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

Terms & ConditionsAccessibility statement

Loading footer...