[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
by Daniel Azarov (JIRA)
[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ]
Daniel Azarov reassigned JBDS-2260:
-----------------------------------
Assignee: Daniel Azarov (was: Denis Golovin)
> Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2260
> URL: https://issues.jboss.org/browse/JBDS-2260
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 5.0.0.GA
> Reporter: Isaac Rooskov
> Assignee: Daniel Azarov
> Priority: Blocker
> Labels: respin-b
> Fix For: 7.0.0.Alpha1
>
> Attachments: JavaVersionReader.java.patch
>
>
> *From customer in Bugzilla*
> Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793
> Description of issue from customer:
> Description of problem:
> Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4
> Version-Release number of selected component (if applicable):
> JBOSS Developer Studio 5.0.0.GA
> How reproducible:
> Start installation using
> java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar
> Actual results:
> Installation is not passing at step 7 of 9, progress 1 of 4.
> Expected results:
> Additional info:
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-13381) ESB Editor removes "http-client-property" property (JBDS-2446)
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13381?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-13381:
-------------------------------------------
Perfect. Thanks Slava. Appreciate the help!!
> ESB Editor removes "http-client-property" property (JBDS-2446)
> --------------------------------------------------------------
>
> Key: JBIDE-13381
> URL: https://issues.jboss.org/browse/JBIDE-13381
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb
> Affects Versions: 3.3.0.Final-SOA
> Reporter: Brian Fitzpatrick
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Fix For: 3.3.x, 4.0.x
>
> Attachments: JBIDE-13381-3.3.x.patch, jbide-13381.patch
>
>
> When editing an ESB file (jboss-esb.xml), we have two ways which are using the native XML editor or the visual way.
> When we want to use the property X. We created our service and our SOAPClient using the visual editor, then we have to add the "http-client-property" manually
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername">
> <http-client-property name="file" value="httpclient.properties" />
> </property>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> Notice the "http-client-property" in the action property element. The problem is that when using visual editor of this file and adding something new or editing existing thing, the code related to this property is deleted. In the example above, I have the following result, showing what the editor removed: (in this case I just changed the service name from service-test to service-test-edited)
> <?xml version="1.0"?>
> <jbossesb parameterReloadSecs="5"
> xmlns="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml..."
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:schemaLocation="http://anonsvn.labs.jboss.com/labs/jbossesb/trunk/product/etc/schemas/xml... http://anonsvn.jboss.org/repos/labs/labs/jbossesb/trunk/product/etc/schem...">
> <services>
> <service category="c1" description="d1" name="s1-edited">
> <actions>
> <action class="org.jboss.soa.esb.actions.soap.SOAPClient" name="client">
> <property name="wsdl" value="someWsdl"/>
> <property name="SOAPAction" value="noAction"/>
> <property name="endpointUrl" value="http://host/servername"/>
> </action>
> </actions>
> </service>
> </services>
> </jbossesb>
> One test we have done is change the XSD used by the JBDS(1.3.1 to the one used in quickstars (1.0.1). The http-client-property worked fine, but other things stopped working. So we need to know what's wrong with the schema and what should make it works fine.
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-13383) Support running on Eclipse Kepler (4.3) platform
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13383?page=com.atlassian.jira.plugi... ]
Denis Golovin edited comment on JBIDE-13383 at 1/24/13 2:18 PM:
----------------------------------------------------------------
h3. How that was done
# Local maven build
# parent/pom.xml and tycho-plugins are build locally and installed into local repo
# Aggregation pom used from my repo on [github|https://github.com/dgolovin/jbosstools-fork-submodules/blob/master...]
# Modified parent/pom.xml without profiles and with just one repository http://download.jboss.org/jbosstools/updates/kepler/M4/REPO to be sure nothing else getting in
# -DskipTests falg added to compile only without running tests
h3. Results
Full reactor summary is in attached files, below is only failures and skipped features with my comments after # char.
{code}# base site build error. It is not easy to guess by name but the errors unveil it in the end
[INFO] site .............................................. FAILURE [11.469s]
# Dali cahnges with public and private API's
[INFO] org.hibernate.eclipse.console ..................... FAILURE [1.001s]
# Bellow plugins are skipped because of dependencies to hibernate plugins
[INFO] org.jboss.tools.birt.oda.ui ....................... SKIPPED
[INFO] org.jboss.tools.birt.feature ...................... SKIPPED
[INFO] birt.site ......................................... SKIPPED
[INFO] org.jboss.tools.seam.ui ........................... SKIPPED
[INFO] org.jboss.tools.maven.seam ........................ SKIPPED
[INFO] org.jboss.tools.maven.seam.feature ................ SKIPPED
[INFO] org.jboss.tools.maven.hibernate ................... SKIPPED
[INFO] org.jboss.tools.maven.hibernate.feature ........... SKIPPED
# See compilation problems in the end
[INFO] org.jboss.tools.maven.jpa ......................... FAILURE [0.298s]
#skipped because compilation problems in dependecies
[INFO] org.jboss.tools.maven.configurators.tests ......... SKIPPED
[INFO] org.jboss.tools.maven.test.feature ................ SKIPPED
[INFO] org.jboss.tools.maven.jpa.feature ................. SKIPPED
[INFO] org.jboss.tools.project.examples.test ............. SKIPPED
[INFO] org.jboss.tools.project.examples.test.feature ..... SKIPPED
[INFO] org.hibernate.eclipse.jdt.apt.ui .................. SKIPPED
[INFO] org.hibernate.eclipse.jdt.ui ...................... SKIPPED
[INFO] org.hibernate.eclipse.mapper ...................... SKIPPED
# Skipped by maven but both jpt plugins below have compilation problems related to changes in privat/public API in Daly
[INFO] org.jboss.tools.hibernate.jpt.core ................ SKIPPED
[INFO] org.jboss.tools.hibernate.jpt.ui .................. SKIPPED
# Skipped because of compilation problems in dependencies
[INFO] org.jboss.tools.hibernate.ui ...................... SKIPPED
[INFO] org.jboss.tools.hibernate3_5 ...................... SKIPPED
[INFO] org.jboss.tools.hibernate3_6 ...................... SKIPPED
[INFO] org.jboss.tools.hibernate4_0 ...................... SKIPPED
[INFO] org.hibernate.eclipse.feature ..................... SKIPPED
[INFO] org.jboss.tools.seam.feature ...................... SKIPPED
[INFO] org.jboss.tools.runtime.seam.detector ............. SKIPPED
[INFO] org.jboss.tools.runtime.seam.detector.feature ..... SKIPPED
[INFO] org.jboss.tools.community.central.feature ......... SKIPPED
[INFO] central.maven.examples.site ....................... SKIPPED
[INFO] org.hibernate.eclipse.console.test ................ SKIPPED
[INFO] org.hibernate.eclipse.jdt.ui.test ................. SKIPPED
[INFO] org.jboss.tools.hibernate.ui.test ................. SKIPPED
[INFO] org.hibernate.eclipse.test.feature ................ SKIPPED
[INFO] org.jboss.tools.hibernate.jpt.core.test ........... SKIPPED
[INFO] hibernatetools.site ............................... SKIPPED
[INFO] org.jboss.tools.seam.base.test .................... SKIPPED
[INFO] org.jboss.tools.seam.core.test .................... SKIPPED
[INFO] org.jboss.tools.seam.ui.test ...................... SKIPPED
[INFO] org.jboss.tools.seam121EAP.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam121EAP.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam201GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam201GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam202SP1.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam202SP1.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam203CR1.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam203CR1.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam211GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam211GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam212GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam212GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam220CR1.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam220CR1.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam220GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam220GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam221GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam221GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam230.core.test ................. SKIPPED
[INFO] org.jboss.tools.seam230.ui.test ................... SKIPPED
[INFO] org.jboss.tools.seamfp.core.test .................. SKIPPED
[INFO] org.jboss.tools.seamfp.ui.test .................... SKIPPED
[INFO] org.jboss.tools.runtime.seam.detector.test ........ SKIPPED
[INFO] org.jboss.tools.seam.test.feature ................. SKIPPED
[INFO] javaee.site ....................................... SKIPPED
[INFO] org.jboss.tools.portlet.feature ................... SKIPPED
[INFO] portlet.site ...................................... SKIPPED
# the same error as in base component update site
[INFO] server.site ....................................... FAILURE [10.652s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38:06.099s
[INFO] Finished at: Wed Jan 16 17:56:43 PST 2013
[INFO] Final Memory: 1078M/3058M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade (generate-facade) on project site: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade: org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo$2
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/jboss/tools/tycho-plugins/repository-utils/0.0.1-SNAPSHOT/repository-utils-0.0.1-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[2] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[3] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[4] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/eclipse/tycho/tycho-packaging-plugin/0.15.0/tycho-packaging-plugin-0.15.0.jar
[ERROR] urls[5] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[6] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[8] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[9] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[10] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar
[ERROR] urls[11] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-archiver/1.2/plexus-archiver-1.2.jar
[ERROR] urls[12] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-io/1.0.1/plexus-io-1.0.1.jar
[ERROR] urls[13] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon/8.7/saxon-8.7.jar
[ERROR] urls[14] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:base:4.0.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo$2
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.hibernate.eclipse.console: Compilation failure: Compilation failure:
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[26,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[27,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[446,0]
[ERROR] if (!JpaFacet.isInstalled(findJavaProject.getProject())) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[450,0]
[ERROR] String projectCPName = JptJpaCorePlugin.getConnectionProfileName(findJavaProject.getProject());
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[20,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[21,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[146,0]
[ERROR] if (!JpaFacet.isInstalled(project)) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[149,0]
[ERROR] String projectCPName = JptJpaCorePlugin.getConnectionProfileName(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[228,0]
[ERROR] if (!JpaFacet.isInstalled(project)) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[231,0]
[ERROR] String defCatalog = JptJpaCorePlugin.getUserOverrideDefaultCatalog(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[232,0]
[ERROR] String defSchema = JptJpaCorePlugin.getUserOverrideDefaultSchema(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[46,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[49,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[289,0]
[ERROR] if (!JpaFacet.isInstalled(project)) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[292,0]
[ERROR] String jpaPlatformId = JptJpaCorePlugin.getJpaPlatformId(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] 15 problems (15 errors)
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.maven.jpa: Compilation failure: Compilation failure:
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[21,0]
[ERROR] import org.eclipse.jpt.common.core.JptCommonCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.common.core.JptCommonCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[23,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[26,0]
[ERROR] import org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.resource.xml cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[55,0]
[ERROR] public static XmlPersistenceUnit getFirstXmlPersistenceUnit(JpaXmlResource persistenceXml) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[69,0]
[ERROR] public static IProjectFacetVersion getVersion(JpaXmlResource persistenceXml) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[75,0]
[ERROR] return JpaFacet.FACET.getDefaultVersion();
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[77,0]
[ERROR] return JpaFacet.FACET.getVersion(version);
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[84,0]
[ERROR] getResourceLocator = JptCommonCorePlugin.class.getMethod("getResourceLocator", IProject.class);
[ERROR] ^^^^^^^^^^^^^^^^^^^
[ERROR] JptCommonCorePlugin cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[28,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[29,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[34,0]
[ERROR] import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[36,0]
[ERROR] import org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.resource.xml cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[112,0]
[ERROR] JpaXmlResource jpaXmlResource = provider.getXmlResource();
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[116,0]
[ERROR] JpaPlatformDescription platform = getPlatform(jpaXmlResource, version);
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[129,0]
[ERROR] private JpaPlatformDescription getPlatform(JpaXmlResource persistenceXml, IProjectFacetVersion facetVersion) {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[129,0]
[ERROR] private JpaPlatformDescription getPlatform(JpaXmlResource persistenceXml, IProjectFacetVersion facetVersion) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[137,0]
[ERROR] for (JpaPlatformDescription platform : JptJpaCorePlugin.getJpaPlatformManager().getJpaPlatforms()) {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[137,0]
[ERROR] for (JpaPlatformDescription platform : JptJpaCorePlugin.getJpaPlatformManager().getJpaPlatforms()) {
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[149,0]
[ERROR] JpaPlatformDescription platform) {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[171,0]
[ERROR] && !JpaFacet.isInstalled(project)
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] 20 problems (20 errors)
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade (generate-facade) on project server.site: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade: org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo$2
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/jboss/tools/tycho-plugins/repository-utils/0.0.1-SNAPSHOT/repository-utils-0.0.1-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[2] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[3] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[4] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/eclipse/tycho/tycho-packaging-plugin/0.15.0/tycho-packaging-plugin-0.15.0.jar
[ERROR] urls[5] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[6] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[8] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[9] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[10] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar
[ERROR] urls[11] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-archiver/1.2/plexus-archiver-1.2.jar
[ERROR] urls[12] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-io/1.0.1/plexus-io-1.0.1.jar
[ERROR] urls[13] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon/8.7/saxon-8.7.jar
[ERROR] urls[14] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:base:4.0.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo$2
[ERROR] -> [Help 1]
[ERROR]{code}
h3. Problems to fix:
# compilation problems in hibernate and maven
# rename base component site to be able identify module in reactor summary
# base update site buile error (see JBIDE-13417)
# xulrunner has reference to parent pom as ../build/parent/pom.xml
# webservices has reference to parent pom as ../build/parent/pom.xml
# add build folder to hibernate module .gitignore (need to run git clean -d -f to remove untracked build folders)
was (Author: dgolovin):
h3. How that was done
# Local maven build
# parent/pom.xml and tycho-plugins are build locally and installed into local repo
# Aggregation pom used from my repo on [github|https://github.com/dgolovin/jbosstools-fork-submodules/blob/master...]
# Modified parent/pom.xml without profiles and with just one repository http://download.jboss.org/jbosstools/updates/kepler/M4/REPO to be sure nothing else getting in
# -DskipTests falg added to compile only without running tests
h3. Results
Full reactor summary is in attached files, below is only failures and skipped features with my comments after # char.
{code}# base site build error. It is not easy to guess by name but the errors unveil it in the end
[INFO] site .............................................. FAILURE [11.469s]
# Dali cahnges with public and private API's
[INFO] org.hibernate.eclipse.console ..................... FAILURE [1.001s]
# Bellow plugins are skipped because of dependencies to hibernate plugins
[INFO] org.jboss.tools.birt.oda.ui ....................... SKIPPED
[INFO] org.jboss.tools.birt.feature ...................... SKIPPED
[INFO] birt.site ......................................... SKIPPED
[INFO] org.jboss.tools.seam.ui ........................... SKIPPED
[INFO] org.jboss.tools.maven.seam ........................ SKIPPED
[INFO] org.jboss.tools.maven.seam.feature ................ SKIPPED
[INFO] org.jboss.tools.maven.hibernate ................... SKIPPED
[INFO] org.jboss.tools.maven.hibernate.feature ........... SKIPPED
# See compilation problems in the end
[INFO] org.jboss.tools.maven.jpa ......................... FAILURE [0.298s]
#skipped because compilation problems in dependecies
[INFO] org.jboss.tools.maven.configurators.tests ......... SKIPPED
[INFO] org.jboss.tools.maven.test.feature ................ SKIPPED
[INFO] org.jboss.tools.maven.jpa.feature ................. SKIPPED
[INFO] org.jboss.tools.project.examples.test ............. SKIPPED
[INFO] org.jboss.tools.project.examples.test.feature ..... SKIPPED
[INFO] org.hibernate.eclipse.jdt.apt.ui .................. SKIPPED
[INFO] org.hibernate.eclipse.jdt.ui ...................... SKIPPED
[INFO] org.hibernate.eclipse.mapper ...................... SKIPPED
# Skipped by maven but both jpt plugins below have compilation problems related to changes in privat/public API in Daly
[INFO] org.jboss.tools.hibernate.jpt.core ................ SKIPPED
[INFO] org.jboss.tools.hibernate.jpt.ui .................. SKIPPED
# Skipped because of compilation problems in dependencies
[INFO] org.jboss.tools.hibernate.ui ...................... SKIPPED
[INFO] org.jboss.tools.hibernate3_5 ...................... SKIPPED
[INFO] org.jboss.tools.hibernate3_6 ...................... SKIPPED
[INFO] org.jboss.tools.hibernate4_0 ...................... SKIPPED
[INFO] org.hibernate.eclipse.feature ..................... SKIPPED
[INFO] org.jboss.tools.seam.feature ...................... SKIPPED
[INFO] org.jboss.tools.runtime.seam.detector ............. SKIPPED
[INFO] org.jboss.tools.runtime.seam.detector.feature ..... SKIPPED
[INFO] org.jboss.tools.community.central.feature ......... SKIPPED
[INFO] central.maven.examples.site ....................... SKIPPED
[INFO] org.hibernate.eclipse.console.test ................ SKIPPED
[INFO] org.hibernate.eclipse.jdt.ui.test ................. SKIPPED
[INFO] org.jboss.tools.hibernate.ui.test ................. SKIPPED
[INFO] org.hibernate.eclipse.test.feature ................ SKIPPED
[INFO] org.jboss.tools.hibernate.jpt.core.test ........... SKIPPED
[INFO] hibernatetools.site ............................... SKIPPED
[INFO] org.jboss.tools.seam.base.test .................... SKIPPED
[INFO] org.jboss.tools.seam.core.test .................... SKIPPED
[INFO] org.jboss.tools.seam.ui.test ...................... SKIPPED
[INFO] org.jboss.tools.seam121EAP.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam121EAP.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam201GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam201GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam202SP1.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam202SP1.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam203CR1.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam203CR1.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam211GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam211GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam212GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam212GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam220CR1.core.test .............. SKIPPED
[INFO] org.jboss.tools.seam220CR1.ui.test ................ SKIPPED
[INFO] org.jboss.tools.seam220GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam220GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam221GA.core.test ............... SKIPPED
[INFO] org.jboss.tools.seam221GA.ui.test ................. SKIPPED
[INFO] org.jboss.tools.seam230.core.test ................. SKIPPED
[INFO] org.jboss.tools.seam230.ui.test ................... SKIPPED
[INFO] org.jboss.tools.seamfp.core.test .................. SKIPPED
[INFO] org.jboss.tools.seamfp.ui.test .................... SKIPPED
[INFO] org.jboss.tools.runtime.seam.detector.test ........ SKIPPED
[INFO] org.jboss.tools.seam.test.feature ................. SKIPPED
[INFO] javaee.site ....................................... SKIPPED
[INFO] org.jboss.tools.portlet.feature ................... SKIPPED
[INFO] portlet.site ...................................... SKIPPED
# the same error as in base component update site
[INFO] server.site ....................................... FAILURE [10.652s]
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 38:06.099s
[INFO] Finished at: Wed Jan 16 17:56:43 PST 2013
[INFO] Final Memory: 1078M/3058M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade (generate-facade) on project site: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade: org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo$2
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/jboss/tools/tycho-plugins/repository-utils/0.0.1-SNAPSHOT/repository-utils-0.0.1-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[2] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[3] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[4] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/eclipse/tycho/tycho-packaging-plugin/0.15.0/tycho-packaging-plugin-0.15.0.jar
[ERROR] urls[5] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[6] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[8] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[9] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[10] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar
[ERROR] urls[11] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-archiver/1.2/plexus-archiver-1.2.jar
[ERROR] urls[12] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-io/1.0.1/plexus-io-1.0.1.jar
[ERROR] urls[13] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon/8.7/saxon-8.7.jar
[ERROR] urls[14] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:base:4.0.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo$2
[ERROR] -> [Help 1]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.hibernate.eclipse.console: Compilation failure: Compilation failure:
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[26,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[27,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[446,0]
[ERROR] if (!JpaFacet.isInstalled(findJavaProject.getProject())) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/launch/ConsoleConfigurationMainTab.java:[450,0]
[ERROR] String projectCPName = JptJpaCorePlugin.getConnectionProfileName(findJavaProject.getProject());
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[20,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[21,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[146,0]
[ERROR] if (!JpaFacet.isInstalled(project)) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[149,0]
[ERROR] String projectCPName = JptJpaCorePlugin.getConnectionProfileName(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[228,0]
[ERROR] if (!JpaFacet.isInstalled(project)) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[231,0]
[ERROR] String defCatalog = JptJpaCorePlugin.getUserOverrideDefaultCatalog(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/EclipseLaunchConsoleConfigurationPreferences.java:[232,0]
[ERROR] String defSchema = JptJpaCorePlugin.getUserOverrideDefaultSchema(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[46,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[49,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[289,0]
[ERROR] if (!JpaFacet.isInstalled(project)) {
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-hibernate/plugins/org.hibernate.eclipse.console/src/org/hibernate/eclipse/console/properties/HibernatePropertyPage.java:[292,0]
[ERROR] String jpaPlatformId = JptJpaCorePlugin.getJpaPlatformId(project);
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] 15 problems (15 errors)
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.maven.jpa: Compilation failure: Compilation failure:
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[21,0]
[ERROR] import org.eclipse.jpt.common.core.JptCommonCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.common.core.JptCommonCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[23,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[26,0]
[ERROR] import org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.resource.xml cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[55,0]
[ERROR] public static XmlPersistenceUnit getFirstXmlPersistenceUnit(JpaXmlResource persistenceXml) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[69,0]
[ERROR] public static IProjectFacetVersion getVersion(JpaXmlResource persistenceXml) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[75,0]
[ERROR] return JpaFacet.FACET.getDefaultVersion();
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[77,0]
[ERROR] return JpaFacet.FACET.getVersion(version);
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JptUtils.java:[84,0]
[ERROR] getResourceLocator = JptCommonCorePlugin.class.getMethod("getResourceLocator", IProject.class);
[ERROR] ^^^^^^^^^^^^^^^^^^^
[ERROR] JptCommonCorePlugin cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[28,0]
[ERROR] import org.eclipse.jpt.jpa.core.JpaFacet;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JpaFacet cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[29,0]
[ERROR] import org.eclipse.jpt.jpa.core.JptJpaCorePlugin;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[34,0]
[ERROR] import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.platform.JpaPlatformDescription cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[36,0]
[ERROR] import org.eclipse.jpt.jpa.core.resource.xml.JpaXmlResource;
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
[ERROR] The import org.eclipse.jpt.jpa.core.resource.xml cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[112,0]
[ERROR] JpaXmlResource jpaXmlResource = provider.getXmlResource();
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[116,0]
[ERROR] JpaPlatformDescription platform = getPlatform(jpaXmlResource, version);
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[129,0]
[ERROR] private JpaPlatformDescription getPlatform(JpaXmlResource persistenceXml, IProjectFacetVersion facetVersion) {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[129,0]
[ERROR] private JpaPlatformDescription getPlatform(JpaXmlResource persistenceXml, IProjectFacetVersion facetVersion) {
[ERROR] ^^^^^^^^^^^^^^
[ERROR] JpaXmlResource cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[137,0]
[ERROR] for (JpaPlatformDescription platform : JptJpaCorePlugin.getJpaPlatformManager().getJpaPlatforms()) {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[137,0]
[ERROR] for (JpaPlatformDescription platform : JptJpaCorePlugin.getJpaPlatformManager().getJpaPlatforms()) {
[ERROR] ^^^^^^^^^^^^^^^^
[ERROR] JptJpaCorePlugin cannot be resolved
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[149,0]
[ERROR] JpaPlatformDescription platform) {
[ERROR] ^^^^^^^^^^^^^^^^^^^^^^
[ERROR] JpaPlatformDescription cannot be resolved to a type
[ERROR] /home/eskimo/Projects/jbds/jbosstools-fork-submodules/jbosstools-central/maven/plugins/org.jboss.tools.maven.jpa/src/org/jboss/tools/maven/jpa/configurators/JpaProjectConfigurator.java:[171,0]
[ERROR] && !JpaFacet.isInstalled(project)
[ERROR] ^^^^^^^^
[ERROR] JpaFacet cannot be resolved
[ERROR] 20 problems (20 errors)
[ERROR] -> [Help 2]
[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade (generate-facade) on project server.site: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade: org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo$2
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/jboss/tools/tycho-plugins/repository-utils/0.0.1-SNAPSHOT/repository-utils-0.0.1-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[2] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[3] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[4] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/eclipse/tycho/tycho-packaging-plugin/0.15.0/tycho-packaging-plugin-0.15.0.jar
[ERROR] urls[5] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[6] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[8] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[9] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[10] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar
[ERROR] urls[11] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-archiver/1.2/plexus-archiver-1.2.jar
[ERROR] urls[12] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-io/1.0.1/plexus-io-1.0.1.jar
[ERROR] urls[13] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon/8.7/saxon-8.7.jar
[ERROR] urls[14] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:base:4.0.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo$2
[ERROR] -> [Help 1]
[ERROR]{code}
h3. Problems to fix:
# compilation problems in hibernate and maven
# rename base component site to be able identify module in reactor summary
# xulrunner has reference to parent pom as ../build/parent/pom.xml
# webservices has reference to parent pom as ../build/parent/pom.xml
# add build folder to hibernate module .gitignore (need to run git clean -d -f to remove untracked build folders)
> Support running on Eclipse Kepler (4.3) platform
> ------------------------------------------------
>
> Key: JBIDE-13383
> URL: https://issues.jboss.org/browse/JBIDE-13383
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: Build/Releng, target-platform, updatesite
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Reporter: Max Rydahl Andersen
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
> Attachments: full-reactor-summary-with-compilation-errors.txt
>
>
> Kepler is coming and it have many improvements performance wise over Juno and is the only version certified to run on Windows 8 afaics. It is also the first version where WTP static web project becomes more usable. and of course the general notion that Kepler is the only version we can actually get fixes into.
> Migration guide for Eclipse Platform (currently empty - I've posted question on http://dev.eclipse.org/mhonarc/lists/eclipse-dev/ to check if better new doc)
> http://htmlpreview.github.com/?https://github.com/eclipse/eclipse.platfor...
> Migration tips for WTP (this time there are *Actual* changes!)
> http://wiki.eclipse.org/New_Help_for_Old_Friends_VIII
> Last years migration: JBIDE-11549 (Juno), JBIDE-8624 (Indigo).
> Please link related Kepler runtime/build issues to this issue.
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-13417) Maven plugin org.jboss.tools.tycho-plugins:repository-utils fails to update p2repository archive in full jbosstools build
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-13417:
-------------------------------------
Summary: Maven plugin org.jboss.tools.tycho-plugins:repository-utils fails to update p2repository archive in full jbosstools build
Key: JBIDE-13417
URL: https://issues.jboss.org/browse/JBIDE-13417
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Reporter: Denis Golovin
Assignee: Mickael Istria
Noticed that base/site build fails with error during the full jbosstools build with error below, but it is fine for component build. The problem is that jbosstools-maven-plugins module is not using jbosstools/parent and thus using tycho version 0.15.0 which is defined in jbosstools-maven-plugins/pom.xml After setting it to the same version as in jbosstools/parent/pom.xml problem is gone.
{code}[ERROR] Failed to execute goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade (generate-facade) on project server.site: Execution generate-facade of goal org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade failed: A required class was missing while executing org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT:generate-repository-facade: org/jboss/tools/tycho/sitegenerator/GenerateRepositoryFacadeMojo$2
[ERROR] -----------------------------------------------------
[ERROR] realm = plugin>org.jboss.tools.tycho-plugins:repository-utils:0.0.1-SNAPSHOT
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/jboss/tools/tycho-plugins/repository-utils/0.0.1-SNAPSHOT/repository-utils-0.0.1-SNAPSHOT.jar
[ERROR] urls[1] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-component-annotations/1.5.5/plexus-component-annotations-1.5.5.jar
[ERROR] urls[2] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[3] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[4] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/eclipse/tycho/tycho-packaging-plugin/0.15.0/tycho-packaging-plugin-0.15.0.jar
[ERROR] urls[5] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/aether/aether-util/1.7/aether-util-1.7.jar
[ERROR] urls[6] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-interpolation/1.14/plexus-interpolation-1.14.jar
[ERROR] urls[7] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-sec-dispatcher/1.3/plexus-sec-dispatcher-1.3.jar
[ERROR] urls[8] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/sonatype/plexus/plexus-cipher/1.4/plexus-cipher-1.4.jar
[ERROR] urls[9] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-utils/2.0.4/plexus-utils-2.0.4.jar
[ERROR] urls[10] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/apache/maven/maven-archiver/2.4/maven-archiver-2.4.jar
[ERROR] urls[11] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-archiver/1.2/plexus-archiver-1.2.jar
[ERROR] urls[12] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/org/codehaus/plexus/plexus-io/1.0.1/plexus-io-1.0.1.jar
[ERROR] urls[13] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon/8.7/saxon-8.7.jar
[ERROR] urls[14] = file:/home/eskimo/Projects/jbds/jbosstools-fork-submodules/../.m2/jbosstools-fork-submodules-maximum1/master/net/sf/saxon/saxon-dom/8.7/saxon-dom-8.7.jar
[ERROR] Number of foreign imports: 1
[ERROR] import: Entry[import from realm ClassRealm[project>org.jboss.tools:base:4.0.0-SNAPSHOT, parent: ClassRealm[maven.api, parent: null]]]
[ERROR]
[ERROR] -----------------------------------------------------: org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo$2
{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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBDS-2424) Still seeing screen corruption after an initial install
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBDS-2424?page=com.atlassian.jira.plugin.... ]
Snjezana Peco reassigned JBDS-2424:
-----------------------------------
Assignee: Len DiMaggio (was: Snjezana Peco)
> Still seeing screen corruption after an initial install
> -------------------------------------------------------
>
> Key: JBDS-2424
> URL: https://issues.jboss.org/browse/JBDS-2424
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central
> Affects Versions: 6.0.0.CR1
> Environment: Version: 6.0.0.CR1
> Build id: CR1-v20121204-0201-B166
> Build date: 20121204-0201
> Reporter: Len DiMaggio
> Assignee: Len DiMaggio
> Fix For: LATER
>
> Attachments: Screenshot-4.png, Screenshot-5.png
>
>
> See attached screen shot - this is seen on the initial startup after install.
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-12175) Automatic namespace completion in Facelets files
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12175?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-12175:
-----------------------------------------
JUnit Test is added due to verify the issue:
tests/org.jboss.tools.jst.jsp.test/src/org/jboss/tools/jst/jsp/test/ca/JstCAOnCustomPrefixesTest.java
> Automatic namespace completion in Facelets files
> ------------------------------------------------
>
> Key: JBIDE-12175
> URL: https://issues.jboss.org/browse/JBIDE-12175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JSF
> Affects Versions: 3.3.0.CR1
> Reporter: Lukáš Fryč
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> RichFaces community is complaining about complexity of maintaining namespaces through the JSF projects [1]
> as the sample could be following project file:
> https://github.com/richfaces/sandbox/blob/760fca06c7db23b542fa8d077f73dfe...
> It is very hard to maintain namespaces through project.
> ----
> What are current options when using JBoss Tools?
> * modify Facelets file templates for creating new files and list all favorite namespaces there
> * use autocompletion of detected namespaces (write {{xmlns:xyz="..."}} and autocompletion will offer you available namespaces)
> But both of the solutions are not as straight-forward as it could be.
> ----
> Tools could help and store the preferences for namespaces,
> so user would need only to start typing tag with prefix of the namespace (e.g. {{<a4j:}} and once he will complete the tag {{<a4j:ajax>}}, the namespace will be automatically added to the root of the XML file. ({{xmlns:a4j="http://richfaces.org/a4j"}}).
> ----
> The information about the prefixes could be retrieved from:
> * faces-config.xml generated by RichFaces CDK: {{faces-config/faces-config-extension/cdk:prefix}}
> * scanning the Facelets (XHTML) files in a project and collecting used namespace prefixes ({{xmlns:*}})
> [1] https://community.jboss.org/message/738739#738739
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-12175) Automatic namespace completion in Facelets files
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12175?page=com.atlassian.jira.plugi... ]
Victor Rubezhny reassigned JBIDE-12175:
---------------------------------------
Assignee: Alexey Kazakov (was: Victor Rubezhny)
> Automatic namespace completion in Facelets files
> ------------------------------------------------
>
> Key: JBIDE-12175
> URL: https://issues.jboss.org/browse/JBIDE-12175
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: JSF
> Affects Versions: 3.3.0.CR1
> Reporter: Lukáš Fryč
> Assignee: Alexey Kazakov
> Fix For: 4.1.0.Alpha1
>
>
> RichFaces community is complaining about complexity of maintaining namespaces through the JSF projects [1]
> as the sample could be following project file:
> https://github.com/richfaces/sandbox/blob/760fca06c7db23b542fa8d077f73dfe...
> It is very hard to maintain namespaces through project.
> ----
> What are current options when using JBoss Tools?
> * modify Facelets file templates for creating new files and list all favorite namespaces there
> * use autocompletion of detected namespaces (write {{xmlns:xyz="..."}} and autocompletion will offer you available namespaces)
> But both of the solutions are not as straight-forward as it could be.
> ----
> Tools could help and store the preferences for namespaces,
> so user would need only to start typing tag with prefix of the namespace (e.g. {{<a4j:}} and once he will complete the tag {{<a4j:ajax>}}, the namespace will be automatically added to the root of the XML file. ({{xmlns:a4j="http://richfaces.org/a4j"}}).
> ----
> The information about the prefixes could be retrieved from:
> * faces-config.xml generated by RichFaces CDK: {{faces-config/faces-config-extension/cdk:prefix}}
> * scanning the Facelets (XHTML) files in a project and collecting used namespace prefixes ({{xmlns:*}})
> [1] https://community.jboss.org/message/738739#738739
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBTIS-2) ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-2?page=com.atlassian.jira.plugin.sy... ]
Nick Boldt edited comment on JBTIS-2 at 1/24/13 1:07 PM:
---------------------------------------------------------
I've moved content from /development/ to /stable/ (if it had ".Final" in the name) and symlinked it back (using sftp). This way people can simply look to these URLs below to get any of the contained projects' content as either a stable or dev feed.
* http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/
* http://download.jboss.org/jbosstools/updates/stable/juno/soa-tooling/
When a new project is added, someone has to ensure that symlinks are created and composite*.xml files are updated on the server (and in github [1]). Pull Req #61 [0] shows what changes I did.
[0] https://github.com/jbosstools/jbosstools-download.jboss.org/pull/61
[1] https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... & https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j...
---
To perform a symlink:
{code}
TOOLS=tools@filemgmt.jboss.org:/downloads_htdocs/tools
project=modeshape
version=3.1.0.Final
echo "ln ../../../../stable/juno/soa-tooling/${project}/${version} ${version}" | sftp $TOOLS/updates/development/juno/soa-tooling/${project}/
{code}
The above process is pseudo-coded / documented here [2].
[2] https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/2...
was (Author: nickboldt):
I've moved content from /development/ to /stable/ (if it had ".Final" in the name) and symlinked it back (using sftp). This way people can simply look to these URLs below to get any of the contained projects' content as either a stable or dev feed.
* http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling/
* http://download.jboss.org/jbosstools/updates/stable/juno/soa-tooling/
When a new project is added, someone has to ensure that symlinks are created and composite*.xml files are updated on the server (and in github [1]). Pull Req #61 [0] shows what changes I did.
[0] https://github.com/jbosstools/jbosstools-download.jboss.org/pull/61
[1] https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... & https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j...
---
To perform a symlink:
TOOLS=tools@filemgmt.jboss.org:/downloads_htdocs/tools
project=modeshape
version=3.1.0.Final
echo "ln ../../../../stable/juno/soa-tooling/${project}/${version} ${version}" | sftp $TOOLS/updates/development/juno/soa-tooling/${project}/
The above process is pseudo-coded / documented here [2].
[2] https://svn.jboss.org/repos/devstudio/trunk/documentation/Release_Guide/2...
> ensure all ten (10) JBT SOA components have published exploded update sites on http://download.jboss.org/jbosstools/updates/
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-2
> URL: https://issues.jboss.org/browse/JBTIS-2
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Nick Boldt
>
> For each of the JBT SOA components, we should ensure that they're all publishing into standard locations on http://download.jboss.org/jbosstools/updates/.
> This issue should be a container for child issues assigned to each project's releng person.
> Most important part of this is the documentation of process / rules / expecations / nomenclature, and creation of tooling to make it simple for project leads to publish & promote their bits:
> * JBIDE-12220 create generic publishing job which takes as input three parameters
> Done:
> * SwitchYard - JBIDE-10672 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/sw...
> * Modeshape Tools - JBBUILD-720, MODE-1506
> *- http://download.jboss.org/jbosstools/updates/development/indigo/soa-tooli... and
> *- http://download.jboss.org/jbosstools/updates/development/juno/soa-tooling...
> Publishes elsewhere, manually symlinked:
> * Drools/jbpm5 - JBRULES-3470 - http://download.jboss.org/jbosstools/updates/stable/indigo/soa-tooling/dr...
> Publishes elsewhere:
> * Savara - http://download.jboss.org/savara/releases/updates/2.0.x/
> * pi4soa - http://pi4soa.sourceforge.net/updates/
> Publishes as zip only:
> * Teiid Designer - https://www.jboss.org/teiiddesigner/downloads/ -> http://sourceforge.net/projects/teiid/files/teiid-designer/7.7/teiid_desi...
> No publishing or archiving strategy (staging only):
> * SOA Runtime Detection - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> * ESB - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> * jbpm3 - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> --> see also https://issues.jboss.org/browse/JBIDE-12631
> * JBoss BPEL - staging site only, eg., http://download.jboss.org/jbosstools/builds/staging/jbosstools-3.3_trunk....
> ---
> Once all the components are publishing sites, they can
> a) easily link to those individual sites from their download pages on www.jboss.org/{projectname}
> b) easily composite those sites into a single site and reference that site from www.jboss.org/tools/
> c) more easily aggregate the components into a single site & zip, proving that the content can be co-installed via p2 and that there are no unmet or conflicting dependencies
> d) (with a through c met) therefore provide additional stability checking for JBDS SOA/BRMS tooling, provided individually via JBDS Central.
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13232:
------------------------------------
We used to have one rolling version for all the TPs used in a given release... M4, M5, M6, M7, RC1, GA, SR1-pre, SR1, SR1a, SR2-pre, SR2, etc. but that introduced more problems than it solved.
Regardless of the suffix (-SNAPSHOT or Alpha/Beta/CR/Final, or a combination) the fact is we need to version each TP release uniquely and use them until they're expired by a newer one. Often in the past we've needed several in use in parallel... for example if we've released a milestone build based on one TP (eg., M4), are working in stable branch for the next milestone release using second one (M5), and developing trunk against a newer third one (M6). M4 can vanish once the stable branch release is done and released (at which point M5 becomes the minimum one we have to keep around), but we often need more than one actively used TP at a time... and that's not even including the upper limit ones (mins AND maxs) or testing against past/future releases.
As well, we have a bug trying to publish TPs w/o the -SNAPSHOT suffix so currently everything has to be a SNAPSHOT whether it's Final or in-development.
See JBIDE-13408 -- maybe you have some insight on how to solve that?
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
> Attachments: JBIDE13232.parent.pom.tweaks.txt
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 2 months
- 1
- 0
[JBoss JIRA] (JBIDE-13232) refactor target platforms' GAVs, names, labels (was target platforms has the same name)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13232?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13232 at 1/24/13 12:57 PM:
--------------------------------------------------------------
[~rcernich]
{quote}I know I'm late to the party and I didn't read the whole history of comments, but it seems like this would be more useful if the tp projects were versioned along with JBT. Obviously, you could add min/max as necessary. This would allow me to say something akin to: use the target platform that goes with JBT 4.0, e.g. (maven management key) org.jboss.tools:target-platform:target:unified-min:4.0
As a downstream consumer, I don't really care what version of the Eclipse platform the TP is tied to, since I will be targeting some version of JBT (e.g. 4.0, 4.1, 5.0, etc.). The current approach leaves me having to map a JBT version to a TP version (unnecessarily so, in my opinion).{quote}
The approach you're suggesting doesn't scale because there is not a 1-1 mapping that would allow to bind a version of JBT to a (min/max) target platforms couple. We change TPs more often that we release milestone of JBT at the beginning of a release stream; and less than there are JBT milestones at the end of the stream.
Also some TPs are used in different stream (eg for now, JBT 4.1.0.Alpha1 shares the same minimal TP as JBT 4.0.0), and it's pretty difficult to maintain this mapping from target-platforms. That's why TPs now follow their own versioning scheme and JBT parent is updated to select one of the available TPs.
I understand that, as a downstream consumer, it's not the easiest to guess which TP is used for which JBT. For that, you'll have to either check the parent pom of the JBT version you're targetting, the TP version is written in it; or simply come to mailing-list/IRC/whatever and ask.
was (Author: mickael_istria):
[~rcernich]
{quote}I know I'm late to the party and I didn't read the whole history of comments, but it seems like this would be more useful if the tp projects were versioned along with JBT. Obviously, you could add min/max as necessary. This would allow me to say something akin to: use the target platform that goes with JBT 4.0, e.g. (maven management key) org.jboss.tools:target-platform:target:unified-min:4.0
As a downstream consumer, I don't really care what version of the Eclipse platform the TP is tied to, since I will be targeting some version of JBT (e.g. 4.0, 4.1, 5.0, etc.). The current approach leaves me having to map a JBT version to a TP version (unnecessarily so, in my opinion).{quote}
The approach you're suggesting doesn't scale because there is not a 1-1 mapping that would allow to bind a version of JBT to a (min/max) target platforms couple. We change TPs more often that we release milestone of JBT at the beginning of a release stream; and less than there are JBT milestones at the end of the stream.
Also some TPs are used in different stream (eg for now, JBT 4.1.0.Alpha1 shares the same minimal TP as JBT 4.0.0), and it's pretty difficult to maintain this mapping from target-platforms. That's why TPs now follow there versioning scheme and JBT parent is updated to select on of the available TPs.
I understand that, as a downstream consumer, it's not the easiest why to guess which TP is used for JBT x. For that, you'll have to either check the parent pom of the JBT version you're targetting, the TP version is written in it; or simply come to mailing-list/IRC/whatever and ask.
> refactor target platforms' GAVs, names, labels (was target platforms has the same name)
> ---------------------------------------------------------------------------------------
>
> Key: JBIDE-13232
> URL: https://issues.jboss.org/browse/JBIDE-13232
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.1.0.Alpha1
> Environment:
> Reporter: Max Rydahl Andersen
> Assignee: Nick Boldt
> Fix For: 4.1.0.Alpha1
>
> Attachments: JBIDE13232.parent.pom.tweaks.txt
>
>
> .target files are all called "e42-wtp34-jbds6" even though they are for jbosstools and not specific to jbds6 either.
> Makes it hard to actually see which target platform to choose
--
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
13 years, 2 months
- 1
- 0