Hi Alasdair,
Thank you very much for pointing to your blog. Since I don't see a
sample pom.xml using the technique you have described there, I have a
couple of questions for you:
a) Do you use war plugin or bundle-plugin to package the WAB?
b) Does the final Bundle-ClassPath have "." in it?
Hi Clement,
Thanks for pointing me to the ipojo webconsole plugin
I noticed that one of my 'required' services is in the state invalid. That's
the issue.
It probably could have saved me lots of time if I had seen this information
when deploying an iPojo service in the command line.
Thanks,
Kr
The Felix Team has just release the above updates on those subprojects:
* FileInstall 3.1.10: a bug fix maintenance release
* WebConsole 3.1.8: a bug fix release
* maven bundle plugin 2.3.4: this new version contains enhancements
to better leverage the maven informations, mostly detect option
On 2/7/11 5:18, Lindley Andrew wrote:
Hi Clement,
Thanks for pointing me to the ipojo webconsole plugin
I noticed that one of my 'required' services is in the state invalid. That's
the issue.
It probably could have saved me lots of time if I had seen this information
when deploying an iPojo s
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.
Sahoo
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
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 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 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.
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
10 matches
Mail list logo