You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@aries.apache.org by John W Ross <jw...@us.ibm.com> on 2013/04/18 11:55:31 UTC
[VOTE] subsystem-bundle 1.0.0
This is a vote for the release of subsystem-bundle 1.0.0, an uber bundle
containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
Staging Area:
https://repository.apache.org/content/repositories/orgapachearies-117/
Tags:
http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
This vote will remain open for at least 72 hours.
John
Re: [VOTE] subsystem-bundle 1.0.0
Posted by Tang Yong <ta...@cn.fujitsu.com>.
+1 have waited for the day long time, :)
--Tang
John W Ross wrote:
> This is a vote for the release of subsystem-bundle 1.0.0, an uber bundle
> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>
> Staging Area:
> https://repository.apache.org/content/repositories/orgapachearies-117/
>
> Tags:
> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>
> This vote will remain open for at least 72 hours.
>
> John
--
－－－－－－－－－－－－－－－－－－－－－－
Tang Yong
Senior Engineer
Glassfish Team Developer(OSGi&OSGi-JavaEE)
OSGi Alliance Supporter
Blog: http://osgizone.typepad.com/tangyong/
Nanjing Fujitsu NanDa Software Tec CO.,LTD
http://www.fujitsu.com/cn/fnst
Tel: +86-25-86630566-8310
Fax: +86-25-83317685
－－－－－－－－－－－－－－－－－－－－－－
Re: Generating source for uber bundles
Posted by David Jencks <da...@yahoo.com>.
+1 thanks :-)
david jencks
On Apr 25, 2013, at 9:12 AM, Jeremy Hughes <jp...@gmail.com> wrote:
> +1 .. if it helps some people and doesn't hurt the rest then it must be
> good.
>
>
> On 25 April 2013 17:04, John W Ross <jw...@us.ibm.com> wrote:
>
>>
>> I agree, and, based on Stuart's response to your other note, it seems like
>> he's at least okay with it.
>>
>> The infrastructure for generating the sources.jar is already there as long
>> as you specify the deploy profile when running mvn release:prepare/perform.
>>
>> Unless there are any objections, I'll redo the subsystem-bundle release
>> with a sources.jar containing the complete source, but a source-release.zip
>> representing what was actually there when it was built (which is how it is
>> now).
>>
>> John
>>
>>>
>>> Re: Generating source for uber bundles
>>>
>>> As I mentioned in another thread, the source-release is supposed to
>>> be an accurate representation of how you built the project. Since
>>> this one is built by aggregating other jars, it should NOT include
>>> the source of those jars, it should be what the maven plugin comes
>>> up with unassisted.
>>>
>>> The non-mandatory for-the-convenience-of-debugging source.jar can
>>> have the aggregated source of the aggregated jars, but you can also
>>> leave it out.
>>>
>>> thanks
>>> david jencks
>>> On Apr 25, 2013, at 6:55 AM, John W Ross <jw...@us.ibm.com> wrote:
>>>
>>>>
>>>> The subsystem pom, following the pattern of other projects with uber
>>>> bundles such as application and blueprint, was already configured to
>>>> aggregate the source. However, one must specify the "deploy" profile
>> when
>>>> generating the release artifacts in order for the aggregation to occur.
>>>>
>>>> Specifying the "deploy" profile will get the source in the sources jar
>>>> (e.g., org.apache.aries.subsystem-1.0.0-SNAPSHOT-sources.jar) but not
>> in
>>>> the source-release zip (e.g.,
>>>> org.apache.aries.subsystem-1.0.0-SNAPSHOT-source-release.zip).
>>>>
>>>> Any advice on how to get the aggregated source in the source-release
>> zip
>>>> file?
>>>>
>>>> John
>>>>
>>>>>
>>>>> Re: [VOTE] subsystem-bundle 1.0.0
>>>>>
>>>>> Yep, they're empty. Nice catch. I wonder if there's a way to put some
>>>> sort
>>>>> of sanity check into the verify script for this.
>>>>>
>>>>> Anyway, I'll have to figure out how to fix this. Presumably this means
>>>>> dropping the current staging repository, deleting the svn tag, and
>>>> starting
>>>>> over. Sorry!
>>>>>
>>>>> John
>>>>>
>>>>>>
>>>>>> Re: [VOTE] subsystem-bundle 1.0.0
>>>>>>
>>>>>> On 18 Apr 2013, at 10:55, John W Ross wrote:
>>>>>>
>>>>>>> This is a vote for the release of subsystem-bundle 1.0.0, an uber
>>>>> bundle
>>>>>>> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>>>>>>>
>>>>>>> Staging Area:
>>>>>>>
>>>> https://repository.apache.org/content/repositories/orgapachearies-117/
>>>>>>>
>>>>>>> Tags:
>>>>>>>
>>>>>
>> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>>>>>>>
>>>>>>> This vote will remain open for at least 72 hours.
>>>>>>
>>>>>> I can't see any sources in either org.apache.aries.subsystem-1.0.0-
>>>>>> sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
>>>>>>
>>>>>> It's important that the release contains sources so people can build
>>>>>> it themselves: http://www.apache.org/dev/release.html#what-must-
>>>>>> every-release-contain
>>>>>>
>>>>>> Note that it is possible to aggregate the source for "uber-bundles"
>>>>>> by using the maven-dependency-plugin to unpack the sources of all
>>>>>> bundled dependencies.
>>>>>>
>>>>>>> John
>>>
>>
Re: Generating source for uber bundles
Posted by Jeremy Hughes <jp...@gmail.com>.
+1 .. if it helps some people and doesn't hurt the rest then it must be
good.
On 25 April 2013 17:04, John W Ross <jw...@us.ibm.com> wrote:
>
> I agree, and, based on Stuart's response to your other note, it seems like
> he's at least okay with it.
>
> The infrastructure for generating the sources.jar is already there as long
> as you specify the deploy profile when running mvn release:prepare/perform.
>
> Unless there are any objections, I'll redo the subsystem-bundle release
> with a sources.jar containing the complete source, but a source-release.zip
> representing what was actually there when it was built (which is how it is
> now).
>
> John
>
> >
> > Re: Generating source for uber bundles
> >
> > As I mentioned in another thread, the source-release is supposed to
> > be an accurate representation of how you built the project. Since
> > this one is built by aggregating other jars, it should NOT include
> > the source of those jars, it should be what the maven plugin comes
> > up with unassisted.
> >
> > The non-mandatory for-the-convenience-of-debugging source.jar can
> > have the aggregated source of the aggregated jars, but you can also
> > leave it out.
> >
> > thanks
> > david jencks
> > On Apr 25, 2013, at 6:55 AM, John W Ross <jw...@us.ibm.com> wrote:
> >
> > >
> > > The subsystem pom, following the pattern of other projects with uber
> > > bundles such as application and blueprint, was already configured to
> > > aggregate the source. However, one must specify the "deploy" profile
> when
> > > generating the release artifacts in order for the aggregation to occur.
> > >
> > > Specifying the "deploy" profile will get the source in the sources jar
> > > (e.g., org.apache.aries.subsystem-1.0.0-SNAPSHOT-sources.jar) but not
> in
> > > the source-release zip (e.g.,
> > > org.apache.aries.subsystem-1.0.0-SNAPSHOT-source-release.zip).
> > >
> > > Any advice on how to get the aggregated source in the source-release
> zip
> > > file?
> > >
> > > John
> > >
> > >>
> > >> Re: [VOTE] subsystem-bundle 1.0.0
> > >>
> > >> Yep, they're empty. Nice catch. I wonder if there's a way to put some
> > > sort
> > >> of sanity check into the verify script for this.
> > >>
> > >> Anyway, I'll have to figure out how to fix this. Presumably this means
> > >> dropping the current staging repository, deleting the svn tag, and
> > > starting
> > >> over. Sorry!
> > >>
> > >> John
> > >>
> > >>>
> > >>> Re: [VOTE] subsystem-bundle 1.0.0
> > >>>
> > >>> On 18 Apr 2013, at 10:55, John W Ross wrote:
> > >>>
> > >>>> This is a vote for the release of subsystem-bundle 1.0.0, an uber
> > >> bundle
> > >>>> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
> > >>>>
> > >>>> Staging Area:
> > >>>>
> > > https://repository.apache.org/content/repositories/orgapachearies-117/
> > >>>>
> > >>>> Tags:
> > >>>>
> > >>
> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
> > >>>>
> > >>>> This vote will remain open for at least 72 hours.
> > >>>
> > >>> I can't see any sources in either org.apache.aries.subsystem-1.0.0-
> > >>> sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
> > >>>
> > >>> It's important that the release contains sources so people can build
> > >>> it themselves: http://www.apache.org/dev/release.html#what-must-
> > >>> every-release-contain
> > >>>
> > >>> Note that it is possible to aggregate the source for "uber-bundles"
> > >>> by using the maven-dependency-plugin to unpack the sources of all
> > >>> bundled dependencies.
> > >>>
> > >>>> John
> >
>
Re: Generating source for uber bundles
Posted by John W Ross <jw...@us.ibm.com>.
I agree, and, based on Stuart's response to your other note, it seems like
he's at least okay with it.
The infrastructure for generating the sources.jar is already there as long
as you specify the deploy profile when running mvn release:prepare/perform.
Unless there are any objections, I'll redo the subsystem-bundle release
with a sources.jar containing the complete source, but a source-release.zip
representing what was actually there when it was built (which is how it is
now).
John
>
> Re: Generating source for uber bundles
>
> As I mentioned in another thread, the source-release is supposed to
> be an accurate representation of how you built the project. Since
> this one is built by aggregating other jars, it should NOT include
> the source of those jars, it should be what the maven plugin comes
> up with unassisted.
>
> The non-mandatory for-the-convenience-of-debugging source.jar can
> have the aggregated source of the aggregated jars, but you can also
> leave it out.
>
> thanks
> david jencks
> On Apr 25, 2013, at 6:55 AM, John W Ross <jw...@us.ibm.com> wrote:
>
> >
> > The subsystem pom, following the pattern of other projects with uber
> > bundles such as application and blueprint, was already configured to
> > aggregate the source. However, one must specify the "deploy" profile
when
> > generating the release artifacts in order for the aggregation to occur.
> >
> > Specifying the "deploy" profile will get the source in the sources jar
> > (e.g., org.apache.aries.subsystem-1.0.0-SNAPSHOT-sources.jar) but not
in
> > the source-release zip (e.g.,
> > org.apache.aries.subsystem-1.0.0-SNAPSHOT-source-release.zip).
> >
> > Any advice on how to get the aggregated source in the source-release
zip
> > file?
> >
> > John
> >
> >>
> >> Re: [VOTE] subsystem-bundle 1.0.0
> >>
> >> Yep, they're empty. Nice catch. I wonder if there's a way to put some
> > sort
> >> of sanity check into the verify script for this.
> >>
> >> Anyway, I'll have to figure out how to fix this. Presumably this means
> >> dropping the current staging repository, deleting the svn tag, and
> > starting
> >> over. Sorry!
> >>
> >> John
> >>
> >>>
> >>> Re: [VOTE] subsystem-bundle 1.0.0
> >>>
> >>> On 18 Apr 2013, at 10:55, John W Ross wrote:
> >>>
> >>>> This is a vote for the release of subsystem-bundle 1.0.0, an uber
> >> bundle
> >>>> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
> >>>>
> >>>> Staging Area:
> >>>>
> > https://repository.apache.org/content/repositories/orgapachearies-117/
> >>>>
> >>>> Tags:
> >>>>
> >>
http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
> >>>>
> >>>> This vote will remain open for at least 72 hours.
> >>>
> >>> I can't see any sources in either org.apache.aries.subsystem-1.0.0-
> >>> sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
> >>>
> >>> It's important that the release contains sources so people can build
> >>> it themselves: http://www.apache.org/dev/release.html#what-must-
> >>> every-release-contain
> >>>
> >>> Note that it is possible to aggregate the source for "uber-bundles"
> >>> by using the maven-dependency-plugin to unpack the sources of all
> >>> bundled dependencies.
> >>>
> >>>> John
>
Re: Generating source for uber bundles
Posted by David Jencks <da...@yahoo.com>.
As I mentioned in another thread, the source-release is supposed to be an accurate representation of how you built the project. Since this one is built by aggregating other jars, it should NOT include the source of those jars, it should be what the maven plugin comes up with unassisted.
The non-mandatory for-the-convenience-of-debugging source.jar can have the aggregated source of the aggregated jars, but you can also leave it out.
thanks
david jencks
On Apr 25, 2013, at 6:55 AM, John W Ross <jw...@us.ibm.com> wrote:
>
> The subsystem pom, following the pattern of other projects with uber
> bundles such as application and blueprint, was already configured to
> aggregate the source. However, one must specify the "deploy" profile when
> generating the release artifacts in order for the aggregation to occur.
>
> Specifying the "deploy" profile will get the source in the sources jar
> (e.g., org.apache.aries.subsystem-1.0.0-SNAPSHOT-sources.jar) but not in
> the source-release zip (e.g.,
> org.apache.aries.subsystem-1.0.0-SNAPSHOT-source-release.zip).
>
> Any advice on how to get the aggregated source in the source-release zip
> file?
>
> John
>
>>
>> Re: [VOTE] subsystem-bundle 1.0.0
>>
>> Yep, they're empty. Nice catch. I wonder if there's a way to put some
> sort
>> of sanity check into the verify script for this.
>>
>> Anyway, I'll have to figure out how to fix this. Presumably this means
>> dropping the current staging repository, deleting the svn tag, and
> starting
>> over. Sorry!
>>
>> John
>>
>>>
>>> Re: [VOTE] subsystem-bundle 1.0.0
>>>
>>> On 18 Apr 2013, at 10:55, John W Ross wrote:
>>>
>>>> This is a vote for the release of subsystem-bundle 1.0.0, an uber
>> bundle
>>>> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>>>>
>>>> Staging Area:
>>>>
> https://repository.apache.org/content/repositories/orgapachearies-117/
>>>>
>>>> Tags:
>>>>
>> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>>>>
>>>> This vote will remain open for at least 72 hours.
>>>
>>> I can't see any sources in either org.apache.aries.subsystem-1.0.0-
>>> sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
>>>
>>> It's important that the release contains sources so people can build
>>> it themselves: http://www.apache.org/dev/release.html#what-must-
>>> every-release-contain
>>>
>>> Note that it is possible to aggregate the source for "uber-bundles"
>>> by using the maven-dependency-plugin to unpack the sources of all
>>> bundled dependencies.
>>>
>>>> John
Generating source for uber bundles
Posted by John W Ross <jw...@us.ibm.com>.
The subsystem pom, following the pattern of other projects with uber
bundles such as application and blueprint, was already configured to
aggregate the source. However, one must specify the "deploy" profile when
generating the release artifacts in order for the aggregation to occur.
Specifying the "deploy" profile will get the source in the sources jar
(e.g., org.apache.aries.subsystem-1.0.0-SNAPSHOT-sources.jar) but not in
the source-release zip (e.g.,
org.apache.aries.subsystem-1.0.0-SNAPSHOT-source-release.zip).
Any advice on how to get the aggregated source in the source-release zip
file?
John
>
> Re: [VOTE] subsystem-bundle 1.0.0
>
> Yep, they're empty. Nice catch. I wonder if there's a way to put some
sort
> of sanity check into the verify script for this.
>
> Anyway, I'll have to figure out how to fix this. Presumably this means
> dropping the current staging repository, deleting the svn tag, and
starting
> over. Sorry!
>
> John
>
> >
> > Re: [VOTE] subsystem-bundle 1.0.0
> >
> > On 18 Apr 2013, at 10:55, John W Ross wrote:
> >
> > > This is a vote for the release of subsystem-bundle 1.0.0, an uber
> bundle
> > > containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
> > >
> > > Staging Area:
> > >
https://repository.apache.org/content/repositories/orgapachearies-117/
> > >
> > > Tags:
> > >
> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
> > >
> > > This vote will remain open for at least 72 hours.
> >
> > I can't see any sources in either org.apache.aries.subsystem-1.0.0-
> > sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
> >
> > It's important that the release contains sources so people can build
> > it themselves: http://www.apache.org/dev/release.html#what-must-
> > every-release-contain
> >
> > Note that it is possible to aggregate the source for "uber-bundles"
> > by using the maven-dependency-plugin to unpack the sources of all
> > bundled dependencies.
> >
> > > John
> >
Re: [VOTE] subsystem-bundle 1.0.0
Posted by John W Ross <jw...@us.ibm.com>.
Yep, they're empty. Nice catch. I wonder if there's a way to put some sort
of sanity check into the verify script for this.
Anyway, I'll have to figure out how to fix this. Presumably this means
dropping the current staging repository, deleting the svn tag, and starting
over. Sorry!
John
>
> Re: [VOTE] subsystem-bundle 1.0.0
>
> On 18 Apr 2013, at 10:55, John W Ross wrote:
>
> > This is a vote for the release of subsystem-bundle 1.0.0, an uber
bundle
> > containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
> >
> > Staging Area:
> > https://repository.apache.org/content/repositories/orgapachearies-117/
> >
> > Tags:
> >
http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
> >
> > This vote will remain open for at least 72 hours.
>
> I can't see any sources in either org.apache.aries.subsystem-1.0.0-
> sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
>
> It's important that the release contains sources so people can build
> it themselves: http://www.apache.org/dev/release.html#what-must-
> every-release-contain
>
> Note that it is possible to aggregate the source for "uber-bundles"
> by using the maven-dependency-plugin to unpack the sources of all
> bundled dependencies.
>
> > John
>
Re: [VOTE] subsystem-bundle 1.0.0
Posted by Stuart McCulloch <mc...@gmail.com>.
On 25 Apr 2013, at 16:21, David Jencks wrote:
> I object to this reasoning. The sources for this binary artifact are binary files, so the sources and source-release are appropriately empty. Supplying source files for source-release in particular will definitely not help anyone build the artifact. Aggregating source files into the -sources jar to make debugging easier is OK but IMO not essential.
It just seems odd to be asked to vote on a binary release without knowing what source went into it. I guess I could go and manually track down the original source based on the dependencies in the pom.xml, but it makes it easier to review when the source is sitting there alongside the binaries.
Wrt. building, you could say that the source-release.zip is OK because the pom.xml will fetch the constituent parts and rebuild the uber-bundle - but I'd still appreciate the aggregate source jar for review purposes.
> What do the other aggregate jars have?
>
> thanks
> david jencks
>
> On Apr 25, 2013, at 4:20 AM, Stuart McCulloch <mc...@gmail.com> wrote:
>
>> On 18 Apr 2013, at 10:55, John W Ross wrote:
>>
>>> This is a vote for the release of subsystem-bundle 1.0.0, an uber bundle
>>> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>>>
>>> Staging Area:
>>> https://repository.apache.org/content/repositories/orgapachearies-117/
>>>
>>> Tags:
>>> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>>>
>>> This vote will remain open for at least 72 hours.
>>
>> I can't see any sources in either org.apache.aries.subsystem-1.0.0-sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
>>
>> It's important that the release contains sources so people can build it themselves: http://www.apache.org/dev/release.html#what-must-every-release-contain
>>
>> Note that it is possible to aggregate the source for "uber-bundles" by using the maven-dependency-plugin to unpack the sources of all bundled dependencies.
>>
>>> John
>>
>
Re: [VOTE] subsystem-bundle 1.0.0
Posted by David Jencks <da...@yahoo.com>.
I object to this reasoning. The sources for this binary artifact are binary files, so the sources and source-release are appropriately empty. Supplying source files for source-release in particular will definitely not help anyone build the artifact. Aggregating source files into the -sources jar to make debugging easier is OK but IMO not essential.
What do the other aggregate jars have?
thanks
david jencks
On Apr 25, 2013, at 4:20 AM, Stuart McCulloch <mc...@gmail.com> wrote:
> On 18 Apr 2013, at 10:55, John W Ross wrote:
>
>> This is a vote for the release of subsystem-bundle 1.0.0, an uber bundle
>> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>>
>> Staging Area:
>> https://repository.apache.org/content/repositories/orgapachearies-117/
>>
>> Tags:
>> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>>
>> This vote will remain open for at least 72 hours.
>
> I can't see any sources in either org.apache.aries.subsystem-1.0.0-sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
>
> It's important that the release contains sources so people can build it themselves: http://www.apache.org/dev/release.html#what-must-every-release-contain
>
> Note that it is possible to aggregate the source for "uber-bundles" by using the maven-dependency-plugin to unpack the sources of all bundled dependencies.
>
>> John
>
Re: [CANCELLED] [VOTE] subsystem-bundle 1.0.0
Posted by John W Ross <jw...@us.ibm.com>.
Cancelling this vote due to the missing source.
John
>
> Re: [VOTE] subsystem-bundle 1.0.0
>
> On 18 Apr 2013, at 10:55, John W Ross wrote:
>
> > This is a vote for the release of subsystem-bundle 1.0.0, an uber
bundle
> > containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
> >
> > Staging Area:
> > https://repository.apache.org/content/repositories/orgapachearies-117/
> >
> > Tags:
> >
http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
> >
> > This vote will remain open for at least 72 hours.
>
> I can't see any sources in either org.apache.aries.subsystem-1.0.0-
> sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
>
> It's important that the release contains sources so people can build
> it themselves: http://www.apache.org/dev/release.html#what-must-
> every-release-contain
>
> Note that it is possible to aggregate the source for "uber-bundles"
> by using the maven-dependency-plugin to unpack the sources of all
> bundled dependencies.
>
> > John
>
Re: [VOTE] subsystem-bundle 1.0.0
Posted by Stuart McCulloch <mc...@gmail.com>.
On 18 Apr 2013, at 10:55, John W Ross wrote:
> This is a vote for the release of subsystem-bundle 1.0.0, an uber bundle
> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>
> Staging Area:
> https://repository.apache.org/content/repositories/orgapachearies-117/
>
> Tags:
> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>
> This vote will remain open for at least 72 hours.
I can't see any sources in either org.apache.aries.subsystem-1.0.0-sources.jar or org.apache.aries.subsystem-1.0.0-source-release.zip
It's important that the release contains sources so people can build it themselves: http://www.apache.org/dev/release.html#what-must-every-release-contain
Note that it is possible to aggregate the source for "uber-bundles" by using the maven-dependency-plugin to unpack the sources of all bundled dependencies.
> John
Re: [VOTE] subsystem-bundle 1.0.0
Posted by John W Ross <jw...@us.ibm.com>.
I created subsystem-bundle early in the process because I saw other
components doing the same thing (e.g. blueprint and applications) and
assumed it was either mandatory or considered a best practice. I
subsequently realized, however, that these other components probably only
did it because they consist of much more than two bundles. So, now I kind
of regret creating something else to maintain :) But the cat is out of the
bag and appears to be in demand, so I guess we're stuck with it.
Perhaps there would be more value if it also included optional components
like subsystem-obr?
John
>
> Re: [VOTE] subsystem-bundle 1.0.0
>
> Thanks John. Was actually just playing with this component. I guess this
> makes it easier to get started with subsystems, but I think in real
> deployments people would probably be better off using the embedded
> components by themselves. Would you agree?
>
> In any case, here's my +1 to releasing this component.
>
>
> On 18 April 2013 10:55, John W Ross <jw...@us.ibm.com> wrote:
>
> >
> > This is a vote for the release of subsystem-bundle 1.0.0, an uber
bundle
> > containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
> >
> > Staging Area:
> > https://repository.apache.org/content/repositories/orgapachearies-117/
> >
> > Tags:
> >
http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
> >
> > This vote will remain open for at least 72 hours.
> >
> > John
Re: [VOTE] subsystem-bundle 1.0.0
Posted by David Bosschaert <da...@gmail.com>.
Thanks John. Was actually just playing with this component. I guess this
makes it easier to get started with subsystems, but I think in real
deployments people would probably be better off using the embedded
components by themselves. Would you agree?
In any case, here's my +1 to releasing this component.
On 18 April 2013 10:55, John W Ross <jw...@us.ibm.com> wrote:
>
> This is a vote for the release of subsystem-bundle 1.0.0, an uber bundle
> containing subsystem-api 1.0.0 and subsystem-core 1.0.0.
>
> Staging Area:
> https://repository.apache.org/content/repositories/orgapachearies-117/
>
> Tags:
> http://svn.apache.org/viewvc/aries/tags/org.apache.aries.subsystem-1.0.0/
>
> This vote will remain open for at least 72 hours.
>
> John