[jbosstools-issues] [JBoss JIRA] (JBIDE-19814) sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)

[Nick Boldt (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-19814?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13089299#comment-13089299 ] 

Nick Boldt commented on JBIDE-19814:
------------------------------------

Reminder to me: need to update JBDS src zip usage instructions [1] because now the sources are in a subfolder. 

[1] https://github.com/jbdevstudio/jbdevstudio-product/blob/master/results/customer-portal/installer-src.manual-instructions.txt 

Thus:

{code}
   # unpack the Red Hat JBoss Developer Studio sources zip
    unzip jboss-devstudio-*-installer-src.zip

    # find the Red Hat JBoss Developer Studio sources
    cd jboss-devstudio-*-installer-src/jbdevstudio-product-*/

    # verify you're using Maven 3.2 or later, with Java 8 or later
    mvn --version
    # eg., Apache Maven 3.2.5
    # Java version: 1.8.0, vendor: Oracle Corporation

    # finally, run a build
    mvn clean install {code}


> sources zip should include local sources too (jbosstools-build-sites or jbdevstudio-product)
> --------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-19814
>                 URL: https://issues.jboss.org/browse/JBIDE-19814
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: build
>    Affects Versions: 4.3.0.Beta1
>            Reporter: Nick Boldt
>            Assignee: Nick Boldt
>             Fix For: 4.3.0.Beta2, 4.3.0.CR1
>
>
> If we change the way the jbosstools-src.zip is produced, such that in addition to upstream projects it ALSO includes the contents of jbosstools-build-sites too, then we can reuse that mojo for the jbdevstudio-product src.zip too, as it will ALSO include the 17 upstream JBT zips (from Github) and also the local JBDS sources. 
> This would mean a large chunk of ant code in jbdevstudio-product/sources/build.xml (if not all of it) could go away. Hooray for 1 solution spanning both projects and product! :D
> Max also suggested that we use a clean copy of the sources just in case the build process makes them dirty:
> {code}
>  git clone --depth=1 . clean-sources-dir && rm -rf clean-sources-dir/.git{code}



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)