Activity
From 09/09/2012 to 10/08/2012
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...
09/10/2012
- 07:32 PM Feature #1531 (Closed): update the "Techniques for Integrating Java Code into Reconverted 4GL Cod...
- 07:28 PM Feature #1530 (Closed): update the "Other Customization" chapter of the Conversion Handbook to ad...
- 07:26 PM Feature #1529: move customer_specific_conversion.rules into p2j/rules/conversion/ and improve/ref...
- This rule set was incorrectly placed in TIMCO's pattern/ directory. It has nothing TIMCO-specific in it. Please mov...
- 07:18 PM Feature #1529 (Closed): move customer_specific_conversion.rules into p2j/rules/conversion/ and im...
- 12:25 PM Feature #1521 (WIP): implement gap analysis rules or backing database/marker approach
- 12:24 PM Feature #1520 (Closed): design gap analysis approach
- 12:20 PM Feature #1519 (New): report improvements
- 12:20 PM Feature #1518 (New): report fixes
- 12:19 PM Feature #1517 (WIP): move to a completely database-backed approach to displaying the conversion a...
- 12:19 PM Feature #1516 (Closed): eliminate the overhead from copying artifacts (.cache, .lexer...) multipl...
- 12:17 PM Feature #1515 (New): implement gap analysis views in all reports
- 12:16 PM Feature #1514 (Closed): implement fully dynamic reports (backed by the database)
- 12:14 PM Feature #1513 (Closed): store all filter results (matches, dump text...) in database
- 12:13 PM Feature #1512 (Closed): separate match processing into a single pass of all report filters per file
- 12:12 PM Feature #1511 (New): Reporting v3
Also available in: Atom