[jira] [Created] (TAVERNA-870) Move Taverna website away from SVN and cms.apache.org?
Stian Soiland-Reyes created TAVERNA-870: --- Summary: Move Taverna website away from SVN and cms.apache.org? Key: TAVERNA-870 URL: https://issues.apache.org/jira/browse/TAVERNA-870 Project: Apache Taverna Issue Type: Bug Components: Website Reporter: Stian Soiland-Reyes Assignee: Stian Soiland-Reyes While having the Github mirroring at https://github.com/apache/incubator-taverna-site is great for contributors (thanks Gale and Dennis!) - merging those pull requests against the SVN is quite a bit of a pain - I've actually had to do it by manual copy and paste. The system at https://cms.apache.org/taverna/ is not quite fit for purpose as it is very close to SVN, and frequently has issues such as not being updated. The build system is tricky to figure out. While we have been able to tweak the templates etc - I am now actually not understanding it myself anymore when trying to modify the menu bars. The SVN-based web publishing and cms.apache.org will at some point be deprecated by ASF INFRA (or so is the rumour) - and git-based websites are already available: https://blogs.apache.org/infra/entry/git_based_websites_available The new git-based system is basically Write HTML files to git, they are immediately live - so no more staging area or web-based editing. This git-based system seem however seem to require that you do any kind of building yourself, e.g. to convert Markdown to HTML and to apply templates with common menus. Would it be worth re-examining the options here? E.g. Jekyll or Maven Site or something else? As an example - http://commonsrdf.incubator.apache.org/ is built with Maven Site and published through SVN from https://github.com/apache/incubator-commonsrdf/tree/master/src/site with stuff inherited from Apache Commons poms and styles. There's quite a reduction in flexibility - but deploying that website is simply mvn clean site scm-publish:publish-scm and provide the SVN password. I will imagine this would work the same way with a git backend, although that has not been tested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Draft: Taverna Language download page
How about like this with split sections? http://taverna.staging.apache.org/download/language/ On 10 August 2015 at 15:46, Stian Soiland-Reyes st...@apache.org wrote: Here means the 0.15.0-incubating headline right below.. so I'll change it to Below? On 10 August 2015 at 15:01, Gale Naylor ga...@noventussolutions.com wrote: Hi Stain, Is there supposed to be a link in the sentence (under Source Code) where it says, Here you can find all Taverna Language source releases.? Thanks, Gale -Original Message- From: Stian Soiland-Reyes [mailto:st...@apache.org] Sent: Monday, August 10, 2015 6:44 AM To: dev@taverna.incubator.apache.org Subject: Draft: Taverna Language download page I have drafted a download page for Taverna Language here: http://taverna.staging.apache.org/download/language/ Note that the download and Maven links don't work yet, as Ian has push the right buttons and then we have to wait 24h for the mirrors. I included the taverna-parent download here, as I think it would be a bit silly on a page by itself. You wouldn't normally need it as it would be downloaded from Central if you just tried to build Language. Comments? Feel free to edit! Should we rename the file downloads to apache-taverna-* ? The checksums should stay the same, but Ian might have to regenerate the .asc signature. Mentors, is that permitted given that we voted on a sha1 sum? Obviously for the future we should need to modify the Maven build so the release files always get the apache- prefix directly: -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
[jira] [Commented] (TAVERNA-870) Move Taverna website away from SVN and cms.apache.org?
[ https://issues.apache.org/jira/browse/TAVERNA-870?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680285#comment-14680285 ] Stian Soiland-Reyes commented on TAVERNA-870: - Exampes of projects using Jekyll and publishing directly to: https://github.com/apache/orc/blob/master/site/BUILD.md https://github.com/apache/drill/tree/gh-pages-master One downside I found with Jekyll is that you need to install ruby, rvm etc.. and then there's potential versioning issues. I have not got much experience beyond Github Pages. Using Jekyll can give compatibility with github pages (e.g. using gh-pages branch), e.g.with previews like http://apache.github.io/drill/ is good - but also a bit confusing perhaps? Move Taverna website away from SVN and cms.apache.org? -- Key: TAVERNA-870 URL: https://issues.apache.org/jira/browse/TAVERNA-870 Project: Apache Taverna Issue Type: Bug Components: Website Reporter: Stian Soiland-Reyes Assignee: Stian Soiland-Reyes While having the Github mirroring at https://github.com/apache/incubator-taverna-site is great for contributors (thanks Gale and Dennis!) - merging those pull requests against the SVN is quite a bit of a pain - I've actually had to do it by manual copy and paste. The system at https://cms.apache.org/taverna/ is not quite fit for purpose as it is very close to SVN, and frequently has issues such as not being updated. The build system is tricky to figure out. While we have been able to tweak the templates etc - I am now actually not understanding it myself anymore when trying to modify the menu bars. The SVN-based web publishing and cms.apache.org will at some point be deprecated by ASF INFRA (or so is the rumour) - and git-based websites are already available: https://blogs.apache.org/infra/entry/git_based_websites_available The new git-based system is basically Write HTML files to git, they are immediately live - so no more staging area or web-based editing. This git-based system seem however seem to require that you do any kind of building yourself, e.g. to convert Markdown to HTML and to apply templates with common menus. Would it be worth re-examining the options here? E.g. Jekyll or Maven Site or something else? As an example - http://commonsrdf.incubator.apache.org/ is built with Maven Site and published through SVN from https://github.com/apache/incubator-commonsrdf/tree/master/src/site with stuff inherited from Apache Commons poms and styles. There's quite a reduction in flexibility - but deploying that website is simply mvn clean site scm-publish:publish-scm and provide the SVN password. I will imagine this would work the same way with a git backend, although that has not been tested. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Re: Draft: Taverna Language download page
@Stian One other minor thing: In the second paragraph, I think there should be a semi-color between -section.jar and however, and a comma after however. So, like this: ...artifacts include -javadoc.jar and -section.jar; however, you might prefer ... Cheers! Gale On Mon, Aug 10, 2015 at 7:57 AM, Stian Soiland-Reyes st...@apache.org wrote: How about like this with split sections? http://taverna.staging.apache.org/download/language/ On 10 August 2015 at 15:46, Stian Soiland-Reyes st...@apache.org wrote: Here means the 0.15.0-incubating headline right below.. so I'll change it to Below? On 10 August 2015 at 15:01, Gale Naylor ga...@noventussolutions.com wrote: Hi Stain, Is there supposed to be a link in the sentence (under Source Code) where it says, Here you can find all Taverna Language source releases.? Thanks, Gale -Original Message- From: Stian Soiland-Reyes [mailto:st...@apache.org] Sent: Monday, August 10, 2015 6:44 AM To: dev@taverna.incubator.apache.org Subject: Draft: Taverna Language download page I have drafted a download page for Taverna Language here: http://taverna.staging.apache.org/download/language/ Note that the download and Maven links don't work yet, as Ian has push the right buttons and then we have to wait 24h for the mirrors. I included the taverna-parent download here, as I think it would be a bit silly on a page by itself. You wouldn't normally need it as it would be downloaded from Central if you just tried to build Language. Comments? Feel free to edit! Should we rename the file downloads to apache-taverna-* ? The checksums should stay the same, but Ian might have to regenerate the .asc signature. Mentors, is that permitted given that we voted on a sha1 sum? Obviously for the future we should need to modify the Maven build so the release files always get the apache- prefix directly: -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
Re: Draft: Taverna Language download page
Yes! I think that looks better. On Mon, Aug 10, 2015 at 7:57 AM, Stian Soiland-Reyes st...@apache.org wrote: How about like this with split sections? http://taverna.staging.apache.org/download/language/ On 10 August 2015 at 15:46, Stian Soiland-Reyes st...@apache.org wrote: Here means the 0.15.0-incubating headline right below.. so I'll change it to Below? On 10 August 2015 at 15:01, Gale Naylor ga...@noventussolutions.com wrote: Hi Stain, Is there supposed to be a link in the sentence (under Source Code) where it says, Here you can find all Taverna Language source releases.? Thanks, Gale -Original Message- From: Stian Soiland-Reyes [mailto:st...@apache.org] Sent: Monday, August 10, 2015 6:44 AM To: dev@taverna.incubator.apache.org Subject: Draft: Taverna Language download page I have drafted a download page for Taverna Language here: http://taverna.staging.apache.org/download/language/ Note that the download and Maven links don't work yet, as Ian has push the right buttons and then we have to wait 24h for the mirrors. I included the taverna-parent download here, as I think it would be a bit silly on a page by itself. You wouldn't normally need it as it would be downloaded from Central if you just tried to build Language. Comments? Feel free to edit! Should we rename the file downloads to apache-taverna-* ? The checksums should stay the same, but Ian might have to regenerate the .asc signature. Mentors, is that permitted given that we voted on a sha1 sum? Obviously for the future we should need to modify the Maven build so the release files always get the apache- prefix directly: -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
Re: [DISCUSS] Release Apache Taverna Parent 1-incubating-RC4 Apache Taverna Language 0.15.0-incubating RC4
-BEGIN PGP SIGNED MESSAGE- Hash: SHA256 Hello, I've moved the release candidate to https://dist.apache.org/repos/dist/release/incubator/taverna/source/. I'll give it the 24 hours as stated in the our docs for the mirrors to pick it up before updating the download page and clicking 'release' on the staging repo. Cheers, Ian On 07/08/2015 17:25, Stian Soiland-Reyes wrote: I'll have a look at TAVERNA-864 over the weekend. I think we can do the same move here as for the distro, move the NOTICE text to amendmends to their retrospective META-INF/LICENSE - it's not as obvious as NOTICE when inside a JAR file (say you only look at the top of the LICENSE file), but it shouldn't be wrong legally speaking. We should try to release the taverna-language module some point again after GSOC to include the final version of Menaka's command line tool. Independent of that, if this goes out, then we should be free to start releasing taverna-osgi and taverna-engine, and then work on the command line release. I think the other repository that has similar schema-bundling issues would be taverna-server. The command line release would have more NOTICE/LICENSE-like work needed as it would include a binary distribution with all the dependency JARs. On 6 August 2015 at 16:08, Andy Seaborne a...@apache.org wrote: On 06/08/15 14:58, Pierce, Marlon wrote: You mean https://issues.apache.org/jira/browse/TAVERNA-864? Yes - and the VOTE comment. I hope that having recognized it with a JIRA will help smooth the way through general@ though I'm not clear if this module (language) would be released again before graduation. There's a lot of repos. Team - How many releases of other modules might here be? Andy On 8/6/15, 9:39 AM, Andy Seaborne a...@apache.org wrote: Marlon, What's your take on the inner NOTICE files? Andy On 06/08/15 14:10, Pierce, Marlon wrote: Yes, will do so. On 8/6/15, 5:30 AM, Ian Dunlop ian.dun...@manchester.ac.uk wrote: Hello, I've sent the [VOTE] email to general http://mail-archives.apache.org/mod_mbox/incubator-general/201508.mbox /% 3C55C1EF75.9020403%40manchester.ac.uk%3E. I think Marlon will have to vote again (if you want to of course) since the vote on the taverna list may not have been marked as binding. Cheers, Ian On 05/08/2015 13:52, Andy Seaborne wrote: On 01/08/15 12:57, Andy Seaborne wrote: 1/ The NOTICE says: Copyright 2014-2015 The Apache Software Foundation The Apache ICLA does not transfer copyright. Copyright remains with the original contributor. The ICLA is a license-to-use. TAVERNA-868 is a proposed fix for this. My confusion was that the product, the output of a release, is (c) Apache but the code inside it is not. Sampling several apache projects - at least ones that actually have a NOTICE in the top of the repo - the following form looks better. Apache Taverna Maven Parent Copyright 2014-2015 The Apache Software Foundation Portions of this software were originally based on the following: - Copyright 2010-2014 University of Manchester, UK These have been licensed to the Apache Software Foundation under a software grant. This product includes software developed at The Apache Software Foundation (http://www.apache.org/). It might be arguable about whether the originally paragraph are needed but the U of Manchester is so significant, and it ties it to pre-Apache Taverna, that I think it is worth it. other projects have it (Jena, Marmotta) Andy -BEGIN PGP SIGNATURE- Version: GnuPG v2 iQEcBAEBCAAGBQJVyL/rAAoJEPK45GBX+Cy58acH/1CV3CrjJPe07q9iUAil+PiG oTAOLi+cFLpSubOrofPQGTQcJlennaIi7AoHlGJXWM2jQThqvi018Vvg9WvA074l mXNoj0ajo1ZV2eF9RuC5pGjiUVjvdsH1Bk+92FakkyZ6jn5StW8VcXMT/fyd4Nls eYNA/nv/5bASWo0QvSEd9SXx3sb1mOh4PNImnKU4yqccG82j9QmwxMu1XffhJZUM HVRo3zpjwoUEL/GYf8RpqLp3hJqyEycCLKYJUdJdYZi8kR0nr7AXtiRNcUwH8bYg eCOswCzhjazjY4LglhfTPonjvQ5NPqvbcctUI1U3inmfmMxZsSYuNavvJEBfBi0= =Gli1 -END PGP SIGNATURE-
[GitHub] incubator-taverna-language pull request: Test case modified
Github user menaka121 commented on a diff in the pull request:
https://github.com/apache/incubator-taverna-language/pull/23#discussion_r36667959
--- Diff:
taverna-robundle/src/test/java/org/apache/taverna/robundle/validator/ValidatorTest.java
---
@@ -21,23 +21,45 @@
import static org.junit.Assert.*;
+import java.io.IOException;
+import java.nio.file.CopyOption;
+import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
+import java.nio.file.StandardCopyOption;
+import org.junit.Assert;
+import org.junit.Before;
import org.junit.Test;
public class ValidatorTest {
- private Path path =
Paths.get(src/test/resources/workflowrun.bundle.zip);
+Path path;
+ @Before
+ public void copyExample() {
+ try {
+ path =
Files.createTempFile(test, .bundle.zip);
+ } catch (IOException e1) {
+ // TODO Auto-generated catch
block
+ e1.printStackTrace();
--- End diff --
Hello Stian,
I'll check it out.!!! :-)
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
Re: Draft: Taverna Language download page
Here means the 0.15.0-incubating headline right below.. so I'll change it to Below? On 10 August 2015 at 15:01, Gale Naylor ga...@noventussolutions.com wrote: Hi Stain, Is there supposed to be a link in the sentence (under Source Code) where it says, Here you can find all Taverna Language source releases.? Thanks, Gale -Original Message- From: Stian Soiland-Reyes [mailto:st...@apache.org] Sent: Monday, August 10, 2015 6:44 AM To: dev@taverna.incubator.apache.org Subject: Draft: Taverna Language download page I have drafted a download page for Taverna Language here: http://taverna.staging.apache.org/download/language/ Note that the download and Maven links don't work yet, as Ian has push the right buttons and then we have to wait 24h for the mirrors. I included the taverna-parent download here, as I think it would be a bit silly on a page by itself. You wouldn't normally need it as it would be downloaded from Central if you just tried to build Language. Comments? Feel free to edit! Should we rename the file downloads to apache-taverna-* ? The checksums should stay the same, but Ian might have to regenerate the .asc signature. Mentors, is that permitted given that we voted on a sha1 sum? Obviously for the future we should need to modify the Maven build so the release files always get the apache- prefix directly: -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718 -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
Re: Taverna poster
I just added both.. I think the SVG file is an SVG+Inkscape and not so usable outside Inkscape - so I renamed it as such. On 7 August 2015 at 17:24, Alan Williams alanin...@googlemail.com wrote: On 07-Aug-15 00:29, Denis Karyakin wrote: 2015-08-05 17:53 GMT+03:00 alaninmcr alanin...@googlemail.com: On 04/08/2015 23:28, Denis Karyakin wrote: Thank you very much for supporting and advices. People are interested in poster, they asked many questions about Taverna and some of them promised to try the Taverna Workbench. I create pull request with poster in svg and pdf formats https://github.com/apache/incubator-taverna-site/pull/3 Can you check the svg? On my machine it has no text in the space below INTRODUCTION and then almost all the rest of the text is invisible. I can see that it is there in the svg source though. I checked the svg. When I opened it in image viewer, I saw black fields instead of texts. Similar in nautilus (file manager) preview. But when I opened the svg in Inkscape, text is properly. I will look closely to check this, maybe need to change text Alternatively, just commit the PDF (unless someone objects). The PDF looks good to me. Alan Alan -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
Re: [VOTE] Release Apache Taverna Parent 1-incubating-RC4 Apache Taverna Language 0.15.0-incubating RC4
On 01/08/15 12:57, Andy Seaborne wrote: Thank you to Ian for putting this together. Downloaded source. Signatures and build OK. But there some point issues which mount up to me voting -0 With TAVERNA-864 done, I revise my vote to +1. Andy Comments: 1/ The NOTICE says: Copyright 2014-2015 The Apache Software Foundation The Apache ICLA does not transfer copyright. Copyright remains with the original contributor. The ICLA is a license-to-use. 2/ commits mis-aligned (good catch by Stian) It would be good if the Release Manager sent an email saying the commits should have been ... and giving 24 hours for objections to continue the vote as is. That said, items here might make it worth RC5 to tidy up. language: 3/ LN in every jar I found ./taverna-scufl2-schemas/src/main/resources/META-INF/NOTICE ./taverna-scufl2-wfdesc/src/main/resources/META-INF/NOTICE ./taverna-scufl2-ucfpackage/src/main/resources/META-INF/NOTICE ./taverna-robundle/src/main/resources/META-INF/NOTICE and there is material in these NOTICE files deeper in which (1) should be in LICENSE and (2) aren't rolled up into the top files. In fact, the material is rolled up into the top level LICENSE so it's not -1 territory for me. Andy
Re: [VOTE] Release Apache Taverna Parent 1-incubating-RC4 Apache Taverna Language 0.15.0-incubating RC4
Thank you - would you and Marlon be OK to repeat your binding +1 on the incubator thread? (which went silent! :-( ) http://mail-archives.apache.org/mod_mbox/incubator-general/201508.mbox/%3C55C1EF75.9020403%40manchester.ac.uk%3E On 10 August 2015 at 10:14, Andy Seaborne a...@apache.org wrote: On 01/08/15 12:57, Andy Seaborne wrote: Thank you to Ian for putting this together. Downloaded source. Signatures and build OK. But there some point issues which mount up to me voting -0 With TAVERNA-864 done, I revise my vote to +1. Andy Comments: 1/ The NOTICE says: Copyright 2014-2015 The Apache Software Foundation The Apache ICLA does not transfer copyright. Copyright remains with the original contributor. The ICLA is a license-to-use. 2/ commits mis-aligned (good catch by Stian) It would be good if the Release Manager sent an email saying the commits should have been ... and giving 24 hours for objections to continue the vote as is. That said, items here might make it worth RC5 to tidy up. language: 3/ LN in every jar I found ./taverna-scufl2-schemas/src/main/resources/META-INF/NOTICE ./taverna-scufl2-wfdesc/src/main/resources/META-INF/NOTICE ./taverna-scufl2-ucfpackage/src/main/resources/META-INF/NOTICE ./taverna-robundle/src/main/resources/META-INF/NOTICE and there is material in these NOTICE files deeper in which (1) should be in LICENSE and (2) aren't rolled up into the top files. In fact, the material is rolled up into the top level LICENSE so it's not -1 territory for me. Andy -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
[jira] [Created] (TAVERNA-869) Require Java 8?
Stian Soiland-Reyes created TAVERNA-869: --- Summary: Require Java 8? Key: TAVERNA-869 URL: https://issues.apache.org/jira/browse/TAVERNA-869 Project: Apache Taverna Issue Type: Bug Components: Taverna Maven Parent Affects Versions: parent 1 Reporter: Stian Soiland-Reyes Assignee: Stian Soiland-Reyes Relating to TAVERNA-867 - would it now make sense to overall change Java requirement to Java 8? Our current compile setting says Java 7 for source compiling and target binary (JAR) compatibility: https://github.com/apache/incubator-taverna-maven-parent/blob/master/pom.xml#L93 I'm not suggesting this because of the doclint option - that could be fixed with a Maven profile if we still wanted to support compiling on Java 7 - but because Java 7 has already reached End of Life, and Java 8 has many nice new features that (with time) could be useful. Java 8 is now working fine on all 3 major OS-es, right? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAVERNA-864) Correct Java META-INF/NOTICE files
[
https://issues.apache.org/jira/browse/TAVERNA-864?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stian Soiland-Reyes updated TAVERNA-864:
Fix Version/s: language 0.16.0
Correct Java META-INF/NOTICE files
---
Key: TAVERNA-864
URL: https://issues.apache.org/jira/browse/TAVERNA-864
Project: Apache Taverna
Issue Type: Bug
Components: Taverna Language
Affects Versions: language 0.15.0
Reporter: Andy Seaborne
Assignee: Stian Soiland-Reyes
Fix For: language 0.16.0
These NOTICE files contain information that is in the top level LICENSE:
{noformat}
./taverna-scufl2-schemas/src/main/resources/META-INF/NOTICE
./taverna-scufl2-wfdesc/src/main/resources/META-INF/NOTICE
./taverna-scufl2-ucfpackage/src/main/resources/META-INF/NOTICE
./taverna-robundle/src/main/resources/META-INF/NOTICE
{noformat}
The information should be in LICENSE for embedding in jars.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (TAVERNA-869) Require Java 8?
[ https://issues.apache.org/jira/browse/TAVERNA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated TAVERNA-869: Fix Version/s: parent 2 Require Java 8? --- Key: TAVERNA-869 URL: https://issues.apache.org/jira/browse/TAVERNA-869 Project: Apache Taverna Issue Type: Bug Components: Taverna Maven Parent Affects Versions: parent 1 Reporter: Stian Soiland-Reyes Assignee: Stian Soiland-Reyes Labels: java Fix For: parent 2 Relating to TAVERNA-867 - would it now make sense to overall change Java requirement to Java 8? Our current compile setting says Java 7 for source compiling and target binary (JAR) compatibility: https://github.com/apache/incubator-taverna-maven-parent/blob/master/pom.xml#L93 I'm not suggesting this because of the doclint option - that could be fixed with a Maven profile if we still wanted to support compiling on Java 7 - but because Java 7 has already reached End of Life, and Java 8 has many nice new features that (with time) could be useful. Java 8 is now working fine on all 3 major OS-es, right? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAVERNA-869) Require Java 8?
[ https://issues.apache.org/jira/browse/TAVERNA-869?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14679919#comment-14679919 ] Ian Dunlop commented on TAVERNA-869: I think it's ok to go with Java 8 as long as it is clear in the docs/website etc. Although Java 7 is end-of-life there doesn't seem to be a 'do not use' statement from Oracle, see https://www.java.com/en/download/faq/java_7.xml, since they still support for paying customers. I guess its similar to the IE6 issues where users may still have it on their PCs so you have to make the call as to whether its worth it for the minority who will have that platform. I say go for Java 8. I guess taverna will also be targeting http://openjdk.java.net/projects/jdk8/, what is the package support like in Linux? It will be worth stating what OS/Java combinations have been tested in the release notes. Require Java 8? --- Key: TAVERNA-869 URL: https://issues.apache.org/jira/browse/TAVERNA-869 Project: Apache Taverna Issue Type: Bug Components: Taverna Maven Parent Affects Versions: parent 1 Reporter: Stian Soiland-Reyes Assignee: Stian Soiland-Reyes Labels: java Fix For: parent 2 Relating to TAVERNA-867 - would it now make sense to overall change Java requirement to Java 8? Our current compile setting says Java 7 for source compiling and target binary (JAR) compatibility: https://github.com/apache/incubator-taverna-maven-parent/blob/master/pom.xml#L93 I'm not suggesting this because of the doclint option - that could be fixed with a Maven profile if we still wanted to support compiling on Java 7 - but because Java 7 has already reached End of Life, and Java 8 has many nice new features that (with time) could be useful. Java 8 is now working fine on all 3 major OS-es, right? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAVERNA-828) Release taverna-language to dist.apache and Maven repo
[ https://issues.apache.org/jira/browse/TAVERNA-828?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated TAVERNA-828: Assignee: Ian Dunlop (was: Stian Soiland-Reyes) Release taverna-language to dist.apache and Maven repo -- Key: TAVERNA-828 URL: https://issues.apache.org/jira/browse/TAVERNA-828 Project: Apache Taverna Issue Type: Sub-task Components: Taverna Language, Taverna Maven Parent Reporter: Stian Soiland-Reyes Assignee: Ian Dunlop Labels: release Fix For: parent 1, language 0.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAVERNA-828) Release taverna-language to dist.apache and Maven repo
[ https://issues.apache.org/jira/browse/TAVERNA-828?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680112#comment-14680112 ] Stian Soiland-Reyes commented on TAVERNA-828: - Should we rename the files (not the folders) to apache-taverna-* ? Would need a new GPG signature, but sha1/md5 would stay consistent with vote. Release taverna-language to dist.apache and Maven repo -- Key: TAVERNA-828 URL: https://issues.apache.org/jira/browse/TAVERNA-828 Project: Apache Taverna Issue Type: Sub-task Components: Taverna Language, Taverna Maven Parent Reporter: Stian Soiland-Reyes Assignee: Ian Dunlop Labels: release Fix For: parent 1, language 0.15.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAVERNA-833) Update git tags
[ https://issues.apache.org/jira/browse/TAVERNA-833?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated TAVERNA-833: Assignee: Ian Dunlop (was: Stian Soiland-Reyes) Update git tags --- Key: TAVERNA-833 URL: https://issues.apache.org/jira/browse/TAVERNA-833 Project: Apache Taverna Issue Type: Sub-task Components: Taverna Language, Taverna Maven Parent Reporter: Stian Soiland-Reyes Assignee: Ian Dunlop Fix For: parent 1, language 0.15.0 git tag like 0.15.0-incubating-RC2 to be retagged as 0.15.0-incubating -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAVERNA-832) Document release process
[ https://issues.apache.org/jira/browse/TAVERNA-832?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated TAVERNA-832: Assignee: Ian Dunlop (was: Stian Soiland-Reyes) Document release process Key: TAVERNA-832 URL: https://issues.apache.org/jira/browse/TAVERNA-832 Project: Apache Taverna Issue Type: Sub-task Components: Website Reporter: Stian Soiland-Reyes Assignee: Ian Dunlop Fix For: parent 1, language 0.15.0 To be at http://taverna.incubator.apache.org/community/releasing See also release process for other Apache projects: https://cwiki.apache.org/confluence/display/JENA/Release+Process -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (TAVERNA-847) Fix workflow mark as favorite
[ https://issues.apache.org/jira/browse/TAVERNA-847?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated TAVERNA-847: Fix Version/s: (was: parent 1) Fix workflow mark as favorite -- Key: TAVERNA-847 URL: https://issues.apache.org/jira/browse/TAVERNA-847 Project: Apache Taverna Issue Type: Task Components: GSOC: Taverna Mobile Affects Versions: parent 1 Environment: Android studio 1.1.0 Reporter: larry akah Assignee: larry akah Labels: features Original Estimate: 72h Remaining Estimate: 72h Fix the marking a workflow as favorite such that it gets added to the local database properly and also how the button transitions to indicate the state. it requires adding an entity seprately to the database when a given workflow item is selected from the list. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (TAVERNA-834) Update Jira following Taverna Language release
[ https://issues.apache.org/jira/browse/TAVERNA-834?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=14680123#comment-14680123 ] Stian Soiland-Reyes commented on TAVERNA-834: - Done - except for the Release 0.15.0 bugs. Update Jira following Taverna Language release -- Key: TAVERNA-834 URL: https://issues.apache.org/jira/browse/TAVERNA-834 Project: Apache Taverna Issue Type: Sub-task Components: Website Reporter: Stian Soiland-Reyes Assignee: Ian Dunlop Fix For: parent 1, language 0.15.0 Mark versions as released in Jira, create new unreleased versions. Update Resolved - Closed with Fix For 0.15.0. Change Fix For versions for still open issues. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[GitHub] incubator-taverna-language pull request: Test case modified
Github user stain commented on a diff in the pull request:
https://github.com/apache/incubator-taverna-language/pull/23#discussion_r36632957
--- Diff:
taverna-robundle/src/test/java/org/apache/taverna/robundle/validator/ValidatorTest.java
---
@@ -21,23 +21,45 @@
import static org.junit.Assert.*;
+import java.io.IOException;
+import java.nio.file.CopyOption;
+import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
+import java.nio.file.StandardCopyOption;
+import org.junit.Assert;
+import org.junit.Before;
import org.junit.Test;
public class ValidatorTest {
- private Path path =
Paths.get(src/test/resources/workflowrun.bundle.zip);
+Path path;
+ @Before
+ public void copyExample() {
+ try {
+ path =
Files.createTempFile(test, .bundle.zip);
+ } catch (IOException e1) {
+ // TODO Auto-generated catch
block
+ e1.printStackTrace();
--- End diff --
If this fails (e.g. out of disk space?), then a printStackTrace does not
help as much as simply letting the error make the whole test fail by cahnging
`copyExample` to have `throws IOEXception`
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
[jira] [Updated] (TAVERNA-812) Release Taverna Language 0.15.0-incubating
[ https://issues.apache.org/jira/browse/TAVERNA-812?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stian Soiland-Reyes updated TAVERNA-812: Assignee: Ian Dunlop (was: Stian Soiland-Reyes) Release Taverna Language 0.15.0-incubating -- Key: TAVERNA-812 URL: https://issues.apache.org/jira/browse/TAVERNA-812 Project: Apache Taverna Issue Type: Task Components: Taverna Language, Taverna Maven Parent Reporter: Stian Soiland-Reyes Assignee: Ian Dunlop Labels: release Fix For: parent 1, language 0.15.0 I think we are ready to release Taverna Maven Parent and Taverna Language. Any volunteers for having a go? As this is the first release, I've made a Jira Task to track what remains to be done. The tasks here form the basis for documenting the release procedure. (This message also serves as a test that Jira - dev@taverna works :) ) -- This message was sent by Atlassian JIRA (v6.3.4#6332)
Draft: Taverna Language download page
I have drafted a download page for Taverna Language here: http://taverna.staging.apache.org/download/language/ Note that the download and Maven links don't work yet, as Ian has push the right buttons and then we have to wait 24h for the mirrors. I included the taverna-parent download here, as I think it would be a bit silly on a page by itself. You wouldn't normally need it as it would be downloaded from Central if you just tried to build Language. Comments? Feel free to edit! Should we rename the file downloads to apache-taverna-* ? The checksums should stay the same, but Ian might have to regenerate the .asc signature. Mentors, is that permitted given that we voted on a sha1 sum? Obviously for the future we should need to modify the Maven build so the release files always get the apache- prefix directly: -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
Re: [GitHub] incubator-taverna-language pull request: Test case modified
Menaka, Thanks for updating the pull request. I think e.printStackTrace(); is of no use within a unit test - a unit test should fail right away if there is an error - not cause strange errors further down. Could you fix..? Sorry about being picky.. On 5 August 2015 at 18:52, menaka121 g...@git.apache.org wrote: GitHub user menaka121 opened a pull request: https://github.com/apache/incubator-taverna-language/pull/23 Test case modified You can merge this pull request into a Git repository by running: $ git pull https://github.com/menaka121/incubator-taverna-language rovalidator Alternatively you can review and apply these changes as the patch at: https://github.com/apache/incubator-taverna-language/pull/23.patch To close this pull request, make a commit to your master/trunk branch with (at least) the following in the commit message: This closes #23 commit 667c40d1429f021af21308d3ab0eddaf5b058c1d Author: Menaka Madushanka menaka12...@gmail.com Date: 2015-08-05T17:50:21Z Test case modified --- If your project is set up for it, you can reply to this email and have your reply appear on GitHub as well. If your project does not have this feature enabled and wishes so, or if the feature is enabled but not working, please contact infrastructure at infrastruct...@apache.org or file a JIRA ticket with INFRA. --- -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
[GitHub] incubator-taverna-language pull request: Test case modified
Github user stain commented on a diff in the pull request:
https://github.com/apache/incubator-taverna-language/pull/23#discussion_r36632858
--- Diff:
taverna-robundle/src/test/java/org/apache/taverna/robundle/validator/ValidatorTest.java
---
@@ -21,23 +21,45 @@
import static org.junit.Assert.*;
+import java.io.IOException;
+import java.nio.file.CopyOption;
+import java.nio.file.Files;
import java.nio.file.Path;
import java.nio.file.Paths;
+import java.nio.file.StandardCopyOption;
+import org.junit.Assert;
+import org.junit.Before;
import org.junit.Test;
public class ValidatorTest {
- private Path path =
Paths.get(src/test/resources/workflowrun.bundle.zip);
+Path path;
+ @Before
+ public void copyExample() {
+ try {
+ path =
Files.createTempFile(test, .bundle.zip);
+ } catch (IOException e1) {
+ // TODO Auto-generated catch
block
+ e1.printStackTrace();
+ }
+ try {
+
Files.copy(getClass().getResourceAsStream(/workflowrun.bundle.zip), path,
StandardCopyOption.REPLACE_EXISTING);
+ } catch (IOException e) {
+ // TODO Auto-generated catch
block
+ e.printStackTrace();
+ }
+ }
@Test
public void test() {
RoValidator validator = new RoValidator(path);
ValidationReport r = validator.check();
- System.out.println(r.getErrorList());
- System.out.println(r.getInfoWarnings());
- System.out.println(r.getWarnings());
+ assertTrue(r.getErrorList()!=null);
--- End diff --
This should check if the lists are empty so that the example passed without
any errors or warning - I guess the code would not ever return them as `null`?
if there is a genuine warning, then the test should check that.
---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---
Re: [VOTE] Release Apache Taverna Parent 1-incubating-RC4 Apache Taverna Language 0.15.0-incubating RC4
On 10/08/15 10:55, Stian Soiland-Reyes wrote: Thank you - would you and Marlon be OK to repeat your binding +1 on the incubator thread? (which went silent! :-( ) The text: has voted +5 to release is possibly confusing people. I'll bump the thread. Andy http://mail-archives.apache.org/mod_mbox/incubator-general/201508.mbox/%3C55C1EF75.9020403%40manchester.ac.uk%3E On 10 August 2015 at 10:14, Andy Seaborne a...@apache.org wrote: On 01/08/15 12:57, Andy Seaborne wrote: Thank you to Ian for putting this together. Downloaded source. Signatures and build OK. But there some point issues which mount up to me voting -0 With TAVERNA-864 done, I revise my vote to +1. Andy Comments: 1/ The NOTICE says: Copyright 2014-2015 The Apache Software Foundation The Apache ICLA does not transfer copyright. Copyright remains with the original contributor. The ICLA is a license-to-use. 2/ commits mis-aligned (good catch by Stian) It would be good if the Release Manager sent an email saying the commits should have been ... and giving 24 hours for objections to continue the vote as is. That said, items here might make it worth RC5 to tidy up. language: 3/ LN in every jar I found ./taverna-scufl2-schemas/src/main/resources/META-INF/NOTICE ./taverna-scufl2-wfdesc/src/main/resources/META-INF/NOTICE ./taverna-scufl2-ucfpackage/src/main/resources/META-INF/NOTICE ./taverna-robundle/src/main/resources/META-INF/NOTICE and there is material in these NOTICE files deeper in which (1) should be in LICENSE and (2) aren't rolled up into the top files. In fact, the material is rolled up into the top level LICENSE so it's not -1 territory for me. Andy
RE: Draft: Taverna Language download page
Hi Stain, Is there supposed to be a link in the sentence (under Source Code) where it says, Here you can find all Taverna Language source releases.? Thanks, Gale -Original Message- From: Stian Soiland-Reyes [mailto:st...@apache.org] Sent: Monday, August 10, 2015 6:44 AM To: dev@taverna.incubator.apache.org Subject: Draft: Taverna Language download page I have drafted a download page for Taverna Language here: http://taverna.staging.apache.org/download/language/ Note that the download and Maven links don't work yet, as Ian has push the right buttons and then we have to wait 24h for the mirrors. I included the taverna-parent download here, as I think it would be a bit silly on a page by itself. You wouldn't normally need it as it would be downloaded from Central if you just tried to build Language. Comments? Feel free to edit! Should we rename the file downloads to apache-taverna-* ? The checksums should stay the same, but Ian might have to regenerate the .asc signature. Mentors, is that permitted given that we voted on a sha1 sum? Obviously for the future we should need to modify the Maven build so the release files always get the apache- prefix directly: -- Stian Soiland-Reyes Apache Taverna (incubating), Apache Commons RDF (incubating) http://orcid.org/-0001-9842-9718
