buildbot success in on juddi-trunk-hibernate
The Buildbot has detected a restored build on builder juddi-trunk-hibernate while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-hibernate/builds/54 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] 2a8bed4efd34bccb11e0f97192a3e273355ad5fa Blamelist: Alex O'Ree Build succeeded! Sincerely, -The Buildbot
buildbot failure in on juddi-trunk-openjpa
The Buildbot has detected a new failure on builder juddi-trunk-openjpa while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-openjpa/builds/55 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] 2a8bed4efd34bccb11e0f97192a3e273355ad5fa Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
buildbot failure in on juddi-trunk-hibernate
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/53 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] e2521334f05b05551da024054d9b09d732a18786 Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-982) Removing the juddi-client-plugins module
[ https://issues.apache.org/jira/browse/JUDDI-982?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197880#comment-16197880 ] ASF subversion and git services commented on JUDDI-982: --- Commit 2a8bed4efd34bccb11e0f97192a3e273355ad5fa in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=2a8bed4 ] JUDDI-982 deleting the client plugin module. JUDDI-977 more findbugs fixes > Removing the juddi-client-plugins module > > > Key: JUDDI-982 > URL: https://issues.apache.org/jira/browse/JUDDI-982 > Project: jUDDI > Issue Type: Task > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > in module was added a while ago and was just stubbed out as an example. It > didn't actually have an implementation though so kind of pointless -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Resolved] (JUDDI-982) Removing the juddi-client-plugins module
[ https://issues.apache.org/jira/browse/JUDDI-982?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-982. -- Resolution: Fixed > Removing the juddi-client-plugins module > > > Key: JUDDI-982 > URL: https://issues.apache.org/jira/browse/JUDDI-982 > Project: jUDDI > Issue Type: Task > Components: build >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > in module was added a while ago and was just stubbed out as an example. It > didn't actually have an implementation though so kind of pointless -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-977) reduce findbugs warnings
[ https://issues.apache.org/jira/browse/JUDDI-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197881#comment-16197881 ] ASF subversion and git services commented on JUDDI-977: --- Commit 2a8bed4efd34bccb11e0f97192a3e273355ad5fa in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=2a8bed4 ] JUDDI-982 deleting the client plugin module. JUDDI-977 more findbugs fixes > reduce findbugs warnings > > > Key: JUDDI-977 > URL: https://issues.apache.org/jira/browse/JUDDI-977 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (JUDDI-982) Removing the juddi-client-plugins module
Alex O'Ree created JUDDI-982: Summary: Removing the juddi-client-plugins module Key: JUDDI-982 URL: https://issues.apache.org/jira/browse/JUDDI-982 Project: jUDDI Issue Type: Task Components: build Reporter: Alex O'Ree Assignee: Alex O'Ree Fix For: 3.3.5 in module was added a while ago and was just stubbed out as an example. It didn't actually have an implementation though so kind of pointless -- This message was sent by Atlassian JIRA (v6.4.14#64029)
buildbot failure in on juddi-trunk-win7-openjpa
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/58 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] e2521334f05b05551da024054d9b09d732a18786 Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
buildbot success in on juddi-trunk-openjpa
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/54 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] d147fa7496319382fd19c5ebe70fc31855f795a8 Blamelist: Alex O'Ree Build succeeded! Sincerely, -The Buildbot
buildbot success in on juddi-trunk-hibernate
The Buildbot has detected a restored build on builder juddi-trunk-hibernate while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-hibernate/builds/52 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] d147fa7496319382fd19c5ebe70fc31855f795a8 Blamelist: Alex O'Ree Build succeeded! Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197766#comment-16197766 ] ASF subversion and git services commented on JUDDI-981: --- Commit e2521334f05b05551da024054d9b09d732a18786 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=e252133 ] JUDDI-981 attempting to fix build issues on bb > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-981) Force all tests to run in a random order
[ https://issues.apache.org/jira/browse/JUDDI-981?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197613#comment-16197613 ] ASF subversion and git services commented on JUDDI-981: --- Commit d147fa7496319382fd19c5ebe70fc31855f795a8 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=d147fa7 ] JUDDI-981 enabled > Force all tests to run in a random order > > > Key: JUDDI-981 > URL: https://issues.apache.org/jira/browse/JUDDI-981 > Project: jUDDI > Issue Type: Improvement > Components: build, uddi-tck >Reporter: Alex O'Ree >Assignee: Alex O'Ree > > The seemingly random test failures in certain environment can probably be > caught earlier if we enable randomization of the test build order. There's > most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
buildbot success in on juddi-trunk-win7-openjpa
The Buildbot has detected a restored build on builder juddi-trunk-win7-openjpa while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-win7-openjpa/builds/55 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] 9c77acdf9f3d47accec70a6e91cabf6ad304a00c Blamelist: Alex O'Ree Build succeeded! Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-977) reduce findbugs warnings
[ https://issues.apache.org/jira/browse/JUDDI-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197354#comment-16197354 ] ASF subversion and git services commented on JUDDI-977: --- Commit 9c77acdf9f3d47accec70a6e91cabf6ad304a00c in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=9c77acd ] JUDDI-977 findbugs > reduce findbugs warnings > > > Key: JUDDI-977 > URL: https://issues.apache.org/jira/browse/JUDDI-977 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (JUDDI-943) WebHelper class: Client name not set in servletContext after getUDDIClient is called
[
https://issues.apache.org/jira/browse/JUDDI-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree updated JUDDI-943:
-
Fix Version/s: 3.3.5
> WebHelper class: Client name not set in servletContext after getUDDIClient is
> called
>
>
> Key: JUDDI-943
> URL: https://issues.apache.org/jira/browse/JUDDI-943
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
> Fix For: 3.3.5
>
>
> The client name is not set after the method:
> WebHelper.getUDDIClient(servletContext) is called and it seems it should be.
> Because the client name is not set a new UDDI client is returned each time
> the method is called despite the same servletContext is passed.
> The problem is here (from WebHelper class):
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " +
> client.getName() + "...");
> } else {
> throw new ConfigurationException("A client name
> needs to be specified in the client config file.");
> }
> {code}
> it should be according to me:
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " + client.getName() + "...");
> clientName = client.getName();
> } else {
> throw new ConfigurationException("A client name needs to be specified in
> the client config file.");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Resolved] (JUDDI-943) WebHelper class: Client name not set in servletContext after getUDDIClient is called
[
https://issues.apache.org/jira/browse/JUDDI-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree resolved JUDDI-943.
--
Resolution: Fixed
> WebHelper class: Client name not set in servletContext after getUDDIClient is
> called
>
>
> Key: JUDDI-943
> URL: https://issues.apache.org/jira/browse/JUDDI-943
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
> Fix For: 3.3.5
>
>
> The client name is not set after the method:
> WebHelper.getUDDIClient(servletContext) is called and it seems it should be.
> Because the client name is not set a new UDDI client is returned each time
> the method is called despite the same servletContext is passed.
> The problem is here (from WebHelper class):
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " +
> client.getName() + "...");
> } else {
> throw new ConfigurationException("A client name
> needs to be specified in the client config file.");
> }
> {code}
> it should be according to me:
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " + client.getName() + "...");
> clientName = client.getName();
> } else {
> throw new ConfigurationException("A client name needs to be specified in
> the client config file.");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (JUDDI-943) WebHelper class: Client name not set in servletContext after getUDDIClient is called
[
https://issues.apache.org/jira/browse/JUDDI-943?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197220#comment-16197220
]
ASF subversion and git services commented on JUDDI-943:
---
Commit 6ea7ff2503c0a536c6f35d6806b114688d7d4063 in juddi's branch
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=6ea7ff2 ]
JUDDI-943 fixed
> WebHelper class: Client name not set in servletContext after getUDDIClient is
> called
>
>
> Key: JUDDI-943
> URL: https://issues.apache.org/jira/browse/JUDDI-943
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>
> The client name is not set after the method:
> WebHelper.getUDDIClient(servletContext) is called and it seems it should be.
> Because the client name is not set a new UDDI client is returned each time
> the method is called despite the same servletContext is passed.
> The problem is here (from WebHelper class):
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " +
> client.getName() + "...");
> } else {
> throw new ConfigurationException("A client name
> needs to be specified in the client config file.");
> }
> {code}
> it should be according to me:
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " + client.getName() + "...");
> clientName = client.getName();
> } else {
> throw new ConfigurationException("A client name needs to be specified in
> the client config file.");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Assigned] (JUDDI-943) WebHelper class: Client name not set in servletContext after getUDDIClient is called
[
https://issues.apache.org/jira/browse/JUDDI-943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Alex O'Ree reassigned JUDDI-943:
Assignee: Alex O'Ree
> WebHelper class: Client name not set in servletContext after getUDDIClient is
> called
>
>
> Key: JUDDI-943
> URL: https://issues.apache.org/jira/browse/JUDDI-943
> Project: jUDDI
> Issue Type: Bug
> Components: juddi-client
>Affects Versions: 3.3.1
>Reporter: Matthieu Ghilain
>Assignee: Alex O'Ree
>
> The client name is not set after the method:
> WebHelper.getUDDIClient(servletContext) is called and it seems it should be.
> Because the client name is not set a new UDDI client is returned each time
> the method is called despite the same servletContext is passed.
> The problem is here (from WebHelper class):
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " +
> client.getName() + "...");
> } else {
> throw new ConfigurationException("A client name
> needs to be specified in the client config file.");
> }
> {code}
> it should be according to me:
> {code}
> if (client.getName()!=null) {
> logger.info("Starting Client " + client.getName() + "...");
> clientName = client.getName();
> } else {
> throw new ConfigurationException("A client name needs to be specified in
> the client config file.");
> }
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (JUDDI-961) Add OWASP maven plugin
[ https://issues.apache.org/jira/browse/JUDDI-961?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree closed JUDDI-961. Resolution: Won't Fix > Add OWASP maven plugin > -- > > Key: JUDDI-961 > URL: https://issues.apache.org/jira/browse/JUDDI-961 > Project: jUDDI > Issue Type: New Feature >Reporter: Alex O'Ree > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
buildbot failure in on juddi-trunk-openjpa
The Buildbot has detected a new failure on builder juddi-trunk-openjpa while building juddi. Full details are available at: https://ci.apache.org/builders/juddi-trunk-openjpa/builds/50 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] 193fa4c56e8a44c9672a043d5e9e56c1d6cc99c2 Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-977) reduce findbugs warnings
[ https://issues.apache.org/jira/browse/JUDDI-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197190#comment-16197190 ] ASF subversion and git services commented on JUDDI-977: --- Commit de1de4c4f243f182fe548bae45c8615026ae7e76 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=de1de4c ] JUDDI-973 more code clean up JUDDI-977 find bugs > reduce findbugs warnings > > > Key: JUDDI-977 > URL: https://issues.apache.org/jira/browse/JUDDI-977 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-973) Code clean up juddi-client-cli
[ https://issues.apache.org/jira/browse/JUDDI-973?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197189#comment-16197189 ] ASF subversion and git services commented on JUDDI-973: --- Commit de1de4c4f243f182fe548bae45c8615026ae7e76 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=de1de4c ] JUDDI-973 more code clean up JUDDI-977 find bugs > Code clean up juddi-client-cli > -- > > Key: JUDDI-973 > URL: https://issues.apache.org/jira/browse/JUDDI-973 > Project: jUDDI > Issue Type: Task > Components: juddi-client >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > > There's a bunch of dead stores, unused imports etc. I'm totally to blame too. > Clean up in progress -- This message was sent by Atlassian JIRA (v6.4.14#64029)
buildbot failure in on juddi-trunk-win7-openjpa
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/53 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] 193fa4c56e8a44c9672a043d5e9e56c1d6cc99c2 Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
buildbot failure in on juddi-trunk-hibernate
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/48 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] 193fa4c56e8a44c9672a043d5e9e56c1d6cc99c2 Blamelist: Alex O'Ree BUILD FAILED: failed compile_1 Sincerely, -The Buildbot
[jira] [Commented] (JUDDI-960) TCK tests not passing (windows 7, java 1.8)
[ https://issues.apache.org/jira/browse/JUDDI-960?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197088#comment-16197088 ] ASF subversion and git services commented on JUDDI-960: --- Commit 193fa4c56e8a44c9672a043d5e9e56c1d6cc99c2 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=193fa4c ] JUDDI-977 more findbugs fixes JUDDI-960 test cleanup > TCK tests not passing (windows 7, java 1.8) > --- > > Key: JUDDI-960 > URL: https://issues.apache.org/jira/browse/JUDDI-960 > Project: jUDDI > Issue Type: Bug > Components: juddi-tomcat >Reporter: Matthieu Ghilain >Assignee: Alex O'Ree > Fix For: 3.3.5 > > Attachments: org.apache.juddi.v3.bpel.BPEL_020_IntegrationTest.txt, > org.apache.juddi.v3.tck.JUDDI_300_MultiNodeIntegrationTest.txt > > > Two tests are not passing on my side. > Running mvn clean install -P dist on *windows 7 java 1.8* > I have uploaded the logs of the tests which are not passing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (JUDDI-977) reduce findbugs warnings
[ https://issues.apache.org/jira/browse/JUDDI-977?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16197087#comment-16197087 ] ASF subversion and git services commented on JUDDI-977: --- Commit 193fa4c56e8a44c9672a043d5e9e56c1d6cc99c2 in juddi's branch refs/heads/master from [~spyhunter99] [ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=193fa4c ] JUDDI-977 more findbugs fixes JUDDI-960 test cleanup > reduce findbugs warnings > > > Key: JUDDI-977 > URL: https://issues.apache.org/jira/browse/JUDDI-977 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3.5 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Reopened] (JUDDI-960) TCK tests not passing (windows 7, java 1.8)
[ https://issues.apache.org/jira/browse/JUDDI-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree reopened JUDDI-960: -- > TCK tests not passing (windows 7, java 1.8) > --- > > Key: JUDDI-960 > URL: https://issues.apache.org/jira/browse/JUDDI-960 > Project: jUDDI > Issue Type: Bug > Components: juddi-tomcat >Reporter: Matthieu Ghilain >Assignee: Alex O'Ree > Fix For: 3.3.5 > > Attachments: org.apache.juddi.v3.bpel.BPEL_020_IntegrationTest.txt, > org.apache.juddi.v3.tck.JUDDI_300_MultiNodeIntegrationTest.txt > > > Two tests are not passing on my side. > Running mvn clean install -P dist on *windows 7 java 1.8* > I have uploaded the logs of the tests which are not passing. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (JUDDI-981) Force all tests to run in a random order
Alex O'Ree created JUDDI-981: Summary: Force all tests to run in a random order Key: JUDDI-981 URL: https://issues.apache.org/jira/browse/JUDDI-981 Project: jUDDI Issue Type: Improvement Components: build, uddi-tck Reporter: Alex O'Ree Assignee: Alex O'Ree The seemingly random test failures in certain environment can probably be caught earlier if we enable randomization of the test build order. There's most likely some test that is not cleaning up after itself. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (JUDDI-980) Update juddi's parent pom to the latest apache pom
Alex O'Ree created JUDDI-980: Summary: Update juddi's parent pom to the latest apache pom Key: JUDDI-980 URL: https://issues.apache.org/jira/browse/JUDDI-980 Project: jUDDI Issue Type: Improvement Components: build Reporter: Alex O'Ree Priority: Minor -- This message was sent by Atlassian JIRA (v6.4.14#64029)
