You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@juddi.apache.org by Anou Manavalan <an...@hotmail.com> on 2004/03/16 15:22:44 UTC
FW: RE: [VOTE] Graduate jUDDI from incubator
Steve,
On removing the jars, looks like jce and the jdbc one's are the problematic.
Lets remove them and may be send one more Exit request ? What do you think ?
I don't think we need to remove saaj, junit...
regards,
-Anou
>From: "Viens, Steve" <St...@FMR.COM>
>Reply-To: general@incubator.apache.org
>To: "'dims@yahoo.com'" <di...@yahoo.com>, general@incubator.apache.org,
> pmc@incubator.apache.org
>Subject: RE: [VOTE] Graduate jUDDI from incubator
>Date: Fri, 12 Mar 2004 22:22:48 -0500
>
>Sure thing, the juddi.cwiki was updated earlier in the week but I haven't
>yet updated the site. We were already dicussing which jar's to remove from
>CVS:
>
>http://marc.theaimsgroup.com/?l=juddi-dev&m=107902078216120&w=2
>
>Steve
>
>-----Original Message-----
>From: Davanum Srinivas [mailto:dims@yahoo.com]
>Sent: Friday, March 12, 2004 5:26 PM
>To: general@incubator.apache.org; pmc@incubator.apache.org
>Cc: Viens, Steve
>Subject: RE: [VOTE] Graduate jUDDI from incubator
>
>
>Steve,
>
>Can you please take care of items mentioned?
>
>thanks,
>dims
>
>--- "Noel J. Bergman" <no...@devtech.com> wrote:
> > Dims,
> >
> > I don't see a record of Steve Vien's message.
> >
> > Before I vote, I reviewed
>http://incubator.apache.org/projects/juddi.html.
> > It appears to be a bit out of date, e.g., Anil Saldhana's account as
>long
> > since created. Would you please clean it up when you finalize the
>document?
> >
> > The list of third party jar files
> > (http://cvs.apache.org/viewcvs.cgi/ws-juddi/lib/README?rev=1.1) caught
>my
> > eye, due to the current discussions over BCL jars. From what i see,
>both
> > jce.jar and jdbc2_0-stdext.jar should be removed from the jUDDI CVS
>module.
> >
> > Those packages are licensed under the BCL, with the typical clause
>stating
> > (in part): "Sun grants you a non-exclusive, non-transferable, limited
> > license to reproduce and distribute the Software in binary code form
>only,
> > provided that you (i) distribute the Software complete and unmodified
>and
> > only bundled as part of your Programs [...]" The license does mean
>that,
> > pending any policy or licensing change, a release package of jUDDI can
> > include those BCL jars, as per Sun's license.
> >
> > Other than the issue of jars covered by BCL being in CVS, I don't see
>any
> > other problem, and would be +1 to release jUDDI to the WS PMC once this
>is
> > addressed.
> >
> > --- Noel
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>
_________________________________________________________________
Get business advice and resources to improve your work life, from bCentral.
http://special.msn.com/bcentral/loudclear.armx
RE: Removing jar files from jUDDI CVS
Posted by Steve Viens <st...@viens.net>.
jaxrpc.jar and saaj.jar have been removed from cvs as well now.
If you need them (and you will to build jUDDI) they're bundled in with
Axis 1.1 release which is where the copies I just removed came from in
the first place:
http://ws.apache.org/axis/download.cgi
If you're building with JDK 1.3.x you'll need copies of jca.jar and
jdbc2_0-stdext.jar (these are included in JDK 1.4.x)
Java Cryptography Extendsion (jca.jar)
http://java.sun.com/products/jce/
I originally aquired the JDBC 2.0 optional package jar file
from Tomcat's common/lib directory. I'm having some trouble
locating a location to grab it now.
http:// ???
If you would like to build and run the UDDI4j unit tests you'll need
junit.jar and uddi4j.jar
JUnit
http://www.junit.org/
UDDI4j
http://www-124.ibm.com/developerworks/oss/uddi4j/
Please let me know if I missed anything.
Steve
-----Original Message-----
From: Steve Viens [mailto:steve@viens.net]
Sent: Tuesday, March 16, 2004 10:59 AM
To: juddi-dev@ws.apache.org
Subject: Removing jar files from jUDDI CVS
I made the changes (removals) last night based on what I saw in the
ws-axis CVS module.
All I *left* in ws-juddi/lib were the following:
axis.jar
commons-collections.jar
commons-dbcp.jar
commons-discovery.jar
commons-logging.jar
commons-pool.jar
log4j-1.2.8.jar
servlet-api.jar
wsdl4j.jar
These two are still in CVS at the moment as well but the Axis project
doesn't store them in CVS so I'm thinking that jUDDI shouldn't either:
jaxrpc.jar
saaj.jar
I thought a good approach might be to simply document how to build jUDDI
in the developers guide (to-do) and indicate in that document which
products/libraries to include, the versions of those libraries and where
to put them. Again, something Axis does already.
Axis uses a decision-tree process for assembling the libraries needed to
perform a specific task.
A. If you want to build jUDDI you A & B (saaj, jaxrpc)
B. If you want to build the tests you need D & E (junit, uddi4j) C. If
you want to build CryptedAuthenticator with JDK 1.3.1 you need F
(jce)
D. (etc)
This may be more inconvenient for those that want to build the project
but once you grab the appropriate jars and drop them into jUDDI's 'lib'
directory then there's nothing more you'll need to do.
It sounds like that when we produce a release we can include some of the
jar files that we are no longer keeping in CVS such as jaxrpc.jar and
saaj.jar.
What do you think?
Steve
-----Original Message-----
From: Anou Manavalan [mailto:anou_mana@hotmail.com]
Sent: Tuesday, March 16, 2004 9:23 AM
To: juddi-dev@ws.apache.org
Subject: FW: RE: [VOTE] Graduate jUDDI from incubator
Steve,
On removing the jars, looks like jce and the jdbc one's are the
problematic.
Lets remove them and may be send one more Exit request ? What do you
think ?
I don't think we need to remove saaj, junit...
regards,
-Anou
>From: "Viens, Steve" <St...@FMR.COM>
>Reply-To: general@incubator.apache.org
>To: "'dims@yahoo.com'" <di...@yahoo.com>, general@incubator.apache.org,
> pmc@incubator.apache.org
>Subject: RE: [VOTE] Graduate jUDDI from incubator
>Date: Fri, 12 Mar 2004 22:22:48 -0500
>
>Sure thing, the juddi.cwiki was updated earlier in the week but I
>haven't yet updated the site. We were already dicussing which jar's to
>remove from
>CVS:
>
>http://marc.theaimsgroup.com/?l=juddi-dev&m=107902078216120&w=2
>
>Steve
>
>-----Original Message-----
>From: Davanum Srinivas [mailto:dims@yahoo.com]
>Sent: Friday, March 12, 2004 5:26 PM
>To: general@incubator.apache.org; pmc@incubator.apache.org
>Cc: Viens, Steve
>Subject: RE: [VOTE] Graduate jUDDI from incubator
>
>
>Steve,
>
>Can you please take care of items mentioned?
>
>thanks,
>dims
>
>--- "Noel J. Bergman" <no...@devtech.com> wrote:
> > Dims,
> >
> > I don't see a record of Steve Vien's message.
> >
> > Before I vote, I reviewed
>http://incubator.apache.org/projects/juddi.html.
> > It appears to be a bit out of date, e.g., Anil Saldhana's account as
>long
> > since created. Would you please clean it up when you finalize the
>document?
> >
> > The list of third party jar files
> > (http://cvs.apache.org/viewcvs.cgi/ws-juddi/lib/README?rev=1.1)
> > caught
>my
> > eye, due to the current discussions over BCL jars. From what i see,
>both
> > jce.jar and jdbc2_0-stdext.jar should be removed from the jUDDI CVS
>module.
> >
> > Those packages are licensed under the BCL, with the typical clause
>stating
> > (in part): "Sun grants you a non-exclusive, non-transferable,
> > limited license to reproduce and distribute the Software in binary
> > code form
>only,
> > provided that you (i) distribute the Software complete and
> > unmodified
>and
> > only bundled as part of your Programs [...]" The license does mean
>that,
> > pending any policy or licensing change, a release package of jUDDI
> > can include those BCL jars, as per Sun's license.
> >
> > Other than the issue of jars covered by BCL being in CVS, I don't
> > see
>any
> > other problem, and would be +1 to release jUDDI to the WS PMC once
> > this
>is
> > addressed.
> >
> > --- Noel
> >
> >
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>
_________________________________________________________________
Get business advice and resources to improve your work life, from
bCentral.
http://special.msn.com/bcentral/loudclear.armx
Removing jar files from jUDDI CVS
Posted by Steve Viens <st...@viens.net>.
I made the changes (removals) last night based on what I saw in the
ws-axis CVS module.
All I *left* in ws-juddi/lib were the following:
axis.jar
commons-collections.jar
commons-dbcp.jar
commons-discovery.jar
commons-logging.jar
commons-pool.jar
log4j-1.2.8.jar
servlet-api.jar
wsdl4j.jar
These two are still in CVS at the moment as well but the Axis project
doesn't store them in CVS so I'm thinking that jUDDI shouldn't either:
jaxrpc.jar
saaj.jar
I thought a good approach might be to simply document how to build jUDDI
in the developers guide (to-do) and indicate in that document which
products/libraries to include, the versions of those libraries and where
to put them. Again, something Axis does already.
Axis uses a decision-tree process for assembling the libraries needed to
perform a specific task.
A. If you want to build jUDDI you A & B (saaj, jaxrpc)
B. If you want to build the tests you need D & E (junit, uddi4j)
C. If you want to build CryptedAuthenticator with JDK 1.3.1 you need F
(jce)
D. (etc)
This may be more inconvenient for those that want to build the project
but once you grab the appropriate jars and drop them into jUDDI's 'lib'
directory then there's nothing more you'll need to do.
It sounds like that when we produce a release we can include some of the
jar files that we are no longer keeping in CVS such as jaxrpc.jar and
saaj.jar.
What do you think?
Steve
-----Original Message-----
From: Anou Manavalan [mailto:anou_mana@hotmail.com]
Sent: Tuesday, March 16, 2004 9:23 AM
To: juddi-dev@ws.apache.org
Subject: FW: RE: [VOTE] Graduate jUDDI from incubator
Steve,
On removing the jars, looks like jce and the jdbc one's are the
problematic.
Lets remove them and may be send one more Exit request ? What do you
think ?
I don't think we need to remove saaj, junit...
regards,
-Anou
>From: "Viens, Steve" <St...@FMR.COM>
>Reply-To: general@incubator.apache.org
>To: "'dims@yahoo.com'" <di...@yahoo.com>, general@incubator.apache.org,
> pmc@incubator.apache.org
>Subject: RE: [VOTE] Graduate jUDDI from incubator
>Date: Fri, 12 Mar 2004 22:22:48 -0500
>
>Sure thing, the juddi.cwiki was updated earlier in the week but I
>haven't yet updated the site. We were already dicussing which jar's to
>remove from
>CVS:
>
>http://marc.theaimsgroup.com/?l=juddi-dev&m=107902078216120&w=2
>
>Steve
>
>-----Original Message-----
>From: Davanum Srinivas [mailto:dims@yahoo.com]
>Sent: Friday, March 12, 2004 5:26 PM
>To: general@incubator.apache.org; pmc@incubator.apache.org
>Cc: Viens, Steve
>Subject: RE: [VOTE] Graduate jUDDI from incubator
>
>
>Steve,
>
>Can you please take care of items mentioned?
>
>thanks,
>dims
>
>--- "Noel J. Bergman" <no...@devtech.com> wrote:
> > Dims,
> >
> > I don't see a record of Steve Vien's message.
> >
> > Before I vote, I reviewed
>http://incubator.apache.org/projects/juddi.html.
> > It appears to be a bit out of date, e.g., Anil Saldhana's account as
>long
> > since created. Would you please clean it up when you finalize the
>document?
> >
> > The list of third party jar files
> > (http://cvs.apache.org/viewcvs.cgi/ws-juddi/lib/README?rev=1.1)
> > caught
>my
> > eye, due to the current discussions over BCL jars. From what i see,
>both
> > jce.jar and jdbc2_0-stdext.jar should be removed from the jUDDI CVS
>module.
> >
> > Those packages are licensed under the BCL, with the typical clause
>stating
> > (in part): "Sun grants you a non-exclusive, non-transferable,
> > limited license to reproduce and distribute the Software in binary
> > code form
>only,
> > provided that you (i) distribute the Software complete and
> > unmodified
>and
> > only bundled as part of your Programs [...]" The license does mean
>that,
> > pending any policy or licensing change, a release package of jUDDI
> > can include those BCL jars, as per Sun's license.
> >
> > Other than the issue of jars covered by BCL being in CVS, I don't
> > see
>any
> > other problem, and would be +1 to release jUDDI to the WS PMC once
> > this
>is
> > addressed.
> >
> > --- Noel
> >
> >
> > --------------------------------------------------------------------
> > -
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
>
>
>=====
>Davanum Srinivas - http://webservices.apache.org/~dims/
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>For additional commands, e-mail: general-help@incubator.apache.org
>
_________________________________________________________________
Get business advice and resources to improve your work life, from
bCentral.
http://special.msn.com/bcentral/loudclear.armx