Mojo
  1. Mojo
  2. MOJO-912

Plugin submission: maven-jflex-plugin

    Details

    • Type: New Feature New Feature
    • Status: Closed Closed
    • Priority: Major Major
    • Resolution: Won't Fix
    • Affects Version/s: None
    • Fix Version/s: None
    • Component/s: _Plugin Submission
    • Labels:
      None
    • Complexity:
      Intermediate
    • Number of attachments :
      0

      Description

      This is a plugin to run JFlex.

      JFlex is a lexical analyzer generator. It is similar to JLex, antlr, lex/yacc. JFlex has rencently been uploaded to codehaus repository (MAVENUPLOAD-1641) and I think having the related plugin would be useful to others.

        Issue Links

          Activity

          Hide
          Régis Décamps added a comment - - edited

          The source code is available on https://jflex.svn.sourceforge.net/svnroot/jflex/trunk/maven-jflex-plugin

          This plugin submission has already been discussed on the mojo-dev ML: http://archive.mojo.codehaus.org/dev/002e01c7dea0%24d8ce2270%24bb195dd4%40lan

          Show
          Régis Décamps added a comment - - edited The source code is available on https://jflex.svn.sourceforge.net/svnroot/jflex/trunk/maven-jflex-plugin This plugin submission has already been discussed on the mojo-dev ML: http://archive.mojo.codehaus.org/dev/002e01c7dea0%24d8ce2270%24bb195dd4%40lan
          Hide
          Régis Décamps added a comment -
          Show
          Régis Décamps added a comment - The site is now online. http://jflex.sourceforge.net/maven-jflex-plugin/usage.html
          Hide
          Subhash Chandran added a comment -

          I am a contributer to the JSyntaxPane ( http://jsyntaxpane.googlecode.com/ ) project which uses the Maven JFlex plugin to build. We are unable to upload JSyntaxPane to Maven public repository because this dependency is hosted in a different repository.

          Please accept this as part of the Mojo project, it will be very useful for us.

          Show
          Subhash Chandran added a comment - I am a contributer to the JSyntaxPane ( http://jsyntaxpane.googlecode.com/ ) project which uses the Maven JFlex plugin to build. We are unable to upload JSyntaxPane to Maven public repository because this dependency is hosted in a different repository. Please accept this as part of the Mojo project, it will be very useful for us.
          Hide
          Benjamin Bentmann added a comment -

          The code is currently licensed under the GPL which is not acceptable for Codehaus projects (compare Licenses). I have contacted the author to see if he is willing to change it. If this go well, I would try to incubate the plugin into the sandbox and hopefully not too long after this, do a release.

          Show
          Benjamin Bentmann added a comment - The code is currently licensed under the GPL which is not acceptable for Codehaus projects (compare Licenses ). I have contacted the author to see if he is willing to change it. If this go well, I would try to incubate the plugin into the sandbox and hopefully not too long after this, do a release.
          Hide
          Herve Boutemy added a comment -

          If there is a problem to add this plugin to Codehaus, why not simply upload the artifact to central repo?
          Just follow the doc here

          Show
          Herve Boutemy added a comment - If there is a problem to add this plugin to Codehaus, why not simply upload the artifact to central repo? Just follow the doc here
          Hide
          Subhash Chandran added a comment - - edited

          The discussion on this is going on in the JFlex mailing list. Hopefully, before next weekend, we would come to a conclusion.

          Show
          Subhash Chandran added a comment - - edited The discussion on this is going on in the JFlex mailing list. Hopefully, before next weekend, we would come to a conclusion.
          Hide
          Dan Tran added a comment -

          I think the plugin should stay with jfex to get proper attention.

          Show
          Dan Tran added a comment - I think the plugin should stay with jfex to get proper attention.
          Hide
          Herve Boutemy added a comment -

          so do I: jflex already has its repo, for its Maven plugin but JFlex core too. A simple sync is necessary like it is done with many artifacts hosted on SourceForge

          Régis: you just have to read Sync'ing your own repository to the central repository automatically section of the Guide to uploading artifacts to the Central Repository.
          Then open a Jira issue and the sync will be done for everything under de.jflex)

          Show
          Herve Boutemy added a comment - so do I: jflex already has its repo , for its Maven plugin but JFlex core too. A simple sync is necessary like it is done with many artifacts hosted on SourceForge Régis: you just have to read Sync'ing your own repository to the central repository automatically section of the Guide to uploading artifacts to the Central Repository . Then open a Jira issue and the sync will be done for everything under de.jflex )
          Hide
          Subhash Chandran added a comment -

          Régis: If you plan to sync the repo, here are the details:

          "de.jflex.maven.plugin","jflex@shell.sourceforge.net:/TODO/SSH/INFO","rsync_ssh","Régis Décamps","decamps@users.sf.net"

          [Just change the second CSV value to reflect the correct path.]

          Then open an issue here:

          http://jira.codehaus.org/secure/CreateIssue.jspa?pid=10367&issuetype=5

          Show
          Subhash Chandran added a comment - Régis: If you plan to sync the repo, here are the details: "de.jflex.maven.plugin","jflex@shell.sourceforge.net:/TODO/SSH/INFO","rsync_ssh","Régis Décamps","decamps@users.sf.net" [Just change the second CSV value to reflect the correct path.] Then open an issue here: http://jira.codehaus.org/secure/CreateIssue.jspa?pid=10367&issuetype=5
          Hide
          Herve Boutemy added a comment - - edited

          IMHO, having sync for JFlex plugin only (groupId de.jlfex.maven.plugin) is not a good idea.
          Better have a full JFlex sync repo (groupId de.jflex), that will contain JFlex core (de.jflex:jflex) and JFlex Maven Plugin (de.jflex.maven.plugin:maven-jflex-plugin)

          The sync line would be:
          "de.jflex","mavensync@shell.sourceforge.net:/home/groups/j/jf/jflex/htdocs/repo","rsync_ssh","Régis Décamps","decamps@users.sf.net",,

          That said, I think the plugin's groupId shoud be changed from de.jflex.maven.plugin to simply de.jflex: de.jflex:maven-jflex-plugin is simpler and sufficient.

          Show
          Herve Boutemy added a comment - - edited IMHO, having sync for JFlex plugin only (groupId de.jlfex.maven.plugin ) is not a good idea. Better have a full JFlex sync repo (groupId de.jflex ), that will contain JFlex core ( de.jflex:jflex ) and JFlex Maven Plugin ( de.jflex.maven.plugin:maven-jflex-plugin ) The sync line would be: "de.jflex","mavensync@shell.sourceforge.net:/home/groups/j/jf/jflex/htdocs/repo","rsync_ssh","Régis Décamps","decamps@users.sf.net",, That said, I think the plugin's groupId shoud be changed from de.jflex.maven.plugin to simply de.jflex : de.jflex:maven-jflex-plugin is simpler and sufficient.
          Hide
          Régis Décamps added a comment -
          • I am the author of the plugin (with the help of Benjamin) but Gerwin Klein is the author of Jflex and owner of the Flex project
          • I see the user mavensync exists on sourceforge. A user with a shell access has read only access on the Jflex maven repo. I think the sync line given by Hervé is enough for the repo to be synchronized
          • I am OK with changing the groupid of the plugin. But, this probably implies a new version to be released in a clean new repository)
          • Hervé: are there any coding guidelines for being in the cenrtal repo? In particular, what about Java 1.4 vs Java 5
          Show
          Régis Décamps added a comment - I am the author of the plugin (with the help of Benjamin) but Gerwin Klein is the author of Jflex and owner of the Flex project I see the user mavensync exists on sourceforge. A user with a shell access has read only access on the Jflex maven repo. I think the sync line given by Hervé is enough for the repo to be synchronized I am OK with changing the groupid of the plugin. But, this probably implies a new version to be released in a clean new repository) Hervé: are there any coding guidelines for being in the cenrtal repo? In particular, what about Java 1.4 vs Java 5
          Hide
          Benjamin Bentmann added a comment -

          are there any coding guidelines for being in the cenrtal repo? In particular, what about Java 1.4 vs Java 5

          You can use whatever Java version you like, this is not a requirement for upload/sync to central.

          Show
          Benjamin Bentmann added a comment - are there any coding guidelines for being in the cenrtal repo? In particular, what about Java 1.4 vs Java 5 You can use whatever Java version you like, this is not a requirement for upload/sync to central.
          Hide
          Subhash Chandran added a comment -

          > I am OK with changing the groupid of the plugin. But, this probably implies a new version to be released in a clean new repository)

          I believe, changing the group id and making a release in a clean repository is worth the effort

          (And I am waiting for this to happen, so that I will be able to release a version of JSyntaxPane and finally RESTClient--which depends on JSyntaxPane).

          Show
          Subhash Chandran added a comment - > I am OK with changing the groupid of the plugin. But, this probably implies a new version to be released in a clean new repository) I believe, changing the group id and making a release in a clean repository is worth the effort (And I am waiting for this to happen, so that I will be able to release a version of JSyntaxPane and finally RESTClient--which depends on JSyntaxPane).
          Hide
          Gin-Ting Chen added a comment -

          Any progress on this?
          It seems that http://jflex.sourceforge.net/repo/ is down and although I can build this and deploy it to my own repo it would be nice to have it on central.

          Show
          Gin-Ting Chen added a comment - Any progress on this? It seems that http://jflex.sourceforge.net/repo/ is down and although I can build this and deploy it to my own repo it would be nice to have it on central.
          Hide
          Régis Décamps added a comment -

          The repository is not browsable any more because as of 2008-10-23 directory index display has been disabled by sourceforge.

          I have renamed the plugin groupId from de.jflex.mave.plugin to de.jflex, as suggested by Hervé

          Hence, I have rebuild a new repository http://jflex.sourceforge.net/m2repo/

          I have asked for repository synchronization in MAVENUPLOAD-2285

          Sorry for having you wait for so long

          Show
          Régis Décamps added a comment - The repository is not browsable any more because as of 2008-10-23 directory index display has been disabled by sourceforge. I have renamed the plugin groupId from de.jflex.mave.plugin to de.jflex, as suggested by Hervé Hence, I have rebuild a new repository http://jflex.sourceforge.net/m2repo/ I have asked for repository synchronization in MAVENUPLOAD-2285 Sorry for having you wait for so long
          Hide
          Régis Décamps added a comment -

          synchronization on central repo instead http://jira.codehaus.org/browse/MAVENUPLOAD-2285

          Show
          Régis Décamps added a comment - synchronization on central repo instead http://jira.codehaus.org/browse/MAVENUPLOAD-2285

            People

            • Assignee:
              Unassigned
              Reporter:
              Régis Décamps
            • Votes:
              4 Vote for this issue
              Watchers:
              4 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: