TOMEE-2907 - Transaction not marked RollbackOnly when @Transactional annotated via @Stereotype

[Frankie]

Hi,

just created the above issue in JIRA.
How is this handled if it happens to be a bug in one of the libraries (CDI?
JPA? ...) TomEE uses?
Comments are welcome - perhaps I misunderstood something concerning
transactions ...?

Thanks
Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: [ANNOUNCE] Apache TomEE 8.0.0-M2 Released

[Frankie]

Just found it: TomEE Users mailing list ...



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: [ANNOUNCE] Apache TomEE 8.0.0-M2 Released

[Frankie]

Congratulations! Well done!

BTW: Where are "announcing"-mails sent to? Here I can find only the replies
on it ... ?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: JakartaEE TCK

[Frankie]

Very nice ...
It seems there is coming up another topic for documentation ... ;-)



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Another 8.0.0 milestone release

[Frankie]

I like the idea.
+1

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Jakarta EE TCKs and compatibility logo

[Frankie]

+1

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How can I help?

[Frankie]

I can't assign the ticket to you - can't find your User in the list.
I See you in https://issues.apache.org/jira/browse/TOMEE-2455 and from there
I can see your profile.
Does anybody know what could be the problem?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2452 - Translate examples/access-timeout to Spanish

[Frankie]

Done

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Where do we remember outstanding dependency updates for release?

[Frankie]

Absolutely.
What I meant was a ticket to "store" the information about the proceeding
concerning SNAPSHOT dependencies when releasing though.
Obviously not clearly expressed by me ...




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Where do we remember outstanding dependency updates for release?

[Frankie]

So the pom.xml is the central place of information I was looking for ... ;-)
And the existence of SNAPSHOT entries in pom.xml are our todo-markers for
release.
I'm fine with that.
JIRA tickets in addition would be great but on the other hand redundant
work. 
Now I wonder what would be a good way to document this. Is there
documentation for the release process?
As a first step: create a JIRA ticket with this information?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Where do we remember outstanding dependency updates for release?

[Frankie]

Hi,

today I noticed that the Version of bval-jsr has to be updated to 2.0.1
because of missing properties for new Validation Constraints like NotEmpty.
But bval-jsr 2.0.1 is not yet released.
So before creating a redundant JIRA ticket I did some investigation and
found
http://tomee-openejb.979440.n4.nabble.com/Finish-the-bval-setup-td4685085.html.
In the there-mentioned PR the dependency is set to 2.0.1-SNAPSHOT.

I wondered if there is a place where I could have easily found such external
dependencies we are waiting for so that I can update it.
All I found was https://issues.apache.org/jira/browse/TOMEE-2115 ("TomEE-8
work"), but there are only two other tickets linked to ...

Any hints?

Thank you
Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2339 Describe Workflow for Contribution

[Frankie]

Hi César,

next step? I have to wait now until merge is done by a committer, right?

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2339 Describe Workflow for Contribution

[Frankie]

Hi Cesar,

thanks for your feedback.

A visual diagram would be great but I don't have a good idea at the moment
how to realize it - and keep it up to date when text changes.
Besides, there is more information to be added, for example from this post
from David:
http://tomee-openejb.979440.n4.nabble.com/Anyone-can-help-review-PRs-td4685806.html.
So if you or anybody else wants to add a diagram I would recommend to wait
until the text is in a more final state... ;-)

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Website: Questions and Errors

[Frankie]

Hi Richard,

thank you. 

The main point is that we need an easier and more handy way to manage the
information for the community section. I suggested the wiki because it
already exists and obviously belongs to the Apache infrastructure so that I
hope we could quickly start with this. But I'm open to any alternative
proposal.

So could you please explain the drawbacks you see when using confluence? I
can't imagine what "has never been a favorite of mine" means ... ;-)

As the wiki would help us to collect information that is now spread over
threads in the mailing list or even lost we should consider using it even if
it's not perfect.

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Website: Questions and Errors

[Frankie]

Obviously the information is distributed over many heads and we have to bring
it together to one place.

A mailing list is great to discuss topics but at the end we need one place
to merge the results. At the end it must be possible to find the desired
information without reading hundreds of posts ...

The TomEE website (tomee-site-builder) can be used to concentrate this
information. However to add information there you have to go through the
whole contribution workflow. So I worry that lots of little information
pieces won't find their way into it.

It would be helpful to have a tool where we can add/update and share
information more quickly - like a wiki. I don't know about the possibilities
we have on the apache infrastructure but I found an already existing wiki
for TomEE: https://cwiki.apache.org/confluence/display/TOMEE/Index

