You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by Jeremy Hughes <hu...@apache.org> on 2011/09/30 17:35:22 UTC
DEPENDENCIES file
Hi Kevan,
On another thread (see bottom of this email) a few days ago you said:
"This archive contains DISCLAIMER and DEPENDENCIES files which are not
in the svn tag."
There doesn't seem to be consistency across Apache on whether to
include the DEPENDENCIES file or not. What are the arguments for not
including it? Certainly Apache Felix favour including it [1]
The way we create releases is our default-parent/pom.xml is configured
to use the maven-remote-resources-plugin to pull in the resource
bundle org.apache:apache-jar-resource-bundle:1.4 ... which is an
Apache standard set of resources as far as I can tell. This includes a
DEPENDENCIES.vm file which of course means our release artifacts have
a DEPENDENCIES file in them.
I've tried adding an
<excludes><exclude>**/DEPENDENCIES*</exclude></excludes> to the
<configuration> element of the maven-remote-resources-plugin in our
parent/default-parent/pom.xml but that doesn't affect what is put into
the source zip.
I'd like to continue using the apache-jar-resource-bundle but without
pulling in the DEPENDENCIES. Unless someone knows of a way of using
the apache-jar-resources-bundle without the DEPENDENCIES file part, I
think our best option is to pull the contents of that into the
default-pom module. Anyone got any other suggestions?
[1] http://felix.apache.org/site/dependencies-file-template.html
Cheers,
Jeremy
---------- Forwarded message ----------
From: Kevan Miller <ke...@gmail.com>
Date: 25 September 2011 16:47
Subject: Re: [RESULT] [VOTE] Release Aries application-0.2.2 (1st attempt)
To: dev@aries.apache.org
On Sep 25, 2011, at 11:01 AM, Rex Wang wrote:
> Vote result:
> The vote for Aries application-0.2.2 release passed with the following +1s from PMC members:
> Jarek Gawor,
> Jeremy Hughes,
> Kevan Miller
>
> There is no +0 or -1, Thanks for the review. I will promote it soon.
>
> BTW, I sorry not note this, what's DISCLAIMER do you mean?
Look inside the source release artifact
(application-0.2.2-source-release.zip). This archive contains
DISCLAIMER and DEPENDENCIES files which are not in the svn tag.
The DISCLAIMER is not needed, since we aren't in incubator any longer...
--kevan
Re: DEPENDENCIES file
Posted by Jeremy Hughes <hu...@apache.org>.
Hi David, any hints on how to configure the remote resources plugin to
use org.apache:apache-jar-resource-bundle:1.4 but exclude the
DEPENDENCIES file?
I've tried adding an
<excludes><exclude>**/DEPENDENCIES*</exclude></excludes> to the
<configuration> element of the maven-remote-resources-plugin in our
parent/default-parent/pom.xml but that doesn't affect what is put into
the source zip.
Thanks,
Jeremy
On 3 October 2011 17:09, David Jencks <da...@yahoo.com> wrote:
> I'm the origin of the DEPENDENCIES file generated by the maven-remote-resources-plugin (before that the same info was being mistakenly included in the generated NOTICE file) but for an osgi project I think it is misleading and better dropped. It was supposed to give you a hint about the other jars you'd probably want to use with the jar with the DEPENDENCIES file, a function better served by package imports and OBR.
>
> thanks
> david jencks
>
> On Oct 3, 2011, at 8:41 AM, Kevan Miller wrote:
>
>>
>> On Sep 30, 2011, at 11:35 AM, Jeremy Hughes wrote:
>>
>>> Hi Kevan,
>>>
>>> On another thread (see bottom of this email) a few days ago you said:
>>>
>>> "This archive contains DISCLAIMER and DEPENDENCIES files which are not
>>> in the svn tag."
>>>
>>> There doesn't seem to be consistency across Apache on whether to
>>> include the DEPENDENCIES file or not. What are the arguments for not
>>> including it? Certainly Apache Felix favour including it [1]
>>
>> That's a decision of the Felix project. There's no ASF requirement for such a file (ASF requirements are for a LICENSE/NOTICE file). If the Aries project would find a DEPENDENCIES file useful, then by all means include the file. If the file is useful, why only include in source releases? Why not include the file in SVN?
>>
>> In my experience, the DEPENDENDENCIES do not necessarily reflect the artifacts that might be used in an actual runtime environment. DEPENDENCIES for a jar/bundle are more useful than DEPENDENCIES for an entire project...
>>
>> I object to a DISCLAIMER file being included in any future Aries' releases. I have no objection to DEPENDENCIES files -- just question their utility. I probably wouldn't have mentioned DEPENDENCIES if I wasn't mentioning DISCLAIMER...
>>
>> --kevan
>
>
Re: DEPENDENCIES file
Posted by David Jencks <da...@yahoo.com>.
I'm the origin of the DEPENDENCIES file generated by the maven-remote-resources-plugin (before that the same info was being mistakenly included in the generated NOTICE file) but for an osgi project I think it is misleading and better dropped. It was supposed to give you a hint about the other jars you'd probably want to use with the jar with the DEPENDENCIES file, a function better served by package imports and OBR.
thanks
david jencks
On Oct 3, 2011, at 8:41 AM, Kevan Miller wrote:
>
> On Sep 30, 2011, at 11:35 AM, Jeremy Hughes wrote:
>
>> Hi Kevan,
>>
>> On another thread (see bottom of this email) a few days ago you said:
>>
>> "This archive contains DISCLAIMER and DEPENDENCIES files which are not
>> in the svn tag."
>>
>> There doesn't seem to be consistency across Apache on whether to
>> include the DEPENDENCIES file or not. What are the arguments for not
>> including it? Certainly Apache Felix favour including it [1]
>
> That's a decision of the Felix project. There's no ASF requirement for such a file (ASF requirements are for a LICENSE/NOTICE file). If the Aries project would find a DEPENDENCIES file useful, then by all means include the file. If the file is useful, why only include in source releases? Why not include the file in SVN?
>
> In my experience, the DEPENDENDENCIES do not necessarily reflect the artifacts that might be used in an actual runtime environment. DEPENDENCIES for a jar/bundle are more useful than DEPENDENCIES for an entire project...
>
> I object to a DISCLAIMER file being included in any future Aries' releases. I have no objection to DEPENDENCIES files -- just question their utility. I probably wouldn't have mentioned DEPENDENCIES if I wasn't mentioning DISCLAIMER...
>
> --kevan
Re: DEPENDENCIES file
Posted by Kevan Miller <ke...@gmail.com>.
On Sep 30, 2011, at 11:35 AM, Jeremy Hughes wrote:
> Hi Kevan,
>
> On another thread (see bottom of this email) a few days ago you said:
>
> "This archive contains DISCLAIMER and DEPENDENCIES files which are not
> in the svn tag."
>
> There doesn't seem to be consistency across Apache on whether to
> include the DEPENDENCIES file or not. What are the arguments for not
> including it? Certainly Apache Felix favour including it [1]
That's a decision of the Felix project. There's no ASF requirement for such a file (ASF requirements are for a LICENSE/NOTICE file). If the Aries project would find a DEPENDENCIES file useful, then by all means include the file. If the file is useful, why only include in source releases? Why not include the file in SVN?
In my experience, the DEPENDENDENCIES do not necessarily reflect the artifacts that might be used in an actual runtime environment. DEPENDENCIES for a jar/bundle are more useful than DEPENDENCIES for an entire project...
I object to a DISCLAIMER file being included in any future Aries' releases. I have no objection to DEPENDENCIES files -- just question their utility. I probably wouldn't have mentioned DEPENDENCIES if I wasn't mentioning DISCLAIMER...
--kevan