[JBoss JIRA] (JBIDE-13429) setOutput method call doesn't work in testInstall.groovy script
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13429?page=com.atlassian.jira.plugi... ]
Pavol Srna updated JBIDE-13429:
-------------------------------
Summary: setOutput method call doesn't work in testInstall.groovy script (was: setOutput method doesn't work in testInstall.groovy script)
> setOutput method call doesn't work in testInstall.groovy script
> ---------------------------------------------------------------
>
> Key: JBIDE-13429
> URL: https://issues.jboss.org/browse/JBIDE-13429
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Build/Releng
> Affects Versions: 4.0.0.Final
> Reporter: Pavol Srna
> Assignee: Pavol Srna
> Fix For: 4.1.0.Alpha1
>
>
> org.apache.tools.ant.taskdefs.Java setOutput method call doesn't work in runSWTBotInstallRoutine in testInstall.groovy script. It means that the output from the process is not redirected to the temporary output file. The temporary output file is then empty and the errors cannot be detected. And it also means that the testInstall script can return SUCCESS even if there are errors.
> This issue is very well hidden, because testInstall.groovy script is mainly used in jenkins jobs and all of the jobs publish JUnit reports which will change the job status into yellow according to the produced xml report.
> But if you uncheck the "Publish JUnit report" option, then the job can be blue even if there are test errors.
>
--
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
[JBoss JIRA] (JBIDE-13429) setOutput method doesn't work in testInstall.groovy script
by Pavol Srna (JIRA)
Pavol Srna created JBIDE-13429:
----------------------------------
Summary: setOutput method doesn't work in testInstall.groovy script
Key: JBIDE-13429
URL: https://issues.jboss.org/browse/JBIDE-13429
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng
Affects Versions: 4.0.0.Final
Reporter: Pavol Srna
Assignee: Pavol Srna
Fix For: 4.1.0.Alpha1
org.apache.tools.ant.taskdefs.Java setOutput method call doesn't work in runSWTBotInstallRoutine in testInstall.groovy script. It means that the output from the process is not redirected to the temporary output file. The temporary output file is then empty and the errors cannot be detected. And it also means that the testInstall script can return SUCCESS even if there are errors.
This issue is very well hidden, because testInstall.groovy script is mainly used in jenkins jobs and all of the jobs publish JUnit reports which will change the job status into yellow according to the produced xml report.
But if you uncheck the "Publish JUnit report" option, then the job can be blue even if there are test errors.
--
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
[JBoss JIRA] (JBIDE-13417) Maven plugin org.jboss.tools.tycho-plugins:repository-utils fails to update p2repository archive in full jbosstools build
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13417?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13417:
----------------------------------------
Before changing anything, I did run the base job locally, and on CI with a clean workspace and I could not reproduce the issue you got.
> 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
> Fix For: 4.1.0.Alpha1
>
>
> 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
[JBoss JIRA] (JBIDE-13428) Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT/JBDS update sites, installers
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-13428:
-----------------------------------
Summary: Remove JBoss Maven JPA, JSF, JAX-RS features from the JBT/JBDS update sites, installers
Key: JBIDE-13428
URL: https://issues.jboss.org/browse/JBIDE-13428
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: Build/Releng
Reporter: Fred Bricon
Assignee: Nick Boldt
The JBoss Maven JPA, JSF, JAX-RS being migrated over m2e-wtp, the plugins and features have been removed from the git repo.
We need to make sure the the JBT/JBDS update sites, installers are curated as well.
--
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
[JBoss JIRA] (JBIDE-13365) Maven Hibernate plugin fails to build against Kepler
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13365?page=com.atlassian.jira.plugi... ]
Fred Bricon resolved JBIDE-13365.
---------------------------------
Resolution: Done
Fixed in master. The maven hibernate plugin now requires Dali 3.3.0 to compile.
Commit https://github.com/jbosstools/jbosstools-central/commit/c0f580f2d8c8ed556...
> Maven Hibernate plugin fails to build against Kepler
> ----------------------------------------------------
>
> Key: JBIDE-13365
> URL: https://issues.jboss.org/browse/JBIDE-13365
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: maven
> Reporter: Mickael Istria
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> Using TP from JBIDE-13336 which contain:
> {code}
> <unit id="org.eclipse.jpt.common.feature.feature.group" version="1.3.0.v201210121950-67A-AkF7BFAM7P7EQM"/>
> <unit id="org.eclipse.jpt.common.eclipselink.feature.feature.group" version="1.3.0.v201210121950-35-8s73574E3D38C8"/>
> <unit id="org.eclipse.jpt.jpa.eclipselink.feature.feature.group" version="3.3.0.v201210121950-7K7P0EVVFNVKhJeGepg6NHG"/>
> <unit id="org.eclipse.jpt.jpa.feature.feature.group" version="3.3.0.v201210121950-7W7W4FBBoParY-XLUG4H6NHG"/>
> <unit id="org.eclipse.jpt.jaxb.feature.feature.group" version="1.3.0.v201210121950-57A-AkF7BFAM7P7EQM"/>
> {code},
> I couldn't build the maven/central component because of an issue in org.jboss.tools.maven.hibernate bundle
> {code}
> [ERROR] Failed to execute goal org.eclipse.tycho:tycho-compiler-plugin:0.16.0:compile (default-compile) on project org.jboss.tools.maven.hibernate: Compilation failure: Compilation failure:
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[15,0]
> [ERROR] import org.eclipse.jpt.common.core.JptCommonCorePlugin;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The import org.eclipse.jpt.common.core.JptCommonCorePlugin cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[18,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/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[25,0]
> [ERROR] public class MavenHibernateLibraryProviderInstallOperationConfig extends MavenLibraryProviderInstallOperationConfig implements JpaLibraryProviderInstallOperationConfig {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type MavenHibernateLibraryProviderInstallOperationConfig must implement the inherited abstract method JpaLibraryProviderInstallOperationConfig.setJpaPlatformConfig(JpaPlatformConfig)
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[25,0]
> [ERROR] public class MavenHibernateLibraryProviderInstallOperationConfig extends MavenLibraryProviderInstallOperationConfig implements JpaLibraryProviderInstallOperationConfig {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] The type MavenHibernateLibraryProviderInstallOperationConfig must implement the inherited abstract method JpaLibraryProviderInstallOperationConfig.getJpaPlatformConfig()
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[27,0]
> [ERROR] private JpaPlatformDescription jpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[29,0]
> [ERROR] public JpaPlatformDescription getJpaPlatform() {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[30,0]
> [ERROR] return jpaPlatformDescription;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[33,0]
> [ERROR] public void setJpaPlatform(JpaPlatformDescription jpaPlatform) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[34,0]
> [ERROR] this.jpaPlatformDescription = jpaPlatform;
> [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^
> [ERROR] JpaPlatformDescription cannot be resolved to a type
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[43,0]
> [ERROR] if (getJpaPlatform() != null) {
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getJpaPlatform() from the type MavenHibernateLibraryProviderInstallOperationConfig refers to the missing type JpaPlatformDescription
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/MavenHibernateLibraryProviderInstallOperationConfig.java:[44,0]
> [ERROR] for (LibraryValidator libraryValidator : JptCommonCorePlugin.getLibraryValidators(this)) {
> [ERROR] ^^^^^^^^^^^^^^^^^^^
> [ERROR] JptCommonCorePlugin cannot be resolved
> [ERROR] /home/mistria/git/jbosstools-central/maven/plugins/org.jboss.tools.maven.hibernate/src/org/jboss/tools/maven/hibernate/libprov/HibernateLibValidator.java:[26,0]
> [ERROR] if (jpaConfig.getJpaPlatform().getId().contains("hibernate")) {
> [ERROR] ^^^^^^^^^^^^^^
> [ERROR] The method getJpaPlatform() is undefined for the type JpaLibraryProviderInstallOperationConfig
> [ERROR] 12 problems (12 errors)
> {code}
> Please re-assign this issue to me if you think we should use and ship another version of JBT.
--
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