exporting package definitions with vlt

[Former Community Member]

We're trying to export as much configuration info to our source control system as we can. Generally we use vlt to export the appropriate crx nodes.  However, we are stuck on packages.  As far as I can tell, the package definitions are stored under /etc/packages/group/package.zip/jcr:content/vlt:definition.  The problem is that the built package itself is "package.zip", which we don't want to export and put in source control, just the definition (name, description, filters, etc); and vlt doesn't seem to want to exclude a directory but include children of that directory. 

How can we export the package definition but not the actual package?

[Yogesh_Upadhyay · Accepted solution]

Hello,

Recommend you to use sling vault plugin. You can store packaging information under META-INF folder.

http://dev.day.com/docs/en/cq/current/core/how_to/how_to_use_the_vlttool/vlt-mavenplugin.html

http://dev.day.com/docs/en/cq/current/core/how_to/how_to_use_the_vlttool/vlt-mavenplugin.html#Adding...

Let me know if that make sense.

Yogesh

[Yogesh_Upadhyay]

In that case you use vlt export or import or something to export package definition (Which is under /etc/packages/GROUP/YOUR PACKAGE) to your file system.

http://dev.day.com/docs/en/crx/current/how_to/how_to_use_the_vlttool.html

There are eclipse plugin to do that too, http://sourceforge.net/projects/vaultclipse/ you can use that a long with your SVN. 

Yogesh

[Former Community Member]

It looks like this could be used to import the package definitions from the local filesystem (and source control) to crx, not the other way around.  We are creating the packages using the crx package manager ui and we want to export those definitions.   Am I misunderstanding what the maven plugin does here?