You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@taverna.apache.org by Dmitry <re...@list.ru> on 2015/03/20 15:28:02 UTC
taverna build.
Hello,
Could anybody give me a hint how incubation is going?
As far as I understand no workable build is possible from the incubator
right now. (?)
I refactored "incubator-taverna-common-activities" to
"org.apache.taverna.*" package and would like to proceed further.
For instance, "incubator-taverna-workbench" has many modules that may be
refactored.
In a usual project I would be cautious to do it in the main branch, but
since we are incubating how safe is this?
Kind regards,
Dmitry
Re: taverna build.
Posted by alaninmcr <al...@googlemail.com>.
On 20/03/2015 14:28, Dmitry wrote:
> Hello,
>
> Could anybody give me a hint how incubation is going?
> As far as I understand no workable build is possible from the incubator
> right now. (?)
Taverna Language is OK.
> I refactored "incubator-taverna-common-activities" to
> "org.apache.taverna.*" package and would like to proceed further.
>
> For instance, "incubator-taverna-workbench" has many modules that may be
> refactored.
> In a usual project I would be cautious to do it in the main branch, but
> since we are incubating how safe is this?
My reaction would be to just do it in the master branch. That is what I
did for the Taverna Language repository.
> Kind regards,
>
> Dmitry
Alan
Re: taverna build.
Posted by Dmitry <re...@list.ru>.
OK. Thank you.
I am also overwhelmed with number of submodules :-)
Just trying to go down -> up to do not break too many things.
Cheers,
Dmitry
On 3/20/2015 3:52 PM, Stian Soiland-Reyes wrote:
> Build status:
>
> https://builds.apache.org/user/stain/my-views/view/taverna/
>
> All of those that have a successful build would also be in the
> snapshot repository.
> http://taverna.incubator.apache.org/download/code/#snapshot-builds
>
>
> You might be interested in this fresh build failure:
>
> https://builds.apache.org/user/stain/my-views/view/taverna/job/incubator-taverna-common-activities/20/
>
>
> Everything down to and including "incubator-taverna-server" on
> http://taverna.incubator.apache.org/download/code/ have been updated
> to the new groupIds. All of those above taverna-server should also
> compile and pass tests. Feel free to update the POMs of the
> remaining! See incubator-taverna-engine etc. for style.
>
>
>
> I've started on fixing incubator-taverna-workbench - but it takes a
> while as it has too many submodules - many of these should ideally be
> merged to form a proper taverna-workbench-api - but that will have to
> wait. Basically all the <artifactId>s should now be taverna-SOMETHING
> and the <groupId> and <version> of all the dependencies to be updated
> to the style of org.apache.taverna.engine and ${taverna.engine} (or
> ${project.parent.groupId} and ${project.parent.version} if it's a
> sibling).
>
>
>
> Feel free to fix the Java packages to org.apache.taverna.* anywhere!
> Master branch is good - we don't need to keep the old packages.
> Obviously it's good if it actually compiles first - so you know if
> you've broken anything afterward.. (e.g. the downstream builds would
> probably break if they are not also updated)
>
>
> On 20 March 2015 at 14:28, Dmitry <re...@list.ru> wrote:
>> Hello,
>>
>> Could anybody give me a hint how incubation is going?
>> As far as I understand no workable build is possible from the incubator
>> right now. (?)
>>
>> I refactored "incubator-taverna-common-activities" to "org.apache.taverna.*"
>> package and would like to proceed further.
>>
>> For instance, "incubator-taverna-workbench" has many modules that may be
>> refactored.
>> In a usual project I would be cautious to do it in the main branch, but
>> since we are incubating how safe is this?
>>
>> Kind regards,
>>
>> Dmitry
>
>
Re: taverna build.
Posted by Stian Soiland-Reyes <st...@apache.org>.
Build status:
https://builds.apache.org/user/stain/my-views/view/taverna/
All of those that have a successful build would also be in the
snapshot repository.
http://taverna.incubator.apache.org/download/code/#snapshot-builds
You might be interested in this fresh build failure:
https://builds.apache.org/user/stain/my-views/view/taverna/job/incubator-taverna-common-activities/20/
Everything down to and including "incubator-taverna-server" on
http://taverna.incubator.apache.org/download/code/ have been updated
to the new groupIds. All of those above taverna-server should also
compile and pass tests. Feel free to update the POMs of the
remaining! See incubator-taverna-engine etc. for style.
I've started on fixing incubator-taverna-workbench - but it takes a
while as it has too many submodules - many of these should ideally be
merged to form a proper taverna-workbench-api - but that will have to
wait. Basically all the <artifactId>s should now be taverna-SOMETHING
and the <groupId> and <version> of all the dependencies to be updated
to the style of org.apache.taverna.engine and ${taverna.engine} (or
${project.parent.groupId} and ${project.parent.version} if it's a
sibling).
Feel free to fix the Java packages to org.apache.taverna.* anywhere!
Master branch is good - we don't need to keep the old packages.
Obviously it's good if it actually compiles first - so you know if
you've broken anything afterward.. (e.g. the downstream builds would
probably break if they are not also updated)
On 20 March 2015 at 14:28, Dmitry <re...@list.ru> wrote:
> Hello,
>
> Could anybody give me a hint how incubation is going?
> As far as I understand no workable build is possible from the incubator
> right now. (?)
>
> I refactored "incubator-taverna-common-activities" to "org.apache.taverna.*"
> package and would like to proceed further.
>
> For instance, "incubator-taverna-workbench" has many modules that may be
> refactored.
> In a usual project I would be cautious to do it in the main branch, but
> since we are incubating how safe is this?
>
> Kind regards,
>
> Dmitry
--
Stian Soiland-Reyes
Apache Taverna (incubating), Apache Commons RDF (incubating)
http://orcid.org/0000-0001-9842-9718