[JBoss JIRA] (JBDS-2896) com.jboss.jbds.product.EclipseGenerator application failure in installer
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2896?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2896.
----------------------------
Verified in 7.1.1.GA-v20140303-1841-B672.
> com.jboss.jbds.product.EclipseGenerator application failure in installer
> ------------------------------------------------------------------------
>
> Key: JBDS-2896
> URL: https://issues.jboss.org/browse/JBDS-2896
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 7.1.1.CR1
>
>
> {code}!SESSION 2014-01-16 16:34:55.784 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_51
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -application com.jboss.jbds.product.EclipseGenerator
> Command-line arguments: -application com.jboss.jbds.product.EclipseGenerator -clean
> !ENTRY org.eclipse.osgi 4 0 2014-01-16 16:34:57.716
> !MESSAGE Application error
> !STACK 1
> java.lang.RuntimeException: Application "com.jboss.jbds.product.EclipseGenerator" could not be found in the registry. The applications available are: com.jboss.jbds.p2.director, org.eclipse.equinox.app.error, org.eclipse.equinox.p2.director, org.eclipse.equinox.p2.garbagecollector.application, org.eclipse.equinox.p2.publisher.InstallPublisher, org.eclipse.equinox.p2.publisher.EclipseGenerator, org.eclipse.equinox.p2.publisher.ProductPublisher, org.eclipse.equinox.p2.publisher.FeaturesAndBundlesPublisher, org.eclipse.equinox.p2.repository.repo2runnable, org.eclipse.equinox.p2.repository.metadataverifier, org.eclipse.equinox.p2.artifact.repository.mirrorApplication, org.eclipse.equinox.p2.metadata.repository.mirrorApplication.
> at org.eclipse.equinox.internal.app.EclipseAppContainer.startDefaultApp(EclipseAppContainer.java:248)
> at org.eclipse.equinox.internal.app.MainApplicationLauncher.run(MainApplicationLauncher.java:29)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426){code}
> Installer could not run this application becasue it is trying to start it inside p2 director, just installed product should be used instead.
--
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, 1 month
[JBoss JIRA] (JBIDE-15788) Download runtime wizard shouldn't complain if install folder doesn't exist
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15788?page=com.atlassian.jira.plugi... ]
Rob Stryker resolved JBIDE-15788.
---------------------------------
Resolution: Done
Workflow will not be rewritten for maintenance (already mostly out the door already). Feel free to clone for master if you wish ;) I can investigate the possibility while working on the zero-dollar subscription stuff.
> Download runtime wizard shouldn't complain if install folder doesn't exist
> --------------------------------------------------------------------------
>
> Key: JBIDE-15788
> URL: https://issues.jboss.org/browse/JBIDE-15788
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: runtime-detection, server
> Affects Versions: 4.1.1.Alpha2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Fix For: 4.1.2.CR1
>
> Attachments: cr1-nonexistent-folder.png, install_folder_must_exist.png
>
>
> If the install folder is missing, the download runtime wizard should cope with it, instead of displaying an error (i.e. create the missing folders when necessary)
> - assert no EAP/AS7 are installed
> - create a new html5 project from central
> - click download and install for the server requirement
> - enter a non-existing location for the install folder
> !install_folder_must_exist.png!
--
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, 1 month
[JBoss JIRA] (JBIDE-16699) create drools features overview for tools.jboss.org
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-16699:
-------------------------------------------
Summary: create drools features overview for tools.jboss.org
Key: JBIDE-16699
URL: https://issues.jboss.org/browse/JBIDE-16699
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: website
Reporter: Max Rydahl Andersen
Fix For: 4.2.0.Beta1
Create a features/drools.adoc in jbosstools-website describing the main/cool features
We are refreshing jboss.org/tools (new name: tools.jboss.org) and one of the areas on the new website is a features overview page to let visitors know what features are actually covered in jboss tools.
You can see the current list at http://tools-stg.jboss.org/features/ following the pattern of component/project logo + component name + "tag line".
And then individual pages like http://tools-stg.jboss.org/features/openshift.html which follows the pattern of alternating paragraph + image/screenshot with title/tagline + description for each main feature.
It would be great if you could help create this page for your component.
The process is as follows:
git@github.com:jbosstools/jbosstools-website.git
cd jbosstools-website/features
create componentname.adoc (use i.e. openshift.adoc as inspiration with respect to header names)
Submit this page and related images as pullrequest
The expected launch of the site is end of march so the sooner the better :)
--
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, 1 month
[JBoss JIRA] (JBIDE-14964) LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14964?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-14964:
---------------------------------------------
okey - if you can confirm its no longer an issue I would like to close this jira since I honestly can't see a good way of fixing it if jrebel wont allow automatic publishing.
btw. please note we added JBIDE-14999 just for you too ;)
> LiveReload doesn't reload when JRebel is used, because resources are "never published automatically"
> ----------------------------------------------------------------------------------------------------
>
> Key: JBIDE-14964
> URL: https://issues.jboss.org/browse/JBIDE-14964
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: livereload
> Affects Versions: 4.1.0.Beta1
> Reporter: Lukáš Fryč
> Assignee: Xavier Coulon
> Priority: Critical
> Fix For: 4.2.x
>
>
> When JRebel is used together with LiveReload, "Never Publish Automatically" needs to be turned on in Publishing setup of Server Runtime (AS/EAP) settings.
> In this mode, LiveReload does not work, because new resources are never published according to the IDE.
> However JRebel reloads those resources in a background.
> ----
> In the opposite case ("Automatically publish after resource change"), I'm getting "Concurrent resource modification" error occasionally which might not be related to JRebel usage.
--
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, 1 month
[JBoss JIRA] (JBIDE-15071) Remove the "Update Modules States" message from the status bar
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15071?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-15071:
---------------------------------------
[~xcoulon], [~rob.stryker] how often does this check occur? I've been waiting for 5 minutes or so and still haven't seen it in progress view after enabling system jobs in the view. I have the html5 project deployed on a running EAP 6.2 server.
> Remove the "Update Modules States" message from the status bar
> --------------------------------------------------------------
>
> Key: JBIDE-15071
> URL: https://issues.jboss.org/browse/JBIDE-15071
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: server
> Affects Versions: 4.1.0.CR1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.1.2.CR1, 4.2.0.Alpha2
>
>
> Sometimes, the server adapter calls the server to check if all modules are deployed. This operation can take a few seconds and the status bar displays a message. As a user, I believe that I should wait until this operation is done, which is a bit annoying
--
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, 1 month
[JBoss JIRA] (JBDS-2895) org.eclipse.core.net bundle is not included in p2director
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBDS-2895?page=com.atlassian.jira.plugin.... ]
Pavol Srna closed JBDS-2895.
----------------------------
Verified in 7.1.1.GA-v20140303-1841-B672.
> org.eclipse.core.net bundle is not included in p2director
> ---------------------------------------------------------
>
> Key: JBDS-2895
> URL: https://issues.jboss.org/browse/JBDS-2895
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 7.1.0.GA
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 7.1.1.CR1
>
>
> Missing bundle triggers ClassNotFoundExceptions during installation:
> {code}!ENTRY org.eclipse.ecf.provider.filetransfer 4 0 2014-01-16 16:34:37.018
> !MESSAGE org.eclipse.core.runtime.Status[plugin=org.eclipse.ecf.provider.filetransfer;code=4;message=Warning: Platform proxy API not available;severity2;exception=java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService;children=[]]
> !STACK 0
> java.lang.NoClassDefFoundError: org/eclipse/core/net/proxy/IProxyService
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.setupProxies(AbstractRetrieveFileTransfer.java:946)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:878)
> at org.eclipse.ecf.provider.filetransfer.retrieve.AbstractRetrieveFileTransfer.sendRetrieveRequest(AbstractRetrieveFileTransfer.java:570)
> at org.eclipse.ecf.provider.filetransfer.retrieve.MultiProtocolRetrieveAdapter.sendRetrieveRequest(MultiProtocolRetrieveAdapter.java:106)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.sendRetrieveRequest(FileReader.java:422)
> at org.eclipse.equinox.internal.p2.transport.ecf.FileReader.readInto(FileReader.java:355)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:101)
> at org.eclipse.equinox.internal.p2.transport.ecf.RepositoryTransport.download(RepositoryTransport.java:156)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:668)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.downloadArtifact(SimpleArtifactRepository.java:590)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:723)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.getArtifact(MirrorRequest.java:287)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transferSingle(MirrorRequest.java:267)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.transfer(MirrorRequest.java:208)
> at org.eclipse.equinox.internal.p2.artifact.repository.MirrorRequest.perform(MirrorRequest.java:162)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.SimpleArtifactRepository.getArtifact(SimpleArtifactRepository.java:707)
> at org.eclipse.equinox.internal.p2.artifact.repository.simple.DownloadJob.run(DownloadJob.java:63)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> Caused by: java.lang.ClassNotFoundException: org.eclipse.core.net.proxy.IProxyService cannot be found by org.eclipse.ecf.provider.filetransfer_3.2.0.v20130604-1622
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:501)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:421)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:412)
> at org.eclipse.osgi.internal.baseadaptor.DefaultClassLoader.loadClass(DefaultClassLoader.java:107)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:358)
> ... 18 more{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, 1 month
[JBoss JIRA] (JBIDE-13727) Enable generation of tests for Seam components
by Tomas Remes (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13727?page=com.atlassian.jira.plugi... ]
Tomas Remes commented on JBIDE-13727:
-------------------------------------
Hey Alexey, any updates on this?
> Enable generation of tests for Seam components
> ----------------------------------------------
>
> Key: JBIDE-13727
> URL: https://issues.jboss.org/browse/JBIDE-13727
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: seam2
> Affects Versions: 4.0.0.Final, 4.1.0.Beta1
> Environment: JBDS 6.0.0.GA, JBDS 7.0.0.Beta1. JBDS 7.1.0.GA
> Reporter: Tomas Remes
> Assignee: Alexey Kazakov
> Fix For: 4.2.x
>
>
> Currently the test generation for Seam Action, Form is disabled (but not properly - see JBIDE-13596) because of previous Seam version (I guess 2.3.0.Final). In latest Seam version test can be already generated by seam-gen and are even valid and usable.
> JBDS should enable and support this functionality again.
--
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, 1 month
[JBoss JIRA] (JBIDE-12109) JMX connection to AS7/EAP6 not working if server started with Java 1.7
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12109?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-12109.
---------------------------------
Cannot replicate. Closing. Verified in JBDS 7.1.1.CR1 B672
> JMX connection to AS7/EAP6 not working if server started with Java 1.7
> ----------------------------------------------------------------------
>
> Key: JBIDE-12109
> URL: https://issues.jboss.org/browse/JBIDE-12109
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 3.3.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v20120605-2229-H183-CR1.jar
> Mac OS X 10.7 Lion
> Reporter: Martin Malina
> Assignee: Martin Malina
> Fix For: 4.1.1.Final
>
>
> When you set up your AS7/EAP6 server to use Java 1.7 runtime, the tooling fails to connect to the server via JMX. The error in the log is:
> {code}
> !ENTRY org.jboss.ide.eclipse.as.jmx.integration 4 0 2012-06-06 12:17:52.897
> !MESSAGE Error connecting to jmx for server jboss-eap-6.0.0.CR1
> !STACK 1
> org.jboss.tools.jmx.core.JMXException: Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:78)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> Caused by: java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
> ... 6 more
> !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-06-06 12:17:52.897
> !MESSAGE Unable to reach JBoss instance. Please ensure your server is up and exposes its management ports via the -Djboss.bind.address.management=yourwebsite.com system property
> !STACK 0
> java.lang.RuntimeException: Operation failed with status WAITING
> at org.jboss.remotingjmx.RemotingConnector.internalConnect(RemotingConnector.java:168)
> at org.jboss.remotingjmx.RemotingConnector.connect(RemotingConnector.java:94)
> at javax.management.remote.JMXConnectorFactory.connect(JMXConnectorFactory.java:248)
> at org.jboss.ide.eclipse.as.jmx.integration.JBoss71ServerConnection.createConnection(JBoss71ServerConnection.java:67)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:138)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:122)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:111)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.connectToStartedServer(JBossServerConnection.java:221)
> at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection$1.run(JBossServerConnection.java:213)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
> {code}
> This has several consequences:
> - server cannot be connected in MBean Explorer
> - management startup poller does not work and hence the server keeps starting forever until it reaches timeout (and then it tries to stop the server, but fails to do so - see below)
> - server fails to stop because it seems it tries to do so using management service, second attempt kills the process successfully
> Unfortunately I didn't catch this earlier. AS7/EAP6 with Java 1.7 worked for me in JBDS in the past, but that was probably before the jmx connection started working correctly at all.
--
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, 1 month