[JBoss JIRA] (JBIDE-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-13319.
------------------------------------
Resolution: Won't Fix
closing after removal of release notes
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13319:
-------------------------------------
Release Notes Text: (was: The OpenShift platform was upgraded to use MongoDB 2.2. For this release of the associated tooling, MongoDB 2.2 is now fully supported.)
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-13319:
-------------------------------------
Release Notes Docs Status: (was: Documented as Feature Request)
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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-13319) CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13319?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-13319:
------------------------------------------
@Michelle: This issue was cloned from JBIDE-13087, thus all links, release notes etc. were cloned along the issue itself. JBIDE-13087 was commited to JBT 4.0, this issue here was about backporting the fix to JBT 3.x branch. Max refused to have the patch backported. Thus the *Wont fix*.
> CLONE - Can't embed RockMongo, can't embed MongoDB 2.2
> ------------------------------------------------------
>
> Key: JBIDE-13319
> URL: https://issues.jboss.org/browse/JBIDE-13319
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 3.3.2
> Reporter: Stefan Bunciak
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: respin-b
> Fix For: 3.3.2
>
> Attachments: embed-by-name.patch, mongodb22-installed.png, mongodb22.png
>
>
> The MongoDB version supported by OpenShift has been recently changed. Now it support MongoDB 2.2.
> In JBoss Tools Plugin when I want to embed cartridge like RockMongo or PHPMoAdmin Eclipse warns me that 'mongodb-2.0' is a dependency.
> Additionally I'm unable to embed those cartridges. I can see the following error message.
> Could not embed cartridges for application myphptesting
> Could not request https://50.19.70.119/broker/rest/domains/myd2012111401x/applications/myph...: Operation failed on parameter "cartridge", sevirty "ERROR" with exit code "109".Reason given: "Invalid cartridge. Valid values are (mongodb-2.2, switchyard-0.6, cron-1.4, mysql-5.1, postgresql-8.4, haproxy-1.4, 10gen-mms-agent-0.1, phpmyadmin-3.4, metrics-0.1, phpmoadmin-1.0, rockmongo-1.1, jenkins-client-1.4)"
--
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-13329) should unified.target includes sources?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13329 at 1/21/13 12:59 AM:
--------------------------------------------------------------
+1 to using them. They build fine via this matrix job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
However, there appears to be a problem validating one of the 5 configs - *4.21.3.Final/jbdevstudio/unified/target/unified.target*:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/label=RHEL5,projectName=jbdevstudio,version=4.21.3.Final/6/console}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.atlassian.connector.eclipse.jira.ui 3.0.6.v20120628
[ERROR] Missing requirement: com.atlassian.connector.eclipse.jira.core 3.0.6.v20120628 requires 'bundle org.eclipse.mylyn.commons.soap [3.0.0,4.0.0)' but it could not be found
[ERROR] Cannot satisfy dependency: com.atlassian.connector.eclipse.jira.ui 3.0.6.v20120628 depends on: bundle com.atlassian.connector.eclipse.jira.core 0.0.0
{code}
Seems the problem's a simple typo:
{code}
- <unid id="org.eclipse.mylyn.commons.xmlrpc" version="3.8.2.v20120916-1200"/>
- <unid id="org.eclipse.mylyn.commons.soap" version="3.8.2.v20120916-1200"/>
+ <unit id="org.eclipse.mylyn.commons.xmlrpc" version="3.8.2.v20120916-1200"/>
+ <unit id="org.eclipse.mylyn.commons.soap" version="3.8.2.v20120916-1200"/>
{code}
Respinning...
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
was (Author: nickboldt):
+1 to using them. They build fine via this matrix job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
However, there appears to be a problem validating one of the 5 configs - *4.21.3.Final/jbdevstudio/unified/target/unified.target*:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/label=RHEL5,projectName=jbdevstudio,version=4.21.3.Final/6/console}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.atlassian.connector.eclipse.jira.ui 3.0.6.v20120628
[ERROR] Missing requirement: com.atlassian.connector.eclipse.jira.core 3.0.6.v20120628 requires 'bundle org.eclipse.mylyn.commons.soap [3.0.0,4.0.0)' but it could not be found
[ERROR] Cannot satisfy dependency: com.atlassian.connector.eclipse.jira.ui 3.0.6.v20120628 depends on: bundle com.atlassian.connector.eclipse.jira.core 0.0.0
{code}
> should unified.target includes sources?
> ---------------------------------------
>
> Key: JBIDE-13329
> URL: https://issues.jboss.org/browse/JBIDE-13329
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not.
> However:
> {code}
> unified-4.2.1.a-20121220.173723-14-unified.target:
> <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
> multiple-4.2.1.a-20121220.173233-14-multiple.target:
> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true">
> {code}
> And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles:
> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/
> Is this intentional? Or is there a bug in your flatten mojo?
> https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
--
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-13329) should unified.target includes sources?
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13329?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13329 at 1/21/13 12:46 AM:
--------------------------------------------------------------
+1 to using them. They build fine via this matrix job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
However, there appears to be a problem validating one of the 5 configs - *4.21.3.Final/jbdevstudio/unified/target/unified.target*:
{code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Target-Platforms/job/jbosstoolstargetplatforms-matrix/label=RHEL5,projectName=jbdevstudio,version=4.21.3.Final/6/console}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: com.atlassian.connector.eclipse.jira.ui 3.0.6.v20120628
[ERROR] Missing requirement: com.atlassian.connector.eclipse.jira.core 3.0.6.v20120628 requires 'bundle org.eclipse.mylyn.commons.soap [3.0.0,4.0.0)' but it could not be found
[ERROR] Cannot satisfy dependency: com.atlassian.connector.eclipse.jira.ui 3.0.6.v20120628 depends on: bundle com.atlassian.connector.eclipse.jira.core 0.0.0
{code}
was (Author: nickboldt):
+1 to using them. They build fine via this matrix job: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/Targ...
> should unified.target includes sources?
> ---------------------------------------
>
> Key: JBIDE-13329
> URL: https://issues.jboss.org/browse/JBIDE-13329
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: target-platform
> Affects Versions: 4.0.0.Final
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Fix For: 4.1.0.Alpha1
>
>
> I was under the impression that the generated multiple.target would include source features, while the generated unified.target would not.
> However:
> {code}
> unified-4.2.1.a-20121220.173723-14-unified.target:
> <location includeAllPlatforms="false" includeMode="planner" includeSource="true" type="InstallableUnit">
> multiple-4.2.1.a-20121220.173233-14-multiple.target:
> <location includeAllPlatforms="false" includeMode="planner" type="InstallableUnit" includeSource="true">
> {code}
> And the generated update site for 4.2.1.a (SR1a) target platform contains many feature.source bundles:
> http://download.jboss.org/jbosstools/updates/juno/SR1a/REPO/features/
> Is this intentional? Or is there a bug in your flatten mojo?
> https://github.com/jbosstools/jbosstools-maven-plugins/blob/master/tycho-...
--
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-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Michelle Murray resolved JBDS-2364.
-----------------------------------
Resolution: Won't Fix
> 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] (JBDS-2364) Cannot resolve org.eclipse.m2e.jdt when installing build-helper-maven-plugin
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/JBDS-2364?page=com.atlassian.jira.plugin.... ]
Michelle Murray updated JBDS-2364:
----------------------------------
Release Notes Docs Status: Documented as Known Issue
Writer: mmurray
> 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