May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13414: ------------------------------------------- Will update the JIRA as soon as I have a build this appears in. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBIDE-13414 > URL: https://issues.jboss.org/browse/JBIDE-13414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Labels: jax-ws, web_service_client > Fix For: 4.3.0.Beta1 > > Attachments: echoService.wsdl, new-error.png, screenshot-1.png > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick updated JBIDE-13414: -------------------------------------- Fix Version/s: 4.3.0.Beta1 (was: LATER) > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBIDE-13414 > URL: https://issues.jboss.org/browse/JBIDE-13414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Labels: jax-ws, web_service_client > Fix For: 4.3.0.Beta1 > > Attachments: echoService.wsdl, new-error.png, screenshot-1.png > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-13414) No Error reported when WS Client code generation fails

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13414?page=com.atlassian.jira.plugi... ] Brian Fitzpatrick commented on JBIDE-13414: ------------------------------------------- Went ahead and merged this into master. > No Error reported when WS Client code generation fails > ------------------------------------------------------ > > Key: JBIDE-13414 > URL: https://issues.jboss.org/browse/JBIDE-13414 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Reporter: Mustafa Musaji > Assignee: Brian Fitzpatrick > Labels: jax-ws, web_service_client > Fix For: 4.3.0.Beta1 > > Attachments: echoService.wsdl, new-error.png, screenshot-1.png > > > If you have a WSDL which would normally fail because of JAXB collision. From command line you would get an error like this: > Failed to invoke WSDLToJava > org.apache.cxf.tools.common.ToolException: Thrown by JAXB: > Thrown by JAXB: > Two declarations cause a collision in the ObjectFactory class. > ... > However, in JBDS you don't get any error. It just doesn't create any sources and there is no indication of what the issue is. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ] Paul Richardson commented on JBIDE-19808: ----------------------------------------- [~nickboldt] Thanks for generating those update sites. According to p2browser, they both show all plugins as PARTIAL and adding them to JBT-IS target again fails validation. I have built the plugins and p2 repository from the [source|https://svn.apache.org/repos/asf/directory/studio/trunk/p2repository/] and that does validate so I expect will need to wait for a release then use a newly-build update site. > Teiid Designer would like to depend on org.apache.directory.studio plugins > -------------------------------------------------------------------------- > > Key: JBIDE-19808 > URL: https://issues.jboss.org/browse/JBIDE-19808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, teiid > Affects Versions: 4.2.3.Final > Reporter: Paul Richardson > Assignee: Barry LaFond > Attachments: p2.diff > > > *Reason:* > Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478]. > The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense. > The current working implementation of Teiid with this widget can be found here: > https://github.com/phantomjinx/teiid-designer/tree/ldap-studio > The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits. > *Project page/sources:* > * [directory.apache.org|https://directory.apache.org] > * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] > * [udpate site | http://directory.apache.org/studio/update/2.x/] > *Version:* 2.0.0 > *License and owner:* Apache licence and Foundation > *Original p2 repo:* http://directory.apache.org/studio/update/2.x/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director... > *Include Sources:* Not available from existing update site but may well be in the next release. > *Affected projects:* Teiid Designer > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > * org.apache.directory.api.ldap.model > * org.apache.directory.studio.common.core > * org.apache.directory.studio.common.ui > * org.apache.directory.studio.connection.core > * org.apache.directory.studio.connection.ui > * org.apache.directory.studio.ldapbrowser.common > * org.apache.directory.studio.ldapbrowser.core > * -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency > {code} >  > <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> > <repository location="http://directory.apache.org/studio/update/2.x/"/> > <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/> > </location> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19808) Teiid Designer would like to depend on org.apache.directory.studio plugins

