Plugin submission: maven-jflex-plugin

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

The site is now online.
http://jflex.sourceforge.net/maven-jflex-plugin/usage.html

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.

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.

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

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

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

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)

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

• 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

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.

> 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).

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.

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

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