Re: [VOTE] Release jUDDI-3.3.3

[Matthieu Ghilain]

+1

On Sun, 11 Sep 2016 22:15 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/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
>

[VOTE] Release jUDDI-3.3.3

[Alex O'Ree]

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

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[subes (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482088#comment-15482088
 ] 

subes commented on JUDDI-965:
-

looks good now, thanks a lot :)

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[Alex O'Ree (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482080#comment-15482080
 ] 

Alex O'Ree commented on JUDDI-965:
--

ok thanks for the feedback. the change has been made. I'm way over due for 
cutting a release, so i'll to get it done today.

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482079#comment-15482079
 ] 

ASF subversion and git services commented on JUDDI-965:
---

Commit 83312bd2aa23fbed63312f1ff2cabb0770baf998 in juddi's branch 
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=83312bd ]

JUDDI-965 fixed


> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[subes (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482074#comment-15482074
 ] 

subes commented on JUDDI-965:
-

As long as the TargetException is somehow logged, i am totally fine with it. 
Also note that getCause will normally be *null* on an 
InvocationTargetException, since the constructor puts null into the super 
constructor when fed with a cause and instead stores it as "target" variable.

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[subes (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482063#comment-15482063
 ] 

subes commented on JUDDI-965:
-

I am not using DispositionReportFaultMessage it myself, it is just that the 
UDDIClient let DispositionReportFaultMessage handle an 
InvocationTargetException when I was using a service description with more than 
256 characters.

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[Alex O'Ree (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482064#comment-15482064
 ] 

Alex O'Ree commented on JUDDI-965:
--

how does this sound to you?

else if (e instanceof InvocationTargetException){
  log.error("InvocationTargetException: It's not a known instance of 
DispositionReport. Cause: ",((InvocationTargetException)e).getCause());
  log.error("InvocationTargetException: It's not a known instance of 
DispositionReport. Target: 
",((InvocationTargetException)e).getTargetException());
 } else{
log.error("Unsupported Exception: It's not a known instance of 
DispositionReport. ",e);
  
}



> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[Alex O'Ree (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482057#comment-15482057
 ] 

Alex O'Ree commented on JUDDI-965:
--

under what what circumstances are you using an InvocationTargetException?

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[Alex O'Ree (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482055#comment-15482055
 ] 

Alex O'Ree commented on JUDDI-965:
--

are you referring to DispositionReportFaultMessage.java?


> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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/22

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] 4f63c9cb7a749ed1eefaecb4673786aa1595a4a1
Blamelist: Alex 

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot

[jira] [Updated] (JUDDI-960) TCK tests not passing (windows 7, java 1.8)

[Alex O'Ree (JIRA)]

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

Alex O'Ree updated JUDDI-960:
-
Fix Version/s: (was: 3.3.3)
   3.3.4

> 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
> Fix For: 3.3.4
>
> 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.3.4#6332)

buildbot failure in on juddi-trunk-openjpa

[buildbot]

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/25

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] 4f63c9cb7a749ed1eefaecb4673786aa1595a4a1
Blamelist: Alex 

BUILD FAILED: failed compile_1

Sincerely,
 -The Buildbot

[jira] [Reopened] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[subes (JIRA)]

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

subes reopened JUDDI-965:
-

I just reviewed the code. The fix for the stacktrace is fine, but 
InvocationTargetException will still get logged instead of the actual exception 
that is hidden inside invocationTargetException.getTargetException(). Please 
add code that unwraps InvocationTargetException.

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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/23

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

Buildslave for this Build: bb-win7

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

BUILD FAILED: failed compile

Sincerely,
 -The Buildbot

buildbot failure in on juddi-trunk-dotnet

[buildbot]

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

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

Buildslave for this Build: bb-win7

Build Reason: The SingleBranchScheduler scheduler named 
'on-juddi-trunk-dotnet-commit' triggered this build
Build Source Stamp: [branch master] 4f63c9cb7a749ed1eefaecb4673786aa1595a4a1
Blamelist: Alex 

BUILD FAILED: failed compile

Sincerely,
 -The Buildbot

buildbot failure in on juddi-trunk-win7-hibernate

[buildbot]

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

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

Buildslave for this Build: bb-win7

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

BUILD FAILED: failed compile

Sincerely,
 -The Buildbot

[jira] [Resolved] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[Alex O'Ree (JIRA)]

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

Alex O'Ree resolved JUDDI-965.
--
   Resolution: Fixed
Fix Version/s: 3.3.3

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482005#comment-15482005
 ] 

ASF subversion and git services commented on JUDDI-965:
---

Commit 4f63c9cb7a749ed1eefaecb4673786aa1595a4a1 in juddi's branch 
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=4f63c9c ]

JUDDI-966 sources jars are fixed
JUDDI-965 exception is now logged and thrown


> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-966) sources jars are no longer installed while building juddi

[ASF subversion and git services (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15482004#comment-15482004
 ] 

ASF subversion and git services commented on JUDDI-966:
---

Commit 4f63c9cb7a749ed1eefaecb4673786aa1595a4a1 in juddi's branch 
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=4f63c9c ]

JUDDI-966 sources jars are fixed
JUDDI-965 exception is now logged and thrown


> sources jars are no longer installed while building juddi
> -
>
> Key: JUDDI-966
> URL: https://issues.apache.org/jira/browse/JUDDI-966
> Project: jUDDI
>  Issue Type: Bug
>  Components: build
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> not sure what happened, but it looks like
> org.apache.maven.plugins
> maven-source-plugin
> changed behaviors between v2.0 and 2.1 to longer install source jar's by 
> default. currently the pom does not specify the version number. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (JUDDI-966) sources jars are no longer installed while building juddi

[Alex O'Ree (JIRA)]

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

Alex O'Ree resolved JUDDI-966.
--
Resolution: Fixed

> sources jars are no longer installed while building juddi
> -
>
> Key: JUDDI-966
> URL: https://issues.apache.org/jira/browse/JUDDI-966
> Project: jUDDI
>  Issue Type: Bug
>  Components: build
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> not sure what happened, but it looks like
> org.apache.maven.plugins
> maven-source-plugin
> changed behaviors between v2.0 and 2.1 to longer install source jar's by 
> default. currently the pom does not specify the version number. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-966) sources jars are no longer installed while building juddi

[Alex O'Ree (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-966?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481999#comment-15481999
 ] 

Alex O'Ree commented on JUDDI-966:
--

https://issues.apache.org/jira/browse/FELIX-3058

> sources jars are no longer installed while building juddi
> -
>
> Key: JUDDI-966
> URL: https://issues.apache.org/jira/browse/JUDDI-966
> Project: jUDDI
>  Issue Type: Bug
>  Components: build
>Reporter: Alex O'Ree
>Assignee: Alex O'Ree
> Fix For: 3.3.3
>
>
> not sure what happened, but it looks like
> org.apache.maven.plugins
> maven-source-plugin
> changed behaviors between v2.0 and 2.1 to longer install source jar's by 
> default. currently the pom does not specify the version number. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (JUDDI-966) sources jars are no longer installed while building juddi

[Alex O'Ree (JIRA)]

Alex O'Ree created JUDDI-966:


 Summary: sources jars are no longer installed while building juddi
 Key: JUDDI-966
 URL: https://issues.apache.org/jira/browse/JUDDI-966
 Project: jUDDI
  Issue Type: Bug
  Components: build
Reporter: Alex O'Ree
Assignee: Alex O'Ree
 Fix For: 3.3.3


not sure what happened, but it looks like
org.apache.maven.plugins
maven-source-plugin

changed behaviors between v2.0 and 2.1 to longer install source jar's by 
default. currently the pom does not specify the version number. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[Alex O'Ree (JIRA)]

[ 
https://issues.apache.org/jira/browse/JUDDI-965?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15481665#comment-15481665
 ] 

Alex O'Ree commented on JUDDI-965:
--

Ahh i see you want mean. It's swallowing the error message completely. Sorry 
about that.

> DispositionReportFaultMessage is hiding exception messages
> --
>
> Key: JUDDI-965
> URL: https://issues.apache.org/jira/browse/JUDDI-965
> Project: jUDDI
>  Issue Type: Bug
>  Components: juddi-client
>Affects Versions: 3.3.2
>Reporter: subes
>Assignee: Alex O'Ree
>
> I got the following Log message: 
> Unsupported Exception: class java.lang.reflect.InvocationTargetException
> This is caused by line 112 in DispositionReportFaultMessage:
> log.error("Unsupported Exception: " + e.getClass());
> Please change it so it outputs the exception stacktrace and unwrap 
> InvocationTargetException. I had to actually remote debug the application to 
> get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Created] (JUDDI-965) DispositionReportFaultMessage is hiding exception messages

[subes (JIRA)]

subes created JUDDI-965:
---

 Summary: DispositionReportFaultMessage is hiding exception messages
 Key: JUDDI-965
 URL: https://issues.apache.org/jira/browse/JUDDI-965
 Project: jUDDI
  Issue Type: Bug
  Components: juddi-client
Affects Versions: 3.3.2
Reporter: subes


I got the following Log message: 
Unsupported Exception: class java.lang.reflect.InvocationTargetException

This is caused by line 112 in DispositionReportFaultMessage:
log.error("Unsupported Exception: " + e.getClass());

Please change it so it outputs the exception stacktrace and unwrap 
InvocationTargetException. I had to actually remote debug the application to 
get the actual error message...



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)