Hi
all
I
checked this out and
made a small documentation at http://wiki.eclipse.org/How_to_use_Eclipse_copyright_tool
Greetings
Allan
Hmmm, it has worked for us in the past. Not sure
what
is going on for you. Perhaps posting to the releng forum would get
some
hints.
Jeff
Thomas Menzel wrote:
hi,
thx
jeff fort he hint.
I
found the tool @ http://wiki.eclipse.org/Eclipse_copyright_tool
and
I have the
command in the context menu but for some reason it doesn’t do squat…
…
using eclipse
3.3 and the respective tool version from CVS.
Kind
regards
Thomas Menzel
brox IT-Solutions GmbH
there exists a "copyright tool"
in the Eclipse project releng tooling. I don't remember all the
details
but like a search for copyright tool or something on the wiki or a
question on
the platform-releng mailing list would help.
Jeff
Thomas Menzel wrote:
hi fellow-suffers,
i guess i state the obvious
that no one is
really excited about the task to add the EPL header to ALL source files.
and I wonder if we can automate
it with a
tool that either exists or we may write on our own.
before we dive into this: I
wonder if it is
worth it.
hence the question: how far
along are u
with this task and do u think it is worth to invest the time.
I see two main functions for
this tool that
should work for the most common source files, e.g. .java, .properties,
.xml
(and other xml docs such as .xsd)
check if
the header is present and correct
if not: flag/report the file
add EPL headers
to files. this would need to be parameterized to some extend, e.g. the
initial
contributor.
for b) I at least see
continuous need to
avoid having to do this manually all the time even after initial
contribution.
I would also do a fairly simple
implementation,
such as a
normalize
target EPL header to A
normalize
file to be checked to B
text
search A in B
normalize would mean: strip out
all non
alpha-numeric chars including whitespace.
so, what is ur idea on the
subject?
PS: the eclipse plugin javadoc
can also
generate the file headers, if none are present.
but this
only for java files (AFAIK)
and wont
correct any present header either
Kind
regards
Thomas Menzel
brox IT-Solutions GmbH
_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev
_______________________________________________
smila-dev mailing list
smila-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/smila-dev