commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Rob Tompkins <chtom...@gmail.com>
Subject Re: Release Commons Jelly 1.0.1 Based on RC2
Date Tue, 29 Aug 2017 15:54:27 GMT
So I built everything using ant and manually uploaded everything to nexus using the existent
pom.xml in nexus with the version number changed.

The way I ran the build was in that docker container (essentially a VM) with a directory inside
the container mounted to my project directory. That’s the direction I give in the release
candidate email. More specifically I would do the following:

(1) Install docker for mac or docker for windows.
(2) Prepare your directory in which you wish to perform the build.
(3) In the docker client make sure that you are properly “sharing” the directory in which
you have the release candidate unpacked or checked out.
	Windows: https://rominirani.com/docker-on-windows-mounting-host-directories-d96f3f056a2c
<https://rominirani.com/docker-on-windows-mounting-host-directories-d96f3f056a2c>
	Mac: Click on the docker fish in the toolbar>Click on preferences>Click on Sharing.
Ensure a parent-directory is in the list of shared directories.
(4) Run the following docker command:
	Windows: “docker run -it -v c:/path/to/release/candidate/unpacked:/root/commons-jelly-1.X
chtompki/commons-jelly-build-env bash”
	Mac/Linux: “docker run -it -v /path/to/release/candidate/unpacked:/root/commons-jelly-1.X
chtompki/commons-jelly-build-env bash”
     You will now be on the command line of a Ubuntu 12.04 container (or VM) as the root user
at the root directory. The container has Java 1.5 installed and in the path 
     as well as Ant 1.6.0. So you should be able to run “java -version” and “ant -version”
and get the expected outputs.
(5) You’ll want to cd to the shared directory, namely “/root/commons-jelly-1.X”. From
here you can run the ant build as you wish and it’ll manipulate everything on your 
     local machine’s filesystem because of the shared directory into the container. 

Further if you wish to explore the container, you can see everything that I’ve installed
in it by exploring https://github.com/chtompki/Dockerfiles/blob/master/commons-jelly-build-env
<https://github.com/chtompki/Dockerfiles/blob/master/commons-jelly-build-env>. More
specifically, I’ve installed “curl,” “subversion,” “java 1.5,” “ant 1.6.0,”
and the following libraries needed for compilation: https://github.com/chtompki/Dockerfiles/blob/master/commons-jelly-build-env/install.sh#L31-L45
<https://github.com/chtompki/Dockerfiles/blob/master/commons-jelly-build-env/install.sh#L31-L45>

Regarding the maven build in the project, I’m a little skeptical over the ability for that
to run, particularly because it was run under maven 1, and the previous release 1.0 was done
with Java 1.5, and Ant 1.6. Hence my above process.

Pardon if that was a clear as mud, but that’s what I had to do to get an environment in
which we could actually do the build. 

Let me know if there are any question, as I’m quite happy to answer them.

Cheers,
-Rob



