You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID> on 2024/11/12 08:25:58 UTC
RE: [EXTERNAL] RE: RE: Re: maven compiler plugin question
Ok sorry for the spam but I found that it is not a too long classpath issue.
One jar in the classpath is causing a strange error
[ERROR] error: illegal argument for --class-path: Illegal char <:> at index 54: C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/.:lib
I don't know what's wrong with this guy, it is available in the repo and the classpath displayed in the error message is not the actual path file in the generated option file:
C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/jhealpix-3.2.0.jar
There is something really strange happening here , maybe some conflicting jar libs ?
...
Good news is that the problem is being solved and there is no issue on the compiler side
Cheers
-----Original Message-----
From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
Sent: Tuesday, November 12, 2024 8:38 AM
To: Maven Users List <us...@maven.apache.org>
Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
I spotted the generated option files in the target folder and the javac.bat script to launch java using this option file.
So now I'am even more puzzled as these options files are supposed to solve the too long class path issue !
...
To follow
-----Original Message-----
From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
Sent: Tuesday, November 12, 2024 8:29 AM
To: Maven Users List <us...@maven.apache.org>
Subject: [EXTERNAL] RE: Re: maven compiler plugin question
Indeed, you are right.
Actually I wanted to use arg files to solve the too long class path on Windows... I though fork would be enough but there is something else that I don't understand.
I checked in the code of the plexus javac compiler and internally it already generates an @option file with all args passed to JVM in fork mode.
What is curious is that I don't see this option appearing in command line using mvn -X I just see plain args on the terminal.
Any hints ?
Thanks
-----Original Message-----
From: Martin Desruisseaux <ma...@geomatys.com>
Sent: Monday, November 11, 2024 5:02 PM
To: users@maven.apache.org
Subject: [EXTERNAL] Re: maven compiler plugin question
Hello
Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
> I have difficulties finding documentation on the support of Java arguments files on the maven compiler plugin.
> I'd like to put my long classpath in a file and use it as in javac documentation for : javac @classpath ....
I think that the support of "@option-file" syntax is specific to the javac command tool. which would expand this option before to pass it to the compiler. I just verified that "@option-file" is not supported by javax.tools.JavaCompiler. Maven 3 uses the Plexus compiler, but I presume that it doesn't expand that option neither.
I don't know if we want to add similar functionality to Maven compiler plugin. But if so, it would be useful to know why options in a file are desired, in order to see if it would be possible to do the same in a more "Maven way".
Martin
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Ce message est envoyé depuis une adresse extérieure à l'UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
This message is sent from an address outside UNIGE, be careful (sender, content).
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
This message is sent from an address outside UNIGE, be careful (sender, content).
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
This message is sent from an address outside UNIGE, be careful (sender, content).
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [EXTERNAL] Re: RE: RE: RE: Re: maven compiler plugin question
Posted by Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>.
Thanks for suggestion
I replaced this lib, as it was deprecated and superseded by another one called cds-healpix without too many API changes.
Problem solved on my side !
Thanks for all hints in any case there are no maven issues here. I started with the wrong diagnostic thinking it was caused by the length of the classpath, even if the error message was actually clear (once you understand the actual issue) ☹ But I had not clue that one of the lib had this custom class-path !
Cheers
Gregory
-----Original Message-----
From: Mantas Gridinas <mg...@gmail.com>
Sent: Tuesday, November 12, 2024 10:11 AM
To: Maven Users List <us...@maven.apache.org>
Subject: [EXTERNAL] Re: RE: RE: RE: Re: maven compiler plugin question
It's a dirty workaround but you could run ant task to replace the manifest in that jar, asuming you don't care about signatures.
jar uvf foo.jar META-INF/MANIFEST.MF
Where the new manifest is the one that does not care about classpath entry (not that you should unless you're building "main" jar).
On Tue, Nov 12, 2024, 10:37 Grégory Jevardat De Fombelle <Gr...@unige.ch.invalid> wrote:
> Ok I found the exact explanation:
>
> This specific library has a MANIFEST file containing a classpath as follow:
>
> Class-Path: .:lib
>
> Obviously it breaks the rule of class separator.
>
> So I'am not sure how to deal with this situation with maven and or javac.
>
>
> -----Original Message-----
> From: Alexander Kriegisch <Al...@Kriegisch.name>
> Sent: Tuesday, November 12, 2024 9:31 AM
> To: Maven Users List <us...@maven.apache.org>
> Subject: [EXTERNAL] RE: RE: RE: Re: maven compiler plugin question
>
> On Windows, the path separator is not a colon but a semicolon.
>
>
>
> Am 12. November 2024 15:25:58 GMT+07:00 schrieb "Grégory Jevardat De
> Fombelle" <Gr...@unige.ch.INVALID>:
> >Ok sorry for the spam but I found that it is not a too long classpath
> issue.
> >
> >One jar in the classpath is causing a strange error [ERROR] error:
> >illegal argument for --class-path: Illegal char <:> at index 54:
> >C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/.:lib
> >
> >I don't know what's wrong with this guy, it is available in the repo
> >and
> the classpath displayed in the error message is not the actual path
> file in the generated option file:
> >C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/jhealpix-3.2.0.j
> >ar
> >
> >There is something really strange happening here , maybe some
> >conflicting
> jar libs ?
> >
> >...
> >Good news is that the problem is being solved and there is no issue
> >on the compiler side Cheers
> >
> >-----Original Message-----
> >From: Grégory Jevardat De Fombelle
> ><Gr...@unige.ch.INVALID>
> >Sent: Tuesday, November 12, 2024 8:38 AM
> >To: Maven Users List <us...@maven.apache.org>
> >Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
> >
> >I spotted the generated option files in the target folder and the
> javac.bat script to launch java using this option file.
> >So now I'am even more puzzled as these options files are supposed to
> solve the too long class path issue !
> >
> >...
> >To follow
> >
> >
> >-----Original Message-----
> >From: Grégory Jevardat De Fombelle
> ><Gr...@unige.ch.INVALID>
> >Sent: Tuesday, November 12, 2024 8:29 AM
> >To: Maven Users List <us...@maven.apache.org>
> >Subject: [EXTERNAL] RE: Re: maven compiler plugin question
> >
> >Indeed, you are right.
> >
> >Actually I wanted to use arg files to solve the too long class path
> >on
> Windows... I though fork would be enough but there is something else
> that I don't understand.
> >
> >I checked in the code of the plexus javac compiler and internally it
> already generates an @option file with all args passed to JVM in fork mode.
> >What is curious is that I don't see this option appearing in command
> >line
> using mvn -X I just see plain args on the terminal.
> >
> >Any hints ?
> >Thanks
> >
> >-----Original Message-----
> >From: Martin Desruisseaux <ma...@geomatys.com>
> >Sent: Monday, November 11, 2024 5:02 PM
> >To: users@maven.apache.org
> >Subject: [EXTERNAL] Re: maven compiler plugin question
> >
> >Hello
> >
> >Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
> >
> >> I have difficulties finding documentation on the support of Java
> arguments files on the maven compiler plugin.
> >> I'd like to put my long classpath in a file and use it as in javac
> documentation for : javac @classpath ....
> >
> >I think that the support of "@option-file" syntax is specific to the
> javac command tool. which would expand this option before to pass it
> to the compiler. I just verified that "@option-file" is not supported
> by javax.tools.JavaCompiler. Maven 3 uses the Plexus compiler, but I
> presume that it doesn't expand that option neither.
> >
> >I don't know if we want to add similar functionality to Maven
> >compiler
> plugin. But if so, it would be useful to know why options in a file
> are desired, in order to see if it would be possible to do the same in
> a more "Maven way".
> >
> > Martin
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >Ce message est envoyé depuis une adresse extérieure à l'UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> >This message is sent from an address outside UNIGE, be careful
> >(sender,
> content).
> >
> >---------------------------------------------------------------------
> >--
> >-------
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> >This message is sent from an address outside UNIGE, be careful
> >(sender,
> content).
> >
> >---------------------------------------------------------------------
> >--
> >-------
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> >This message is sent from an address outside UNIGE, be careful
> >(sender,
> content).
> >
> >---------------------------------------------------------------------
> >--
> >-------
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
>
>
> Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> This message is sent from an address outside UNIGE, be careful
> (sender, content).
>
>
> ----------------------------------------------------------------------
> --------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
This message is sent from an address outside UNIGE, be careful (sender, content).
------------------------------------------------------------------------------
Re: maven compiler plugin question
Posted by Stanimir Stamenkov <s7...@aim.com.INVALID>.
[Re-sending to the list.]
On Tue, Nov 12, 2024, 10:37 Grégory Jevardat De Fombelle wrote:
> Ok I found the exact explanation:
>
> This specific library has a MANIFEST file containing a classpath as follow:
>
> Class-Path: .:lib
>
> Obviously it breaks the rule of class separator.
Shouldn't the manifest Class-Path use space separator?
*
https://docs.oracle.com/javase/8/docs/technotes/guides/jar/jar.html#classpath
(looking at the examples)
Then shouldn't directory entries end with a / (slash)?
> ... These relative URLs may include JAR files and directories for any
> libraries or resources needed by the application. Relative URLs not
> ending with a slash (/) are assumed to refer to JAR files.
--
Stanimir
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [EXTERNAL] RE: RE: RE: Re: maven compiler plugin question
Posted by Mantas Gridinas <mg...@gmail.com>.
It's a dirty workaround but you could run ant task to replace the manifest
in that jar, asuming you don't care about signatures.
jar uvf foo.jar META-INF/MANIFEST.MF
Where the new manifest is the one that does not care about classpath entry
(not that you should unless you're building "main" jar).
On Tue, Nov 12, 2024, 10:37 Grégory Jevardat De Fombelle
<Gr...@unige.ch.invalid> wrote:
> Ok I found the exact explanation:
>
> This specific library has a MANIFEST file containing a classpath as follow:
>
> Class-Path: .:lib
>
> Obviously it breaks the rule of class separator.
>
> So I'am not sure how to deal with this situation with maven and or javac.
>
>
> -----Original Message-----
> From: Alexander Kriegisch <Al...@Kriegisch.name>
> Sent: Tuesday, November 12, 2024 9:31 AM
> To: Maven Users List <us...@maven.apache.org>
> Subject: [EXTERNAL] RE: RE: RE: Re: maven compiler plugin question
>
> On Windows, the path separator is not a colon but a semicolon.
>
>
>
> Am 12. November 2024 15:25:58 GMT+07:00 schrieb "Grégory Jevardat De
> Fombelle" <Gr...@unige.ch.INVALID>:
> >Ok sorry for the spam but I found that it is not a too long classpath
> issue.
> >
> >One jar in the classpath is causing a strange error [ERROR] error:
> >illegal argument for --class-path: Illegal char <:> at index 54:
> >C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/.:lib
> >
> >I don't know what's wrong with this guy, it is available in the repo and
> the classpath displayed in the error message is not the actual path file in
> the generated option file:
> >C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/jhealpix-3.2.0.jar
> >
> >There is something really strange happening here , maybe some conflicting
> jar libs ?
> >
> >...
> >Good news is that the problem is being solved and there is no issue on
> >the compiler side Cheers
> >
> >-----Original Message-----
> >From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
> >Sent: Tuesday, November 12, 2024 8:38 AM
> >To: Maven Users List <us...@maven.apache.org>
> >Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
> >
> >I spotted the generated option files in the target folder and the
> javac.bat script to launch java using this option file.
> >So now I'am even more puzzled as these options files are supposed to
> solve the too long class path issue !
> >
> >...
> >To follow
> >
> >
> >-----Original Message-----
> >From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
> >Sent: Tuesday, November 12, 2024 8:29 AM
> >To: Maven Users List <us...@maven.apache.org>
> >Subject: [EXTERNAL] RE: Re: maven compiler plugin question
> >
> >Indeed, you are right.
> >
> >Actually I wanted to use arg files to solve the too long class path on
> Windows... I though fork would be enough but there is something else that I
> don't understand.
> >
> >I checked in the code of the plexus javac compiler and internally it
> already generates an @option file with all args passed to JVM in fork mode.
> >What is curious is that I don't see this option appearing in command line
> using mvn -X I just see plain args on the terminal.
> >
> >Any hints ?
> >Thanks
> >
> >-----Original Message-----
> >From: Martin Desruisseaux <ma...@geomatys.com>
> >Sent: Monday, November 11, 2024 5:02 PM
> >To: users@maven.apache.org
> >Subject: [EXTERNAL] Re: maven compiler plugin question
> >
> >Hello
> >
> >Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
> >
> >> I have difficulties finding documentation on the support of Java
> arguments files on the maven compiler plugin.
> >> I'd like to put my long classpath in a file and use it as in javac
> documentation for : javac @classpath ....
> >
> >I think that the support of "@option-file" syntax is specific to the
> javac command tool. which would expand this option before to pass it to the
> compiler. I just verified that "@option-file" is not supported by
> javax.tools.JavaCompiler. Maven 3 uses the Plexus compiler, but I presume
> that it doesn't expand that option neither.
> >
> >I don't know if we want to add similar functionality to Maven compiler
> plugin. But if so, it would be useful to know why options in a file are
> desired, in order to see if it would be possible to do the same in a more
> "Maven way".
> >
> > Martin
> >
> >
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >Ce message est envoyé depuis une adresse extérieure à l'UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> >This message is sent from an address outside UNIGE, be careful (sender,
> content).
> >
> >-----------------------------------------------------------------------
> >-------
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >
> >Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> >This message is sent from an address outside UNIGE, be careful (sender,
> content).
> >
> >-----------------------------------------------------------------------
> >-------
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
> >
> >
> >Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> >This message is sent from an address outside UNIGE, be careful (sender,
> content).
> >
> >-----------------------------------------------------------------------
> >-------
> >
> >---------------------------------------------------------------------
> >To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> >For additional commands, e-mail: users-help@maven.apache.org
>
>
> Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez
> vigilant-es (expéditeur, pièces jointes).
> This message is sent from an address outside UNIGE, be careful (sender,
> content).
>
>
> ------------------------------------------------------------------------------
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
RE: [EXTERNAL] RE: RE: RE: Re: maven compiler plugin question
Posted by Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>.
Ok I found the exact explanation:
This specific library has a MANIFEST file containing a classpath as follow:
Class-Path: .:lib
Obviously it breaks the rule of class separator.
So I'am not sure how to deal with this situation with maven and or javac.
-----Original Message-----
From: Alexander Kriegisch <Al...@Kriegisch.name>
Sent: Tuesday, November 12, 2024 9:31 AM
To: Maven Users List <us...@maven.apache.org>
Subject: [EXTERNAL] RE: RE: RE: Re: maven compiler plugin question
On Windows, the path separator is not a colon but a semicolon.
Am 12. November 2024 15:25:58 GMT+07:00 schrieb "Grégory Jevardat De Fombelle" <Gr...@unige.ch.INVALID>:
>Ok sorry for the spam but I found that it is not a too long classpath issue.
>
>One jar in the classpath is causing a strange error [ERROR] error:
>illegal argument for --class-path: Illegal char <:> at index 54:
>C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/.:lib
>
>I don't know what's wrong with this guy, it is available in the repo and the classpath displayed in the error message is not the actual path file in the generated option file:
>C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/jhealpix-3.2.0.jar
>
>There is something really strange happening here , maybe some conflicting jar libs ?
>
>...
>Good news is that the problem is being solved and there is no issue on
>the compiler side Cheers
>
>-----Original Message-----
>From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
>Sent: Tuesday, November 12, 2024 8:38 AM
>To: Maven Users List <us...@maven.apache.org>
>Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
>
>I spotted the generated option files in the target folder and the javac.bat script to launch java using this option file.
>So now I'am even more puzzled as these options files are supposed to solve the too long class path issue !
>
>...
>To follow
>
>
>-----Original Message-----
>From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
>Sent: Tuesday, November 12, 2024 8:29 AM
>To: Maven Users List <us...@maven.apache.org>
>Subject: [EXTERNAL] RE: Re: maven compiler plugin question
>
>Indeed, you are right.
>
>Actually I wanted to use arg files to solve the too long class path on Windows... I though fork would be enough but there is something else that I don't understand.
>
>I checked in the code of the plexus javac compiler and internally it already generates an @option file with all args passed to JVM in fork mode.
>What is curious is that I don't see this option appearing in command line using mvn -X I just see plain args on the terminal.
>
>Any hints ?
>Thanks
>
>-----Original Message-----
>From: Martin Desruisseaux <ma...@geomatys.com>
>Sent: Monday, November 11, 2024 5:02 PM
>To: users@maven.apache.org
>Subject: [EXTERNAL] Re: maven compiler plugin question
>
>Hello
>
>Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
>
>> I have difficulties finding documentation on the support of Java arguments files on the maven compiler plugin.
>> I'd like to put my long classpath in a file and use it as in javac documentation for : javac @classpath ....
>
>I think that the support of "@option-file" syntax is specific to the javac command tool. which would expand this option before to pass it to the compiler. I just verified that "@option-file" is not supported by javax.tools.JavaCompiler. Maven 3 uses the Plexus compiler, but I presume that it doesn't expand that option neither.
>
>I don't know if we want to add similar functionality to Maven compiler plugin. But if so, it would be useful to know why options in a file are desired, in order to see if it would be possible to do the same in a more "Maven way".
>
> Martin
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>Ce message est envoyé depuis une adresse extérieure à l'UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
>This message is sent from an address outside UNIGE, be careful (sender, content).
>
>-----------------------------------------------------------------------
>-------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
>This message is sent from an address outside UNIGE, be careful (sender, content).
>
>-----------------------------------------------------------------------
>-------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
>This message is sent from an address outside UNIGE, be careful (sender, content).
>
>-----------------------------------------------------------------------
>-------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
This message is sent from an address outside UNIGE, be careful (sender, content).
------------------------------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
RE: [EXTERNAL] RE: RE: Re: maven compiler plugin question
Posted by Alexander Kriegisch <Al...@Kriegisch.name>.
On Windows, the path separator is not a colon but a semicolon.
Am 12. November 2024 15:25:58 GMT+07:00 schrieb "Grégory Jevardat De Fombelle" <Gr...@unige.ch.INVALID>:
>Ok sorry for the spam but I found that it is not a too long classpath issue.
>
>One jar in the classpath is causing a strange error
>[ERROR] error: illegal argument for --class-path: Illegal char <:> at index 54: C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/.:lib
>
>I don't know what's wrong with this guy, it is available in the repo and the classpath displayed in the error message is not the actual path file in the generated option file:
>C:/Users/Greg/.m2/repository/jhealpix/jhealpix/3.2.0/jhealpix-3.2.0.jar
>
>There is something really strange happening here , maybe some conflicting jar libs ?
>
>...
>Good news is that the problem is being solved and there is no issue on the compiler side
>Cheers
>
>-----Original Message-----
>From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
>Sent: Tuesday, November 12, 2024 8:38 AM
>To: Maven Users List <us...@maven.apache.org>
>Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
>
>I spotted the generated option files in the target folder and the javac.bat script to launch java using this option file.
>So now I'am even more puzzled as these options files are supposed to solve the too long class path issue !
>
>...
>To follow
>
>
>-----Original Message-----
>From: Grégory Jevardat De Fombelle <Gr...@unige.ch.INVALID>
>Sent: Tuesday, November 12, 2024 8:29 AM
>To: Maven Users List <us...@maven.apache.org>
>Subject: [EXTERNAL] RE: Re: maven compiler plugin question
>
>Indeed, you are right.
>
>Actually I wanted to use arg files to solve the too long class path on Windows... I though fork would be enough but there is something else that I don't understand.
>
>I checked in the code of the plexus javac compiler and internally it already generates an @option file with all args passed to JVM in fork mode.
>What is curious is that I don't see this option appearing in command line using mvn -X I just see plain args on the terminal.
>
>Any hints ?
>Thanks
>
>-----Original Message-----
>From: Martin Desruisseaux <ma...@geomatys.com>
>Sent: Monday, November 11, 2024 5:02 PM
>To: users@maven.apache.org
>Subject: [EXTERNAL] Re: maven compiler plugin question
>
>Hello
>
>Le 2024-11-11 à 13 h 16, Grégory Jevardat De Fombelle a écrit :
>
>> I have difficulties finding documentation on the support of Java arguments files on the maven compiler plugin.
>> I'd like to put my long classpath in a file and use it as in javac documentation for : javac @classpath ....
>
>I think that the support of "@option-file" syntax is specific to the javac command tool. which would expand this option before to pass it to the compiler. I just verified that "@option-file" is not supported by javax.tools.JavaCompiler. Maven 3 uses the Plexus compiler, but I presume that it doesn't expand that option neither.
>
>I don't know if we want to add similar functionality to Maven compiler plugin. But if so, it would be useful to know why options in a file are desired, in order to see if it would be possible to do the same in a more "Maven way".
>
> Martin
>
>
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>Ce message est envoyé depuis une adresse extérieure à l'UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
>This message is sent from an address outside UNIGE, be careful (sender, content).
>
>------------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>
>Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
>This message is sent from an address outside UNIGE, be careful (sender, content).
>
>------------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org
>
>
>Ce message est envoyé depuis une adresse extérieure à l’UNIGE, soyez vigilant-es (expéditeur, pièces jointes).
>This message is sent from an address outside UNIGE, be careful (sender, content).
>
>------------------------------------------------------------------------------
>
>---------------------------------------------------------------------
>To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
>For additional commands, e-mail: users-help@maven.apache.org