I suggest to use this wiki for most of the information that is now in the
community section of the website. Most of this content has to be reviewed
and touched anyway since it is outdated. And it's far easier for everybody
to add one's two cents.
The community section of the website could then be concentrated on some
general information with links to the wiki.

What do you think about this?

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Frankie]

Hi Cesar,

> This is a valuable piece of information.
That's what I thohght, too when I read the information on IRC ... 
Thanks that you want to preserve it on the website.

The JIRA task is now assigned to you. 

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Website: Questions and Errors

[Frankie]

Hi,

while working on "tomee-site-generator" I saw that there were lots of error
messages (before I made changes ...), but running the site was successful.
So these error message (see above) can be ignored?

Questions:
- There is a File doc.adoc but the content of the generated docs.html is
looks completely different. I saw that obviously data is fetched from a git
repo. Does this overwrite the content of docs.html? So the file docs.adoc
could be removed?
- It seems, the files of the old website are still present in folder "dev"
as a result of Davids merge activity. The information on these should be
included/moved to new pages and then the old ones could be removed, right?
- Apart from
http://tomee-openejb.979440.n4.nabble.com/Merging-Old-and-New-Websites-td4685488.html
is there a descritpion how this site builder is working? 

Error messages:
- Class org.apache.tomee.website.Downloads has errors but is not used?
  => could be removed?
- Lots of error messages like:
  asciidoctor: ERROR: : line 28: only book doctypes can contain level
0 sections
- While reading contributor information?:
  javax.ws.rs.client.ResponseProcessingException: Problem with reading the
data, class org.apache.tomee.website.Contributors$Gravatar, ContentType:
application/json.
  ...
  No gravatar for mn...@apache.org

Frankie




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Website: Contribution workflow added - PR#12

[Frankie]

Hi,

please review PR#12 for tomee-site-generator.

This adds a first version of the contribution workflow documentation.

There is still a lot of work on the site since lot of information is not up
to date or even not used. 
While working on the workflow more and more questions appeared ... I will
open an extra thread for these.

Is it ok to move in multiple steps/PRs for one task? I decided to create a
PR to get a feeling if I'm moving in the right direction ... ;-)

Thanks.

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Documentation Contribution Opportunities

[Frankie]

Hi Carlos,

task is now assigned to you.

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How to find out that someone else is already working on a task

[Frankie]

Follow up to
http://tomee-openejb.979440.n4.nabble.com/TOMEE-2339-Describe-Workflow-for-Contribution-td4686169.html




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2339 Describe Workflow for Contribution

[Frankie]

That's great, Bruno!

If I understand correctly these are mainly the steps to be done by the
committer when doing the review.
So I would like to use this for the details page behind "review changes".
As this ocument is mainly addressing new contributors I would prefer to have
all work items that has to be done by a committer in one point.

The last two points are very helpful tips for the work before the PR is
made, so I would put them in the details page behind "work on code"

Doing this we have a brief and clearly description of the workflow with
links to detailed description for any single step.




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2339 Describe Workflow for Contribution

[Frankie]

Thank you, Bruno. I just repost your comment here:

Hi Frankie,

I suggest a middle step between 3. and 4. related to PR review:

Review PR

* Checkout master: `git checkout master`

* Update master: `git fetch upstream` and `git rebase upstream/master`

* Create a local review branch: `git checkout -b review-prXXX`

* Switch to review branch: `checkout review-prXXX`

* Checkout PR: `git fetch upstream pull/XXX/head:prXXX`

* Merge PR into review branch: `git merge prXXX`

* Most times you don't need to build the whole project. It depends on 
what code is being added/changed. If it's and example, go to the 
sub-project and do a `mvn clean install` there.

* If it's an example, check the guidelines for compliance: 
https://github.com/apache/tomee/blob/master/examples/README.adoc


I think we could place Frankie's guidelines as a file in the project, as 
a PR. What do you guys think?

Cheers

Bruno Baptista
https://twitter.com/brunobat_





--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2339 Describe Workflow for Contribution

[Frankie]

Yes, I already created the page, just wanted to know if the direction I move
is ok ... ;-)
PR will follow ...



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Please Assign TOMEE-2339 Describe Workflow for Contribution...

[Frankie]

Cool, thank you very much!

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Frankie]

