I am getting the below error when I build on “develop” branch. However, on the
same machine and env, the build on the release bits went through.
Is there any other additional steps to build off “develop” branch?
Thanks
Bosco
$ mvn -DskipTests clean package
[INFO] Scanning for p
Just JDK8 is required in the develop branch.
I built this branch in my local env (OS X), and it went through well.
Regards,
Qingwen Zhao | Apache Eagle
On 7/25/16, 9:35 AM, "Don Bosco Durai" wrote:
>I am getting the below error when I build on ³develop² branch. However,
>on the same machine
Still same issue on my mac and fresh docker image with Sun JDK 1.8
[root@500777b9b778 incubator-eagle]# git branch
* develop
[root@500777b9b778 incubator-eagle]# $JAVA_HOME/bin/java -version
java version "1.8.0_101"
Java(TM) SE Runtime Environment (build 1.8.0_101-b13)
Java HotSpot(TM) 64-Bit Ser
Just to make sure, are you executing from the project root folder? If
you're executing the mvn command from within a sub folder, it may require
that you've installed depended artifacts to your local maven repository in
previous builds.
Michael
On Mon, Jul 25, 2016 at 1:46 PM, Don Bosco Durai wro
Yes, I am running mvn from the root folder of the project.
Bosco
On 7/24/16, 11:29 PM, "Michael Wu" wrote:
Just to make sure, are you executing from the project root folder? If
you're executing the mvn command from within a sub folder, it may require
that you've installed depended
OK.
Seems there are some problems in this new branch, which is in the
development and unstable right now. Sorry about that.
If you are trying Eagle, please use the newly released version branch 0.4.
If you want to contribute new features, develop branch is ok.
For this issue, we are fixing :)
R
This issue has been fixed in develop branch.
Michael
On Mon, Jul 25, 2016 at 3:07 PM, Zhao, Qingwen wrote:
> OK.
>
> Seems there are some problems in this new branch, which is in the
> development and unstable right now. Sorry about that.
>
> If you are trying Eagle, please use the newly releas
Thanks. This worked. Additionally, I had to install node.js. Let me see if I
can make the Dockerfile available in some form for others to use it (if needed).
Bosco
On 7/25/16, 1:28 AM, "Michael Wu" wrote:
This issue has been fixed in develop branch.
Michael
On Mon, Jul 2
Thanks. Are you saying that you will build docker file for community to use?
As far as I know current docker image is not fully tested and sometimes may
not be stable as it contains HBase which is often down unexpectedly.
Thanks
Edward
On Mon, Jul 25, 2016 at 12:21 PM, Don Bosco Durai wrote:
>
I was mostly referring to a Docker container just for building. I know you have
Docker for runtime. I have not tried that yet.
Thanks
Bosco
On 7/25/16, 12:25 PM, "Edward Zhang" wrote:
Thanks. Are you saying that you will build docker file for community to use?
As far as I know curren
10 matches
Mail list logo