[JBoss JIRA] (JBIDE-13772) Provide a dialog to configure the LiveReload embedded server
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-13772:
-------------------------------------
Summary: Provide a dialog to configure the LiveReload embedded server
Key: JBIDE-13772
URL: https://issues.jboss.org/browse/JBIDE-13772
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: JBossAS/Servers
Affects Versions: 4.1.0.Alpha2
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.1.0.Alpha2
Provide a dialog to configure the LiveReload embedded server when the user starts the LiveReload feature from the Server context menu.
--
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, 1 month
[JBoss JIRA] (JBIDE-13335) remove Juno SR1+ performance fix from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13335?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13335:
------------------------------------
Kinda wish you'd said something sooner (during the "issue must sit idle" period between Dec 21 and Mar 1) but yeah, if we need to keep it in there we can. I've only removed the connector from Central; the feature's still on the JBT/JBDS central sites.
Should we put it back into JBT 4.0.1 Central so that users on Eclipse 4.2 or 4.2.1 will see the optional connector?
> remove Juno SR1+ performance fix from Central
> ----------------------------------------------
>
> Key: JBIDE-13335
> URL: https://issues.jboss.org/browse/JBIDE-13335
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: central
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Denis Golovin
> Labels: respin-a
> Fix For: 4.0.1.Final
>
> Attachments: JBIDE13335.patch.JBDS6.0.1.txt
>
>
> For our 4.0.1 release, we will not need this performance tweak because we'll be including Juno SR2, which already includes the patched versions of Eclipse jars.
> Need to therefore, for JBT 4.0.1 and JBDS 6.0.1:
> a) remove the requirements/eclipse/4.2.1.v20121122-0007-patches/ site from Central composite sites (2 places)
> b) remove the connector from discovery plugins' plugin.xml (2 files)
--
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, 1 month
[JBoss JIRA] (JBIDE-13266) Use pack200 to speed up download and install
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13266?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-13266:
----------------------------------------
Aggregation jobs were updated to use pack200 profile.
Works locally and on CI, waiting for new "normal" executions (triggered by a Git commit in a component) to ensure they are published well.
> Use pack200 to speed up download and install
> --------------------------------------------
>
> Key: JBIDE-13266
> URL: https://issues.jboss.org/browse/JBIDE-13266
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: Build/Releng
> Affects Versions: 4.0.0.CR1
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.1.0.Alpha2
>
>
> p2 provides the pack200 stuff, which offers a better compressions for jars, and then that makes downloads faster when installing.
> We should set up our repo to create the pack200'd artifacts.
--
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, 1 month
[JBoss JIRA] (JBIDE-13446) Forge pick-up command throws NPE
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13446?page=com.atlassian.jira.plugi... ]
Martin Malina updated JBIDE-13446:
----------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.x)
Adding a fix for 4.1.0.Alpha2 so that this issue is not forgotten - I think it's a serious problem.
> Forge pick-up command throws NPE
> --------------------------------
>
> Key: JBIDE-13446
> URL: https://issues.jboss.org/browse/JBIDE-13446
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.0.0.Final, 4.1.0.Alpha1
> Environment: OS X Mountain Lion
> Apple JDK 1.6 32bit
> JBDS 6.0.0.GA / JBT master nightly 4.1.0.Alpha1-v20130129-1449-B6053 on Eclipse Kepler M4
> And:
> Fedora 17, JDK 1.7.0_13, JBDS 6.0.0 GA - all 64-bit
> Reporter: Martin Malina
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.0.x, 4.1.0.Alpha2
>
>
> When playing around w/ Ticket Monster [1] I found out that Show in -> Forge console does not work for me on a project or directory in Project Explorer.
> It throws this exception:
> {code}
> [no project] workspace $ set VERBOSE true
> [no project] workspace $ pick-up /Users/rasp/jbossqa/JBDS/nightly-jbt-2013-01-30/workspace/jboss-javaee6-webapp
> java.lang.NullPointerException***ERROR*** Exception encountered: (type "set VERBOSE false" to disable stack traces)
> [no project] workspace $
> at org.apache.maven.RepositoryUtils.getLayout(RepositoryUtils.java:214)
> at org.apache.maven.RepositoryUtils.toRepo(RepositoryUtils.java:200)
> at org.apache.maven.RepositoryUtils.toRepos(RepositoryUtils.java:190)
> at org.apache.maven.project.DefaultProjectBuilder$InternalConfig.<init>(DefaultProjectBuilder.java:662)
> at org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:102)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.getPartialProjectBuildingResult(MavenCoreFacetImpl.java:86)
> at org.jboss.forge.maven.facets.MavenCoreFacetImpl.resolveProperties(MavenCoreFacetImpl.java:304)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.resolveProperties(MavenDependencyFacet.java:393)
> at org.jboss.forge.maven.facets.MavenDependencyFacet.hasEffectiveDependency(MavenDependencyFacet.java:171)
> at org.jboss.forge.shell.project.DependencyInstallerImpl.isInstalled(DependencyInstallerImpl.java:170)
> at org.jboss.forge.git.GitAPIFacet.isInstalled(GitAPIFacet.java:42)
> at org.jboss.forge.project.BaseProject.registerFacet(BaseProject.java:153)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:208)
> at org.jboss.forge.project.services.ProjectFactory.registerSingleFacet(ProjectFactory.java:186)
> at org.jboss.forge.project.services.ProjectFactory.registerFacets(ProjectFactory.java:178)
> at org.jboss.forge.project.services.ProjectFactory.findProjectRecursively(ProjectFactory.java:117)
> at org.jboss.forge.shell.project.ProjectInitializer.doInit(ProjectInitializer.java:91)
> 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:601)
> at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:628)
> at org.jboss.weld.event.EventImpl.fire(EventImpl.java:75)
> at org.jboss.forge.shell.project.CurrentProject.setCurrentResource(CurrentProject.java:80)
> at org.jboss.forge.shell.ShellImpl.setCurrentResource(ShellImpl.java:1239)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.setCurrentResource(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> at org.jboss.forge.shell.plugins.builtin.PickupResourcePlugin.run(PickupResourcePlugin.java:85)
> 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:601)
> at org.jboss.forge.shell.command.Execution.perform(Execution.java:134)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:109)
> at org.jboss.forge.shell.command.fshparser.FSHRuntime.run(FSHRuntime.java:47)
> at org.jboss.forge.shell.ShellImpl$ExecutorThread.run(ShellImpl.java:818)
> at org.jboss.forge.shell.ShellImpl.execute(ShellImpl.java:841)
> at org.jboss.forge.shell.ShellImpl.doShell(ShellImpl.java:631)
> 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:601)
> at org.jboss.weld.bean.proxy.AbstractBeanInstance.invoke(AbstractBeanInstance.java:48)
> at org.jboss.weld.bean.proxy.ProxyMethodHandler.invoke(ProxyMethodHandler.java:125)
> at org.jboss.forge.shell.ShellImpl$Proxy$_$$_WeldClientProxy.doShell(ShellImpl$Proxy$_$$_WeldClientProxy.java)
> 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:601)
> at org.jboss.weld.util.reflection.SecureReflections$13.work(SecureReflections.java:305)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.run(SecureReflectionAccess.java:54)
> at org.jboss.weld.util.reflection.SecureReflectionAccess.runAsInvocation(SecureReflectionAccess.java:163)
> at org.jboss.weld.util.reflection.SecureReflections.invoke(SecureReflections.java:299)
> at org.jboss.weld.introspector.jlr.WeldMethodImpl.invokeOnInstance(WeldMethodImpl.java:188)
> at org.jboss.weld.introspector.ForwardingWeldMethod.invokeOnInstance(ForwardingWeldMethod.java:59)
> at org.jboss.weld.injection.MethodInjectionPoint.invokeOnInstanceWithSpecialValue(MethodInjectionPoint.java:198)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:282)
> at org.jboss.weld.event.ObserverMethodImpl.sendEvent(ObserverMethodImpl.java:265)
> at org.jboss.weld.event.ObserverMethodImpl.notify(ObserverMethodImpl.java:234)
> at org.jboss.weld.manager.BeanManagerImpl.notifyObservers(BeanManagerImpl.java:635)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:622)
> at org.jboss.weld.manager.BeanManagerImpl.fireEvent(BeanManagerImpl.java:616)
> at org.jboss.forge.shell.Bootstrap$1.run(Bootstrap.java:172)
> at java.lang.Thread.run(Thread.java:722)
> {code}
> This happens in both JBDS 6 and JBT 4.1 nightly, but not in JBDS 5. It's probably only reproducible on Mac - psrna verified this on Linux today and it worked for him. I tried two different instances of JBDS 6 and one instance of JBT 4.1.0.Alpha1 nightly installed on Eclipse Kepler M4.
> Please let me know if I should create a FORGE issue.
> The forge runtime versions:
> JBDS 6: org.jboss.tools.forge.runtime_1.1.0.Final-v20121205-1934-B69
> JBT nightly: org.jboss.tools.forge.runtime_1.2.0.Alpha1-v20130128-1407-B204
> [1] http://www.jboss.org/jdf/examples/ticket-monster/tutorial/Introduction/#_...
--
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, 1 month
[JBoss JIRA] (JBIDE-13768) Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13768?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-13768:
----------------------------------------
Component/s: JBossAS/Servers
> Server Fails to Start (Kinda) - Mixing of JRE6/JDK7 on Mac OS X
> ---------------------------------------------------------------
>
> Key: JBIDE-13768
> URL: https://issues.jboss.org/browse/JBIDE-13768
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: JBossAS/Servers
> Reporter: Burr Sutter
> Attachments: Error_Failed_to_start.png, failed_start.png, Installation1.png, runtime_JDK_7_selection.png, server_state_detectors.png
>
>
> My Mac has both the Apple Java 6 and Oracle Java 7 installed.
> If I take the defaults from the JBDS Installer, allowing it to pick a Java 6 JRE, but then manually adding a server with Java 7 - the IDE fails to see that the server started.
> Installation1.png - a screenshot of the defaults selected by the installer.
> This places the following in my jbdevstudio.ini
> -vm
> /Library/Internet Plug-Ins/JavaAppletPlugin.plugin/Contents/Home/bin/java
> and in About - Installation Details - Configuration:
> -vm
> /System/Library/Frameworks/JavaVM.framework
> Adding a New Server (EAP 6 or 6.1) - but selecting Java 7 for the Runtime - is where the IDE fails to see that the server has started (runtime_JDK_7_selection.png)
> The result is a failed start (failed_start.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
13 years, 1 month
[JBoss JIRA] (JBIDE-13769) Cannot import OpenShift maven project twice: "Could not import project null"
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13769?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13769:
-------------------------------------
Steps to Reproduce:
# ASSERT: make sure you have a java/maven application on OpenShift (ex. jbossas-7, jbosseap-6, springeap-6)
# EXEC: import your application to your workspace via Import-wizard
# EXEC: once it's imported, try to import it a 2nd time: You have to provide a custom git clone location
Result
The import starts, the cloning happens, but when the maven import is executed, the wizard reports that the maven project *null* could not be imported:
!could-not-maven-import-null.png!
was:
# ASSERT: make sure you have a java/maven application on OpenShift (ex. jbossas-7, jbosseap-6, springeap-6)
# EXEC: import your application to your workspace via Import-wizard
# EXEC: once it's imported, try to import it a 2nd time: You have to provide a custom git clone location
Result
The import starts, the cloning happens, but when the maven import is executed, the wizard reports that the maven project *null* could not be imported:
!could-not-maven-import-null.png!
!could-not-maven-import-null.png!
> Cannot import OpenShift maven project twice: "Could not import project null"
> ----------------------------------------------------------------------------
>
> Key: JBIDE-13769
> URL: https://issues.jboss.org/browse/JBIDE-13769
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.1.0.Alpha2
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.1.x
>
> Attachments: could-not-maven-import-null.png
>
>
> You cannot import an OpenShift java/maven project twice since the project name has to be unique within the very same Eclipse workspace. The OpenShift import wizard errors while importing and reports that it could not import the maven project *null*.
> !could-not-maven-import-null.png!
> We cannot change the wizard to error before importing since we have to clone the application repo and look into the pom to find out about the name clash.
> Nevertheless, we should fix the lacking error message that's missing the project name.
--
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, 1 month