[jbosstools-issues] [JBoss JIRA] (JBDS-2548) Add com.google.gdt.eclipse.suite.e42.feature to JBDS target platform to make building simpler

[Nick Boldt (JIRA)]

Nick Boldt created JBDS-2548:
--------------------------------

             Summary: Add com.google.gdt.eclipse.suite.e42.feature to JBDS target platform to make building simpler
                 Key: JBDS-2548
                 URL: https://issues.jboss.org/browse/JBDS-2548
             Project: Developer Studio (JBoss Developer Studio)
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: 3rdPartyCertification, 3rdPartyDependencies, Build, updatesite
    Affects Versions: 7.0.0.Alpha2
            Reporter: Nick Boldt
            Assignee: Nick Boldt
             Fix For: 7.0.0.Beta1


Discovered while documenting limitations & build instructions in JBDS-2456 that if we add com.google.gdt.eclipse.suite.e42.feature to the JBDS "multiple" target platform (or equivalently, if we we build using {code}mvn clean install -Punified.target -Dtpc.group=jbosstools{code}, we no longer need to include this profile to build JBDS:

{code}-Pjboss-requirements-composite-extras-mirror{code}

And can therefore build like this:

{code}mvn clean install -Pmaximum,multiple.target{code}

So, I propose we add *com.google.gdt.eclipse.suite.e42.feature* to the JBDS TP so as to make building easier. The reason it's required is this dependency chain:

*com.jboss.jbds.site.product* depends on *org.jboss.tools.maven.gwt* depends on bundle *com.google.gwt.eclipse.core* which is included in *com.google.gdt.eclipse.suite.e42.feature*.

If you currently try to build using the JBDS TP and omit the *-Pjboss-requirements-composite-extras-mirror* profile flag, you get this:

{code}
[ERROR]   Software being installed: com.jboss.jbds.site.product raw:7.0.0.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):7.0.0-SNAPSHOT
[ERROR]   Missing requirement: org.jboss.tools.maven.gwt 1.5.0.Alpha2-v20130412-2122-B29 requires 'bundle com.google.gwt.eclipse.core 2.5.0' but it could not be found
{code}

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira