Hi Jean-Luc, Indeed the ANT build file's root element name is called "project", similar with the Oxygen project.xpr but there is no relationship between them, it's just a naming coincidence. The ANT build file is usually called "build.xml", you can create a new ANT build file by using Oxygen's File->New. Once you have an ANT build file the "Configure Transformation Scenarios" toolbar action should already show a predefined transformation scenario for it. You can duplicate the transformation scenario and define a custom set of parameters that you want to send to the build file. Regards, Radu Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com On 6/19/2019 12:20 PM, Jean-Luc Chevillard wrote:
Dear Radu,
which extension should be given to the ANT file.
I have several times examined (with the help of a text editor, namely Notepad++) the content of Oxygen's "project files" (which come with an .xpr extension)
This is for instance what appears at the top level of my current project (in which the .xpr file has 4987 lines (and contains 48 scenario elements
<?xml version="1.0" encoding="UTF-8"?> <project version="21.1"> <meta> ........................ </meta> <projectTree name="Proen%C3%A7a.xpr"> <folder path="."/> </projectTree> </project>
The top element is callled "project", as in your ANT example
However, since the .xpr files are created by Oxygen and I (the user) do not have any control on their content, I imagine it might be dangerous to create manually an .xpr without understanding the structure which is expected.
Can you confirm that Oxygen users are not expected to manually edit .xpr file?
Best wishes
-- Jean-Luc (in Paris)
https://univ-paris-diderot.academia.edu/JeanLucChevillard
On 18/06/2019 14:13, Oxygen XML Editor Support (Radu Coravu) wrote:
Hi Jean-Luc,
The fourth alternative is by using an ANT build file:
<project basedir="." name="" default="dist"> <target name="dist"> <xslt in="File_A.xml" out="File_B.xml " style="Script_1.xslt" force="true"/>
<xslt in="File_B.xml" out="File_C.xml " style="Script_2.xslt" force="true"/> </target> </project>
and creating a transformation scenario in Oxygen which applies it.
Regards, Radu
Radu Coravu <oXygen/> XML Editor http://www.oxygenxml.com
On 6/17/2019 10:54 AM, Jean-Luc Chevillard wrote:
Dear Patrick,
thanks a lot!
I have just tried solution 2 (with a very short pipeline) and it worked like a charm
I had never noticed the "Additional XSLT Stylesheets" button, inside the "Edit Scenario" small window. Thanks for showing it to me. :-)
I had been looking for it in the wrong place (the "Configure Transformation Scenarios")
I am also glad to have been told about the existence of https://www.w3.org/TR/xproc/
It looks like an interesting domain to explore
Best wishes
-- Jean-Luc (in Paris)
https://univ-paris-diderot.academia.edu/JeanLucChevillard
On 17/06/2019 06:20, Dr. Patrik Stellmann wrote:
Hi Jean-Luc,
I see the following options: 1. Create an XProc transformation scenario. There you will be able to create a pipeline with several xslt-stages. But you will need to learn a new programming language... 2. Create an XSLT transformation scenario and specify "additional XSLT stylesheets". But you will only get the final result file without intermediate results. 3. Create a new XSLT stylesheet the includes/imports you current stylesheets and. But this might not work if your current xslt stylesheets are incompatible (e.g. they all use the default transformation mode).
I'd recommend to start with option 2.
Regards, Patrik
Dr. Patrik Stellmann
Anwendungsarchitektur und Koordination GDV Dienstleistungs-GmbH | Niederlassung Frankenstraße Tel: +49(40)33449-1142 Fax: +49(40)33449-1400 E-Mail: mailto:Patrik.Stellmann@gdv-dl.de
GDV Dienstleistungs-GmbH Glockengießerwall 1 D-20095 Hamburg www.gdv-dl.de
Niederlassungen:
Wilhelmstraße 43 / 43 G 10117 Berlin
Frankenstraße 18a 20097 Hamburg
Sitz und Registergericht: Hamburg HRB 145291 USt.-IdNr : DE 205183123
Geschäftsführer: Dr. Jens Bartenwerfer Fred di Giuseppe Chiachiarella
Aufsichtsratsvorsitzender: Werner Schmidt
------------------------------------------------------------------ Diese E-Mail und alle Anhänge enthalten vertrauliche und/oder rechtlich geschützte Informationen. Wenn Sie nicht der richtige Adressat sind oder diese E-Mail irrtümlich erhalten haben, informieren Sie bitte sofort den Absender und vernichten Sie diese E-Mail. Das unerlaubte Kopieren sowie die unbefugte Weitergabe der E-Mail ist nicht gestattet.
This e-mail and any attached files may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorised copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
-----Ursprüngliche Nachricht-----
Von: oXygen-user [mailto:oxygen-user-bounces@oxygenxml.com] Im Auftrag von Jean-Luc Chevillard Gesendet: Sonntag, 16. Juni 2019 21:23 An: oXygen-user@oxygenxml.com Betreff: [oXygen-user] How do I do a pipe-line in Oxygen?
Dear Oxygen suport and Oxygen experts,
can someone tell me how to make a pipeline in Oxygen?
Typically, I start from a file called File_A.xml to which I apply a script called Script_1.xslt the result being a file called File_B.xml to which I apply a script called Script_2.xslt the result being a file called File_C.xml to which I apply a script called Script_3.xslt the result being a file called ..................... ................... ........... ................ File_M.xml to which I apply a script called Script_m.xslt the result being a file called File_N.xml
Usually, when configuring the scenarios File_A.xml is associated with Script_1.xslt File_B.xml is associated with Script_2.xslt File_C.xml is associated with Script_3.xslt ...................... File_M.xml is associated with Script_m.xslt
Therefore what I do is:
press the Apply Transformation Scenario(s) BUTTON Wait press the Apply Transformation Scenario(s) BUTTON Wait press the Apply Transformation Scenario(s) BUTTON Wait ................... press the Apply Transformation Scenario(s) BUTTON Wait
However, I have not understood how to further simplify the process
If I select several scripts in the "configuring the scenarios" window they all apply to the same base file, which is not what I want
Is it possible? and IF YES what do I miss
Thanks in advance for any pointers
-- Jean-Luc Chevillard (in Paris)
https://univ-paris-diderot.academia.edu/JeanLucChevillard _______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
_______________________________________________ oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user
oXygen-user mailing list oXygen-user@oxygenxml.com https://www.oxygenxml.com/mailman/listinfo/oxygen-user