New Version Creation

[GoogleCodeExporter]

Before uploading to the Maven public repository, it would be good to have a
new version released. There has been some changes in the code since last
release.

The version numbering scheme also needs to change. Having the date as
versioning detail is convenient from the developer perspective, but from
the user perspective difficult to remember. Also some OpenSource software
which had this type of naming are ordered wrongly in the MVNRepository
search page. For example:

http://www.mvnrepository.com/artifact/commons-pool/commons-pool

Older version files are shown in the top, which might tempt unwary users to
include that instead of the latest stable version.

So what is the best version? Well, this has to be just thought out. My
personal preference would be something like 0.8.0. This indicates it is a
fairly stable product which has not yet reached 1.0 release.

Once you let me know the version number, I can create that version, tag it,
and open an issue to upload to the Maven public repository.

Original issue reported on code.google.com by subwiz on 7 Aug 2008 at 8:41

[GoogleCodeExporter]

I agree about changing the version number scheme.  I actually did not think this
project will be popular at all!  So, it is best to stick with the standard 
dotted
formats.  

However i think we have reached a pretty stable, and almost feature complete 
stage,
to what i initially envisioned for the project.  So it is very close to the 1.0
stage.  The other Enhancement issues should wait for a 1.5 or a 2.0 release.

Therefore I think we can use a 1.0.0 or a 0.9.0.  

When that is done, we also need to add a binary download that includes the 
tester. 
What I generally do NOT like about many software is that it takes some effort 
to just
see what it can do.  I like to see something before even attempting to compile, 
and
the tester binary jar download does exactly that.

I hope to get back on this in about a week time when I finally get a PC and 
some free
time.  

Many thanks for taking the time to work on this.

Original comment by ayman.al...@gmail.com on 8 Aug 2008 at 9:21

[GoogleCodeExporter]

> I actually did not think this project will be popular at all!

Well, it is one of the best pieces of OpenSource software to come out! I have 
been
waiting for such a component for such a long time :-) (yes, more than 4 years 
now,
since I wrote my first text editor).

> Therefore I think we can use a 1.0.0 or a 0.9.0.

Then I will tag the current code line as 0.9.0 (yeah, I am a bit conservative 
type)

Probably for 1.0.0 we can have extensions architecture where people can write 
their
own JFlex parsers for their own syntax types and register it with JSyntaxPane.

> When that is done, we also need to add a binary download that includes the 
tester.

Brilliant idea. Never striked me. In fact I provide dynamic changing of Syntax
highlighting in RESTClient--I can possibly add a class for doing this in the 
main
line itself. It is a very tiny class infact, and adding a separate Jar for it 
might
not be needed (but you take the final call).

> I hope to get back on this in about a week time when I finally get a PC and 
some
free time.

Eager to see you back in action :-)

Original comment by subwiz on 8 Aug 2008 at 12:23

[GoogleCodeExporter]

A more complete story of my wait is in my blog:

http://jroller.com/jcraze/entry/jsyntaxpane_syntax_highlighting_component_for

Original comment by subwiz on 8 Aug 2008 at 12:47

[GoogleCodeExporter]

Glad the wait is over :-) case closed?

Original comment by ayman.al...@gmail.com on 11 Aug 2008 at 6:29

• Changed state: Fixed

[GoogleCodeExporter]

Not yet! When we make a new release, it will be closed.

Original comment by subwiz on 12 Aug 2008 at 4:12

• Changed state: Accepted

[GoogleCodeExporter]

Release 0.9.0 binary added as binary.  

Original comment by ayman.al...@gmail.com on 21 Sep 2008 at 12:28

• Changed state: Fixed