December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-15383) Server Launch Configuration loses Classpath User Entries

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15383?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-15383. --------------------------------- I checked that custom entries are properly persisted - they do not disappear. And the revert button works as expected. Closing. Verified in JBDS 8.0.1.CR1 B333. > Server Launch Configuration loses Classpath User Entries > -------------------------------------------------------- > > Key: JBIDE-15383 > URL: https://issues.jboss.org/browse/JBIDE-15383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.0.Final > Environment: Windows 7 64-bit, Java7u25 64-bit, Eclipse Kepler, JBoss AS 7.1.1 > Reporter: Daniel Atallah > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: JBIDE_1.png, JBIDE_2.png, JBIDE_3.png > > > Any additions to the Server Launch Configuration's Classpath "User Entries" are lost when the dialog is closed and reopened. > This is likely related; there appears to be an issue where the initial values of "User Entries" are also incorrect (and are reverted from the "Restore Default Entries" value) when the dialog is reopened. > Specifically, the "org.jboss.ide.eclipse.as.core.server.launch.runJarContainer/JBoss 7.1 Runtime Server" library to a single external "jboss-modules.jar". > The attachments describe what happens: > * The initial state when editing the Launch Configuration is in [^JBIDE_1.png]. > * When the "Restore Default Entries" button is clicked, the values are changed to what should be the default state ([^JBIDE_2.png]). > * When the dialog is closed and reopened, it reverts back to the way it appeared in [^JBIDE_1.png]. > * Similarly if I manually add an external directory (or any other entry, for that matter), as appears in [^JBIDE_3.png], after closing and reopening the dialog, it reverts back to the [^JBIDE_1.png] state. > I've tried simply clicking "OK" and also making sure I click "Apply" before clicking "OK", but that doesn't seem to have an effect. > I've been able to replicate this on two separate (similarly configured) machines. > This sounds very similar to JBIDE-786, but that's very old and marked as Resolved a long time ago, so I figured it'd be appropriate to file a new issue. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16580) jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16580?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen closed JBIDE-16580. --------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.Beta1) Resolution: Done marking as closed! missed in query for bulk update ;/ > jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16580 > URL: https://issues.jboss.org/browse/JBIDE-16580 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Final > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16580) jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16580?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-16580: ---------------------------------------- Epic Status: Done (was: To Do) > jboss.org/tools does not represent the current state/feature set of the tooling. We should update our website to show off all the awesome features and provide easier download > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-16580 > URL: https://issues.jboss.org/browse/JBIDE-16580 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: website > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 4.2.0.Beta1 > > -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18741) Java EE 7 batch API missing from WildFly classpath container

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18741?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-18741. --------------------------------- I checked that the missing classpath entries are now added (not only are they now included in Default Set in preferences, but when I create a dynamic web project, they are included in the classpath). Rasto is right that those two (deploy.api and xml.registry.api) are not there (they are in the default list, but not in the actual classpath when I create a project). But I guess that's not an issue to have something extra there. Verified in JBDS 8.0.1.CR1 B333. > Java EE 7 batch API missing from WildFly classpath container > ------------------------------------------------------------ > > Key: JBIDE-18741 > URL: https://issues.jboss.org/browse/JBIDE-18741 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Final > Reporter: Valentin Baciu > Assignee: Rob Stryker > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > > I recently upgraded to Eclipse Luna SR1 + JBoss Tools 4.2 and my workspace failed to build properly. > It appears that the javax.batch API is missing from the WildFly classpath container. The API is exposed by the javax.batch.api WildFly module (jboss-batch-api_1.0_spec-1.0.0.Final.jar). > As a workaround, I had to add the module via Preferences->Server->Runtime Environments->Default Classpath Entries. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-350) Missing BPEL source plugins

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-350?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-350: ----------------------------------------- If you install org.jboss.tools.bpel.feature you will get all bpel bundles (15), but if you install org.jboss.tools.bpel.source.feature you will get only org.jboss.tools.bpel.runtimes.source. This is quite useless feature. Note that all the other source features install appropriate source bundles. > Missing BPEL source plugins > --------------------------- > > Key: JBTIS-350 > URL: https://issues.jboss.org/browse/JBTIS-350 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 8.0.0.Beta1 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > > After installing all components included in Beta1 there are only the following souce plugins for BPEL > org.jboss.tools.bpel.runtimes.source_1.2.101.Final-v20140108-1353-B1045.jar > org.switchyard.tools.ui.bpel.source_2.0.0.v20141011-0508-H499-Alpha3.jar > but there are much more BPEL plugins such as > org.eclipse.bpel.ui, org.eclipse.bpel.ui.validator -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18692) Jenkins build for jbosstools-incubator-ripple

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18692?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18692: ------------------------------------- [~mickael_istria] it would be great to have all files from the pkg/hosted folder directly at the root of the zip > Jenkins build for jbosstools-incubator-ripple > --------------------------------------------- > > Key: JBIDE-18692 > URL: https://issues.jboss.org/browse/JBIDE-18692 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Gorkem Ercan > Assignee: Mickael Istria > Fix For: 4.3.0.Alpha1 > > > We need a jenkins job to build for jbosstools-incubator-ripple, and have it > invoking "./configure && jake" and distribute the builds to Nexus so that cordovasim can start using ripple from this repo. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- Snaphots/ folder should have the same layout as /staging/ and others (with composites referencing central, TP and so on). > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3208) reorg/refactor directories for consistency across JBT/JBDS

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBDS-3208?page=com.atlassian.jira.plugin.... ] Mickael Istria commented on JBDS-3208: -------------------------------------- {quote}/stable (updates/mars/stable is a pointer back into updates/mars){quote} Do we really want updates/mars to contain anything at all? And if we want it to be a p2 repo, I believe it's easier to have update/mars referencing updates/mars/stable. > reorg/refactor directories for consistency across JBT/JBDS > ---------------------------------------------------------- > > Key: JBDS-3208 > URL: https://issues.jboss.org/browse/JBDS-3208 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: build > Affects Versions: 9.0.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 9.0.0.Alpha1 > > > Be it resolved - we should reorg directories for consistency across JBT/JBDS: > {code} > download.jboss.org > <earlyaccess,updates,discovery>/mars > /snapshots [replace nightly] > /staging [rename content for QE, moves to development when approved] > /development > /stable (updates/mars/stable is a pointer back into updates/mars) > drop /integration (not used) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > and > {code} > devstudio.redhat.com > <earlyaccess,updates,discovery>/9.0 > /snapshots > /staging > /development > /stable (updates/9.0/stable is a pointer back into updates/9.0) > builds/<jobname>/<buildid> > builds/<jobname>/composite*.xml for last 2 builds > targetplatforms/<type>/<version> > {code} > Further discussion in http://ether-man.rhcloud.com/p/build.next.20141112 > This would remove the idea of the composite staging site [1] and the composite install job [2], today used to determine when it's time to run the aggregate builds, in favour of a new p2diff mechanism for determining if aggregates should be published. See JBIDE-18742 and JBIDE-16970. > [1] http://download.jboss.org/jbosstools/builds/staging/_composite_/core/4.2.... > [2] https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18559) when no updates available the full but empty p2 install UI is still shown

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18559?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18559: ----------------------------------- Affects Version/s: 4.2.0.Final > when no updates available the full but empty p2 install UI is still shown > ------------------------------------------------------------------------- > > Key: JBIDE-18559 > URL: https://issues.jboss.org/browse/JBIDE-18559 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > run check for updates from central with no updates available. > P2 ui with two step wizards is shown with no content. > Would have expected something like a simple "No updates found" instead. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18559) when no updates available the full but empty p2 install UI is still shown

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18559?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-18559: ----------------------------------- Priority: Minor (was: Major) > when no updates available the full but empty p2 install UI is still shown > ------------------------------------------------------------------------- > > Key: JBIDE-18559 > URL: https://issues.jboss.org/browse/JBIDE-18559 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: central > Affects Versions: 4.2.0.Final > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha1 > > > run check for updates from central with no updates available. > P2 ui with two step wizards is shown with no content. > Would have expected something like a simple "No updates found" instead. -- This message was sent by Atlassian JIRA (v6.3.8#6338)

11 years, 4 months

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 December 2014