import-able build.xml

I'm working on setting up a project template for myself and
others as
described by email in msg 1357 "GSoC/plugin project
templates"  (in
the archives at
https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).

Basically the idea is to have a subproject in a folder next
to
sip-communicator under the same parent directory. The
subproject's
build.xml will import sip-communicator's build.xml,
redefining
(overloading?) necessary targets to build the subproject's
new code
and modified versions of sip-communicator code when
necessary. In this
way the subproject author can keep the sip-communicator code
up to
date while working on his/her own code and avoid merge-hell
at project
end.

Anyway, I've finished the first step in this process, which
is to
change some of the syntax in sip-communicator's build.xml to
make it
import-able. The problem with the current file is that
references to
source directories were not written in a way that they stay
consistent
after the file is imported.

Take my own project as an example. I've got two
directories:

/home/ryan/code/sip/sip-communicator   --> this is
sip-communicator from CVS
/home/ryan/code/sip/sc-avmailbox         --> this is my
own project

/home/ryan/code/sip/sc-avmailbox/build.xml imports
/home/ryan/code/sip/sip-communicator/build.xml , redefining
necessary targets.

However, a reference to src/some/file location in the
build.xml will
end up resolving to
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
/home/ryan/code/sip/sip-communicator/src/some/file/location
after the
file is imported.

I've fixed all such references as per the relevant ant
documentation
at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll down to
"resolving files against the imported file"

As of right now I'm not done with the rest of the tricks
necessary to
make the subproject build as intended, but I'm sending this
patch now
because (1) it shouldn't change anything if run from the
sip-communicator directory, (2) submitting it now allows
more time for
everyone to make sure I didn't mess something up, and (3)
this way as
people add targets to build.xml they can use the correct
syntax to
keep the build.xml importable.

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Maybe I jumped the gun a little on that one, as I've already
found a
few lines that I messed up in the build.xml.

Consider my last message a status report with a general
example of how
I am modifying build.xml ;)

On 6/13/07, Ryan Ricard <evilhecubusgmail.com> wrote:
> I'm working on setting up a project template for myself
and others as
> described by email in msg 1357 "GSoC/plugin
project templates"  (in
> the archives at
> https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).
>
> Basically the idea is to have a subproject in a folder
next to
> sip-communicator under the same parent directory. The
subproject's
> build.xml will import sip-communicator's build.xml,
redefining
> (overloading?) necessary targets to build the
subproject's new code
> and modified versions of sip-communicator code when
necessary. In this
> way the subproject author can keep the sip-communicator
code up to
> date while working on his/her own code and avoid
merge-hell at project
> end.
>
> Anyway, I've finished the first step in this process,
which is to
> change some of the syntax in sip-communicator's
build.xml to make it
> import-able. The problem with the current file is that
references to
> source directories were not written in a way that they
stay consistent
> after the file is imported.
>
> Take my own project as an example. I've got two
directories:
>
> /home/ryan/code/sip/sip-communicator   --> this is
sip-communicator from CVS
> /home/ryan/code/sip/sc-avmailbox         --> this is
my own project
>
> /home/ryan/code/sip/sc-avmailbox/build.xml imports
> /home/ryan/code/sip/sip-communicator/build.xml ,
redefining necessary targets.
>
> However, a reference to src/some/file location in the
build.xml will
> end up resolving to
> /home/ryan/code/sip/sc-avmailbox/src/some/file/location
 instead of
>
/home/ryan/code/sip/sip-communicator/src/some/file/location
after the
> file is imported.
>
> I've fixed all such references as per the relevant ant
documentation
> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll down to
> "resolving files against the imported file"
>
> As of right now I'm not done with the rest of the
tricks necessary to
> make the subproject build as intended, but I'm sending
this patch now
> because (1) it shouldn't change anything if run from
the
> sip-communicator directory, (2) submitting it now
allows more time for
> everyone to make sure I didn't mess something up, and
(3) this way as
> people add targets to build.xml they can use the
correct syntax to
> keep the build.xml importable.
>
>


-- 
My life has no purpose...my life has no direction...no
aim...no
meaning... and yet I'm happy... I can't figure it out...
What am I
doing right?

Charles Schultz

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

alright, lets try this again.

Attached is a working patch.

Here's a test strategy:

1. set up a new directory 'test' to hold sip-communicator
and my subproject.
2. do a new checkout of sip communicator into
'test/sip-communicator'
3. do a new checkout of sc-avmailbox
(https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
'test/sc-avmailbox'
4. either
 a) apply the attached patch to
test/sip-communicator/build.xml
-OR-
 b) copy test/sc-avmailbox/build.xml.sip-communicator to
test/sip-communicator/build.xml
5. navigate to test/sip-communicator and do an 'ant rebuild
run.' Sip
Communicator should build as normal
6. navigate to test/sc-avmailbox and do an 'ant rebuild
run.' Sip
Communicator should be built with the sc-avmailbox code. My
mailbox
plugin should be built and run (NOTE: my mailbox plugin
doesn't work
as intended yet. This is just to show that it will be built
and run)


