server side plugin versions

Bryan Kearney bkearney at redhat.com
Tue Jan 12 13:42:15 UTC 2010


I looked a bit at this, could we stick the git commit hash in there as well?

-- bk

On 01/11/2010 06:33 PM, Ian Springer wrote:
> If you mean how does the Maven artifact version end up in the Manifest,
> this is done via a couple configuration options that are passed to the
> jar plugin, specifically:
>
> <plugin>
> <artifactId>maven-jar-plugin</artifactId>
> <configuration>
> <archive>
> <manifest>
> <addDefaultSpecificationEntries>true</addDefaultSpecificationEntries>
> <addDefaultImplementationEntries>true</addDefaultImplementationEntries>
> </manifest>
>               ...
> </archive>
> </configuration>
> </plugin>
>
> This is found in the RHQ root pom, so I'm surprised that the server
> plugin jars' Manifests do not already contain the version attributes.
>
> On 01/11/2010 04:45 PM, John Mazzitelli wrote:
>> The agent plugins seem to get their version strings injected into
>> MANIFEST.MF ImplementationVersion by maven. This lets our build process
>> stamp the plugins with the proper versions.
>>
>> Server side plugins don't have that. Versioning is ad-hoc for server
>> plugins.
>>
>> We need a common way for all our server plugins to be versioned so its
>> more maintainable.
>>
>> I actually don't know the trick the agent plugins do to get themselves
>> versioned. Ian? do you know? I want the server plugins to do the same
>> thing so everthing is consistent.
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/rhq-devel
>>
>
> _______________________________________________
> rhq-devel mailing list
> rhq-devel at lists.fedorahosted.org
> https://fedorahosted.org/mailman/listinfo/rhq-devel



More information about the rhq-devel mailing list