Hi,
Am Montag, den 07.02.2011, 18:22 + schrieb Sahoo:
> On Monday 07 February 2011 11:00 PM, Stuart McCulloch wrote:
> >
> >> Since I can't use Export-Package: ...; version=${project.version}, is there
> >> a variable/macro available to get the old behavior?
> >>
> >>
> > {local-pac
On Monday 07 February 2011 11:00 PM, Stuart McCulloch wrote:
Since I can't use Export-Package: ...; version=${project.version}, is there
a variable/macro available to get the old behavior?
{local-packages};version="${project.version}"
I didn't know I could actually use ${project.
On 7 February 2011 16:59, Sahoo wrote:
> On Monday 07 February 2011 10:10 PM, Stuart McCulloch wrote:
>
>> On 7 February 2011 15:50, Sahoo wrote:
>>
>>
>>
>>> After upgrading to 2.2.0 as well as 2.3.4 versions of the plugin, I don't
>>> see any version attribute in exported packages unless I exp
On Monday 07 February 2011 10:10 PM, Stuart McCulloch wrote:
On 7 February 2011 15:50, Sahoo wrote:
After upgrading to 2.2.0 as well as 2.3.4 versions of the plugin, I don't
see any version attribute in exported packages unless I explicitly specify
the version in the plugin configuration.
On 7 February 2011 15:50, Sahoo wrote:
> After upgrading to 2.2.0 as well as 2.3.4 versions of the plugin, I don't
> see any version attribute in exported packages unless I explicitly specify
> the version in the plugin configuration. This seems like a serious
> regression to me.
>
You'll need
5 matches
Mail list logo