On 6/13/07, Ryan Ricard <ryan.ricardstudent.utdallas.edu> wrote:
> Maybe I jumped the gun a little on that one, as I've
already found a
> few lines that I messed up in the build.xml.
>
> Consider my last message a status report with a general
example of how
> I am modifying build.xml ;)
>
> On 6/13/07, Ryan Ricard <evilhecubusgmail.com> wrote:
> > I'm working on setting up a project template for
myself and others as
> > described by email in msg 1357 "GSoC/plugin
project templates"  (in
> > the archives at
> > https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).
> >
> > Basically the idea is to have a subproject in a
folder next to
> > sip-communicator under the same parent directory.
The subproject's
> > build.xml will import sip-communicator's
build.xml, redefining
> > (overloading?) necessary targets to build the
subproject's new code
> > and modified versions of sip-communicator code
when necessary. In this
> > way the subproject author can keep the
sip-communicator code up to
> > date while working on his/her own code and avoid
merge-hell at project
> > end.
> >
> > Anyway, I've finished the first step in this
process, which is to
> > change some of the syntax in sip-communicator's
build.xml to make it
> > import-able. The problem with the current file is
that references to
> > source directories were not written in a way that
they stay consistent
> > after the file is imported.
> >
> > Take my own project as an example. I've got two
directories:
> >
> > /home/ryan/code/sip/sip-communicator   --> this
is sip-communicator from CVS
> > /home/ryan/code/sip/sc-avmailbox         -->
this is my own project
> >
> > /home/ryan/code/sip/sc-avmailbox/build.xml
imports
> > /home/ryan/code/sip/sip-communicator/build.xml ,
redefining necessary targets.
> >
> > However, a reference to src/some/file location in
the build.xml will
> > end up resolving to
> >
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
> >
/home/ryan/code/sip/sip-communicator/src/some/file/location
after the
> > file is imported.
> >
> > I've fixed all such references as per the relevant
ant documentation
> > at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll down to
> > "resolving files against the imported
file"
> >
> > As of right now I'm not done with the rest of the
tricks necessary to
> > make the subproject build as intended, but I'm
sending this patch now
> > because (1) it shouldn't change anything if run
from the
> > sip-communicator directory, (2) submitting it now
allows more time for
> > everyone to make sure I didn't mess something up,
and (3) this way as
> > people add targets to build.xml they can use the
correct syntax to
> > keep the build.xml importable.
> >
> >
>
>
> --
> My life has no purpose...my life has no direction...no
aim...no
> meaning... and yet I'm happy... I can't figure it
out... What am I
> doing right?
>
> Charles Schultz
>


-- 
My life has no purpose...my life has no direction...no
aim...no
meaning... and yet I'm happy... I can't figure it out...
What am I
doing right?

Charles Schultz

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hello Ryan,

Nice work!

I've just applied, tested, committed and ack-ed your patch.

I remember I had tried once before to use absolute path so
that things 
would work from outside the sip-communicator directory. Back
at the time 
I broke the DMG builds.

I hope this won't be the case this time since your patch
seems to be 
more complete than mine was but just the same, Romain, let
me know if 
the Mac builds fail and we'll find a solution.

Thanks for the contrib, Ryan!

Cheers
Emil

Ryan Ricard wrote:
> alright, lets try this again.
> 
> Attached is a working patch.
> 
> Here's a test strategy:
> 
> 1. set up a new directory 'test' to hold
sip-communicator and my subproject.
> 2. do a new checkout of sip communicator into
'test/sip-communicator'
> 3. do a new checkout of sc-avmailbox
> (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
> 'test/sc-avmailbox'
> 4. either
>  a) apply the attached patch to
test/sip-communicator/build.xml
> -OR-
>  b) copy test/sc-avmailbox/build.xml.sip-communicator
to
> test/sip-communicator/build.xml
> 5. navigate to test/sip-communicator and do an 'ant
rebuild run.' Sip
> Communicator should build as normal
> 6. navigate to test/sc-avmailbox and do an 'ant rebuild
run.' Sip
> Communicator should be built with the sc-avmailbox
code. My mailbox
> plugin should be built and run (NOTE: my mailbox plugin
doesn't work
> as intended yet. This is just to show that it will be
built and run)
> 
> 
> On 6/13/07, Ryan Ricard <ryan.ricardstudent.utdallas.edu> wrote:
>> Maybe I jumped the gun a little on that one, as
I've already found a
>> few lines that I messed up in the build.xml.
>>
>> Consider my last message a status report with a
general example of how
>> I am modifying build.xml ;)
>>
>> On 6/13/07, Ryan Ricard <evilhecubusgmail.com> wrote:
>>> I'm working on setting up a project template
for myself and others as
>>> described by email in msg 1357
"GSoC/plugin project templates"  (in
>>> the archives at
>>> https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).
>>>
>>> Basically the idea is to have a subproject in a
folder next to
>>> sip-communicator under the same parent
directory. The subproject's
>>> build.xml will import sip-communicator's
build.xml, redefining
>>> (overloading?) necessary targets to build the
subproject's new code
>>> and modified versions of sip-communicator code
when necessary. In this
>>> way the subproject author can keep the
sip-communicator code up to
>>> date while working on his/her own code and
avoid merge-hell at project
>>> end.
>>>
>>> Anyway, I've finished the first step in this
process, which is to
>>> change some of the syntax in sip-communicator's
build.xml to make it
>>> import-able. The problem with the current file
is that references to
>>> source directories were not written in a way
that they stay consistent
>>> after the file is imported.
>>>
>>> Take my own project as an example. I've got two
directories:
>>>
>>> /home/ryan/code/sip/sip-communicator   -->
this is sip-communicator from CVS
>>> /home/ryan/code/sip/sc-avmailbox         -->
this is my own project
>>>
>>> /home/ryan/code/sip/sc-avmailbox/build.xml
imports
>>> /home/ryan/code/sip/sip-communicator/build.xml
, redefining necessary targets.
>>>
>>> However, a reference to src/some/file location
in the build.xml will
>>> end up resolving to
>>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
>>>
/home/ryan/code/sip/sip-communicator/src/some/file/location
after the
>>> file is imported.
>>>
>>> I've fixed all such references as per the
relevant ant documentation
>>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll down to
>>> "resolving files against the imported
file"
>>>
>>> As of right now I'm not done with the rest of
the tricks necessary to
>>> make the subproject build as intended, but I'm
sending this patch now
>>> because (1) it shouldn't change anything if run
from the
>>> sip-communicator directory, (2) submitting it
now allows more time for
>>> everyone to make sure I didn't mess something
up, and (3) this way as
>>> people add targets to build.xml they can use
the correct syntax to
>>> keep the build.xml importable.
>>>
>>>
>>
>> --
>> My life has no purpose...my life has no
direction...no aim...no
>> meaning... and yet I'm happy... I can't figure it
out... What am I
>> doing right?
>>
>> Charles Schultz
>>
> 
> 
> 
>
------------------------------------------------------------
------------
> 
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Thanks Emil,

I also didn't have a chance to test Windows builds, but I
suppose that
any errors in those would show up rather quickly.

