[JBoss JIRA] (JBIDE-8531) WSDL files should be accessible to BPEL project from another project (without copying)
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8531?page=com.atlassian.jira.plugin... ]
Robert (Bob) Brodt closed JBIDE-8531.
-------------------------------------
> WSDL files should be accessible to BPEL project from another project (without copying)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-8531
> URL: https://issues.jboss.org/browse/JBIDE-8531
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: bpel
> Affects Versions: 3.2.0.CR1
> Environment: all
> Reporter: Robert (Bob) Brodt
> Assignee: Robert (Bob) Brodt
> Fix For: 3.3.0.CR1-SOA, 3.3.2.Final
>
>
> SOA-P 5.2 PRD document requirement SOA-TOOL-2:
> The SOA-5.2 PRD requirements include the ability of a BPEL project to reference WSDLs (and probably XSDs as well) in another project without having to make copies. The assumption is that all resources are in the same eclipse workspace, not in a file system folder or remote server.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-8531) WSDL files should be accessible to BPEL project from another project (without copying)
by Robert (Bob) Brodt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-8531?page=com.atlassian.jira.plugin... ]
Robert (Bob) Brodt resolved JBIDE-8531.
---------------------------------------
Fix Version/s: 3.3.2.Final
(was: LATER)
Resolution: Done
> WSDL files should be accessible to BPEL project from another project (without copying)
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-8531
> URL: https://issues.jboss.org/browse/JBIDE-8531
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: bpel
> Affects Versions: 3.2.0.CR1
> Environment: all
> Reporter: Robert (Bob) Brodt
> Assignee: Robert (Bob) Brodt
> Fix For: 3.3.2.Final, 3.3.0.CR1-SOA
>
>
> SOA-P 5.2 PRD document requirement SOA-TOOL-2:
> The SOA-5.2 PRD requirements include the ability of a BPEL project to reference WSDLs (and probably XSDs as well) in another project without having to make copies. The assumption is that all resources are in the same eclipse workspace, not in a file system folder or remote server.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Jiri Peterka edited comment on JBDS-2847 at 8/7/14 9:15 AM:
------------------------------------------------------------
[~xcoulon] , I see your point. But it is expected to have it working out of box. If there are some additional actions required these should be available for a user by some QuickFix options or some appropriate automatically invoked wizards. And also Groovy dependencies for JEE example seem strange to me. I would expect this: Projects imported, facets configured and no errors in Problems View. If quickfixes are needed or some connectors need to be installed they should be offered to a user by default. IDE should provide more comfort and than a console approach, not less, don't you think?
was (Author: jpeterka):
[~xcoulon] , I see your point. But it is expected to have it working out of box. If there are some additional actions required these should be available for a user by some QuickFix options or some appropriate automatically invoked wizards. And also Groovy dependencies for JEE example seem strange to me. I would expect this: Projects imported, facets configured and no errors in Problems View. If quickfixes are needed or some connectors need to be installed they should be offered to a user by default. IDE should provide more comfort and then a console approach, not less, don't you think?
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBTIS-221) Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-221?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-221 at 8/7/14 9:12 AM:
----------------------------------------------------------
Complete list of affected files:
[^anonsvn.jboss.org_refs_in_examples_xml.txt]
Workspaces in use include:
* [~snjeza] (seam, portlet, resteasy, weld, richfaces, jbossas7)
* Denny (esb)
* [~elvisisking] (teiid designer)
* [~jdoyle] (teiid designer)
* Grid (bpel, esb)
* [~rcernich] (esb)
* [~fbricon] (archetypeRepo?)
* [~bfitzpat] (SOA 5.2)
* [~dgolovin] (richfaces)
So... the people mentioned above (except for Denny and Grid) need to migrate this content to a new location in github.
Do we want to host all this stuff in a new repo, or just put it into https://github.com/jbosstools/jbosstools-download.jboss.org/tree/master/j... ?
Should the JBTIS stuff be split out into a separate repo? (cc: [~pleacu] )
was (Author: nickboldt):
Complete list of affected files:
[^anonsvn.jboss.org_refs_in_examples_xml.txt]
Workspaces in use include:
* [~snjeza] (seam, portlet, resteasy, weld, richfaces, jbossas7)
* Denny (esb)
* [~elvisisking] (teiid designer)
* [~jdoyle] (teiid designer)
* Grid (bpel, esb)
* [~rcernich] (esb)
* [~fbricon] (archetypeRepo?)
* [~bfitzpat] (SOA 5.2)
* [~dgolovin] (richfaces)
So... the people mentioned above (except for Denny and Grid) need to migrate this content to a new location in github.
Do we want to host all this stuff in a new repo, or just put it into https://github.com/nickboldt/jbosstools-download.jboss.org/tree/master/jb... ?
Should the JBTIS stuff be split out into a separate repo? (cc: [~pleacu] )
> Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-221
> URL: https://issues.jboss.org/browse/JBTIS-221
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Labels: f2f2012
> Attachments: anonsvn.jboss.org_refs_in_examples_xml.txt
>
>
> Instead of referencing files in dev workspaces, commit your files into this path in SVN [1] and they'll appear automatically [2] after the next rsync here [3]. Then you can point at a path that's served via a download server (file tracking, better throughput, backups) instead of our anonsvn web UI (slow, untracked).
> [1] https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool...
> [2] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j...
> [3] http://download.jboss.org/jbosstools/examples/
> These files (line numbers shown) need fixing:
> {code}
> ./project-examples-jbds40.xml
> 851: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 877: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 894: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer...
> ./project-examples-3.2.xml
> 17: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 43: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 60: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Jiri Peterka edited comment on JBDS-2847 at 8/7/14 9:07 AM:
------------------------------------------------------------
[~xcoulon] , I see your point. But it is expected to have it working out of box. If there are some additional actions required these should be available for a user by some QuickFix options or some appropriate automatically invoked wizards. And also Groovy dependencies for JEE example seem strange to me. I would expect this: Projects imported, facets configured and no errors in Problems View. If quickfixes are needed or some connectors need to be installed they should be offered to a user by default. IDE should provide more comfort and then a console approach, not less, don't you think?
was (Author: jpeterka):
[~xcoulon] , I see you point. But it is expected to have it working out of box. If there are some additional actions required these should be available for a user by some QuickFix options or some appropriate automatically invoked wizards. And also Groovy dependencies for JEE example seem strange to me. I would expect this: Projects imported, facets configured and no errors in Problems View. If quickfixes are needed or some connectors need to be installed they should be offered to a user by default. IDE should provide more comfort and then a console approach, not less, don't you think?
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBDS-2847) Java EE 7 Tech Preview
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-2847?page=com.atlassian.jira.plugin.... ]
Jiri Peterka commented on JBDS-2847:
------------------------------------
[~xcoulon] , I see you point. But it is expected to have it working out of box. If there are some additional actions required these should be available for a user by some QuickFix options or some appropriate automatically invoked wizards. And also Groovy dependencies for JEE example seem strange to me. I would expect this: Projects imported, facets configured and no errors in Problems View. If quickfixes are needed or some connectors need to be installed they should be offered to a user by default. IDE should provide more comfort and then a console approach, not less, don't you think?
> Java EE 7 Tech Preview
> ----------------------
>
> Key: JBDS-2847
> URL: https://issues.jboss.org/browse/JBDS-2847
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Xavier Coulon
> Labels: JBDS80_Approved_Scope
> Fix For: 8.0.0.CR1
>
>
> Successfully/cleanly import the Java EE 7 Samples that have been migrated/ported to Wildfly
> https://github.com/javaee-samples/javaee7-samples
> They should import nicely (without errors) into JBT/JBDS and deploy to a JBT/JBDS managed Wildfly.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBTIS-221) Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-221?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-221:
-----------------------------
Attachment: anonsvn.jboss.org_refs_in_examples_xml.txt
Complete list of affected files:
[^anonsvn.jboss.org_refs_in_examples_xml.txt]
Workspaces in use include:
* [~snjeza] (seam, portlet, resteasy, weld, richfaces, jbossas7)
* Denny (esb)
* [~elvisisking] (teiid designer)
* [~jdoyle] (teiid designer)
* Grid (bpel, esb)
* [~rcernich] (esb)
* [~fbricon] (archetypeRepo?)
* [~bfitzpat] (SOA 5.2)
* [~dgolovin] (richfaces)
So... the people mentioned above (except for Denny and Grid) need to migrate this content to a new location in github.
Do we want to host all this stuff in a new repo, or just put it into https://github.com/nickboldt/jbosstools-download.jboss.org/tree/master/jb... ?
Should the JBTIS stuff be split out into a separate repo? (cc: [~pleacu] )
> Move files in developer workspaces in SVN to examples folder in trunk for automated publishing to download.jboss.org/jbosstools/examples/
> -----------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-221
> URL: https://issues.jboss.org/browse/JBTIS-221
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Security Level: Public(Everyone can see)
> Reporter: Nick Boldt
> Assignee: Fred Bricon
> Labels: f2f2012
> Attachments: anonsvn.jboss.org_refs_in_examples_xml.txt
>
>
> Instead of referencing files in dev workspaces, commit your files into this path in SVN [1] and they'll appear automatically [2] after the next rsync here [3]. Then you can point at a path that's served via a download server (file tracking, better throughput, backups) instead of our anonsvn web UI (slow, untracked).
> [1] https://svn.jboss.org/repos/jbosstools/trunk/download.jboss.org/jbosstool...
> [2] http://hudson.qa.jboss.com/hudson/view/DevStudio/view/DevStudio_All/job/j...
> [3] http://download.jboss.org/jbosstools/examples/
> These files (line numbers shown) need fixing:
> {code}
> ./project-examples-jbds40.xml
> 851: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 877: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 894: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer...
> ./project-examples-3.2.xml
> 17: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 43: http://anonsvn.jboss.org/repos/jbosstools/workspace/dflorian/teiid-design...
> 60: http://anonsvn.jboss.org/repos/jbosstools/workspace/jdoyle/teiid-designer...
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months
[JBoss JIRA] (JBIDE-18057) JBoss Server Runtime creation wizard uses a wrong path
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-18057:
-------------------------------------
Summary: JBoss Server Runtime creation wizard uses a wrong path
Key: JBIDE-18057
URL: https://issues.jboss.org/browse/JBIDE-18057
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.2.0.CR1
Reporter: Xavier Coulon
Priority: Blocker
When trying to create a server runtime for Wildfly 8.1, the dialog fails to find the standalone.xml from the installation path that I provided, but it seems like the path itself is wrong.
The dialog reports that it couldn't find {{/Users/xcoulon/DevToolz/jbossas/wildfly-8.1.0.Final/tandalone/configuration/standalone.xml}}
The path above is missing a {{s}} in {{/standalone/}} ;-)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 10 months