Jim,
Our
normal process here is to use profiles and the -P “profile
name” . Inside IntelliJ we just have to check a box under
the Maven tab.
For
command line, it would usually go something like mvn clean
install -P “Accumulo 1.5”
I
was not aware of the activation portion of the profile
element in maven until I researched it trying to determine
what profiles were being activated. Using the -P “Accumulo
1.5” did not activate that profile as the property is not
set or defaulted.
If
the expected default is to be Accumulo 1.6, I will leave
things as they are and always ensure I set the property the
appropriate way for the build I am working.
Thanks,
Chris
Snider
Senior
Software Engineer
Intelligent
Software Solutions, Inc.
Hi Chris,
The build profiles are brand new, and apologies for not
documenting them. My thought is that most current Accumulo
development is likely targeted at Accumulo 1.6 rather than
1.5. At least that was my thinking while setting things up
initially.
As a note, the two builds should produce the same artifacts.
We were shooting for producing jars which are compatible with
Accumulo 1.5 and 1.6. That said, Emilio did fix some issues
with that initial work. Most of the API differences between
1.5 and 1.6 are focused on MapReduce support. Due to that
fact, the main point of the profiles to run the unit tests
against the different versions to try and catch any major
problems.
If there's a better way to let the two profiles live together
in IntelliJ, I'm all ears. To build at the command line, one
can use 'mvn clean install' (*) to build for Accumulo 1.6 and
'mvn clean install -Daccumulo-1.5' to build with just the
Accumulo 1.5 profile.
I hope that helps explain things. Again, if there's a better
way, I'm happy to hear it.
Cheers,
Jim
* './build/mvn clean install' to try out Zinc. YMMV on
Windows.
On 08/07/2015 05:56 PM, Chris Snider
wrote:
Hi,
I
am working through the final updates for
GeoServer/GeoTools/Scala. I found several tests that fail
on my Windows system due to character encoding and file
paths. I am changing these to be more forgiving with
respect to building in Windows.
One
hiccup I found is the defaulting to Accumulo 1.6.2 version
based on the property “Accumulo-1.5”. I did not see in
the documentation anywhere that this property had to be
set to activate the “Accumulo 1.5” profile. I use
IntelliJ and normally just check the profile check box
when building. However, this activates the “Accumulo 1.6”
profile (since the activation flag is set to
“!accumulo1.5”) as well as the “Accumulo 1.5” profile.
Is
there an issue if I reverse the ordering of the profiles
such that you must specifically turn on Accumulo 1.6 and
defaults to Accumulo 1.5 vice the current default of 1.6
unless you turn on 1.5?
Chris
Snider
Senior
Software Engineer
Intelligent
Software Solutions, Inc.
_______________________________________________
geomesa-dev mailing list
geomesa-dev@xxxxxxxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
http://locationtech.org/mailman/listinfo/geomesa-dev
