David,

Think I have most of these addressed except the lack of source jars for the shaded jars -- something to work on.

I ran offline and online and nothing ever downloaded bcprov-jdk13-132 jar, not sure what was going on.


-David


On May 29, 2009, at 1:35 PM, David Jencks wrote:

I located the source distros at https://repository.apache.org/content/repositories/openejb-034/org/apache/openejb/openejb/3.1.1/ pulled down the tar.gz and tried to build it.

After a while I found that I had to build deps. Then I discovered that deps downloaded stuff from an openejb private repo in openejb svn for unreleased xbean artifacts. IIUC the process is like this:

-By hand, not part of normal openejb build:
-- check out xbean trunk rxxxx.
-- build it
-- deploy into svn repo (I'm not sure where the artifact ID came from)

-As part of deps build, not part of root openejb build:
-- use shade plugin to copy it to an artifact with org.apache.openejb groupId

-As part of root openejb build:
-- depend on these repackaged artifacts in a few places in the build
-- include the result in the binary assemblies.

While I know geronimo has pulled stunts like this in the past I no longer think its OK. It looks to me as if openejb is including binary artifacts (the shaded xbean jars) where the
-- source code has not been voted for release by any pmc
-- source code is not included in openejb source distro.

I'd be fine with fixing this in either of 2 ways:
- don't include the shaded xbean jars in the binary distros, tell people to build them themselves - do include the source for the xbean code in the source distro, and explicitly vote on releasing it here. In this case the xbean build needs to be modified to only come up with artifacts with an openejb groupId.

Since geronimo has been equally guilty in the past I'm not going to vote -1 but I also don't feel I can vote +1 either. I'm planning to fix geronimo's similar problems soon at which point without strong arguments I'll start voting -1 to situations like this.

On a happier note after working through these private artifact issues the source distro does in fact build!!!



Other problems:
in server/openejb-cxf:
Downloading: 
http://ws.zones.apache.org/repository2//bouncycastle/bcprov-jdk13/132/bcprov-jdk13-132.jar

permissions on data/README.txt seem a little weird:
--wxr----x  1 david  david  100 May 29 16:26 README.txt

thanks
david jencks


On May 28, 2009, at 7:58 PM, David Blevins wrote:

Ok. At long last the binaries are ready! All was rat scanned[1] for missing headers; there were a few and all that needed them were fixed. The LICENSE and NOTICE files updated for the new dependencies we've added since 3.1. One of the new jars is Bouncy Castle which previously had some patented algorithms, but in the 140 version the patented algorithms were removed, so we're good there.


Binaries tested on OS X with Java 1.5 in modes:

- OpenEJB Standalone
- Tomcat 6.0.14 w/o installer
- Tomcat 6.0.14 w/ installer
- Tomcat 5.5.26 w/o installer
- Tomcat 5.5.26 w/ installer

If you'd like to help test (please please), just grab this ant file and run 'ant test:all'

http://people.apache.org/~dblevins/stage/build.xml

Ideally the script should be run on OS X, Linux, Windows XP using JDK 1.5 and JDK 1.6. More platforms and JDKs welcome, but those are the ones we've been been doing in all our releases so far. Just reply with the OS and JDK version+vendor you used. Hopefully between all of us we can get the full matrix covered.


- - - - - -

Repo:

https://repository.apache.org/content/repositories/openejb-034/

Binaries:

http://people.apache.org/~dblevins/stage/3.1.1/

Tag:

https://svn.apache.org/repos/asf/openejb/tags/openejb-3.1.1/

- - - - - -

Vote will be open for 72 hours. And as usual, anyone and everyone is welcome to vote! It's a great way to show support.


-David


[1] http://incubator.apache.org/rat


Reply via email to