Bind connection factories into JNDI
-----------------------------------
Key: JBJCA-258
URL: https://jira.jboss.org/jira/browse/JBJCA-258
Project: JBoss JCA
Issue Type: Task
Components: Deployer
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Bind each connection factory into JNDI.
Also set the naming reference in each connection factory.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
SJC: Add support for property maps
----------------------------------
Key: JBJCA-106
URL: https://jira.jboss.org/jira/browse/JBJCA-106
Project: JBoss JCA
Issue Type: Task
Components: Core
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0.0.Alpha2
Add support for property maps, so they can be passed in the configuration.
The remotable naming server is an example of an use-case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Add Maven based build system
----------------------------
Key: JBJCA-3
URL: https://jira.jboss.org/jira/browse/JBJCA-3
Project: JBoss JCA
Issue Type: Sub-task
Components: Build
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Fix For: 1.0 Alpha1
Add Maven style build environment
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Define JCA SPI
--------------
Key: JBAS-5426
URL: http://jira.jboss.com/jira/browse/JBAS-5426
Project: JBoss Application Server
Issue Type: Task
Security Level: Public (Everyone can see)
Components: JCA service
Reporter: Jesper Pedersen
Assigned To: Jesper Pedersen
Fix For: JBossAS-5.0.0.CR1
We need to define a SPI for the JCA layer in order to better separate clients (f.ex. EJB3) of JCA from the actual implementation.
The SPI will live in the jboss-integration module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Provide JCA 1.5 profile of the container
----------------------------------------
Key: JBJCA-268
URL: https://jira.jboss.org/jira/browse/JBJCA-268
Project: JBoss JCA
Issue Type: Task
Components: Build, Common, Core, Deployer, Documentation, Embedded
Reporter: Jesper Pedersen
Assignee: Jesper Pedersen
Priority: Blocker
Fix For: 1.1.0.CR1
Create a JCA 1.5 profile of the container
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
Look into bug with maven plugin manager.
----------------------------------------
Key: JBBUILD-430
URL: http://jira.jboss.com/jira/browse/JBBUILD-430
Project: JBoss Build System
Issue Type: Task
Components: Maven
Reporter: Paul Gier
Fix For: Maven Build - Maint 2007
There seems to be a bug in maven in the plugin resolution when there are different versions of plugins available in different repositories.
A maven bug should be submitted, and the issue should be patched.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
The audit plugin seems to conflict with checksum validation
-----------------------------------------------------------
Key: JBBUILD-658
URL: https://jira.jboss.org/browse/JBBUILD-658
Project: JBoss Build System
Issue Type: Bug
Components: Artifact Repositories
Reporter: Paul Gier
Fix For: Repository Support 2010
When the checksum validation is turned on in Nexus it complains about missing checksums for the audit.json files. The Audit plugin should either generate these checksums, or integrate with Nexus to have them automatically generated before the staging repository is closed.
--
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
Add description field to nexus audit plugin
-------------------------------------------
Key: JBBUILD-631
URL: https://jira.jboss.org/browse/JBBUILD-631
Project: JBoss Build System
Issue Type: Feature Request
Components: Artifact Repositories
Reporter: Paul Gier
Assignee: John Casey
Fix For: Repository Support 2010
The audit plugin currently has no information in the description field in the nexus plugin console. A description should be added so that it's easy for new users to understand the purpose of the plugin.
--
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