Hi Gandhi,
* So post release I would be able to run mvn clean
install on web rest module rather than relying on resources in .m2 folder
The opposite. Pre-release there are no jars on maven central, post-release
there are.
Running 'mvn package' directly on the ctakes-web-rest project (in its directory)
or
running 'mvn package' on the ctakes -main- project (in the main ctakes root
directory) with the web-rest-build profile enabled '-Pweb-rest-build'
will build the ctakes-web-rest.war web package.
That profile is defined in the main ctakes pom.
https://github.com/apache/ctakes/blob/main/pom.xml#L1074
I added a little bit to your instructions in the ctakes-web-rest README
https://github.com/apache/ctakes/blob/main/ctakes-web-rest/README
The lines here indirectly applies to pre-release builds:
https://github.com/apache/ctakes/blob/main/ctakes-web-rest/README#L22
The 5.1.0-SNAPSHOT version of ctakes-web-rest has a dependency on the 5.1.0
version of ctakes modules (not the SNAPSHOT).
https://github.com/apache/ctakes/blob/main/ctakes-web-rest/pom.xml#L14
The pre-release basically contains an equivalent to "changed code or resources"
in that the code and resources in the pre-release do not exist on maven
central, which is where a maven build would normally get them.
When maven builds the pre-release it will not be able to find version 5.1.0 of
any jars through maven central, so it will look for them in your local .m2
directory.
Maven puts the 5.1.0 jars in your .m2 directory when you run 'mvn install' on
the main ctakes project.
In summary,
To build ctakes-web-rest to test the pre-release war, one must run 'mvn
install' on the ctakes main project before they run 'mvn package' on the
ctakes-web-rest project (or on the main project's web-rest-build profile).
To build ctakes-web-rest once ctakes 5.1.0 has been released, the extra
preliminary step of running 'mvn install' will not be necessary.
* If you have some time this week, we can connect to understand what
exactly is the problem.
I can meet you tomorrow evening your time (4-7 pm IST) to work with you in the
SQL problem. If you'd rather keep your Friday night to yourself, I can work
with the same time slot any time through next Monday evening.
Before the 6.0.0 release I will put some Release Manager information in the
wiki. The maven release process using a GitHub repo requires a little trick
that took me a long time to figure out, and the pre-release testing deserves
some recorded documentation.
Sean
From: gandhi rajan
Sent: Thursday, May 2, 2024 1:42 AM
To: dev@ctakes.apache.org
Subject: Re: Please test the Apache cTAKES 5.1.0 release candidate [EXTERNAL]
* External Email - Caution *
Hi Sean,
Thanks for the update. So post release I would be able to run mvn clean
install on web rest module rather than relying on resources in .m2 folder
you mean? Infact I was trying to build them on a machine which doesnt have
any historic jars in the .m2 folder and thats why it was failing.
And ytex issue still remains a mystery to me. If you have some time this
week, we can connect to understand what exactly is the problem.
On Thu, 2 May 2024 at 02:32, Finan, Sean
wrote:
> Hi Gandhi,
>
> I can build the web-rest module. I should have mentioned that to build
> any of the rest projects you need to run mvn install. As the rest requires
> 5.1.0 module jars and they don't exist externally (pre-release), maven must
> be able to fetch them from your .m2 directory.
>
> I haven't been able to duplicate the ytex problems that you see and don't
> know what might be causing them.
>
> Sean
>
>
> From: gandhi rajan
> Sent: Tuesday, April 30, 2024 11:18 AM
> To: dev@ctakes.apache.org
> Subject: Re: Please test the Apache cTAKES 5.1.0 release candidate
> [EXTERNAL]
>
> * External Email - Caution *
>
>
> Hi Peter,
>
> Thanks for the response. I dont think the generate test action is trying to
> use mysql but hsql DB. Anyways, I am able to build other modules apart from
> ytex and ytex-uima module.
>
> Sean, did you try building ctakes-web-rest module by any chance? It seems
> to be broken in my case.
>
> On Tue, 30 Apr 2024 at 01:28, Peter Abramowitsch
> wrote:
>
> > Hi Gandhi, I think the email from Jeff Painter may explain your
> > situation. It's a question of your version of mysql being new. The
> > crucial lines in your trace are:
> >
> > org.apache.ctakes.jdl.AppMain.main(AppMain.java:84)
> > [INFO] [java] Caused by:
> > java.lang.reflect.InaccessibleObjectException: Unable to make protected
> > final java.lang.Class
> > java.lang.ClassLoader.defineClass(java.lang.String,byte[],int,int) throws
> > java.lang.ClassFormatError accessible: module java.base does not "opens
> > java.lang" to unnamed module @61ca2dfa
> >
> > And this makes it sound like it is expecting a library version where
> > certain classnames or accessibility has changed. Check Jeff's
