Re: [Website-Antora] New preview
> On Aug 9, 2020, at 8:49 PM, David Blevins wrote: > >> On Aug 9, 2020, at 8:10 PM, Willes Reis wrote: >> >>> I’m not sure supplying identical copies of the documentation that claim >>> to be for different versions is entirely desirable. Presumably we need two >>> copies for javax/jakarta, but I’m not sure the one in tomee-site (from CMS) >>> or the identical 7.0, 7.1, and 8.0 versions are truly essential. >>> >>> Next I may look into the examples. IIUC the java source for them is going >>> to remain as javax for the foreseeable future. I think that means that the >>> README’s should also remain javax-only. Among other things this should >>> enable easy inclusion of source-code snippets and avoid confusion when the >>> doc says jakarta and the source says javax. >>> >>> I suggested earlier that there’s no need for more than one version of the >>> examples. I haven’t changed my mind on this and although someone didn’t >>> seem to like the idea, I didn’t see any arguments why having more than one >>> version was a good idea. Since IMO the largest problem with the docs site >>> is that there’s too much outdated useless and wrong content, and it’s >>> nearly totally disorganized, I think reducing the size will make everything >>> else easier. >>> >> >> I agree with David Jencks. >> For sake of organization, I would like to suggest that we keep the >> documentations isolated by branches, where each branch is a documentation >> version (7.0.x, 7.1.x, 8.x and 9.x). Therefore, old docs will be >> kept, while newly created ones evolve, beyond being compatible with >> Antora's source repositories through branches. > > I'd agree with that as well and it's what we currently have. I get the > impression this is what David points out as a problem. > > We historically have had one base of documentation that applied to all > versions. It's only been in the last year that we've attempted to branch the > documentation as described. I'm the only one who put any effort into it, so > it didn't go far. I do think that's the right long-term approach, but I am > sympathetic to the argument with the documentation in the shape it's in we > perhaps branched too early. > > I could be on board for focusing on one branch for a while with the plan to > return to branching once we get something we like. > > As we have done one doc-base for all the versions over 19 of the last 20 > years I wouldn't be willing to make that the permanent plan. A major problem > with it is no one deletes anything because "maybe it applies to an older > version." When Romain created the JBake setup he included only a subset of > the documentation in an attempt to fix that problem. The way he did it ended > up creating new problems as much of those documents still applied, but I > understand what he was trying to solve. > I didn’t notice any differences between any of the doc versions in february except fairly different bad attempts to translate from markdown to asciidoc. IIRC some pages disappeared but I didn’t see any content updates in the versioned docs. I think it would be a really good idea for someone (hopefully someone more familiar with TomEE than me) to spend some time and organize the existing docs by hand. To me, the current “sort by tag” approach is an admission that the docs are incoherent and will stay that way. One way this might work would be to copy the “originals” from common to 7.0.x, then organize them there, and then propagate the organization to include stubs in the other versions, removing the copy from common. I suppose it might be possible to write a script to produce an include stub matching every “original” in all the copied versions, in which case we could start by moving the “originals” from common to 7.0.x. David Jencks > > > -David
Issue of the JIRA TOMEE-2897 - Translate to Portuguese: examples/singleton-startup-ordering
I created the issue on the JIRA [1] to translate to portugueses of the document examples/singleton-startup-ordering/. Can some of the JIRA admins please assign the ticket to my username:evaldoapjunior [1]https://issues.apache.org/jira/browse/TOMEE-2897 Regards, Evaldo Junior >
Re: [Website-Antora] New preview
> On Aug 9, 2020, at 8:10 PM, Willes Reis wrote: > >> I’m not sure supplying identical copies of the documentation that claim >> to be for different versions is entirely desirable. Presumably we need two >> copies for javax/jakarta, but I’m not sure the one in tomee-site (from CMS) >> or the identical 7.0, 7.1, and 8.0 versions are truly essential. >> >> Next I may look into the examples. IIUC the java source for them is going >> to remain as javax for the foreseeable future. I think that means that the >> README’s should also remain javax-only. Among other things this should >> enable easy inclusion of source-code snippets and avoid confusion when the >> doc says jakarta and the source says javax. >> >> I suggested earlier that there’s no need for more than one version of the >> examples. I haven’t changed my mind on this and although someone didn’t >> seem to like the idea, I didn’t see any arguments why having more than one >> version was a good idea. Since IMO the largest problem with the docs site >> is that there’s too much outdated useless and wrong content, and it’s >> nearly totally disorganized, I think reducing the size will make everything >> else easier. >> > > I agree with David Jencks. > For sake of organization, I would like to suggest that we keep the > documentations isolated by branches, where each branch is a documentation > version (7.0.x, 7.1.x, 8.x and 9.x). Therefore, old docs will be > kept, while newly created ones evolve, beyond being compatible with > Antora's source repositories through branches. I'd agree with that as well and it's what we currently have. I get the impression this is what David points out as a problem. We historically have had one base of documentation that applied to all versions. It's only been in the last year that we've attempted to branch the documentation as described. I'm the only one who put any effort into it, so it didn't go far. I do think that's the right long-term approach, but I am sympathetic to the argument with the documentation in the shape it's in we perhaps branched too early. I could be on board for focusing on one branch for a while with the plan to return to branching once we get something we like. As we have done one doc-base for all the versions over 19 of the last 20 years I wouldn't be willing to make that the permanent plan. A major problem with it is no one deletes anything because "maybe it applies to an older version." When Romain created the JBake setup he included only a subset of the documentation in an attempt to fix that problem. The way he did it ended up creating new problems as much of those documents still applied, but I understand what he was trying to solve. -David
Re: [Website-Antora] New preview
> I’m not sure supplying identical copies of the documentation that claim > to be for different versions is entirely desirable. Presumably we need two > copies for javax/jakarta, but I’m not sure the one in tomee-site (from CMS) > or the identical 7.0, 7.1, and 8.0 versions are truly essential. > > Next I may look into the examples. IIUC the java source for them is going > to remain as javax for the foreseeable future. I think that means that the > README’s should also remain javax-only. Among other things this should > enable easy inclusion of source-code snippets and avoid confusion when the > doc says jakarta and the source says javax. > > I suggested earlier that there’s no need for more than one version of the > examples. I haven’t changed my mind on this and although someone didn’t > seem to like the idea, I didn’t see any arguments why having more than one > version was a good idea. Since IMO the largest problem with the docs site > is that there’s too much outdated useless and wrong content, and it’s > nearly totally disorganized, I think reducing the size will make everything > else easier. > I agree with David Jencks. For sake of organization, I would like to suggest that we keep the documentations isolated by branches, where each branch is a documentation version (7.0.x, 7.1.x, 8.x and 9.x). Therefore, old docs will be kept, while newly created ones evolve, beyond being compatible with Antora's source repositories through branches. Willes.
Re: [Website-Antora] New preview
I’ve rebased my branches on current work, added 9.0 docs and implemented
javax/jakarta via an attribute, and pushed the preview.
You can see the javax/jakarta at work by looking at different versions of
https://tomee-preview.s3-us-west-2.amazonaws.com/tomee/9.0/jpa-concepts.html#_valid_resource_local_unit_usage
I think a few pages got added to explain 9.0 but I don’t think they are in the
right place in any of my branches. Could someone point me to all the new pages?
I asked about this in perhaps february with no response, but I’ll try again
since the situation is now 25% worse.
With the exception of a few pages getting dropped as time went on, there are
now 5 identical copies of every page in the docs component. The original is in
tomes-site, where I found it. In order to prevent the sort of unintended drift
that plagues the current site, the other copies are all made to be identical
with include stubs, like this:
include::{common-vc}::page$unix-daemon.adoc[]
I’m not sure supplying identical copies of the documentation that claim to be
for different versions is entirely desirable. Presumably we need two copies
for javax/jakarta, but I’m not sure the one in tomee-site (from CMS) or the
identical 7.0, 7.1, and 8.0 versions are truly essential.
Next I may look into the examples. IIUC the java source for them is going to
remain as javax for the foreseeable future. I think that means that the
README’s should also remain javax-only. Among other things this should enable
easy inclusion of source-code snippets and avoid confusion when the doc says
jakarta and the source says javax.
I suggested earlier that there’s no need for more than one version of the
examples. I haven’t changed my mind on this and although someone didn’t seem
to like the idea, I didn’t see any arguments why having more than one version
was a good idea. Since IMO the largest problem with the docs site is that
there’s too much outdated useless and wrong content, and it’s nearly totally
disorganized, I think reducing the size will make everything else easier.
BTW if anyone wants to try editing asciidoc I recommend using intellij tools
with the asciidctor plugin. It’s fairly Antora-aware and is by far the best
tool I’ve found. IDEA CE works fine for this.
David Jencks
> On Aug 7, 2020, at 10:56 PM, David Jencks wrote:
>
>
>
>> On Aug 7, 2020, at 6:16 PM, David Blevins wrote:
>>
>>> On Aug 7, 2020, at 5:02 PM, David Jencks wrote:
>>>
>>> It’s possible to customize antora to do some sorts of editing on the fly,
>>> but I really don’t recommend it. The first two possibilities are also
>>> pretty bad ideas near Antora.
>>
>> Do you have a link on the editing capabilities?
>
> As far as I know no one has ever done this, and as I said I think it’s a
> really bad idea. However, Antora is flexible enough so this is possible.
>
> IMO magic is really bad news in something like a website that no one is
> really interested in dedicating themselves to. Any time you have something
> happening that is the least bit non-standard and non-obvious you dramatically
> increase the barriers to contribution and maintenance. Maven is sort of
> awful, but it’s fairly consistent, and it pretty much brought about a
> revolution in build systems by a great deal of transparency and consistency.
> I’m going to argue really strongly against any solution that isn’t entirely
> visible from the source. The two solutions I know of are two copies of the
> docs, with the EE prefix hardcoded, and one copy with the prefix as an
> attribute, i.e. asciidoctor “variable”.
>
> Lets look for a solution that is completely visible in the adoc source. I
> think an ee prefix attribute will do that, lets try it.
>
>>
>> Recommended or not, is it possible to do either of the last two and what
>> would that look like?
>
> It would look like incomprehensible magic, and no one would be able to figure
> out how the result was obtained. At least I wouldn’t be able to if I stepped
> away for a week.
>
>>
>>> I think we should take a look at the attribute idea in action before ruling
>>> it out. For one thing, it might be possible to check for non-use of the
>>> attribute by grepping for javax or jakarta, maybe in a pre-commit hook.
>>
>> We can certainly take a look. Even if the feature doesn't get used for this
>> problem doesn't mean learning about it is bad -- we may see another valuable
>> way to use it.
>>
>> In terms of commit hooks, if I had to chose between writing tool/script to
>> force a developer to do something or writing a tool/script to do it for
>> them, I'll always favor the latter if that's possible.
>
> Well, the commit hook might replace either of ‘javax’ or ‘jakarta’ with
> {ee-prefix}. I imagine there would need to be a way to use the other prefix
> in a particular document. That could be another 2 attributes.
>
> David Jencks
>
>>
>>
>> -David
>>
>
Re: [jira] [Commented] (TOMEE-2896) Translate to Portuguese: examples/tomee-jersey-eclipselink
Sergio, i am new in the group. I don't no, the with right thing to be made. But, close the PR, is one of hers. Atenciosamente, Evaldo Junior Em dom., 9 de ago. de 2020 às 11:20, Sergio Chancay escreveu: > HI, i found task free and decided resolved. > > If is a problem close could close PR. > > What I do? > > > On Aug 9, 2020, at 08:06, Evaldo Junior > wrote: > > > > Sergio, i want make more one observation, i send a email for the group, > > after with has opened the issue, warning with i has opened the task, for > it > > can be directioned for me. > > > > > > Regards, > > > > > > Evaldo Junior > > > > > > Em dom., 9 de ago. de 2020 às 09:40, Evaldo Junior < > evaldoapjun...@gmail.com> > > escreveu: > > > >> > >> Sergio, i opened this issue yestarday, but you send a email for group, > >> requisitioned this Issue a d Pr for you. This issue 2896, with the task > >> "Translate to Portuguese: examples/tomee-jersey-eclipselink", translate > the > >> document "examples/tomee-jersey-eclipselink", was anteriorly opened for > >> you ? > >> I searched in all emails of the group, and i don't finded none email for > >> this task. > >> > >> > >> Regards, > >> > >> > >> Evaldo Junior > >> > >> > >> Em dom., 9 de ago. de 2020 às 01:15, Sergio Chancay (Jira) < > >> j...@apache.org> escreveu: > >> > >>> > >>>[ > >>> > https://issues.apache.org/jira/browse/TOMEE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173743#comment-17173743 > >>> ] > >>> > >>> Sergio Chancay commented on TOMEE-2896: > >>> --- > >>> > >>> Pull Request created: [PR 704|https://github.com/apache/tomee/pull/704 > ] > >>> > Translate to Portuguese: examples/tomee-jersey-eclipselink > -- > > Key: TOMEE-2896 > URL: https://issues.apache.org/jira/browse/TOMEE-2896 > Project: TomEE > Issue Type: Sub-task > Components: Examples and Documentation > Affects Versions: 8.0.5 > Reporter: Evaldo Junior > Priority: Major > > Translate into Portuguese the README file using a suffix `_pt` to > allow > >>> the Tomee Website to pick up and configure this version and > corresponding > >>> language > >>> > >>> > >>> > >>> -- > >>> This message was sent by Atlassian Jira > >>> (v8.3.4#803005) > >>> > >> > >
Re: [jira] [Commented] (TOMEE-2896) Translate to Portuguese: examples/tomee-jersey-eclipselink
HI, i found task free and decided resolved. If is a problem close could close PR. What I do? > On Aug 9, 2020, at 08:06, Evaldo Junior wrote: > > Sergio, i want make more one observation, i send a email for the group, > after with has opened the issue, warning with i has opened the task, for it > can be directioned for me. > > > Regards, > > > Evaldo Junior > > > Em dom., 9 de ago. de 2020 às 09:40, Evaldo Junior > escreveu: > >> >> Sergio, i opened this issue yestarday, but you send a email for group, >> requisitioned this Issue a d Pr for you. This issue 2896, with the task >> "Translate to Portuguese: examples/tomee-jersey-eclipselink", translate the >> document "examples/tomee-jersey-eclipselink", was anteriorly opened for >> you ? >> I searched in all emails of the group, and i don't finded none email for >> this task. >> >> >> Regards, >> >> >> Evaldo Junior >> >> >> Em dom., 9 de ago. de 2020 às 01:15, Sergio Chancay (Jira) < >> j...@apache.org> escreveu: >> >>> >>>[ >>> https://issues.apache.org/jira/browse/TOMEE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173743#comment-17173743 >>> ] >>> >>> Sergio Chancay commented on TOMEE-2896: >>> --- >>> >>> Pull Request created: [PR 704|https://github.com/apache/tomee/pull/704] >>> Translate to Portuguese: examples/tomee-jersey-eclipselink -- Key: TOMEE-2896 URL: https://issues.apache.org/jira/browse/TOMEE-2896 Project: TomEE Issue Type: Sub-task Components: Examples and Documentation Affects Versions: 8.0.5 Reporter: Evaldo Junior Priority: Major Translate into Portuguese the README file using a suffix `_pt` to allow >>> the Tomee Website to pick up and configure this version and corresponding >>> language >>> >>> >>> >>> -- >>> This message was sent by Atlassian Jira >>> (v8.3.4#803005) >>> >>
Re: [jira] [Commented] (TOMEE-2896) Translate to Portuguese: examples/tomee-jersey-eclipselink
Sergio, i want make more one observation, i send a email for the group, after with has opened the issue, warning with i has opened the task, for it can be directioned for me. Regards, Evaldo Junior Em dom., 9 de ago. de 2020 às 09:40, Evaldo Junior escreveu: > > Sergio, i opened this issue yestarday, but you send a email for group, > requisitioned this Issue a d Pr for you. This issue 2896, with the task > "Translate to Portuguese: examples/tomee-jersey-eclipselink", translate the > document "examples/tomee-jersey-eclipselink", was anteriorly opened for > you ? > I searched in all emails of the group, and i don't finded none email for > this task. > > > Regards, > > > Evaldo Junior > > > Em dom., 9 de ago. de 2020 às 01:15, Sergio Chancay (Jira) < > j...@apache.org> escreveu: > >> >> [ >> https://issues.apache.org/jira/browse/TOMEE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173743#comment-17173743 >> ] >> >> Sergio Chancay commented on TOMEE-2896: >> --- >> >> Pull Request created: [PR 704|https://github.com/apache/tomee/pull/704] >> >> > Translate to Portuguese: examples/tomee-jersey-eclipselink >> > -- >> > >> > Key: TOMEE-2896 >> > URL: https://issues.apache.org/jira/browse/TOMEE-2896 >> > Project: TomEE >> > Issue Type: Sub-task >> > Components: Examples and Documentation >> >Affects Versions: 8.0.5 >> >Reporter: Evaldo Junior >> >Priority: Major >> > >> > Translate into Portuguese the README file using a suffix `_pt` to allow >> the Tomee Website to pick up and configure this version and corresponding >> language >> >> >> >> -- >> This message was sent by Atlassian Jira >> (v8.3.4#803005) >> >
Re: [jira] [Commented] (TOMEE-2896) Translate to Portuguese: examples/tomee-jersey-eclipselink
Sergio, i opened this issue yestarday, but you send a email for group, requisitioned this Issue a d Pr for you. This issue 2896, with the task "Translate to Portuguese: examples/tomee-jersey-eclipselink", translate the document "examples/tomee-jersey-eclipselink", was anteriorly opened for you ? I searched in all emails of the group, and i don't finded none email for this task. Regards, Evaldo Junior Em dom., 9 de ago. de 2020 às 01:15, Sergio Chancay (Jira) escreveu: > > [ > https://issues.apache.org/jira/browse/TOMEE-2896?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17173743#comment-17173743 > ] > > Sergio Chancay commented on TOMEE-2896: > --- > > Pull Request created: [PR 704|https://github.com/apache/tomee/pull/704] > > > Translate to Portuguese: examples/tomee-jersey-eclipselink > > -- > > > > Key: TOMEE-2896 > > URL: https://issues.apache.org/jira/browse/TOMEE-2896 > > Project: TomEE > > Issue Type: Sub-task > > Components: Examples and Documentation > >Affects Versions: 8.0.5 > >Reporter: Evaldo Junior > >Priority: Major > > > > Translate into Portuguese the README file using a suffix `_pt` to allow > the Tomee Website to pick up and configure this version and corresponding > language > > > > -- > This message was sent by Atlassian Jira > (v8.3.4#803005) >
Re: [VOTE] Release Apache TomEE 7.0.9
+1 On Wed, Aug 5, 2020 at 14:49 Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Hi All, > > I am delighted to present a vote for Apache TomEE 7.0.9 > > > Maven Repo: > https://repository.apache.org/content/repositories/orgapachetomee-1175/ > > Binaries & Source: > https://dist.apache.org/repos/dist/dev/tomee/staging-1175/tomee-7.0.9/ > > Source code: > > https://dist.apache.org/repos/dist/dev/tomee/staging-1175/tomee-7.0.9/tomee-project-7.0.9-source-release.zip > > Tags: > > https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-7.0.9 > > Release notes: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348295 > > Please VOTE: > > [+1] Yes, release it > [+0] Not fussed > [-1] Don't release, there's a showstopper (please specify what the > showstopper is) > > Vote will be open for 72 hours. > > Here is my +1. > > Thanks > > Jon > -- Atentamente: César Hernández.
Re: [VOTE] Release TomEE 7.1.4
+1 On Wed, Aug 5, 2020 at 14:44 Jonathan Gallimore < jonathan.gallim...@gmail.com> wrote: > Hi All, > > I am delighted to present a vote for Apache TomEE 7.1.4 > > > Maven Repo: > https://repository.apache.org/content/repositories/orgapachetomee-1174/ > > Binaries & Source: > https://dist.apache.org/repos/dist/dev/tomee/staging-1174/tomee-7.1.4/ > > Source code: > > https://dist.apache.org/repos/dist/dev/tomee/staging-1174/tomee-7.1.4/tomee-project-7.1.4-source-release.zip > > Tags: > > https://gitbox.apache.org/repos/asf?p=tomee.git;a=tag;h=refs/tags/tomee-7.1.4 > > Release notes: > > https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12312320=12348433 > > Please VOTE: > > [+1] Yes, release it > [+0] Not fussed > [-1] Don't release, there's a showstopper (please specify what the > showstopper is) > > Vote will be open for 72 hours. > > Here is my +1. > > Thanks > > Jon > -- Atentamente: César Hernández.
