Re: [VOTE] SCOUT v1.2.8

[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
> *
>
> 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
> *
>
>
> 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 ] - Bad
>string generation for logs/exceptions
>- [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 ] -
>Scout runs integration tests against a very old version of jUDDI, running
>against the current causes compile errors and unit test failures
>- [SCOUT-135 ] -
>Incorrect mappings for UDDI Address line
>- [SCOUT-136 ] -
>Scout adds sort by name desc to findBinding UDDI requests, which is invalid
>
>

[VOTE] SCOUT v1.2.8

[Alex O'Ree]

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
*

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
*


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 ] - Bad
   string generation for logs/exceptions
   - [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 ] - Scout
   runs integration tests against a very old version of jUDDI, running against
   the current causes compile errors and unit test failures
   - [SCOUT-135 ] -
   Incorrect mappings for UDDI Address line
   - [SCOUT-136 ] - Scout
   adds sort by name desc to findBinding UDDI requests, which is invalid

[ANNOUNCE] jUDDI 3.3.6

[Alex O'Ree]

Dear jUDDI enthusiasts,

Today, we have release jUDDI version 3.3.6. This release is primarily bug
fixes.

You can grab the release at:
http://www.apache.org/dyn/closer.cgi/juddi/juddi/3.3.
6

The website has been updated, artifacts are published and the distribution
should be available globally with a day or so.

buildbot failure in on juddi-trunk-hibernate

[buildbot]

The Buildbot has detected a new failure on builder juddi-trunk-hibernate while 
building juddi. Full details are available at:
https://ci.apache.org/builders/juddi-trunk-hibernate/builds/99

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: The SingleBranchScheduler scheduler named 
'on-juddi-hibernate-commit' triggered this build
Build Source Stamp: [branch master] e1a7476912d8c85e9958e91a14d2e3aa41d33109
Blamelist: Alex O'Ree 

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot

buildbot failure in on juddi-trunk-win7-openjpa

[buildbot]

The Buildbot has detected a new failure on builder juddi-trunk-win7-openjpa 
while building juddi. Full details are available at:
https://ci.apache.org/builders/juddi-trunk-win7-openjpa/builds/99

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: bb-win10

Build Reason: The SingleBranchScheduler scheduler named 
'on-juddi-hibernate-commit' triggered this build
Build Source Stamp: [branch master] e1a7476912d8c85e9958e91a14d2e3aa41d33109
Blamelist: Alex O'Ree 

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot

buildbot success in on juddi-trunk-openjpa

[buildbot]

The Buildbot has detected a restored build on builder juddi-trunk-openjpa while 
building juddi. Full details are available at:
https://ci.apache.org/builders/juddi-trunk-openjpa/builds/99

Buildbot URL: https://ci.apache.org/

Buildslave for this Build: orcus_ubuntu

Build Reason: The SingleBranchScheduler scheduler named 
'on-juddi-hibernate-commit' triggered this build
Build Source Stamp: [branch master] e1a7476912d8c85e9958e91a14d2e3aa41d33109
Blamelist: Alex O'Ree 

Build succeeded!

Sincerely,
 -The Buildbot

[jira] [Closed] (JUDDI-962) Convert juddi.apache.org back to mvn site

[Alex O'Ree (JIRA)]

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

Alex O'Ree closed JUDDI-962.


> Convert juddi.apache.org back to mvn site
> -
>
> Key: JUDDI-962
> URL: https://issues.apache.org/jira/browse/JUDDI-962
> Project: jUDDI
>  Issue Type: Task
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.6
>
>
> For juddi.apache.org, we are currently using the ASF based CMS setup. It 
> works well, but we'd like to convert back to a mvn site based solution



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (JUDDI-994) Bash scripts containing windows CRLF line endings

[Alex O'Ree (JIRA)]

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

Alex O'Ree closed JUDDI-994.


> Bash scripts containing windows CRLF line endings
> -
>
> Key: JUDDI-994
> URL: https://issues.apache.org/jira/browse/JUDDI-994
> Project: jUDDI
>  Issue Type: Bug
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.6
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (JUDDI-988) Update to tomcat 9

[Alex O'Ree (JIRA)]

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

Alex O'Ree closed JUDDI-988.


> Update to tomcat 9
> --
>
> Key: JUDDI-988
> URL: https://issues.apache.org/jira/browse/JUDDI-988
> Project: jUDDI
>  Issue Type: Improvement
>  Components: juddi-tomcat
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.6
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (JUDDI-992) FindBinding API call doesn't exactly match the spec, can't search for just the service key

[Alex O'Ree (JIRA)]

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

Alex O'Ree closed JUDDI-992.


> FindBinding API call doesn't exactly match the spec, can't search for just 
> the service key
> --
>
> Key: JUDDI-992
> URL: https://issues.apache.org/jira/browse/JUDDI-992
> Project: jUDDI
>  Issue Type: Bug
>  Components: core
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
>Priority: Major
> Fix For: 3.3.6
>
>
> this appears to affect most versions starting with 3.1.5 and newer
> The spec isn't exactly clear on what the expected behavior is supposed to be 
> in the case when nothing is specified except for the service key in a 
> findBinding api call. The most logical thing is to return all bindings for 
> that service. The current version of juddi throws an exception stating that 
> it is not a valid request. According to the spec, it looks like it is. The 
> spec actually doesn't really specify what isn't valid except for conflicting 
> find qualifiers
>  
> Example XML request that fits this profile
>  
>  xmlns:ns2="http://www.w3.org/2000/09/xmldsig#; maxRows="10" 
> serviceKey="uddi:juddi.apache.org:4ff68cf9-0463-45c4-bb9e-5a12f321a9c1">sortByNameAscapproximateMatch
>  
> This was discovered in trying to bring Apache Scout up to current jUDDI API 
> levels and debugging unit test failures against 3.3.5.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)