Re: [VOTE] The retirement of Apache jUDDI (moving to the Apache Attic)

2022-12-22 Thread Steve Viens 
+1 (resend)

On Thu, Dec 22, 2022 at 2:42 AM Kurt Stam  wrote:

> +1 from me
>
> —Kurt
>
> On Dec 22, 2022, at 01:00, Alex O'Ree  wrote:
>
> 
> Resending...2 votes is not enough to pass, otherwise the board may have to
> take action directly
>
> On Thu, Dec 15, 2022 at 12:52 PM Steve Viens  wrote:
>
>> +1 from me as well.
>>
>> Steve
>>
>> On Wed, Dec 14, 2022 at 7:28 PM Alex O'Ree  wrote:
>>
>>> After some discussion over the past month or so, there seems to be
>>> enough of a consensus to hold a vote on retiring Apache jUDDI. I've pretty
>>> much been the only maintainer for a while now and unfortunately have a
>>> number of outstanding issues that I can't solve without assistance from the
>>> community.
>>>
>>> Unfortunately, most, if not all, of the committers and other community
>>> members have moved on to other projects. Usage of the UDDI specification
>>> and Apache jUDDI has never really been that high in general. Recently over
>>> the fast few years, JIRA issue reporting, mailing list traffic and all
>>> known out of band traffic have been near zero. Download statistics are
>>> pretty minimal as well and if anyone is using our libraries, there's little
>>> recent evidence to support that via mvnreponsitory.com's cross
>>> reference capabilities.
>>>
>>> The process for moving a project to the Attic is outlined here:
>>> https://attic.apache.org/process.html
>>>
>>> On Nov 11th, an email was dispatched to both the user and dev lists
>>> about this with no replies. It's time for the formal vote.
>>>
>>> +1 from me
>>>
>>
>>> --
>> Steve Viens
>> svi...@gmail.com
>> 603-828-2397
>>
> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: [VOTE] The retirement of Apache jUDDI (moving to the Apache Attic)

2022-12-15 Thread Steve Viens 
+1 from me as well.

Steve

On Wed, Dec 14, 2022 at 7:28 PM Alex O'Ree  wrote:

> After some discussion over the past month or so, there seems to be enough
> of a consensus to hold a vote on retiring Apache jUDDI. I've pretty much
> been the only maintainer for a while now and unfortunately have a number of
> outstanding issues that I can't solve without assistance from the community.
>
> Unfortunately, most, if not all, of the committers and other community
> members have moved on to other projects. Usage of the UDDI specification
> and Apache jUDDI has never really been that high in general. Recently over
> the fast few years, JIRA issue reporting, mailing list traffic and all
> known out of band traffic have been near zero. Download statistics are
> pretty minimal as well and if anyone is using our libraries, there's little
> recent evidence to support that via mvnreponsitory.com's cross reference
> capabilities.
>
> The process for moving a project to the Attic is outlined here:
> https://attic.apache.org/process.html
>
> On Nov 11th, an email was dispatched to both the user and dev lists about
> this with no replies. It's time for the formal vote.
>
> +1 from me
>
-- 
Steve Viens
svi...@gmail.com
603-828-2397

Re: Moving jUDDI to the attic

2022-11-11 Thread Steve Viens 
Agree a vote to possibly retire is a good idea.

Steve

On Fri, Nov 11, 2022 at 12:17 PM Alex O'Ree  wrote:

> None that I know of aside from some integration points. No off mailing
> list emails in several years that i recall
>
> On Fri, Nov 11, 2022 at 10:10 AM Tom Cunningham 
> wrote:
>
>> Hi Alex,
>>
>> I checked out the project in December of last year to check for log4j
>> exposure, but I'm not using UDDI in my day to day so I've been spending my
>> open source time on other projects.
>>
>> I think you have a better idea than any of us do as to how much the
>> project is being used and by who - are there JIRA coming in on it, are you
>> getting any emails off list on your end?
>>
>> --Tom
>>
>>
>>
>>
>> On Wed, Nov 9, 2022 at 9:42 PM Alex O'Ree  wrote:
>>
>>> Anyone alive? Or should we start discussing moving this project to the
>>> attic?
>>>
>>> I'm getting tired of maintaining this project by myself. I understand
>>> everyone is busy with other stuff. I am too, but we do have a certain level
>>> of responsibility for supporting this project.
>>>
>>> Is it time to call the vote on retiring jUDDI?
>>>
>> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: [VOTE] jUDDI v3.3.10

2021-06-22 Thread Steve Viens 
+1

On Tue, Jun 22, 2021 at 10:27 PM Alex O'Ree  wrote:

> Dear jUDDI enthusiasts,
>
> The new release is here! This release resolves 1 JIRA for an unspecified
> security issue.
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/t1m6md4sjphsoqc/AACOiHR6EV7ohKOtIMe83d3Aa?dl=0
> <https://www.dropbox.com/sh/k2ojoye8y2916bf/AACRJoqqI5X4zlTKBlhASjCma?dl=0>
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1020
> <https://repository.apache.org/content/repositories/orgapachejuddi-1019>
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.
> <https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.9>
> 1
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
> +1 for me
>
> Bug
>
>- [JUDDI-1018 <https://issues.apache.org/jira/browse/JUDDI-1018>] - TBD
>
> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: [VOTE] jUDDI v3.3.9

2020-08-15 Thread Steve Viens 
+1 from me!

Steve Viens
svi...@gmail.com
603-828-2397


On Sat, Aug 15, 2020 at 9:39 AM Alex O'Ree  wrote:

> Dear jUDDI enthusiasts,
>
> The new release is here! This release resolves 11 JIRAs, 3 enhancements
> and the rest bugs. I did update the release notes in the distro, however I
> had incorrectly labeled some of the JIRA as being fixed in the previous
> version so it's missing a few issues. It's corrected in JIRA now
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/k2ojoye8y2916bf/AACRJoqqI5X4zlTKBlhASjCma?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1019
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.9
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
> +1 for me
>
> Bug
>
>- [JUDDI-1004 <https://issues.apache.org/jira/browse/JUDDI-1004>] -
>JUDDI-3.3.7 With SQL Server Database Gives Primary Key Violation For Table
>j3_category_bag
>- [JUDDI-1006 <https://issues.apache.org/jira/browse/JUDDI-1006>] -
>Saving an Access Point Type
>- [JUDDI-1008 <https://issues.apache.org/jira/browse/JUDDI-1008>] -
>find_business returns an error when querying a tModel when using the v2
>Inquire API
>- [JUDDI-1009 <https://issues.apache.org/jira/browse/JUDDI-1009>] -
>Browse Businesses using juddiv2 page navigation issue
>- [JUDDI-1010 <https://issues.apache.org/jira/browse/JUDDI-1010>] -
>save_business does not properly save the accessPoint URLType when using the
>v2 Publish API
>- [JUDDI-1011 <https://issues.apache.org/jira/browse/JUDDI-1011>] - MS
>SQL Server table - length of field too large
>- [JUDDI-1013 <https://issues.apache.org/jira/browse/JUDDI-1013>] -
>GUI adding records
>- [JUDDI-1015 <https://issues.apache.org/jira/browse/JUDDI-1015>] -
>Oracle database start up issue due to max string length
>
> Improvement
>
>- [JUDDI-1012 <https://issues.apache.org/jira/browse/JUDDI-1012>] - MS
>SQL Server Sequence table change
>- [JUDDI-1014 <https://issues.apache.org/jira/browse/JUDDI-1014>] -
>Binding Editor – tModel Instance Information
>- [JUDDI-1016 <https://issues.apache.org/jira/browse/JUDDI-1016>] -
>Add DDL generators for all available hibernate supported dialetcs
>
>

Re: [VOTE] jUDDI v3.3.8

2020-03-12 Thread Steve Viens 
+1

Missed it!  Sorry, crazy times.


Steve Viens
svi...@gmail.com
603-828-2397


On Thu, Mar 12, 2020 at 7:27 AM Alex O'Ree  wrote:

> 5 days and no responses...
>
> On Sat, Mar 7, 2020, 7:36 PM Alex O'Ree  wrote:
>
>> Dear jUDDI enthusiasts,
>>
>> The new release is here! This release resolves 4 JIRAs, 2 bugs and 2
>> minor enhancements. I did miss updating the release notes within the distro
>> but
>>
>> The release distribution is temporarily available here
>> https://www.dropbox.com/sh/mknyo1s4g7er3wl/AAAGJf9LuCDRt1et4tqlKa8ua?dl=0
>>
>> The release artifacts are staged in nexus:
>> https://repository.apache.org/content/repositories/orgapachejuddi-1018
>>
>> and we have a tag at:
>>
>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.8
>>
>> Please give it a spin and cast your vote. This vote will be open for
>> the next 72 hours per the release policy, which is:
>> - the vote will be closed as soon as 6 hours have past and  >7 +1
>> votes are received with no -1 vote being cast, or
>>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
>> that
>>  - after 72h provided at least 3 +1 votes have been cast and there is
>> a majority of +1 votes from the cast votes.
>>
>> +1 for me
>>
>>
>> Bug
>>
>>- [JUDDI-937 <https://issues.apache.org/jira/browse/JUDDI-937>] -
>>PolicyRoundRobin not working without service cache
>>- [JUDDI-1003 <https://issues.apache.org/jira/browse/JUDDI-1003>] -
>>spring-web jar supplied with latest JUDDI distribution has security
>>vulnerability
>>
>> Improvement
>>
>>- [JUDDI-993 <https://issues.apache.org/jira/browse/JUDDI-993>] -
>>InVm transport for embedded juddi needs to handle authentication and a
>>sample for usage
>>- [JUDDI-1002 <https://issues.apache.org/jira/browse/JUDDI-1002>] -
>>tModelInstanceInfo value does not check for maximum length
>>
>>

Re: [VOTE] jUDDI v3.3.7

2020-01-11 Thread Steve Viens 
+1 ... 

On Sat, Jan 11, 2020 at 5:26 PM Alex O'Ree  wrote:

> ok so that's 3 +1 votes, i'll finish the release process
>
> On Sat, Jan 11, 2020 at 4:36 PM Kurt Stam  wrote:
>
>> +1 from me! —Kurt
>>
>> On Jan 11, 2020, at 11:53, Anil Saldanha  wrote:
>>
>> +1 from me
>>
>> On Jan 11, 2020, at 7:29 AM, Alex O'Ree  wrote:
>>
>> 
>> Any other votes on this? there are at least 5 voting members on this
>> board.
>>
>> On Sat, Dec 14, 2019 at 9:56 PM Alex O'Ree  wrote:
>>
>>> Dear jUDDI enthusiasts,
>>>
>>> The new release is here! This release resolves 6 JIRAs, 4 bugs, 1 build
>>> related issue, and one maintenance issue.
>>>
>>> The release distribution is temporarily available here (without hashes)
>>> https://www.dropbox.com/sh/28qfjhx0h38h3dg/AADVdOIkStgu88y2ggXU-_F5a?dl=0
>>>
>>> The release artifacts are staged in nexus:
>>> https://repository.apache.org/content/repositories/orgapachejuddi-1017
>>>
>>> and we have a tag at:
>>>
>>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.7
>>>
>>> Please give it a spin and cast your vote. This vote will be open for
>>> the next 72 hours per the release policy, which is:
>>> - the vote will be closed as soon as 6 hours have past and  >7 +1
>>> votes are received with no -1 vote being cast, or
>>>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>>>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
>>> that
>>>  - after 72h provided at least 3 +1 votes have been cast and there is
>>> a majority of +1 votes from the cast votes.
>>>
>>> +1 for me
>>>
>>> Bug
>>>
>>>- [JUDDI-991 <https://jira.apache.org/jira/browse/JUDDI-991>] -
>>>JUDDI Uses EOL Version of Apache CXF
>>>- [JUDDI-996 <https://jira.apache.org/jira/browse/JUDDI-996>] -
>>>Admin gui, get all client subscriptions throws a classcast error
>>>- [JUDDI-997 <https://jira.apache.org/jira/browse/JUDDI-997>] -
>>>Admin gui has strange behavior and no feedback if the login fails
>>>- [JUDDI-999 <https://jira.apache.org/jira/browse/JUDDI-999>] -
>>>Issue with SQL Server Database with JUDDI 3.3.6 : The size (8192) given 
>>> to
>>>the column 'instance_parms' exceeds the maximum allowed for any data type
>>>(8000)
>>>
>>> Improvement
>>>
>>>- [JUDDI-995 <https://jira.apache.org/jira/browse/JUDDI-995>] - Add
>>>automated generation of sha512 hashes during the build
>>>- [JUDDI-1000 <https://jira.apache.org/jira/browse/JUDDI-1000>] -
>>>Update embedded tomcat to the latest version available
>>>
>>> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: Updating the demo site

2019-09-21 Thread Steve Viens 
Not Guilty! ... but good grief - I am totally guilty of negligence.  I
completely forgot about this.  My apologies.

Steve



On Sat, Sep 21, 2019 at 4:23 PM Kurt Stam  wrote:

> Steve did it!
>
> On Sep 21, 2019, at 22:20, Alex O'Ree  wrote:
>
> 
> did anyone delete the root business? hmmm
>
> On Wed, Jul 31, 2019 at 11:55 AM Steve Viens  wrote:
>
>> Awesome Alex.  I’ve been buried for past two weeks and just catching up
>> with personal email and saw yours.  I’ll take a look as soon as I can.
>>
>> Steve
>>
>> On Sat, Jul 27, 2019 at 8:47 PM Alex O'Ree  wrote:
>>
>>> good news, i got the demo set up and running
>>>
>>> https://demo.juddi.apache.org/
>>> some important paths
>>> /var/log/tomcat9
>>> /var/lib/tomcat9/webapps
>>> /etc/tomcat9
>>>
>>> the original tomcat root app was moved to /opt in case we need it in the
>>> future.
>>> ssl cert is via lets encrypt, good until oct 25th
>>>
>>> the hard part was getting derby to fire up. it ended up at
>>> /etc/tomcat9/Catalina/...
>>> all other locations had file permissions issues (or maybe a security
>>> manager?)
>>>
>>> finally the site also runs on port 80 if needed, but tls should be used
>>> when possible.
>>>
>>> On Sat, Jul 27, 2019 at 5:23 PM Alex O'Ree  wrote:
>>>
>>>> Steve, Kurt
>>>>
>>>> Please confirm that you can sign into (via ssh) demo.juddi.apache.org
>>>> use your asf credentials. You'll also want to test sudoing. ASF infra
>>>> uses something all opie for open time passwords for sudo.
>>>> Details here:
>>>> https://issues.apache.org/jira/browse/INFRA-18617?focusedCommentId=16893249=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16893249
>>>>
>>>> Anyhow, try to sign in and run
>>>> ortpasswd
>>>> use the linked website to create the one time password and paste it in
>>>> then run
>>>> sudo apt update
>>>> it should prompt for a open time password, again, repeat the process
>>>>
>>>> On Tue, Jun 18, 2019 at 5:33 PM Steve Viens  wrote:
>>>>
>>>>> I’ll volunteer!  Sign me up.
>>>>>
>>>>> Steve
>>>>>
>>>>> On Tue, Jun 18, 2019 at 5:26 PM Alex O'Ree 
>>>>> wrote:
>>>>>
>>>>>> Thanks Kurt!
>>>>>>
>>>>>> Just need one more person to act as a backup
>>>>>>
>>>>>> On Tue, Jun 18, 2019 at 10:30 AM Kurt Stam 
>>>>>> wrote:
>>>>>>
>>>>>>> Hi Alex,
>>>>>>>
>>>>>>> I can help.
>>>>>>>
>>>>>>> Cheers,
>>>>>>>
>>>>>>> —Kurt
>>>>>>>
>>>>>>> > On Jun 15, 2019, at 4:57 PM, Alex O'Ree 
>>>>>>> wrote:
>>>>>>> >
>>>>>>> > Dear jUDDI enthusiasts,
>>>>>>> >
>>>>>>> > We used to have a "gear" in the redhat cloud that hosted a demo
>>>>>>> instance of juddi. I'm not too sure what happened but i think it either
>>>>>>> expired or redhat turned them all off or whatever and migrated to 
>>>>>>> something
>>>>>>> else. Regardless, that instance has been dead for a while.
>>>>>>> >
>>>>>>> > Moving forward, i've asked the ASF infra team if they have a
>>>>>>> solution. The answer is yes, they can fire up a VM for this purpose. The
>>>>>>> only catch is that they want to have at least 3 people be designated as
>>>>>>> maintainers of the VM.
>>>>>>> >
>>>>>>> > I'll certainly volunteer but i'll need 2 others to volunteer in
>>>>>>> order to move forward. I would expect that time requirement by those
>>>>>>> volunteers would be super minimal, every now and again type of thing. 
>>>>>>> It'll
>>>>>>> be an ubuntu vm.
>>>>>>> >
>>>>>>> > Anyone out there want to help?
>>>>>>
>>>>>>
>>>>>>>
>>>>>>> --
>>>>> Steve Viens
>>>>> svi...@gmail.com
>>>>> 603-828-2397
>>>>>
>>>> --
>> Steve Viens
>> svi...@gmail.com
>> 603-828-2397
>>
>

Re: Updating the demo site

2019-07-31 Thread Steve Viens 
Awesome Alex.  I’ve been buried for past two weeks and just catching up
with personal email and saw yours.  I’ll take a look as soon as I can.

Steve

On Sat, Jul 27, 2019 at 8:47 PM Alex O'Ree  wrote:

> good news, i got the demo set up and running
>
> https://demo.juddi.apache.org/
> some important paths
> /var/log/tomcat9
> /var/lib/tomcat9/webapps
> /etc/tomcat9
>
> the original tomcat root app was moved to /opt in case we need it in the
> future.
> ssl cert is via lets encrypt, good until oct 25th
>
> the hard part was getting derby to fire up. it ended up at
> /etc/tomcat9/Catalina/...
> all other locations had file permissions issues (or maybe a security
> manager?)
>
> finally the site also runs on port 80 if needed, but tls should be used
> when possible.
>
> On Sat, Jul 27, 2019 at 5:23 PM Alex O'Ree  wrote:
>
>> Steve, Kurt
>>
>> Please confirm that you can sign into (via ssh) demo.juddi.apache.org
>> use your asf credentials. You'll also want to test sudoing. ASF infra
>> uses something all opie for open time passwords for sudo.
>> Details here:
>> https://issues.apache.org/jira/browse/INFRA-18617?focusedCommentId=16893249=com.atlassian.jira.plugin.system.issuetabpanels%3Acomment-tabpanel#comment-16893249
>>
>> Anyhow, try to sign in and run
>> ortpasswd
>> use the linked website to create the one time password and paste it in
>> then run
>> sudo apt update
>> it should prompt for a open time password, again, repeat the process
>>
>> On Tue, Jun 18, 2019 at 5:33 PM Steve Viens  wrote:
>>
>>> I’ll volunteer!  Sign me up.
>>>
>>> Steve
>>>
>>> On Tue, Jun 18, 2019 at 5:26 PM Alex O'Ree 
>>> wrote:
>>>
>>>> Thanks Kurt!
>>>>
>>>> Just need one more person to act as a backup
>>>>
>>>> On Tue, Jun 18, 2019 at 10:30 AM Kurt Stam  wrote:
>>>>
>>>>> Hi Alex,
>>>>>
>>>>> I can help.
>>>>>
>>>>> Cheers,
>>>>>
>>>>> —Kurt
>>>>>
>>>>> > On Jun 15, 2019, at 4:57 PM, Alex O'Ree  wrote:
>>>>> >
>>>>> > Dear jUDDI enthusiasts,
>>>>> >
>>>>> > We used to have a "gear" in the redhat cloud that hosted a demo
>>>>> instance of juddi. I'm not too sure what happened but i think it either
>>>>> expired or redhat turned them all off or whatever and migrated to 
>>>>> something
>>>>> else. Regardless, that instance has been dead for a while.
>>>>> >
>>>>> > Moving forward, i've asked the ASF infra team if they have a
>>>>> solution. The answer is yes, they can fire up a VM for this purpose. The
>>>>> only catch is that they want to have at least 3 people be designated as
>>>>> maintainers of the VM.
>>>>> >
>>>>> > I'll certainly volunteer but i'll need 2 others to volunteer in
>>>>> order to move forward. I would expect that time requirement by those
>>>>> volunteers would be super minimal, every now and again type of thing. 
>>>>> It'll
>>>>> be an ubuntu vm.
>>>>> >
>>>>> > Anyone out there want to help?
>>>>
>>>>
>>>>>
>>>>> --
>>> Steve Viens
>>> svi...@gmail.com
>>> 603-828-2397
>>>
>> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: Updating the demo site

2019-06-18 Thread Steve Viens 
I’ll volunteer!  Sign me up.

Steve

On Tue, Jun 18, 2019 at 5:26 PM Alex O'Ree  wrote:

> Thanks Kurt!
>
> Just need one more person to act as a backup
>
> On Tue, Jun 18, 2019 at 10:30 AM Kurt Stam  wrote:
>
>> Hi Alex,
>>
>> I can help.
>>
>> Cheers,
>>
>> —Kurt
>>
>> > On Jun 15, 2019, at 4:57 PM, Alex O'Ree  wrote:
>> >
>> > Dear jUDDI enthusiasts,
>> >
>> > We used to have a "gear" in the redhat cloud that hosted a demo
>> instance of juddi. I'm not too sure what happened but i think it either
>> expired or redhat turned them all off or whatever and migrated to something
>> else. Regardless, that instance has been dead for a while.
>> >
>> > Moving forward, i've asked the ASF infra team if they have a solution.
>> The answer is yes, they can fire up a VM for this purpose. The only catch
>> is that they want to have at least 3 people be designated as maintainers of
>> the VM.
>> >
>> > I'll certainly volunteer but i'll need 2 others to volunteer in order
>> to move forward. I would expect that time requirement by those volunteers
>> would be super minimal, every now and again type of thing. It'll be an
>> ubuntu vm.
>> >
>> > Anyone out there want to help?
>>
>> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: [NOTICE] Mandatory relocation of Apache git repositories on git-wip-us.apache.org

2018-12-09 Thread Steve Viens 
+1 from me too.

Steve

On Sun, Dec 9, 2018 at 5:58 PM Kurt Stam  wrote:

> +1 from me too
>
> Where will we move to? Github or gitbox.apache.org?
>
> On Dec 8, 2018, at 5:09 PM, Alex O'Ree  wrote:
>
> Juddi devs, I got this from infra yesterday and it does apply to both
> juddi and scout. It sounds like it will be a minimal impact besides
> updating some links on the website and poms.
> All those in favor of moving during the voluntary time period, vote +1
> otherwise state your intentions.
>
> +1 for the voluntary period for me.
>
>
> -- Forwarded message -
> From: Daniel Gruno 
> Date: Fri, Dec 7, 2018, 11:52 AM
> Subject: [NOTICE] Mandatory relocation of Apache git repositories on
> git-wip-us.apache.org
> To: us...@infra.apache.org 
>
>
> [IF YOUR PROJECT DOES NOT HAVE GIT REPOSITORIES ON GIT-WIP-US PLEASE
>   DISREGARD THIS EMAIL; IT WAS MASS-MAILED TO ALL APACHE PROJECTS]
>
> Hello Apache projects,
>
> I am writing to you because you may have git repositories on the
> git-wip-us server, which is slated to be decommissioned in the coming
> months. All repositories will be moved to the new gitbox service which
> includes direct write access on github as well as the standard ASF
> commit access via gitbox.apache.org.
>
> ## Why this move? ##
> The move comes as a result of retiring the git-wip service, as the
> hardware it runs on is longing for retirement. In lieu of this, we
> have decided to consolidate the two services (git-wip and gitbox), to
> ease the management of our repository systems and future-proof the
> underlying hardware. The move is fully automated, and ideally, nothing
> will change in your workflow other than added features and access to
> GitHub.
>
> ## Timeframe for relocation ##
> Initially, we are asking that projects voluntarily request to move
> their repositories to gitbox, hence this email. The voluntary
> timeframe is between now and January 9th 2019, during which projects
> are free to either move over to gitbox or stay put on git-wip. After
> this phase, we will be requiring the remaining projects to move within
> one month, after which we will move the remaining projects over.
>
> To have your project moved in this initial phase, you will need:
>
> - Consensus in the project (documented via the mailing list)
> - File a JIRA ticket with INFRA to voluntarily move your project repos
>over to gitbox (as stated, this is highly automated and will take
>between a minute and an hour, depending on the size and number of
>your repositories)
>
> To sum up the preliminary timeline;
>
> - December 9th 2018 -> January 9th 2019: Voluntary (coordinated)
>relocation
> - January 9th -> February 6th: Mandated (coordinated) relocation
> - February 7th: All remaining repositories are mass migrated.
>
> This timeline may change to accommodate various scenarios.
>
> ## Using GitHub with ASF repositories ##
> When your project has moved, you are free to use either the ASF
> repository system (gitbox.apache.org) OR GitHub for your development
> and code pushes. To be able to use GitHub, please follow the primer
> at: https://reference.apache.org/committer/github
>
>
> We appreciate your understanding of this issue, and hope that your
> project can coordinate voluntarily moving your repositories in a
> timely manner.
>
> All settings, such as commit mail targets, issue linking, PR
> notification schemes etc will automatically be migrated to gitbox as
> well.
>
> With regards, Daniel on behalf of ASF Infra.
>
> PS:For inquiries, please reply to us...@infra.apache.org, not your
> project's dev list :-).
>
>
>
> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: [VOTE] SCOUT v1.2.8

2018-12-05 Thread Steve Viens 
+1

Steve Viens
svi...@gmail.com
603-828-2397


On Wed, Dec 5, 2018 at 3:00 PM Alex O'Ree  wrote:

> Dear jUDDI enthusiasts,
>
> The new release for SCOUT is here! This release resolves 5 JIRAs, most of
> them are bug fixes and maintenance related issues. It also resolves several
> issues that were introduced when resolving UDDI spec adherence with jUDDI
> 3.1.5 that were never retested with SCOUT. The largest change was related
> to JXR Address to UDDI Addressline line mappings which may cause some
> issues if upgrading.
>
> The release distribution is temporarily available here (without hashes)
>
> https://www.dropbox.com/sh/v4patewpkybo8an/AABWquVy2IUxBo1NPEJr_I_3a?dl=0
>
> The release artifacts are staged in nexus:
> *https://repository.apache.org/content/repositories/orgapachejuddi-1016
> <https://repository.apache.org/content/repositories/orgapachejuddi-1016>*
>
> and we have a tag at:
> *https://git-wip-us.apache.org/repos/asf?p=juddi-scout.git;a=log;h=refs/tags/scout-1.2.8
> <https://git-wip-us.apache.org/repos/asf?p=juddi-scout.git;a=log;h=refs/tags/scout-1.2.8>*
>
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
> Bug
>
>- [SCOUT-132 <https://issues.apache.org/jira/browse/SCOUT-132>] - Bad
>string generation for logs/exceptions
>- [SCOUT-133 <https://issues.apache.org/jira/browse/SCOUT-133>] -
>Website lists 1.2.6 as the latest version, however there is a tag and a
>release for 1.2.7
>- [SCOUT-134 <https://issues.apache.org/jira/browse/SCOUT-134>] -
>Scout runs integration tests against a very old version of jUDDI, running
>against the current causes compile errors and unit test failures
>- [SCOUT-135 <https://issues.apache.org/jira/browse/SCOUT-135>] -
>Incorrect mappings for UDDI Address line
>- [SCOUT-136 <https://issues.apache.org/jira/browse/SCOUT-136>] -
>Scout adds sort by name desc to findBinding UDDI requests, which is invalid
>
>

Re: [VOTE] jUDDI v3.3.6 (second attempt)

2018-12-02 Thread Steve Viens 
+1

On Sun, Dec 2, 2018 at 5:45 PM Anil Saldanha  wrote:

> +1
>
> ~~
>
> On Dec 2, 2018, at 12:37 PM, Alex O'Ree  wrote:
>
> Dear jUDDI enthusiasts,
>
> The new release is here! This release resolves 4 JIRAs, 2 tasks and 2 bug
> fixes related to incorrect logic of the findBinding API and some line
> ending issues with bash scripts. The API bug was preventing updates to the
> SCOUT project. Once this release is complete, then we can cut a new version
> of SCOUT. The release notes file is missing the bash script issue but other
> than that, it should be good to go.
>
> The release distribution is temporarily available here (without hashes)
> *https://www.dropbox.com/sh/4rsd8o78nib8o7s/AABjmEhGK4PAYLSDnYj5x6tba?dl=0
> <https://www.dropbox.com/sh/4rsd8o78nib8o7s/AABjmEhGK4PAYLSDnYj5x6tba?dl=0>*
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1014
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.6
> r2
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
> Bug
>
>- [JUDDI-992 <https://issues.apache.org/jira/browse/JUDDI-992>] -
>FindBinding API call doesn't exactly match the spec, can't search for just
>the service key
>-
>   1. [JUDDI-994 <https://issues.apache.org/jira/browse/JUDDI-994>]
>   - Bash scripts containing windows CRLF line endings
>
> Improvement
>
>- [JUDDI-988 <https://issues.apache.org/jira/browse/JUDDI-988>] -
>Update to tomcat 9
>
> Task
>
>- [JUDDI-962 <https://issues.apache.org/jira/browse/JUDDI-962>] -
>Convert juddi.apache.org back to mvn site
>
> --
Steve Viens
svi...@gmail.com
603-828-2397

Re: [VOTE] jUDDI-3.3.6

2018-11-26 Thread Steve Viens 
Hi Alex, are you waiting for Apache Scout commit privs or having difficulty 
contacting them? 

About to fly out of Logan ... will download, try and reply this afternoon.  

Steve

Sent from my iPhone

> On Nov 26, 2018, at 5:39 AM, Kurt Stam  wrote:
> 
> Hi Alex,
> 
> The file format of the juddi-distro-3.3.6/juddi-tomcat-3.3.6/bin/catalina.sh
> 
> Is not unix, so it won’t startup tomcat. What do you prefer, adding something 
> to the release notes or do you want to respin the release?
> 
> Cheers,
> 
> —Kurt
> 
>> On Nov 24, 2018, at 8:53 PM, Alex O'Ree  wrote:
>> 
>> Dear jUDDI enthusiasts,
>> 
>> The new release is here! This release resolves 3 JIRAs, 2 tasks and a bug 
>> fix related to incorrect logic of the findBinding API. The bug was 
>> preventing updates to the SCOUT project. Once this release is complete (and 
>> I finally get commit permissions on SCOUT), then we can cut a new version of 
>> SCOUT. 
>> 
>> The release distribution is temporarily available here (without hashes)
>> https://www.dropbox.com/sh/loyuchxtxg0zrwq/AAA4nqh9rUBEXiRQ7JK43fl6a?dl=0
>> 
>> The release artifacts are staged in nexus:
>> https://repository.apache.org/content/repositories/orgapachejuddi-1013/
>> 
>> and we have a tag at:
>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.6
>> 
>> Please give it a spin and cast your vote. This vote will be open for
>> the next 72 hours per the release policy, which is:
>> - the vote will be closed as soon as 6 hours have past and  >7 +1
>> votes are received with no -1 vote being cast, or
>>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing that
>>  - after 72h provided at least 3 +1 votes have been cast and there is
>> a majority of +1 votes from the cast votes.
>> 
>> Bug
>> [JUDDI-992] - FindBinding API call doesn't exactly match the spec, can't 
>> search for just the service key
>> Improvement
>> [JUDDI-988] - Update to tomcat 9
>> Task
>> [JUDDI-962] - Convert juddi.apache.org back to mvn site
>

Re: [VOTE] convert juddi back to mvn site

2018-02-09 Thread Steve Viens 
+1 for mvn 

Steve

Sent from my iPhone

> On Feb 9, 2018, at 10:00 AM, Kurt Stam  wrote:
> 
> +1 for mvn site.
> 
> —Kurt
> 
>> On Feb 9, 2018, at 9:14 AM, Alex O'Ree  wrote:
>> 
>> A while ago, we switched from a maven based site to the Apache CMS based 
>> site. There are some pros and cons of this setup.
>> 
>> Pros (for using CMS over mvn site)
>> - Site can be updated at any point in time, independent of maven builds
>> - Builds are usually very quick and do not require
>> 
>> Cons
>> - Source control is not in the main repository. As a committer, i need to 
>> have 5 repos checked out pretty much all the time.
>> 
>> So I'm proposing that we which back to a maven based site. I've already done 
>> the work and the source is up to date with what is currently on 
>> juddi.apache.org. There will be some minor formatting differences but for 
>> the most part the change is minimal. Assuming the vote passes, I'll open a 
>> infra ticket to start the switch
>> 
>> To prevent the site, simple check out our git repo, then use `mvn site`. 
>> Standard voting rules apply.
>> 
>> +1 i'm obviously for it
>

Re: [VOTE] jUDDI-3.3.5

2017-11-15 Thread Steve Viens 
Sorry Alex.  Thank you for keeping jUDDI alive!

+1

Steve Viens
svi...@gmail.com
603-828-2397 <(603)%20828-2397>

On Tue, Nov 14, 2017 at 7:46 PM, Alex O'Ree <alexo...@apache.org> wrote:

> 3 days and not a single vote. Perhaps I wasn't clear enough. This set of
> fixes resolves a number of security issues.
>
> Is it time to retire this project?
>
> I don't mine maintaining it but ASF is committee driven and has pretty
> specific rules. A passing vote is required for release and we can't get
> enough votes for a release that resolves security issues, we'll have to
> move this to the attic.
>
> On Sat, Nov 11, 2017 at 8:26 PM, Alex O'Ree <alexo...@apache.org> wrote:
>
>> Dear jUDDI enthusiasts,
>>
>> The new release is here! This release resolves 23 JIRAs, primarily bug
>> fixes and resolves several security related issues.
>>
>> The release distribution is temporarily available here
>> https://www.dropbox.com/sh/4j3n8z1c0ssbn0v/AACOs0pyLdQQW2HQ0JI52ToWa?dl=0
>>
>> The release artifacts are staged in nexus:
>> *https://repository.apache.org/content/repositories/orgapachejuddi-1011
>> <https://repository.apache.org/content/repositories/orgapachejuddi-1011>*
>>
>> and we have a tag at:
>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.g
>> it;a=tag;h=refs/tags/juddi-3.3.
>> <https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.3.4>
>> 5
>>
>> Please give it a spin and cast your vote. This vote will be open for
>> the next 72 hours per the release policy, which is:
>> - the vote will be closed as soon as 6 hours have past and  >7 +1
>> votes are received with no -1 vote being cast, or
>>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
>> that
>>  - after 72h provided at least 3 +1 votes have been cast and there is
>> a majority of +1 votes from the cast votes.
>> Bug
>>
>>- [JUDDI-904 <https://issues.apache.org/jira/browse/JUDDI-904>] -
>>intermittent test failures
>>- [JUDDI-943 <https://issues.apache.org/jira/browse/JUDDI-943>] -
>>WebHelper class: Client name not set in servletContext after getUDDIClient
>>is called
>>- [JUDDI-948 <https://issues.apache.org/jira/browse/JUDDI-948>] -
>>API_070_FindEntityTest is not passing anymore
>>- [JUDDI-957 <https://issues.apache.org/jira/browse/JUDDI-957>] -
>>Integration test not passing. org.apache.juddi.v3.tck.UDDI_0
>>70_FindEntityIntegrationTest:findSignedEntities()
>>- [JUDDI-960 <https://issues.apache.org/jira/browse/JUDDI-960>] - TCK
>>tests not passing (windows 7, java 1.8)
>>- [JUDDI-970 <https://issues.apache.org/jira/browse/JUDDI-970>] -
>>Code smell that ignores InvalidValueException
>>- [JUDDI-975 <https://issues.apache.org/jira/browse/JUDDI-975>] - mvn
>>site is broken
>>- [JUDDI-977 <https://issues.apache.org/jira/browse/JUDDI-977>] -
>>reduce findbugs warnings
>>- [JUDDI-978 <https://issues.apache.org/jira/browse/JUDDI-978>] -
>>Build instability with Replication tests
>>- [JUDDI-983 <https://issues.apache.org/jira/browse/JUDDI-983>] -
>>Unable to compile under centos, openjdk8, 
>> sun.security.provider.certpath.OCSP
>>api mismatch
>>- [JUDDI-984 <https://issues.apache.org/jira/browse/JUDDI-984>] -
>>Hibernate profile fails to deploy due to extraneous class in the orm xml
>>file
>>- [JUDDI-985 <https://issues.apache.org/jira/browse/JUDDI-985>] -
>>Replication change record delete fails with hibernate
>>- [JUDDI-987 <https://issues.apache.org/jira/browse/JUDDI-987>] - TBD
>>
>> Improvement
>>
>>- [JUDDI-955 <https://issues.apache.org/jira/browse/JUDDI-955>] - Pom
>>maintenance
>>- [JUDDI-974 <https://issues.apache.org/jira/browse/JUDDI-974>] - Add
>>findbugs to the site reporting tasks
>>- [JUDDI-979 <https://issues.apache.org/jira/browse/JUDDI-979>] - Add
>>maven enforcer rules
>>- [JUDDI-980 <https://issues.apache.org/jira/browse/JUDDI-980>] -
>>Update juddi's parent pom to the latest apache pom
>>- [JUDDI-981 <https://issues.apache.org/jira/browse/JUDDI-981>] -
>>Force all tests to run in a random order
>>- [JUDDI-986 <https://issues.apache.org/jira/browse/JUDDI-986>] -
>>Update hibernate dependencies
>>
>> Task
>>
>>- [JUDDI-971 <https://issues.apache.org/jira/browse/JUDDI-971>] -
>>Update embedded tomcat to a more recent version
>>- [JUDDI-973 <https://issues.apache.org/jira/browse/JUDDI-973>] -
>>Code clean up juddi-client-cli
>>- [JUDDI-976 <https://issues.apache.org/jira/browse/JUDDI-976>] - Add
>>jacoco test results to mvn site
>>- [JUDDI-982 <https://issues.apache.org/jira/browse/JUDDI-982>] -
>>Removing the juddi-client-plugins module
>>
>>
>>
>>
>>
>

Re: [VOTE] jUDDI-3.3.4 (fixed)

2017-02-05 Thread Steve Viens 
+1 from me as well.

Steve Viens
svi...@gmail.com
603-828-2397

On Sun, Feb 5, 2017 at 10:24 AM, Kurt T Stam <kurt.s...@gmail.com> wrote:

> +1 from me. --Kurt
>
> On 2/5/17 8:30 AM, Alex O'Ree wrote:
>
>> Sorry, the last email had the incorrect subject line!
>>
>>
>> Dear jUDDI enthusiasts,
>>
>> The new release is here! This release is primarily bug fixes.
>>
>> The release distribution is temporarily available here
>> https://www.dropbox.com/sh/bt7jes1jzl94qh1/AACh43p7QIfu5hyCb9gut6_Ka?dl=0
>>
>> The release artifacts are staged in nexus:
>> https://repository.apache.org/content/repositories/orgapachejuddi-1009/
>>
>> and we have a tag at:
>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.g
>> it;a=tag;h=refs/tags/juddi-3.3.4
>>
>>
>> Small change set this time. 1 bug fix and the rest were pom updates.
>> Testing on non default tomcat/cxf/debry containers is appreciated.
>>
>>
>> Please give it a spin and cast your vote. This vote will be open for
>> the next 72 hours per the release policy, which is:
>> - the vote will be closed as soon as 6 hours have past and  >7 +1
>> votes are received with no -1 vote being cast, or
>>   - if after 12h >5 +1 votes have been cast with no -1 vote, or
>>   - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
>> that
>>   - after 72h provided at least 3 +1 votes have been cast and there is
>> a majority of +1 votes from the cast votes.
>>
>>
>> +1
>>
>> Bug
>>
>> [JUDDI-967] - Suspicious incrementers in for loops
>> [JUDDI-968] - Update pom dependencies for vulnerable libraries
>>
>
>
>

Re: [VOTE] Release jUDDI-3.3.3

2016-09-12 Thread Steve Viens 
+1

Steve Viens
svi...@gmail.com
603-828-2397

On Sun, Sep 11, 2016 at 4:15 PM, Alex O'Ree <spyhunte...@gmail.com> wrote:

> Dear jUDDI enthusiasts,
>
> The new release is here! This release is primarily bug fixes.
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/qu3g9jwz9j8yws9/AABHG45Fuw71X_eBWRpn-gj3a?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1007/
>
> and we have a tag at:
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.
> git;a=tag;h=refs/tags/juddi-3.3.3
>
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
>
> +1
>
>
> Bug
>
> [JUDDI-945] - Validation error in the JUDDI web.xml (non-Tomcat containers)
> [JUDDI-946] - Incorrect annotation on JPA entity classes
> [JUDDI-951] - EntityManagerFactory not closed when undeploying juddi
> [JUDDI-953] - juddi-core and juddi-core-openjpa do not use the same JPA
> version
> [JUDDI-956] - Adding a tModel without category as Keyed Reference
> Groups to another tModel generates an exception.
> [JUDDI-958] - Running mvn clean install -Pdist fails (validation of
> apache licences by rat plugin fails)
> [JUDDI-959] - Running mvn clean install -Pdist fails with java 1.8
> (javadocs generation problem)
> [JUDDI-965] - DispositionReportFaultMessage is hiding exception messages
> [JUDDI-966] - sources jars are no longer installed while building juddi
>
> Improvement
>
> [JUDDI-947] - Avoid copying the source juddi-core in juddi-core-openjpa
> [JUDDI-952] - Add unit test code coverage reports
>
> Task
>
> [JUDDI-944] - update the gitignore file
>

Re: [VOTE] Release jUDDI-3.3.2

2015-11-09 Thread Steve Viens 
+1 from me as well.

Steve

On Sun, Nov 8, 2015 at 10:44 PM, Alex O'Ree  wrote:

> Dear jUDDI enthusiasts,
>
> The new release is here! This release is primarily bug fixes.
>
> The release distribution is temporarily available here
> https://www.dropbox.com/sh/1j59ewsxz57k6xl/AAC1Gq8YLgL_CneWOQENeQFya?dl=0
>
> The release artifacts are staged in nexus:
> https://repository.apache.org/content/repositories/orgapachejuddi-1006
>
> and we have a tag at:
>
> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=commit;h=de58d7deaddf52ae5c93e289d70ac2af60f6a6cf
>
>
> Please give it a spin and cast your vote. This vote will be open for
> the next 72 hours per the release policy, which is:
> - the vote will be closed as soon as 6 hours have past and  >7 +1
> votes are received with no -1 vote being cast, or
>  - if after 12h >5 +1 votes have been cast with no -1 vote, or
>  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
> that
>  - after 72h provided at least 3 +1 votes have been cast and there is
> a majority of +1 votes from the cast votes.
>
>
>
> My vote, +1
>
>
> Release Notes:
>
> Bug
>
> [JUDDI-936] - OutOfMemoryError accessing admin interface.
> [JUDDI-938] - Javadoc incorrect (UDDIServiceCache)
> [JUDDI-939] - NullPointerException when using service cache
> [JUDDI-940] - Wrong namespace for portType: "UDDI_Inquiry_PortType"
> (not compliant with UDDI V3 !)
>

Re: [VOTE] Release jUDDI-3.3.1

2015-10-04 Thread Steve Viens 
+1

Sent from my iPhone

> On Oct 4, 2015, at 8:31 AM, Alex O'Ree  wrote:
> 
> ping, we're over 3 days now. we need a few more votes for release
> 
>> On Wed, Sep 30, 2015 at 10:59 PM, Kurt Stam  wrote:
>> +1 from me! --Kurt
>> 
>>> On Sep 30, 2015, at 18:24, Alex O'Ree  wrote:
>>> 
>>> Dear jUDDI enthusiasts,
>>> 
>>> The new release is here! This release is primarily bug fixes and the
>>> inclusion of the CLI client.
>>> 
>>> The release distribution is temporarily available here
>>> https://www.dropbox.com/sh/zycq6j314gvuy52/AAAzhvpRqOXsmEQXaAiIExtBa?dl=0
>>> 
>>> 
>>> The release artifacts are staged in nexus:
>>> https://repository.apache.org/content/repositories/orgapachejuddi-1005/
>>> 
>>> and we have a tag at:
>>> https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=2e8c72ce557a9b5bd673c03fc5300179fb1f2db4
>>> 
>>> 
>>> Please give it a spin and cast your vote. This vote will be open for
>>> the next 72 hours per the release policy, which is:
>>> - the vote will be closed as soon as 6 hours have past and  >7 +1
>>> votes are received with no -1 vote being cast, or
>>> - if after 12h >5 +1 votes have been cast with no -1 vote, or
>>> - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing that
>>> - after 72h provided at least 3 +1 votes have been cast and there is
>>> a majority of +1 votes from the cast votes.
>>> 
>>> 
>>> 
>>> My vote, +1
>>> 
>>> 
>>> Release Notes:
>>> 
>>> Bug
>>> 
>>> [JUDDI-934] - jUDDI CLI client is not included in the distribution zips
>>> [JUDDI-935] - AdminUI/Statistics page fails to render under JDK8
>>> 
>>> Improvement
>>> 
>>> [JUDDI-933] - File based authentication mechanisms do not auto insert
>>> to the database

Re: [VOTE] Release jUDDI-3.3.0

2015-07-10 Thread Steve Viens 
My vote is +1

Steve Viens
svi...@gmail.com
603-828-2397

On Thu, Jul 9, 2015 at 7:30 PM, Alex O'Ree alexo...@apache.org wrote:

 Dear jUDDI enthusiasts,

 The new release is here! We are long overdue (again!). This release is
 primarily bug fixes however there's a number of new features. Just check
 out the release notes below!

 Here’s are some highlights for this version 3.3.0

-

Implementation of UDDIv3 Replication API and completed implementation
of the Custody Transfer API

-

juddi-gui, numerous enhancements, service editor was redesigned to
help make binding editing easier and simpler, more i18n work and security
fixes
-

Nodes can change IDs
-

More administrative UI capabilities
-

A semi full featured command line jUDDI client

 With this release have have two distros, a juddi and a uddi-client. The
 juddi-distro has the server, client and gui, the uddi-client-distro has the
 client, the gui and our TCK.

 The release artifacts are staged in nexus:

 *https://repository.apache.org/content/repositories/orgapachejuddi-1004/
 https://repository.apache.org/content/repositories/orgapachejuddi-1004/*

 and we have a tag at

 *https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=c3dbbabdd30f393e12ceae74fb40211d0ddde384
 https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=c3dbbabdd30f393e12ceae74fb40211d0ddde384*



 Please give it a spin and cast your vote. This vote will be open for the
 next 72 hours per the release policy, which is:
 - the vote will be closed as soon as 6 hours have past and  7 +1 votes are
 received with no -1 vote being cast, or
  - if after 12h 5 +1 votes have been cast with no -1 vote, or
  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing
 that
  - after 72h provided at least 3 +1 votes have been cast and there is a
 majority of +1 votes from the cast votes.



 My vote, +1

 Sub-task

- [JUDDI-753 https://issues.apache.org/jira/browse/JUDDI-753] - Add
jpa classes for the uddi replication data structures
- [JUDDI-895 https://issues.apache.org/jira/browse/JUDDI-895] - add
install data for replication config
- [JUDDI-901 https://issues.apache.org/jira/browse/JUDDI-901] -
update admin user interface
- [JUDDI-906 https://issues.apache.org/jira/browse/JUDDI-906] -
Create tck test cases for replication
- [JUDDI-910 https://issues.apache.org/jira/browse/JUDDI-910] -
Implement directed graph replication
- [JUDDI-916 https://issues.apache.org/jira/browse/JUDDI-916] -
reduce logout of replication related activities
- [JUDDI-917 https://issues.apache.org/jira/browse/JUDDI-917] -
juddi api adminSaveBusiness/TModel changes should be added for 
 replicatation
- [JUDDI-919 https://issues.apache.org/jira/browse/JUDDI-919] -
investigate security options for the replication processes

 Bug

- [JUDDI-242 https://issues.apache.org/jira/browse/JUDDI-242] -
Expand UDDI_090_SubscriptionListenerIntegrationTest to more elements
- [JUDDI-256 https://issues.apache.org/jira/browse/JUDDI-256] - We
need a test for CustodyTransfer
- [JUDDI-644 https://issues.apache.org/jira/browse/JUDDI-644] -
Subscription Integration Listener SMTP Tests fail intermittently on Windows
- [JUDDI-653 https://issues.apache.org/jira/browse/JUDDI-653] -
Build fails on Ubuntu using OpenJDK
- [JUDDI-708 https://issues.apache.org/jira/browse/JUDDI-708] -
juddi-client .NET mono compatibility
- [JUDDI-734 https://issues.apache.org/jira/browse/JUDDI-734] -
Handle when a Node changes it ID
- [JUDDI-735 https://issues.apache.org/jira/browse/JUDDI-735] -
juddi api wsdls do not have fault information listed
- [JUDDI-739 https://issues.apache.org/jira/browse/JUDDI-739] -
juddi-gui businessEditor throws up
- [JUDDI-743 https://issues.apache.org/jira/browse/JUDDI-743] -
UDDI_001_UDDIServiceTest has some invalid tests
- [JUDDI-747 https://issues.apache.org/jira/browse/JUDDI-747] -
Expand jUDDI API test cases
- [JUDDI-749 https://issues.apache.org/jira/browse/JUDDI-749] -
juddi-gui may throw NPE on redeploy
- [JUDDI-752 https://issues.apache.org/jira/browse/JUDDI-752] -
UDDI_040_BusinessServiceLoadTest fails to run
- [JUDDI-870 https://issues.apache.org/jira/browse/JUDDI-870] -
ORA-00910: specified length too long for its datatype in openjpa
- [JUDDI-873 https://issues.apache.org/jira/browse/JUDDI-873] -
Subscription Listener doesn't work for publisher assertion updates
- [JUDDI-881 https://issues.apache.org/jira/browse/JUDDI-881] -
find_business does not filter services when providing a tModelBag
- [JUDDI-891 https://issues.apache.org/jira/browse/JUDDI-891] -
revise juddi install data to match the root node id per spec
- [JUDDI-892 https://issues.apache.org/jira/browse/JUDDI-892] -
Broken links on juddi tomcat page
- [JUDDI-896 https

Re: [VOTE] Release jUDDI-3.2.1

2014-12-04 Thread Steve Viens 
+1

Sent from my iPhone

 On Dec 4, 2014, at 6:26 PM, Alex O'Ree spyhunte...@gmail.com wrote:
 
 Dear jUDDI enthusiasts,
 
 The new release is here! We are long overdue. This release is primarily bug 
 fixes however there's a number of new featuresJust check out the release 
 notes below!
 
 Here’s are some highlights for this version 3.2.1
 More TCK Tests were added and refactored
 
 
 juddi-gui, numerous enhancements, service editor was redesigned to help make 
 binding editing easier and simpler, more i18n work and security fixes
 
 
 DDL files are now generated at build time. No more manual updates
 
 
 With this release have have two distros, a juddi and a uddi-client. The 
 juddi-distro has the server, client and gui, the uddi-client-distro has the 
 client, the gui and our TCK. Both distros are staged here:
 
 http://people.apache.org/~kstam/releases/juddi-3.2.1/
 
 The release artifacts are staged in nexus:
 
 https://repository.apache.org/content/repositories/orgapachejuddi-1003
 
 and we have a tag at
 
 https://git-wip-us.apache.org/repos/asf/juddi.git/?p=juddi.git;a=tag;h=refs/tags/juddi-3.2.1
 
 and finally our new website is staged at:
 
 http://juddi.staging.apache.org/
 
 Please give it a spin and cast your vote. This vote will be open for the next 
 72 hours per the release policy, which is:
 - the vote will be closed as soon as 6 hours have past and  7 +1 votes are 
 received with no -1 vote being cast, or
  - if after 12h 5 +1 votes have been cast with no -1 vote, or
  - if after 24h if 3 +1 votes have been cast with no -1 vote, or failing that
  - after 72h provided at least 3 +1 votes have been cast and there is a 
 majority of +1 votes from the cast votes.
 
 
 
 My vote, +1
 
 
 Sub-task
 [JUDDI-754] - update ddl files
 Bug
 [JUDDI-587] - JUDDI incompatible with Hibernate 4.1.x and 4.2.x
 [JUDDI-699] - add automatic reauthentication to juddi-client UDDIClerk 
 functions
 [JUDDI-806] - refactor service editor, move binding templates to another page
 [JUDDI-835] - .net client only works for the home node
 [JUDDI-836] - The target namespace of publish v2 endpoint is 
 urn:uddi-org:inquiry_v2
 [JUDDI-838] - restore or recreate SCOUT web pages
 [JUDDI-839] - uddi-migration tool option preserveOwnership doesn't work
 [JUDDI-840] - Fix file authentication
 [JUDDI-841] - save entity permissions with undefined keys
 [JUDDI-843] - search for tmodel with lang defined returns no results
 [JUDDI-844] - links to user/admin guides point to the wrong version
 [JUDDI-845] - creating subscription for a specific tmodel throw 'alert 
 criteria invaliderror'
 [JUDDI-846] - i18n subscription editor error messages
 [JUDDI-847] - support signing binding templates
 [JUDDI-848] - Publish.SaveBinding throws up when passed an invalid key
 [JUDDI-850] - Filter invalid find qualifiers from UDDIv2 Mappers
 [JUDDI-851] - access control roles are incorrect for uddiv2 keys
 [JUDDI-852] - find binding's ListDescription's count values are always null
 [JUDDI-855] - findBinding with a service key defined always returns service 
 not found
 [JUDDI-857] - edit subscription page doesn't populate binding key
 [JUDDI-863] - save subscription doesn't check subscription key length
 [JUDDI-864] - Deploy to wildfly may fail with SubscriptionCallbackListener 
 may not declare a finalize() method
 [JUDDI-865] - subscription listener url is not mapped from clerk.getApiNode
 [JUDDI-866] - subscription notifier may fail to send messages under certain 
 conditions
 [JUDDI-867] - clerk does not honor methods that specify a node
 [JUDDI-871] - Insert empty j3_category_bag
 [JUDDI-875] - mvn hibernate3:hbm2ddl fails
 [JUDDI-878] - Fix Jboss AS 7.x deployment
 [JUDDI-883] - browse business page down won't function repeatedly
 [JUDDI-884] - CSRF Potential for juddi-gui/ajax/tmodelsearch.jsp
 [JUDDI-886] - web based digital signature applet fails to run due to missing 
 permissions attribute
 [JUDDI-889] - fix example juddi client config files (undefined xml prefix xsi)
 [JUDDI-890] - when saving a config with node/properties defined, the output 
 is concat'd
 Improvement
 [JUDDI-751] - Refactor Subscription TCK test cases
 [JUDDI-766] - add tck tests cases for find qualifiers
 [JUDDI-808] - add options to externalize encryption keys
 [JUDDI-812] - add in browser help on search page
 [JUDDI-831] - add tck tests for juddiv2 endpoints
 [JUDDI-832] - add uddiv2 apis to .net client
 [JUDDI-833] - modalize all save/failure ajax responses
 [JUDDI-849] - resolve issues with address line entry
 [JUDDI-853] - subscription callback api only works on the default node
 [JUDDI-868] - add client names to the error message
 [JUDDI-869] - misc formatting revisions
 [JUDDI-885] - when deleting a binding, redirect to the parent service's 
 detail pages
 New Feature
 [JUDDI-684] - juddi-gui add copy this entity button
 [JUDDI-764] - Add TCK test cases for all sort order and find qualifiers
 [JUDDI-773] - User friendly email subscription templates

Re: Proposal for a new Project Lead

2014-05-13 Thread Steve Viens 
No objections.  Thank you Kurt for your dedication to this project for so
long!

[jira] [Created] (JUDDI-837) Update jUDDI incubation site to better reflect that it graduated

2014-02-05 Thread Steve Viens (JIRA) 
Steve Viens created JUDDI-837:
-

 Summary: Update jUDDI incubation site to better reflect that it 
graduated
 Key: JUDDI-837
 URL: https://issues.apache.org/jira/browse/JUDDI-837
 Project: jUDDI
  Issue Type: Task
  Components: website
Affects Versions: 3.2
 Environment: Apache Incubator
Reporter: Alex O'Ree
Assignee: Steve Viens
Priority: Minor


Source of this work is in the following thread: 
http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser

Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI 
graduated in March 2014.  Also fix broken urls to source control, issue 
tracking and mailing lists to point to current.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Updated] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated

2014-02-05 Thread Steve Viens (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Steve Viens updated JUDDI-837:
--

Summary: Update jUDDI incubation site to better reflect that it has 
graduated  (was: Update jUDDI incubation site to better reflect that it 
graduated)

 Update jUDDI incubation site to better reflect that it has graduated
 

 Key: JUDDI-837
 URL: https://issues.apache.org/jira/browse/JUDDI-837
 Project: jUDDI
  Issue Type: Task
  Components: website
Affects Versions: 3.2
 Environment: Apache Incubator
Reporter: Alex O'Ree
Assignee: Steve Viens
Priority: Minor
   Original Estimate: 2h
  Remaining Estimate: 2h

 Source of this work is in the following thread: 
 http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser
 Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI 
 graduated in March 2014.  Also fix broken urls to source control, issue 
 tracking and mailing lists to point to current.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Work started] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated

2014-02-05 Thread Steve Viens (JIRA) 

 [ 
https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Work on JUDDI-837 started by Steve Viens.

 Update jUDDI incubation site to better reflect that it has graduated
 

 Key: JUDDI-837
 URL: https://issues.apache.org/jira/browse/JUDDI-837
 Project: jUDDI
  Issue Type: Task
  Components: website
Affects Versions: 3.2
 Environment: Apache Incubator
Reporter: Alex O'Ree
Assignee: Steve Viens
Priority: Minor
   Original Estimate: 2h
  Remaining Estimate: 2h

 Source of this work is in the following thread: 
 http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser
 Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI 
 graduated in March 2014.  Also fix broken urls to source control, issue 
 tracking and mailing lists to point to current.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated

2014-02-05 Thread Steve Viens (JIRA) 

[ 
https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892428#comment-13892428
 ] 

Steve Viens commented on JUDDI-837:
---

jUDDI's incubation page has been modified to clearly indicating graduation from 
the Incubator in March 2004.  Outdated or broken links to jUDDI's  web site, 
mailing lists, source code and issue tracking to current locations. Assume 
updates to the site happen on relatively frequent schedule (daily?).

 Update jUDDI incubation site to better reflect that it has graduated
 

 Key: JUDDI-837
 URL: https://issues.apache.org/jira/browse/JUDDI-837
 Project: jUDDI
  Issue Type: Task
  Components: website
Affects Versions: 3.2
 Environment: Apache Incubator
Reporter: Alex O'Ree
Assignee: Steve Viens
Priority: Minor
   Original Estimate: 2h
  Remaining Estimate: 2h

 Source of this work is in the following thread: 
 http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser
 Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI 
 graduated in March 2014.  Also fix broken urls to source control, issue 
 tracking and mailing lists to point to current.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

[jira] [Commented] (JUDDI-837) Update jUDDI incubation site to better reflect that it has graduated

2014-02-05 Thread Steve Viens (JIRA) 

[ 
https://issues.apache.org/jira/browse/JUDDI-837?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=13892430#comment-13892430
 ] 

Steve Viens commented on JUDDI-837:
---

jUDDI's Incubation page: http://incubator.apache.org/projects/juddi.html

 Update jUDDI incubation site to better reflect that it has graduated
 

 Key: JUDDI-837
 URL: https://issues.apache.org/jira/browse/JUDDI-837
 Project: jUDDI
  Issue Type: Task
  Components: website
Affects Versions: 3.2
 Environment: Apache Incubator
Reporter: Alex O'Ree
Assignee: Steve Viens
Priority: Minor
   Original Estimate: 2h
  Remaining Estimate: 2h

 Source of this work is in the following thread: 
 http://mail-archives.apache.org/mod_mbox/juddi-dev/201312.mbox/browser
 Will update the jUDDI page on the Apache Incubator site to reflect that jUDDI 
 graduated in March 2014.  Also fix broken urls to source control, issue 
 tracking and mailing lists to point to current.



--
This message was sent by Atlassian JIRA
(v6.1.5#6160)

Re: [VOTE] Release jUDDI-3.2.0

2014-02-04 Thread Steve Viens 
+1 Really well done. Incredible  amount of work.

Sent from my iPhone

 On Feb 4, 2014, at 9:03 AM, Kurt T Stam kurt.s...@gmail.com wrote:
 
 Dear jUDDI enthusiasts,
 
 The new release is here! Long, long overdue and hopefully we won't go this 
 long between releases again. The amount of work that when in is pretty 
 incredible ( 206 jiras), the brunt of it all done by Alex. Just check out the 
 release notes below!
 
 Here’s are some highlights for this version 3.2
 A new end user interface based on Twitter’s Bootstrap
 
 
 A new administrative user interface based on Twitter’s 
 Bootstrap with in browser monitoring
 
 
 A client side subscription callback API
 
 
 Client distribution package
 
 
 Many more examples
 
 
 WADL to UDDI mappings
 
 
 All credentials are now encryptable with command line tools
 
 
 Removal of the porlet services
 
 
 Deployment templates for Jboss EAP 6+
 
 
 Client side digital signature support
 
 
 REST style interface for Inquiry API
 
 
 Added many more tModels to the base install
 
 
 More documentation
 
 With this release have have two distros, a juddi and a uddi-client. The 
 juddi-distro has the server, client and gui, the uddi-client-distro has the 
 client, the gui and our TCK. Both distros are staged here:
 
 http://people.apache.org/~kstam/releases/juddi-3.2.0/
 
 The release artifacts are staged in nexus:
 
 https://repository.apache.org/content/repositories/orgapachejuddi-1001/
 
 and we have a tag at
 
 http://svn.apache.org/repos/asf/juddi/tags/juddi-3.2.0/
 
 and finally our new website is staged at:
 
 http://juddi.staging.apache.org/
 
 Please give it a spin and cast your vote. This vote will be open for the next 
 72 hours.
 
 My vote a huge +1 :)
 
 Cheers,
 
 --Kurt
 
 Sub-task
 
 [JUDDI-782] - Add v2 API
 Bug
 
 [JUDDI-405] - Improve LDAP integration
 [JUDDI-581] - Client side digital signature
 [JUDDI-590] - getAssertionStatusReport does not return incomplete assertions
 [JUDDI-593] - Upgrade to the latest CXF version
 [JUDDI-595] - Subscription API NPE, Validation required
 [JUDDI-596] - Subscription callback without a transport type is not delivered
 [JUDDI-597] - Binding template access point value is converted toLowerCase()
 [JUDDI-603] - Subscription email notifier shouldn't require mailto: prefix
 [JUDDI-606] - Subscription API does not validate on saveSubscription
 [JUDDI-610] - add canned query support in the console
 [JUDDI-615] - NPE when trying to sign an artifact
 [JUDDI-616] - Build fails on during JAR signing of DigSig Applet
 [JUDDI-619] - jUDDI API wsdl is not synchronized to the code base
 [JUDDI-620] - uddi-tck-test.jar is missing from the bundle
 [JUDDI-622] - no stack traces should be thrown in the console during test
 [JUDDI-623] - WSDL files are not syncronized with JUDDI API ws
 [JUDDI-626] - Create verbiage for WSDL/WADL import with for Juddi-gui
 [JUDDI-630] - Implement Inquiry tmodel uddi:uddi.org:findqualifier:orallkeys
 [JUDDI-631] - Add JAVA_OPTs memory settings for Windows catalina.bat
 [JUDDI-632] - New juddi user console does not display correctly in IE8
 [JUDDI-634] - juddi client's xsd is invalid
 [JUDDI-637] - Add source code documentation to UDDIClerk, UDDIClient, 
 UDDIService and more
 [JUDDI-643] - Documentation pom fails
 [JUDDI-645] - NodeId config setting is not honored
 [JUDDI-646] - Configuring the node id causes the splash page to fail to render
 [JUDDI-649] - Error importing WSDL from juddi-gui
 [JUDDI-653] - Build fails on Ubuntu using OpenJDK
 [JUDDI-654] - Max Tries delivery count for subscription notification is not 
 honored
 [JUDDI-655] - Maximum subscription results count is not honored for asynch 
 notifications
 [JUDDI-662] - Name length of j3_signature_transform_data_value too long
 [JUDDI-663] - juddi-gui-disg jar signer is signing the wrong jar file
 [JUDDI-664] - Remove dependency on sun/oracle jdk
 [JUDDI-666] - revise documentation for ddl generation
 [JUDDI-667] - jUDDI should be able to run on a server not connected to the www
 [JUDDI-669] - Fix juddi-gui settings page
 [JUDDI-671] - Convert the uddi-samples projects maven
 [JUDDI-675] - exception throw when UDDIClient.stop is called more than once
 [JUDDI-676] - juddi-gui business editor page may not render
 [JUDDI-677] - save business does not validate business key for UDDI key rules
 [JUDDI-678] - juddi-gui does not trap expired auth tokens correctly
 [JUDDI-679] - juddi-gui NPE performing find service by id
 [JUDDI-681] - When saving a new business, the business key is not casted 
 correctly
 [JUDDI-682] - fix uddi root business entity install file, invalid discovery 
 url and type
 [JUDDI-685] - Asciidoc generation fails
 [JUDDI-690] - juddi-client java wsdl2uddi may not include 
 uddi-org:protocol:http for all bindings/ports using soap 1.2
 [JUDDI-691] - NPE querying for Publisher Assertions
 [JUDDI-696] - juddi-gui may not generate aes keys using oracle jre without jce
 [JUDDI-698] - juddi-gui edit subscription

Re: older wiki sites

2013-12-31 Thread Steve Viens 
Think those are from my era.  I'll take a look this week.  For the
incubator site what do you think about a bit of content about exiting the
incubator on {date} with a link to http://juddi.apache.org ?

Also, is the SVN mailing list still in operation:
http://juddi.apache.org/mail-lists.html ?

Steve Viens
svi...@gmail.com
603-828-2397


On Sun, Dec 29, 2013 at 7:44 PM, Alex O'Ree spyhunte...@gmail.com wrote:

 Does anyone have write access to the following urls?

 http://incubator.apache.org/projects/juddi

 http://wiki.apache.org/general/jUDDI

 We should probably update them to point to the top level site

Re: [VOTE] Release jUDDI-3.1.5

2013-05-16 Thread Steve Viens 
Impressive amount of features and fixes.

+1 (non-binding)

Steve Viens
svi...@gmail.com
603-828-2397


On Wed, May 15, 2013 at 10:44 PM, Kurt T Stam kurt.s...@gmail.com wrote:

  Hi guys,

 The biggest new feature is validation, some long overdue performance
 fixes, WSDL2UDDI support, a shiny distro with examples, docs and javadoc
 and the ability to create wars for a few different platforms and
 configurations (OpenJPA vs Hibernate and CXF vs JBossWS). That, and lots
 and lots of bugfixes (see the release notes below).

 We have a tag at:

 http://svn.apache.org/repos/asf/juddi/tags/juddi-3.1.5/

 the maven release artifacts are staged at:

 https://repository.apache.org/content/repositories/orgapachejuddi-004/

 and the distribution is staged at:

 http://people.apache.org/~kstam/releases/juddi-3.1.5/

 Please give it a spin and cast your vote in the next 72 hours!

 My vote: +1

 Cheers,

 --Kurt


 Full Release Notes:

 Bug

- [JUDDI-363 https://issues.apache.org/jira/browse/JUDDI-363] - Move
hibernate and openjpa persistence files out of resources
- [JUDDI-409 https://issues.apache.org/jira/browse/JUDDI-409] -
problems in digital signature on entity
- [JUDDI-496 https://issues.apache.org/jira/browse/JUDDI-496] - The
tModel is not loaded in the SubscriptionNotifier
- [JUDDI-545 https://issues.apache.org/jira/browse/JUDDI-545] -
combineCategoryBags findQualifier not performing correctly when used in
find_business call
- [JUDDI-548 https://issues.apache.org/jira/browse/JUDDI-548] -
java7 compatibility
- [JUDDI-553 https://issues.apache.org/jira/browse/JUDDI-553] -
TModelDetail not deleted when TModel is deleted
- [JUDDI-557 https://issues.apache.org/jira/browse/JUDDI-557] -
Update all POMs on example
- [JUDDI-560 https://issues.apache.org/jira/browse/JUDDI-560] -
Issues from findbugs
- [JUDDI-561 https://issues.apache.org/jira/browse/JUDDI-561] -
Transaction rollback when PersonName Lang is greater than 5 characters
- [JUDDI-562 https://issues.apache.org/jira/browse/JUDDI-562] - CI
build integration failures
- [JUDDI-565 https://issues.apache.org/jira/browse/JUDDI-565] -
Binding template validation rules are incorrect
- [JUDDI-566 https://issues.apache.org/jira/browse/JUDDI-566] -
Using service/binding/hostingDirector causes a NPE
- [JUDDI-568 https://issues.apache.org/jira/browse/JUDDI-568] - If
publication of the root publisher fails, juddi goes into an infinite loop
- [JUDDI-569 https://issues.apache.org/jira/browse/JUDDI-569] -
Performance Issue fetching service list
- [JUDDI-571 https://issues.apache.org/jira/browse/JUDDI-571] -
find_services lang issue
- [JUDDI-572 https://issues.apache.org/jira/browse/JUDDI-572] -
Sending a business key for getServiceDetail causing a class cast exception
- [JUDDI-573 https://issues.apache.org/jira/browse/JUDDI-573] -
Performance Issue fetching business
- [JUDDI-574 https://issues.apache.org/jira/browse/JUDDI-574] -
findTmodel search results does not return the Lang element
- [JUDDI-576 https://issues.apache.org/jira/browse/JUDDI-576] - Fix
broken links and old wiki site
- [JUDDI-582 https://issues.apache.org/jira/browse/JUDDI-582] -
KeyedReferenceGroup/tModelKey is either not saved or not retrieved
- [JUDDI-589 https://issues.apache.org/jira/browse/JUDDI-589] - find
qualifier signaturePresent doesn't appear to follow the spec
- [JUDDI-591 https://issues.apache.org/jira/browse/JUDDI-591] - Add
support for email alerts for Subscription API
- [JUDDI-592 https://issues.apache.org/jira/browse/JUDDI-592] -
failing unit test on latest trunk
- [JUDDI-612 https://issues.apache.org/jira/browse/JUDDI-612] -
Build 'clean' target does not remove the content in
juddi-core-openjpa\src\main

 Improvement

- [JUDDI-89 https://issues.apache.org/jira/browse/JUDDI-89] - JDBC
Datastore performance improvements
- [JUDDI-554 https://issues.apache.org/jira/browse/JUDDI-554] - Link
to wiki from participation page goes to a different url
- [JUDDI-555 https://issues.apache.org/jira/browse/JUDDI-555] - Add
additional examples for working with UDDI
- [JUDDI-559 https://issues.apache.org/jira/browse/JUDDI-559] -
Authentication Tokens do not expire
- [JUDDI-575 https://issues.apache.org/jira/browse/JUDDI-575] -
Referential Integrity Check
- [JUDDI-588 https://issues.apache.org/jira/browse/JUDDI-588] -
Default Juddi business has services with endpoints starting with
${juddi.server.baseurl}/juddiv3
- [JUDDI-601 https://issues.apache.org/jira/browse/JUDDI-601] - Add
more constant fields and documentation to juddi-client
- [JUDDI-611 https://issues.apache.org/jira/browse/JUDDI-611] -
UDDIClerkManager renamed to UDDIClient

 New Feature

- [JUDDI-563 https://issues.apache.org/jira/browse/JUDDI-563] -
Package a Jboss 5/6

Re: [VOTE] commit rights for Alex O'Ree

2013-03-05 Thread Steve Viens 
Like the console.

+1

- Steve

On Mon, Mar 4, 2013 at 9:45 PM, Kurt T Stam kurt.s...@gmail.com wrote:

 Hi guys,

 Alex O'Ree has been submitting some great patches, for example:

 https://issues.apache.org/**jira/browse/JUDDI-559https://issues.apache.org/jira/browse/JUDDI-559
 https://issues.apache.org/**jira/browse/JUDDI-560https://issues.apache.org/jira/browse/JUDDI-560
 https://issues.apache.org/**jira/browse/JUDDI-557https://issues.apache.org/jira/browse/JUDDI-557
 https://issues.apache.org/**jira/browse/JUDDI-555https://issues.apache.org/jira/browse/JUDDI-555

 Currently he is working on a proper console for jUDDI. For a quick demo on
 what he has right now see: http://apachejuddi.blogspot.**
 com/2013/03/new-juddi-console-**is-under-construction.htmlhttp://apachejuddi.blogspot.com/2013/03/new-juddi-console-is-under-construction.html

 Alex has UDDI domain knowledge as well, since he did his masters on UDDI.
 See the dev mailing list:
 http://mail-archives.apache.**org/mod_mbox/juddi-dev/201302.**mbox/%**
 3CCALLT8ki058NzJV33KL2qJCidd0e**1ZhX6xoUpbqTOZyhfNDPfUA%**
 40mail.gmail.com%3Ehttp://mail-archives.apache.org/mod_mbox/juddi-dev/201302.mbox/%3CCALLT8ki058NzJV33KL2qJCidd0e1ZhX6xoUpbqTOZyhfNDPfUA%40mail.gmail.com%3E

 I'd be great to have him as a committer on the project.

 This vote will be open for the next 72 hours.

 My vote +1.

 Cheers,

 --Kurt





-- 
Steve Viens
svi...@gmail.com
603-828-2397

Re: [VOTE] Release jUDDI-3.0.4

2010-11-04 Thread Steve Viens 
+1

On 11/4/10, Thomas Cunningham tcunn...@redhat.com wrote:

 +1


 On 11/03/2010 08:27 AM, Kurt T Stam wrote:
 Hi guys,

 I'd like to put out a 3.0.4 release, followed quickly by 3.0.5 release
 to fix additional jiras.

 I have tagged the codebase for the 3.0.4 release:

 http://svn.apache.org/repos/asf/juddi/tags/juddi-3.0.4/

 and the release artifacts are staged on nexus at:

 https://repository.apache.org/content/repositories/orgapachews-016/

 and for the bundles:

 http://people.apache.org/~kstam/releases/juddi-3.0.4/mirror/

 Please give it a spin and cast your vote in the next 72 hours!

 My vote: +1

 Cheers,

 --Kurt

 --

 Release notes:

 https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10401styleName=Htmlversion=12315365




 Release Notes - jUDDI - Version 3.0.4

 ** Sub-task
 * [JUDDI-417] - move ws/juddi website content to juddi website
 * [JUDDI-418] - update website

 ** Bug
 * [JUDDI-412] - OverviewDoc.overviewUrl should be nullable
 * [JUDDI-420] - NPE in the console if the business does not have
 any services.

 ** Improvement
 * [JUDDI-410] - Move the application context value to the
 baseurl parameter
 * [JUDDI-419] - Add functionality to the juddi-client to remove a
 bindingtemplate from a server

 ** New Feature
 * [JUDDI-424] - Add support for Sybase SQL

 ** Task
 * [JUDDI-411] - Change Derby to run in memory.
 * [JUDDI-416] - promote jUDDI and Scout to TLP project







-- 
Sent from my mobile device