[JBoss JIRA] (JBIDE-21351) Error during "Update Maven projects configuration"
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21351?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-21351:
--------------------------------------
Assignee: Mickael Istria
> Error during "Update Maven projects configuration"
> --------------------------------------------------
>
> Key: JBIDE-21351
> URL: https://issues.jboss.org/browse/JBIDE-21351
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: easymport
> Affects Versions: 4.3.1.Beta1
> Reporter: Radim Hopp
> Assignee: Mickael Istria
> Fix For: 4.3.1.Beta2
>
>
> Sometimes I get
> {noformat}
> An internal error occurred during: "Update Maven projects configuration".
> Cannot add projects when processing is started{noformat}
> when I'm importing maven project using easymport.
> Full stacktrace:
> {noformat}
> java.lang.IllegalStateException: Cannot add projects when processing is started
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$CumulativeMappingDiscoveryJob.addProjects(MavenProjectConfigurator.java:97)
> at org.jboss.tools.playground.easymport.maven.MavenProjectConfigurator$UpdateMavenConfigurationJob.run(MavenProjectConfigurator.java:161)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55){noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JBIDE-21391) upstream IU version decreases
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21391?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21391:
---------------------------------------------
have we reported these to the upstream projects ?
btw. is it our our reporting that is bogus/bad since the error message don't actually list *why* it thinks they need to be bumped.
> upstream IU version decreases
> -----------------------------
>
> Key: JBIDE-21391
> URL: https://issues.jboss.org/browse/JBIDE-21391
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
>
> As of Neon M4, three IUs have versions which decreased relative to their Mars.1 versions.
> {code}
> org.eclipse.equinox.p2.rcp.feature 1.2.101.v20150826-1318 Version must be higher than 1.2.101.v20150826-1318
> org.eclipse.equinox.p2.user.ui 2.2.101.v20150826-1318 Version must be higher than 2.2.101.v20150826-1318
> org.eclipse.ecf.provider.filetransfer.httpclient4 1.0.2000.v20150810-1719 Version must be higher than 1.0.2000.v20150810-1719
> {code} -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt...
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JBIDE-21382) remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21382?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21382:
---------------------------------------------
Marking this as blocker to fix for at least our plugins by time of Alpha.
I'm surprised it is still needed by that many eclipse.org bundles though - [~mickael_istria] could you look into this ?
> remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)
> ---------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21382
> URL: https://issues.jboss.org/browse/JBIDE-21382
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Alexey Kazakov
> Priority: Blocker
> Fix For: 4.4.0.Alpha1
>
>
> org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of M3. It is required by these IUs:
> * o.j.t.common.model.ui,
> * o.e.platform.feature,
> * o.e.m2e.feature,
> * o.e.datatools.oda.cshelp,
> * o.aspectj.ajde,
> * o.e.wst.xml.xpath.core, and
> * o.e.birt.feature
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months
[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-21377:
---------------------------------------------
We already has this editor or at least part of it in our TP as part of SpringIDE.
Can we simply remove this from the Central TP and include it in our "base" TP and then we solve this issue + reuse it for the SpringIDE dependency ?
Any limits/version ranges on what SpringIDE needs that restricts us ?
> Include Yaml editor in JBoss Tools (& JBDS?) via feature dep, new Central connector, or just add to CoreTools category
> ----------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21377
> URL: https://issues.jboss.org/browse/JBIDE-21377
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.3.1.Beta1
> Reporter: Mickael Istria
>
> There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default.
> This would require adding it to the TP and adding a dependency from a JBT feature to it.
> On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny])
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
8 years, 5 months