March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13712) TP should not contain old org.mortbay.jetty plugins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13712?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13712: ------------------------------------ Current 4.30.5 TP includes: {code:title=http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.30.5.Alpha-SNAPSHOT/REPO/plugins/} org.eclipse.equinox.http.jetty_3.0.100.v20121210-201919.jar org.eclipse.jetty.server_8.1.3.v20120522.jar org.eclipse.jetty.http_8.1.3.v20120522.jar org.mortbay.jetty.server_6.1.23.v201004211559.jar {code} > TP should not contain old org.mortbay.jetty plugins > ---------------------------------------------------- > > Key: JBIDE-13712 > URL: https://issues.jboss.org/browse/JBIDE-13712 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.0.0.Final > Reporter: Xavier Coulon > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > I'm hitting a problem where a plugin I'm working on cannot be loaded at startup. > {code} > ENTRY org.eclipse.osgi 2 0 2013-03-05 09:17:56.748 > !MESSAGE The following is a complete list of bundles which are not resolved, see the prior log entry for the root cause if it exists: > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.748 > !MESSAGE Bundle com.google.gdt.eclipse.platform.e42_3.1.3.v201212122042-rel-r42 [46] was not resolved. > !SUBENTRY 2 com.google.gdt.eclipse.platform.e42 2 0 2013-03-05 09:17:56.749 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="0.0.0" > !SUBENTRY 2 com.google.gdt.eclipse.platform.e42 2 0 2013-03-05 09:17:56.749 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.server; bundle-version="0.0.0" > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.749 > !MESSAGE Bundle org.eclipse.equinox.http.servletbridge_1.0.300.v20120912-125810 [477] was not resolved. > !SUBENTRY 2 org.eclipse.equinox.http.servletbridge 2 0 2013-03-05 09:17:56.750 > !MESSAGE Missing imported package org.eclipse.equinox.servletbridge_1.0.0. > !SUBENTRY 2 org.eclipse.equinox.http.servletbridge 2 0 2013-03-05 09:17:56.750 > !MESSAGE Missing required capability Require-Capability: osgi.ee; filter="(|(&(osgi.ee=CDC/Foundation)(version=1.0))(&(osgi.ee=JavaSE)(version=1.3)))". > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.750 > !MESSAGE Bundle org.eclipse.wst.server.preview_1.1.102.v20130123_1813 [949] was not resolved. > !SUBENTRY 2 org.eclipse.wst.server.preview 2 0 2013-03-05 09:17:56.751 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.server; bundle-version="[8.0.4,9.0.0)" > !SUBENTRY 2 org.eclipse.wst.server.preview 2 0 2013-03-05 09:17:56.751 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.servlet; bundle-version="[8.0.4,9.0.0)" > !SUBENTRY 1 org.eclipse.osgi 2 0 2013-03-05 09:17:56.751 > !MESSAGE Bundle org.jboss.tools.web.pagereloader_1.0.0.qualifier [1101] was not resolved. > !SUBENTRY 2 org.jboss.tools.web.pagereloader 2 0 2013-03-05 09:17:56.751 > !MESSAGE Package uses conflict: Require-Bundle: org.eclipse.jetty.continuation; bundle-version="8.1.3" > {code} > After a bit of investigation, I managed get it started by removing the old org.mortbay.jetty plugins from the TP of the runtime workbench > Furthermore, Max found this: http://www.eclipse.org/eclipse/development/porting/4.2/incompatibilities.... > BUT > Attlassian Connector v3.0.7 depends on the org.mortbay.jetty bundles, and they have an open issue to migrate to the recommended org.eclipse.jetty bundles: https://ecosystem.atlassian.net/browse/PLE-1405 -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13599: ------------------------------------ Some comments inline in https://github.com/jbosstools/jbosstools-central/pull/64/files -- re: typo and testing from reading in plugin.properties rather than system properties. > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-13599 at 3/6/13 11:41 AM: ------------------------------------------------------------- If the PR was applied in the 700Alpha1 branch, you could do something like this: -Djboss.central.site.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/ and -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/devstudio-directory.xml was (Author: nickboldt): @len: -Djboss.central.site.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/ and -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/devstudio-directory.xml > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-13599: ------------------------------------ @len: -Djboss.central.site.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/ and -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/updates/development/7.0.0.Alpha1c.core/devstudio-directory.xml > externalize Central site URL into a commandline property so that testing or mirroring is easier > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-13599 > URL: https://issues.jboss.org/browse/JBIDE-13599 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE. > A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value. > This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13628) Only one JBoss Central Configurator is selected for display

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13628?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13628: --------------------------------------- Max, I have done what you suggested. > Only one JBoss Central Configurator is selected for display > ----------------------------------------------------------- > > Key: JBIDE-13628 > URL: https://issues.jboss.org/browse/JBIDE-13628 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Reporter: Paul Richardson > Assignee: Max Rydahl Andersen > Priority: Minor > Fix For: 4.1.0.Alpha2 > > > I wanted to contribute Teiid Designer's 'new model project' wizard as a link in the 'Create Projects' section of JBoss Central. [link|http://www.phantomjinx.co.uk/stuff/jboss-central.png] > However, I found that the list of project wizards is hard-coded in the default configurator [1]. Thus, the only way I can contribute this link is by extending the default configurator and using the configurators extension point[2] to load my configurator. > This works correctly but if another project decides to do the same thing then their configurator 'could' be loaded instead of mine due to the following logic in [3]: > {code:title=ProjectExamplesActivator.java|borderStyle=solid} > // ... ~ Line 1163 > IExtension extension = extensions[0]; > IConfigurationElement[] configurationElements = extension.getConfigurationElements(); > for (int j = 0; j < configurationElements.length; j++) { > IConfigurationElement configurationElement = configurationElements[j]; > if (CONFIGURATOR.equals(configurationElement.getName())) { > try { > configurator = (IJBossCentralConfigurator) configurationElement.createExecutableExtension("class"); > } catch (CoreException e) { > ProjectExamplesActivator.log(e); > continue; > } > break; > } > } > // ... > {code} > > Thought an alternative configurator that aggregates all extension-pointed configurators and displays the content of each accordingly. > Happy to provide a patch if required. > [1] org.jboss.tools.project.examples.configurators.DefaultJBossCentralConfigurator > [2] org.jboss.tools.project.examples.configurators > [3] org.jboss.tools.project.examples.ProjectExamplesActivator.java -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13671) parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-13671: ------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Alpha2) Slip to 4.1.x - not ready for prime time. > parent pom should use last-mod-timestamp from git for a plugin/feature instead of current timestamp when building > ----------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13671 > URL: https://issues.jboss.org/browse/JBIDE-13671 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.x > > Attachments: jbide13671-before-and-after.png > > > This needs to be added to master parent pom: > {code} > <plugin> > <groupId>org.eclipse.tycho</groupId> > <artifactId>tycho-packaging-plugin</artifactId> > <version>${tycho.version}</version> > <dependencies> > <dependency> > <groupId>org.eclipse.tycho.extras</groupId> > <artifactId>tycho-buildtimestamp-jgit</artifactId> > <version>${tycho-extras.version}</version> > </dependency> > </dependencies> > <configuration> > <strictBinIncludes>false</strictBinIncludes> > <format>'v'yyyyMMdd-HHmm</format> > <timestampProvider>jgit</timestampProvider> > <jgit.ignore> > </jgit.ignore> > </configuration> > </plugin> > {code} > Ref: http://pweclipse.blogspot.ch/2012_09_01_archive.html -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13734) Need a note in the 7.0.0.alpha1 rel notes - Mylyn connectors will not be in Central

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13734?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-13734: --------------------------------- Affects: Release Notes > Need a note in the 7.0.0.alpha1 rel notes - Mylyn connectors will not be in Central > ----------------------------------------------------------------------------------- > > Key: JBIDE-13734 > URL: https://issues.jboss.org/browse/JBIDE-13734 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Len DiMaggio > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Need this in the 7.0.0.alpha1 release notes > * The Mylyn connectors will not be visible in 7.0.0.alpha1 > * This is due to Atlassian 3.0.7/3.2 https://issues.jboss.org/browse/JBIDE-13682 > * And: https://issues.jboss.org/browse/JBIDE-13670 (cannot install 3.0.6) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13734) Need a note in the 7.0.0.alpha1 rel notes - Mylyn connectors will not be in Central

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-13734: ------------------------------------ Summary: Need a note in the 7.0.0.alpha1 rel notes - Mylyn connectors will not be in Central Key: JBIDE-13734 URL: https://issues.jboss.org/browse/JBIDE-13734 Project: Tools (JBoss Tools) Issue Type: Task Components: central Affects Versions: 4.1.0.Alpha1 Reporter: Len DiMaggio Assignee: Nick Boldt Fix For: 4.1.0.Alpha2 Need this in the 7.0.0.alpha1 release notes * The Mylyn connectors will not be visible in 7.0.0.alpha1 * This is due to Atlassian 3.0.7/3.2 https://issues.jboss.org/browse/JBIDE-13682 * And: https://issues.jboss.org/browse/JBIDE-13670 (cannot install 3.0.6) -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13561) Cannot embed cartridges

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13561?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13561: ------------------------------------------------- openshift-github-bot <openshift-github-bot(a)redhat.com> made a comment on [bug 911322|https://bugzilla.redhat.com/show_bug.cgi?id=911322] Commits pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/362768aea42cfb0b5c22efa... Bug 911322 https://github.com/openshift/origin-server/commit/10a7bfbedc5a4b031285331... Merge pull request #1561 from lnader/master Bug 911322 > Cannot embed cartridges > ----------------------- > > Key: JBIDE-13561 > URL: https://issues.jboss.org/browse/JBIDE-13561 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > Attachments: apptype-is-embedded-cartridge.png, cartridge-type-not-embedded.png, jbds6-erroring-embedding-cartridge.png > > > If you try to embed cartridges (or remove embedded cartridges) in 4.0.0 Final or JBDS6, then you wont be able to do it. > This is an issue that shall help us track modifications on the OpenShift platform. There's nothing we can do about it, it's *OpenShift that has to hot-fix*. -- 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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13559) Cannot embed cartridges

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13559?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13559: ------------------------------------------------- openshift-github-bot <openshift-github-bot(a)redhat.com> made a comment on [bug 911322|https://bugzilla.redhat.com/show_bug.cgi?id=911322] Commits pushed to master at https://github.com/openshift/origin-server https://github.com/openshift/origin-server/commit/362768aea42cfb0b5c22efa... Bug 911322 https://github.com/openshift/origin-server/commit/10a7bfbedc5a4b031285331... Merge pull request #1561 from lnader/master Bug 911322 > Cannot embed cartridges > ----------------------- > > Key: JBIDE-13559 > URL: https://issues.jboss.org/browse/JBIDE-13559 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: cannot-remove-apptype.png > > > If you try to embed cartridges (or remove embedded cartridges) in Alpha2 (not released yet), then you wont be able to do it. The Eclipse toolign is complaining that it cannot remove an embeddable cartridge that's actually matching the application type. -- 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, 1 month

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues March 2013