I can't claim any great familiarity with the codebase (I have only used 
clerezza in downstream projects),
 but it seems the codebase can be built by descending into the 
./jaxrs.rdf.providers directory and then
navigating to the ./rdf directory.

Adding this to the ./pom.xml file does the trick:

<modules>
  <module>parent</module>
  <module>jaxrs.rdf.providers</module>
  <module>rdf</module>
</modules>

However, a lot of the clerezza modules are released independently, so I suspect 
that the lack of a defined <modules>
block has something to do with wanting to exert more control over which modules 
are released at what time.

That said, a more helpful README.txt file wouldn't be amiss here.

Regards,
Aaron


On 11/20/17, 5:41 AM, "Hasan" <[email protected]> wrote:

    We should be able to build the codebase. I think, it is just a missing
    pom.xml file or configuration.
    If no one will fix that in the near future (talking about one or two weeks),
    I tend to support the idea to move Apache Clerezza to Attic.
    
    Regards
    Hasan
    
    
    
    On Sun, Nov 19, 2017 at 2:39 PM, ajs6f <[email protected]> wrote:
    
    > I hate to say it, but if we can't build the codebase (or we don't even
    > know whether we can!) and we can't get advice from anyone who can, then in
    > spite of Hasan's noble attempt to wake up this community, maybe it's time
    > to talk about moving Clerezza to the Apache Attic?
    >
    > ajs6f; Jena PMC
    >
    > > On Nov 14, 2017, at 2:15 PM, Hasan <[email protected]> wrote:
    > >
    > > I think you are right. I experienced the same.
    > >
    > > @Reto, is this intended?
    > >
    > > Cheers
    > > Hasan
    > >
    > >
    > > On Tue, Nov 14, 2017 at 5:37 PM, <[email protected]> wrote:
    > >
    > >> Out of curiosity, I git cloned Clerezza and tried to build it. `mvn
    > >> install` doesn't actually build the code (just the top level project)
    > and
    > >> http://clerezza.apache.org/getting-started/building-clerezza/ is a dead
    > >> link.
    > >>
    > >> Surely we're not expected to manually recurse into the various modules
    > to
    > >> build? I must be missing something...? Or if there is a different
    > context
    > >> within the code base from which to build, shouldn't that be noted on 
the
    > >> main README?
    > >>
    > >>
    > >> ajs6f
    > >>
    >
    >
    

Reply via email to