RE: Not using pom.xml

Hi My mistake with the "=" sign. Maybe you should file an RFE in Jira for this. This might come in to flavours: 1. @requiresProject should ignore existing pom, or 2. introduce a new parameter @ingnoreProject. Hermod -Original Message- From: Jagan Padmanabha Pillai -X (jpadmana - Insi

RE: maven dependecies

Hi Jörg, Joerg Hohwiller wrote on Thursday, July 13, 2006 9:47 PM: > Jörg Schaible wrote: >> Hi Jörg, > Hi Jörg, > > nice to "meet" again ;) :) [snip] > I created one module per package. This is in principle the > idea of maven to have > one artifact per module. OK, I just wanted to point ou

RE: Not using pom.xml

I think there is no "=" sign. Its just @requiresProject false. This will run fine with no pom.xml but if pom is available it uses it. I want it to ignore the pom.xml even if the file is available. Any idea ?? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent:

RE: Not using pom.xml

Hi Did you set @requiresProject=false? Hermod -Original Message- From: Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions, Inc. at Cisco) [mailto:[EMAIL PROTECTED] Sent: Thursday, July 13, 2006 11:08 PM To: Maven Developers List Subject: Not using pom.xml Hi, Is there any way

Re: codehaus sync is back

On 7/14/06, Brett Porter <[EMAIL PROTECTED]> wrote: Hi, I've worked with Ben at codehaus to get the rsync working again, so we can now pick up releases from there. great! J - To unsubscribe, e-mail: [EMAIL PROTECTED] For add

codehaus sync is back

Hi, I've worked with Ben at codehaus to get the rsync working again, so we can now pick up releases from there. Cheers, Brett -- Apache Maven - http://maven.apache.org/ Better Builds with Maven - http://library.mergere.com/

[jira] Subscription: Design & Best Practices

Issue Subscription Filter: Design & Best Practices (37 issues) Subscriber: mavendevlist Key Summary MNG-2184Possible problem with @aggregator and forked lifecycles http://jira.codehaus.org/browse/MNG-2184 MNG-612 implement conflict resolution techniques htt

Re: Layout of "multiproject" projects

Joerg Hohwiller wrote: Anyways the user should be quite free to layout his project. Yes, the use is free to use his own layout... like I said, the tree layout is the "recommended" layout. ^_^ - To unsubscribe, e-mail: [EM

Re: [m2] Where is maven-plugins?

On 7/14/06, dan tran <[EMAIL PROTECTED]> wrote: since it is the parent of mavevn-install-plugin, it must be one level up http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml Thank you all for the quick replies. I must have had a brain fade not to look in the parent directory, I'm used

Re: Fwd: svn commit: r421661 - /maven/plugins/trunk/maven-assembly-plugin/pom.xml

I have no idea what I was doing at the time either. Kind of unusual for me not to refer to the bug I was trying to work around... and this caused problems down the line and the POM in the repo needed to have the exclusion removed. Anyway, I had the same change you made in my local copy uncommi

Re: Problem with the new plugin plugin: missing parameters from parent mojo

Sounds like a bug... On 14/07/2006 6:13 AM, Dennis Lundberg wrote: Thanks, now it's working better. But I have one component that slips through. Do I need to change it? It looks like this: /** * @component */ private MavenProjectHelper projectHelper; A component should not b

Re: What are the required annotations for a mojo?

On 14/07/2006 7:56 AM, Dennis Lundberg wrote: I'm confused... In "Guide to Developing Java Plugins" [1] it says, in the simple mojo example: "The comment lines starting with "@goal" and "@description" are examples of annotations. These two annotations are required, ..." In "Maven 2.0 - M

Re: [m2] Where is maven-plugins?

Barrie Treloar wrote: The pom for maven-install-plugin has maven-plugins org.apache.maven.plugins 2-SNAPSHOT but I cant find this - in svn at http://svn.apache.org/repos/asf or - in the snapshot repo http://snapshots.maven.codehaus.org/maven2 Any suggestions? I'd just like to poi

Re: [m2] Where is maven-plugins?

On 7/13/06, Barrie Treloar <[EMAIL PROTECTED]> wrote: The pom for maven-install-plugin has maven-plugins org.apache.maven.plugins 2-SNAPSHOT but I cant find this - in svn at http://svn.apache.org/repos/asf http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml - in th

Re: [m2] Where is maven-plugins?

since it is the parent of mavevn-install-plugin, it must be one level up http://svn.apache.org/repos/asf/maven/plugins/trunk/pom.xml -D On 7/13/06, Barrie Treloar <[EMAIL PROTECTED]> wrote: The pom for maven-install-plugin has maven-plugins org.apache.maven.plugins 2-SNAPSHOT bu

[m2] Where is maven-plugins?

The pom for maven-install-plugin has maven-plugins org.apache.maven.plugins 2-SNAPSHOT but I cant find this - in svn at http://svn.apache.org/repos/asf or - in the snapshot repo http://snapshots.maven.codehaus.org/maven2 Any suggestions? I'd just like to point to the snapshot repo

Re: Layout of "multiproject" projects

Two pieces of info: there is already an optional tag in the parent that allows you to specify where the parent is - : http://maven.apache.org/ref/2.0.3-SNAPSHOT/maven-model/maven.html#class_parent Also, rather than running with -N, you should look at the option: http://maven.apache.org/ref/cur

What are the required annotations for a mojo?

I'm confused... In "Guide to Developing Java Plugins" [1] it says, in the simple mojo example: "The comment lines starting with "@goal" and "@description" are examples of annotations. These two annotations are required, ..." In "Maven 2.0 - Mojo API Specification" [2] it says, under "The

RE: Not using pom.xml

The reason is, the dependencies are resolved based on where we are running the build i.e., which branch in clear case. For diff branches I may need to select diff versions of the artifact which my plug-in is automated to take care. For this to work, I don't want maven to start looking for the d

Re: Not using pom.xml

I don't believe that is an option. The question is... why? Is it because you want to always require the user to enter command-line parameters? Thanks; Eric On 7/13/06, Jagan Padmanabha Pillai -X (jpadmana - Insight Solutions, Inc. at Cisco) <[EMAIL PROTECTED]> wrote: Hi, Is there any way I c

Not using pom.xml

Hi, Is there any way I can force my custom made plugin to not use pom.xml. There is a parameter @requiresProject (which is used in archetype), this works fine if there is no pom.xml. But if pom is available the plugin will use it. What I want is even if the pom.xml is available do NOT use it.

Re: Please review the documentation for the maven-jar-plugin

Fixed! Edwin Punzalan wrote: The Introduction (index.html) have two. Dennis Lundberg wrote: Thanks for the review Edwin. Which place are you referring to? Edwin Punzalan wrote: I think I remember that we should be using "Maven" instead of "Maven 2". Aside from that, everything's just g

Re: Please review the documentation for the maven-jar-plugin

Barrie Treloar wrote: On 7/12/06, Dennis Lundberg <[EMAIL PROTECTED]> wrote: - Add FAQ In the FAQ, could you link to documentation that tells you how to set parameters in the configuration section. At the moment you have to know you can specify tags that match the attributes of the class to s

Re: Problem with the new plugin plugin: missing parameters from parent mojo

Thanks, now it's working better. But I have one component that slips through. Do I need to change it? It looks like this: /** * @component */ private MavenProjectHelper projectHelper; A component should not be included in the report, right? But this one is. -- Dennis Lundberg

Re: Layout of "multiproject" projects

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Edwin, Edwin Punzalan wrote: > > The TREE layout is recommended... the plugins are laid-out flat bec they > are all plugins which means they all have a single parent. No use for a > sub-parent for now... but there have been talks of categorizing

Re: Default Filtered Resources Directory

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Brett Porter wrote: > I think this has already been suggested in JIRA, but if not it is worth > adding. I only found issues that are slightly related, but not yet the same thing. I'll put it into JIRA on monday... > > - Brett Thanks Jörg -BEGIN

Re: maven dependecies

-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Jörg Schaible wrote: > Hi Jörg, Hi Jörg, nice to "meet" again ;) > > [snip] > > So did you have multiple modules for each Solaris package or a single module > with a Mojo that creates two artifacts (like the EJB and its client)? I created one modul

Re: Inter Plugin communication

Hi! My use-easy is simple: to pass build information collected/generated by a buildinfo (our own - not the public one) to a second plugin (FreeMarker plugin, also our own) that generates Java Source code using templates. The build information is Java System Properties, Maven Effective POM, Perfo

Re: Inter Plugin communication

A Plugin, IMHO, is atomic. I don't think you can actually have 2 plugins inter-communicate (the way you need it), except for reading the configuration from pom.xml, which was on one of the threads on the user@ or dev@ list just a couple of days ago. What is your use-case - there might be anoth

Fwd: svn commit: r421661 - /maven/plugins/trunk/maven-assembly-plugin/pom.xml

Brett, I don't know why you excluded plexus-archiver, assembly plugin didn't compile for me Although is added later the bug with exclusions makes it globally excluded -- Forwarded message -- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: Jul 13, 2006 6:33 PM Subject: svn commi

Inter Plugin communication

Hi! Is it possible to communicate between plugins run in the same build? I would like a "Build Conext" where plugins can set properties/objects for use by plugins following in execution. E.g. Plugin A gathers some information that is input for plugin B. Now, I solve it by having plugin A write t

Are @parameter in non-AbstractMojo parsed?

Hi! I have some problems with the the expression attribute to the parameter tag. Are @parameter tags only processed when they exist in a Mojo (extends AbstractMojo)? My mojo (MyMojo) has a bean (MyBean). MyCfgBean has a String instance variable outputFilename that I want to populate with a defa

Re: Plugins can't be built!

There's a few things going on here: - the plugin report uses the plugin tools, which really shouldn't be in the Maven release cycle since they are really independant (but they are there to make bootstrap possible without the shared SVN repo) - the plugin descriptor generator uses the model th

Re: [proposal] Maven 2.1 Design Topics

and as rahul reminded me on the continuum dev list.. http://www.nabble.com/2.1-Design-and-Process-tf1617559.html#a4383722 might be time to resurrect that idea with this jason :) jesse On 7/13/06, Jason van Zyl <[EMAIL PROTECTED]> wrote: On 12 Jul 06, at 10:40 PM 12 Jul 06, John Casey wrote:

Re: Plugins can't be built!

We have the same error message... which seems a logical error since we're building plugins that use those plugins during the build. [EMAIL PROTECTED] wrote: Hi When I try to build the plugins, I get the following: [INFO] Scanning for projects... [INFO] -

RE: Problem Accessing docck Plugin

I appreciate the assistance, but my question was this: Is it an error for there to be metadata in central for a snapshot plugin? It seems to me that we should not have any metadata in a release-only repository which resolves to a snapshot. -Original Message- From: Dennis Lundberg [mailto

RE: Plugins can't be built!

Hi When I try to build the plugins, I get the following: [INFO] Scanning for projects... [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The projects in the

Re: Plugins can't be built!

Dennis Lundberg wrote: Brett Porter wrote: This shouldn't have broken - needs investigation. A while back, we agreed to add a feature to 2.0.5 (the implementation attribute). The plugin plugin was updated to use the new tools and such. However, it also has a prereq of maven 2.0.5, so maven

Re: Plugins can't be built!

Dennis Lundberg wrote: Brett Porter wrote: This shouldn't have broken - needs investigation. A while back, we agreed to add a feature to 2.0.5 (the implementation attribute). The plugin plugin was updated to use the new tools and such. However, it also has a prereq of maven 2.0.5, so maven

Re: Plugins can't be built!

Brett Porter wrote: This shouldn't have broken - needs investigation. A while back, we agreed to add a feature to 2.0.5 (the implementation attribute). The plugin plugin was updated to use the new tools and such. However, it also has a prereq of maven 2.0.5, so maven 2.0.4 and below which gi

Re: Please review maven-idea-plugin documentation

The site has been updated with your reviews. Dennis Lundberg wrote: Edwin Punzalan wrote: I've just finished updating the documentation for the maven-idea-plugin. Your feedback is highly appreciated. Thanks. Here are my comments: All - "IntelliJ Idea" -> "IntelliJ IDEA" and "Idea" -> "I

Re: Please review maven-idea-plugin documentation

Dennis Lundberg wrote: examples/provide_deployment_descriptor_file.html - Just out of curiosity, what would happen if you have a project with one ejb module and one war module? Would the two modules get the same descriptor file? if its configured it the command-line, yes. If you are creati

Re: [proposal] Maven 2.1 Design Topics

On 12 Jul 06, at 10:40 PM 12 Jul 06, John Casey wrote: Hi everyone, I guess it's fairly obvious from some of the advanced discussions going on in this list that we're starting to think a little more seriously about writing Maven 2.1. I think it's a bad idea for us to attempt another mass

RE: maven dependecies

Hi Jörg, Joerg Hohwiller wrote on Thursday, July 13, 2006 12:19 AM: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Hi there, > > Maven2 really rocks! I figured out a way to build a plugin that allows > "solaris" as and builds a solaris package for a > maven project. > > Therefore I add

Re: Please review maven source plugin documentation

Ok, thanks for the comments :) Will post it on jira and revise the docs. Dennis Lundberg wrote: Maria Odea Ching wrote: Hi Everyone, The documentation for the source plugin is now ready for review :) Thanks, Odea My comments: faq.html - "Use the source:test-jar to" -> "Use the source:te

Re: HTTP compression (http://jira.codehaus.org/browse/WAGON-55)

Hi Nathan; It looks that the Jetty ResourceHandler will only return zipped content ending in ".gz", so perhaps its a simple as hello.txt.gz? ( http://www.dpml.net/api/jetty/5.1.6/org/mortbay/http/handler/ResourceHandler.html#setMinGzipLength(int)