Log4j 2
  1. Log4j 2
  2. LOG4J2-345

logging.log4j-1.2-api doesn't export the log4j API 1.2. Dependent bundles can not be resolved.

    Details

      Description

      Hi all Log4j/OSGi experts!

      Yesterday I started to migrate from log4j to log4j2. I replaced all Log4j 1.x bundles with log4j-1.2-api as described here: http://logging.apache.org/log4j/2.x/log4j-1.2-api/index.html

      But I got following error:

      Unresolved constraint in bundle MyBundle [21]: Unable to resolve 21.0: missing requirement [21.0] osgi.wiring.package; (&(osgi.wiring.package=org.apache.log4j)(version>=1.2.0)(!(version>=2.0.0)))

      so...I checked the capabilities of the log4j-1.2-api bundle:

      g! inspect cap * 11
      org.apache.logging.log4j-1.2-api [11] provides:
      -----------------------------------------------
      osgi.wiring.bundle; org.apache.logging.log4j-1.2-api 2.0.0.beta8 [UNUSED]
      osgi.wiring.host; org.apache.logging.log4j-1.2-api 2.0.0.beta8 [UNUSED]

      As you can see logging.log4j-1.2-api doesn't export the log4j API 1.2. It still requires log4j 1.2. All dependent bundles can not be resolved until I add the old log4j.jar.

      The maven-bundle-plugin does not export the packages.

      Roland

      1. 0001-Add-log4j-1.x-OSGi-bundle.patch
        5 kB
        Matt Sicker
      2. log4j2-345-patch-issue.png
        94 kB
        Remko Popma
      3. log4j2 1.2api.patch
        2 kB
        Roland Weiglhofer

        Activity

        Hide
        Matt Sicker added a comment -

        Fixed this recently with the OSGi bundles clean-ups going on.

        Show
        Matt Sicker added a comment - Fixed this recently with the OSGi bundles clean-ups going on.
        Hide
        Remko Popma added a comment -

        Re-opening this issue as the fix seems incomplete/incorrect:

        the OSGi bin archive for RC1 does not include a log4j-1.2-osgi-api-2.0-rc1.jar...

        but it does have jar files for all other submodules of log4j-osgi:
        log4j-core-osgi-async-2.0-rc1.jar
        log4j-core-osgi-jpa-2.0-rc1.jar
        log4j-core-osgi-net-2.0-rc1.jar
        log4j-core-osgi-nosql-couchdb-2.0-rc1.jar
        log4j-core-osgi-nosql-mongodb-2.0-rc1.jar
        log4j-core-osgi-reduced-2.0-rc1.jar

        I wonder what went wrong...

        Show
        Remko Popma added a comment - Re-opening this issue as the fix seems incomplete/incorrect: the OSGi bin archive for RC1 does not include a log4j-1.2-osgi-api-2.0-rc1.jar ... but it does have jar files for all other submodules of log4j-osgi: log4j-core-osgi-async-2.0-rc1.jar log4j-core-osgi-jpa-2.0-rc1.jar log4j-core-osgi-net-2.0-rc1.jar log4j-core-osgi-nosql-couchdb-2.0-rc1.jar log4j-core-osgi-nosql-mongodb-2.0-rc1.jar log4j-core-osgi-reduced-2.0-rc1.jar I wonder what went wrong...
        Hide
        Remko Popma added a comment - - edited

        They are all submodules of the log4j-osgi module.
        And the artifact Ids do start with "log4j-", so the resulting jar files start with "log4j-".

        Show
        Remko Popma added a comment - - edited They are all submodules of the log4j-osgi module. And the artifact Ids do start with "log4j-", so the resulting jar files start with "log4j-".
        Hide
        Gary Gregory added a comment -

        Why don't all the names start with "log4j"?

        Show
        Gary Gregory added a comment - Why don't all the names start with "log4j"?
        Hide
        Remko Popma added a comment -

        Ah! Oops. Good point. The log4j-1.2-api is not core... (I missed that, sorry.)

        Perhaps we should change the osgi module names to start with osgi:
        core-osgi-async -> osgi-core-async
        core-osgi-jpa -> osgi-core-jpa
        core-osgi-net -> osgi-core-net
        ...

        Then the non-core modules would have "osgi-noncore" names:
        core-osgi-legacy-api (my mistake) -> osgi-1.2-api (or osgi-legacy-api)
        (and, for example) -> osgi-jcl
        (and, for example) -> osgi-slf4j-impl
        (and, for example) -> osgi-taglib-submodule1
        (and, for example) -> osgi-taglib-submodule2
        ...

        Show
        Remko Popma added a comment - Ah! Oops. Good point. The log4j-1.2-api is not core... (I missed that, sorry.) Perhaps we should change the osgi module names to start with osgi: core-osgi-async -> osgi-core-async core-osgi-jpa -> osgi-core-jpa core-osgi-net -> osgi-core-net ... Then the non-core modules would have "osgi-noncore" names: core-osgi-legacy-api (my mistake) -> osgi-1.2-api (or osgi-legacy-api) (and, for example) -> osgi-jcl (and, for example) -> osgi-slf4j-impl (and, for example) -> osgi-taglib-submodule1 (and, for example) -> osgi-taglib-submodule2 ...
        Hide
        Matt Sicker added a comment -

        Looks good. I didn't know how to go about naming the artifact because all the others were core bundles.

        Show
        Matt Sicker added a comment - Looks good. I didn't know how to go about naming the artifact because all the others were core bundles.
        Hide
        Remko Popma added a comment - - edited

        One more thing about naming: I noticed that the submodules in the log4j-osgi module all seem to use a naming convention for their artifact Id. Should the new legacy-api do something similar (use artifact Id=log4j-core-osgi-legacy-api ?) I like the version number log4j-1.2 in the artifact Id though; makes it clear which legacy we are talking about...

        Would module name core-osgi-log4j-1.2-legacy-api be too long?

        module artifact Id
        core-osgi-async log4j-core-osgi-async
        core-osgi-jpa log4j-core-osgi-jpa
        core-osgi-legacy-api log4j-1.2-osgi-api
        core-osgi-net log4j-core-osgi-net
        core-osgi-nosql-couch log4j-core-osgi-nosql-couch
        core-osgi-nosql-mongo log4j-core-osgi-nosql-mongo
        core-osgi-reduced log4j-core-osgi-reduced
        Show
        Remko Popma added a comment - - edited One more thing about naming: I noticed that the submodules in the log4j-osgi module all seem to use a naming convention for their artifact Id. Should the new legacy-api do something similar (use artifact Id=log4j-core-osgi-legacy-api ?) I like the version number log4j-1.2 in the artifact Id though; makes it clear which legacy we are talking about... Would module name core-osgi-log4j-1.2-legacy-api be too long? module artifact Id core-osgi-async log4j-core-osgi-async core-osgi-jpa log4j-core-osgi-jpa core-osgi-legacy-api log4j-1.2-osgi-api core-osgi-net log4j-core-osgi-net core-osgi-nosql-couch log4j-core-osgi-nosql-couch core-osgi-nosql-mongo log4j-core-osgi-nosql-mongo core-osgi-reduced log4j-core-osgi-reduced
        Hide
        Remko Popma added a comment -

        Thanks Gary. I actually tried that before but gave up when I still got a red error mark... I tried again just now and it turns out that I can ignore this error and forcing ahead does the trick!

        Matt, I renamed the module from "legacy-osgi-api" to "core-osgi-legacy-api" to be consistent with the existing modules. Hope that is okay, let me know if that messes things up.

        Fixed in revision 1564289.
        Please verify and close.

        Show
        Remko Popma added a comment - Thanks Gary. I actually tried that before but gave up when I still got a red error mark... I tried again just now and it turns out that I can ignore this error and forcing ahead does the trick! Matt, I renamed the module from "legacy-osgi-api" to "core-osgi-legacy-api" to be consistent with the existing modules. Hope that is okay, let me know if that messes things up. Fixed in revision 1564289. Please verify and close.
        Hide
        Gary Gregory added a comment -

        Remko Popma In the Eclipse apply patch wizard, don't forget to set the "Ignore leading path elements" value to 1. This usually deals with the "a" and "b" folders.

        Show
        Gary Gregory added a comment - Remko Popma In the Eclipse apply patch wizard, don't forget to set the "Ignore leading path elements" value to 1. This usually deals with the "a" and "b" folders.
        Hide
        Remko Popma added a comment - - edited

        I see. Looks interesting.
        I'm using Subclipse (Subversion plugin for Eclipse) which uses something called the "unified diff format".

        Can you try again with the --no-prefix option? Perhaps without the "a/" source and "b/" destination prefix I'll be able to apply the patch.

        ... or perhaps git diff instead of git format-patch?

        Show
        Remko Popma added a comment - - edited I see. Looks interesting. I'm using Subclipse (Subversion plugin for Eclipse) which uses something called the "unified diff format". Can you try again with the --no-prefix option? Perhaps without the "a/" source and "b/" destination prefix I'll be able to apply the patch. ... or perhaps git diff instead of git format-patch ?
        Hide
        Matt Sicker added a comment -

        I used git-format-patch(1) to make the patch.

        Show
        Matt Sicker added a comment - I used git-format-patch(1) to make the patch.
        Hide
        Remko Popma added a comment -

        The new patch seems to have the same issue. I'm no expert on the patch format but I suspect it has to do with the path in the diff.

        The file to add would be {{ b/log4j-osgi/legacy-osgi-api/pom.xml}} (based on the screenshot, Eclipse is about to create a file in the "b/" directory),

        diff --git a/log4j-osgi/legacy-osgi-api/pom.xml b/log4j-osgi/legacy-osgi-api/pom.xml
        new file mode 100644
        index 0000000..176cd52
        --- /dev/null
        +++ b/log4j-osgi/legacy-osgi-api/pom.xml
        @@ -0,0 +1,115 @@
        ...
        

        and the file to modify would be a/log4j-osgi/pom.xml which does not exist (log4j-osgi/pom.xml does exist).

        diff --git a/log4j-osgi/pom.xml b/log4j-osgi/pom.xml
        index 540ffc8..d86d827 100644
        --- a/log4j-osgi/pom.xml
        +++ b/log4j-osgi/pom.xml
        @@ -46,6 +46,7 @@
        ...
        

        I wonder about the "a" and "b" path prefixes. They seem to be about different versions of the same file, but I've never seen this notation. What tool are you using? Is there a patch "type" or "mode" that you can select?

        I would expect something like this:

        --- log4j12-api/pom.xml	(revision 1516096)
        +++ log4j12-api/pom.xml	(working copy)
        @@ -24,7 +24,7 @@
        ...
        

        Attaching the pom is fine this time but going forward it would be better to have patches work smoothly...

        Show
        Remko Popma added a comment - The new patch seems to have the same issue. I'm no expert on the patch format but I suspect it has to do with the path in the diff. The file to add would be {{ b/log4j-osgi/legacy-osgi-api/pom.xml}} (based on the screenshot, Eclipse is about to create a file in the "b/" directory), diff --git a/log4j-osgi/legacy-osgi-api/pom.xml b/log4j-osgi/legacy-osgi-api/pom.xml new file mode 100644 index 0000000..176cd52 --- /dev/ null +++ b/log4j-osgi/legacy-osgi-api/pom.xml @@ -0,0 +1,115 @@ ... and the file to modify would be a/log4j-osgi/pom.xml which does not exist ( log4j-osgi/pom.xml does exist). diff --git a/log4j-osgi/pom.xml b/log4j-osgi/pom.xml index 540ffc8..d86d827 100644 --- a/log4j-osgi/pom.xml +++ b/log4j-osgi/pom.xml @@ -46,6 +46,7 @@ ... I wonder about the "a" and "b" path prefixes. They seem to be about different versions of the same file, but I've never seen this notation. What tool are you using? Is there a patch "type" or "mode" that you can select? I would expect something like this: --- log4j12-api/pom.xml (revision 1516096) +++ log4j12-api/pom.xml (working copy) @@ -24,7 +24,7 @@ ... Attaching the pom is fine this time but going forward it would be better to have patches work smoothly...
        Hide
        Matt Sicker added a comment -

        Huh, weird. Here's a git format-patch trunk using the latest data. If this still doesn't work, I can just attach the new pom.xml file instead.

        Show
        Matt Sicker added a comment - Huh, weird. Here's a git format-patch trunk using the latest data. If this still doesn't work, I can just attach the new pom.xml file instead.
        Hide
        Remko Popma added a comment -

        Matt, I have trouble applying the patch. Please see attached log4j2-345-patch-issue.png

        Show
        Remko Popma added a comment - Matt, I have trouble applying the patch. Please see attached log4j2-345-patch-issue.png
        Hide
        Matt Sicker added a comment -

        The patch only adds another module. There's no code in this one. I think this would be rather important for OSGi support in 2.0, especially in helping get people to upgrade.

        Show
        Matt Sicker added a comment - The patch only adds another module. There's no code in this one. I think this would be rather important for OSGi support in 2.0, especially in helping get people to upgrade.
        Hide
        Gary Gregory added a comment -

        It seems to me that all Log4j bundles should start with "log4j-". Don't some start with "core-" now?

        Show
        Gary Gregory added a comment - It seems to me that all Log4j bundles should start with "log4j-". Don't some start with "core-" now?
        Hide
        Remko Popma added a comment -

        Can we safely apply this patch now, or would it be better to wait until after RC1/GA and we do all OSGi stuff in one go?
        (Any impact to non-OSGi apps if I apply this patch?)

        Show
        Remko Popma added a comment - Can we safely apply this patch now, or would it be better to wait until after RC1/GA and we do all OSGi stuff in one go? (Any impact to non-OSGi apps if I apply this patch?)
        Hide
        Matt Sicker added a comment -

        Here you go. One patch for adding the 1.x API as another bundle.

        Show
        Matt Sicker added a comment - Here you go. One patch for adding the 1.x API as another bundle.
        Hide
        Matt Sicker added a comment -

        The attached patch is the same as the one in the comments. I don't think the version numbers being exported are correct, though. Some should be using pre-defined properties. Plus, the log4j 1.2 API bundle should be a separate pom. I don't think converting it form jar to bundle makes a whole lot of sense, but I'm not very experienced with OSGi.

        Show
        Matt Sicker added a comment - The attached patch is the same as the one in the comments. I don't think the version numbers being exported are correct, though. Some should be using pre-defined properties. Plus, the log4j 1.2 API bundle should be a separate pom. I don't think converting it form jar to bundle makes a whole lot of sense, but I'm not very experienced with OSGi.
        Hide
        Roland Weiglhofer added a comment - - edited

        Sorry for the blocker, but we will soon decide whether log4j2 will be dead for the next few years or not.

        Show
        Roland Weiglhofer added a comment - - edited Sorry for the blocker, but we will soon decide whether log4j2 will be dead for the next few years or not.
        Hide
        Ralph Goers added a comment - - edited

        Is the patch file that is attached the same as what you have above? I would prefer patch files rather than trying to cut and paste from Jira. Did you provide a way to for the build to verify that this is working properly? For example, an OSGi based unit test that performs a bit of logging?

        I do want to apply these patches before the next release so we will get to them as soon as we can.

        Show
        Ralph Goers added a comment - - edited Is the patch file that is attached the same as what you have above? I would prefer patch files rather than trying to cut and paste from Jira. Did you provide a way to for the build to verify that this is working properly? For example, an OSGi based unit test that performs a bit of logging? I do want to apply these patches before the next release so we will get to them as soon as we can.
        Hide
        Roland Weiglhofer added a comment -

        I don't dare ask because I know that you are volunteers. But it would be nice to get some feedback if the patch is a acceptable solution, and when you have the time to apply it.

        Thanks and Regards!!

        Show
        Roland Weiglhofer added a comment - I don't dare ask because I know that you are volunteers. But it would be nice to get some feedback if the patch is a acceptable solution, and when you have the time to apply it. Thanks and Regards!!
        Hide
        Roland Weiglhofer added a comment -

        Index: pom.xml
        ===================================================================
        — pom.xml (revision 1516096)
        +++ pom.xml (working copy)
        @@ -142,6 +142,8 @@
        <!-- Configuration properties for the OSGi maven-bundle-plugin -->
        <osgi.symbolicName>org.apache.logging.$

        {project.artifactId}

        </osgi.symbolicName>
        <osgi.export>org.apache.logging.log4j.*;version=$

        {project.version};-noimport:=true</osgi.export>
        + <osgi.export.slf4jbinding>org.slf4j.impl;version=1.7.5,org.slf4j.helpers;version=1.7.5,org.apache.logging.slf4j;version=${project.version}

        </osgi.export.slf4jbinding>
        + <osgi.export.log4j1.2>org.apache.log4j;version=1.2,org.apache.log4j.helpers;version=1.2,org.apache.log4j.config;version=1.2,org.apache.log4j.spi;version=1.2,org.apache.log4j.xml;version=1.2</osgi.export.log4j1.2>
        <osgi.import>*</osgi.import>
        <osgi.dynamicImport />
        <osgi.private />
        Index: log4j12-api/pom.xml
        ===================================================================
        — log4j12-api/pom.xml (revision 1516096)
        +++ log4j12-api/pom.xml (working copy)
        @@ -24,7 +24,7 @@
        <relativePath>../</relativePath>
        </parent>
        <artifactId>log4j-1.2-api</artifactId>

        • <packaging>jar</packaging>
          + <packaging>bundle</packaging>
          <name>Apache Log4j 1.x Compatibility API</name>
          <description>The Log4j 1.x Compatibility API</description>
          <properties>
          @@ -55,6 +55,22 @@
          </dependencies>
          <build>
          <plugins>
          + <plugin>
          + <groupId>org.apache.felix</groupId>
          + <artifactId>maven-bundle-plugin</artifactId>
          + <extensions>true</extensions>
          + <inherited>true</inherited>
          + <configuration>
          + <instructions>
          + <Bundle-SymbolicName>$ {osgi.symbolicName}

          </Bundle-SymbolicName>
          + <Export-Package>$

          {osgi.export.log4j1.2}

          </Export-Package>
          + <Private-Package>$

          {osgi.private}

          </Private-Package>
          + <Import-Package>$

          {osgi.import}

          </Import-Package>
          + <DynamicImport-Package>$

          {osgi.dynamicImport}

          </DynamicImport-Package>
          + <Bundle-DocURL>$

          {project.url}

          </Bundle-DocURL>
          + </instructions>
          + </configuration>
          + </plugin>
          <!-- Include the standard NOTICE and LICENSE -->
          <plugin>
          <groupId>org.apache.maven.plugins</groupId>

        Show
        Roland Weiglhofer added a comment - Index: pom.xml =================================================================== — pom.xml (revision 1516096) +++ pom.xml (working copy) @@ -142,6 +142,8 @@ <!-- Configuration properties for the OSGi maven-bundle-plugin --> <osgi.symbolicName>org.apache.logging.$ {project.artifactId} </osgi.symbolicName> <osgi.export>org.apache.logging.log4j.*;version=$ {project.version};-noimport:=true</osgi.export> + <osgi.export.slf4jbinding>org.slf4j.impl;version=1.7.5,org.slf4j.helpers;version=1.7.5,org.apache.logging.slf4j;version=${project.version} </osgi.export.slf4jbinding> + <osgi.export.log4j1.2>org.apache.log4j;version=1.2,org.apache.log4j.helpers;version=1.2,org.apache.log4j.config;version=1.2,org.apache.log4j.spi;version=1.2,org.apache.log4j.xml;version=1.2</osgi.export.log4j1.2> <osgi.import>*</osgi.import> <osgi.dynamicImport /> <osgi.private /> Index: log4j12-api/pom.xml =================================================================== — log4j12-api/pom.xml (revision 1516096) +++ log4j12-api/pom.xml (working copy) @@ -24,7 +24,7 @@ <relativePath>../</relativePath> </parent> <artifactId>log4j-1.2-api</artifactId> <packaging>jar</packaging> + <packaging>bundle</packaging> <name>Apache Log4j 1.x Compatibility API</name> <description>The Log4j 1.x Compatibility API</description> <properties> @@ -55,6 +55,22 @@ </dependencies> <build> <plugins> + <plugin> + <groupId>org.apache.felix</groupId> + <artifactId>maven-bundle-plugin</artifactId> + <extensions>true</extensions> + <inherited>true</inherited> + <configuration> + <instructions> + <Bundle-SymbolicName>$ {osgi.symbolicName} </Bundle-SymbolicName> + <Export-Package>$ {osgi.export.log4j1.2} </Export-Package> + <Private-Package>$ {osgi.private} </Private-Package> + <Import-Package>$ {osgi.import} </Import-Package> + <DynamicImport-Package>$ {osgi.dynamicImport} </DynamicImport-Package> + <Bundle-DocURL>$ {project.url} </Bundle-DocURL> + </instructions> + </configuration> + </plugin> <!-- Include the standard NOTICE and LICENSE --> <plugin> <groupId>org.apache.maven.plugins</groupId>
        Hide
        Roland Weiglhofer added a comment - - edited

        Hi,
        I changed the poms and I created a patch. To whom should I send the patch-file?

        Regards
        Roland

        --------------------------------------------------------------------
        output

        lb
        START LEVEL 4
        ID|State |Level|Name
        0|Active | 0|System Bundle (4.2.1)
        4|Active | 2|Apache Felix Bundle Repository (1.6.6)
        5|Active | 2|Apache Felix Configuration Admin Service (1.6.0)
        6|Active | 2|Apache Felix Gogo Command (0.12.0)
        7|Active | 2|Apache Felix Gogo Runtime (0.10.0)
        8|Active | 2|Apache Felix Gogo Shell (0.10.0)
        9|Resolved | 2|Apache Felix Security Provider (2.2.0)
        10|Active | 2|Apache Felix Shell Service (1.4.3)
        11|Active | 2|Apache Log4j 1.x Compatibility API (2.0.0.beta9-SNAPSHOT)
        12|Active | 2|Apache Log4j API (2.0.0.beta9-SNAPSHOT)
        13|Active | 2|Apache Log4j Commons Logging Bridge (2.0.0.beta9-SNAPSHOT)
        14|Active | 2|Apache Log4j Core (2.0.0.beta9-SNAPSHOT)
        15|Active | 2|Apache Log4j SLF4J Binding (2.0.0.beta9-SNAPSHOT)
        16|Active | 2|cal10n-api (0.7.4)
        17|Active | 2|Commons Codec (1.6.0)
        18|Active | 2|Commons IO (2.4.0)
        19|Active | 2|Commons Lang (2.6.0)
        20|Active | 2|Data mapper for Jackson JSON processor (1.9.13)
        21|Active | 2|Disruptor Framework (3.1.1)
        22|Active | 2|Gson (2.2.4)
        23|Active | 2|Jackson JSON processor (1.9.13)
        24|Active | 2|Jackson-annotations (2.2.2)
        25|Active | 2|Jackson-core (2.2.2)
        26|Active | 2|jackson-databind (2.2.2)
        27|Active | 2|JSON.simple (1.1.1)
        28|Active | 2|MongoDB Java Driver (2.11.2.RELEASE)
        29|Active | 2|slf4j-api (1.7.5)
        30|Active | 2|slf4j-ext (1.7.5)

        Show
        Roland Weiglhofer added a comment - - edited Hi, I changed the poms and I created a patch. To whom should I send the patch-file? Regards Roland -------------------------------------------------------------------- output lb START LEVEL 4 ID|State |Level|Name 0|Active | 0|System Bundle (4.2.1) 4|Active | 2|Apache Felix Bundle Repository (1.6.6) 5|Active | 2|Apache Felix Configuration Admin Service (1.6.0) 6|Active | 2|Apache Felix Gogo Command (0.12.0) 7|Active | 2|Apache Felix Gogo Runtime (0.10.0) 8|Active | 2|Apache Felix Gogo Shell (0.10.0) 9|Resolved | 2|Apache Felix Security Provider (2.2.0) 10|Active | 2|Apache Felix Shell Service (1.4.3) 11|Active | 2|Apache Log4j 1.x Compatibility API (2.0.0.beta9-SNAPSHOT) 12|Active | 2|Apache Log4j API (2.0.0.beta9-SNAPSHOT) 13|Active | 2|Apache Log4j Commons Logging Bridge (2.0.0.beta9-SNAPSHOT) 14|Active | 2|Apache Log4j Core (2.0.0.beta9-SNAPSHOT) 15|Active | 2|Apache Log4j SLF4J Binding (2.0.0.beta9-SNAPSHOT) 16|Active | 2|cal10n-api (0.7.4) 17|Active | 2|Commons Codec (1.6.0) 18|Active | 2|Commons IO (2.4.0) 19|Active | 2|Commons Lang (2.6.0) 20|Active | 2|Data mapper for Jackson JSON processor (1.9.13) 21|Active | 2|Disruptor Framework (3.1.1) 22|Active | 2|Gson (2.2.4) 23|Active | 2|Jackson JSON processor (1.9.13) 24|Active | 2|Jackson-annotations (2.2.2) 25|Active | 2|Jackson-core (2.2.2) 26|Active | 2|jackson-databind (2.2.2) 27|Active | 2|JSON.simple (1.1.1) 28|Active | 2|MongoDB Java Driver (2.11.2.RELEASE) 29|Active | 2|slf4j-api (1.7.5) 30|Active | 2|slf4j-ext (1.7.5)

          People

          • Assignee:
            Matt Sicker
            Reporter:
            Roland Weiglhofer
          • Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development