[sip-comm-dev] Eclipse build.xml


#1

Hi!

I'd like to change the following line in build.xml

    <!--REBUILD-->

    <target name="rebuild" depends="clean,make,-deploy-os-specific-bundles"

        description="Clean and make the project (including bundles).">

        <echo message="ver=${sip-communicator.version}"/>

        </target>

This


#2

Hi Thomas,

Sorry for lagging with the reply to this one.

(more inline)

Thomas Hofer wrote:

Hi!

I�d like to change the following line in build.xml

    <!--REBUILD-->

    <target name="rebuild" depends="clean,make*,-deploy-os-specific-bundles"
        description="Clean and make the project (including bundles).">
        <echo message="ver=${sip-communicator.version}"/>
    </target>

This

I am afraid that it might be trickier than that. The
-deploy-os-specific-bundles target copies all bundles specific to the OS
that we are currently running, into the sc-bundles directory where all
the other bundles are.

The reason why it is only called before "run" and "test" is that that's
when you know what operating system you are going to run on since you
are about to launch SIP Communicator.

This is not always the case with rebuild. Our nightly build machine for
example would rebuild the project and then create all the platform
specific installers. The installer generation scripts would copy all the
content inside the sc-bundles directory and would then prepare it for
deployment on whatever operating system it is supposed to deploy. In
most cases the destination OS (Windows, Mac, Fedora) would not match the
one that we are building on (Debian) and this could lead to conflicts
after the installation has completed.

Therefore, in order to fix the problem for Eclipse we'd have to deal
with it differently. One option would be to call the
-deploy-os-specific-bundles target directly from eclipse. Another
solution would be to create a new "ide-rebuild" target that would depend
on rebuild and deploy-os-bundles.

I am not familiar with Eclipse, so I don't know whether this would work,
but the cleanest solution would probably be to simply make it use the
"run" target when starting SIP Communicator. Is this possible at all?

WDYT?

Emil

···

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


#3

Hi! Answers inline.

Von: Emil Ivov [mailto:emcho@sip-communicator.org]
Gesendet: Freitag, 26. Oktober 2007 16:00
I am afraid that it might be trickier than that. The
-deploy-os-specific-bundles target copies all bundles specific to the
OS
that we are currently running, into the sc-bundles directory where all
the other bundles are.

The reason why it is only called before "run" and "test" is that that's
when you know what operating system you are going to run on since you
are about to launch SIP Communicator.

This is not always the case with rebuild. Our nightly build machine for
example would rebuild the project and then create all the platform
specific installers.

Oh, yes, that's a reason I forgot. You are right.

I am not familiar with Eclipse, so I don't know whether this would
work,
but the cleanest solution would probably be to simply make it use the
"run" target when starting SIP Communicator. Is this possible at all?

I'm not sure, but I think it is not possible. But the run-target starts the
VM, which is not good for debugging. Probably the best would be to edit the
documentation, that the -deploy.. target must be called once after
rebuilding, when not invoking the run-target. So everyone who is familiar
with eclipse can add the deploy-... target to the rebuild-target on the
build-dialog. And it does not interfere with the automatic build system.

WDYT?

Cheers, thomas

···

-----Ursprüngliche Nachricht-----

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


#4

Hi Thomas,

(inline)

Thomas Hofer wrote:

Hi! Answers inline.

-----Urspr�ngliche Nachricht-----
Von: Emil Ivov [mailto:emcho@sip-communicator.org]
Gesendet: Freitag, 26. Oktober 2007 16:00
I am afraid that it might be trickier than that. The
-deploy-os-specific-bundles target copies all bundles specific to the
OS
that we are currently running, into the sc-bundles directory where all
the other bundles are.

The reason why it is only called before "run" and "test" is that that's
when you know what operating system you are going to run on since you
are about to launch SIP Communicator.

This is not always the case with rebuild. Our nightly build machine for
example would rebuild the project and then create all the platform
specific installers.

Oh, yes, that's a reason I forgot. You are right.

I am not familiar with Eclipse, so I don't know whether this would
work,
but the cleanest solution would probably be to simply make it use the
"run" target when starting SIP Communicator. Is this possible at all?

I'm not sure, but I think it is not possible. But the run-target starts the
VM, which is not good for debugging. Probably the best would be to edit the
documentation, that the -deploy.. target must be called once after
rebuilding, when not invoking the run-target. So everyone who is familiar
with eclipse can add the deploy-... target to the rebuild-target on the
build-dialog. And it does not interfere with the automatic build system.

WDYT?

Agreed! I thought that it would probably be a good idea to add an IDE
build target but then decided against it since it would still require
users to go through the documentation in order to know that they should
use that target. So, yes, I agree that adding a tip in the doc is
probably the best way to go. Would you like to take care of this?

Emil

···

Cheers, thomas

---------------------------------------------------------------------
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


#5

Sure
thomas

···

-----Ursprüngliche Nachricht-----
Von: Emil Ivov [mailto:emcho@sip-communicator.org]
Gesendet: Montag, 29. Oktober 2007 13:00
An: dev@sip-communicator.dev.java.net
Betreff: Re: AW: [sip-comm-dev] Eclipse build.xml
So, yes, I agree that adding a tip in the doc is
probably the best way to go. Would you like to take care of this?

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


#6

Just edited the documentation.

Best Regards, Thomas

···

-----Ursprüngliche Nachricht-----
Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
Gesendet: Montag, 29. Oktober 2007 13:32
An: dev@sip-communicator.dev.java.net
Betreff: AW: AW: [sip-comm-dev] Eclipse build.xml

Sure
thomas

> -----Ursprüngliche Nachricht-----
> Von: Emil Ivov [mailto:emcho@sip-communicator.org]
> Gesendet: Montag, 29. Oktober 2007 13:00
> An: dev@sip-communicator.dev.java.net
> Betreff: Re: AW: [sip-comm-dev] Eclipse build.xml
> So, yes, I agree that adding a tip in the doc is
> probably the best way to go. Would you like to take care of this?

---------------------------------------------------------------------
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


#7

Thanks for taking care of this!

Thomas Hofer wrote:

···

Just edited the documentation.

Best Regards, Thomas

-----Urspr�ngliche Nachricht-----
Von: Thomas Hofer [mailto:mailinglisten@familie-hofer.net]
Gesendet: Montag, 29. Oktober 2007 13:32
An: dev@sip-communicator.dev.java.net
Betreff: AW: AW: [sip-comm-dev] Eclipse build.xml

Sure
thomas

-----Urspr�ngliche Nachricht-----
Von: Emil Ivov [mailto:emcho@sip-communicator.org]
Gesendet: Montag, 29. Oktober 2007 13:00
An: dev@sip-communicator.dev.java.net
Betreff: Re: AW: [sip-comm-dev] Eclipse build.xml
So, yes, I agree that adding a tip in the doc is
probably the best way to go. Would you like to take care of this?

---------------------------------------------------------------------
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

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