You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@guacamole.apache.org by "Nick Couchman (JIRA)" <ji...@apache.org> on 2019/06/30 11:03:00 UTC

[jira] [Commented] (GUACAMOLE-832) build problems

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

Nick Couchman commented on GUACAMOLE-832:
-----------------------------------------

{quote}
I had some problems (pom.xml) to build version 1.1.0:
{quote}

This should probably start on the mailing list, and not, here.  1.1.0 has not been released, yet - it is still in development, and I build from various branches of the git repo that are 1.1.0 or higher and they seem to work fine.  Finally, there are many pom.xml files within the source code, so you need to be more clear about which one you intend on "fixing."

{quote}
one:wrong java-version (1.6) it must be be >1.7
{quote}

Most of the source code is at version 1.8 or higher, but we have intentionally left guacamole-common at 1.6, and have been very deliberate about avoiding changes that would break compatibility in this version.  If there is something recent that has shifted compatibility of that, it would be good to know, but your description here doesn't really give enough information.

{quote}
two or three: javadoc generation
{quote}

Where?

{quote}
two or three: package javax.xml.bind does not exist
{quote}

This is a known issue with moving to Java 1.8 and higher, and has already been addressed.

{quote}
should I check in my changes? How should I became access for your git?
{quote}

No, this is not how it works.  Please read the contribution guidelines for the project: http://guacamole.apache.org/open-source/

Your process should be:
* Fork the github project
* Create a development branch within your fork of the project
* Commit changes to your development branch, and tag them with the JIRA issue number (GUACAMOLE-832:)
* Create a pull request against the apache/guacamole-client repo.  Your changes will be reviewed and, once one or more of the project committers are happy with them we will push them.

> build problems 
> ---------------
>
>                 Key: GUACAMOLE-832
>                 URL: https://issues.apache.org/jira/browse/GUACAMOLE-832
>             Project: Guacamole
>          Issue Type: Improvement
>          Components: guacamole
>            Reporter: Chris
>            Priority: Major
>             Fix For: 1.1.0
>
>
> I had some problems (pom.xml) to build version 1.1.0:
>  * one:wrong java-version (1.6) it must be be >1.7
>  * jtwo or three: avadoc generation
>  * two or three: package javax.xml.bind does not exist
> should I check in my changes? How should I became access for your git?
> thanks
> chris



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)