My favorites | Sign in
Google
       
Details: Show all Hide all

Last 7 days

  • Mar 15, 2010
    issue 10 (objenesis for Debian) Status changed   -   The tag is now set. The sources are already in the bundle.
    Status: Fixed
    The tag is now set. The sources are already in the bundle.
    Status: Fixed
  • Mar 15, 2010
    issue 10 (objenesis for Debian) changed   -  
    Owner: henri.tremblay
    Labels: Type-Task
    Owner: henri.tremblay
    Labels: Type-Task
  • Mar 15, 2010
    r208 ([No log message]) committed   -   [No log message]
    [No log message]

Earlier this year

  • Feb 19, 2010
    r7 (Comment a bit) committed   -   Comment a bit
    Comment a bit
  • Feb 19, 2010
    r6 (Initial version) committed   -   Initial version
    Initial version
  • Feb 16, 2010
    r5 ([No log message]) committed   -   [No log message]
    [No log message]
  • Jan 07, 2010
    r207 (Skip tests for license update) committed   -   Skip tests for license update
    Skip tests for license update
  • Jan 07, 2010
    r206 (Update copyrights to 2010) committed   -   Update copyrights to 2010
    Update copyrights to 2010

Older

  • Dec 31, 2009
    issue 9 (Maven Central maven-metadata.xml does not list all available...) Status changed   -   The versions were added. It should now work correctly.
    Status: Fixed
    The versions were added. It should now work correctly.
    Status: Fixed
  • Dec 15, 2009
    issue 9 (Maven Central maven-metadata.xml does not list all available...) changed   -   You are right. It seems the metadata are synchronized from the Objenesis repository. I didn't know that (and not all versions are in it). I'll check what I can do.
    Status: Accepted
    Owner: henri.tremblay
    Labels: Type-Defect Priority-Medium
    You are right. It seems the metadata are synchronized from the Objenesis repository. I didn't know that (and not all versions are in it). I'll check what I can do.
    Status: Accepted
    Owner: henri.tremblay
    Labels: Type-Defect Priority-Medium
  • Aug 26, 2009
    r205 (Site for version 1.2) committed   -   Site for version 1.2
    Site for version 1.2
  • Aug 26, 2009
    r204 (Change download urls) committed   -   Change download urls
    Change download urls
  • Aug 26, 2009
    objenesis-1.2-bin.zip (Objenesis 1.2 Bundle) file uploaded
  • Aug 26, 2009
    objenesis-tck-1.2.jar (Objenesis 1.2 TCK ) file uploaded
  • Aug 26, 2009
    r203 (Generate bundle with assembly plugin) committed   -   Generate bundle with assembly plugin
    Generate bundle with assembly plugin
  • Aug 26, 2009
    r202 (Fix javadoc links in TCK) committed   -   Fix javadoc links in TCK
    Fix javadoc links in TCK
  • Aug 26, 2009
    r201 (Deliver 1.2 version) committed   -   Deliver 1.2 version
    Deliver 1.2 version
  • Aug 23, 2009
    r200 (Have OSGi be an Objenesis bundle) committed   -   Have OSGi be an Objenesis bundle
    Have OSGi be an Objenesis bundle
  • Aug 23, 2009
    issue 8 (Move to Apache 2.0 license) reported   -   Move to Apache 2.0 license to allow a greater range of users to use Objenesis
    Move to Apache 2.0 license to allow a greater range of users to use Objenesis
  • Aug 23, 2009
    issue 7 (Please OSGi-ify the objenesis jar.) Labels changed   -  
    Labels: Type-Enhancement Priority-Medium Milestone-1.2
    Labels: Type-Enhancement Priority-Medium Milestone-1.2
  • Aug 23, 2009
    issue 7 (Please OSGi-ify the objenesis jar.) Status changed   -  
    Status: Fixed
    Status: Fixed
  • Aug 23, 2009
    r199 (Ignore eclipse_config ) committed   -   Ignore eclipse_config
    Ignore eclipse_config
  • Aug 23, 2009
    r198 (Package as a pom since it's not a jar) committed   -   Package as a pom since it's not a jar
    Package as a pom since it's not a jar
  • Aug 23, 2009
    r197 (Have OSGi be an Objenesis bundle) committed   -   Have OSGi be an Objenesis bundle
    Have OSGi be an Objenesis bundle
  • Jun 28, 2009
    r196 (Configure deploy) committed   -   Configure deploy
    Configure deploy
  • Jun 23, 2009
    HowToBuild Wiki page edited
  • Jun 23, 2009
    r194 (Simplify the build a lot) committed   -   Simplify the build a lot
    Simplify the build a lot
  • Jun 21, 2009
    r193 (Add pmd and findbugs reports) committed   -   Add pmd and findbugs reports
    Add pmd and findbugs reports
  • Jun 21, 2009
    r192 (Catch explicit exceptions instead of generic Exception) committed   -   Catch explicit exceptions instead of generic Exception
    Catch explicit exceptions instead of generic Exception
  • Jun 21, 2009
    r191 (Remove useless final keywords) committed   -   Remove useless final keywords
    Remove useless final keywords
  • Jun 21, 2009
    r190 (Tests for JDK6) committed   -   Tests for JDK6
    Tests for JDK6
  • Jun 21, 2009
    r189 (Talk about maven-shade-plugin) committed   -   Talk about maven-shade-plugin
    Talk about maven-shade-plugin
  • Jun 21, 2009
    r188 (Be compliant with xsite-maven-plugin 1.0, specify encoding i...) committed   -   Be compliant with xsite-maven-plugin 1.0, specify encoding in Eclipse, use copy-resources instead of antrun
    Be compliant with xsite-maven-plugin 1.0, specify encoding in Eclipse, use copy-resources instead of antrun
  • Jun 21, 2009
    r187 (Move to Apache 2 license) committed   -   Move to Apache 2 license
    Move to Apache 2 license
  • Jun 21, 2009
    HowToBuild Wiki page edited
  • Jun 21, 2009
    r185 (Add Apache 2 license to files) committed   -   Add Apache 2 license to files
    Add Apache 2 license to files
  • Jun 21, 2009
    r184 (Duplicate of root license) committed   -   Duplicate of root license
    Duplicate of root license
  • Jun 17, 2009
    r183 (Add Apache 2 license to files) committed   -   Add Apache 2 license to files
    Add Apache 2 license to files
  • Jun 17, 2009
    r182 (Add author anywhere it's missing) committed   -   Add author anywhere it's missing
    Add author anywhere it's missing
  • Jun 17, 2009
    r181 (Add apache license) committed   -   Add apache license
    Add apache license
  • Jun 13, 2009
    issue 7 (Please OSGi-ify the objenesis jar.) commented on   -   Thanks a lot for your answers. I've been able to OSGified EasyMock and to test it with the Spring bundle test framework. I'll do the same thing for Objenesis. One thing I'm not sure about is the JVM inner implementation packages. To answer your question, yes, Objenesis is using a lot of JVM inner packages like com.sun, COM.jrockit and COM.newmonics. That's why it appears. But I don't think it should be an issue with OSGi since there are low enough in the class loading. I'll tell you how it goes.
    Thanks a lot for your answers. I've been able to OSGified EasyMock and to test it with the Spring bundle test framework. I'll do the same thing for Objenesis. One thing I'm not sure about is the JVM inner implementation packages. To answer your question, yes, Objenesis is using a lot of JVM inner packages like com.sun, COM.jrockit and COM.newmonics. That's why it appears. But I don't think it should be an issue with OSGi since there are low enough in the class loading. I'll tell you how it goes.
  • Jun 06, 2009
    r180 (Add serialVersionUIDs to make Eclipse compiler happy) committed   -   Add serialVersionUIDs to make Eclipse compiler happy
    Add serialVersionUIDs to make Eclipse compiler happy
  • Jun 06, 2009
    r179 (Upgrade dependencies and plugins versions) committed   -   Upgrade dependencies and plugins versions
    Upgrade dependencies and plugins versions
  • Apr 12, 2009
    issue 7 (Please OSGi-ify the objenesis jar.) commented on   -   I read the best practice to know a little more what I was doing. Then I tried maven-bundle-plugin. Version 2.0.0. Using the manifest goal which seems to be what I want. The results is below and now my comments/questions: * Will only exported package be accessible to others? What happens when compiling with a jar/bundle that then do not expose the package used? NoClassDefFoundError? * I'm asking this because I'm wondering if I should hide Objenesis inner implementation. Most users won't need it but some power users might. * I need to import my own packages to be able to "use" them in the export part? * If there's some dynamic use between packages, should I trace them and add them? * all the "Bundle-***" seems fine * In the import section, aonic and jrockit packages are JVM implementations. I guess I need to remove them? * I don't understand why the import section is referencing version 1.1 of objenesis (1.1.1-SNAPSHOT is the currently bundled version) -------------------------------------------------------------------------- Export-Package: org.objenesis;uses:="org.objenesis.instantiator,org.ob jenesis.strategy";version="1.1.1.SNAPSHOT",org.objenesis.instantiator ;version="1.1.1.SNAPSHOT",org.objenesis.instantiator.basic;uses:="org .objenesis,org.objenesis.instantiator";version="1.1.1.SNAPSHOT",org.o bjenesis.instantiator.gcj;uses:="org.objenesis,org.objenesis.instanti ator";version="1.1.1.SNAPSHOT",org.objenesis.instantiator.jrockit;use s:="COM.jrockit.reflect,org.objenesis,org.objenesis.instantiator,jroc kit.vm";version="1.1.1.SNAPSHOT",org.objenesis.instantiator.perc;uses :="org.objenesis,org.objenesis.instantiator,COM.newmonics.PercClassLo ader";version="1.1.1.SNAPSHOT",org.objenesis.instantiator.sun;uses:=" org.objenesis,org.objenesis.instantiator,sun.reflect";version="1.1.1. SNAPSHOT",org.objenesis.strategy;uses:="org.objenesis.instantiator,or g.objenesis.instantiator.perc,org.objenesis,org.objenesis.instantiato r.basic,org.objenesis.instantiator.gcj,org.objenesis.instantiator.sun ,org.objenesis.instantiator.jrockit";version="1.1.1.SNAPSHOT" Bundle-Version: 1.1.1.SNAPSHOT Tool: Bnd-0.0.311 Bundle-Name: Objenesis Bnd-LastModified: 1239409710046 Bundle-ManifestVersion: 2 Bundle-License: http://www.opensource.org/licenses/mit-license.php Bundle-Description: A library for instantiating Java objects Bundle-SymbolicName: org.objenesis Import-Package: COM.jrockit.reflect,COM.newmonics.PercClassLoader,jroc kit.vm,org.objenesis;version="1.1",org.objenesis.instantiator;version ="1.1",org.objenesis.instantiator.basic;version="1.1",org.objenesis.i nstantiator.gcj;version="1.1",org.objenesis.instantiator.jrockit;vers ion="1.1",org.objenesis.instantiator.perc;version="1.1",org.objenesis .instantiator.sun;version="1.1",org.objenesis.strategy;version="1.1", sun.reflect
    I read the best practice to know a little more what I was doing. Then I tried maven-bundle-plugin. Version 2.0.0. Using the manifest goal which seems to be what I want. The results is below and now my comments/questions: * Will only exported package be accessible to others? What happens when compiling with a jar/bundle that then do not expose the package used? NoClassDefFoundError? * I'm asking this because I'm wondering if I should hide Objenesis inner implementation. Most users won't need it but some power users might. * I need to import my own packages to be able to "use" them in the export part? * If there's some dynamic use between packages, should I trace them and add them? * all the "Bundle-***" seems fine * In the import section, aonic and jrockit packages are JVM implementations. I guess I need to remove them? * I don't understand why the import section is referencing version 1.1 of objenesis (1.1.1-SNAPSHOT is the currently bundled version) -------------------------------------------------------------------------- Export-Package: org.objenesis;uses:="org.objenesis.instantiator,org.ob jenesis.strategy";version="1.1.1.SNAPSHOT",org.objenesis.instantiator ;version="1.1.1.SNAPSHOT",org.objenesis.instantiator.basic;uses:="org .objenesis,org.objenesis.instantiator";version="1.1.1.SNAPSHOT",org.o bjenesis.instantiator.gcj;uses:="org.objenesis,org.objenesis.instanti ator";version="1.1.1.SNAPSHOT",org.objenesis.instantiator.jrockit;use s:="COM.jrockit.reflect,org.objenesis,org.objenesis.instantiator,jroc kit.vm";version="1.1.1.SNAPSHOT",org.objenesis.instantiator.perc;uses :="org.objenesis,org.objenesis.instantiator,COM.newmonics.PercClassLo ader";version="1.1.1.SNAPSHOT",org.objenesis.instantiator.sun;uses:=" org.objenesis,org.objenesis.instantiator,sun.reflect";version="1.1.1. SNAPSHOT",org.objenesis.strategy;uses:="org.objenesis.instantiator,or g.objenesis.instantiator.perc,org.objenesis,org.objenesis.instantiato r.basic,org.objenesis.instantiator.gcj,org.objenesis.instantiator.sun ,org.objenesis.instantiator.jrockit";version="1.1.1.SNAPSHOT" Bundle-Version: 1.1.1.SNAPSHOT Tool: Bnd-0.0.311 Bundle-Name: Objenesis Bnd-LastModified: 1239409710046 Bundle-ManifestVersion: 2 Bundle-License: http://www.opensource.org/licenses/mit-license.php Bundle-Description: A library for instantiating Java objects Bundle-SymbolicName: org.objenesis Import-Package: COM.jrockit.reflect,COM.newmonics.PercClassLoader,jroc kit.vm,org.objenesis;version="1.1",org.objenesis.instantiator;version ="1.1",org.objenesis.instantiator.basic;version="1.1",org.objenesis.i nstantiator.gcj;version="1.1",org.objenesis.instantiator.jrockit;vers ion="1.1",org.objenesis.instantiator.perc;version="1.1",org.objenesis .instantiator.sun;version="1.1",org.objenesis.strategy;version="1.1", sun.reflect
  • Apr 10, 2009
    ListOfCurrentlySupportedVMs Wiki page edited
  • Apr 08, 2009
    issue 7 (Please OSGi-ify the objenesis jar.) Status changed   -   Should be done soon. I'll see how the plugin goes. Can you give me the expected result? I'm not using OSGi right now and don't know how to test my result. I'm assuming it should be something like this thought. Export-Package: org.objenesis;version="1.1.0";uses:="org.objenesis.ins tantiator,org.objenesis.strategy",org.objenesis.instantiator;version= "1.1.0",org.objenesis.instantiator.basic;version="1.1.0",org.objenesi s.instantiator.gcj;version="1.1.0",org.objenesis.instantiator.jrockit ;version="1.1.0",org.objenesis.instantiator.sun;version="1.0.0",org.o bjenesis.strategy;version="1.1.0";uses:="org.objenesis.instantiator" Bundle-Vendor: Objenesis Bundle-Classpath: . Bundle-Version: 1.1.0 Bundle-Name: Objenesis Bundle-ManifestVersion: 2 Bundle-SymbolicName: org.objenesis
    Status: Accepted
    Should be done soon. I'll see how the plugin goes. Can you give me the expected result? I'm not using OSGi right now and don't know how to test my result. I'm assuming it should be something like this thought. Export-Package: org.objenesis;version="1.1.0";uses:="org.objenesis.ins tantiator,org.objenesis.strategy",org.objenesis.instantiator;version= "1.1.0",org.objenesis.instantiator.basic;version="1.1.0",org.objenesi s.instantiator.gcj;version="1.1.0",org.objenesis.instantiator.jrockit ;version="1.1.0",org.objenesis.instantiator.sun;version="1.0.0",org.o bjenesis.strategy;version="1.1.0";uses:="org.objenesis.instantiator" Bundle-Vendor: Objenesis Bundle-Classpath: . Bundle-Version: 1.1.0 Bundle-Name: Objenesis Bundle-ManifestVersion: 2 Bundle-SymbolicName: org.objenesis
    Status: Accepted
  • Dec 27, 2008
    issue 6 (Portable Unsafe) Labels changed   -  
    Labels: Type-Enhancement
    Labels: Type-Enhancement
  • Dec 27, 2008
    issue 5 (Testing objenesis with JamVM) Labels changed   -  
    Labels: Type-Enhancement Type-Defect
    Labels: Type-Enhancement Type-Defect
  • Dec 27, 2008
    issue 6 (Portable Unsafe) commented on   -   That could be an idea. Objenesis was originally created to solve only the instantiation issue but why not expand it. The sad thing is that Unsafe contains lots of methods. Making them work on every platform seems like a huge job. But let's see. Maybe not.
    That could be an idea. Objenesis was originally created to solve only the instantiation issue but why not expand it. The sad thing is that Unsafe contains lots of methods. Making them work on every platform seems like a huge job. But let's see. Maybe not.
 
Powered by Google Project Hosting