[JBoss JIRA] Created: (JBIDE-687) Server should put it's deployable modules on its runtime/debug classpath
8:36 p.m.
Server should put it's deployable modules on its runtime/debug classpath
------------------------------------------------------------------------
Key: JBIDE-687
URL: http://jira.jboss.com/jira/browse/JBIDE-687
Project: JBoss Tools
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Rob Stryker
Priority: Critical
Fix For: 2.0.0.Beta4
when running in debug mode itfeels strange that I have to manually add my project the
first time i hit a breakpoint....couldn't the server update its launchconfig or
something to make sure it's already ready ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:39 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-687) Server should put it's deployable modules on its runtime/debug classpath
[ http://jira.jboss.com/jira/browse/JBIDE-687?page=comments#action_12371825 ]
Max Andersen commented on JBIDE-687:
------------------------------------
As discussed on IRC:
launchconfiguration types can have a custom source path computer associated with them.
That is done by adding e.g.
sourcePathComputerId="org.eclipse.jst.server.tomcat.core.sourcePathComputer"
to
<launchConfigurationType
category="JBoss"
delegate="org.jboss.ide.eclipse.as.core.server.JBossServerLaunchConfiguration"
id="org.jboss.ide.eclipse.as.core.server.launchConfiguration"
modes="run,debug"
name="JBoss Application Server"
public="true"
sourceLocatorId="org.eclipse.jdt.launching.sourceLocator.JavaSourceLookupDirector"/>
the exact sourcePathComputerId should probably be our own to make sure we can actually
control it.
Server should put it's deployable modules on its runtime/debug
classpath
------------------------------------------------------------------------
Key: JBIDE-687
URL: http://jira.jboss.com/jira/browse/JBIDE-687
Project: JBoss Tools
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Rob Stryker
Priority: Critical
Fix For: 2.0.0.Beta4
when running in debug mode itfeels strange that I have to manually add my project the
first time i hit a breakpoint....couldn't the server update its launchconfig or
something to make sure it's already ready ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:50 p.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-687) Server should put it's deployable modules on its runtime/debug classpath
[ http://jira.jboss.com/jira/browse/JBIDE-687?page=all ]
Rob Stryker resolved JBIDE-687.
-------------------------------
Resolution: Done
Committed to svn
Server should put it's deployable modules on its runtime/debug
classpath
------------------------------------------------------------------------
Key: JBIDE-687
URL: http://jira.jboss.com/jira/browse/JBIDE-687
Project: JBoss Tools
Issue Type: Feature Request
Components: JBossAS
Affects Versions: 2.0.0.Beta3
Reporter: Max Andersen
Assigned To: Rob Stryker
Priority: Critical
Fix For: 2.0.0.Beta4
when running in debug mode itfeels strange that I have to manually add my project the
first time i hit a breakpoint....couldn't the server update its launchconfig or
something to make sure it's already ready ?
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6808
days inactive
6815
days old
jbosstools-issues@lists.jboss.org
2 comments
2 participants
participants (2)
-
Max Andersen (JIRA) -
Rob Stryker (JIRA)