[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17676:
-------------------------------------
Using phonecat master branch JBDS 8.0.0.Beta3b and converting imported project JavaScript project I have correct code completion in controller.js file
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17724) Changes cause full redeployment of exploded WAR
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17724?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17724.
---------------------------------
I tried a couple of things.
I checked the forge website, that now correctly uses incremental updates when you only change a file.
I checked Rob's sample workspace with the 2 layers of nested utility projects. I verified that changing a file in the war project does not cause redeploy, while changing something (java or text file) in one of the nested utility projects will cause full redeploy.
Verified in JBDS 8.0.0.Beta3b B193
> Changes cause full redeployment of exploded WAR
> -----------------------------------------------
>
> Key: JBIDE-17724
> URL: https://issues.jboss.org/browse/JBIDE-17724
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta2
> Environment: Windows 8.1 x64
> Java 7u51 x64
> Luna x64
> Reporter: Cody Lerum
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: respin-b
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
> Attachments: workspace.zip
>
>
> After moving to Luna from Kepler any changes to java or jsf resources are causing a full redeployment of the exploded war to JBoss 7.1.3.Final
> This prevents any updating of JSF resources or debugging java code.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17856) Fix favicon so edges are crisp on any background (not just white)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17856?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17856:
---------------------------------------------
I would appreciate we dont apply PR's when there is still uncertainty/not cleared.
I looked into this more last night as commented on the PR but couldn't leave comments here since I was on the move.
community.jboss.org/en/tools last night referenced http://static.jboss.org/images/tools/tools-banner-1180px.png AND http://static.jboss.org/images/tools/favicon.ico - urls you say does not work but still all my browsers and curl can fetch them.
Thus the status last night was that the shared location for these images was working at http://static.jboss.org/images/tools/*
Notice the *tools* url.
jbosstools and the tools on static.jboss.org/* looks like previous attempts on cleaning this up but was never completed. That is why the various profiles in site.yml seem to have *different* urls for these locations. Thus the right place to put these would be in a shared location with community.jboss.org so they do not drift apart.
But in the meantime it looks like community.jboss.org got updated over night and our jboss tools community page lost *all* project branding making it barely noticeable which project you are looking at now ;/
I'm asking #jbossorg what happend there and if that is intentional.
Then back to what url is the right one, here are the current list of "tools" vs "jbosstools" on filemgmt.jboss.org:
/static_htdocs/tools and /static_htdocs/jbosstools both exist (but different content)
/design_htdocs/jbosstools
/downlods_htdocs/jbosstools AND /downloads_htdocs/tools both exist (one is symbolic link for the other)
/docs_htdocs/tools
/stg_htdocs/tools
/www_htdocs/tools
In short: tools is the one used for majority of our locations on filemgmt. It is only named jbosstools on design and download due to them being created *before* we actually got tools urls defined (~8 years ago).
Thus to clean this up i've symbolic linked static_htdocs/tools/images to static_htdocs/jbosstools/images so we can continue the more consistent use of tools without breaking the urls.
I'm also going to update site.yml again since the pull/181 PR did not actually fix *all* of the occurrences of this path.
> Fix favicon so edges are crisp on any background (not just white)
> -----------------------------------------------------------------
>
> Key: JBIDE-17856
> URL: https://issues.jboss.org/browse/JBIDE-17856
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: website
> Affects Versions: 4.2.0.Beta2
> Reporter: Max Rydahl Andersen
>
> as reported here https://twitter.com/vogella/status/487527322770497536 our favicon has white artifacts making it look ugly - should get fixed
> !https://pbs.twimg.com/media/BsQLhBvCAAAOkBU.png!
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-17676 at 7/22/14 3:51 AM:
--------------------------------------------------------------
According to this http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta2.html... AngularJS code completion should be available in JBoss Tools HTML editor. Could you give me a project where I can test it please?
Regarding to this issue should I change it to Feature request?
was (Author: vpakan):
According to this http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta2.html... AngularJS code completion should be available in JBoss Toosl HTML editor. Could you give me a project where I can test it please?
Regarding to this issue should I change it to Feature request?
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17676) Angular Code Assist doesn't work for angular phonecat app
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17676?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17676:
-------------------------------------
According to this http://tools.jboss.org/documentation/whatsnew/jbosstools/4.2.0.Beta2.html... AngularJS code completion should be available in JBoss Toosl HTML editor. Could you give me a project where I can test it please?
Regarding to this issue should I change it to Feature request?
> Angular Code Assist doesn't work for angular phonecat app
> ---------------------------------------------------------
>
> Key: JBIDE-17676
> URL: https://issues.jboss.org/browse/JBIDE-17676
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.Beta2
> Environment: JBT 4.2.0.Beta2, Linux, AngulaJS for Eclipse installed from JBoss Central Early access
> Reporter: Vlado Pakan
> Assignee: Victor Rubezhny
> Fix For: 4.2.0.CR1
>
> Attachments: angular.png, phonecatControllers.png
>
>
> 1. Follow steps from JBIDE-16544 to import angular phonecat project
> 2. Open controllers.js in Java Script editor
> ERROR: There is no code assist for angular.| or phonecatControllers.|
> 3. Open phone-detail.html
> ERROR: There is no code assist for {{|}} or {{phone.|}}
> Is it not supported scenario?
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17826) Unable to run Aerogear Cordova project with CordovaSim
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17826?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-17826 at 7/22/14 3:41 AM:
--------------------------------------------------------------
Working fine with:
{noformat}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/jbosstools-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
-Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
{noformat}
For JBDS discovery site this site has to be used instead the one mentioned in previous comment
{noformat}
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/earlyaccess/4.2.luna/devstudio-directory.xml
{noformat}
was (Author: vpakan):
Working fine with:
{noformat}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/jbosstools-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
-Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
{noformat}
For JBDS discovery site this site has to be used instead the one mentioned in previous comment
{noformat}
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/earlyaccess/4.2.luna/devstudio-directory.xml
{noformat}
devstudio-directory.xml
> Unable to run Aerogear Cordova project with CordovaSim
> ------------------------------------------------------
>
> Key: JBIDE-17826
> URL: https://issues.jboss.org/browse/JBIDE-17826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Beta3
> Environment: Fedora 18 KDE 64bit
> JBDS 8.0.0.Beta3-v20140706-0939-B172 (jboss-devstudio-8.0.0.Beta3-v20140706-0939-B172-installer-eap.jar)
> Oracle JDK 1.8
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
> Attachments: central-respinB.png, central.png
>
>
> 1. Import Hybrid Mobile Project from JBoss Central
> 2. Run it with CordovaSim
> ERROR:
> {noformat}
> no protocol: /home/vpakan/jbds800Beta3/studio/configuration
> Stack trace:
> java.net.MalformedURLException: no protocol: /home/vpakan/jbds800Beta3/studio/configuration
> at java.net.URL.<init>(URL.java:586)
> at java.net.URL.<init>(URL.java:483)
> at java.net.URL.<init>(URL.java:432)
> at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.getPortFromURL(CordovaSimArgs.java:100)
> at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.parseArgs(CordovaSimArgs.java:51)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:88)
> org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object;
> Stack trace:
> java.lang.NoSuchMethodError: org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object;
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.loadPreferences(CordovaSimRunner.java:165)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:179)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:110)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:89)
> org.jboss.tools.vpe.cordavasim.command.stop.server: Server on port 0 was stopped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17826) Unable to run Aerogear Cordova project with CordovaSim
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17826?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17826:
-------------------------------------
Working fine with:
{noformat}
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/jbosstools-directory.xml
-Djboss.discovery.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
-Djboss.discovery.earlyaccess.site.url=http://download.jboss.org/jbosstools/discovery/nightly/earlyaccess/4.2.luna/
{noformat}
For JBDS discovery site this site has to be used instead the one mentioned in previous comment
{noformat}
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/nightly/earlyaccess/4.2.luna/devstudio-directory.xml
{noformat}
devstudio-directory.xml
> Unable to run Aerogear Cordova project with CordovaSim
> ------------------------------------------------------
>
> Key: JBIDE-17826
> URL: https://issues.jboss.org/browse/JBIDE-17826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Affects Versions: 4.2.0.Beta3
> Environment: Fedora 18 KDE 64bit
> JBDS 8.0.0.Beta3-v20140706-0939-B172 (jboss-devstudio-8.0.0.Beta3-v20140706-0939-B172-installer-eap.jar)
> Oracle JDK 1.8
> Reporter: Vlado Pakan
> Assignee: Ilya Buziuk
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
> Attachments: central-respinB.png, central.png
>
>
> 1. Import Hybrid Mobile Project from JBoss Central
> 2. Run it with CordovaSim
> ERROR:
> {noformat}
> no protocol: /home/vpakan/jbds800Beta3/studio/configuration
> Stack trace:
> java.net.MalformedURLException: no protocol: /home/vpakan/jbds800Beta3/studio/configuration
> at java.net.URL.<init>(URL.java:586)
> at java.net.URL.<init>(URL.java:483)
> at java.net.URL.<init>(URL.java:432)
> at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.getPortFromURL(CordovaSimArgs.java:100)
> at org.jboss.tools.vpe.cordovasim.CordovaSimArgs.parseArgs(CordovaSimArgs.java:51)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:88)
> org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object;
> Stack trace:
> java.lang.NoSuchMethodError: org.jboss.tools.vpe.cordovasim.model.preferences.CordavaSimSpecificPreferencesStorage.load()Ljava/lang/Object;
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.loadPreferences(CordovaSimRunner.java:165)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:179)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:110)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:89)
> org.jboss.tools.vpe.cordavasim.command.stop.server: Server on port 0 was stopped
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3098) MissingResourceException after JBDS startup
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-3098?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-3098.
----------------------------
Resolution: Done
This one really seems to be fixed as consequence of fixes in JBDS-3099. Closing.
> MissingResourceException after JBDS startup
> -------------------------------------------
>
> Key: JBDS-3098
> URL: https://issues.jboss.org/browse/JBDS-3098
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: central, discovery
> Affects Versions: 8.0.0.Beta3
> Environment: 8.0.0.Beta3b
> Reporter: Radim Hopp
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 8.0.0.Beta3
>
>
> Exception in error log right after JBDS startup:
> {noformat:title=Cannot load bundle com.jboss.jbds.central.discovery.earlyaccess_8.0.0.Beta3_v20140718_1800_B191.jar_1783823812217829775.jar from url https://devstudio.jboss.com/updates/8.0-staging/discovery/com.jboss.jbds....: Can't find resource for bundle java.util.PropertyResourceBundle, key html5.wizard.description}
> java.util.MissingResourceException: Can't find resource for bundle java.util.PropertyResourceBundle, key html5.wizard.description
> at java.util.ResourceBundle.getObject(ResourceBundle.java:450)
> at java.util.ResourceBundle.getString(ResourceBundle.java:407)
> at org.eclipse.core.internal.registry.RegistrySupport.translate(RegistrySupport.java:42)
> at org.eclipse.core.runtime.spi.RegistryStrategy.translate(RegistryStrategy.java:145)
> at org.eclipse.core.internal.registry.ExtensionRegistry.translate(ExtensionRegistry.java:863)
> at org.eclipse.core.internal.registry.ExtensionsParser.translate(ExtensionsParser.java:673)
> at org.eclipse.core.internal.registry.ExtensionsParser.parseConfigurationElementAttributes(ExtensionsParser.java:427)
> at org.eclipse.core.internal.registry.ExtensionsParser.handleExtensionState(ExtensionsParser.java:333)
> at org.eclipse.core.internal.registry.ExtensionsParser.startElement(ExtensionsParser.java:613)
> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:509)
> at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:378)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2770)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:606)
> at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:117)
> at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:510)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:848)
> at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:777)
> at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:141)
> at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1213)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:649)
> at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl.parse(SAXParserImpl.java:333)
> at org.eclipse.core.internal.registry.ExtensionsParser.parseManifest(ExtensionsParser.java:405)
> at org.eclipse.core.internal.registry.ExtensionRegistry.addContribution(ExtensionRegistry.java:1062)
> at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundle(DiscoveryRegistryStrategy.java:157)
> at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.processBundles(DiscoveryRegistryStrategy.java:126)
> at org.jboss.tools.project.examples.internal.discovery.xpl.DiscoveryRegistryStrategy.onStart(DiscoveryRegistryStrategy.java:78)
> at org.eclipse.core.internal.registry.ExtensionRegistry.<init>(ExtensionRegistry.java:725)
> at org.jboss.tools.project.examples.internal.discovery.xpl.ExternalBundleDiscoveryStrategy.performDiscovery(ExternalBundleDiscoveryStrategy.java:125)
> at org.jboss.tools.project.examples.internal.discovery.ChainedDiscoveryStrategy.performDiscovery(ChainedDiscoveryStrategy.java:62)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:114)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardManager.loadWizards(ProxyWizardManager.java:101)
> at org.jboss.tools.central.internal.discovery.wizards.ProxyWizardUpdateJob.run(ProxyWizardUpdateJob.java:44)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> On first sight it seems that this error does not affect HTML5 Project archetype.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBDS-3099) No Early Access features in Central
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBDS-3099?page=com.atlassian.jira.plugin.... ]
Radim Hopp closed JBDS-3099.
----------------------------
I'm able to install early access features from central ;-) Closing.
> No Early Access features in Central
> -----------------------------------
>
> Key: JBDS-3099
> URL: https://issues.jboss.org/browse/JBDS-3099
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: central, updatesite
> Affects Versions: 8.0.0.Beta3
> Environment: JBDS 8.0.0.Beta3b
> Reporter: Radim Hopp
> Assignee: Nick Boldt
> Priority: Critical
> Fix For: 8.0.0.Beta3
>
>
> There are no Early Access features in Central and there is error in error log:
> {noformat:title=Provisioning exception}
> org.eclipse.equinox.p2.core.ProvisionException: No repository found at https://devstudio.jboss.com/updates/8.0.0/jboss-devstudio-8.0.0.Beta3b-ta....
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.fail(AbstractRepositoryManager.java:395)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:692)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.addChild(CompositeMetadataRepository.java:166)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepository.<init>(CompositeMetadataRepository.java:106)
> at org.eclipse.equinox.internal.p2.metadata.repository.CompositeMetadataRepositoryFactory.load(CompositeMetadataRepositoryFactory.java:122)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.factoryLoad(MetadataRepositoryManager.java:57)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:768)
> at org.eclipse.equinox.internal.p2.repository.helpers.AbstractRepositoryManager.loadRepository(AbstractRepositoryManager.java:668)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:96)
> at org.eclipse.equinox.internal.p2.metadata.repository.MetadataRepositoryManager.loadRepository(MetadataRepositoryManager.java:92)
> at org.jboss.tools.central.editors.xpl.P2CachedRepoUtil.getRepoForConnector(P2CachedRepoUtil.java:41)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.resolveConnectorUnits(ConnectorDescriptorItemUi.java:428)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi.access$3(ConnectorDescriptorItemUi.java:427)
> at org.jboss.tools.central.editors.xpl.ConnectorDescriptorItemUi$6.run(ConnectorDescriptorItemUi.java:309)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {noformat}
> JBT 4.2.0.Beta3b seems not to be affected by this issue.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
[JBoss JIRA] (JBIDE-17700) project archives initialization fails, cascades to server publishing, due to strange classloader
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17700?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17700.
---------------------------------
[~olpf] feel free to check this with respin-b of Beta3:
http://download.jboss.org/jbosstools/updates/staging/jbosstools-4.2.0.Bet...
Or you can wait until Beta3 is released - soon.
And reopen, if you still see issues.
For now, I'm gonna close this issue.
> project archives initialization fails, cascades to server publishing, due to strange classloader
> ------------------------------------------------------------------------------------------------
>
> Key: JBIDE-17700
> URL: https://issues.jboss.org/browse/JBIDE-17700
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge, maven, server
> Environment: Win 7, Eclilpse Luna, JBoss Tools (via market place)
> Reporter: Oliver Pfau
> Assignee: Rob Stryker
> Priority: Critical
> Labels: respin-b
> Fix For: 4.2.0.Beta3
>
> Attachments: jbosstools-diagnostics-20140707141907.zip, jstack.txt, pom.xml
>
>
> When I publish my war to jboss 7.1 the following error occurs:
> An internal error occurred during: "Publishing to JBoss AS 7.1...".
> Could not initialize class de.schlichtherle.io.ArchiveControllers
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 11 months
