Home » Modeling » EMF "Technology" (Ecore Tools, EMFatic, etc) » Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow?
| Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow? [message #487691] |
Thu, 24 September 2009 03:39  |
Eclipse User |
|
|
|
Hi Michael,
as this is related to the MWE launcher I added the emft newsgroup.
the workspace refresh is hard coded so you cannot deactivate it in the
launch configuration. What you could do is to start the workflow using a
plain Java Application launch configuration.
All you need to do is start 'org.eclipse.emf.mwe.core.WorkflowRunner'
and pass the workflow file as the first parameter.
Note, that usually a refresh is only resources consuming if many files
are out of sync, i.e. have changed externally. You could try to minimize
this by avoid overwriting existing files if nothing has changed.
Cheers,
Sven
Michael Scharf schrieb:
> I have a huge workspace (>30.000 files).
>
> A refresh of the workspace can take up to 10 minutes
> (if the files are not in the disc cache because windows
> in not really good at that)! Even the second time it
> takes 15 seconds.
>
> Is there a way to only refresh the projects that
> have changed?
>
> I understand that it is difficult to figure out
> what has changed, but it would be great to
> specify in the workflow what to update.
>
>
> Michael
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
|
|
| |
| Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow? [message #487920 is a reply to message #487856] |
Thu, 24 September 2009 15:38  |
| Eclipse User |
|
|
|
Hi Stefan,
> I think the problem with your solution is, that it is not easy at all to
> provide a correct class path for this simple plain java application.
Either way (workflow launch or java application launch) you need a
correctly set up classpath. We put the things on the classpath because
they are needed. By leveraging OSGi and it's support for transitive
dependencies this has become fairly easy to manage (IMHO).
However, I admit that if you don't use OSGi but have to set up the
classpath manually it's not that nice...
> In
> my opinion it would be nice to have an eclipse application to run a
> workflow, that would allow to launch workflows from and within other
> tools without bothering about classpath issues (that are already
> resolved by the osgi container).
You'ld still have to define the right dependencies (i.e. classpath) for
your specific workflow.
> Btw. the most annoying thing about this workspace refresh is, that it
> occurs not only at the end of workflow launches but after all other
> types of launches as well.
It only occurs after workflow launches.
What types of launches do you refer to?
Sven
> Stefan
>
>
> Sven Efftinge wrote:
>> Hi Michael,
>>
>> as this is related to the MWE launcher I added the emft newsgroup.
>>
>> the workspace refresh is hard coded so you cannot deactivate it in the
>> launch configuration. What you could do is to start the workflow using
>> a plain Java Application launch configuration.
>>
>> All you need to do is start 'org.eclipse.emf.mwe.core.WorkflowRunner'
>> and pass the workflow file as the first parameter.
>>
>> Note, that usually a refresh is only resources consuming if many files
>> are out of sync, i.e. have changed externally. You could try to
>> minimize this by avoid overwriting existing files if nothing has changed.
>>
>> Cheers,
>> Sven
>>
>>
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
|
|
|
| Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow? [message #490078 is a reply to message #487920] |
Wed, 07 October 2009 05:10 |
| Eclipse User |
|
|
|
Sven Efftinge wrote:
> Hi Stefan,
>
>> I think the problem with your solution is, that it is not easy at all
>> to provide a correct class path for this simple plain java application.
>
> Either way (workflow launch or java application launch) you need a
> correctly set up classpath. We put the things on the classpath because
> they are needed. By leveraging OSGi and it's support for transitive
> dependencies this has become fairly easy to manage (IMHO).
> However, I admit that if you don't use OSGi but have to set up the
> classpath manually it's not that nice...
>
>> In my opinion it would be nice to have an eclipse application to run a
>> workflow, that would allow to launch workflows from and within other
>> tools without bothering about classpath issues (that are already
>> resolved by the osgi container).
>
> You'ld still have to define the right dependencies (i.e. classpath) for
> your specific workflow.
>
>> Btw. the most annoying thing about this workspace refresh is, that it
>> occurs not only at the end of workflow launches but after all other
>> types of launches as well.
>
> It only occurs after workflow launches.
> What types of launches do you refer to?
I mean actually ALL types of launches. Once you were brave enough to
start a workflow you will get these annoying refreshes after all other
launches (e.g. Eclipse Applications) as well.
>
> Sven
>
>
>> Stefan
>>
>>
>> Sven Efftinge wrote:
>>> Hi Michael,
>>>
>>> as this is related to the MWE launcher I added the emft newsgroup.
>>>
>>> the workspace refresh is hard coded so you cannot deactivate it in
>>> the launch configuration. What you could do is to start the workflow
>>> using a plain Java Application launch configuration.
>>>
>>> All you need to do is start 'org.eclipse.emf.mwe.core.WorkflowRunner'
>>> and pass the workflow file as the first parameter.
>>>
>>> Note, that usually a refresh is only resources consuming if many
>>> files are out of sync, i.e. have changed externally. You could try to
>>> minimize this by avoid overwriting existing files if nothing has
>>> changed.
>>>
>>> Cheers,
>>> Sven
>>>
>>>
>
|
|
|
| Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow? [message #621392 is a reply to message #487691] |
Thu, 24 September 2009 11:14 |
| Eclipse User |
|
|
|
Hi Sven,
I think the problem with your solution is, that it is not easy at all to
provide a correct class path for this simple plain java application. In
my opinion it would be nice to have an eclipse application to run a
workflow, that would allow to launch workflows from and within other
tools without bothering about classpath issues (that are already
resolved by the osgi container).
Btw. the most annoying thing about this workspace refresh is, that it
occurs not only at the end of workflow launches but after all other
types of launches as well.
Stefan
Sven Efftinge wrote:
> Hi Michael,
>
> as this is related to the MWE launcher I added the emft newsgroup.
>
> the workspace refresh is hard coded so you cannot deactivate it in the
> launch configuration. What you could do is to start the workflow using a
> plain Java Application launch configuration.
>
> All you need to do is start 'org.eclipse.emf.mwe.core.WorkflowRunner'
> and pass the workflow file as the first parameter.
>
> Note, that usually a refresh is only resources consuming if many files
> are out of sync, i.e. have changed externally. You could try to minimize
> this by avoid overwriting existing files if nothing has changed.
>
> Cheers,
> Sven
>
>
|
|
|
| Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow? [message #621393 is a reply to message #487856] |
Thu, 24 September 2009 15:38 |
| Eclipse User |
|
|
|
Hi Stefan,
> I think the problem with your solution is, that it is not easy at all to
> provide a correct class path for this simple plain java application.
Either way (workflow launch or java application launch) you need a
correctly set up classpath. We put the things on the classpath because
they are needed. By leveraging OSGi and it's support for transitive
dependencies this has become fairly easy to manage (IMHO).
However, I admit that if you don't use OSGi but have to set up the
classpath manually it's not that nice...
> In
> my opinion it would be nice to have an eclipse application to run a
> workflow, that would allow to launch workflows from and within other
> tools without bothering about classpath issues (that are already
> resolved by the osgi container).
You'ld still have to define the right dependencies (i.e. classpath) for
your specific workflow.
> Btw. the most annoying thing about this workspace refresh is, that it
> occurs not only at the end of workflow launches but after all other
> types of launches as well.
It only occurs after workflow launches.
What types of launches do you refer to?
Sven
> Stefan
>
>
> Sven Efftinge wrote:
>> Hi Michael,
>>
>> as this is related to the MWE launcher I added the emft newsgroup.
>>
>> the workspace refresh is hard coded so you cannot deactivate it in the
>> launch configuration. What you could do is to start the workflow using
>> a plain Java Application launch configuration.
>>
>> All you need to do is start 'org.eclipse.emf.mwe.core.WorkflowRunner'
>> and pass the workflow file as the first parameter.
>>
>> Note, that usually a refresh is only resources consuming if many files
>> are out of sync, i.e. have changed externally. You could try to
>> minimize this by avoid overwriting existing files if nothing has changed.
>>
>> Cheers,
>> Sven
>>
>>
--
Need professional support for Eclipse Modeling?
Go visit: http://xtext.itemis.com
|
|
|
| Re: [MWE] Is there a way to prevent to refresh the *entire* workspace after the run of a workflow? [message #621434 is a reply to message #487920] |
Wed, 07 October 2009 05:10 |
| Eclipse User |
|
|
|
Sven Efftinge wrote:
> Hi Stefan,
>
>> I think the problem with your solution is, that it is not easy at all
>> to provide a correct class path for this simple plain java application.
>
> Either way (workflow launch or java application launch) you need a
> correctly set up classpath. We put the things on the classpath because
> they are needed. By leveraging OSGi and it's support for transitive
> dependencies this has become fairly easy to manage (IMHO).
> However, I admit that if you don't use OSGi but have to set up the
> classpath manually it's not that nice...
>
>> In my opinion it would be nice to have an eclipse application to run a
>> workflow, that would allow to launch workflows from and within other
>> tools without bothering about classpath issues (that are already
>> resolved by the osgi container).
>
> You'ld still have to define the right dependencies (i.e. classpath) for
> your specific workflow.
>
>> Btw. the most annoying thing about this workspace refresh is, that it
>> occurs not only at the end of workflow launches but after all other
>> types of launches as well.
>
> It only occurs after workflow launches.
> What types of launches do you refer to?
I mean actually ALL types of launches. Once you were brave enough to
start a workflow you will get these annoying refreshes after all other
launches (e.g. Eclipse Applications) as well.
>
> Sven
>
>
>> Stefan
>>
>>
>> Sven Efftinge wrote:
>>> Hi Michael,
>>>
>>> as this is related to the MWE launcher I added the emft newsgroup.
>>>
>>> the workspace refresh is hard coded so you cannot deactivate it in
>>> the launch configuration. What you could do is to start the workflow
>>> using a plain Java Application launch configuration.
>>>
>>> All you need to do is start 'org.eclipse.emf.mwe.core.WorkflowRunner'
>>> and pass the workflow file as the first parameter.
>>>
>>> Note, that usually a refresh is only resources consuming if many
>>> files are out of sync, i.e. have changed externally. You could try to
>>> minimize this by avoid overwriting existing files if nothing has
>>> changed.
>>>
>>> Cheers,
>>> Sven
>>>
>>>
>
|
|
|
Goto Forum:
Current Time: Wed Jul 23 22:04:28 EDT 2025
Powered by FUDForum. Page generated in 0.04484 seconds |
Home