[ 
https://issues.apache.org/jira/browse/EAGLE-517?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15451511#comment-15451511
 ] 

Jayesh commented on EAGLE-517:
------------------------------

here are the solution, i am thinking...

1) add "com.typesafe.akka" dependency to pom of module: eagle-webservice
2) convert from constant to config.getString method to get values.

Now the main issue here is the jenkins build didnt catch this because it always 
build the project at same location
{code}
/home/jenkins/jenkins-slave/workspace/incubator-eagle-develop
{code}
which i believe still has artifacts and classes under target dir.

3) start jenkins job at new location for every new build, for ex; 
{code}
/home/jenkins/jenkins-slave/workspace/incubator-eagle-develop-#{BUILD_NUMBER}
{code}
or just recreate the same directory and clone the develop branch

Please comment.

> develop branch is actually broken with missing dependencies
> -----------------------------------------------------------
>
>                 Key: EAGLE-517
>                 URL: https://issues.apache.org/jira/browse/EAGLE-517
>             Project: Eagle
>          Issue Type: Bug
>    Affects Versions: v0.5.0
>            Reporter: Jayesh
>             Fix For: v0.5.0
>
>
> I see that module: eagle-application-management is removed (dont have more 
> context)  in develop branch (but it is there in master branch).
> so here are some issues it has caused:
> 1) it makes "com.typesafe.akka" dependency for module: eagle-webservice go 
> missing because it is not added to any other or respective pom.
> 2) ApplicationSchedulerListener.java has invalid imports
> {code} 
> import org.apache.eagle.service.application.AppManagerConstants;
> import org.apache.eagle.stream.application.scheduler.ApplicationScheduler;
> {code}
> and it still uses class constant like {code} 
> AppManagerConstants.APP_COMMAND_LOADER_ENABLED {code}
> Also, same with EagleServiceProfileInitializer.java
> {code}
> import org.apache.eagle.stream.application.scheduler.ApplicationScheduler;
> {code}



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

Reply via email to