RE : [cas-user] 6.2.x Gradle Compilation

2022-07-01 Thread Déreck
Hi. Thanks for you answer, i’ve success to build the war ; It’s a new deploy. Envoyé à partir de Courrier pour Windows De : Ray BonEnvoyé le :lundi 20 juin 2022 17:00À : cas-user@apereo.orgCc : jerem.pile...@gmail.com; dkopyle...@unicon.netObjet :Re: [cas-user] 6.2.x Gradle Compilation Is this a new deploy?If so, you should use 6.5 (there is no .x for the overlay) Ray  On Sat, 2022-06-18 at 12:42 -0700, Gilles-Dereck GNANCADJA wrote:Notice: This message was sent from outside the University of Victoria email system. Please be cautious with links and sensitive information.  Hello, I'need help please please!I'm working on deployement of CAS and for gradlew step i get this error please help me!!┌──(root💀dgtcp)-[/home/dgtcp/cas-management-overlay]└─# ./gradlew executableStarting a Gradle Daemon (subsequent builds will be faster)FAILURE: Build failed with an exception.* What went wrong:A problem occurred configuring root project 'cas-management'.> Could not resolve all files for configuration ':casBootWarOverlay'.   > Could not find org.apereo.cas:cas-mgmt-webapp-tomcat:6.3.0-SNAPSHOT.     Searched in the following locations:       - file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml       - file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom       - https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml       - https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom       - https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml       - https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom       - https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml       - https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom       - https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml       - https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom     Required by:         project :* Try:Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgDeprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.Use '--warning-mode all' to show the individual deprecation warnings.See https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warningsBUILD FAILED in 2m 24s                       Le dimanche 9 février 2020 à 12:29:13 UTC+1, jerem...@gmail.com a écrit :Hello, Thanks for your response.I come back to (try) to finished my installation... I have succeed in compiling, but I have an error when I try to deploy on tomcat9. First, is that possible to use Tomcat-9.0.16 knowing that in gradle.properties it is written tomcatVersion=9.0.30 (On debian package)? Secondly, this is what I have with  ./gradlew run —info./gradlew run —infoFAILURE: Build failed with an exception.* What went wrong:Task '—info' not found in root project 'cas'.* Try:Run gradlew tasks to get a list of available tasks. Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.* Get more help at https://help.gradle.orgDeprecated Gradle features were used in this build, making it incompatible with Gradle 7.0.Use '--warning-mode all' to show the individual deprecation warnings.See https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warningsBUILD FAILED in 463msMany thanks to you, Jérémie Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :You might want to run it with —info or —debug flag to see what might be failing, like so: ./gradlew run —info or build and run as two separate steps: ./gradlew clean buildjava -jar build/libs/cas.war D.  From: Jérémie Pilette Reply: Jérémie Pilette  Date: January 2, 2020 at 2:47:55 PMTo: CAS Community Cc: dkopy...@unicon.net Subject:  Re: [cas-user] 6.2.x Gradle Compilation  Hi Dmitriy,thank you.Now I have another ailed : > Task :run FAILEDFAILURE: Build failed with an exception.* Where:Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57* What went wrong:Execution failed for task ':run'.> Process 'command '/usr/lib/jvm/j

Re: [cas-user] 6.2.x Gradle Compilation

2022-06-20 Thread Ray Bon
Is this a new deploy?
If so, you should use 6.5 (there is no .x for the overlay)

Ray


On Sat, 2022-06-18 at 12:42 -0700, Gilles-Dereck GNANCADJA wrote:
Notice: This message was sent from outside the University of Victoria email 
system. Please be cautious with links and sensitive information.

Hello, I'need help please please!

I'm working on deployement of CAS and for gradlew step i get this error please 
help me!!


┌──(root💀dgtcp)-[/home/dgtcp/cas-management-overlay]
└─# ./gradlew executable
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'cas-management'.
> Could not resolve all files for configuration ':casBootWarOverlay'.
   > Could not find org.apereo.cas:cas-mgmt-webapp-tomcat:6.3.0-SNAPSHOT.
 Searched in the following locations:
   - 
file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
 Required by:
 project :

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 24s


Le dimanche 9 février 2020 à 12:29:13 UTC+1, jerem@gmail.com a écrit :
Hello,

Thanks for your response.
I come back to (try) to finished my installation...

I have succeed in compiling, but I have an error when I try to deploy on 
tomcat9.

First, is that possible to use Tomcat-9.0.16 knowing that in gradle.properties 
it is written tomcatVersion=9.0.30 (On debian package)?

Secondly, this is what I have with  ./gradlew run —info

./gradlew run —info

FAILURE: Build failed with an exception.

* What went wrong:
Task '—info' not found in root project 'cas'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
option to get the stack trace. Run with --info or --debug option to get more 
log output. Run with --scan to get full insights.


* Get more help at https://help.gradle.org<http://help.gradle.org>

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings<http://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings>

BUILD FAILED in 463ms

Many thanks to you,

Jérémie


Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
You might want to run it with —info or —debug flag to see what might be 
failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.


From: Jérémie Pilette 
Reply: Jérémie Pilette 

Date: January 2, 2020 at 2:47:55 PM
To: CAS Community 
Cc: dkopy...@unicon.net 
Subject:  Re: [cas-user] 6.2.x Gradle Compilation


Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
&

Re: [cas-user] 6.2.x Gradle Compilation

2022-06-19 Thread Gmail

Hi,

did you try to do  :

./gradlew clean build ?

Which version did you download ? 6.3 ? or the last 6.6 ?

Jérémie



Le 18/06/2022 à 21:42, Gilles-Dereck GNANCADJA a écrit :

Hello, I'need help please please!

I'm working on deployement of CAS and for gradlew step i get this 
error please help me!!



┌──(root💀dgtcp)-[/home/dgtcp/cas-management-overlay]
└─# ./gradlew executable
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'cas-management'.
> Could not resolve all files for configuration ':casBootWarOverlay'.
   > Could not find org.apereo.cas:cas-mgmt-webapp-tomcat:6.3.0-SNAPSHOT.
     Searched in the following locations:
       - 
file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
       - 
file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
       - 
https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
       - 
https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
       - 
https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
       - 
https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
       - 
https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
       - 
https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
       - 
https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
       - 
https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom

     Required by:
         project :

* Try:
Run with --stacktrace option to get the stack trace. Run with --info 
or --debug option to get more log output. Run with --scan to get full 
insights.


* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it 
incompatible with Gradle 7.0.

Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings


BUILD FAILED in 2m 24s


Le dimanche 9 février 2020 à 12:29:13 UTC+1, jerem@gmail.com a écrit :

Hello,

Thanks for your response.
I come back to (try) to finished my installation...

I have succeed in compiling, but I have an error when I try to
deploy on tomcat9.

First, is that possible to use *Tomcat-9.0.16* knowing that in
gradle.properties it is written *tomcatVersion=9.0.30* (On debian
package)?

Secondly, this is what I have with *./gradlew run —info*

|
./gradlew run —info

FAILURE:Buildfailed withan exception.

*Whatwent wrong:
Task'—info'notfound inroot project 'cas'.

*Try:
Rungradlew tasks to geta list of available
tasks.Runwith--stacktrace option to getthe stack
trace.Runwith--info or--debug option to getmore log
output.Runwith--scan to getfull insights.
|
|


*Getmore help at https://help.gradle.org <http://help.gradle.org>

DeprecatedGradlefeatures were used inthisbuild,making it
incompatible withGradle7.0.
Use'--warning-mode all'to show the individual deprecation warnings.
|
|

Seehttps://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings

<http://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings>

BUILD FAILED in463ms
|

Many thanks to you,

Jérémie


Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :

You might want to run it with —info or —debug flag to see what
might be failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.

From: Jérémie Pilette 
Reply: Jérémie Pilette 

Date: January 2, 2020 at 2:47:55 PM
        To: CAS Community 
    Cc: dkopy...@unicon.net 
Subject: Re: [cas-user] 6.2.x Gradle Compilation



Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script
'/home/USER/bin/cas-overlay-template/gradle/tasks.gradle'
   

Re: [cas-user] 6.2.x Gradle Compilation

2022-06-19 Thread Gilles-Dereck GNANCADJA
Hello, I'need help please please!

I'm working on deployement of CAS and for gradlew step i get this error 
please help me!!


┌──(root💀dgtcp)-[/home/dgtcp/cas-management-overlay]
└─# ./gradlew executable
Starting a Gradle Daemon (subsequent builds will be faster)

FAILURE: Build failed with an exception.

* What went wrong:
A problem occurred configuring root project 'cas-management'.
> Could not resolve all files for configuration ':casBootWarOverlay'.
   > Could not find org.apereo.cas:cas-mgmt-webapp-tomcat:6.3.0-SNAPSHOT.
 Searched in the following locations:
   - 
file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
file:/root/.m2/repository/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://repo.maven.apache.org/maven2/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://oss.sonatype.org/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://oss.sonatype.org/content/repositories/snapshots/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
   - 
https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/maven-metadata.xml
   - 
https://build.shibboleth.net/nexus/content/repositories/releases/org/apereo/cas/cas-mgmt-webapp-tomcat/6.3.0-SNAPSHOT/cas-mgmt-webapp-tomcat-6.3.0-SNAPSHOT.pom
 Required by:
 project :

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or 
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.8/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 2m 24s
   

Le dimanche 9 février 2020 à 12:29:13 UTC+1, jerem@gmail.com a écrit :

> Hello,
>
> Thanks for your response.
> I come back to (try) to finished my installation...
>
> I have succeed in compiling, but I have an error when I try to deploy on 
> tomcat9.
>
> First, is that possible to use *Tomcat-9.0.16* knowing that in 
> gradle.properties it is written *tomcatVersion=9.0.30* (On debian 
> package)?
>
> Secondly, this is what I have with  *./gradlew run —info*
>
> ./gradlew run —info
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Task '—info' not found in root project 'cas'.
>
> * Try:
> Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
> option to get the stack trace. Run with --info or --debug option to get 
> more log output. Run with --scan to get full insights.
>
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it 
> incompatible with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See https://
> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> BUILD FAILED in 463ms
>
> Many thanks to you,
>
> Jérémie
>
>
> Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
>
>> You might want to run it with —info or —debug flag to see what might be 
>> failing, like so:
>>
>> ./gradlew run —info
>>
>> or build and run as two separate steps:
>>
>> ./gradlew clean build
>> java -jar build/libs/cas.war
>>
>> D.
>>
>> From: Jérémie Pilette 
>> Reply: Jérémie Pilette 
>>
> Date: January 2, 2020 at 2:47:55 PM
>> To: CAS Community 
>> Cc: dkopy...@unicon.net 
>> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>>
>
>> Hi Dmitriy,
>> thank you.
>> Now I have another ailed :
>>
>> > Task :run FAILED
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>>
>> * What went wrong:
>> Execution failed for task ':run'.
>&g

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Pavlos Drandakis
By default, systemd, allows tomcat to write only under the following
directories:
/etc/tomcat9/Catalina/
/var/lib/tomcat9/webapps/
/var/log/tomcat9/

So, you should override systemd - tomcat settings, to allow writing to any
other directory (/var/log/ in your case).

