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/25 15:55:28 UTC
Generating source for uber bundles
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>.
+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