nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Changes to java classes in TS not checked in SVN

manishrathi

TS732, WS2008

------------------------

In our organization, SVN is code repository and any changes to java classes are checked in SVN.

If I am making any changes to java classes in TeamSite for workflow development, do these changes need to be checked in to SVN ? OR chenges to java classes in TeamSIte are staying withing TS only and not in SVN ?

A consultant made changes to TS classes and never checked them in SVN. Is this practice allowed ? I am sure that consultant may not have missed existing procedures. So I am wondering changes made to java classes in TS can be checked in repository or not.

Thanks

Find more posts tagged with

Comments

Rick Poulin

I'm not sure what you're asking here. We obviously can't comment on the rules and practices of your organization. Generally speaking, the best practice is to version every single customization you make to your server post-install, so that you can reproduce them in a disaster recovery situation. For me, this usually means that code gets versioned in SVN (or other tool), and environment-specific config gets documented in a Word doc. Each organization has its own view of that, because it depends on what you're doing and how you're used to doing it.

PS. If by "TS classes" you mean someone is overwriting com.interwoven.* classes with their own, that's a huge no-no for support purposes and should be avoided at all costs, even if that means finding less pleasant workarounds.

manishrathi

Thanks.

I am not very familiar with java classes in TS and may be working with customization of these classes. So you mean to say, I can use these java interfaces only to develop new java classes, but DO NOT make any changes to existing vendor provided classes.

nipper

This are political questions rather than technical questions.

You need a well documented procedure for code changes.

Everybody does things differently. I like to keep code whereever you what, but the code is pushed into a branch in TS and then built in the TS branch, where the JAR is checked in. The JAR then can be pushed down to the iw-home and the UI rebuild is quick and, most important it always works.

Rick has his way, which while they are Canadian, they are still valid, though with a funny accent. :-)

nipper

> So you mean to say, I can use these java interfaces only to develop new java classes, but

> DO NOT make any changes to existing vendor provided classes.

This is a general Java best practice rather than specific to TeamSite development.