Re: Maven variables

2010-08-04 Thread Flavio Pompermaier
Maybe you miss a reply:
I tried also with help:describe but, with this command, not all
parameters have an associated description of default value (although
it exists because I remember that the old site documentation says that
the default value for source is 1.4, for version 2.0.2 of the compiler
plugin).

The command I wrote was:

mvn help:describe -DgroupId=org.apache.maven.plugins
-DartifactId=maven-compiler-plugin -Dversion=2.0.2
-Dcmd=compiler:compile -Ddetail

did I miss something?

2010/8/3 Anders Hammar and...@hammar.net:
 As I describe in my blog post, the help mojo doesn't always exist. In those
 cases, help:describe would work. It's all in the post, with examples and
 all.

 /Anders

 On Tue, Aug 3, 2010 at 17:36, Flavio Pompermaier fla8...@gmail.com wrote:

 I tried the suggested command with the current version:
       mvn org.apache.maven.plugins:maven-compiler-plugin:2.3.1:help
 -Ddetail -Dgoal=compile
 and things are fine (as I was searching for).

 However for the old version I was searching for (2.0.2) it doesn't
 work..such auto-documentation was not implemented for that version..?
       mvn org.apache.maven.plugins:maven-compiler-plugin:2.0.2:help
 -Ddetail -Dgoal=compile

 2010/8/3 Flavio Pompermaier fla8...@gmail.com:
  I think you intend
 
  mvn help:describe -DgroupId=org.apache.maven.plugins
  -DartifactId=maven-compiler-plugin -Dversion=2.0.2
  -Dcmd=compiler:compile -Ddetail
 
  However such documentation doesn't show the default value of
  parameters (not all at least)!
 
  2010/8/3 Anders Hammar and...@hammar.net:
  You can always get the docs from the plugin. Here's how:
 
 http://www.sonatype.com/people/2010/06/diy-retrieving-a-maven-plugins-documentation/
 
  /Anders
 
  On Tue, Aug 3, 2010 at 14:12, Flavio Pompermaier fla8...@gmail.com
 wrote:
 
  Ok..so, if it is not defined how can I know the default value for
  source parameter in the maven-compiler-plugin verion 2.0.2 if the
  documentation is no more online?
  It should be 1.4 but I want to know how verify it..and I want to know
  how to behave in similar situations..
 
  2010/8/3 Justin Edelson justinedel...@gmail.com:
  
  
   On Aug 3, 2010, at 4:57 AM, Flavio Pompermaier fla8...@gmail.com
  wrote:
  
   And the default value is..? I still haven't understand how to
 evaluate
   the maven.compiler.xxx variables..
   For example, the documentation on the web site says that default
 value
   of maven.compiler.source is 1.5,
   As previously discussed, the documentation says no such thing.
  
   maven.compiler.source is not defined by default.
  
  
   but this holds for the current
   version (2.3.1)...
   What if I want to know the default value for the
 maven.compiler-plugin
   version 2.0.2?
   I cannot found any documentation about it..I cannot think that
 there's
   no way to evaluate its value!!
  
   2010/7/13 Stephen Connolly stephen.alan.conno...@gmail.com:
   On 13 July 2010 07:40, Flavio Pompermaier fla8...@gmail.com
 wrote:
  
   This is the description on the source paramenter of the compiler
   plugin page (of the goal compile:compile):
  
   source:
   The -source argument for the Java compiler.
  
      * Type: java.lang.String
      * Since: 2.0
      * Required: No
      * Expression: ${maven.compiler.source}
  
   This means that if the property maven.compiler.source is defined,
 use
  that
   value, otherwise assume that the value is...
  
      * Default: 1.5
  
   How can I get that value? If it is not evaluable as an expression,
 how
   can I know how it will be evaluated by the plugin?
   My JavaHome points to a Java 1.6 but as far as I know the 2.0.2
   compiler use 1.4 compilation, isn't it?
  
   2010/7/13 Anders Hammar and...@hammar.net:
   No, you're not configuring the property that way. You're
 configuring
  the
   plugin, but you're not setting the property.
   A property is set in hte properties section of the pom.
  
   /Anders
  
   On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier 
 fla8...@gmail.com
  
   wrote:
  
   I set that variable via the configuration section of the
 compiler
   plugin of my pom.xml but the result of help:evaluate of that
  variable
   returns null! My question is: how can I retrieve the default
 values
  of
   the parameters of a certain plugin version?if I look at the
 plugin
   site I can see that its default value is 1.5. But this is valid
 for
   the current version..if I want to know its default value for an
  older
   version what am I supposed to do??
  
   2010/7/12, Anders Hammar and...@hammar.net:
   This does work for me:
  
   mvn help:evaluate -Dmaven.compiler.source=1.5
   -Dexpression=maven.compiler.source
  
   I'm setting the maven.compiler.source property here on command
 line
   instead
   of specifying it in the project, which should work the same.
  
   /Anders
  
   On Mon, Jul 12, 2010 at 23:27, Justin Edelson
   justinedel...@gmail.comwrote:
  
   From a shell, help:evaluate should be the right thing to do.
  
   Could

