Hi Sandro, I've changed the package and added the copyright header to the sources. I've got a Gradle build for this project so it's easiest to have the dependencies come from maven central so when or if this jar is published the external dependencies are ok in the pom.
Created https://issues.apache.org/jira/browse/PIVOT-904 for this. Kr, Tom On 22 April 2013 17:27, Tom Eyckmans <[email protected]> wrote: > Hi Sandro, > > My google account name is [email protected], I'll make the needed > changes. > > Kr, > > Tom > > > On 19 April 2013 14:46, Sandro Martini <[email protected]> wrote: > >> Hi Tom, >> I think that we can proceed in two steps: >> >> 1 - send me your google account name (if different from current email) so >> I can grant to you committer rights into pivot-contrib, then create there >> (under trunk) a Java project with your classes (and maybe all related >> libraries, etc). >> Remember only to change your package to something like >> pivot_contrib.<your-project-name>, and if possible, attach the license >> header in any source file (like in Pivot). Of course I can help you to >> review the project and sources one time published there (if it's ok for >> you) ... remember only to checkout the trunk in https or you will not be >> able to commit :-) : >> https://code.google.com/a/apache-extras.org/p/pivot-contrib/ >> Put any doc/wiki as you want there ... >> Note that for dependencies on Pivot libraries I suggest to depend on the >> project pivot2-dependencies from its trunk ( >> https://code.google.com/a/apache-extras.org/p/pivot-common/ ) and >> download in the same workspace, or use maven (but at the moment Pivot jars >> for 2.0.3 aren't published, until we have a successful vote for that >> release). But I can do this "cleanup" later. >> Last, I suggest a build script in root on your project (ant or maven, or >> maybe even gradle or sbt) to generate a jar for your project. >> >> 2 (for mid/long-term) - you can add a new JIRA issue ( >> https://issues.apache.org/jira/browse/PIVOT ) targeted for 2.1 release >> and attach there the code, or link to existing code under pivot-contrib. >> Don't worry on details, I can help/fix things there after you post/write >> something there. >> After this we can discuss if/how/when to integrate in core Pivot, and see >> what others think. There is always the problem of external dependencies >> etc, but we have more time for all this stuff. >> >> Tell me if it's ok, and of course if you need info/help ask to us. >> Thanks for now. >> >> Bye, >> Sandro >> >> >> >> 2013/4/18 teyckmans <[email protected]> >> >>> Hi Sandro, >>> >>> I'm happy to go with the option that you think is best. What is your >>> prefference? >>> >>> Kind regards, >>> >>> Tom >>> >>> >>> >>> -- >>> View this message in context: >>> http://apache-pivot-users.399431.n3.nabble.com/Guice-integration-for-apache-pivot-tp4022557p4022572.html >>> Sent from the Apache Pivot - Users mailing list archive at Nabble.com. >>> >> >> >
