Hi Stefan,
About this remark:
Usually the XPR is modified when you "publish" something. The reason
is that oXygen always associates a file with a transformation. This
leads to a change in the scenarioAssociation element of the XPR file.
I think this is a very useless feature in oXygen projects.
I agree, by default we should not have saved the association directly in
the XPR, but this can be controlled.
In the Oxygen Preferences->"Project Level Settings" page you have a
checkbox named "Allow transformation scenario associations to be saved
at project level" which you can uncheck and then commit the XPR which
will get modified because of this change.
About this other remark:
It would help to have a setting which disables the file association
completely for DITA projects.
You mean transformation scenario association, right?
Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 5/6/22 11:54, Stefan Eike wrote:
Hi,
we usually stash the XPR to ignore it. After a while we delete the
stashes. This is not nice, but probably the best work around. Usually
the XPR is modified when you "publish" something. The reason is that
oXygen always associates a file with a transformation. This leads to a
change in the scenarioAssociation element of the XPR file. I think
this is a very useless feature in oXygen projects.
As an idea for the oXygen development team: It would help to have a
setting which disables the file association completely for DITA projects.
BR
Oxygen XML Editor Support (Radu Coravu) <supp...@oxygenxml.com> hat
am 06.05.2022 08:58 geschrieben:
Hi Franz-Josef,
Can you make a list of setting changes which usually seem to make the
xpr file volatile?
In the Oxygen Preferences->"Project Level Settings" you have various
checkboxes which can be unchecked and then the xpr file can be pushed
to the Git repo and it should become less volatile to change when for
example someone associates a transformation scenario to an XML document.
About handling this, probably end users should avoid committing the
XPR, revert it from time to time if they see if it has local changes.
Regards,
Radu
Radu Coravu
Oxygen XML Editor
On 5/6/22 09:18, Franz-Josef Knelangen wrote:
Hi there,
recently we went form SVG to Git. We don’t want to commit the XPR
every time but we also want to have project settings for the team.
How do you handle this?
- Don’t push the XPR?
- Put the XPR in the stash and let it stay there until a project
setting is changed, push the change and back to stash again?
Any suggestions greatly appreciated.
Greetings
Franz-Josef
*AKG Software Consulting GmbH
Franz-Josef Knelangen*
Uhlandstraße 12
79423 Heitersheim
Germany
Tel.: +49 (0)7634 5612-611
Fax: +49 (0)7634 5612-300
E-Mail: _fjk@akgsoftware.de_
Internet: www.akgsoftware.de <http://www.akgsoftware.de>
Geschäftsführer: Dipl.-Ing. Artur K. Günther, Dipl.-Ing. Arno
Brüggemann, Dipl.-Ing. (FH) Bernhard Feser, Dipl.-Ing. Jens Günther
Sitz der Gesellschaft: Heitersheim, HRB 310383 (Amtsgericht Freiburg)
_______________________________________________
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
*Stefan Eike Consulting*
Philipp-Manz-Straße 54
48268 Greven
*Mail*: stefan-eike-consult...@mailbox.org
*Phone* : +49 163 7431585
*Web*: stefaneike.com <https://www.stefaneike.com>
_______________________________________________
oXygen-user mailing list
oXygen-user@oxygenxml.com
https://www.oxygenxml.com/mailman/listinfo/oxygen-user
