Accumulo
  1. Accumulo
  2. ACCUMULO-1910

Add source to jar files used for testing

    Details

    • Type: Task Task
    • Status: Resolved
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 1.4.4, 1.5.0
    • Fix Version/s: 1.4.5, 1.5.1, 1.6.0
    • Component/s: test
    • Labels:

      Description

      Some of the jars we include for testing purposes have the source included. Some do not.

      It would be nice to make sure that we included the source for all of these jars, not just the class files.

      Jars in 1.4 with no source

      • ./src/start/src/test/resources/ClassLoaderTestA/Test.jar
      • ./src/start/src/test/resources/ClassLoaderTestB/Test.jar
      • ./src/start/src/test/resources/ClassLoaderTestC/Test.jar
      • ./test/system/auto/TestCombinerX.jar
      • ./test/system/auto/TestCombinerY.jar

      Jars in 1.5 and 1.6 with no source:

      • ./start/src/test/resources/ClassLoaderTestA/Test.jar
      • ./start/src/test/resources/ClassLoaderTestB/Test.jar
      • ./start/src/test/resources/ClassLoaderTestC/Test.jar
      • ./start/src/test/resources/HelloWorld2.jar
      • ./test/src/test/resources/FooConstraint.jar
      • ./test/system/auto/TestCombinerX.jar
      • ./test/system/auto/TestCombinerY.jar
      1. test-jars-src.tgz
        23 kB
        Ed Coleman
      2. ACCUMULO-1910-1.6.0-SNAPSHOT.patch
        25 kB
        Ed Coleman
      3. ACCUMULO-1910-1.5.1-SNAPSHOT.patch
        25 kB
        Ed Coleman
      4. ACCUMULO-1910-1.4.5-SNAPSHOT.patch
        17 kB
        Ed Coleman

        Issue Links

          Activity

          Hide
          ASF subversion and git services added a comment -

          Commit 280b6a6dee719bcef68d7f4f8e187b2a6abcd3d2 in branch refs/heads/master from Josh Elser
          [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=280b6a6 ]

          ACCUMULO-1910 Add updated HelloWorld2.jar and FooConstraint.jar, provided by Ed Coleman, which contain source files as well as the class files.

          Show
          ASF subversion and git services added a comment - Commit 280b6a6dee719bcef68d7f4f8e187b2a6abcd3d2 in branch refs/heads/master from Josh Elser [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=280b6a6 ] ACCUMULO-1910 Add updated HelloWorld2.jar and FooConstraint.jar, provided by Ed Coleman, which contain source files as well as the class files.
          Hide
          Josh Elser added a comment -

          Thanks, Ed Coleman! I applied your 1.4 patch, and then pulling the jars for HelloWorld2.jar and FooConstraint.jar out of the tarball to make the commit history a little bit cleaner.

          Show
          Josh Elser added a comment - Thanks, Ed Coleman ! I applied your 1.4 patch, and then pulling the jars for HelloWorld2.jar and FooConstraint.jar out of the tarball to make the commit history a little bit cleaner.
          Hide
          ASF subversion and git services added a comment -

          Commit 280b6a6dee719bcef68d7f4f8e187b2a6abcd3d2 in branch refs/heads/1.6.0-SNAPSHOT from Josh Elser
          [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=280b6a6 ]

          ACCUMULO-1910 Add updated HelloWorld2.jar and FooConstraint.jar, provided by Ed Coleman, which contain source files as well as the class files.

          Show
          ASF subversion and git services added a comment - Commit 280b6a6dee719bcef68d7f4f8e187b2a6abcd3d2 in branch refs/heads/1.6.0-SNAPSHOT from Josh Elser [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=280b6a6 ] ACCUMULO-1910 Add updated HelloWorld2.jar and FooConstraint.jar, provided by Ed Coleman, which contain source files as well as the class files.
          Hide
          ASF subversion and git services added a comment -

          Commit 43ab1ef70581c56169aa6ba4a5f715565519a333 in branch refs/heads/1.6.0-SNAPSHOT from Ed Coleman
          [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=43ab1ef ]

          ACCUMULO-1910 Add source to to test jars that did not have source.

          Some of the jars used in test cases did not have source code. This patch
          replaces those jars in 1.4.5-SNAPSHOT with jars that contain both .class
          and .java files.

          Signed-off-by: Josh Elser <elserj@apache.org>

          Show
          ASF subversion and git services added a comment - Commit 43ab1ef70581c56169aa6ba4a5f715565519a333 in branch refs/heads/1.6.0-SNAPSHOT from Ed Coleman [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=43ab1ef ] ACCUMULO-1910 Add source to to test jars that did not have source. Some of the jars used in test cases did not have source code. This patch replaces those jars in 1.4.5-SNAPSHOT with jars that contain both .class and .java files. Signed-off-by: Josh Elser <elserj@apache.org>
          Hide
          ASF subversion and git services added a comment -

          Commit 280b6a6dee719bcef68d7f4f8e187b2a6abcd3d2 in branch refs/heads/1.5.1-SNAPSHOT from Josh Elser
          [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=280b6a6 ]

          ACCUMULO-1910 Add updated HelloWorld2.jar and FooConstraint.jar, provided by Ed Coleman, which contain source files as well as the class files.

          Show
          ASF subversion and git services added a comment - Commit 280b6a6dee719bcef68d7f4f8e187b2a6abcd3d2 in branch refs/heads/1.5.1-SNAPSHOT from Josh Elser [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=280b6a6 ] ACCUMULO-1910 Add updated HelloWorld2.jar and FooConstraint.jar, provided by Ed Coleman, which contain source files as well as the class files.
          Hide
          ASF subversion and git services added a comment -

          Commit 43ab1ef70581c56169aa6ba4a5f715565519a333 in branch refs/heads/1.5.1-SNAPSHOT from Ed Coleman
          [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=43ab1ef ]

          ACCUMULO-1910 Add source to to test jars that did not have source.

          Some of the jars used in test cases did not have source code. This patch
          replaces those jars in 1.4.5-SNAPSHOT with jars that contain both .class
          and .java files.

          Signed-off-by: Josh Elser <elserj@apache.org>

          Show
          ASF subversion and git services added a comment - Commit 43ab1ef70581c56169aa6ba4a5f715565519a333 in branch refs/heads/1.5.1-SNAPSHOT from Ed Coleman [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=43ab1ef ] ACCUMULO-1910 Add source to to test jars that did not have source. Some of the jars used in test cases did not have source code. This patch replaces those jars in 1.4.5-SNAPSHOT with jars that contain both .class and .java files. Signed-off-by: Josh Elser <elserj@apache.org>
          Hide
          ASF subversion and git services added a comment -

          Commit 43ab1ef70581c56169aa6ba4a5f715565519a333 in branch refs/heads/1.4.5-SNAPSHOT from Ed Coleman
          [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=43ab1ef ]

          ACCUMULO-1910 Add source to to test jars that did not have source.

          Some of the jars used in test cases did not have source code. This patch
          replaces those jars in 1.4.5-SNAPSHOT with jars that contain both .class
          and .java files.

          Signed-off-by: Josh Elser <elserj@apache.org>

          Show
          ASF subversion and git services added a comment - Commit 43ab1ef70581c56169aa6ba4a5f715565519a333 in branch refs/heads/1.4.5-SNAPSHOT from Ed Coleman [ https://git-wip-us.apache.org/repos/asf?p=accumulo.git;h=43ab1ef ] ACCUMULO-1910 Add source to to test jars that did not have source. Some of the jars used in test cases did not have source code. This patch replaces those jars in 1.4.5-SNAPSHOT with jars that contain both .class and .java files. Signed-off-by: Josh Elser <elserj@apache.org>
          Hide
          Ed Coleman added a comment -

          Attached files contain ACCUMULO-1910-1.4.5-SNAPSHOT.patch, ACCUMULO-1910-1.5.1-SNAPSHOT.patch, and ACCUMULO-1910-1.6.0-SNAPSHOT.patch.

          I created separate patch files to minimize the chance that I would somehow pull changes that do not belong in this patch set.

          1.4.5-SNAPSHOT - mvn clean package completes without errors
          1.5.1-SNAPSHOT - mvn clean package completes without errors
          1.6.0-SNAPSHOT - mvn clean package and mvn clean package -P assemble complete without errors.

          Show
          Ed Coleman added a comment - Attached files contain ACCUMULO-1910 -1.4.5-SNAPSHOT.patch, ACCUMULO-1910 -1.5.1-SNAPSHOT.patch, and ACCUMULO-1910 -1.6.0-SNAPSHOT.patch. I created separate patch files to minimize the chance that I would somehow pull changes that do not belong in this patch set. 1.4.5-SNAPSHOT - mvn clean package completes without errors 1.5.1-SNAPSHOT - mvn clean package completes without errors 1.6.0-SNAPSHOT - mvn clean package and mvn clean package -P assemble complete without errors.
          Hide
          Ed Coleman added a comment -

          These files contain the test jars with source (*.patch files) and also the maven projects that I used to create them.

          I created separate patches for each accumulo version so that they would be clean and I would not wreck havoc if I tried to merge / pull them.

          The tar with the maven project(s) are really just so that they can be archived here (for when someone finds I made a mistake) but I don't expect they need to be incorporated to any release branch. If test jar generators are going to be include in future release, we should examine the approach, because this way is much more difficult that it really needs to be.

          A few notes and lessons learned:

          The issue that I was having with 1.4.5-SNAPSHOT build appears to have been because I had ACCUMULO_HOME set for my run-time environment. Un-setting that variable was all that I needed to do.

          The timeout errors that I received under 1.5.1-SNAPSHOT were do to an error in the package name that I had for FooConstraint - I suspect the test were throwing class-not-found exceptions, but the junit error that was reported look like it was a timeout error in the test case. So no timeouts, just test errors because of my mistake(s)

          Not sure that mvn package tests use ClassLoader[B/C]. I had an error where I copied ClassLoaderA/Test.jar to both B and C and only 1.4.5-SNAPSHOT seemed to recognize the error.

          Each generator project has a createJar directory with a createJar.sh script that will run maven, copy the files to a temp directory outside of the maven build path and then run the jar cvf command. The jar command was used instead of maven plug-ins so that only the default manifest is included in the resulting jar files.

          Show
          Ed Coleman added a comment - These files contain the test jars with source (*.patch files) and also the maven projects that I used to create them. I created separate patches for each accumulo version so that they would be clean and I would not wreck havoc if I tried to merge / pull them. The tar with the maven project(s) are really just so that they can be archived here (for when someone finds I made a mistake) but I don't expect they need to be incorporated to any release branch. If test jar generators are going to be include in future release, we should examine the approach, because this way is much more difficult that it really needs to be. A few notes and lessons learned: The issue that I was having with 1.4.5-SNAPSHOT build appears to have been because I had ACCUMULO_HOME set for my run-time environment. Un-setting that variable was all that I needed to do. The timeout errors that I received under 1.5.1-SNAPSHOT were do to an error in the package name that I had for FooConstraint - I suspect the test were throwing class-not-found exceptions, but the junit error that was reported look like it was a timeout error in the test case. So no timeouts, just test errors because of my mistake(s) Not sure that mvn package tests use ClassLoader [B/C] . I had an error where I copied ClassLoaderA/Test.jar to both B and C and only 1.4.5-SNAPSHOT seemed to recognize the error. Each generator project has a createJar directory with a createJar.sh script that will run maven, copy the files to a temp directory outside of the maven build path and then run the jar cvf command. The jar command was used instead of maven plug-ins so that only the default manifest is included in the resulting jar files.
          Hide
          Ed Coleman added a comment -

          test jars with source for 1.6.0 (same as 1.5.1?) Created separate patch for 1.6.0 so that the was no chance that I would introduce other merge artifacts by pulling my changes from 1.5.1.

          Show
          Ed Coleman added a comment - test jars with source for 1.6.0 (same as 1.5.1?) Created separate patch for 1.6.0 so that the was no chance that I would introduce other merge artifacts by pulling my changes from 1.5.1.
          Hide
          Ed Coleman added a comment -

          The files in ACCUMULO-1910-1.5.1.patch are the same files that I posted earlier. The test failures seem to have been transient timeout in the mini-cluster and shell tests. The tests have passed once I ran on a quite system - I must be right on the edge for having those tests pass or fail.

          Working 1.6.0 now.

          Show
          Ed Coleman added a comment - The files in ACCUMULO-1910 -1.5.1.patch are the same files that I posted earlier. The test failures seem to have been transient timeout in the mini-cluster and shell tests. The tests have passed once I ran on a quite system - I must be right on the edge for having those tests pass or fail. Working 1.6.0 now.
          Hide
          Ed Coleman added a comment -

          This file contains the test jars that did not have source code with functionally jars that contain both .class and .java files.

          Show
          Ed Coleman added a comment - This file contains the test jars that did not have source code with functionally jars that contain both .class and .java files.
          Hide
          Ed Coleman added a comment -

          Removed files because tests started to fail - need to verify I did this correctly.

          Show
          Ed Coleman added a comment - Removed files because tests started to fail - need to verify I did this correctly.
          Hide
          Ed Coleman added a comment -

          Will follow-up with 1.4.5 and 1.6.x (if necessary) once those files are in place I'll submit the patch - should be within the next day or two.

          Show
          Ed Coleman added a comment - Will follow-up with 1.4.5 and 1.6.x (if necessary) once those files are in place I'll submit the patch - should be within the next day or two.
          Hide
          Ed Coleman added a comment -

          Patch that includes only replaced jar files for 1.5.1-SNAPSHOT

          Show
          Ed Coleman added a comment - Patch that includes only replaced jar files for 1.5.1-SNAPSHOT
          Hide
          Ed Coleman added a comment -

          Revising to only include revised jars with source instead of separate maven projects.

          Show
          Ed Coleman added a comment - Revising to only include revised jars with source instead of separate maven projects.
          Hide
          Josh Elser added a comment -

          just jar cvf

          This is what I was initially thinking of. These jars are only used in unit tests. I was just thinking it would be nice to have the source in the jar if/when someone has to debug a test that uses it and they don't have to guess at what the source is actually doing.

          I believe that all of the tests which currently use these jars are using them for testing something else. That being said, I do appreciate you trying to go above and beyond

          Show
          Josh Elser added a comment - just jar cvf This is what I was initially thinking of. These jars are only used in unit tests. I was just thinking it would be nice to have the source in the jar if/when someone has to debug a test that uses it and they don't have to guess at what the source is actually doing. I believe that all of the tests which currently use these jars are using them for testing something else. That being said, I do appreciate you trying to go above and beyond
          Hide
          Ed Coleman added a comment -

          I have no problem with just putting the jars into a patch. However, are there any issues with the manifest? Maven seems to insist that some of my info leak in - no problem with that if everyone is okay with it.

          With the current patch, it could be built on the jenkis server and then have only accumulo build artifacts. - (Seems cleaner to me.)

          Alternately, I could modify the build on my end, but sometimes it seems than me and maven are not the best of friends (i.e. suggestions more than welcome,) Or I could ditch maven and just jar cvf ... as long as no one wants to replicate the build...

          Show
          Ed Coleman added a comment - I have no problem with just putting the jars into a patch. However, are there any issues with the manifest? Maven seems to insist that some of my info leak in - no problem with that if everyone is okay with it. With the current patch, it could be built on the jenkis server and then have only accumulo build artifacts. - (Seems cleaner to me.) Alternately, I could modify the build on my end, but sometimes it seems than me and maven are not the best of friends (i.e. suggestions more than welcome,) Or I could ditch maven and just jar cvf ... as long as no one wants to replicate the build...
          Hide
          Mike Drob added a comment -

          Yea... I think we're making this complicated for the sake of preserving compatibility in something that isn't part of the public API anyway. I strongly encourage the shortest path solution here, as the code was never functionally wrong, just a slight bit opaque. Like Josh Elser alluded to earlier, a binary patch of swapping out one jar for another would likely have been sufficient.

          I added src/test-jars-src as another module to the main pom.xml and then saw the artifacts get built.

          I think it would be easiest for new users to grok fewer jars, since the source files will exist in the tree anyway, but feel free to disagree. My main concern at this point is making sure that the jars we are generating are the ones getting used by our tests, which I'm not convinced is the case right now.

          Can you create a new JIRA for the doc-gen issues that you are running into?

          Show
          Mike Drob added a comment - Yea... I think we're making this complicated for the sake of preserving compatibility in something that isn't part of the public API anyway. I strongly encourage the shortest path solution here, as the code was never functionally wrong, just a slight bit opaque. Like Josh Elser alluded to earlier, a binary patch of swapping out one jar for another would likely have been sufficient. I added src/test-jars-src as another module to the main pom.xml and then saw the artifacts get built. I think it would be easiest for new users to grok fewer jars, since the source files will exist in the tree anyway, but feel free to disagree. My main concern at this point is making sure that the jars we are generating are the ones getting used by our tests, which I'm not convinced is the case right now. Can you create a new JIRA for the doc-gen issues that you are running into?
          Hide
          Ed Coleman added a comment -

          To get it to create both type of artifacts I just run:

          mvn clean package.

          Show
          Ed Coleman added a comment - To get it to create both type of artifacts I just run: mvn clean package.
          Hide
          Ed Coleman added a comment -

          Yes, it is the dependency for accumulo-core. In the pom(s) for TestCombinerX, Y the dependency for accumulo-core is set to (1.4.4,], overriding the project version. For 1.5.1 I can compile just fine, so 1.5.1-SNAPSHOT works okay (matches project version). This was just a work-around for me because 1.4.5-SNAPSHOT build was causing problems with docgen so I don't have 1.4.5-SNAPSHOT artifacts to compile against..

          The sources end-up in the [Artifact]-sources.jar file - those have both the class and the source (.java) file(s). So for ClassloaderA you should have had both Test.jar and Test-sources.jar

          I've probably over-thought this, but I didn't want to change existing artifacts and it does not seem "natural" to have both class and java files in a jar used at run-time? At least, that's what the maven sources plugin was leading me to believe and rather than fight convention I thought it may be best to provide both. I see that the test jars with source for 1.5.1 do have both, so... well, didn't know which way to go. I thought we could provide both, or rename [Artifact]-sources to [Artifact].jar and call it complete. (i.e. figured it is easier to delete than to create). If the [Artifact]-source.jars are just renamed, the whole sub-project thing could go away, but maybe they could be useful if someone wanted to tweak the samples as a starting point?

          Working on 1.5.1 and have FooConstraints mostly done, just need to get HelloWorld2.

          Show
          Ed Coleman added a comment - Yes, it is the dependency for accumulo-core. In the pom(s) for TestCombinerX, Y the dependency for accumulo-core is set to (1.4.4,], overriding the project version. For 1.5.1 I can compile just fine, so 1.5.1-SNAPSHOT works okay (matches project version). This was just a work-around for me because 1.4.5-SNAPSHOT build was causing problems with docgen so I don't have 1.4.5-SNAPSHOT artifacts to compile against.. The sources end-up in the [Artifact] -sources.jar file - those have both the class and the source (.java) file(s). So for ClassloaderA you should have had both Test.jar and Test-sources.jar I've probably over-thought this, but I didn't want to change existing artifacts and it does not seem "natural" to have both class and java files in a jar used at run-time? At least, that's what the maven sources plugin was leading me to believe and rather than fight convention I thought it may be best to provide both. I see that the test jars with source for 1.5.1 do have both, so... well, didn't know which way to go. I thought we could provide both, or rename [Artifact] -sources to [Artifact] .jar and call it complete. (i.e. figured it is easier to delete than to create). If the [Artifact] -source.jars are just renamed, the whole sub-project thing could go away, but maybe they could be useful if someone wanted to tweak the samples as a starting point? — Working on 1.5.1 and have FooConstraints mostly done, just need to get HelloWorld2.
          Hide
          Mike Drob added a comment - - edited

          Thanks for the patch, Ed!

          When you say that the project version is set to 1.4.4, do you mean that the dependency version is set to 1.4.4? Because I don't see anything else that it might be. It looks like it compiled cleanly for me as applied, so I'm not really sure what the problem that you're describing is.

          After applying the patch and running mvn clean package, I spot checked ./src/start/src/test/resources/ClassLoaderTestA/Test.jar and ./src/start/target/test-classes/ClassLoaderTestA/Test.jar, and neither one had source. Should I have used a different maven goal to make it work?

          Minor nit: there is trailing white space in some of the files: Test.java, TestObject.java, and some (but not all) of the pom.xml.

          Show
          Mike Drob added a comment - - edited Thanks for the patch, Ed! When you say that the project version is set to 1.4.4, do you mean that the dependency version is set to 1.4.4? Because I don't see anything else that it might be. It looks like it compiled cleanly for me as applied, so I'm not really sure what the problem that you're describing is. After applying the patch and running mvn clean package , I spot checked ./src/start/src/test/resources/ClassLoaderTestA/Test.jar and ./src/start/target/test-classes/ClassLoaderTestA/Test.jar , and neither one had source. Should I have used a different maven goal to make it work? Minor nit: there is trailing white space in some of the files: Test.java , TestObject.java , and some (but not all) of the pom.xml .
          Hide
          Ed Coleman added a comment -

          Files and maven projects with source to create jar used for testing (1.4.5-SNAPSHOT)

          Show
          Ed Coleman added a comment - Files and maven projects with source to create jar used for testing (1.4.5-SNAPSHOT)
          Hide
          Ed Coleman added a comment -

          Source files and maven projects to for jars used in testing.

          Note that the TestCombinerX and Y projects have project version set to 1.4.4 because I'm having issues building with docgen in 1.4.5-SNAPSHOT. The dependency is a compile time dependency on accumulo-core but does not get included in test jars created.

          Show
          Ed Coleman added a comment - Source files and maven projects to for jars used in testing. Note that the TestCombinerX and Y projects have project version set to 1.4.4 because I'm having issues building with docgen in 1.4.5-SNAPSHOT. The dependency is a compile time dependency on accumulo-core but does not get included in test jars created.
          Hide
          Ed Coleman added a comment -

          I'll have some free time over the next few days and will try to wrap this up and provide some options.

          Show
          Ed Coleman added a comment - I'll have some free time over the next few days and will try to wrap this up and provide some options.
          Hide
          Mike Drob added a comment -

          Ed Coleman - Did Josh Elser provide enough guidance, or do you have further questions on this? We'd love to see this submitted and committed.

          Show
          Mike Drob added a comment - Ed Coleman - Did Josh Elser provide enough guidance, or do you have further questions on this? We'd love to see this submitted and committed.
          Hide
          Josh Elser added a comment -

          Because this is a classloader test, was this created as a separate project so that it would not be in the accumulo namespace and is that how it went missing?

          I'd have to look at the test cases that load these jars, but I don't think they were in their own namespace. I don't think we need to have anything in our source tree for them, but having the source files in the jar with the class file would be nice, IMO. So, a new jar for those which have no source is what I was thinking of. You could attach either the source Java files or a new jar (which contains the source). It's up to you.

          My gut reaction was that we need source (per ASF policy), but Billie Rinaldi pointed out on the mailing list that she doesn't think that to be the case. Regardless, it would be nice for people trying to understand this code to have access to all the source we use to test.

          Show
          Josh Elser added a comment - Because this is a classloader test, was this created as a separate project so that it would not be in the accumulo namespace and is that how it went missing? I'd have to look at the test cases that load these jars, but I don't think they were in their own namespace. I don't think we need to have anything in our source tree for them, but having the source files in the jar with the class file would be nice, IMO. So, a new jar for those which have no source is what I was thinking of. You could attach either the source Java files or a new jar (which contains the source). It's up to you. My gut reaction was that we need source (per ASF policy), but Billie Rinaldi pointed out on the mailing list that she doesn't think that to be the case. Regardless, it would be nice for people trying to understand this code to have access to all the source we use to test.
          Hide
          Ed Coleman added a comment -

          The source for ./start/src/test/resources/ClassLoaderTestA/Test.jar (and B, C) is below. I have a question about packaging. Because this is a classloader test, was this created as a separate project so that it would not be in the accumulo namespace and is that how it went missing?

          TestCombinerX,Y are different, I need to check the others, but how do you want these to be packaged? (Stand-alone maven module, or maybe not as a source / class file but just added as a readme?)

          +++++++++

          package test;

          public class TestObject implements Test {

          private int count = 0;

          public String hello()

          { return "Hello from testA"; }

          public int add()

          { return ++count; }

          }

          Show
          Ed Coleman added a comment - The source for ./start/src/test/resources/ClassLoaderTestA/Test.jar (and B, C) is below. I have a question about packaging. Because this is a classloader test, was this created as a separate project so that it would not be in the accumulo namespace and is that how it went missing? TestCombinerX,Y are different, I need to check the others, but how do you want these to be packaged? (Stand-alone maven module, or maybe not as a source / class file but just added as a readme?) +++++++++ package test; public class TestObject implements Test { private int count = 0; public String hello() { return "Hello from testA"; } public int add() { return ++count; } }

            People

            • Assignee:
              Ed Coleman
              Reporter:
              Josh Elser
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved:

                Development