[JBoss JIRA] Created: (JBDS-1235) 3rd party certification
by Max Rydahl Andersen (JIRA)
3rd party certification
-----------------------
Key: JBDS-1235
URL: https://jira.jboss.org/browse/JBDS-1235
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Components: Requirements
Reporter: Max Rydahl Andersen
Priority: Blocker
Fix For: 4.0.0.GA
We should define what kind of certifications we want and then certify 3rd party plugins with JBDS
Certifiaction could for example be for Groovy Plugin we know it installs, but beyond that there aren't any guarantees.
For m2eclipse it would be the same with respect to installation but that we support the maven integration plugins and provide fixes for that - but not m2eclipse it self.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-9782) Web Service client throws WebServiceException
by Jaroslav Jankovič (JIRA)
Web Service client throws WebServiceException
---------------------------------------------
Key: JBIDE-9782
URL: https://issues.jboss.org/browse/JBIDE-9782
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: Webservices
Affects Versions: 3.2.2.M1
Environment: JBoss EAP, JBDS 4.1.1 M1
Reporter: Jaroslav Jankovič
Assignee: Brian Fitzpatrick
Fix For: 3.2.2.M1
1. create Sample Web Service through wizard
2. create Bottom Up Web Service from class (created in 1. step) through wizard
3. deploy Web Service
4. create Web Service Client through wizard
5. run Web Service Client as java application
After running Web Service Client as Java application, WebServiceException is thrown.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (TOOLSDOC-252) No version update in JBDS documentation.
by Jaroslav Jankovič (JIRA)
No version update in JBDS documentation.
----------------------------------------
Key: TOOLSDOC-252
URL: https://issues.jboss.org/browse/TOOLSDOC-252
Project: Documentation for JBoss Tools and Developer Studio
Issue Type: Bug
Security Level: Public (Everyone can see)
Components: General documentation issues
Affects Versions: 3.2.2.Final
Reporter: Jaroslav Jankovič
Assignee: Isaac Rooskov
Fix For: 3.2.2.Final
JBDS 4.1.1 M1 documentation refers to 4.1.0 GA. I have checked some components and all of them have "Edition 4.1.0" in the title page. Revision history said, that no changes has been made too. I would like to know, if any changes since 4.1.0 GA version have been made and if so, please update documentation properly (title, revision history) because it seems like there is only one branch for JBDS 4.1 refering to 4.1.0 GA version.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months
[JBoss JIRA] Created: (JBIDE-9497) Add support for SAR projects
by Fred Bricon (JIRA)
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects (a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects, most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
>From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
14 years, 6 months