On 6/17/07, Emil Ivov <emchoemcho.com> wrote:
> Hello Ryan,
>
> Nice work!
>
> I've just applied, tested, committed and ack-ed your
patch.
>
> I remember I had tried once before to use absolute path
so that things
> would work from outside the sip-communicator directory.
Back at the time
> I broke the DMG builds.
>
> I hope this won't be the case this time since your
patch seems to be
> more complete than mine was but just the same, Romain,
let me know if
> the Mac builds fail and we'll find a solution.
>
> Thanks for the contrib, Ryan!
>
> Cheers
> Emil
>
> Ryan Ricard wrote:
> > alright, lets try this again.
> >
> > Attached is a working patch.
> >
> > Here's a test strategy:
> >
> > 1. set up a new directory 'test' to hold
sip-communicator and my subproject.
> > 2. do a new checkout of sip communicator into
'test/sip-communicator'
> > 3. do a new checkout of sc-avmailbox
> > (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
> > 'test/sc-avmailbox'
> > 4. either
> >  a) apply the attached patch to
test/sip-communicator/build.xml
> > -OR-
> >  b) copy
test/sc-avmailbox/build.xml.sip-communicator to
> > test/sip-communicator/build.xml
> > 5. navigate to test/sip-communicator and do an
'ant rebuild run.' Sip
> > Communicator should build as normal
> > 6. navigate to test/sc-avmailbox and do an 'ant
rebuild run.' Sip
> > Communicator should be built with the sc-avmailbox
code. My mailbox
> > plugin should be built and run (NOTE: my mailbox
plugin doesn't work
> > as intended yet. This is just to show that it will
be built and run)
> >
> >
> > On 6/13/07, Ryan Ricard <ryan.ricardstudent.utdallas.edu> wrote:
> >> Maybe I jumped the gun a little on that one,
as I've already found a
> >> few lines that I messed up in the build.xml.
> >>
> >> Consider my last message a status report with
a general example of how
> >> I am modifying build.xml ;)
> >>
> >> On 6/13/07, Ryan Ricard <evilhecubusgmail.com> wrote:
> >>> I'm working on setting up a project
template for myself and others as
> >>> described by email in msg 1357
"GSoC/plugin project templates"  (in
> >>> the archives at
> >>> https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).
> >>>
> >>> Basically the idea is to have a subproject
in a folder next to
> >>> sip-communicator under the same parent
directory. The subproject's
> >>> build.xml will import sip-communicator's
build.xml, redefining
> >>> (overloading?) necessary targets to build
the subproject's new code
> >>> and modified versions of sip-communicator
code when necessary. In this
> >>> way the subproject author can keep the
sip-communicator code up to
> >>> date while working on his/her own code and
avoid merge-hell at project
> >>> end.
> >>>
> >>> Anyway, I've finished the first step in
this process, which is to
> >>> change some of the syntax in
sip-communicator's build.xml to make it
> >>> import-able. The problem with the current
file is that references to
> >>> source directories were not written in a
way that they stay consistent
> >>> after the file is imported.
> >>>
> >>> Take my own project as an example. I've
got two directories:
> >>>
> >>> /home/ryan/code/sip/sip-communicator  
--> this is sip-communicator from CVS
> >>> /home/ryan/code/sip/sc-avmailbox        
--> this is my own project
> >>>
> >>> /home/ryan/code/sip/sc-avmailbox/build.xml
imports
> >>>
/home/ryan/code/sip/sip-communicator/build.xml , redefining
necessary targets.
> >>>
> >>> However, a reference to src/some/file
location in the build.xml will
> >>> end up resolving to
> >>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
> >>>
/home/ryan/code/sip/sip-communicator/src/some/file/location
after the
> >>> file is imported.
> >>>
> >>> I've fixed all such references as per the
relevant ant documentation
> >>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll down to
> >>> "resolving files against the imported
file"
> >>>
> >>> As of right now I'm not done with the rest
of the tricks necessary to
> >>> make the subproject build as intended, but
I'm sending this patch now
> >>> because (1) it shouldn't change anything
if run from the
> >>> sip-communicator directory, (2) submitting
it now allows more time for
> >>> everyone to make sure I didn't mess
something up, and (3) this way as
> >>> people add targets to build.xml they can
use the correct syntax to
> >>> keep the build.xml importable.
> >>>
> >>>
> >>
> >> --
> >> My life has no purpose...my life has no
direction...no aim...no
> >> meaning... and yet I'm happy... I can't figure
it out... What am I
> >> doing right?
> >>
> >> Charles Schultz
> >>
> >
> >
> >
> >
------------------------------------------------------------
------------
> >
> >
------------------------------------------------------------
---------
> > To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> > For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>


-- 
Ryan Ricard
evilhecubusgmail.com
ryan.ricardstudent.utdallas.edu

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Emil, Ryan,

We use JarBundler to create MacOSX packages, and it does not
work  
with absolute paths: the specific command to include jars
only takes  
1 argument that points both to the source and destination of
the jar  
files.

So I have changed the build.xml in the macosx build section
to  
replace the variables with the correct static path.

Cheers,
romain

On 2007/06/18, at 3:54, Emil Ivov wrote:

