[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
To: Maven Users List
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 th
parator.
>
> So I'am not sure how to deal with this situation with maven and or javac.
>
>
> -Original Message-
> From: Alexander Kriegisch
> Sent: Tuesday, November 12, 2024 9:31 AM
> To: Maven Users List
> Subject: [EXTERNAL] RE: RE: RE: Re: maven co
Le 2024-11-12 à 08 h 29, Grégory Jevardat De Fombelle a écrit :
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.
Just for information, the proposed 4.0.0-beta-2 version of the c
From: Alexander Kriegisch
Sent: Tuesday, November 12, 2024 9:31 AM
To: Maven Users List
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 Fombel
lved and there is no issue on the
>compiler side
>Cheers
>
>-Original Message-
>From: Grégory Jevardat De Fombelle
>Sent: Tuesday, November 12, 2024 8:38 AM
>To: Maven Users List
>Subject: [EXTERNAL] RE: RE: Re: maven compiler plugin question
>
>I spotted the
ge-
From: Grégory Jevardat De Fombelle
Sent: Tuesday, November 12, 2024 8:29 AM
To: Maven Users List
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 b
ardat De Fombelle
Sent: Tuesday, November 12, 2024 8:29 AM
To: Maven Users List
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 some
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
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
Hello
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
In maven I started to generate this file and try to add it in the co
The includes parameter works only on files inside the
compileSourceRoots. So if you have compileSourceRoots as
"src/main/java" and have include as "src/generated/java" then the
compiler searches for "src/main/java/src/generated/java".
Even if you put ${basedir} in the includes, it will stil
Thanks! Like moving the "generated" sources to "src/main", that does
solve my immediate need, but there might be source in the "real"
source directory in the future and that those (pre)generated sources
will eventually get generated in the correct way, I hope.
The question still remains about ho
If there are no sources in src/main/java but only in src/generated/java why
don't you set the project source root to src/generated/java like this:
...
${basedir}/src/generated/java
...
Kind regards,
Valeri Felberg
On 6/29/06, Mykel Alvis <[EMAIL PROTECTED]> wrote:
I may have misconfigured
I may have misconfigured it, but the
/home/malvis/code/test-checkout/orm/src/main/java reference comes for free,
since /home/.../orm is the project's base directory.
The sources are ONLY in src/generated/java. There are no sources in
src/main/java. The generated sources are generated prior to s
I think you misconfigured it.
You've set the includes to search only in src/generate/java but it seems
like the generated sources are in src/main/java (from
/home/malvis/code/test-checkout/orm/src/main/java).
Hope that helps.
^_^
Mykel Alvis wrote:
Sorry if this is a repeat, but I haven
Sorry if this is a repeat, but I haven't located an answer on the web
anywhere.
I found http://jira.codehaus.org/browse/MCOMPILER-26 but it appears closed.
In the pom of a module, I have included the following:
org.apache.maven.plugins
maven-compiler-pl
17 matches
Mail list logo