StarTeam Plugins

Paul Coste <[email protected]>
Newsgroups gmane.comp.java.cruise-control.devel
Message-ID <[email protected]>
Hello,

I am a StarTeam expert of over 12 years, and an experienced Java developer,
and would like to propose some enhancements to your StarTeam plugin.  I am
not sure the best way to go about this, but I would appreciate the
opportunity to post code changes to the community.  The following is the
list of proposed changes:

1) Add the code ClientApplication.setName("CruiseControlPlugin
<version.number>") during initialization of the plugin.  This will cause
this string to be the client identifier in the StarTeam application log
file.  Otherwise the plugin shows as "Unknown Application."  This is very
important from a standardization and administration perspective when there
are many teams using StarTeam and we want to know who is using what kind of
plugin.  This is also important in StarTeam 2009 and above, in order to
conform with the new client connection control feature, which can block
logins based on client name, SDK version, etc.  (This particular function
call is supported all the way back to version 5.3, I believe, although I
don't know how far back you need to go anyway, since current support for
StarTeam only goes back to version 2006.)

2) I would like to address the documentation which states that the Jar file
is external and not freely available.  This was true until several months
ago; now the new company Micro Focus (which bought Borland) has released
StarTeam Express edition which is free to up to 10 users, and for which the
SDK Jar file is included fully functional.  This may actually put the
StarTeam plugin back into the standard library of plugins distributed as
binary, since the SourceForge team will be able to compile the library.

3) The documentation states that the StarTeam plugin is based on the
command-line interface.  If this is true, the newest command-line interface
now supports encrypted (i.e. obfuscated) external password files, which is a
preferred way to operate, so that developers do not store clear text
passwords in their build scripts or properties files, allowing these files
to be safely stored in source control without compromising security.  I
would like to add this as a new feature.

Please let me know how I can contribute.  For my company I plan on making
custom modifications, for item #1 and #3, but these should be included as a
general enhancement to the community if possible.

Thank You,
Paul Coste

------------------------------------------------------------------------------
Download new Adobe(R) Flash(R) Builder(TM) 4
The new Adobe(R) Flex(R) 4 and Flash(R) Builder(TM) 4 (formerly 
Flex(R) Builder(TM)) enable the development of rich applications that run
across multiple browsers and platforms. Download your free trials today!
http://p.sf.net/sfu/adobe-dev2dev

_______________________________________________
Cruisecontrol-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/cruisecontrol-devel
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.