maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Ton Swieb (JIRA)" <>
Subject [jira] (MSHARED-220) Apply filtering to filenames
Date Mon, 10 Feb 2014 08:36:57 GMT


Ton Swieb commented on MSHARED-220:

My specific use case is related to running multiple versions (branches) of an OSGi services
in the same OSGi container.
For example:
v1.0 of a Foo service
v2.0 of a Foo service 

Each version of the Foo service needs it own set of configuration, which is accomplished by
specifying a PID which exists of the identifier of the OSGi service with its versionnumber
For example:

As a consequence the configuration on disk is stored in a filename which has the PID in it.
For example:

I have a Maven project for the Foo service which delivers:
1) An OSGi bundle (JAR) containing the Foo service
2) A configuration file foo-{pom.version}.cfg which contains the default configuration for
this specific version/branch of the service.

I am using the supplied patch for the filtering plugin to create the filename foo-1.0.cfg,

> Apply filtering to filenames
> ----------------------------
>                 Key: MSHARED-220
>                 URL:
>             Project: Maven Shared Components
>          Issue Type: New Feature
>          Components: maven-filtering
>            Reporter: Ton Swieb
>         Attachments: patch.txt
> It would be very helpfull if this kind of functionality can be added to the Maven Filtering
project and then subsequently to the Maven Resources Plugin.
> I added a patch which can be enabled by setting the MavenResourcesExecution.isFilterFilenames(true).
> Then ${..} parts in filenames will be replaced as part of the resource filtering.

This message was sent by Atlassian JIRA

View raw message