Unable to use SVN 1.3 after upgrading to oXygen8.1
Having trouble installing Oxygen? Got a bug to report? Post it all here.
-
- Posts: 7
- Joined: Thu Jun 01, 2006 11:38 pm
Unable to use SVN 1.3 after upgrading to oXygen8.1
Post by deannelson »
Hello
I just upgraded to oXygen 8.1 from 8.0. I am using SuSE 10.1 which comes with an SVN 1.3 client. All of the development source code that I am working in is handled by the stock SVN client.
When I am doing documentation with oXygen, I will point the oXygen SVN client to the start of the doc tree and do updates from the oxygen SVN client.
The problem is when the whole development (including the documentation) tree starts out using 1.3 and then I declare a working copy of the docs, oxygen SVN marks all of the existing docs as 1.4 and the stock SVN client(1.3) is not able to do any updates after that.
Is there a way to use the SVN client in a 1.3 compatible way? Otherwise I cannot use it, if it takes over the tree.
Dean Nelson
I just upgraded to oXygen 8.1 from 8.0. I am using SuSE 10.1 which comes with an SVN 1.3 client. All of the development source code that I am working in is handled by the stock SVN client.
When I am doing documentation with oXygen, I will point the oXygen SVN client to the start of the doc tree and do updates from the oxygen SVN client.
The problem is when the whole development (including the documentation) tree starts out using 1.3 and then I declare a working copy of the docs, oxygen SVN marks all of the existing docs as 1.4 and the stock SVN client(1.3) is not able to do any updates after that.
Is there a way to use the SVN client in a 1.3 compatible way? Otherwise I cannot use it, if it takes over the tree.
Dean Nelson
-
- Posts: 388
- Joined: Thu Jul 01, 2004 12:29 pm
Hello,
Thank you for your feedback. In the current development stream we implemented a fix for this problem, the old working copies are no longer updated automatically. This fix will be available in the next release version.
Please contact us at support at oxygenxml dot com to give you a workaround.
Best Regards,
Octavian
Thank you for your feedback. In the current development stream we implemented a fix for this problem, the old working copies are no longer updated automatically. This fix will be available in the next release version.
Please contact us at support at oxygenxml dot com to give you a workaround.
Best Regards,
Octavian
Jump to
- Oxygen XML Editor/Author/Developer
- ↳ Feature Request
- ↳ Common Problems
- ↳ DITA (Editing and Publishing DITA Content)
- ↳ SDK-API, Frameworks - Document Types
- ↳ DocBook
- ↳ TEI
- ↳ XHTML
- ↳ Other Issues
- Oxygen XML Web Author
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Content Fusion
- ↳ Feature Request
- ↳ Common Problems
- Oxygen JSON Editor
- ↳ Feature Request
- ↳ Common Problems
- Oxygen PDF Chemistry
- ↳ Feature Request
- ↳ Common Problems
- Oxygen Feedback
- ↳ Feature Request
- ↳ Common Problems
- Oxygen XML WebHelp
- ↳ Feature Request
- ↳ Common Problems
- XML
- ↳ General XML Questions
- ↳ XSLT and FOP
- ↳ XML Schemas
- ↳ XQuery
- NVDL
- ↳ General NVDL Issues
- ↳ oNVDL Related Issues
- XML Services Market
- ↳ Offer a Service