> Hello Ryan,
>
> Nice work!
>
> I've just applied, tested, committed and ack-ed your
patch.
>
> I remember I had tried once before to use absolute path
so that  
> things would work from outside the sip-communicator
directory. Back  
> at the time I broke the DMG builds.
>
> I hope this won't be the case this time since your
patch seems to  
> be more complete than mine was but just the same,
Romain, let me  
> know if the Mac builds fail and we'll find a solution.
>
> Thanks for the contrib, Ryan!
>
> Cheers
> Emil
>
> Ryan Ricard wrote:
>> alright, lets try this again.
>> Attached is a working patch.
>> Here's a test strategy:
>> 1. set up a new directory 'test' to hold
sip-communicator and my  
>> subproject.
>> 2. do a new checkout of sip communicator into
'test/sip-communicator'
>> 3. do a new checkout of sc-avmailbox
>> (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
>> 'test/sc-avmailbox'
>> 4. either
>>  a) apply the attached patch to
test/sip-communicator/build.xml
>> -OR-
>>  b) copy
test/sc-avmailbox/build.xml.sip-communicator to
>> test/sip-communicator/build.xml
>> 5. navigate to test/sip-communicator and do an 'ant
rebuild run.' Sip
>> Communicator should build as normal
>> 6. navigate to test/sc-avmailbox and do an 'ant
rebuild run.' Sip
>> Communicator should be built with the sc-avmailbox
code. My mailbox
>> plugin should be built and run (NOTE: my mailbox
plugin doesn't work
>> as intended yet. This is just to show that it will
be built and run)
>> On 6/13/07, Ryan Ricard <ryan.ricardstudent.utdallas.edu> wrote:
>>> Maybe I jumped the gun a little on that one, as
I've already found a
>>> few lines that I messed up in the build.xml.
>>>
>>> Consider my last message a status report with a
general example  
>>> of how
>>> I am modifying build.xml ;)
>>>
>>> On 6/13/07, Ryan Ricard <evilhecubusgmail.com> wrote:
>>>> I'm working on setting up a project
template for myself and  
>>>> others as
>>>> described by email in msg 1357
"GSoC/plugin project templates"  (in
>>>> the archives at
>>>> https://sip-communicator.dev.java.net/servlets/ReadMsg? 
>>>> list=dev&msgNo=1357).
>>>>
>>>> Basically the idea is to have a subproject
in a folder next to
>>>> sip-communicator under the same parent
directory. The subproject's
>>>> build.xml will import sip-communicator's
build.xml, redefining
>>>> (overloading?) necessary targets to build
the subproject's new code
>>>> and modified versions of sip-communicator
code when necessary.  
>>>> In this
>>>> way the subproject author can keep the
sip-communicator code up to
>>>> date while working on his/her own code and
avoid merge-hell at  
>>>> project
>>>> end.
>>>>
>>>> Anyway, I've finished the first step in
this process, which is to
>>>> change some of the syntax in
sip-communicator's build.xml to  
>>>> make it
>>>> import-able. The problem with the current
file is that  
>>>> references to
>>>> source directories were not written in a
way that they stay  
>>>> consistent
>>>> after the file is imported.
>>>>
>>>> Take my own project as an example. I've got
two directories:
>>>>
>>>> /home/ryan/code/sip/sip-communicator  
--> this is sip- 
>>>> communicator from CVS
>>>> /home/ryan/code/sip/sc-avmailbox        
--> this is my own project
>>>>
>>>> /home/ryan/code/sip/sc-avmailbox/build.xml
imports
>>>>
/home/ryan/code/sip/sip-communicator/build.xml , redefining 

>>>> necessary targets.
>>>>
>>>> However, a reference to src/some/file
location in the build.xml  
>>>> will
>>>> end up resolving to
>>>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
>>>>
/home/ryan/code/sip/sip-communicator/src/some/file/location 

>>>> after the
>>>> file is imported.
>>>>
>>>> I've fixed all such references as per the
relevant ant  
>>>> documentation
>>>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll  
>>>> down to
>>>> "resolving files against the imported
file"
>>>>
>>>> As of right now I'm not done with the rest
of the tricks  
>>>> necessary to
>>>> make the subproject build as intended, but
I'm sending this  
>>>> patch now
>>>> because (1) it shouldn't change anything if
run from the
>>>> sip-communicator directory, (2) submitting
it now allows more  
>>>> time for
>>>> everyone to make sure I didn't mess
something up, and (3) this  
>>>> way as
>>>> people add targets to build.xml they can
use the correct syntax to
>>>> keep the build.xml importable.
>>>>
>>>>
>>>
>>> --
>>> My life has no purpose...my life has no
direction...no aim...no
>>> meaning... and yet I'm happy... I can't figure
it out... What am I
>>> doing right?
>>>
>>> Charles Schultz
>>>
>>
------------------------------------------------------------
--------- 
>> ---
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip- 
>> communicator.dev.java.net
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip- 
> communicator.dev.java.net
>

-- 
Romain KUNTZ
kuntzlsiit.u-strasbg.fr
Louis Pasteur University - Networks and Protocols Team


------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Oh,

This was actually my fault. Ryan had not modified your
target in his 
original patch.

Thanks for taking care of it.

Emil

