| Compare packages [message #129912] |
Fri, 26 December 2003 14:42  |
Eclipse User |
|
|
|
Originally posted by: wk5657.henleykidd.ns01.us
I have some generated code.
My technique for keeping it up to date is the following:
1). I generate the code into a separate project.
2). I compare the packages by selecting the package in both projects and
running "Compare with --> each other"
3). I move differences into the target environment and then cvs commit
the changes
There are a couple of problems with this approach. Some serious and
some not so serious:
1). Before generating into the separate project, I delete the package
from the separate project. If the real target project is open, the
package is also deleted from there. This is annoying, but not so
serious since I can get it back from cvs or close the project before the
delete.
2). When I compare the packages with each other, the .class files find
their way into the compare list. This is also annoying and I would like
to have them not appear. This is not so serious.
3). When I compare the packages with each other, the .java files ALL
appear in the compare list. This is true even if there are no
structural differences. This is my most serious issue since I am only
interested in the files that have structural differences (I want to
selectively merge the changes from the new generation into the target
project). This is important so that I have a valid set of diffs to see
the progression of these generated class definitions. I do not want a
wholesale replacement of the package of generated classes.
Are there settings that I am missing or have I selected the wrong
technique for keeping this subset of my work up to date?
Thanks in advance.
Wayne
|
|
|
| Re: Compare packages [message #130168 is a reply to message #129912] |
Sun, 28 December 2003 08:39  |
| Eclipse User |
|
|
|
Originally posted by: Andre_Weinand.oti.com
On 26.12.2003 20:42 Uhr, in article bsi2cq$cn4$1@eclipse.org, "G. Wayne
Kidd" <wk5657@henleykidd.ns01.us> wrote:
> I have some generated code.
>
> My technique for keeping it up to date is the following:
>
> 1). I generate the code into a separate project.
> 2). I compare the packages by selecting the package in both projects and
> running "Compare with --> each other"
> 3). I move differences into the target environment and then cvs commit
> the changes
>
>
> There are a couple of problems with this approach. Some serious and
> some not so serious:
>
> 1). Before generating into the separate project, I delete the package
> from the separate project. If the real target project is open, the
> package is also deleted from there. This is annoying, but not so
> serious since I can get it back from cvs or close the project before the
> delete.
>
> 2). When I compare the packages with each other, the .class files find
> their way into the compare list. This is also annoying and I would like
> to have them not appear. This is not so serious.
>
> 3). When I compare the packages with each other, the .java files ALL
> appear in the compare list. This is true even if there are no
> structural differences. This is my most serious issue since I am only
> interested in the files that have structural differences (I want to
> selectively merge the changes from the new generation into the target
> project). This is important so that I have a valid set of diffs to see
> the progression of these generated class definitions. I do not want a
> wholesale replacement of the package of generated classes.
>
> Are there settings that I am missing or have I selected the wrong
> technique for keeping this subset of my work up to date?
>
> Thanks in advance.
>
> Wayne
>
Please file a feature request for 3).
2) has already been addressed. Compare filters are already in HEAD and will
be in M7.
--andre
|
|
|
Powered by
FUDForum. Page generated in 0.03933 seconds
Home