You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Jean-Sebastien Delfino <js...@apache.org> on 2007/04/05 04:36:04 UTC
Build update, was: SCA source tree and build structure
Jean-Sebastien Delfino wrote:
> Venkata Krishnan wrote:
>> Hi,
>>
>> Yes, what Luciano is suggesting here makes sense to me as well.
>>
>> Thanks
>>
>> - Venkat
>>
>> On 4/4/07, Luciano Resende <lu...@gmail.com> wrote:
>>>
>>> Sebastien wrote:
>>> > I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
>>> alpha1 is
>>> >probably better. I'll start with alpha1 then.
>>>
>>> Should we leave like 1.0-incubating-SNAPSHOT, and only add M3 or alpha1
>>> when
>>> we branch/tag for release, together with the removal of SNAPSHOT ? This
>>> would make trunk always with same version id, right ?
>>>
>>> On 4/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>>> >
>>> > [snip]
>>> > Raymond Feng wrote:
>>> > > Forgot to ask one question:
>>> > >
>>> > > We have inconsistent version ids for artifacts in the trunk, do you
>>> > > plan to reconcile them? If so, what should the version id look
>>> like? I
>>> > > propose that we use something like
>>> 1.0-incubating-alpha1-SNAPSHOT to
>>> > > reflect the fact that we're working toward a 1.0 release.
>>> > >
>>> > > Thanks,
>>> > > Raymond
>>> > >
>>> >
>>> > Yes I plan to reconcile them, like this:
>>> >
>>> > >
>>> > >> - Version of our modules will be specified once in
>>> java/sca/pom.xml,
>>> > >> child poms don't need specify a version as they get it from their
>>> > parent
>>> > >>
>>> >
>>> > I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
>>> alpha1 is
>>> > probably better. I'll start with alpha1 then.
>>> >
>>> > --
>>> > 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
>>> http://people.apache.org/~lresende
>>>
>>
>
> OK then, it makes sense to me too, I'll change to
> 1.0-incubating-SNAPSHOT.
>
Here's an update on the progress with the new build structure.
To build the sca tree, you should now be able to do the following:
cd tuscany/java/sca
mvn
and get the following output.
[INFO]
------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO]
------------------------------------------------------------------------
[INFO] Apache Tuscany Project Parent ......................... SUCCESS
[1.356s]
[INFO] Apache Tuscany Build Tools ............................ SUCCESS
[0.975s]
[INFO] SCA API Version 1.0 ................................... SUCCESS
[0.900s]
[INFO] Apache Tuscany SCA Implementation Project ............. SUCCESS
[0.033s]
[INFO] Apache Tuscany SCA Implementation Modules ............. SUCCESS
[0.044s]
[INFO] Apache Tuscany Interface Model ........................ SUCCESS
[0.972s]
[INFO] Apache Tuscany Policy Model ........................... SUCCESS
[1.206s]
[INFO] Apache Tuscany Assembly Model ......................... SUCCESS
[2.266s]
[INFO] Apache Tuscany SCA Contribution Service ............... SUCCESS
[1.134s]
[INFO] Apache Tuscany SCA XML Assembly Support ............... SUCCESS
[2.860s]
[INFO] Apache Tuscany DataBinding Framework .................. SUCCESS
[4.500s]
[INFO] Apache Tuscany Data Binding for Axiom ................. SUCCESS
[1.746s]
[INFO] Apache Tuscany HTTP Servlet Host ...................... SUCCESS
[0.331s]
[INFO] Apache Tuscany Jetty HTTP Service ..................... SUCCESS
[4.493s]
[INFO] Apache Tuscany Tomcat HTTP Service .................... SUCCESS
[2.545s]
[INFO] Apache Tuscany Java Interface Model ................... SUCCESS
[0.687s]
[INFO] Apache Tuscany SCA XML Java Interface Extension ....... SUCCESS
[1.365s]
[INFO] Apache Tuscany WSDL Interface Model ................... SUCCESS
[0.750s]
[INFO] Apache Tuscany SCA XML WSDL Interface Extension ....... SUCCESS
[1.383s]
[INFO] Apache Tuscany Java Implementation Model .............. SUCCESS
[0.823s]
[INFO] Apache Tuscany SCA XML Java Implementation Extension .. SUCCESS
[1.436s]
[INFO] Apache Tuscany Axis2 Java2WSDL Tool ................... SUCCESS
[9.311s]
[INFO] Apache Tuscany Maven Plugin for Java2WSDL ............. SUCCESS
[1.400s]
[INFO] Apache Tuscany Axis2 WSDL2Java Tool ................... SUCCESS
[6.734s]
[INFO] Apache Tuscany Maven Plugin for WSDL2Java ............. SUCCESS
[0.594s]
[INFO]
------------------------------------------------------------------------
[INFO]
------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO]
------------------------------------------------------------------------
[INFO] Total time: 50 seconds
[INFO] Finished at: Wed Apr 04 19:23:58 PDT 2007
[INFO] Final Memory: 28M/115M
[INFO]
------------------------------------------------------------------------
This is just a subset of the whole SCA tree, more work is required to
bring up the remaining pieces, in particular:
- the core runtime
- the contribution service implementation
- the SDO, JaxB and SDO-Axiom databinding
- the various Axis2, JMS, RMI etc. bindings
- The support for JMX management and the discovery/JMS
- the Spring implementation support
Our integration tests are under java/sca/itest but not included in the
build yet, as we need to get the above modules building first.
The java/sca/samples directory is currently empty. The work to bring
them up and get them to at least compile could be done in parallel if
people are interested in helping out with that.
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Build update, was: SCA source tree and build structure
Posted by Luciano Resende <lu...@gmail.com>.
I have added the Contribution Service implementation to the build.
On 4/4/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> Jean-Sebastien Delfino wrote:
> > Venkata Krishnan wrote:
> >> Hi,
> >>
> >> Yes, what Luciano is suggesting here makes sense to me as well.
> >>
> >> Thanks
> >>
> >> - Venkat
> >>
> >> On 4/4/07, Luciano Resende <lu...@gmail.com> wrote:
> >>>
> >>> Sebastien wrote:
> >>> > I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
> >>> alpha1 is
> >>> >probably better. I'll start with alpha1 then.
> >>>
> >>> Should we leave like 1.0-incubating-SNAPSHOT, and only add M3 or
> alpha1
> >>> when
> >>> we branch/tag for release, together with the removal of SNAPSHOT ?
> This
> >>> would make trunk always with same version id, right ?
> >>>
> >>> On 4/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >>> >
> >>> > [snip]
> >>> > Raymond Feng wrote:
> >>> > > Forgot to ask one question:
> >>> > >
> >>> > > We have inconsistent version ids for artifacts in the trunk, do
> you
> >>> > > plan to reconcile them? If so, what should the version id look
> >>> like? I
> >>> > > propose that we use something like
> >>> 1.0-incubating-alpha1-SNAPSHOT to
> >>> > > reflect the fact that we're working toward a 1.0 release.
> >>> > >
> >>> > > Thanks,
> >>> > > Raymond
> >>> > >
> >>> >
> >>> > Yes I plan to reconcile them, like this:
> >>> >
> >>> > >
> >>> > >> - Version of our modules will be specified once in
> >>> java/sca/pom.xml,
> >>> > >> child poms don't need specify a version as they get it from their
> >>> > parent
> >>> > >>
> >>> >
> >>> > I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
> >>> alpha1 is
> >>> > probably better. I'll start with alpha1 then.
> >>> >
> >>> > --
> >>> > 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
> >>> http://people.apache.org/~lresende
> >>>
> >>
> >
> > OK then, it makes sense to me too, I'll change to
> > 1.0-incubating-SNAPSHOT.
> >
>
> Here's an update on the progress with the new build structure.
>
> To build the sca tree, you should now be able to do the following:
> cd tuscany/java/sca
> mvn
> and get the following output.
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Apache Tuscany Project Parent ......................... SUCCESS
> [1.356s]
> [INFO] Apache Tuscany Build Tools ............................ SUCCESS
> [0.975s]
> [INFO] SCA API Version 1.0 ................................... SUCCESS
> [0.900s]
> [INFO] Apache Tuscany SCA Implementation Project ............. SUCCESS
> [0.033s]
> [INFO] Apache Tuscany SCA Implementation Modules ............. SUCCESS
> [0.044s]
> [INFO] Apache Tuscany Interface Model ........................ SUCCESS
> [0.972s]
> [INFO] Apache Tuscany Policy Model ........................... SUCCESS
> [1.206s]
> [INFO] Apache Tuscany Assembly Model ......................... SUCCESS
> [2.266s]
> [INFO] Apache Tuscany SCA Contribution Service ............... SUCCESS
> [1.134s]
> [INFO] Apache Tuscany SCA XML Assembly Support ............... SUCCESS
> [2.860s]
> [INFO] Apache Tuscany DataBinding Framework .................. SUCCESS
> [4.500s]
> [INFO] Apache Tuscany Data Binding for Axiom ................. SUCCESS
> [1.746s]
> [INFO] Apache Tuscany HTTP Servlet Host ...................... SUCCESS
> [0.331s]
> [INFO] Apache Tuscany Jetty HTTP Service ..................... SUCCESS
> [4.493s]
> [INFO] Apache Tuscany Tomcat HTTP Service .................... SUCCESS
> [2.545s]
> [INFO] Apache Tuscany Java Interface Model ................... SUCCESS
> [0.687s]
> [INFO] Apache Tuscany SCA XML Java Interface Extension ....... SUCCESS
> [1.365s]
> [INFO] Apache Tuscany WSDL Interface Model ................... SUCCESS
> [0.750s]
> [INFO] Apache Tuscany SCA XML WSDL Interface Extension ....... SUCCESS
> [1.383s]
> [INFO] Apache Tuscany Java Implementation Model .............. SUCCESS
> [0.823s]
> [INFO] Apache Tuscany SCA XML Java Implementation Extension .. SUCCESS
> [1.436s]
> [INFO] Apache Tuscany Axis2 Java2WSDL Tool ................... SUCCESS
> [9.311s]
> [INFO] Apache Tuscany Maven Plugin for Java2WSDL ............. SUCCESS
> [1.400s]
> [INFO] Apache Tuscany Axis2 WSDL2Java Tool ................... SUCCESS
> [6.734s]
> [INFO] Apache Tuscany Maven Plugin for WSDL2Java ............. SUCCESS
> [0.594s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 50 seconds
> [INFO] Finished at: Wed Apr 04 19:23:58 PDT 2007
> [INFO] Final Memory: 28M/115M
> [INFO]
> ------------------------------------------------------------------------
>
> This is just a subset of the whole SCA tree, more work is required to
> bring up the remaining pieces, in particular:
> - the core runtime
> - the contribution service implementation
> - the SDO, JaxB and SDO-Axiom databinding
> - the various Axis2, JMS, RMI etc. bindings
> - The support for JMX management and the discovery/JMS
> - the Spring implementation support
>
> Our integration tests are under java/sca/itest but not included in the
> build yet, as we need to get the above modules building first.
>
> The java/sca/samples directory is currently empty. The work to bring
> them up and get them to at least compile could be done in parallel if
> people are interested in helping out with that.
>
> --
> 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
http://people.apache.org/~lresende
Re: Moving spec/sca-api module under sca? was: Build update
Posted by Luciano Resende <lu...@gmail.com>.
Ok then, let's move to the modules directory for now, as we will need to
release it anyway on our next release. When the time arrives and we need to
re think the spec module location, then we revisit the case.
On 4/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> [snip]
> Luciano Resende wrote:
> > But we probably want to release 2 things, sca-spec and sca, right ?
> > and then
> > in subsequent releases of sca, we are only going to release sca,
> > unless the
> > spec changes and we need to update sca-spec jar.
> >
> >
> [snip]
> >>
> >>
> >> I could be convinced, but I'm not sure I understand yet :)
> >>
> >> Aren't we going to release an sca-api JAR in our next
> >> tuscany-incubating-xyz.tar.gz?
> >>
> >> --
> >> Jean-Sebastien
> >>
> >>
>
> I'm still confused :) Let's imagine for illustration purposes that we
> have 2 alpha releases, alpha1 and alpha2. I am assuming that:
> tuscany-incubating-1.0-alpha1.tar.gz will contain an sca-api JAR from a
> specific SVN revision, let's say X
> tuscany-incubating-1.0-alpha2.tar.gz will contain an sca-api JAR from an
> SVN revision Y
> where the sca-api JAR is just the API provided to application developers
> for one the many component implementation types that we want to support,
> POJO component implementations in this case.
>
> Is there a reason why we'd want to single this JAR out and force POJO
> component developers to get this one (and only this one) from a
> different distribution than tuscany-incubating.tar.gz?
>
> Also, perhaps SVN revision X will be the same revision as Y, or not...
> we can't really predict that, as we may find bugs in the spec interfaces
> or their javadocs. But isn't the same true for any other module in our
> distribution? Why would we want to handle the release of sca-api JAR
> differently?
>
> --
> 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
http://people.apache.org/~lresende
Re: Moving spec/sca-api module under sca? was: Build update
Posted by Jean-Sebastien Delfino <js...@apache.org>.
[snip]
Luciano Resende wrote:
> But we probably want to release 2 things, sca-spec and sca, right ?
> and then
> in subsequent releases of sca, we are only going to release sca,
> unless the
> spec changes and we need to update sca-spec jar.
>
>
[snip]
>>
>>
>> I could be convinced, but I'm not sure I understand yet :)
>>
>> Aren't we going to release an sca-api JAR in our next
>> tuscany-incubating-xyz.tar.gz?
>>
>> --
>> Jean-Sebastien
>>
>>
I'm still confused :) Let's imagine for illustration purposes that we
have 2 alpha releases, alpha1 and alpha2. I am assuming that:
tuscany-incubating-1.0-alpha1.tar.gz will contain an sca-api JAR from a
specific SVN revision, let's say X
tuscany-incubating-1.0-alpha2.tar.gz will contain an sca-api JAR from an
SVN revision Y
where the sca-api JAR is just the API provided to application developers
for one the many component implementation types that we want to support,
POJO component implementations in this case.
Is there a reason why we'd want to single this JAR out and force POJO
component developers to get this one (and only this one) from a
different distribution than tuscany-incubating.tar.gz?
Also, perhaps SVN revision X will be the same revision as Y, or not...
we can't really predict that, as we may find bugs in the spec interfaces
or their javadocs. But isn't the same true for any other module in our
distribution? Why would we want to handle the release of sca-api JAR
differently?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Moving spec/sca-api module under sca? was: Build update
Posted by Luciano Resende <lu...@gmail.com>.
But we probably want to release 2 things, sca-spec and sca, right ? and then
in subsequent releases of sca, we are only going to release sca, unless the
spec changes and we need to update sca-spec jar.
On 4/5/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
>
> Raymond Feng wrote:
> > Good points. I agree it's probably better to keep it at sca/spec level.
> >
> > Thanks,
> > Raymond
> >
> > ----- Original Message ----- From: "Venkata Krishnan"
> > <fo...@gmail.com>
> > To: <tu...@ws.apache.org>
> > Sent: Thursday, April 05, 2007 10:15 AM
> > Subject: Re: Build update, was: SCA source tree and build structure
> >
> >
> >> Yes and I very faintly remember this to be the reason why we moved
> >> the specs
> >> out to where it is now. Isn't it ?
> >>
> >> - Venkat
> >>
> >> On 4/5/07, Luciano Resende <lu...@gmail.com> wrote:
> >>>
> >>> I was under the impression that the spec-sca-api-r1.0 module would be
> a
> >>> stable one unless the spec changes. Isn't right that, under spec/ we
> >>> can
> >>> have multiple sca releases based on the same spec-sca-api-r1.0, but
> >>> moving
> >>> it to /modules we will be forced to have a spec api release every
> >>> time we
> >>> release sca ?
> >>>
> >>> On 4/5/07, Raymond Feng <en...@gmail.com> wrote:
> >>> >
> >>> > Hi,
> >>> >
> >>> > For SCA, I suggest that we further move it to >
> >>> "modules/spec-sca-api-r1.0
> >>> ".
> >>> >
> >>> > Thanks,
> >>> > Raymond
> >>> >
> >>> > ----- Original Message -----
> >>> > From: "Jean-Sebastien Delfino" <js...@apache.org>
> >>> > To: <tu...@ws.apache.org>
> >>> > Sent: Thursday, April 05, 2007 8:36 AM
> >>> > Subject: Re: Build update, was: SCA source tree and build structure
> >>> >
> >>> >
> >>> > > Bert Lamb wrote:
> >>> > >> Just to note, in order for this build to work from a fresh empty
> >>> maven
> >>> > >> local repo, you'll need to run "mvn" from the > >>
> >>> /java/spec/sca-api-r1.0
> >>> /
> >>> > >> directory first.
> >>> > >>
> >>> > >> -Bert
> >>> > >>
> >>> > >
> >>> > > Good point. I had forgotten to commit my change to
> >>> java/sca/pom.xml > > to
> >>> > > include the spec-api in the top-down build. It's now fixed in >
> >>> > revision
> >>> > > r525846.
> >>> > >
> >>> > > Also, I'm not sure it's obvious to everybody that the SCA API is
> >>> hiding
> >>> > > under java/spec instead of being under the java/sca folder.
> Similar
> >>> > > comment for the SDO API.
> >>> > >
> >>> > > How about moving java/spec/sca-api-r1.0 to java/sca and
> >>> > > java/spec/sdo-api to java/sdo as well?
> >>> > >
> >>> > > Thoughts?
> >>> > >
> >>> > > --
> >>> > > Jean-Sebastien
> >>> > >
> >>> > >
>
> I could be convinced, but I'm not sure I understand yet :)
>
> Aren't we going to release an sca-api JAR in our next
> tuscany-incubating-xyz.tar.gz?
>
> --
> 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
http://people.apache.org/~lresende
Moving spec/sca-api module under sca? was: Build update
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Raymond Feng wrote:
> Good points. I agree it's probably better to keep it at sca/spec level.
>
> Thanks,
> Raymond
>
> ----- Original Message ----- From: "Venkata Krishnan"
> <fo...@gmail.com>
> To: <tu...@ws.apache.org>
> Sent: Thursday, April 05, 2007 10:15 AM
> Subject: Re: Build update, was: SCA source tree and build structure
>
>
>> Yes and I very faintly remember this to be the reason why we moved
>> the specs
>> out to where it is now. Isn't it ?
>>
>> - Venkat
>>
>> On 4/5/07, Luciano Resende <lu...@gmail.com> wrote:
>>>
>>> I was under the impression that the spec-sca-api-r1.0 module would be a
>>> stable one unless the spec changes. Isn't right that, under spec/ we
>>> can
>>> have multiple sca releases based on the same spec-sca-api-r1.0, but
>>> moving
>>> it to /modules we will be forced to have a spec api release every
>>> time we
>>> release sca ?
>>>
>>> On 4/5/07, Raymond Feng <en...@gmail.com> wrote:
>>> >
>>> > Hi,
>>> >
>>> > For SCA, I suggest that we further move it to >
>>> "modules/spec-sca-api-r1.0
>>> ".
>>> >
>>> > Thanks,
>>> > Raymond
>>> >
>>> > ----- Original Message -----
>>> > From: "Jean-Sebastien Delfino" <js...@apache.org>
>>> > To: <tu...@ws.apache.org>
>>> > Sent: Thursday, April 05, 2007 8:36 AM
>>> > Subject: Re: Build update, was: SCA source tree and build structure
>>> >
>>> >
>>> > > Bert Lamb wrote:
>>> > >> Just to note, in order for this build to work from a fresh empty
>>> maven
>>> > >> local repo, you'll need to run "mvn" from the > >>
>>> /java/spec/sca-api-r1.0
>>> /
>>> > >> directory first.
>>> > >>
>>> > >> -Bert
>>> > >>
>>> > >
>>> > > Good point. I had forgotten to commit my change to
>>> java/sca/pom.xml > > to
>>> > > include the spec-api in the top-down build. It's now fixed in >
>>> > revision
>>> > > r525846.
>>> > >
>>> > > Also, I'm not sure it's obvious to everybody that the SCA API is
>>> hiding
>>> > > under java/spec instead of being under the java/sca folder. Similar
>>> > > comment for the SDO API.
>>> > >
>>> > > How about moving java/spec/sca-api-r1.0 to java/sca and
>>> > > java/spec/sdo-api to java/sdo as well?
>>> > >
>>> > > Thoughts?
>>> > >
>>> > > --
>>> > > Jean-Sebastien
>>> > >
>>> > >
I could be convinced, but I'm not sure I understand yet :)
Aren't we going to release an sca-api JAR in our next
tuscany-incubating-xyz.tar.gz?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Build update, was: SCA source tree and build structure
Posted by Raymond Feng <en...@gmail.com>.
Good points. I agree it's probably better to keep it at sca/spec level.
Thanks,
Raymond
----- Original Message -----
From: "Venkata Krishnan" <fo...@gmail.com>
To: <tu...@ws.apache.org>
Sent: Thursday, April 05, 2007 10:15 AM
Subject: Re: Build update, was: SCA source tree and build structure
> Yes and I very faintly remember this to be the reason why we moved the
> specs
> out to where it is now. Isn't it ?
>
> - Venkat
>
> On 4/5/07, Luciano Resende <lu...@gmail.com> wrote:
>>
>> I was under the impression that the spec-sca-api-r1.0 module would be a
>> stable one unless the spec changes. Isn't right that, under spec/ we can
>> have multiple sca releases based on the same spec-sca-api-r1.0, but
>> moving
>> it to /modules we will be forced to have a spec api release every time we
>> release sca ?
>>
>> On 4/5/07, Raymond Feng <en...@gmail.com> wrote:
>> >
>> > Hi,
>> >
>> > For SCA, I suggest that we further move it to
>> > "modules/spec-sca-api-r1.0
>> ".
>> >
>> > Thanks,
>> > Raymond
>> >
>> > ----- Original Message -----
>> > From: "Jean-Sebastien Delfino" <js...@apache.org>
>> > To: <tu...@ws.apache.org>
>> > Sent: Thursday, April 05, 2007 8:36 AM
>> > Subject: Re: Build update, was: SCA source tree and build structure
>> >
>> >
>> > > Bert Lamb wrote:
>> > >> Just to note, in order for this build to work from a fresh empty
>> maven
>> > >> local repo, you'll need to run "mvn" from the
>> > >> /java/spec/sca-api-r1.0
>> /
>> > >> directory first.
>> > >>
>> > >> -Bert
>> > >>
>> > >
>> > > Good point. I had forgotten to commit my change to java/sca/pom.xml
>> > > to
>> > > include the spec-api in the top-down build. It's now fixed in
>> > > revision
>> > > r525846.
>> > >
>> > > Also, I'm not sure it's obvious to everybody that the SCA API is
>> hiding
>> > > under java/spec instead of being under the java/sca folder. Similar
>> > > comment for the SDO API.
>> > >
>> > > How about moving java/spec/sca-api-r1.0 to java/sca and
>> > > java/spec/sdo-api to java/sdo as well?
>> > >
>> > > Thoughts?
>> > >
>> > > --
>> > > Jean-Sebastien
>> > >
>> > >
>> > > ---------------------------------------------------------------------
>> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> > >
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
>> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>> >
>> >
>>
>>
>> --
>> Luciano Resende
>> http://people.apache.org/~lresende
>>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Build update, was: SCA source tree and build structure
Posted by Venkata Krishnan <fo...@gmail.com>.
Yes and I very faintly remember this to be the reason why we moved the specs
out to where it is now. Isn't it ?
- Venkat
On 4/5/07, Luciano Resende <lu...@gmail.com> wrote:
>
> I was under the impression that the spec-sca-api-r1.0 module would be a
> stable one unless the spec changes. Isn't right that, under spec/ we can
> have multiple sca releases based on the same spec-sca-api-r1.0, but moving
> it to /modules we will be forced to have a spec api release every time we
> release sca ?
>
> On 4/5/07, Raymond Feng <en...@gmail.com> wrote:
> >
> > Hi,
> >
> > For SCA, I suggest that we further move it to "modules/spec-sca-api-r1.0
> ".
> >
> > Thanks,
> > Raymond
> >
> > ----- Original Message -----
> > From: "Jean-Sebastien Delfino" <js...@apache.org>
> > To: <tu...@ws.apache.org>
> > Sent: Thursday, April 05, 2007 8:36 AM
> > Subject: Re: Build update, was: SCA source tree and build structure
> >
> >
> > > Bert Lamb wrote:
> > >> Just to note, in order for this build to work from a fresh empty
> maven
> > >> local repo, you'll need to run "mvn" from the /java/spec/sca-api-r1.0
> /
> > >> directory first.
> > >>
> > >> -Bert
> > >>
> > >
> > > Good point. I had forgotten to commit my change to java/sca/pom.xml to
> > > include the spec-api in the top-down build. It's now fixed in revision
> > > r525846.
> > >
> > > Also, I'm not sure it's obvious to everybody that the SCA API is
> hiding
> > > under java/spec instead of being under the java/sca folder. Similar
> > > comment for the SDO API.
> > >
> > > How about moving java/spec/sca-api-r1.0 to java/sca and
> > > java/spec/sdo-api to java/sdo as well?
> > >
> > > Thoughts?
> > >
> > > --
> > > Jean-Sebastien
> > >
> > >
> > > ---------------------------------------------------------------------
> > > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> > >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
> >
>
>
> --
> Luciano Resende
> http://people.apache.org/~lresende
>
Re: Build update, was: SCA source tree and build structure
Posted by Luciano Resende <lu...@gmail.com>.
I was under the impression that the spec-sca-api-r1.0 module would be a
stable one unless the spec changes. Isn't right that, under spec/ we can
have multiple sca releases based on the same spec-sca-api-r1.0, but moving
it to /modules we will be forced to have a spec api release every time we
release sca ?
On 4/5/07, Raymond Feng <en...@gmail.com> wrote:
>
> Hi,
>
> For SCA, I suggest that we further move it to "modules/spec-sca-api-r1.0".
>
> Thanks,
> Raymond
>
> ----- Original Message -----
> From: "Jean-Sebastien Delfino" <js...@apache.org>
> To: <tu...@ws.apache.org>
> Sent: Thursday, April 05, 2007 8:36 AM
> Subject: Re: Build update, was: SCA source tree and build structure
>
>
> > Bert Lamb wrote:
> >> Just to note, in order for this build to work from a fresh empty maven
> >> local repo, you'll need to run "mvn" from the /java/spec/sca-api-r1.0/
> >> directory first.
> >>
> >> -Bert
> >>
> >
> > Good point. I had forgotten to commit my change to java/sca/pom.xml to
> > include the spec-api in the top-down build. It's now fixed in revision
> > r525846.
> >
> > Also, I'm not sure it's obvious to everybody that the SCA API is hiding
> > under java/spec instead of being under the java/sca folder. Similar
> > comment for the SDO API.
> >
> > How about moving java/spec/sca-api-r1.0 to java/sca and
> > java/spec/sdo-api to java/sdo as well?
> >
> > Thoughts?
> >
> > --
> > Jean-Sebastien
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> > For additional commands, e-mail: tuscany-dev-help@ws.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
--
Luciano Resende
http://people.apache.org/~lresende
Re: Build update, was: SCA source tree and build structure
Posted by Raymond Feng <en...@gmail.com>.
Hi,
For SCA, I suggest that we further move it to "modules/spec-sca-api-r1.0".
Thanks,
Raymond
----- Original Message -----
From: "Jean-Sebastien Delfino" <js...@apache.org>
To: <tu...@ws.apache.org>
Sent: Thursday, April 05, 2007 8:36 AM
Subject: Re: Build update, was: SCA source tree and build structure
> Bert Lamb wrote:
>> Just to note, in order for this build to work from a fresh empty maven
>> local repo, you'll need to run "mvn" from the /java/spec/sca-api-r1.0/
>> directory first.
>>
>> -Bert
>>
>
> Good point. I had forgotten to commit my change to java/sca/pom.xml to
> include the spec-api in the top-down build. It's now fixed in revision
> r525846.
>
> Also, I'm not sure it's obvious to everybody that the SCA API is hiding
> under java/spec instead of being under the java/sca folder. Similar
> comment for the SDO API.
>
> How about moving java/spec/sca-api-r1.0 to java/sca and
> java/spec/sdo-api to java/sdo as well?
>
> Thoughts?
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Build update, was: SCA source tree and build structure
Posted by Jean-Sebastien Delfino <js...@apache.org>.
Bert Lamb wrote:
> Just to note, in order for this build to work from a fresh empty maven
> local repo, you'll need to run "mvn" from the /java/spec/sca-api-r1.0/
> directory first.
>
> -Bert
>
Good point. I had forgotten to commit my change to java/sca/pom.xml to
include the spec-api in the top-down build. It's now fixed in revision
r525846.
Also, I'm not sure it's obvious to everybody that the SCA API is hiding
under java/spec instead of being under the java/sca folder. Similar
comment for the SDO API.
How about moving java/spec/sca-api-r1.0 to java/sca and
java/spec/sdo-api to java/sdo as well?
Thoughts?
--
Jean-Sebastien
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org
Re: Build update, was: SCA source tree and build structure
Posted by Bert Lamb <al...@pobox.com>.
Just to note, in order for this build to work from a fresh empty maven
local repo, you'll need to run "mvn" from the /java/spec/sca-api-r1.0/
directory first.
-Bert
On 4/4/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> Jean-Sebastien Delfino wrote:
> > Venkata Krishnan wrote:
> >> Hi,
> >>
> >> Yes, what Luciano is suggesting here makes sense to me as well.
> >>
> >> Thanks
> >>
> >> - Venkat
> >>
> >> On 4/4/07, Luciano Resende <lu...@gmail.com> wrote:
> >>>
> >>> Sebastien wrote:
> >>> > I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
> >>> alpha1 is
> >>> >probably better. I'll start with alpha1 then.
> >>>
> >>> Should we leave like 1.0-incubating-SNAPSHOT, and only add M3 or alpha1
> >>> when
> >>> we branch/tag for release, together with the removal of SNAPSHOT ? This
> >>> would make trunk always with same version id, right ?
> >>>
> >>> On 4/3/07, Jean-Sebastien Delfino <js...@apache.org> wrote:
> >>> >
> >>> > [snip]
> >>> > Raymond Feng wrote:
> >>> > > Forgot to ask one question:
> >>> > >
> >>> > > We have inconsistent version ids for artifacts in the trunk, do you
> >>> > > plan to reconcile them? If so, what should the version id look
> >>> like? I
> >>> > > propose that we use something like
> >>> 1.0-incubating-alpha1-SNAPSHOT to
> >>> > > reflect the fact that we're working toward a 1.0 release.
> >>> > >
> >>> > > Thanks,
> >>> > > Raymond
> >>> > >
> >>> >
> >>> > Yes I plan to reconcile them, like this:
> >>> >
> >>> > >
> >>> > >> - Version of our modules will be specified once in
> >>> java/sca/pom.xml,
> >>> > >> child poms don't need specify a version as they get it from their
> >>> > parent
> >>> > >>
> >>> >
> >>> > I was initially thinking about 1.0-incubating-M3-SNAPSHOT, but
> >>> alpha1 is
> >>> > probably better. I'll start with alpha1 then.
> >>> >
> >>> > --
> >>> > 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
> >>> http://people.apache.org/~lresende
> >>>
> >>
> >
> > OK then, it makes sense to me too, I'll change to
> > 1.0-incubating-SNAPSHOT.
> >
>
> Here's an update on the progress with the new build structure.
>
> To build the sca tree, you should now be able to do the following:
> cd tuscany/java/sca
> mvn
> and get the following output.
>
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Reactor Summary:
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Apache Tuscany Project Parent ......................... SUCCESS
> [1.356s]
> [INFO] Apache Tuscany Build Tools ............................ SUCCESS
> [0.975s]
> [INFO] SCA API Version 1.0 ................................... SUCCESS
> [0.900s]
> [INFO] Apache Tuscany SCA Implementation Project ............. SUCCESS
> [0.033s]
> [INFO] Apache Tuscany SCA Implementation Modules ............. SUCCESS
> [0.044s]
> [INFO] Apache Tuscany Interface Model ........................ SUCCESS
> [0.972s]
> [INFO] Apache Tuscany Policy Model ........................... SUCCESS
> [1.206s]
> [INFO] Apache Tuscany Assembly Model ......................... SUCCESS
> [2.266s]
> [INFO] Apache Tuscany SCA Contribution Service ............... SUCCESS
> [1.134s]
> [INFO] Apache Tuscany SCA XML Assembly Support ............... SUCCESS
> [2.860s]
> [INFO] Apache Tuscany DataBinding Framework .................. SUCCESS
> [4.500s]
> [INFO] Apache Tuscany Data Binding for Axiom ................. SUCCESS
> [1.746s]
> [INFO] Apache Tuscany HTTP Servlet Host ...................... SUCCESS
> [0.331s]
> [INFO] Apache Tuscany Jetty HTTP Service ..................... SUCCESS
> [4.493s]
> [INFO] Apache Tuscany Tomcat HTTP Service .................... SUCCESS
> [2.545s]
> [INFO] Apache Tuscany Java Interface Model ................... SUCCESS
> [0.687s]
> [INFO] Apache Tuscany SCA XML Java Interface Extension ....... SUCCESS
> [1.365s]
> [INFO] Apache Tuscany WSDL Interface Model ................... SUCCESS
> [0.750s]
> [INFO] Apache Tuscany SCA XML WSDL Interface Extension ....... SUCCESS
> [1.383s]
> [INFO] Apache Tuscany Java Implementation Model .............. SUCCESS
> [0.823s]
> [INFO] Apache Tuscany SCA XML Java Implementation Extension .. SUCCESS
> [1.436s]
> [INFO] Apache Tuscany Axis2 Java2WSDL Tool ................... SUCCESS
> [9.311s]
> [INFO] Apache Tuscany Maven Plugin for Java2WSDL ............. SUCCESS
> [1.400s]
> [INFO] Apache Tuscany Axis2 WSDL2Java Tool ................... SUCCESS
> [6.734s]
> [INFO] Apache Tuscany Maven Plugin for WSDL2Java ............. SUCCESS
> [0.594s]
> [INFO]
> ------------------------------------------------------------------------
> [INFO]
> ------------------------------------------------------------------------
> [INFO] BUILD SUCCESSFUL
> [INFO]
> ------------------------------------------------------------------------
> [INFO] Total time: 50 seconds
> [INFO] Finished at: Wed Apr 04 19:23:58 PDT 2007
> [INFO] Final Memory: 28M/115M
> [INFO]
> ------------------------------------------------------------------------
>
> This is just a subset of the whole SCA tree, more work is required to
> bring up the remaining pieces, in particular:
> - the core runtime
> - the contribution service implementation
> - the SDO, JaxB and SDO-Axiom databinding
> - the various Axis2, JMS, RMI etc. bindings
> - The support for JMX management and the discovery/JMS
> - the Spring implementation support
>
> Our integration tests are under java/sca/itest but not included in the
> build yet, as we need to get the above modules building first.
>
> The java/sca/samples directory is currently empty. The work to bring
> them up and get them to at least compile could be done in parallel if
> people are interested in helping out with that.
>
> --
> Jean-Sebastien
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
> For additional commands, e-mail: tuscany-dev-help@ws.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: tuscany-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: tuscany-dev-help@ws.apache.org