Activity
From 09/15/2012 to 10/14/2012
10/12/2012
- 05:13 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- OK. The Windows conversion is in progress.
For now the known issues are:
1. The maximum heap size I can request o... - 04:25 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- I agree, the truncation problem does appear to happen on staging too, so that is just a bug that already exists.
G... - 03:32 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The news.
I have converted another MAJIC build. The source is from staging + "New" rule set and helper update. The... - 07:00 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Guys,
The problem with
> compile_jasper:
> [jrc] Compiling 1 report design files.
> File : /home/eugenie/timco_... - 05:32 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Another very interesting finding. Take a look at staging build on lightning. The files
src/syman/adp/adpchkls.p.lexe... - 04:58 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Constantin, Greg,
Strange thing I have got while converting staging sources:
Conversion has been finished but the... - 04:29 PM Bug #1589: during parsing the .lexer file is sometimes arbitrarily truncated
- This behavior can be seen by:
1. Make an exact copy of a conversion project (duplicate the entire directory tree).... - 04:26 PM Bug #1589 (New): during parsing the .lexer file is sometimes arbitrarily truncated
10/11/2012
- 07:15 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- OK.
- 05:48 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Those versions of the code (from 2009 and 2010) are much too old to be useful. Please rebuild your local environment ...
- 04:58 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Another question. Trying to run conversion in Windows I have the following message:
D:\timco_win>CMD.EXE /C ""C:\Prog... - 04:52 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- > Where did you get these?
In my current timco/src subdirectory:
eugenie@cyborg64:~/timco/src> ls -l *.zip
-rw-r... - 04:48 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- ...
- 04:30 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The previous message is updated with customer_libs directrory instruction. And I have checked all created log files a...
- 04:21 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- > Do you have 2 completely independent project installations? With 2 completely separate P2J installations?
Yes, the... - 02:34 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- I didn't mean that the command line environment itself was a problem (although it is possible). I meant that in gene...
- 11:15 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- > The .lexer file is truncated at [01386:003] and there is nothing after that?
Yes, this file finished at [01386:0... - 10:59 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- OK, these are some strange results....
- 09:10 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- One more note.
> Since the comparisons are just about the differences in src/aero/timco/majic/
These directorie... - 09:02 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- > Please show examples of both.
Here is the src/syman/adp/adpout0.p.lexer
The Old MAJIC conversion with "classi... - 11:08 PM Feature #1579: review and merge 12/2011 conversion fixes into main P2J code base, regression test...
- The following is the text of an email I sent to Greg regarding one of the fixes, which had to do with schema parsing ...
- 11:06 PM Feature #1579: review and merge 12/2011 conversion fixes into main P2J code base, regression test...
- In December 2011, Greg and I made a number of fixes to P2J to enable early work on a large customer project (updates ...
- 10:33 PM Feature #1579 (Closed): review and merge 12/2011 conversion fixes into main P2J code base, regres...
10/10/2012
- 07:39 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- ...
- 07:06 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- OK.
BTW, I have faced the strange issue. I did run two conversions in Linux. The both was OK. Then I have compared... - 06:49 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Since the comparisons are just about the differences in src/aero/timco/majic/, the amount of code is actually not so ...
- 06:27 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Greg,
OK. I'm running the conversions. The difference reports will be here. But what is the place to upload result... - 05:16 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Please report on the status of the 2 testing activities:
1. Old P2J majic conversion on Linux vs new P2J majic con... - 06:44 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Understood. Then you need to put the cfg files for MAJIC in a separate update.
- 05:21 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Constantin,
This was not mistake. I have added the config files for TIMCO conversion under Linux/Windows. This is ... - 03:36 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Eugenie,
Please remove the cfg/ folder from the root of your update. Except this, the update looks OK.
10/09/2012
- 11:45 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Eugenie,
For 2 - as you change a file, if the current year is different than the one in the copyright area, you ne... - 10:06 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Constantin,
1. OK.
2. I do not understand. Why this special update need this modification? Do we need every file ... - 05:57 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Eugenie,
Please address the following:
1. the p2j.cfg.xml you sent is for Windows OS. Please leave the p2j.cfg.xml ...
10/08/2012
- 05:41 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- OK.
The files to be changed to run conversion on Windows.
Rules:
p2j/rules/annotations/annotations.xml
p2j/rule... - 04:04 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Don't apply the changes to staging or CVS yet. Please do the following:
1. Send the changes to Constantin (and co... - 03:49 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The changes are tested and prepared. Do we need them to be applied to the current P2J build? Note we still need to ma...
- 09:20 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Please do use the quoteReplacement() for all of the 2nd parameter cases. That is exactly what that code is meant to ...
10/05/2012
- 04:42 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Greg, Constantin,
I've performed a bit more testing and found we can use both fixupRegex() and quoteReplacement() ... - 10:21 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Constantin,
Yes, the call
replaceAll("\.", quoteReplacement(fileSep))
does work. So I applied fixupRegex() and q... - 06:26 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Eugenie, please try the following call in the conversion rules:
replaceAll("\.", quoteReplacement(fileSep))
I sus... - 09:42 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Preliminary results:
1. Substitution replaceAll(fileSep, ".") with replaceAll(fixupRegex(fileSep), ".") works fine.
...
10/04/2012
- 01:25 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- ...
- 01:10 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Constantin,
There are no such elements in our rule files as second parameter for replaceAll(): "\\" as the file se... - 12:48 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Please prepare the minimum set of changes needed to resolve all the known problems. Add a helper as needed to Common...
- 12:45 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Greg,
I've done a little more testing in why it abends in the first place and it looks like calls like this:
<pre... - 12:01 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- After thinking more about this, I realize that my idea about adding a getFileSepRegex() is not a full solution. The ...
- 11:45 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- I think this would be a more appropriate solution.
OK. I'll look into this.
> > Is it mandatory to use replaceA... - 08:01 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- ...
10/03/2012
- 07:32 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Further investigations and testing shows the only real issue we have converting on Windows is the replaceAll call wit...
10/01/2012
- 12:16 PM Bug #1574: broken report links when they target very long filenames
- From ECF:
I've noticed that some detail reports with really long names create links with longer names than the act... - 12:14 PM Bug #1574 (Closed): broken report links when they target very long filenames
09/30/2012
- 03:01 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Now we have the promes.p converted. The main issue is the Windows file separator char: "\" and some calls that uses t...
09/28/2012
- 04:35 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Eugenie, a question. Are you sure that the following:
<annotation datatype="java.lang.String" key="path" value="co... - 02:55 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Eugenie, a question. Are you sure that the following:...
- 02:37 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- There is still issue with p2o generation I guess. Consider the following:
In Linux we have the following line:
... - 02:18 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- I think real problem here is how windows JRE handles regexps... especially cases when special regexp characters need...
- 01:41 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The backslash issue is the real problem. Now we have stopped in the other place on the generating DDL stage:
28.09.2... - 12:12 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The main difference at conversion stage is the primes.p.ast files. For example the following lines are missed in Win3...
- 11:58 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The resulting files primes.p.schema have difference:
The Windows version does not have the entries like this:
<an... - 11:55 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The resulting files:
primes.p.cache, primes.p.dict, primes.p.lexer, primes.p.parser
are the same for both Linux... - 11:50 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The schema conversion has the difference:
Win32 version does not have any peerid entries like below:
<annotation da... - 11:46 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- For some reason, on a Windows machine, any escaped value in a regexp needs two backslashes, as in:
package.replaceAl... - 11:43 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The conversion from *.df to *.dict is performing without the problems. The results are the same for Linux and Win32 e...
- 10:54 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The conversion log file:
------------------------------------------------------------------------------
P2J Convers... - 10:43 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The java P2J classes are compiled without problems with ANT 170 and Java 160_u35. To be able to start the conversion ...
- 11:48 AM Feature #1529 (WIP): move customer_specific_conversion.rules into p2j/rules/conversion/ and impro...
09/21/2012
- 10:02 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Windows XP is fine.
Yes, p2j/testcases/uast/primes.p from CVS is the correct file. - 09:45 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The file has been found. Is it correct file?
- 09:36 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Another question:
Where the primes.p file is located?
EVL: I have found the file under timco/p2j/testcases/uast. Is... - 08:00 AM Feature #1565: test the full conversion process on Windows and document all problems that are found
- The question:
Is it important to have specific Windows version to test the conversion? I can run it in Windows XP,... - 08:39 PM Feature #1565: test the full conversion process on Windows and document all problems that are found
- Run the conversion process for primes.p on Windows. Put detailed documentation into this issue's history for all pro...
- 08:35 PM Feature #1565 (Closed): test the full conversion process on Windows and document all problems tha...
Also available in: Atom