Add the following in /etc/systemd/system/tomcat9.service.d/override.conf
file (if it's not already there, just create it)

[Service]
ReadWritePaths=/var/log/

If you want to add more directories add more ReadWritePaths=xxx entries

Pavlos




On Tue, Feb 11, 2020 at 8:18 PM Ray Bon  wrote:

> tomcat user will need write access to those files. If the files do not
> exist, create them:
> # touch /var/log/cas.log
> # chgrp tomcat /var/log/cas.log
>
> My /var/log has these permissions
> drwxrwxr-x 18 root syslog   4096 Feb 11 00:00 log
>
> so tomcat user can not create those files, it must be done beforehand.
>
> Ray
>
> On Tue, 2020-02-11 at 10:05 -0800, Jérémie Pilette wrote:
>
> I work with Debian 10 / Tomcat 9.0.16
>
> To start : systemctl start tomcat9
>
> root@debian10:~# ps aux | grep tomcat
> tomcat9793  1.9  3.6 14146344 1197524 ?Ssl  17:07   1:06 /usr/lib/
> jvm/java-11-openjdk-amd64/bin/java -Djava.util.logging.config.file=/var/
> lib/tomcat9/conf/logging.properties -Djava.util.logging.manager=org.apache
> .juli.ClassLoaderLogManager -Djava.awt.headless=true -Djdk.tls.
> ephemeralDHKeySize=2048 
> -Djava.protocol.handler.pkgs=org.apache.catalina.webresources
> -Dorg.apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.
> endorsed.dirs= -classpath /usr/share/tomcat9/bin/bootstrap.jar:/usr/share/
> tomcat9/bin/tomcat-juli.jar -Dcatalina.base=/var/lib/tomcat9 -Dcatalina.
> home=/usr/share/tomcat9 -Djava.io.tmpdir=/tmp
> org.apache.catalina.startup.Bootstrap start
> root 10085  0.0  0.0   6144   896 pts/0S+   18:03   0:00 grep
> tomcat
>
>
> Jérémie
>
>
> Le mardi 11 février 2020 19:00:21 UTC+1, rbon a écrit :
>
> How are you starting tomcat?
> Is catalina.out being written to /var/log or is it in TOMCAT_HOME/logs?
>
> To see process owner:
> $ ps aux | grep tomcat
>
> Ray
>
> On Tue, 2020-02-11 at 09:06 -0800, Jérémie Pilette wrote:
>
> Sorry, it is
>
>- cas.log
>- cas_audit.log
>
> of course...
>
> --
>
>
> Ray Bon
> Programmer Analyst
> Development Services, University Systems
> 2507218831 | CLE 019 | rb...@uvic.ca
>
> I respectfully acknowledge that my place of work is located within the
> ancestral, traditional and unceded territory of the Songhees, Esquimalt and
> WSÁNEĆ Nations.
>
> --
>
> Ray Bon
> Programmer Analyst
> Development Services, University Systems
> 2507218831 | CLE 019 | r...@uvic.ca
>
> I respectfully acknowledge that my place of work is located within the
> ancestral, traditional and unceded territory of the Songhees, Esquimalt and
> WSÁNEĆ Nations.
>
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> ---
> You received this message because you are subscribed to the Google Groups
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an
> email to cas-user+unsubscr...@apereo.org.
> To view this discussion on the web visit
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/d1fb4904d98bd038ef7614a1ba3fd6e33f4963c4.camel%40uvic.ca
> 
> .
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/CAKP%3DBg0YD2nnt_KBZuGrr8mt3vrzs4fvhVd2XS_DPz%3DMcv%2BwKA%40mail.gmail.com.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
Oh! many thanks,
it seems to be good. Just about this line!

I have the authentification page and a connection test with a usename and 
password in LDAP run...

Many thanks,

Jérémie

Le mardi 11 février 2020 20:06:29 UTC+1, rbon a écrit :
>
> Try searchFilter (I do not see userFilter, it may be from a previous 
> version - I am using 6.1)
> cas.authn.ldap[0].searchFilter=uid={user}
>
> I do not see searchFilter in the properties for authentication, it does 
> show up elsewhere on the properties page, 
> https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#ldap-authentication
>
> Ray
>
> On Tue, 2020-02-11 at 10:39 -0800, Jérémie Pilette wrote:
>
> I have some difficulties to solve this for the moment... about rights...
>
> Waiting, 
> I have selected the main log which could be interesting (attached file)
> My cas.properties too.
>
> Thank you,
>
> Jérémie
>
>
> -- 
>
> Ray Bon
> Programmer Analyst
> Development Services, University Systems
> 2507218831 | CLE 019 | rb...@uvic.ca 
>
> I respectfully acknowledge that my place of work is located within the 
> ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
> WSÁNEĆ Nations.
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/9637f52c-af19-44f7-9d82-c3a6cbae65bf%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Ray Bon
Try searchFilter (I do not see userFilter, it may be from a previous version - 
I am using 6.1)
cas.authn.ldap[0].searchFilter=uid={user}

I do not see searchFilter in the properties for authentication, it does show up 
elsewhere on the properties page, 
https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#ldap-authentication

Ray

On Tue, 2020-02-11 at 10:39 -0800, Jérémie Pilette wrote:
I have some difficulties to solve this for the moment... about rights...

Waiting,
I have selected the main log which could be interesting (attached file)
My cas.properties too.

Thank you,

Jérémie



--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/ef11fd6bbcd91d0a5a7adb590c5d8b8e538aecf7.camel%40uvic.ca.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
I have some difficulties to solve this for the moment... about rights...

Waiting, 
I have selected the main log which could be interesting (attached file)
My cas.properties too.

Thank you,

Jérémie


-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/708ce02b-9837-4906-a21e-76094f8903c0%40apereo.org.


cas.properties
Description: Binary data


catalina.out
Description: Binary data


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Ray Bon
tomcat user will need write access to those files. If the files do not exist, 
create them:
# touch /var/log/cas.log
# chgrp tomcat /var/log/cas.log

My /var/log has these permissions
drwxrwxr-x 18 root syslog   4096 Feb 11 00:00 log

so tomcat user can not create those files, it must be done beforehand.

Ray

On Tue, 2020-02-11 at 10:05 -0800, Jérémie Pilette wrote:
I work with Debian 10 / Tomcat 9.0.16

To start : systemctl start tomcat9

root@debian10:~# ps aux | grep tomcat
tomcat9793  1.9  3.6 14146344 1197524 ?Ssl  17:07   1:06 
/usr/lib/jvm/java-11-openjdk-amd64/bin/java 
-Djava.util.logging.config.file=/var/lib/tomcat9/conf/logging.properties 
-Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager 
-Djava.awt.headless=true -Djdk.tls.ephemeralDHKeySize=2048 
-Djava.protocol.handler.pkgs=org.apache.catalina.webresources 
-Dorg.apache.catalina.security.SecurityListener.UMASK=0027 
-Dignore.endorsed.dirs= -classpath 
/usr/share/tomcat9/bin/bootstrap.jar:/usr/share/tomcat9/bin/tomcat-juli.jar 
-Dcatalina.base=/var/lib/tomcat9 -Dcatalina.home=/usr/share/tomcat9 
-Djava.io.tmpdir=/tmp org.apache.catalina.startup.Bootstrap start
root 10085  0.0  0.0   6144   896 pts/0S+   18:03   0:00 grep tomcat


Jérémie


Le mardi 11 février 2020 19:00:21 UTC+1, rbon a écrit :
How are you starting tomcat?
Is catalina.out being written to /var/log or is it in TOMCAT_HOME/logs?

To see process owner:
$ ps aux | grep tomcat

Ray

On Tue, 2020-02-11 at 09:06 -0800, Jérémie Pilette wrote:
Sorry, it is

  *   cas.log
  *   cas_audit.log

of course...

--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | rb...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/d1fb4904d98bd038ef7614a1ba3fd6e33f4963c4.camel%40uvic.ca.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
I work with Debian 10 / Tomcat 9.0.16

To start : systemctl start tomcat9

root@debian10:~# ps aux | grep tomcat
tomcat9793  1.9  3.6 14146344 1197524 ?Ssl  17:07   1:06 /usr/lib/
jvm/java-11-openjdk-amd64/bin/java -Djava.util.logging.config.file=/var/lib/
tomcat9/conf/logging.properties -Djava.util.logging.manager=org.apache.juli.
ClassLoaderLogManager -Djava.awt.headless=true -Djdk.tls.ephemeralDHKeySize=
2048 -Djava.protocol.handler.pkgs=org.apache.catalina.webresources -Dorg.
apache.catalina.security.SecurityListener.UMASK=0027 -Dignore.endorsed.dirs= 
-classpath /usr/share/tomcat9/bin/bootstrap.jar:/usr/share/tomcat9/bin/
tomcat-juli.jar -Dcatalina.base=/var/lib/tomcat9 
-Dcatalina.home=/usr/share/tomcat9 
-Djava.io.tmpdir=/tmp org.apache.catalina.startup.Bootstrap start
root 10085  0.0  0.0   6144   896 pts/0S+   18:03   0:00 grep tomcat


Jérémie


Le mardi 11 février 2020 19:00:21 UTC+1, rbon a écrit :
>
> How are you starting tomcat?
> Is catalina.out being written to /var/log or is it in TOMCAT_HOME/logs?
>
> To see process owner:
> $ ps aux | grep tomcat
>
> Ray
>
> On Tue, 2020-02-11 at 09:06 -0800, Jérémie Pilette wrote:
>
> Sorry, it is 
>
>- cas.log
>- cas_audit.log
>
> of course...
>
> -- 
>
> Ray Bon
> Programmer Analyst
> Development Services, University Systems
> 2507218831 | CLE 019 | rb...@uvic.ca 
>
> I respectfully acknowledge that my place of work is located within the 
> ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
> WSÁNEĆ Nations.
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/832cde38-1375-448e-b6c5-7fa1fd6b6a54%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Ray Bon
How are you starting tomcat?
Is catalina.out being written to /var/log or is it in TOMCAT_HOME/logs?

To see process owner:
$ ps aux | grep tomcat

Ray

On Tue, 2020-02-11 at 09:06 -0800, Jérémie Pilette wrote:
Sorry, it is

  *   cas.log
  *   cas_audit.log

of course...

--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/016687850adb2c4ea0a7d1d276ed4aee5e9c5064.camel%40uvic.ca.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
Sorry, it is 

   - cas.log
   - cas_audit.log

of course...

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/26291c56-164a-45e6-8dcf-a4c2bb78af4f%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
I have some difficulties to know the user who can write in this files :

   - cas.out
   - cas_audit.out

It is not tomcat.

Unless using chmod 777 ...

Jérémie

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/90fe9950-bd2a-4792-85b4-356c1b61e323%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Ray Bon
Jérémie,

Check your log and make sure that 'permission denied' errors are gone.
I did not see anything related to CAS failures in the previous log you posted. 
There were spring boot issues (maybe related to tomcat version mismatch).

Get most recent version of tomcat, then post the logs.

Ray

On Tue, 2020-02-11 at 08:17 -0800, Jérémie Pilette wrote:
Yes Bob,
I have change the right from root to tomcat in /var/log   (*.cas..)

For information this is my dependancies to compile :
dependencies {
// Other CAS dependencies/modules may be listed here...
// implementation 
"org.apereo.cas:cas-server-support-json-service-registry:${casServerVersion}"
compile "org.apereo.cas:cas-server-support-ldap:${project.'cas.version'}"
compile "org.apereo.cas:cas-server-support-pm-ldap:${project.'cas.version'}"
compile 
"org.apereo.cas:cas-server-support-pm-webflow:${project.'cas.version'}"
compile 
"org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"
compile "org.apereo.cas:cas-server-support-saml:${project.'cas.version'}"
}


Jérémie


Le mardi 11 février 2020 16:32:21 UTC+1, Jérémie Pilette a écrit :
Sorry,

my log in the attached file.

Thank you

Jérémie




--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/9ede68687296cd5682f9f91ac9f6559fbb28e5f9.camel%40uvic.ca.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
Yes Bob,
I have change the right from root to tomcat in /var/log   (*.cas..)

For information this is my dependancies to compile :
dependencies {
// Other CAS dependencies/modules may be listed here...
// implementation 
"org.apereo.cas:cas-server-support-json-service-registry:${casServerVersion}"
compile 
"org.apereo.cas:cas-server-support-ldap:${project.'cas.version'}"
compile 
"org.apereo.cas:cas-server-support-pm-ldap:${project.'cas.version'}"
compile 
"org.apereo.cas:cas-server-support-pm-webflow:${project.'cas.version'}"
compile 
"org.apereo.cas:cas-server-support-json-service-registry:${project.'cas.version'}"
compile 
"org.apereo.cas:cas-server-support-saml:${project.'cas.version'}"
}


Jérémie


Le mardi 11 février 2020 16:32:21 UTC+1, Jérémie Pilette a écrit :
>
> Sorry,
>
> my log in the attached file.
>
> Thank you
>
> Jérémie
>
>
>
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/8b358f22-0b0b-48a8-9c92-13e26c01f07d%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
Sorry,

my log in the attached file.

Thank you

Jérémie



-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/bbb17e6b-7ed6-41af-bfa2-7adf0b9a5a04%40apereo.org.


catalina.out
Description: Binary data


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Bob
iguration$EmbeddedTomcat.class]:
>>>  
>>> Initialization of bean failed; nested exception is 
>>> java.lang.NoSuchMethodError: 'void 
>>> org.apache.catalina.valves.RemoteIpValve.setHostHeader(java.lang.String)'
>>>
>>>
>>>
>>> Jérémie
>>>
>>>
>>> Le lundi 10 février 2020 17:50:56 UTC+1, rbon a écrit : 
>>>>
>>>> Jérémie,
>>>>
>>>> That means that 'cas.serviceregistry.config.location' is not a 
>>>> property. See properties here, 
>>>> https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#service-registry,
>>>>  
>>>> for 6.1.x
>>>>
>>>> 'config.location' is not there.
>>>> Also, it is 'serviceRegistry'.
>>>>
>>>> Ray
>>>>
>>>> On Sun, 2020-02-09 at 05:04 -0800, Jérémie Pilette wrote:
>>>>
>>>> Sorry for the secondly part of my previous message.
>>>> It was not the good command line.
>>>>
>>>> With the good command line I have this :
>>>>
>>>> [...]
>>>> 2020-02-09 12:54:49,372 ERROR [org.apereo.cas.configuration.
>>>> CasConfigurationPropertiesValidator] - <
>>>> Failed to bind properties under 'cas' to org.apereo.cas.configuration.
>>>> CasConfigurationProperties
>>>>
>>>> cas.serviceregistry.config.location = file:/etc/cas/services (
>>>> Origin: "cas.serviceRegistry.config.location" from property source 
>>>> "bootstrapProperties-applicationProfilesCompositeProperties")
>>>>
>>>> Listed settings above are no longer recognized by CAS 6.2.0-RC2. They may 
>>>> have been renamed, removed, or relocated to a new address in the CAS 
>>>> configuration schema. CAS will ignore such settings and will proceed 
>>>> with its normal initialization sequence. Please consult the CAS 
>>>> documentation to review and adjust each setting to find an alternative 
>>>> or remove the definition. Failure to do so puts the stability of the 
>>>> CAS server deployment in danger and complicates future upgrades.
>>>> >
>>>> [...]
>>>> > Task :run FAILED
>>>> :run (Thread[Execution worker for ':' Thread 7,5,main]) completed. Took 
>>>> 13.924 secs.
>>>>
>>>> FAILURE: Build failed with an exception.
>>>>
>>>> * Where:
>>>> Script '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' 
>>>> line: 64
>>>>
>>>> * What went wrong:
>>>> Execution failed for task ':run'.
>>>> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
>>>> finished with non-zero exit value 1
>>>>
>>>> * Try:
>>>> Run with --stacktrace option to get the stack trace. Run with --debug 
>>>> option to get more log output. Run with --scan to get full insights.
>>>>
>>>> * Get more help at https://help.gradle.org
>>>>
>>>> Deprecated Gradle features were used in this build, making it 
>>>> incompatible with Gradle 7.0.
>>>> Use '--warning-mode all' to show the individual deprecation warnings.
>>>> See https://
>>>> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>>>>
>>>> BUILD FAILED in 15s
>>>> 5 actionable tasks: 3 executed, 2 up-to-date
>>>>
>>>>
>>>>
>>>> Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit : 
>>>>
>>>> Hello,
>>>>
>>>> Thanks for your response.
>>>> I come back to (try) to finished my installation...
>>>>
>>>> I have succeed in compiling, but I have an error when I try to deploy 
>>>> on tomcat9.
>>>>
>>>> First, is that possible to use *Tomcat-9.0.16* knowing that in 
>>>> gradle.properties it is written *tomcatVersion=9.0.30* (On debian 
>>>> package)?
>>>>
>>>> Secondly, this is what I have with  *./gradlew run —info*
>>>>
>>>> ./gradlew run —info
>>>>
>>>> FAILURE: Build failed with an exception.
>>>>
>>>> * What went wrong:
>>>> Task '—info' not found in root project 'ca

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Dmitriy Kopylenko
CAS documentation to review and 
> > > > > > > adjust each setting to find an alternative or remove the 
> > > > > > > definition. Failure to do so puts the stability of the CAS server 
> > > > > > > deployment in danger and complicates future upgrades.
> > > > > > > >
> > > > > > > [...]
> > > > > > > > Task :run FAILED
> > > > > > > :run (Thread[Execution worker for ':' Thread 7,5,main]) 
> > > > > > > completed. Took 13.924 secs.
> > > > > > >
> > > > > > > FAILURE: Build failed with an exception.
> > > > > > >
> > > > > > > * Where:
> > > > > > > Script 
> > > > > > > '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' 
> > > > > > > line: 64
> > > > > > >
> > > > > > > * What went wrong:
> > > > > > > Execution failed for task ':run'.
> > > > > > > > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
> > > > > > > > finished with non-zero exit value 1
> > > > > > >
> > > > > > > * Try:
> > > > > > > Run with --stacktrace option to get the stack trace. Run with 
> > > > > > > --debug option to get more log output. Run with --scan to get 
> > > > > > > full insights.
> > > > > > >
> > > > > > > * Get more help at https://help.gradle.org
> > > > > > >
> > > > > > > Deprecated Gradle features were used in this build, making it 
> > > > > > > incompatible with Gradle 7.0.
> > > > > > > Use '--warning-mode all' to show the individual deprecation 
> > > > > > > warnings.
> > > > > > > See 
> > > > > > > https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
> > > > > > >
> > > > > > > BUILD FAILED in 15s
> > > > > > > 5 actionable tasks: 3 executed, 2 up-to-date
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a 
> > > > > > > écrit :
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > Thanks for your response.
> > > > > > > > I come back to (try) to finished my installation...
> > > > > > > >
> > > > > > > > I have succeed in compiling, but I have an error when I try to 
> > > > > > > > deploy on tomcat9.
> > > > > > > >
> > > > > > > > First, is that possible to use Tomcat-9.0.16 knowing that in 
> > > > > > > > gradle.properties it is written tomcatVersion=9.0.30 (On debian 
> > > > > > > > package)?
> > > > > > > >
> > > > > > > > Secondly, this is what I have with  ./gradlew run —info
> > > > > > > >
> > > > > > > > ./gradlew run —info
> > > > > > > >
> > > > > > > > FAILURE: Build failed with an exception.
> > > > > > > >
> > > > > > > > * What went wrong:
> > > > > > > > Task '—info' not found in root project 'cas'.
> > > > > > > >
> > > > > > > > * Try:
> > > > > > > > Run gradlew tasks to get a list of available tasks. Run with 
> > > > > > > > --stacktrace option to get the stack trace. Run with --info or 
> > > > > > > > --debug option to get more log output. Run with --scan to get 
> > > > > > > > full insights.
> > > > > > > >
> > > > > > > > * Get more help at https://help.gradle.org
> > > > > > > >
> > > > > > > > Deprecated Gradle features were used in this build, making it 
> > > > > > > > incompatible with Gradle 7.0.
> > > > > > > > Use '--warning-mode all' to show the individual deprecation 
> > > > > > > > warnings.
>

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
onfiguration.
>>> CasConfigurationProperties
>>>
>>> cas.serviceregistry.config.location = file:/etc/cas/services (
>>> Origin: "cas.serviceRegistry.config.location" from property source 
>>> "bootstrapProperties-applicationProfilesCompositeProperties")
>>>
>>> Listed settings above are no longer recognized by CAS 6.2.0-RC2. They may 
>>> have been renamed, removed, or relocated to a new address in the CAS 
>>> configuration schema. CAS will ignore such settings and will proceed 
>>> with its normal initialization sequence. Please consult the CAS 
>>> documentation to review and adjust each setting to find an alternative 
>>> or remove the definition. Failure to do so puts the stability of the 
>>> CAS server deployment in danger and complicates future upgrades.
>>> >
>>> [...]
>>> > Task :run FAILED
>>> :run (Thread[Execution worker for ':' Thread 7,5,main]) completed. Took 
>>> 13.924 secs.
>>>
>>> FAILURE: Build failed with an exception.
>>>
>>> * Where:
>>> Script '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' 
>>> line: 64
>>>
>>> * What went wrong:
>>> Execution failed for task ':run'.
>>> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
>>> finished with non-zero exit value 1
>>>
>>> * Try:
>>> Run with --stacktrace option to get the stack trace. Run with --debug 
>>> option to get more log output. Run with --scan to get full insights.
>>>
>>> * Get more help at https://help.gradle.org
>>>
>>> Deprecated Gradle features were used in this build, making it 
>>> incompatible with Gradle 7.0.
>>> Use '--warning-mode all' to show the individual deprecation warnings.
>>> See https://
>>> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>>>
>>> BUILD FAILED in 15s
>>> 5 actionable tasks: 3 executed, 2 up-to-date
>>>
>>>
>>>
>>> Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit : 
>>>
>>> Hello,
>>>
>>> Thanks for your response.
>>> I come back to (try) to finished my installation...
>>>
>>> I have succeed in compiling, but I have an error when I try to deploy on 
>>> tomcat9.
>>>
>>> First, is that possible to use *Tomcat-9.0.16* knowing that in 
>>> gradle.properties it is written *tomcatVersion=9.0.30* (On debian 
>>> package)?
>>>
>>> Secondly, this is what I have with  *./gradlew run —info*
>>>
>>> ./gradlew run —info
>>>
>>> FAILURE: Build failed with an exception.
>>>
>>> * What went wrong:
>>> Task '—info' not found in root project 'cas'.
>>>
>>> * Try:
>>> Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
>>> option to get the stack trace. Run with --info or --debug option to get 
>>> more 
>>> log output. Run with --scan to get full insights.
>>>
>>> * Get more help at https://help.gradle.org
>>>
>>> Deprecated Gradle features were used in this build, making it 
>>> incompatible with Gradle 7.0.
>>> Use '--warning-mode all' to show the individual deprecation warnings.
>>> See https://
>>> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>>>
>>> BUILD FAILED in 463ms
>>>
>>> Many thanks to you,
>>>
>>> Jérémie
>>>
>>>
>>> Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit : 
>>>
>>> You might want to run it with —info or —debug flag to see what might be 
>>> failing, like so:
>>>
>>> ./gradlew run —info
>>>
>>> or build and run as two separate steps:
>>>
>>> ./gradlew clean build
>>> java -jar build/libs/cas.war
>>>
>>> D.
>>>
>>>
>>> From: Jérémie Pilette 
>>> Reply: Jérémie Pilette 
>>> Date: January 2, 2020 at 2:47:55 PM
>>> To: CAS Community 
>>> Cc: dkopy...@unicon.net 
>>> Subject:  Re: [cas-user] 6.2.x Gradle Compilation
>>>
>>> Hi Dmitriy,
>>> thank you.
>>> Now I have another ailed :
>>>
>>> > Task :run FAILED
>>>
>>> FAILURE: Build failed with an 

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Dmitriy Kopylenko
.location' is not there.
> > > > Also, it is 'serviceRegistry'.
> > > >
> > > > Ray
> > > >
> > > > On Sun, 2020-02-09 at 05:04 -0800, Jérémie Pilette wrote:
> > > > > Sorry for the secondly part of my previous message.
> > > > > It was not the good command line.
> > > > >
> > > > > With the good command line I have this :
> > > > >
> > > > > [...]
> > > > > 2020-02-09 12:54:49,372 ERROR 
> > > > > [org.apereo.cas.configuration.CasConfigurationPropertiesValidator] - <
> > > > > Failed to bind properties under 'cas' to 
> > > > > org.apereo.cas.configuration.CasConfigurationProperties
> > > > >
> > > > >         cas.serviceregistry.config.location = file:/etc/cas/services 
> > > > > (Origin: "cas.serviceRegistry.config.location" from property source 
> > > > > "bootstrapProperties-applicationProfilesCompositeProperties")
> > > > >
> > > > > Listed settings above are no longer recognized by CAS 6.2.0-RC2. They 
> > > > > may have been renamed, removed, or relocated to a new address in the 
> > > > > CAS configuration schema. CAS will ignore such settings and will 
> > > > > proceed with its normal initialization sequence. Please consult the 
> > > > > CAS documentation to review and adjust each setting to find an 
> > > > > alternative or remove the definition. Failure to do so puts the 
> > > > > stability of the CAS server deployment in danger and complicates 
> > > > > future upgrades.
> > > > > >
> > > > > [...]
> > > > > > Task :run FAILED
> > > > > :run (Thread[Execution worker for ':' Thread 7,5,main]) completed. 
> > > > > Took 13.924 secs.
> > > > >
> > > > > FAILURE: Build failed with an exception.
> > > > >
> > > > > * Where:
> > > > > Script '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' 
> > > > > line: 64
> > > > >
> > > > > * What went wrong:
> > > > > Execution failed for task ':run'.
> > > > > > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
> > > > > > finished with non-zero exit value 1
> > > > >
> > > > > * Try:
> > > > > Run with --stacktrace option to get the stack trace. Run with --debug 
> > > > > option to get more log output. Run with --scan to get full insights.
> > > > >
> > > > > * Get more help at https://help.gradle.org
> > > > >
> > > > > Deprecated Gradle features were used in this build, making it 
> > > > > incompatible with Gradle 7.0.
> > > > > Use '--warning-mode all' to show the individual deprecation warnings.
> > > > > See 
> > > > > https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
> > > > >
> > > > > BUILD FAILED in 15s
> > > > > 5 actionable tasks: 3 executed, 2 up-to-date
> > > > >
> > > > >
> > > > >
> > > > > Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit :
> > > > > > Hello,
> > > > > >
> > > > > > Thanks for your response.
> > > > > > I come back to (try) to finished my installation...
> > > > > >
> > > > > > I have succeed in compiling, but I have an error when I try to 
> > > > > > deploy on tomcat9.
> > > > > >
> > > > > > First, is that possible to use Tomcat-9.0.16 knowing that in 
> > > > > > gradle.properties it is written tomcatVersion=9.0.30 (On debian 
> > > > > > package)?
> > > > > >
> > > > > > Secondly, this is what I have with  ./gradlew run —info
> > > > > >
> > > > > > ./gradlew run —info
> > > > > >
> > > > > > FAILURE: Build failed with an exception.
> > > > > >
> > > > > > * What went wrong:
> > > > > > Task '—info' not found in root project 'cas'.
> > > > > >
> > > > > > * Try:
> > &

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
 15s
