[JBoss JIRA] (JBIDE-10276) test failures in org.jboss.tools.maven.ui.bot.test
by Nick Boldt (Created) (JIRA)
test failures in org.jboss.tools.maven.ui.bot.test
--------------------------------------------------
Key: JBIDE-10276
URL: https://issues.jboss.org/browse/JBIDE-10276
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: maven
Affects Versions: 3.3.0.M5
Reporter: Nick Boldt
Assignee: Fred Bricon
Fix For: 3.3.0.M5
https://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_Trunk/jo...
{code}
15 failures (+15)
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.testOpenMavenProfiles
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.testErrors
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.createJSFProjectTest_AS6_v2
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.activateMavenFacet_AS6_v2
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.buildProject_AS6_v2
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.createJSFProjectTest_AS7_v2
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.activateMavenFacet_AS7_v2
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.buildProject_AS7_v2
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.createJSFProjectTest_AS6_v1
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.activateMavenFacet_AS6_v1
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.buildProject_AS6_v1
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.createJSFProjectTest_AS7_v1
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.activateMavenFacet_AS7_v1
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.buildProject_AS7_v1
>>> org.jboss.tools.maven.ui.bot.test.MavenAllBotTests.createSimpleJsfProjectArchetype
{code}
Also failing in overall tests job:
http://hudson.qa.jboss.com/hudson/job/jbosstools-3.3_trunk.tests/1122/tes...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-10779) "Plugin execution not covered by lifecycle configuration" for maven-compiler-plugin when importing Seam 2.3 examples
by Fred Bricon (JIRA)
Fred Bricon created JBIDE-10779:
-----------------------------------
Summary: "Plugin execution not covered by lifecycle configuration" for maven-compiler-plugin when importing Seam 2.3 examples
Key: JBIDE-10779
URL: https://issues.jboss.org/browse/JBIDE-10779
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Build/Releng, maven
Affects Versions: 3.3.0.M5
Reporter: Fred Bricon
Assignee: Fred Bricon
Fix For: 3.3.0.Beta1
When importing Seam 2.3 examples (ex booking from http://anonsvn.jboss.org/repos/seam/branches/community/Seam_2_3/examples/...), Java projects are not configured properly and you get red error markers like
{quote}Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile (execution: default-compile, phase: compile){quote}
The problem is some parent configures the maven-compiler-plugin to use compilerId=eclipse, which is not supported out of the box by m2e (it only supports the default compilerId=javac).
To fix this issue, you have to either :
* Modify your parent pom.xml to map the compilerId=eclipse pluginExecution to the org.eclipse.m2e.jdt.javaConfigurator by adding
{code:xml}
<pluginManagement>
<plugins>
<plugin>
<groupId>org.eclipse.m2e</groupId>
<artifactId>lifecycle-mapping</artifactId>
<version>1.0.0</version>
<configuration>
<lifecycleMappingMetadata>
<pluginExecutions>
<pluginExecution>
<pluginExecutionFilter>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<versionRange>[2.0,)</versionRange>
<goals>
<goal>compile</goal>
<goal>testCompile</goal>
</goals>
<parameters>
<compilerId>eclipse</compilerId>
</parameters>
</pluginExecutionFilter>
<action>
<configurator>
<id>org.eclipse.m2e.jdt.javaConfigurator</id>
</configurator>
</action>
</pluginExecution>
</pluginExecutions>
</lifecycleMappingMetadata>
</configuration>
</plugin>
</plugins>
</pluginManagement>
{code}
* or install m2e-jdt-compiler from http://download.jboss.org/jbosstools/builds/staging/m2e-jdt-compiler/all/...
2nd option is obviously far less intrusive. It requires m2e-jdt-compiler to be made available from a stable URL and added as a build requirement.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month
[JBoss JIRA] (JBIDE-11002) Error in wizard when typing complete existing application name
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-11002:
-------------------------------------
Summary: Error in wizard when typing complete existing application name
Key: JBIDE-11002
URL: https://issues.jboss.org/browse/JBIDE-11002
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 3.3.0.Beta1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Priority: Critical
Fix For: 3.3.0.Beta1
Attachments: org.jboss.tools.openshift.express.ui.11002.patch
When typing a complete existing application name in the OpenShift Wizard, the project page will report an error indicating some missing path segment. The underlying cause is the lack of existing application name being properly set.
Also, when starting the wizard from Central, the existing app text has no content assist.
Also, when typing an existing app name, the app name, app type and configure cartridges should appear in the 'create application' group of the wizard page.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 1 month