February 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13684) BrowserSim: create iPad skin

by Ilya Buziuk (JIRA)

Ilya Buziuk created JBIDE-13684: ----------------------------------- Summary: BrowserSim: create iPad skin Key: JBIDE-13684 URL: https://issues.jboss.org/browse/JBIDE-13684 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Reporter: Ilya Buziuk Assignee: Yahor Radtsevich Fix For: 4.0.x Need to create iPad skin for BrowserSim -- 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-13670) Can't install some Atlassian connector from Central

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13670?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13670: ---------------------------------------- +1, using 3.0.7.v20121218 seems to be the best choice: easier now, longer-term solution. > Can't install some Atlassian connector from Central > --------------------------------------------------- > > Key: JBIDE-13670 > URL: https://issues.jboss.org/browse/JBIDE-13670 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: target-platform > Reporter: Mickael Istria > Assignee: Nick Boldt > Fix For: 4.1.0.Alpha1 > > > Can't install Atlassian from Central > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... > * Contains: Missing requirement: Atlassian Connector for Eclipse Usage Monitoring 3.0.6.v20120628 (com.atlassian.connector.eclipse.monitor.feature.group 3.0.6.v20120628) requires 'org.eclipse.update.ui 0.0.0' but it could not be found > 2 solutions possible, by order of preference: > # Use a more recent version of Atlassian connectors compliant with Kepler > # Remove Atlassian stuff from Central until we have a good version -- 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 Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-13671: ---------------------------------------- This is OK to me. However, it makes it easier to see differences between 2 bundles that built the same stuff, but whom content differs because of some build configuration directly in parent pom (for example if we add .api_description in bundle, or change target Java version) because Git timestamp will be the same whereas the output may differ. But it's a specific case and it's not a big deal. Moreover, when we'll be ready to consume non-SNAPSHOTs of parent pom, the issue I mentioned won't happen because updating build will imply a commit to use another parent pom. So +1 for that change. > 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] (JBIDE-13612) Add m2e 1.3 and m2e-wtp (+jsf/jpa/jax-rs) 0.17.0 to the Kepler TP

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13612?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-13612. --------------------------------- Resolution: Done Everything installs properly from the Kepler update site. JBDS has the proper versions too. Resolving. > Add m2e 1.3 and m2e-wtp (+jsf/jpa/jax-rs) 0.17.0 to the Kepler TP > ----------------------------------------------------------------- > > Key: JBIDE-13612 > URL: https://issues.jboss.org/browse/JBIDE-13612 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Build/Releng, maven > Affects Versions: 4.1.0.Alpha1 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > Turns out the m2e-wtp version picked for the Alpha1 build is not compatible with Dali. The fix happened right after M5. This causes JBIDE-13607 > So we'd need the latest m2e / m2e-wtp features in this Alpha1 build. > * from http://download.eclipse.org/m2e-wtp/releases/kepler/ : > org.eclipse.m2e.wtp.feature 0.17.0.20130212-1819 > org.eclipse.m2e.wtp.jsf.feature 0.17.0.20130212-1819 > org.eclipse.m2e.wtp.jaxrs.feature 0.17.0.20130212-1819 > org.eclipse.m2e.wtp.jpa.feature 0.17.0.e43-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/releases/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-13669) add refactored m2e-wtp features to maven project examples feature as dependencies so they'll be installed OOTB

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13669?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-13669: -------------------------------- Attachment: install_jbt_4.1.0.Alpha1.png All m2e-wtp features are installed with JBoss Central via Maven Examples. !install_jbt_4.1.0.Alpha1.png! It's aaaalll good :-) > add refactored m2e-wtp features to maven project examples feature as dependencies so they'll be installed OOTB > --------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-13669 > URL: https://issues.jboss.org/browse/JBIDE-13669 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Fred Bricon > Labels: respin-c > Fix For: 4.1.0.Alpha1 > > Attachments: install_jbt_4.1.0.Alpha1.png > > > Must add these as requirements to org.jboss.tools.maven.project.examples.feature: > https://github.com/jbosstools/jbosstools-central/blob/master/maven/featur... > * org.eclipse.m2e.wtp.jsf.feature > * org.eclipse.m2e.wtp.jaxrs.feature > * org.eclipse.m2e.wtp.jpa.feature -- 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-13631) URL for embedded cartridges is empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13631: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 916268|https://bugzilla.redhat.com/show_bug.cgi?id=916268] @Xiaoli: do "curl -H "Accept: application/xml;version=1.0" --user "<USER>:<PASSWORD>" https://openshift.redhat.com/broker/rest/domains/honkabonka2/applications... (notice the ;version=1.0 in the accept-header). You'll see that you dont get the above properties. In this issue we're talking about our existing JBDS users which cannot have their library replaced easily (300K+ users). We have to ensure that they get an URL. > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- 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-13631) URL for embedded cartridges is empty

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13631?page=com.atlassian.jira.plugi... ] RH Bugzilla Integration commented on JBIDE-13631: ------------------------------------------------- Andre Dietisheim <adietish(a)redhat.com> made a comment on [bug 916268|https://bugzilla.redhat.com/show_bug.cgi?id=916268] Afaik the above is only valid for protocol 1.1. JBDS is currently only talking 1.0 where the above is not available. > URL for embedded cartridges is empty > ------------------------------------ > > Key: JBIDE-13631 > URL: https://issues.jboss.org/browse/JBIDE-13631 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.0.0.Final > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: existing-application.json, no-url.png > > > Embedded cartridges for OpenShift application have an URL property. Currently JBDS/JBT doesn't show any, all URLs are blank -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13671?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13671: --------------------------------------- Interesting. Looks good to me. Don't forget to send out an email to everybody so they're aware. We were used to the fact that the plugin name corresponds to a certain build, so same string means same build. This will no longer be true, so people need to be aware. > 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] (JBIDE-13639) remove struts tests from integration-tests update site

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13639?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13639: --------------------------------------- [~nickboldt], be sure to always relay such a change to everybody before it happens. Maybe we just missed it, but neither me nor [~jpeterka] noticed the removal of struts. > remove struts tests from integration-tests update site > ------------------------------------------------------ > > Key: JBIDE-13639 > URL: https://issues.jboss.org/browse/JBIDE-13639 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng, struts/shale > Affects Versions: 4.1.0.Alpha1 > Reporter: Nick Boldt > Assignee: Martin Malina > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > {code:title=https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevStudio_7.0.kepler/job/jbosstools-integration-tests.aggregate_master/53/console} > [ERROR] Cannot resolve project dependencies: > [ERROR] Software being installed: org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier > [ERROR] Missing requirement: org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier requires 'bundle org.jboss.tools.struts.ui 3.1.0' but it could not be found > [ERROR] > [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.struts.ui.bot.test 4.0.0.qualifier to bundle org.jboss.tools.struts.ui 3.1.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1] > {code} > This is failing because struts has been removed from the upstream sites (it's been removed from JBT4.1/JBDS 7). So, need to also remove it from your integration tests site's category.xml file [1]. > [1] https://github.com/jbosstools/jbosstools-integration-tests/blob/master/si... -- 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-13666) Error when renaming a domain with 1+ applications

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13666?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13666: ------------------------------------------ This is a WATCHER/TRACKER issue. This is an issue on the OpenShift platform. There's nothing we can do about it. > Error when renaming a domain with 1+ applications > ------------------------------------------------- > > Key: JBIDE-13666 > URL: https://issues.jboss.org/browse/JBIDE-13666 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Andre Dietisheim > Fix For: 4.1.0.Alpha2 > > Attachments: rename-domain-error.png > > > When trying to rename an existing domain to a domain name which already exists (within different openshift account): > {code} > Could not rename domain "sbunciak": [Operation failed with exit code "1".Reason given: " > Problem: > Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa. > Summary: > When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa. > Resolution: > Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples."] > Could not request https://openshift.redhat.com/broker/rest/domains/pipistik: Operation failed with exit code "1".Reason given: " > Problem: > Document(s) not found for class PendingDomainOps with id(s) 512df956e0b8cd59a20001fa. > Summary: > When calling PendingDomainOps.find with an id or array of ids, each parameter must match a document in the database or this error will be raised. The search was for the id(s): 512df956e0b8cd59a20001fa ... (1 total) and the following ids were not found: 512df956e0b8cd59a20001fa. > Resolution: > Search for an id that is in the database or set the Mongoid.raise_not_found_error configuration option to false, which will cause a nil to be returned instead of raising this error when searching for a single id, or only the matched documents when searching for multiples." > {code} > This message really doesn't describe the real problem - that I'm trying to use a domain name which is already used. -- 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 February 2013