Re: [cf-dev] 1.0.0-M2

[Julien Vermillard <jvermillard@xxxxxxxxx>]

Go for M2 :) just skip the tools M1

The javadoc was really broken, I fixed a bunch of @link erorrs and unescapted >,< ,& chars which prevented maven to produce the javadoc jars.

There is still a lot of warning to fix. Try "mvn install -Prelease" on some of the projects :)

I suppose you don't use the same version? I'm using maven 3.1.0

--
Julien Vermillard :::: http://people.apache.org/~jvermillard/

On Fri, Oct 10, 2014 at 9:02 PM, Kovatsch Matthias <kovatsch@xxxxxxxxxxx> wrote:

I managed to have the credentials for pushing on mavne central for org.eclipse.californium (Matthias you should have it allso).

 

I did not receive any notification, but org.eclipse.californium appears in the staging profiles. Should be good.

 

So I'm up for releasing a M2, with writing the documentation and following the proper maven central process (javadoc jar, gpg signatures..).

 

JavaDoc should be quite in good shape since I fixed the stuff for the final ch.ethz release.

 

Since it's already quite complex to release all the repository at the same time, I propose we always release *all* the californium sub-project at the same time.

So we keep the version number in sync (Cf M2 depends on Sc M2 which depends on EC M2, etc..)

 

Sounds good! Should I fix californium.tools before the the 15^th and catch up with M1 or do we simply go directly for M2?

_______________________________________________
cf-dev mailing list
cf-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/cf-dev