Re: [VOTE] Release Tobago 5.4.0 and checkstyle-rules 20

+1 Dennis

[jira] [Commented] (TOBAGO-2084) CVE suppression for Tobago 5

[ https://issues.apache.org/jira/browse/TOBAGO-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17354216#comment-17354216 ] Dennis Kieselhorst commented on TOBAGO-2084: Why do we require a checkstyle suppression

Re: [VOTE] Release Tobago 4.5.4, 5.0.0-alpha-1 and checkstyle-rules 14

Hi, why do we require a checkstyle suppression for CVE-2021-23343 path-parse? https://nvd.nist.gov/vuln/detail/CVE-2021-23343 mentions that it's fixed in 1.0.7, can't we just use that version? Best, Dennis

Re: [VOTE] Release Tobago 2.4.3 and checkstyle-rules 13

+1 Thanks Udo!

Re: [VOTE] Release Tobago 4.5.1

+1

Re: Release MyFaces Core 3.0.0-M1?

Thank you for driving this Thomas. I like releasing early and often but just indicating a completely refactored version from a different branch with a classifier sounds confusing for me. Why not using 2.4? There will be no JSF 2.4 version so I don't see any conflict there. Regarding extension

[jira] [Commented] (TRINIDAD-2566) NullPointerException after upgrading from apache-tomcat-8.5.47 to apache-tomcat-8.5.49

[ https://issues.apache.org/jira/browse/TRINIDAD-2566?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16990422#comment-16990422 ] Dennis Kieselhorst commented on TRINIDAD-2566: -- Thanks for your bug report

Re: [VOTE] release of MyFaces Core 2.3.5

+1 Thanks Paul!

Re: [VOTE] Release Tobago 4.4.1

+1 Thanks!

Re: [VOTE] Release Tobago 2.4.0

+1 although I don't think it's a good idea to have this breaking change in this old version. Users need to migrate from FileItem to Part and it's no longer possible to use releases as a drop-in replacement in case of security fixes. I'm no longer using 2.x and as no one else spoke up it seems

Re: MyFaces 2.3.3 release issue - any help is appreciated

Hi Paul, looks like an old assembly-plugin version is used. This one is for the stacktrace https://github.com/apache/maven-assembly-plugin/blob/maven-assembly-plugin-2.2.1/src/main/java/org/apache/maven/plugin/assembly/mojos/AbstractAssemblyMojo.java and doesn't allow posix while master

Re: MyFaces 2.3.3 release?

Hi Paul! > I started taking a look at starting the new release today and Eduardo > reminded me that we need to move from SHA1 hashes to SHA256 or SHA512. > > Does anyone know what we need to do in order to fix this in our builds for > the release? See

Re: Jakarta JSF-API at Eclipse EE4J

> I can image something like this: > the javaee-api.jar could contain flatten API classes, without > implementation details. Just the plain API, without actual logic. > user could simply add this as provided dependency. Right that's what I had in mind. Regards Dennis

Jakarta JSF-API at Eclipse EE4J

Hi, yesterday I noticed this issue: https://github.com/eclipse-ee4j/mojarra/issues/4480 Is it that complicated to create an API jar that both works for Mojarra and MyFaces? Regards Dennis

Sonar analysis results for 3.0.0-SNAPSHOT available

Hi, I changed the config for the Sonar build job from SVN to Gitbox master. The Sonar analysis results are now available at: https://builds.apache.org/analysis/overview?id=28170 Regards Dennis

Re: [VOTE] Release Tobago 3.1.1 and 4.3.2

+1

Re: [VOTE] Release Tobago 4.3.1 and checkstyle-rules 12

+1

Re: [VOTE] Release Tobago 2.3.0

+1

Re: MyFaces 3.x - Remove "Impl Shaded" + "Impl Shaded Public"? @cc tobago-guys :P

Go ahead, I don't see a good reason to keep it. Cheers Dennis

Re: MyFaces Core 3.0

On 2018/10/11 12:43:01, Thomas Andraschko wrote: > We could but -1; users can simple stay on 2.x > > Also moving it to own modules is much effort to create and maintain. +1

Re: [VOTE] Release Tobago 2.2.0, 3.1.0, 4.3.0 and checkstyle-rules 11

+1 Thanks!

Re: 2.3.2 Release

> When I perform the above operation there is no new tag created in SVN with > the source code for the 2.3.2 release. Is this now expected since all of > our source is in GIT? I just want to ensure that I'm not missing anything. Yes, SVN is no longer involved (only for site publishing). I can see

Re: 2.3.2 Release

On 2018/08/27 13:19:25, Thomas Andraschko wrote: > I think we just need to change the version after the release in the > core-pom. Correct. I've just updated the file. Regards Dennis

Re: [VOTE] Release of MyFaces Master POM version 19

+1 Thanks!

Re: 2.3.2 Release

Hi! > In the meantime, I have some questions after the move to Git. I'm not sure > if after the move, we have to modify some pom.xml files, do you guys know > if we have to make any modification? Does the release process stay the > same? Any help here would be great. I've changed the scm

Re: Migrate all MyFaces projects to Git

Great, thank you! On 2018/06/21 13:59:15, Werner Punz wrote: > Just deleted it...>

Re: Migrate all MyFaces projects to Git

2.4 etc we'll catch the 2.3.x branch up to master and> > do new forward development in master?> > > Thanks,> > > Paul Nicolucci> > > > > From: Dennis Kieselhorst > > To: > > Date: 05/23/2018 06:20 AM> > Subject: Re: Migrate all MyFaces

[jira] [Commented] (TRINIDAD-2564) maven-faces-plugin

[ https://issues.apache.org/jira/browse/TRINIDAD-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16515854#comment-16515854 ] Dennis Kieselhorst commented on TRINIDAD-2564: -- Find a dev who prepares a release

Re: MyFaces Svn or Git?

Hi Eduardo, you have to use Git. SVN has been switched to readonly. Regards Dennis

Re: Migrate all MyFaces projects to Git

> AFAICS you merged the 2.3.x into master, right? Shoudln't we remove the > 2.3.x branch then? You are right. I was waiting for other opinions regarding 2.4.x in master. For now I've removed the 2.3.x branch. Regards Dennis

[jira] [Commented] (TOBAGO-1899) Error building tobago 4.2.1 on windows 10

[ https://issues.apache.org/jira/browse/TOBAGO-1899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16477002#comment-16477002 ] Dennis Kieselhorst commented on TOBAGO-1899: I was able to reproduce this on a Windows

Re: Migrate all MyFaces projects to Git

So the git migration is finished from INFRA point of view. All active projects from SVN have been moved to git and all previous mirrored repos have also been transfered (except portlet-bridge which was never setup properly and therefore removed). In total we have now 11 repos:

Re: Migrate all MyFaces projects to Git

Build-tools are now also finished, please use https://gitbox.apache.org/repos/asf/myfaces-build-tools.git or https://github.com/apache/myfaces-build-tools from now (default branch is currently wrong on GitHub, needs to be fixed by INFRA). The site needs an update. Several places still mention

Re: Migrate all MyFaces projects to Git

> > WDYT about deleting some unused branches? > > IMO we can remove everything, we just need the normal versions like 2.2.x, > > 1.1.x, ... > > > > 2.1.x-client-window, 2.1.x-copy, 2.0.8_windowid_prototype, ... can be > > removerd. I agree, feel free to remove them. I just took over what we had

Re: Migrate all MyFaces projects to Git

To avoid further confusion I've just done the merge from 2.3.x to master. Please have a look, if everything is fine for you. After that we can delete the 2.3.x branch. Cheers Dennis

Re: Migrate all MyFaces projects to Git

You need to switch to 2.3.x branch. Master still points to 2.2.x because this was trunk before the migration.

Re: Migrate all MyFaces projects to Git

So the migration of MyFaces Core is done. Please use https://gitbox.apache.org/repos/asf/myfaces.git or https://github.com/apache/myfaces from now. Any volunteer who merges 2.3.x to master (former 2.2.x trunk)? I think it makes sense to switch now. I'll continue with build-tools, it's more

Re: Migrate all MyFaces projects to Git

As you might have read in the INFRA issue we are close to migrate the core repo so please do not commit until further notice. This simplifies the migration process. I already have a local git repo, just waiting for INFRA to cleanup old mirrors.

Re: [VOTE] Release Tobago 4.2.1

+1

[jira] [Commented] (TRINIDAD-2564) maven-faces-plugin

[ https://issues.apache.org/jira/browse/TRINIDAD-2564?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463427#comment-16463427 ] Dennis Kieselhorst commented on TRINIDAD-2564: -- Please note that the sources have been

[jira] [Commented] (TRINIDAD-2527) Row selection retains with tr:table

[ https://issues.apache.org/jira/browse/TRINIDAD-2527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16463426#comment-16463426 ] Dennis Kieselhorst commented on TRINIDAD-2527: -- Mike's statement above is still valid. So

Re: Migrate all MyFaces projects to Git

test has been moved to https://gitbox.apache.org/repos/asf/myfaces-test.git and https://github.com/apache/myfaces-test

Re: [VOTE] release of MyFaces Core 2.3.1

+1

Re: Migrate all MyFaces projects to Git

myfaces-master-pom has been moved to https://gitbox.apache.org/repos/asf/myfaces-master-pom.git and https://github.com/apache/myfaces-master-pom I was unable to clone myfaces-core from svn: Checksum mismatch:

Re: Perform MyFaces 2.3.1 release?

Feel free. Could be also a chance to see if everything on Git is working... Regards Dennis

Re: Migrate all MyFaces projects to Git

> > I tried to convert the existing svn repo to git, but unfortunately there > > are historical svn authors like royalts, dave, o_rossmueller, How > > to map them? Are there corresponding Apache committer names or should I use > > dev-n...@apache.org for them? I found out that those

Re: Migrate all MyFaces projects to Git

> I've opened an INFRA issue to get the repos ready: > https://issues.apache.org/jira/browse/INFRA-16402 Got feedback from INFRA, plan is to update existing myfaces repo first and then migrate it to Gitbox. I tried to convert the existing svn repo to git, but unfortunately there are

Re: [VOTE] Release Tobago 4.2.0

Just played around a bit, has anyone seen this before? java.lang.IllegalArgumentException: Intermediate identifier j_id_k in search expression j_id_k::command identifies a UIComponent that is not a NamingContainer at javax.faces.component.UIComponentBase.findComponent(UIComponentBase.java:747)

Re: [VOTE] Release Tobago 4.2.0

Hi Udo, could you please update http://tobago-vm.apache.org with this version? Cheers Dennis

Re: Migrate all MyFaces projects to Git

I've opened an INFRA issue to get the repos ready: https://issues.apache.org/jira/browse/INFRA-16402

Re: Migrate all MyFaces projects to Git

ckstyle files and move them to the tobago and > core itself instead maintain a projects which contains both... > > It think it would be the right momemt to do a cleanup now, to make it > easier to maintain in the future. > > > 2017-09-17 20:16 GMT+02:00 Dennis Kieselhorst <d...@apa

Re: [VOTE] Release of MyFaces Master POM version 18

+1

Re: Questions about MyFaces 2.3.0 release

On 2018/03/10 03:04:46, Eduardo B wrote: > I can even see it here: > http://central.maven.org/maven2/org/apache/myfaces/core/myfaces-api/2.3.0/ > > But not sure why I cannot see it here when I do the search: >

[jira] [Commented] (TOBAGO-1868) Update release process: remove MD5 support

[ https://issues.apache.org/jira/browse/TOBAGO-1868?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16386034#comment-16386034 ] Dennis Kieselhorst commented on TOBAGO-1868: Should be done in myfaces-master-pom for all

Re: [VOTE] release of MyFaces Core 2.3.0

+1 Cheers Dennis

Re: [VOTE] release of MyFaces Core 2.3.0

Hi Eduardo, thanks for building the release. I plan to check it on the weekend. Sorry for the delay... Cheers Dennis

Re: [VOTE] Release Tobago 4.1.0 (2nd try)

+1

Re: [VOTE] Checkstyle Rules version 10

+1

Re: [VOTE] Release Tobago 4.1.0

+1 Next time you could directly use checkstyle-rules 10 if you start a parallel vote anyway.

Re: [Tobago] Preparation for the 4.1.0 release

Hi Udo, I appreciate that. Looks like we will be the first library with Bootstrap 4 final. Cheers Dennis

Re: MyFaces 2.3.0 Release?

Hi Thomas! > Also we probably need to cleanup the branches/trunk a bit?! > Trunk is actually 2.2.x - we should move it to a 2.2.x branch. > Then we would need to merge the changes from 2.3.x into trunk and make > trunk 2.4.x? I would leave 2.3.x in trunk for a while as we did with 2.2.x before.

Re: [VOTE] Release Tobago 2.1.1

+1

Re: [VOTE] Checkstyle Rules version 9

+1

[jira] [Commented] (TOBAGO-1837) Update Bootstrap to 4.0.0 beta 3 (from beta 2)

[ https://issues.apache.org/jira/browse/TOBAGO-1837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16331943#comment-16331943 ] Dennis Kieselhorst commented on TOBAGO-1837: FYI 4.0.0 stable has just been released

[jira] [Resolved] (MYFACES-4140) NullPointerException instead of InvalidViewIdException

[ https://issues.apache.org/jira/browse/MYFACES-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved MYFACES-4140. - Resolution: Duplicate Assignee: Dennis Kieselhorst Fix Version/s

[jira] [Updated] (MYFACES-4002) Regression? - References to external entities not working with WebXmlParser

[ https://issues.apache.org/jira/browse/MYFACES-4002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst updated MYFACES-4002: Resolution: Not A Problem Status: Resolved (was: Patch Available

Re: [VOTE] Release of MyFaces Master POM version 17

+1

[jira] [Resolved] (TOBAGO-1836) Add Automatic-Module-Name MANIFEST entry for Java 9 compatibility

[ https://issues.apache.org/jira/browse/TOBAGO-1836?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved TOBAGO-1836. Resolution: Fixed Fix Version/s: 4.1.0 I've set

Re: [ANNOUNCE] Apache Tobago 4.0.0 Release

Hi Udo, thanks for doing the release. I've reposted the annoucement to annou...@apache.org, should be part at least for major releases. Regards Dennis

Re: MyFaces Master POM should be released

> I wish the master pom.xml should be released soon. It hasn't been > released a long time (2015). The last release has apache pom 13 (2013) > as parent, currently 18 (2016) is released. > I fully agree, already suggested that a year ago. Cheers Dennis

Re: [VOTE] Release Tobago 4.0.0 2nd try

+1

[jira] [Commented] (TRINIDAD-2561) JSF Partial State Saving is not enabled

[ https://issues.apache.org/jira/browse/TRINIDAD-2561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16275991#comment-16275991 ] Dennis Kieselhorst commented on TRINIDAD-2561: -- We welcome your pull requests: https

Re: [VOTE] Release Tobago 4.0.0

+1

Re: [Tobago] Preparation for the 4.0.0 release

> the email address in the ~/.gitconfig must be added to the account in > github.org Right, it works out of the box if you use the apache.org address. Looks better now. Verified is another story, I don't think that's important, but you could of course sign your commits:

Re: [Tobago] Preparation for the 4.0.0 release

Hi! > I plan to build the 4.0.0 of Tobago soon. Great to hear that. Some things I've noticed while reviewing it today: Udo and Henning, your commits are no longer linked to your GitHub account (see https://github.com/apache/myfaces-tobago/commits/master) - you should fix that.

[tobago] (INFRA-13743) Allow deploy execution from builds.apache.org on *-vm.apache.org

Hi, please check the comment from Daniel and participate in the discussion. Cheers Dennis Re: Allow deploy execution from builds.apache.org on *-vm.apache.org For updating the demo instance of the app on your VM, is polling the public

Re: Increase checkstyle max line length?

definitely +1

Re: myfaces 2.3.x impl pom.xml update question

> Is there any reason to still have the import? No of course not, good catch. I've fixed it. Cheers Dennis

Re: Need help with git

Hi Volker! > first i tried github credentials on > https://github.com/apache/myfaces-tobago. It looks like git on console > did not work with the two factor auth. You need to setup a personal access token for that:

Re: Migrate all MyFaces projects to Git

> https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been > migrated yet, I've requested a new repo for it. Migration of trinidad-maven is finished: https://github.com/apache/myfaces-trinidad-maven or https://gitbox.apache.org/repos/asf?p=myfaces-trinidad-maven.git

Re: Migrate all MyFaces projects to Git

I finally managed to migrate trinidad. Please use https://gitbox.apache.org/repos/asf/myfaces-trinidad.git or https://github.com/apache/myfaces-trinidad from now on. SVN has been marked as readonly. https://svn.apache.org/repos/asf/myfaces/trinidad-maven/ has not been migrated yet, I've

Re: [VOTE] Release Tobago 3.0.6

+1 Looks fine for me but please note that integration tests are failing in 3.0.x branch and also in master: https://builds.apache.org/view/M-R/view/MyFaces/job/Tobago%20Trunk%20integration-test/

Re: Migrate all MyFaces projects to Git

On 2017-09-08 09:49, Dennis Kieselhorst <d...@apache.org> wrote: > Trinidad will follow till Sunday. Short update on Trinidad git migration. I used the following command: git svn clone --stdlayout --no-metadata --authors-file=authors.txt https://svn.apache.org/repos/asf/myfaces

[jira] [Commented] (MYFACES-4140) NullPointerException instead of InvalidViewIdException

[ https://issues.apache.org/jira/browse/MYFACES-4140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16159837#comment-16159837 ] Dennis Kieselhorst commented on MYFACES-4140: - Well I'm unsure how to fix it. Simply adding

Re: Migrate all MyFaces projects to Git

> Finally I have a working setup to migrate the subversion history to git. > I already started with Tobago yesterday, Trinidad will follow till Sunday. > > The result for Tobago is the following, will send another mail after > having pushed this to Gitbox: Tobago is finished:

Re: Migrate all MyFaces projects to Git

Finally I have a working setup to migrate the subversion history to git. I already started with Tobago yesterday, Trinidad will follow till Sunday. The result for Tobago is the following, will send another mail after having pushed this to Gitbox: origin/TOBAGO-1719 origin/lofwyr

[jira] [Commented] (MYFACES-4135) Use Java8 instead of commons

[ https://issues.apache.org/jira/browse/MYFACES-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16152667#comment-16152667 ] Dennis Kieselhorst commented on MYFACES-4135: - I think we should keep it. The beanutils

[jira] [Commented] (MYFACES-4135) Use Java8 instead of commons

[ https://issues.apache.org/jira/browse/MYFACES-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16144239#comment-16144239 ] Dennis Kieselhorst commented on MYFACES-4135: - Ok, just fixed the log message and simplified

[jira] [Commented] (MYFACES-4135) Use Java8 instead of commons

[ https://issues.apache.org/jira/browse/MYFACES-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16142663#comment-16142663 ] Dennis Kieselhorst commented on MYFACES-4135: - I would use java.util.function.Predicate

[jira] [Commented] (MYFACES-4135) Use Java8 instead of commons

[ https://issues.apache.org/jira/browse/MYFACES-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141320#comment-16141320 ] Dennis Kieselhorst commented on MYFACES-4135: - How to migrate

[jira] [Commented] (MYFACES-4135) Use Java8 instead of commons

[ https://issues.apache.org/jira/browse/MYFACES-4135?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16141317#comment-16141317 ] Dennis Kieselhorst commented on MYFACES-4135: - [~tandraschko] in the comment you mentioned

[jira] [Created] (MYFACES-4140) NullPointerException instead of InvalidViewIdException

Dennis Kieselhorst created MYFACES-4140: --- Summary: NullPointerException instead of InvalidViewIdException Key: MYFACES-4140 URL: https://issues.apache.org/jira/browse/MYFACES-4140 Project

[jira] [Commented] (MYFACES-4134) Update to commons-collections 4

[ https://issues.apache.org/jira/browse/MYFACES-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16138407#comment-16138407 ] Dennis Kieselhorst commented on MYFACES-4134: - Ok great I'll close this one as duplicate

[jira] [Commented] (TRINIDAD-2559) UNZIP_STATE_FAILED Exception

[ https://issues.apache.org/jira/browse/TRINIDAD-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16135518#comment-16135518 ] Dennis Kieselhorst commented on TRINIDAD-2559: -- Please tell us more about the page

[jira] [Commented] (MYFACES-4134) Update to commons-collections 4

[ https://issues.apache.org/jira/browse/MYFACES-4134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16130193#comment-16130193 ] Dennis Kieselhorst commented on MYFACES-4134: - Only four classes are in use

[jira] [Created] (MYFACES-4134) Update to commons-collections 4

Dennis Kieselhorst created MYFACES-4134: --- Summary: Update to commons-collections 4 Key: MYFACES-4134 URL: https://issues.apache.org/jira/browse/MYFACES-4134 Project: MyFaces Core Issue

[jira] [Resolved] (TOBAGO-1781) Update to commons-lang 3

[ https://issues.apache.org/jira/browse/TOBAGO-1781?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved TOBAGO-1781. Resolution: Fixed > Update to commons-lan

[jira] [Created] (TOBAGO-1781) Update to commons-lang 3

Dennis Kieselhorst created TOBAGO-1781: -- Summary: Update to commons-lang 3 Key: TOBAGO-1781 URL: https://issues.apache.org/jira/browse/TOBAGO-1781 Project: MyFaces Tobago Issue Type

[jira] [Resolved] (TOBAGO-1780) Update to commons-collections 4

[ https://issues.apache.org/jira/browse/TOBAGO-1780?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dennis Kieselhorst resolved TOBAGO-1780. Resolution: Fixed > Update to commons-collection

[jira] [Created] (TOBAGO-1780) Update to commons-collections 4

Dennis Kieselhorst created TOBAGO-1780: -- Summary: Update to commons-collections 4 Key: TOBAGO-1780 URL: https://issues.apache.org/jira/browse/TOBAGO-1780 Project: MyFaces Tobago Issue

  1   2   3   4   >