Hey guys,
The "dist" target discussion started offline and I
asked Pavel to move
it to the mailing list. I personally feel it is a good idea
to have such
a target in the build.xml (there was one like it in the
previous
version). I'd like it to build a tar.gz/zip of the sources
and another
one for the OSCAR repository (the binaries). The latter
should include
run scripts that should be the same as those used in the
platform
specific packages.
I also think that it is important to have this package
target ready
before the release so that it could be a part of it. I need
to debug JMF
and the SIP implementation some more so this would give
Pavel the time
to implement the target.
Brian Burch wrote:
> The cc-buildloop target is used by CruiseControl to
ensure we test
> against a 100% clean build.
>
> In my opinion, ANY/ALL distribution targets should
depend on
> cc-buildloop, even if they are not always run as part
of cc-buildloop.
> In other words, we should only distribute after a
perfect
> clean/build/test cycle.
I agree. Adding an ant dependency on cc-buildloop to the
dist target
might be a bit too heavy though.
Here's what I'd suggest: CruiseControl uses its own
build.xml that
references that of SIP Communicator. Right now it looks
pretty much
like this.
><target name="build">
> <Get the latest from CVS>
>
> <!-- Call cc-buildloop-->
> <ant antfile="build.xml"
target="cc-buildloop"/>
>
> <!-- Generate the javadocs -->
> <ant antfile="build.xml"
target="javadoc"/>
> <copy
todir="public_html/sip-comm-doc">
> <fileset dir="doc/api"/>
> </copy>
>
> <!-- Create installation packages -->
> <ant antfile="build.xml"
target="build-installation-generic" />
> <ant antfile="build.xml"
target="build-installation-windows" />
> <ant antfile="build.xml"
target="build-installation-linux" />
>
> <!-- Upload install-->
> <dirname property="lbasedir"
file="${ant.file}"/>
> <exec dir="$"
executable="upload-sip-communicator.sh"/>
></target>
You notice that we're already generating the izpack
installers there.
Since ant would stop executing when it encounters an error,
these
installers are only generated if cc-buildloop has gone ok. I
guess we
could do the same for a possble dist target.
Cheers
Emil
Brian Burch wrote:
> Pavel Tankov wrote:
>> Thank you for the explanations. What you say about
having the first release stabilised and then
>> reviewing the build.xml make sense to me and I
agree with you.
>>
>> Yet, I still need help with structuring the layout
of the rpm package. I reviewed the deb package
>> and, certainly, can take it as a model to follow,
but if you could point me to some description of
>> the desired layout that would help a great deal.
>>
>
> Sorry, Pavel, I cannot offer you any help. Although
I've been a *nix
> user for several years, I haven't had any experience
with either rpm or
> deb packaging. All my ant packaging work has been
related to building
> and deploying j2ee war files, so it isn't very
relevant.
>
> However, if you need advice on how to craft your manual
packaging stages
> into the existing build.xml, I'll try to help if
everyone else is too
> busy working on the code. (I've been hoping Emil would
have commented on
> this thread, but perhaps he is too busy?)
>
> Regards,
>
> Brian
>
>
------------------------------------------------------------
---------
> To unsubscribe, e-mail: dev-unsubscribe sip-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
|