[sip-comm-dev] bcprov-jdk14-140.jar?


#1

Guys,

The file bcprov-jdk14-140.jar is located in lib. But the classpaths of
Eclipse and NetBeans are set up to look either for it or an earlier
version of it in lib\installer-exclude and at least Eclipse fails with
a compile-time error because of its lack in the latter location.
However, I don't see it referenced elsewhere. Is the file necessary?
If yes, where is it supposed to be?

Thank you,
Lubo

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#2

Hi Lubomir,

The file bcprov-jdk14-140.jar is located in lib. But the classpaths of
Eclipse and NetBeans are set up to look either for it or an earlier
version of it in lib\installer-exclude and at least Eclipse fails with
a compile-time error because of its lack in the latter location.

Yes, I actually moved it from lib/installer-exclude to lib/ yesterday, as it is needed for ZRTP.
I've now updated it and changed its name to bcprovider.jar, which will ease the update of the lib.
May I let you change the eclipse & netbeans path accordingly?

However, I don't see it referenced elsewhere. Is the file necessary?
If yes, where is it supposed to be?

The MAC build actually includes "lib/*.jar" so bcprovider.jar is actually automatically included in the package and the classpath. I forgot to advertise it but I'll send another mail to tell the packe mainteners that they should take it into account for their builds.

Cheers,
romain

···

On 2008/10/07, at 14:41, Lubomir Marinov wrote:

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#3

Romain,

Thank you for the explanation!

May I let you change the eclipse & netbeans path accordingly?

Sure.

Regards,
Lubo

···

On Tue, Oct 7, 2008 at 3:56 PM, Romain KUNTZ <kuntz@lsiit.u-strasbg.fr> wrote:

Hi Lubomir,

On 2008/10/07, at 14:41, Lubomir Marinov wrote:

The file bcprov-jdk14-140.jar is located in lib. But the classpaths of
Eclipse and NetBeans are set up to look either for it or an earlier
version of it in lib\installer-exclude and at least Eclipse fails with
a compile-time error because of its lack in the latter location.

Yes, I actually moved it from lib/installer-exclude to lib/ yesterday, as it
is needed for ZRTP.
I've now updated it and changed its name to bcprovider.jar, which will ease
the update of the lib.
May I let you change the eclipse & netbeans path accordingly?

However, I don't see it referenced elsewhere. Is the file necessary?
If yes, where is it supposed to be?

The MAC build actually includes "lib/*.jar" so bcprovider.jar is actually
automatically included in the package and the classpath. I forgot to
advertise it but I'll send another mail to tell the packe mainteners that
they should take it into account for their builds.

Cheers,
romain

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#4

Lubomir Marinov wrote:

May I let you change the eclipse & netbeans path accordingly?

I have just picked up and installed the new netbeans classpath for lib/bcprov.jar. That fixes a lot of the ide compilation errors for bouncy castle imports.

However, there are LOADS of failures associated with "import gnu.java.zrtp.*". I've added lib/installer-exclude/zrtp4j-0.9.0.jar to the netbeans classpath - it probably needs to be put onto the eclipse classpath too.

There were also errors associated with "import net.sf.profiler4j.console.*", so I have added lib/installer-exclude/profiler4j-1.0-beta3-SC.jar" to project.xml. Is it needed for eclipse too?

PLEASE, PLEASE, would ALL developers make sure that if they need to add a new jar (or rename one) to the build compile classpath, TELL those of use who care about the IDE environments what you have done and ask us to change the sample project files! (What happened today with bcprov.jar is a good example of doing the "right thing").

Thanks in anticipation...

Brian

p.s. Emil... is the project close to stability now, or is this going to be a recurring problem. It seems to me to be so counter-productive that we need to give some careful thought to improving infrastructure stability. An elegant solution would be great, but we haven't really got close to one in our discussions. Perhaps you need to introduce some manual controls and standards?

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#5

Hi Brian,

About profiler4j, it should be ok for eclipse. Sorry for forgetting to do
this for netbean.

Ben

···

2008/10/7 Brian Burch <brian@pingtoo.com>

Lubomir Marinov wrote:

May I let you change the eclipse & netbeans path accordingly?

I have just picked up and installed the new netbeans classpath for
lib/bcprov.jar. That fixes a lot of the ide compilation errors for bouncy
castle imports.

However, there are LOADS of failures associated with "import
gnu.java.zrtp.*". I've added lib/installer-exclude/zrtp4j-0.9.0.jar to the
netbeans classpath - it probably needs to be put onto the eclipse classpath
too.

