[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1:
URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583198402
##
File path:
src/main/g8/src/test/scala/$package$/$name__camel$/Test$name__Camel$.scala
##
@@ -0,0 +1,38 @@
+$!
+// Licensed to the Apache Software Foundation (ASF) under one or more
+// contributor license agreements. See the NOTICE file distributed with
+// this work for additional information regarding copyright ownership.
+// The ASF licenses this file to You under the Apache License, Version 2.0
+// (the "License"); you may not use this file except in compliance with
+// the License. You may obtain a copy of the License at
+//
+// http://www.apache.org/licenses/LICENSE-2.0
+//
+// Unless required by applicable law or agreed to in writing, software
+// distributed under the License is distributed on an "AS IS" BASIS,
+// WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+// See the License for the specific language governing permissions and
+// limitations under the License.
+!$
+package $package$.$name;format="camel"$
+
+import org.junit.AfterClass
+import org.junit.Test
+
+import org.apache.daffodil.tdml.Runner
+
+object Test$name;format="Camel"$ {
+ lazy val runner =
Runner("/$package;format="packaged"$/$name;format="camel"$/",
"Test$name;format="Camel"$.tdml")
+
+ @AfterClass def shutDown {
+runner.reset
+ }
+}
+
+class Test$name;format="Camel"$ {
+
+ import Test$name;format="Camel"$._
Review comment:
Looks like the convention we use in Daffodil test scala files is to have
the blank line before the import, I think I might keep this one just to be
consistent with that.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1: URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583195152 ## File path: src/main/g8/src/test/resources/$package$/$name__camel$/infosets/test_01.$name__camel$.xml ## @@ -0,0 +1,21 @@ + Review comment: Good eye, will fix. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1: URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583193742 ## File path: src/main/g8/.gitattributes ## @@ -0,0 +1,18 @@ +$if(false)$ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at +# +# http://www.apache.org/licenses/LICENSE-2.0 +# +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. +$endif$ + +/src/test/resources/**/data/** text=false Review comment: Yep, I'll fix all the blank line issues. I think the beginning slash actually doesn't make a difference in this pattern, but it does look at bit weird. I'll remove it. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1: URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583186620 ## File path: NOTICE ## @@ -0,0 +1,5 @@ +Apache Daffodil Schema Template +Copyright 2021 The Apache Software Foundation + +This product includes software developed at +The Apache Software Foundation (http://www.apache.org/). Review comment: The "software" in this case is all this source code. I believe this is the standard boilerplate that goes in Apache notice files. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1:
URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583185152
##
File path: .github/workflows/main.yml
##
@@ -0,0 +1,53 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+name: Daffodil Schema Template CI
+
+on: [push, pull_request]
+
+jobs:
+ test:
+name: Java ${{ matrix.java_version }}, Scala ${{ matrix.scala_version }},
${{ matrix.os }}
+strategy:
+ fail-fast: false
+ matrix:
+java_version: [ 8, 11, 15 ]
+scala_version: [ 2.12.11 ]
+os: [ 'ubuntu-latest' ]
+runs-on: ${{ matrix.os }}
+
+steps:
+
+
+ # Setup
+
+
+ - name: Checkout Repository
+uses: actions/checkout@v2.0.0
Review comment:
I know we've ran into an issue at one point where github made an update
to the action that had the same major version and it actually broke something.
To avoid that, we changed our actions to specify a specific version. I'm fine
updating to a newer version if one exist, but to prevent random breakages, I
sort of like to stick with known good versions.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1:
URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583181257
##
File path: .github/workflows/main.yml
##
@@ -0,0 +1,53 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+name: Daffodil Schema Template CI
+
+on: [push, pull_request]
+
+jobs:
+ test:
+name: Java ${{ matrix.java_version }}, Scala ${{ matrix.scala_version }},
${{ matrix.os }}
+strategy:
+ fail-fast: false
+ matrix:
+java_version: [ 8, 11, 15 ]
+scala_version: [ 2.12.11 ]
+os: [ 'ubuntu-latest' ]
+runs-on: ${{ matrix.os }}
+
+steps:
+
+
+ # Setup
+
+
+ - name: Checkout Repository
+uses: actions/checkout@v2.0.0
+
+ - name: Install Java
+uses: actions/setup-java@v1
+with:
+ java-version: ${{ matrix.java_version }}
+
+
+ # Test
+
+
+ - name: Run Rat Check
+run: sbt ++${{ matrix.scala_version }} ratCheck
+
+ - name: Test
+run: sbt ++${{ matrix.scala_version }} test
Review comment:
Yeah, this "sbt test" will run the scripted g8 test mentioned before.
Ill rename the action to make it more clear.
I think maybe the GitHub action won't be enabled until it's in the master
branch, maybe? You can look see what it will look like on my fork:
https://github.com/stevedlawrence/daffodil-schema.g8/runs/1982074448
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
[GitHub] [daffodil-schema.g8] stevedlawrence commented on a change in pull request #1: Add Daffodil schema template
stevedlawrence commented on a change in pull request #1: URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583178535 ## File path: src/test/g8/test ## @@ -0,0 +1,21 @@ +# Licensed to the Apache Software Foundation (ASF) under one or more +# contributor license agreements. See the NOTICE file distributed with +# this work for additional information regarding copyright ownership. +# The ASF licenses this file to You under the Apache License, Version 2.0 +# (the "License"); you may not use this file except in compliance with +# the License. You may obtain a copy of the License at + +# http://www.apache.org/licenses/LICENSE-2.0 + +# Unless required by applicable law or agreed to in writing, software +# distributed under the License is distributed on an "AS IS" BASIS, +# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. +# See the License for the specific language governing permissions and +# limitations under the License. + +# make sure the jar is built +> package +$ exists target/dfdl-format-0.1.0-SNAPSHOT.jar + +# make sure the tests pass +> test Review comment: This is a [scripted](https://www.scala-sbt.org/1.x/docs/Testing-sbt-plugins.html) test file. These are usually used for testing plugins, but it can also be used for testing g8. Essentially what happens is g8 will run "sbt new" on itself, then use this file to run sbt commands and commands that test that those sbt commands work. So this essentially does "sbt new "..., then "sbt package" and makes sure it builds the jar file, then "sbt test" and makes sure those tests pass. This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
[GitHub] [daffodil-schema.g8] tuxji commented on a change in pull request #1: Add Daffodil schema template
tuxji commented on a change in pull request #1:
URL: https://github.com/apache/daffodil-schema.g8/pull/1#discussion_r583134862
##
File path: src/main/g8/.gitattributes
##
@@ -0,0 +1,18 @@
+$if(false)$
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+$endif$
+
+/src/test/resources/**/data/** text=false
Review comment:
You might want to remove the blank line at 17 or move it before line 16
so that the generated .gitattributes doesn't start with a blank line. Also,
should the directory at 18 start with a slash - shouldn't it be a relative path
(`src/test/resources/**/data/**`)?
##
File path: src/main/g8/.gitignore
##
@@ -0,0 +1,18 @@
+$!
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+!$
+
+target
Review comment:
You might want to remove the blank line at 17 or move it before line 16
so the generated .gitignore doesn't start with a blank line.
##
File path: src/test/g8/test
##
@@ -0,0 +1,21 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+
+# http://www.apache.org/licenses/LICENSE-2.0
+
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+# make sure the jar is built
+> package
+$ exists target/dfdl-format-0.1.0-SNAPSHOT.jar
+
+# make sure the tests pass
+> test
Review comment:
If this file is supposed to be a template, I didn't see any file like it
in the generated project. Is the sbt test command in
`.github/workflows/main.yml` supposed to call this file?
##
File path: .github/workflows/main.yml
##
@@ -0,0 +1,53 @@
+# Licensed to the Apache Software Foundation (ASF) under one or more
+# contributor license agreements. See the NOTICE file distributed with
+# this work for additional information regarding copyright ownership.
+# The ASF licenses this file to You under the Apache License, Version 2.0
+# (the "License"); you may not use this file except in compliance with
+# the License. You may obtain a copy of the License at
+#
+# http://www.apache.org/licenses/LICENSE-2.0
+#
+# Unless required by applicable law or agreed to in writing, software
+# distributed under the License is distributed on an "AS IS" BASIS,
+# WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+# See the License for the specific language governing permissions and
+# limitations under the License.
+
+name: Daffodil Schema Template CI
+
+on: [push, pull_request]
+
+jobs:
+ test:
+name: Java ${{ matrix.java_version }}, Scala ${{ matrix.scala_version }},
${{ matrix.os }}
+strategy:
+ fail-fast: false
+ matrix:
+java_version: [ 8, 11, 15 ]
+scala_version: [ 2.12.11 ]
+os: [ 'ubuntu-latest' ]
+runs-on: ${{ matrix.os }}
+
+steps:
+
+
+ # Setup
+
+
Re: New Repository for Daffodil Schema Template?
For those interested, I've created a new pull request so that we can see what this would look like: https://github.com/apache/daffodil-schema.g8/pull/1 If you want to test it out, you can run the command: sbt new stevedlawrence/daffodil-schema.g8 - Steve On 2/25/21 1:18 PM, Beckerle, Mike wrote: > I asked INFRA because I saw that the basic tooling doesn't support it. > > If it's not something easy for them I suggest we should not bother with this, > just put it on github/OpenDFDL with ASL license as now. > > > > From: Steve Lawrence > Sent: Thursday, February 25, 2021 1:12 PM > To: dev@daffodil.apache.org > Subject: Re: New Repository for Daffodil Schema Template? > > Is it possible that the github mirror the .git extension is removed? For > example, our daffodil repo isn't daffodil.git. We don't really care what > the gitbox repo name is. > > I'd also like to give a chance for others to provide input before we > bother infra with this in case a better name is determined, or if > there's a valid objection. > > On 2/25/21 12:58 PM, Beckerle, Mike wrote: >> I have an INFRA ticket requesting this. We'll see if they can do this for us. >> >> https://issues.apache.org/jira/browse/INFRA-21478 >> >> From: Beckerle, Mike >> Sent: Thursday, February 25, 2021 12:54 PM >> To: dev@daffodil.apache.org >> Subject: Re: New Repository for Daffodil Schema Template? >> >> To get a repository created with this ".g8" extension will require an INFRA >> ticket. >> The GUI for creating a new Apache repo just takes a name like "schema" and >> creates a repo named "daffodil-schema.git" from it. >> >> From: Steve Lawrence >> Sent: Thursday, February 25, 2021 12:44 PM >> To: dev@daffodil.apache.org >> Subject: New Repository for Daffodil Schema Template? >> >> >> The below relates to DAFFODIL-2144: >> >> https://issues.apache.org/jira/browse/DAFFODIL-2144 >> >> On github.com/OpenDFDL, there is a repository called >> "dfdl-project-layout.g8". This repository is a Giter8 [1] template repo >> that makes it easier for users to create a new schema that follows the >> standard project layout for developing schemas with Daffodil, as >> described here: >> >> https://daffodil.apache.org/dfdl-layout/ >> >> With this template repo, users can run the following command to generate >> a standard project layout for a new format: >> >> sbt new OpenDFDL/dfdl-project-layout.g8 >> >> This will ask a couple questions and then generate files/dirs based on >> the template in the repo. This is very convenient for users to quickly >> start with Daffodil schema development. >> >> However, since this project is so closely related to Daffodil, and since >> it can all be contributed as ALv2, that I think it makes more sense to >> move the template to a repository on ASF infrastructure. A Giter8 >> template repo has some requirements though: >> >> 1) It be in its own repository >> 2) The repository name ends .g8 >> 3) The repository is hosted on GitHub >> >> Requirements 1 and 2 mean we cannot use the existing daffodil repo, so a >> new repo is required. We can very easily create a new repo on Apache >> infrastructure with GitBox to meet those requirments, and GitBox will >> mirror it to GitHub to meet the third requirement. >> >> So questions are: >> >> 1) Are there any objections to moving this to Apache infrastructure? >> >> 2) Assuming no objections, what should the name of this new repo be? I >> was thinking something simple like "daffodil-schema.g8" might be a good >> candidate. It's short and easy to remember, and it reads nicely when >> considering that the command to use it would look like >> >> sbt new apache/daffodil-schema.g8 >> >> But I'm open to other suggestions. >> >> Thanks, >> - Steve >> >> [1] http://www.foundweekends.org/giter8/ >> > >
[GitHub] [daffodil-schema.g8] stevedlawrence opened a new pull request #1: Add Daffodil schema template
stevedlawrence opened a new pull request #1: URL: https://github.com/apache/daffodil-schema.g8/pull/1 - Create a Giter8 template repository for easily creating Daffodil schema projects. Everything in src/main/g8/ uses template syntax. Note that all the files in this directory are Apache Licensed, but the licenses are in g8 comments so that when files are generated they are not licensed. This lets the user determine what license they want their schema to use. - Also includes .asf.yaml and .github files to configure GithHub settings and continuous integration DAFFODIL-2144 This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org
Re: New Repository for Daffodil Schema Template?
I asked INFRA because I saw that the basic tooling doesn't support it. If it's not something easy for them I suggest we should not bother with this, just put it on github/OpenDFDL with ASL license as now. From: Steve Lawrence Sent: Thursday, February 25, 2021 1:12 PM To: dev@daffodil.apache.org Subject: Re: New Repository for Daffodil Schema Template? Is it possible that the github mirror the .git extension is removed? For example, our daffodil repo isn't daffodil.git. We don't really care what the gitbox repo name is. I'd also like to give a chance for others to provide input before we bother infra with this in case a better name is determined, or if there's a valid objection. On 2/25/21 12:58 PM, Beckerle, Mike wrote: > I have an INFRA ticket requesting this. We'll see if they can do this for us. > > https://issues.apache.org/jira/browse/INFRA-21478 > > From: Beckerle, Mike > Sent: Thursday, February 25, 2021 12:54 PM > To: dev@daffodil.apache.org > Subject: Re: New Repository for Daffodil Schema Template? > > To get a repository created with this ".g8" extension will require an INFRA > ticket. > The GUI for creating a new Apache repo just takes a name like "schema" and > creates a repo named "daffodil-schema.git" from it. > > From: Steve Lawrence > Sent: Thursday, February 25, 2021 12:44 PM > To: dev@daffodil.apache.org > Subject: New Repository for Daffodil Schema Template? > > > The below relates to DAFFODIL-2144: > > https://issues.apache.org/jira/browse/DAFFODIL-2144 > > On github.com/OpenDFDL, there is a repository called > "dfdl-project-layout.g8". This repository is a Giter8 [1] template repo > that makes it easier for users to create a new schema that follows the > standard project layout for developing schemas with Daffodil, as > described here: > > https://daffodil.apache.org/dfdl-layout/ > > With this template repo, users can run the following command to generate > a standard project layout for a new format: > > sbt new OpenDFDL/dfdl-project-layout.g8 > > This will ask a couple questions and then generate files/dirs based on > the template in the repo. This is very convenient for users to quickly > start with Daffodil schema development. > > However, since this project is so closely related to Daffodil, and since > it can all be contributed as ALv2, that I think it makes more sense to > move the template to a repository on ASF infrastructure. A Giter8 > template repo has some requirements though: > > 1) It be in its own repository > 2) The repository name ends .g8 > 3) The repository is hosted on GitHub > > Requirements 1 and 2 mean we cannot use the existing daffodil repo, so a > new repo is required. We can very easily create a new repo on Apache > infrastructure with GitBox to meet those requirments, and GitBox will > mirror it to GitHub to meet the third requirement. > > So questions are: > > 1) Are there any objections to moving this to Apache infrastructure? > > 2) Assuming no objections, what should the name of this new repo be? I > was thinking something simple like "daffodil-schema.g8" might be a good > candidate. It's short and easy to remember, and it reads nicely when > considering that the command to use it would look like > > sbt new apache/daffodil-schema.g8 > > But I'm open to other suggestions. > > Thanks, > - Steve > > [1] http://www.foundweekends.org/giter8/ >
Re: New Repository for Daffodil Schema Template?
Is it possible that the github mirror the .git extension is removed? For example, our daffodil repo isn't daffodil.git. We don't really care what the gitbox repo name is. I'd also like to give a chance for others to provide input before we bother infra with this in case a better name is determined, or if there's a valid objection. On 2/25/21 12:58 PM, Beckerle, Mike wrote: > I have an INFRA ticket requesting this. We'll see if they can do this for us. > > https://issues.apache.org/jira/browse/INFRA-21478 > > From: Beckerle, Mike > Sent: Thursday, February 25, 2021 12:54 PM > To: dev@daffodil.apache.org > Subject: Re: New Repository for Daffodil Schema Template? > > To get a repository created with this ".g8" extension will require an INFRA > ticket. > The GUI for creating a new Apache repo just takes a name like "schema" and > creates a repo named "daffodil-schema.git" from it. > > From: Steve Lawrence > Sent: Thursday, February 25, 2021 12:44 PM > To: dev@daffodil.apache.org > Subject: New Repository for Daffodil Schema Template? > > > The below relates to DAFFODIL-2144: > > https://issues.apache.org/jira/browse/DAFFODIL-2144 > > On github.com/OpenDFDL, there is a repository called > "dfdl-project-layout.g8". This repository is a Giter8 [1] template repo > that makes it easier for users to create a new schema that follows the > standard project layout for developing schemas with Daffodil, as > described here: > > https://daffodil.apache.org/dfdl-layout/ > > With this template repo, users can run the following command to generate > a standard project layout for a new format: > > sbt new OpenDFDL/dfdl-project-layout.g8 > > This will ask a couple questions and then generate files/dirs based on > the template in the repo. This is very convenient for users to quickly > start with Daffodil schema development. > > However, since this project is so closely related to Daffodil, and since > it can all be contributed as ALv2, that I think it makes more sense to > move the template to a repository on ASF infrastructure. A Giter8 > template repo has some requirements though: > > 1) It be in its own repository > 2) The repository name ends .g8 > 3) The repository is hosted on GitHub > > Requirements 1 and 2 mean we cannot use the existing daffodil repo, so a > new repo is required. We can very easily create a new repo on Apache > infrastructure with GitBox to meet those requirments, and GitBox will > mirror it to GitHub to meet the third requirement. > > So questions are: > > 1) Are there any objections to moving this to Apache infrastructure? > > 2) Assuming no objections, what should the name of this new repo be? I > was thinking something simple like "daffodil-schema.g8" might be a good > candidate. It's short and easy to remember, and it reads nicely when > considering that the command to use it would look like > > sbt new apache/daffodil-schema.g8 > > But I'm open to other suggestions. > > Thanks, > - Steve > > [1] http://www.foundweekends.org/giter8/ >
Re: New Repository for Daffodil Schema Template?
I have an INFRA ticket requesting this. We'll see if they can do this for us. https://issues.apache.org/jira/browse/INFRA-21478 From: Beckerle, Mike Sent: Thursday, February 25, 2021 12:54 PM To: dev@daffodil.apache.org Subject: Re: New Repository for Daffodil Schema Template? To get a repository created with this ".g8" extension will require an INFRA ticket. The GUI for creating a new Apache repo just takes a name like "schema" and creates a repo named "daffodil-schema.git" from it. From: Steve Lawrence Sent: Thursday, February 25, 2021 12:44 PM To: dev@daffodil.apache.org Subject: New Repository for Daffodil Schema Template? The below relates to DAFFODIL-2144: https://issues.apache.org/jira/browse/DAFFODIL-2144 On github.com/OpenDFDL, there is a repository called "dfdl-project-layout.g8". This repository is a Giter8 [1] template repo that makes it easier for users to create a new schema that follows the standard project layout for developing schemas with Daffodil, as described here: https://daffodil.apache.org/dfdl-layout/ With this template repo, users can run the following command to generate a standard project layout for a new format: sbt new OpenDFDL/dfdl-project-layout.g8 This will ask a couple questions and then generate files/dirs based on the template in the repo. This is very convenient for users to quickly start with Daffodil schema development. However, since this project is so closely related to Daffodil, and since it can all be contributed as ALv2, that I think it makes more sense to move the template to a repository on ASF infrastructure. A Giter8 template repo has some requirements though: 1) It be in its own repository 2) The repository name ends .g8 3) The repository is hosted on GitHub Requirements 1 and 2 mean we cannot use the existing daffodil repo, so a new repo is required. We can very easily create a new repo on Apache infrastructure with GitBox to meet those requirments, and GitBox will mirror it to GitHub to meet the third requirement. So questions are: 1) Are there any objections to moving this to Apache infrastructure? 2) Assuming no objections, what should the name of this new repo be? I was thinking something simple like "daffodil-schema.g8" might be a good candidate. It's short and easy to remember, and it reads nicely when considering that the command to use it would look like sbt new apache/daffodil-schema.g8 But I'm open to other suggestions. Thanks, - Steve [1] http://www.foundweekends.org/giter8/
Re: New Repository for Daffodil Schema Template?
To get a repository created with this ".g8" extension will require an INFRA ticket. The GUI for creating a new Apache repo just takes a name like "schema" and creates a repo named "daffodil-schema.git" from it. From: Steve Lawrence Sent: Thursday, February 25, 2021 12:44 PM To: dev@daffodil.apache.org Subject: New Repository for Daffodil Schema Template? The below relates to DAFFODIL-2144: https://issues.apache.org/jira/browse/DAFFODIL-2144 On github.com/OpenDFDL, there is a repository called "dfdl-project-layout.g8". This repository is a Giter8 [1] template repo that makes it easier for users to create a new schema that follows the standard project layout for developing schemas with Daffodil, as described here: https://daffodil.apache.org/dfdl-layout/ With this template repo, users can run the following command to generate a standard project layout for a new format: sbt new OpenDFDL/dfdl-project-layout.g8 This will ask a couple questions and then generate files/dirs based on the template in the repo. This is very convenient for users to quickly start with Daffodil schema development. However, since this project is so closely related to Daffodil, and since it can all be contributed as ALv2, that I think it makes more sense to move the template to a repository on ASF infrastructure. A Giter8 template repo has some requirements though: 1) It be in its own repository 2) The repository name ends .g8 3) The repository is hosted on GitHub Requirements 1 and 2 mean we cannot use the existing daffodil repo, so a new repo is required. We can very easily create a new repo on Apache infrastructure with GitBox to meet those requirments, and GitBox will mirror it to GitHub to meet the third requirement. So questions are: 1) Are there any objections to moving this to Apache infrastructure? 2) Assuming no objections, what should the name of this new repo be? I was thinking something simple like "daffodil-schema.g8" might be a good candidate. It's short and easy to remember, and it reads nicely when considering that the command to use it would look like sbt new apache/daffodil-schema.g8 But I'm open to other suggestions. Thanks, - Steve [1] http://www.foundweekends.org/giter8/
New Repository for Daffodil Schema Template?
The below relates to DAFFODIL-2144: https://issues.apache.org/jira/browse/DAFFODIL-2144 On github.com/OpenDFDL, there is a repository called "dfdl-project-layout.g8". This repository is a Giter8 [1] template repo that makes it easier for users to create a new schema that follows the standard project layout for developing schemas with Daffodil, as described here: https://daffodil.apache.org/dfdl-layout/ With this template repo, users can run the following command to generate a standard project layout for a new format: sbt new OpenDFDL/dfdl-project-layout.g8 This will ask a couple questions and then generate files/dirs based on the template in the repo. This is very convenient for users to quickly start with Daffodil schema development. However, since this project is so closely related to Daffodil, and since it can all be contributed as ALv2, that I think it makes more sense to move the template to a repository on ASF infrastructure. A Giter8 template repo has some requirements though: 1) It be in its own repository 2) The repository name ends .g8 3) The repository is hosted on GitHub Requirements 1 and 2 mean we cannot use the existing daffodil repo, so a new repo is required. We can very easily create a new repo on Apache infrastructure with GitBox to meet those requirments, and GitBox will mirror it to GitHub to meet the third requirement. So questions are: 1) Are there any objections to moving this to Apache infrastructure? 2) Assuming no objections, what should the name of this new repo be? I was thinking something simple like "daffodil-schema.g8" might be a good candidate. It's short and easy to remember, and it reads nicely when considering that the command to use it would look like sbt new apache/daffodil-schema.g8 But I'm open to other suggestions. Thanks, - Steve [1] http://www.foundweekends.org/giter8/
