October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-15653 at 10/11/13 5:29 AM: -------------------------------------------------------------------- JBIDE-15495 is only loosely related. It covers a similar topic but the cause here is a different one: {code:title=OpenShiftApplicationWizard#publishServerAdapter} if (!EGitUtils.isDirty(model.getProject())) { IsAheadJob isAheadJob = new IsAheadJob(model.getProject(), model.getRemoteName()); IStatus status = WizardUtils.runInWizard(isAheadJob, isAheadJob.getDelegatingProgressMonitor(), getContainer()); if (!status.isOK()) { return false; } if (!isAheadJob.isAhead()) { return true; } } {code} The above code will publish a non-dirty, non-ahead project which is clearly wrong, it should not get published. was (Author: adietish): JBIDE-15495 is only loosely related. It covers a similar topic but the cause here is a different one: {code:title=OpenShiftApplicationWizard#publishServerAdapter} if (!EGitUtils.isDirty(model.getProject())) { IsAheadJob isAheadJob = new IsAheadJob(model.getProject(), model.getRemoteName()); IStatus status = WizardUtils.runInWizard(isAheadJob, isAheadJob.getDelegatingProgressMonitor(), getContainer()); if (!status.isOK()) { return false; } if (!isAheadJob.isAhead()) { return true; } } {code} The above code will publish a non-dirty, non-ahead project which is clearly wrong, it should not get published. > Import application wizard: Errors "Could not publish: Attempted to begin rule" > ------------------------------------------------------------------------------ > > Key: JBIDE-15653 > URL: https://issues.jboss.org/browse/JBIDE-15653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: could-not-import.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15495: ------------------------------------- Summary: OpenShift server adapter: publish locks the whole workspace (was: OpenShift publication locks the whole workspace) > OpenShift server adapter: publish locks the whole workspace > ----------------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15495: ------------------------------------- Labels: openshift_server_adapter (was: ) > OpenShift server adapter: publish locks the whole workspace > ----------------------------------------------------------- > > Key: JBIDE-15495 > URL: https://issues.jboss.org/browse/JBIDE-15495 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift, server > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Rob Stryker > Labels: openshift_server_adapter > Fix For: 4.2.0.Alpha1 > > Attachments: Screen Shot 2013-09-17 at 10.42.43 AM.png > > > Have 2 projects in a workspace, one of them is an OpenShift application > Deploy some changes on OpenShift, and while the publication is performed (git push, then OS restarts the server), go to the second (unrelated) project and try to move a file from a package to another package in the same project. > The 'Publish' operation locked the whoel workspace, which means that the move operation needs to wait. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-15653: ------------------------------------------ JBIDE-15495 is only loosely related. It covers a similar topic but the cause here is a different one: {code:title=OpenShiftApplicationWizard#publishServerAdapter} if (!EGitUtils.isDirty(model.getProject())) { IsAheadJob isAheadJob = new IsAheadJob(model.getProject(), model.getRemoteName()); IStatus status = WizardUtils.runInWizard(isAheadJob, isAheadJob.getDelegatingProgressMonitor(), getContainer()); if (!status.isOK()) { return false; } if (!isAheadJob.isAhead()) { return true; } } {code} The above code will publish a non-dirty, non-ahead project which is clearly wrong, it should not get published. > Import application wizard: Errors "Could not publish: Attempted to begin rule" > ------------------------------------------------------------------------------ > > Key: JBIDE-15653 > URL: https://issues.jboss.org/browse/JBIDE-15653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: could-not-import.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15653?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15653: ------------------------------------- Attachment: could-not-import.png > Import application wizard: Errors "Could not publish: Attempted to begin rule" > ------------------------------------------------------------------------------ > > Key: JBIDE-15653 > URL: https://issues.jboss.org/browse/JBIDE-15653 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.2.0.Alpha1 > > Attachments: could-not-import.png > > -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15653) Import application wizard: Errors "Could not publish: Attempted to begin rule"

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15653: ---------------------------------------- Summary: Import application wizard: Errors "Could not publish: Attempted to begin rule" Key: JBIDE-15653 URL: https://issues.jboss.org/browse/JBIDE-15653 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.Alpha1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Blocker Fix For: 4.2.0.Alpha1 Attachments: could-not-import.png -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2795) make sure current JBDS works with mult-domain OpenShift instance

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2795?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2795: ---------------------------------- Affects: Documentation (Ref Guide, User Guide, etc.) > make sure current JBDS works with mult-domain OpenShift instance > ---------------------------------------------------------------- > > Key: JBDS-2795 > URL: https://issues.jboss.org/browse/JBDS-2795 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: openshift > Affects Versions: 7.0.0.GA > Environment: JBDS 7, > multidomain DEVENV (2013-10-9) > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 7.1.0.Alpha2 > > Attachments: cannot-create-application.png, explorer-1.png, explorer-2.png, explorer-3.png, explorer-4.png, explorer-5.png, explorer-5.png, explorer-6.png, explorer-6.png, explorer-7.png, explorer-7.png, explorer-8.png, explorer-9.png, multi-domain-setup-adietish.png, multi-domain-setup-test.png, properties-shows-the-domain.png > > > With the upcoming support for multiple domains, we have to make sure that the existing JBDS/JBT work smoothly even with this newer OpenShift. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15482: ---------------------------------------- I'm coming late in this discussion, but here is what I think would be a good trade-off: * Put various builds as subsites of http://download.jboss.org/jbosstools/builds/staging/<jobName>/ with URL http://download.jboss.org/jbosstools/builds/staging/<jobName>/<build#> * Have current URL http://download.jboss.org/jbosstools/builds/staging/<jobName>/all/repo/ a composite on available sites at http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_41/a...<jobName>/<build#>/all/repo So there would be some static URLs to reference builds, but the public facade for the latest bits wouldn't change. > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15374) Create target platform from Luna M2 dependencies

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15374?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-15374: ----------------------------------- Fix Version/s: 4.2.0.Alpha1 > Create target platform from Luna M2 dependencies > ------------------------------------------------ > > Key: JBIDE-15374 > URL: https://issues.jboss.org/browse/JBIDE-15374 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Affects Versions: 4.2.0.Alpha1 > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.2.0.Alpha1 > > > Create a new target platform for use with JBoss Tools 4.2 (Luna). Should be versioned 4.40.x. > Luna schedule: > http://wiki.eclipse.org/Luna/Simultaneous_Release_Plan#Schedule -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15482: --------------------------------------- Thanks, [~nickboldt], we only need a static url for the updatesite. So in that case we just stick in the extra "CI". So personally I would vote for Max' suggestion and keep it as is :) What Max meant, I believe, is to put a file in the folder - a readme or something - that would make it possible to recognize that this is the new publish.sh at work - if one needs to know that. > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2013