Overlooked that, sorry.
I intended to concentrate on the documentation for contribution workflow,
that's why I asked.
So no problem if Jean-Louis picks it up.
And: what about a JIRA ticket for that ... ? ;-)





--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How to find out that someone else is already working on a task

[Frankie]

Follow up discussion on workflow to
http://tomee-openejb.979440.n4.nabble.com/TOMEE-2339-Describe-Workflow-for-Contribution-td4686169.html



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

TOMEE-2339 Describe Workflow for Contribution

[Frankie]

I started to work on the documentation of the workflow as discussed in
http://tomee-openejb.979440.n4.nabble.com/How-to-find-out-that-someone-else-is-already-working-on-a-task-td4685855.html.

As a result of the discussion in
http://tomee-openejb.979440.n4.nabble.com/Stabilize-TomEE-Build-td4685909.html
I think it would be nice to detect (and fix) potential build problems before
a PR is created so I decided to include this under "Submit change" and
dropped the step "Monitor build" ...

So this would be the workflow as a compact overview - for most of the single
steps I plan to link to additional information in detail - comments are
welcome:

1. Check JIRA
  * create ticket, if not already existing
  * if ticket already assigned to someone else => stop & talk
  * assign ticket to contributor, if not already assigned
(ask on mailing list, if no permission to assign)

2. Process Task
  * fork repository
  * create branch in own repository (name = JIRA ticket number …​)
  * discuss on mailing list
  * work on code
  * document work in JIRA ticket

3. Submit Change
  * ensure code compiles
  * ensure tests passes
  * create PR (pull request)
  * ask for review on mailing list

4. Merge Change (done by a committer)
  * review changes
  * merge code
  * change JIRA ticket status / close ticket

5. Clean up
  * wait until PR is merged (ticket status change)
  * remove branch in own repository




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Please Assign TOMEE-2339 Describe Workflow for Contribution...

[Frankie]

... to me

Thanks



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How to find out that someone else is already working on a task

[Frankie]

Hi Jon,

could you send me the mail address of the JIRA mailing list per PM? It's
replaced here by "hidden email" ...

(Most of )The content from the link I posted will be at
http://tomee.apache.org/community/contributing/contribution-tips.html - as
soon as the current master branch is published.

I think we could split this into "contribution tips" with (only) general
hints on contributing and something like "workflow" with the description of
the steps when taking up a task.

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Stabilize TomEE Build

[Frankie]