Romain KUNTZ wrote:
> Hi Emil, Ryan,
> 
> We use JarBundler to create MacOSX packages, and it
does not work  
> with absolute paths: the specific command to include
jars only takes  
> 1 argument that points both to the source and
destination of the jar  
> files.
> 
> So I have changed the build.xml in the macosx build
section to  
> replace the variables with the correct static path.
> 
> Cheers,
> romain
> 
> On 2007/06/18, at 3:54, Emil Ivov wrote:
> 
>> Hello Ryan,
>>
>> Nice work!
>>
>> I've just applied, tested, committed and ack-ed
your patch.
>>
>> I remember I had tried once before to use absolute
path so that  
>> things would work from outside the sip-communicator
directory. Back  
>> at the time I broke the DMG builds.
>>
>> I hope this won't be the case this time since your
patch seems to  
>> be more complete than mine was but just the same,
Romain, let me  
>> know if the Mac builds fail and we'll find a
solution.
>>
>> Thanks for the contrib, Ryan!
>>
>> Cheers
>> Emil
>>
>> Ryan Ricard wrote:
>>> alright, lets try this again.
>>> Attached is a working patch.
>>> Here's a test strategy:
>>> 1. set up a new directory 'test' to hold
sip-communicator and my  
>>> subproject.
>>> 2. do a new checkout of sip communicator into
'test/sip-communicator'
>>> 3. do a new checkout of sc-avmailbox
>>> (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
>>> 'test/sc-avmailbox'
>>> 4. either
>>>  a) apply the attached patch to
test/sip-communicator/build.xml
>>> -OR-
>>>  b) copy
test/sc-avmailbox/build.xml.sip-communicator to
>>> test/sip-communicator/build.xml
>>> 5. navigate to test/sip-communicator and do an
'ant rebuild run.' Sip
>>> Communicator should build as normal
>>> 6. navigate to test/sc-avmailbox and do an 'ant
rebuild run.' Sip
>>> Communicator should be built with the
sc-avmailbox code. My mailbox
>>> plugin should be built and run (NOTE: my
mailbox plugin doesn't work
>>> as intended yet. This is just to show that it
will be built and run)
>>> On 6/13/07, Ryan Ricard <ryan.ricardstudent.utdallas.edu> wrote:
>>>> Maybe I jumped the gun a little on that
one, as I've already found a
>>>> few lines that I messed up in the
build.xml.
>>>>
>>>> Consider my last message a status report
with a general example  
>>>> of how
>>>> I am modifying build.xml ;)
>>>>
>>>> On 6/13/07, Ryan Ricard <evilhecubusgmail.com> wrote:
>>>>> I'm working on setting up a project
template for myself and  
>>>>> others as
>>>>> described by email in msg 1357
"GSoC/plugin project templates"  (in
>>>>> the archives at
>>>>> https://sip-communicator.dev.java.net/servlets/ReadMsg? 
>>>>> list=dev&msgNo=1357).
>>>>>
>>>>> Basically the idea is to have a
subproject in a folder next to
>>>>> sip-communicator under the same parent
directory. The subproject's
>>>>> build.xml will import
sip-communicator's build.xml, redefining
>>>>> (overloading?) necessary targets to
build the subproject's new code
>>>>> and modified versions of
sip-communicator code when necessary.  
>>>>> In this
>>>>> way the subproject author can keep the
sip-communicator code up to
>>>>> date while working on his/her own code
and avoid merge-hell at  
>>>>> project
>>>>> end.
>>>>>
>>>>> Anyway, I've finished the first step in
this process, which is to
>>>>> change some of the syntax in
sip-communicator's build.xml to  
>>>>> make it
>>>>> import-able. The problem with the
current file is that  
>>>>> references to
>>>>> source directories were not written in
a way that they stay  
>>>>> consistent
>>>>> after the file is imported.
>>>>>
>>>>> Take my own project as an example. I've
got two directories:
>>>>>
>>>>> /home/ryan/code/sip/sip-communicator  
--> this is sip- 
>>>>> communicator from CVS
>>>>> /home/ryan/code/sip/sc-avmailbox       
 --> this is my own project
>>>>>
>>>>>
/home/ryan/code/sip/sc-avmailbox/build.xml imports
>>>>>
/home/ryan/code/sip/sip-communicator/build.xml , redefining 

>>>>> necessary targets.
>>>>>
>>>>> However, a reference to src/some/file
location in the build.xml  
>>>>> will
>>>>> end up resolving to
>>>>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
>>>>>
/home/ryan/code/sip/sip-communicator/src/some/file/location 

>>>>> after the
>>>>> file is imported.
>>>>>
>>>>> I've fixed all such references as per
the relevant ant  
>>>>> documentation
>>>>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll  
>>>>> down to
>>>>> "resolving files against the
imported file"
>>>>>
>>>>> As of right now I'm not done with the
rest of the tricks  
>>>>> necessary to
>>>>> make the subproject build as intended,
but I'm sending this  
>>>>> patch now
>>>>> because (1) it shouldn't change
anything if run from the
>>>>> sip-communicator directory, (2)
submitting it now allows more  
>>>>> time for
>>>>> everyone to make sure I didn't mess
something up, and (3) this  
>>>>> way as
>>>>> people add targets to build.xml they
can use the correct syntax to
>>>>> keep the build.xml importable.
>>>>>
>>>>>
>>>> --
>>>> My life has no purpose...my life has no
direction...no aim...no
>>>> meaning... and yet I'm happy... I can't
figure it out... What am I
>>>> doing right?
>>>>
>>>> Charles Schultz
>>>>
>>>
------------------------------------------------------------
--------- 
>>> ---
>>>
------------------------------------------------------------
---------
>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>> For additional commands, e-mail: dev-helpsip- 
>>> communicator.dev.java.net
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip- 
>> communicator.dev.java.net
>>
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi,

I've just fixed the windows, generic and linux installers.
I had to replace all ${sc.basedir}/${inst.resrc} with
${inst.resrc}.
Works for me will see does it works for cruisecontrol 

damencho

