You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Luciano Resende <lu...@gmail.com> on 2007/05/23 18:24:42 UTC
Automated nightly builds
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
Ok, I have fixed the sca build issue described by Jean-Sebastien, so
now, SCA, SDO and DAS are configured to run with the distribution
profile. Once the three builds are passing successfully, I'll send
the link to the nightly distributions in a new thread.
On 6/22/07, Luciano Resende <lu...@gmail.com> wrote:
> The current status is:
> DAS is building with the distribution profile enabled.
> SCA distribution profile was causing errors as mentioned in [1].
> Did we find a solution for them ?
> SDO was missing distribution profile. Ant was working on SDO
> distributions, but I'm not sure the profile is done.
>
>
> [1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg18807.html
>
> On 6/22/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> > Simon Laws wrote:
> > > Are the distribution artefacts now being produced? Can we add the
> > > links to
> > > the web site? If so what should they be?
> > >
> > > Simon
> > >
> >
> > It doesn't look like they are. Luciano, or anybody who has access to the
> > confluence config, would it be possible to switch the build profile to
> > -Pdistribution?
> >
> > Thanks...
> >
> > --
> > Jean-Sebastien
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
>
> --
> Luciano Resende
> Apache Tuscany Committer
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
The current status is:
DAS is building with the distribution profile enabled.
SCA distribution profile was causing errors as mentioned in [1].
Did we find a solution for them ?
SDO was missing distribution profile. Ant was working on SDO
distributions, but I'm not sure the profile is done.
[1] http://www.mail-archive.com/tuscany-dev@ws.apache.org/msg18807.html
On 6/22/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> Simon Laws wrote:
> > Are the distribution artefacts now being produced? Can we add the
> > links to
> > the web site? If so what should they be?
> >
> > Simon
> >
>
> It doesn't look like they are. Luciano, or anybody who has access to the
> confluence config, would it be possible to switch the build profile to
> -Pdistribution?
>
> Thanks...
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Simon Laws wrote:
> Are the distribution artefacts now being produced? Can we add the
> links to
> the web site? If so what should they be?
>
> Simon
>
It doesn't look like they are. Luciano, or anybody who has access to the
confluence config, would it be possible to switch the build profile to
-Pdistribution?
Thanks...
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Simon Laws <si...@googlemail.com>.
Are the distribution artefacts now being produced? Can we add the links to
the web site? If so what should they be?
Simon
Re: Automated nightly builds
Posted by Mike Edwards <mi...@gmail.com>.
+1 from me
Yours, Mike.
ant elder wrote:
> On 6/7/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
>>
>> Luciano Resende wrote:
>> > Wouldn't that fail if you start from a clean repo ? It expects the
>> > other modules to be built or available as deployed snapshots no ?
>> >
>> > On 6/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>> >> [snip]
>> >> Luciano Resende wrote:
>> >> >> I'm looking for a distribution that I could use directly, as the
>> >> >> individual JARs are not so useful. Is there a way to get the
>> >> >> distribution built as part of the automated build?
>> >> >
>> >> > For DAS, I have a "distribution" profile that generate javadoc,
>> >> > distributions, etc
>> >> > Maybe we could do same for SCA (and SDO) , and I could use this
>> >> > profile on the automated builds.
>> >> >
>> >> > Thougths ?
>> >> >
>> >>
>> >> or maybe even simpler than a profile, is it possible to just add the
>> >> distribution Maven module to the confluence build config?
>> >>
>> >> --
>> >> Jean-Sebastien
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> I was thinking about building adding the distribution build after the
>> sca build in the same confluence build config, but it doesn't look like
>> it's possible, so I guess a build profile, as you suggested is the best
>> solution.
>>
>> Another thought, how about adding a link to the nightly builds to the
>> Tuscany SCA Java download page? What do people think?
>
>
>
> Yes thant would be good.
>
> ...ant
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by ant elder <an...@apache.org>.
On 6/7/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> Luciano Resende wrote:
> > Wouldn't that fail if you start from a clean repo ? It expects the
> > other modules to be built or available as deployed snapshots no ?
> >
> > On 6/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >> [snip]
> >> Luciano Resende wrote:
> >> >> I'm looking for a distribution that I could use directly, as the
> >> >> individual JARs are not so useful. Is there a way to get the
> >> >> distribution built as part of the automated build?
> >> >
> >> > For DAS, I have a "distribution" profile that generate javadoc,
> >> > distributions, etc
> >> > Maybe we could do same for SCA (and SDO) , and I could use this
> >> > profile on the automated builds.
> >> >
> >> > Thougths ?
> >> >
> >>
> >> or maybe even simpler than a profile, is it possible to just add the
> >> distribution Maven module to the confluence build config?
> >>
> >> --
> >> Jean-Sebastien
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
> I was thinking about building adding the distribution build after the
> sca build in the same confluence build config, but it doesn't look like
> it's possible, so I guess a build profile, as you suggested is the best
> solution.
>
> Another thought, how about adding a link to the nightly builds to the
> Tuscany SCA Java download page? What do people think?
Yes thant would be good.
...ant
Error building distribution, was: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Venkata Krishnan wrote:
> +1 from me - sounds very useful especially if distributions are going
> to be
> available.
>
> - Venkat
>
> On 6/7/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>>
>> Luciano Resende wrote:
>> > Wouldn't that fail if you start from a clean repo ? It expects the
>> > other modules to be built or available as deployed snapshots no ?
>> >
>> > On 6/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>> >> [snip]
>> >> Luciano Resende wrote:
>> >> >> I'm looking for a distribution that I could use directly, as the
>> >> >> individual JARs are not so useful. Is there a way to get the
>> >> >> distribution built as part of the automated build?
>> >> >
>> >> > For DAS, I have a "distribution" profile that generate javadoc,
>> >> > distributions, etc
>> >> > Maybe we could do same for SCA (and SDO) , and I could use this
>> >> > profile on the automated builds.
>> >> >
>> >> > Thougths ?
>> >> >
>> >>
>> >> or maybe even simpler than a profile, is it possible to just add the
>> >> distribution Maven module to the confluence build config?
>> >>
>> >> --
>> >> Jean-Sebastien
>> >>
>> >>
>> >> ---------------------------------------------------------------------
>> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >>
>> >>
>> >
>> >
>>
>> I was thinking about building adding the distribution build after the
>> sca build in the same confluence build config, but it doesn't look like
>> it's possible, so I guess a build profile, as you suggested is the best
>> solution.
>>
>> Another thought, how about adding a link to the nightly builds to the
>> Tuscany SCA Java download page? What do people think?
>>
>> --
>> Jean-Sebastien
>>
>>
Under revision r546709 I added a distribution profile to
tuscany/java/sca including the distribution module, but I'm running into
a weird Maven error.
I am able to build the distribution module alone.
cd tuscany/java/sca/distribution
mvn
... works.
But
cd tuscany/java/sca
mvn -Pdistribution
... gives the the following error when it reaches the distribution
build, after having successfully built all the other SCA modules:
[INFO]
----------------------------------------------------------------------------
[INFO] Building Apache Tuscany Distribution
[INFO] task-segment: [install]
[INFO]
----------------------------------------------------------------------------
[INFO] [ant:ant {execution: generate-sources}]
Wrote Ant project for tuscany-distribution to
/home/delfinoj/Tuscany/apache-repos/java/sca/distribution
[INFO] [antrun:run {execution: process-sources-xsl}]
[INFO] Executing tasks
[xslt] DEPRECATED - xalan processor is deprecated. Use trax instead.
[xslt] DEPRECATED - xslp processor is deprecated. Use trax instead.
java.lang.ClassNotFoundException:
org.apache.tools.ant.taskdefs.optional.XslpLiaison
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at
org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
at
org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at
org.apache.tools.ant.taskdefs.XSLTProcess.loadClass(XSLTProcess.java:419)
at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:397)
at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:619)
at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:212)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
java.lang.ClassNotFoundException:
org.apache.tools.ant.taskdefs.optional.XalanLiaison
at java.net.URLClassLoader$1.run(URLClassLoader.java:200)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:188)
at java.lang.ClassLoader.loadClass(ClassLoader.java:306)
at
org.codehaus.classworlds.RealmClassLoader.loadClassDirect(RealmClassLoader.java:195)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:255)
at
org.codehaus.classworlds.DefaultClassRealm.loadClass(DefaultClassRealm.java:274)
at
org.codehaus.classworlds.RealmClassLoader.loadClass(RealmClassLoader.java:214)
at java.lang.ClassLoader.loadClass(ClassLoader.java:251)
at java.lang.ClassLoader.loadClassInternal(ClassLoader.java:319)
at java.lang.Class.forName0(Native Method)
at java.lang.Class.forName(Class.java:164)
at
org.apache.tools.ant.taskdefs.XSLTProcess.loadClass(XSLTProcess.java:419)
at
org.apache.tools.ant.taskdefs.XSLTProcess.resolveProcessor(XSLTProcess.java:402)
at
org.apache.tools.ant.taskdefs.XSLTProcess.getLiaison(XSLTProcess.java:616)
at
org.apache.tools.ant.taskdefs.XSLTProcess.execute(XSLTProcess.java:212)
at
org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275)
at org.apache.tools.ant.Task.perform(Task.java:364)
at org.apache.tools.ant.Target.execute(Target.java:341)
at
org.apache.maven.plugin.antrun.AbstractAntMojo.executeTasks(AbstractAntMojo.java:108)
at
org.apache.maven.plugin.antrun.AntRunMojo.execute(AntRunMojo.java:83)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error executing ant tasks
Embedded error: java.lang.ClassNotFoundException:
org.apache.tools.ant.taskdefs.optional.TraXLiaison
Any idea?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Venkata Krishnan <fo...@gmail.com>.
+1 from me - sounds very useful especially if distributions are going to be
available.
- Venkat
On 6/7/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> Luciano Resende wrote:
> > Wouldn't that fail if you start from a clean repo ? It expects the
> > other modules to be built or available as deployed snapshots no ?
> >
> > On 6/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >> [snip]
> >> Luciano Resende wrote:
> >> >> I'm looking for a distribution that I could use directly, as the
> >> >> individual JARs are not so useful. Is there a way to get the
> >> >> distribution built as part of the automated build?
> >> >
> >> > For DAS, I have a "distribution" profile that generate javadoc,
> >> > distributions, etc
> >> > Maybe we could do same for SCA (and SDO) , and I could use this
> >> > profile on the automated builds.
> >> >
> >> > Thougths ?
> >> >
> >>
> >> or maybe even simpler than a profile, is it possible to just add the
> >> distribution Maven module to the confluence build config?
> >>
> >> --
> >> Jean-Sebastien
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
> I was thinking about building adding the distribution build after the
> sca build in the same confluence build config, but it doesn't look like
> it's possible, so I guess a build profile, as you suggested is the best
> solution.
>
> Another thought, how about adding a link to the nightly builds to the
> Tuscany SCA Java download page? What do people think?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Luciano Resende wrote:
> Wouldn't that fail if you start from a clean repo ? It expects the
> other modules to be built or available as deployed snapshots no ?
>
> On 6/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>> [snip]
>> Luciano Resende wrote:
>> >> I'm looking for a distribution that I could use directly, as the
>> >> individual JARs are not so useful. Is there a way to get the
>> >> distribution built as part of the automated build?
>> >
>> > For DAS, I have a "distribution" profile that generate javadoc,
>> > distributions, etc
>> > Maybe we could do same for SCA (and SDO) , and I could use this
>> > profile on the automated builds.
>> >
>> > Thougths ?
>> >
>>
>> or maybe even simpler than a profile, is it possible to just add the
>> distribution Maven module to the confluence build config?
>>
>> --
>> Jean-Sebastien
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>
>
I was thinking about building adding the distribution build after the
sca build in the same confluence build config, but it doesn't look like
it's possible, so I guess a build profile, as you suggested is the best
solution.
Another thought, how about adding a link to the nightly builds to the
Tuscany SCA Java download page? What do people think?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
Wouldn't that fail if you start from a clean repo ? It expects the
other modules to be built or available as deployed snapshots no ?
On 6/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> [snip]
> Luciano Resende wrote:
> >> I'm looking for a distribution that I could use directly, as the
> >> individual JARs are not so useful. Is there a way to get the
> >> distribution built as part of the automated build?
> >
> > For DAS, I have a "distribution" profile that generate javadoc,
> > distributions, etc
> > Maybe we could do same for SCA (and SDO) , and I could use this
> > profile on the automated builds.
> >
> > Thougths ?
> >
>
> or maybe even simpler than a profile, is it possible to just add the
> distribution Maven module to the confluence build config?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
[snip]
Luciano Resende wrote:
>> I'm looking for a distribution that I could use directly, as the
>> individual JARs are not so useful. Is there a way to get the
>> distribution built as part of the automated build?
>
> For DAS, I have a "distribution" profile that generate javadoc,
> distributions, etc
> Maybe we could do same for SCA (and SDO) , and I could use this
> profile on the automated builds.
>
> Thougths ?
>
or maybe even simpler than a profile, is it possible to just add the
distribution Maven module to the confluence build config?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Simon Nash <na...@hursley.ibm.com>.
Comments inline below.
Simon
Luciano Resende wrote:
>> I'm looking for a distribution that I could use directly, as the
>> individual JARs are not so useful. Is there a way to get the
>> distribution built as part of the automated build?
>
>
> For DAS, I have a "distribution" profile that generate javadoc,
> distributions, etc
> Maybe we could do same for SCA (and SDO) , and I could use this
> profile on the automated builds.
>
> Thougths ?
>
+1 for including the distribution in the nightly build.
> On 6/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
>> Luciano Resende wrote:
>> > On 6/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>> >> Luciano Resende wrote:
>> >> > I have changed all ports to 8085 and all the builds are working
>> now on
>> >> > the apache machine [1]. I'll add a page to our Wiki describing
>> how you
>> >> > can watch the results, I'll also configure the builds to send
>> failure
>> >> > notification to the dev-list. I still have a todo to investigate the
>> >> > usage of the binary created on the build.
>> >> >
>> >> > [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
>> >> >
>> >>
>> >> The Apache Tuscany SCA Implementation Project says "Tuscany SDO
>> >> Implementation Project" in the Group column. I was expecting to see
>> SCA
>> >> instead. What is the Group used for?
>> >
>> > The default behavior of the continuum admin ui is to add all
>> > sub-projects of a given pom, and because SCA was generating many
>> > projects, I decided to just re-use a SDO one and point to the SCA
>> > project pom to build it recursively. The group description you are
>> > seeing should not really affect anything, but also it's not an edit
>> > field (at least I couldn't find a place to edit it).
>>
>> I'm thinking that it's a little confusing, as our SCA implementation
>> does not have a hard dependency on SDO.
>
I think these should be kept separate. What is the disadvantage of
doing this?
>> >
>> >> I just triggered a successfull build of the SCA runtime. Where can
>> I get
>> >> the binaries produced by the build? I couldn't find a link to them...
>> >>
>> >
>> > Open the continuum build project, go to Working copy tab on the top
>> > and you should have access to all built artifacts (same folder
>> > structure as local build)
>> >
>>
>> I'm looking for a distribution that I could use directly, as the
>> individual JARs are not so useful. Is there a way to get the
>> distribution built as part of the automated build?
>>
>> >> Thanks
>> >>
>> >> --
>> >> Jean-Sebastien
>> >>
>> >>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
> I'm looking for a distribution that I could use directly, as the
> individual JARs are not so useful. Is there a way to get the
> distribution built as part of the automated build?
For DAS, I have a "distribution" profile that generate javadoc,
distributions, etc
Maybe we could do same for SCA (and SDO) , and I could use this
profile on the automated builds.
Thougths ?
On 6/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> Luciano Resende wrote:
> > On 6/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >> Luciano Resende wrote:
> >> > I have changed all ports to 8085 and all the builds are working now on
> >> > the apache machine [1]. I'll add a page to our Wiki describing how you
> >> > can watch the results, I'll also configure the builds to send failure
> >> > notification to the dev-list. I still have a todo to investigate the
> >> > usage of the binary created on the build.
> >> >
> >> > [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
> >> >
> >>
> >> The Apache Tuscany SCA Implementation Project says "Tuscany SDO
> >> Implementation Project" in the Group column. I was expecting to see SCA
> >> instead. What is the Group used for?
> >
> > The default behavior of the continuum admin ui is to add all
> > sub-projects of a given pom, and because SCA was generating many
> > projects, I decided to just re-use a SDO one and point to the SCA
> > project pom to build it recursively. The group description you are
> > seeing should not really affect anything, but also it's not an edit
> > field (at least I couldn't find a place to edit it).
>
> I'm thinking that it's a little confusing, as our SCA implementation
> does not have a hard dependency on SDO.
> >
> >> I just triggered a successfull build of the SCA runtime. Where can I get
> >> the binaries produced by the build? I couldn't find a link to them...
> >>
> >
> > Open the continuum build project, go to Working copy tab on the top
> > and you should have access to all built artifacts (same folder
> > structure as local build)
> >
>
> I'm looking for a distribution that I could use directly, as the
> individual JARs are not so useful. Is there a way to get the
> distribution built as part of the automated build?
>
> >> Thanks
> >>
> >> --
> >> Jean-Sebastien
> >>
> >>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Luciano Resende wrote:
> On 6/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>> Luciano Resende wrote:
>> > I have changed all ports to 8085 and all the builds are working now on
>> > the apache machine [1]. I'll add a page to our Wiki describing how you
>> > can watch the results, I'll also configure the builds to send failure
>> > notification to the dev-list. I still have a todo to investigate the
>> > usage of the binary created on the build.
>> >
>> > [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
>> >
>>
>> The Apache Tuscany SCA Implementation Project says "Tuscany SDO
>> Implementation Project" in the Group column. I was expecting to see SCA
>> instead. What is the Group used for?
>
> The default behavior of the continuum admin ui is to add all
> sub-projects of a given pom, and because SCA was generating many
> projects, I decided to just re-use a SDO one and point to the SCA
> project pom to build it recursively. The group description you are
> seeing should not really affect anything, but also it's not an edit
> field (at least I couldn't find a place to edit it).
I'm thinking that it's a little confusing, as our SCA implementation
does not have a hard dependency on SDO.
>
>> I just triggered a successfull build of the SCA runtime. Where can I get
>> the binaries produced by the build? I couldn't find a link to them...
>>
>
> Open the continuum build project, go to Working copy tab on the top
> and you should have access to all built artifacts (same folder
> structure as local build)
>
I'm looking for a distribution that I could use directly, as the
individual JARs are not so useful. Is there a way to get the
distribution built as part of the automated build?
>> Thanks
>>
>> --
>> Jean-Sebastien
>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>
>
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
On 6/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> Luciano Resende wrote:
> > I have changed all ports to 8085 and all the builds are working now on
> > the apache machine [1]. I'll add a page to our Wiki describing how you
> > can watch the results, I'll also configure the builds to send failure
> > notification to the dev-list. I still have a todo to investigate the
> > usage of the binary created on the build.
> >
> > [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
> >
>
> The Apache Tuscany SCA Implementation Project says "Tuscany SDO
> Implementation Project" in the Group column. I was expecting to see SCA
> instead. What is the Group used for?
The default behavior of the continuum admin ui is to add all
sub-projects of a given pom, and because SCA was generating many
projects, I decided to just re-use a SDO one and point to the SCA
project pom to build it recursively. The group description you are
seeing should not really affect anything, but also it's not an edit
field (at least I couldn't find a place to edit it).
> I just triggered a successfull build of the SCA runtime. Where can I get
> the binaries produced by the build? I couldn't find a link to them...
>
Open the continuum build project, go to Working copy tab on the top
and you should have access to all built artifacts (same folder
structure as local build)
> Thanks
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Luciano Resende wrote:
> I have changed all ports to 8085 and all the builds are working now on
> the apache machine [1]. I'll add a page to our Wiki describing how you
> can watch the results, I'll also configure the builds to send failure
> notification to the dev-list. I still have a todo to investigate the
> usage of the binary created on the build.
>
> [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
>
The Apache Tuscany SCA Implementation Project says "Tuscany SDO
Implementation Project" in the Group column. I was expecting to see SCA
instead. What is the Group used for?
I just triggered a successfull build of the SCA runtime. Where can I get
the binaries produced by the build? I couldn't find a link to them...
Thanks
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Changing default Tomcat and Jetty ports to 8080, was: Automated nightly
builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Luciano Resende wrote:
> I have changed all ports to 8085 and all the builds are working now on
> the apache machine [1]. I'll add a page to our Wiki describing how you
> can watch the results, I'll also configure the builds to send failure
> notification to the dev-list. I still have a todo to investigate the
> usage of the binary created on the build.
>
> [1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
>
While working on some improvements of the Jetty and Tomcat embedded
servers, I noticed that they now use port 8085 by default instead of
8080. I thought we were going to change all the test case artifacts to
use 8085, but not actually make 8085 the default port in the Tuscany Web
Server runtime integration.
I changed the defaults in TomcatServer and JettyServer to 8080, which is
a widely used default for Tomcat, Jetty, and most server targeting tools
and went through all the remaining test cases that didn't specify a port
to specify 8085 in the test case artifacts.
I also ran a build with port 8080 being used by another process on my
machine to verify that there's no remaining test case using 8080. It
worked, so it should work as well on the Confluence build machine.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
I have changed all ports to 8085 and all the builds are working now on
the apache machine [1]. I'll add a page to our Wiki describing how you
can watch the results, I'll also configure the builds to send failure
notification to the dev-list. I still have a todo to investigate the
usage of the binary created on the build.
[1] http://vmbuild.apache.org:8080/continuum/servlet/continuum
On 5/30/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> [snip]
> Luciano Resende wrote:
> > I can look into these requirements, and try to get it setup on vmbuild.
> >
> > Right now I'm having a more basic issue, where the SCA test cases that
> > need http require a port that, in the apache machine, is already in
> > use by the continuum http web container (jetty), should we have an
> > easy way to globally identify the ports to use for the unit tests ?
> > And could we use something different then the defaults ?
> >
>
> The port numbers are configured by the binding uri or the wsdl port or
> endpoint. Changing all 8080 to 8083 or another available port number in
> the composite and wsdl files should work. I am suggesting 8083 as 8081
> and 8082 are already used by some test cases if I remember correctly.
>
> Hope this helps.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
[snip]
Luciano Resende wrote:
> I can look into these requirements, and try to get it setup on vmbuild.
>
> Right now I'm having a more basic issue, where the SCA test cases that
> need http require a port that, in the apache machine, is already in
> use by the continuum http web container (jetty), should we have an
> easy way to globally identify the ports to use for the unit tests ?
> And could we use something different then the defaults ?
>
The port numbers are configured by the binding uri or the wsdl port or
endpoint. Changing all 8080 to 8083 or another available port number in
the composite and wsdl files should work. I am suggesting 8083 as 8081
and 8082 are already used by some test cases if I remember correctly.
Hope this helps.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
I can look into these requirements, and try to get it setup on vmbuild.
Right now I'm having a more basic issue, where the SCA test cases that
need http require a port that, in the apache machine, is already in
use by the continuum http web container (jetty), should we have an
easy way to globally identify the ports to use for the unit tests ?
And could we use something different then the defaults ?
On 5/29/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> 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 <js...@apache.org> 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 <fo...@gmail.com> wrote:
> >> >> Thanks for doing this :). +1 for separating out SCA, SDO and DAS
> >> builds
> >> >>
> >> >> - Venkat
> >> >>
> >> >> On 5/23/07, Luciano Resende <lu...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> >> >> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >> >> >
> >> >> >
> >> >>
> >> >
> >> >
> >>
> >> 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: tuscany-dev-unsubscribe@ws.apache.org
> >> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >>
> >>
> >
> >
>
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
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 <js...@apache.org> 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 <fo...@gmail.com> wrote:
>> >> Thanks for doing this :). +1 for separating out SCA, SDO and DAS
>> builds
>> >>
>> >> - Venkat
>> >>
>> >> On 5/23/07, Luciano Resende <lu...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
>> >> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >> >
>> >> >
>> >>
>> >
>> >
>>
>> 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: tuscany-dev-unsubscribe@ws.apache.org
>> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>>
>>
>
>
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
>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.
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
On 5/29/07, Jean-Sebastien Delfino <js...@apache.org> 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 <fo...@gmail.com> wrote:
> >> Thanks for doing this :). +1 for separating out SCA, SDO and DAS builds
> >>
> >> - Venkat
> >>
> >> On 5/23/07, Luciano Resende <lu...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> >> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >> >
> >> >
> >>
> >
> >
>
> 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: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Jean-Sebastien Delfino <js...@apache.org>.
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 <fo...@gmail.com> wrote:
>> Thanks for doing this :). +1 for separating out SCA, SDO and DAS builds
>>
>> - Venkat
>>
>> On 5/23/07, Luciano Resende <lu...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >
>> >
>>
>
>
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: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Luciano Resende <lu...@gmail.com>.
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 <fo...@gmail.com> wrote:
> Thanks for doing this :). +1 for separating out SCA, SDO and DAS builds
>
> - Venkat
>
> On 5/23/07, Luciano Resende <lu...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
--
Luciano Resende
Apache Tuscany Committer
http://people.apache.org/~lresende
http://lresende.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Automated nightly builds
Posted by Venkata Krishnan <fo...@gmail.com>.
Thanks for doing this :). +1 for separating out SCA, SDO and DAS builds
- Venkat
On 5/23/07, Luciano Resende <lu...@gmail.com> 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: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
Re: Automated nightly builds
Posted by Simon Laws <si...@googlemail.com>.
+1 for
>
> - Have three builds, that would build each project separately
Simon