March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13656) New project dialog from central does not reflect runtimes defined in stacks.yaml

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13656?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13656: --------------------------------------- In order to use stacks.yaml, we have to fix JBIDE-13686. We also need some other properties in stacks.yaml to download runtimes. They are the following: - license URL - size - disclaimer (true for a community runtime) - requireSso (if https://github.com/jbosstools/jbosstools-base/pull/50 is applied) These properties can be added as labels. JBT runtime IDs: JBoss AS 3.2-7.1: org.jboss.ide.eclipse.as.runtime.32 org.jboss.ide.eclipse.as.runtime.40 org.jboss.ide.eclipse.as.runtime.42 org.jboss.ide.eclipse.as.runtime.50 org.jboss.ide.eclipse.as.runtime.51 org.jboss.ide.eclipse.as.runtime.60 org.jboss.ide.eclipse.as.runtime.70 org.jboss.ide.eclipse.as.runtime.71 EAP 4.3-6.1 (EPP, SOA-P, EWP use the same IDs): org.jboss.ide.eclipse.as.runtime.eap.43 org.jboss.ide.eclipse.as.runtime.eap.50 org.jboss.ide.eclipse.as.runtime.eap.60 org.jboss.ide.eclipse.as.runtime.eap.61 I am not sure if there is a JDF jira related to this issue, but will fix the issue when the JDF team names a label property(ies). > New project dialog from central does not reflect runtimes defined in stacks.yaml > -------------------------------------------------------------------------------- > > Key: JBIDE-13656 > URL: https://issues.jboss.org/browse/JBIDE-13656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.0.0.Final, 4.1.0.Alpha1 > Environment: JBDS 7.0.0.Alpha1b > Reporter: Martin Malina > Assignee: Fred Bricon > Fix For: 4.0.0.Final, 4.1.0.Alpha2 > > > This is a follow-up of JDF-216. > They created a new branch of jdf-stacks to test EAP 6.1. But even if I used that branch using > -Dorg.jboss.examples.stacks.url=https://raw.github.com/jboss-jdf/jdf-stack/eap6.1/stacks.yaml > I am still told that the required runtime is not defined and that I need to have EAP 6 or AS 7. > The dialog should take advantage of the information provided by stacks.yaml and notice that the correct server is defined. > See JDF-216 for more details. -- 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 Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-13599: --------------------------------------- {quote} btw. here is the usecase for recursive replacement: {quote} In order that feature to work, we have to update the dmr plugin. Would you like me to do it? > 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-13731) error when creating html5 project from central: duplicate listener

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13731?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13731: --------------------------------------- ok, thanks, Max > 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] (JBDS-2401) remove old version of installer code & refactor new stuff to remove "pde" from the name

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBDS-2401?page=com.atlassian.jira.plugin.... ] Pavol Srna closed JBDS-2401. ---------------------------- > remove old version of installer code & refactor new stuff to remove "pde" from the name > --------------------------------------------------------------------------------------- > > Key: JBDS-2401 > URL: https://issues.jboss.org/browse/JBDS-2401 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.0.0.Alpha1 > > Attachments: jbds2401.patch.txt > > > Many moons ago, we forked the inpack installer code so that we now have these files: > {code:title=https://svn.jboss.org/repos/devstudio/trunk/product/installer} > ./build-pde.xml > ./src/config/install-pde.xml > ./src/config/resources/default_shortcut_specification_pde.xml > ./src/config/resources/p2-meta-gen-action-pde.xml > ./src/config/resources/p2-meta-gen-script-pde.xml > ./src/config/resources/readme-pde.txt > ./src/config/resources/unix_shortcut_specification_pde.xml > and > ./build.xml > ./src/config/install.xml > ./src/config/resources/default_shortcut_specification.xml > ./src/config/resources/p2-meta-gen-action.xml > ./src/config/resources/p2-meta-gen-script.xml > ./src/config/resources/readme.txt > ./src/config/resources/unix_shortcut_specification.xml > {code} > The old code should be removed from trunk, and the new stuff refactored so that there's no longer a "-pde" or "_pde" marker in it, since we don't build w/ PDE anymore. -- 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-10541) If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-10541: ------------------------------------------ put to 4.1.x since there's no urgency to this. It would be a nice enhancement though > If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Fix For: 4.1.x > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- 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-13562) Repository is synchronized but adapter states [Started, Republish]

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13562?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-13562: ------------------------------------------ Rob, any chance we can fix this for Alpha2 or should we move this to later? > Repository is synchronized but adapter states [Started, Republish] > ------------------------------------------------------------------ > > Key: JBIDE-13562 > URL: https://issues.jboss.org/browse/JBIDE-13562 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, openshift > Affects Versions: 4.1.0.Alpha1 > Reporter: Stefan Bunciak > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > Attachments: console.png, server.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-10541) If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-10541?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-10541: ------------------------------------- Fix Version/s: 4.1.x (was: 4.1.0.Alpha2) > If I add a file to my project, the OpenShift server adapter does not handle it well: should show EGit commit dialog > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-10541 > URL: https://issues.jboss.org/browse/JBIDE-10541 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 3.3.0.M5 > Reporter: Andre Dietisheim > Assignee: Max Rydahl Andersen > Fix For: 4.1.x > > > Currently the dialog showing up when committing/pushing is confusing since it says there are no changes which is not correct if comparing to opehsfnit remote repo. > Should make a check against the fetched upstream and see what has changed since that is a fast local operation. -- 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: ---------------------------------------- [~maxandersen]: Both sentences are not correlated. They are 2 distinct ideas. Nothing to elaborate ;) > 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-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: --------------------------------------------- [~nickboldt](d) is problematic. Then you would have never versions of something that might be build from older than the actual real build. Adding -CI or just a -dev qualifer or something could work. But apparently according to tycho-dev this should be possible of this plugin already but isn't. > 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-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: --------------------------------------------- [~mickael_istria] not following what you meant here: "It's possible to exclude pom from watched resources for the Git timestamp provider. Ideally, we would like to achieve a similar behaviour that would ignore qualifiers, so we won't have to brainstorm about what's the best qualifier to implement this, Tycho would take an already built bundle if the content are the same, except qualifier." Not following how exclude pom from watched resources relates to the latter about "similar behaviour" and ignoring qualifiers. CAn you elaborate ? > 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

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