What can I do to already detect such problems when I work on the code?
What is the difference on the build system? (additional checkstyle rules
...?

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How to find out that someone else is already working on a task

[Frankie]

Extended considering
http://tomee-openejb.979440.n4.nabble.com/Stabilize-TomEE-Build-td4685909.html 

[1] Check JIRA
- create ticket, if not exists
- (request to) assign ticket
=> the assignment of the ticket could raise an automated post in the mailing
list

[2] Process Task
- fork repo
- create branch in fork
- discuss on mailing list / in JIRA ticket (prefered?)
- work on code

[3] Submit Change
- create PR
- ask for review on mailing list

[4] Merge Change (by a committer)
- review changes
- merge code
- change JIRA ticket status / close ticket => would help to inform
contributor that merge is done ...

[5] Monitor build - on build errors caused by my changes:
- reopen JIRA ticket
- comment ticket
- fix build issues
- goto [3]

[6] Clean up
- wait until PR is merged (ticket status change)
- remove branch in fork 

Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How to find out that someone else is already working on a task

[Frankie]

I found hints at http://tomee.apache.org/dev/contribution-tips.html but the
important point "how to assign" a task to a person is not completely clear
there.

So the workflow for a task one is interested in could be like this?:

[1] Check JIRA
- create ticket, if not exists
- (request to) assign ticket
=> the assignment of the ticket could raise an automated post in the mailing
list

[2] Process Task
- fork repo
- create branch in fork
- discuss on mailing list / in JIRA ticket (prefered?)
- work on code

[3] Submit Change
- create PR
- ask for review on mailing list

[4] Merge Change (by a committer)
- review changes
- merge code
- change JIRA ticket status / close ticket => would help to inform
contributor that merge is done ...

[5] Clean up
- wait until PR is merged (ticket status change)
- remove branch in fork

I think it would be important not only to have this defined (and documented)
but that it matches the way we act in working on tasks so one can rely on
it.

Frankie




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: How to find out that someone else is already working on a task

[Frankie]

Hi Jon,

that's great. So others could see that I am working on a task.

However for the above mentioned samples this would not help me to see if a
task is already in progress by someone else - when there is "no ticket" or
"ticket not assigned".

That's why I asked if there are any rules or a defined workflow - I need to
understand the way we actually cooperate in this project. 

Perhaps I just think too complicated - obviously it worked somehow in the
past. I just want to know how ...

Frankie




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

How to find out that someone else is already working on a task

[Frankie]

Now it has happened the second time to me that I prepared to work on a task
and only by chance noticed in time that someone else has already picked it
up.
It would be frustrating spending time for nothing - or knowing that someone
else did (when I have been faster)

David said "Most important thing I think is to say what code you'll be
working on before you invest the time, just to make sure someone else is not
also cleaning the same code (duplication)."
(http://tomee-openejb.979440.n4.nabble.com/JIRA-ticket-and-PR-s-td4685790.html)
- but I dont't know how to do this.

The two examples:

[1]
http://tomee-openejb.979440.n4.nabble.com/Merging-Old-and-New-Websites-td4685488.html
David worked on this when I wanted to add some notes to the website. There
was no JIRA ticket. So obviously it's not enough to check JIRA before
creating a new ticket ...

[2]
https://issues.apache.org/jira/projects/TOMEE/issues/TOMEE-2316?filter=allopenissues
When I prepared to have a look at this I saw a PR message in the mailing
list.
There was a JIRA ticket but noone seemed to be working on it since it was
unassigned ...

So I wonder how this is organized in this project. How can I know that a
task is "free" (noone working on it) and how can I tell the community that
I'm gonna work on a task? 
When I read throught the mailing list I often found that for every task
there should be a JIRA ticket. But it doesn't seem to happen in real life
reliably. And even when I create a JIRA ticket I have no permission to
assign it to myself to let others know that I will do the task.

Any hints to help me to feel more comfortable? Is there an "official
workflow"?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TomEE for the Holidays

[Frankie]

Hi David,

I really would like to understand how we work in this project. 
That's why I asked you a question concerning ticket here:
http://tomee-openejb.979440.n4.nabble.com/Merging-Old-and-New-Websites-td4685488.html
Did you eventually overlook it?




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Merging Old and New Websites

[Frankie]

Sounds great!
As said in
(http://tomee-openejb.979440.n4.nabble.com/Feedback-as-newbie-td4685477.html)
I would like to share some experiences with my first steps and Jon pointed
to your work on the website. So probably it would be better to wait until
you finished merging.
BTW: Is there a JIRA ticket for the merge so that I can see when it's done?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Feedback as newbie

[Frankie]

Thanks for all the helpful input.
I hope I will find time the next days to read, learn and play with the
site-builder and then hopefully work on its content.



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Feedback as newbie

[Frankie]

I will be happy to generate a PR for the site if somebody could provide
information to answer the questions in my post ... ;-)Again the
questions:[1] Which one of the two
(http://tomee.apache.org/community/sources.html or Which one of the
following) is the right place? And what should happen with the other one? At
least a hint should be added that its outdated and a link to the new
place?[2] Can somebody confirm, that the development for 8.0.0 is done in
the master branch? And explain what the branch "tomee-8.0.0-ML1-rel" is for?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Feedback as newbie

[Frankie]

I will be happy to generate a PR for the site if somebody could provide
information to answer the questions in my post ... ;-)

Again the questions:

[1] Which one of the two (http://tomee.apache.org/community/sources.html or
http://tomee.apache.org/dev/source-code.html) is the right place? And what
should happen with the other one? At least a hint should be added that its
outdated and a link to the new place?

[2] Can somebody confirm, that the development for 8.0.0 is done in the
master branch? And explain what the branch "tomee-8.0.0-ML1-rel" is for?





--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Feedback as newbie

[Frankie]

Did my first tiny contrubution yesterday and would like to share how it felt
for me.

First of all I have to say thanks for the great support and the fast reply
to posts on the TomEE Dev mailing list. I feel very comfortable and welcomed
with that.

There were some little points of struggle that caused unsureness. I would
like to take this as a chance to help to get the docu updated/improved so
that other newcomers can benefit - or to get hints where I should have
looked ... ;-)

[1] current docu pages
How can I tell which docu page is current, e.g. from:
*  http://tomee.apache.org/community/sources.html
  
*  http://tomee.apache.org/dev/source-code.html
  

[2] git workflow: howto find the correct branch
http://tomee.apache.org/dev/git.html   
says:
* The 'develop' repository is the equivalent of the SVN trunk directory
   => branch "develop"? In github it is not active and the last commit on
this is dated march 2015 ... ?
* The 'master' repository is the equivalent of the SVN tags directory.
   => branch "master" seems to be the used for the actual developing on
Version 8.0.0?
   => Branches "tomee-7.1.x", "tomee-7.0.x" and "tomee-1.7.x" obvoiusly used
for the matching versions
   => branch "tomee-8.0.0-ML1-rel"?
I read through some PRs to figure out that I had to use the master for 8.0.0
...




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Please review PR# 217

[Frankie]

BTW: why is the automatic generated message from the PR noted "by
cesarhernandezgt"?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Please review PR# 217

[Frankie]

Could someone please review this PR?

It is my first contribution to an open source project ever, so please be
graceful (and give hints) if I missed something ... ;-)
This trivial dependency update was the perfect issue for that, so I could
focus on the tools and processes.