>> 5 actionable tasks: 3 executed, 2 up-to-date
>>
>>
>>
>> Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit :
>>
>> Hello,
>>
>> Thanks for your response.
>> I come back to (try) to finished my installation...
>>
>> I have succeed in compiling, but I have an error when I try to deploy on
>> tomcat9.
>>
>> First, is that possible to use *Tomcat-9.0.16* knowing that in
>> gradle.properties it is written *tomcatVersion=9.0.30* (On debian
>> package)?
>>
>> Secondly, this is what I have with  *./gradlew run —info*
>>
>> ./gradlew run —info
>>
>> FAILURE: Build failed with an exception.
>>
>> * What went wrong:
>> Task '—info' not found in root project 'cas'.
>>
>> * Try:
>> Run gradlew tasks to get a list of available tasks. Run with --stacktrace
>> option to get the stack trace. Run with --info or --debug option to get
>> more log output. Run with --scan to get full insights.
>>
>> * Get more help at https://help.gradle.org
>>
>> Deprecated Gradle features were used in this build, making it
>> incompatible with Gradle 7.0.
>> Use '--warning-mode all' to show the individual deprecation warnings.
>> See https://
>> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>>
>> BUILD FAILED in 463ms
>>
>> Many thanks to you,
>>
>> Jérémie
>>
>>
>> Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
>>
>> You might want to run it with —info or —debug flag to see what might be
>> failing, like so:
>>
>> ./gradlew run —info
>>
>> or build and run as two separate steps:
>>
>> ./gradlew clean build
>> java -jar build/libs/cas.war
>>
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: Jérémie Pilette 
>> Date: January 2, 2020 at 2:47:55 PM
>> To: CAS Community 
>> Cc: dkopy...@unicon.net 
>> Subject:  Re: [cas-user] 6.2.x Gradle Compilation
>>
>> Hi Dmitriy,
>> thank you.
>> Now I have another ailed :
>>
>> > Task :run FAILED
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>>
>> * What went wrong:
>> Execution failed for task ':run'.
>> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java''
>> finished with non-zero exit value 1
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or
>> --debug option to get more log output. Run with --scan to get full insights.
>>
>> * Get more help at https://help.gradle.org
>>
>> Deprecated Gradle features were used in this build, making it
>> incompatible with Gradle 7.0.
>> Use '--warning-mode all' to show the individual deprecation warnings.
>> See
>> https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings
>>
>> Thank you,
>> Jérémie
>>
>>
>> Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit :
>>
>> Hi there.
>>
>> Change version of CAS to 6.2 RC2 in gradle.properties like so:
>>
>> *cas.version=6.2.0-RC2*
>>
>> Best,
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: cas-...@apereo.org 
>> Date: January 2, 2020 at 7:57:00 AM
>> To: CAS Community 
>> Subject:  [cas-user] 6.2.x Gradle Compilation
>>
>> Hi everybody,
>> I have a problem with my first compilation of cas-overlay-template (6.2.x)
>>
>> Here this is  my messages :
>>
>> FAILURE: Build failed with an exception.
>> A problem occurred evaluating root project 'cas'.
>> > Could not resolve all artifacts for configuration 'classpath'.
>>> Could not find
>> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
>> [...]
>> Could not find
>> org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
>>  Searched in the following locations:
>> [...]
>>
>>
>> Do you have an idea please ?
>>
>> Jérémie
>> --
>> - Website: https://apereo.github.io/cas
>> - Gitter Chatroom: https://gitter.im/apereo/cas
>> - List Guidelines: https://goo.gl/1VRrw7
>> - Contributions: https://goo.gl/mh7qDG
>> ---
>> You received this message because you are subscribed to the Google Groups
>&g

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-11 Thread Jérémie Pilette
tomcatServletWebServerFactory' defined in class path 
resource 
[org/springframework/boot/autoconfigure/web/servlet/ServletWebServerFactoryConfiguration$EmbeddedTomcat.class]:
 
Initialization of bean failed; nested exception is 
java.lang.NoSuchMethodError: 'void 
org.apache.catalina.valves.RemoteIpValve.setHostHeader(java.lang.String)'



Jérémie


Le lundi 10 février 2020 17:50:56 UTC+1, rbon a écrit :
>
> Jérémie,
>
> That means that 'cas.serviceregistry.config.location' is not a property. 
> See properties here, 
> https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#service-registry,
>  
> for 6.1.x
>
> 'config.location' is not there.
> Also, it is 'serviceRegistry'.
>
> Ray
>
> On Sun, 2020-02-09 at 05:04 -0800, Jérémie Pilette wrote:
>
> Sorry for the secondly part of my previous message.
> It was not the good command line.
>
> With the good command line I have this :
>
> [...]
> 2020-02-09 12:54:49,372 ERROR [org.apereo.cas.configuration.
> CasConfigurationPropertiesValidator] - <
> Failed to bind properties under 'cas' to org.apereo.cas.configuration.
> CasConfigurationProperties
>
> cas.serviceregistry.config.location = file:/etc/cas/services (
> Origin: "cas.serviceRegistry.config.location" from property source 
> "bootstrapProperties-applicationProfilesCompositeProperties")
>
> Listed settings above are no longer recognized by CAS 6.2.0-RC2. They may 
> have been renamed, removed, or relocated to a new address in the CAS 
> configuration schema. CAS will ignore such settings and will proceed with 
> its normal initialization sequence. Please consult the CAS documentation 
> to review and adjust each setting to find an alternative or remove the 
> definition. Failure to do so puts the stability of the CAS server 
> deployment in danger and complicates future upgrades.
> >
> [...]
> > Task :run FAILED
> :run (Thread[Execution worker for ':' Thread 7,5,main]) completed. Took 
> 13.924 secs.
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' line: 
> 64
>
> * What went wrong:
> Execution failed for task ':run'.
> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
> finished with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --debug 
> option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it 
> incompatible with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See https://
> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> BUILD FAILED in 15s
> 5 actionable tasks: 3 executed, 2 up-to-date
>
>
>
> Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit : 
>
> Hello,
>
> Thanks for your response.
> I come back to (try) to finished my installation...
>
> I have succeed in compiling, but I have an error when I try to deploy on 
> tomcat9.
>
> First, is that possible to use *Tomcat-9.0.16* knowing that in 
> gradle.properties it is written *tomcatVersion=9.0.30* (On debian 
> package)?
>
> Secondly, this is what I have with  *./gradlew run —info*
>
> ./gradlew run —info
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Task '—info' not found in root project 'cas'.
>
> * Try:
> Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
> option to get the stack trace. Run with --info or --debug option to get 
> more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it 
> incompatible with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See https://
> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> BUILD FAILED in 463ms
>
> Many thanks to you,
>
> Jérémie
>
>
> Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit : 
>
> You might want to run it with —info or —debug flag to see what might be 
> failing, like so:
>
> ./gradlew run —info
>
> or build and run as two separate steps:
>
> ./gradlew clean build
> java -jar build/libs/cas.war
>
> D.
>
>
> From: Jérémie Pilette 
> Reply: Jérémie Pilette 
> Date: January 2, 2020 at 

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-10 Thread Ray Bon
Jérémie,

That means that 'cas.serviceregistry.config.location' is not a property. See 
properties here, 
https://apereo.github.io/cas/6.1.x/configuration/Configuration-Properties.html#service-registry,
 for 6.1.x

'config.location' is not there.
Also, it is 'serviceRegistry'.

Ray

On Sun, 2020-02-09 at 05:04 -0800, Jérémie Pilette wrote:
Sorry for the secondly part of my previous message.
It was not the good command line.

With the good command line I have this :

[...]
2020-02-09 12:54:49,372 ERROR 
[org.apereo.cas.configuration.CasConfigurationPropertiesValidator] - <
Failed to bind properties under 'cas' to 
org.apereo.cas.configuration.CasConfigurationProperties

cas.serviceregistry.config.location = file:/etc/cas/services (Origin: 
"cas.serviceRegistry.config.location" from property source 
"bootstrapProperties-applicationProfilesCompositeProperties")

Listed settings above are no longer recognized by CAS 6.2.0-RC2. They may have 
been renamed, removed, or relocated to a new address in the CAS configuration 
schema. CAS will ignore such settings and will proceed with its normal 
initialization sequence. Please consult the CAS documentation to review and 
adjust each setting to find an alternative or remove the definition. Failure to 
do so puts the stability of the CAS server deployment in danger and complicates 
future upgrades.
>
[...]
> Task :run FAILED
:run (Thread[Execution worker for ':' Thread 7,5,main]) completed. Took 13.924 
secs.

FAILURE: Build failed with an exception.

* Where:
Script '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' line: 64

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
> non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug option to 
get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 15s
5 actionable tasks: 3 executed, 2 up-to-date



Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit :
Hello,

Thanks for your response.
I come back to (try) to finished my installation...

I have succeed in compiling, but I have an error when I try to deploy on 
tomcat9.

First, is that possible to use Tomcat-9.0.16 knowing that in gradle.properties 
it is written tomcatVersion=9.0.30 (On debian package)?

Secondly, this is what I have with  ./gradlew run —info

./gradlew run —info

FAILURE: Build failed with an exception.

* What went wrong:
Task '—info' not found in root project 'cas'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
option to get the stack trace. Run with --info or --debug option to get more 
log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org<http://help.gradle.org>

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings<http://docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings>

BUILD FAILED in 463ms

Many thanks to you,

Jérémie


Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
You might want to run it with —info or —debug flag to see what might be 
failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.


From: Jérémie Pilette 
Reply: Jérémie Pilette 
Date: January 2, 2020 at 2:47:55 PM
To: CAS Community 
Cc: dkopy...@unicon.net 
Subject:  Re: [cas-user] 6.2.x Gradle Compilation

Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
> non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-09 Thread Jérémie Pilette
Sorry for the secondly part of my previous message.
It was not the good command line.

With the good command line I have this :

[...]
2020-02-09 12:54:49,372 ERROR [org.apereo.cas.configuration.
CasConfigurationPropertiesValidator] - <
Failed to bind properties under 'cas' to org.apereo.cas.configuration.
CasConfigurationProperties

cas.serviceregistry.config.location = file:/etc/cas/services (Origin
: "cas.serviceRegistry.config.location" from property source 
"bootstrapProperties-applicationProfilesCompositeProperties")

Listed settings above are no longer recognized by CAS 6.2.0-RC2. They may 
have been renamed, removed, or relocated to a new address in the CAS 
configuration schema. CAS will ignore such settings and will proceed with 
its normal initialization sequence. Please consult the CAS documentation to 
review and adjust each setting to find an alternative or remove the 
definition. Failure to do so puts the stability of the CAS server 
deployment in danger and complicates future upgrades.
>
[...]
> Task :run FAILED
:run (Thread[Execution worker for ':' Thread 7,5,main]) completed. Took 
13.924 secs.

FAILURE: Build failed with an exception.

* Where:
Script '/home//bin/cas-overlay-template-6.2/gradle/tasks.gradle' line: 
64

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished 
with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https:
//docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 15s
5 actionable tasks: 3 executed, 2 up-to-date



Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit :
>
> Hello,
>
> Thanks for your response.
> I come back to (try) to finished my installation...
>
> I have succeed in compiling, but I have an error when I try to deploy on 
> tomcat9.
>
> First, is that possible to use *Tomcat-9.0.16* knowing that in 
> gradle.properties it is written *tomcatVersion=9.0.30* (On debian 
> package)?
>
> Secondly, this is what I have with  *./gradlew run —info*
>
> ./gradlew run —info
>
> FAILURE: Build failed with an exception.
>
> * What went wrong:
> Task '—info' not found in root project 'cas'.
>
> * Try:
> Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
> option to get the stack trace. Run with --info or --debug option to get 
> more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it 
> incompatible with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See https://
> docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> BUILD FAILED in 463ms
>
> Many thanks to you,
>
> Jérémie
>
>
> Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
>>
>> You might want to run it with —info or —debug flag to see what might be 
>> failing, like so:
>>
>> ./gradlew run —info
>>
>> or build and run as two separate steps:
>>
>> ./gradlew clean build
>> java -jar build/libs/cas.war
>>
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: Jérémie Pilette 
>> Date: January 2, 2020 at 2:47:55 PM
>> To: CAS Community 
>> Cc: dkopy...@unicon.net 
>> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>>
>> Hi Dmitriy,
>> thank you.
>> Now I have another ailed :
>>
>> > Task :run FAILED
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>>
>> * What went wrong:
>> Execution failed for task ':run'.
>> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
>> finished with non-zero exit value 1
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or 
>> --debug option to get more log output. Run with --scan to get full insights.
>>
>> * Get more help at https://help.gradle.org
>>
>> Deprecated Gradle features were used in this build, making it 
>> incompatible with Gradle 7.0.
>> Use '--warnin

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-09 Thread Jérémie Pilette


Le dimanche 9 février 2020 12:29:13 UTC+1, Jérémie Pilette a écrit :
>
> Hello,
>
> Thanks for your response.
> I come back to (try) to finished my installation...
>
> I have succeed in compiling, but I have an error when I try to deploy on 
> tomcat9.
>
> Is that possible to use *Tomcat-9.0.16* knowing that in gradle.properties 
> it is written *tomcatVersion=9.0.30* (On debian package)?
>
>
> Many thanks to you,
>
> Jérémie
>
>
> Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
>>
>> You might want to run it with —info or —debug flag to see what might be 
>> failing, like so:
>>
>> ./gradlew run —info
>>
>> or build and run as two separate steps:
>>
>> ./gradlew clean build
>> java -jar build/libs/cas.war
>>
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: Jérémie Pilette 
>> Date: January 2, 2020 at 2:47:55 PM
>> To: CAS Community 
>> Cc: dkopy...@unicon.net 
>> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>>
>> Hi Dmitriy,
>> thank you.
>> Now I have another ailed :
>>
>> > Task :run FAILED
>>
>> FAILURE: Build failed with an exception.
>>
>> * Where:
>> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>>
>> * What went wrong:
>> Execution failed for task ':run'.
>> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' 
>> finished with non-zero exit value 1
>>
>> * Try:
>> Run with --stacktrace option to get the stack trace. Run with --info or 
>> --debug option to get more log output. Run with --scan to get full insights.
>>
>> * Get more help at https://help.gradle.org
>>
>> Deprecated Gradle features were used in this build, making it 
>> incompatible with Gradle 7.0.
>> Use '--warning-mode all' to show the individual deprecation warnings.
>> See 
>> https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings
>>
>> Thank you,
>> Jérémie
>>
>>
>> Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit : 
>>>
>>> Hi there.
>>>
>>> Change version of CAS to 6.2 RC2 in gradle.properties like so:
>>>
>>> *cas.version=6.2.0-RC2*
>>>
>>> Best,
>>> D.
>>>
>>>
>>> From: Jérémie Pilette 
>>> Reply: cas-...@apereo.org 
>>> Date: January 2, 2020 at 7:57:00 AM
>>> To: CAS Community 
>>> Subject:  [cas-user] 6.2.x Gradle Compilation
>>>
>>> Hi everybody,
>>> I have a problem with my first compilation of cas-overlay-template 
>>> (6.2.x)
>>>
>>> Here this is  my messages :
>>>
>>> FAILURE: Build failed with an exception.
>>> A problem occurred evaluating root project 'cas'.
>>> > Could not resolve all artifacts for configuration 'classpath'.
>>>> Could not find 
>>> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
>>> [...]
>>> Could not find 
>>> org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
>>>  Searched in the following locations:
>>> [...]
>>>
>>>
>>> Do you have an idea please ?
>>>
>>> Jérémie
>>> --
>>> - Website: https://apereo.github.io/cas
>>> - Gitter Chatroom: https://gitter.im/apereo/cas
>>> - List Guidelines: https://goo.gl/1VRrw7
>>> - Contributions: https://goo.gl/mh7qDG
>>> ---
>>> You received this message because you are subscribed to the Google 
>>> Groups "CAS Community" group.
>>> To unsubscribe from this group and stop receiving emails from it, send 
>>> an email to cas-...@apereo.org.
>>> To view this discussion on the web visit 
>>> https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org
>>>  
>>> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org?utm_medium=email&utm_source=footer>
>>> .
>>>
>>>
>>  
>> --
>>
>> This email has been scanned for spam and viruses by Proofpoint 
>> Essentials. Click here 
>> <https://us2.proofpointessentials.com/index01.php?mod_id=11&mod_option=logitem&mail_id=1577994474-hk1Nk1kKYSlm&r_address=dkopylenko%40unicon.net&report=1>
>>  
>> to report this email as spam.
>>
>> = 
>>
>>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/4e44159e-bcd1-408d-803b-a67d5a07bed4%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-02-09 Thread Jérémie Pilette
Hello,

Thanks for your response.
I come back to (try) to finished my installation...

I have succeed in compiling, but I have an error when I try to deploy on 
tomcat9.

First, is that possible to use *Tomcat-9.0.16* knowing that in 
gradle.properties it is written *tomcatVersion=9.0.30* (On debian package)?

Secondly, this is what I have with  *./gradlew run —info*

./gradlew run —info

FAILURE: Build failed with an exception.

* What went wrong:
Task '—info' not found in root project 'cas'.

* Try:
Run gradlew tasks to get a list of available tasks. Run with --stacktrace 
option to get the stack trace. Run with --info or --debug option to get 
more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https:
//docs.gradle.org/6.1.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 463ms

Many thanks to you,

Jérémie


Le jeudi 2 janvier 2020 20:59:28 UTC+1, Dmitriy Kopylenko a écrit :
>
> You might want to run it with —info or —debug flag to see what might be 
> failing, like so:
>
> ./gradlew run —info
>
> or build and run as two separate steps:
>
> ./gradlew clean build
> java -jar build/libs/cas.war
>
> D.
>
>
> From: Jérémie Pilette  
> Reply: Jérémie Pilette  
> Date: January 2, 2020 at 2:47:55 PM
> To: CAS Community  
> Cc: dkopy...@unicon.net   
> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>
> Hi Dmitriy,
> thank you.
> Now I have another ailed :
>
> > Task :run FAILED
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>
> * What went wrong:
> Execution failed for task ':run'.
> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished 
> with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it incompatible 
> with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See 
> https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> Thank you,
> Jérémie
>
>
> Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit : 
>>
>> Hi there.
>>
>> Change version of CAS to 6.2 RC2 in gradle.properties like so:
>>
>> *cas.version=6.2.0-RC2*
>>
>> Best,
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: cas-...@apereo.org 
>> Date: January 2, 2020 at 7:57:00 AM
>> To: CAS Community 
>> Subject:  [cas-user] 6.2.x Gradle Compilation
>>
>> Hi everybody,
>> I have a problem with my first compilation of cas-overlay-template (6.2.x)
>>
>> Here this is  my messages :
>>
>> FAILURE: Build failed with an exception.
>> A problem occurred evaluating root project 'cas'.
>> > Could not resolve all artifacts for configuration 'classpath'.
>>> Could not find 
>> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
>> [...]
>> Could not find 
>> org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
>>  Searched in the following locations:
>> [...]
>>
>>
>> Do you have an idea please ?
>>
>> Jérémie
>> --
>> - Website: https://apereo.github.io/cas
>> - Gitter Chatroom: https://gitter.im/apereo/cas
>> - List Guidelines: https://goo.gl/1VRrw7
>> - Contributions: https://goo.gl/mh7qDG
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "CAS Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to cas-...@apereo.org.
>> To view this discussion on the web visit 
>> https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org
>>  
>> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org?utm_medium=email&utm_source=footer>
>> .
>>
>>
>  
> --
>
> This email has been scanned for spam and viruses by Proofpoint Essentials. 
> Click here 
> <https://us2.proofpointessentials.com/index0

Re: [cas-user] 6.2.x Gradle Compilation

2020-02-01 Thread Tom Healey
Thanks Dmitriy!
Tom

On Fri, Jan 31, 2020 at 2:20 PM Dmitriy Kopylenko 
wrote:

