[old comonents/jelly] ant builds and releases.

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

[old comonents/jelly] ant builds and releases.

Rob Tompkins
Hello all,

Does anyone remember how to, from an old ant build, get a project released. I think that I can piece it together by simply do a bunch of manual stuff to md5, sha1, and gpg sign things and publish artifacts and then manually update the site, but that feels fairly heavy. Does anyone recall an easier way to do this? Is there any documentation on how this was performed before migrating to maven 2+?

The build environment isn’t too difficult from my end as I have created a dockerized build environment:

https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env <https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env>

for folks curiosity.

Cheers,
-Rob
Reply | Threaded
Open this post in threaded view
|

Re: [old comonents/jelly] ant builds and releases.

sebb-2-2
On 23 August 2017 at 05:13, Rob Tompkins <[hidden email]> wrote:
> Hello all,
>
> Does anyone remember how to, from an old ant build, get a project released. I think that I can piece it together by simply do a bunch of manual stuff to md5, sha1, and gpg sign things and publish artifacts and then manually update the site, but that feels fairly heavy. Does anyone recall an easier way to do this? Is there any documentation on how this was performed before migrating to maven 2+?

I'm fairly sure it was all manual.

Nexus did not exist then, nor did dist.apache.org.

As I recall, Ant was used to create the jars.
I think sigs and hashes must have been created manually.

The RC was then uploaded to the users minotaur account somewhere under
public_html.
Assuming success, the ASF release artifacts had to be copied to
/www/www.apache.org/dist/commons/xxx on minotaur.

I think Maven artifacts were published in a similar way, i.e. upload
to a folder on minotaur and wait for changes to be picked up.

Most of the above is easy enough to do with the new systems apart from
Maven/Nexus.

The dev list archives might have some additional useful info.

> The build environment isn’t too difficult from my end as I have created a dockerized build environment:
>
> https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env <https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env>
>
> for folks curiosity.
>
> Cheers,
> -Rob

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [old comonents/jelly] ant builds and releases.

Oliver Heger-3


Am 23.08.2017 um 12:15 schrieb sebb:

> On 23 August 2017 at 05:13, Rob Tompkins <[hidden email]> wrote:
>> Hello all,
>>
>> Does anyone remember how to, from an old ant build, get a project released. I think that I can piece it together by simply do a bunch of manual stuff to md5, sha1, and gpg sign things and publish artifacts and then manually update the site, but that feels fairly heavy. Does anyone recall an easier way to do this? Is there any documentation on how this was performed before migrating to maven 2+?
>
> I'm fairly sure it was all manual.
>
> Nexus did not exist then, nor did dist.apache.org.
>
> As I recall, Ant was used to create the jars.
> I think sigs and hashes must have been created manually.
>
> The RC was then uploaded to the users minotaur account somewhere under
> public_html.
> Assuming success, the ASF release artifacts had to be copied to
> /www/www.apache.org/dist/commons/xxx on minotaur.
>
> I think Maven artifacts were published in a similar way, i.e. upload
> to a folder on minotaur and wait for changes to be picked up.
>
> Most of the above is easy enough to do with the new systems apart from
> Maven/Nexus.
>
> The dev list archives might have some additional useful info.

I remember that I also did some releases with Maven 1 in the old days.
Here the advantage is that at least the site can be generated.

I think the site will be a major problem for a Jelly release. The
artifacts for Jelly core can certainly be constructed somehow, but
getting the site build to work and then publishing the pages... :-(

Oliver

>
>> The build environment isn’t too difficult from my end as I have created a dockerized build environment:
>>
>> https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env <https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env>
>>
>> for folks curiosity.
>>
>> Cheers,
>> -Rob
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: [old comonents/jelly] ant builds and releases.

Benedikt Ritter-4
Do we really want to go through this pain?
Oliver Heger <[hidden email]> schrieb am Mi. 23. Aug. 2017 um
21:19:

>
>
> Am 23.08.2017 um 12:15 schrieb sebb:
> > On 23 August 2017 at 05:13, Rob Tompkins <[hidden email]> wrote:
> >> Hello all,
> >>
> >> Does anyone remember how to, from an old ant build, get a project
> released. I think that I can piece it together by simply do a bunch of
> manual stuff to md5, sha1, and gpg sign things and publish artifacts and
> then manually update the site, but that feels fairly heavy. Does anyone
> recall an easier way to do this? Is there any documentation on how this was
> performed before migrating to maven 2+?
> >
> > I'm fairly sure it was all manual.
> >
> > Nexus did not exist then, nor did dist.apache.org.
> >
> > As I recall, Ant was used to create the jars.
> > I think sigs and hashes must have been created manually.
> >
> > The RC was then uploaded to the users minotaur account somewhere under
> > public_html.
> > Assuming success, the ASF release artifacts had to be copied to
> > /www/www.apache.org/dist/commons/xxx on minotaur.
> >
> > I think Maven artifacts were published in a similar way, i.e. upload
> > to a folder on minotaur and wait for changes to be picked up.
> >
> > Most of the above is easy enough to do with the new systems apart from
> > Maven/Nexus.
> >
> > The dev list archives might have some additional useful info.
>
> I remember that I also did some releases with Maven 1 in the old days.
> Here the advantage is that at least the site can be generated.
>
> I think the site will be a major problem for a Jelly release. The
> artifacts for Jelly core can certainly be constructed somehow, but
> getting the site build to work and then publishing the pages... :-(
>
> Oliver
>
> >
> >> The build environment isn’t too difficult from my end as I have created
> a dockerized build environment:
> >>
> >>
> https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env
> <
> https://github.com/chtompki/Dockerfiles/tree/master/commons-jelly-build-env
> >
> >>
> >> for folks curiosity.
> >>
> >> Cheers,
> >> -Rob
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [hidden email]
> > For additional commands, e-mail: [hidden email]
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [hidden email]
> For additional commands, e-mail: [hidden email]
>
>