BTW, I am using JDK 1.8 on Mac. Not sure if anything special did by Apple.
:)
regards,
Lin
On Thu, Apr 16, 2015 at 3:43 PM, Lin Ma wrote:
> Thanks Gruss for the details,
>
> I tried mvn -U help:effective-pom -Doutput=epom.xml, and find
> sourceDirectory is without "main" directory in the midd
Thanks Gruss for the details,
I tried mvn -U help:effective-pom -Doutput=epom.xml, and find
sourceDirectory is without "main" directory in the middle, which conform to
what compiles actually when I execute mvn package.
Then I tried mvn -U
org.apache.maven.plugins:maven-dependency-plugin:2.10:di
Am Wed, 15 Apr 2015 14:49:21 -0700
schrieb Lin Ma :
> The document is very helpful. Any thoughts how to check why
> src/java/com/foo/goo works is great. Is there some other files like
> super POM or other files to check? Thanks.
You can print out the effective pom and check if sourceDirectory is
> > > > > > > > looks like your pom reconfigures the default source ( ie
> > > > > > > > build-->sourceDirectory) this may help
> > > > > > > > https://maven.apache.org/pom.html
> > > > > > > &g
? this may help
> > > > > > > https://maven.apache.org/pom.html
> > > > > > >
> > > > > > > -D
> > > > > > >
> > > > > > > On Sat, Apr 11, 2015 at 10:06 PM, Lin Ma
> > > > > > >
> > wro
Dan
On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma
wrote:
Hi Maven masters,
For maven-compiler-plugin, how to check what are the source
files/directories it will scan for to compile? And add other
source
file
directories? Thanks.
thanks in advance,
Lin
---
gt; > >
> > > > > >> Hi Dan,
> > > > > >>
> > > > > >> I have this question since I tried it compiles fine with sources
> > in
> > > > > >> src/java/com/foo/..., are they default location as well? I do
> not
> > > find
> > > > > >> sub-directory "main" in the middle of the path.
> > > > > >>
> > > > > >> regards,
> > > > > >> Lin
> > > > > >>
> > > > > >> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran
> > > wrote:
> > > > > >>
> > > > > >> > default main source is at src/main/java
> > > > > >> >
> > > > > >> > to add more sources, use build-helper-maven-plugin
> > > > > >> >
> > > > > >> > -Dan
> > > > > >> >
> > > > > >> > On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma
> > wrote:
> > > > > >> >
> > > > > >> > > Hi Maven masters,
> > > > > >> > >
> > > > > >> > > For maven-compiler-plugin, how to check what are the source
> > > > > >> > > files/directories it will scan for to compile? And add other
> > > > source
> > > > > >> file
> > > > > >> > > directories? Thanks.
> > > > > >> > >
> > > > > >> > > thanks in advance,
> > > > > >> > > Lin
> > > > > >> > >
> > > > > >> >
> > > > > >>
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
> > > >> Hi Dan,
> > > > >>
> > > > >> I have this question since I tried it compiles fine with sources
> in
> > > > >> src/java/com/foo/..., are they default location as well? I do not
> > find
> > > > >> s
> >> regards,
> > > >> Lin
> > > >>
> > > >> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran
> wrote:
> > > >>
> > > >> > default main source is at src/main/java
> > > >> >
> > > >> > to add more sources, use build-helper-maven-plugin
> > > >> >
> > > >> > -Dan
> > > >> >
> > > >> > On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma wrote:
> > > >> >
> > > >> > > Hi Maven masters,
> > > >> > >
> > > >> > > For maven-compiler-plugin, how to check what are the source
> > > >> > > files/directories it will scan for to compile? And add other
> > source
> > > >> file
> > > >> > > directories? Thanks.
> > > >> > >
> > > >> > > thanks in advance,
> > > >> > > Lin
> > > >> > >
> > > >> >
> > > >>
> > > >
> > > >
> > >
> >
>
dle of the path.
> > >>
> > >> regards,
> > >> Lin
> > >>
> > >> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran wrote:
> > >>
> > >> > default main source is at src/main/java
> > >> >
> > >> &
"main" in the middle of the path.
> > > >>
> > > >> regards,
> > > >> Lin
> > > >>
> > > >> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran
> wrote:
> > > >>
> > > >&
ds,
> > >> Lin
> > >>
> > >> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran wrote:
> > >>
> > >> > default main source is at src/main/java
> > >> >
> > >> > to add more sources, use build-hel
2015 at 9:59 PM, Dan Tran wrote:
> >>
> >> > default main source is at src/main/java
> >> >
> >> > to add more sources, use build-helper-maven-plugin
> >> >
> >> > -Dan
> >> >
> >> > On Sat, Apr 1
t;>
>> regards,
>> Lin
>>
>> On Sat, Apr 11, 2015 at 9:59 PM, Dan Tran wrote:
>>
>> > default main source is at src/main/java
>> >
>> > to add more sources, use build-helper-maven-plugin
>> >
>> > -Dan
>> >
e sources, use build-helper-maven-plugin
> >
> > -Dan
> >
> > On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma wrote:
> >
> > > Hi Maven masters,
> > >
> > > For maven-compiler-plugin, how to check what are the source
> > > files/directories it will scan for to compile? And add other source
> file
> > > directories? Thanks.
> > >
> > > thanks in advance,
> > > Lin
> > >
> >
>
s at src/main/java
>
> to add more sources, use build-helper-maven-plugin
>
> -Dan
>
> On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma wrote:
>
> > Hi Maven masters,
> >
> > For maven-compiler-plugin, how to check what are the source
> > files/director
default main source is at src/main/java
to add more sources, use build-helper-maven-plugin
-Dan
On Sat, Apr 11, 2015 at 8:10 PM, Lin Ma wrote:
> Hi Maven masters,
>
> For maven-compiler-plugin, how to check what are the source
> files/directories it will scan for to compile? A
Hi Maven masters,
For maven-compiler-plugin, how to check what are the source
files/directories it will scan for to compile? And add other source file
directories? Thanks.
thanks in advance,
Lin
an example of how this is
done.
--
View this message in context:
http://maven.40175.n5.nabble.com/Separate-executions-for-maven-compiler-plugin-tp3300553p3300553.html
Sent from the Maven - Users mailing list archive at Nabble.com.
: Thu, 11 Jun 2009 18:37:42 -0500
> Subject: Re: "always compile option" for maven-compiler-plugin?
> From: l...@leemeador.com
> To: users@maven.apache.org
>
> Or you could put an antrun task to run in generate-sources that would delete
> all the class files in target/clas
Or you could put an antrun task to run in generate-sources that would delete
all the class files in target/classes and target/testclasses every time
before compiling. (Oh and check my spelling there.)
-- Lee
On Wed, Jun 10, 2009 at 12:29 PM, Wayne Fay wrote:
> > anyway to request maven-compiler
> anyway to request maven-compiler-plugin "always compile"
> (instead of check source newer than class)
If not, it would be pretty simple to add.
Having said that, the recommended approach would be to always use "mvn
clean ..." which will delete the files in /target, thus guaranteeing
the "always
Hi Folks
currently using the maven-compiler-plugin d/l from
http://maven.apache.org/plugins/maven-compiler-plugin
anyway to request maven-compiler-plugin "always compile"
(instead of check source newer than class)
?
thanks!
Martin Gainty
__
Verzicht
I saw this thread and figured this must be a simple bug. I dug into
the sources (of Maven and Plexus) and found what I believe is the root
of the problem. In short, while the Maven plugin supports the verbose
configuration, the underlying plexus-compiler does not, so it never
does anything no matte
I filed http://jira.codehaus.org/browse/MNG-3764.
As a work around, I am thinking of setting fork=true and passing
-verbose as option to compiler.
Sahoo
Gabriel Garcia wrote:
Count me in for someone that wanted to compile with more verbosity
(e.g., to see warnings properly). The only thing th
Count me in for someone that wanted to compile with more verbosity
(e.g., to see warnings properly). The only thing that worked for me is
seeing the deprecated classes (which is another parameter). Other than
that, verbose=true didn't work.
Gabriel
2008/9/24 Sahoo <[EMAIL PROTECTED]>:
> Has anyo
Has anyone experienced this problem?
--- Begin Message ---
I don't see the effect of true. When I run with -X, I
do see that verbose = true, but I don't see it being passed to javac. I
tried with fork = true and the command line that was used to invoke
javac did not have verbose option set. I
I don't see the effect of true. When I run with -X, I
do see that verbose = true, but I don't see it being passed to javac. I
tried with fork = true and the command line that was used to invoke
javac did not have verbose option set. I am using default compiler.
Thanks,
Sahoo
---
t;>>
>>>> Have all your projects with a common parent.
>>>>
>>>> In the common parent add a pluginManagement section that defines the
>>>> defaults for the compiler plugin.
>>>>
>>>> On Fri, Aug 15, 2008 at 1:51 PM, monika7
parent.
In the common parent add a pluginManagement section that defines
the
defaults for the compiler plugin.
On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]>
wrote:
I know that current default for maven-compiler-plugin is java 1.3
and
that
I
can override it in pom.xml
de it.
-Original Message-
From: Trent Rosenbaum [mailto:[EMAIL PROTECTED]
Sent: Friday, August 15, 2008 6:59 AM
To: Maven Users List
Subject: Re: Changing default compiler version for maven-compiler-plugin
(outside pom.xml)
I use the pom approach suggested, but the sonatype book shows an examp
parent.
>>>
>>> In the common parent add a pluginManagement section that defines the
>>> defaults for the compiler plugin.
>>>
>>> On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]>
>>> wrote:
>>>
>>>>
>>>&g
projects with a common parent.
In the common parent add a pluginManagement section that defines the
defaults for the compiler plugin.
On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]>
wrote:
I know that current default for maven-compiler-plugin is java 1.3
and
tha
rmanently
>> without having to include the plugin in pom.xml.
>> I don't see anything in the settings.xml that would allow me to do it. Is
>> that possible and if yes, can someone suggest how to do it?
>> --
>> View this message in context:
>> http://www.nabble
;
> > On 15/08/2008, Stephen Connolly <[EMAIL PROTECTED]> wrote:
> > >
> > > Have all your projects with a common parent.
> > >
> > > In the common parent add a pluginManagement section that defines the
> > > defaults for the compiler plugin.
&
> >
> > Have all your projects with a common parent.
> >
> > In the common parent add a pluginManagement section that defines the
> > defaults for the compiler plugin.
> >
> > On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]> wrote:
> >
t;> defaults for the compiler plugin.
>>
>> On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]> wrote:
>>
>> >
>> > I know that current default for maven-compiler-plugin is java 1.3 and
>> that
>> > I
>> > can override it
5, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]> wrote:
>
> >
> > I know that current default for maven-compiler-plugin is java 1.3 and
> that
> > I
> > can override it in pom.xml file by adding source and target attributes to
> > the plugin configuration
Have all your projects with a common parent.
In the common parent add a pluginManagement section that defines the
defaults for the compiler plugin.
On Fri, Aug 15, 2008 at 1:51 PM, monika7 <[EMAIL PROTECTED]> wrote:
>
> I know that current default for maven-compiler-plugin is java
I know that current default for maven-compiler-plugin is java 1.3 and that I
can override it in pom.xml file by adding source and target attributes to
the plugin configuration.
However I would prefer to override the default compiler version permanently
without having to include the plugin in
Maven does not really "like" passing things via arguments -- this is
the exception rather than the norm.
You could probably use -Dmy.arg="blah blah" and then in the
m-compiler-p set ${my.arg}. But this is not the
"right" way to use Maven.
If you have a few different sets of arguments, you should
Hello,
Regarding maven-compiler-plugin, is there a way to pass compiler arguments
on the command line rather than through pom.xml? I don't find "expression"
defined in its manual page though.
Thanks
Yan
Appears to be a brain explosion on my part. Fixed.
- Brett
On 11/5/05, KC Baltz <[EMAIL PROTECTED]> wrote:
> The documentation for the compiler plugin says that the "debug" parameter is
> deprecated. Why is this and what's the recommended replacement?
>
> http://maven.apache.org/plugins/maven-c
The documentation for the compiler plugin says that the "debug" parameter is
deprecated. Why is this and what's the recommended replacement?
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html
K.C.
Please file this in JIRA - it looks like it should work to me.
- Brett
On 11/2/05, Lars Trieloff <[EMAIL PROTECTED]> wrote:
> Hi,
>
> according to the maven-compiler-plugin documentation I can set the
> compiler to be used by adding the compilerId element to my pom.xml.
>
> However my small examp
Hi,
according to the maven-compiler-plugin documentation I can set the
compiler to be used by adding the compilerId element to my pom.xml.
However my small example POM which includes following build
configuration is unable to work with maven.
maven-compiler-plug
46 matches
Mail list logo
