geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Forrest Xia <forres...@gmail.com>
Subject Re: Why convert OSGi version when building an eba module ID?
Date Wed, 02 Mar 2011 16:28:07 GMT
The patch of jira 5427 is to convert maven-like version to OSGi-like
version, while my question is about why not using OSGi-like version directly
in the module ID for a deployed eba module?

Forrest

On Thu, Mar 3, 2011 at 12:14 AM, Shawn Jiang <genspring@gmail.com> wrote:

> See https://issues.apache.org/jira/browse/GERONIMO-5427 for the
> background.
>
>
> On Wed, Mar 2, 2011 at 11:52 PM, Forrest Xia <forrestxm@gmail.com> wrote:
>
>> Hi,
>>
>> Anyone could explain to me why need this piece of code? why not directly
>> use OSGi version in the module ID?
>>
>> public class BundleUtil {
>>
>>    ...
>>
>>     public static String getVersion(org.osgi.framework.
>> Version version) {
>>         String str = version.getMajor() + "." + version.getMinor() + "." +
>> version.getMicro();
>>         String qualifier = version.getQualifier();
>>         if (qualifier != null && qualifier.trim().length() > 0) {
>>             str += "-" + version.getQualifier().trim();
>>         }
>>         return str;
>>     }
>>
>> The piece of code convert OSGi version into traditional maven-like
>> version, I want to know why do this transformation.
>>
>> One of my concern is when I use geronimo-maven-plugin to deploy and
>> undeploy an eba, I need to manually specify the eba's Application-Version,
>> then tell geronimo-maven-plugin the exact module ID to undeploy it. But I
>> want to use maven property replacement to describe the module ID
>> automatically. Can I do that? Please advise. thanks!
>>
>> Forrest
>>
>
>
>
> --
> Shawn
>

Mime
View raw message