continuum-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vishnu Raj (JIRA)" <>
Subject [jira] (CONTINUUM-2712) Release issue :: Unable to release components
Date Thu, 10 Oct 2013 07:59:52 GMT


Vishnu Raj commented on CONTINUUM-2712:

Hi Brent,

Thanks a lot for your support. The issue is resolved. Solution was that, the jetty-util jar
version, as you assisted was changed to a 7.x version from 8.x version in both Continuum Webapp
and Build Agent.

Another issue that I face currently is with the Notifier (E-Mail). Here are the details. Please
look if you can provide me some hint on this:

- When I add one notifier to a Project Group, the first E-Mail address (defined in the reciepient
area of Notifier) is taken as the 'From' address and it will try to send the E-Mail to the
same address. Just wanted to know how to configure the 'From' address for Notifier in Continuum.
- Even then, the E-Mail is not sent, but throwing 'Relaying denied' exception. I understand
the same is because of trying to send an E-Mail to another domain. But, just wanted to know
how to let it send to the domain that we specify.

Thanks in advance.
> Release issue :: Unable to release components
> ---------------------------------------------
>                 Key: CONTINUUM-2712
>                 URL:
>             Project: Continuum
>          Issue Type: Bug
>          Components: Release
>    Affects Versions: 1.4.1
>         Environment: OS: Linux
> Server: Tomcat 6.0.35
> Apache Maven 2.2.1
> JDK 1.5
>            Reporter: Vishnu Raj
>         Attachments: Continuum-Release Issue.txt
> While performing release, exception is being thrown by the Continuum build agent saying
"java.lang.UnsupportedClassVersionError: Bad version number in .class file (unable to load
> I am new to Contiuum and setting it up for the first time. Any help in this would be
greatly appreciated. Thanks in advance.
> Attached the log file. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:

View raw message