|
View:
New views
8 Messages
—
Rating Filter:
Alert me
|
|
|
[jira] Created: (LABS-398) [eclipse] too many rebuilds are triggered[eclipse] too many rebuilds are triggered
----------------------------------------- Key: LABS-398 URL: https://issues.apache.org/jira/browse/LABS-398 Project: Labs Issue Type: Bug Components: Magma Affects Versions: Current Reporter: Simone Gianni Assignee: Simone Gianni Fix For: Current When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Commented: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741871#action_12741871 ] Simone Gianni commented on LABS-398: ------------------------------------ One of the problems here is not easily resolvable : if in the pom a new dependency has been added, there may be the need to download sources from the maven repo, this is an async request that may be completed in the middle of a build, in that case maven reports that a new source attachment is present, Magma creates a new linked folder for those sources, and the build is fired again. If this happens for a number of dependencies, then there are multiple builds. It would be nice to catch the maven event "I have finished downloading every possible source I can think of" and create linked folders only at that point, or create a delayed job that creates linked folders only if Maven has not reported the addition of another source attachment for X seconds, so that these modifications are batched somehow. > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Current > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Current > > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Commented: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741872#action_12741872 ] Simone Gianni commented on LABS-398: ------------------------------------ The other problem is that Eclipse reports modified files in the linked source folders even if they are not, I still does not know if Magma does something that tricks Eclipse into thinking those files are modified, but seems like not. > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Current > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Current > > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Commented: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12741906#action_12741906 ] Simone Gianni commented on LABS-398: ------------------------------------ I had to rewrite quite a bit. Now I query the Maven project model directly instead of polling the classpath container, this gives some advantages like using maven artifact resolution independently of the "attach sources" action. Still have to deal with the download part, tracked in LABS-408 . This has the disadvantage of not enabling the use of non-maven aspectj libraries, but since there are not many known, this is very low priority :D Still the loop with async download is present, again this is in LABS-408. Moreover, there is a (not clear) problem in deleting some folders, probably it's because Eclipse is using them. I solved that situation with a different workaround. > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Current > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Current > > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Resolved: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Gianni resolved LABS-398. -------------------------------- Resolution: Fixed > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Current > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Current > > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Reopened: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Gianni reopened LABS-398: -------------------------------- This issue re-emerged after wrapping some operations as jobs, cause jobs does not block the workspace from triggering builds while they are in execution. We should use workspace/project locks inside these jobs. > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Current > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Current > > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Updated: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Gianni updated LABS-398: ------------------------------- Remaining Estimate: 0h Original Estimate: 0h Even if jobs try to lock the workspace, still it is cycling. Another option could be to make the source folders stuff inside the builder itself. The builder should not trigger more build cycles. > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Next > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Next > > Original Estimate: 0h > Remaining Estimate: 0h > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
|
|
[jira] Resolved: (LABS-398) [eclipse] too many rebuilds are triggered[ https://issues.apache.org/jira/browse/LABS-398?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Simone Gianni resolved LABS-398. -------------------------------- Resolution: Fixed Moving it inside the builder seems to resolve the issue. Still have to test some corner cases, but seems to work. In reality it still triggers another rebuild, after the first one is completed, cause the workspace has been modified. I don't know if there is a way to tell Eclipse that those modifications are not to be taken into account for another build cause they are generated by the build itself. Anyway, that second build is an incremental one finding nothing changed and seems to resolve in a few millisecs. > [eclipse] too many rebuilds are triggered > ----------------------------------------- > > Key: LABS-398 > URL: https://issues.apache.org/jira/browse/LABS-398 > Project: Labs > Issue Type: Bug > Components: Magma > Affects Versions: Next > Reporter: Simone Gianni > Assignee: Simone Gianni > Fix For: Next > > Original Estimate: 0h > Remaining Estimate: 0h > > When the pom is modified, it triggers a mavn update, which triggers a magma linked sources update, which triggers an aspectjbuild. > Somehow, often this cycle is repeated multiple times, while in theory only once should be enough. > Additionally AJDT often triggers a complete recompile, seeing a lot of files changed, even if they are not (magma has not reunzipped them). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online. --------------------------------------------------------------------- To unsubscribe, e-mail: labs-unsubscribe@... For additional commands, e-mail: labs-help@... |
| Free embeddable forum powered by Nabble | Forum Help |