Re: Maven variables

2010-08-03 Thread Flavio Pompermaier
And the default value is..? I still haven't understand how to evaluate
the maven.compiler.xxx variables..
For example, the documentation on the web site says that default value
of maven.compiler.source is 1.5, but this holds for the current
version (2.3.1)...
What if I want to know the default value for the maven.compiler-plugin
version 2.0.2?
I cannot found any documentation about it..I cannot think that there's
no way to evaluate its value!!

2010/7/13 Stephen Connolly stephen.alan.conno...@gmail.com:
 On 13 July 2010 07:40, Flavio Pompermaier fla8...@gmail.com wrote:

 This is the description on the source paramenter of the compiler
 plugin page (of the goal compile:compile):

 source:
 The -source argument for the Java compiler.

    * Type: java.lang.String
    * Since: 2.0
    * Required: No
    * Expression: ${maven.compiler.source}

 This means that if the property maven.compiler.source is defined, use that
 value, otherwise assume that the value is...

    * Default: 1.5

 How can I get that value? If it is not evaluable as an expression, how
 can I know how it will be evaluated by the plugin?
 My JavaHome points to a Java 1.6 but as far as I know the 2.0.2
 compiler use 1.4 compilation, isn't it?

 2010/7/13 Anders Hammar and...@hammar.net:
  No, you're not configuring the property that way. You're configuring the
  plugin, but you're not setting the property.
  A property is set in hte properties section of the pom.
 
  /Anders
 
  On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier fla8...@gmail.com
 wrote:
 
  I set that variable via the configuration section of the compiler
  plugin of my pom.xml but the result of help:evaluate of that variable
  returns null! My question is: how can I retrieve the default values of
  the parameters of a certain plugin version?if I look at the plugin
  site I can see that its default value is 1.5. But this is valid for
  the current version..if I want to know its default value for an older
  version what am I supposed to do??
 
  2010/7/12, Anders Hammar and...@hammar.net:
   This does work for me:
  
   mvn help:evaluate -Dmaven.compiler.source=1.5
   -Dexpression=maven.compiler.source
  
   I'm setting the maven.compiler.source property here on command line
  instead
   of specifying it in the project, which should work the same.
  
   /Anders
  
   On Mon, Jul 12, 2010 at 23:27, Justin Edelson
   justinedel...@gmail.comwrote:
  
   From a shell, help:evaluate should be the right thing to do.
  
   Could it be that maven.compiler.source is, in fact, null?
  
   On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
I mean,how can I display their value?
   
2010/7/12, Justin Edelson justinedel...@gmail.com:
what do you mean by inspect?
   
On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
Hi to all,
is there a way to inspect maven.* variables (such as
${maven.compiler.source})?
I tried to use the help:evaluate tool but it tells me null
 object
  or
invalid expression.
   
Any idea??
   
Best regards,
Flavio
   
   
  -
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
   
   
   
   
 -
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
   
   
   
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
  
 
  --
  Inviato dal mio dispositivo mobile
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven variables

