Success maybe?

I forgot to tell maven to skip tests , so I threw in that switch to get a 
snapshot.

Probing deeper – it seems this is what I needed -the source matches the 
binaries and now I understand how to build the web console  (? Lets see if I 
get through this without crying for yelp again ??  πŸ˜ƒ  )

Thanks for looking and telepathically sending me in the right direction (hope 
my humor is appreciated).   Still – if you have any guidance on doing the 
snapshot builds – all ears.

Cheers,

SCott

[INFO] Executing tasks

main:
      [zip] Building zip: 
C:\cygwin64\home\scote\ignite\target\bin\apache-ignite-2.8.0-SNAPSHOT-bin.zip
[INFO] Executed tasks
[INFO]
[INFO] --- maven-remote-resources-plugin:1.5:process (default) @ apache-ignite 
---
[INFO]
[INFO] --- flatten-maven-plugin:1.0.1:flatten (flatten) @ apache-ignite ---
[INFO] Generating flattened POM of project 
org.apache.ignite:apache-ignite:pom:2.8.0-SNAPSHOT...
[WARNING] FlattenMode minimum is deprecated!
[WARNING] Ignoring multiple XML header comment!
[INFO]
[INFO] --- maven-dependency-plugin:2.8:copy-dependencies (copy-libs) @ 
apache-ignite ---
[INFO]
[INFO] --- maven-site-plugin:3.4:attach-descriptor (attach-descriptor) @ 
apache-ignite ---
[INFO]
[INFO] --- maven-source-plugin:2.2.1:jar-no-fork (source) @ apache-ignite ---
[INFO]
[INFO] --- maven-javadoc-plugin:2.10.1:jar (module-javadoc) @ apache-ignite ---
[INFO] Not executing Javadoc as the project is not a Java classpath-capable 
package
[INFO] ------------------------------------------------------------------------
[INFO] Reactor Summary for apache-ignite 2.8.0-SNAPSHOT:
[INFO]
[INFO] ignite-apache-license-gen .......................... SUCCESS [  1.467 s]
[INFO] ignite-tools ....................................... SUCCESS [  4.726 s]
[INFO] ignite-core ........................................ SUCCESS [03:08 min]
[INFO] ignite-compress .................................... SUCCESS [  2.163 s]
[INFO] ignite-indexing .................................... SUCCESS [ 21.963 s]
[INFO] ignite-dev-utils ................................... SUCCESS [  5.840 s]
[INFO] ignite-direct-io ................................... SUCCESS [  2.395 s]
[INFO] ignite-log4j ....................................... SUCCESS [  2.527 s]
[INFO] ignite-urideploy ................................... SUCCESS [  4.088 s]
[INFO] ignite-spring ...................................... SUCCESS [  4.534 s]
[INFO] ignite-hadoop ...................................... SUCCESS [ 20.785 s]
[INFO] ignite-extdata-p2p ................................. SUCCESS [  5.059 s]
[INFO] ignite-extdata-uri-dep ............................. SUCCESS [  1.289 s]
[INFO] ignite-extdata-uri ................................. SUCCESS [  7.147 s]
[INFO] ignite-extdata-platform ............................ SUCCESS [  0.393 s]
[INFO] ignite-rest-http ................................... SUCCESS [  2.956 s]
[INFO] ignite-clients ..................................... SUCCESS [  4.582 s]
[INFO] ignite-spring-data ................................. SUCCESS [  3.083 s]
[INFO] ignite-spring-data_2.0 ............................. SUCCESS [  2.902 s]
[INFO] ignite-web ......................................... SUCCESS [  2.269 s]
[INFO] ignite-aop ......................................... SUCCESS [  2.937 s]
[INFO] ignite-ssh ......................................... SUCCESS [  1.659 s]
[INFO] ignite-jta ......................................... SUCCESS [  3.922 s]
[INFO] ignite-aws ......................................... SUCCESS [  4.271 s]
[INFO] ignite-log4j2 ...................................... SUCCESS [  2.574 s]
[INFO] ignite-slf4j ....................................... SUCCESS [  1.987 s]
[INFO] ignite-jcl ......................................... SUCCESS [  2.063 s]
[INFO] ignite-codegen ..................................... SUCCESS [  1.682 s]
[INFO] ignite-gce ......................................... SUCCESS [  2.239 s]
[INFO] ignite-cloud ....................................... SUCCESS [  4.905 s]
[INFO] ignite-mesos ....................................... SUCCESS [  3.837 s]
[INFO] ignite-kafka ....................................... SUCCESS [  4.915 s]
[INFO] ignite-flume ....................................... SUCCESS [  2.703 s]
[INFO] ignite-yarn ........................................ SUCCESS [  6.842 s]
[INFO] ignite-jms11 ....................................... SUCCESS [  2.244 s]
[INFO] ignite-twitter ..................................... SUCCESS [  2.425 s]
[INFO] ignite-mqtt ........................................ SUCCESS [  3.896 s]
[INFO] ignite-zookeeper ................................... SUCCESS [  5.786 s]
[INFO] ignite-hibernate-core .............................. SUCCESS [  2.811 s]
[INFO] ignite-camel ....................................... SUCCESS [  2.742 s]
[INFO] ignite-storm ....................................... SUCCESS [  2.348 s]
[INFO] ignite-osgi-paxlogging ............................. SUCCESS [  0.181 s]
[INFO] ignite-osgi-karaf .................................. SUCCESS [  0.146 s]
[INFO] ignite-osgi ........................................ SUCCESS [  3.435 s]
[INFO] ignite-appserver-test .............................. SUCCESS [  0.238 s]
[INFO] ignite-websphere-test .............................. SUCCESS [  3.407 s]
[INFO] ignite-cassandra ................................... SUCCESS [  0.032 s]
[INFO] ignite-cassandra-store ............................. SUCCESS [ 13.330 s]
[INFO] ignite-cassandra-serializers ....................... SUCCESS [  2.496 s]
[INFO] ignite-flink ....................................... SUCCESS [  3.267 s]
[INFO] ignite-kubernetes .................................. SUCCESS [  1.767 s]
[INFO] ignite-zeromq ...................................... SUCCESS [  1.821 s]
[INFO] ignite-rocketmq .................................... SUCCESS [  2.214 s]
[INFO] ignite-sqlline ..................................... SUCCESS [  0.155 s]
[INFO] ignite-ml .......................................... SUCCESS [ 19.731 s]
[INFO] ignite-ml-xgboost-model-parser ..................... SUCCESS [  3.004 s]
[INFO] ignite-tensorflow .................................. SUCCESS [  4.865 s]
[INFO] ignite-ml-mleap-model-parser ....................... SUCCESS [  3.029 s]
[INFO] ignite-scalar ...................................... SUCCESS [ 18.580 s]
[INFO] ignite-spark ....................................... SUCCESS [  7.264 s]
[INFO] ignite-visor-console ............................... SUCCESS [ 12.424 s]
[INFO] ignite-visor-plugins ............................... SUCCESS [  1.901 s]
[INFO] apache-ignite ...................................... SUCCESS [ 42.934 s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time:  08:25 min
[INFO] Finished at: 2019-01-17T18:05:33-06:00
[INFO] ------------------------------------------------------------------------

scote@lt-scote10 ~/ignite


From: Scott Cote <sc...@etcc.com>
Sent: Thursday, January 17, 2019 5:27 PM
To: user@ignite.apache.org
Subject: RE: building and running from source

Am trying out :
mvn package -P release

this builds a snapshot?

SCott

From: Scott Cote <sc...@etcc.com<mailto:sc...@etcc.com>>
Sent: Thursday, January 17, 2019 4:32 PM
To: user@ignite.apache.org<mailto:user@ignite.apache.org>
Subject: building and running from source

Hello,

I want to build a copy of ignite with the web console.  Cannot – as far as I 
can tell – download a binary for the web console (don’t want to use the 
gridgain cloud version).  The instructions for the web console state that one 
must build it from source.   To that point, the binary distribution of 2.7 does 
NOT have a modules folder.


I have downloaded the source (git clone https://github.com/apache/ignite) so 
that I can build the web console, but the outcome of executing:

Mvn clean package -dskipTests

Does not leave me with a distribution anything like as if I downloaded the 
β€œbin” .   For example, there are modules, but no lib folders.

If I issue the command ignite.bat, I observe errors on my pc such as

c:\cygwin64\home\scote\ignite>bin\ignite.bat
The input line is too long.
"C:\cygwin64\home\scote\ignite\modules\kafka\target\classes" was unexpected at 
this time.

What is the maven command to build a copy of ignite from the command line using 
maven and then be able to run the ignite.sh command  ?


Thanks in advance.

SCott

Reply via email to