You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@ctakes.apache.org by Peter Abramowitsch <pa...@gmail.com> on 2023/11/26 08:17:19 UTC

Compilation Errors and the context.tokenizer

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

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

Hi Ghandi

I am not an expert in these things, but I did notice that I needed to
modify the maven configuration to allow http fetching instead of only
https.  Otherwise I get an error while fetching dependencies and it all
blocks.   Unfortunately slf4j-api comes from a source that has an http
url.
So on my Mac at /usr/local/maven/config/settings.xml  I needed to comment
this out:

   <mirror>
      <id>maven-default-http-blocker</id>
      <mirrorOf>external:http:*</mirrorOf>
      <name>Pseudo repository to mirror external repositories initially
using HTTP.</name>
      <url>http://0.0.0.0/</url>
      <blocked>true</blocked>
    </mirror>



See if that helps.

Once your repository is up to date for this project you can also use mvn
--offline <goal>  to speed things up



On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <ga...@gmail.com>
wrote:

> 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 <pa...@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 <
> > pabramowitsch@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 <ga...@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 <
> > pabramowitsch@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
> !!!"
>

Re: Compilation Errors and the context.tokenizer [EXTERNAL]

Posted by "Finan, Sean" <Se...@childrens.harvard.edu.INVALID>.

Hi guys,

There is supposed to be another way to get around this that doesn't require changes to the maven setting.xml

I checked in the fix back in January and it looks like the change is still present in the main branch.
https://github.com/apache/ctakes/commit/ec37c5948a0abc6dcd278077911db2a651c288f8


The problem as I discovered was:

  1.  maven 3.8 stopped supporting http: links by default - which Peter has noted.
  2.  For some reason maven points to apache builds with the prefix http:  - even though they are actually https:

https://repository.apache.org/content/groups/snapshots/org/apache/ctakes/

Anyway, the change that I made to the main pom has since allowed everybody at boston children's hospital to build without jumping through any hoops.  I suppose that there could be something else that needs to be done.
A different fix/workaround is listed here: https://stackoverflow.com/questions/67001968/how-to-disable-maven-blocking-external-http-repositories

I did not use that solution as it causes greater perturbation and (from our testing) didn't seem to be necessary.

I am glad that the problem's resurgence is being caught now, even though I cannot duplicate it without backing out my previous change.

Sean


________________________________
From: Peter Abramowitsch <pa...@gmail.com>
Sent: Monday, November 27, 2023 7:01 AM
To: dev@ctakes.apache.org <de...@ctakes.apache.org>
Subject: Re: Compilation Errors and the context.tokenizer [EXTERNAL]

* External Email - Caution *


Ghandi,

As I mentioned at the beginning of this thread, there's only one change I
needed to make to the settings.xml:  to comment out the dummy mirror server
that maven uses as a way of enforcing the https requirement.  Commenting it
out allowed maven to fetch slf4j-api.

Since slf4j  is integral to the build, it halted everything.   The error
manifested itself as maven just hanging with a message saying it was trying
to access https://urldefense.com/v3/__http://0.0.0.0__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxuIKXiFw$    I made no other changes and there's nothing
about the settings.xml which is ctakes-specific.

Comment out this part of settings:

    <mirror>
      <id>maven-default-http-blocker</id>
      <mirrorOf>external:http:*</mirrorOf>
      <name>Pseudo repository to mirror external repositories initially
using HTTP.</name>
      <url>https://urldefense.com/v3/__http://0.0.0.0/__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzn8LRPpw$ </url>
      <blocked>true</blocked>
    </mirror>

Have you already tried doing it?

For the model.jars it seems they are just brought to your local maven repo
from maven.apache.org.
Then a goal called unpack-dependencies copies the relevant files into your
build tree.

Generally, if you look very carefully at the maven output, it will tell you
what is the original cause of your error.
Don't just go by what the last output lines are

If this doesn't help,  I'm afraid you'll need to ask someone else who may
be able to ask you better questions about your environment.

Peter

On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <ga...@gmail.com>
wrote:

> Hi Peter,
>
> I did found your old discussion with Sean in the following link -
> https://urldefense.com/v3/__https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxc2xW_0A$
>
> I am facing the same issue while building cakes core module. Could you
> please send me the URL details from your 'settings.xml' under
> '/usr/local/maven/config'
> folder to figure out from which repo you are trying to pull the
> dependencies from during build?
>
> On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Hi Ghandi
> > I did some checking around and sure enough, the resource files are not in
> > the git archive.  I remember a conversation about this from long ago,
> that
> > git wasn't the best place for large binaries.  And they're not in git.
> So
> > I looked in my maven repository to see where my model files had come
> from.
> > Those models and in fact all the resource data for ctakes comes from
> these
> > sources:
> >
> > here's the content of my
> > .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> >
> > _remote.repositories
> > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > m2e-lastUpdated.properties
> > maven-metadata-apache.snapshots.xml
> > maven-metadata-apache.snapshots.xml.sha1
> > resolver-status.properties
> >
> > and here's the content of m2e-lastUpdated.properties
> >
> > #Fri Nov 17 22:03:31 CET 2023
> > apache.snapshots|https\://
> > repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$ >
> > <
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> >
> > apache.snapshots|https\://
> > repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$ >
> > <
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> >
> > central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
> <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$ >
> > <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$ >
> > central|https\://repo.maven.apache.org/maven2|sources=1700255007489
> <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$ >
> > <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$ >
> >
> > I'm not a maven export, but perhaps where you're located (inside an
> > organization?) you cannot access these addresses, or they need to be put
> in
> > a whitelist somewhere?  Sean might know.
> >
> > Sorry about the confusion.  Maven makes things both transparent and
> opaque
> > at the same time.  Most disturbin
> > Peter
> >
> >
> >
> > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <ga...@gmail.com>
> > wrote:
> >
> > > Hi Peter,
> > >
> > > I have pulled the code from main branch and the local copy is clean
> > without
> > > any changes to it. My issue still remains the same. The build is trying
> > to
> > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from the
> > > remote maven repo which its not able to find.
> > >
> > > Complete error trace as follows:
> > >
> > > [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):
> Cannot
> > > access nexus (https://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$ ) in offline mode and the
> > > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has
> not
> > > been downloaded from it before.
> > >
> > >
> > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > pabramowitsch@gmail.com>
> > > wrote:
> > >
> > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you are
> with
> > > git,
> > > > so forgive me if this is obvious
> > > >
> > > >
> > > >
> > > > *$ git statusOn branch mainnothing to commit, working tree clean*
> > > >
> > > > If you've started making changes stash them in a branch and make sure
> > > your
> > > > tree is clean to simplify what you are finding.
> > > >
> > > > Peter
> > > >
> > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > pabramowitsch@gmail.com>
> > > > wrote:
> > > >
> > > > > Nope,  that is not the issue. Those version changes are intentional
> > and
> > > > > necessary.   The core pom and the subsidiary poms have been changed
> > to
> > > > > 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> > > > > compiles and runs fine (I am waiting for permission to check in my
> > > > changes
> > > > > for the context token path issue to help with eclipse building.
> But
> > if
> > > > > you're just using mvn  to build you should be fine.
> > > > >
> > > > > The problem you're having seems to be that maven isn't able to
> fetch
> > > the
> > > > > dependencies you need to build it.
> > > > >
> > > > > From your top level, if you do a *git status* and see that there
> are
> > no
> > > > > modifications or missing files,
> > > > >
> > > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > > dependencies are already present)
> > > > >
> > > > > and send me the output.
> > > > >
> > > > >
> > > > >
> > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > gandhirajan.n@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> hi Peter,
> > > > >>
> > > > >> Thanks for the inputs. But I could see that ctakes-core module's
> > > pom.xml
> > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this
> > is
> > > > >> causing the issue in my case. Please find the pom.xml changes for
> > > > >> your reference:
> > > > >>
> > > > >> *ctakes-core 4.0.1:*
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>org.apache.ctakes</groupId>
> > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > >>  </dependency>
> > > > >>
> > > > >> *ctakes-core 5.0.0:*
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>org.apache.ctakes</groupId>
> > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > >>  <version>${ctakes.models.version}</version>
> > > > >>  </dependency>
> > > > >>
> > > > >> Do u know about the changes Peter by any chance? or only Sean can
> > > throw
> > > > >> some light on these changes?
> > > > >>
> > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > pabramowitsch@gmail.com
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > Hi Ghandi
> > > > >> >
> > > > >> > See how far you get when you built using --offline
> > > > >> >
> > > > >> > Peter
> > > > >> >
> > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > gandhirajan.n@gmail.com
> > > > >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Hi Peter,
> > > > >> > >
> > > > >> > > I am not using any IDE to build the project. I just used git
> > bash
> > > to
> > > > >> pull
> > > > >> > > the project from https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$  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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$  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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$  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 <
> > > > >> > pabramowitsch@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 <
> > > > >> > > > pabramowitsch@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 <
> > > > >> > gandhirajan.n@gmail.com>
> > > > >> > > > > wrote:
> > > > >> > > > >
> > > > >> > > > >> Hi Peter,
> > > > >> > > > >>
> > > > >> > > > >> I tried building the ctakes project from
> > > > >> > > > https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > >> > > > >> 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 <
> > > > >> > > > pabramowitsch@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
> > > > >> > > !!!"
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >> 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
> > > !!!"
> > >
> >
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>

Re: Compilation Errors and the context.tokenizer [EXTERNAL]

Posted by gandhi rajan <ga...@gmail.com>.

Hi Peter,

I did a quick check and I was able to compile the ctakes-core module by
switching the repo url from "https://repo1.maven.org/maven2" to "
https://repository.apache.org/content/groups/snapshots",  pull the core
models jar and switch back the repo url to "https://repo1.maven.org/maven2"

I guess you or Sean may not hit this issue as the required artifacts are
already available in your. m2 local repo. A fresh install on a new machine
may help simulating this issue.

On Tue, 28 Nov 2023 at 22:41, Peter Abramowitsch <pa...@gmail.com>
wrote:

> Hi Gandhi
>
> I checked in the various changes that helped me get it to compile
> properly.  I checked my maven settings and there are no repositories
> mentioned - I.e. it is running completely on its defaults.  Have you tried
> removing the entry you mentioned in your email rather than trying to add to
> or change your existing ones?
>
> Peter
>
> On Mon, Nov 27, 2023 at 5:45 PM gandhi rajan <ga...@gmail.com>
> wrote:
>
> > Hi Sean/Peter,
> >
> > Thanks for the insights. As Sean mentioned, I do have the root pom.xml
> > changes in my codebase as well. But in my settings.xml file, I have
> > mentioned the maven repo as "https://repo1.maven.org/maven2" and the
> > maven build is trying to fetch
> > " org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT" from that repo
> > where its not available obviously. The repository settings changes in
> > pom.xml doesnt seems to be working in my case.
> >
> > But "https://repository.apache.org/content/groups/snapshots/" is the
> only
> > repo where I could find the missing jars the build is looking for. I can
> > probably work around this problem by referring this link in settings.xml
> > but will that be feasible is my point?
> >
> > On Mon, 27 Nov 2023 at 21:24, Peter Abramowitsch <
> pabramowitsch@gmail.com>
> > wrote:
> >
> > > Thanks Sean.  Could be that slf4j is available from two sites, one of
> > them
> > > still on http and for whatever reason it is coming up first.
> > > I'm not sure though whether all this is the same as the problem Gandhi
> > has
> > > been having.  Let's see what e says.
> > >
> > > - Peter
> > >
> > > On Mon, Nov 27, 2023 at 4:43 PM Finan, Sean
> > > <Se...@childrens.harvard.edu.invalid> wrote:
> > >
> > > > As for slf4j being on http:, I don't know that I ever saw that.  If
> you
> > > > check maven central it is actually https:
> > > >
> > > > https://repo1.maven.org/maven2/org/slf4j/
> > > >
> > > > As referred to here:
> > > > https://mvnrepository.com/artifact/org.slf4j/slf4j-api/2.0.5
> > > >
> > > > I will do some more research on this tonight, though I welcome people
> > to
> > > > beat me to a solution!
> > > >
> > > > Sean
> > > >
> > > > ________________________________
> > > > From: Peter Abramowitsch <pa...@gmail.com>
> > > > Sent: Monday, November 27, 2023 7:01 AM
> > > > To: dev@ctakes.apache.org <de...@ctakes.apache.org>
> > > > Subject: Re: Compilation Errors and the context.tokenizer [EXTERNAL]
> > > >
> > > > * External Email - Caution *
> > > >
> > > >
> > > > Ghandi,
> > > >
> > > > As I mentioned at the beginning of this thread, there's only one
> > change I
> > > > needed to make to the settings.xml:  to comment out the dummy mirror
> > > server
> > > > that maven uses as a way of enforcing the https requirement.
> > Commenting
> > > it
> > > > out allowed maven to fetch slf4j-api.
> > > >
> > > > Since slf4j  is integral to the build, it halted everything.   The
> > error
> > > > manifested itself as maven just hanging with a message saying it was
> > > trying
> > > > to access
> > > >
> > >
> >
> https://urldefense.com/v3/__http://0.0.0.0__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxuIKXiFw$
> > > >   I made no other changes and there's nothing
> > > > about the settings.xml which is ctakes-specific.
> > > >
> > > > Comment out this part of settings:
> > > >
> > > >     <mirror>
> > > >       <id>maven-default-http-blocker</id>
> > > >       <mirrorOf>external:http:*</mirrorOf>
> > > >       <name>Pseudo repository to mirror external repositories
> initially
> > > > using HTTP.</name>
> > > >       <url>
> > > >
> > >
> >
> https://urldefense.com/v3/__http://0.0.0.0/__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzn8LRPpw$
> > > > </url>
> > > >       <blocked>true</blocked>
> > > >     </mirror>
> > > >
> > > > Have you already tried doing it?
> > > >
> > > > For the model.jars it seems they are just brought to your local maven
> > > repo
> > > > from maven.apache.org.
> > > > Then a goal called unpack-dependencies copies the relevant files into
> > > your
> > > > build tree.
> > > >
> > > > Generally, if you look very carefully at the maven output, it will
> tell
> > > you
> > > > what is the original cause of your error.
> > > > Don't just go by what the last output lines are
> > > >
> > > > If this doesn't help,  I'm afraid you'll need to ask someone else who
> > may
> > > > be able to ask you better questions about your environment.
> > > >
> > > > Peter
> > > >
> > > > On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <
> gandhirajan.n@gmail.com
> > >
> > > > wrote:
> > > >
> > > > > Hi Peter,
> > > > >
> > > > > I did found your old discussion with Sean in the following link -
> > > > >
> > > >
> > >
> >
> https://urldefense.com/v3/__https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxc2xW_0A$
> > > > >
> > > > > I am facing the same issue while building cakes core module. Could
> > you
> > > > > please send me the URL details from your 'settings.xml' under
> > > > > '/usr/local/maven/config'
> > > > > folder to figure out from which repo you are trying to pull the
> > > > > dependencies from during build?
> > > > >
> > > > > On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <
> > > > pabramowitsch@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Ghandi
> > > > > > I did some checking around and sure enough, the resource files
> are
> > > not
> > > > in
> > > > > > the git archive.  I remember a conversation about this from long
> > ago,
> > > > > that
> > > > > > git wasn't the best place for large binaries.  And they're not in
> > > git.
> > > > > So
> > > > > > I looked in my maven repository to see where my model files had
> > come
> > > > > from.
> > > > > > Those models and in fact all the resource data for ctakes comes
> > from
> > > > > these
> > > > > > sources:
> > > > > >
> > > > > > here's the content of my
> > > > > >
> .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> > > > > >
> > > > > > _remote.repositories
> > > > > > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > > > > > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > > > > > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > > > > > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > > > > > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > > > > > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > > > > > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > > > > > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > > > > > m2e-lastUpdated.properties
> > > > > > maven-metadata-apache.snapshots.xml
> > > > > > maven-metadata-apache.snapshots.xml.sha1
> > > > > > resolver-status.properties
> > > > > >
> > > > > > and here's the content of m2e-lastUpdated.properties
> > > > > >
> > > > > > #Fri Nov 17 22:03:31 CET 2023
> > > > > > apache.snapshots|https\://
> > > > > >
> > > repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> >
> > > <
> >
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> > >
> > > > <
> > >
> >
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> > > >
> > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > > > >
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > > > > >
> > > > > > apache.snapshots|https\://
> > > > > >
> > > repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> >
> > > <
> >
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> > >
> > > > <
> > >
> >
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> > > >
> > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > > > >
> > > > > > <
> > > > >
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > > > > >
> > > > > > central|https\://
> > repo.maven.apache.org/maven2|javadoc=1700255011056
> <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > > > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> > > > >
> > > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> > > > >
> > > > > > central|https\://
> > repo.maven.apache.org/maven2|sources=1700255007489
> <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > > > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> > > > >
> > > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> > > > >
> > > > > >
> > > > > > I'm not a maven export, but perhaps where you're located (inside
> an
> > > > > > organization?) you cannot access these addresses, or they need to
> > be
> > > > put
> > > > > in
> > > > > > a whitelist somewhere?  Sean might know.
> > > > > >
> > > > > > Sorry about the confusion.  Maven makes things both transparent
> and
> > > > > opaque
> > > > > > at the same time.  Most disturbin
> > > > > > Peter
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <
> > > gandhirajan.n@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Peter,
> > > > > > >
> > > > > > > I have pulled the code from main branch and the local copy is
> > clean
> > > > > > without
> > > > > > > any changes to it. My issue still remains the same. The build
> is
> > > > trying
> > > > > > to
> > > > > > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar
> > from
> > > > the
> > > > > > > remote maven repo which its not able to find.
> > > > > > >
> > > > > > > Complete error trace as follows:
> > > > > > >
> > > > > > > [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):
> > > > > Cannot
> > > > > > > access nexus (
> > > >
> > >
> >
> https://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > > > ) in offline mode and the
> > > > > > > artifact
> org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT
> > > has
> > > > > not
> > > > > > > been downloaded from it before.
> > > > > > >
> > > > > > >
> > > > > > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > > > > > pabramowitsch@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you
> > are
> > > > > with
> > > > > > > git,
> > > > > > > > so forgive me if this is obvious
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > *$ git statusOn branch mainnothing to commit, working tree
> > clean*
> > > > > > > >
> > > > > > > > If you've started making changes stash them in a branch and
> > make
> > > > sure
> > > > > > > your
> > > > > > > > tree is clean to simplify what you are finding.
> > > > > > > >
> > > > > > > > Peter
> > > > > > > >
> > > > > > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > > > > > pabramowitsch@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Nope,  that is not the issue. Those version changes are
> > > > intentional
> > > > > > and
> > > > > > > > > necessary.   The core pom and the subsidiary poms have been
> > > > changed
> > > > > > to
> > > > > > > > > 5.0.0-SNAPSHOT as well because this is a new release.
>  For
> > > me
> > > > it
> > > > > > > > > compiles and runs fine (I am waiting for permission to
> check
> > in
> > > > my
> > > > > > > > changes
> > > > > > > > > for the context token path issue to help with eclipse
> > building.
> > > > > But
> > > > > > if
> > > > > > > > > you're just using mvn  to build you should be fine.
> > > > > > > > >
> > > > > > > > > The problem you're having seems to be that maven isn't able
> > to
> > > > > fetch
> > > > > > > the
> > > > > > > > > dependencies you need to build it.
> > > > > > > > >
> > > > > > > > > From your top level, if you do a *git status* and see that
> > > there
> > > > > are
> > > > > > no
> > > > > > > > > modifications or missing files,
> > > > > > > > >
> > > > > > > > > then try:    *mvn --offline package*  (to see if the
> relevant
> > > > > > > > > dependencies are already present)
> > > > > > > > >
> > > > > > > > > and send me the output.
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > > > > > gandhirajan.n@gmail.com>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > >> hi Peter,
> > > > > > > > >>
> > > > > > > > >> Thanks for the inputs. But I could see that ctakes-core
> > > module's
> > > > > > > pom.xml
> > > > > > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I
> > guess
> > > > this
> > > > > > is
> > > > > > > > >> causing the issue in my case. Please find the pom.xml
> > changes
> > > > for
> > > > > > > > >> your reference:
> > > > > > > > >>
> > > > > > > > >> *ctakes-core 4.0.1:*
> > > > > > > > >>
> > > > > > > > >> <dependency>
> > > > > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > > > > > >>  </dependency>
> > > > > > > > >>
> > > > > > > > >> *ctakes-core 5.0.0:*
> > > > > > > > >>
> > > > > > > > >> <dependency>
> > > > > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > > > > > >>  <version>${ctakes.models.version}</version>
> > > > > > > > >>  </dependency>
> > > > > > > > >>
> > > > > > > > >> Do u know about the changes Peter by any chance? or only
> > Sean
> > > > can
> > > > > > > throw
> > > > > > > > >> some light on these changes?
> > > > > > > > >>
> > > > > > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > > > > > pabramowitsch@gmail.com
> > > > > > > > >> >
> > > > > > > > >> wrote:
> > > > > > > > >>
> > > > > > > > >> > Hi Ghandi
> > > > > > > > >> >
> > > > > > > > >> > See how far you get when you built using --offline
> > > > > > > > >> >
> > > > > > > > >> > Peter
> > > > > > > > >> >
> > > > > > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > > > > > gandhirajan.n@gmail.com
> > > > > > > > >
> > > > > > > > >> > wrote:
> > > > > > > > >> >
> > > > > > > > >> > > Hi Peter,
> > > > > > > > >> > >
> > > > > > > > >> > > I am not using any IDE to build the project. I just
> used
> > > git
> > > > > > bash
> > > > > > > to
> > > > > > > > >> pull
> > > > > > > > >> > > the project from
> > > >
> > >
> >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > > > 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > > > 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 <
> > > > > > > > >> > pabramowitsch@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 <
> > > > > > > > >> > > > pabramowitsch@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 <
> > > > > > > > >> > gandhirajan.n@gmail.com>
> > > > > > > > >> > > > > wrote:
> > > > > > > > >> > > > >
> > > > > > > > >> > > > >> Hi Peter,
> > > > > > > > >> > > > >>
> > > > > > > > >> > > > >> I tried building the ctakes project from
> > > > > > > > >> > > >
> > > >
> > >
> >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > > > > > >> > > > >> 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
> <
> > > > > > > > >> > > > pabramowitsch@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
> > > > > > > > >> > > !!!"
> > > > > > > > >> > >
> > > > > > > > >> >
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> --
> > > > > > > > >> 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
> > > > > > > !!!"
> > > > > > >
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > 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
> > !!!"
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Compilation Errors and the context.tokenizer [EXTERNAL]

Posted by Peter Abramowitsch <pa...@gmail.com>.

Hi Gandhi

I checked in the various changes that helped me get it to compile
properly.  I checked my maven settings and there are no repositories
mentioned - I.e. it is running completely on its defaults.  Have you tried
removing the entry you mentioned in your email rather than trying to add to
or change your existing ones?

Peter

On Mon, Nov 27, 2023 at 5:45 PM gandhi rajan <ga...@gmail.com>
wrote:

> Hi Sean/Peter,
>
> Thanks for the insights. As Sean mentioned, I do have the root pom.xml
> changes in my codebase as well. But in my settings.xml file, I have
> mentioned the maven repo as "https://repo1.maven.org/maven2" and the
> maven build is trying to fetch
> " org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT" from that repo
> where its not available obviously. The repository settings changes in
> pom.xml doesnt seems to be working in my case.
>
> But "https://repository.apache.org/content/groups/snapshots/" is the only
> repo where I could find the missing jars the build is looking for. I can
> probably work around this problem by referring this link in settings.xml
> but will that be feasible is my point?
>
> On Mon, 27 Nov 2023 at 21:24, Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Thanks Sean.  Could be that slf4j is available from two sites, one of
> them
> > still on http and for whatever reason it is coming up first.
> > I'm not sure though whether all this is the same as the problem Gandhi
> has
> > been having.  Let's see what e says.
> >
> > - Peter
> >
> > On Mon, Nov 27, 2023 at 4:43 PM Finan, Sean
> > <Se...@childrens.harvard.edu.invalid> wrote:
> >
> > > As for slf4j being on http:, I don't know that I ever saw that.  If you
> > > check maven central it is actually https:
> > >
> > > https://repo1.maven.org/maven2/org/slf4j/
> > >
> > > As referred to here:
> > > https://mvnrepository.com/artifact/org.slf4j/slf4j-api/2.0.5
> > >
> > > I will do some more research on this tonight, though I welcome people
> to
> > > beat me to a solution!
> > >
> > > Sean
> > >
> > > ________________________________
> > > From: Peter Abramowitsch <pa...@gmail.com>
> > > Sent: Monday, November 27, 2023 7:01 AM
> > > To: dev@ctakes.apache.org <de...@ctakes.apache.org>
> > > Subject: Re: Compilation Errors and the context.tokenizer [EXTERNAL]
> > >
> > > * External Email - Caution *
> > >
> > >
> > > Ghandi,
> > >
> > > As I mentioned at the beginning of this thread, there's only one
> change I
> > > needed to make to the settings.xml:  to comment out the dummy mirror
> > server
> > > that maven uses as a way of enforcing the https requirement.
> Commenting
> > it
> > > out allowed maven to fetch slf4j-api.
> > >
> > > Since slf4j  is integral to the build, it halted everything.   The
> error
> > > manifested itself as maven just hanging with a message saying it was
> > trying
> > > to access
> > >
> >
> https://urldefense.com/v3/__http://0.0.0.0__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxuIKXiFw$
> > >   I made no other changes and there's nothing
> > > about the settings.xml which is ctakes-specific.
> > >
> > > Comment out this part of settings:
> > >
> > >     <mirror>
> > >       <id>maven-default-http-blocker</id>
> > >       <mirrorOf>external:http:*</mirrorOf>
> > >       <name>Pseudo repository to mirror external repositories initially
> > > using HTTP.</name>
> > >       <url>
> > >
> >
> https://urldefense.com/v3/__http://0.0.0.0/__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzn8LRPpw$
> > > </url>
> > >       <blocked>true</blocked>
> > >     </mirror>
> > >
> > > Have you already tried doing it?
> > >
> > > For the model.jars it seems they are just brought to your local maven
> > repo
> > > from maven.apache.org.
> > > Then a goal called unpack-dependencies copies the relevant files into
> > your
> > > build tree.
> > >
> > > Generally, if you look very carefully at the maven output, it will tell
> > you
> > > what is the original cause of your error.
> > > Don't just go by what the last output lines are
> > >
> > > If this doesn't help,  I'm afraid you'll need to ask someone else who
> may
> > > be able to ask you better questions about your environment.
> > >
> > > Peter
> > >
> > > On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <gandhirajan.n@gmail.com
> >
> > > wrote:
> > >
> > > > Hi Peter,
> > > >
> > > > I did found your old discussion with Sean in the following link -
> > > >
> > >
> >
> https://urldefense.com/v3/__https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxc2xW_0A$
> > > >
> > > > I am facing the same issue while building cakes core module. Could
> you
> > > > please send me the URL details from your 'settings.xml' under
> > > > '/usr/local/maven/config'
> > > > folder to figure out from which repo you are trying to pull the
> > > > dependencies from during build?
> > > >
> > > > On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <
> > > pabramowitsch@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Ghandi
> > > > > I did some checking around and sure enough, the resource files are
> > not
> > > in
> > > > > the git archive.  I remember a conversation about this from long
> ago,
> > > > that
> > > > > git wasn't the best place for large binaries.  And they're not in
> > git.
> > > > So
> > > > > I looked in my maven repository to see where my model files had
> come
> > > > from.
> > > > > Those models and in fact all the resource data for ctakes comes
> from
> > > > these
> > > > > sources:
> > > > >
> > > > > here's the content of my
> > > > > .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> > > > >
> > > > > _remote.repositories
> > > > > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > > > > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > > > > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > > > > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > > > > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > > > > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > > > > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > > > > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > > > > m2e-lastUpdated.properties
> > > > > maven-metadata-apache.snapshots.xml
> > > > > maven-metadata-apache.snapshots.xml.sha1
> > > > > resolver-status.properties
> > > > >
> > > > > and here's the content of m2e-lastUpdated.properties
> > > > >
> > > > > #Fri Nov 17 22:03:31 CET 2023
> > > > > apache.snapshots|https\://
> > > > >
> > repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> >
> > > <
> >
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> > >
> > > > <
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > > >
> > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > > > >
> > > > > apache.snapshots|https\://
> > > > >
> > repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> >
> > > <
> >
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> > >
> > > > <
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > > >
> > > > > <
> > > >
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > > > >
> > > > > central|https\://
> repo.maven.apache.org/maven2|javadoc=1700255011056
> <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > > > <
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> > > >
> > > > > <
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> > > >
> > > > > central|https\://
> repo.maven.apache.org/maven2|sources=1700255007489
> <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > > > <
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> > > >
> > > > > <
> > >
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> > > >
> > > > >
> > > > > I'm not a maven export, but perhaps where you're located (inside an
> > > > > organization?) you cannot access these addresses, or they need to
> be
> > > put
> > > > in
> > > > > a whitelist somewhere?  Sean might know.
> > > > >
> > > > > Sorry about the confusion.  Maven makes things both transparent and
> > > > opaque
> > > > > at the same time.  Most disturbin
> > > > > Peter
> > > > >
> > > > >
> > > > >
> > > > > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <
> > gandhirajan.n@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Hi Peter,
> > > > > >
> > > > > > I have pulled the code from main branch and the local copy is
> clean
> > > > > without
> > > > > > any changes to it. My issue still remains the same. The build is
> > > trying
> > > > > to
> > > > > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar
> from
> > > the
> > > > > > remote maven repo which its not able to find.
> > > > > >
> > > > > > Complete error trace as follows:
> > > > > >
> > > > > > [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):
> > > > Cannot
> > > > > > access nexus (
> > >
> >
> https://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > > ) in offline mode and the
> > > > > > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT
> > has
> > > > not
> > > > > > been downloaded from it before.
> > > > > >
> > > > > >
> > > > > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > > > > pabramowitsch@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you
> are
> > > > with
> > > > > > git,
> > > > > > > so forgive me if this is obvious
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > *$ git statusOn branch mainnothing to commit, working tree
> clean*
> > > > > > >
> > > > > > > If you've started making changes stash them in a branch and
> make
> > > sure
> > > > > > your
> > > > > > > tree is clean to simplify what you are finding.
> > > > > > >
> > > > > > > Peter
> > > > > > >
> > > > > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > > > > pabramowitsch@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Nope,  that is not the issue. Those version changes are
> > > intentional
> > > > > and
> > > > > > > > necessary.   The core pom and the subsidiary poms have been
> > > changed
> > > > > to
> > > > > > > > 5.0.0-SNAPSHOT as well because this is a new release.     For
> > me
> > > it
> > > > > > > > compiles and runs fine (I am waiting for permission to check
> in
> > > my
> > > > > > > changes
> > > > > > > > for the context token path issue to help with eclipse
> building.
> > > > But
> > > > > if
> > > > > > > > you're just using mvn  to build you should be fine.
> > > > > > > >
> > > > > > > > The problem you're having seems to be that maven isn't able
> to
> > > > fetch
> > > > > > the
> > > > > > > > dependencies you need to build it.
> > > > > > > >
> > > > > > > > From your top level, if you do a *git status* and see that
> > there
> > > > are
> > > > > no
> > > > > > > > modifications or missing files,
> > > > > > > >
> > > > > > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > > > > > dependencies are already present)
> > > > > > > >
> > > > > > > > and send me the output.
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > > > > gandhirajan.n@gmail.com>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > >> hi Peter,
> > > > > > > >>
> > > > > > > >> Thanks for the inputs. But I could see that ctakes-core
> > module's
> > > > > > pom.xml
> > > > > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I
> guess
> > > this
> > > > > is
> > > > > > > >> causing the issue in my case. Please find the pom.xml
> changes
> > > for
> > > > > > > >> your reference:
> > > > > > > >>
> > > > > > > >> *ctakes-core 4.0.1:*
> > > > > > > >>
> > > > > > > >> <dependency>
> > > > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > > > > >>  </dependency>
> > > > > > > >>
> > > > > > > >> *ctakes-core 5.0.0:*
> > > > > > > >>
> > > > > > > >> <dependency>
> > > > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > > > > >>  <version>${ctakes.models.version}</version>
> > > > > > > >>  </dependency>
> > > > > > > >>
> > > > > > > >> Do u know about the changes Peter by any chance? or only
> Sean
> > > can
> > > > > > throw
> > > > > > > >> some light on these changes?
> > > > > > > >>
> > > > > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > > > > pabramowitsch@gmail.com
> > > > > > > >> >
> > > > > > > >> wrote:
> > > > > > > >>
> > > > > > > >> > Hi Ghandi
> > > > > > > >> >
> > > > > > > >> > See how far you get when you built using --offline
> > > > > > > >> >
> > > > > > > >> > Peter
> > > > > > > >> >
> > > > > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > > > > gandhirajan.n@gmail.com
> > > > > > > >
> > > > > > > >> > wrote:
> > > > > > > >> >
> > > > > > > >> > > Hi Peter,
> > > > > > > >> > >
> > > > > > > >> > > I am not using any IDE to build the project. I just used
> > git
> > > > > bash
> > > > > > to
> > > > > > > >> pull
> > > > > > > >> > > the project from
> > >
> >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > > 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > > 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 <
> > > > > > > >> > pabramowitsch@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 <
> > > > > > > >> > > > pabramowitsch@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 <
> > > > > > > >> > gandhirajan.n@gmail.com>
> > > > > > > >> > > > > wrote:
> > > > > > > >> > > > >
> > > > > > > >> > > > >> Hi Peter,
> > > > > > > >> > > > >>
> > > > > > > >> > > > >> I tried building the ctakes project from
> > > > > > > >> > > >
> > >
> >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > > > > >> > > > >> 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 <
> > > > > > > >> > > > pabramowitsch@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
> > > > > > > >> > > !!!"
> > > > > > > >> > >
> > > > > > > >> >
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >> 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
> > > > > > !!!"
> > > > > >
> > > > >
> > > >
> > > >
> > > > --
> > > > 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
> !!!"
>

Re: Compilation Errors and the context.tokenizer [EXTERNAL]

Posted by gandhi rajan <ga...@gmail.com>.

Hi Sean/Peter,

Thanks for the insights. As Sean mentioned, I do have the root pom.xml
changes in my codebase as well. But in my settings.xml file, I have
mentioned the maven repo as "https://repo1.maven.org/maven2" and the
maven build is trying to fetch
" org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT" from that repo
where its not available obviously. The repository settings changes in
pom.xml doesnt seems to be working in my case.

But "https://repository.apache.org/content/groups/snapshots/" is the only
repo where I could find the missing jars the build is looking for. I can
probably work around this problem by referring this link in settings.xml
but will that be feasible is my point?

On Mon, 27 Nov 2023 at 21:24, Peter Abramowitsch <pa...@gmail.com>
wrote:

> Thanks Sean.  Could be that slf4j is available from two sites, one of them
> still on http and for whatever reason it is coming up first.
> I'm not sure though whether all this is the same as the problem Gandhi has
> been having.  Let's see what e says.
>
> - Peter
>
> On Mon, Nov 27, 2023 at 4:43 PM Finan, Sean
> <Se...@childrens.harvard.edu.invalid> wrote:
>
> > As for slf4j being on http:, I don't know that I ever saw that.  If you
> > check maven central it is actually https:
> >
> > https://repo1.maven.org/maven2/org/slf4j/
> >
> > As referred to here:
> > https://mvnrepository.com/artifact/org.slf4j/slf4j-api/2.0.5
> >
> > I will do some more research on this tonight, though I welcome people to
> > beat me to a solution!
> >
> > Sean
> >
> > ________________________________
> > From: Peter Abramowitsch <pa...@gmail.com>
> > Sent: Monday, November 27, 2023 7:01 AM
> > To: dev@ctakes.apache.org <de...@ctakes.apache.org>
> > Subject: Re: Compilation Errors and the context.tokenizer [EXTERNAL]
> >
> > * External Email - Caution *
> >
> >
> > Ghandi,
> >
> > As I mentioned at the beginning of this thread, there's only one change I
> > needed to make to the settings.xml:  to comment out the dummy mirror
> server
> > that maven uses as a way of enforcing the https requirement.  Commenting
> it
> > out allowed maven to fetch slf4j-api.
> >
> > Since slf4j  is integral to the build, it halted everything.   The error
> > manifested itself as maven just hanging with a message saying it was
> trying
> > to access
> >
> https://urldefense.com/v3/__http://0.0.0.0__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxuIKXiFw$
> >   I made no other changes and there's nothing
> > about the settings.xml which is ctakes-specific.
> >
> > Comment out this part of settings:
> >
> >     <mirror>
> >       <id>maven-default-http-blocker</id>
> >       <mirrorOf>external:http:*</mirrorOf>
> >       <name>Pseudo repository to mirror external repositories initially
> > using HTTP.</name>
> >       <url>
> >
> https://urldefense.com/v3/__http://0.0.0.0/__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzn8LRPpw$
> > </url>
> >       <blocked>true</blocked>
> >     </mirror>
> >
> > Have you already tried doing it?
> >
> > For the model.jars it seems they are just brought to your local maven
> repo
> > from maven.apache.org.
> > Then a goal called unpack-dependencies copies the relevant files into
> your
> > build tree.
> >
> > Generally, if you look very carefully at the maven output, it will tell
> you
> > what is the original cause of your error.
> > Don't just go by what the last output lines are
> >
> > If this doesn't help,  I'm afraid you'll need to ask someone else who may
> > be able to ask you better questions about your environment.
> >
> > Peter
> >
> > On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <ga...@gmail.com>
> > wrote:
> >
> > > Hi Peter,
> > >
> > > I did found your old discussion with Sean in the following link -
> > >
> >
> https://urldefense.com/v3/__https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxc2xW_0A$
> > >
> > > I am facing the same issue while building cakes core module. Could you
> > > please send me the URL details from your 'settings.xml' under
> > > '/usr/local/maven/config'
> > > folder to figure out from which repo you are trying to pull the
> > > dependencies from during build?
> > >
> > > On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <
> > pabramowitsch@gmail.com>
> > > wrote:
> > >
> > > > Hi Ghandi
> > > > I did some checking around and sure enough, the resource files are
> not
> > in
> > > > the git archive.  I remember a conversation about this from long ago,
> > > that
> > > > git wasn't the best place for large binaries.  And they're not in
> git.
> > > So
> > > > I looked in my maven repository to see where my model files had come
> > > from.
> > > > Those models and in fact all the resource data for ctakes comes from
> > > these
> > > > sources:
> > > >
> > > > here's the content of my
> > > > .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> > > >
> > > > _remote.repositories
> > > > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > > > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > > > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > > > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > > > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > > > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > > > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > > > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > > > m2e-lastUpdated.properties
> > > > maven-metadata-apache.snapshots.xml
> > > > maven-metadata-apache.snapshots.xml.sha1
> > > > resolver-status.properties
> > > >
> > > > and here's the content of m2e-lastUpdated.properties
> > > >
> > > > #Fri Nov 17 22:03:31 CET 2023
> > > > apache.snapshots|https\://
> > > >
> repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> >
> > > <
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > >
> > > > <
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > > >
> > > > apache.snapshots|https\://
> > > >
> repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> >
> > > <
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > >
> > > > <
> > >
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > > >
> > > > central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
> <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > > <
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> > >
> > > > <
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> > >
> > > > central|https\://repo.maven.apache.org/maven2|sources=1700255007489
> <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > > <
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> > >
> > > > <
> >
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> > >
> > > >
> > > > I'm not a maven export, but perhaps where you're located (inside an
> > > > organization?) you cannot access these addresses, or they need to be
> > put
> > > in
> > > > a whitelist somewhere?  Sean might know.
> > > >
> > > > Sorry about the confusion.  Maven makes things both transparent and
> > > opaque
> > > > at the same time.  Most disturbin
> > > > Peter
> > > >
> > > >
> > > >
> > > > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <
> gandhirajan.n@gmail.com>
> > > > wrote:
> > > >
> > > > > Hi Peter,
> > > > >
> > > > > I have pulled the code from main branch and the local copy is clean
> > > > without
> > > > > any changes to it. My issue still remains the same. The build is
> > trying
> > > > to
> > > > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from
> > the
> > > > > remote maven repo which its not able to find.
> > > > >
> > > > > Complete error trace as follows:
> > > > >
> > > > > [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):
> > > Cannot
> > > > > access nexus (
> >
> https://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > ) in offline mode and the
> > > > > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT
> has
> > > not
> > > > > been downloaded from it before.
> > > > >
> > > > >
> > > > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > > > pabramowitsch@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you are
> > > with
> > > > > git,
> > > > > > so forgive me if this is obvious
> > > > > >
> > > > > >
> > > > > >
> > > > > > *$ git statusOn branch mainnothing to commit, working tree clean*
> > > > > >
> > > > > > If you've started making changes stash them in a branch and make
> > sure
> > > > > your
> > > > > > tree is clean to simplify what you are finding.
> > > > > >
> > > > > > Peter
> > > > > >
> > > > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > > > pabramowitsch@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > > > Nope,  that is not the issue. Those version changes are
> > intentional
> > > > and
> > > > > > > necessary.   The core pom and the subsidiary poms have been
> > changed
> > > > to
> > > > > > > 5.0.0-SNAPSHOT as well because this is a new release.     For
> me
> > it
> > > > > > > compiles and runs fine (I am waiting for permission to check in
> > my
> > > > > > changes
> > > > > > > for the context token path issue to help with eclipse building.
> > > But
> > > > if
> > > > > > > you're just using mvn  to build you should be fine.
> > > > > > >
> > > > > > > The problem you're having seems to be that maven isn't able to
> > > fetch
> > > > > the
> > > > > > > dependencies you need to build it.
> > > > > > >
> > > > > > > From your top level, if you do a *git status* and see that
> there
> > > are
> > > > no
> > > > > > > modifications or missing files,
> > > > > > >
> > > > > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > > > > dependencies are already present)
> > > > > > >
> > > > > > > and send me the output.
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > > > gandhirajan.n@gmail.com>
> > > > > > > wrote:
> > > > > > >
> > > > > > >> hi Peter,
> > > > > > >>
> > > > > > >> Thanks for the inputs. But I could see that ctakes-core
> module's
> > > > > pom.xml
> > > > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess
> > this
> > > > is
> > > > > > >> causing the issue in my case. Please find the pom.xml changes
> > for
> > > > > > >> your reference:
> > > > > > >>
> > > > > > >> *ctakes-core 4.0.1:*
> > > > > > >>
> > > > > > >> <dependency>
> > > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > > > >>  </dependency>
> > > > > > >>
> > > > > > >> *ctakes-core 5.0.0:*
> > > > > > >>
> > > > > > >> <dependency>
> > > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > > > >>  <version>${ctakes.models.version}</version>
> > > > > > >>  </dependency>
> > > > > > >>
> > > > > > >> Do u know about the changes Peter by any chance? or only Sean
> > can
> > > > > throw
> > > > > > >> some light on these changes?
> > > > > > >>
> > > > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > > > pabramowitsch@gmail.com
> > > > > > >> >
> > > > > > >> wrote:
> > > > > > >>
> > > > > > >> > Hi Ghandi
> > > > > > >> >
> > > > > > >> > See how far you get when you built using --offline
> > > > > > >> >
> > > > > > >> > Peter
> > > > > > >> >
> > > > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > > > gandhirajan.n@gmail.com
> > > > > > >
> > > > > > >> > wrote:
> > > > > > >> >
> > > > > > >> > > Hi Peter,
> > > > > > >> > >
> > > > > > >> > > I am not using any IDE to build the project. I just used
> git
> > > > bash
> > > > > to
> > > > > > >> pull
> > > > > > >> > > the project from
> >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> > 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 <
> > > > > > >> > pabramowitsch@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 <
> > > > > > >> > > > pabramowitsch@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 <
> > > > > > >> > gandhirajan.n@gmail.com>
> > > > > > >> > > > > wrote:
> > > > > > >> > > > >
> > > > > > >> > > > >> Hi Peter,
> > > > > > >> > > > >>
> > > > > > >> > > > >> I tried building the ctakes project from
> > > > > > >> > > >
> >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > > > >> > > > >> 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 <
> > > > > > >> > > > pabramowitsch@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
> > > > > > >> > > !!!"
> > > > > > >> > >
> > > > > > >> >
> > > > > > >>
> > > > > > >>
> > > > > > >> --
> > > > > > >> 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
> > > > > !!!"
> > > > >
> > > >
> > >
> > >
> > > --
> > > 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 !!!"

Re: Compilation Errors and the context.tokenizer [EXTERNAL]

Posted by Peter Abramowitsch <pa...@gmail.com>.

Thanks Sean.  Could be that slf4j is available from two sites, one of them
still on http and for whatever reason it is coming up first.
I'm not sure though whether all this is the same as the problem Gandhi has
been having.  Let's see what e says.

- Peter

On Mon, Nov 27, 2023 at 4:43 PM Finan, Sean
<Se...@childrens.harvard.edu.invalid> wrote:

> As for slf4j being on http:, I don't know that I ever saw that.  If you
> check maven central it is actually https:
>
> https://repo1.maven.org/maven2/org/slf4j/
>
> As referred to here:
> https://mvnrepository.com/artifact/org.slf4j/slf4j-api/2.0.5
>
> I will do some more research on this tonight, though I welcome people to
> beat me to a solution!
>
> Sean
>
> ________________________________
> From: Peter Abramowitsch <pa...@gmail.com>
> Sent: Monday, November 27, 2023 7:01 AM
> To: dev@ctakes.apache.org <de...@ctakes.apache.org>
> Subject: Re: Compilation Errors and the context.tokenizer [EXTERNAL]
>
> * External Email - Caution *
>
>
> Ghandi,
>
> As I mentioned at the beginning of this thread, there's only one change I
> needed to make to the settings.xml:  to comment out the dummy mirror server
> that maven uses as a way of enforcing the https requirement.  Commenting it
> out allowed maven to fetch slf4j-api.
>
> Since slf4j  is integral to the build, it halted everything.   The error
> manifested itself as maven just hanging with a message saying it was trying
> to access
> https://urldefense.com/v3/__http://0.0.0.0__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxuIKXiFw$
>   I made no other changes and there's nothing
> about the settings.xml which is ctakes-specific.
>
> Comment out this part of settings:
>
>     <mirror>
>       <id>maven-default-http-blocker</id>
>       <mirrorOf>external:http:*</mirrorOf>
>       <name>Pseudo repository to mirror external repositories initially
> using HTTP.</name>
>       <url>
> https://urldefense.com/v3/__http://0.0.0.0/__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzn8LRPpw$
> </url>
>       <blocked>true</blocked>
>     </mirror>
>
> Have you already tried doing it?
>
> For the model.jars it seems they are just brought to your local maven repo
> from maven.apache.org.
> Then a goal called unpack-dependencies copies the relevant files into your
> build tree.
>
> Generally, if you look very carefully at the maven output, it will tell you
> what is the original cause of your error.
> Don't just go by what the last output lines are
>
> If this doesn't help,  I'm afraid you'll need to ask someone else who may
> be able to ask you better questions about your environment.
>
> Peter
>
> On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <ga...@gmail.com>
> wrote:
>
> > Hi Peter,
> >
> > I did found your old discussion with Sean in the following link -
> >
> https://urldefense.com/v3/__https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxc2xW_0A$
> >
> > I am facing the same issue while building cakes core module. Could you
> > please send me the URL details from your 'settings.xml' under
> > '/usr/local/maven/config'
> > folder to figure out from which repo you are trying to pull the
> > dependencies from during build?
> >
> > On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <
> pabramowitsch@gmail.com>
> > wrote:
> >
> > > Hi Ghandi
> > > I did some checking around and sure enough, the resource files are not
> in
> > > the git archive.  I remember a conversation about this from long ago,
> > that
> > > git wasn't the best place for large binaries.  And they're not in git.
> > So
> > > I looked in my maven repository to see where my model files had come
> > from.
> > > Those models and in fact all the resource data for ctakes comes from
> > these
> > > sources:
> > >
> > > here's the content of my
> > > .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> > >
> > > _remote.repositories
> > > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > > m2e-lastUpdated.properties
> > > maven-metadata-apache.snapshots.xml
> > > maven-metadata-apache.snapshots.xml.sha1
> > > resolver-status.properties
> > >
> > > and here's the content of m2e-lastUpdated.properties
> > >
> > > #Fri Nov 17 22:03:31 CET 2023
> > > apache.snapshots|https\://
> > > repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056>
> > <
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> >
> > > <
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> > >
> > > apache.snapshots|https\://
> > > repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489>
> > <
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> >
> > > <
> >
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> > >
> > > central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
> <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > <
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> >
> > > <
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$
> >
> > > central|https\://repo.maven.apache.org/maven2|sources=1700255007489
> <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > <
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> >
> > > <
> https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$
> >
> > >
> > > I'm not a maven export, but perhaps where you're located (inside an
> > > organization?) you cannot access these addresses, or they need to be
> put
> > in
> > > a whitelist somewhere?  Sean might know.
> > >
> > > Sorry about the confusion.  Maven makes things both transparent and
> > opaque
> > > at the same time.  Most disturbin
> > > Peter
> > >
> > >
> > >
> > > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <ga...@gmail.com>
> > > wrote:
> > >
> > > > Hi Peter,
> > > >
> > > > I have pulled the code from main branch and the local copy is clean
> > > without
> > > > any changes to it. My issue still remains the same. The build is
> trying
> > > to
> > > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from
> the
> > > > remote maven repo which its not able to find.
> > > >
> > > > Complete error trace as follows:
> > > >
> > > > [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):
> > Cannot
> > > > access nexus (
> https://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> ) in offline mode and the
> > > > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has
> > not
> > > > been downloaded from it before.
> > > >
> > > >
> > > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > > pabramowitsch@gmail.com>
> > > > wrote:
> > > >
> > > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you are
> > with
> > > > git,
> > > > > so forgive me if this is obvious
> > > > >
> > > > >
> > > > >
> > > > > *$ git statusOn branch mainnothing to commit, working tree clean*
> > > > >
> > > > > If you've started making changes stash them in a branch and make
> sure
> > > > your
> > > > > tree is clean to simplify what you are finding.
> > > > >
> > > > > Peter
> > > > >
> > > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > > pabramowitsch@gmail.com>
> > > > > wrote:
> > > > >
> > > > > > Nope,  that is not the issue. Those version changes are
> intentional
> > > and
> > > > > > necessary.   The core pom and the subsidiary poms have been
> changed
> > > to
> > > > > > 5.0.0-SNAPSHOT as well because this is a new release.     For me
> it
> > > > > > compiles and runs fine (I am waiting for permission to check in
> my
> > > > > changes
> > > > > > for the context token path issue to help with eclipse building.
> > But
> > > if
> > > > > > you're just using mvn  to build you should be fine.
> > > > > >
> > > > > > The problem you're having seems to be that maven isn't able to
> > fetch
> > > > the
> > > > > > dependencies you need to build it.
> > > > > >
> > > > > > From your top level, if you do a *git status* and see that there
> > are
> > > no
> > > > > > modifications or missing files,
> > > > > >
> > > > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > > > dependencies are already present)
> > > > > >
> > > > > > and send me the output.
> > > > > >
> > > > > >
> > > > > >
> > > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > > gandhirajan.n@gmail.com>
> > > > > > wrote:
> > > > > >
> > > > > >> hi Peter,
> > > > > >>
> > > > > >> Thanks for the inputs. But I could see that ctakes-core module's
> > > > pom.xml
> > > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess
> this
> > > is
> > > > > >> causing the issue in my case. Please find the pom.xml changes
> for
> > > > > >> your reference:
> > > > > >>
> > > > > >> *ctakes-core 4.0.1:*
> > > > > >>
> > > > > >> <dependency>
> > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > > >>  </dependency>
> > > > > >>
> > > > > >> *ctakes-core 5.0.0:*
> > > > > >>
> > > > > >> <dependency>
> > > > > >> <groupId>org.apache.ctakes</groupId>
> > > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > > >>  <version>${ctakes.models.version}</version>
> > > > > >>  </dependency>
> > > > > >>
> > > > > >> Do u know about the changes Peter by any chance? or only Sean
> can
> > > > throw
> > > > > >> some light on these changes?
> > > > > >>
> > > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > > pabramowitsch@gmail.com
> > > > > >> >
> > > > > >> wrote:
> > > > > >>
> > > > > >> > Hi Ghandi
> > > > > >> >
> > > > > >> > See how far you get when you built using --offline
> > > > > >> >
> > > > > >> > Peter
> > > > > >> >
> > > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > > gandhirajan.n@gmail.com
> > > > > >
> > > > > >> > wrote:
> > > > > >> >
> > > > > >> > > Hi Peter,
> > > > > >> > >
> > > > > >> > > I am not using any IDE to build the project. I just used git
> > > bash
> > > > to
> > > > > >> pull
> > > > > >> > > the project from
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> 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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$
> 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 <
> > > > > >> > pabramowitsch@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 <
> > > > > >> > > > pabramowitsch@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 <
> > > > > >> > gandhirajan.n@gmail.com>
> > > > > >> > > > > wrote:
> > > > > >> > > > >
> > > > > >> > > > >> Hi Peter,
> > > > > >> > > > >>
> > > > > >> > > > >> I tried building the ctakes project from
> > > > > >> > > >
> https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > > >> > > > >> 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 <
> > > > > >> > > > pabramowitsch@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
> > > > > >> > > !!!"
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > > >>
> > > > > >> --
> > > > > >> 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
> > > > !!!"
> > > >
> > >
> >
> >
> > --
> > Regards,
> > Gandhi
> >
> > "The best way to find urself is to lose urself in the service of others
> > !!!"
> >
>

Re: Compilation Errors and the context.tokenizer [EXTERNAL]

Posted by "Finan, Sean" <Se...@childrens.harvard.edu.INVALID>.

As for slf4j being on http:, I don't know that I ever saw that.  If you check maven central it is actually https:

https://repo1.maven.org/maven2/org/slf4j/

As referred to here:
https://mvnrepository.com/artifact/org.slf4j/slf4j-api/2.0.5

I will do some more research on this tonight, though I welcome people to beat me to a solution!

Sean

________________________________
From: Peter Abramowitsch <pa...@gmail.com>
Sent: Monday, November 27, 2023 7:01 AM
To: dev@ctakes.apache.org <de...@ctakes.apache.org>
Subject: Re: Compilation Errors and the context.tokenizer [EXTERNAL]

* External Email - Caution *


Ghandi,

As I mentioned at the beginning of this thread, there's only one change I
needed to make to the settings.xml:  to comment out the dummy mirror server
that maven uses as a way of enforcing the https requirement.  Commenting it
out allowed maven to fetch slf4j-api.

Since slf4j  is integral to the build, it halted everything.   The error
manifested itself as maven just hanging with a message saying it was trying
to access https://urldefense.com/v3/__http://0.0.0.0__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxuIKXiFw$    I made no other changes and there's nothing
about the settings.xml which is ctakes-specific.

Comment out this part of settings:

    <mirror>
      <id>maven-default-http-blocker</id>
      <mirrorOf>external:http:*</mirrorOf>
      <name>Pseudo repository to mirror external repositories initially
using HTTP.</name>
      <url>https://urldefense.com/v3/__http://0.0.0.0/__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzn8LRPpw$ </url>
      <blocked>true</blocked>
    </mirror>

Have you already tried doing it?

For the model.jars it seems they are just brought to your local maven repo
from maven.apache.org.
Then a goal called unpack-dependencies copies the relevant files into your
build tree.

Generally, if you look very carefully at the maven output, it will tell you
what is the original cause of your error.
Don't just go by what the last output lines are

If this doesn't help,  I'm afraid you'll need to ask someone else who may
be able to ask you better questions about your environment.

Peter

On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <ga...@gmail.com>
wrote:

> Hi Peter,
>
> I did found your old discussion with Sean in the following link -
> https://urldefense.com/v3/__https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHxc2xW_0A$
>
> I am facing the same issue while building cakes core module. Could you
> please send me the URL details from your 'settings.xml' under
> '/usr/local/maven/config'
> folder to figure out from which repo you are trying to pull the
> dependencies from during build?
>
> On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Hi Ghandi
> > I did some checking around and sure enough, the resource files are not in
> > the git archive.  I remember a conversation about this from long ago,
> that
> > git wasn't the best place for large binaries.  And they're not in git.
> So
> > I looked in my maven repository to see where my model files had come
> from.
> > Those models and in fact all the resource data for ctakes comes from
> these
> > sources:
> >
> > here's the content of my
> > .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> >
> > _remote.repositories
> > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > m2e-lastUpdated.properties
> > maven-metadata-apache.snapshots.xml
> > maven-metadata-apache.snapshots.xml.sha1
> > resolver-status.properties
> >
> > and here's the content of m2e-lastUpdated.properties
> >
> > #Fri Nov 17 22:03:31 CET 2023
> > apache.snapshots|https\://
> > repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$ >
> > <
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHw9y4WMOQ$
> >
> > apache.snapshots|https\://
> > repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$ >
> > <
> https://urldefense.com/v3/__http://repository.apache.org/content/groups/snapshots/*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwCxeiF8g$
> >
> > central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
> <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$ >
> > <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Cjavadoc=1700255011056__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHzwJNZ2GQ$ >
> > central|https\://repo.maven.apache.org/maven2|sources=1700255007489
> <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$ >
> > <https://urldefense.com/v3/__http://repo.maven.apache.org/maven2*7Csources=1700255007489__;JQ!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHx0qGkFYA$ >
> >
> > I'm not a maven export, but perhaps where you're located (inside an
> > organization?) you cannot access these addresses, or they need to be put
> in
> > a whitelist somewhere?  Sean might know.
> >
> > Sorry about the confusion.  Maven makes things both transparent and
> opaque
> > at the same time.  Most disturbin
> > Peter
> >
> >
> >
> > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <ga...@gmail.com>
> > wrote:
> >
> > > Hi Peter,
> > >
> > > I have pulled the code from main branch and the local copy is clean
> > without
> > > any changes to it. My issue still remains the same. The build is trying
> > to
> > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from the
> > > remote maven repo which its not able to find.
> > >
> > > Complete error trace as follows:
> > >
> > > [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):
> Cannot
> > > access nexus (https://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$ ) in offline mode and the
> > > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has
> not
> > > been downloaded from it before.
> > >
> > >
> > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > pabramowitsch@gmail.com>
> > > wrote:
> > >
> > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you are
> with
> > > git,
> > > > so forgive me if this is obvious
> > > >
> > > >
> > > >
> > > > *$ git statusOn branch mainnothing to commit, working tree clean*
> > > >
> > > > If you've started making changes stash them in a branch and make sure
> > > your
> > > > tree is clean to simplify what you are finding.
> > > >
> > > > Peter
> > > >
> > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > pabramowitsch@gmail.com>
> > > > wrote:
> > > >
> > > > > Nope,  that is not the issue. Those version changes are intentional
> > and
> > > > > necessary.   The core pom and the subsidiary poms have been changed
> > to
> > > > > 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> > > > > compiles and runs fine (I am waiting for permission to check in my
> > > > changes
> > > > > for the context token path issue to help with eclipse building.
> But
> > if
> > > > > you're just using mvn  to build you should be fine.
> > > > >
> > > > > The problem you're having seems to be that maven isn't able to
> fetch
> > > the
> > > > > dependencies you need to build it.
> > > > >
> > > > > From your top level, if you do a *git status* and see that there
> are
> > no
> > > > > modifications or missing files,
> > > > >
> > > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > > dependencies are already present)
> > > > >
> > > > > and send me the output.
> > > > >
> > > > >
> > > > >
> > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > gandhirajan.n@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> hi Peter,
> > > > >>
> > > > >> Thanks for the inputs. But I could see that ctakes-core module's
> > > pom.xml
> > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this
> > is
> > > > >> causing the issue in my case. Please find the pom.xml changes for
> > > > >> your reference:
> > > > >>
> > > > >> *ctakes-core 4.0.1:*
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>org.apache.ctakes</groupId>
> > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > >>  </dependency>
> > > > >>
> > > > >> *ctakes-core 5.0.0:*
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>org.apache.ctakes</groupId>
> > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > >>  <version>${ctakes.models.version}</version>
> > > > >>  </dependency>
> > > > >>
> > > > >> Do u know about the changes Peter by any chance? or only Sean can
> > > throw
> > > > >> some light on these changes?
> > > > >>
> > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > pabramowitsch@gmail.com
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > Hi Ghandi
> > > > >> >
> > > > >> > See how far you get when you built using --offline
> > > > >> >
> > > > >> > Peter
> > > > >> >
> > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > gandhirajan.n@gmail.com
> > > > >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > Hi Peter,
> > > > >> > >
> > > > >> > > I am not using any IDE to build the project. I just used git
> > bash
> > > to
> > > > >> pull
> > > > >> > > the project from https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$  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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$  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://urldefense.com/v3/__https://repo1.maven.org/maven2__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHze0ilTAg$  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 <
> > > > >> > pabramowitsch@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 <
> > > > >> > > > pabramowitsch@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 <
> > > > >> > gandhirajan.n@gmail.com>
> > > > >> > > > > wrote:
> > > > >> > > > >
> > > > >> > > > >> Hi Peter,
> > > > >> > > > >>
> > > > >> > > > >> I tried building the ctakes project from
> > > > >> > > > https://urldefense.com/v3/__https://github.com/apache/ctakes__;!!NZvER7FxgEiBAiR_!rossFJrjv7RCYPsO0XiTkn5cwu5oMIZg_q3p8SFPSLVMfs4GvriQpnATGog-DGXyb4aNKBsQfqVmK9-9NDZUr7WdBHwMwCj7uQ$
> > > > >> > > > >> 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 <
> > > > >> > > > pabramowitsch@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
> > > > >> > > !!!"
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >> 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
> > > !!!"
> > >
> >
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

Ghandi,

As I mentioned at the beginning of this thread, there's only one change I
needed to make to the settings.xml:  to comment out the dummy mirror server
that maven uses as a way of enforcing the https requirement.  Commenting it
out allowed maven to fetch slf4j-api.

Since slf4j  is integral to the build, it halted everything.   The error
manifested itself as maven just hanging with a message saying it was trying
to access http://0.0.0.0   I made no other changes and there's nothing
about the settings.xml which is ctakes-specific.

Comment out this part of settings:

    <mirror>
      <id>maven-default-http-blocker</id>
      <mirrorOf>external:http:*</mirrorOf>
      <name>Pseudo repository to mirror external repositories initially
using HTTP.</name>
      <url>http://0.0.0.0/</url>
      <blocked>true</blocked>
    </mirror>

Have you already tried doing it?

For the model.jars it seems they are just brought to your local maven repo
from maven.apache.org.
Then a goal called unpack-dependencies copies the relevant files into your
build tree.

Generally, if you look very carefully at the maven output, it will tell you
what is the original cause of your error.
Don't just go by what the last output lines are

If this doesn't help,  I'm afraid you'll need to ask someone else who may
be able to ask you better questions about your environment.

Peter

On Mon, Nov 27, 2023 at 11:07 AM gandhi rajan <ga...@gmail.com>
wrote:

> Hi Peter,
>
> I did found your old discussion with Sean in the following link -
> https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw
>
> I am facing the same issue while building cakes core module. Could you
> please send me the URL details from your 'settings.xml' under
> '/usr/local/maven/config'
> folder to figure out from which repo you are trying to pull the
> dependencies from during build?
>
> On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Hi Ghandi
> > I did some checking around and sure enough, the resource files are not in
> > the git archive.  I remember a conversation about this from long ago,
> that
> > git wasn't the best place for large binaries.  And they're not in git.
> So
> > I looked in my maven repository to see where my model files had come
> from.
> > Those models and in fact all the resource data for ctakes comes from
> these
> > sources:
> >
> > here's the content of my
> > .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
> >
> > _remote.repositories
> > ctakes-core-models-5.0.0-20221224.062752-3.jar
> > ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> > ctakes-core-models-5.0.0-20221224.062752-3.pom
> > ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> > ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> > ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> > ctakes-core-models-5.0.0-SNAPSHOT.jar
> > ctakes-core-models-5.0.0-SNAPSHOT.pom
> > m2e-lastUpdated.properties
> > maven-metadata-apache.snapshots.xml
> > maven-metadata-apache.snapshots.xml.sha1
> > resolver-status.properties
> >
> > and here's the content of m2e-lastUpdated.properties
> >
> > #Fri Nov 17 22:03:31 CET 2023
> > apache.snapshots|https\://
> > repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056
> >
> > apache.snapshots|https\://
> > repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489>
> > <
> http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489
> >
> > central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
> <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> > central|https\://repo.maven.apache.org/maven2|sources=1700255007489
> <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> > <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
> >
> > I'm not a maven export, but perhaps where you're located (inside an
> > organization?) you cannot access these addresses, or they need to be put
> in
> > a whitelist somewhere?  Sean might know.
> >
> > Sorry about the confusion.  Maven makes things both transparent and
> opaque
> > at the same time.  Most disturbin
> > Peter
> >
> >
> >
> > On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <ga...@gmail.com>
> > wrote:
> >
> > > Hi Peter,
> > >
> > > I have pulled the code from main branch and the local copy is clean
> > without
> > > any changes to it. My issue still remains the same. The build is trying
> > to
> > > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from the
> > > remote maven repo which its not able to find.
> > >
> > > Complete error trace as follows:
> > >
> > > [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):
> Cannot
> > > access nexus (https://repo1.maven.org/maven2) in offline mode and the
> > > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has
> not
> > > been downloaded from it before.
> > >
> > >
> > > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> > pabramowitsch@gmail.com>
> > > wrote:
> > >
> > > > Ghandi,  I'm going out for a bit.   Not sure how familiar you are
> with
> > > git,
> > > > so forgive me if this is obvious
> > > >
> > > >
> > > >
> > > > *$ git statusOn branch mainnothing to commit, working tree clean*
> > > >
> > > > If you've started making changes stash them in a branch and make sure
> > > your
> > > > tree is clean to simplify what you are finding.
> > > >
> > > > Peter
> > > >
> > > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > > pabramowitsch@gmail.com>
> > > > wrote:
> > > >
> > > > > Nope,  that is not the issue. Those version changes are intentional
> > and
> > > > > necessary.   The core pom and the subsidiary poms have been changed
> > to
> > > > > 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> > > > > compiles and runs fine (I am waiting for permission to check in my
> > > > changes
> > > > > for the context token path issue to help with eclipse building.
> But
> > if
> > > > > you're just using mvn  to build you should be fine.
> > > > >
> > > > > The problem you're having seems to be that maven isn't able to
> fetch
> > > the
> > > > > dependencies you need to build it.
> > > > >
> > > > > From your top level, if you do a *git status* and see that there
> are
> > no
> > > > > modifications or missing files,
> > > > >
> > > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > > dependencies are already present)
> > > > >
> > > > > and send me the output.
> > > > >
> > > > >
> > > > >
> > > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> > gandhirajan.n@gmail.com>
> > > > > wrote:
> > > > >
> > > > >> hi Peter,
> > > > >>
> > > > >> Thanks for the inputs. But I could see that ctakes-core module's
> > > pom.xml
> > > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this
> > is
> > > > >> causing the issue in my case. Please find the pom.xml changes for
> > > > >> your reference:
> > > > >>
> > > > >> *ctakes-core 4.0.1:*
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>org.apache.ctakes</groupId>
> > > > >> <artifactId>ctakes-core-res</artifactId>
> > > > >>  </dependency>
> > > > >>
> > > > >> *ctakes-core 5.0.0:*
> > > > >>
> > > > >> <dependency>
> > > > >> <groupId>org.apache.ctakes</groupId>
> > > > >> <artifactId>ctakes-core-models</artifactId>
> > > > >>  <version>${ctakes.models.version}</version>
> > > > >>  </dependency>
> > > > >>
> > > > >> Do u know about the changes Peter by any chance? or only Sean can
> > > throw
> > > > >> some light on these changes?
> > > > >>
> > > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > > pabramowitsch@gmail.com
> > > > >> >
> > > > >> wrote:
> > > > >>
> > > > >> > Hi Ghandi
> > > > >> >
> > > > >> > See how far you get when you built using --offline
> > > > >> >
> > > > >> > Peter
> > > > >> >
> > > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > > gandhirajan.n@gmail.com
> > > > >
> > > > >> > wrote:
> > > > >> >
> > > > >> > > 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 <
> > > > >> > pabramowitsch@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 <
> > > > >> > > > pabramowitsch@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 <
> > > > >> > gandhirajan.n@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 <
> > > > >> > > > pabramowitsch@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
> > > > >> > > !!!"
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >> --
> > > > >> 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
> > > !!!"
> > >
> >
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>

Re: Compilation Errors and the context.tokenizer

Posted by gandhi rajan <ga...@gmail.com>.

Hi Peter,

I did found your old discussion with Sean in the following link -
https://lists.apache.org/thread/w9c33421vxb21bnr6gd9r2tb3n1odnnw

I am facing the same issue while building cakes core module. Could you
please send me the URL details from your 'settings.xml' under
'/usr/local/maven/config'
folder to figure out from which repo you are trying to pull the
dependencies from during build?

On Mon, 27 Nov 2023 at 13:22, Peter Abramowitsch <pa...@gmail.com>
wrote:

> Hi Ghandi
> I did some checking around and sure enough, the resource files are not in
> the git archive.  I remember a conversation about this from long ago, that
> git wasn't the best place for large binaries.  And they're not in git.  So
> I looked in my maven repository to see where my model files had come from.
> Those models and in fact all the resource data for ctakes comes from these
> sources:
>
> here's the content of my
> .m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT
>
> _remote.repositories
> ctakes-core-models-5.0.0-20221224.062752-3.jar
> ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
> ctakes-core-models-5.0.0-20221224.062752-3.pom
> ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
> ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
> ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
> ctakes-core-models-5.0.0-SNAPSHOT.jar
> ctakes-core-models-5.0.0-SNAPSHOT.pom
> m2e-lastUpdated.properties
> maven-metadata-apache.snapshots.xml
> maven-metadata-apache.snapshots.xml.sha1
> resolver-status.properties
>
> and here's the content of m2e-lastUpdated.properties
>
> #Fri Nov 17 22:03:31 CET 2023
> apache.snapshots|https\://
> repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
> <http://repository.apache.org/content/groups/snapshots/%7Cjavadoc=1700255011056>
> apache.snapshots|https\://
> repository.apache.org/content/groups/snapshots/|sources=1700255007489
> <http://repository.apache.org/content/groups/snapshots/%7Csources=1700255007489>
> central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
> <http://repo.maven.apache.org/maven2%7Cjavadoc=1700255011056>
> central|https\://repo.maven.apache.org/maven2|sources=1700255007489
> <http://repo.maven.apache.org/maven2%7Csources=1700255007489>
>
> I'm not a maven export, but perhaps where you're located (inside an
> organization?) you cannot access these addresses, or they need to be put in
> a whitelist somewhere?  Sean might know.
>
> Sorry about the confusion.  Maven makes things both transparent and opaque
> at the same time.  Most disturbin
> Peter
>
>
>
> On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <ga...@gmail.com>
> wrote:
>
> > Hi Peter,
> >
> > I have pulled the code from main branch and the local copy is clean
> without
> > any changes to it. My issue still remains the same. The build is trying
> to
> > pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from the
> > remote maven repo which its not able to find.
> >
> > Complete error trace as follows:
> >
> > [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): Cannot
> > access nexus (https://repo1.maven.org/maven2) in offline mode and the
> > artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has not
> > been downloaded from it before.
> >
> >
> > On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <
> pabramowitsch@gmail.com>
> > wrote:
> >
> > > Ghandi,  I'm going out for a bit.   Not sure how familiar you are with
> > git,
> > > so forgive me if this is obvious
> > >
> > >
> > >
> > > *$ git statusOn branch mainnothing to commit, working tree clean*
> > >
> > > If you've started making changes stash them in a branch and make sure
> > your
> > > tree is clean to simplify what you are finding.
> > >
> > > Peter
> > >
> > > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > > pabramowitsch@gmail.com>
> > > wrote:
> > >
> > > > Nope,  that is not the issue. Those version changes are intentional
> and
> > > > necessary.   The core pom and the subsidiary poms have been changed
> to
> > > > 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> > > > compiles and runs fine (I am waiting for permission to check in my
> > > changes
> > > > for the context token path issue to help with eclipse building.  But
> if
> > > > you're just using mvn  to build you should be fine.
> > > >
> > > > The problem you're having seems to be that maven isn't able to fetch
> > the
> > > > dependencies you need to build it.
> > > >
> > > > From your top level, if you do a *git status* and see that there are
> no
> > > > modifications or missing files,
> > > >
> > > > then try:    *mvn --offline package*  (to see if the relevant
> > > > dependencies are already present)
> > > >
> > > > and send me the output.
> > > >
> > > >
> > > >
> > > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <
> gandhirajan.n@gmail.com>
> > > > wrote:
> > > >
> > > >> hi Peter,
> > > >>
> > > >> Thanks for the inputs. But I could see that ctakes-core module's
> > pom.xml
> > > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this
> is
> > > >> causing the issue in my case. Please find the pom.xml changes for
> > > >> your reference:
> > > >>
> > > >> *ctakes-core 4.0.1:*
> > > >>
> > > >> <dependency>
> > > >> <groupId>org.apache.ctakes</groupId>
> > > >> <artifactId>ctakes-core-res</artifactId>
> > > >>  </dependency>
> > > >>
> > > >> *ctakes-core 5.0.0:*
> > > >>
> > > >> <dependency>
> > > >> <groupId>org.apache.ctakes</groupId>
> > > >> <artifactId>ctakes-core-models</artifactId>
> > > >>  <version>${ctakes.models.version}</version>
> > > >>  </dependency>
> > > >>
> > > >> Do u know about the changes Peter by any chance? or only Sean can
> > throw
> > > >> some light on these changes?
> > > >>
> > > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > > pabramowitsch@gmail.com
> > > >> >
> > > >> wrote:
> > > >>
> > > >> > Hi Ghandi
> > > >> >
> > > >> > See how far you get when you built using --offline
> > > >> >
> > > >> > Peter
> > > >> >
> > > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> > gandhirajan.n@gmail.com
> > > >
> > > >> > wrote:
> > > >> >
> > > >> > > 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 <
> > > >> > pabramowitsch@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 <
> > > >> > > > pabramowitsch@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 <
> > > >> > gandhirajan.n@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 <
> > > >> > > > pabramowitsch@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
> > > >> > > !!!"
> > > >> > >
> > > >> >
> > > >>
> > > >>
> > > >> --
> > > >> 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
> > !!!"
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

Hi Ghandi
I did some checking around and sure enough, the resource files are not in
the git archive.  I remember a conversation about this from long ago, that
git wasn't the best place for large binaries.  And they're not in git.  So
I looked in my maven repository to see where my model files had come from.
Those models and in fact all the resource data for ctakes comes from these
sources:

here's the content of my
.m2/repository/org/apache/ctakes/ctakes-core-models/5.0.0-SNAPSHOT

_remote.repositories
ctakes-core-models-5.0.0-20221224.062752-3.jar
ctakes-core-models-5.0.0-20221224.062752-3.jar.sha1
ctakes-core-models-5.0.0-20221224.062752-3.pom
ctakes-core-models-5.0.0-20221224.062752-3.pom.sha1
ctakes-core-models-5.0.0-SNAPSHOT-javadoc.jar.lastUpdated
ctakes-core-models-5.0.0-SNAPSHOT-sources.jar.lastUpdated
ctakes-core-models-5.0.0-SNAPSHOT.jar
ctakes-core-models-5.0.0-SNAPSHOT.pom
m2e-lastUpdated.properties
maven-metadata-apache.snapshots.xml
maven-metadata-apache.snapshots.xml.sha1
resolver-status.properties

and here's the content of m2e-lastUpdated.properties

#Fri Nov 17 22:03:31 CET 2023
apache.snapshots|https\://
repository.apache.org/content/groups/snapshots/|javadoc=1700255011056
apache.snapshots|https\://
repository.apache.org/content/groups/snapshots/|sources=1700255007489
central|https\://repo.maven.apache.org/maven2|javadoc=1700255011056
central|https\://repo.maven.apache.org/maven2|sources=1700255007489

I'm not a maven export, but perhaps where you're located (inside an
organization?) you cannot access these addresses, or they need to be put in
a whitelist somewhere?  Sean might know.

Sorry about the confusion.  Maven makes things both transparent and opaque
at the same time.  Most disturbin
Peter



On Mon, Nov 27, 2023 at 7:50 AM gandhi rajan <ga...@gmail.com>
wrote:

> Hi Peter,
>
> I have pulled the code from main branch and the local copy is clean without
> any changes to it. My issue still remains the same. The build is trying to
> pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from the
> remote maven repo which its not able to find.
>
> Complete error trace as follows:
>
> [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): Cannot
> access nexus (https://repo1.maven.org/maven2) in offline mode and the
> artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has not
> been downloaded from it before.
>
>
> On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Ghandi,  I'm going out for a bit.   Not sure how familiar you are with
> git,
> > so forgive me if this is obvious
> >
> >
> >
> > *$ git statusOn branch mainnothing to commit, working tree clean*
> >
> > If you've started making changes stash them in a branch and make sure
> your
> > tree is clean to simplify what you are finding.
> >
> > Peter
> >
> > On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> > pabramowitsch@gmail.com>
> > wrote:
> >
> > > Nope,  that is not the issue. Those version changes are intentional and
> > > necessary.   The core pom and the subsidiary poms have been changed to
> > > 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> > > compiles and runs fine (I am waiting for permission to check in my
> > changes
> > > for the context token path issue to help with eclipse building.  But if
> > > you're just using mvn  to build you should be fine.
> > >
> > > The problem you're having seems to be that maven isn't able to fetch
> the
> > > dependencies you need to build it.
> > >
> > > From your top level, if you do a *git status* and see that there are no
> > > modifications or missing files,
> > >
> > > then try:    *mvn --offline package*  (to see if the relevant
> > > dependencies are already present)
> > >
> > > and send me the output.
> > >
> > >
> > >
> > > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <ga...@gmail.com>
> > > wrote:
> > >
> > >> hi Peter,
> > >>
> > >> Thanks for the inputs. But I could see that ctakes-core module's
> pom.xml
> > >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this is
> > >> causing the issue in my case. Please find the pom.xml changes for
> > >> your reference:
> > >>
> > >> *ctakes-core 4.0.1:*
> > >>
> > >> <dependency>
> > >> <groupId>org.apache.ctakes</groupId>
> > >> <artifactId>ctakes-core-res</artifactId>
> > >>  </dependency>
> > >>
> > >> *ctakes-core 5.0.0:*
> > >>
> > >> <dependency>
> > >> <groupId>org.apache.ctakes</groupId>
> > >> <artifactId>ctakes-core-models</artifactId>
> > >>  <version>${ctakes.models.version}</version>
> > >>  </dependency>
> > >>
> > >> Do u know about the changes Peter by any chance? or only Sean can
> throw
> > >> some light on these changes?
> > >>
> > >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> > pabramowitsch@gmail.com
> > >> >
> > >> wrote:
> > >>
> > >> > Hi Ghandi
> > >> >
> > >> > See how far you get when you built using --offline
> > >> >
> > >> > Peter
> > >> >
> > >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <
> gandhirajan.n@gmail.com
> > >
> > >> > wrote:
> > >> >
> > >> > > 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 <
> > >> > pabramowitsch@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 <
> > >> > > > pabramowitsch@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 <
> > >> > gandhirajan.n@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 <
> > >> > > > pabramowitsch@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
> > >> > > !!!"
> > >> > >
> > >> >
> > >>
> > >>
> > >> --
> > >> 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
> !!!"
>

Re: Compilation Errors and the context.tokenizer

Posted by gandhi rajan <ga...@gmail.com>.

Hi Peter,

I have pulled the code from main branch and the local copy is clean without
any changes to it. My issue still remains the same. The build is trying to
pull the org.apache.ctakes:ctakes-core:jar:5.0.0-SNAPSHOT jar from the
remote maven repo which its not able to find.

Complete error trace as follows:

[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): Cannot
access nexus (https://repo1.maven.org/maven2) in offline mode and the
artifact org.apache.ctakes:ctakes-core-models:jar:5.0.0-SNAPSHOT has not
been downloaded from it before.


On Sun, 26 Nov 2023 at 23:25, Peter Abramowitsch <pa...@gmail.com>
wrote:

> Ghandi,  I'm going out for a bit.   Not sure how familiar you are with git,
> so forgive me if this is obvious
>
>
>
> *$ git statusOn branch mainnothing to commit, working tree clean*
>
> If you've started making changes stash them in a branch and make sure your
> tree is clean to simplify what you are finding.
>
> Peter
>
> On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <
> pabramowitsch@gmail.com>
> wrote:
>
> > Nope,  that is not the issue. Those version changes are intentional and
> > necessary.   The core pom and the subsidiary poms have been changed to
> > 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> > compiles and runs fine (I am waiting for permission to check in my
> changes
> > for the context token path issue to help with eclipse building.  But if
> > you're just using mvn  to build you should be fine.
> >
> > The problem you're having seems to be that maven isn't able to fetch the
> > dependencies you need to build it.
> >
> > From your top level, if you do a *git status* and see that there are no
> > modifications or missing files,
> >
> > then try:    *mvn --offline package*  (to see if the relevant
> > dependencies are already present)
> >
> > and send me the output.
> >
> >
> >
> > On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <ga...@gmail.com>
> > wrote:
> >
> >> hi Peter,
> >>
> >> Thanks for the inputs. But I could see that ctakes-core module's pom.xml
> >> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this is
> >> causing the issue in my case. Please find the pom.xml changes for
> >> your reference:
> >>
> >> *ctakes-core 4.0.1:*
> >>
> >> <dependency>
> >> <groupId>org.apache.ctakes</groupId>
> >> <artifactId>ctakes-core-res</artifactId>
> >>  </dependency>
> >>
> >> *ctakes-core 5.0.0:*
> >>
> >> <dependency>
> >> <groupId>org.apache.ctakes</groupId>
> >> <artifactId>ctakes-core-models</artifactId>
> >>  <version>${ctakes.models.version}</version>
> >>  </dependency>
> >>
> >> Do u know about the changes Peter by any chance? or only Sean can throw
> >> some light on these changes?
> >>
> >> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <
> pabramowitsch@gmail.com
> >> >
> >> wrote:
> >>
> >> > Hi Ghandi
> >> >
> >> > See how far you get when you built using --offline
> >> >
> >> > Peter
> >> >
> >> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <gandhirajan.n@gmail.com
> >
> >> > wrote:
> >> >
> >> > > 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 <
> >> > pabramowitsch@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 <
> >> > > > pabramowitsch@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 <
> >> > gandhirajan.n@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 <
> >> > > > pabramowitsch@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
> >> > > !!!"
> >> > >
> >> >
> >>
> >>
> >> --
> >> 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 !!!"

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

Ghandi,  I'm going out for a bit.   Not sure how familiar you are with git,
so forgive me if this is obvious



*$ git statusOn branch mainnothing to commit, working tree clean*

If you've started making changes stash them in a branch and make sure your
tree is clean to simplify what you are finding.

Peter

On Sun, Nov 26, 2023 at 6:47 PM Peter Abramowitsch <pa...@gmail.com>
wrote:

> Nope,  that is not the issue. Those version changes are intentional and
> necessary.   The core pom and the subsidiary poms have been changed to
> 5.0.0-SNAPSHOT as well because this is a new release.     For me it
> compiles and runs fine (I am waiting for permission to check in my changes
> for the context token path issue to help with eclipse building.  But if
> you're just using mvn  to build you should be fine.
>
> The problem you're having seems to be that maven isn't able to fetch the
> dependencies you need to build it.
>
> From your top level, if you do a *git status* and see that there are no
> modifications or missing files,
>
> then try:    *mvn --offline package*  (to see if the relevant
> dependencies are already present)
>
> and send me the output.
>
>
>
> On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <ga...@gmail.com>
> wrote:
>
>> hi Peter,
>>
>> Thanks for the inputs. But I could see that ctakes-core module's pom.xml
>> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this is
>> causing the issue in my case. Please find the pom.xml changes for
>> your reference:
>>
>> *ctakes-core 4.0.1:*
>>
>> <dependency>
>> <groupId>org.apache.ctakes</groupId>
>> <artifactId>ctakes-core-res</artifactId>
>>  </dependency>
>>
>> *ctakes-core 5.0.0:*
>>
>> <dependency>
>> <groupId>org.apache.ctakes</groupId>
>> <artifactId>ctakes-core-models</artifactId>
>>  <version>${ctakes.models.version}</version>
>>  </dependency>
>>
>> Do u know about the changes Peter by any chance? or only Sean can throw
>> some light on these changes?
>>
>> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <pabramowitsch@gmail.com
>> >
>> wrote:
>>
>> > Hi Ghandi
>> >
>> > See how far you get when you built using --offline
>> >
>> > Peter
>> >
>> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <ga...@gmail.com>
>> > wrote:
>> >
>> > > 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 <
>> > pabramowitsch@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 <
>> > > > pabramowitsch@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 <
>> > gandhirajan.n@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 <
>> > > > pabramowitsch@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
>> > > !!!"
>> > >
>> >
>>
>>
>> --
>> Regards,
>> Gandhi
>>
>> "The best way to find urself is to lose urself in the service of others
>> !!!"
>>
>

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

Nope,  that is not the issue. Those version changes are intentional and
necessary.   The core pom and the subsidiary poms have been changed to
5.0.0-SNAPSHOT as well because this is a new release.     For me it
compiles and runs fine (I am waiting for permission to check in my changes
for the context token path issue to help with eclipse building.  But if
you're just using mvn  to build you should be fine.

The problem you're having seems to be that maven isn't able to fetch the
dependencies you need to build it.

From your top level, if you do a *git status* and see that there are no
modifications or missing files,

then try:    *mvn --offline package*  (to see if the relevant dependencies
are already present)

and send me the output.



On Sun, Nov 26, 2023 at 6:30 PM gandhi rajan <ga...@gmail.com>
wrote:

> hi Peter,
>
> Thanks for the inputs. But I could see that ctakes-core module's pom.xml
> has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this is
> causing the issue in my case. Please find the pom.xml changes for
> your reference:
>
> *ctakes-core 4.0.1:*
>
> <dependency>
> <groupId>org.apache.ctakes</groupId>
> <artifactId>ctakes-core-res</artifactId>
>  </dependency>
>
> *ctakes-core 5.0.0:*
>
> <dependency>
> <groupId>org.apache.ctakes</groupId>
> <artifactId>ctakes-core-models</artifactId>
>  <version>${ctakes.models.version}</version>
>  </dependency>
>
> Do u know about the changes Peter by any chance? or only Sean can throw
> some light on these changes?
>
> On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <pa...@gmail.com>
> wrote:
>
> > Hi Ghandi
> >
> > See how far you get when you built using --offline
> >
> > Peter
> >
> > On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <ga...@gmail.com>
> > wrote:
> >
> > > 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 <
> > pabramowitsch@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 <
> > > > pabramowitsch@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 <
> > gandhirajan.n@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 <
> > > > pabramowitsch@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
> > > !!!"
> > >
> >
>
>
> --
> Regards,
> Gandhi
>
> "The best way to find urself is to lose urself in the service of others
> !!!"
>

Re: Compilation Errors and the context.tokenizer

Posted by gandhi rajan <ga...@gmail.com>.

hi Peter,

Thanks for the inputs. But I could see that ctakes-core module's pom.xml
has changed from 4.0.1 snapshot to 5.0.0 snapshot and I guess this is
causing the issue in my case. Please find the pom.xml changes for
your reference:

*ctakes-core 4.0.1:*

<dependency>
<groupId>org.apache.ctakes</groupId>
<artifactId>ctakes-core-res</artifactId>
 </dependency>

*ctakes-core 5.0.0:*

<dependency>
<groupId>org.apache.ctakes</groupId>
<artifactId>ctakes-core-models</artifactId>
 <version>${ctakes.models.version}</version>
 </dependency>

Do u know about the changes Peter by any chance? or only Sean can throw
some light on these changes?

On Sun, 26 Nov 2023 at 22:54, Peter Abramowitsch <pa...@gmail.com>
wrote:

> Hi Ghandi
>
> See how far you get when you built using --offline
>
> Peter
>
> On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <ga...@gmail.com>
> wrote:
>
> > 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 <
> pabramowitsch@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 <
> > > pabramowitsch@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 <
> gandhirajan.n@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 <
> > > pabramowitsch@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
> > !!!"
> >
>


-- 
Regards,
Gandhi

"The best way to find urself is to lose urself in the service of others !!!"

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

Hi Ghandi

See how far you get when you built using --offline

Peter

On Sun, Nov 26, 2023 at 6:00 PM gandhi rajan <ga...@gmail.com>
wrote:

> 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 <pa...@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 <
> > pabramowitsch@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 <ga...@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 <
> > pabramowitsch@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
> !!!"
>

Re: Compilation Errors and the context.tokenizer

Posted by gandhi rajan <ga...@gmail.com>.

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 <pa...@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 <
> pabramowitsch@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 <ga...@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 <
> pabramowitsch@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 !!!"

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

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 <pa...@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 <ga...@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 <pabramowitsch@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
>> !!!"
>>
>

Re: Compilation Errors and the context.tokenizer

Posted by Peter Abramowitsch <pa...@gmail.com>.

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 <ga...@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 <pa...@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
> !!!"
>

Re: Compilation Errors and the context.tokenizer

Posted by gandhi rajan <ga...@gmail.com>.

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 <pa...@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 !!!"