2010-08-03 Thread Flavio Pompermaier
Ok..so, if it is not defined how can I know the default value for
source parameter in the maven-compiler-plugin verion 2.0.2 if the
documentation is no more online?
It should be 1.4 but I want to know how verify it..and I want to know
how to behave in similar situations..

2010/8/3 Justin Edelson justinedel...@gmail.com:


 On Aug 3, 2010, at 4:57 AM, Flavio Pompermaier fla8...@gmail.com wrote:

 And the default value is..? I still haven't understand how to evaluate
 the maven.compiler.xxx variables..
 For example, the documentation on the web site says that default value
 of maven.compiler.source is 1.5,
 As previously discussed, the documentation says no such thing.

 maven.compiler.source is not defined by default.


 but this holds for the current
 version (2.3.1)...
 What if I want to know the default value for the maven.compiler-plugin
 version 2.0.2?
 I cannot found any documentation about it..I cannot think that there's
 no way to evaluate its value!!

 2010/7/13 Stephen Connolly stephen.alan.conno...@gmail.com:
 On 13 July 2010 07:40, Flavio Pompermaier fla8...@gmail.com wrote:

 This is the description on the source paramenter of the compiler
 plugin page (of the goal compile:compile):

 source:
 The -source argument for the Java compiler.

    * Type: java.lang.String
    * Since: 2.0
    * Required: No
    * Expression: ${maven.compiler.source}

 This means that if the property maven.compiler.source is defined, use that
 value, otherwise assume that the value is...

    * Default: 1.5

 How can I get that value? If it is not evaluable as an expression, how
 can I know how it will be evaluated by the plugin?
 My JavaHome points to a Java 1.6 but as far as I know the 2.0.2
 compiler use 1.4 compilation, isn't it?

 2010/7/13 Anders Hammar and...@hammar.net:
 No, you're not configuring the property that way. You're configuring the
 plugin, but you're not setting the property.
 A property is set in hte properties section of the pom.

 /Anders

 On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier fla8...@gmail.com
 wrote:

 I set that variable via the configuration section of the compiler
 plugin of my pom.xml but the result of help:evaluate of that variable
 returns null! My question is: how can I retrieve the default values of
 the parameters of a certain plugin version?if I look at the plugin
 site I can see that its default value is 1.5. But this is valid for
 the current version..if I want to know its default value for an older
 version what am I supposed to do??

 2010/7/12, Anders Hammar and...@hammar.net:
 This does work for me:

 mvn help:evaluate -Dmaven.compiler.source=1.5
 -Dexpression=maven.compiler.source

 I'm setting the maven.compiler.source property here on command line
 instead
 of specifying it in the project, which should work the same.

 /Anders

 On Mon, Jul 12, 2010 at 23:27, Justin Edelson
 justinedel...@gmail.comwrote:

 From a shell, help:evaluate should be the right thing to do.

 Could it be that maven.compiler.source is, in fact, null?

 On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
 I mean,how can I display their value?

 2010/7/12, Justin Edelson justinedel...@gmail.com:
 what do you mean by inspect?

 On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
 Hi to all,
 is there a way to inspect maven.* variables (such as
 ${maven.compiler.source})?
 I tried to use the help:evaluate tool but it tells me null
 object
 or
 invalid expression.

 Any idea??

 Best regards,
 Flavio


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org





 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 --
 Inviato dal mio dispositivo mobile

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-
To unsubscribe, e-mail: users-unsubscr

Re: Maven variables

2010-08-03 Thread Flavio Pompermaier
I think you intend

mvn help:describe -DgroupId=org.apache.maven.plugins
-DartifactId=maven-compiler-plugin -Dversion=2.0.2
-Dcmd=compiler:compile -Ddetail

However such documentation doesn't show the default value of
parameters (not all at least)!

