[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-15495:
--------------------------------
Comment: was deleted
(was: Try this patch, assign to andre:
{code}
diff --git a/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java b/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
index 4dfa751..c6402cb 100644
--- a/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
+++ b/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
@@ -15,6 +15,7 @@ import java.io.File;
import org.eclipse.core.resources.IContainer;
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
+import org.eclipse.core.resources.IResourceRuleFactory;
import org.eclipse.core.resources.ResourcesPlugin;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.IPath;
@@ -24,6 +25,8 @@ import org.eclipse.core.runtime.NullProgressMonitor;
import org.eclipse.core.runtime.Path;
import org.eclipse.core.runtime.Status;
import org.eclipse.core.runtime.SubProgressMonitor;
+import org.eclipse.core.runtime.jobs.ISchedulingRule;
+import org.eclipse.core.runtime.jobs.Job;
import org.eclipse.egit.core.op.AddToIndexOperation;
import org.eclipse.egit.core.op.PushOperationResult;
import org.eclipse.jgit.lib.Repository;
@@ -196,6 +199,9 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
protected PushOperationResult commitAndPushProject(IProject p, IDeployableServerBehaviour behaviour,
IProgressMonitor monitor) throws CoreException {
+ // Keep a reference to the existing rule
+ ISchedulingRule existing = Job.getJobManager().currentJob().getRule();
+
PushOperationResult result = null;
int changes = OpenShiftServerUtils.countCommitableChanges(p, behaviour.getServer(), monitor);
if (changes > 0) {
@@ -204,21 +210,42 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
NLS.bind(OpenShiftServerMessages.commitAndPushMsg, changes, p.getName())
};
+ // Create a workspace lock
+ IResourceRuleFactory ruleFactory = ResourcesPlugin.getWorkspace().getRuleFactory();
+ ISchedulingRule workspaceLock = ruleFactory.modifyRule(ResourcesPlugin.getWorkspace().getRoot());
+ // suspend current rule, use workspace lock instead
+
Object[] ret = OpenshiftCoreUIIntegration.openMultiReturnQuestion(IQuestionHandler.COMMIT_AND_PUSH_QUESTION, data);
if( ret != null && ret.length > 0 && ret[0] != null && ((Boolean)ret[0]).booleanValue()) {
- String msg = (ret.length > 1 && ret[1] != null) ? ((String)ret[1]) : null;
-
- monitor.beginTask("Publishing " + p.getName(), 300);
- if( msg == null )
- EGitUtils.commit(p, new SubProgressMonitor(monitor, 100));
- else
- EGitUtils.commit(p, msg, new SubProgressMonitor(monitor, 100));
+ try {
+ // Commit needs a workspace lock
+ Job.getJobManager().endRule(existing);
+ Job.getJobManager().beginRule(workspaceLock, new NullProgressMonitor());
- OpenshiftCoreUIIntegration.displayConsoleView(behaviour.getServer());
- result = push(p, behaviour.getServer(), monitor);
+ String msg = (ret.length > 1 && ret[1] != null) ? ((String)ret[1]) : null;
+ monitor.beginTask("Publishing " + p.getName(), 300);
+ if( msg == null )
+ EGitUtils.commit(p, new SubProgressMonitor(monitor, 100));
+ else
+ EGitUtils.commit(p, msg, new SubProgressMonitor(monitor, 100));
+ // end the workspace lock
+ Job.getJobManager().endRule(workspaceLock);
+
+ // perform the push with no lock. Egit will capture what lock it needs
+ // and we don't fear workspace changes during a push
+ OpenshiftCoreUIIntegration.displayConsoleView(behaviour.getServer());
+ result = push(p, behaviour.getServer(), monitor);
+ } catch(CoreException ce) {
+ OpenShiftCoreActivator.pluginLog().logError(ce);
+ } finally {
+ Job.getJobManager().beginRule(existing, new NullProgressMonitor());
+ }
}
} else {
try {
+ // We don't fear workspace changes during a push, so end the rule
+ Job.getJobManager().endRule(existing);
+
String openShiftRemoteName =
OpenShiftServerUtils.getExpressRemoteName(behaviour.getServer());
if (!EGitUtils.isAhead(p, openShiftRemoteName, monitor)) {
@@ -238,6 +265,8 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
}
} catch (Exception e) {
OpenShiftCoreActivator.pluginLog().logError(e);
+ }finally {
+ Job.getJobManager().beginRule(existing, new NullProgressMonitor());
}
}
{code})
> 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: Andre Dietisheim
> Labels: openshift_server_adapter
> Fix For: LATER
>
> 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, 5 months
[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15495:
-------------------------------------
Try this patch, assign to andre:
{code}
diff --git a/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java b/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
index 4dfa751..c6402cb 100644
--- a/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
+++ b/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
@@ -15,6 +15,7 @@ import java.io.File;
import org.eclipse.core.resources.IContainer;
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
+import org.eclipse.core.resources.IResourceRuleFactory;
import org.eclipse.core.resources.ResourcesPlugin;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.IPath;
@@ -24,6 +25,8 @@ import org.eclipse.core.runtime.NullProgressMonitor;
import org.eclipse.core.runtime.Path;
import org.eclipse.core.runtime.Status;
import org.eclipse.core.runtime.SubProgressMonitor;
+import org.eclipse.core.runtime.jobs.ISchedulingRule;
+import org.eclipse.core.runtime.jobs.Job;
import org.eclipse.egit.core.op.AddToIndexOperation;
import org.eclipse.egit.core.op.PushOperationResult;
import org.eclipse.jgit.lib.Repository;
@@ -196,6 +199,9 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
protected PushOperationResult commitAndPushProject(IProject p, IDeployableServerBehaviour behaviour,
IProgressMonitor monitor) throws CoreException {
+ // Keep a reference to the existing rule
+ ISchedulingRule existing = Job.getJobManager().currentJob().getRule();
+
PushOperationResult result = null;
int changes = OpenShiftServerUtils.countCommitableChanges(p, behaviour.getServer(), monitor);
if (changes > 0) {
@@ -204,21 +210,42 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
NLS.bind(OpenShiftServerMessages.commitAndPushMsg, changes, p.getName())
};
+ // Create a workspace lock
+ IResourceRuleFactory ruleFactory = ResourcesPlugin.getWorkspace().getRuleFactory();
+ ISchedulingRule workspaceLock = ruleFactory.modifyRule(ResourcesPlugin.getWorkspace().getRoot());
+ // suspend current rule, use workspace lock instead
+
Object[] ret = OpenshiftCoreUIIntegration.openMultiReturnQuestion(IQuestionHandler.COMMIT_AND_PUSH_QUESTION, data);
if( ret != null && ret.length > 0 && ret[0] != null && ((Boolean)ret[0]).booleanValue()) {
- String msg = (ret.length > 1 && ret[1] != null) ? ((String)ret[1]) : null;
-
- monitor.beginTask("Publishing " + p.getName(), 300);
- if( msg == null )
- EGitUtils.commit(p, new SubProgressMonitor(monitor, 100));
- else
- EGitUtils.commit(p, msg, new SubProgressMonitor(monitor, 100));
+ try {
+ // Commit needs a workspace lock
+ Job.getJobManager().endRule(existing);
+ Job.getJobManager().beginRule(workspaceLock, new NullProgressMonitor());
- OpenshiftCoreUIIntegration.displayConsoleView(behaviour.getServer());
- result = push(p, behaviour.getServer(), monitor);
+ String msg = (ret.length > 1 && ret[1] != null) ? ((String)ret[1]) : null;
+ monitor.beginTask("Publishing " + p.getName(), 300);
+ if( msg == null )
+ EGitUtils.commit(p, new SubProgressMonitor(monitor, 100));
+ else
+ EGitUtils.commit(p, msg, new SubProgressMonitor(monitor, 100));
+ // end the workspace lock
+ Job.getJobManager().endRule(workspaceLock);
+
+ // perform the push with no lock. Egit will capture what lock it needs
+ // and we don't fear workspace changes during a push
+ OpenshiftCoreUIIntegration.displayConsoleView(behaviour.getServer());
+ result = push(p, behaviour.getServer(), monitor);
+ } catch(CoreException ce) {
+ OpenShiftCoreActivator.pluginLog().logError(ce);
+ } finally {
+ Job.getJobManager().beginRule(existing, new NullProgressMonitor());
+ }
}
} else {
try {
+ // We don't fear workspace changes during a push, so end the rule
+ Job.getJobManager().endRule(existing);
+
String openShiftRemoteName =
OpenShiftServerUtils.getExpressRemoteName(behaviour.getServer());
if (!EGitUtils.isAhead(p, openShiftRemoteName, monitor)) {
@@ -238,6 +265,8 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
}
} catch (Exception e) {
OpenShiftCoreActivator.pluginLog().logError(e);
+ }finally {
+ Job.getJobManager().beginRule(existing, new NullProgressMonitor());
}
}
{code}
> 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: LATER
>
> 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, 5 months
[JBoss JIRA] (JBIDE-15495) OpenShift server adapter: publish locks the whole workspace
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15495?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-15495:
-------------------------------------
Try this patch, assign to andre:
{code}
diff --git a/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java b/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
index 4dfa751..c6402cb 100644
--- a/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
+++ b/plugins/org.jboss.tools.openshift.express.core/src/org/jboss/tools/openshift/express/internal/core/behaviour/OpenShiftServerPublishMethod.java
@@ -15,6 +15,7 @@ import java.io.File;
import org.eclipse.core.resources.IContainer;
import org.eclipse.core.resources.IProject;
import org.eclipse.core.resources.IResource;
+import org.eclipse.core.resources.IResourceRuleFactory;
import org.eclipse.core.resources.ResourcesPlugin;
import org.eclipse.core.runtime.CoreException;
import org.eclipse.core.runtime.IPath;
@@ -24,6 +25,8 @@ import org.eclipse.core.runtime.NullProgressMonitor;
import org.eclipse.core.runtime.Path;
import org.eclipse.core.runtime.Status;
import org.eclipse.core.runtime.SubProgressMonitor;
+import org.eclipse.core.runtime.jobs.ISchedulingRule;
+import org.eclipse.core.runtime.jobs.Job;
import org.eclipse.egit.core.op.AddToIndexOperation;
import org.eclipse.egit.core.op.PushOperationResult;
import org.eclipse.jgit.lib.Repository;
@@ -196,6 +199,9 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
protected PushOperationResult commitAndPushProject(IProject p, IDeployableServerBehaviour behaviour,
IProgressMonitor monitor) throws CoreException {
+ // Keep a reference to the existing rule
+ ISchedulingRule existing = Job.getJobManager().currentJob().getRule();
+
PushOperationResult result = null;
int changes = OpenShiftServerUtils.countCommitableChanges(p, behaviour.getServer(), monitor);
if (changes > 0) {
@@ -204,21 +210,42 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
NLS.bind(OpenShiftServerMessages.commitAndPushMsg, changes, p.getName())
};
+ // Create a workspace lock
+ IResourceRuleFactory ruleFactory = ResourcesPlugin.getWorkspace().getRuleFactory();
+ ISchedulingRule workspaceLock = ruleFactory.modifyRule(ResourcesPlugin.getWorkspace().getRoot());
+ // suspend current rule, use workspace lock instead
+
Object[] ret = OpenshiftCoreUIIntegration.openMultiReturnQuestion(IQuestionHandler.COMMIT_AND_PUSH_QUESTION, data);
if( ret != null && ret.length > 0 && ret[0] != null && ((Boolean)ret[0]).booleanValue()) {
- String msg = (ret.length > 1 && ret[1] != null) ? ((String)ret[1]) : null;
-
- monitor.beginTask("Publishing " + p.getName(), 300);
- if( msg == null )
- EGitUtils.commit(p, new SubProgressMonitor(monitor, 100));
- else
- EGitUtils.commit(p, msg, new SubProgressMonitor(monitor, 100));
+ try {
+ // Commit needs a workspace lock
+ Job.getJobManager().endRule(existing);
+ Job.getJobManager().beginRule(workspaceLock, new NullProgressMonitor());
- OpenshiftCoreUIIntegration.displayConsoleView(behaviour.getServer());
- result = push(p, behaviour.getServer(), monitor);
+ String msg = (ret.length > 1 && ret[1] != null) ? ((String)ret[1]) : null;
+ monitor.beginTask("Publishing " + p.getName(), 300);
+ if( msg == null )
+ EGitUtils.commit(p, new SubProgressMonitor(monitor, 100));
+ else
+ EGitUtils.commit(p, msg, new SubProgressMonitor(monitor, 100));
+ // end the workspace lock
+ Job.getJobManager().endRule(workspaceLock);
+
+ // perform the push with no lock. Egit will capture what lock it needs
+ // and we don't fear workspace changes during a push
+ OpenshiftCoreUIIntegration.displayConsoleView(behaviour.getServer());
+ result = push(p, behaviour.getServer(), monitor);
+ } catch(CoreException ce) {
+ OpenShiftCoreActivator.pluginLog().logError(ce);
+ } finally {
+ Job.getJobManager().beginRule(existing, new NullProgressMonitor());
+ }
}
} else {
try {
+ // We don't fear workspace changes during a push, so end the rule
+ Job.getJobManager().endRule(existing);
+
String openShiftRemoteName =
OpenShiftServerUtils.getExpressRemoteName(behaviour.getServer());
if (!EGitUtils.isAhead(p, openShiftRemoteName, monitor)) {
@@ -238,6 +265,8 @@ public class OpenShiftServerPublishMethod implements IJBossServerPublishMethod {
}
} catch (Exception e) {
OpenShiftCoreActivator.pluginLog().logError(e);
+ }finally {
+ Job.getJobManager().beginRule(existing, new NullProgressMonitor());
}
}
{code}
> 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: LATER
>
> 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, 5 months
[JBoss JIRA] (JBDS-2824) Preferences for project examples references 7.0
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2824?page=com.atlassian.jira.plugin.... ]
Fred Bricon resolved JBDS-2824.
-------------------------------
Fix Version/s: 7.1.0.CR1
Resolution: Done
Fixed for next 7.1.CR1.
master branch was updated to reference 8.0
> Preferences for project examples references 7.0
> -----------------------------------------------
>
> Key: JBDS-2824
> URL: https://issues.jboss.org/browse/JBDS-2824
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: project-examples
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Fred Bricon
> Fix For: 7.1.0.CR1
>
>
> Click Preferences > JBoss Tools > Project Examples.
> In Sites section, expand Plugin provided sites.
> This lists 7.0 examples and 7.0 portal examples.
> Should these be updated to 7.1?
> Perhaps this is a feature that only gets updated at GA?
> Build id: Beta1-v20131102-1529-B493
--
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, 5 months
[JBoss JIRA] (JBDS-2824) Preferences for project examples references 7.0
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2824?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-2824:
------------------------------
Component/s: project-examples
> Preferences for project examples references 7.0
> -----------------------------------------------
>
> Key: JBDS-2824
> URL: https://issues.jboss.org/browse/JBDS-2824
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: project-examples
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Fred Bricon
>
> Click Preferences > JBoss Tools > Project Examples.
> In Sites section, expand Plugin provided sites.
> This lists 7.0 examples and 7.0 portal examples.
> Should these be updated to 7.1?
> Perhaps this is a feature that only gets updated at GA?
> Build id: Beta1-v20131102-1529-B493
--
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, 5 months
[JBoss JIRA] (JBDS-2824) Preferences for project examples references 7.0
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2824?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-2824:
------------------------------
Affects Version/s: 7.1.0.Beta1
(was: 7.1.0.Alpha2)
> Preferences for project examples references 7.0
> -----------------------------------------------
>
> Key: JBDS-2824
> URL: https://issues.jboss.org/browse/JBDS-2824
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Affects Versions: 7.1.0.Beta1
> Reporter: Michelle Murray
> Assignee: Fred Bricon
>
> Click Preferences > JBoss Tools > Project Examples.
> In Sites section, expand Plugin provided sites.
> This lists 7.0 examples and 7.0 portal examples.
> Should these be updated to 7.1?
> Perhaps this is a feature that only gets updated at GA?
> Build id: Beta1-v20131102-1529-B493
--
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, 5 months
[JBoss JIRA] (JBIDE-15868) 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15868?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-15868:
-------------------------------------
Wow that's a tricky one. it seems it's a combination of having a .settings/*.component without having .project/.classpath.
How did you manage to find he cause?
Please add the WTP bug # here for future reference, when you have it.
> 1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component
> ----------------------------------------------------------
>
> Key: JBIDE-15868
> URL: https://issues.jboss.org/browse/JBIDE-15868
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: maven
> Affects Versions: 4.1.1.Beta1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Priority: Critical
> Labels: testfailure
>
> *1 Test Failure(s) in JBIDE 4.1.1.Beta1 for maven component:*
> https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS...
> # [org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest|https://je...] (failing for 18 builds)
> [Search for Test Failure JIRAs in JBIDE 4.1.1.Beta1 for maven component|https://issues.jboss.org/issues/?jql=labels+IN+%28%22testfailur...]
> -----
> * {color:red}org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest : testJBIDE11570_constraintViolations{color} (failing for 18 builds)
>
> {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-central_41/103/testReport/org.jboss.tools.maven.configurators.tests/SeamConfiguratorTest/testJBIDE11570_constraintViolations}
> <case>
> <age>18</age>
> <className>org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest</className>
> <duration>1.229</duration>
> <errorStackTrace>java.lang.NullPointerException
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.getProjectRelativePaths(VirtualResource.java:119)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingFiles(VirtualFile.java:104)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualFile.getUnderlyingResources(VirtualFile.java:93)
> at org.eclipse.wst.common.componentcore.internal.resources.VirtualResource.exists(VirtualResource.java:88)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getNonBinaryComponentManifest(ManifestUtilities.java:124)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifest(ManifestUtilities.java:81)
> at org.eclipse.jst.common.internal.modulecore.util.ManifestUtilities.getManifestClasspath(ManifestUtilities.java:147)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getManifestClasspath(J2EEModuleVirtualComponent.java:248)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.calculateManifestReferences(J2EEModuleVirtualComponent.java:368)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.cacheManifestReferences(J2EEModuleVirtualComponent.java:360)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:176)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:214)
> at org.eclipse.jst.j2ee.componentcore.J2EEModuleVirtualComponent.getReferences(J2EEModuleVirtualComponent.java:207)
> at org.eclipse.m2e.wtp.WebProjectConfiguratorDelegate.configureClasspath(WebProjectConfiguratorDelegate.java:386)
> at org.eclipse.m2e.wtp.WTPProjectConfigurator.configureClasspath(WTPProjectConfigurator.java:107)
> at org.eclipse.m2e.jdt.internal.DefaultClasspathManagerDelegate.populateClasspath(DefaultClasspathManagerDelegate.java:61)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:253)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:363)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:343)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.getClasspath(BuildPathManager.java:371)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.updateClasspath(BuildPathManager.java:191)
> at org.eclipse.m2e.jdt.internal.BuildPathManager.mavenProjectChanged(BuildPathManager.java:180)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.notifyProjectChangeListeners(ProjectRegistryManager.java:746)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.applyMutableProjectRegistry(ProjectRegistryManager.java:865)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.refresh(ProjectRegistryManager.java:289)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:216)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:159)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:161)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:137)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:89)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1305)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:134)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase$4.run(AbstractMavenProjectTestCase.java:326)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2345)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:324)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProjects(AbstractMavenProjectTestCase.java:299)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:286)
> at org.eclipse.m2e.tests.common.AbstractMavenProjectTestCase.importProject(AbstractMavenProjectTestCase.java:273)
> at org.jboss.tools.maven.configurators.tests.SeamConfiguratorTest.testJBIDE11570_constraintViolations(SeamConfiguratorTest.java:132)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.runTests(AbstractUITestApplication.java:44)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Testable$1.run(E4Testable.java:72)
> at java.lang.Thread.run(Thread.java:662)
> </errorStackTrace>
> <failedSince>86</failedSince>
> <name>testJBIDE11570_constraintViolations</name>
> <skipped>false</skipped>
> <status>FAILED</status>
> <stdout>TEST-SETUP: testJBIDE11570_constraintViolations
> Restoring user settings file: /home/hudson/.m2/settings.xml
> </stdout>
> </case>
> {code}
--
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, 5 months
[JBoss JIRA] (JBIDE-15904) Test Cordova combinations
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15904:
---------------------------------------------
#4 is simply that you can import a project created in one workspace into a new workspace.
The Git part is optional IMO but it is a good verification that if you push things to github and then are
able to import on another users machine (on a different OS) that there are no (unwarranted) system specific paths
stored in any settings etc.
> Test Cordova combinations
> -------------------------
>
> Key: JBIDE-15904
> URL: https://issues.jboss.org/browse/JBIDE-15904
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Vlado Pakan
> Priority: Blocker
> Fix For: 4.1.1.CR1
>
>
> Use this jira to collect results from testing:
> 1)
> Run On Android Emulator. On windows, Linux and Mac (in that prio order).
>
> Run On Android Device: On windows, Linux and Mac (in that prio order)
>
> The more SDK version we cover the better with the above two. I do not think
> we can cover all so we should start with latest and make our way down.
>
> 2)
> Changes on the Run configurations for Run on Android...
>
> 3)
> Install Cordova Plugin:
>
> Offline, windows, Linux, Mac
>
> 4)
> Share project via git. Import existing project.
>
> 5)
> Export native platform project
>
> 6)
> Export Mobile Application
> windows, linux, mac
--
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, 5 months
[JBoss JIRA] (JBIDE-15904) Test Cordova combinations
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15904?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-15904 at 11/8/13 2:57 AM:
--------------------------------------------------------------
What exactly means step 4.? Please provide steps how to verify it thanks
Point 1. Are you talking about Adroid SDK or Jave SDK?
Point 3. Do you mean add Cordova feature via Cordova Configuration Editor and Cordova Discovery Dialog or installing Hybrid Mobile Tooling plugins to JBT/JBDS
was (Author: vpakan):
What exactly means step 4.? Please provide steps how to verify it thanks
> Test Cordova combinations
> -------------------------
>
> Key: JBIDE-15904
> URL: https://issues.jboss.org/browse/JBIDE-15904
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Affects Versions: 4.1.1.Beta1
> Reporter: Max Rydahl Andersen
> Assignee: Vlado Pakan
> Priority: Blocker
> Fix For: 4.1.1.CR1
>
>
> Use this jira to collect results from testing:
> 1)
> Run On Android Emulator. On windows, Linux and Mac (in that prio order).
>
> Run On Android Device: On windows, Linux and Mac (in that prio order)
>
> The more SDK version we cover the better with the above two. I do not think
> we can cover all so we should start with latest and make our way down.
>
> 2)
> Changes on the Run configurations for Run on Android...
>
> 3)
> Install Cordova Plugin:
>
> Offline, windows, Linux, Mac
>
> 4)
> Share project via git. Import existing project.
>
> 5)
> Export native platform project
>
> 6)
> Export Mobile Application
> windows, linux, mac
--
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, 5 months