You can just do `-Dimpsort.skip` to get around that error for now. Updating to the newer impsort will fix it going forward.
On Sat, Apr 15, 2023 at 5:17 PM Keith Turner <ke...@deenlo.com> wrote: > > Thanks for taking a look Drew. > > I have not recently had any problems with Maven. I use the version of > Maven from my Linux distro so I suppose I have been lucky that it > worked. I don't fully understand why a newer version of Maven fails, > kinda curious what is going on there. The enforcer settings sound like > a good idea, I can take a look at that. > > The last Fluo release was against Java 8, Hadoop 2, and Accumulo 1. > This new RC brings Fluo up to newer dependency versions. Fluo recipes > are not currently working and need the similar updates as Fluo for > Java 11, Hadoop 3, and Accuulo 2.1. I was planning to look into that > after this release. It will be much easier to make PRs against Fluo > Recipes after Fluo 2 is released. I should have mentioned that in the > initial email. I had not looked at the release instructions > recently, I usually just run stresso and Fluo ITs for release testing. > > Fluo Uno and the stresso test in Fluo examples are working. However, > for stresso I have a branch with changes for Java 11, Hadoop 3, > Accumulo 2.1, and Fluo 2. That branch is here. There was one little > change I ran into during rc1 testing that I realized I had not pushed. > I just pushed that to the branch. After Fluo 2 is released, that > branch could be updated with the new version and merged. > > https://github.com/apache/fluo-examples/pull/11 > > The two other examples are not working, those need similar updates as > in the branch above. I was going to circle back to those after the > release after doing release notes. > > For uno I made the following config changes for it to run and I put > the rc1 fluo bin tgz in the uno downloads dir. > > diff --git a/conf/uno.conf b/conf/uno.conf > index 41144df..e53b00f 100644 > --- a/conf/uno.conf > +++ b/conf/uno.conf > @@ -6,7 +6,7 @@ > export HADOOP_VERSION=${HADOOP_VERSION:-3.3.4} > export ZOOKEEPER_VERSION=${ZOOKEEPER_VERSION:-3.8.1} > export ACCUMULO_VERSION=${ACCUMULO_VERSION:-2.1.0} > -export FLUO_VERSION=${FLUO_VERSION:-1.2.0} > +export FLUO_VERSION=${FLUO_VERSION:-2.0.0} > export FLUO_YARN_VERSION=${FLUO_YARN_VERSION:-1.0.0} > > # Hashes (supports MD5, SHA-1, SHA-256, and SHA-512; MD5 requires md5sum) > @@ -16,7 +16,7 @@ export FLUO_YARN_VERSION=${FLUO_YARN_VERSION:-1.0.0} > HADOOP_HASH=$(grep -F hadoop:"${HADOOP_VERSION}": > "${UNO_HOME:?}"/conf/checksums | cut -d : -f 3) > ZOOKEEPER_HASH=$(grep -F zookeeper:"${ZOOKEEPER_VERSION}": > "${UNO_HOME:?}"/conf/checksums | cut -d : -f 3) > ACCUMULO_HASH=$(grep -F accumulo:"${ACCUMULO_VERSION}": > "${UNO_HOME:?}"/conf/checksums | cut -d : -f 3) > -FLUO_HASH=037f89cd2bfdaf76a1368256c52de46d6b9a85c9c1bfc776ec4447d02c813fb2 > +FLUO_HASH=d980f0c8b22eb134cc33a54a7e69eb83955519d5227eac2556a531790c31e43e > > FLUO_YARN_HASH=c6220d35cf23127272f3b5638c44586504dc17a46f5beecdfee5027b5ff874b0 > export HADOOP_HASH ZOOKEEPER_HASH ACCUMULO_HASH FLUO_HASH FLUO_YARN_HASH > > > On Fri, Apr 14, 2023 at 8:26 PM Drew Farris <d...@apache.org> wrote: > > > > At Keith's behest, I took a look at 2.0.0.rc1 - I didn't want to pollute > > the [VOTE] thread with this, but had an observation and a question about > > testing the rc. Take all this with the grain of salt that It's been awhile > > since I've tested a fluo RC, so I chalk this up to inexperience more than > > anything.. > > > > First, building fluo with maven 3.9.0 and java11: > > > > git clone -b 2.0.0-rc1 g...@github.com:apache/fluo.git && cd fluo && mvn > > clean install > > [...] > > [ERROR] Failed to execute goal > > net.revelc.code:impsort-maven-plugin:1.0.1:sort (sort-imports) on project > > fluo-api: Execution sort-imports of goal > > net.revelc.code:impsort-maven-plugin:1.0.1:sort failed: A required class > > was missing while executing > > net.revelc.code:impsort-maven-plugin:1.0.1:sort: > > org/codehaus/plexus/util/DirectoryScanner > > > > Reverting to maven 3.8.8 addressed this issue. Not a blocker, but it would > > be nice to enforce the maven and java version if possible. > > > > Once I adjusted the maven version, things built, unit tests and integration > > tests ran correctly. > > > > I spent some time reviewing and working through > > https://fluo.apache.org/release-process/#test-a-fluo-release - but had > > mixed results. Would we expect fluo-recipies, uno and fluo-examples to work > > with 2.0.0 at this point, or do they still need to be updated? > > > > Drew
