Generate GUI into Java source build problems (EAP 5594)

Avatar
Permanently deleted user
创建于

The combination of using a version control system (perforce in my case) and
using the option to generate the GUI into java source does is unworkable for
teams. When other developers refresh their code from version control, and
they get updated GUI parts (form files and java files containing the class
bound to the form) they get build errors resulting from the fact that the
java file is read-only.

This occurs regardless of the fact that the form and java files are already
consistent and up-to-date. If they go through the laborious process of
making each bound java file writeable, the build will succeed, but no actual
changes are ever made to the contents of the files proving that no
alteration were necessary in the first place.

I believe your algorithm to decide when to process form files to update the
generated parts of the java source is too aggressive.

Rob


Votes

0

分享

2 条评论
Avatar
Permanently deleted user
创建于

Hello Rob,

RK> The combination of using a version control system (perforce in my
RK> case) and using the option to generate the GUI into java source does
RK> is unworkable for teams. When other developers refresh their code
RK> from version control, and they get updated GUI parts (form files and
RK> java files containing the class bound to the form) they get build
RK> errors resulting from the fact that the java file is read-only.
RK>
RK> This occurs regardless of the fact that the form and java files are
RK> already consistent and up-to-date. If they go through the laborious
RK> process of making each bound java file writeable, the build will
RK> succeed, but no actual changes are ever made to the contents of the
RK> files proving that no alteration were necessary in the first place.
RK>
RK> I believe your algorithm to decide when to process form files to
RK> update the generated parts of the java source is too aggressive.

This is indeed a bug: IDEA should not try to update the source if the generated
code is not different from the actual contents of the file. Could you please
file a JIRA issue for this problem?

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"


0
Avatar
Permanently deleted user
创建于

Bug IDEA-9268 filed. Thanks.

Rob

"Dmitry Jemerov" <yole@jetbrains.com> wrote in message
news:c8a8949df6e748c898fd079d87af@news.jetbrains.com...

Hello Rob,

>

RK> The combination of using a version control system (perforce in my
RK> case) and using the option to generate the GUI into java source does
RK> is unworkable for teams. When other developers refresh their code
RK> from version control, and they get updated GUI parts (form files and
RK> java files containing the class bound to the form) they get build
RK> errors resulting from the fact that the java file is read-only.
RK> RK> This occurs regardless of the fact that the form and java files
are
RK> already consistent and up-to-date. If they go through the laborious
RK> process of making each bound java file writeable, the build will
RK> succeed, but no actual changes are ever made to the contents of the
RK> files proving that no alteration were necessary in the first place.
RK> RK> I believe your algorithm to decide when to process form files to
RK> update the generated parts of the java source is too aggressive.

>

This is indeed a bug: IDEA should not try to update the source if the
generated code is not different from the actual contents of the file.
Could you please file a JIRA issue for this problem?

>

--
Dmitry Jemerov
Software Developer
http://www.jetbrains.com/
"Develop with Pleasure!"

>



0

请先登录再写评论。