2010/8/3 Anders Hammar and...@hammar.net:
 You can always get the docs from the plugin. Here's how:
 http://www.sonatype.com/people/2010/06/diy-retrieving-a-maven-plugins-documentation/

 /Anders

 On Tue, Aug 3, 2010 at 14:12, Flavio Pompermaier fla8...@gmail.com wrote:

 Ok..so, if it is not defined how can I know the default value for
 source parameter in the maven-compiler-plugin verion 2.0.2 if the
 documentation is no more online?
 It should be 1.4 but I want to know how verify it..and I want to know
 how to behave in similar situations..

 2010/8/3 Justin Edelson justinedel...@gmail.com:
 
 
  On Aug 3, 2010, at 4:57 AM, Flavio Pompermaier fla8...@gmail.com
 wrote:
 
  And the default value is..? I still haven't understand how to evaluate
  the maven.compiler.xxx variables..
  For example, the documentation on the web site says that default value
  of maven.compiler.source is 1.5,
  As previously discussed, the documentation says no such thing.
 
  maven.compiler.source is not defined by default.
 
 
  but this holds for the current
  version (2.3.1)...
  What if I want to know the default value for the maven.compiler-plugin
  version 2.0.2?
  I cannot found any documentation about it..I cannot think that there's
  no way to evaluate its value!!
 
  2010/7/13 Stephen Connolly stephen.alan.conno...@gmail.com:
  On 13 July 2010 07:40, Flavio Pompermaier fla8...@gmail.com wrote:
 
  This is the description on the source paramenter of the compiler
  plugin page (of the goal compile:compile):
 
  source:
  The -source argument for the Java compiler.
 
     * Type: java.lang.String
     * Since: 2.0
     * Required: No
     * Expression: ${maven.compiler.source}
 
  This means that if the property maven.compiler.source is defined, use
 that
  value, otherwise assume that the value is...
 
     * Default: 1.5
 
  How can I get that value? If it is not evaluable as an expression, how
  can I know how it will be evaluated by the plugin?
  My JavaHome points to a Java 1.6 but as far as I know the 2.0.2
  compiler use 1.4 compilation, isn't it?
 
  2010/7/13 Anders Hammar and...@hammar.net:
  No, you're not configuring the property that way. You're configuring
 the
  plugin, but you're not setting the property.
  A property is set in hte properties section of the pom.
 
  /Anders
 
  On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier fla8...@gmail.com
 
  wrote:
 
  I set that variable via the configuration section of the compiler
  plugin of my pom.xml but the result of help:evaluate of that
 variable
  returns null! My question is: how can I retrieve the default values
 of
  the parameters of a certain plugin version?if I look at the plugin
  site I can see that its default value is 1.5. But this is valid for
  the current version..if I want to know its default value for an
 older
  version what am I supposed to do??
 
  2010/7/12, Anders Hammar and...@hammar.net:
  This does work for me:
 
  mvn help:evaluate -Dmaven.compiler.source=1.5
  -Dexpression=maven.compiler.source
 
  I'm setting the maven.compiler.source property here on command line
  instead
  of specifying it in the project, which should work the same.
 
  /Anders
 
  On Mon, Jul 12, 2010 at 23:27, Justin Edelson
  justinedel...@gmail.comwrote:
 
  From a shell, help:evaluate should be the right thing to do.
 
  Could it be that maven.compiler.source is, in fact, null?
 
  On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
  I mean,how can I display their value?
 
  2010/7/12, Justin Edelson justinedel...@gmail.com:
  what do you mean by inspect?
 
  On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
  Hi to all,
  is there a way to inspect maven.* variables (such as
  ${maven.compiler.source})?
  I tried to use the help:evaluate tool but it tells me null
  object
  or
  invalid expression.
 
  Any idea??
 
  Best regards,
  Flavio
 
 
 
 -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
 
 
 -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  --
  Inviato dal mio dispositivo mobile
 
 
 -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven variables

2010-08-03 Thread Flavio Pompermaier
I tried the suggested command with the current version:
   mvn org.apache.maven.plugins:maven-compiler-plugin:2.3.1:help
-Ddetail -Dgoal=compile
and things are fine (as I was searching for).

However for the old version I was searching for (2.0.2) it doesn't
work..such auto-documentation was not implemented for that version..?
   mvn org.apache.maven.plugins:maven-compiler-plugin:2.0.2:help
-Ddetail -Dgoal=compile