There were also errors associated with "import
net.sf.profiler4j.console.*", so I have added
lib/installer-exclude/profiler4j-1.0-beta3-SC.jar" to project.xml. Is it
needed for eclipse too?

PLEASE, PLEASE, would ALL developers make sure that if they need to add a
new jar (or rename one) to the build compile classpath, TELL those of use
who care about the IDE environments what you have done and ask us to change
the sample project files! (What happened today with bcprov.jar is a good
example of doing the "right thing").

Thanks in anticipation...

Brian

p.s. Emil... is the project close to stability now, or is this going to be
a recurring problem. It seems to me to be so counter-productive that we need
to give some careful thought to improving infrastructure stability. An
elegant solution would be great, but we haven't really got close to one in
our discussions. Perhaps you need to introduce some manual controls and
standards?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#6

If you use netbeans, please read this carefully. If not, please ignore (unless you are complaining that I've broken something!)

I have just committed a new version of build.xml that NO LONGER contains the netbeans-specific debug-single ant target. I think that is an improvement because this target could never be run outside the netbeans IDE. However, I've added a new <path> definition that ensures the netbeans debugger can find the service lick jars and honour breakpoints set in the corresponding source files.

I have also committed a new file to hold the "debug-single-file-in-test" target. This target is now wired into the new version of the netbeans project.xml file.

I will update the wiki soon, but here is how to use my change...

1. svn update (of course)

2. close the netbeans sip-communicator project (never mess around with nb project files while a project is open!)

3. do a file system copy of project.xml, ide-targets.xml and ide-file-targets.xml from xxx/ide/nbproject/ to xxx/nbproject/

4. open the sc project under netbeans.

5. set some breakpoints (double-click a source line) in one of the slicks... I tested with GibberishProtocolProviderServiceLick.start(), TestAccountInstallation.testInstallAccount() and TestAccountInstallation.tearDown()

6. expand the Projects hierarchy until you can select the source file called test/net.java.sip.communicator.slick.protocol.provider.GibberishProtocolProviderServiceLick.java

7. right-click the selected source file and choose the "Debug File" action. Netbeans will start felix under the debugger, instructing it to start the selected service lick. You should hit the start() breakpoint and step through the process of adding the service licks to the junit test suite. When you click "continue", felix and junit will run each of the test classes. Your breakpoints within the test class should be triggered.

note: my step 7 test blew with an NPE in TestUninstallAccount when calling MclStorageManager.createProtoContactGroupNode. If no-one fixes it soon, I will investigate whether there is a subtle setup problem in my new debug target.

Have fun!

Brian

···

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net


#7

Hello Brian,

I'm really sorry for the burden. As I don't use neither eclipse nor netbeans, I've completely forgotten to update their classpath or to advertise those new libraries on the ML. I've added a note in the developer documentation (http://www.sip-communicator.org/index.php/Documentation/CommittingCode) in the "After Commiting Code" section.

I'll be more careful next time.

Cheers,
romain

···

On 2008/10/07, at 19:15, Brian Burch wrote:

Lubomir Marinov wrote:

May I let you change the eclipse & netbeans path accordingly?

I have just picked up and installed the new netbeans classpath for lib/bcprov.jar. That fixes a lot of the ide compilation errors for bouncy castle imports.

However, there are LOADS of failures associated with "import gnu.java.zrtp.*". I've added lib/installer-exclude/zrtp4j-0.9.0.jar to the netbeans classpath - it probably needs to be put onto the eclipse classpath too.

There were also errors associated with "import net.sf.profiler4j.console.*", so I have added lib/installer-exclude/profiler4j-1.0-beta3-SC.jar" to project.xml. Is it needed for eclipse too?

PLEASE, PLEASE, would ALL developers make sure that if they need to add a new jar (or rename one) to the build compile classpath, TELL those of use who care about the IDE environments what you have done and ask us to change the sample project files! (What happened today with bcprov.jar is a good example of doing the "right thing").

Thanks in anticipation...

Brian

p.s. Emil... is the project close to stability now, or is this going to be a recurring problem. It seems to me to be so counter-productive that we need to give some careful thought to improving infrastructure stability. An elegant solution would be great, but we haven't really got close to one in our discussions. Perhaps you need to introduce some manual controls and standards?

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@sip-communicator.dev.java.net
For additional commands, e-mail: dev-help@sip-communicator.dev.java.net