Re: Status of Maven Ant Tasks in Maven 3
What's in the Aether Ant Tasks is identical logic to what Maven 3.x does. On Sep 19, 2011, at 8:51 PM, Paul King wrote: > So would you describe the Aether Ant Tasks as almost a drop in > replacement for the (dependency resolution part of the) Maven Ant > Tasks? > > Thanks, Paul. > > On Tue, Sep 20, 2011 at 10:23 AM, Jason van Zyl wrote: >> The resolution logic for Maven 3.x is done by Aether, so you may want to >> look at the Aether Ant Tasks[1]. >> >> [1]: https://github.com/sonatype/aether-ant-tasks >> >> On Sep 19, 2011, at 1:47 PM, alejandro.alves wrote: >> >>> Hello, >>> I am having the same issue, how could I solve the problem. >>> Best regards >>> >>> -- >>> View this message in context: >>> http://maven.40175.n5.nabble.com/Status-of-Maven-Ant-Tasks-in-Maven-3-tp4574457p4819792.html >>> Sent from the Maven - Users mailing list archive at Nabble.com. >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> http://twitter.com/jvanzyl >> - >> >> Simplex sigillum veri. (Simplicity is the seal of truth.) >> >> >> >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society
[maven-plugin-plugin] Is there a way I can have Ddetail default to true when generating HelpMojo?
I'm getting a hang of the maven-plugin-plugin and there's one thing I can't figure out how to accomplish When I generate a HelpMojo with the http://maven.apache.org/plugins/maven-plugin-plugin/helpmojo-mojo.html helpmojo goal , the "detail" parameter is set to 'false' automatically by helpmojo in the Apache maven-plugin-plugin.jar (in other words, not anywhere in my code). I'd very much like that to be 'true' instead (Almost all our goals have required parameters and our users have requested that these parameters get automatically listed when they run the 'help' goal). I realize the problem is alleviated by just typing [foo]:help -Ddetail=true but does anyone know of a way to configure things such that I can set detail to true by default, such I don't need to specify the -Ddetail parameter? Thanks! -- View this message in context: http://maven.40175.n5.nabble.com/maven-plugin-plugin-Is-there-a-way-I-can-have-Ddetail-default-to-true-when-generating-HelpMojo-tp4820999p4820999.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Status of Maven Ant Tasks in Maven 3
So would you describe the Aether Ant Tasks as almost a drop in replacement for the (dependency resolution part of the) Maven Ant Tasks? Thanks, Paul. On Tue, Sep 20, 2011 at 10:23 AM, Jason van Zyl wrote: > The resolution logic for Maven 3.x is done by Aether, so you may want to look > at the Aether Ant Tasks[1]. > > [1]: https://github.com/sonatype/aether-ant-tasks > > On Sep 19, 2011, at 1:47 PM, alejandro.alves wrote: > >> Hello, >> I am having the same issue, how could I solve the problem. >> Best regards >> >> -- >> View this message in context: >> http://maven.40175.n5.nabble.com/Status-of-Maven-Ant-Tasks-in-Maven-3-tp4574457p4819792.html >> Sent from the Maven - Users mailing list archive at Nabble.com. >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> > > Thanks, > > Jason > > -- > Jason van Zyl > Founder, Apache Maven > http://twitter.com/jvanzyl > - > > Simplex sigillum veri. (Simplicity is the seal of truth.) > > > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Status of Maven Ant Tasks in Maven 3
The resolution logic for Maven 3.x is done by Aether, so you may want to look at the Aether Ant Tasks[1]. [1]: https://github.com/sonatype/aether-ant-tasks On Sep 19, 2011, at 1:47 PM, alejandro.alves wrote: > Hello, > I am having the same issue, how could I solve the problem. > Best regards > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Status-of-Maven-Ant-Tasks-in-Maven-3-tp4574457p4819792.html > Sent from the Maven - Users mailing list archive at Nabble.com. > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - Simplex sigillum veri. (Simplicity is the seal of truth.)
Re: Status of Maven Ant Tasks in Maven 3
Hello, I am having the same issue, how could I solve the problem. Best regards -- View this message in context: http://maven.40175.n5.nabble.com/Status-of-Maven-Ant-Tasks-in-Maven-3-tp4574457p4819792.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugins not properly loading properties
I'll admit knowing this was a loaded question. I've previously solved this via a separate configuration artifact. I was just shocked to see how m3 doesn't allow the import of property files anymore the way 2.2.1 did. Thanks again all - I appreciate it! On Mon, Sep 19, 2011 at 5:19 PM, Wayne Fay wrote: > > How does this work when you have to deploy the same artifact to 10 > different > > environments? > > > > 10 profiles and build the artifact 10 times? > > We get this question so often on this list, and similar questions. You > should check the archives for various comments. > > The standard answer is "use JNDI" or some other DI > technique/framework. Bundle all environment settings into the artifact > and use some method to tell your app or app server which settings to > use for this specific server. Or extract all settings into a single > "configurations" artifact if you'd prefer. > > This also guarantees that the artifact you perform QA on is identical > (same code etc) to the artifact you deploy to PROD which is a > requirement for most sensibly-defined environments. If you build 10 > artifacts (one per environment) as you suggested then there is no such > guarantee. > > Wayne > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Plugins not properly loading properties
> How does this work when you have to deploy the same artifact to 10 different > environments? > > 10 profiles and build the artifact 10 times? We get this question so often on this list, and similar questions. You should check the archives for various comments. The standard answer is "use JNDI" or some other DI technique/framework. Bundle all environment settings into the artifact and use some method to tell your app or app server which settings to use for this specific server. Or extract all settings into a single "configurations" artifact if you'd prefer. This also guarantees that the artifact you perform QA on is identical (same code etc) to the artifact you deploy to PROD which is a requirement for most sensibly-defined environments. If you build 10 artifacts (one per environment) as you suggested then there is no such guarantee. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugins not properly loading properties
How does this work when you have to deploy the same artifact to 10 different environments? 10 profiles and build the artifact 10 times? On Mon, Sep 19, 2011 at 4:25 PM, Anders Hammar wrote: > I don't think so unless the tomcat plugin can be configured to use it. > Using a separate properties file is IMHO not a good idea, for reasons > you now see. And there are even worse examples where you could > effectively be distributing a non-working pom making people using your > artifact lives' miserable. > > Keep everything in the POM, > /Anders > On Mon, Sep 19, 2011 at 22:15, Maven User wrote: > > And there's no way to inject the property files we've loaded at that > level? > > > > On Mon, Sep 19, 2011 at 3:59 PM, Anders Hammar > wrote: > > > >> It will get properties defined in the effective POM. > >> > >> /Anders > >> On Mon, Sep 19, 2011 at 21:48, Maven User > wrote: > >> > Yet it gets properties from profiles/plugin configuration/etc? > >> > > >> > On Mon, Sep 19, 2011 at 2:35 PM, Anders Hammar > >> wrote: > >> > > >> >> When you execute > >> >> mvn tomcat:deploy > >> >> you're NOT executing the build lifecycle but only the specify plugin > >> >> goal. Thus, your plugin that loads the props is not executed. > >> >> > >> >> /Anders > >> >> > >> >> On Mon, Sep 19, 2011 at 17:35, Maven User > >> wrote: > >> >> > Hi all - > >> >> > > >> >> > Quick question, I think there's some confusion on my end. > >> >> > > >> >> > We have a plugin that loads properties into the reactor so they're > >> >> available > >> >> > for things like resource processing, various other plugins, etc. > >> >> > > >> >> > However, when using the tomcat plugin directly on the command line > >> (such > >> >> as > >> >> > mvn tomcat:deploy), the properties are not expanded when they've > come > >> >> from a > >> >> > property file. > >> >> > > >> >> > If we use the standard plugin configuration and bind the deployment > to > >> a > >> >> > particular lifecycle goal with an execution, the property is > expanded > >> >> > successfully. > >> >> > > >> >> > What are we doing wrong/what are we missing? > >> >> > > >> >> > When the tomcat goals are called on the command line, it's as if > they > >> >> skip > >> >> > several steps but grab things from activated profiles and > > >> >> > blocks. > >> >> > > >> >> > Suggestions? > >> >> > > >> >> > >> >> - > >> >> 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: Plugins not properly loading properties
BTW - this is totally not the behavior we're seeing with a "tomcat:deploy". That seems to go through all the standard build lifecycle goals, then NOT pull in any dynamically loaded configuration...
Re: Plugins not properly loading properties
I don't think so unless the tomcat plugin can be configured to use it. Using a separate properties file is IMHO not a good idea, for reasons you now see. And there are even worse examples where you could effectively be distributing a non-working pom making people using your artifact lives' miserable. Keep everything in the POM, /Anders On Mon, Sep 19, 2011 at 22:15, Maven User wrote: > And there's no way to inject the property files we've loaded at that level? > > On Mon, Sep 19, 2011 at 3:59 PM, Anders Hammar wrote: > >> It will get properties defined in the effective POM. >> >> /Anders >> On Mon, Sep 19, 2011 at 21:48, Maven User wrote: >> > Yet it gets properties from profiles/plugin configuration/etc? >> > >> > On Mon, Sep 19, 2011 at 2:35 PM, Anders Hammar >> wrote: >> > >> >> When you execute >> >> mvn tomcat:deploy >> >> you're NOT executing the build lifecycle but only the specify plugin >> >> goal. Thus, your plugin that loads the props is not executed. >> >> >> >> /Anders >> >> >> >> On Mon, Sep 19, 2011 at 17:35, Maven User >> wrote: >> >> > Hi all - >> >> > >> >> > Quick question, I think there's some confusion on my end. >> >> > >> >> > We have a plugin that loads properties into the reactor so they're >> >> available >> >> > for things like resource processing, various other plugins, etc. >> >> > >> >> > However, when using the tomcat plugin directly on the command line >> (such >> >> as >> >> > mvn tomcat:deploy), the properties are not expanded when they've come >> >> from a >> >> > property file. >> >> > >> >> > If we use the standard plugin configuration and bind the deployment to >> a >> >> > particular lifecycle goal with an execution, the property is expanded >> >> > successfully. >> >> > >> >> > What are we doing wrong/what are we missing? >> >> > >> >> > When the tomcat goals are called on the command line, it's as if they >> >> skip >> >> > several steps but grab things from activated profiles and >> >> > blocks. >> >> > >> >> > Suggestions? >> >> > >> >> >> >> - >> >> 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: Plugins not properly loading properties
And there's no way to inject the property files we've loaded at that level? On Mon, Sep 19, 2011 at 3:59 PM, Anders Hammar wrote: > It will get properties defined in the effective POM. > > /Anders > On Mon, Sep 19, 2011 at 21:48, Maven User wrote: > > Yet it gets properties from profiles/plugin configuration/etc? > > > > On Mon, Sep 19, 2011 at 2:35 PM, Anders Hammar > wrote: > > > >> When you execute > >> mvn tomcat:deploy > >> you're NOT executing the build lifecycle but only the specify plugin > >> goal. Thus, your plugin that loads the props is not executed. > >> > >> /Anders > >> > >> On Mon, Sep 19, 2011 at 17:35, Maven User > wrote: > >> > Hi all - > >> > > >> > Quick question, I think there's some confusion on my end. > >> > > >> > We have a plugin that loads properties into the reactor so they're > >> available > >> > for things like resource processing, various other plugins, etc. > >> > > >> > However, when using the tomcat plugin directly on the command line > (such > >> as > >> > mvn tomcat:deploy), the properties are not expanded when they've come > >> from a > >> > property file. > >> > > >> > If we use the standard plugin configuration and bind the deployment to > a > >> > particular lifecycle goal with an execution, the property is expanded > >> > successfully. > >> > > >> > What are we doing wrong/what are we missing? > >> > > >> > When the tomcat goals are called on the command line, it's as if they > >> skip > >> > several steps but grab things from activated profiles and > >> > blocks. > >> > > >> > Suggestions? > >> > > >> > >> - > >> 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: Plugins not properly loading properties
It will get properties defined in the effective POM. /Anders On Mon, Sep 19, 2011 at 21:48, Maven User wrote: > Yet it gets properties from profiles/plugin configuration/etc? > > On Mon, Sep 19, 2011 at 2:35 PM, Anders Hammar wrote: > >> When you execute >> mvn tomcat:deploy >> you're NOT executing the build lifecycle but only the specify plugin >> goal. Thus, your plugin that loads the props is not executed. >> >> /Anders >> >> On Mon, Sep 19, 2011 at 17:35, Maven User wrote: >> > Hi all - >> > >> > Quick question, I think there's some confusion on my end. >> > >> > We have a plugin that loads properties into the reactor so they're >> available >> > for things like resource processing, various other plugins, etc. >> > >> > However, when using the tomcat plugin directly on the command line (such >> as >> > mvn tomcat:deploy), the properties are not expanded when they've come >> from a >> > property file. >> > >> > If we use the standard plugin configuration and bind the deployment to a >> > particular lifecycle goal with an execution, the property is expanded >> > successfully. >> > >> > What are we doing wrong/what are we missing? >> > >> > When the tomcat goals are called on the command line, it's as if they >> skip >> > several steps but grab things from activated profiles and >> > blocks. >> > >> > Suggestions? >> > >> >> - >> 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: Plugins not properly loading properties
Yet it gets properties from profiles/plugin configuration/etc? On Mon, Sep 19, 2011 at 2:35 PM, Anders Hammar wrote: > When you execute > mvn tomcat:deploy > you're NOT executing the build lifecycle but only the specify plugin > goal. Thus, your plugin that loads the props is not executed. > > /Anders > > On Mon, Sep 19, 2011 at 17:35, Maven User wrote: > > Hi all - > > > > Quick question, I think there's some confusion on my end. > > > > We have a plugin that loads properties into the reactor so they're > available > > for things like resource processing, various other plugins, etc. > > > > However, when using the tomcat plugin directly on the command line (such > as > > mvn tomcat:deploy), the properties are not expanded when they've come > from a > > property file. > > > > If we use the standard plugin configuration and bind the deployment to a > > particular lifecycle goal with an execution, the property is expanded > > successfully. > > > > What are we doing wrong/what are we missing? > > > > When the tomcat goals are called on the command line, it's as if they > skip > > several steps but grab things from activated profiles and > > blocks. > > > > Suggestions? > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Plugins not properly loading properties
When you execute mvn tomcat:deploy you're NOT executing the build lifecycle but only the specify plugin goal. Thus, your plugin that loads the props is not executed. /Anders On Mon, Sep 19, 2011 at 17:35, Maven User wrote: > Hi all - > > Quick question, I think there's some confusion on my end. > > We have a plugin that loads properties into the reactor so they're available > for things like resource processing, various other plugins, etc. > > However, when using the tomcat plugin directly on the command line (such as > mvn tomcat:deploy), the properties are not expanded when they've come from a > property file. > > If we use the standard plugin configuration and bind the deployment to a > particular lifecycle goal with an execution, the property is expanded > successfully. > > What are we doing wrong/what are we missing? > > When the tomcat goals are called on the command line, it's as if they skip > several steps but grab things from activated profiles and > blocks. > > Suggestions? > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Project With Many Artifacts - Maven Install Artifacts Problem
Check the build-helper-maven-plugin
http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html
-Robert
> Date: Thu, 15 Sep 2011 04:46:04 -0700
> From: rodrigo.zampi...@gmail.com
> To: users@maven.apache.org
> Subject: Project With Many Artifacts - Maven Install Artifacts Problem
>
> Hi,
>
> I have a project which generates six artifacts, one jar and five zips, when
> I install them in repository all zips are installed with the same name.
>
> Look the output of install below:
> [INFO] [install:install {execution: default-install}]
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-1.1.jar*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\zabbix-trapper\1.1\*za
> bbix-trapper-1.1.jar*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-hpux_ia_32-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\zabbix
> -trapper\1.1\*zabbix-trapper-1.1-bin.zip*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-hpux_ia_64-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\zabbix
> -trapper\1.1\*zabbix-trapper-1.1-bin.zip*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-hpux_parisc_32-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\za
> bbix-trapper\1.1\*zabbix-trapper-1.1-bin.zip*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-hpux_parisc_64-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\za
> bbix-trapper\1.1\*zabbix-trapper-1.1-bin.zip*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-linux_x86_32-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\zabb
> ix-trapper\1.1\*zabbix-trapper-1.1-bin.zip*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-linux_x86_64-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\zabb
> ix-trapper\1.1\*zabbix-trapper-1.1-bin.zip*
> [INFO] Installing C:\Documents and
> Settings\92035067\workspace\zabbix-trapper\target\*zabbix-trapper-win_x86_32-1.1-bin.zip*
> to \.m2\book-repository\br\com\claro\zabbixtrapper\zabbix
> -trapper\1.1\*zabbix-trapper-1.1-bin.zip*
>
> Can I fix that?
>
> Thanks!!!
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Project-With-Many-Artifacts-Maven-Install-Artifacts-Problem-tp4806469p4806469.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> 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
Plugins not properly loading properties
Hi all - Quick question, I think there's some confusion on my end. We have a plugin that loads properties into the reactor so they're available for things like resource processing, various other plugins, etc. However, when using the tomcat plugin directly on the command line (such as mvn tomcat:deploy), the properties are not expanded when they've come from a property file. If we use the standard plugin configuration and bind the deployment to a particular lifecycle goal with an execution, the property is expanded successfully. What are we doing wrong/what are we missing? When the tomcat goals are called on the command line, it's as if they skip several steps but grab things from activated profiles and blocks. Suggestions?
Re: maven build with android API 11 failed, Cann't find symbol
Thanks a lot. -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4819252.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
OK, I guess this is the main issue then. From what I understand: * Android guys do not publish their jars to a public Maven repo * If the version used in your dependencies matches the ones used by the Android team, then 2.2= API Level 8. If you want API Level 11, you need version 3.0 (http://developer.android.com/sdk/android-3.0.html) * There are some cool dudes who create jars with Class skeletons and empty method stubs to reproduce all the class names and method signatures so that you can compile your project. Unfortunately, the latests jars have not been created and/or published yet. * There is another guy (who just replied you) who has created a project just for the purpose of deploying the jars from the Android SDK to your local Maven repository: https://github.com/mosabua/maven-android-sdk-deployer. Read this for how to use this tool: https://github.com/mosabua/maven-android-sdk-deployer/blob/master/README.markdown Cheers, Guillaume Le 19/09/2011 16:23, darakok a écrit : I think you're right. My dependency references Android 2.2. android android 2.2_r2 provided Thanks for your help. darakok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4819154.html Sent from the Maven - Users mailing list archive at Nabble.com. - 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 build with android API 11 failed, Cann't find symbol
Use my Maven Android SDK Deployed you can find on github and add a dependency
as documented in the readers. The version should be 11_r1 on the dependency...
Manfred
darakok wrote:
This is part of my POM file where i specify the version of Android API jar
file to compile with.
com.jayway.maven.plugins.android.generation2
maven-android-plugin
2.9.0-beta-5
8
true
${project.build.directory}/filtered-resources
true
I'm sure the correct Android jar file is used to compile my project because
it shows the jar file path in the console just before the error comes up.
Interestingly, that same jar file is reference in my project in eclipse and
Eclipse recognize the method that I have problem with when building with
maven.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818946.html
Sent from the Maven - Users mailing list archive at Nabble.com.
_
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
I think you're right. My dependency references Android 2.2. android android 2.2_r2 provided Thanks for your help. darakok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4819154.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
Find my answers in your e-mail:
Le 19/09/2011 15:20, darakok a écrit :
This is part of my POM file where i specify the version of Android API jar
file to compile with.
com.jayway.maven.plugins.android.generation2
maven-android-plugin
2.9.0-beta-5
8
true
${project.build.directory}/filtered-resources
true
Ok, so If you change here to 11, it does not modify the classpath of the
maven compiler plugin. It simply informs thet maven android plugin that
you are targetting the level 11. The jar used by the maven compiler is
defined in your dependencies.
I'm sure the correct Android jar file is used to compile my project because
it shows the jar file path in the console just before the error comes up.
Interestingly, that same jar file is reference in my project in eclipse and
Eclipse recognize the method that I have problem with when building with
maven.
Can't really know what's going on here since you have not posted your
dependencies and since we don't know where Maven resolves your artifacts
(if you installed the jars manually, you can put whatever version you
want and therefore have an the wrong jar).
Eclipse is of no use here because you can easily add jars through other
means (add a jar, add a library container, etc...). Actually, if you
have such external (to Maven) dependency , you should remove it because
they are not portable from one IDE to another and mainly because this
will not be reflected in your Maven build (probably indicates why you
are having some issues in your build now).
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818946.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Cheers,
Guillaume
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
This is part of my POM file where i specify the version of Android API jar
file to compile with.
com.jayway.maven.plugins.android.generation2
maven-android-plugin
2.9.0-beta-5
8
true
${project.build.directory}/filtered-resources
true
I'm sure the correct Android jar file is used to compile my project because
it shows the jar file path in the console just before the error comes up.
Interestingly, that same jar file is reference in my project in eclipse and
Eclipse recognize the method that I have problem with when building with
maven.
--
View this message in context:
http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818946.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a plugin to check the standard directory layout?
On Mon, Sep 19, 2011 at 9:18 PM, sebb wrote: >> I don't think the meta-information about locations is available to >> Maven from the plugins, each plugin defines its own configuration and >> Maven doesn't interpret that in anyway. >> You would have to bake each plugin's default layouts into your >> standard directory plugin checker. > > Yes, that would be required, unless plugins can be interrogated for > their defaults somehow. Probably, but I dont know how. You would still need to know what configuration fields to query, but you should be able to get that information out of the Mojos programmatically. >> What is the problem you are trying to solve? > > Consistency. > > It's a lot easier to understand projects if they use a standard layout. > > Many of the Commons projects started before Maven 2 and the standard layout. You have my vote, I'm just bitter from experience trying to convince people to change :) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Is there a plugin to check the standard directory layout?
On 19 September 2011 03:49, Barrie Treloar wrote: > On Mon, Sep 19, 2011 at 10:56 AM, sebb wrote: >>> The standard directories layout >>> http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html >>> lists what you are looking for. >> >> It lists only some of the standard files and paths. >> For example it does not list src/changes/changes.xml > > Yes, that's because the changes plugin defines this location. > See > http://maven.apache.org/plugins/maven-changes-plugin/examples/alternate-changes-xml-location.html > As do all the other plugins for non-core locations. > > I don't think the meta-information about locations is available to > Maven from the plugins, each plugin defines its own configuration and > Maven doesn't interpret that in anyway. > You would have to bake each plugin's default layouts into your > standard directory plugin checker. Yes, that would be required, unless plugins can be interrogated for their defaults somehow. >>> It's just as quick to visually inspect them. >> >> Maybe if one knows the locations by heart, and does not have lots of >> projects to check. >> >>> And the only way to know if they are using non-standard directories >>> would be if the pom defined those non-standard directories, otherwise >>> maven wont know about them. >> >> Again, that involves more work than running a plugin; poms can be >> large and don't have a standard order of top-level entries. > > I hear you that this is a lot of work, but I'm still trying to > understand why you want to do this. > Not using the standard directories is a pain, but its a once off > configuration. > > What is the problem you are trying to solve? Consistency. It's a lot easier to understand projects if they use a standard layout. Many of the Commons projects started before Maven 2 and the standard layout. >> Also, Maven seems to be able to detect certain non-standard directory >> locations. >> >> For example, Commons DbUtils currently uses src/java and src/test, and >> the pom does not define these locations, yet Maven can compile the >> source and tests. > > It's defined in the pom, see > https://svn.apache.org/repos/asf/commons/proper/dbutils/trunk/pom.xml > > src/java > src/test Sorry, don't know how I managed to miss that. >>> I guess the tool could also help you migrate to the standard layout... >> >> The intention was to produce a compliance report, a sort of checkstyle >> for the layout. >> You could then decide what fixes to make. > > I definitely agree, life is easier when the defaults are used. > But once configured its done and can be ignored again. > > And my fingers definitely twitch to relocation the code to the default > locations, but unless I'm the admin of that project the inertia is > normally too great to see this change occur. > > - > 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: wicket is secure by default. why use spring security?
The default auth-roles project is just an example of how to do *simple* authentication and authorization. It only supports 3 roles: not logged in, logged in user and administrator. For more complex things or flexibility you'll need something like Apache Shiro, Wicket Security (now hosted on wicket stuff), or spring security. Some applications are a hybrid of old Spring MVC pages/insert other framework that use [spring security|shiro]. Migrating those applications to Wicket could leave the old pages alive, using the spring security stuff. Wicket being secure by default is different from having an authorization/authentication scheme out of the box. Security frameworks are just as encompassing as ORM frameworks. Java comes with JDBC, so why use Hibernate? Martijn On Mon, Sep 19, 2011 at 9:55 AM, Zilvinas Vilutis wrote: > Hi all Wicket users. > > While I was trying to design a wicket app in my mind - the first thing > I thought of was authentication and ( spring ) security. > > I know that "wicket is secure" by default ( a quote from wicket > features? :), we can use wicket auth & annotation based security. > Wicket will automatically redirect to original page after login. > > So...did anyone think of it - what is the real reason to use spring or > other security framework ( shiro? ) for authentication? what benefits > does it bring apart from some standards & overhead for the app? is it > integration with other auth systems ( OpenID, Facebook login or > whatever )? or what? > > Just pennies for thought... > > Žilvinas Vilutis > > Mobile: (+1) 623 330 6048 > E-mail: cika...@gmail.com > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: wicket is secure by default. why use spring security?
please discard this email. wrong mailing list :) Žilvinas Vilutis Mobile: (+1) 623 330 6048 E-mail: cika...@gmail.com On Mon, Sep 19, 2011 at 12:55 AM, Zilvinas Vilutis wrote: > Hi all Wicket users. > > While I was trying to design a wicket app in my mind - the first thing > I thought of was authentication and ( spring ) security. > > I know that "wicket is secure" by default ( a quote from wicket > features? :), we can use wicket auth & annotation based security. > Wicket will automatically redirect to original page after login. > > So...did anyone think of it - what is the real reason to use spring or > other security framework ( shiro? ) for authentication? what benefits > does it bring apart from some standards & overhead for the app? is it > integration with other auth systems ( OpenID, Facebook login or > whatever )? or what? > > Just pennies for thought... > > Žilvinas Vilutis > > Mobile: (+1) 623 330 6048 > E-mail: cika...@gmail.com > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven build with android API 11 failed, Cann't find symbol
Not much information here, but I guess that when you say "11" you mean that this is the target level. From what it looks like, it seems that android API jars for that version are not available. See also this: http://stackoverflow.com/questions/5253029/why-arent-the-android-sdk-jars-in-any-maven-repository Regarding the message you are mentionning, it just says that the method getActionView cannot be found on the class MenuItem (but the message is quite clear and comes from the java compiler), meaning that Maven is not using the new version you expect. As to why this is the case, without the pom and settings or more information, it is impossible to help you more. Regards, Guillaume Le 19/09/2011 10:35, darakok a écrit : I use maven to build my android project. It was working fine until I make use of method exclusively available to API 11 and above. In the pom file, I do change the android build version to "11". So presume I have set the right android jar for maven build to succeed. But it turns out to be completely the opposite. Because exactly the one method that I just added failed during the build. Maven complains "Cannot find symbol: MenuItem.getActionView" So do you have any idea what is the problem? Thanks dara kok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818232.html Sent from the Maven - Users mailing list archive at Nabble.com. - 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 build with android API 11 failed, Cann't find symbol
I use maven to build my android project. It was working fine until I make use of method exclusively available to API 11 and above. In the pom file, I do change the android build version to "11". So presume I have set the right android jar for maven build to succeed. But it turns out to be completely the opposite. Because exactly the one method that I just added failed during the build. Maven complains "Cannot find symbol: MenuItem.getActionView" So do you have any idea what is the problem? Thanks dara kok -- View this message in context: http://maven.40175.n5.nabble.com/maven-build-with-android-API-11-failed-Cann-t-find-symbol-tp4818232p4818232.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] webstart-maven-plugin-1.0-beta-2 Released
Hi, The Mojo team is pleased to announce the release of the webstart-maven-plugin version 1.0-beta-2. The Webstart Maven Plugin generates application bundles that can be deployed via Web Start. The plugin can be used to prepare standalone Web Start applications or Web Start applications bundled in WAR files (with or without Sun's Download Servlet). It handles the generation of JNLP files and optional version.xml files, using Velocity templates. It also handles the selection and preparation of the dependencies, performing signing, unsigning and Pack200 compression when required. Some links : Documentation: http://mojo.codehaus.org/webstart JIRA: http://jira.codehaus.org/browse/MWEBSTART svn: https://svn.codehaus.org/mojo/tags/webstart-1.0-beta-2 To get this update, simply specify the version in your project's plugin configuration: org.codehaus.mojo.webstart webstart 1.0-beta-2 Some configuration may have changed since 1.0-beta-1, especially concerning the codebase of generated jnlp components files (and the report). Please checkout this in your configuration if something is wrong before all. Release Notes - Maven 2.x Webstart Plugin - Version 1.0-beta-2 ** Bug * [MWEBSTART-134] - jnlp resources are in libPath * [MWEBSTART-138] - The number of signed artifacts differ from the number of modified artifacts * [MWEBSTART-148] - Fix dependency resolution/handling * [MWEBSTART-151] - offlineAllowed and allPermissions don't have any effect * [MWEBSTART-154] - Some links are broken on the site of beta-1 * [MWEBSTART-155] - it002 and it003 are broken * [MWEBSTART-159] - JARs are not Pack200-compressed if libPath is set * [MWEBSTART-160] - Maven 3.0 Compatibility Issue * [MWEBSTART-161] - Transitive dependencies specified in profile don't get included * [MWEBSTART-163] - Webstart zip contains Maven jars that are not required for the webstart app ** Improvement * [MWEBSTART-158] - Customize code base * [MWEBSTART-168] - Make mojo and reports unified * [MWEBSTART-171] - Improve pack200 integration ** New Feature * [MWEBSTART-14] - support component extension mecanism for already signed jars * [MWEBSTART-156] - Generate extension files * [MWEBSTART-157] - Add makeArchive and attachArchive parameter to mojo * [MWEBSTART-169] - Add french report translations * [MWEBSTART-170] - Add a canSign parameter to authorize or forbbid unsigning of already signed jar ** Task * [MWEBSTART-99] - Add an integration test for the report mojo Enjoy, The Mojo team. Tony Chemit - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release from Git branch
On 17/09/2011, at 12:37 AM, Stuart Sierra wrote: > Hello list! > > I use Git, maven-release-plugin, Hudson, and the Hudson M2 Release > Plugin. Can I perform a release from a Git branch other than "master"? > > Right now, to do a release, Hudson checks out the "master" branch and > calls "mvn release:prepare release:perform". If the release succeeds, > the M2 Extra Steps Plugin runs "git push origin master `git tag | grep > -v ^hudson`" to update Git tags. > > If I change my Hudson config to build a different branch, like > "1.2.x", will the maven-release-plugin still do the right thing? I believe so. You may need to set the element in the section of the POM on the branch. In my experience, the release plugin correctly releases in that situation (I'm not using Hudson for that, however). - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
wicket is secure by default. why use spring security?
Hi all Wicket users. While I was trying to design a wicket app in my mind - the first thing I thought of was authentication and ( spring ) security. I know that "wicket is secure" by default ( a quote from wicket features? :), we can use wicket auth & annotation based security. Wicket will automatically redirect to original page after login. So...did anyone think of it - what is the real reason to use spring or other security framework ( shiro? ) for authentication? what benefits does it bring apart from some standards & overhead for the app? is it integration with other auth systems ( OpenID, Facebook login or whatever )? or what? Just pennies for thought... Žilvinas Vilutis Mobile: (+1) 623 330 6048 E-mail: cika...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
