Re: Apache OpenEJB 3.2.0 release

[David Blevins <da...@gmail.com>]

On Jun 30, 2011, at 8:17 AM, Romain Manni-Bucau wrote:

> done
> 
> buildbot seems happy
> http://ci.apache.org/builders/openejb-branch32/builds/23/steps/compile-test/logs/stdio
> 
> say me if you have any trouble with the modification
> 
> Note: i put the api version in the parent pom -> ${javaee-api.version}, it
> find it simpler. I just kept it hard coded in each pom for examples (of
> course ;))

Hopefully someday soon we can do servlets embedded too, so I can see that name being outgrown pretty quickly.


-David


> 
> PS: it is still in snapshot
> 
> - Romain
> 
> 2011/6/30 Romain Manni-Bucau <rm...@gmail.com>
> 
>> i take this action,
>> 
>> javaee-api-noweb could maybe be renamed javaee-api-embedded?
>> 
>> - Romain
>> 
>> 
>> 2011/6/30 David Blevins <da...@gmail.com>
>> 
>>> 
>>> On Jun 29, 2011, at 6:52 AM, Jean-Louis MONTEIRO wrote:
>>> 
>>>> OK did some small fixes and merge Transaction stuff (root cause from
>>> David's
>>>> changes).
>>>> Also had a look to JIRA and close some of them.
>>>> 
>>>> That's definitely an area where we have to focus on because there are a
>>> lot
>>>> of non relevant JIRA and some of them are really old :)
>>>> 
>>>> Everything seems to compile on our CI and I deploy snapshots.
>>>> 
>>>> There are still 2 pending issues where I'd like to get some feedback.
>>>> 
>>>> 1. javaee-api has a version 6.0-SNAPSHOT
>>>> I do not like to release with a SNAPSHOT.
>>>> As it's only a subset of JavaEE 6 api, I propose to change and release
>>>> javaee-api as 6.0-preview (or alpha, beta, ..).
>>> 
>>> I see what you mean.  We essentially have two jars that together make an
>>> actual 'javaee-api' jar.   The two added together make "one" whole
>>> javaee-api jar.
>>> 
>>> We're going to have this same problem in trunk if we want to maintain
>>> Tomcat 6 and 5.5 compatibility.  Not sure how we want to deal with that.
>>> 
>>> We could actually have two jars, one with everything (for use in compiling
>>> and outside tomcat) and one with everything minus the servlet stuff for use
>>> in Tomcat.  Since the current solution is a two jar approach, that might be
>>> an alternate two jar approach that could be a little more useful.
>>> Basically:
>>> 
>>>  - javaee-api.jar (full, nothing excluded)
>>>  - javaee-api-noweb.jar (the partial jar we currently have as
>>> javaee-api.jar)
>>> 
>>> Not sure if 'javaee-api-noweb' is the best name, but you get the idea.
>>> 
>>> 
>>> -David
>>> 
>>> 
>>> 
>>>> 
>>>> 2. Following transaction changes, we now depend on geronimo transaction
>>>> component 2.2.2-SNAPSHOT
>>>> Can someone release connector and transaction components or do I have to
>>>> revert my changes?
>>>> BTW, this is something users ask ofter so if you could fix it, that's be
>>>> great.
>>>> 
>>>> Then, I check commits since latest release (3.1.4 in January) and do not
>>>> noticed big change without JIRAs.
>>>> 
>>>> Then I can enter in the whole release process.
>>>> 
>>>> Thanks,
>>>> Jean-Louis
>>>> 
>>>> --
>>>> View this message in context:
>>> http://openejb.979440.n4.nabble.com/Apache-OpenEJB-3-2-0-release-tp3632295p3632893.html
>>>> Sent from the OpenEJB Dev mailing list archive at Nabble.com.
>>> 
>>> 
>> 

Re: Apache OpenEJB 3.2.0 release

[David Blevins <da...@gmail.com>]

On Jul 28, 2011, at 5:34 AM, Jean-Louis MONTEIRO wrote:

> Hi,
> 
> As soon as we are all ok (or not ;-) ) on that proposal [1], can we release
> the deps module?
> Then, I can change the snapshot to the final release in 3.2.x branch.

We've always just released the deps with the OpenEJB release itself, so we can just add the deps module back to the build and maven will take care of it.

That said, we got the split part backwards.  We need plain "javaee-api" everywhere in the build.  Only TomEE is the odd case where we can't use all the API classes.  TomEE needs a jar without the servlet, jsp, el APIs.

I'll be back from OSCON tomorrow and can help as needed.


-David

Re: Apache OpenEJB 3.2.0 release

[Jean-Louis MONTEIRO <je...@gmail.com>]

Hi,

As soon as we are all ok (or not ;-) ) on that proposal [1], can we release
the deps module?
Then, I can change the snapshot to the final release in 3.2.x branch.

Jean-Louis


[1]  http://openejb.979440.n4.nabble.com/Refactoring-deps-td3696086.html
http://openejb.979440.n4.nabble.com/Refactoring-deps-td3696086.html 

--
View this message in context: http://openejb.979440.n4.nabble.com/Apache-OpenEJB-3-2-0-release-tp3632295p3701201.html
Sent from the OpenEJB Dev mailing list archive at Nabble.com.