Yes, I was thinking about that too.. <div>I think that the folder+http access is OK for now and I understand tihomir points on the matter, but if we will keep it in that way, what about having a public github repository with all the source code and the compiled version in the same place. To keep them separate from the jBPM source code.. allowing easy compilation and collaboration from the open source community. My two cents..</div>
<div><br></div><div>Cheers<br><br><div class="gmail_quote">On Tue, Mar 13, 2012 at 7:31 PM, Giovanni Marigi <span dir="ltr"><<a href="mailto:gmarigi@redhat.com">gmarigi@redhat.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Kris,<br>
I was wondering why the workitems included in the jbpm-workitems module are not in the repo :-) some of them are really useful and I took inspiration from the java handler to create a EJB work item.<br>
<br>
I don't know if it's too much risky but opening it to the community with a kind of "open" API to publish servie tasks, maybe can give even more enthusiasm to jbpm 5.x<br>
Another point; I think the old jbpm 3 suffered from the lack of "adapters"; if there is a maintained and public repo with service tasks I think even the integration between jbpm and external systems can be easier.<br>
<span class="HOEnZb"><font color="#888888"><br>
Giovanni<br>
</font></span><div class="im HOEnZb"><br>
----- Original Message -----<br>
From: "Kris Verlaenen" <<a href="mailto:kverlaen@redhat.com">kverlaen@redhat.com</a>><br>
To: "Giovanni Marigi" <<a href="mailto:gmarigi@redhat.com">gmarigi@redhat.com</a>><br>
Cc: <a href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
</div><div class="HOEnZb"><div class="h5">Sent: Tuesday, March 13, 2012 8:23:32 PM<br>
Subject: Re: [jbpm-dev] [JBPM 5.x] service task repository<br>
<br>
Giovanni,<br>
<br>
You are right, the current repo hasn't been extended to include the other service tasks that are already implemented in the jbpm-workitems module. Some of them have already been configured, documented and tested and should just be uploaded, I'll try to do that asap. We have made it an action item that every team member contributes a service task to the repository once in a while.<br>
<br>
We would also welcome contributions. There is no predefined automated process there, but we would like to evaluate if JIRA might be used for this purpose (where the necessary files are attached, we review and add to the repository). But we welcome any feedback.<br>
<br>
The service repository integration currently is based on a defined directory structure that allows us to figure out which services are available. If you set up your own repository (local or HTTP), you can easily control access to it. At this point, we don't have a management process to automate this, since developing service tasks like this is probably a job for developers, and they usually don't have any problems to upload completed service tasks to a directory somewhere. But again, feel free to provide feedback.<br>
<br>
Kris<br>
<br>
----- Oorspronkelijk bericht -----<br>
Van: "Giovanni Marigi" <<a href="mailto:gmarigi@redhat.com">gmarigi@redhat.com</a>><br>
Aan: <a href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
Verzonden: Dinsdag 13 maart 2012 17:08:11<br>
Onderwerp: [jbpm-dev] [JBPM 5.x] service task repository<br>
<br>
Hi,<br>
I would like to know the status of service task repository;<br>
I really appreciate the idea behind it and delivering some POC, customers were really enthusiastic about this feature (especially its integration with jbpm designer and BRMS) but it seems that the actual repo doesn't have some new effort.<br>
Will we provide API to push service tasks to the repository? I think it should be useful to provide some mechanism to approve a new service task before to make it public.<br>
<br>
Thanks,<br>
Giovanni<br>
<br>
--<br>
Giovanni Marigi<br>
Red Hat - JBoss Consultant -<br>
email: <a href="mailto:gmarigi@redhat.com">gmarigi@redhat.com</a><br>
Mobile: <a href="tel:%2B39%203423175986" value="+393423175986">+39 3423175986</a><br>
Office: <a href="tel:%2B39%200687502315" value="+390687502315">+39 0687502315</a><br>
<br>
Red Hat Italy<br>
Via Andrea Doria 41m<br>
00192 Roma - Italy<br>
<a href="http://www.redhat.com" target="_blank">www.redhat.com</a><br>
<br>
Prima di stampare, pensa all'ambiente ** Think about the environment before printing<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbpm-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
<br>
--<br>
Giovanni Marigi<br>
Red Hat - JBoss Consultant -<br>
email: <a href="mailto:gmarigi@redhat.com">gmarigi@redhat.com</a><br>
Mobile: <a href="tel:%2B39%203423175986" value="+393423175986">+39 3423175986</a><br>
Office: <a href="tel:%2B39%200687502315" value="+390687502315">+39 0687502315</a><br>
<br>
Red Hat Italy<br>
Via Andrea Doria 41m<br>
00192 Roma - Italy<br>
<a href="http://www.redhat.com" target="_blank">www.redhat.com</a><br>
<br>
Prima di stampare, pensa all'ambiente ** Think about the environment before printing<br>
_______________________________________________<br>
jbpm-dev mailing list<br>
<a href="mailto:jbpm-dev@lists.jboss.org">jbpm-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/jbpm-dev" target="_blank">https://lists.jboss.org/mailman/listinfo/jbpm-dev</a><br>
</div></div></blockquote></div><br><br clear="all"><div><br></div>-- <br> - MyJourney @ <a href="http://salaboy.wordpress.com" target="_blank">http://salaboy.wordpress.com</a><div> - Co-Founder @ <a href="http://www.jugargentina.org" target="_blank">http://www.jugargentina.org</a><br>
- Co-Founder @ <a href="http://www.jbug.com.ar" target="_blank">http://www.jbug.com.ar</a><br> <br> - Salatino "Salaboy" Mauricio -</div><br>
</div>