> This might be helpful:
> https://apereo.github.io/2019/01/07/cas61-gettingstarted-overlay/
>
> D.
> On Jan 31, 2020, 14:12 -0500, Tom Healey , wrote:
>
> Ray,
> Again thanks for the quick response.
> I COULD use 6.1.3. I switched to the 6.1 branch and was able to
> successfully build the war.
> THANKS!
>
> Could you point me to some resources on how to work with the CAS overlay?
> I DOCs aren't as helpful to me as I need and this is my first time working
> with the overlays.
>
> Thanks again.
> Tom
>
> On Friday, January 31, 2020 at 12:46:54 PM UTC-5, rbon wrote:
>>
>> Tom,
>>
>> I have only recently started working with the docker build process, so
>> not an expert.
>> You should be able to see in the build log where gradle is looking for
>> the packages (may need to turn of gradle output). You can then browse those
>> locations to see what is there.
>>
>> If you are intending to pull a completed war into a docker, could you use
>> 6.1.x version?
>> Since it is officially released, the packages should all be there. It may
>> be that some of 6.2.x has not been pushed.
>>
>> Ray
>>
>> On Fri, 2020-01-31 at 07:28 -0800, Tom Healey wrote:
>>
>>
>> Ray,
>> Thanks for the quick response.
>>
>> Some of that follows is a repeat but I am rewriting for clarity, I hope.
>> Sorry.
>>
>> I am working from this project:
>> https://github.com/apereo/cas-overlay-template/
>> <https://github.com/apereo/cas-overlay-template/blob/master/gradle.properties>
>> as I am trying to build a docker image of the CAS war eventually.
>>
>> Running the ./docker-build.sh task successfully builds the war and the
>> docker image but only after I changed the cas.version property to 6.2.0-RC2.
>>
>> Background:
>> When I used what was container build in the gradle.preperties file in the
>> repo ( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed
>> cas.version property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT
>> doesn’t exist in the maven repo, I am assuming.
>>
>> Current problem:
>> I am trying to modify this CAS overlay for my own needs and am trying to
>> build the war without building the docker image to speed up development. It
>> takes 10 mins to build the image on my machine because a fair bit of the
>> time it downloads the gradle version specified in the build event though it
>> exists on my machine already.
>> When I run ./gradlew it fails with this error:
>> could not resolve
>> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.
>>
>> again it doesn’t fail when building under docker.
>>
>>
>>
>> Any thoughts?
>>
>> Tom
>>
>> On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote:
>>
>> Tom,
>>
>> I think if you are running the release candidates, check
>> https://github.com/apereo/cas/blob/master/gradle.properties to see what
>> master is set at.
>> Try 6.2.0-SNAPSHOT
>>
>> Ray
>>
>> On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
>>
>> Hi all,
>> I am trying to modify the overlay from
>>
>> from the CAS overlay directory that i downloaded from  gitbub.
>>
>>
>> I have changed my gradle.properties
>> to *cas.version=6.2.0-RC2*
>>
>> *(I copied it right from the posting. )*
>>
>> and I get:
>>
>>
>> *Could not resolve
>> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.*
>>
>> I am running ./gradlew from the command line.
>>
>> When I run it from the docker-build file it works but I can't use that
>> all the time. I want to configure the CAS war to suit my needs and I think
>> I need to do that with gradlew.
>> I looked through the docker build to see if I could reverse engineer it
>> to get the right things in place so it can find what it needs to run from
>> the command line with ./gradlew only.
>>
>> Thanks,
>> Tom
>>
>> On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko
>> wrote:
>>
>> You might want to run it with —info or —debug flag to see what might be
>> failing, like so:
>>
>> ./gradlew run —info
>>
>> or build and run as two separate steps:
>>
>> ./gradlew clean build
>> java -jar build/libs/cas.war
>>
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: Jérémie Pilette 
>> Date: January 2, 2

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-31 Thread Tom Healey
Thanks Ray!

On Fri, Jan 31, 2020 at 2:41 PM Ray Bon  wrote:

> Tom,
>
> There is David Curry's build log,
> https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html
> .
> And this on the overlay,
> https://apereo.github.io/2018/11/16/cas60-gettingstarted-overlay/
>
> Ray
>
> On Fri, 2020-01-31 at 11:12 -0800, Tom Healey wrote:
>
> Ray,
> Again thanks for the quick response.
> I COULD use 6.1.3. I switched to the 6.1 branch and was able to
> successfully build the war.
> THANKS!
>
> Could you point me to some resources on how to work with the CAS overlay?
> I DOCs aren't as helpful to me as I need and this is my first time working
> with the overlays.
>
> Thanks again.
> Tom
>
> On Friday, January 31, 2020 at 12:46:54 PM UTC-5, rbon wrote:
>
> Tom,
>
> I have only recently started working with the docker build process, so not
> an expert.
> You should be able to see in the build log where gradle is looking for the
> packages (may need to turn of gradle output). You can then browse those
> locations to see what is there.
>
> If you are intending to pull a completed war into a docker, could you use
> 6.1.x version?
> Since it is officially released, the packages should all be there. It may
> be that some of 6.2.x has not been pushed.
>
> Ray
>
> On Fri, 2020-01-31 at 07:28 -0800, Tom Healey wrote:
>
>
> Ray,
> Thanks for the quick response.
>
> Some of that follows is a repeat but I am rewriting for clarity, I hope.
> Sorry.
>
> I am working from this project:
> https://github.com/apereo/cas-overlay-template/
> <https://github.com/apereo/cas-overlay-template/blob/master/gradle.properties>
> as I am trying to build a docker image of the CAS war eventually.
>
> Running the ./docker-build.sh task successfully builds the war and the
> docker image but only after I changed the cas.version property to
> 6.2.0-RC2.
>
> Background:
> When I used what was container build in the gradle.preperties file in the
> repo ( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed
> cas.version property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT
> doesn’t exist in the maven repo, I am assuming.
>
> Current problem:
> I am trying to modify this CAS overlay for my own needs and am trying to
> build the war without building the docker image to speed up development. It
> takes 10 mins to build the image on my machine because a fair bit of the
> time it downloads the gradle version specified in the build event though it
> exists on my machine already.
> When I run ./gradlew it fails with this error:
> could not resolve
> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.
>
> again it doesn’t fail when building under docker.
>
>
>
> Any thoughts?
>
> Tom
>
> On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote:
>
> Tom,
>
> I think if you are running the release candidates, check
> https://github.com/apereo/cas/blob/master/gradle.properties to see what
> master is set at.
> Try 6.2.0-SNAPSHOT
>
> Ray
>
> On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
>
> Hi all,
> I am trying to modify the overlay from
>
> from the CAS overlay directory that i downloaded from  gitbub.
>
>
> I have changed my gradle.properties
> to *cas.version=6.2.0-RC2*
>
> *(I copied it right from the posting. ) *
>
> and I get:
>
>
> *Could not resolve
> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2. *
>
> I am running ./gradlew from the command line.
>
> When I run it from the docker-build file it works but I can't use that all
> the time. I want to configure the CAS war to suit my needs and I think I
> need to do that with gradlew.
> I looked through the docker build to see if I could reverse engineer it to
> get the right things in place so it can find what it needs to run from the
> command line with ./gradlew only.
>
> Thanks,
> Tom
>
> On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote:
>
> You might want to run it with —info or —debug flag to see what might be
> failing, like so:
>
> ./gradlew run —info
>
> or build and run as two separate steps:
>
> ./gradlew clean build
> java -jar build/libs/cas.war
>
> D.
>
>
> From: Jérémie Pilette 
> Reply: Jérémie Pilette 
> Date: January 2, 2020 at 2:47:55 PM
> To: CAS Community 
> Cc: dkopy...@unicon.net 
> Subject:  Re: [cas-user] 6.2.x Gradle Compilation
>
> Hi Dmitriy,
> thank you.
> Now I have another ailed :
>
> > Task :run FAILED
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/hom

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-31 Thread Ray Bon
Tom,

There is David Curry's build log, 
https://dacurry-tns.github.io/deploying-apereo-cas/introduction_overview.html.
And this on the overlay, 
https://apereo.github.io/2018/11/16/cas60-gettingstarted-overlay/

Ray

On Fri, 2020-01-31 at 11:12 -0800, Tom Healey wrote:
Ray,
Again thanks for the quick response.
I COULD use 6.1.3. I switched to the 6.1 branch and was able to successfully 
build the war.
THANKS!

Could you point me to some resources on how to work with the CAS overlay?
I DOCs aren't as helpful to me as I need and this is my first time working with 
the overlays.

Thanks again.
Tom

On Friday, January 31, 2020 at 12:46:54 PM UTC-5, rbon wrote:
Tom,

I have only recently started working with the docker build process, so not an 
expert.
You should be able to see in the build log where gradle is looking for the 
packages (may need to turn of gradle output). You can then browse those 
locations to see what is there.

If you are intending to pull a completed war into a docker, could you use 6.1.x 
version?
Since it is officially released, the packages should all be there. It may be 
that some of 6.2.x has not been pushed.

Ray

On Fri, 2020-01-31 at 07:28 -0800, Tom Healey wrote:

Ray,
Thanks for the quick response.

Some of that follows is a repeat but I am rewriting for clarity, I hope. Sorry.

I am working from this project:
https://github.com/apereo/cas-overlay-template/<https://github.com/apereo/cas-overlay-template/blob/master/gradle.properties>
as I am trying to build a docker image of the CAS war eventually.

Running the ./docker-build.sh task successfully builds the war and the docker 
image but only after I changed the cas.version property to 6.2.0-RC2.

Background:
When I used what was container build in the gradle.preperties file in the repo 
( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed cas.version 
property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT doesn’t exist in 
the maven repo, I am assuming.

Current problem:
I am trying to modify this CAS overlay for my own needs and am trying to build 
the war without building the docker image to speed up development. It takes 10 
mins to build the image on my machine because a fair bit of the time it 
downloads the gradle version specified in the build event though it exists on 
my machine already.
When I run ./gradlew it fails with this error:
could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.

again it doesn’t fail when building under docker.



Any thoughts?

Tom

On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote:
Tom,

I think if you are running the release candidates, check 
https://github.com/apereo/cas/blob/master/gradle.properties to see what master 
is set at.
Try 6.2.0-SNAPSHOT

Ray

On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
Hi all,
I am trying to modify the overlay from

from the CAS overlay directory that i downloaded from  gitbub.


I have changed my gradle.properties
to cas.version=6.2.0-RC2
(I copied it right from the posting. )

and I get:

Could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.

I am running ./gradlew from the command line.

When I run it from the docker-build file it works but I can't use that all the 
time. I want to configure the CAS war to suit my needs and I think I need to do 
that with gradlew.
I looked through the docker build to see if I could reverse engineer it to get 
the right things in place so it can find what it needs to run from the command 
line with ./gradlew only.

Thanks,
Tom

On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote:
You might want to run it with —info or —debug flag to see what might be 
failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.


From: Jérémie Pilette 
Reply: Jérémie Pilette 
Date: January 2, 2020 at 2:47:55 PM
To: CAS Community 
Cc: dkopy...@unicon.net 
Subject:  Re: [cas-user] 6.2.x Gradle Compilation

Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
> non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

Thank you,
Jérémie


Le jeudi 2 janvier 2020 14:24:48 U

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-31 Thread Dmitriy Kopylenko
This might be helpful: 
https://apereo.github.io/2019/01/07/cas61-gettingstarted-overlay/

D.
On Jan 31, 2020, 14:12 -0500, Tom Healey , wrote:
> Ray,
> Again thanks for the quick response.
> I COULD use 6.1.3. I switched to the 6.1 branch and was able to successfully 
> build the war.
> THANKS!
>
> Could you point me to some resources on how to work with the CAS overlay?
> I DOCs aren't as helpful to me as I need and this is my first time working 
> with the overlays.
>
> Thanks again.
> Tom
>
> On Friday, January 31, 2020 at 12:46:54 PM UTC-5, rbon wrote:
> > Tom,
> >
> > I have only recently started working with the docker build process, so not 
> > an expert.
> > You should be able to see in the build log where gradle is looking for the 
> > packages (may need to turn of gradle output). You can then browse those 
> > locations to see what is there.
> >
> > If you are intending to pull a completed war into a docker, could you use 
> > 6.1.x version?
> > Since it is officially released, the packages should all be there. It may 
> > be that some of 6.2.x has not been pushed.
> >
> > Ray
> >
> > On Fri, 2020-01-31 at 07:28 -0800, Tom Healey wrote:
> > >
> > > Ray,
> > > Thanks for the quick response.
> > >
> > > Some of that follows is a repeat but I am rewriting for clarity, I hope. 
> > > Sorry.
> > >
> > > I am working from this project:
> > > https://github.com/apereo/cas-overlay-template/
> > > as I am trying to build a docker image of the CAS war eventually.
> > >
> > > Running the ./docker-build.sh task successfully builds the war and the 
> > > docker image but only after I changed the cas.version property to 
> > > 6.2.0-RC2.
> > >
> > > Background:
> > > When I used what was container build in the gradle.preperties file in the 
> > > repo ( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed 
> > > cas.version property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT 
> > > doesn’t exist in the maven repo, I am assuming.
> > >
> > > Current problem:
> > > I am trying to modify this CAS overlay for my own needs and am trying to 
> > > build the war without building the docker image to speed up development. 
> > > It takes 10 mins to build the image on my machine because a fair bit of 
> > > the time it downloads the gradle version specified in the build event 
> > > though it exists on my machine already.
> > > When I run ./gradlew it fails with this error:
> > > could not resolve 
> > > org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.
> > >
> > > again it doesn’t fail when building under docker.
> > >
> > >
> > >
> > > Any thoughts?
> > >
> > > Tom
> > >
> > > On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote:
> > > > Tom,
> > > >
> > > > I think if you are running the release candidates, check 
> > > > https://github.com/apereo/cas/blob/master/gradle.properties to see what 
> > > > master is set at.
> > > > Try 6.2.0-SNAPSHOT
> > > >
> > > > Ray
> > > >
> > > > On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
> > > > > Hi all,
> > > > > I am trying to modify the overlay from
> > > > >
> > > > > from the CAS overlay directory that i downloaded from  gitbub.
> > > > >
> > > > >
> > > > > I have changed my gradle.properties
> > > > > to cas.version=6.2.0-RC2
> > > > > (I copied it right from the posting. )
> > > > >
> > > > > and I get:
> > > > >
> > > > > Could not resolve 
> > > > > org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.
> > > > >
> > > > > I am running ./gradlew from the command line.
> > > > >
> > > > > When I run it from the docker-build file it works but I can't use 
> > > > > that all the time. I want to configure the CAS war to suit my needs 
> > > > > and I think I need to do that with gradlew.
> > > > > I looked through the docker build to see if I could reverse engineer 
> > > > > it to get the right things in place so it can find what it needs to 
> > > > > run from the command line with ./gradlew only.
> > > > >
> > > 

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-31 Thread Tom Healey
Ray,
Again thanks for the quick response.
I COULD use 6.1.3. I switched to the 6.1 branch and was able to 
successfully build the war.
THANKS!

Could you point me to some resources on how to work with the CAS overlay? 
I DOCs aren't as helpful to me as I need and this is my first time working 
with the overlays.

Thanks again.
Tom

On Friday, January 31, 2020 at 12:46:54 PM UTC-5, rbon wrote:
>
> Tom,
>
> I have only recently started working with the docker build process, so not 
> an expert.
> You should be able to see in the build log where gradle is looking for the 
> packages (may need to turn of gradle output). You can then browse those 
> locations to see what is there.
>
> If you are intending to pull a completed war into a docker, could you use 
> 6.1.x version?
> Since it is officially released, the packages should all be there. It may 
> be that some of 6.2.x has not been pushed.
>
> Ray
>
> On Fri, 2020-01-31 at 07:28 -0800, Tom Healey wrote:
>
>
> Ray,
> Thanks for the quick response.  
>
> Some of that follows is a repeat but I am rewriting for clarity, I hope. 
> Sorry. 
>
> I am working from this project: 
> https://github.com/apereo/cas-overlay-template/ 
> <https://github.com/apereo/cas-overlay-template/blob/master/gradle.properties>
> as I am trying to build a docker image of the CAS war eventually. 
>
> Running the ./docker-build.sh task successfully builds the war and the 
> docker image but only after I changed the cas.version property to 
> 6.2.0-RC2. 
>
> Background: 
> When I used what was container build in the gradle.preperties file in the 
> repo ( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed 
> cas.version property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT 
> doesn’t exist in the maven repo, I am assuming. 
>
> Current problem: 
> I am trying to modify this CAS overlay for my own needs and am trying to 
> build the war without building the docker image to speed up development. It 
> takes 10 mins to build the image on my machine because a fair bit of the 
> time it downloads the gradle version specified in the build event though it 
> exists on my machine already. 
> When I run ./gradlew it fails with this error: 
> could not resolve 
> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.
>
> again it doesn’t fail when building under docker. 
>
>
>
> Any thoughts? 
>
> Tom 
>
> On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote: 
>
> Tom,
>
> I think if you are running the release candidates, check 
> https://github.com/apereo/cas/blob/master/gradle.properties to see what 
> master is set at.
> Try 6.2.0-SNAPSHOT
>
> Ray
>
> On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
>
> Hi all,
> I am trying to modify the overlay from
>
> from the CAS overlay directory that i downloaded from  gitbub.
>
>
> I have changed my gradle.properties
> to *cas.version=6.2.0-RC2*
>
> *(I copied it right from the posting. ) *
>
> and I get:
>
>
> *Could not resolve 
> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2. *
>
> I am running ./gradlew from the command line.
>
> When I run it from the docker-build file it works but I can't use that all 
> the time. I want to configure the CAS war to suit my needs and I think I 
> need to do that with gradlew.
> I looked through the docker build to see if I could reverse engineer it to 
> get the right things in place so it can find what it needs to run from the 
> command line with ./gradlew only.
>
> Thanks,
> Tom
>
> On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote: 
>
> You might want to run it with —info or —debug flag to see what might be 
> failing, like so:
>
> ./gradlew run —info
>
> or build and run as two separate steps:
>
> ./gradlew clean build
> java -jar build/libs/cas.war
>
> D.
>
>
> From: Jérémie Pilette 
> Reply: Jérémie Pilette 
> Date: January 2, 2020 at 2:47:55 PM
> To: CAS Community 
> Cc: dkopy...@unicon.net 
> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>
> Hi Dmitriy,
> thank you.
> Now I have another ailed :
>
> > Task :run FAILED
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>
> * What went wrong:
> Execution failed for task ':run'.
> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished 
> with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-31 Thread Ray Bon
Tom,

I have only recently started working with the docker build process, so not an 
expert.
You should be able to see in the build log where gradle is looking for the 
packages (may need to turn of gradle output). You can then browse those 
locations to see what is there.

If you are intending to pull a completed war into a docker, could you use 6.1.x 
version?
Since it is officially released, the packages should all be there. It may be 
that some of 6.2.x has not been pushed.

Ray

On Fri, 2020-01-31 at 07:28 -0800, Tom Healey wrote:

Ray,
Thanks for the quick response.

Some of that follows is a repeat but I am rewriting for clarity, I hope. Sorry.

I am working from this project:
https://github.com/apereo/cas-overlay-template/<https://github.com/apereo/cas-overlay-template/blob/master/gradle.properties>
as I am trying to build a docker image of the CAS war eventually.

Running the ./docker-build.sh task successfully builds the war and the docker 
image but only after I changed the cas.version property to 6.2.0-RC2.

Background:
When I used what was container build in the gradle.preperties file in the repo 
( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed cas.version 
property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT doesn’t exist in 
the maven repo, I am assuming.

Current problem:
I am trying to modify this CAS overlay for my own needs and am trying to build 
the war without building the docker image to speed up development. It takes 10 
mins to build the image on my machine because a fair bit of the time it 
downloads the gradle version specified in the build event though it exists on 
my machine already.
When I run ./gradlew it fails with this error:
could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.

again it doesn’t fail when building under docker.



Any thoughts?

Tom

On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote:
Tom,

I think if you are running the release candidates, check 
https://github.com/apereo/cas/blob/master/gradle.properties to see what master 
is set at.
Try 6.2.0-SNAPSHOT

Ray

On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
Hi all,
I am trying to modify the overlay from

from the CAS overlay directory that i downloaded from  gitbub.


I have changed my gradle.properties
to cas.version=6.2.0-RC2
(I copied it right from the posting. )

and I get:

Could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.

I am running ./gradlew from the command line.

When I run it from the docker-build file it works but I can't use that all the 
time. I want to configure the CAS war to suit my needs and I think I need to do 
that with gradlew.
I looked through the docker build to see if I could reverse engineer it to get 
the right things in place so it can find what it needs to run from the command 
line with ./gradlew only.

Thanks,
Tom

On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote:
You might want to run it with —info or —debug flag to see what might be 
failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.


From: Jérémie Pilette 
Reply: Jérémie Pilette 
Date: January 2, 2020 at 2:47:55 PM
To: CAS Community 
Cc: dkopy...@unicon.net 
Subject:  Re: [cas-user] 6.2.x Gradle Compilation

Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
> non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

Thank you,
Jérémie


Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit :
Hi there.

Change version of CAS to 6.2 RC2 in gradle.properties like so:

cas.version=6.2.0-RC2

Best,
D.


From: Jérémie Pilette 
Reply: cas-...@apereo.org 
Date: January 2, 2020 at 7:57:00 AM
To: CAS Community 
Subject:  [cas-user] 6.2.x Gradle Compilation

Hi everybody,
I have a problem with my first compilation of cas-overlay-template (6.2.x)

Here this is  my messages :

FAILURE: Build failed with an exception.
A problem occurred evaluating root project 'cas'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not find 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSH

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-31 Thread Tom Healey

Ray,
Thanks for the quick response.  

Some of that follows is a repeat but I am rewriting for clarity, I hope. 
Sorry. 

I am working from this project: 
https://github.com/apereo/cas-overlay-template/ 
<https://github.com/apereo/cas-overlay-template/blob/master/gradle.properties>
as I am trying to build a docker image of the CAS war eventually. 

Running the ./docker-build.sh task successfully builds the war and the 
docker image but only after I changed the cas.version property to 
6.2.0-RC2. 

Background: 
When I used what was container build in the gradle.preperties file in the 
repo ( 6.2.0-SNAPSHOT) it would fail.  It wasn’t until I changed 
cas.version property to 6.2.0-RC2 that it worked because 6.2.0-SNAPSHOT 
doesn’t exist in the maven repo, I am assuming. 

Current problem: 
I am trying to modify this CAS overlay for my own needs and am trying to 
build the war without building the docker image to speed up development. It 
takes 10 mins to build the image on my machine because a fair bit of the 
time it downloads the gradle version specified in the build event though it 
exists on my machine already. 
When I run ./gradlew it fails with this error: 
could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.

again it doesn’t fail when building under docker. 



Any thoughts? 

Tom 

On Wednesday, January 29, 2020 at 7:19:46 PM UTC-5, rbon wrote:
>
> Tom,
>
> I think if you are running the release candidates, check 
> https://github.com/apereo/cas/blob/master/gradle.properties to see what 
> master is set at.
> Try 6.2.0-SNAPSHOT
>
> Ray
>
> On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
>
> Hi all,
> I am trying to modify the overlay from
>
> from the CAS overlay directory that i downloaded from  gitbub.
>
>
> I have changed my gradle.properties
> to *cas.version=6.2.0-RC2*
>
> *(I copied it right from the posting. ) *
>
> and I get:
>
>
> *Could not resolve 
> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2. *
>
> I am running ./gradlew from the command line.
>
> When I run it from the docker-build file it works but I can't use that all 
> the time. I want to configure the CAS war to suit my needs and I think I 
> need to do that with gradlew.
> I looked through the docker build to see if I could reverse engineer it to 
> get the right things in place so it can find what it needs to run from the 
> command line with ./gradlew only.
>
> Thanks,
> Tom
>
> On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote: 
>
> You might want to run it with —info or —debug flag to see what might be 
> failing, like so:
>
> ./gradlew run —info
>
> or build and run as two separate steps:
>
> ./gradlew clean build
> java -jar build/libs/cas.war
>
> D.
>
>
> From: Jérémie Pilette 
> Reply: Jérémie Pilette 
> Date: January 2, 2020 at 2:47:55 PM
> To: CAS Community 
> Cc: dkopy...@unicon.net 
> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>
> Hi Dmitriy,
> thank you.
> Now I have another ailed :
>
> > Task :run FAILED
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>
> * What went wrong:
> Execution failed for task ':run'.
> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished 
> with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it incompatible 
> with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See 
> https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> Thank you,
> Jérémie
>
>
> Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit : 
>
> Hi there.
>
> Change version of CAS to 6.2 RC2 in gradle.properties like so:
>
> *cas.version=6.2.0-RC2*
>
> Best,
> D.
>
>
> From: Jérémie Pilette 
> Reply: cas-...@apereo.org 
> Date: January 2, 2020 at 7:57:00 AM
> To: CAS Community 
> Subject:  [cas-user] 6.2.x Gradle Compilation
>
> Hi everybody,
> I have a problem with my first compilation of cas-overlay-template (6.2.x)
>
> Here this is  my messages :
>
> FAILURE: Build failed with an exception.
> A problem occurred evaluating root project 'cas'.
> > Could not resolve all artifacts for configuration 'classpath'.
>> Could not find 
&g

Re: [cas-user] 6.2.x Gradle Compilation

2020-01-29 Thread Ray Bon
Tom,

I think if you are running the release candidates, check 
https://github.com/apereo/cas/blob/master/gradle.properties to see what master 
is set at.
Try 6.2.0-SNAPSHOT

Ray

On Wed, 2020-01-29 at 13:35 -0800, Tom Healey wrote:
Hi all,
I am trying to modify the overlay from

from the CAS overlay directory that i downloaded from  gitbub.


I have changed my gradle.properties
to cas.version=6.2.0-RC2
(I copied it right from the posting. )

and I get:

Could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.

I am running ./gradlew from the command line.

When I run it from the docker-build file it works but I can't use that all the 
time. I want to configure the CAS war to suit my needs and I think I need to do 
that with gradlew.
I looked through the docker build to see if I could reverse engineer it to get 
the right things in place so it can find what it needs to run from the command 
line with ./gradlew only.

Thanks,
Tom

On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote:
You might want to run it with —info or —debug flag to see what might be 
failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.


From: Jérémie Pilette 
Reply: Jérémie Pilette 
Date: January 2, 2020 at 2:47:55 PM
To: CAS Community 
Cc: dkopy...@unicon.net 
Subject:  Re: [cas-user] 6.2.x Gradle Compilation

Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
> non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

Thank you,
Jérémie


Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit :
Hi there.

Change version of CAS to 6.2 RC2 in gradle.properties like so:

cas.version=6.2.0-RC2

Best,
D.


From: Jérémie Pilette 
Reply: cas-...@apereo.org 
Date: January 2, 2020 at 7:57:00 AM
To: CAS Community 
Subject:  [cas-user] 6.2.x Gradle Compilation

Hi everybody,
I have a problem with my first compilation of cas-overlay-template (6.2.x)

Here this is  my messages :

FAILURE: Build failed with an exception.
A problem occurred evaluating root project 'cas'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not find 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
[...]
Could not find 
org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
 Searched in the following locations:
[...]


Do you have an idea please ?

Jérémie
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org<https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org?utm_medium=email&utm_source=footer>.







This email has been scanned for spam and viruses by Proofpoint Essentials. 
Click 
here<https://us2.proofpointessentials.com/index01.php?mod_id=11&mod_option=logitem&mail_id=1577994474-hk1Nk1kKYSlm&r_address=dkopylenko%40unicon.net&report=1>
 to report this email as spam.

=

--

Ray Bon
Programmer Analyst
Development Services, University Systems
2507218831 | CLE 019 | r...@uvic.ca<mailto:r...@uvic.ca>

I respectfully acknowledge that my place of work is located within the 
ancestral, traditional and unceded territory of the Songhees, Esquimalt and 
WSÁNEĆ Nations.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/ba2e0b088c01cb6efd68b28266d3c2591bf65ad1.camel%40uvic.ca.


Re: [cas-user] 6.2.x Gradle Compilation

2020-01-29 Thread Tom Healey
Hi all,
I am trying to modify the overlay from

from the CAS overlay directory that i downloaded from  gitbub.


I have changed my gradle.properties
to *cas.version=6.2.0-RC2*

*(I copied it right from the posting. )*

and I get:


*Could not resolve 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-RC2.*

I am running ./gradlew from the command line.

When I run it from the docker-build file it works but I can't use that all 
the time. I want to configure the CAS war to suit my needs and I think I 
need to do that with gradlew.
I looked through the docker build to see if I could reverse engineer it to 
get the right things in place so it can find what it needs to run from the 
command line with ./gradlew only.

Thanks,
Tom

On Thursday, January 2, 2020 at 2:59:28 PM UTC-5, Dmitriy Kopylenko wrote:
>
> You might want to run it with —info or —debug flag to see what might be 
> failing, like so:
>
> ./gradlew run —info
>
> or build and run as two separate steps:
>
> ./gradlew clean build
> java -jar build/libs/cas.war
>
> D.
>
>
> From: Jérémie Pilette  
> Reply: Jérémie Pilette  
> Date: January 2, 2020 at 2:47:55 PM
> To: CAS Community  
> Cc: dkopy...@unicon.net   
> Subject:  Re: [cas-user] 6.2.x Gradle Compilation 
>
> Hi Dmitriy,
> thank you.
> Now I have another ailed :
>
> > Task :run FAILED
>
> FAILURE: Build failed with an exception.
>
> * Where:
> Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57
>
> * What went wrong:
> Execution failed for task ':run'.
> > Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished 
> with non-zero exit value 1
>
> * Try:
> Run with --stacktrace option to get the stack trace. Run with --info or 
> --debug option to get more log output. Run with --scan to get full insights.
>
> * Get more help at https://help.gradle.org
>
> Deprecated Gradle features were used in this build, making it incompatible 
> with Gradle 7.0.
> Use '--warning-mode all' to show the individual deprecation warnings.
> See 
> https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings
>
> Thank you,
> Jérémie
>
>
> Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit : 
>>
>> Hi there.
>>
>> Change version of CAS to 6.2 RC2 in gradle.properties like so:
>>
>> *cas.version=6.2.0-RC2*
>>
>> Best,
>> D.
>>
>>
>> From: Jérémie Pilette 
>> Reply: cas-...@apereo.org 
>> Date: January 2, 2020 at 7:57:00 AM
>> To: CAS Community 
>> Subject:  [cas-user] 6.2.x Gradle Compilation
>>
>> Hi everybody,
>> I have a problem with my first compilation of cas-overlay-template (6.2.x)
>>
>> Here this is  my messages :
>>
>> FAILURE: Build failed with an exception.
>> A problem occurred evaluating root project 'cas'.
>> > Could not resolve all artifacts for configuration 'classpath'.
>>> Could not find 
>> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
>> [...]
>> Could not find 
>> org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
>>  Searched in the following locations:
>> [...]
>>
>>
>> Do you have an idea please ?
>>
>> Jérémie
>> --
>> - Website: https://apereo.github.io/cas
>> - Gitter Chatroom: https://gitter.im/apereo/cas
>> - List Guidelines: https://goo.gl/1VRrw7
>> - Contributions: https://goo.gl/mh7qDG
>> ---
>> You received this message because you are subscribed to the Google Groups 
>> "CAS Community" group.
>> To unsubscribe from this group and stop receiving emails from it, send an 
>> email to cas-...@apereo.org.
>> To view this discussion on the web visit 
>> https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org
>>  
>> <https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org?utm_medium=email&utm_source=footer>
>> .
>>
>>
>  
> --
>
> This email has been scanned for spam and viruses by Proofpoint Essentials. 
> Click here 
> <https://us2.proofpointessentials.com/index01.php?mod_id=11&mod_option=logitem&mail_id=1577994474-hk1Nk1kKYSlm&r_address=dkopylenko%40unicon.net&report=1>
>  
> to report this email as spam.
>
> = 
>
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/47959119-ab24-4f80-a565-62127952737e%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-01-02 Thread Dmitriy Kopylenko
You might want to run it with —info or —debug flag to see what might be 
failing, like so:

./gradlew run —info

or build and run as two separate steps:

./gradlew clean build
java -jar build/libs/cas.war

D.


From: Jérémie Pilette 
Reply: Jérémie Pilette 
Date: January 2, 2020 at 2:47:55 PM
To: CAS Community 
Cc: dkopyle...@unicon.net 
Subject:  Re: [cas-user] 6.2.x Gradle Compilation  

Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished with 
> non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug 
option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with 
Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

Thank you,
Jérémie


Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit :
Hi there.

Change version of CAS to 6.2 RC2 in gradle.properties like so:

cas.version=6.2.0-RC2

Best,
D.


From: Jérémie Pilette 
Reply: cas-...@apereo.org 
Date: January 2, 2020 at 7:57:00 AM
To: CAS Community 
Subject:  [cas-user] 6.2.x Gradle Compilation

Hi everybody,
I have a problem with my first compilation of cas-overlay-template (6.2.x)

Here this is  my messages :

FAILURE: Build failed with an exception.
A problem occurred evaluating root project 'cas'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not find 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
[...]
Could not find 
org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
 Searched in the following locations:
[...]


Do you have an idea please ?

Jérémie
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org.

 

This email has been scanned for spam and viruses by Proofpoint Essentials. 
Click here to report this email as spam.


=

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/etPan.5e0e4b9a.2e06f415.6e1d%40unicon.net.


Re: [cas-user] 6.2.x Gradle Compilation

2020-01-02 Thread Jérémie Pilette
Hi Dmitriy,
thank you.
Now I have another ailed :

> Task :run FAILED

FAILURE: Build failed with an exception.

* Where:
Script '/home/USER/bin/cas-overlay-template/gradle/tasks.gradle' line: 57

* What went wrong:
Execution failed for task ':run'.
> Process 'command '/usr/lib/jvm/java-11-openjdk-amd64/bin/java'' finished 
with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or 
--debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible 
with Gradle 7.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See 
https://docs.gradle.org/6.0.1/userguide/command_line_interface.html#sec:command_line_warnings

Thank you,
Jérémie


Le jeudi 2 janvier 2020 14:24:48 UTC+1, Dmitriy Kopylenko a écrit :
>
> Hi there.
>
> Change version of CAS to 6.2 RC2 in gradle.properties like so:
>
> *cas.version=6.2.0-RC2*
>
> Best,
> D.
>
>
> From: Jérémie Pilette  
> Reply: cas-...@apereo.org   
> Date: January 2, 2020 at 7:57:00 AM
> To: CAS Community  
> Subject:  [cas-user] 6.2.x Gradle Compilation 
>
> Hi everybody,
> I have a problem with my first compilation of cas-overlay-template (6.2.x)
>
> Here this is  my messages :
>
> FAILURE: Build failed with an exception.
> A problem occurred evaluating root project 'cas'.
> > Could not resolve all artifacts for configuration 'classpath'.
>> Could not find 
> org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
> [...]
> Could not find 
> org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
>  Searched in the following locations:
> [...]
>
>
> Do you have an idea please ?
>
> Jérémie
> --
> - Website: https://apereo.github.io/cas
> - Gitter Chatroom: https://gitter.im/apereo/cas
> - List Guidelines: https://goo.gl/1VRrw7
> - Contributions: https://goo.gl/mh7qDG
> ---
> You received this message because you are subscribed to the Google Groups 
> "CAS Community" group.
> To unsubscribe from this group and stop receiving emails from it, send an 
> email to cas-...@apereo.org .
> To view this discussion on the web visit 
> https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org
>  
> 
> .
>
>

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/363ec94e-70a1-401d-8ffe-23d56965558b%40apereo.org.


Re: [cas-user] 6.2.x Gradle Compilation

2020-01-02 Thread Dmitriy Kopylenko
Hi there.

Change version of CAS to 6.2 RC2 in gradle.properties like so:

cas.version=6.2.0-RC2

Best,
D.


From: Jérémie Pilette 
Reply: cas-user@apereo.org 
Date: January 2, 2020 at 7:57:00 AM
To: CAS Community 
Subject:  [cas-user] 6.2.x Gradle Compilation  

Hi everybody,
I have a problem with my first compilation of cas-overlay-template (6.2.x)

Here this is  my messages :

FAILURE: Build failed with an exception.
A problem occurred evaluating root project 'cas'.
> Could not resolve all artifacts for configuration 'classpath'.
   > Could not find 
org.apereo.cas:cas-server-core-api-configuration-model:6.2.0-SNAPSHOT.
[...]
Could not find 
org.apereo.cas:cas-server-core-configuration-metadata-repository:6.2.0-SNAPSHOT.
 Searched in the following locations:
[...]


Do you have an idea please ?

Jérémie
--
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
---
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/5f89af02-21ff-4d66-82ca-73474ffb4b52%40apereo.org.

-- 
- Website: https://apereo.github.io/cas
- Gitter Chatroom: https://gitter.im/apereo/cas
- List Guidelines: https://goo.gl/1VRrw7
- Contributions: https://goo.gl/mh7qDG
--- 
You received this message because you are subscribed to the Google Groups "CAS 
Community" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to cas-user+unsubscr...@apereo.org.
To view this discussion on the web visit 
https://groups.google.com/a/apereo.org/d/msgid/cas-user/etPan.5e0def1a.67e33a65.3c1%40unicon.net.