2010/8/3 Flavio Pompermaier fla8...@gmail.com:
 I think you intend

 mvn help:describe -DgroupId=org.apache.maven.plugins
 -DartifactId=maven-compiler-plugin -Dversion=2.0.2
 -Dcmd=compiler:compile -Ddetail

 However such documentation doesn't show the default value of
 parameters (not all at least)!

 2010/8/3 Anders Hammar and...@hammar.net:
 You can always get the docs from the plugin. Here's how:
 http://www.sonatype.com/people/2010/06/diy-retrieving-a-maven-plugins-documentation/

 /Anders

 On Tue, Aug 3, 2010 at 14:12, Flavio Pompermaier fla8...@gmail.com wrote:

 Ok..so, if it is not defined how can I know the default value for
 source parameter in the maven-compiler-plugin verion 2.0.2 if the
 documentation is no more online?
 It should be 1.4 but I want to know how verify it..and I want to know
 how to behave in similar situations..

 2010/8/3 Justin Edelson justinedel...@gmail.com:
 
 
  On Aug 3, 2010, at 4:57 AM, Flavio Pompermaier fla8...@gmail.com
 wrote:
 
  And the default value is..? I still haven't understand how to evaluate
  the maven.compiler.xxx variables..
  For example, the documentation on the web site says that default value
  of maven.compiler.source is 1.5,
  As previously discussed, the documentation says no such thing.
 
  maven.compiler.source is not defined by default.
 
 
  but this holds for the current
  version (2.3.1)...
  What if I want to know the default value for the maven.compiler-plugin
  version 2.0.2?
  I cannot found any documentation about it..I cannot think that there's
  no way to evaluate its value!!
 
  2010/7/13 Stephen Connolly stephen.alan.conno...@gmail.com:
  On 13 July 2010 07:40, Flavio Pompermaier fla8...@gmail.com wrote:
 
  This is the description on the source paramenter of the compiler
  plugin page (of the goal compile:compile):
 
  source:
  The -source argument for the Java compiler.
 
     * Type: java.lang.String
     * Since: 2.0
     * Required: No
     * Expression: ${maven.compiler.source}
 
  This means that if the property maven.compiler.source is defined, use
 that
  value, otherwise assume that the value is...
 
     * Default: 1.5
 
  How can I get that value? If it is not evaluable as an expression, how
  can I know how it will be evaluated by the plugin?
  My JavaHome points to a Java 1.6 but as far as I know the 2.0.2
  compiler use 1.4 compilation, isn't it?
 
  2010/7/13 Anders Hammar and...@hammar.net:
  No, you're not configuring the property that way. You're configuring
 the
  plugin, but you're not setting the property.
  A property is set in hte properties section of the pom.
 
  /Anders
 
  On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier fla8...@gmail.com
 
  wrote:
 
  I set that variable via the configuration section of the compiler
  plugin of my pom.xml but the result of help:evaluate of that
 variable
  returns null! My question is: how can I retrieve the default values
 of
  the parameters of a certain plugin version?if I look at the plugin
  site I can see that its default value is 1.5. But this is valid for
  the current version..if I want to know its default value for an
 older
  version what am I supposed to do??
 
  2010/7/12, Anders Hammar and...@hammar.net:
  This does work for me:
 
  mvn help:evaluate -Dmaven.compiler.source=1.5
  -Dexpression=maven.compiler.source
 
  I'm setting the maven.compiler.source property here on command line
  instead
  of specifying it in the project, which should work the same.
 
  /Anders
 
  On Mon, Jul 12, 2010 at 23:27, Justin Edelson
  justinedel...@gmail.comwrote:
 
  From a shell, help:evaluate should be the right thing to do.
 
  Could it be that maven.compiler.source is, in fact, null?
 
  On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
  I mean,how can I display their value?
 
  2010/7/12, Justin Edelson justinedel...@gmail.com:
  what do you mean by inspect?
 
  On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
  Hi to all,
  is there a way to inspect maven.* variables (such as
  ${maven.compiler.source})?
  I tried to use the help:evaluate tool but it tells me null
  object
  or
  invalid expression.
 
  Any idea??
 
  Best regards,
  Flavio
 
 
 
 -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven variables

