[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 resolved JBDS-2364.
-------------------------------
Resolution: Won't Fix
Sorry I misunderstood the problem earlier. Pretend I didn't say anything :-)
Agreed to resolving as won't fix as :
* Either we'd have to find the proper m2eclipse-builder feature from https://repository.sonatype.org/content/repositories/forge-sites/m2e-extr... and embed it to the JBDS 5.0.2 installer
* Or make JBDS 5.0.2 compatible with m2e 1.1+
both solutions require significant changes for a +0.0.1 version bump.
Best solution is definitely install JBDS 6.
> 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, 3 months
[JBoss JIRA] (JBDS-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2364:
-----------------------------
Release Notes Text:
Workaround exists:
a) use JBDS 6 via installer
b) use JBDS 6 via Marketplace
c) use JBT 4.0
d) use JBT 3.3
> 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, 3 months
[JBoss JIRA] (JBDS-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2364:
----------------------------------
If I try to install the buildhelper feature into JBDS 5.0.1.GA from the URL above [0] I get this:
{code}
Cannot complete the install because of a conflicting dependency.
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)
Software currently installed: JBoss Developer Studio (Branded Product) 5.0.1.v20120715-0533-H232-GA (com.jboss.jbds.all 5.0.1.v20120715-0533-H232-GA)
Only one of the following can be installed at once:
Maven Integration for Eclipse 1.0.200.20111228-1245 (org.eclipse.m2e.core.ui 1.0.200.20111228-1245)
Maven Integration for Eclipse 1.2.0.20120903-1050 (org.eclipse.m2e.core.ui 1.2.0.20120903-1050)
{code}
So... same problem as before. Either we need to stick a newer version of m2e.core.ui into the JBDS target platform [1] and rebuild JBDS 5.0.2, or we doc this as a problem with 4 possible workarounds:
a) use JBDS 6 via installer
b) use JBDS 6 via Marketplace
c) use JBT 4.0
d) use JBT 3.3
[0] http://repo1.maven.org/maven2/.m2e/connectors/m2eclipse-buildhelper/0.15....
[1] http://www.qa.jboss.com/binaries/RHDS/updates/jbds-target-platform_3.3.in... contains org.eclipse.m2e.core.ui_1.0.200.20111228-1245.jar
IMHO, this is a Won't Fix since there are multiple workarounds. This was really only an issue before JBDS 6 was released.
[~fbricon] Do you agree?
> 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, 3 months
[JBoss JIRA] (JBDS-2180) Support Oracle OSX Java 7 version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2180?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2180:
-----------------------------
Assignee: Michelle Murray (was: Denis Golovin)
> Support Oracle OSX Java 7 version
> ---------------------------------
>
> Key: JBDS-2180
> URL: https://issues.jboss.org/browse/JBDS-2180
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, installer
> Affects Versions: 5.0.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> Reporter: Martin Malina
> Assignee: Michelle Murray
> Fix For: 5.0.2.GA
>
>
> I accidentally had my java set to java 1.7 on my mac computer:
> vokuro:5.0.0.CR1 rasp$ java -version
> java version "1.7.0_04"
> Java(TM) SE Runtime Environment (build 1.7.0_04-b21)
> Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
> When you then launch the installer using
> java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed.
> Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit?
> FYI, on Mac OS X Lion, there are currently these jdk versions:
> Apple JDK 1.6 32-bit
> Apple JDK 1.6 64-bit
> Oracle JDK 1.7 64-bit
> I don't expect there will ever be Oracle JDK 1.7 32-bit available.
--
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, 3 months
[JBoss JIRA] (JBDS-2180) Document the fact that Oracle OSX Java 7 is not supported by JBDS 5
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2180?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2180:
-----------------------------
Summary: Document the fact that Oracle OSX Java 7 is not supported by JBDS 5 (was: Support Oracle OSX Java 7 version)
> Document the fact that Oracle OSX Java 7 is not supported by JBDS 5
> -------------------------------------------------------------------
>
> Key: JBDS-2180
> URL: https://issues.jboss.org/browse/JBDS-2180
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, installer
> Affects Versions: 5.0.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> Reporter: Martin Malina
> Assignee: Michelle Murray
> Fix For: 5.0.2.GA
>
>
> I accidentally had my java set to java 1.7 on my mac computer:
> vokuro:5.0.0.CR1 rasp$ java -version
> java version "1.7.0_04"
> Java(TM) SE Runtime Environment (build 1.7.0_04-b21)
> Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
> When you then launch the installer using
> java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed.
> Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit?
> FYI, on Mac OS X Lion, there are currently these jdk versions:
> Apple JDK 1.6 32-bit
> Apple JDK 1.6 64-bit
> Oracle JDK 1.7 64-bit
> I don't expect there will ever be Oracle JDK 1.7 32-bit available.
--
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, 3 months
[JBoss JIRA] (JBDS-2180) Document the fact that Oracle OSX Java 7 is not supported by JBDS 5
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2180?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-2180:
----------------------------------
Update JIRA title and assign to Michelle to add to Release notes. Michelle, we need a blurb somewhere stating that JBDS 5 won't run with Oracle OSX Java 7.
> Document the fact that Oracle OSX Java 7 is not supported by JBDS 5
> -------------------------------------------------------------------
>
> Key: JBDS-2180
> URL: https://issues.jboss.org/browse/JBDS-2180
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, installer
> Affects Versions: 5.0.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> Reporter: Martin Malina
> Assignee: Michelle Murray
> Fix For: 5.0.2.GA
>
>
> I accidentally had my java set to java 1.7 on my mac computer:
> vokuro:5.0.0.CR1 rasp$ java -version
> java version "1.7.0_04"
> Java(TM) SE Runtime Environment (build 1.7.0_04-b21)
> Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
> When you then launch the installer using
> java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed.
> Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit?
> FYI, on Mac OS X Lion, there are currently these jdk versions:
> Apple JDK 1.6 32-bit
> Apple JDK 1.6 64-bit
> Oracle JDK 1.7 64-bit
> I don't expect there will ever be Oracle JDK 1.7 32-bit available.
--
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, 3 months
[JBoss JIRA] (JBDS-2180) Support Oracle OSX Java 7 version
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2180?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-2180:
-----------------------------
Component/s: documentation
> Support Oracle OSX Java 7 version
> ---------------------------------
>
> Key: JBDS-2180
> URL: https://issues.jboss.org/browse/JBDS-2180
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: documentation, installer
> Affects Versions: 5.0.0.CR1
> Environment: jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Fix For: 5.0.2.GA
>
>
> I accidentally had my java set to java 1.7 on my mac computer:
> vokuro:5.0.0.CR1 rasp$ java -version
> java version "1.7.0_04"
> Java(TM) SE Runtime Environment (build 1.7.0_04-b21)
> Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode)
> When you then launch the installer using
> java -jar jbdevstudio-product-universal-5.0.0.v201205272317M-H143-CR1.jar
> everything seems ok, you are allowed to select either 32 or 64-bit installation, but regardless of what you choose, the 64-bit version will be installed.
> Not sure how this can be handled. At the very least we should disable the radio buttons and preselect 64-bit if that's what must be installed. But the fact is that JBDS will run with java 1.6 anyway. Even if you installed it using 1.7. So wouldn't it be possible to install the 32-bit version even if the installer is run using java 1.7 64-bit?
> FYI, on Mac OS X Lion, there are currently these jdk versions:
> Apple JDK 1.6 32-bit
> Apple JDK 1.6 64-bit
> Oracle JDK 1.7 64-bit
> I don't expect there will ever be Oracle JDK 1.7 32-bit available.
--
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, 3 months
[JBoss JIRA] (JBDS-2272) Bump PMD version in JBDS Extras/Central to 3.2.6 (net.sourceforge.pmd.eclipse 3.2.4 has invalid OSGi MANIFEST)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-2272?page=com.atlassian.jira.plugin.... ]
Nick Boldt resolved JBDS-2272.
------------------------------
Resolution: Done
Seems the commit was accidentally lost at some point. Re-committed to both 5.0/ and 5.0-staging/
Just need to verify that we can install PMD 3.2.6 from JBT3.3/JBDS5 Central, rather than the older 3.2.4 version.
> Bump PMD version in JBDS Extras/Central to 3.2.6 (net.sourceforge.pmd.eclipse 3.2.4 has invalid OSGi MANIFEST)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-2272
> URL: https://issues.jboss.org/browse/JBDS-2272
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: 3rdPartyCertification, 3rdPartyDependencies, central, updatesite, Upstream
> Affects Versions: 5.0.1.GA, 6.0.0.Alpha1
> Environment: JBT 4.0.0.Alpha1
> Reporter: Jiri Peterka
> Assignee: Nick Boldt
> Fix For: 5.0.2.GA, 6.0.0.Beta2
>
>
> net.sourceforge.pmd.eclipse is not valid OSGI bundle and cannot be loaded as target runtime in eclipse
> It contains only:
> Manifest-Version: 1.0
> Ant-Version: Apache Ant 1.7.0
> Created-By: 10.0-b19 (Sun Microsystems Inc.)
--
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, 3 months