Activity for Thomas Bark
-
Thomas Bark modified a comment on ticket #404
Hi Avner, are you using plugin version 2.2.43? I'm also using eclipse 2022-12 (CDT), with base clearcase (not UCM). I dont have such errors when using "clearcase refresh". br, Thomas
-
Hi Avner, are you using plugin version 2.2.43? br, Thomas
-
Hi Nimrod, I will try to check next days, in my CC environment at work. Do you use UCM or base CC? br, Thomas
-
Hello Lidia, Sorry I didn't watched the discussion. Now I pushed the missing file on master branch and merged master to develop. P.S. For version 2.2.43 I couldn't reach the maintainer (Mikael) of the project, so the web site is not up-to-date. I have no access rights for doing this. Best regards Thomas
-
plugin.properties added to META-INF
-
Hi, did you restart eclipse after installing the plugin? Only then the CC menu is visible. After installing the plugin from update site https://sourceforge.net/projects/eclipse-ccase/files/updatesite/ and restarting Eclipse you should also see it in Help->About Eclipse IDE->Installation Details in both "Features" and "Plugins" page. As far as I remember the plugin should also work with jre-1.8. (For Testing and Deployment I needed jre-1.11) br, tom
-
Hi Nimrod, can you please update to plugin version 2.2.43 and try again. Thanks, Thomas
-
Version 2.2.43
-
Version 2.2.43
-
Hi Lydia, Now that I’m back from Romania, I checked my commits. After releasing 2.2.42, I discovered this error and wrote bug#403. https://sourceforge.net/p/eclipse-ccase/bugs/403/ https://sourceforge.net/p/eclipse-ccase/bugs/403/ It’s solved with commit 8702bda... (I checked in my CC environment). @Mike: Hi Mike, is it possible that you deliver a version 2.2.43, with ALL the commits I did after 2.2.42? I use this code in productive environment, since February. As I switched my Linux environment...
-
<meta name="viewport" content="width=device-width"> <meta http-equiv="Content-Type" content="text/vnd.ui.insecure+html;charset=utf-8"> Hi Lidia,Right now I'm In vacation in Maramures. So i cannot check the details.I did a mistake in latest version of the plugin. It's already solved on a branch, but not delivered as a new version. Please check my commits after last official delivery.Buna, Thomas--Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 01.09.21, 19:33 schrieb...
-
branch deprecation merged to develop
-
The fault was applicable for "compare to other view (external)" too. [bug_403_extdiff 8702bda] Bug #403 solved
-
[bug_403_extdiff 8702bda] Bug #403 solved
-
Bug #403 solved
-
:-)
-
comapre against predecessor with external tool fails for checked-outs
-
Hi Adalbert, I was not aware of your proposed link for the update site. I get an empty screen if you try to open it in the browser. Can you please try again with the "official" updatesite: https://sourceforge.net/projects/eclipse-ccase/files/updatesite/ Best regards Thomas
-
Cu placere, Lydia. Seara buna, Thomas Am 12.01.2021 um 17:46 schrieb Lidia Popescu lidochca@users.sourceforge.net: Thank you Thomas for adding this. Kind Regards Lidia
-
Merge branch 'master' into develop
-
Merge branch 'master' into develop
-
Improvement: only one dialogue for UCM checkout
-
Solved in 2.2.42. Please close ticket.
-
Solved in 2.2.42. Please close ticket.
-
Solved in 2.2.42. Please close ticket.
-
Solved in 2.2.42. Please close ticket.
-
linux,macosx,win32 marked in site.xml
-
Deployment should go directory /home/frs/project/e/ec/eclipse-ccase/eclipse-ccase_Eclipse_4.0 iso 4.x
-
2.2.42 Release
-
2.2.42 Release
-
branch bug_388_extdiff merged
-
local branch get_rid_of_warnings_2 merged
-
superflous import removed
-
Bugs #387, #388, #391 solved
-
Hi Mike, I solved this within bug_388 branch. Please set to open-accepted. br, tom
-
Hi Mike, please set do duplicate of #388. Will be solved with #388. br, Tom
-
Hi Mike, In the commit [7c9eff] (in the develop branch of CC for Java) I did a more generic solution, based on Lidia's commit. Also the tests run successfully without any changes. My prososal is to make a 2.2.42, and then I continue (don't have much time) with replacing some deprecated functions, and/or solving other bugs. What is your opinion. br, tom
-
bug_369_trigger_causes_array_outof branch merged to develop
-
Use if JavaSE-1.8; some deprecated functions replaced
-
generic solution for #369
-
when I adapt the String in ForbiddenToCreateElementInDumbo.java to the output of my trigger, then I get the dialog in the attachment.
-
My CC admin created a mkelem preop trigger for me. When I tried to add a file, with the solution on 369 branch I neither get any dialog nor any exception. The text of the trigger, which refused mkelem , is simply printed in the console: Executing cleartool command: co -nwa -c add /data/il90/vobs/ilsmplay Checked out "/data/il90/vobs/ilsmplay" from version "/main/4". Command 26 returned status 0 --> finished, exit status 0, duration: 29ms Executing cleartool command: mkelem -c add -pti -master /data/il90/vobs/ilsmplay/testfile_mkelem.c...
-
My CC admin created a mkelem preop trigger for me. When I tried to add a file, with the solution on 369 branch I neither get any dialog nor any exception. The text of the trigger, which refused mkelem , is simply printed in the console: Executing cleartool command: co -nwa -c add /data/il90/vobs/ilsmplay Checked out "/data/il90/vobs/ilsmplay" from version "/main/4". Command 26 returned status 0 --> finished, exit status 0, duration: 29ms Executing cleartool command: mkelem -c add -pti -master /data/il90/vobs/ilsmplay/testfile_mkelem.c...
-
Or simply all-in-one: cleartool lstype -long -kind trtype -invob /vobs/my_vob List all mkelem triggers in all vobs of one path_ for dir in ./* ;do echo $dir; cleartool lstype -long -kind trtype -invob $dir |grep -B 5 mkelem;done
-
Or simply all-in-one: cleartool lstype -long -kind trtype -invob /vobs/my_vob
-
lidia's commit [680a73]
-
Hi Lidia, when testing with your clone, I got 2 failing tests. * MoveOutputScenarioTest.testSuccessfulMove() line: 37 One Element is expected, but there are 2 strings in cess: 1. cleartool: Warning: Moved element with checkouts to "src/cm_add.c"; CHECKED_IN CHECKED_OUT CHECKED_OUT_BY_DIFFERENT_USER CHECKED_OUT_IN_DIFFERENT_BRANCH CHECKED_OUT_IN_DIFFERENT_VIEW HIJACKED MISSING OUTSIDE_VOB RESERVED UNRESERVED VIEW_PRIVATE DERIVED_OBJECT LINK ALREADY_CHECKED_OUT MOVED, 2. cm_add.c MOVED DeleteOutputScenarios.testSuccessfulDelete()...
-
Bună ziua Lidia! Thanks for the commits, I will check if I can simply merge them, or if they interfere with Mike's bugfix. Still in search for an "add to CC"-trigger in the vobs I have access to :-( Weekend plăcut, Thomas
-
@eraonel I didn't found a "add to source control" trigger in our vobs, and don't have admin right to create one. I try to ask the admin to temporarely add one.
-
Eclipse ccase plugin 2.2.41
-
updatesite/lib updated to actual versions
-
further updates in deployment files
-
update of the deployment files
-
Ok, I will give it a try :-) Thanks. Tom
-
master merged to develop
-
Hi Mike, yes, I would suggest so. With the current status the plugin can be used with more recent Eclipse versions, and some of the bugs are fixed. I would continue bugfixing after the release, in subbranches of develop branch. If I could help with the reelase, or learn the how to, please tell me. br, tom
-
Hallo Michael, bist du noch in der Firma nebenan? Gefällt es dir dort? @mike: resolved by commit [b059ab] Bug #398 resolved Pls. set bug to accepted (as well as #389,397,401). Best regards, Thomas
-
Bug #398 resolved
-
merged from master
-
CHANGELOG.TXT: Bug #397 added
-
hi mike commit aa0366 tom
-
Bug #397: System.out.println debug statement commented out
-
Hi, I solved the test errors. More or less elegant. Should I now try to solve other bugs? I would prefer to make a 2.2.41 release now, for use with newer versions of eclipse. And then to start with other bugs, like #398 (from my former collegue). br, Tom
-
unused 3rdparty libs removed
-
Errors of tests resolved
-
Hi Mike, now that I'm able to run the tests, with an actual version of powermock/easymock, I will solve some of the failing tests (NullPointerException). I'll keep you informed, when its finished. br, Tom
-
revert unneeded change in ClearCaseCLIImplTest.java
-
powermock-easymock-junit-1.4.10 replaced by powermock-easymock-junit-2.0.2 to enable tests with java 1.12
-
Hi Mike, no progress with the 2 test suites. Also my son, who is more into it, couldn't solve the errors about missing powermock while starting the tests. I will try with the commit for 2.2.40 in an extra eclipse workspace, to get the tests running. But any help is appreciated. Must be something in the eclipse configuration for running tests. As the static code analyser doesn't complain about the test sources, its not a problem in the source files. br, Tom
-
Hi, it is included in the git repo: /Users/tom/git/eclipse-ccase-new/eclipse-ccase-code/net.sourceforge.eclipseccase/lib tom@Thomass-MBP lib % tree .. zsh: command not found: tree tom@Thomass-MBP lib % ls -lr total 0 drwxr-xr-x 8 tom staff 256 6 Okt 12:33 powermock-easymock-junit-1.4.10 tom@Thomass-MBP lib % ls -lR total 0 drwxr-xr-x 8 tom staff 256 6 Okt 12:33 powermock-easymock-junit-1.4.10 ./powermock-easymock-junit-1.4.10: total 3544 -rw-r--r-- 1 tom staff 322362 6 Okt 12:33 cglib-nodep-2.2.jar...
-
Now it found the missing packages. I had to check them in Java Build Path. When starting the test it now complains about java.lang.TypeNotPresentException: Type org.powermock.modules.junit4.PowerMockRunner not present
-
one of the 2 failing test logs.
-
the successful junit of clearcase_for_java. on master with commit 2f652b.
-
did new clones, import from existing projects into workspace, plugin.xml - export wizard, same errors in eclipseccase.test and .ui.test. couldnt resolve easymock.. couldn't resolve Powermock.. Eclipse RCP 2020-09-R
-
I coudn't adapte the test, as they are not runing here. 2.1.) Maybe I did it wrong. I used the Import/Git/Projects from Git (with smart import). I should have used the General/Existing Projects into workspace instead? I wasn't aware that the eclipse .project files are part of the repo. I think I will open a second workspace, with import existing project wizard. 3.2.) plugin.xml - Export Wizard
-
Eclipse Compiler for Java(TM) v20200828-0941, 3.23.0, Copyright IBM Corp 2000, 2020. All rights reserved. ERROR in /Users/tom/git/code/net.sourceforge.eclipseccase.test/src/net/sourceforge/eclipseccase/test/ClearCaseProviderTest.java (at line 20) import org.easymock.EasyMock; ^^^^^^^^^^^^ The import org.easymock cannot be resolved
-
Hi Mike. Now I was able to run the junit for the clearcase for java project! So I suppose in my eclipse-case eclipse project this 3rdparty link to easymock-3.0(like in clearacse project) etc. is missing. Do you have a hint, how I get it into the eclipse-ccase project? br, tom
-
some warnings removed
-
Good Morning, I merged the clearcase develop branch to master too (no changes by me, I think). cu, Tom
-
develop branch merged to master for 2.2.41
-
.gitignore added
-
Hi Mike, I merged the develop branch into master (commit 8f3916), for the eclipse-ccase project only (for clearcase I have no access rights, I assume?). Please try to get the tests running. Tomorrow I will check the build of the master branch in my CC installation. CU, Tom
-
develop branch merged for 2.2.41
-
.gitignore added
-
CHANGELOG.txt updated
-
branch bug_389 merged
-
branch get_rid_of_warnings merged
-
get rid of some warnings, part 2
-
bug 387 .. bug 389;JSE1.5
-
CHANGELOG.txt only bug 387
-
Merge branch 'bug_389' of ssh://git.code.sf.net/p/eclipse-ccase/code into bug_389
-
getAdapter Warnings removed
-
#389 + adaption to OPenJDK 11, and Eclipse 4.17
-
get rid of some warnings
-
<meta content="width=device-width" name="viewport"> <meta content="text/vnd.ui.insecure+html;charset=utf-8" http-equiv="Content-Type"> Yes, I can check it.And verify with eclipse 2020-09 (jre1.11) and 2020-03(jre1.8).What I cannot do, is running the junit tests (due to lack of knowledge, and missing easy mock 3.0 in my eclipse project).-- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 05.10.20, 15:37 schrieb Mikael Petterson <eraonel@users.sourceforge.net>: I don't...
-
<meta content="width=device-width" name="viewport"> <meta content="text/vnd.ui.insecure+html;charset=utf-8" http-equiv="Content-Type"> Hi Mike,Which parts shall I merge in the master branch?Only #401?Also #389?Whole develop branch?Tom-- Diese Nachricht wurde von meinem Android Mobiltelefon mit GMX Mail gesendet.Am 05.10.20, 13:06 schrieb Mikael Petterson <eraonel@users.sourceforge.net>: Hi, Can you merge into master so we can make a delivery? //mike [bugs:#401] Preference "No. of versions in history:"...
-
Hi, with the commit [72986b] in the develop branch the history limit works as expected, both with numbers, e.g. "7:" or by date, e.g. ":2018-01-01". Tom
-
Hi, in https://sourceforge.net/p/eclipse-ccase/code/ci/72986bbd28650b28e7fe10df994ec88d77fd2364/tree/net.sourceforge.eclipseccase/src/net/sourceforge/eclipseccase/ClearCasePreferences.java I added Jan's correction in ClearCasePreferences::getHistoryRecord to the develop branch. Somehow the patch didn't made it into the branch before. On monday I can test it in a CC installation. Have a nice weekend Tom
-
#401 solution from Jan's patch put to ClearCasePreferences.java
-
bug 387 .. bug 389;JSE1.5
1 >