[JBoss JIRA] (JBDS-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-2364:
-----------------------------------
the m2e discovery catalog references the buildhelper feature from http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-buildhelper/0.15.... You couldn't find a site with a better uptime :-)
Source : http://repo1.maven.org/maven2/.m2e/discovery-catalog/connectors.xml
> Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
> ----------------------------------------------------------------------------
>
> Key: JBDS-2364
> URL: https://issues.jboss.org/browse/JBDS-2364
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer, maven, updatesite
> Affects Versions: 5.0.0.GA, 5.0.1.GA
> Reporter: Martin Malina
> Assignee: Nick Boldt
> Fix For: 5.0.2.GA
>
> Attachments: install-error.png
>
>
> Steps to reproduce:
> 1. Clone git://github.com/jbossas/jboss-as.git somewhere
> 2. File -> Import -> Existing maven project
> 3. Select <jboss_git_checkout>/cmp/pom.xml and try to import
> 4. build-helper-maven-plugin will be required - try to have it resolved
> 5. build-helper-maven-plugin will fail on dependencies - cannot satisfy org.eclipse.m2e.jdt
> When you try to import for example the cmp project from as7 (git://github.com/jbossas/jboss-as.git) you will need to install build-helper-maven-plugin. But that will fail because of unsatisfied dependency for org.eclipse.m2e.jdt .
> The problem is that org.eclipse.m2e.jdt is available, but only in version 1.0.x whereas the required version is [1.1.0,2.0.0).
> This is the error message:
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201207090124)
> Missing requirement: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper 0.15.0.201207090124) requires 'bundle org.eclipse.m2e.jdt [1.1.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: m2e connector for build-helper-maven-plugin 0.15.0.201207090124 (org.sonatype.m2e.buildhelper.feature.feature.group 0.15.0.201207090124)
> To: org.sonatype.m2e.buildhelper [0.15.0.201207090124]
> {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
13 years, 2 months
[JBoss JIRA] (JBIDE-12299) Too restrictive dependency on org.eclipse.mylyn.commons.ui
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12299?page=com.atlassian.jira.plugi... ]
Nick Boldt closed JBIDE-12299.
------------------------------
Resolution: Won't Fix
JBoss Tools 4 is available which works on Juno and uses the latest Mylyn. JBoss Tools 3.3 is set to run on Indigo. There is a separate connector in the Eclipse Marketplace for the Juno (4.0) and Indigo (3.3) versions of JBT, plus a new one for JBDS 6 (also Juno).
Bottom line... Won't Fix.
> Too restrictive dependency on org.eclipse.mylyn.commons.ui
> ----------------------------------------------------------
>
> Key: JBIDE-12299
> URL: https://issues.jboss.org/browse/JBIDE-12299
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples
> Affects Versions: 3.3.0.Final
> Reporter: Mickael Istria
> Assignee: Snjezana Peco
> Priority: Critical
> Fix For: 3.3.2
>
>
> Bundle org.jboss.tools.project.examples has a very restrictive dependency range on org.eclipse.mylyn.commons.ui that prevent it from being installed on Eclipse Juno, which ships with Mylyn 3.8.
> Is this restriction intentional? If possible we should get rid of it.
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-1786) Installing m2eclipse 1.0 from community site fails
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-1786?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-1786.
----------------------------
Resolution: Won't Fix
As this is an upstream issue, and we provide a mirror as workaround, I'm closing this as Won't Fix for 5.0.2. Does not affect later JBT/JBDS releases as they depend on newer versions of m2e.
> Installing m2eclipse 1.0 from community site fails
> --------------------------------------------------
>
> Key: JBDS-1786
> URL: https://issues.jboss.org/browse/JBDS-1786
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: updatesite, Upstream
> Affects Versions: 5.0.0.M2
> Reporter: Marius Bogoevici
> Assignee: Marius Bogoevici
> Fix For: 5.0.2.GA
>
>
> Installing m2eclipse from http://eclipse.org/m2e/download/ fails with:
> Missing requirement: m2e Marketplace 1.0.0.20110607-2117 (org.eclipse.m2e.discovery 1.0.0.20110607-2117) requires 'package org.eclipse.equinox.internal.p2.discovery.compatibility 0.0.0' but it could not be found
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-1630) 3rd party cert: springide 2.8
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-1630?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-1630.
----------------------------
Resolution: Won't Fix
Won't fix in JBDS 5 or 6. See JBDS-2395 for progress on providing SpringIDE 3.x in JBDS 7's Central.
Users who want a newer version of SpringIDE should uninstall the feature from JBDS then install it directly from Springsource.
> 3rd party cert: springide 2.8
> -----------------------------
>
> Key: JBDS-1630
> URL: https://issues.jboss.org/browse/JBDS-1630
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, updatesite
> Affects Versions: 5.0.0.M4
> Reporter: Nick Boldt
> Assignee: Jaroslav Jankovič
> Fix For: 5.0.2.GA
>
>
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-2001) Investigate use of egit 1.3 in JBDS 5 and JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2001?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-2001.
----------------------------
Resolution: Won't Fix
JBT 4 / JBDS 6 includes EGit 2.1 (it's part of Juno).
Indigo SR2 includes EGit 1.3 - users can install it from there rather than getting it from JBoss Central.
Closing won't fix.
> Investigate use of egit 1.3 in JBDS 5 and JBoss Central
> -------------------------------------------------------
>
> Key: JBDS-2001
> URL: https://issues.jboss.org/browse/JBDS-2001
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central, updatesite
> Affects Versions: 5.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Len DiMaggio
> Priority: Critical
> Fix For: 5.0.2.GA
>
>
> While updating Indigo Sr2 dependencies, I notice there's now eGit 1.3 builds.
> Should we adopt 1.3?
--
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
13 years, 2 months
[JBoss JIRA] (JBDS-1998) Investigate use of subclipse 1.8 in JBDS 5 and JBoss Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-1998?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-1998.
----------------------------
Resolution: Won't Fix
JBT 4 / JBDS 6 includes Subclipse 1.8.16_1.7.5.v1 in Central. Closing won't fix - please use more recent release if you need a newer version of Subclipse.
> Investigate use of subclipse 1.8 in JBDS 5 and JBoss Central
> ------------------------------------------------------------
>
> Key: JBDS-1998
> URL: https://issues.jboss.org/browse/JBDS-1998
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, Build, central, updatesite
> Affects Versions: 5.0.0.M5
> Reporter: Fred Bricon
> Assignee: Len DiMaggio
> Priority: Blocker
> Fix For: 5.0.2.GA
>
> Attachments: JavaHL.png
>
>
> I've been using native svn 1.7 for a while now, Today while reinstalling a new Eclipse installation from scratch, I installed subclipse from JBoss Central.
> After installation, I tried to share my existing projects in eclipse but couldn't, since the 1.7 checkout is not supported by subclipse (based on svn 1.6).
> Can we update the subclipse version from central to use the 1.8.x stream?
> With svn 1.7, you have only have one .svn folder at the root of your checkout, no more .svn folders crawling everywhere making copying and moving folders a breathe.
--
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
13 years, 2 months