Thank you.



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2241: Best way to handle resolved Issue when update required?

[Frankie]

Thank you, Jon.
What is the best way to claim a ticket then? Obviously we already had the
case that more than one wanted to do that ... ;-)



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: TOMEE-2241: Best way to handle resolved Issue when update required?

[Frankie]

OK, Ticket created.

I would like to create a patch, too. But I`m new with that in open source
projects.
So I have some questions on it.
Is there a process to claim a Ticket to avoid multiple people working
redundantly on it?
Where can I find information how to use JIRA in TomEE project?




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

TOMEE-2241: Best way to handle resolved Issue when update required?

[Frankie]

The  TOMEE-2241 - Need to upgrade commons-lang3-3.5.jar to
commons-lang3-3.8.jar to allows Struts users to fix CVE-2018-11776 in their
app    is already
resolved, updating commons-lang3 dependency to 3.8.0.There is a bugfix
version 3.8.1 of commons-lang3 available (which is used as dependency by
commons-configuration2, for example).What is the best way to handle this if
I want to have it updated?Create a new Issue? "Reopen" the issue?



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Issue TOMEE-2063 not solved in TomEE 7.0.4?

[Frankie]

You are right! I mixed up the constant names and used LIBRARY_BEFORE (1000)
instead of PLATFORM_BEFORE (0), so I expected 1200 ... 



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: Issue TOMEE-2063 not solved in TomEE 7.0.4?

[Frankie]

Yes, I saw that in the git repo, but when I download TomEE 7.0.4 PluME, the
fix seems not to be included, since my built-in check using reflection says
so ...

Decompiled RequiredInterceptor.class:
*@Priority(200)* 
instead of:
*@Priority(Interceptor.Priority.PLATFORM_BEFORE + 200)*




--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Issue TOMEE-2063 not solved in TomEE 7.0.4?

[Frankie]

Hello,

it seems, the fix for the resolved Issue  TOMEE-2063
<https://issues.apache.org/jira/browse/TOMEE-2063>   ist not included in
TomEE 7.0.4? Did I misunderstand something?

Thank you

Best regards
Frankie



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: 7.0.4 release plans

[Frankie]

Of cource I understand ... and I hope, you are well again. 
I know and honor the effort in open source development. And if there is no
definite release date because of some blockers thats fine for me.
My intention was not to pressure anyone but to get information about the
dependencies or blockers for the release. I checked out the page with JIRA
issues but I can't determine which of them have to be resolved for a new
release.
Thats why I asked that questions to get a better understanding of the
release process of TomEE. Perhaps you or somebody else could help me by
answering this questions.

Thank you!





--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: 7.0.4 release plans

[Frankie]

I really would appreciate a clear and reliable statement concerning the
status and the release date.
Do you wait for the Apache 8.5.21 like suggested?
Are there any other blockers?
Who takes that decision und is authorized to rollout a release? 
Is there another place like a project status site where I can get this
information?

There are quite a lot of important improvements I urgently am waiting for
...

Thank you.



--
Sent from: http://tomee-openejb.979440.n4.nabble.com/TomEE-Dev-f982480.html

Re: 7.0.4 release plans

[Frankie]

Is there any new information when this will happen?
I checked https://issues.apache.org/jira/projects/TOMEE/versions/12339959
but didn't find any hints there. Is there a more up-to-date project status
page?

Thank you 

Romain Manni-Bucau wrote
> Yes, will be released soon normally





--
View this message in context: 
http://tomee-openejb.979440.n4.nabble.com/7-0-4-release-plans-tp4682014p4682458.html
Sent from the TomEE Dev mailing list archive at Nabble.com.