Pivot
  1. Pivot
  2. PIVOT-397

maven archetype for a minimal pivot application, to use as a starting point

    Details

    • Type: New Feature New Feature
    • Status: Resolved
    • Priority: Minor Minor
    • Resolution: Fixed
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: maven-archetypes
    • Labels:
      None

      Description

      Create a maven archetype for a basic (minimal, near-empty) pivot application (like most -basic archetypes for other frameworks).

      This is inside a dedicated new subproject ( pivot-archetype-quickstart ), because tools is not the right place for it, and to avoid confusion with other Pivot projects, currently it's under /skunk .

      1. myapp.zip
        21 kB
        Sandro Martini
      2. myapp_generated.zip
        19 kB
        Sandro Martini
      3. pivot-archetype-quickstart-1.0.4.jar
        20 kB
        Sandro Martini
      4. pivot-archetype-quickstart-1.0.2.zip
        35 kB
        Sandro Martini
      5. pivot-archetype-quickstart-1.0.1.zip
        35 kB
        Sandro Martini

        Activity

        Hide
        Sandro Martini added a comment -

        Wait until some user requires this.

        Show
        Sandro Martini added a comment - Wait until some user requires this.
        Hide
        Patrick Slamp added a comment -

        Quickstart Archetype for Apache Pivot.

        First zip: contains jar file including pom for Maven.

        Second zip: contains the source of the archetype.

        Show
        Patrick Slamp added a comment - Quickstart Archetype for Apache Pivot. First zip: contains jar file including pom for Maven. Second zip: contains the source of the archetype.
        Hide
        Greg Brown added a comment -

        Looks good to me, though I'm not really familiar with how Maven archetypes work. Just a couple of comments:

        1) Since this will probably be added to Pivot 2.x, you'll need to update it to use BXML rather than WTKX.

        2) I'd suggest including an example of Bindable in the sample. For example, rather than a Window for a root element, create a custom Window subclass that implements Bindable and use that as your root element. Most applications are probably going to need a main window that implements Bindable, so this will help simplify the process of getting started.

        FYI, the tools project no longer exists in Pivot 2.0 so we'll need to figure out another place to put it. What do other projects generally do?

        Show
        Greg Brown added a comment - Looks good to me, though I'm not really familiar with how Maven archetypes work. Just a couple of comments: 1) Since this will probably be added to Pivot 2.x, you'll need to update it to use BXML rather than WTKX. 2) I'd suggest including an example of Bindable in the sample. For example, rather than a Window for a root element, create a custom Window subclass that implements Bindable and use that as your root element. Most applications are probably going to need a main window that implements Bindable, so this will help simplify the process of getting started. FYI, the tools project no longer exists in Pivot 2.0 so we'll need to figure out another place to put it. What do other projects generally do?
        Hide
        Greg Brown added a comment -

        You might be able to use the JavaWindow.java and java_window.bxml files in this example as a starting point:

        http://svn.apache.org/repos/asf/pivot/trunk/examples/src/org/apache/pivot/examples/scripting/

        Actually, the examples project would probably be a good place for the archetype app.

        Show
        Greg Brown added a comment - You might be able to use the JavaWindow.java and java_window.bxml files in this example as a starting point: http://svn.apache.org/repos/asf/pivot/trunk/examples/src/org/apache/pivot/examples/scripting/ Actually, the examples project would probably be a good place for the archetype app.
        Hide
        Sandro Martini added a comment -

        Hi to all,
        Patrick, thanks for the samples ... and thanks to Greg for suggestions.
        I'll start with it (implementing the changes suggested by Greg) just after the 2.0 release.

        In the meantime I'll try to look at it, and start to see how Maven archetypes should be created and tested.
        Probably I'll have to ask to Patrick some info ...

        Last, I have to see how we can publish it in the main Maven repository ... if someone has some info, please tell me or writehere.

        Thank you for the moment.

        Bye,
        Sandro

        Show
        Sandro Martini added a comment - Hi to all, Patrick, thanks for the samples ... and thanks to Greg for suggestions. I'll start with it (implementing the changes suggested by Greg) just after the 2.0 release. In the meantime I'll try to look at it, and start to see how Maven archetypes should be created and tested. Probably I'll have to ask to Patrick some info ... Last, I have to see how we can publish it in the main Maven repository ... if someone has some info, please tell me or writehere. Thank you for the moment. Bye, Sandro
        Hide
        Sandro Martini added a comment -

        > FYI, the tools project no longer exists in Pivot 2.0 so we'll need to figure out another place to put it.
        Instead of examples, I'm thinking if /skunk could be a better place, maybe temporary, (skunk is an experimental area, and outside trunk so all this will not be linked to Pivot releases and in this case could be good).
        So the first archetype will have there its project, then maybe others ...

        > What do other projects generally do?
        I think they have a dedicated project (and this is a safer approach, for dependencies, etc).

        Show
        Sandro Martini added a comment - > FYI, the tools project no longer exists in Pivot 2.0 so we'll need to figure out another place to put it. Instead of examples, I'm thinking if /skunk could be a better place, maybe temporary, (skunk is an experimental area, and outside trunk so all this will not be linked to Pivot releases and in this case could be good). So the first archetype will have there its project, then maybe others ... > What do other projects generally do? I think they have a dedicated project (and this is a safer approach, for dependencies, etc).
        Hide
        Greg Brown added a comment -

        I think the examples project is appropriate, because a Maven archetype is essentially an example that you can start working from. If we end up creating more than one, we could consider moving it to a separate project. But I don't think I'd put it in /skunk, because that isn't included in any distribution and isn't all that easy to find.

        Show
        Greg Brown added a comment - I think the examples project is appropriate, because a Maven archetype is essentially an example that you can start working from. If we end up creating more than one, we could consider moving it to a separate project. But I don't think I'd put it in /skunk, because that isn't included in any distribution and isn't all that easy to find.
        Hide
        Sandro Martini added a comment -

        A quick comment:
        maven archetypes are used (consumed) by downloading them from a (remote) repository usually, so could be good to not have them in Pivot distribution.

        But for me having them under examples or other is not a problem, I can start under examples, and maybe move it later if/when needed.

        Bye,
        Sandro

        Show
        Sandro Martini added a comment - A quick comment: maven archetypes are used (consumed) by downloading them from a (remote) repository usually, so could be good to not have them in Pivot distribution. But for me having them under examples or other is not a problem, I can start under examples, and maybe move it later if/when needed. Bye, Sandro
        Hide
        Greg Brown added a comment -

        The examples project is not included in the distribution.

        Show
        Greg Brown added a comment - The examples project is not included in the distribution.
        Hide
        Sandro Martini added a comment -

        > The examples project is not included in the distribution.
        Yes, I know.
        So this makes sense even for the 2.0 (if I find enough time), or should I defer to 2.1 (as the current plan) ?
        I'll start to write something under examples, and see later what to do.

        But if we want (maybe later) to have this archetype (and maybe others too) published in main Apache Maven repository (and for this we have to see how to do), probably we''l need some build script for it and a deploy script, and a maven descriptor.

        I'll post here updates as soon as possible.

        Sandro

        Show
        Sandro Martini added a comment - > The examples project is not included in the distribution. Yes, I know. So this makes sense even for the 2.0 (if I find enough time), or should I defer to 2.1 (as the current plan) ? I'll start to write something under examples, and see later what to do. But if we want (maybe later) to have this archetype (and maybe others too) published in main Apache Maven repository (and for this we have to see how to do), probably we''l need some build script for it and a deploy script, and a maven descriptor. I'll post here updates as soon as possible. Sandro
        Hide
        Greg Brown added a comment -

        It should be OK to put the POM for this in the examples/maven-archetype directory directly, or wherever is most appropriate (for example, we have an Ant script called deployment-example.xml in the root directory that isn't included in the distribution, but is used to build Windows and OS X native deployment containers for a sample app in the examples project).

        Show
        Greg Brown added a comment - It should be OK to put the POM for this in the examples/maven-archetype directory directly, or wherever is most appropriate (for example, we have an Ant script called deployment-example.xml in the root directory that isn't included in the distribution, but is used to build Windows and OS X native deployment containers for a sample app in the examples project).
        Hide
        Sandro Martini added a comment -

        Hi, after many time now I'm restarting to look at this issue ... some info here:
        http://maven.apache.org/guides/mini/guide-creating-archetypes.html

        In short I think this is not suitable to be put under examples because for example the package inside java sources has to be parametric, for example using the quickstart maven archetype, inside the sample App.java we have this:
        package $package;

        so if I'd put this stuff under examples (of course in a dedicated folder) we break the build of examples for all IDE users.

        So I propose (another time, but now with more reasons ) to put it under /skunk (and not in one of our other secondary Pivot-related projects on GoogleCode).
        Or this could be a folder inside examples, but NOT under src (so not in build path in eclipse).
        What do you prefer ?

        After this, I'd like to have it published in the Main Apache Repository (so maven users could use it directly, without having to download/compile examples), but someone of us has rights to do this (for example with a Company mirror) ?
        I'm sorry but I haven't this ability ...

        Tell me what you think.

        Bye,
        Sandro

        Show
        Sandro Martini added a comment - Hi, after many time now I'm restarting to look at this issue ... some info here: http://maven.apache.org/guides/mini/guide-creating-archetypes.html In short I think this is not suitable to be put under examples because for example the package inside java sources has to be parametric, for example using the quickstart maven archetype, inside the sample App.java we have this: package $package; so if I'd put this stuff under examples (of course in a dedicated folder) we break the build of examples for all IDE users. So I propose (another time, but now with more reasons ) to put it under /skunk (and not in one of our other secondary Pivot-related projects on GoogleCode). Or this could be a folder inside examples, but NOT under src (so not in build path in eclipse). What do you prefer ? After this, I'd like to have it published in the Main Apache Repository (so maven users could use it directly, without having to download/compile examples), but someone of us has rights to do this (for example with a Company mirror) ? I'm sorry but I haven't this ability ... Tell me what you think. Bye, Sandro
        Show
        Sandro Martini added a comment - some info here: http://apache-pivot-developers.417237.n3.nabble.com/PIVOT-397-td2931279.html
        Hide
        Sandro Martini added a comment -

        As Greg suggested some time ago maybe a custom Window implementing Bindable could be useful to have in the archetype.

        Show
        Sandro Martini added a comment - As Greg suggested some time ago maybe a custom Window implementing Bindable could be useful to have in the archetype.
        Hide
        Edvin Syse added a comment -

        I created a quickstart archetype for Pivot 2.0 that showcases Bindable and @BXML as a reply to a question on the mailing list the other day:

        http://apache-pivot-users.399431.n3.nabble.com/Maven-Archetype-td2968451.html

        It uses the new archetype-metadata format, so it should be a good starting point for an official quickstart archetype. It might actually be production ready as it is. Check it out

        I'll repeat the usage info here:

        Unzip the archive and run mvn install to install the quickstart archetype to your local repo.

        To create, do:

        mvn archetype:generate -DarchetypeGroupId=org.apache.pivot -DarchetypeArtifactId=quickstart -DarchetypeVersion=2.0 -DgroupId=com.mycompany -DartifactId=myapp

        From there you can either start the app using Maven like this:

        mvn compile
        mvn exec:java

        Or you can start org.apache.pivot.wtk.DesktopApplicationContext with com.mycompany.PivotApplication as the first argument from your IDE.

        For convenience, a main method is included in com.mycompany.PivotApplication as well.

        Show
        Edvin Syse added a comment - I created a quickstart archetype for Pivot 2.0 that showcases Bindable and @BXML as a reply to a question on the mailing list the other day: http://apache-pivot-users.399431.n3.nabble.com/Maven-Archetype-td2968451.html It uses the new archetype-metadata format, so it should be a good starting point for an official quickstart archetype. It might actually be production ready as it is. Check it out I'll repeat the usage info here: Unzip the archive and run mvn install to install the quickstart archetype to your local repo. To create, do: mvn archetype:generate -DarchetypeGroupId=org.apache.pivot -DarchetypeArtifactId=quickstart -DarchetypeVersion=2.0 -DgroupId=com.mycompany -DartifactId=myapp From there you can either start the app using Maven like this: mvn compile mvn exec:java Or you can start org.apache.pivot.wtk.DesktopApplicationContext with com.mycompany.PivotApplication as the first argument from your IDE. For convenience, a main method is included in com.mycompany.PivotApplication as well.
        Hide
        Edvin Syse added a comment -

        Pivot 2.0 quickstart archetype

        Show
        Edvin Syse added a comment - Pivot 2.0 quickstart archetype
        Hide
        Rob Shepherd added a comment - - edited

        @pivot-quickstart.zip +1

        Worked great for me.

        Show
        Rob Shepherd added a comment - - edited @pivot-quickstart.zip +1 Worked great for me.
        Hide
        Sandro Martini added a comment -

        Hi,
        just looked at sources and seems good .
        Only few little things, just for reference:

        • name, probably to avoid confusion with other Apache Quickstart we could name it pivot-archetype-quickstart
        • inside there is an IDEA project file (probably should be better to not include it, otherwise we could even add eclipse project files)
        • resource filtering, I'd add a filter so .bxml files and others would be accepted only in resources folder, to be more in aligned with Maven conventions
        • HelloWorldFrame, I'd use another name, like MainFrame or PivotApplicationFrame
        • bindable, I'd reuse the same as in JavaWindow (under examples)

        Comments ?

        I'll try all this stuff and commit it if possible this week (but not under /trunk, under /skunk, here http://svn.apache.org/repos/asf/pivot/skunk/ instead, because it's not strictly related to Pivot codebase and to a Pivot Release).
        Next, for having it in the main Maven Repository I'll see what to do as soon as possible.

        Thank you very much,
        Sandro

        Show
        Sandro Martini added a comment - Hi, just looked at sources and seems good . Only few little things, just for reference: name, probably to avoid confusion with other Apache Quickstart we could name it pivot-archetype-quickstart inside there is an IDEA project file (probably should be better to not include it, otherwise we could even add eclipse project files) resource filtering, I'd add a filter so .bxml files and others would be accepted only in resources folder, to be more in aligned with Maven conventions HelloWorldFrame, I'd use another name, like MainFrame or PivotApplicationFrame bindable, I'd reuse the same as in JavaWindow (under examples) Comments ? I'll try all this stuff and commit it if possible this week (but not under /trunk, under /skunk, here http://svn.apache.org/repos/asf/pivot/skunk/ instead, because it's not strictly related to Pivot codebase and to a Pivot Release). Next, for having it in the main Maven Repository I'll see what to do as soon as possible. Thank you very much, Sandro
        Hide
        Edvin Syse added a comment -

        I agree with all your points. I did this in 10 minutes just to get it out the door, didn't think much about naming conventions etc Just make the changes to the archive I uploaded or tell me if you want me to do it.

        Show
        Edvin Syse added a comment - I agree with all your points. I did this in 10 minutes just to get it out the door, didn't think much about naming conventions etc Just make the changes to the archive I uploaded or tell me if you want me to do it.
        Hide
        Sandro Martini added a comment -

        Hi Edvin,
        if you have time to do it, for me it would be a time saver (so I'll only have to do checks on code, files, etc the same).
        Don't worry, if you find time do it and upload the newer version, otherwise I'll do it.
        Thank you again for your work (code and comments).

        Bye,
        Sandro

        Show
        Sandro Martini added a comment - Hi Edvin, if you have time to do it, for me it would be a time saver (so I'll only have to do checks on code, files, etc the same). Don't worry, if you find time do it and upload the newer version, otherwise I'll do it. Thank you again for your work (code and comments). Bye, Sandro
        Hide
        Edvin Syse added a comment -

        Performed the following changes:

        • Renamed to pivot-archetype-quickstart
        • Added licensing information
        • Switched Frame for Window, renamed, and now use the same components as JavaWindow

        I think the default resource filtering rules are good, but change them if you want

        Command to run is now:

        mvn archetype:generate -DarchetypeGroupId=org.apache.pivot -DarchetypeArtifactId=pivot-archetype-quickstart -DarchetypeVersion=2.0 -DgroupId=com.mycompany -DartifactId=myapp -DinteractiveMode=false

        Hope this is OK

        Show
        Edvin Syse added a comment - Performed the following changes: Renamed to pivot-archetype-quickstart Added licensing information Switched Frame for Window, renamed, and now use the same components as JavaWindow I think the default resource filtering rules are good, but change them if you want Command to run is now: mvn archetype:generate -DarchetypeGroupId=org.apache.pivot -DarchetypeArtifactId=pivot-archetype-quickstart -DarchetypeVersion=2.0 -DgroupId=com.mycompany -DartifactId=myapp -DinteractiveMode=false Hope this is OK
        Hide
        Sandro Martini added a comment -

        I'll check new artifact as soon as possible, thank you very much for now
        And ... great job .

        Bye

        Show
        Sandro Martini added a comment - I'll check new artifact as soon as possible, thank you very much for now And ... great job . Bye
        Hide
        Sandro Martini added a comment -

        Hi all,
        just checked a (little revised version) of the archetype under the /skunk area of our SVN.
        All seems to be good, and I've added some of our "standard files" in root, like BUILD with some info on how to use it.

        For simplicity, I attach here a zip with updated sources, and a zip of a sample application generated, for lazy people like me ...
        To avoid confusion with other attachments here I think it will be good to delete others (old), ok ?

        Tell me if there is something to improve or to change, otherwise I'll try to go to the next step now, or "see how to publish it in the main maven repository" and probably we should take a vote on it.

        Bye

        Show
        Sandro Martini added a comment - Hi all, just checked a (little revised version) of the archetype under the /skunk area of our SVN. All seems to be good, and I've added some of our "standard files" in root, like BUILD with some info on how to use it. For simplicity, I attach here a zip with updated sources, and a zip of a sample application generated, for lazy people like me ... To avoid confusion with other attachments here I think it will be good to delete others (old), ok ? Tell me if there is something to improve or to change, otherwise I'll try to go to the next step now, or "see how to publish it in the main maven repository" and probably we should take a vote on it. Bye
        Hide
        Sandro Martini added a comment -

        Latest version of artifact sources and sample application generated by it.

        Show
        Sandro Martini added a comment - Latest version of artifact sources and sample application generated by it.
        Hide
        Sandro Martini added a comment -

        Extract from BUILD file (in archetype sources), for some quick test on it (after unzipping it):

        • To install the archetype in a local Maven repository:

        $ cd pivot-archetype-quickstart
        $ mvn -U install
        $ cd ..

        • To Test is, generating a Pivot Project (called "myapp") with it
          (and give to it the desired package name when requested, like "com.mycompany.myapp",
          note that usually the ".myapp" part in the package is written only if overridden here):
          $ mvn archetype:generate -U -DarchetypeGroupId=org.apache.pivot -DarchetypeArtifactId=pivot-archetype-quickstart -DarchetypeVersion=1.0 -DgroupId=com.mycompany -DartifactId=myapp -Dversion=1.0
          then, compile the project and run it.

        This is currently missing in BUILD file, telle me if you think could be useful:
        Tu run it (for example from the Command-line):

        $ cd myapp
        $ mvn -U clean package
        or
        $ mvn -U compile
        $ mvn -U exec:java
        $ cd ..

        Note that here I force the update mode in maven commands (-U flag) but of course it's optional (but useful to ensure all is updated).

        Tell me what you think.

        Bye

        Show
        Sandro Martini added a comment - Extract from BUILD file (in archetype sources), for some quick test on it (after unzipping it): To install the archetype in a local Maven repository: $ cd pivot-archetype-quickstart $ mvn -U install $ cd .. To Test is, generating a Pivot Project (called "myapp") with it (and give to it the desired package name when requested, like "com.mycompany.myapp", note that usually the ".myapp" part in the package is written only if overridden here): $ mvn archetype:generate -U -DarchetypeGroupId=org.apache.pivot -DarchetypeArtifactId=pivot-archetype-quickstart -DarchetypeVersion=1.0 -DgroupId=com.mycompany -DartifactId=myapp -Dversion=1.0 then, compile the project and run it. This is currently missing in BUILD file, telle me if you think could be useful: Tu run it (for example from the Command-line): $ cd myapp $ mvn -U clean package or $ mvn -U compile $ mvn -U exec:java $ cd .. Note that here I force the update mode in maven commands (-U flag) but of course it's optional (but useful to ensure all is updated). Tell me what you think. Bye
        Hide
        Edvin Syse added a comment -

        Looks good, but why do you exclude */.java from src/main/resources? If someone actually puts a java-file in src/main/resources, maybe it is because they want to actually use that resource in their application

        Show
        Edvin Syse added a comment - Looks good, but why do you exclude * / .java from src/main/resources? If someone actually puts a java-file in src/main/resources, maybe it is because they want to actually use that resource in their application
        Hide
        Sandro Martini added a comment -

        In what case you put Java sources as resources (what use cases you have for this, I'm curious) ?
        In this way I force users to put sources in the usual src folder, and resources (bxml, images, etc, or everything but not sources) in the usual resources folder, I think it's a best practice ... I agree that seems too restrictive, but if this doesn't break user application I'd prefer to keep as is.

        What do you think ?

        And last, I have created test folders for sources and resources but currently are empty, if useful I could add a trivial JUnit test there just to have it as a marker ... for example I could test that the bxml file (the same used by the application) is loaded.

        Bye

        Show
        Sandro Martini added a comment - In what case you put Java sources as resources (what use cases you have for this, I'm curious) ? In this way I force users to put sources in the usual src folder, and resources (bxml, images, etc, or everything but not sources) in the usual resources folder, I think it's a best practice ... I agree that seems too restrictive, but if this doesn't break user application I'd prefer to keep as is. What do you think ? And last, I have created test folders for sources and resources but currently are empty, if useful I could add a trivial JUnit test there just to have it as a marker ... for example I could test that the bxml file (the same used by the application) is loaded. Bye
        Hide
        Edvin Syse added a comment -

        Let's say a user includes a java-file to be used as a template for an editor for example. I think the only thing you can achieve by not copying in java-resources is a confused user and questions on the mailing list later on

        It's nice that you set up the testing infrastructure. I think it's a good idea to keep the tests empty, any test you put there will be cruft the user will most likely want to remove anyway.

        Show
        Edvin Syse added a comment - Let's say a user includes a java-file to be used as a template for an editor for example. I think the only thing you can achieve by not copying in java-resources is a confused user and questions on the mailing list later on It's nice that you set up the testing infrastructure. I think it's a good idea to keep the tests empty, any test you put there will be cruft the user will most likely want to remove anyway.
        Hide
        Sandro Martini added a comment - - edited

        Ok on empty tests, that was my thinking (avoid to put trivial things that any user has to delete).

        On resource filtering I understand your reasons, and I could change the current behavior, to disable the filtering both in sources and in resources, so if someone prefers to put bxml files under sources and (for whatever reason) java under resources, it will be possible ... we are always in time to re-enable the filtering in the future if wanted .

        In next days (the change is trivial but you know I have very little time to work on it) I'll make the change, and re-test all.
        In the meantime, send me usage feedback, improvements, etc ...

        Edvin, thanks again for the help/support on this feature.

        Greg and others, what do you think ?

        Sorry, a last thing, if there aren't objections I'm planning to remove old attachments here to avoid confusion, and attach only the latest version.

        Show
        Sandro Martini added a comment - - edited Ok on empty tests, that was my thinking (avoid to put trivial things that any user has to delete). On resource filtering I understand your reasons, and I could change the current behavior, to disable the filtering both in sources and in resources, so if someone prefers to put bxml files under sources and (for whatever reason) java under resources, it will be possible ... we are always in time to re-enable the filtering in the future if wanted . In next days (the change is trivial but you know I have very little time to work on it) I'll make the change, and re-test all. In the meantime, send me usage feedback, improvements, etc ... Edvin, thanks again for the help/support on this feature. Greg and others, what do you think ? Sorry, a last thing, if there aren't objections I'm planning to remove old attachments here to avoid confusion, and attach only the latest version.
        Hide
        Sandro Martini added a comment -

        Just commited the exclusion of java sources from resources folders (but keep commented), and little changes in BUILD file.
        And removed ald attachments here and post only latest (current) version, to avoid confusion.

        Now I'm ready to tag this project under SVN (like pivot-archetype-quickstart-1.0), if there aren't objections.
        I'll write a post on our developers mailing list on this.

        Show
        Sandro Martini added a comment - Just commited the exclusion of java sources from resources folders (but keep commented), and little changes in BUILD file. And removed ald attachments here and post only latest (current) version, to avoid confusion. Now I'm ready to tag this project under SVN (like pivot-archetype-quickstart-1.0), if there aren't objections. I'll write a post on our developers mailing list on this.
        Hide
        Sandro Martini added a comment -

        Latest version of archetype and a sample of generated application.

        Show
        Sandro Martini added a comment - Latest version of archetype and a sample of generated application.
        Hide
        Sandro Martini added a comment -

        Removed a specific release, because (for its nature) this has to be done (updated) AFTER any Pivot release.

        In future verify if add other archetypes.

        Show
        Sandro Martini added a comment - Removed a specific release, because (for its nature) this has to be done (updated) AFTER any Pivot release. In future verify if add other archetypes.
        Hide
        Sandro Martini added a comment -

        Work note (for me):
        add missing files,
        verify if/where to write that this uses Pivot-2.0,
        verify where to write run/test info (in BUILD, or in README),
        then re-test all, re-create zip (export of its sources, and of the sample generated application), and maybe attach here even a (binary) name-1.0.jar, and a (source) name-src-1.0.jar .

        Verify if this is really needed:
        then, ask to Pivot Developers a vote on it, with some info to test and run, and when all is Ok, publish the artifact in maven main repository (this could require to sign with asc signatures the artifact).
        And tag it into svn ... note that could be done setting SCM info in its pom.xml files, but to avoid problems maybe do this later.

        Show
        Sandro Martini added a comment - Work note (for me): add missing files, verify if/where to write that this uses Pivot-2.0, verify where to write run/test info (in BUILD, or in README), then re-test all, re-create zip (export of its sources, and of the sample generated application), and maybe attach here even a (binary) name-1.0.jar, and a (source) name-src-1.0.jar . Verify if this is really needed: then, ask to Pivot Developers a vote on it, with some info to test and run, and when all is Ok, publish the artifact in maven main repository (this could require to sign with asc signatures the artifact). And tag it into svn ... note that could be done setting SCM info in its pom.xml files, but to avoid problems maybe do this later.
        Hide
        Sandro Martini added a comment -

        Just upload my PGP Public Key (needed to sign maven artifacts, and maybe others ...) to the MIT PGP Server here: http://pgp.mit.edu/
        You can find me as "Sandro Martini - Apache", the other sign for "Sandro Martini" there is mine but not used for signing public artifacts.

        Now some final touch on artifact, and probably tomorrow I'll request for a vote, to release it as 1.0.0 (using Pivot-2.0.0) (and after, tag it in svn).
        When we will release the 2.0.1 final (soon), I'll update it to 1.0.1.

        Show
        Sandro Martini added a comment - Just upload my PGP Public Key (needed to sign maven artifacts, and maybe others ...) to the MIT PGP Server here: http://pgp.mit.edu/ You can find me as "Sandro Martini - Apache", the other sign for "Sandro Martini" there is mine but not used for signing public artifacts. Now some final touch on artifact, and probably tomorrow I'll request for a vote, to release it as 1.0.0 (using Pivot-2.0.0) (and after, tag it in svn). When we will release the 2.0.1 final (soon), I'll update it to 1.0.1.
        Hide
        Sandro Martini added a comment -

        the new archetype, and a sample of gerenated application.
        I hope ready for the 1.0 version.
        All missing files were added, and inside you can find in the BUILD file all the necessary to build and install in a local maven repository the archetype, and to generate a quickstart application (with inside another BUILD file containing commands to build and run).

        Show
        Sandro Martini added a comment - the new archetype, and a sample of gerenated application. I hope ready for the 1.0 version. All missing files were added, and inside you can find in the BUILD file all the necessary to build and install in a local maven repository the archetype, and to generate a quickstart application (with inside another BUILD file containing commands to build and run).
        Show
        Sandro Martini added a comment - Results of first vote on it: http://apache-pivot-developers.417237.n3.nabble.com/VOTE-Release-Pivot-Quickstart-Archetype-1-0-td3371018.html
        Hide
        Sandro Martini added a comment -

        After Pivot release 2.0.1 , I'll update it to 1.0.1 (of course using Pivot 2.0.1 jars) and tag in svn, and maybe post here zip and jar updated.

        Show
        Sandro Martini added a comment - After Pivot release 2.0.1 , I'll update it to 1.0.1 (of course using Pivot 2.0.1 jars) and tag in svn, and maybe post here zip and jar updated.
        Hide
        Sandro Martini added a comment -

        Just put its jar (for the binary release) here:
        code.google.com/a/apache-extras.org/p/pivot-common/downloads/detail?name=pivot-archetype-quickstart-1.0.jar
        with a minimal info on how to install it and use it.

        Show
        Sandro Martini added a comment - Just put its jar (for the binary release) here: code.google.com/a/apache-extras.org/p/pivot-common/downloads/detail?name=pivot-archetype-quickstart-1.0.jar with a minimal info on how to install it and use it.
        Hide
        Sandro Martini added a comment -

        Reopen just to update it for Pivot-2.0.1

        Show
        Sandro Martini added a comment - Reopen just to update it for Pivot-2.0.1
        Hide
        Sandro Martini added a comment -

        The Maven Quickstart archetype, and the generated application, updated to use Pivot-2.0.1

        Show
        Sandro Martini added a comment - The Maven Quickstart archetype, and the generated application, updated to use Pivot-2.0.1
        Hide
        Sandro Martini added a comment -

        Update the archetype to Pivot-2.0.2, and update some plugin inside.

        Show
        Sandro Martini added a comment - Update the archetype to Pivot-2.0.2, and update some plugin inside.
        Hide
        Sandro Martini added a comment -

        The generated application (just generated, and even after add eclipse project files and built).

        Show
        Sandro Martini added a comment - The generated application (just generated, and even after add eclipse project files and built).
        Hide
        Sandro Martini added a comment -

        Update the archetype to Pivot-2.0.4, and update some plugin inside.

        Show
        Sandro Martini added a comment - Update the archetype to Pivot-2.0.4, and update some plugin inside.
        Hide
        Sandro Martini added a comment -

        Update archetype and (generated) test skeleton application to latest.

        Show
        Sandro Martini added a comment - Update archetype and (generated) test skeleton application to latest.

          People

          • Assignee:
            Sandro Martini
            Reporter:
            Sandro Martini
          • Votes:
            2 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development