You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by Mark Combellack <mc...@apache.org> on 2009/01/26 11:21:07 UTC
[2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790
Hi,
Recently, the OASIS SCA-J committee agreed to change the package name from
org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
raised as TUSCANY-2790.
I would like to start working on changing the package name to
org.oasisopen.sca on the 2.x root. However, I realise that this could be a
rather disruptive change especially if we are planning to release M1.
How do people feel about me attempting this change later this week or early
next?
Thanks,
Mark
[1] https://issues.apache.org/jira/browse/TUSCANY-2790
RE: [2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790
Posted by Mark Combellack <mc...@apache.org>.
Hi Simon,
In one of the recent OASIS SCA-J meeting (23rd January), we agreed to change
the package name to org.oasisopen.sca.annotation to be consistent with
Java's use of java.lang.annotation. I thought I would make this change at
the same time as moving to org.oasisopen.
See http://www.osoa.org/jira/browse/JAVA-120 for more details.
I don't believe this change has yet made it into any of the SCA-J released
documents but it is being worked on at the moment. Hopefully, an updated
document will be out fairly soon.
Thanks,
Mark
_____
From: Simon Laws [mailto:simonslaws@googlemail.com]
Sent: 29 January 2009 11:20
To: dev@tuscany.apache.org
Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
On Wed, Jan 28, 2009 at 4:55 PM, Raymond Feng <en...@gmail.com> wrote:
Hi, Mark.
Thank you for doing this. Now we are the journey to the OASIS Smile
emoticon.
BTW, what about the license header for the OASIS APIs?
Thanks,
Raymond
From: Mark <ma...@apache.org> Combellack
Sent: Wednesday, January 28, 2009 6:14 AM
To: 'Luciano <ma...@gmail.com> Resende'
Cc: Simon Laws <ma...@googlemail.com> ; dev@tuscany.apache.org
Subject: RE: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
Hi Luciano,
I have just committed the change of package name back into the 2.x version
of Tuscany as SVN revision 738490.
The change involved:
* Changing package org.osoa.sca to org.oasisopen.sca
* Changing package org.osoa.sca.annotations to
org.oasisopen.sca.annotation
* Updating all references in the 2.x branch so they use
org.oasisopen
The branch mostly builds with this change. The following projects do not
build. Note: I had these problems before the package name changes so I don't
believe my change has caused it:
* Apache Tuscany SCA Web Service Distribution
* Apache Tuscany SCA Binding WS Calculator Sample
* Apache Tuscany SCA Host Webapp Calculator Sample
* Apache Tuscany SCA All-in-one Distribution
* Apache Tuscany SCA PDE Target Platform Distribution
(See full error log below)
Hopefully, I have made all the changes that are needed. Apologies if I have
missed/broken anything.
Thanks,
Mark
[INFO] Apache Tuscany SCA Web Service Distribution ........... FAILED
[0.487s]
[INFO] Apache Tuscany SCA Binding WS Calculator Sample ....... SKIPPED
(dependency build failed or was skipped)
[INFO] Apache Tuscany SCA Host Webapp Calculator Sample ...... SKIPPED
(dependency build failed or was skipped)
[INFO] Apache Tuscany SCA All-in-one Distribution ............ SKIPPED
(dependency build failed or was skipped)
[INFO] Apache Tuscany SCA PDE Target Platform Distribution ... SKIPPED
(dependency build failed or was skipped)
[INFO]
------------------------------------------------------------------------
[INFO] Error for project: Apache Tuscany SCA Web Service Distribution
(during install)
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
----------
2 required artifacts are missing.
for artifact:
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.ws.zone (http://ws.zones.apache.org/repository2),
apache.incubator (http://people.apache.org/repo/m2-incubating-repository),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
osuosl.org (http://ftp.osuosl.org/pub/eclipse/tools/emf/maven2),
indiana (http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/)
> -----Original Message-----
> From: Luciano Resende [mailto:luckbr1975@gmail.com]
> Sent: 27 January 2009 00:20
> To: dev@tuscany.apache.org; mcombellack@apache.org
> Cc: Simon Laws
> Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-
> J specification - TUSCANY-2790
>
> Mark,
>
> What's the time frame you have in mind to get these changes in ?
> Just trying to check if this would be available for M1 or not.
>
> On Mon, Jan 26, 2009 at 2:55 AM, Mark Combellack <mc...@apache.org>
> wrote:
> > Hi Simon,
> >
> >
> >
> > The OASIA SCA specification does not provide any "binary" backwards
> > compatibility with OSOA code. This means that all OSOA code would need
> to be
> > updated to work with an OASIS Open SCA runtime.
> >
> >
> >
> > The way that I see it working is that OSOA code would be supported on
> > Tuscany 1.x releases and OASIS Open code would be supported on the
> Tuscany
> > 2.x releases. Ideally, at some point in the future, we would provide
> some
> > tooling support along with Tuscany 2.x that would help developers
> convert
> > 1.x applications to 2.x applications.
> >
> >
> >
> > Currently, I feel that adding support for both the OSOA and OASIS Open
> > applications to the 2.x codebase would add considerable complexity so I
> > would prefer not to do it at this time.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> > ________________________________
> >
> > From: Simon Laws [mailto:simonslaws@googlemail.com]
> > Sent: 26 January 2009 10:38
> > To: dev@tuscany.apache.org; mcombellack@apache.org
> > Subject: Re: [2.x] Updating the package names to match the OASIS Open
> SCA-J
> > specification - TUSCANY-2790
> >
> >
> >
> >
> >
> > On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack
> <mc...@apache.org>
> > wrote:
> >
> > Hi,
> >
> >
> >
> > Recently, the OASIS SCA-J committee agreed to change the package name
> from
> > org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
> > raised as TUSCANY-2790.
> >
> >
> >
> > I would like to start working on changing the package name to
> > org.oasisopen.sca on the 2.x root. However, I realise that this could be
> a
> > rather disruptive change especially if we are planning to release M1.
> >
> >
> >
> > How do people feel about me attempting this change later this week or
> early
> > next?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/TUSCANY-2790
> >
> >
> >
> >
> >
> >
> >
> > Hi Mark
> >
> > Is the proposal to change what is there or to add a new modules
> alongside
> > what is there with the new package names.
> >
> > To ask the question another way. Do we expect that 2.x will support 1.x
> > compatible applications also. It would be very nice if backward
> > compatibility were provided but it adds complexity.
> >
> > Simon
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende <http://people.apache.org/%7Elresende>
> http://lresende.blogspot.com/
Hi Mark
Should it be
org.oasisopen.sca.annotation
or
org.oasisopen.sca.annotations
Looking at the latest Javacaa spec it looks like
"org.oasisopen.sca.annotations" is used but I expect I'm just not bang up to
date with the TC.
Regards
Simon
Re: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
Posted by Simon Laws <si...@googlemail.com>.
On Wed, Jan 28, 2009 at 4:55 PM, Raymond Feng <en...@gmail.com> wrote:
> Hi, Mark.
>
> Thank you for doing this. Now we are the journey to the OASIS [image:
> Smile emoticon].
>
> BTW, what about the license header for the OASIS APIs?
>
> Thanks,
> Raymond
>
> *From:* Mark Combellack <mc...@apache.org>
> *Sent:* Wednesday, January 28, 2009 6:14 AM
> *To:* 'Luciano Resende' <lu...@gmail.com>
> *Cc:* Simon Laws <si...@googlemail.com> ; dev@tuscany.apache.org
> *Subject:* RE: [2.x] Updating the package names to match the OASIS Open
> SCA-J specification - TUSCANY-2790
>
> Hi Luciano,
>
>
>
> I have just committed the change of package name back into the 2.x version
> of Tuscany as SVN revision 738490.
>
>
>
> The change involved:
>
>
>
> · Changing package org.osoa.sca to org.oasisopen.sca
>
> · Changing package org.osoa.sca.annotations to
> org.oasisopen.sca.annotation
>
> · Updating all references in the 2.x branch so they use
> org.oasisopen
>
>
>
> The branch mostly builds with this change. The following projects do not
> build. Note: I had these problems before the package name changes so I don't
> believe my change has caused it:
>
>
>
> · Apache Tuscany SCA Web Service Distribution
>
> · Apache Tuscany SCA Binding WS Calculator Sample
>
> · Apache Tuscany SCA Host Webapp Calculator Sample
>
> · Apache Tuscany SCA All-in-one Distribution
>
> · Apache Tuscany SCA PDE Target Platform Distribution
>
>
>
> (See full error log below)
>
>
>
>
>
> Hopefully, I have made all the changes that are needed. Apologies if I have
> missed/broken anything.
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
>
>
>
>
>
>
> [INFO] Apache Tuscany SCA Web Service Distribution ........... FAILED
> [0.487s]
>
> [INFO] Apache Tuscany SCA Binding WS Calculator Sample ....... SKIPPED
> (dependency build failed or was skipped)
>
> [INFO] Apache Tuscany SCA Host Webapp Calculator Sample ...... SKIPPED
> (dependency build failed or was skipped)
>
> [INFO] Apache Tuscany SCA All-in-one Distribution ............ SKIPPED
> (dependency build failed or was skipped)
>
> [INFO] Apache Tuscany SCA PDE Target Platform Distribution ... SKIPPED
> (dependency build failed or was skipped)
>
>
>
>
>
>
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Error for project: Apache Tuscany SCA Web Service Distribution
> (during install)
>
> [INFO]
> ------------------------------------------------------------------------
>
> [INFO] Failed to resolve artifact.
>
>
>
> Missing:
>
> ----------
>
> 1) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
>
>
>
> Try downloading the file manually from the project website.
>
>
>
> Then, install it using the command:
>
> mvn install:install-file -DgroupId=org.apache.tuscany.sca
> -DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>
>
> Alternatively, if you host your own repository you can deploy the file
> there:
>
> mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca
> -DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
>
> Path to dependency:
>
> 1)
> org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
>
> 2) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
>
>
>
> 2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
>
>
>
> Try downloading the file manually from the project website.
>
>
>
> Then, install it using the command:
>
> mvn install:install-file -DgroupId=org.apache.tuscany.sca
> -DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file
>
>
>
> Alternatively, if you host your own repository you can deploy the file
> there:
>
> mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca
> -DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar
> -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
>
>
>
> Path to dependency:
>
> 1)
> org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
>
> 2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
>
>
>
> ----------
>
> 2 required artifacts are missing.
>
>
>
> for artifact:
>
> org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
>
>
>
> from the specified remote repositories:
>
> central (http://repo1.maven.org/maven2),
>
> apache.ws.zone (http://ws.zones.apache.org/repository2),
>
> apache.incubator (http://people.apache.org/repo/m2-incubating-repository
> ),
>
> apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
>
> osuosl.org (http://ftp.osuosl.org/pub/eclipse/tools/emf/maven2),
>
> indiana (http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/)
>
>
>
>
>
>
>
> > -----Original Message-----
>
> > From: Luciano Resende [mailto:luckbr1975@gmail.com]
>
> > Sent: 27 January 2009 00:20
>
> > To: dev@tuscany.apache.org; mcombellack@apache.org
>
> > Cc: Simon Laws
>
> > Subject: Re: [2.x] Updating the package names to match the OASIS Open
> SCA-
>
> > J specification - TUSCANY-2790
>
> >
>
> > Mark,
>
> >
>
> > What's the time frame you have in mind to get these changes in ?
>
> > Just trying to check if this would be available for M1 or not.
>
> >
>
> > On Mon, Jan 26, 2009 at 2:55 AM, Mark Combellack <mcombellack@apache.org
> >
>
> > wrote:
>
> > > Hi Simon,
>
> > >
>
> > >
>
> > >
>
> > > The OASIA SCA specification does not provide any "binary" backwards
>
> > > compatibility with OSOA code. This means that all OSOA code would need
>
> > to be
>
> > > updated to work with an OASIS Open SCA runtime.
>
> > >
>
> > >
>
> > >
>
> > > The way that I see it working is that OSOA code would be supported on
>
> > > Tuscany 1.x releases and OASIS Open code would be supported on the
>
> > Tuscany
>
> > > 2.x releases. Ideally, at some point in the future, we would provide
>
> > some
>
> > > tooling support along with Tuscany 2.x that would help developers
>
> > convert
>
> > > 1.x applications to 2.x applications.
>
> > >
>
> > >
>
> > >
>
> > > Currently, I feel that adding support for both the OSOA and OASIS Open
>
> > > applications to the 2.x codebase would add considerable complexity so I
>
> > > would prefer not to do it at this time.
>
> > >
>
> > >
>
> > >
>
> > > Thanks,
>
> > >
>
> > >
>
> > >
>
> > > Mark
>
> > >
>
> > >
>
> > >
>
> > > ________________________________
>
> > >
>
> > > From: Simon Laws [mailto:simonslaws@googlemail.com]
>
> > > Sent: 26 January 2009 10:38
>
> > > To: dev@tuscany.apache.org; mcombellack@apache.org
>
> > > Subject: Re: [2.x] Updating the package names to match the OASIS Open
>
> > SCA-J
>
> > > specification - TUSCANY-2790
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack
>
> > <mc...@apache.org>
>
> > > wrote:
>
> > >
>
> > > Hi,
>
> > >
>
> > >
>
> > >
>
> > > Recently, the OASIS SCA-J committee agreed to change the package name
>
> > from
>
> > > org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has
> been
>
> > > raised as TUSCANY-2790.
>
> > >
>
> > >
>
> > >
>
> > > I would like to start working on changing the package name to
>
> > > org.oasisopen.sca on the 2.x root. However, I realise that this could
> be
>
> > a
>
> > > rather disruptive change especially if we are planning to release M1.
>
> > >
>
> > >
>
> > >
>
> > > How do people feel about me attempting this change later this week or
>
> > early
>
> > > next?
>
> > >
>
> > >
>
> > >
>
> > > Thanks,
>
> > >
>
> > >
>
> > >
>
> > > Mark
>
> > >
>
> > >
>
> > >
>
> > > [1] https://issues.apache.org/jira/browse/TUSCANY-2790
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > >
>
> > > Hi Mark
>
> > >
>
> > > Is the proposal to change what is there or to add a new modules
>
> > alongside
>
> > > what is there with the new package names.
>
> > >
>
> > > To ask the question another way. Do we expect that 2.x will support 1.x
>
> > > compatible applications also. It would be very nice if backward
>
> > > compatibility were provided but it adds complexity.
>
> > >
>
> > > Simon
>
> >
>
> >
>
> >
>
> > --
>
> > Luciano Resende
>
> > Apache Tuscany, Apache PhotArk
>
> > http://people.apache.org/~lresende<http://people.apache.org/%7Elresende>
>
> > http://lresende.blogspot.com/
>
Hi Mark
Should it be
org.oasisopen.sca.annotation
or
org.oasisopen.sca.annotations
Looking at the latest Javacaa spec it looks like
"org.oasisopen.sca.annotations" is used but I expect I'm just not bang up to
date with the TC.
Regards
Simon
Re: [2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790
Posted by Raymond Feng <en...@gmail.com>.
Hi, Mark.
Thank you for doing this. Now we are the journey to the OASIS .
BTW, what about the license header for the OASIS APIs?
Thanks,
Raymond
From: Mark Combellack
Sent: Wednesday, January 28, 2009 6:14 AM
To: 'Luciano Resende'
Cc: Simon Laws ; dev@tuscany.apache.org
Subject: RE: [2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790
Hi Luciano,
I have just committed the change of package name back into the 2.x version of Tuscany as SVN revision 738490.
The change involved:
· Changing package org.osoa.sca to org.oasisopen.sca
· Changing package org.osoa.sca.annotations to org.oasisopen.sca.annotation
· Updating all references in the 2.x branch so they use org.oasisopen
The branch mostly builds with this change. The following projects do not build. Note: I had these problems before the package name changes so I don't believe my change has caused it:
· Apache Tuscany SCA Web Service Distribution
· Apache Tuscany SCA Binding WS Calculator Sample
· Apache Tuscany SCA Host Webapp Calculator Sample
· Apache Tuscany SCA All-in-one Distribution
· Apache Tuscany SCA PDE Target Platform Distribution
(See full error log below)
Hopefully, I have made all the changes that are needed. Apologies if I have missed/broken anything.
Thanks,
Mark
[INFO] Apache Tuscany SCA Web Service Distribution ........... FAILED [0.487s]
[INFO] Apache Tuscany SCA Binding WS Calculator Sample ....... SKIPPED (dependency build failed or was skipped)
[INFO] Apache Tuscany SCA Host Webapp Calculator Sample ...... SKIPPED (dependency build failed or was skipped)
[INFO] Apache Tuscany SCA All-in-one Distribution ............ SKIPPED (dependency build failed or was skipped)
[INFO] Apache Tuscany SCA PDE Target Platform Distribution ... SKIPPED (dependency build failed or was skipped)
[INFO] ------------------------------------------------------------------------
[INFO] Error for project: Apache Tuscany SCA Web Service Distribution (during install)
[INFO] ------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file there:
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca -DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1) org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
----------
2 required artifacts are missing.
for artifact:
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.ws.zone (http://ws.zones.apache.org/repository2),
apache.incubator (http://people.apache.org/repo/m2-incubating-repository),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
osuosl.org (http://ftp.osuosl.org/pub/eclipse/tools/emf/maven2),
indiana (http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/)
> -----Original Message-----
> From: Luciano Resende [mailto:luckbr1975@gmail.com]
> Sent: 27 January 2009 00:20
> To: dev@tuscany.apache.org; mcombellack@apache.org
> Cc: Simon Laws
> Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-
> J specification - TUSCANY-2790
>
> Mark,
>
> What's the time frame you have in mind to get these changes in ?
> Just trying to check if this would be available for M1 or not.
>
> On Mon, Jan 26, 2009 at 2:55 AM, Mark Combellack <mc...@apache.org>
> wrote:
> > Hi Simon,
> >
> >
> >
> > The OASIA SCA specification does not provide any "binary" backwards
> > compatibility with OSOA code. This means that all OSOA code would need
> to be
> > updated to work with an OASIS Open SCA runtime.
> >
> >
> >
> > The way that I see it working is that OSOA code would be supported on
> > Tuscany 1.x releases and OASIS Open code would be supported on the
> Tuscany
> > 2.x releases. Ideally, at some point in the future, we would provide
> some
> > tooling support along with Tuscany 2.x that would help developers
> convert
> > 1.x applications to 2.x applications.
> >
> >
> >
> > Currently, I feel that adding support for both the OSOA and OASIS Open
> > applications to the 2.x codebase would add considerable complexity so I
> > would prefer not to do it at this time.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> > ________________________________
> >
> > From: Simon Laws [mailto:simonslaws@googlemail.com]
> > Sent: 26 January 2009 10:38
> > To: dev@tuscany.apache.org; mcombellack@apache.org
> > Subject: Re: [2.x] Updating the package names to match the OASIS Open
> SCA-J
> > specification - TUSCANY-2790
> >
> >
> >
> >
> >
> > On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack
> <mc...@apache.org>
> > wrote:
> >
> > Hi,
> >
> >
> >
> > Recently, the OASIS SCA-J committee agreed to change the package name
> from
> > org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
> > raised as TUSCANY-2790.
> >
> >
> >
> > I would like to start working on changing the package name to
> > org.oasisopen.sca on the 2.x root. However, I realise that this could be
> a
> > rather disruptive change especially if we are planning to release M1.
> >
> >
> >
> > How do people feel about me attempting this change later this week or
> early
> > next?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/TUSCANY-2790
> >
> >
> >
> >
> >
> >
> >
> > Hi Mark
> >
> > Is the proposal to change what is there or to add a new modules
> alongside
> > what is there with the new package names.
> >
> > To ask the question another way. Do we expect that 2.x will support 1.x
> > compatible applications also. It would be very nice if backward
> > compatibility were provided but it adds complexity.
> >
> > Simon
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
RE: [2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790
Posted by Mark Combellack <mc...@apache.org>.
Hi Luciano,
I have just committed the change of package name back into the 2.x version
of Tuscany as SVN revision 738490.
The change involved:
* Changing package org.osoa.sca to org.oasisopen.sca
* Changing package org.osoa.sca.annotations to
org.oasisopen.sca.annotation
* Updating all references in the 2.x branch so they use
org.oasisopen
The branch mostly builds with this change. The following projects do not
build. Note: I had these problems before the package name changes so I don't
believe my change has caused it:
* Apache Tuscany SCA Web Service Distribution
* Apache Tuscany SCA Binding WS Calculator Sample
* Apache Tuscany SCA Host Webapp Calculator Sample
* Apache Tuscany SCA All-in-one Distribution
* Apache Tuscany SCA PDE Target Platform Distribution
(See full error log below)
Hopefully, I have made all the changes that are needed. Apologies if I have
missed/broken anything.
Thanks,
Mark
[INFO] Apache Tuscany SCA Web Service Distribution ........... FAILED
[0.487s]
[INFO] Apache Tuscany SCA Binding WS Calculator Sample ....... SKIPPED
(dependency build failed or was skipped)
[INFO] Apache Tuscany SCA Host Webapp Calculator Sample ...... SKIPPED
(dependency build failed or was skipped)
[INFO] Apache Tuscany SCA All-in-one Distribution ............ SKIPPED
(dependency build failed or was skipped)
[INFO] Apache Tuscany SCA PDE Target Platform Distribution ... SKIPPED
(dependency build failed or was skipped)
[INFO]
------------------------------------------------------------------------
[INFO] Error for project: Apache Tuscany SCA Web Service Distribution
(during install)
[INFO]
------------------------------------------------------------------------
[INFO] Failed to resolve artifact.
Missing:
----------
1) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-host-jetty -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-host-jetty:jar:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
mvn deploy:deploy-file -DgroupId=org.apache.tuscany.sca
-DartifactId=tuscany-binding-ws-axis2 -Dversion=2.0-SNAPSHOT -Dpackaging=jar
-Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id]
Path to dependency:
1)
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
2) org.apache.tuscany.sca:tuscany-binding-ws-axis2:jar:2.0-SNAPSHOT
----------
2 required artifacts are missing.
for artifact:
org.apache.tuscany.sca:tuscany-distribution-webservice:pom:2.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2),
apache.ws.zone (http://ws.zones.apache.org/repository2),
apache.incubator (http://people.apache.org/repo/m2-incubating-repository),
apache.snapshots (http://people.apache.org/repo/m2-snapshot-repository),
osuosl.org (http://ftp.osuosl.org/pub/eclipse/tools/emf/maven2),
indiana (http://ftp.ussg.iu.edu/eclipse/modeling/emf/emf/maven2/)
> -----Original Message-----
> From: Luciano Resende [mailto:luckbr1975@gmail.com]
> Sent: 27 January 2009 00:20
> To: dev@tuscany.apache.org; mcombellack@apache.org
> Cc: Simon Laws
> Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-
> J specification - TUSCANY-2790
>
> Mark,
>
> What's the time frame you have in mind to get these changes in ?
> Just trying to check if this would be available for M1 or not.
>
> On Mon, Jan 26, 2009 at 2:55 AM, Mark Combellack <mc...@apache.org>
> wrote:
> > Hi Simon,
> >
> >
> >
> > The OASIA SCA specification does not provide any "binary" backwards
> > compatibility with OSOA code. This means that all OSOA code would need
> to be
> > updated to work with an OASIS Open SCA runtime.
> >
> >
> >
> > The way that I see it working is that OSOA code would be supported on
> > Tuscany 1.x releases and OASIS Open code would be supported on the
> Tuscany
> > 2.x releases. Ideally, at some point in the future, we would provide
> some
> > tooling support along with Tuscany 2.x that would help developers
> convert
> > 1.x applications to 2.x applications.
> >
> >
> >
> > Currently, I feel that adding support for both the OSOA and OASIS Open
> > applications to the 2.x codebase would add considerable complexity so I
> > would prefer not to do it at this time.
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> > ________________________________
> >
> > From: Simon Laws [mailto:simonslaws@googlemail.com]
> > Sent: 26 January 2009 10:38
> > To: dev@tuscany.apache.org; mcombellack@apache.org
> > Subject: Re: [2.x] Updating the package names to match the OASIS Open
> SCA-J
> > specification - TUSCANY-2790
> >
> >
> >
> >
> >
> > On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack
> <mc...@apache.org>
> > wrote:
> >
> > Hi,
> >
> >
> >
> > Recently, the OASIS SCA-J committee agreed to change the package name
> from
> > org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
> > raised as TUSCANY-2790.
> >
> >
> >
> > I would like to start working on changing the package name to
> > org.oasisopen.sca on the 2.x root. However, I realise that this could be
> a
> > rather disruptive change especially if we are planning to release M1.
> >
> >
> >
> > How do people feel about me attempting this change later this week or
> early
> > next?
> >
> >
> >
> > Thanks,
> >
> >
> >
> > Mark
> >
> >
> >
> > [1] https://issues.apache.org/jira/browse/TUSCANY-2790
> >
> >
> >
> >
> >
> >
> >
> > Hi Mark
> >
> > Is the proposal to change what is there or to add a new modules
> alongside
> > what is there with the new package names.
> >
> > To ask the question another way. Do we expect that 2.x will support 1.x
> > compatible applications also. It would be very nice if backward
> > compatibility were provided but it adds complexity.
> >
> > Simon
>
>
>
> --
> Luciano Resende
> Apache Tuscany, Apache PhotArk
> http://people.apache.org/~lresende
> http://lresende.blogspot.com/
Re: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
Posted by Luciano Resende <lu...@gmail.com>.
Mark,
What's the time frame you have in mind to get these changes in ?
Just trying to check if this would be available for M1 or not.
On Mon, Jan 26, 2009 at 2:55 AM, Mark Combellack <mc...@apache.org> wrote:
> Hi Simon,
>
>
>
> The OASIA SCA specification does not provide any "binary" backwards
> compatibility with OSOA code. This means that all OSOA code would need to be
> updated to work with an OASIS Open SCA runtime.
>
>
>
> The way that I see it working is that OSOA code would be supported on
> Tuscany 1.x releases and OASIS Open code would be supported on the Tuscany
> 2.x releases. Ideally, at some point in the future, we would provide some
> tooling support along with Tuscany 2.x that would help developers convert
> 1.x applications to 2.x applications.
>
>
>
> Currently, I feel that adding support for both the OSOA and OASIS Open
> applications to the 2.x codebase would add considerable complexity so I
> would prefer not to do it at this time.
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
> ________________________________
>
> From: Simon Laws [mailto:simonslaws@googlemail.com]
> Sent: 26 January 2009 10:38
> To: dev@tuscany.apache.org; mcombellack@apache.org
> Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-J
> specification - TUSCANY-2790
>
>
>
>
>
> On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack <mc...@apache.org>
> wrote:
>
> Hi,
>
>
>
> Recently, the OASIS SCA-J committee agreed to change the package name from
> org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
> raised as TUSCANY-2790.
>
>
>
> I would like to start working on changing the package name to
> org.oasisopen.sca on the 2.x root. However, I realise that this could be a
> rather disruptive change especially if we are planning to release M1.
>
>
>
> How do people feel about me attempting this change later this week or early
> next?
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
> [1] https://issues.apache.org/jira/browse/TUSCANY-2790
>
>
>
>
>
>
>
> Hi Mark
>
> Is the proposal to change what is there or to add a new modules alongside
> what is there with the new package names.
>
> To ask the question another way. Do we expect that 2.x will support 1.x
> compatible applications also. It would be very nice if backward
> compatibility were provided but it adds complexity.
>
> Simon
--
Luciano Resende
Apache Tuscany, Apache PhotArk
http://people.apache.org/~lresende
http://lresende.blogspot.com/
RE: [2.x] Updating the package names to match the OASIS Open SCA-J specification - TUSCANY-2790
Posted by Mark Combellack <mc...@apache.org>.
Hi Simon,
The OASIA SCA specification does not provide any "binary" backwards
compatibility with OSOA code. This means that all OSOA code would need to be
updated to work with an OASIS Open SCA runtime.
The way that I see it working is that OSOA code would be supported on
Tuscany 1.x releases and OASIS Open code would be supported on the Tuscany
2.x releases. Ideally, at some point in the future, we would provide some
tooling support along with Tuscany 2.x that would help developers convert
1.x applications to 2.x applications.
Currently, I feel that adding support for both the OSOA and OASIS Open
applications to the 2.x codebase would add considerable complexity so I
would prefer not to do it at this time.
Thanks,
Mark
_____
From: Simon Laws [mailto:simonslaws@googlemail.com]
Sent: 26 January 2009 10:38
To: dev@tuscany.apache.org; mcombellack@apache.org
Subject: Re: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack <mc...@apache.org>
wrote:
Hi,
Recently, the OASIS SCA-J committee agreed to change the package name from
org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
raised as TUSCANY-2790.
I would like to start working on changing the package name to
org.oasisopen.sca on the 2.x root. However, I realise that this could be a
rather disruptive change especially if we are planning to release M1.
How do people feel about me attempting this change later this week or early
next?
Thanks,
Mark
[1] https://issues.apache.org/jira/browse/TUSCANY-2790
Hi Mark
Is the proposal to change what is there or to add a new modules alongside
what is there with the new package names.
To ask the question another way. Do we expect that 2.x will support 1.x
compatible applications also. It would be very nice if backward
compatibility were provided but it adds complexity.
Simon
Re: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
Posted by ant elder <an...@gmail.com>.
On Mon, Jan 26, 2009 at 10:37 AM, Simon Laws <si...@googlemail.com>wrote:
>
>
> On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack <mc...@apache.org>wrote:
>
>> Hi,
>>
>>
>>
>> Recently, the OASIS SCA-J committee agreed to change the package name from
>> org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
>> raised as TUSCANY-2790.
>>
>>
>>
>> I would like to start working on changing the package name to
>> org.oasisopen.sca on the 2.x root. However, I realise that this could be a
>> rather disruptive change especially if we are planning to release M1.
>>
>>
>>
>> How do people feel about me attempting this change later this week or
>> early next?
>>
>>
>>
>> Thanks,
>>
>>
>>
>> Mark
>>
>>
>>
>> [1] https://issues.apache.org/jira/browse/TUSCANY-2790
>>
>>
>>
>>
>>
>>
>>
>
> Hi Mark
>
> Is the proposal to change what is there or to add a new modules alongside
> what is there with the new package names.
>
> To ask the question another way. Do we expect that 2.x will support 1.x
> compatible applications also. It would be very nice if backward
> compatibility were provided but it adds complexity.
>
> Simon
>
Agree with both of those, it would be nice to support both but it will add
complexity. We have voted to have 2.x be the place to support the OASIS
specs so it seems to me if we're not sure how to do this yet then OASIS
should take priority so i'd be happy if for now we change to support OASIS
and look at adding backward compatibility at some point in the future.
As to the when to make this particular change I think now or next week seems
fine, and it would be good to include that in 2.0 M1 so it starts to show
that OASIS is what we're doing in 2.0.
...ant
Re: [2.x] Updating the package names to match the OASIS Open SCA-J
specification - TUSCANY-2790
Posted by Simon Laws <si...@googlemail.com>.
On Mon, Jan 26, 2009 at 10:21 AM, Mark Combellack <mc...@apache.org>wrote:
> Hi,
>
>
>
> Recently, the OASIS SCA-J committee agreed to change the package name from
> org.osoa.sca to org.oasisopen.sca. A JIRA issue for this change has been
> raised as TUSCANY-2790.
>
>
>
> I would like to start working on changing the package name to
> org.oasisopen.sca on the 2.x root. However, I realise that this could be a
> rather disruptive change especially if we are planning to release M1.
>
>
>
> How do people feel about me attempting this change later this week or early
> next?
>
>
>
> Thanks,
>
>
>
> Mark
>
>
>
> [1] https://issues.apache.org/jira/browse/TUSCANY-2790
>
>
>
>
>
>
>
Hi Mark
Is the proposal to change what is there or to add a new modules alongside
what is there with the new package names.
To ask the question another way. Do we expect that 2.x will support 1.x
compatible applications also. It would be very nice if backward
compatibility were provided but it adds complexity.
Simon