March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13386) Create dedicated Git repo for target platforms

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13386?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-13386. ------------------------------ > Create dedicated Git repo for target platforms > ---------------------------------------------- > > Key: JBIDE-13386 > URL: https://issues.jboss.org/browse/JBIDE-13386 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha1 > > > Since target platforms follow their own schedule, independently of JBT/JBDS and we maintain many streams, it would be more convenient to have them in their own Git repo. -- 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13599: --------------------------------------------- btw. here is the usecase for recursive replacement: ${jboss.discovery.mylyn.site:${jboss.central.site.url:http://devstudio.jboss.com/updates/staging/etc/}} ${jboss.discovery.atlassian.site:${jboss.central.site.url:http://devstudio.jboss.com/updates/staging/etc/}} Now QE and others can in normal cases just use -Djboss.central.site.url, and if you need to test for specific subsites (for quick/easy testing) you can set it individually. Allows you to test central with smaller sites instead of one big working one. > 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 Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13599: --------------------------------------------- Len - this feature is not done yet. Use the old/regular approach sent around in the email. > 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-13706) Cannot install Google tools from Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13706?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-13706. ------------------------------ I have successfully installed Google tools in JBT 4.1.0.Alpha1c. Closing. > Cannot install Google tools from Central > ---------------------------------------- > > Key: JBIDE-13706 > URL: https://issues.jboss.org/browse/JBIDE-13706 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Alpha1 > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Blocker > Fix For: 4.1.0.Alpha1 > > > Here is what log says: > {code} > Contains: Cannot complete the install because one or more required items could not be found. > Contains: Software being installed: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711) > Contains: Missing requirement: WindowBuilder XML Core (requires Eclipse WTP/WST) 1.5.2.r42x201302111919 (org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919) requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found > Contains: Cannot satisfy dependency: > Contains: From: GWT Designer Editor 3.1.2.r42x201302131711 (com.google.gdt.eclipse.designer.editor.feature.feature.group 3.1.2.r42x201302131711) > Contains: To: org.eclipse.wb.core.xml.feature.feature.group 1.5.2.r42x201302111919 > {code} > Main message: *requires 'org.eclipse.wb.core.java.feature.feature.group 1.5.2.r42x201302111907' but it could not be found* -- 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-11495) Improve ability to configure dependent hudson jobs and provide accessable documentation

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11495?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-11495: ---------------------------------------- Should this issue move to the new JBTIS project? The ability to have more control over dependencies could be resolved by component-specific target platforms (ie each component uses a target-definition or some repositories in its pom to specify dependencies). > Improve ability to configure dependent hudson jobs and provide accessable documentation > --------------------------------------------------------------------------------------- > > Key: JBIDE-11495 > URL: https://issues.jboss.org/browse/JBIDE-11495 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: Build/Releng > Reporter: Barry LaFond > Assignee: Douglas Palmer > Fix For: 4.0.x > > > SOA decoupling has elevated the need to have more configurable control over upstream and downstream dependencies. > Notes from Nick: > * a number of jobs are now set to build only when triggered by upstream, but SOA stuff is not as well handled > * ideally you'd want: a) check svn every N hours (usually 6) and b) upstream should use Parameterized Trigger to cause downstream to fire > * you can also ensure that you're building against a stable aggregate using an override like the one I've set up for SOA Tooling aggregate... > * in your maven invocation, under Properties, you can do this: # use latest upstream nightly Core update site instead of "wild components" in the composite staging site jbosstools-nightly-staging-composite=http://download.jboss.org/jbosstools... > * that way you pull from the aggregate (updates weekly) instead of the composite (updates every time a component respins) > * means if you depended on something like tests/common/jst/vpe/jsf/seam/maven/central/usage stack, you wouldn't need to worry about getting incompatible pieces -- 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-13749) "Abridged Jboss Tools" category has 4.0 version in label

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13749?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13749. ------------------------------------ Resolution: Done Fixed with commit https://github.com/jbosstools/jbosstools-build-sites/commit/d279d49e8a589... > "Abridged Jboss Tools" category has 4.0 version in label > -------------------------------------------------------- > > Key: JBIDE-13749 > URL: https://issues.jboss.org/browse/JBIDE-13749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > Attachments: installDialog.png > > > AbridgedTools category still has label "Abridged JBoss Tools 4.0" (version should be 4.1) > !installDialog.png! -- 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-13731) error when creating html5 project from central: duplicate listener

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13731?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-13731: --------------------------------------------- Martin/Stefan - just because you opened the project from central don't mean the issue is for central - I would say in most cases it is not central :) i.e. this error would most likely also happen if you import the plain project and just added jpa/hibernate to it. Thus moving this to hibernate conmponent so central doesn't gets filled with non-related issues :). > error when creating html5 project from central: duplicate listener > ------------------------------------------------------------------ > > Key: JBIDE-13731 > URL: https://issues.jboss.org/browse/JBIDE-13731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Environment: JBDS 7.0.0.Alpha1c B124 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you try to create the html5 project from JBoss Central, you get this error in the workspace log: > {code} > !ENTRY org.eclipse.jpt.jpa.core 4 0 2013-03-06 13:45:23.414 > !MESSAGE duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile)) > !STACK 0 > java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile)) > at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95) > at org.eclipse.jpt.common.core.resource.xml.JptXmlResource.addResourceModelListener(JptXmlResource.java:270) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:587) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:560) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1664) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:264) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1649) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1841) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1833) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1816) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1627) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1619) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:759) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:741) > at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13731) error when creating html5 project from central: duplicate listener

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13731?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-13731: ---------------------------------------- Component/s: hibernate (was: central) > error when creating html5 project from central: duplicate listener > ------------------------------------------------------------------ > > Key: JBIDE-13731 > URL: https://issues.jboss.org/browse/JBIDE-13731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Affects Versions: 4.1.0.Alpha1 > Environment: JBDS 7.0.0.Alpha1c B124 > Reporter: Martin Malina > Assignee: Snjezana Peco > Fix For: 4.1.0.Alpha2 > > > When you try to create the html5 project from JBoss Central, you get this error in the workspace log: > {code} > !ENTRY org.eclipse.jpt.jpa.core 4 0 2013-03-06 13:45:23.414 > !MESSAGE duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile)) > !STACK 0 > java.lang.IllegalArgumentException: duplicate listener: AbstractJpaProject.ResourceModelListener[06-25-5B-29](HibernateJpaProject[7E-83-E3-E5](jboss-as-kitchensink-html5-mobile)) > at org.eclipse.jpt.common.utility.internal.ListenerList.add(ListenerList.java:95) > at org.eclipse.jpt.common.core.resource.xml.JptXmlResource.addResourceModelListener(JptXmlResource.java:270) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe_(AbstractJpaProject.java:587) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.addJpaFileMaybe(AbstractJpaProject.java:560) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.synchronizeJpaFiles(AbstractJpaProject.java:1664) > at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject.synchronizeJpaFiles(HibernateJpaProject.java:264) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$InternalResourceDeltaVisitor.fileChangeIsSignificant(AbstractJpaProject.java:1649) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.fileChanged(AbstractJpaProject.java:1841) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visit(AbstractJpaProject.java:1833) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80) > at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject$ResourceDeltaVisitor.visitDelta(AbstractJpaProject.java:1816) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.internalProjectChanged(AbstractJpaProject.java:1627) > at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.projectChanged(AbstractJpaProject.java:1619) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager.projectChanged_(InternalJpaProjectManager.java:759) > at org.eclipse.jpt.jpa.core.internal.InternalJpaProjectManager$ProjectChangeEventHandlerCommand.execute(InternalJpaProjectManager.java:741) > at org.eclipse.jpt.common.core.internal.utility.command.JobCommandJob.run(JobCommandJob.java:42) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {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, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-13749) "Abridged Jboss Tools" category has 4.0 version in label

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13749?page=com.atlassian.jira.plugi... ] Mickael Istria reassigned JBIDE-13749: -------------------------------------- Assignee: Mickael Istria (was: Nick Boldt) > "Abridged Jboss Tools" category has 4.0 version in label > -------------------------------------------------------- > > Key: JBIDE-13749 > URL: https://issues.jboss.org/browse/JBIDE-13749 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Build/Releng > Affects Versions: 4.1.0.Alpha1 > Reporter: Radim Hopp > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > Attachments: installDialog.png > > > AbridgedTools category still has label "Abridged JBoss Tools 4.0" (version should be 4.1) > !installDialog.png! -- 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-13719) Set up CI job + publication for jbosstools-aerogear

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13719?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-13719. ------------------------------------ Resolution: Done Publish script did work after a couple of tweaks. jbosstools-aerogear now builds normally on CI at https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... and ouput repo is published at http://download.jboss.org/jbosstools/builds/staging/jbosstools-aerogear_m... > Set up CI job + publication for jbosstools-aerogear > --------------------------------------------------- > > Key: JBIDE-13719 > URL: https://issues.jboss.org/browse/JBIDE-13719 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aerogear-hybrid, Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Fix For: 4.1.0.Alpha2 > > > Set up CI job for jbosstools-aerogear and publish nightly 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

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