by Paul Richardson (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19808?page=com.atlassian.jira.plugi... ] Paul Richardson edited comment on JBIDE-19808 at 5/29/15 6:23 AM: ------------------------------------------------------------------ [~nickboldt] Thanks for generating those update sites. According to p2browser, they both show all plugins as PARTIAL and adding them to JBT-IS target again fails validation. I have built the plugins and p2 repository from the [source|https://svn.apache.org/repos/asf/directory/studio/trunk/p2repository/] and that does validate so I expect will need to wait for a release then use a newly-built update site. was (Author: phantomjinx): [~nickboldt] Thanks for generating those update sites. According to p2browser, they both show all plugins as PARTIAL and adding them to JBT-IS target again fails validation. I have built the plugins and p2 repository from the [source|https://svn.apache.org/repos/asf/directory/studio/trunk/p2repository/] and that does validate so I expect will need to wait for a release then use a newly-build update site. > Teiid Designer would like to depend on org.apache.directory.studio plugins > -------------------------------------------------------------------------- > > Key: JBIDE-19808 > URL: https://issues.jboss.org/browse/JBIDE-19808 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, teiid > Affects Versions: 4.2.3.Final > Reporter: Paul Richardson > Assignee: Barry LaFond > Attachments: p2.diff > > > *Reason:* > Teiid Designer currently employs a UI for interrogating and importing metadata from an LDAP server. This UI (2 wizards) is limited and prone to issues, eg. [TEIIDDES-2478|https://issues.jboss.org/browse/TEIIDDES-2478]. > The project [directory.apache.org|https://directory.apache.org] provides a more sophisticated LDAP browser View UI but has componentized into smaller reusable widgets. The BrowserWidget provides the main tree view and querying ability. Teiid would like to reuse this widget in its UI. Originally, an attempt was made to copy the widget yet porting in this fashion required the porting of 100+ classes hence a dependency makes far more sense. > The current working implementation of Teiid with this widget can be found here: > https://github.com/phantomjinx/teiid-designer/tree/ldap-studio > The current release of the apache.directory project is 2 years old. However, speaking to one of the developers on #apache-directory, the project is being actively maintained and a release is being considered with the next couple of months. In addition, the [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] is receiving commits. > *Project page/sources:* > * [directory.apache.org|https://directory.apache.org] > * [svn repository|https://svn.apache.org/repos/asf/directory/studio/trunk] > * [udpate site | http://directory.apache.org/studio/update/2.x/] > *Version:* 2.0.0 > *License and owner:* Apache licence and Foundation > *Original p2 repo:* http://directory.apache.org/studio/update/2.x/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/apache-director... > *Include Sources:* Not available from existing update site but may well be in the next release. > *Affected projects:* Teiid Designer > *Include in JBDS:* Yes > *Type of dependency:* distribution > *List of bundles added/removed:* > * org.apache.directory.api.ldap.model > * org.apache.directory.studio.common.core > * org.apache.directory.studio.common.ui > * org.apache.directory.studio.connection.core > * org.apache.directory.studio.connection.ui > * org.apache.directory.studio.ldapbrowser.common > * org.apache.directory.studio.ldapbrowser.core > * -org.apache.directory.studio.ldapbrowser.ui- Eliminated the dependency > {code} >  > <location includeAllPlatforms="false" includeMode="slicer" includeSource="true" type="InstallableUnit"> > <repository location="http://directory.apache.org/studio/update/2.x/"/> > <unit id="org.apache.directory.studio.ldapbrowser.feature.feature.group" version="2.0.0.v20130628"/> > </location> > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19810) easymport is slow and wrong compared to basic import since it lets mvn overrule .project

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19810?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19810: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > easymport is slow and wrong compared to basic import since it lets mvn overrule .project > ---------------------------------------------------------------------------------------- > > Key: JBIDE-19810 > URL: https://issues.jboss.org/browse/JBIDE-19810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > > when using git://git.eclipse.org/gitroot/mylyn/org.eclipse.mylyn.docs.git it already has tons of projects with .project in it but also pom.xml. Resulting in slow and eventually wrong imported projects. > This import is *really* slow with easyimport vs just using plain file import. > Shouldn't easyimport honor existing .project files over presence of a pom.xml (or anything else) ? > If not could we allow users to disable certain configurators for an import or even reorder priority so mvn wont win ? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19768: ----------------------------------- Fix Version/s: 4.3.0.Beta1 > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19885) Make target deployment destination configurable

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19885?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19885: ---------------------------------------- [~nickboldt] {quote:Nick Boldt} To parameterize these variables into the parent pom, we need variable names. How about these? * jbosstools_rsync_path = t**@f*:/**htdocs/tools * devstudio_rsync_path = d**@f*:/**htdocs/devstudio * jbosstools_site = http://download.jboss.org/jbosstools * devstudio_site = https://devstudio.redhat.com {quote} I'd rather have a more generic "target_rsync_path" variable, that we would override for the JBDS pom files. > Make target deployment destination configurable > ----------------------------------------------- > > Key: JBIDE-19885 > URL: https://issues.jboss.org/browse/JBIDE-19885 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.0.Beta1 > Reporter: Mickael Istria > > Now that deploy steps are in the pom files (JBIDE-18772), it would be interesting to make them parameterized so that we could set up a parallel deployment area for JBoss Tools without pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18772) Include publish steps in pom files

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18772?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-18772: ---------------------------------------- Configurable deployment destination in one step further, worth another jira entry. Please track this discussion in JBIDE-19885. > Include publish steps in pom files > ---------------------------------- > > Key: JBIDE-18772 > URL: https://issues.jboss.org/browse/JBIDE-18772 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Critical > Fix For: 4.3.0.Beta1 > > Attachments: jbds-publish-to-snapshots.png > > > instead of relying to publish.sh being on master, we should use a versioned publish.sh (or maybe even mojo) that the build then uses. > suggestion: > publish.sh (or mojo) gets released to our maven repo, use it in the pom.xml to perform publishing. > What this helps with is: > a) can do changes to publish mechanism without affecting every past builds. > b) more movable build system > c) isolated testing possible > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19885) Make target deployment destination configurable

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-19885: -------------------------------------- Summary: Make target deployment destination configurable Key: JBIDE-19885 URL: https://issues.jboss.org/browse/JBIDE-19885 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: build Affects Versions: 4.3.0.Beta1 Reporter: Mickael Istria Now that deploy steps are in the pom files (JBIDE-18772), it would be interesting to make them parameterized so that we could set up a parallel deployment area for JBoss Tools without pain. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015