Re: Problem with Dependencies Report Generation
Get the same error here. Looks like it is caused by https://issues.apache.org/bugzilla/show_bug.cgi?id=28069 2008/7/18 Dhruva Reddy [EMAIL PROTECTED]: Hi, I am on a multi-module project with a large number of dependencies. I am trying to run the site:site goal in Maven 2.0.8. When it gets to the Dependencies report, it appears to process all of the dependencies, but then it seems to connect to each of our specified repositories several times. This last part takes *forever* (I have killed it after waiting as long as 8 hours). I see the following output (when running Maven in debug mode) when it tries to connect to the repositories: https://maven-repository.dev.java.net/nonav/repository - Session: Opened https://maven-repository.dev.java.net/nonav/repository - Session: Disconnecting https://maven-repository.dev.java.net/nonav/repository - Session: Disconnected One bit of output I see before it starts connecting to the repositories is: [WARNING] Unable to process class com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File C:\Documents and Settings\[username]\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.j ar org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 60 Can someone tell me why it tries to connect to the repositories? I also tried to disable this report by excluding it as follows, but it still tries to generate it. ... reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId reportSets reportSet reports reportcim/report reportissue-tracking/report reportmailing-list/report reportindex/report reportsummary/report reportscm/report reportproject-team/report /reports /reportSet /reportSets /plugin ... Other reporting plugins in use are: * findbugs-maven-plugin * cobertura-maven-plugin * maven-checkstyle-plugin * maven-pmd-plugin * maven-surefire-report-plugin Could one of these be causing it to generate the Dependencies report, despite my excluding it? Thanks, Dhruva - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Avoid to bring in new repositories via dependencies
Hi Wendy! Thanks for your reply. On Thursday 11 September 2008 Wendy Smoak wrote: On Thu, Sep 11, 2008 at 5:03 AM, Martin Höller [EMAIL PROTECTED] wrote: Unfortunately this dependency's pom.xml specifies other remote repositories. Could someone please tell me what is the recomended way to avoid getting a new repository into my environment? You can use mirrors, especially mirrorOf=*, to prevent additional repositories from being introduced. http://maven.apache.org/guides/mini/guide-mirror-settings.html That doesn't prevent additional repositories of beeing introduced. It just prevents direct usage of them, which is IMHO just a workaround but no solution. It might also be worth bringing this up to the dev team responsible for the pom to get them to remove it in future releases. I'm not suscribed to the maven-developer mailinglist and was hoping to find some solution on the users list. However, eventually I'll bring this up on the developers list... regards, - martin signature.asc Description: This is a digitally signed message part.
Re: Avoid to bring in new repositories via dependencies
Hi Martin, Martin Höller wrote: On Thursday 11 September 2008 Wendy Smoak wrote: On Thu, Sep 11, 2008 at 5:03 AM, Martin Höller [EMAIL PROTECTED] wrote: Unfortunately this dependency's pom.xml specifies other remote repositories. Could someone please tell me what is the recomended way to avoid getting a new repository into my environment? You can use mirrors, especially mirrorOf=*, to prevent additional repositories from being introduced. http://maven.apache.org/guides/mini/guide-mirror-settings.html That doesn't prevent additional repositories of beeing introduced. It just prevents direct usage of them, which is IMHO just a workaround but no solution. I am not sure what you try to do? You want to add a new jar file, but you do not want to introduce a dependency to the repository where that jar file lives, right? Let's introduce some names: - your pom : project.pom.xml - the dependency that you introduced by hand : A.pom.original.xml - a sub dependency that A.pom.original.xml mentions : B.pom.xml That jar file has in its A.pom.original.xml other dependencies that live in other remote repositories that you do not want to introduce in your project.pom.xml of your project. For sure the jar that you included needs these additional dependencies, because otherwise it would not mention them in its A.pom.original.xml in the first place. If you fulfilled those dependencies on the several B.pom.xml already by some other way, e.g. you introduced them in your local repository by hand and introduced those dependencies into your project.pom.xml via a separate dependency/, then you can use exclude/ on the original dependency that you have in project.pom.xml like that: dependency groupId.../groupId artifactIdA/artifactId version.../version exclusions exclusion groupId.../groupId artifactIdB/artifactId /exclusion ... /exclusions /dependency In this case maven will not try to resolve the dependencies you have in the A.pom.original.xml Another even simpler way is to create a A.pom.modified.xml yourself for your jar that you introduced in your local repository :) Why do you want to use the A.pom.original.xml that you downloaded manually from the remote repository if that pom.xml causes you problems? I hop that helps, -- Christian Schuhegger http://www.el-chef.de/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem with Dependencies Report Generation
Reported this bug as MSITE-359 (http://jira.codehaus.org/browse/MSITE-359) 2008/7/18 Dhruva Reddy [EMAIL PROTECTED]: Hi, I am on a multi-module project with a large number of dependencies. I am trying to run the site:site goal in Maven 2.0.8. When it gets to the Dependencies report, it appears to process all of the dependencies, but then it seems to connect to each of our specified repositories several times. This last part takes *forever* (I have killed it after waiting as long as 8 hours). I see the following output (when running Maven in debug mode) when it tries to connect to the repositories: https://maven-repository.dev.java.net/nonav/repository - Session: Opened https://maven-repository.dev.java.net/nonav/repository - Session: Disconnecting https://maven-repository.dev.java.net/nonav/repository - Session: Disconnected One bit of output I see before it starts connecting to the repositories is: [WARNING] Unable to process class com/ibm/icu/impl/data/LocaleElements_zh__PINYIN.class in JarAnalyzer File C:\Documents and Settings\[username]\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.j ar org.apache.bcel.classfile.ClassFormatException: Invalid byte tag in constant pool: 60 Can someone tell me why it tries to connect to the repositories? I also tried to disable this report by excluding it as follows, but it still tries to generate it. ... reporting plugins plugin artifactIdmaven-project-info-reports-plugin/artifactId reportSets reportSet reports reportcim/report reportissue-tracking/report reportmailing-list/report reportindex/report reportsummary/report reportscm/report reportproject-team/report /reports /reportSet /reportSets /plugin ... Other reporting plugins in use are: * findbugs-maven-plugin * cobertura-maven-plugin * maven-checkstyle-plugin * maven-pmd-plugin * maven-surefire-report-plugin Could one of these be causing it to generate the Dependencies report, despite my excluding it? Thanks, Dhruva - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using springframework in maven project
Hi, Thanks for your reply. I tried many different alternatives how to set up the proxy. At the end I also just placed the IP address of the machine handling the proxy and that still did not work out. I then downloaded spring framework from the repository and installed it using the suggested command. Re-built my solution and everything worked fine. I do not know what the problem is exactly. However I will try to do some more experimenting :) Regards, Simon J. Date: Thu, 11 Sep 2008 08:42:45 -0700 From: [EMAIL PROTECTED] To: users@maven.apache.org Subject: Re: Using springframework in maven project On Thu, Sep 11, 2008 at 00:26, Simon Aquilina [EMAIL PROTECTED] wrote: hosthttp://redhat1/pxy.pac/host That doesn't look like a host to me. Try hostredhat1/host. And read http://maven.apache.org/guides/mini/guide-proxies.html. The pxy.pac is probably some sort of script, you might want to read it and see what it does. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ News, entertainment and everything you care about at Live.com. Get it now! http://www.live.com/getstarted.aspx
Re: Property access from a plugin
Yeah,
I'm just saying what I vaguely recall from the list a couple of months back.
It's nothing to do with me and I don't even pretend to understand it ;-)
-Stephen
On Fri, Sep 12, 2008 at 4:48 AM, EJ Ciramella [EMAIL PROTECTED]wrote:
This is hit or miss as well - if I do -P+base,+override, it ignores the
activeByDefaults profiles.
If I do -P+profile1 -P+profile2, then it doesn't take profile2 at all
(so my plugin isn't activated).
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 8:02 PM
To: Maven Users List
Subject: Re: Property access from a plugin
You need to do
-P+base,+override
I think
On Fri, Sep 12, 2008 at 1:01 AM, Stephen Connolly
[EMAIL PROTECTED] wrote:
activation on the comandline will disable any defaults.
there is (added at some stage not sure what maven version) the ability
to
add and remove with -P+otherProfile or -P-otherProfile
On Fri, Sep 12, 2008 at 12:34 AM, EJ Ciramella
[EMAIL PROTECTED]wrote:
So with further research, if within a single pom, you have an
activeByDefault plugin and one that you're activating by specifying
an
ID on the commandline, the activeByDefault one is ignored.
Additionally, I set up three profiles, two of which are active by
default and when you activate the third profile, the other two are
deactivated.
When did this change? This seems broken
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 7:03 PM
To: Maven Users List
Subject: RE: Property access from a plugin
Can you give me an example of what you're talking about?
The properties that are coming from this profile are used for
filtering
other files during process-resources. If I do a
mavenProject().getProperties() the missing properties are not
listed...
The activeByDefault profile is truly active:
System.out.println(mavenProject.getActiveProfiles());
Yields:
E:\work\mvn process-resources -Dtest=asdf -Pbase,override
[INFO] Scanning for projects...
[INFO]
-
[INFO] Building Backoffice Process
[INFO]task-segment: [process-resources]
[INFO]
-
[INFO] [prop-override:override {execution: default}]
[
Profile {id: common-defaults, source: pom}
Profile {id: base, source: settings.xml}
Profile {id: proxies, source: settings.xml}
Profile {id: proxies, source: settings.xml}
]
[INFO] [dependency:unpack-dependencies {execution: unpack}]
[INFO] lty-utils-resources-1.0.0.16.jar already exists in
destination.
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [antrun:run {execution: default}]
[INFO] Executing tasks
[INFO] Executed tasks
[INFO]
-
[INFO] BUILD SUCCESSFUL
[INFO]
-
[INFO] Total time: 9 seconds
[INFO] Finished at: Thu Sep 11 18:42:39 EDT 2008
[INFO] Final Memory: 13M/26M
[INFO]
-
Additionally, in the commandline specified above, do you notice the
-Pbase,override?
Base is a profile in my settings.xml, override is in the pom at the
root
of the project (the parent pom). Override is a plugin INSIDE a
profile.
Common-defaults is also a profile inside the root level pom (override
and common-defaults are right next to each other) - where to activate
override, you have to either specify -Doverride or -Poverride and
common-defaults is activeByDefault - why would activating manually
ONE
profile deactivate another one? Maven shows it's active (see my
snippet
above), but it's truly NOT putting the properties stored in it into
play.
-Original Message-
From: Stephen Connolly [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 11, 2008 6:39 PM
To: Maven Users List
Subject: Re: Property access from a plugin
On Thu, Sep 11, 2008 at 11:33 PM, EJ Ciramella
[EMAIL PROTECTED]wrote:
So what's happening is, I'm activating a few profiles, yet the
properties that are missing are set in an activeByDefault
profile.
It
appears that the activeByDefault profile is either not activated
or
ignored.
If I turn on this profile (along with my other profiles), the
properties
are expanded properly.
My plugin is simply loading some properties from a property file
and
pushing them into the mavenProject property listing.
So two questions:
1 - do I need to do anything special to load all the properties
defined
in any activeByDefault profiles?
2 - What lifecycle goal should I bind my plugin to?
The earliest possible phase (validate AFAIK)
Note that any
Re: Avoid to bring in new repositories via dependencies
Chirstian, the problem is that the pom for the dependency that he wants to use declares repositories to use for resolving its transitive dependencies. He does not want to have that repository dragged in to his build. Other than re-releasing the jar with a different version (e.g. releasing log4j:log4j:1.2.14-mycompany-1 it'd be the same jar as 1.2.14, but using a hand rolled pom) there is no real solution to this. I know that plans for Maven 2.2 or 3.0 or some such is/was to deprecate the declaration of repositories within the pom because of this very problem. Of course banning repository declarations within poms is a swings and roundabouts solution: + fix this type of problem - cause problems if you need something that you cannot get pushed into repo1 Stephen On Fri, Sep 12, 2008 at 8:11 AM, Christian Schuhegger [EMAIL PROTECTED] wrote: Hi Martin, Martin Höller wrote: On Thursday 11 September 2008 Wendy Smoak wrote: On Thu, Sep 11, 2008 at 5:03 AM, Martin Höller [EMAIL PROTECTED] wrote: Unfortunately this dependency's pom.xml specifies other remote repositories. Could someone please tell me what is the recomended way to avoid getting a new repository into my environment? You can use mirrors, especially mirrorOf=*, to prevent additional repositories from being introduced. http://maven.apache.org/guides/mini/guide-mirror-settings.html That doesn't prevent additional repositories of beeing introduced. It just prevents direct usage of them, which is IMHO just a workaround but no solution. I am not sure what you try to do? You want to add a new jar file, but you do not want to introduce a dependency to the repository where that jar file lives, right? Let's introduce some names: - your pom : project.pom.xml - the dependency that you introduced by hand : A.pom.original.xml - a sub dependency that A.pom.original.xml mentions : B.pom.xml That jar file has in its A.pom.original.xml other dependencies that live in other remote repositories that you do not want to introduce in your project.pom.xml of your project. For sure the jar that you included needs these additional dependencies, because otherwise it would not mention them in its A.pom.original.xml in the first place. If you fulfilled those dependencies on the several B.pom.xml already by some other way, e.g. you introduced them in your local repository by hand and introduced those dependencies into your project.pom.xml via a separate dependency/, then you can use exclude/ on the original dependency that you have in project.pom.xml like that: dependency groupId.../groupId artifactIdA/artifactId version.../version exclusions exclusion groupId.../groupId artifactIdB/artifactId /exclusion ... /exclusions /dependency In this case maven will not try to resolve the dependencies you have in the A.pom.original.xml Another even simpler way is to create a A.pom.modified.xml yourself for your jar that you introduced in your local repository :) Why do you want to use the A.pom.original.xml that you downloaded manually from the remote repository if that pom.xml causes you problems? I hop that helps, -- Christian Schuhegger http://www.el-chef.de/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Avoid to bring in new repositories via dependencies
On Friday 12 September 2008 Stephen Connolly wrote: Chirstian, the problem is that the pom for the dependency that he wants to use declares repositories to use for resolving its transitive dependencies. He does not want to have that repository dragged in to his build. Exactly. Other than re-releasing the jar with a different version (e.g. releasing log4j:log4j:1.2.14-mycompany-1 it'd be the same jar as 1.2.14, but using a hand rolled pom) there is no real solution to this. :( I know that plans for Maven 2.2 or 3.0 or some such is/was to deprecate the declaration of repositories within the pom because of this very problem. Of course banning repository declarations within poms is a swings and roundabouts solution: + fix this type of problem - cause problems if you need something that you cannot get pushed into repo1 Well, one could always declare additional repos in settings.xml. I'd say this is a far better place than pom.xml. Thank's Stephen for clarifying this. - martin signature.asc Description: This is a digitally signed message part.
Re: type=test-jar vs classifier=tests
On Fri, Aug 1, 2008 at 9:14 PM, Stefano Bagnara [EMAIL PROTECTED] wrote: I have a multimodule project where some module tests have dependencies on other modules tests. I can use both classifiertests/classifier scopetest/scope and typetest-jar/type scopetest/scope I think I notice that the type test-jar works when I build it in reactor without installing while the classifier does not work in that case if I don't add install as one of my goals. Is there any other change in this? Why isn't the classifier method working in reactor? I see here http://maven.apache.org/guides/mini/guide-attached-tests.html you suggest the classifier method, but I think in past I always read about the type test-jar method Has anyone got advice on this? I had a similar problem, where I was using classifier as per the guide but maven-eclipse-plugin then includes the project twice. But if I change to typetest-jar/type everything works. Which one is the correct way? Should the guide be updated? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Avoid to bring in new repositories via dependencies
On Fri, Sep 12, 2008 at 8:46 AM, Martin Höller [EMAIL PROTECTED] wrote: On Friday 12 September 2008 Stephen Connolly wrote: Chirstian, the problem is that the pom for the dependency that he wants to use declares repositories to use for resolving its transitive dependencies. He does not want to have that repository dragged in to his build. Exactly. Other than re-releasing the jar with a different version (e.g. releasing log4j:log4j:1.2.14-mycompany-1 it'd be the same jar as 1.2.14, but using a hand rolled pom) there is no real solution to this. :( I know that plans for Maven 2.2 or 3.0 or some such is/was to deprecate the declaration of repositories within the pom because of this very problem. Of course banning repository declarations within poms is a swings and roundabouts solution: + fix this type of problem - cause problems if you need something that you cannot get pushed into repo1 Well, one could always declare additional repos in settings.xml. I'd say this is a far better place than pom.xml. Thank's Stephen for clarifying this. - martin Yeah but the problem with having to declare the additional repos in your settings.xml is now the project builds for me but not for you (until you get my settings.xml) And additionally, each repository that you add slows down the build as Maven has to check _all_ repositories that it knows about for the artifacts... and then if one of those is feeling slow your (normally fast) build becomes increasingly slow. Hm One change that _might_ work would be to force all repositories added via a pom.xml to have the update policy of never. Thus that way you'd get the artifact the first time and it would never be checked again (ok, so it would be more seldom than never!)
AW: How to define a parent POM in a company wide.
Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it?
Re: Avoid to bring in new repositories via dependencies
On Friday 12 September 2008 Stephen Connolly wrote: On Fri, Sep 12, 2008 at 8:46 AM, Martin Höller [EMAIL PROTECTED] wrote: On Friday 12 September 2008 Stephen Connolly wrote: I know that plans for Maven 2.2 or 3.0 or some such is/was to deprecate the declaration of repositories within the pom because of this very problem. Of course banning repository declarations within poms is a swings and roundabouts solution: + fix this type of problem - cause problems if you need something that you cannot get pushed into repo1 Well, one could always declare additional repos in settings.xml. I'd say this is a far better place than pom.xml. Thank's Stephen for clarifying this. - martin Yeah but the problem with having to declare the additional repos in your settings.xml is now the project builds for me but not for you (until you get my settings.xml) That's true, but usually building some project imlies reading the installation instruction anyway... at least in theory ;) On the other hand reproducablity is an important requirement. Relying on a repository which some dependency introduced doesn't really increase reproducablity. And additionally, each repository that you add slows down the build as Maven has to check _all_ repositories that it knows about for the artifacts... and then if one of those is feeling slow your (normally fast) build becomes increasingly slow. At least for companies working seriously on software projects having an internal remote repository is a must, which reduces this problem. OTOH, for OSS developers working on multiple OSS projects, this might be a bigger issue. - martin signature.asc Description: This is a digitally signed message part.
Re: How to define a parent POM in a company wide.
that's a tricky way to solve this problem, does maven provide some mechanism to do this? 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it?
AW: How to define a parent POM in a company wide.
Thats the standard way. Why is this tricky? Maybe I explained to complicated. You have a parent pom (where you place it is rather irrelevant): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupId#a groupt for the parent pom/groupId artifactId# an artifact id for the parent pom/artifactId version1.0.0-SNAPSHOT/version packagingpom/packaging nameGlobal parent pom/name ... dependencies build definitions profiles plugins distribution definitions... /project This is the way how maven works with configuring global configurations. You can create very precise configuration hierarchies for all your projects. Look at the apache and codehaus projects, they show how this can be done very efficently. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:32 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. that's a tricky way to solve this problem, does maven provide some mechanism to do this? 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it?
Re: How to define a parent POM in a company wide.
can you give me a specific exmaple URL ,so i can understand this efficiently,Thanks! 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Thats the standard way. Why is this tricky? Maybe I explained to complicated. You have a parent pom (where you place it is rather irrelevant): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupId#a groupt for the parent pom/groupId artifactId# an artifact id for the parent pom/artifactId version1.0.0-SNAPSHOT/version packagingpom/packaging nameGlobal parent pom/name ... dependencies build definitions profiles plugins distribution definitions... /project This is the way how maven works with configuring global configurations. You can create very precise configuration hierarchies for all your projects. Look at the apache and codehaus projects, they show how this can be done very efficently. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:32 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. that's a tricky way to solve this problem, does maven provide some mechanism to do this? 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it?
Re: How to define a parent POM in a company wide.
The parent POM/child POM mechanism is explained in Maven documentation. See the POM reference page about multi-module, aggregation and/or inheritance: http://maven.apache.org/pom.html BR, *Olivier Gies* *Delivery Manager Customs Tax Software Engineering Center Bull, Architect of an Open World ^TM Phone: +86 (10) 65978001 - Ext 555 * *www.bull.com http://www.bull.com/* *This e-mail contains material that is confidential for the sole use of the intended recipient. Any review, reliance or distribution by others or forwarding without express permission is strictly prohibited. If you are not the intended recipient, please contact the sender and delete all copies.* Original Message Subject: Re: How to define a parent POM in a company wide. From: 陈思淼 [EMAIL PROTECTED] To: Maven Users List users@maven.apache.org Date: 12/09/2008 17:01 can you give me a specific exmaple URL ,so i can understand this efficiently,Thanks! 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Thats the standard way. Why is this tricky? Maybe I explained to complicated. You have a parent pom (where you place it is rather irrelevant): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupId#a groupt for the parent pom/groupId artifactId# an artifact id for the parent pom/artifactId version1.0.0-SNAPSHOT/version packagingpom/packaging nameGlobal parent pom/name ... dependencies build definitions profiles plugins distribution definitions... /project This is the way how maven works with configuring global configurations. You can create very precise configuration hierarchies for all your projects. Look at the apache and codehaus projects, they show how this can be done very efficently. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:32 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. that's a tricky way to solve this problem, does maven provide some mechanism to do this? 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: How to define a parent POM in a company wide.
Take a look at the svn repository for maven. Start here and then follow around: http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?view=markup http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=markup http://svn.apache.org/viewvc/maven/components/trunk/pom.xml?view=markup -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 11:00 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. can you give me a specific exmaple URL ,so i can understand this efficiently,Thanks! 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Thats the standard way. Why is this tricky? Maybe I explained to complicated. You have a parent pom (where you place it is rather irrelevant): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupId#a groupt for the parent pom/groupId artifactId# an artifact id for the parent pom/artifactId version1.0.0-SNAPSHOT/version packagingpom/packaging nameGlobal parent pom/name ... dependencies build definitions profiles plugins distribution definitions... /project This is the way how maven works with configuring global configurations. You can create very precise configuration hierarchies for all your projects. Look at the apache and codehaus projects, they show how this can be done very efficently. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:32 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. that's a tricky way to solve this problem, does maven provide some mechanism to do this? 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it?
Re: How to define a parent POM in a company wide.
I got it!Thanks for christian domsch's warm heart! 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Take a look at the svn repository for maven. Start here and then follow around: http://svn.apache.org/viewvc/maven/pom/trunk/asf/pom.xml?view=markup http://svn.apache.org/viewvc/maven/pom/trunk/maven/pom.xml?view=markup http://svn.apache.org/viewvc/maven/components/trunk/pom.xml?view=markup -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 11:00 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. can you give me a specific exmaple URL ,so i can understand this efficiently,Thanks! 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Thats the standard way. Why is this tricky? Maybe I explained to complicated. You have a parent pom (where you place it is rather irrelevant): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupId#a groupt for the parent pom/groupId artifactId# an artifact id for the parent pom/artifactId version1.0.0-SNAPSHOT/version packagingpom/packaging nameGlobal parent pom/name ... dependencies build definitions profiles plugins distribution definitions... /project This is the way how maven works with configuring global configurations. You can create very precise configuration hierarchies for all your projects. Look at the apache and codehaus projects, they show how this can be done very efficently. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:32 An: Maven Users List Betreff: Re: How to define a parent POM in a company wide. that's a tricky way to solve this problem, does maven provide some mechanism to do this? 2008/9/12 christian domsch (innoWake gmbh) [EMAIL PROTECTED] Hi, This is done by creating a POM-Project. You just create a normal project with just a pom in it. The type here is pom and there you configurate all your stuff, installed (or deploy) it in the repository and now you can use it as a parent pom. -- christian domsch [software developer] innoWake gmbh innovative.software.development(); graf-arco-strasse 18 | 89079 ulm-donautal fon: +49 (0)7 31 - 5 50 27 - 0 fax: +49 (0)7 31 - 5 50 27 - 20 [EMAIL PROTECTED] www.innowake.de innoWake gmbh hrb ulm 4584 geschäftsführer: thorsten bernecker This e-mail may contain confidential information. If you are not the intended recipient please notify the sender immediately and destroy this e-mail. -Ursprüngliche Nachricht- Von: 陈思淼 [mailto:[EMAIL PROTECTED] Gesendet: Freitag, 12. September 2008 10:16 An: users@maven.apache.org Betreff: How to define a parent POM in a company wide. we use Maven in our company, but there are some plugin config like source plugin ,compile plugin we'd like to define for everyone, there is a Super POM concept in Maven , can anybody tell me how to config it?
Specify text in Maven site generated pages
Hi all, I've been looking for how to change the text that appears in the generated html pages from the Maven site plugin, but I haven't found any information about this. Where are the templates or files used to generate each page (index.html, license.html, integration.html, etc)? Thank you in advance.
Re: Release translation
Done : http://jira.codehaus.org/browse/MPIR-141 Cheers. 2008/9/11 Hervé BOUTEMY [EMAIL PROTECTED] Le mercredi 10 septembre 2008, Baptiste MATHUS a écrit : Hi all, Well, this is more a question to the french translation of release I just saw in the 2.1 of the project-info-reports:dependencies plugin. Release had been translated Dégagement in french, which seems inadequate imo. Moreover Snapshot was left as is. I guess that not translating those words is the right choice in this case. Should I file an issue somewhere? In the MPIR jira? Yes, please Cheers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
creating target directory for 'packaging' of type 'pom'
Hi, I would like to use some plugins (like 'scm:status' goal) within packaging of type 'pom'. Unfortunately the pom type packaging does not creates target directory (nor scm:status plugin). Should I create a special plugin just for creating and cleaning the target directory and use it before scm:status goal? I'm not sure how it would affect http://jira.codehaus.org/browse/MCLEAN-20 Tibor
Re: How to override properties selectively with multiple filter files or profiles
I'm currently having the same problem as below. Not migrating from ant
though, but I need to be able to filter different set of properties having
the same name.
I don't think it's possible to affect a specific filter to a chosen
resource.
To illustrate, let's say you have two instances of an FTP module in your
main application.
These modules must be given a properties file for configuration.
ftp1.properties and ftp2.properties. Those two properties files hold the
exact same set of properties.
If one need to filter them, for say, different staging environment, one has
to find a trick. Unless I'm mistaken.
i'm about to code a complex system of prefix to be given to these set of
properties to be able to differentiate them. After some thinking, I'd rather
be able to affect a specific filter to a resource and be able to configure
multiple filters.
Is this already possible with Maven? Has anyone be confronted with that
problem?
cheers
Martin Buechler-3 wrote:
Hello,
I am still stuck with a mechanism, that I used a lot when writing
build and deploy systems for many developers and configurations with
ant. The main goal here is to avoid redundancy when listing
configuration properties, using a default build.properties and then
selectively override special property setting for a developers
enviromnent or for the target systems. Example:
build.xml:
propertyfile name=${user.name}.properties/
propertyfile name=${hostname}.properties/
propertyfile name=build.properties/
buid.properties:
prop1=val1
prop2=val2
prop3=val3
prop4=val4
prop5=val5
hostname.properties:
prop2=otherval
user.properties:
prop5=otherval
That way I never have to touch all existing properties, if I add a
new config value, i.e. to build.properties.
If I use profiles to modify the build element of the POM, I have to
inject a quite complete copy of the original build element. And, if I
try to list multiple filters int the filters element, the behaviour
is also not very obvious. Seems that only one of the
filter.properties files is in effect.
Is there a way to adjust properties non-redundant when using
profiles, or did I miss a maven feature, that does exactly that?
Thank you for reading
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/How-to-override-properties-selectively-with-multiple-filter-files-or-profiles-tp13662475p19454645.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Surefire, TestNG, and @ContextConfiguration
Hello all, This is my first post to maven-users mailing list, and from the start, I'm here to brag about my problems with maven. I'm having a problem with a TestNG test which runs successfully in Eclipse(3.4) TestNG plugin(5.8.02), but in Maven (2.0.9) Surefire (2.4.3) same test fails. It's a spring(2.5.5)-based integration test, it extends AbstractTestNGSpringContextTests, and through @ContextConfiguration annotation and its locations attribute it gets configured to load 3 context files, two of them referenced as classpath:/com/ while third one is from a dependent project/library (test is in one module [war] which depends on another module [jar] from same multimodule project [pom]) and is referenced using classpath*:/com/. . Among other things, test makes use of a bean (well) defined in that third (classpath*) context file. That referenced bean is injected to the test through use of autowiring (@Autowired). Problem is that that bean doesn't get found and test initialization fails. Log doesn't print that problematic context failed to load, just any of it's beans aren't accessible/registered. Btw, if I leave out * from classpath* spring reports that it couldn't load context file as it is missing. I've tried substituting autowiring with getting bean by name manually in setUp method through this.applicationContext.getBean but this also failed. Then I've thought that it has to do with loader used to load context's, so I explicitly specified loader attribute of @ContextConfiguration annotation to be GenericXmlContextLoader.class. This didn't work either. In all of these tweaks, test would continue to run well in eclipse testng plugin, but it fails in maven (both external and m2eclipse internal). Because I use reportng, I though it interfered with the test somehow but removing reportng didn't help as well as removing parallel mode for test execution. With this I ran out of options, with you guys being my last resort. Any comments and pointers are welcome! Thanks in advance! Regards, Stevo.
Re: Specify text in Maven site generated pages
Le vendredi 12 septembre 2008, Junco Hueco a écrit : Hi all, I've been looking for how to change the text that appears in the generated html pages from the Maven site plugin, but I haven't found any information about this. Where are the templates or files used to generate each page (index.html, license.html, integration.html, etc)? Thank you in advance. these files are generated by Maven Project Info Report Plugin http://maven.apache.org/plugins/maven-project-info-reports-plugin/ and you can create more content: http://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0-alpha-4 archetype plugin
On Fri, Sep 12, 2008 at 5:54 AM, Richard Chamberlain [EMAIL PROTECTED] wrote: Does anyone know if the latest archetype plugin is available yet? If so where can i pick it up from (it's not in central). It hasn't been released yet. The best way to find out when that might happen is to watch the dev list, for example: http://maven.markmail.org/search/?q=list%3Adev+archetype+order%3Adate-backward -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Surefire, TestNG, and @ContextConfiguration
Hello all, This is my first post to maven-users mailing list, and from the start, I'm here to brag about my problems with maven. I'm having a problem with a TestNG test which runs successfully in Eclipse(3.4) TestNG plugin(5.8.02), but in Maven (2.0.9) Surefire (2.4.3) same test fails. It's a spring(2.5.5)-based integration test, it extends AbstractTestNGSpringContextTests, and through @ContextConfiguration annotation and its locations attribute it gets configured to load 3 context files, two of them referenced as classpath:/com/ while third one is from a dependent project/library (test is in one module [war] which depends on another module [jar] from same multimodule project [pom]) and is referenced using classpath*:/com/. . Among other things, test makes use of a bean (well) defined in that third (classpath*) context file. That referenced bean is injected to the test through use of autowiring (@Autowired). Problem is that that bean doesn't get found and test initialization fails. Log doesn't print that problematic context failed to load, just any of it's beans aren't accessible/registered. Btw, if I leave out * from classpath* spring reports that it couldn't load context file as it is missing. I've tried substituting autowiring with getting bean by name manually in setUp method through this.applicationContext.getBean but this also failed. Then I've thought that it has to do with loader used to load context's, so I explicitly specified loader attribute of @ContextConfiguration annotation to be GenericXmlContextLoader.class. This didn't work either. In all of these tweaks, test would continue to run well in eclipse testng plugin, but it fails in maven (both external and m2eclipse internal). Because I use reportng, I though it interfered with the test somehow but removing reportng didn't help as well as removing parallel mode for test execution. With this I ran out of options, with you guys being my last resort. Any comments and pointers are welcome! Thanks in advance! Regards, Stevo.
Re: Custom repository problem
Yes, that was it. Thank you for your help. I used the DSMP proxy server and copied those into the repository folder and everything started working. Thanks again, Yaakov. On Thu, Sep 11, 2008 at 5:55 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Thu, Sep 11, 2008 at 2:40 PM, Yaakov Chaikin [EMAIL PROTECTED] wrote: Yes, it's there. I basically checked out my code under one of the users on the server, then issued 'mvn clean install', then collected everything from the ~/.m2/repository and moved it to a folder configured to be accessible over the web. Ah, that's probably why you're having trouble. The metadata is different in local and remote repositories, and plugins (and snapshots) are resolved using that metadata. There are some scripts around to convert local metadata to remote if you check the archives. Using a repository manager (Archiva, Nexus, Artifactory) is also something to consider. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 2.0-alpha-4 archetype plugin
Thanks, Is it possible to pick up a snapshot from somewhere? I wanted to try out the feature ARCHETYPE-191. Or is it a case of building from source? Richard -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 14:05 To: Maven Users List Subject: Re: 2.0-alpha-4 archetype plugin On Fri, Sep 12, 2008 at 5:54 AM, Richard Chamberlain [EMAIL PROTECTED] wrote: Does anyone know if the latest archetype plugin is available yet? If so where can i pick it up from (it's not in central). It hasn't been released yet. The best way to find out when that might happen is to watch the dev list, for example: http://maven.markmail.org/search/?q=list%3Adev+archetype+order%3Adate-ba ckward -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Specifying jdk version for maven-javadoc-plugin
Hi, I'm using jdk 1.6 for the maven compiler plugin. But JAVA_HOME env is set to jdk 1.5. So during the site phase, generating javadoc goal fails. It's because it still uses jdk 1.5. Is there a way to specify the jdk version to be used for the maven-javadoc-plugin and also following plugins: maven-pmd-plugin cobertura-maven-plugin Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: creating target directory for 'packaging' of type 'pom'
If a plugin needs to write to target directory, it is responsible to create it. if that the case, you need to file a JIRA against that plugin for the time being, you can use antrun plugin to create target dir for you prior to executing the plugin -D On Fri, Sep 12, 2008 at 5:37 AM, Tibor Kiss [EMAIL PROTECTED] wrote: Hi, I would like to use some plugins (like 'scm:status' goal) within packaging of type 'pom'. Unfortunately the pom type packaging does not creates target directory (nor scm:status plugin). Should I create a special plugin just for creating and cleaning the target directory and use it before scm:status goal? I'm not sure how it would affect http://jira.codehaus.org/browse/MCLEAN-20 Tibor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0-alpha-4 archetype plugin
Hi, I just uploaded a snapshot of 2.0-alpha-4 on the apache's snapshot repository Regards, Raphaël 2008/9/12 Richard Chamberlain [EMAIL PROTECTED]: Thanks, Is it possible to pick up a snapshot from somewhere? I wanted to try out the feature ARCHETYPE-191. Or is it a case of building from source? Richard -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 14:05 To: Maven Users List Subject: Re: 2.0-alpha-4 archetype plugin On Fri, Sep 12, 2008 at 5:54 AM, Richard Chamberlain [EMAIL PROTECTED] wrote: Does anyone know if the latest archetype plugin is available yet? If so where can i pick it up from (it's not in central). It hasn't been released yet. The best way to find out when that might happen is to watch the dev list, for example: http://maven.markmail.org/search/?q=list%3Adev+archetype+order%3Adate-ba ckward -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specifying jdk version for maven-javadoc-plugin
Is there a reason you cannot simply update the JAVA_HOME to point it at JDK5? Wayne On Fri, Sep 12, 2008 at 7:23 AM, Krishnamurthi, Venkat [EMAIL PROTECTED] wrote: Hi, I'm using jdk 1.6 for the maven compiler plugin. But JAVA_HOME env is set to jdk 1.5. So during the site phase, generating javadoc goal fails. It's because it still uses jdk 1.5. Is there a way to specify the jdk version to be used for the maven-javadoc-plugin and also following plugins: maven-pmd-plugin cobertura-maven-plugin Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Specifying jdk version for maven-javadoc-plugin
Err, point at JDK6. ;-) Wayne On Fri, Sep 12, 2008 at 10:40 AM, Wayne Fay [EMAIL PROTECTED] wrote: Is there a reason you cannot simply update the JAVA_HOME to point it at JDK5? Wayne On Fri, Sep 12, 2008 at 7:23 AM, Krishnamurthi, Venkat [EMAIL PROTECTED] wrote: Hi, I'm using jdk 1.6 for the maven compiler plugin. But JAVA_HOME env is set to jdk 1.5. So during the site phase, generating javadoc goal fails. It's because it still uses jdk 1.5. Is there a way to specify the jdk version to be used for the maven-javadoc-plugin and also following plugins: maven-pmd-plugin cobertura-maven-plugin Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Specifying jdk version for maven-javadoc-plugin
Yeah. We have to have both jdk5 and jdk6. Only very few projects in cruisecontrol use jdk.. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Friday, September 12, 2008 1:41 PM To: Maven Users List Subject: Re: Specifying jdk version for maven-javadoc-plugin Err, point at JDK6. ;-) Wayne On Fri, Sep 12, 2008 at 10:40 AM, Wayne Fay [EMAIL PROTECTED] wrote: Is there a reason you cannot simply update the JAVA_HOME to point it at JDK5? Wayne On Fri, Sep 12, 2008 at 7:23 AM, Krishnamurthi, Venkat [EMAIL PROTECTED] wrote: Hi, I'm using jdk 1.6 for the maven compiler plugin. But JAVA_HOME env is set to jdk 1.5. So during the site phase, generating javadoc goal fails. It's because it still uses jdk 1.5. Is there a way to specify the jdk version to be used for the maven-javadoc-plugin and also following plugins: maven-pmd-plugin cobertura-maven-plugin Thanks, Venkat - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
filter module when deploying multi-modules project
Hi, If I have a multi-modules project with a package type jar and war, how can I disable the upload of the war file when I perform a deploy to my own repository? In another word, I just want to upload the jar as artifact and ignore the war file. Is this possible? -- Come visit my open source projects: http://code.google.com/p/sweetscala - a Scala web framework. Building web application the sweet way. http://code.google.com/p/javasupport - a collection of libraries and tools for Java development. Get a SpringMVC webapp started fast!
Generating performance tests/reports?
Does anyone have pointers to easily generate performance reports for the tests? with historical comparisons etc? ie. similar to how the eclipse project reports etc (example: http://download.eclipse.org/eclipse/downloads/drops/R-3.4-200806172000/performance/performance.php ) Looking at the surefire documentation, it doesn't seem surefire can do this? Thanks, Kent
Re: Multi-module site generation?
On Fri, Sep 12, 2008 at 5:52 PM, Dave Newton [EMAIL PROTECTED] wrote:
Where should I look in TFM/TFW to find a canonical way for a multi-module
project to create a complete website including the modules?
Right now I've configured each module's site plugin's outputDirectory to
point at ../target/site/${artifactId} and set each modules's url to
${artifactId} but this feels hokey and wrong and makes me feel bad about
myself.
Should I just assemble the disparate module sites and get them to the final
site directory somehow?
What are you trying to do by setting those values? Preview it locally
before deploying it?
The site plugin builds each piece of the site under the module's
'target' directory, but the links won't work from there. You'll need
to deploy it somewhere for it to all work together. (I'd say stage
it, but I think some links are still broken using the stage-deploy
goal.)
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0-alpha-4 archetype plugin
Hi Raphaël, I appreciate the enhancement to support file renaming. I actually took it a step further to support token replacement with any available context property. I attached the patch with those changes including a test to http://jira.codehaus.org/browse/ARCHETYPE-191 Would you be willing to review that patch and apply it? I think it will be useful. Thanks again and let me know if you need any clarification or anything else. Thanks! ~Brad http://jira.codehaus.org/secure/attachment/37014/ReplaceAnyContextPropertyEnhancement.patch -Original Message- From: Raphaël Piéroni [EMAIL PROTECTED] Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org Subject: Re: 2.0-alpha-4 archetype plugin Date: Fri, 12 Sep 2008 18:00:14 +0200 Hi, I just uploaded a snapshot of 2.0-alpha-4 on the apache's snapshot repository Regards, Raphaël 2008/9/12 Richard Chamberlain [EMAIL PROTECTED]: Thanks, Is it possible to pick up a snapshot from somewhere? I wanted to try out the feature ARCHETYPE-191. Or is it a case of building from source? Richard -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 14:05 To: Maven Users List Subject: Re: 2.0-alpha-4 archetype plugin On Fri, Sep 12, 2008 at 5:54 AM, Richard Chamberlain [EMAIL PROTECTED] wrote: Does anyone know if the latest archetype plugin is available yet? If so where can i pick it up from (it's not in central). It hasn't been released yet. The best way to find out when that might happen is to watch the dev list, for example: http://maven.markmail.org/search/?q=list%3Adev+archetype+order%3Adate-ba ckward -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dependency plugin
Can some one please shine some light on the following scenario.. I have parent pom and 2 modules. Module A produces a jar file Module B has Module A's jar as dependency, but it uses the dependency plugin to unpack it. If I run mvn package from the parent. Module B's dependency plugin is always trying to take the jar from the repository, not from Module A's target So my build fails with [INFO] Unable to find artifact. I always have to run mvn install on Module A before using Module B. Quite tedious.. And I do have the jar listed in Module B as a dependency and then again in he plugin like so: dependency groupIdfoo.bar/groupId artifactIdmyjar/artifactId version1.0.0-SNAPSHOT/version typejar/type scopecompile/scope /dependency plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0/version executions execution idgetjar/id phasegenerate-sources/phase goals goalunpack/goal /goals configuration artifactItems artifactItem groupIdfoo.bar/groupId artifactIdmyjar/artifactId typejar/type overWritetrue/overWrite outputDirectory target/tmp /outputDirectory /artifactItem /artifactItems overWriteReleasestrue/overWriteReleases overWriteSnapshotstrue/overWriteSnapshots /configuration /execution /executions /plugin Any thoughts? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency plugin
did you use install goal ? -D On Fri, Sep 12, 2008 at 6:54 PM, Build Guy [EMAIL PROTECTED] wrote: Can some one please shine some light on the following scenario.. I have parent pom and 2 modules. Module A produces a jar file Module B has Module A's jar as dependency, but it uses the dependency plugin to unpack it. If I run mvn package from the parent. Module B's dependency plugin is always trying to take the jar from the repository, not from Module A's target So my build fails with [INFO] Unable to find artifact. I always have to run mvn install on Module A before using Module B. Quite tedious.. And I do have the jar listed in Module B as a dependency and then again in he plugin like so: dependency groupIdfoo.bar/groupId artifactIdmyjar/artifactId version1.0.0-SNAPSHOT/version typejar/type scopecompile/scope /dependency plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0/version executions execution idgetjar/id phasegenerate-sources/phase goals goalunpack/goal /goals configuration artifactItems artifactItem groupIdfoo.bar/groupId artifactIdmyjar/artifactId typejar/type overWritetrue/overWrite outputDirectory target/tmp /outputDirectory /artifactItem /artifactItems overWriteReleasestrue/overWriteReleases overWriteSnapshotstrue/overWriteSnapshots /configuration /execution /executions /plugin Any thoughts? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency plugin
well, the whole point is that... If module A's jar is a dependency thats needed for compilation of Module B. I don't need to use the install goal. Module B finds the Module A jar when building from the parent. How ever. If I further want to do something with Module A's jar in Module B. Like extract it using dependency unpack. I can't, unless I 1st run install goal from Module A. But this means the release plugin won't properly work from the parent pom unless I release Module A and B individually. Here's what my project looks like: -parent pom | - Module A (produces Jar) | - Module B (includes jar) I'm wondering if this is just a limitation of the dependency plugin.. :-/ I've been struggling with this for quite some time. Thought? thanks! Taras Dan Tran wrote: did you use install goal ? -D On Fri, Sep 12, 2008 at 6:54 PM, Build Guy [EMAIL PROTECTED] wrote: Can some one please shine some light on the following scenario.. I have parent pom and 2 modules. Module A produces a jar file Module B has Module A's jar as dependency, but it uses the dependency plugin to unpack it. If I run mvn package from the parent. Module B's dependency plugin is always trying to take the jar from the repository, not from Module A's target So my build fails with [INFO] Unable to find artifact. I always have to run mvn install on Module A before using Module B. Quite tedious.. And I do have the jar listed in Module B as a dependency and then again in he plugin like so: dependency groupIdfoo.bar/groupId artifactIdmyjar/artifactId version1.0.0-SNAPSHOT/version typejar/type scopecompile/scope /dependency plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-dependency-plugin/artifactId version2.0/version executions execution idgetjar/id phasegenerate-sources/phase goals goalunpack/goal /goals configuration artifactItems artifactItem groupIdfoo.bar/groupId artifactIdmyjar/artifactId typejar/type overWritetrue/overWrite outputDirectory target/tmp /outputDirectory /artifactItem /artifactItems overWriteReleasestrue/overWriteReleases overWriteSnapshotstrue/overWriteSnapshots /configuration /execution /executions /plugin Any thoughts? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency plugin
On Fri, Sep 12, 2008 at 7:10 PM, Build Guy [EMAIL PROTECTED] wrote: But this means the release plugin won't properly work from the parent pom unless I release Module A and B individually. Not necessarily. You can configure the release plugin to run all the way through install in the prepare phase. (By default it only goes through integration-test, which is before install.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
--- On Fri, 9/12/08, Wendy Smoak wrote: What are you trying to do by setting those values? Preview it locally before deploying it? That was the initial goal, but it's likely the final site will be deployed to a local directory location on the CI machine. I've tried site:deploy with the following distributionManagement in the top-level POM in the hopes it would all get dumped to a directory in the parent site, but so far no joy; only the parent shows up. distributionManagement site urlfile://deployed-site/url /site /distributionManagement The parent and two module POMs are at http://pastebin.com/m1c8573cc. I'm assuming that there are multiple things wrong with what I'm doing (finally trying to figure out Maven) so any advice/criticisms/etc. are welcome. I also tried site:stage-deploy, which created the following hierarchy: target/staging/localhost/MultiModCli/... .../MultiModCore/... .../deployed-site/(the parent project) So I'd guess I'm just doing (one of many :) things all cow's legs up, 'cuz it's close. Thanks, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency plugin
I see, so what you suggest is add install to the goals conf of the release plugin? Cheers Wendy Smoak wrote: On Fri, Sep 12, 2008 at 7:10 PM, Build Guy [EMAIL PROTECTED] wrote: But this means the release plugin won't properly work from the parent pom unless I release Module A and B individually. Not necessarily. You can configure the release plugin to run all the way through install in the prepare phase. (By default it only goes through integration-test, which is before install.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2.0-alpha-4 archetype plugin
I have attached a second version of the patch. This one properly handles undefined properties. http://jira.codehaus.org/secure/attachment/37015/ReplaceAnyContextPropertyEnhancement-v2.patch I added an additional test for this. Again, please review and consider applying the patch. Thanks, Brad -Original Message- From: Brad [EMAIL PROTECTED] Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org Subject: Re: 2.0-alpha-4 archetype plugin Date: Fri, 12 Sep 2008 18:47:53 -0700 Hi Raphaël, I appreciate the enhancement to support file renaming. I actually took it a step further to support token replacement with any available context property. I attached the patch with those changes including a test to http://jira.codehaus.org/browse/ARCHETYPE-191 Would you be willing to review that patch and apply it? I think it will be useful. Thanks again and let me know if you need any clarification or anything else. Thanks! ~Brad http://jira.codehaus.org/secure/attachment/37014/ReplaceAnyContextPropertyEnhancement.patch -Original Message- From: Raphaël Piéroni [EMAIL PROTECTED] Reply-To: Maven Users List users@maven.apache.org To: Maven Users List users@maven.apache.org Subject: Re: 2.0-alpha-4 archetype plugin Date: Fri, 12 Sep 2008 18:00:14 +0200 Hi, I just uploaded a snapshot of 2.0-alpha-4 on the apache's snapshot repository Regards, Raphaël 2008/9/12 Richard Chamberlain [EMAIL PROTECTED]: Thanks, Is it possible to pick up a snapshot from somewhere? I wanted to try out the feature ARCHETYPE-191. Or is it a case of building from source? Richard -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 14:05 To: Maven Users List Subject: Re: 2.0-alpha-4 archetype plugin On Fri, Sep 12, 2008 at 5:54 AM, Richard Chamberlain [EMAIL PROTECTED] wrote: Does anyone know if the latest archetype plugin is available yet? If so where can i pick it up from (it's not in central). It hasn't been released yet. The best way to find out when that might happen is to watch the dev list, for example: http://maven.markmail.org/search/?q=list%3Adev+archetype+order%3Adate-ba ckward -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
On Fri, Sep 12, 2008 at 7:17 PM, Dave Newton [EMAIL PROTECTED] wrote: I've tried site:deploy with the following distributionManagement in the top-level POM in the hopes it would all get dumped to a directory in the parent site, but so far no joy; only the parent shows up. Try 'mvn site-deploy' instead, from a parent which has modules defined. It should work. http://maven.apache.org/guides/mini/guide-site.html (site-deploy is a lifecycle phase, while site:deploy means to run one specific goal of the site plugin.) (You may need an id for the site in distribution management. Wagon complained when I didn't have one...) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
--- On Fri, 9/12/08, Wendy Smoak wrote: http://maven.apache.org/guides/mini/guide-site.html (site-deploy is a lifecycle phase, while site:deploy means to run one specific goal of the site plugin.) Oh. Hrm. Something new every day, and all that. Running site-deploy works, as long as I define a file URI that isn't broken. Which I couldn't. Turns out site:deploy works just fine too (once the sites have been generated, I mean). Sheesh :/ Thanks much, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependency plugin
I am not sure why you are reluctant to run install goal? This sort of thing works for me every day. Have you try cut release from the parent pom? -D On Fri, Sep 12, 2008 at 7:31 PM, Build Guy [EMAIL PROTECTED] wrote: I see, so what you suggest is add install to the goals conf of the release plugin? Cheers Wendy Smoak wrote: On Fri, Sep 12, 2008 at 7:10 PM, Build Guy [EMAIL PROTECTED] wrote: But this means the release plugin won't properly work from the parent pom unless I release Module A and B individually. Not necessarily. You can configure the release plugin to run all the way through install in the prepare phase. (By default it only goes through integration-test, which is before install.) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module site generation?
--- On Fri, 9/12/08, Dave Newton lied: Running site-deploy works, as long as I define a file URI that isn't broken. Which I couldn't. Turns out site:deploy works just fine too (once the sites have been generated, I mean). Spoke too soon; I thought it had worked at one point but now the module links it's creating point to the parent POM directory + parent artifactId. Ah; removing *all* the url elements seems to have fixed it; I think my root POM's url messed up all the others. Curious; I'll look into it again tomorrow. Thanks again, Dave - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Assembly question
I have a multi-module project. One of the modules inside of it has multiple source directories using build-helper-maven-plugin. I need the source in one of those directories to be included in a special place in the assembly. I was able to get that to work. There are a couple java files in that dir and I need the compiled class files as well. However, whenever I try to add the binaries element, I get all the binaries in all the source folders instead of only the one source folder that I want. moduleSet includes includecom.c:Services/include /includes sources includeModuleDirectoryfalse/includeModuleDirectory fileSets fileSet directorysrc/main/user//directory outputDirectoryuser/outputDirectory /fileSet /fileSets /sources binaries includeDependenciesfalse/includeDependencies includesincludesrc/main/user/include/includes excludes excludecom/**/*.*/exclude excludesrc/main/*/com/**/*.*/exclude excludesrc/main/java/**/*.*/exclude excludesrc/main/java/exclude excludesrc//exclude excludesrc/main/**/*.*/exclude excludesrc/**/*.*/exclude /excludes outputDirectoryuser/outputDirectory /binaries /moduleSet The excludes clause is a mess because I was trying anything--even with all that, all the binaries were included in the output user directory. How can I get it to include only the binaries from a certain source folder? Or, it is delineated by specific packages, so how could I do it by including only certain packages? Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: 2.0-alpha-4 archetype plugin
That's great, thanks. -Original Message- From: Raphaël Piéroni [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 17:00 To: Maven Users List Subject: Re: 2.0-alpha-4 archetype plugin Hi, I just uploaded a snapshot of 2.0-alpha-4 on the apache's snapshot repository Regards, Raphaël 2008/9/12 Richard Chamberlain [EMAIL PROTECTED]: Thanks, Is it possible to pick up a snapshot from somewhere? I wanted to try out the feature ARCHETYPE-191. Or is it a case of building from source? Richard -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: 12 September 2008 14:05 To: Maven Users List Subject: Re: 2.0-alpha-4 archetype plugin On Fri, Sep 12, 2008 at 5:54 AM, Richard Chamberlain [EMAIL PROTECTED] wrote: Does anyone know if the latest archetype plugin is available yet? If so where can i pick it up from (it's not in central). It hasn't been released yet. The best way to find out when that might happen is to watch the dev list, for example: http://maven.markmail.org/search/?q=list%3Adev+archetype+order%3Adate-ba ckward -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
