Luciano Resende wrote:
From previous discussions on the mailing list [1], there are two
scenarios here :
* Users interested in only checking out specific Tuscany sub-projects
and be able to build it and work with it. These users would rely on
all dependencies to be available from a maven repo (e.g SDO and DAS,
among external dependencies)
* Users interested in all Tuscany, they would come and build from the
root, and would expect the trunk version of SCA, SDO and DAS to build
and work together.
So, maybe we could try to have both scenarios automated, instead of
deciding for one, as I was proposing in the original question.
OK, people can check out SVN trees and build them themselves using
Maven. They can either build SDO + SCA + DAS or just a subset and Maven
published snapshots for the rest. Actually they can even go more fine
grained and build individual modules if they want. I guess this is
development / build as usual...
As for the downloading, I wasn't planning to publish any jars from the
nightly build, at least for now... but if people think we should do
it, I can look into it as well.
[1] http://www.mail-archive.com/tuscany-dev%40ws.apache.org/msg17979.html
Yes... I guess a build becomes more useful if you can actually download
and use what's built :)
The scenario I'm particularly interested in is:
- I'm a user of Tuscany/SCA and I'm not interested in building the
bleeding edge source on my machine, I care about integrating Tuscany
with my environment, developing Tuscany extensions, or developing SCA
applications that run on top of Tuscany.
- I reported a Tuscany/SCA bug, the bug got fixed, I'd like to use the
latest Tuscany nightly build which contains the fix.
- I'm not necessarily using Maven. I could be using Maven, but maybe I'm
just using my IDE and/or Ant. I'm assuming that I can just point my Web
browser to a few Zips or some other form of archive, download them, and
go from there.
- I'd like to understand what I need to download.
I think that this is a pretty simple use case. Will the new nightly
builds support it? Will I get a Tuscany/SCA distribution? Or will I have
to download individual Tuscany/SCA, SDO and DAS pieces? Can I get some
indication from the build status that the various pieces are going to
work together?
Thanks
On 5/29/07, Jean-Sebastien Delfino <[EMAIL PROTECTED]> wrote:
Luciano Resende wrote:
> I pretty much have it working locally, building SCA, SDO and DAS
> independently.
>
> As for hosting the build at the shared machine at Apache, I have
> created a JIRA [1] asking for an account to add and administer the
> builds on the shared machine.
>
> [1] https://issues.apache.org/jira/browse/INFRA-1261
>
> On 5/26/07, Venkata Krishnan <[EMAIL PROTECTED]> wrote:
>> Thanks for doing this :). +1 for separating out SCA, SDO and DAS
builds
>>
>> - Venkat
>>
>> On 5/23/07, Luciano Resende <[EMAIL PROTECTED]> wrote:
>> >
>> > I'm starting to pursue a nightly build for Apache Tuscany with the
>> > Apache Infra guys, and I just want to double check what people
think
>> > it's the best build layout that we should use
>> >
>> > - Have one top-down build, that would build all Tuscany subprojects
>> > (SCA/SDO/DAS)
>> >
>> > - Have three builds, that would build each project separately
>> >
>> > I particularly would prefer the second option, as that would
ensure
>> > each subproject can work independently, based on published
>> > releases/snapshots of it's dependencies.
>> >
>> > Thoughts ?
>> >
>> > --
>> > Luciano Resende
>> > Apache Tuscany Committer
>> > http://people.apache.org/~lresende
>> > http://lresende.blogspot.com/
>> >
>> >
---------------------------------------------------------------------
>> > To unsubscribe, e-mail: [EMAIL PROTECTED]
>> > For additional commands, e-mail: [EMAIL PROTECTED]
>> >
>> >
>>
>
>
Nice. Quick question, as it looks like you're going to have 3 different
builds for SCA, SDO and DAS:
If I download the SCA and SDO builds for example, will the SCA build use
the exact same level of SDO that I'll get with the SDO build? In other
words are we making sure that they work together?
Thanks
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
