Hi Peter, I am not using any IDE to build the project. I just used git bash to pull the project from https://github.com/apache/ctakes to local folder and tried build the project from the root pom.xml
The issue reported by build seems to be something strange. ERROR] Failed to execute goal on project ctakes-core: Could not resolve dependencies for project org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT (absent): org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT was not found in https://repo1.maven.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of nexus has elapsed or updates are forced -> [Help 1] org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal on project ctakes-core: Could not resolve dependencies for project org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT: The following artifacts could not be resolved: org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT (absent): org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT was not found in https://repo1.maven.org/maven2 during a previous attempt. This failure was cached in the local repository and resolution is not reattempted until the update interval of nexus has elapsed or updates are forced. Looks like maven build is expecting "ctakes:ctakes-core-models" in the maven repository and trying to pull the same from remote repo. On Sun, 26 Nov 2023 at 21:19, Peter Abramowitsch <pabramowit...@gmail.com> wrote: > Just a curiosity - Ghandi, are you using Eclipse+Maven? If not, do you > have another IDE wrapped around Maven ? > > > > On Sun, Nov 26, 2023 at 4:43 PM Peter Abramowitsch < > pabramowit...@gmail.com> > wrote: > > > HI Ghandi, > > > > That's one of the fundamental jars that gets built when you start from > the > > top. And if you encounter the error I found, "core" isn't going to be > > built and therefore any succeeding component also dependent on core will > > also fail. Check your build log and see if it doesn't mention the > > "contexttokenizer" > > > > I will be checking in a fix. A bunch of files, in the next day or so. > > > > Peter > > > > On Sun, Nov 26, 2023 at 3:46 PM gandhi rajan <gandhiraja...@gmail.com> > > wrote: > > > >> Hi Peter, > >> > >> I tried building the ctakes project from > https://github.com/apache/ctakes > >> out of curiosity to check on this issue. But I am hitting on a different > >> issue in building ctakes-core module. The error is "Could not resolve > >> dependencies for project > org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT" > >> > >> Am I missing something? Where do I get or build > >> org.apache.ctakes:ctakes-core.jar? > >> > >> On Sun, 26 Nov 2023 at 13:47, Peter Abramowitsch < > pabramowit...@gmail.com > >> > > >> wrote: > >> > >> > About package naming and the context tokenizer, I was quite puzzled as > >> to > >> > why no one had so far complained about the compilation issues in the > Git > >> > Archive which I noticed. > >> > > >> > The issue is that a bunch of the ctakes files refer to a package > >> > > >> > *org.apache.ctakes.* > >> > *contexttokenizer/...* > >> > > >> > when its contents actually live in the folder > >> > > >> > *org/apache/ctakes/context/**tokenizer/....* > >> > > >> > I did some research and discovered something that I hadn't known. > >> > Apparently the Java spec suggests but doesn't enforce that package > names > >> > and folder structure should mirror each other. > >> > > >> > While Eclipse enforces it, some other build environments may not. > This > >> was > >> > reported to the Eclipse team years ago and was assigned "wont-fix" > >> status. > >> > I think I agree with that decision. Since Java's consistency is one of > >> its > >> > great virtues, with class names required to mirror file names, why > allow > >> > fuzzy folder placement of sources? > >> > > >> > In the case of the Git archive for ctakes, the folders are already > >> logical > >> > and "correct", but in some files the package names and imports for the > >> > *context.tokenizer* are mismatching. Since I do use Eclipse, I know > >> that > >> > the context.tokenizer is the only instance of this issue. > >> > > >> > Would anyone mind if I corrected the package names and references to > >> match > >> > the folders? > >> > > >> > Peter > >> > > >> > >> > >> -- > >> Regards, > >> Gandhi > >> > >> "The best way to find urself is to lose urself in the service of others > >> !!!" > >> > > > -- Regards, Gandhi "The best way to find urself is to lose urself in the service of others !!!"