2010-07-13 Thread Flavio Pompermaier
This is the description on the source paramenter of the compiler
plugin page (of the goal compile:compile):

source:
The -source argument for the Java compiler.

* Type: java.lang.String
* Since: 2.0
* Required: No
* Expression: ${maven.compiler.source}
* Default: 1.5

How can I get that value? If it is not evaluable as an expression, how
can I know how it will be evaluated by the plugin?
My JavaHome points to a Java 1.6 but as far as I know the 2.0.2
compiler use 1.4 compilation, isn't it?

2010/7/13 Anders Hammar and...@hammar.net:
 No, you're not configuring the property that way. You're configuring the
 plugin, but you're not setting the property.
 A property is set in hte properties section of the pom.

 /Anders

 On Tue, Jul 13, 2010 at 00:34, Flavio Pompermaier fla8...@gmail.com wrote:

 I set that variable via the configuration section of the compiler
 plugin of my pom.xml but the result of help:evaluate of that variable
 returns null! My question is: how can I retrieve the default values of
 the parameters of a certain plugin version?if I look at the plugin
 site I can see that its default value is 1.5. But this is valid for
 the current version..if I want to know its default value for an older
 version what am I supposed to do??

 2010/7/12, Anders Hammar and...@hammar.net:
  This does work for me:
 
  mvn help:evaluate -Dmaven.compiler.source=1.5
  -Dexpression=maven.compiler.source
 
  I'm setting the maven.compiler.source property here on command line
 instead
  of specifying it in the project, which should work the same.
 
  /Anders
 
  On Mon, Jul 12, 2010 at 23:27, Justin Edelson
  justinedel...@gmail.comwrote:
 
  From a shell, help:evaluate should be the right thing to do.
 
  Could it be that maven.compiler.source is, in fact, null?
 
  On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
   I mean,how can I display their value?
  
   2010/7/12, Justin Edelson justinedel...@gmail.com:
   what do you mean by inspect?
  
   On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
   Hi to all,
   is there a way to inspect maven.* variables (such as
   ${maven.compiler.source})?
   I tried to use the help:evaluate tool but it tells me null object
 or
   invalid expression.
  
   Any idea??
  
   Best regards,
   Flavio
  
  
 -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
  
   -
   To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
   For additional commands, e-mail: users-h...@maven.apache.org
  
  
  
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 

 --
 Inviato dal mio dispositivo mobile

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Maven variables

2010-07-12 Thread Flavio Pompermaier
Hi to all,
is there a way to inspect maven.* variables (such as ${maven.compiler.source})?
I tried to use the help:evaluate tool but it tells me null object or
invalid expression.

Any idea??

Best regards,
Flavio

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Maven variables

2010-07-12 Thread Flavio Pompermaier
Hi to all,
is there a way to inspect maven.* variables (such as ${maven.compiler.source})?
I tried to use the help:evaluate tool but it tells me null object or
invalid expression.

Any idea??

Best regards,
Flavio

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven variables

2010-07-12 Thread Flavio Pompermaier
I mean,how can I display their value?

2010/7/12, Justin Edelson justinedel...@gmail.com:
 what do you mean by inspect?

 On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
 Hi to all,
 is there a way to inspect maven.* variables (such as
 ${maven.compiler.source})?
 I tried to use the help:evaluate tool but it tells me null object or
 invalid expression.

 Any idea??

 Best regards,
 Flavio

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org



-- 
Inviato dal mio dispositivo mobile

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: Maven variables

2010-07-12 Thread Flavio Pompermaier
I set that variable via the configuration section of the compiler
plugin of my pom.xml but the result of help:evaluate of that variable
returns null! My question is: how can I retrieve the default values of
the parameters of a certain plugin version?if I look at the plugin
site I can see that its default value is 1.5. But this is valid for
the current version..if I want to know its default value for an older
version what am I supposed to do??

