Skip to Content
0
Nov 06, 2012 at 02:57 PM

Java DC's public parts for otther DCs' dependencies

27 Views

Hello experts.

We have just come across the following trouble working within one development team.

One of us developed some Java Classes components, created public part (Compilations and one Assembly) and inserted necessary developed Java classes to there. Assigned necessary permissions. Then he checked in created activity. By the way developed component is available for other team members.

Another person syncs existing software componets, tries to use the created Java class component and he fails. Import of Java classes is impossible.

It turned out that created public parts are unavailable. He isn't able to define dependency properties for the public parts. Public parts are highlighted in red and they are unmanaged for other developers to set dependecies.

But if he creates project of the Java class component the public parts are available.

I suppose the public parts must be available withot creation of the project.

My question is that what we need to fix and pay attantion.

In general, how to implement public parts correctly? How to make them available for other developer to use as dependecies?

Could you please help us with your valuable pieces of advise?

Sincerely,

Anton