避免用代号One覆盖build.xml [英] Avoid overwriting of build.xml by Codename One

查看:52
本文介绍了避免用代号One覆盖build.xml的处理方法,对大家解决问题具有一定的参考价值,需要的朋友们下面随着小编来一起学习吧!

问题描述

这个问题的答案多个Codename一个CSS 效果很好(我更喜欢多个CSS,而不是无法管理的数千行单个CSS ...),但是它依赖于Codename One不会覆盖我手动编辑的 build.xml 。

The answer to the question Multiple Codename One CSS works fine (I prefer multiple CSSes than an unmanageable single CSS of thousands of lines...), but it relies on the fact that Codename One will not overwrite my manually edited build.xml.

如何完全避免Codename One覆盖该文件?我将其设置为只读,但是我不知道是否足够。

How can I avoid at all that Codename One will overwrite that file? I set it as read-only, but I don't know if it's enough.

此外,是否有充分的理由允许Codename One覆盖该文件? / p>

Moreover, is there any good reason to allow Codename One to overwrite that file?

推荐答案

当我们具有应该在此处表达的新功能时,此文件将被覆盖。新的构建目标等。

This file is overwritten when we have new features that should be expressed there e.g. new build targets etc.

在覆盖之前,我们会提示用户。因此,当您打开代号一个设置并保存时,会发生这种情况。您可以随时说不。我建议备份文件并进行相对简单的更改。

Before overwriting we prompt the user. So this would happen when you open Codename One Settings and save. You can always say "No". I suggest backing up the file and doing relatively simple changes.

我们打算做的另一项更改是剥离大部分内容的文件,类似于build.xml /。 netbeans中的build-impl.xml关系。这将使我们能够无缝更新impl XML文件,并允许您自定义XML文件。

One future change we intend to make is stripping the file of most of it's content similarly to the build.xml/build-impl.xml relation in netbeans. This will allow us to update the impl XML file seamlessly and allow you to customize the XML file.

这篇关于避免用代号One覆盖build.xml的文章就介绍到这了,希望我们推荐的答案对大家有所帮助,也希望大家多多支持IT屋!

查看全文
登录 关闭
扫码关注1秒登录
发送“验证码”获取 | 15天全站免登陆