| JAX-WS 2.0 [message #14004] |
Mon, 04 August 2008 20:06  |
|
Hi,
The ORMF project requires JAX-WS 2.0. I would be happy to bundle this
for Orbit if it is wanted. Can I get my CQ and an Orbit CQ approved in
parallel or should I get usage of the libraries approved before
starting a process with Orbit.
All the best,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme and the
|) ::: (| Open Requirements Management Framework
====w=w==== [http://www.eclipse.org/ormf]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: JAX-WS 2.0 [message #14012 is a reply to message #14004] |
Mon, 04 August 2008 20:27  |
Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Joel Rosi-Schwartz wrote:
> Hi,
>
> The ORMF project requires JAX-WS 2.0. I would be happy to bundle this
> for Orbit if it is wanted. Can I get my CQ and an Orbit CQ approved in
> parallel or should I get usage of the libraries approved before starting
> a process with Orbit.
You can do both at the same time. I'd file the CQ for JAX-WS 2.0 against
ORMF first, than a CQ in Orbit for reuse of the previous CQ.
Cheers,
~ Chris
|
|
|
| Re: JAX-WS 2.0 [message #14028 is a reply to message #14012] |
Tue, 05 August 2008 15:43 |
|
On 2008-08-04 21:27:03 +0100, Chris Aniszczyk <zx@code9.com> said:
> Joel Rosi-Schwartz wrote:
>> Hi,
>>
>> The ORMF project requires JAX-WS 2.0. I would be happy to bundle this
>> for Orbit if it is wanted. Can I get my CQ and an Orbit CQ approved in
>> parallel or should I get usage of the libraries approved before
>> starting a process with Orbit.
>
> You can do both at the same time. I'd file the CQ for JAX-WS 2.0
> against ORMF first, than a CQ in Orbit for reuse of the previous CQ.
>
> Cheers,
>
> ~ Chris
Thanks Chris, will do. I am waiting on the answer to a question I asked
the emo-ip team, but perhaps you know the answer. Here is the question
as I posed it:
Before I start filling out a CQ I would like your advice on how to
structure it. JAX-WS is a standard Java 5 EE component that is
developed as a part of Glassfish here. It is distributed as a
single executable jar file that installs as a hierarchy which contains
16 jar files. The source for JAX-WS is also distributed as a
single executable jar file that installs as a hierarchy, but the source
for all target jars are in a unified tree. Is it possible to have the
entire library approved in one go or do I have to fill in 16 CQ? If I
need to do 16 CQ, should I create a 17th that contains the source and
point all of the other to it or attach a copy of the source to each?
Can you advise on this or should I wait for an answer from them?
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Too
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
| Re: JAX-WS 2.0 [message #14043 is a reply to message #14028] |
Tue, 05 August 2008 16:05 |
| Eclipse User |
|
|
|
Originally posted by: zx.code9.com
Joel Rosi-Schwartz wrote:
> Can you advise on this or should I wait for an answer from them?
I'd wait on what the IP team has to say.
It depends what those 16 folders are... if it's just all source
representative of JAX-WS than 1 CQ should be enough. However, if those
16 folders represent JAX-WS dependencies than that could be an issue and
require separate CQs.
Good luck!
Cheers,
~ Chris
|
|
|
| Re: JAX-WS 2.0 [message #14057 is a reply to message #14043] |
Tue, 05 August 2008 20:32 |
|
On 2008-08-05 17:05:10 +0100, Chris Aniszczyk <zx@code9.com> said:
> Joel Rosi-Schwartz wrote:
>> Can you advise on this or should I wait for an answer from them?
>
> I'd wait on what the IP team has to say.
>
> It depends what those 16 folders are... if it's just all source
> representative of JAX-WS than 1 CQ should be enough. However, if those
> 16 folders represent JAX-WS dependencies than that could be an issue
> and require separate CQs.
>
> Good luck!
>
> Cheers,
>
> ~ Chris
Chris,
I am having an on going conversation with Sharon Corbett on this. I am
going to add you to the CC list as I think you might want to express
your opinion from the Orbit perspective.
/joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Too
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
|
| Re: JAX-WS 2.0 [message #564064 is a reply to message #14012] |
Tue, 05 August 2008 15:43 |
|
On 2008-08-04 21:27:03 +0100, Chris Aniszczyk <zx@code9.com> said:
> Joel Rosi-Schwartz wrote:
>> Hi,
>>
>> The ORMF project requires JAX-WS 2.0. I would be happy to bundle this
>> for Orbit if it is wanted. Can I get my CQ and an Orbit CQ approved in
>> parallel or should I get usage of the libraries approved before
>> starting a process with Orbit.
>
> You can do both at the same time. I'd file the CQ for JAX-WS 2.0
> against ORMF first, than a CQ in Orbit for reuse of the previous CQ.
>
> Cheers,
>
> ~ Chris
Thanks Chris, will do. I am waiting on the answer to a question I asked
the emo-ip team, but perhaps you know the answer. Here is the question
as I posed it:
Before I start filling out a CQ I would like your advice on how to
structure it. JAX-WS is a standard Java 5 EE component that is
developed as a part of Glassfish here. It is distributed as a
single executable jar file that installs as a hierarchy which contains
16 jar files. The source for JAX-WS is also distributed as a
single executable jar file that installs as a hierarchy, but the source
for all target jars are in a unified tree. Is it possible to have the
entire library approved in one go or do I have to fill in 16 CQ? If I
need to do 16 CQ, should I create a 17th that contains the source and
point all of the other to it or attach a copy of the source to each?
Can you advise on this or should I wait for an answer from them?
Thanks,
Joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Too
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
| Re: JAX-WS 2.0 [message #564110 is a reply to message #14043] |
Tue, 05 August 2008 20:32 |
|
On 2008-08-05 17:05:10 +0100, Chris Aniszczyk <zx@code9.com> said:
> Joel Rosi-Schwartz wrote:
>> Can you advise on this or should I wait for an answer from them?
>
> I'd wait on what the IP team has to say.
>
> It depends what those 16 folders are... if it's just all source
> representative of JAX-WS than 1 CQ should be enough. However, if those
> 16 folders represent JAX-WS dependencies than that could be an issue
> and require separate CQs.
>
> Good luck!
>
> Cheers,
>
> ~ Chris
Chris,
I am having an on going conversation with Sharon Corbett on this. I am
going to add you to the CC list as I think you might want to express
your opinion from the Orbit perspective.
/joel
--
Joel Rosi-Schwartz
Etish Limited [http://www.etish.org]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
^...^
/ o,o \ The proud parents of Useme
|) ::: (| The Open Requirements Management Too
====w=w==== [https://useme.dev.java.net]
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
|
|
|
|
Powered by
FUDForum. Page generated in 0.04363 seconds
] 
Search
Help
Register
Login
Home
