[JBoss JIRA] (JBIDE-18094) Do not force restart modules when server is run in debug mode
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18094?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18094:
-------------------------------------
> How can I get the hot code dialog? I've never seen it.
To get the hotcode dialog, you should change a method signature, or add a member variable to a class.... basically anything that would normally cause a hotcode replace failure.
> Do not force restart modules when server is run in debug mode
> -------------------------------------------------------------
>
> Key: JBIDE-18094
> URL: https://issues.jboss.org/browse/JBIDE-18094
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Labels: affects_documentation, new_and_noteworthy
> Fix For: 4.2.0.CR1
>
> Attachments: initialsuggestionfor_hotcodefailurereplace.bmml, initialsuggestionfor_hotcodefailurereplace.png, JBIDE-18094.png, JBIDE-18094_dialog.png, serversetting.bmml, serversetting.png, update_dialog_based_on_existing_hcr.bmml, update_dialog_based_on_existing_hcr.png
>
>
> The request is that modules should not force-restart when a server is in debug mode. More often than not, a change to a .class file, when the server is in debug mode, does not require any special action or force-restart of the module. The changes to the .class file will be picked up automatically.
> Ideally, we would also detect a hotcode replace failure, and then force-restart the module if possible.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-18128:
--------------------------------
Fix Version/s: 4.2.1.Final
(was: 4.2.0.CR1)
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.1.Final
>
> Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip
>
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
> I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-18128:
-------------------------------------
Since this appears to be a project configuration error, I'm going to move this issue off. I'll mark it as 4.2.1 just so we don't lose the issue.
> Jboss Eclipse Luna plugin doesn't deploy all .class
> ---------------------------------------------------
>
> Key: JBIDE-18128
> URL: https://issues.jboss.org/browse/JBIDE-18128
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: fede pia
> Assignee: Rob Stryker
> Priority: Blocker
> Fix For: 4.2.1.Final
>
> Attachments: 2014-09-04 error.png, 2014-09-04 output.txt, jboss-test.zip, TestJboss-2014-09-03.zip
>
>
> The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException.
> I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random.
> For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean
> As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1.
> I also tried building the war outside Eclipse and deployed manually to JBoss and everything works fine.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17927) Remote EAP 5: empty config dir results in nonworking server
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17927?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-17927.
---------------------------------
Verified in JBDS 8.0.0.CR1 B225
> Remote EAP 5: empty config dir results in nonworking server
> -----------------------------------------------------------
>
> Key: JBIDE-17927
> URL: https://issues.jboss.org/browse/JBIDE-17927
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.2.0.Beta3
> Environment: JBDS 8.0.0.Beta3a B178
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
>
> From JBIDE-17824:
> The default is now "default" even for runtime-less servers. And the validation of "default" is correct. But when I remove that string and click Test, it says ok. When I create the server with empty config string, it will have "--configuration=" in the launch config which will definitely fail.
> I wouldn't complain if the empty field still resulted in default being used (and the Test button would need to work that way too), but perhaps better is to disallow an empty string and also the Test button should return an error.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-14553) Add possibility to enable snapshots for repository
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14553?page=com.atlassian.jira.plugi... ]
Radim Hopp closed JBIDE-14553.
------------------------------
Verified in JBT 4.2.0.CR1. Closing.
> Add possibility to enable snapshots for repository
> --------------------------------------------------
>
> Key: JBIDE-14553
> URL: https://issues.jboss.org/browse/JBIDE-14553
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 4.1.0.Beta1
> Reporter: Rastislav Wagner
> Assignee: Rastislav Wagner
> Labels: new_and_noteworthy
> Fix For: 4.2.0.CR1
>
>
> It would be quite useful if "Add Maven Repository" wizard was able to enable snapshots for repository. Just add some checkbox "Enable snapshots" which would change
> {code}
> <snapshots>
> <enabled>$someValue</enabled>
> <snapshots>
> {code}
> $someValue in settings.xml to true or false for particular repository.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18287) Seam project fails to deploy after IDE restart
by Martin Malina (JIRA)
Martin Malina created JBIDE-18287:
-------------------------------------
Summary: Seam project fails to deploy after IDE restart
Key: JBIDE-18287
URL: https://issues.jboss.org/browse/JBIDE-18287
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: seam2
Affects Versions: 4.2.0.CR1
Reporter: Martin Malina
When you create a seam web project and deploy to EAP 5.2, then stop the server, restart JBDS and start the server again, the project fails to deploy properly:
{code}
10:55:27,380 INFO [config] Initializing Mojarra (1.2_13-b01-FCS) for context '/seamproj'
10:55:27,900 INFO [ServletContextListener] Welcome to Seam 2.2.6.EAP5
10:55:28,862 WARN [PersistentPermissionResolver] no permission store available - please install a PermissionStore with the name 'org.jboss.seam.security.jpaPermissionStore' if persistent permissions are required.
10:55:28,961 INFO [ProfileServiceBootstrap] Loading profile: ProfileKey@6d4879f2[domain=default, server=default, name=default]
10:55:28,962 ERROR [ProfileServiceBootstrap] Failed to load profile: Summary of incomplete deployments (SEE PREVIOUS ERRORS FOR DETAILS):
DEPLOYMENTS MISSING DEPENDENCIES:
Deployment "persistence.unit:unitName=seamproj.war#seamproj" is missing the following dependencies:
Dependency "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" (should be in state "Create", but is actually in state "** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' **")
DEPLOYMENTS IN ERROR:
Deployment "jboss.jca:name=seamprojDatasource,service=DataSourceBinding" is in error due to the following reason(s): ** NOT FOUND Depends on 'jboss.jca:name=seamprojDatasource,service=DataSourceBinding' **
10:55:28,968 INFO [Http11Protocol] Starting Coyote HTTP/1.1 on http-localhost%2F127.0.0.1-8080
10:55:28,982 INFO [AjpProtocol] Starting Coyote AJP/1.3 on ajp-localhost%2F127.0.0.1-8009
10:55:28,988 INFO [ServerImpl] JBoss (Microcontainer) [5.2.0 (build: SVNTag=JBPAPP_5_2_0 date=201211232041)] Started in 15s:311ms
{code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months