[JBoss JIRA] (JBIDE-25426) central build is failing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25426?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25426:
------------------------------------
Related error:
{code}
17:11:38 [ERROR] Cannot resolve project dependencies:
17:11:38 [ERROR] Software being installed: org.jboss.tools.site.core.tests raw:4.5.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.5.1-SNAPSHOT
17:11:38 [ERROR] Missing requirement: org.jboss.tools.central.reddeer 2.1.101.v20170920-1505 requires 'bundle org.jboss.ide.eclipse.as.reddeer [3.3.1,3.4.0)' but it could not be found
17:11:38 [ERROR] Cannot satisfy dependency: org.jboss.tools.central.test.feature.feature.group 2.1.101.v20170920-1505 depends on: org.jboss.tools.central.reddeer [2.1.101.v20170920-1505]
17:11:38 [ERROR] Cannot satisfy dependency: org.jboss.tools.site.core.tests raw:4.5.1.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.5.1-SNAPSHOT depends on: {code}
https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstud...
> central build is failing
> ------------------------
>
> Key: JBIDE-25426
> URL: https://issues.jboss.org/browse/JBIDE-25426
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.5.2.AM1
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.5.2.AM1
>
>
> build is failing since server/as upversioned
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25426) central build is failing
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25426?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-25426.
------------------------------
Resolution: Rejected
Insufficient information provided.
I'm not a mind reader, Jeff. Please provide links, console log, SHAs of the commits that broke the builds, etc.
Rejecting because this is a terrible bug report.
Feel free to reopen and make it a better report. :D
> central build is failing
> ------------------------
>
> Key: JBIDE-25426
> URL: https://issues.jboss.org/browse/JBIDE-25426
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.5.2.AM1
> Reporter: Jeff MAURY
> Assignee: Nick Boldt
> Fix For: 4.5.2.AM1
>
>
> build is failing since server/as upversioned
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25425) Could not parse "2.18.1.redhat-000012" with org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.
by Lars Heinemann (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25425?page=com.atlassian.jira.plugi... ]
Lars Heinemann commented on JBIDE-25425:
----------------------------------------
Seems there is an old facet version used in form of the camel version. With latest tooling release we changed that version to use 3.0 always. Need to investigate why your project import failed.
> Could not parse "2.18.1.redhat-000012" with org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-25425
> URL: https://issues.jboss.org/browse/JBIDE-25425
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: fusetools
> Affects Versions: 10.1.0
> Reporter: Claus Ibsen
> Attachments: import.png
>
>
> Installed 4.5.1 on latest Eclipse editor.
> When I import existing maven project from CiA2 source code
> https://github.com/camelinaction/camelinaction2/tree/master/chapter19/ecl...
> I get this error in the error log
> {code}
> org.eclipse.wst.common.project.facet.core.VersionFormatException: Could not parse "2.18.1.redhat-000012" with org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.
> at org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.parse(DefaultVersionComparator.java:110)
> at org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.parse(DefaultVersionComparator.java:136)
> at org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.compare(DefaultVersionComparator.java:40)
> at org.eclipse.wst.common.project.facet.core.DefaultVersionComparator.compare(DefaultVersionComparator.java:1)
> at org.eclipse.wst.common.project.facet.core.internal.ProjectFacetVersion.compareTo(ProjectFacetVersion.java:520)
> at java.util.TreeMap.put(TreeMap.java:568)
> at java.util.TreeSet.add(TreeSet.java:255)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.refreshAvailableFacets(FacetedProjectWorkingCopy.java:658)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.<init>(FacetedProjectWorkingCopy.java:177)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.createWorkingCopy(FacetedProject.java:1076)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$1.run(FacetedProject.java:290)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2240)
> at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2267)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modify(FacetedProject.java:339)
> at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.uninstallProjectFacet(FacetedProject.java:268)
> at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.repairCamelFacet(CamelProjectConfigurator.java:192)
> at org.fusesource.ide.projecttemplates.maven.CamelProjectConfigurator.configure(CamelProjectConfigurator.java:102)
> at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:120)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:508)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$3.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.execute(MavenExecutionContext.java:151)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:501)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.configureNewMavenProjects(ProjectConfigurationManager.java:288)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:175)
> at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager$1.call(ProjectConfigurationManager.java:1)
> at org.eclipse.m2e.core.internal.embedder.MavenExecutionContext.executeBare(MavenExecutionContext.java:177)
> 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.importProjects(ProjectConfigurationManager.java:143)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob$1.doCreateMavenProjects(ImportMavenProjectsJob.java:68)
> at org.eclipse.m2e.core.ui.internal.wizards.AbstractCreateMavenProjectsOperation.run(AbstractCreateMavenProjectsOperation.java:73)
> at org.eclipse.m2e.core.ui.internal.wizards.ImportMavenProjectsJob.runInWorkspace(ImportMavenProjectsJob.java:77)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:56)
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25228) target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25228?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-25228 at 11/16/17 10:17 AM:
---------------------------------------------------------------
I was forced to revert your changes on Oct 25 [1] so I need to reopen this.
[1] https://github.com/jbosstools/jbosstools-maven-plugins/commits/master
Once you have a fix that doesn't cause compilation errors, we can re-merge that change, I'll verify it works, and we can resolve this.
was (Author: nickboldt):
I reverted your changes so I'm reopening this.
> target platform fix-version and targetToRepoMojo no longer able to find multiple IU versions
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-25228
> URL: https://issues.jboss.org/browse/JBIDE-25228
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.5.1.Final
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.5.2.AM1, 4.5.x
>
>
> With these recent changes [0], [1], target platform resolution is no longer able to fetch more than one version of an IU.
> We need apache.commons.codec 1.6.0.v201305230611, per the .target file [2], but only org.apache.commons.codec_1.9.0.v20170208-1614.jar is found in the update site [3], so the job [4] cannot perform an installation and validation of the TP fails.
> Is there a setting I can pass in to make TargetToRepo more greedy about pulling multiple versions of IUs?
> Note too that I was having problems last night getting the fix-version mojo to properly find and update the versions of WTP in the new 3.9.1a site, even when explicitly setting 0.0.0 to force it to search and update. Seems the target platform resolver will only pull the latest version of an IU, rather than an older one (a few WTP features have gone backwards in their timestamp). But it could also not resolve a version change from 3.3.600 [5] to 3.3.601 [6], so I had to update the version manually.
> [0] https://github.com/jbosstools/jbosstools-maven-plugins/commit/2b724eceadb...
> [1] https://github.com/jbosstools/jbosstools-maven-plugins/commit/ac4e492fab4...
> [2] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo...
> [3] http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.7...
> [4] https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/jbosstoo...
> [5] https://github.com/jbosstools/jbosstools-target-platforms/blob/14ec465a9b...
> [6] https://github.com/jbosstools/jbosstools-target-platforms/blob/4.71.x/jbo...
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months
[JBoss JIRA] (JBIDE-25426) central build is failing
by Jeff MAURY (JIRA)
Jeff MAURY created JBIDE-25426:
----------------------------------
Summary: central build is failing
Key: JBIDE-25426
URL: https://issues.jboss.org/browse/JBIDE-25426
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.5.2.AM1
Reporter: Jeff MAURY
Fix For: 4.5.2.AM1
build is failing since server/as upversioned
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
8 years, 4 months