Ryan Ricard wrote:
> Thanks Emil,
>
> I also didn't have a chance to test Windows builds, but
I suppose that
> any errors in those would show up rather quickly.
>
> On 6/17/07, Emil Ivov <emchoemcho.com> wrote:
>> Hello Ryan,
>>
>> Nice work!
>>
>> I've just applied, tested, committed and ack-ed
your patch.
>>
>> I remember I had tried once before to use absolute
path so that things
>> would work from outside the sip-communicator
directory. Back at the time
>> I broke the DMG builds.
>>
>> I hope this won't be the case this time since your
patch seems to be
>> more complete than mine was but just the same,
Romain, let me know if
>> the Mac builds fail and we'll find a solution.
>>
>> Thanks for the contrib, Ryan!
>>
>> Cheers
>> Emil
>>
>> Ryan Ricard wrote:
>> > alright, lets try this again.
>> >
>> > Attached is a working patch.
>> >
>> > Here's a test strategy:
>> >
>> > 1. set up a new directory 'test' to hold
sip-communicator and my 
>> subproject.
>> > 2. do a new checkout of sip communicator into
'test/sip-communicator'
>> > 3. do a new checkout of sc-avmailbox
>> > (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
>> > 'test/sc-avmailbox'
>> > 4. either
>> >  a) apply the attached patch to
test/sip-communicator/build.xml
>> > -OR-
>> >  b) copy
test/sc-avmailbox/build.xml.sip-communicator to
>> > test/sip-communicator/build.xml
>> > 5. navigate to test/sip-communicator and do an
'ant rebuild run.' Sip
>> > Communicator should build as normal
>> > 6. navigate to test/sc-avmailbox and do an
'ant rebuild run.' Sip
>> > Communicator should be built with the
sc-avmailbox code. My mailbox
>> > plugin should be built and run (NOTE: my
mailbox plugin doesn't work
>> > as intended yet. This is just to show that it
will be built and run)
>> >
>> >
>> > On 6/13/07, Ryan Ricard <ryan.ricardstudent.utdallas.edu> wrote:
>> >> Maybe I jumped the gun a little on that
one, as I've already found a
>> >> few lines that I messed up in the
build.xml.
>> >>
>> >> Consider my last message a status report
with a general example of 
>> how
>> >> I am modifying build.xml ;)
>> >>
>> >> On 6/13/07, Ryan Ricard
<evilhecubusgmail.com> wrote:
>> >>> I'm working on setting up a project
template for myself and 
>> others as
>> >>> described by email in msg 1357
"GSoC/plugin project templates"  (in
>> >>> the archives at
>> >>> 
>> https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357). 
>>
>> >>>
>> >>> Basically the idea is to have a
subproject in a folder next to
>> >>> sip-communicator under the same parent
directory. The subproject's
>> >>> build.xml will import
sip-communicator's build.xml, redefining
>> >>> (overloading?) necessary targets to
build the subproject's new code
>> >>> and modified versions of
sip-communicator code when necessary. In 
>> this
>> >>> way the subproject author can keep the
sip-communicator code up to
>> >>> date while working on his/her own code
and avoid merge-hell at 
>> project
>> >>> end.
>> >>>
>> >>> Anyway, I've finished the first step
in this process, which is to
>> >>> change some of the syntax in
sip-communicator's build.xml to make it
>> >>> import-able. The problem with the
current file is that references to
>> >>> source directories were not written in
a way that they stay 
>> consistent
>> >>> after the file is imported.
>> >>>
>> >>> Take my own project as an example.
I've got two directories:
>> >>>
>> >>> /home/ryan/code/sip/sip-communicator  
--> this is 
>> sip-communicator from CVS
>> >>> /home/ryan/code/sip/sc-avmailbox      
  --> this is my own project
>> >>>
>> >>>
/home/ryan/code/sip/sc-avmailbox/build.xml imports
>> >>>
/home/ryan/code/sip/sip-communicator/build.xml , redefining

>> necessary targets.
>> >>>
>> >>> However, a reference to src/some/file
location in the build.xml will
>> >>> end up resolving to
>> >>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
>> >>>
/home/ryan/code/sip/sip-communicator/src/some/file/location
after 
>> the
>> >>> file is imported.
>> >>>
>> >>> I've fixed all such references as per
the relevant ant documentation
>> >>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll 
>> down to
>> >>> "resolving files against the
imported file"
>> >>>
>> >>> As of right now I'm not done with the
rest of the tricks 
>> necessary to
>> >>> make the subproject build as intended,
but I'm sending this patch 
>> now
>> >>> because (1) it shouldn't change
anything if run from the
>> >>> sip-communicator directory, (2)
submitting it now allows more 
>> time for
>> >>> everyone to make sure I didn't mess
something up, and (3) this 
>> way as
>> >>> people add targets to build.xml they
can use the correct syntax to
>> >>> keep the build.xml importable.
>> >>>
>> >>>
>> >>
>> >> --
>> >> My life has no purpose...my life has no
direction...no aim...no
>> >> meaning... and yet I'm happy... I can't
figure it out... What am I
>> >> doing right?
>> >>
>> >> Charles Schultz
>> >>
>> >
>> >
>> >
>> > 
>>
------------------------------------------------------------
------------
>> >
>> >
------------------------------------------------------------
---------
>> > To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> > For additional commands, e-mail: 
>> dev-helpsip-communicator.dev.java.net
>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
>
>

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

The build.xml that's currently in cvs is broken. It looks
like someone
did a "cvs diff build.xml > build.xml" instead
of "cvs diff build.xml
| patch build.xml" or something like that.



On 6/18/07, Damian Minkov <damenchodamencho.com> wrote:
> Hi,
>
> I've just fixed the windows, generic and linux
installers.
> I had to replace all ${sc.basedir}/${inst.resrc} with
${inst.resrc}.
> Works for me will see does it works for cruisecontrol

