[JBoss JIRA] (JBIDE-15885) Cannot run cordova project on android if a target with API level<13 is present
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15885?page=com.atlassian.jira.plugi... ]
Gorkem Ercan commented on JBIDE-15885:
--------------------------------------
A new patch is on the master. We now demand a target API level >=17 and take the newest ( the hishest API level) target to use. Fix will be merged to 4.1.1RC1 as well.
> Cannot run cordova project on android if a target with API level<13 is present
> ------------------------------------------------------------------------------
>
> Key: JBIDE-15885
> URL: https://issues.jboss.org/browse/JBIDE-15885
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Gorkem Ercan
> Priority: Critical
> Labels: respin-c
> Fix For: 4.1.1.CR1
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> if user has old (api level<13) android target defined the project fails to build for running on android.
> See JBIDE-14544 for details.
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15848) JSF Portal Project XML Problem
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ]
Snjezana Peco updated JBIDE-15848:
----------------------------------
Fix Version/s: 4.2.0.Alpha1
> JSF Portal Project XML Problem
> ------------------------------
>
> Key: JBIDE-15848
> URL: https://issues.jboss.org/browse/JBIDE-15848
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, portal-gatein, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1
> Reporter: Radoslav Rábara
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: jsf - Error.jpg, jsf - show details.jpg
>
>
> Creating JSF Portal Project ends with error:
> Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd).
> Type: XML Error, Resource: faces-config.xml
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15848) JSF Portal Project XML Problem
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15848?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-15848.
-----------------------------------
Resolution: Done
Fixed within JBIDE-15849.
> JSF Portal Project XML Problem
> ------------------------------
>
> Key: JBIDE-15848
> URL: https://issues.jboss.org/browse/JBIDE-15848
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf, portal-gatein, upstream
> Affects Versions: 4.1.1.Beta1
> Environment: JBDS 7.1.0 Beta1-v20131102-1529-B493 and JPP 6.1
> Reporter: Radoslav Rábara
> Assignee: Snjezana Peco
> Priority: Blocker
> Fix For: 4.2.0.Alpha1
>
> Attachments: jsf - Error.jpg, jsf - show details.jpg
>
>
> Creating JSF Portal Project ends with error:
> Referenced file contains errors (jar:file:/home/rrabara/jbdevstudio7.1.0.Beta1b/studio/plugins/org.jboss.tools.jst.web_3.5.1.Alpha2-v20130927-0108-B90.jar!/catalog/web-facesconfig_2_2.xsd).
> Type: XML Error, Resource: faces-config.xml
--
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
12 years, 6 months
[JBoss JIRA] (JBIDE-15868) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15868?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-15868:
---------------------------------------
I have noticed that there is already a bug related to this issue - https://bugs.eclipse.org/bugs/show_bug.cgi?id=421366
I have created a patch.
> 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
> ----------------------------------------------------------
>
> Key: JBIDE-15868
> URL: https://issues.jboss.org/browse/JBIDE-15868
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: testfailure
> Fix For: 4.1.1.Beta1
>
>
> *1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> # [org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest|https://je...] (failing for 18 builds)
> [Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for maven component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest : testJBIDE11570_constraintViolations{color} (failing for 18 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-central_41/103/testReport/org.jboss.tools.maven.configurators.tests/SeamConfiguratorTest/testJBIDE11570_constraintViolations}
> <case>
> <age>18</age>
> <className>org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest</className>
> <duration>1.229</duration>
> <errorStackTrace>java.lang.NullPointerException
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingFiles(VirtualFile.java:104)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingResources(VirtualFile.java:93)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.exists(VirtualResource.java:88)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getNonBinaryComponentManifest(ManifestUtilities.java:124)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifest(ManifestUtilities.java:81)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifestClasspath(ManifestUtilities.java:147)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getManifestClasspath(J2EEModuleVirtualComponent.java:248)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:368)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
> at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
> at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:107)
> at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:746)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:865)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:289)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:216)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:326)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:324)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:299)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:286)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:273)
> at org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest.testJBIDE11570_constraintViolations(SeamConfiguratorTest.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
> at java.lang.Thread.run(Thread.java:662)
> </errorStackTrace>
> <failedSince>86</failedSince>
> <name>testJBIDE11570_constraintViolations</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>TEST-SETUP: testJBIDE11570_constraintViolations
> Restoring user settings file: /home/hudson/.m2/settings.xml
> </stdout>
> </case>
> {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
12 years, 6 months
[JBoss JIRA] (JBIDE-15892) Weird code in JBT installation script: install.sh
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15892?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-15892:
------------------------------------
OK, I'm thinking I'll replace the multiple links with a pointer to http://download.jboss.org/jbosstools/updates/scripted-install/README.html ... once we're happy w/ the content.
See JBIDE-15891 for details.
> Weird code in JBT installation script: install.sh
> --------------------------------------------------
>
> Key: JBIDE-15892
> URL: https://issues.jboss.org/browse/JBIDE-15892
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.1.1.Beta1
> Reporter: Pavol Srna
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 4.1.1.CR1
>
> Attachments: JBIDE15892.png
>
>
> install.sh contains some weird hardcoded stuff. you can download the script from offcial pages: http://www.jboss.org/tools/download/installation/update_4_1.html#fromscript
> [~nickboldt] can you explain how is it meant to be used?
> I don't think it is very straight forward for the user.
> {code}
> #!/bin/bash
> # install all of JBT into Eclipse Standard bundle
> target=${HOME}/eclipse/eclipse43; cd ${target}; rm -fr ${target}/eclipse
> tar xzf /tmp/eclipse-standard-kepler-R-linux-gtk-x86_64.tar.gz
> ${target}/eclipse/eclipse -consolelog -nosplash -data /tmp -application org.eclipse.ant.core.antRunner -f \
> install.xml \
> -DsourceZip=/tmp/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip \
> -DotherRepos=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ \
> -DtargetDir=${target}/eclipse/
> # [p2.dir] Installing org.hibernate.eclipse.feature.source.feature.group 3.7.0.Final-v20130717-0715-B84.
> # ...
> # [p2.dir] Installing org.mozilla.xulrunner.feature.feature.group 1.9.218.Final-v20121126-2356-B155.
> # [p2.dir] Operation completed in 212518 ms.
> # install JBT Central, including Subclipse w/ SVNKit into Eclipse JEE bundle
> target=${HOME}/eclipse/eclipse43; cd ${target}; rm -fr ${target}/eclipse
> tar xzf /tmp/eclipse-jee-kepler-R-linux-gtk-x86_64.tar.gz
> ${target}/eclipse/eclipse -consolelog -nosplash -data /tmp -application org.eclipse.ant.core.antRunner -f \
> install.xml \
> -DsourceZip=/tmp/jbosstools-Update-4.1.0.Final_2013-07-19_19-47-52-B380.zip \
> -DotherRepos=http://download.jboss.org/jbosstools/updates/stable/kepler/central/core/ \
> -DtargetDir=${target}/eclipse/
> -Dinstall="org.jboss.tools.community.central.feature.feature.group,\
> org.tigris.subversion.subclipse.feature.group,\
> org.tigris.subversion.clientadapter.svnkit.feature.feature.group,\
> com.collabnet.subversion.merge.feature.feature.group,\
> net.java.dev.jna.feature.group,\
> org.tigris.subversion.clientadapter.feature.feature.group,\
> org.tigris.subversion.subclipse.graph.feature.feature.group,\
> org.tmatesoft.svnkit.feature.group"
> # [p2.dir] Installing org.jboss.tools.community.central.feature.feature.group 1.2.0.Final-v20130719-2050-B70.
> # [p2.dir] Installing org.tigris.subversion.subclipse.feature.group 1.8.20.
> # [p2.dir] Installing org.tigris.subversion.clientadapter.svnkit.feature.feature.group 1.7.9.1.
> # ...
> # [p2.dir] Operation completed in 55635 ms.
> {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
12 years, 6 months
[JBoss JIRA] (JBIDE-15819) JSF XHTML Validator Ignores or Overrides Project-level XML Validation settings
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15819?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-15819:
-----------------------------------------
[~bfitzpat] Thanks a lot for a good catch!
> JSF XHTML Validator Ignores or Overrides Project-level XML Validation settings
> ------------------------------------------------------------------------------
>
> Key: JBIDE-15819
> URL: https://issues.jboss.org/browse/JBIDE-15819
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsf
> Affects Versions: 4.1.1.Alpha1
> Environment: Windows 7/JBDS 7.1 Beta 1 installed with SwitchYard Editor from the Kepler JBTIS (http://download.jboss.org/jbosstools/updates/integration/kepler/integrati...)
> Reporter: Brian Fitzpatrick
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.Alpha1
>
>
> While testing the SwitchYard Editor, we have hit upon a strange error that occurs in a brand new workspace with JBDS 7.1 Beta 1 and the SwitchYard Editor installed.
> To reproduce:
> 1) Start with an empty workspace (with JBDS 7.1 Beta 1 and SwitchYard Editor installed)
> 2) Create a new SwitchYard project.
> 3) Add a new Bean component (drag the Bean implementation from the palette onto the composite (blue box) on the canvas).
> 4) Save the project.
> Though we by default turn off XML Validation on the new SwitchYard project, the XML validator is run and we find 3 or more errors off the bat.
> We believe this is due to the JSF XHTML validator. If we turn it off (Window->Preferences->Validation; find XHTML Syntax Validator in the list and uncheck "Build" and "Manual"), the errors go away (as they should). And depending on what OS you're on (Linux seems to do one thing, Windows another), you can turn the XHTML Syntax Validator back on and either not see the errors or see the errors on a manual validation.
> There are quite a few internal APIs used by the XHTML Validator, so we're not sure if that plays into it. Perhaps there's a static variable that doesn't get initialized properly until the validator is turned off and on during a workbench session. Or maybe this line should return null instead of the ValidationReport instance. :
> https://github.com/jbosstools/jbosstools-javaee/blob/master/jsf/plugins/o...
> We really don't know. But it shouldn't interfere with the XML Validation settings considering that none of the files in the project are XHTML files and none of them seem to match the rules for the validator.
> The only workaround we've found is to turn off XML File validation at the workbench level (i.e. Window->Preferences->XML->XML Files->Validation; turn off "Honour all XML schema locations") instead of the project level.
--
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
12 years, 6 months