> On Aug 29, 2017, at 11:24 AM, Gary Gregory <garydgregory@gmail.com> wrote:
> 
> Hi Rob,
> 
> Thank you for preparing the RC.
> 
> I think we are going to need a little guidance as to how best test an RC
> based on such an old tool set.
> 
> This is a Maven 1 project (I see maven.xml)? But I also see a pom.xml so
> it's confusing.
> 
> No tests run when I use Maven 2 or 3. I can even get a Maven 1 build to
> download deps.
> 
> Can you please provide some guidance?
> 
> I do not think we need another RC with a BUILDING.md but if you could
> provide some instructions here, it would help a lot.
> 
> Gary
> 
> On Tue, Aug 29, 2017 at 8:18 AM, Rob Tompkins <chtompki@apache.org> wrote:
> 
>> Hello,
>> 
>> Commons Jelly 1.0.1 R2 is available for review here:
>>  https://dist.apache.org/repos/dist/dev/commons/jelly (svn revision
>> 21342)
>> 
>> Note, if anyone needs to get an environment for building and testing the
>> release candidate, I have created a docker container such that if you are
>> currently in the project directory you can run "docker run -it -v
>> $(pwd):/root/commons-jelly-1.X chtompki/commons-jelly-build-env bash”
>> then “cd /root/commons-jelly-1.X” to get to a runnable place for the
>> project. The container comes with JDK 1.5.0_22-b03 and Ant 1.6.0 on the
>> path. If there are any questions about how to use this let me know.
>> 
>> The tag is here:
>>  https://svn.apache.org/repos/asf/commons/proper/jelly/tags/
>> commons-jelly-1.0.1-RC2
>> 
>> Commit the tag points at:
>>  1806595
>> 
>> Maven Artifacts:
>>  https://repository.apache.org/content/repositories/orgapachecommons-1260
>> 
>> These are the Maven artifacts and their hashes:
>> 
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-javadoc.jar
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-javadoc.jar>
>> (SHA1: 3f4cfaccff8c8448f216c60c428dbd2eff7b2313)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-sources.jar.asc
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-sources.jar.asc>
>> (SHA1: 2cb35149c8fa3b26af9684abeeb0d7e7655e18f9)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1.pom.asc
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1.pom.asc>
>> (SHA1: 572e91a206c52ac5c51834e0186a53c9de8246b3)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1.pom
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1.pom>
>> (SHA1: 65333d0abdce02b3ae3a54c513c19b7aa04749ba)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1.jar.asc
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1.jar.asc>
>> (SHA1: f0154dc77befe4f89141a3806e43967869a29ef5)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-javadoc.jar.asc
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-javadoc.jar.asc>
>> (SHA1: ec4465d236ba78415eb6a7aea44b197d5f643934)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-sources.jar
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-sources.jar>
>> (SHA1: 939a76c00db4ea2463fe57e708299a5a989087e2)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1.jar
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1.jar>
>> (SHA1: da868784b796b2c20e5e645ed2739f38c5b74454)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-tests.jar.asc
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-tests.jar.asc>
>> (SHA1: f0117a1f2b32164e1edcd54188ffe232e0304d7f)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-
>> test-sources.jar.asc
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-test-sources.jar.asc>
>> (SHA1: ae1175942a746bf3e40176a3089edb2f2fd89e43)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-test-sources.jar
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-test-sources.jar>
>> (SHA1: b6459e04b66bce00d7b230eef3fa5fefc160ccc1)
>> /commons-jelly/commons-jelly/1.0.1/commons-jelly-1.0.1-tests.jar
>> <https://repository.apache.org/content/repositories/
>> orgapachecommons-1260/commons-jelly/commons-jelly/1.0.1/
>> commons-jelly-1.0.1-tests.jar>
>> (SHA1: e7f7c80dbb05472fcd211a5c726b554ecab02770)
>> 
>> I have tested this with JDK 1.5.0_22-b03 using Ant 1.6.0.
>> 
>> Details of changes since 1.0 are in the release notes:
>>    https://dist.apache.org/repos/dist/dev/commons/jelly/RELEASE-NOTES.txt
>> 
>> Site:
>>      I have no site as this was generated with ant. My plan was to simply
>> make minimal
>>      changes to the existant site for the purpose of documenting the
>> patch.
>> 
>> KEYS:
>>  https://www.apache.org/dist/commons/KEYS
>> 
>> Please review the release candidate and vote.
>> This vote will close no sooner that 72 hours from now,
>> i.e. sometime after 14:20 (UTC) 1-September 2017
>> 
>>  [ ] +1 Release these artifacts
>>  [ ] +0 OK, but...
>>  [ ] -0 OK, but really should fix...
>>  [ ] -1 I oppose this release because...
>> 
>> Thanks!
>> Rob
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@commons.apache.org
>> For additional commands, e-mail: dev-help@commons.apache.org
>> 
>> 


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message