I really believe that Maven support is a MUST, at least to allow the client to be integrated in other applications.
Right now there are 3 pull requests to implement it:
- Pull 56: Prepare build to upload artifacts to maven central This solution is the easier to implement. Even when is not really making the project Maven compliant, is allowing to make the artifacts available - Pull 57: Fun Projects: Maven support Implemented via Ivy. I don't known how complete is this one, since I have never worked with Ivy. - Pull 71: Project Voldemort Maven Support Is trying to add Maven support, but is missing some features. The contrib is not build, I could not make the tests to be executed properly, ....
Sadly none of them is really solving the issue.
I think I proper plan would be to: 1.- Recheck Pull 56 and if works properly accept it, so the artifact with the client code is available 2.- Modify the code structure to adapt it to the maven layout
Step 1 is easy, step 2 requires quite a lot of work, but before starting the needed changes I wanted to check with the community if this plan is acceptable.
> I really believe that Maven support is a MUST, at least to allow the client
> to be integrated in other applications.
> Right now there are 3 pull requests to implement it:
> - Pull 56: Prepare build to upload artifacts to maven central
> This solution is the easier to implement. Even when is not really making
> the project Maven compliant, is allowing to make the artifacts available
> - Pull 57: Fun Projects: Maven support
> Implemented via Ivy. I don't known how complete is this one, since I
> have never worked with Ivy.
> - Pull 71: Project Voldemort Maven Support
> Is trying to add Maven support, but is missing some features. The
> contrib is not build, I could not make the tests to be executed properly,
> ....
> Sadly none of them is really solving the issue.
> I think I proper plan would be to:
> 1.- Recheck Pull 56 and if works properly accept it, so the artifact with
> the client code is available
> 2.- Modify the code structure to adapt it to the maven layout
> Step 1 is easy, step 2 requires quite a lot of work, but before starting
> the needed changes I wanted to check with the community if this plan is
> acceptable.
On Sunday, September 16, 2012, Timothy Perrett wrote:
> +1, as a new user investigating voldemort not having it available in a
> repository is really, really awkward.
> Thanks,
> Tim
> On Sep 13, 9:35 pm, ctasada <ctas...@gmail.com <javascript:;>> wrote:
> > Hi guys,
> > I really believe that Maven support is a MUST, at least to allow the
> client
> > to be integrated in other applications.
> > Right now there are 3 pull requests to implement it:
> > - Pull 56: Prepare build to upload artifacts to maven central
> > This solution is the easier to implement. Even when is not really
> making
> > the project Maven compliant, is allowing to make the artifacts available
> > - Pull 57: Fun Projects: Maven support
> > Implemented via Ivy. I don't known how complete is this one, since I
> > have never worked with Ivy.
> > - Pull 71: Project Voldemort Maven Support
> > Is trying to add Maven support, but is missing some features. The
> > contrib is not build, I could not make the tests to be executed properly,
> > ....
> > Sadly none of them is really solving the issue.
> > I think I proper plan would be to:
> > 1.- Recheck Pull 56 and if works properly accept it, so the artifact with
> > the client code is available
> > 2.- Modify the code structure to adapt it to the maven layout
> > Step 1 is easy, step 2 requires quite a lot of work, but before starting
> > the needed changes I wanted to check with the community if this plan is
> > acceptable.
I have it working already - the lack of published binaries is just annoying as it means i'll have to publish to my own nexus etc. Nice to see a familiar name here though :-)
On Monday, 17 September 2012 13:28:03 UTC+1, maarten wrote:
> Fellow Lifter :-)
> I use V from Scala and Lift, let me know if you need help!
> --Maarten
> On Sunday, September 16, 2012, Timothy Perrett wrote:
>> +1, as a new user investigating voldemort not having it available in a >> repository is really, really awkward.
>> Thanks,
>> Tim
>> On Sep 13, 9:35 pm, ctasada <ctas...@gmail.com> wrote: >> > Hi guys,
>> > I really believe that Maven support is a MUST, at least to allow the >> client >> > to be integrated in other applications.
>> > Right now there are 3 pull requests to implement it:
>> > - Pull 56: Prepare build to upload artifacts to maven central >> > This solution is the easier to implement. Even when is not really >> making >> > the project Maven compliant, is allowing to make the artifacts available >> > - Pull 57: Fun Projects: Maven support >> > Implemented via Ivy. I don't known how complete is this one, since I >> > have never worked with Ivy. >> > - Pull 71: Project Voldemort Maven Support >> > Is trying to add Maven support, but is missing some features. The >> > contrib is not build, I could not make the tests to be executed >> properly, >> > ....
>> > Sadly none of them is really solving the issue.
>> > I think I proper plan would be to: >> > 1.- Recheck Pull 56 and if works properly accept it, so the artifact >> with >> > the client code is available >> > 2.- Modify the code structure to adapt it to the maven layout
>> > Step 1 is easy, step 2 requires quite a lot of work, but before starting >> > the needed changes I wanted to check with the community if this plan is >> > acceptable.
