You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Leonard Gestrin <Le...@markettools.com> on 2006/11/04 01:05:43 UTC
partial answer to first part: RE: selecting active profiles and maven-help-plugin does not work as expected/configuring plugin-repository cauze plugin to be not executed?
Apparently, 1.4.6 version of jspc-maven-plugin is invoked for goals that
after "compile" (like install)
And 1.4.5 version of jspc-maven-plugin is invoked for "compile" also.
It's defined like this in pom.xml
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>jspc-maven-plugin</artifactId>
<!--<version>1.4.5</version>-->
<executions>
<execution>
<id>jspc</id>
<goals>
<goal>compile</goal>
</goals>
</execution>
</executions>
<!--
<configuration>
<warSourceDirectory>${basedir}/target/webapp-panel</warSourceDirectory>
</configuration>
-->
</plugin>
-----Original Message-----
From: Leonard Gestrin [mailto:Leonard.Gestrin@markettools.com]
Sent: Friday, November 03, 2006 3:32 PM
To: Maven Users List
Subject: RE: selecting active profiles and maven-help-plugin does not
work as expected/configuring plugin-repository cauze plugin to be not
executed?
Thanks, that was a good suggestion.
Apparently, when plugin directory is configured, the latest plugin
version for jspc is
..
[DEBUG] jspc-maven-plugin: resolved to version 1.4.6 from repository
ibiblio.org
..
If I don't use biblio, mvn uses 1.4.5, and it also prints this line in
debug output
..
[DEBUG] org.codehaus.mojo:jspc-maven-plugin:maven-plugin:1.4.5:runtime
(selected for runtime)
...
I don't get this line for version 1.4.6
Both plugins are installed in my local repository, but for some reason
1.4.6 is not get invoked for compilation.
P.S. am I correct in my observations for help plugin with active
profiles?
-----Original Message-----
From: Wayne Fay [mailto:waynefay@gmail.com]
Sent: Friday, November 03, 2006 2:26 PM
To: Maven Users List
Subject: Re: selecting active profiles and maven-help-plugin does not
work as expected/configuring plugin-repository cauze plugin to be not
executed?
Have you tried mvn -X ... to see additional debugging information? I'd
assume something is just not working right, and the stacktrace might
help you see/find it.
Wayne
On 11/3/06, Leonard Gestrin <Le...@markettools.com> wrote:
> Hello,
>
> I have the following setup:
>
> 1. Defined "internal" , "external" profiles in settings.xml and set
> "internal" as active. "external" profile has plugin repository
> configuration. (this play important role for some reason)
>
> 2. Defined "jsp-comp" profile to activate jsp compilation for the
build
> in "compile" goal in parent-pom.xml
>
> 3, webapp pom.xml uses the parent pom.
>
>
>
>
>
> $mvn -Pinternal, jsp-compile compile - I can see that internal and
> jsp-compile profiles are being used (jsps are compiled)
>
>
>
> $mvn -Pexternal, jsp-compile compile - I can see that external is
used
> but jsp-compile is ignored!. (jsps are not compiled)
>
>
>
> Anybody has any clue why this might be the case? Plugin "help" does
not
> seem to be helpful since it appears to simply print out settings.xml
(or
> it's portions) and can present flat pom.xml but seem to ignore
> information in parent's pom.xml with respect to profiles.
>
>
>
> I also noticed that jsp-compile does work in conjunction with
"external"
> profile if I comment out this section in "external" profile
definition.
>
>
>
> <pluginRepositories>
>
> <pluginRepository>
>
> <id>ibiblio.org</id>
>
> <name>Maven Plugin Repository</name>
>
> <layout>default</layout>
>
> <url>http://www.ibiblio.org/maven2</url>
>
> <snapshots>
>
> <updatePolicy>interval:60</updatePolicy>
>
> <enabled>false</enabled>
>
> </snapshots>
>
> <releases>
>
> <updatePolicy>never</updatePolicy>
>
> </releases>
>
> </pluginRepository>
>
>
>
>
>
>
>
> Executing commands in webapp dir
>
>
>
> $mvn help:effective-setting prints "internal" is active.
>
>
>
> $mvn -Pexternal help:effective-setting prints "internal" is active
> again. <- is this wrong? The book says that -P option should
overwrite
> active profile? When I build application I do see that external
profile
> is being used.
>
>
>
> Thanks
>
> Leonard
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: partial answer to first part: RE: selecting active profiles and maven-help-plugin does not work as expected/configuring plugin-repository cauze plugin to be not executed?
Posted by Wayne Fay <wa...@gmail.com>.
I actually use the "test" or "package" phases myself by default when
I'm working on webapps, not "compile", so I haven't noticed this
myself.
You could dig into the jspc-maven-plugin to find out what phase(s) the
plugin is configured to run in by default. And of course you can tell
the plugin to execute in a particular phase (in addition to its
default) in your own pom.
Perhaps you could start using a phase other than compile when you run
mvn and you want to have your JSPs compiled?
Wayne
On 11/3/06, Leonard Gestrin <Le...@markettools.com> wrote:
> Apparently, 1.4.6 version of jspc-maven-plugin is invoked for goals that
> after "compile" (like install)
> And 1.4.5 version of jspc-maven-plugin is invoked for "compile" also.
>
> It's defined like this in pom.xml
>
>
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>jspc-maven-plugin</artifactId>
> <!--<version>1.4.5</version>-->
> <executions>
> <execution>
> <id>jspc</id>
> <goals>
> <goal>compile</goal>
> </goals>
> </execution>
> </executions>
> <!--
> <configuration>
>
> <warSourceDirectory>${basedir}/target/webapp-panel</warSourceDirectory>
> </configuration>
> -->
> </plugin>
>
>
>
> -----Original Message-----
> From: Leonard Gestrin [mailto:Leonard.Gestrin@markettools.com]
> Sent: Friday, November 03, 2006 3:32 PM
> To: Maven Users List
> Subject: RE: selecting active profiles and maven-help-plugin does not
> work as expected/configuring plugin-repository cauze plugin to be not
> executed?
>
> Thanks, that was a good suggestion.
>
> Apparently, when plugin directory is configured, the latest plugin
> version for jspc is
>
> ..
> [DEBUG] jspc-maven-plugin: resolved to version 1.4.6 from repository
> ibiblio.org
> ..
> If I don't use biblio, mvn uses 1.4.5, and it also prints this line in
> debug output
>
> ..
> [DEBUG] org.codehaus.mojo:jspc-maven-plugin:maven-plugin:1.4.5:runtime
> (selected for runtime)
> ...
>
> I don't get this line for version 1.4.6
>
> Both plugins are installed in my local repository, but for some reason
> 1.4.6 is not get invoked for compilation.
>
>
> P.S. am I correct in my observations for help plugin with active
> profiles?
>
>
> -----Original Message-----
> From: Wayne Fay [mailto:waynefay@gmail.com]
> Sent: Friday, November 03, 2006 2:26 PM
> To: Maven Users List
> Subject: Re: selecting active profiles and maven-help-plugin does not
> work as expected/configuring plugin-repository cauze plugin to be not
> executed?
>
> Have you tried mvn -X ... to see additional debugging information? I'd
> assume something is just not working right, and the stacktrace might
> help you see/find it.
>
> Wayne
>
> On 11/3/06, Leonard Gestrin <Le...@markettools.com> wrote:
> > Hello,
> >
> > I have the following setup:
> >
> > 1. Defined "internal" , "external" profiles in settings.xml and set
> > "internal" as active. "external" profile has plugin repository
> > configuration. (this play important role for some reason)
> >
> > 2. Defined "jsp-comp" profile to activate jsp compilation for the
> build
> > in "compile" goal in parent-pom.xml
> >
> > 3, webapp pom.xml uses the parent pom.
> >
> >
> >
> >
> >
> > $mvn -Pinternal, jsp-compile compile - I can see that internal and
> > jsp-compile profiles are being used (jsps are compiled)
> >
> >
> >
> > $mvn -Pexternal, jsp-compile compile - I can see that external is
> used
> > but jsp-compile is ignored!. (jsps are not compiled)
> >
> >
> >
> > Anybody has any clue why this might be the case? Plugin "help" does
> not
> > seem to be helpful since it appears to simply print out settings.xml
> (or
> > it's portions) and can present flat pom.xml but seem to ignore
> > information in parent's pom.xml with respect to profiles.
> >
> >
> >
> > I also noticed that jsp-compile does work in conjunction with
> "external"
> > profile if I comment out this section in "external" profile
> definition.
> >
> >
> >
> > <pluginRepositories>
> >
> > <pluginRepository>
> >
> > <id>ibiblio.org</id>
> >
> > <name>Maven Plugin Repository</name>
> >
> > <layout>default</layout>
> >
> > <url>http://www.ibiblio.org/maven2</url>
> >
> > <snapshots>
> >
> > <updatePolicy>interval:60</updatePolicy>
> >
> > <enabled>false</enabled>
> >
> > </snapshots>
> >
> > <releases>
> >
> > <updatePolicy>never</updatePolicy>
> >
> > </releases>
> >
> > </pluginRepository>
> >
> >
> >
> >
> >
> >
> >
> > Executing commands in webapp dir
> >
> >
> >
> > $mvn help:effective-setting prints "internal" is active.
> >
> >
> >
> > $mvn -Pexternal help:effective-setting prints "internal" is active
> > again. <- is this wrong? The book says that -P option should
> overwrite
> > active profile? When I build application I do see that external
> profile
> > is being used.
> >
> >
> >
> > Thanks
> >
> > Leonard
> >
> >
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org