Fwd: JBoss Community announces GIT Pull Request Workflow
by Kabir Khan
Can we enable this for JBoss AS?
Begin forwarded message:
> From: Randall Hauch <rhauch(a)redhat.com>
> Date: 5 April 2011 21:55:53 GMT+01:00
> To: Kabir Khan <kabir.khan(a)jboss.com>
> Cc: The Core <thecore(a)redhat.com>, Mark Newton <mnewton(a)redhat.com>
> Subject: Re: JBoss Community announces GIT Pull Request Workflow
>
> It needs to be explicitly enabled on each JIRA project. See the last paragraph of Mark's email.
>
> On Apr 5, 2011, at 3:19 PM, Kabir Khan wrote:
>
>> I don't see this in the JBAS project? Does it need to be explicitly enabled, or am I looking in the wrong place (the options I get when clicking 'Resolve')?
>> On 24 Mar 2011, at 13:35, Mark Newton wrote:
>>
>>> Hi,
>>>
>>> The JBoss Community Team are proud to announce the availability of the "GIT Pull Request Workflow" in our JIRA instance (http://issues.jboss.org).
>>>
>>> This workflow may be a good choice for projects that want to use better GIT Pull Requests tracking.
>>>
>>> It adds a new step called "Pull Request Sent" into the workflow indicating that work was done for given issue and a pull request has been prepared to be applied into the upstream GIT repository. The "Link Pull Request" action allows a transition to this new step with the possibility to insert a pull request URL into a newly introduced custom field called "Git Pull Request". The issue is then Resolved after the GIT pull request is applied upstream.
>>>
>>> Special thanks go to Dan Allen who came up with the idea and the first version of the workflow for the Seam project. Thanks also go to Lukas Fryc who pointed our team to Dan's workflow and initiated the generalization (he now uses it for the ARQAJO and ARQRUSH projects). The current version of the workflow is slightly improved and generalized to be applicable for other projects too:
>>>
>>> https://issues.jboss.org/browse/ORG-973
>>>
>>> To use this new workflow your jira project must be switched to use "GIT Pull Request workflow scheme". Project Leads can contact the JBoss Community Team by emailing eng-ops(a)redhat.com to create a ticket to perform this change if they can't do it themselves.
>>>
>>> Enjoy!
>>>
>>> Mark Newton
>>> JBoss Community Lead
>>> Mobile: +41 7657 47730
>>> Office: +41 41 760 4636
>>> Email: mnewton(a)redhat.com
>>>
>>
>>
>
>
13 years
JDBC driver version requirement
by Heiko Braun
In order to configure a JDBC driver, I need to specify a driver version
as part of the driver name:
"driver" => {
"description" => "Defines the JDBC driver the datasource should use with this format: <driver-name>#<major-version>.<minor-version> where <driver-name> is the fully qualifed name of the JDBC driver class",
"type" => STRING,
"required" => true,
"access-type" => "read-only",
"storage" => "configuration"
},
IMO this is really awkward and for the average user close to impossible to figure the driver version.
Can somebody explain this requirement?
Ike
13 years
webdav for deployments
by Heiko Braun
has this topic been discussed already?
would it make sense to provide a web dav entry point for the domain content repository?
Ike
13 years
A plea - commit messages
by Heiko W.Rupp
Hi,
while a jira number points to the issue / new feature, only having this in the commit message
is not nice when browsing for changes.
>From the github rss feed:
• maeste committed 5dcb774
JBAS-9334
As the jira-id is not clickable it is cumbersome to lookup, to see if this is something
"of interest".
So my plea: please also add a short description or the jira subject line to the commit message
Heiko
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Brendan Lane, Charlie Peters, Michael Cunningham, Charles Cachera
13 years
Where can I find jboss-ejb3.xsd ?
by Marchioni Francesco
Dear JBoss Dev,
I'm looking for EJB 3.1 configuration parameters. Digging into jboss-as at Github I couldn't find jboss-ejb3.xsd.
Do you have any reference to this .xsd ?
Thanks a lot
Francesco
--------------------------------------------------------------------------------------------------------
Le informazioni trasmesse possono contenere documenti confidenziali e/o materiale riservato; sono
quindi da intendersi esclusivamente ad uso della persona e/o società a cui sono indirizzate.
Qualsiasi modifica, inoltro, diffusione o altro utilizzo, relativo alle informazioni trasmesse, da parte
di persone e/o società diversi dai destinatari indicati, è proibito ai sensi della legge 196/2003.
Qualora questa mail fosse stata ricevuta per errore, si prega di contattare il mittente e cancellarne
il contenuto.
--
Privileged/Confidential Information may be contained in this message. If you are not the addressee
indicated in this message (or responsible for delivery of the message to such person), you may not
copy or deliver this message to anyone. In such case, you should destroy this message and kindly
notify the sender by reply email. Please advise immediately if you or your employer does not consent
to Internet email for messages of this kind. Opinions, conclusions and other information in this
message that do not relate to the official business of my firm shall be understood as neither given
nor endorsed by it.
--------------------------------------------------------------------------------------------------------
13 years
Locating JDBC drivers
by Heiko Braun
I managed to deploy JDBC drivers through the HTTP API.
Creating datasources works as well. The remaining question is:
How to I locate the JDBC drives that are installed as a deployment?
They don't show up under /subsystem=datasources/jdbc-driver=*
In order to create the Datasource I need to provide a list of available drives to the user.
Ike
13 years
JBAS-8680 and JBAS-9178
by Kabir Khan
I'm taking these unassigned issues
• JBAS-8680 More robust handling of previous versions of the configuration files
• JBAS-9178 Ability to specify config file from the command line
If anybody is already working on these please let me know :-)
13 years
