[jbosstools-issues] [JBoss JIRA] (JBIDE-11374) BUILD USABILITY BUG: build should assume target platform is in build/target-platform/REPO

[Nick Boldt (JIRA)]

     [ https://issues.jboss.org/browse/JBIDE-11374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Nick Boldt updated JBIDE-11374:
-------------------------------

    Attachment: JBIDE11374.patch.txt


New approach. Use a path under ~/.m2 which maps directly to the name of the latest target platform. Instead of using 3.3.0.Beta3, use 3.3.indigo.SR2, since that TP will be used for Beta1, Beta2, Beta3, and beyond.

Patch: [^JBIDE11374.patch.txt]
                
> BUILD USABILITY BUG:  build should assume target platform is in build/target-platform/REPO
> ------------------------------------------------------------------------------------------
>
>                 Key: JBIDE-11374
>                 URL: https://issues.jboss.org/browse/JBIDE-11374
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: Build/Releng
>    Affects Versions: 3.3.0.Beta3
>            Reporter: Rob Stryker
>            Assignee: Nick Boldt
>             Fix For: 3.3.0.CR1
>
>         Attachments: JBIDE11374.patch.txt
>
>
> If I run the command:  mvn clean install -f ../build/pom-core.xml -Parchives-bootstrap,default,local.site  -Dmaven.test.skip=true
> Then the build system assumes we're running on hudson. The error is:
> {code}
> [ERROR] Internal error: java.lang.RuntimeException: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/. -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: java.lang.RuntimeException: org.eclipse.equinox.p2.core.ProvisionException: No repository found at file:/home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/.
> {code}
> Our documentation, however, insists we put the repo over in build/target-platform/REPO/.  If our documentation wants the target-platform there, then the build system should assume it is there first, rather than assume it is in a hudson-specific location.   Documentation:  https://community.jboss.org/wiki/HowToBuildJBossToolsWithMaven3
> Currently, if no local.site is set, it assumes it will be at file:/home/hudson/static_build_env/jbds/target-platform_3.3.indigo.SR2/e372M-wtp332M.target/,  but really it should assume it is at ../build/target-platform/REPO/

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira