|
»
»
»
[mule-jira] Created: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
|
View:
New views
6 Messages
—
Rating Filter:
Alert me
|
 |
[mule-jira] Created: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
by JIRA no-reply@mulesource.com
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message Allow target execution to know the workspace from which it was launched ----------------------------------------------------------------------- Key: MULEIDE-160 URL: http://www.mulesource.org/jira/browse/MULEIDE-160 Project: Mule IDE Issue Type: New Feature Components: Deployment Affects Versions: 2.0 Reporter: Francis Upton Assignee: Jesper Steen Møller Sometimes it is desirable for the code running in the Mule configuration being launched to know the workspace associated with the IDE. For example, some transformers may wish to get example documents from the workspace associated with the IDE. So the workspace location and the fact that we are running in development mode should be passed to the Mule configuration being launched. This can be accomplished by setting the osgi.instance.area and osgi.dev system properties. A patch is provided for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://www.mulesource.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MuleForge Dev" group. To post to this group, send email to muleforgedev@... To unsubscribe from this group, send email to muleforgedev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
[mule-jira] Updated: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
by JIRA no-reply@mulesource.com
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://www.mulesource.org/jira/browse/MULEIDE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Francis Upton updated MULEIDE-160: ---------------------------------- Attachment: launch.txt Patch to set the system properties. This has been tested on the muleide-2.0.0 branch. > Allow target execution to know the workspace from which it was launched > ----------------------------------------------------------------------- > > Key: MULEIDE-160 > URL: http://www.mulesource.org/jira/browse/MULEIDE-160 > Project: Mule IDE > Issue Type: New Feature > Components: Deployment > Affects Versions: 2.0 > Reporter: Francis Upton > Assignee: Jesper Steen Møller > Attachments: launch.txt > > > Sometimes it is desirable for the code running in the Mule configuration being launched to know the workspace associated with the IDE. For example, some transformers may wish to get example documents from the workspace associated with the IDE. So the workspace location and the fact that we are running in development mode should be passed to the Mule configuration being launched. This can be accomplished by setting the osgi.instance.area and osgi.dev system properties. > A patch is provided for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://www.mulesource.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MuleForge Dev" group. To post to this group, send email to muleforgedev@... To unsubscribe from this group, send email to muleforgedev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
[mule-jira] Commented: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
by JIRA no-reply@mulesource.com
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://www.mulesource.org/jira/browse/MULEIDE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32282#action_32282 ] Francis Upton commented on MULEIDE-160: --------------------------------------- I think I'm a committer on the Mule IDE, so I can commit this somewhere, but I need some guidance to where so I don't mess things up. > Allow target execution to know the workspace from which it was launched > ----------------------------------------------------------------------- > > Key: MULEIDE-160 > URL: http://www.mulesource.org/jira/browse/MULEIDE-160 > Project: Mule IDE > Issue Type: New Feature > Components: Deployment > Affects Versions: 2.0 > Reporter: Francis Upton > Assignee: Jesper Steen Møller > Attachments: launch.txt > > > Sometimes it is desirable for the code running in the Mule configuration being launched to know the workspace associated with the IDE. For example, some transformers may wish to get example documents from the workspace associated with the IDE. So the workspace location and the fact that we are running in development mode should be passed to the Mule configuration being launched. This can be accomplished by setting the osgi.instance.area and osgi.dev system properties. > A patch is provided for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://www.mulesource.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MuleForge Dev" group. To post to this group, send email to muleforgedev@... To unsubscribe from this group, send email to muleforgedev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
[mule-jira] Updated: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
by JIRA no-reply@mulesource.com
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://www.mulesource.org/jira/browse/MULEIDE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dirk Olmes updated MULEIDE-160: ------------------------------- Priority: Major (was: To be reviewed) Assignee: Dirk Olmes (was: Jesper Steen Møller) Fix Version/s: 2.0.1 > Allow target execution to know the workspace from which it was launched > ----------------------------------------------------------------------- > > Key: MULEIDE-160 > URL: http://www.mulesource.org/jira/browse/MULEIDE-160 > Project: Mule IDE > Issue Type: New Feature > Components: Deployment > Affects Versions: 2.0 > Reporter: Francis Upton > Assignee: Dirk Olmes > Priority: Major > Fix For: 2.0.1 > > Attachments: launch.txt > > > Sometimes it is desirable for the code running in the Mule configuration being launched to know the workspace associated with the IDE. For example, some transformers may wish to get example documents from the workspace associated with the IDE. So the workspace location and the fact that we are running in development mode should be passed to the Mule configuration being launched. This can be accomplished by setting the osgi.instance.area and osgi.dev system properties. > A patch is provided for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://www.mulesource.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MuleForge Dev" group. To post to this group, send email to muleforgedev@... To unsubscribe from this group, send email to muleforgedev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
[mule-jira] Commented: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
by JIRA no-reply@mulesource.com
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://www.mulesource.org/jira/browse/MULEIDE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=32283#action_32283 ] Dirk Olmes commented on MULEIDE-160: ------------------------------------ http://fisheye.muleforge.org/changelog/mule-ide/?cs=549 > Allow target execution to know the workspace from which it was launched > ----------------------------------------------------------------------- > > Key: MULEIDE-160 > URL: http://www.mulesource.org/jira/browse/MULEIDE-160 > Project: Mule IDE > Issue Type: New Feature > Components: Deployment > Affects Versions: 2.0 > Reporter: Francis Upton > Assignee: Dirk Olmes > Priority: Major > Fix For: 2.0.1 > > Attachments: launch.txt > > > Sometimes it is desirable for the code running in the Mule configuration being launched to know the workspace associated with the IDE. For example, some transformers may wish to get example documents from the workspace associated with the IDE. So the workspace location and the fact that we are running in development mode should be passed to the Mule configuration being launched. This can be accomplished by setting the osgi.instance.area and osgi.dev system properties. > A patch is provided for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://www.mulesource.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MuleForge Dev" group. To post to this group, send email to muleforgedev@... To unsubscribe from this group, send email to muleforgedev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en -~----------~----~----~----~------~----~------~--~--- |
|
|
[mule-jira] Closed: (MULEIDE-160) Allow target execution to know the workspace from which it was launched
by JIRA no-reply@mulesource.com
::
Rate this Message:
Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message [ http://www.mulesource.org/jira/browse/MULEIDE-160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dirk Olmes closed MULEIDE-160. ------------------------------ Resolution: Fixed > Allow target execution to know the workspace from which it was launched > ----------------------------------------------------------------------- > > Key: MULEIDE-160 > URL: http://www.mulesource.org/jira/browse/MULEIDE-160 > Project: Mule IDE > Issue Type: New Feature > Components: Deployment > Affects Versions: 2.0 > Reporter: Francis Upton > Assignee: Dirk Olmes > Priority: Major > Fix For: 2.0.1 > > Attachments: launch.txt > > > Sometimes it is desirable for the code running in the Mule configuration being launched to know the workspace associated with the IDE. For example, some transformers may wish to get example documents from the workspace associated with the IDE. So the workspace location and the fact that we are running in development mode should be passed to the Mule configuration being launched. This can be accomplished by setting the osgi.instance.area and osgi.dev system properties. > A patch is provided for this simple change. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://www.mulesource.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "MuleForge Dev" group. To post to this group, send email to muleforgedev@... To unsubscribe from this group, send email to muleforgedev+unsubscribe@... For more options, visit this group at http://groups.google.com/group/muleforgedev?hl=en -~----------~----~----~----~------~----~------~--~--- |
| Free embeddable forum powered by Nabble | Forum Help |
