You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Dan Peretz <dp...@interwise.com> on 2011/08/11 10:04:38 UTC
Add to Application-Content header bundles without importing them
into the EBA
Hi,
I'm working on the OSGI using the EBA Maven Plug-in.
I'm trying to add bundles to the Application-Content EBA header without packaging them into the EBA, without success. I believe that in the pom.xml, if a module is in the scope of provided, it should be written into the Application-Content header without importing it into the EBA. Is it possible to do it for your next release?
Thanks,
Dan Peretz
RE: Add to Application-Content header bundles without importing
them into the EBA
Posted by Dan Peretz <dp...@interwise.com>.
Hi,
I raised a JIRA about this issue.
Thanks,
Dan
-----Original Message-----
From: Graham Charters [mailto:gcharters@gmail.com]
Sent: Monday, August 15, 2011 3:16 PM
To: dev@aries.apache.org
Subject: Re: Add to Application-Content header bundles without importing them into the EBA
Hi Dan, if I understand correctly, you're looking for the ability to
exclude the content bundles from the .eba file. This is not possible
with the eba-maven-plugin at the moment. The
<useTransitiveDependencies /> configuration allows you to exclude
transitive dependencies, but there's no equivalent for the content.
What might have been better would be to have a single configuration of
called something like <archiveContent / > with values of none,
applicationContent, all.
Is this the sort of thing you were looking for? Have you raised a JIRA?
Regards, Graham.
On 11 August 2011 12:55, Alasdair Nottingham <no...@apache.org> wrote:
> Hi,
>
> I don't think that would make sense. The documentation on the provided
> scope[1] says:
>
> This is much like compile, but indicates you expect the JDK or a container
> to provide the dependency at runtime. For example, when building a web
> application for the Java Enterprise Edition, you would set the dependency on
> the Servlet API and related Java EE APIs to scope provided because the web
> container provides those classes.
>
> so extrapolating that to an EBA it would say that I should be excluding
> anything with a provided scope from being in the Application-Content header,
> rather than putting it in there. The important thing here is that the
> Application-Content header defines your application, not the by value
> bundles inside it. So you could have a bundle inside the .eba file that is
> not in the Application-Content and would therefore be ignored. Since the
> provided scope means "not part of my app, provided by my runtime" we should
> not be putting provided scoped dependencies in the application at all.
>
> [1]:
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
>
> On 11 August 2011 09:04, Dan Peretz <dp...@interwise.com> wrote:
>
>> Hi,
>> I'm working on the OSGI using the EBA Maven Plug-in.
>> I'm trying to add bundles to the Application-Content EBA header without
>> packaging them into the EBA, without success. I believe that in the pom.xml,
>> if a module is in the scope of provided, it should be written into the
>> Application-Content header without importing it into the EBA. Is it possible
>> to do it for your next release?
>>
>> Thanks,
>> Dan Peretz
>>
>>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Add to Application-Content header bundles without importing them
into the EBA
Posted by Graham Charters <gc...@gmail.com>.
Hi Dan,
I've checked in code to add the archiveContent support and updated the
docs: http://aries.apache.org/modules/ebamavenpluginproject.html
Note, until it's released, you'll need to check out the code and build
the plugin yourself.
Regards, Graham.
On 22 August 2011 11:57, Dan Peretz <dp...@interwise.com> wrote:
> Jira Link:
> https://issues.apache.org/jira/browse/ARIES-732
>
>
> Thanks,
> Dan
>
>
> -----Original Message-----
> From: Dan Peretz
> Sent: Monday, August 22, 2011 1:57 PM
> To: dev@aries.apache.org
> Subject: RE: Add to Application-Content header bundles without importing them into the EBA
>
> Hi,
> I raised a JIRA about this issue.
>
> Thanks,
> Dan
>
> -----Original Message-----
> From: Graham Charters [mailto:gcharters@gmail.com]
> Sent: Monday, August 15, 2011 3:16 PM
> To: dev@aries.apache.org
> Subject: Re: Add to Application-Content header bundles without importing them into the EBA
>
> Hi Dan, if I understand correctly, you're looking for the ability to
> exclude the content bundles from the .eba file. This is not possible
> with the eba-maven-plugin at the moment. The
> <useTransitiveDependencies /> configuration allows you to exclude
> transitive dependencies, but there's no equivalent for the content.
>
> What might have been better would be to have a single configuration of
> called something like <archiveContent / > with values of none,
> applicationContent, all.
>
> Is this the sort of thing you were looking for? Have you raised a JIRA?
>
> Regards, Graham.
>
> On 11 August 2011 12:55, Alasdair Nottingham <no...@apache.org> wrote:
>> Hi,
>>
>> I don't think that would make sense. The documentation on the provided
>> scope[1] says:
>>
>> This is much like compile, but indicates you expect the JDK or a container
>> to provide the dependency at runtime. For example, when building a web
>> application for the Java Enterprise Edition, you would set the dependency on
>> the Servlet API and related Java EE APIs to scope provided because the web
>> container provides those classes.
>>
>> so extrapolating that to an EBA it would say that I should be excluding
>> anything with a provided scope from being in the Application-Content header,
>> rather than putting it in there. The important thing here is that the
>> Application-Content header defines your application, not the by value
>> bundles inside it. So you could have a bundle inside the .eba file that is
>> not in the Application-Content and would therefore be ignored. Since the
>> provided scope means "not part of my app, provided by my runtime" we should
>> not be putting provided scoped dependencies in the application at all.
>>
>> [1]:
>> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
>>
>> On 11 August 2011 09:04, Dan Peretz <dp...@interwise.com> wrote:
>>
>>> Hi,
>>> I'm working on the OSGI using the EBA Maven Plug-in.
>>> I'm trying to add bundles to the Application-Content EBA header without
>>> packaging them into the EBA, without success. I believe that in the pom.xml,
>>> if a module is in the scope of provided, it should be written into the
>>> Application-Content header without importing it into the EBA. Is it possible
>>> to do it for your next release?
>>>
>>> Thanks,
>>> Dan Peretz
>>>
>>>
>>
>>
>> --
>> Alasdair Nottingham
>> not@apache.org
>>
>
RE: Add to Application-Content header bundles without importing
them into the EBA
Posted by Dan Peretz <dp...@interwise.com>.
Jira Link:
https://issues.apache.org/jira/browse/ARIES-732
Thanks,
Dan
-----Original Message-----
From: Dan Peretz
Sent: Monday, August 22, 2011 1:57 PM
To: dev@aries.apache.org
Subject: RE: Add to Application-Content header bundles without importing them into the EBA
Hi,
I raised a JIRA about this issue.
Thanks,
Dan
-----Original Message-----
From: Graham Charters [mailto:gcharters@gmail.com]
Sent: Monday, August 15, 2011 3:16 PM
To: dev@aries.apache.org
Subject: Re: Add to Application-Content header bundles without importing them into the EBA
Hi Dan, if I understand correctly, you're looking for the ability to
exclude the content bundles from the .eba file. This is not possible
with the eba-maven-plugin at the moment. The
<useTransitiveDependencies /> configuration allows you to exclude
transitive dependencies, but there's no equivalent for the content.
What might have been better would be to have a single configuration of
called something like <archiveContent / > with values of none,
applicationContent, all.
Is this the sort of thing you were looking for? Have you raised a JIRA?
Regards, Graham.
On 11 August 2011 12:55, Alasdair Nottingham <no...@apache.org> wrote:
> Hi,
>
> I don't think that would make sense. The documentation on the provided
> scope[1] says:
>
> This is much like compile, but indicates you expect the JDK or a container
> to provide the dependency at runtime. For example, when building a web
> application for the Java Enterprise Edition, you would set the dependency on
> the Servlet API and related Java EE APIs to scope provided because the web
> container provides those classes.
>
> so extrapolating that to an EBA it would say that I should be excluding
> anything with a provided scope from being in the Application-Content header,
> rather than putting it in there. The important thing here is that the
> Application-Content header defines your application, not the by value
> bundles inside it. So you could have a bundle inside the .eba file that is
> not in the Application-Content and would therefore be ignored. Since the
> provided scope means "not part of my app, provided by my runtime" we should
> not be putting provided scoped dependencies in the application at all.
>
> [1]:
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
>
> On 11 August 2011 09:04, Dan Peretz <dp...@interwise.com> wrote:
>
>> Hi,
>> I'm working on the OSGI using the EBA Maven Plug-in.
>> I'm trying to add bundles to the Application-Content EBA header without
>> packaging them into the EBA, without success. I believe that in the pom.xml,
>> if a module is in the scope of provided, it should be written into the
>> Application-Content header without importing it into the EBA. Is it possible
>> to do it for your next release?
>>
>> Thanks,
>> Dan Peretz
>>
>>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
RE: Add to Application-Content header bundles without importing
them into the EBA
Posted by Dan Peretz <dp...@interwise.com>.
Not yet, I'll raise one today or tommorow
Thanks,
Dan
-----Original Message-----
From: Graham Charters [mailto:gcharters@gmail.com]
Sent: Monday, August 15, 2011 3:16 PM
To: dev@aries.apache.org
Subject: Re: Add to Application-Content header bundles without importing them into the EBA
Hi Dan, if I understand correctly, you're looking for the ability to
exclude the content bundles from the .eba file. This is not possible
with the eba-maven-plugin at the moment. The
<useTransitiveDependencies /> configuration allows you to exclude
transitive dependencies, but there's no equivalent for the content.
What might have been better would be to have a single configuration of
called something like <archiveContent / > with values of none,
applicationContent, all.
Is this the sort of thing you were looking for? Have you raised a JIRA?
Regards, Graham.
On 11 August 2011 12:55, Alasdair Nottingham <no...@apache.org> wrote:
> Hi,
>
> I don't think that would make sense. The documentation on the provided
> scope[1] says:
>
> This is much like compile, but indicates you expect the JDK or a container
> to provide the dependency at runtime. For example, when building a web
> application for the Java Enterprise Edition, you would set the dependency on
> the Servlet API and related Java EE APIs to scope provided because the web
> container provides those classes.
>
> so extrapolating that to an EBA it would say that I should be excluding
> anything with a provided scope from being in the Application-Content header,
> rather than putting it in there. The important thing here is that the
> Application-Content header defines your application, not the by value
> bundles inside it. So you could have a bundle inside the .eba file that is
> not in the Application-Content and would therefore be ignored. Since the
> provided scope means "not part of my app, provided by my runtime" we should
> not be putting provided scoped dependencies in the application at all.
>
> [1]:
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
>
> On 11 August 2011 09:04, Dan Peretz <dp...@interwise.com> wrote:
>
>> Hi,
>> I'm working on the OSGI using the EBA Maven Plug-in.
>> I'm trying to add bundles to the Application-Content EBA header without
>> packaging them into the EBA, without success. I believe that in the pom.xml,
>> if a module is in the scope of provided, it should be written into the
>> Application-Content header without importing it into the EBA. Is it possible
>> to do it for your next release?
>>
>> Thanks,
>> Dan Peretz
>>
>>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Add to Application-Content header bundles without importing them
into the EBA
Posted by Graham Charters <gc...@gmail.com>.
Hi Dan, if I understand correctly, you're looking for the ability to
exclude the content bundles from the .eba file. This is not possible
with the eba-maven-plugin at the moment. The
<useTransitiveDependencies /> configuration allows you to exclude
transitive dependencies, but there's no equivalent for the content.
What might have been better would be to have a single configuration of
called something like <archiveContent / > with values of none,
applicationContent, all.
Is this the sort of thing you were looking for? Have you raised a JIRA?
Regards, Graham.
On 11 August 2011 12:55, Alasdair Nottingham <no...@apache.org> wrote:
> Hi,
>
> I don't think that would make sense. The documentation on the provided
> scope[1] says:
>
> This is much like compile, but indicates you expect the JDK or a container
> to provide the dependency at runtime. For example, when building a web
> application for the Java Enterprise Edition, you would set the dependency on
> the Servlet API and related Java EE APIs to scope provided because the web
> container provides those classes.
>
> so extrapolating that to an EBA it would say that I should be excluding
> anything with a provided scope from being in the Application-Content header,
> rather than putting it in there. The important thing here is that the
> Application-Content header defines your application, not the by value
> bundles inside it. So you could have a bundle inside the .eba file that is
> not in the Application-Content and would therefore be ignored. Since the
> provided scope means "not part of my app, provided by my runtime" we should
> not be putting provided scoped dependencies in the application at all.
>
> [1]:
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
>
> On 11 August 2011 09:04, Dan Peretz <dp...@interwise.com> wrote:
>
>> Hi,
>> I'm working on the OSGI using the EBA Maven Plug-in.
>> I'm trying to add bundles to the Application-Content EBA header without
>> packaging them into the EBA, without success. I believe that in the pom.xml,
>> if a module is in the scope of provided, it should be written into the
>> Application-Content header without importing it into the EBA. Is it possible
>> to do it for your next release?
>>
>> Thanks,
>> Dan Peretz
>>
>>
>
>
> --
> Alasdair Nottingham
> not@apache.org
>
Re: Add to Application-Content header bundles without importing them
into the EBA
Posted by Alasdair Nottingham <no...@apache.org>.
Hi,
I don't think that would make sense. The documentation on the provided
scope[1] says:
This is much like compile, but indicates you expect the JDK or a container
to provide the dependency at runtime. For example, when building a web
application for the Java Enterprise Edition, you would set the dependency on
the Servlet API and related Java EE APIs to scope provided because the web
container provides those classes.
so extrapolating that to an EBA it would say that I should be excluding
anything with a provided scope from being in the Application-Content header,
rather than putting it in there. The important thing here is that the
Application-Content header defines your application, not the by value
bundles inside it. So you could have a bundle inside the .eba file that is
not in the Application-Content and would therefore be ignored. Since the
provided scope means "not part of my app, provided by my runtime" we should
not be putting provided scoped dependencies in the application at all.
[1]:
http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#Dependency_Scope
On 11 August 2011 09:04, Dan Peretz <dp...@interwise.com> wrote:
> Hi,
> I'm working on the OSGI using the EBA Maven Plug-in.
> I'm trying to add bundles to the Application-Content EBA header without
> packaging them into the EBA, without success. I believe that in the pom.xml,
> if a module is in the scope of provided, it should be written into the
> Application-Content header without importing it into the EBA. Is it possible
> to do it for your next release?
>
> Thanks,
> Dan Peretz
>
>
--
Alasdair Nottingham
not@apache.org