[JBoss JIRA] (JBIDE-20118) Test failures after merging JBIDE-19958
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20118?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20118:
------------------------------------------
[~jcantrill] can you please fix those? I missed them when merging after having tested the PR manually.
> Test failures after merging JBIDE-19958
> ---------------------------------------
>
> Key: JBIDE-20118
> URL: https://issues.jboss.org/browse/JBIDE-20118
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Andre Dietisheim
> Assignee: Jeff Cantrill
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
>
> Build currently fails with the following failures in our test suite:
> http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_...
> {code:title=org.jboss.tools.openshift.test.AllTestsSuite}
> Failed tests:
> CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors:100
> Wanted but not invoked:
> template.addLabel(<any>, <any>);
> -> at org.jboss.tools.openshift.test.ui.job.CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors(CreateApplicationFromTemplateJobTest.java:100)
> However, there were other interactions with this mock:
> -> at org.jboss.tools.openshift.test.ui.job.CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors(CreateApplicationFromTemplateJobTest.java:95)
> -> at org.jboss.tools.openshift.test.ui.job.CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors(CreateApplicationFromTemplateJobTest.java:95)
> NewApplicationWizardModelTest.setTemplateShouldCopyParametersAndLabels:76 array lengths differed, expected.length=1 actual.length=0
> Tests run: 120, Failures: 2, Errors: 0, Skipped: 0
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20118) Test failures after merging JBIDE-19958
by Andre Dietisheim (JIRA)
Andre Dietisheim created JBIDE-20118:
----------------------------------------
Summary: Test failures after merging JBIDE-19958
Key: JBIDE-20118
URL: https://issues.jboss.org/browse/JBIDE-20118
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta2
Reporter: Andre Dietisheim
Assignee: Jeff Cantrill
Priority: Critical
Fix For: 4.3.0.Beta2
Build currently fails with the following failures in our test suite:
http://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-openshift_...
{code:title=org.jboss.tools.openshift.test.AllTestsSuite}
Failed tests:
CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors:100
Wanted but not invoked:
template.addLabel(<any>, <any>);
-> at org.jboss.tools.openshift.test.ui.job.CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors(CreateApplicationFromTemplateJobTest.java:100)
However, there were other interactions with this mock:
-> at org.jboss.tools.openshift.test.ui.job.CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors(CreateApplicationFromTemplateJobTest.java:95)
-> at org.jboss.tools.openshift.test.ui.job.CreateApplicationFromTemplateJobTest.shouldReturnInfoStatusWhenAllResourcesCreatedWithoutErrors(CreateApplicationFromTemplateJobTest.java:95)
NewApplicationWizardModelTest.setTemplateShouldCopyParametersAndLabels:76 array lengths differed, expected.length=1 actual.length=0
Tests run: 120, Failures: 2, Errors: 0, Skipped: 0
{code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-18772:
---------------------------------------------
Why are you guys not using jboss tools parent pom ? any reason for that anymore ?
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20117) Playing around in OpenShift v3 connection tree triggers new builds
by Marián Labuda (JIRA)
Marián Labuda created JBIDE-20117:
-------------------------------------
Summary: Playing around in OpenShift v3 connection tree triggers new builds
Key: JBIDE-20117
URL: https://issues.jboss.org/browse/JBIDE-20117
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.3.0.Beta1
Reporter: Marián Labuda
Priority: Critical
After I create an application from template and I play around with OpenShift v3 connection (expand tree items, collapse them, refresh resources, connection etc.) there are several builds triggered, what should not be. Currently I do not know what exactly is triggering builds, it's in state of investigating.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-18772:
----------------------------------------
Thanks for making this change and providing feedback Martin.
I agree with all those points. About 2.2, note that in the parent pom we're also hardcoding a version (referenced via a property) https://github.com/jbosstools/jbosstools-build/blob/master/parent/pom.xml... . It seems actually correct to do that. In some near future, we'll hopefully release the scripts when necessary.
However, most of those issues wouldn't exist if you were just deploying to Nexus ;).
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-18772:
---------------------------------------
RedDeer is finally done.
There are several caveats there.
1. The target url is now both in the job config and the pom, so it's harder to update them and keep in sync (this is true for all jobs, not just RedDeer)
2. We don't use JBoss Tools parent pom, which brings some complications.
2.1 mvn deploy will not work unless we set up the target repository in our pom. For now I disabled deployment in the job using "-Dmaven.deploy.skip=true"
2.2 Using project.version in the pom to specify the version of the publish artifact will not work for us, since for RedDeer it's currently 0.8.0, so we need to hardcode a version (or pass it in the jenkins job) - so that's another thing to keep in sync manually. (We're trying to keep RedDeer independent of JBoss Tools releases, but this is one example that shows that it's not always 100 % - we still need to use *a* version of the publish script.)
3. People in our team wanted to remove mars or luna from the update site url, so now it's this:
http://download.jboss.org/jbosstools/snapshots/builds/RedDeer_master/
> Include publish steps in pom files
> ----------------------------------
>
> Key: JBIDE-18772
> URL: https://issues.jboss.org/browse/JBIDE-18772
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build
> Reporter: Max Rydahl Andersen
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.0.Beta2
>
> Attachments: jbds-publish-to-snapshots.png
>
>
> instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses.
> suggestion:
> publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing.
> What this helps with is:
> a) can do changes to publish mechanism without affecting every past builds.
> b) more movable build system
> c) isolated testing possible
>
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20084) Import of jboss-sandbox-quickstarts
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20084?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-20084:
-----------------------------------
Component/s: upstream
> Import of jboss-sandbox-quickstarts
> -----------------------------------
>
> Key: JBIDE-20084
> URL: https://issues.jboss.org/browse/JBIDE-20084
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport, upstream
> Affects Versions: 4.3.0.Beta1
> Reporter: Lucia Jelinkova
> Fix For: 4.3.0.Beta2
>
>
> I tried to import jboss-sandbox-quickstarts (from https://github.com/jboss-developer/jboss-sandbox-quickstarts.git) and I found following issues with it
> - it takes quite a long time (app 3 and a half minutes to import 9 projects
> - during import it seems to be "stuck" for a while and the following exception is logged
> {code}
> org.eclipse.core.runtime.CoreException: Could not calculate build plan: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:410)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:420)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl$2.call(MavenImpl.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:112)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:418)
> at org.eclipse.m2e.core.internal.project.registry.ProjectRegistryManager.setupMojoExecution(ProjectRegistryManager.java:950)
> at org.eclipse.m2e.core.internal.project.registry.MavenProjectFacade.getMojoExecution(MavenProjectFacade.java:408)
> at org.eclipse.m2e.core.project.configurator.AbstractCustomizableLifecycleMapping.getBuildParticipants(AbstractCustomizableLifecycleMapping.java:76)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:97)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:494)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:281)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$4.run(ProjectConfigurationManager.java:521)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:26)
> at org.eclipse.m2e.core.internal.embedder.AbstractRunnable.call(AbstractRunnable.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:176)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:99)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.execute(MavenImpl.java:1355)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.enableMavenNature(ProjectConfigurationManager.java:518)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator.configure(MavenProjectConfigurator.java:44)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:236)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.access$0(EasymportJob.java:198)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob$CrawlFolderJob.run(EasymportJob.java:154)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.searchAndImportChildrenProjectsRecursively(EasymportJob.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:245)
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:93)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> Caused by: org.apache.maven.plugin.PluginResolutionException: Plugin org.apache.maven.plugins:maven-ejb-plugin:2.3 or one of its dependencies could not be resolved: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:117)
> at org.eclipse.m2e.core.internal.project.registry.EclipsePluginDependenciesResolver.resolve(EclipsePluginDependenciesResolver.java:47)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getPluginDescriptor(DefaultMavenPluginManager.java:179)
> at org.apache.maven.plugin.internal.DefaultMavenPluginManager.getMojoDescriptor(DefaultMavenPluginManager.java:298)
> at org.apache.maven.plugin.DefaultBuildPluginManager.getMojoDescriptor(DefaultBuildPluginManager.java:241)
> at org.apache.maven.lifecycle.internal.DefaultLifecycleExecutionPlanCalculator.setupMojoExecution(DefaultLifecycleExecutionPlanCalculator.java:169)
> at org.eclipse.m2e.core.internal.embedder.MavenImpl.setupMojoExecution(MavenImpl.java:408)
> ... 35 more
> Caused by: org.eclipse.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.plugins:maven-ejb-plugin:jar:2.3
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:302)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:218)
> at org.eclipse.aether.internal.impl.DefaultRepositorySystem.readArtifactDescriptor(DefaultRepositorySystem.java:287)
> at org.apache.maven.plugin.internal.DefaultPluginDependenciesResolver.resolve(DefaultPluginDependenciesResolver.java:103)
> ... 41 more
> Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:444)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifacts(DefaultArtifactResolver.java:246)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtifact(DefaultArtifactResolver.java:223)
> at org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:287)
> ... 44 more
> Caused by: org.eclipse.aether.transfer.ArtifactTransferException: Failure to transfer org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/ was cached in the local repository, resolution will not be reattempted until the update interval of jboss-eap-maven-repository has elapsed or updates are forced. Original error: Could not transfer artifact org.apache.maven.plugins:maven-ejb-plugin:pom:2.3 from/to jboss-eap-maven-repository (file:/home/ljelinko/programs/server/maven-repo/eap-6.4/jboss-eap-6.4.0.GA-maven-repository/): The operation was cancelled.
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newException(DefaultUpdateCheckManager.java:238)
> at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtifact(DefaultUpdateCheckManager.java:206)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownloads(DefaultArtifactResolver.java:585)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownloads(DefaultArtifactResolver.java:503)
> at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(DefaultArtifactResolver.java:421)
> ... 47 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months