| [smila-dev] tool for EPL sourceheaders |
|
I posted the copyright tool question over on the releng list and got
some interesting responses. You might be interested to read this and
any subsequent interactions... Jeff I'm not sure what particular issues Walter was referring to but it may be useful to note that there are actually two copyright actions: Update Copyright and Advanced Update Copyright. The later was contributed by a team (I think from IBM) that did not want to use the EPL for all it's source files. There is a preference page that can be used to specify the default legal template to be used. It may also be of interest that the action was modified recently to allow pluggable repository support. The tool as delivered by the Platform still only supports CVS but it would be possible for SVN support to be added. Michael P.S. I know it is odd to have two commands but I suspect this occurred to ensure that the behavior of the original command used by Eclipse committers was not compromised by the changes to add a bug template.
Good to know. It would be great to find and address these issues. If you (anyone) find ways of improving the tool, please open an enhancement request and supply a patch if you can. Jeff Walter Harley wrote: Any non-IBM Eclipse developers should browse Bugzilla for copyright tool bugs before using it. There are some pitfalls to be aware of, or at least there were the last time I tried. It is still usable, but its default settings are IBM-specific rather than Eclipse-generic, and some of its UI does not do what might be expected. -walter From: platform-releng-dev-bounces@xxxxxxxxxxx [mailto:platform-releng-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer Sent: Tuesday, September 30, 2008 8:00 AM To: Eclipse platform release engineering list. Subject: [platform-releng-dev] [Fwd: AW: [smila-dev] tool for EPL sourceheaders] Forwarded from the SMILA list. It might be worthwhile linking this into some releng doc pages somewhere. Jeff Hi all I checked this out and made a small documentation at http://wiki.eclipse.org/How_to_use_Eclipse_copyright_tool Greetings Allan Von: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] Im Auftrag von Jeff McAffer Gesendet: Montag, 29. September 2008 15:35 An: Smila project developer mailing list Betreff: Re: [smila-dev] tool for EPL source headers 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 From: smila-dev-bounces@xxxxxxxxxxx [mailto:smila-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff McAffer Sent: Samstag, 27. September 2008 17:05 To: Smila project developer mailing list Subject: Re: [smila-dev] tool for EPL source headers 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 _______________________________________________ platform-releng-dev mailing list platform-releng-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/platform-releng-dev _______________________________________________ platform-releng-dev mailing list platform-releng-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/platform-releng-dev |