>
> damencho
>
> Ryan Ricard wrote:
> > Thanks Emil,
> >
> > I also didn't have a chance to test Windows
builds, but I suppose that
> > any errors in those would show up rather quickly.
> >
> > On 6/17/07, Emil Ivov <emchoemcho.com> wrote:
> >> Hello Ryan,
> >>
> >> Nice work!
> >>
> >> I've just applied, tested, committed and
ack-ed your patch.
> >>
> >> I remember I had tried once before to use
absolute path so that things
> >> would work from outside the sip-communicator
directory. Back at the time
> >> I broke the DMG builds.
> >>
> >> I hope this won't be the case this time since
your patch seems to be
> >> more complete than mine was but just the same,
Romain, let me know if
> >> the Mac builds fail and we'll find a
solution.
> >>
> >> Thanks for the contrib, Ryan!
> >>
> >> Cheers
> >> Emil
> >>
> >> Ryan Ricard wrote:
> >> > alright, lets try this again.
> >> >
> >> > Attached is a working patch.
> >> >
> >> > Here's a test strategy:
> >> >
> >> > 1. set up a new directory 'test' to hold
sip-communicator and my
> >> subproject.
> >> > 2. do a new checkout of sip communicator
into 'test/sip-communicator'
> >> > 3. do a new checkout of sc-avmailbox
> >> > (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
> >> > 'test/sc-avmailbox'
> >> > 4. either
> >> >  a) apply the attached patch to
test/sip-communicator/build.xml
> >> > -OR-
> >> >  b) copy
test/sc-avmailbox/build.xml.sip-communicator to
> >> > test/sip-communicator/build.xml
> >> > 5. navigate to test/sip-communicator and
do an 'ant rebuild run.' Sip
> >> > Communicator should build as normal
> >> > 6. navigate to test/sc-avmailbox and do
an 'ant rebuild run.' Sip
> >> > Communicator should be built with the
sc-avmailbox code. My mailbox
> >> > plugin should be built and run (NOTE: my
mailbox plugin doesn't work
> >> > as intended yet. This is just to show
that it will be built and run)
> >> >
> >> >
> >> > On 6/13/07, Ryan Ricard
<ryan.ricardstudent.utdallas.edu> wrote:
> >> >> Maybe I jumped the gun a little on
that one, as I've already found a
> >> >> few lines that I messed up in the
build.xml.
> >> >>
> >> >> Consider my last message a status
report with a general example of
> >> how
> >> >> I am modifying build.xml ;)
> >> >>
> >> >> On 6/13/07, Ryan Ricard
<evilhecubusgmail.com> wrote:
> >> >>> I'm working on setting up a
project template for myself and
> >> others as
> >> >>> described by email in msg 1357
"GSoC/plugin project templates"  (in
> >> >>> the archives at
> >> >>>
> >> https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).
> >>
> >> >>>
> >> >>> Basically the idea is to have a
subproject in a folder next to
> >> >>> sip-communicator under the same
parent directory. The subproject's
> >> >>> build.xml will import
sip-communicator's build.xml, redefining
> >> >>> (overloading?) necessary targets
to build the subproject's new code
> >> >>> and modified versions of
sip-communicator code when necessary. In
> >> this
> >> >>> way the subproject author can
keep the sip-communicator code up to
> >> >>> date while working on his/her own
code and avoid merge-hell at
> >> project
> >> >>> end.
> >> >>>
> >> >>> Anyway, I've finished the first
step in this process, which is to
> >> >>> change some of the syntax in
sip-communicator's build.xml to make it
> >> >>> import-able. The problem with the
current file is that references to
> >> >>> source directories were not
written in a way that they stay
> >> consistent
> >> >>> after the file is imported.
> >> >>>
> >> >>> Take my own project as an
example. I've got two directories:
> >> >>>
> >> >>>
/home/ryan/code/sip/sip-communicator   --> this is
> >> sip-communicator from CVS
> >> >>> /home/ryan/code/sip/sc-avmailbox 
       --> this is my own project
> >> >>>
> >> >>>
/home/ryan/code/sip/sc-avmailbox/build.xml imports
> >> >>>
/home/ryan/code/sip/sip-communicator/build.xml , redefining
> >> necessary targets.
> >> >>>
> >> >>> However, a reference to
src/some/file location in the build.xml will
> >> >>> end up resolving to
> >> >>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
> >> >>>
/home/ryan/code/sip/sip-communicator/src/some/file/location
after
> >> the
> >> >>> file is imported.
> >> >>>
> >> >>> I've fixed all such references as
per the relevant ant documentation
> >> >>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll
> >> down to
> >> >>> "resolving files against the
imported file"
> >> >>>
> >> >>> As of right now I'm not done with
the rest of the tricks
> >> necessary to
> >> >>> make the subproject build as
intended, but I'm sending this patch
> >> now
> >> >>> because (1) it shouldn't change
anything if run from the
> >> >>> sip-communicator directory, (2)
submitting it now allows more
> >> time for
> >> >>> everyone to make sure I didn't
mess something up, and (3) this
> >> way as
> >> >>> people add targets to build.xml
they can use the correct syntax to
> >> >>> keep the build.xml importable.
> >> >>>
> >> >>>
> >> >>
> >> >> --
> >> >> My life has no purpose...my life has
no direction...no aim...no
> >> >> meaning... and yet I'm happy... I
can't figure it out... What am I
> >> >> doing right?
> >> >>
> >> >> Charles Schultz
> >> >>
> >> >
> >> >
> >> >
> >> >
> >>
------------------------------------------------------------
------------
> >> >
> >> >
------------------------------------------------------------
---------
> >> > To unsubscribe, e-mail:
dev-unsubscribesip-communicator.dev.java.net
> >> > For additional commands, e-mail:
> >> dev-helpsip-communicator.dev.java.net
> >>
> >>
------------------------------------------------------------
---------
> >> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> >> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
> >>
> >>
> >
> >
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>
>


-- 
Ryan Ricard
evilhecubusgmail.com
ryan.ricardstudent.utdallas.edu

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net

Hi Ryan,

I don't see a problem with the version on cvs:

https://sip-communicato
r.dev.java.net/source/browse/*checkout*/sip-communicator/bui
ld.xml

And the last CruiseControl build was successful:

https://sip-commu
nicator.dev.java.net/servlets/BrowseList?listName=cruisecont
rol&by=date&from=2007-06-01&to=2007-06-30&fi
rst=1&count=70

Could it be that your last update has introduced conflicts
in your local 
copy?

Emil