2010/7/12, Anders Hammar and...@hammar.net:
 This does work for me:

 mvn help:evaluate -Dmaven.compiler.source=1.5
 -Dexpression=maven.compiler.source

 I'm setting the maven.compiler.source property here on command line instead
 of specifying it in the project, which should work the same.

 /Anders

 On Mon, Jul 12, 2010 at 23:27, Justin Edelson
 justinedel...@gmail.comwrote:

 From a shell, help:evaluate should be the right thing to do.

 Could it be that maven.compiler.source is, in fact, null?

 On 7/12/10 5:23 PM, Flavio Pompermaier wrote:
  I mean,how can I display their value?
 
  2010/7/12, Justin Edelson justinedel...@gmail.com:
  what do you mean by inspect?
 
  On 7/12/10 1:13 PM, Flavio Pompermaier wrote:
  Hi to all,
  is there a way to inspect maven.* variables (such as
  ${maven.compiler.source})?
  I tried to use the help:evaluate tool but it tells me null object or
  invalid expression.
 
  Any idea??
 
  Best regards,
  Flavio
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
 
 
 


 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org




-- 
Inviato dal mio dispositivo mobile

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



Re: maven-changes-plugin error while retrieving tickets from Trac

2009-05-25 Thread Flavio Pompermaier

Excuse me, before I involuntarily sent an incomplete email. This is the 
complete one:

Hi to all,

I tried to launch maven with the following command 

  mvn changes:trac-report

and I received the following error:

[INFO]task-segment: [changes:trac-report]
[INFO] 
[INFO] [changes:trac-report]
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] Failed to parse date 'Fri May 22 06:43:35 CEST 2009' as a date.
Unparseable date: Fri May 22 06:43:35 CEST 2009
[INFO] 
[INFO] Trace
java.lang.RuntimeException: Failed to parse date 'Fri May 22 06:43:35 CEST 
2009' as a date.
at 
org.apache.maven.plugin.trac.TracTicket.parseDate(TracTicket.java:204)
at 
org.apache.maven.plugin.trac.TracTicket.setTimeCreated(TracTicket.java:182)
at 
org.apache.maven.plugin.trac.TracMojo.setQueryResult(TracMojo.java:225)
at 
org.apache.maven.plugin.trac.TracMojo.executeReport(TracMojo.java:151)
at 
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
at 
org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:172)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.text.ParseException: Unparseable date: Fri May 22 06:43:35 
CEST 2009
at java.text.DateFormat.parse(DateFormat.java:337)
at 
org.apache.maven.plugin.trac.TracTicket.parseDate(TracTicket.java:200)
... 23 more

Looking around I found that this problem seems to be caused from the machine 
Locale (see 
http://stackoverflow.com/questions/781257/unexpected-java-simpledateformat-parse-exception)
Any Ideas?




-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org



maven-changes-plugin error while retrieving tickets from Trc

2009-05-25 Thread Flavio Pompermaier

Hi to all,
I tried to launch maven with the following command 
and I received the following error:

[INFO]task-segment: [changes:trac-report]
[INFO] 
[INFO] [changes:trac-report]
[INFO] 
[ERROR] FATAL ERROR
[INFO] 
[INFO] Failed to parse date 'Fri May 22 06:43:35 CEST 2009' as a date.
Unparseable date: Fri May 22 06:43:35 CEST 2009
[INFO] 
[INFO] Trace
java.lang.RuntimeException: Failed to parse date 'Fri May 22 06:43:35 CEST 
2009' as a date.
at 
org.apache.maven.plugin.trac.TracTicket.parseDate(TracTicket.java:204)
at 
org.apache.maven.plugin.trac.TracTicket.setTimeCreated(TracTicket.java:182)
at 
org.apache.maven.plugin.trac.TracMojo.setQueryResult(TracMojo.java:225)
at 
org.apache.maven.plugin.trac.TracMojo.executeReport(TracMojo.java:151)
at 
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:101)
at 
org.apache.maven.plugin.changes.AbstractChangesReport.execute(AbstractChangesReport.java:172)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:512)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:482)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: java.text.ParseException: Unparseable date: Fri May 22 06:43:35 
CEST 2009
at java.text.DateFormat.parse(DateFormat.java:337)
at 
org.apache.maven.plugin.trac.TracTicket.parseDate(TracTicket.java:200)
... 23 more

Looking around I found that this problem seems to be caused from the machine 
Locale.
Any Ideas?





-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org