March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13713) Set up build for Hybrid

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13713?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-13713: -------------------------------------- Assignee: Mickael Istria (was: Gorkem Ercan) > Set up build for Hybrid > ----------------------- > > Key: JBIDE-13713 > URL: https://issues.jboss.org/browse/JBIDE-13713 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid, Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Add poms and repository to make hybrid stuff built with "mvn verify" and ready to be embedded into JBoss Tools. -- 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-13712) TP should not contain old org.mortbay.jetty plugins

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-13712: ------------------------------------- Summary: 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 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-10398) OpenShift Express : Can not delete git project

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10398?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10398: ------------------------------------- Release Notes Text: Cause: The EGit cache held references to files in the project. These references prevented the project from bein deleted on Windows. Consequence: A windows user could not delete projects in his workspace he had imported from OpenShift applications. Fix: A patch was submitted to EGit that was accepted and applied to EGit 2.3.1 (Eclipse Juno SR2). The patch tells the Git cache to release references to missing files. Result: A windows user can delete a project he had imported from OpenShift was: Cause: Consequence: Fix: Result: > OpenShift Express : Can not delete git project > ---------------------------------------------- > > Key: JBIDE-10398 > URL: https://issues.jboss.org/browse/JBIDE-10398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: UpStream > Affects Versions: 3.3.0.M5 > Environment: windows 7 (most likely all windows flavors) > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Minor > Fix For: 4.0.1.Final > > Attachments: openshift.ogv > > > Whenever I try to physically delete my openshift project from the workspace, I get a popup with the following errors : > {noformat} > Problems encountered while deleting resources. > Could not delete '/hello/.git'. > Problems encountered while deleting resources. > Problems encountered while deleting files. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack\pack-10eb864ff7ab3a1edfc8b868c90a743fdee571db.pack. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects\pack. > Could not delete: C:\Users\Fred Bricon\git\hello\.git\objects. > Could not delete: C:\Users\Fred Bricon\git\hello\.git. > Could not delete 'C:\Users\Fred Bricon\git\hello'. > {noformat} -- 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] (JBDS-2489) A method call remains as a red-underlined "problem" after the method has been created in another file

by Matti Linnanvuori (JIRA)

Matti Linnanvuori created JBDS-2489: --------------------------------------- Summary: A method call remains as a red-underlined "problem" after the method has been created in another file Key: JBDS-2489 URL: https://issues.jboss.org/browse/JBDS-2489 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: ui/branding Affects Versions: 6.0.0.GA Environment: Ubuntu 12.10 Linux matti 3.5.0-26-generic #40-Ubuntu SMP Tue Feb 26 19:57:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux Reporter: Matti Linnanvuori Priority: Minor Attachments: jbosstools-diagnostics-20130305100635.zip A method call remains as a red-underlined "problem" after the method has been created in another file. If you first write a method call whose method does not exist yet, the method call is labeled as a red-underlined problem. If you then create the method so that the method call no longer is a problem, the method call remains as a red-underlined "problem". -- 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] (JBDS-2489) A method call remains as a red-underlined "problem" after the method has been created in another file

by Matti Linnanvuori (JIRA)

[ https://issues.jboss.org/browse/JBDS-2489?page=com.atlassian.jira.plugin.... ] Matti Linnanvuori updated JBDS-2489: ------------------------------------ Attachment: jbosstools-diagnostics-20130305100635.zip > A method call remains as a red-underlined "problem" after the method has been created in another file > ----------------------------------------------------------------------------------------------------- > > Key: JBDS-2489 > URL: https://issues.jboss.org/browse/JBDS-2489 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ui/branding > Affects Versions: 6.0.0.GA > Environment: Ubuntu 12.10 Linux matti 3.5.0-26-generic #40-Ubuntu SMP Tue Feb 26 19:57:24 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux > Reporter: Matti Linnanvuori > Priority: Minor > Attachments: jbosstools-diagnostics-20130305100635.zip > > > A method call remains as a red-underlined "problem" after the method has been created in another file. If you first write a method call whose method does not exist yet, the method call is labeled as a red-underlined problem. If you then create the method so that the method call no longer is a problem, the method call remains as a red-underlined "problem". -- 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-13603) Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13603?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13603: ---------------------------------------- [~dgolovin] We have a minimal TP (which is Juno SR0 and m2e 1.3.0), which is done and won't change. The minimal TP is the one we ensure compatibility with. But the next TPs (SR1, SR2...) are the recommended ones, ie the one we'd use to build JBDS. They generally contains maintenance versions of the components to show less bugs to end users in JBDS. In those recommended TPs, it makes a lot of sense to use the best version available of m2e. > Add m2e 1.3 and m2e-wtp (core) 0.17.0 to the SR2 TP > --------------------------------------------------- > > Key: JBIDE-13603 > URL: https://issues.jboss.org/browse/JBIDE-13603 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.0.0.Final > Reporter: Fred Bricon > Assignee: Nick Boldt > Fix For: 4.0.1.Final > > > Although we agreed to not backport all the changes linked to the jbt->m2e-wtp configurator migration (see JBIDE-13048), we can still make the 4.0.x stream of JBT / JBDS use the latest m2e 1.3 and m2e-wtp (core) 0.17.0. > So JBT 4.0.1 / JBDS 6.0.1 would keep their JBoss JSF/JAX-RS/JPA configurators, but still use the latest and greatest m2e core stuff. > * from http://download.eclipse.org/m2e-wtp/milestones/juno/0.17.0 : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1821 > (org.sonatype.m2e.mavenarchiver 0.15.0.201207090125-signed-201209140800 is identical to previous versions) > * m2e 1.3.1 can also be mirrored from http://download.eclipse.org/technology/m2e/milestones/1.3 : > org.eclipse.m2e.feature 1.3.1.20130219-0909.jar > org.eclipse.m2e.logback.feature 1.3.1.20130219-0909.jar -- 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-13672) could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13672?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13672: --------------------------------------------- Nick - as long as our build depend on snapshots this check is going to incorrect in corner cases. This is not reliable and thus we can't trust it and can't have it be part of the automatic setup. > could publish.sh check previous build's GIT_REVISION.txt or ALL_REVISIONS.txt before overriding existing update site w/ new content? > ------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-13672 > URL: https://issues.jboss.org/browse/JBIDE-13672 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, updatesite > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha2 > > > Before we rsync new content from the job's workspace to www.qa or download.jboss.org, we should compare the previous build's git revision(s) to decide if the new build needs to be published. > May want to add an override flag in the job to FORCE a publish (ie., a manually built aggregate). > Sample files to check: > http://download.jboss.org/jbosstools/builds/staging/jbosstools-base_41/lo... > http://download.jboss.org/jbosstools/builds/staging/jbosstools-build-site... -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13671: --------------------------------------------- What happened to the agreement on applying this to one or two modules in a feature branch and be able to see how it works/what we are missing ? The parent pom example on top is still pushing down the "alpha2" qualifier - this would not be aligned anymore with this approach so that should be removed or at least explicitly overridden by components. And yes we need to move away from -snapshot dependencies before we can do this. And JBIDE-13672 looks like an immature change - we aren't ready for that yet afaics. > 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.0.Alpha2 > > 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] (JBDS-2438) include EAP 6.0.1 in JBDS 6.0.1 installer

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2438?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2438: ---------------------------------- Release Notes Text: Cause: Consequence: Fix: Result: > include EAP 6.0.1 in JBDS 6.0.1 installer > ----------------------------------------- > > Key: JBDS-2438 > URL: https://issues.jboss.org/browse/JBDS-2438 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 6.0.1.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 6.0.1.GA, 7.0.0.Alpha1 > > Attachments: JBDS2438.patch.txt, JBDS2438.patch2.txt > > > EAP 6.0.1 is out. Time to update the installer to include the latest n' greatest EAP 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] (JBDS-2365) ESB projects cannot be deployed using Server Add/Remove

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2365?page=com.atlassian.jira.plugin.... ] Michelle Murray updated JBDS-2365: ---------------------------------- Release Notes Text: Cause: Consequence: Fix: Result: > ESB projects cannot be deployed using Server Add/Remove > ------------------------------------------------------- > > Key: JBDS-2365 > URL: https://issues.jboss.org/browse/JBDS-2365 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: SOA Tooling / Platform > Affects Versions: 5.0.0.GA-SOA > Environment: Fedora, jdk7 > Reporter: Jeremy Davis > Assignee: Nick Boldt > Priority: Critical > Fix For: 6.0.0.CR1, 6.0.1.GA > > > * Create a new server runtime for SOA-P 5.3 > -- Preferences -> Server -> Runtime Environments > * Create a new ESB project with the defaults > * Right click the server and chosse "Add and Remove" and the project cannot be added. Error message is, "The server does not support version 4.11 of the JBoss ESB Module specification. > The project can be deployed after right clicking and choosing "Mark as deployable," but it can never be added using "Add and Remove." -- 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