Ryan Ricard wrote:
> The build.xml that's currently in cvs is broken. It
looks like someone
> did a "cvs diff build.xml > build.xml"
instead of "cvs diff build.xml
> | patch build.xml" or something like that.
> 
> 
> 
> On 6/18/07, Damian Minkov <damenchodamencho.com> wrote:
>> Hi,
>>
>> I've just fixed the windows, generic and linux
installers.
>> I had to replace all ${sc.basedir}/${inst.resrc}
with ${inst.resrc}.
>> Works for me will see does it works for
cruisecontrol 
>>
>> damencho
>>
>> Ryan Ricard wrote:
>>> Thanks Emil,
>>>
>>> I also didn't have a chance to test Windows
builds, but I suppose that
>>> any errors in those would show up rather
quickly.
>>>
>>> On 6/17/07, Emil Ivov <emchoemcho.com> wrote:
>>>> Hello Ryan,
>>>>
>>>> Nice work!
>>>>
>>>> I've just applied, tested, committed and
ack-ed your patch.
>>>>
>>>> I remember I had tried once before to use
absolute path so that things
>>>> would work from outside the
sip-communicator directory. Back at the time
>>>> I broke the DMG builds.
>>>>
>>>> I hope this won't be the case this time
since your patch seems to be
>>>> more complete than mine was but just the
same, Romain, let me know if
>>>> the Mac builds fail and we'll find a
solution.
>>>>
>>>> Thanks for the contrib, Ryan!
>>>>
>>>> Cheers
>>>> Emil
>>>>
>>>> Ryan Ricard wrote:
>>>>> alright, lets try this again.
>>>>>
>>>>> Attached is a working patch.
>>>>>
>>>>> Here's a test strategy:
>>>>>
>>>>> 1. set up a new directory 'test' to
hold sip-communicator and my
>>>> subproject.
>>>>> 2. do a new checkout of sip
communicator into 'test/sip-communicator'
>>>>> 3. do a new checkout of sc-avmailbox
>>>>> (https://sc-avmailbox.dev.java.net/source/browse/sc-
avmailbox/) into
>>>>> 'test/sc-avmailbox'
>>>>> 4. either
>>>>>  a) apply the attached patch to
test/sip-communicator/build.xml
>>>>> -OR-
>>>>>  b) copy
test/sc-avmailbox/build.xml.sip-communicator to
>>>>> test/sip-communicator/build.xml
>>>>> 5. navigate to test/sip-communicator
and do an 'ant rebuild run.' Sip
>>>>> Communicator should build as normal
>>>>> 6. navigate to test/sc-avmailbox and do
an 'ant rebuild run.' Sip
>>>>> Communicator should be built with the
sc-avmailbox code. My mailbox
>>>>> plugin should be built and run (NOTE:
my mailbox plugin doesn't work
>>>>> as intended yet. This is just to show
that it will be built and run)
>>>>>
>>>>>
>>>>> On 6/13/07, Ryan Ricard
<ryan.ricardstudent.utdallas.edu> wrote:
>>>>>> Maybe I jumped the gun a little on
that one, as I've already found a
>>>>>> few lines that I messed up in the
build.xml.
>>>>>>
>>>>>> Consider my last message a status
report with a general example of
>>>> how
>>>>>> I am modifying build.xml ;)
>>>>>>
>>>>>> On 6/13/07, Ryan Ricard
<evilhecubusgmail.com> wrote:
>>>>>>> I'm working on setting up a
project template for myself and
>>>> others as
>>>>>>> described by email in msg 1357
"GSoC/plugin project templates"  (in
>>>>>>> the archives at
>>>>>>>
>>>> https://sip-communicator.dev.java.
net/servlets/ReadMsg?list=dev&msgNo=1357).
>>>>
>>>>>>> Basically the idea is to have a
subproject in a folder next to
>>>>>>> sip-communicator under the same
parent directory. The subproject's
>>>>>>> build.xml will import
sip-communicator's build.xml, redefining
>>>>>>> (overloading?) necessary
targets to build the subproject's new code
>>>>>>> and modified versions of
sip-communicator code when necessary. In
>>>> this
>>>>>>> way the subproject author can
keep the sip-communicator code up to
>>>>>>> date while working on his/her
own code and avoid merge-hell at
>>>> project
>>>>>>> end.
>>>>>>>
>>>>>>> Anyway, I've finished the first
step in this process, which is to
>>>>>>> change some of the syntax in
sip-communicator's build.xml to make it
>>>>>>> import-able. The problem with
the current file is that references to
>>>>>>> source directories were not
written in a way that they stay
>>>> consistent
>>>>>>> after the file is imported.
>>>>>>>
>>>>>>> Take my own project as an
example. I've got two directories:
>>>>>>>
>>>>>>>
/home/ryan/code/sip/sip-communicator   --> this is
>>>> sip-communicator from CVS
>>>>>>>
/home/ryan/code/sip/sc-avmailbox         --> this is my
own project
>>>>>>>
>>>>>>>
/home/ryan/code/sip/sc-avmailbox/build.xml imports
>>>>>>>
/home/ryan/code/sip/sip-communicator/build.xml , redefining
>>>> necessary targets.
>>>>>>> However, a reference to
src/some/file location in the build.xml will
>>>>>>> end up resolving to
>>>>>>>
/home/ryan/code/sip/sc-avmailbox/src/some/file/location 
instead of
>>>>>>>
/home/ryan/code/sip/sip-communicator/src/some/file/location
after
>>>> the
>>>>>>> file is imported.
>>>>>>>
>>>>>>> I've fixed all such references
as per the relevant ant documentation
>>>>>>> at ht
tp://ant.apache.org/manual/CoreTasks/import.html .
Scroll
>>>> down to
>>>>>>> "resolving files against
the imported file"
>>>>>>>
>>>>>>> As of right now I'm not done
with the rest of the tricks
>>>> necessary to
>>>>>>> make the subproject build as
intended, but I'm sending this patch
>>>> now
>>>>>>> because (1) it shouldn't change
anything if run from the
>>>>>>> sip-communicator directory, (2)
submitting it now allows more
>>>> time for
>>>>>>> everyone to make sure I didn't
mess something up, and (3) this
>>>> way as
>>>>>>> people add targets to build.xml
they can use the correct syntax to
>>>>>>> keep the build.xml importable.
>>>>>>>
>>>>>>>
>>>>>> --
>>>>>> My life has no purpose...my life
has no direction...no aim...no
>>>>>> meaning... and yet I'm happy... I
can't figure it out... What am I
>>>>>> doing right?
>>>>>>
>>>>>> Charles Schultz
>>>>>>
>>>>>
>>>>>
>>>>>
>>>>
------------------------------------------------------------
------------
>>>>>
------------------------------------------------------------
---------
>>>>> To unsubscribe, e-mail:
dev-unsubscribesip-communicator.dev.java.net
>>>>> For additional commands, e-mail:
>>>> dev-helpsip-communicator.dev.java.net
>>>>
>>>>
------------------------------------------------------------
---------
>>>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>>>> For additional commands, e-mail:
dev-helpsip-communicator.dev.java.net
>>>>
>>>>
>>>
>>
------------------------------------------------------------
---------
>> To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
>> For additional commands, e-mail: dev-helpsip-communicator.dev.java.net
>>
>>
> 
> 

------------------------------------------------------------
---------
To unsubscribe, e-mail: dev-unsubscribesip-communicator.dev.java.net
For additional commands, e-mail: dev-helpsip-communicator.dev.java.net