On Fri, Jul 5, 2019 at 9:57 AM Niubbo75 <[email protected]> wrote:

> Hello Nick and thankyou for your reply!
>
>
> vnick wrote
> > A couple of things, here:
> > - It looks like maybe you're trying to build the TOTP module by itself,
> > without building the entire code base?  You probably should do this -
> > maybe
> > make sure you're executing the "mvn package" command at the top-level
> > guacamole-client directory so that everything gets built?
>
> Exactly! I'm trying to compile only TOTP, not the entire code base (FYI I
> still have 1.0.0 working & running but I can't use TOTP.jar I have into
> extensions from compiled code, it don't work, catalina.out tell it can't
> load it saying "maybe wrong API?").
>

If you post the errors you're getting, we might be able to help clear that
up.


> I'll also would like to learn something new from this (never have had
> experience with maven before).
> Plus. I would like to learn how to "fork" a project like guacamole into
> something customized by me (this for learning purpouse), so I would like to
> try to customize TOTP with, i.e., another language or something else
> different from the original one, another plus for me will be try to build
> my
> own maven's repository for my personal projects, but this seems to be OT
>
>
Cool - maybe soon you'll be contributing to the project!! :-D  To fork the
code the easiest way is to make sure you have a Github account, then go to
the Apache Guacamole Client repository, and click the Fork button.  You'll
be guided through the process of forking to a new repo/location.


> So, what can I do to build my "own" TOTP to have it working on my guacamole
> 1.0.0?


You can do this by cloning the git repository - either your fork or the
original one - and then checking out the 1.0.0 tag.  This is the place in
git where 1.0.0 was released, so it should match your running 1.0.0
version.  You can then modify and build the code from there, and should be
able to build just the TOTP module and add that to your existing
installation.

-Nick

Reply via email to