Re: relativePath not working
Hi Franz, that seems strange. The jira indicates the problem when groupId differs, but in the project I sent you, the groupId is all the same (as far as I can tell). Thanks for looking! Davis On 4/13/07, franz see [EMAIL PROTECTED] wrote: Good day, I got your email and I think I saw the bug ( see [1] ). As for a workaround, I can't think of anything right now. Cheers, Franz [1] http://jira.codehaus.org/browse/MNG-2068 franz see wrote: Good day, I just tried creating a simple project with inheritance and I cannot duplicate your problem. I ran mvn validate, mvn package, mvn compiler:compile and it builds just fine with my Maven 2.0.6, and Java 1.5.0_11, running under Windows XP. I've attached here that simple project, kindly check if it works in your machine. If it does not, then I guess it has something to do with your machine ( maven setup perhaps? ). If it does, then maybe there's something maybe something in your maven project is causing the failure. Thanks http://www.nabble.com/file/7847/relative-path-of-parent.zip relative-path-of-parent.zip , Franz Davis Ford-2 wrote: Hi Adrian, I've tried nearly everything. Note, I'm using 2.0.6. I tried 1 removing the relativePath setting altogether 2 relativePath../pom.xml/relativePath 3 relativePath../../parent_project/relativePath 4 relativePath../../parent_project/pom.xml/relativePath 5 relativePath [absolute path here] /relativePath I've double-checked the artifactId, groupId, and version in all pom's like 100 times to make sure they match. I've double-checked the directory structure the same number of times to make sure it is right. If I sit in parent_project dir and execute: mvn -N install Then, yes, I can go into sub-dirs and run commands just fine, b/c it pulls the parent pom from the local repo. This is not desired, b/c I will have to tell users to execute this command everytime. They will find it confusing, and it is yet another step that is easily forgotten. Is there *any* way to get the relativePath to work? I've seen other posts in the mailing list about it...people having problems, JIRA's filed. Is this still a known issue in 2.0.6? Thanks in advance, Davis On 4/12/07, Adrian Shum [EMAIL PROTECTED] wrote: If I remember correctly, if your parent POM is located at the parent directory, you don't need to declare the relative path, as mvn2 should be able to find it. that is, (hope I remember correctly :P ), mvn2 will find the parent POM in the following order: 1) parent directory 2) modules in the same multi-module build 3) repository (However, in 2.0.4, there seems to be a bug prohibiting 1 from working in some scenerioes) Adrian From: Davis Ford [mailto:[EMAIL PROTECTED] Sent: Fri 4/13/2007 8:51 AM To: Maven Users List Subject: relativePath not working Hi, I'm using mvn 2.0.6 I have a simple structure parent_project sub_project pom.xml pom.xml parent_project has this: groupIdmy.org/groupId artifactIdparent/artifactId version1.0-SNAPSHOT/version packagingpom/packaging sub_project has this: parent groupIdmy.org/groupId artifactIdparent/artifactId version1.0-SNAPSHOT/version relativePath../pom.xml/relativePath /parent groupIdmy.org/groupId artifactIdsub/artifactId packagingpom/packaging version1.0-SNAPSHOT/version anytime i issue any mvn command in the sub_project dir, i get: org.apache.maven.reactor.MavenExecutionException: Cannot find parent: etc... how can i get relativePath to work? thx, davis This email is confidential. If you are not the intended recipient, please delete it from your system and notify the sender immediately. Any unauthorized use, disclosure, dissemination or copying of this email is prohibited. Taifook Securities Group, its group companies and their content providers (Parties) shall not be responsible for the accuracy or completeness of this email or its attachment, if any, which could contain virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive late. The Parties do not accept liability for any damage caused by this email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Zeno Consulting, Inc. http://www.zenoconsulting.biz 248.894.4922 phone 313.884.2977 fax -- View this message in context: http://www.nabble.com/relativePath-not-working-tf3569116s177.html#a9973251 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Zeno Consulting, Inc. http://www.zenoconsulting.biz 248.894.4922 phone 313.884.2977 fax
Re: how can i compile a multiple directories with pom.xml?
Good day, After a quick browse to [1], [2], [3], [4], and [5] - I think they are compiled all at once. I think it's like doing javac -classpath source locations ... If you want to do one java on each source location, you may have to run the maven-compiler-plugin and provide each their own classpath via the compiler arguments ( see [6] and [7] ). Cheers, Franz [1] http://svn.codehaus.org/mojo/trunk/mojo/build-helper-maven-plugin/src/main/java/org/codehaus/mojo/buildhelper/AddSourceMojo.java [2] http://maven.apache.org/ref/current/maven-project/apidocs/org/apache/maven/project/MavenProject.html#getCompileSourceRoots() [3] http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-compiler-plugin/src/main/java/org/apache/maven/plugin/AbstractCompilerMojo.java [4] http://svn.codehaus.org/plexus/tags/plexus-compiler-1.5.3/plexus-compiler-api/src/main/java/org/codehaus/plexus/compiler/CompilerConfiguration.java [5] http://svn.codehaus.org/plexus/tags/plexus-compiler-1.5.3/plexus-compilers/plexus-compiler-javac/src/main/java/org/codehaus/plexus/compiler/javac/JavacCompiler.java [6] http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArgument [7] http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#compilerArguments Baz-6 wrote: Fay, Frank thanks for the replies. Frank, I checked the first example of the link you sent. The example demonstrated how to add sources, what about the order of compilation? Is it sequential? Thanks. A. On 4/11/07, franz see [EMAIL PROTECTED] wrote: Good day, Try [1]. Cheers, Franz [1] http://mojo.codehaus.org/build-helper-maven-plugin/howto.html Wayne Fay wrote: Ideally you would just make multiple poms ie: toplevel/pom.xml (modules a, b, c) toplevel/a/pom.xml (no dependencies) toplevel/b/pom.xml (depends on a) toplevel/c/pom.xml (depends on b) Wayne On 4/11/07, Baz [EMAIL PROTECTED] wrote: All, If I have a directory src and subdirectories a, b and c. Each subdirectories have their own pom.xml files. Output of a depends on b, and b on c. Is it possible to have a pom.xml in src directory and start compilation in directory c, then b then a? Thanks. A. - 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] -- View this message in context: http://www.nabble.com/how-can-i-compile-a-multiple-directories-with-pom.xml--tf3563309s177.html#a9953345 Sent from the Maven - Users mailing list archive at Nabble.com. - 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] -- View this message in context: http://www.nabble.com/how-can-i-compile-a-multiple-directories-with-pom.xml--tf3563309s177.html#a9973455 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: q on mvn dependency plugin
On 4/13/07, franz see [EMAIL PROTECTED] wrote: Good, AFAIK, there's none. But please feel free to file a request in the jira for that :-) and send a patch ! J - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: relativePath not working
Good day, Ah, yes :-) Thanks for pointing that out...then I guess the proper issue is [1] :-) Thanks, Franz [1] http://jira.codehaus.org/browse/MNG-2318 Davis Ford-2 wrote: Hi Franz, that seems strange. The jira indicates the problem when groupId differs, but in the project I sent you, the groupId is all the same (as far as I can tell). Thanks for looking! Davis On 4/13/07, franz see [EMAIL PROTECTED] wrote: Good day, I got your email and I think I saw the bug ( see [1] ). As for a workaround, I can't think of anything right now. Cheers, Franz [1] http://jira.codehaus.org/browse/MNG-2068 franz see wrote: Good day, I just tried creating a simple project with inheritance and I cannot duplicate your problem. I ran mvn validate, mvn package, mvn compiler:compile and it builds just fine with my Maven 2.0.6, and Java 1.5.0_11, running under Windows XP. I've attached here that simple project, kindly check if it works in your machine. If it does not, then I guess it has something to do with your machine ( maven setup perhaps? ). If it does, then maybe there's something maybe something in your maven project is causing the failure. Thanks http://www.nabble.com/file/7847/relative-path-of-parent.zip relative-path-of-parent.zip , Franz Davis Ford-2 wrote: Hi Adrian, I've tried nearly everything. Note, I'm using 2.0.6. I tried 1 removing the relativePath setting altogether 2 relativePath../pom.xml/relativePath 3 relativePath../../parent_project/relativePath 4 relativePath../../parent_project/pom.xml/relativePath 5 relativePath [absolute path here] /relativePath I've double-checked the artifactId, groupId, and version in all pom's like 100 times to make sure they match. I've double-checked the directory structure the same number of times to make sure it is right. If I sit in parent_project dir and execute: mvn -N install Then, yes, I can go into sub-dirs and run commands just fine, b/c it pulls the parent pom from the local repo. This is not desired, b/c I will have to tell users to execute this command everytime. They will find it confusing, and it is yet another step that is easily forgotten. Is there *any* way to get the relativePath to work? I've seen other posts in the mailing list about it...people having problems, JIRA's filed. Is this still a known issue in 2.0.6? Thanks in advance, Davis On 4/12/07, Adrian Shum [EMAIL PROTECTED] wrote: If I remember correctly, if your parent POM is located at the parent directory, you don't need to declare the relative path, as mvn2 should be able to find it. that is, (hope I remember correctly :P ), mvn2 will find the parent POM in the following order: 1) parent directory 2) modules in the same multi-module build 3) repository (However, in 2.0.4, there seems to be a bug prohibiting 1 from working in some scenerioes) Adrian From: Davis Ford [mailto:[EMAIL PROTECTED] Sent: Fri 4/13/2007 8:51 AM To: Maven Users List Subject: relativePath not working Hi, I'm using mvn 2.0.6 I have a simple structure parent_project sub_project pom.xml pom.xml parent_project has this: groupIdmy.org/groupId artifactIdparent/artifactId version1.0-SNAPSHOT/version packagingpom/packaging sub_project has this: parent groupIdmy.org/groupId artifactIdparent/artifactId version1.0-SNAPSHOT/version relativePath../pom.xml/relativePath /parent groupIdmy.org/groupId artifactIdsub/artifactId packagingpom/packaging version1.0-SNAPSHOT/version anytime i issue any mvn command in the sub_project dir, i get: org.apache.maven.reactor.MavenExecutionException: Cannot find parent: etc... how can i get relativePath to work? thx, davis This email is confidential. If you are not the intended recipient, please delete it from your system and notify the sender immediately. Any unauthorized use, disclosure, dissemination or copying of this email is prohibited. Taifook Securities Group, its group companies and their content providers (Parties) shall not be responsible for the accuracy or completeness of this email or its attachment, if any, which could contain virus, be corrupted, destroyed, incomplete, intercepted, lost or arrive late. The Parties do not accept liability for any damage caused by this email. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Zeno Consulting, Inc. http://www.zenoconsulting.biz 248.894.4922 phone 313.884.2977 fax -- View this message in context:
Re: Excluding certain modules in a profile
Exactly.
franz see wrote:
Good day,
Are you saying that you added plugin dependencies for your antrun, and
your antrun cannot see it if it's in the profile-added module?
Cheers,
Franz
takai wrote:
Hi Franz,
The profile-added module runs the integration tests. Usecase: Developer
usually wants to just build the project - not run the entire integration
test suite which takes a while. An explicit -P integration call is
needed to run them. The real reason i want to add profile specific
modules is to avoid cleaning them by default.
The profile-added module contains the antrun plugin. The plugin
dependencies are not accessible to the ant build files (and therefore, i
suppose, to the plugin).
Cheers,
Daniel
franz see wrote:
Good day,
Which project does not include its dependencies...the aggregating or the
profile-added module? ..And which classpath?
Cheers,
Franz
takai wrote:
This seems to work. However i found that putting modules in the profile
somehow breaks the dependency mechanism.
I use the antrun plugin in an integration module. When i execute with a
regular pom or just inside the integration module everything works
fine.
Once i use the aforementioned module by profile approch the plugin does
not include dependencies in the classpath.
Using Maven 2.0.6.
File an issue?
Daniel
Jonathan Anstey wrote:
Try this to set up a default profile:
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
modules
...
/modules
/profile
Cheers,
Jon
Wayne Fay wrote:
I don't believe this is possible. Instead, I think you would need to
set it up as follows:
parent/pom.xml
modules/
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
profile
iddefault/id
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
And then use some activation magic to decide when to turn on default
etc.
No guarantee this would work as I've never done it myself, but I'm
fairly certain your other proposed solution will not work, so give
this a try.
Wayne
On 2/7/07, Balasubramanian, Ravi Shankar [EMAIL PROTECTED]
wrote:
Hi,
I am using maven 2.0.4 and I want to be excluding certain modules
while
building my project in a certain profile. Following is the
scenarion:
This is how my main pom looks like:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdcom.informatica.metadatarepository.qa/groupId
artifactIdmetamodels/artifactId
packagingpom/packaging
name${artifactId}/name
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
With the above pom, when I build the project activating the profile
cpp-qa, all the four modules are being built. I want to be
building
only module3 and module4 using certain configurations in this
profile.
Is there a way by which I can accomplish this in maven2?
Thanks for any help,
Ravi.
Tough times never last, but tough men do...
-
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]
--
View this message in context:
http://www.nabble.com/Excluding-certain-modules-in-a-profile-tf3185303s177.html#a9974771
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn site site:deploy problem
Trashes it in what way? Which files are missing? My understanding is that when you do site:deploy it just copies to file over, it doesn't delete from the target first. But exactly how this works probably depends on how you have it configured. Do you get the same problem if you have: distributionManagement site idwebsite/id urlfile:///C:\Program Files\Apache Group\Apache2\htdocs\site/url /site /distributionManagement What url are you currently using? David On Thu, 12 Apr 2007 06:41:49 -0700 (PDT), Ionut S [EMAIL PROTECTED] said: Hi, Not sure if my problem is related to mvn or continuum, so excuse me if I'm wrong.. Anyway, we have a continuum site in place, which works fine in general. There is one abnormal behaviour that made me write to this list though: if the build fails (for any reason), the site gets trashed. This is because the command we give: mvn clean install site site:deploy starts to copy the files for each project, without waiting for the whole project to be built. This trashes the site and we can't see it unless we fix the build. Is there something we can do in order to fix this issue ? Thank you ! Ionut - Never miss an email again! Yahoo! Toolbar alerts you the instant new Mail arrives. Check it out.
M2: Strange problem with assembly plugin
Hi,
I have a project that creates a tar.gz deliverable that includes unix
shell scripts. In the assembly descriptor, I have:
fileSet
directorytarget/bin/directory
outputDirectorybin/outputDirectory
includes
include*.sh/include
/includes
fileMode0755/fileMode
lineEndinglf/lineEnding
/fileSet
As you can see, I'm specifying the lineEnding.
When I deploy this from the project level it works fine.
However, when I deploy this from the parent level, the bin files get
included, but the lineEnding is not honoured.
Anyone encountered this before? Any suggestions?
Thanks, Ian
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, please contact the
sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and
delete the e-mail and do not disclose its contents to any person. We believe,
but do not warrant, that this e-mail and any attachments are virus free, but
you must take full responsibility for virus checking. Please refer to
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer
statement and monitoring policy.
Dresdner Kleinwort is the trading name of the investment banking division of
Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort
Limited, Dresdner Kleinwort Securities Limited and their affiliated or
associated companies. Dresdner Bank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC007638,
place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the
German Federal Financial Supervisory Authority and by the Financial Services
Authority ('FSA') and regulated by the FSA for the conduct of designated
business in the UK. Dresdner Kleinwort Limited is a company incorporated in
England (registered no. 551334, registered office 30 Gresham Street, London
EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort
Securities Limited is a company incorporated in England (registered no.
1767419, registered office 30 Gresham Street, London EC2V 7PG), and is
authorised and regulated by the FSA.
Re: Excluding certain modules in a profile
Good day,
Not really sure what's happening. But you may want to file a jira issue for
that :-)
Cheers,
Franz
takai wrote:
Exactly.
franz see wrote:
Good day,
Are you saying that you added plugin dependencies for your antrun, and
your antrun cannot see it if it's in the profile-added module?
Cheers,
Franz
takai wrote:
Hi Franz,
The profile-added module runs the integration tests. Usecase: Developer
usually wants to just build the project - not run the entire integration
test suite which takes a while. An explicit -P integration call is
needed to run them. The real reason i want to add profile specific
modules is to avoid cleaning them by default.
The profile-added module contains the antrun plugin. The plugin
dependencies are not accessible to the ant build files (and therefore, i
suppose, to the plugin).
Cheers,
Daniel
franz see wrote:
Good day,
Which project does not include its dependencies...the aggregating or
the profile-added module? ..And which classpath?
Cheers,
Franz
takai wrote:
This seems to work. However i found that putting modules in the
profile somehow breaks the dependency mechanism.
I use the antrun plugin in an integration module. When i execute with
a regular pom or just inside the integration module everything works
fine.
Once i use the aforementioned module by profile approch the plugin
does not include dependencies in the classpath.
Using Maven 2.0.6.
File an issue?
Daniel
Jonathan Anstey wrote:
Try this to set up a default profile:
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
modules
...
/modules
/profile
Cheers,
Jon
Wayne Fay wrote:
I don't believe this is possible. Instead, I think you would need to
set it up as follows:
parent/pom.xml
modules/
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
profile
iddefault/id
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
And then use some activation magic to decide when to turn on default
etc.
No guarantee this would work as I've never done it myself, but I'm
fairly certain your other proposed solution will not work, so give
this a try.
Wayne
On 2/7/07, Balasubramanian, Ravi Shankar [EMAIL PROTECTED]
wrote:
Hi,
I am using maven 2.0.4 and I want to be excluding certain modules
while
building my project in a certain profile. Following is the
scenarion:
This is how my main pom looks like:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdcom.informatica.metadatarepository.qa/groupId
artifactIdmetamodels/artifactId
packagingpom/packaging
name${artifactId}/name
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
With the above pom, when I build the project activating the profile
cpp-qa, all the four modules are being built. I want to be
building
only module3 and module4 using certain configurations in this
profile.
Is there a way by which I can accomplish this in maven2?
Thanks for any help,
Ravi.
Tough times never last, but tough men do...
-
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]
--
View this message in context:
http://www.nabble.com/Excluding-certain-modules-in-a-profile-tf3185303s177.html#a9976266
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Analyze dependency tree without compiling
Hi all, Is it possible to analyze the dependency tree without compiling? Compiling gives a build failure, so the following commands don't work: mvn dependency:analyze mvn site -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Analyze dependency tree without compiling
On 4/13/07, Geoffrey De Smet [EMAIL PROTECTED] wrote: Hi all, Is it possible to analyze the dependency tree without compiling? Compiling gives a build failure, so the following commands don't work: mvn dependency:analyze mvn site I think the analyzer uses the class files to identify unused dependencies... It is build on top of asm (http://asm.objectweb.org/). http://maven.apache.org/plugins/maven-dependency-plugin/dependencies.html Not sure how this works with reflection though... But i guess the relevant libs should be marked as runtime anyway. Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Analyze dependency tree without compiling
Good day, Try project-info-reports:dependencies to generate the dependency report ( which you can only see from mvn site ). The generated report would be in target\site\dependencies.html Cheers, Franz Jerome Lacoste-2 wrote: On 4/13/07, Geoffrey De Smet [EMAIL PROTECTED] wrote: Hi all, Is it possible to analyze the dependency tree without compiling? Compiling gives a build failure, so the following commands don't work: mvn dependency:analyze mvn site I think the analyzer uses the class files to identify unused dependencies... It is build on top of asm (http://asm.objectweb.org/). http://maven.apache.org/plugins/maven-dependency-plugin/dependencies.html Not sure how this works with reflection though... But i guess the relevant libs should be marked as runtime anyway. Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Analyze-dependency-tree-without-compiling-tf3570832s177.html#a9976509 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Excluding certain modules in a profile
http://jira.codehaus.org/browse/MNG-2946
Thanks for validating this.
franz see wrote:
Good day,
Not really sure what's happening. But you may want to file a jira issue
for that :-)
Cheers,
Franz
takai wrote:
Exactly.
franz see wrote:
Good day,
Are you saying that you added plugin dependencies for your antrun, and
your antrun cannot see it if it's in the profile-added module?
Cheers,
Franz
takai wrote:
Hi Franz,
The profile-added module runs the integration tests. Usecase: Developer
usually wants to just build the project - not run the entire
integration test suite which takes a while. An explicit -P
integration call is needed to run them. The real reason i want to add
profile specific modules is to avoid cleaning them by default.
The profile-added module contains the antrun plugin. The plugin
dependencies are not accessible to the ant build files (and therefore,
i suppose, to the plugin).
Cheers,
Daniel
franz see wrote:
Good day,
Which project does not include its dependencies...the aggregating or
the profile-added module? ..And which classpath?
Cheers,
Franz
takai wrote:
This seems to work. However i found that putting modules in the
profile somehow breaks the dependency mechanism.
I use the antrun plugin in an integration module. When i execute with
a regular pom or just inside the integration module everything works
fine.
Once i use the aforementioned module by profile approch the plugin
does not include dependencies in the classpath.
Using Maven 2.0.6.
File an issue?
Daniel
Jonathan Anstey wrote:
Try this to set up a default profile:
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
modules
...
/modules
/profile
Cheers,
Jon
Wayne Fay wrote:
I don't believe this is possible. Instead, I think you would need
to
set it up as follows:
parent/pom.xml
modules/
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
profile
iddefault/id
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
And then use some activation magic to decide when to turn on
default etc.
No guarantee this would work as I've never done it myself, but I'm
fairly certain your other proposed solution will not work, so give
this a try.
Wayne
On 2/7/07, Balasubramanian, Ravi Shankar [EMAIL PROTECTED]
wrote:
Hi,
I am using maven 2.0.4 and I want to be excluding certain modules
while
building my project in a certain profile. Following is the
scenarion:
This is how my main pom looks like:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdcom.informatica.metadatarepository.qa/groupId
artifactIdmetamodels/artifactId
packagingpom/packaging
name${artifactId}/name
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
With the above pom, when I build the project activating the
profile
cpp-qa, all the four modules are being built. I want to be
building
only module3 and module4 using certain configurations in this
profile.
Is there a way by which I can accomplish this in maven2?
Thanks for any help,
Ravi.
Tough times never last, but tough men do...
-
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]
--
View this message in context:
http://www.nabble.com/Excluding-certain-modules-in-a-profile-tf3185303s177.html#a9976884
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven users in the industry
-Original Message- From: Pilgrim, Peter Sent: 11 April 2007 17:51 To: [EMAIL PROTECTED] Subject: RE: Maven users in the industry UBS Investment Bank within Post Trade Services (Maven 2.0) Unsubscribing myself. Finishing UBS contract. Upwards and onwards to find the next one! -- Peter Pilgrim UBS Investment Bank, Client Portal Dev LDN, Triton Court, 14 Finsbury Square, London, EC2A 1PD United Kingdom ( +44 (0)207 56 75692 ) :: Java EE Spring 2.0 Hibernate 3.2 Development :: Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mails are not encrypted and cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for any errors or omissions in the contents of this message which arise as a result of e-mail transmission. If verification is required please request a hard-copy version. This message is provided for informational purposes and should not be construed as a solicitation or offer to buy or sell any securities or related financial instruments. UBS Limited is a company registered in England Wales under company number 2035362, whose registered office is at 1 Finsbury Avenue, London, EC2M 2PP, United Kingdom. UBS AG (London Branch) is registered as a branch of a foreign company under number BR004507, whose registered office is at 1 Finsbury Avenue, London, EC2M 2PP, United Kingdom. UBS Clearing and Execution Services Limited is a company registered in England Wales under company number 03123037, whose registered office is at 1 Finsbury Avenue, London, EC2M 2PP, United Kingdom. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
relase plugin, multimodule-project and internal depenencies
Hi everyone,
It seems that I've got some missunderstanding of the maven2 mechanisms,
and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
root
|--- pom.xml*1
|--- module1
| |--- pom.xml *2
|--- module2
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for the
submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom, no
version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install in
the root folder, and due to the ordering of the modules in the parent
pom maven builds one module after the other, installs it in the local
repository, and uses it to build the other modules. Everything's fine
until here.
Now when I use the maven-release plugin and execute release:prepare, the
plugin changes the version numbers from say 1.12-SNAPSHOT to 1.12
and then executes the build, but only up to the integration-test
lifecycle phase. module1 in my example builds successfully, but the
build of module2 fails since module1-1.12.jar is obviously not
available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
Re: relase plugin, multimodule-project and internal depenencies
Hi,
Nothing wrong, I have a similar problem myself. If you add the release-plugin
to your POM and tell it to run the targets 'clean install' instead of 'clean
intergration-test', everything will work fine.
On Friday 13 April 2007 13:46, Bleier Thomas wrote:
Hi everyone,
It seems that I've got some missunderstanding of the maven2 mechanisms,
and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
root
|--- pom.xml*1
|
|--- module1
|
| |--- pom.xml *2
|
|--- module2
|
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for the
submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom, no
version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install in
the root folder, and due to the ordering of the modules in the parent
pom maven builds one module after the other, installs it in the local
repository, and uses it to build the other modules. Everything's fine
until here.
Now when I use the maven-release plugin and execute release:prepare, the
plugin changes the version numbers from say 1.12-SNAPSHOT to 1.12
and then executes the build, but only up to the integration-test
lifecycle phase. module1 in my example builds successfully, but the
build of module2 fails since module1-1.12.jar is obviously not
available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: relase plugin, multimodule-project and internal depenencies
You have to change the dependency in Module 2 from version 1.12-Snapshot
to 1.12.
Doug Tanner
-Original Message-
From: Bleier Thomas [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 7:46 AM
To: [EMAIL PROTECTED]
Subject: relase plugin, multimodule-project and internal depenencies
Hi everyone,
It seems that I've got some missunderstanding of the maven2
mechanisms,
and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
root
|--- pom.xml*1
|--- module1
| |--- pom.xml *2
|--- module2
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for
the
submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom, no
version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install
in
the root folder, and due to the ordering of the modules in the parent
pom maven builds one module after the other, installs it in the local
repository, and uses it to build the other modules. Everything's fine
until here.
Now when I use the maven-release plugin and execute release:prepare,
the
plugin changes the version numbers from say 1.12-SNAPSHOT to 1.12
and then executes the build, but only up to the integration-test
lifecycle phase. module1 in my example builds successfully, but the
build of module2 fails since module1-1.12.jar is obviously not
available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
BENEFITFOCUS.COM CONFIDENTIALITY NOTICE: This electronic message is intended
only for the individual or entity to which it is addressed and may contain
information that is confidential and protected by law. Unauthorized review,
use, disclosure, or dissemination of this communication or its contents in any
way is prohibited and may be unlawful. If you are not the intended recipient or
a person responsible for delivering this message to an intended recipient,
please notify the original sender immediately by e-mail or telephone, return
the original message to the original sender or to [EMAIL PROTECTED], and
destroy all copies or derivations of the original message. Thank you.
(BFeComNote Rev. 08/01/2005)
***
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[M2][maven-ejb-plugin] dependencies for generated client
Hey all, I do not completely agree with some of the principles used in this [maven-ejb-plugin] plugin when generating the client-jar for the EJB. Currently when you tell Maven to create a client jar, it uses the same dependencies as defined for the EJB. I think this is fundamentally wrong. Clients for a service (EJB) should have as few dependencies as possible. If inside the implementation of the EJB one uses Spring, or Hibernate, or commons-logging, clients should not be aware of that. I think that typically the dependencies on the client are a subset of those of the service. Client dependencies should be kept minimal. So imagine an ideal solution: - while generating the client, Maven inspects the signature of the services offered by the EJB and adds all classes/libraries needed (I think some ant task did this using the BCEL lib). - additional classes/libs can be explicitly added. Would it be possible to implement this? Another option is to let the developer decide which libs/classes must be added as dependency for the client jar. Both options seem (to me) more usable than the current solution. But maybe I'm seeing things too simple? I'm looking forward to have some reactions on this. Currently we're having a problem where a project uses several client-ejb jar. All transitive dependencies are package with the project. The project now contains more than 100MB, due to all transitive dependencies. What are the options to solve this? Create a client jar file separately with the maven-jar-plugin ?
[M2] Native plugin and multi-platform C++ projects How-To
Hi all, I am trying to migrate a C++ project to Maven2, but I have troubles to find out the right way to go. The current project uses a Makefile for several Unix systems (custom, no automake used), and separate Visual Studio project files for Windows. The artifact to generate is a shared library. AFAICS, I have several options for the general project layout: - Use the antrun plugin to build the project using the already existent Makefile and VS project files. Surely, this is the fastest to implement and the best for a quick prototype, but I would prefer to keep a single build system. Right now, I see it more like a patch than a final solution. - Use the native plugin and, making extensive use of profiles, manage to get a single project that can be built in any platform. I am not sure that it would be feasible to make the packaging and classifier of the produced artifact reflect the library extension and the target OS/platform in the file name. - Using again the native plugin, create a multi-module project. The parent would contain the C++ source code, while each child module would be devoted to create a single OS/platform specific artifact. Which one do you think is the best? Is there any other way to do this? By the way, can native be used for C#, VB, Delphi, etc.? There are more issues related to the same migration, but I think it is better to go step by step ;-) Please, any comment or advice would be very welcome! Cheers, -- --- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17 Research Coordinator 07121 Palma de Mallorca Baleares - Spain http://www.gridsystems.com/ --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: relase plugin, multimodule-project and internal depenencies
This shouldn't be the correct way to do this. If I'm releasing my projects,
I want to deploy the (only) release build of the projects, not install one
build and then deploy another build. This is especially true if a company
official build server will be doing the deploy--if I've done an install as
part of the release process, my local repository will already have that version
and won't download the official deployed version. Hopefully there is no real
difference, but the point is to eliminate any risk for this.
..David..
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 5:56 AM
To: Maven Users List
Subject: Re: relase plugin, multimodule-project and internal depenencies
Hi,
Nothing wrong, I have a similar problem myself. If you add the release-plugin
to your POM and tell it to run the targets 'clean install' instead of 'clean
intergration-test', everything will work fine.
On Friday 13 April 2007 13:46, Bleier Thomas wrote:
Hi everyone,
It seems that I've got some missunderstanding of the maven2
mechanisms, and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
root
|--- pom.xml*1
|
|--- module1
|
| |--- pom.xml *2
|
|--- module2
|
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for
the submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom, no
version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install
in the root folder, and due to the ordering of the modules in the
parent pom maven builds one module after the other, installs it in the
local repository, and uses it to build the other modules. Everything's
fine until here.
Now when I use the maven-release plugin and execute release:prepare,
the plugin changes the version numbers from say 1.12-SNAPSHOT to 1.12
and then executes the build, but only up to the integration-test
lifecycle phase. module1 in my example builds successfully, but the
build of module2 fails since module1-1.12.jar is obviously not
available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7
A-1010 Wien FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
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]
How to use/define custom jar file in dependency
I am getting compilation error when I am using custom jar file, for eg: My web project is depend on domainmodel.jar how can I use this ? And also how can I do also compile, build this jar then reffer this jar and compile and build my web applications. As this jar is used by multiple webapps. Thanks, Vinit N -- View this message in context: http://www.nabble.com/How-to-use-define-custom-jar-file-in-dependency-tf3571737s177.html#a9979316 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error in compiling Struts code...
Thanks Wayne.. I got the problem...now it fine...thanks for reply... Wayne Fay wrote: Looks like you're missing some dependencies you need to compile your code: package javax.servlet.http does not exist package org.apache.struts.action does not exist package javax.servlet.jsp does not exist package javax.servlet.jsp.tagext does not exist Add dependencies to your pom.xml to satisfy these errors and I'd expect it will compile successfully. Wayne On 4/12/07, Vinit Nayak [EMAIL PROTECTED] wrote: Hi, I am getting following compilation error while compiling my code: [INFO] [compiler:compile] [INFO] Compiling 63 source files to C:\weblogic\dlymagsoutput [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Compilation failure C:\weblogic\source\dailymagazines\src\org\sae\struts\action\DailyMagNoti ficationAction.java:[12,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\DailyMagNoti ficationAction.java:[13,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\taghandler\UploadTa g.java:[7,25] package javax.servlet.jsp does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\taghandler\UploadTa g.java:[8,25] package javax.servlet.jsp does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\taghandler\UploadTa g.java:[9,32] package javax.servlet.jsp.tagext does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\taghandler\UploadTa g.java:[19,31] cannot resolve symbol symbol : class TagSupport location: class org.sae.struts.taghandler.UploadTag C:\weblogic\source\dailymagazines\src\org\sae\struts\taghandler\UploadTa g.java:[157,39] cannot resolve symbol symbol : class JspTagException location: class org.sae.struts.taghandler.UploadTag C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[5,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[6,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[9,32] package org.apache.struts.action does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[10,32] package org.apache.struts.action does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[11,32] package org.apache.struts.action does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[14,28] package sae.ebeans.adSession does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[15,28] package sae.ebeans.adSession does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[16,17] package sae.utils does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[17,21] package sae.utils.env does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[19,59] package org.apache.struts.action does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[23,37] cannot resolve symbol symbol : class ActionMapping location: class org.sae.struts.action.AdSetupAction C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[23,60] cannot resolve symbol symbol : class ActionForm location: class org.sae.struts.action.AdSetupAction C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[24,12] cannot resolve symbol symbol : class HttpServletRequest location: class org.sae.struts.action.AdSetupAction C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[24,40] cannot resolve symbol symbol : class HttpServletResponse location: class org.sae.struts.action.AdSetupAction C:\weblogic\source\dailymagazines\src\org\sae\struts\action\AdSetupActio n.java:[23,15] cannot resolve symbol symbol : class ActionForward location: class org.sae.struts.action.AdSetupAction C:\weblogic\source\dailymagazines\src\org\sae\struts\action\ImagesAction .java:[20,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\ImagesAction .java:[21,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\ImagesAction .java:[22,26] package javax.servlet.http does not exist C:\weblogic\source\dailymagazines\src\org\sae\struts\action\ImagesAction .java:[25,32] package org.apache.struts.action does not exist
Re: How to use/define custom jar file in dependency
You may try adding this to your pom.xml dependencies ... dependency groupIdmyjar/groupId artifactIdmyjar/artifactId version10.1.2/version scopesystem/scope systemPathC:/myproject/lib/domainmodel.jar/systemPath /dependency ... You must specify the absolute path. I don't know why, but I would like to know ... if someone would enlight me :) Cheers, Cristian. Vinit N wrote: I am getting compilation error when I am using custom jar file, for eg: My web project is depend on domainmodel.jar how can I use this ? And also how can I do also compile, build this jar then reffer this jar and compile and build my web applications. As this jar is used by multiple webapps. Thanks, Vinit N - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: relase plugin, multimodule-project and internal depenencies
I think it should be. Anyway, I've noticed that some packaging-types force me
to do this. I however do not really find this a problem, since we have a
build-server (like you suggested), which cleans its repository (read: deletes
the local repo) before releasing. That way we always have the latest deployed
version(s) of the projects and plug-ins we use.
Packaging-types that have this problem include EJB, WAR and EAR. JARs are no
problem (for me), and the others are more or less logical, since they package
the referenced JARs, so these MUST exist.
I believe it has to do with the order a release is done - first maven checks
if everything builds fine, and deploying is done ONLY if things work.
This means that the release tries to find the newly released project (for the
problematic packaging-types above) to really create the package. If these
packages were build correctly, they are then uploaded to the
deployment-server, not before.
Thinking about it while typing this mail, I believe this is the correct way.
There really is no other way to do this if one of the above packaging-types
is used. Besides, on a 'clean' release-server no problems should occur...
On Friday 13 April 2007 15:46, David Jackman wrote:
This shouldn't be the correct way to do this. If I'm releasing my
projects, I want to deploy the (only) release build of the projects, not
install one build and then deploy another build. This is especially true
if a company official build server will be doing the deploy--if I've done
an install as part of the release process, my local repository will already
have that version and won't download the official deployed version.
Hopefully there is no real difference, but the point is to eliminate any
risk for this.
..David..
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 5:56 AM
To: Maven Users List
Subject: Re: relase plugin, multimodule-project and internal depenencies
Hi,
Nothing wrong, I have a similar problem myself. If you add the
release-plugin to your POM and tell it to run the targets 'clean install'
instead of 'clean intergration-test', everything will work fine.
On Friday 13 April 2007 13:46, Bleier Thomas wrote:
Hi everyone,
It seems that I've got some missunderstanding of the maven2
mechanisms, and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of them
depend on others. To clarify that, I'll try to sketch our project
structure:
root
|--- pom.xml*1
|
|--- module1
|
| |--- pom.xml *2
|
|--- module2
|
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for
the submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom, no
version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install
in the root folder, and due to the ordering of the modules in the
parent pom maven builds one module after the other, installs it in the
local repository, and uses it to build the other modules. Everything's
fine until here.
Now when I use the maven-release plugin and execute release:prepare,
the plugin changes the version numbers from say 1.12-SNAPSHOT to 1.12
and then executes the build, but only up to the integration-test
lifecycle phase. module1 in my example builds successfully, but the
build of module2 fails since module1-1.12.jar is obviously not
available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7
A-1010 Wien FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
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]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe,
Re: How to use/define custom jar file in dependency
You should deploy this JAR to your repository. Look at http://maven.apache.org/guides/mini/guide-3rd-party-jars-remote.html for info on how to do this. When it's in the repo, you can just add a dependency as you would to any other JAR. Of course, if the JAR is already a Maven-project, you don't need to use the above link, but just build that project -- just make sure you tell Maven to 'install' as well! On Friday 13 April 2007 15:48, Vinit N wrote: I am getting compilation error when I am using custom jar file, for eg: My web project is depend on domainmodel.jar how can I use this ? And also how can I do also compile, build this jar then reffer this jar and compile and build my web applications. As this jar is used by multiple webapps. Thanks, Vinit N -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to use/define custom jar file in dependency
This would work, but only on YOUR machine... In team-projects this will cause
lots of problems. The best solution would be to deploy it to the repository
(like I said in my previous post).
Or, in case of some special JARs (in my case GlassFish and JBoss), you could
define a variable '${JAR_HOME}/domainmodel.jar', so that all other developers
can tell their Maven their locations with 'mvn -DJAR_HOME=/path/to/dir'
On Friday 13 April 2007 16:05, Cristian D. Romanescu wrote:
You may try adding this to your pom.xml
dependencies
...
dependency
groupIdmyjar/groupId
artifactIdmyjar/artifactId
version10.1.2/version
scopesystem/scope
systemPathC:/myproject/lib/domainmodel.jar/systemPath
/dependency
...
You must specify the absolute path. I don't know why, but I would like to
know ... if someone would enlight me :)
Cheers,
Cristian.
Vinit N wrote:
I am getting compilation error when I am using custom jar file,
for eg:
My web project is depend on domainmodel.jar how can I use this ?
And also how can I do also compile, build this jar then reffer this jar
and compile and build my web applications.
As this jar is used by multiple webapps.
Thanks,
Vinit N
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[M2] deploy-file with classifier not working
I'm trying to deploy a 3rd party source jar, by setting the classifier when I use deploy:deploy-file, but it is being deployed without the classifier. It appears that the classifier is being ignored entirely. Probably I am just missing something small and stupid. Anyone see a problem: $M2_HOME/bin/mvn deploy:deploy-file -X -DgroupId=com.fja.pdfs \ -DartifactId=pdfs \ -Dversion=$PDFS_VER \ -Dpackaging=jar \ -Dfile=lib/pdfsSrc.jar \ -Dclassifier=sources \ -DgeneratePom=false \ -DrepositoryId=fja-internal-ftp \ -Durl=ftp://myserver.global.fjh.com; ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.1:deploy-file' -- [DEBUG] (f) artifactId = pdfs [DEBUG] (f) file = d:\projects\PDFSProjects\current\releases\3.2.1\lib\pdfsSrc.jar [DEBUG] (f) generatePom = false [DEBUG] (f) groupId = com.fja.pdfs [DEBUG] (s) localRepository = [local] - file://D:\Profiles\ME\.m2\repository [DEBUG] (f) packaging = jar [DEBUG] (f) repositoryId = fja-internal-ftp [DEBUG] (f) url = ftp://myserver.global.fjh.com [DEBUG] (f) version = 3.2.1.52 [DEBUG] -- end configuration -- ... Thanks, -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] deploy-file with classifier not working
I believe that sources have their own packaging-type... And classifier is indeed unused iirc... On Friday 13 April 2007 16:19, Siegmann Daniel, NY wrote: I'm trying to deploy a 3rd party source jar, by setting the classifier when I use deploy:deploy-file, but it is being deployed without the classifier. It appears that the classifier is being ignored entirely. Probably I am just missing something small and stupid. Anyone see a problem: $M2_HOME/bin/mvn deploy:deploy-file -X -DgroupId=com.fja.pdfs \ -DartifactId=pdfs \ -Dversion=$PDFS_VER \ -Dpackaging=jar \ -Dfile=lib/pdfsSrc.jar \ -Dclassifier=sources \ -DgeneratePom=false \ -DrepositoryId=fja-internal-ftp \ -Durl=ftp://myserver.global.fjh.com; ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.1:deploy-file' -- [DEBUG] (f) artifactId = pdfs [DEBUG] (f) file = d:\projects\PDFSProjects\current\releases\3.2.1\lib\pdfsSrc.jar [DEBUG] (f) generatePom = false [DEBUG] (f) groupId = com.fja.pdfs [DEBUG] (s) localRepository = [local] - file://D:\Profiles\ME\.m2\repository [DEBUG] (f) packaging = jar [DEBUG] (f) repositoryId = fja-internal-ftp [DEBUG] (f) url = ftp://myserver.global.fjh.com [DEBUG] (f) version = 3.2.1.52 [DEBUG] -- end configuration -- ... Thanks, -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] deploy-file with classifier not working
Forgot to mention the most important thing: try packaging=java-source or java-sources... I believe it was something like that. On Friday 13 April 2007 16:19, Siegmann Daniel, NY wrote: I'm trying to deploy a 3rd party source jar, by setting the classifier when I use deploy:deploy-file, but it is being deployed without the classifier. It appears that the classifier is being ignored entirely. Probably I am just missing something small and stupid. Anyone see a problem: $M2_HOME/bin/mvn deploy:deploy-file -X -DgroupId=com.fja.pdfs \ -DartifactId=pdfs \ -Dversion=$PDFS_VER \ -Dpackaging=jar \ -Dfile=lib/pdfsSrc.jar \ -Dclassifier=sources \ -DgeneratePom=false \ -DrepositoryId=fja-internal-ftp \ -Durl=ftp://myserver.global.fjh.com; ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.1:deploy-file' -- [DEBUG] (f) artifactId = pdfs [DEBUG] (f) file = d:\projects\PDFSProjects\current\releases\3.2.1\lib\pdfsSrc.jar [DEBUG] (f) generatePom = false [DEBUG] (f) groupId = com.fja.pdfs [DEBUG] (s) localRepository = [local] - file://D:\Profiles\ME\.m2\repository [DEBUG] (f) packaging = jar [DEBUG] (f) repositoryId = fja-internal-ftp [DEBUG] (f) url = ftp://myserver.global.fjh.com [DEBUG] (f) version = 3.2.1.52 [DEBUG] -- end configuration -- ... Thanks, -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: relase plugin, multimodule-project and internal depenencies
Read my email again. It's not the build machine that gets the wrong thing.
It's the machine you used when you did the release:prepare. Because you did an
install on that machine as part of the release:prepare, that machine won't
download the real deployed version of the released project. So your steps for
releasing a project have to include cleaning your own local repository after
release:prepare. I'd rather not.
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 8:05 AM
To: Maven Users List
Subject: Re: relase plugin, multimodule-project and internal depenencies
I think it should be. Anyway, I've noticed that some packaging-types force me
to do this. I however do not really find this a problem, since we have a
build-server (like you suggested), which cleans its repository (read: deletes
the local repo) before releasing. That way we always have the latest deployed
version(s) of the projects and plug-ins we use.
Packaging-types that have this problem include EJB, WAR and EAR. JARs are no
problem (for me), and the others are more or less logical, since they package
the referenced JARs, so these MUST exist.
I believe it has to do with the order a release is done - first maven checks
if everything builds fine, and deploying is done ONLY if things work.
This means that the release tries to find the newly released project (for the
problematic packaging-types above) to really create the package. If these
packages were build correctly, they are then uploaded to the deployment-server,
not before.
Thinking about it while typing this mail, I believe this is the correct way.
There really is no other way to do this if one of the above packaging-types is
used. Besides, on a 'clean' release-server no problems should occur...
On Friday 13 April 2007 15:46, David Jackman wrote:
This shouldn't be the correct way to do this. If I'm releasing my
projects, I want to deploy the (only) release build of the projects,
not install one build and then deploy another build. This is
especially true if a company official build server will be doing the
deploy--if I've done an install as part of the release process, my
local repository will already have that version and won't download the
official deployed version.
Hopefully there is no real difference, but the point is to eliminate
any risk for this.
..David..
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 5:56 AM
To: Maven Users List
Subject: Re: relase plugin, multimodule-project and internal
depenencies
Hi,
Nothing wrong, I have a similar problem myself. If you add the
release-plugin to your POM and tell it to run the targets 'clean install'
instead of 'clean intergration-test', everything will work fine.
On Friday 13 April 2007 13:46, Bleier Thomas wrote:
Hi everyone,
It seems that I've got some missunderstanding of the maven2
mechanisms, and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of
them depend on others. To clarify that, I'll try to sketch our
project
structure:
root
|--- pom.xml*1
|
|--- module1
|
| |--- pom.xml *2
|
|--- module2
|
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for
the submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom,
no version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install
in the root folder, and due to the ordering of the modules in the
parent pom maven builds one module after the other, installs it in
the local repository, and uses it to build the other modules.
Everything's fine until here.
Now when I use the maven-release plugin and execute release:prepare,
the plugin changes the version numbers from say 1.12-SNAPSHOT to 1.12
and then executes the build, but only up to the integration-test
lifecycle phase. module1 in my example builds successfully, but
the build of module2 fails since module1-1.12.jar is obviously
not available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information Management
Austrian Research Centers GmbH - ARC
2444 Seibersdorf, Austria
Mobile: +43 (664) 8251279
E-Mail: [EMAIL PROTECTED] mailto:[EMAIL PROTECTED]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse
1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web:
Re: q on mvn dependency plugin
Hi Davis, There is source code for a plugin named maven-buildinfo-plugin, included with the free book Better Builds with Maven, that seems to do something like what you want (and then some). The source is in the Chapter5 .zip file[1]. Caveat coder: you may need to read Chapter 5 to understand how to use it (I myself have not attempted to do so). It looks like this plugin is also in the mojo sandbox at codehaus.org[2]. Steve [1] http://www.mergere.com/files/no.reg/code/Code_Ch05.zip [2] https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/maven-buildinfo-plugin/ Davis Ford wrote: hi, i know that mvn depenendency:resolve depdendency:build-classpath will dump a classpath list of all transitive/non-transitive jars. i was wondering if there was some other way, either with the dependency plugin, or with any other plugin, to generate the same output but in nicely formatted xml: /artifactId /groupId /version ? Thanks, Davis - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: relase plugin, multimodule-project and internal depenencies
True, but since I do the release:prepare on the release-machine -- which
deletes its local repo like I wrote -- I do get the released version on MY
local machine.
Besides, cleaning out your own local repo now and again doesn't hurt...
On Friday 13 April 2007 16:37, David Jackman wrote:
Read my email again. It's not the build machine that gets the wrong thing.
It's the machine you used when you did the release:prepare. Because you
did an install on that machine as part of the release:prepare, that machine
won't download the real deployed version of the released project. So your
steps for releasing a project have to include cleaning your own local
repository after release:prepare. I'd rather not.
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 8:05 AM
To: Maven Users List
Subject: Re: relase plugin, multimodule-project and internal depenencies
I think it should be. Anyway, I've noticed that some packaging-types force
me to do this. I however do not really find this a problem, since we have a
build-server (like you suggested), which cleans its repository (read:
deletes the local repo) before releasing. That way we always have the
latest deployed version(s) of the projects and plug-ins we use.
Packaging-types that have this problem include EJB, WAR and EAR. JARs are
no problem (for me), and the others are more or less logical, since they
package the referenced JARs, so these MUST exist.
I believe it has to do with the order a release is done - first maven
checks if everything builds fine, and deploying is done ONLY if things
work. This means that the release tries to find the newly released project
(for the problematic packaging-types above) to really create the package.
If these packages were build correctly, they are then uploaded to the
deployment-server, not before.
Thinking about it while typing this mail, I believe this is the correct
way. There really is no other way to do this if one of the above
packaging-types is used. Besides, on a 'clean' release-server no problems
should occur...
On Friday 13 April 2007 15:46, David Jackman wrote:
This shouldn't be the correct way to do this. If I'm releasing my
projects, I want to deploy the (only) release build of the projects,
not install one build and then deploy another build. This is
especially true if a company official build server will be doing the
deploy--if I've done an install as part of the release process, my
local repository will already have that version and won't download the
official deployed version. Hopefully there is no real difference, but the
point is to eliminate any risk for this.
..David..
-Original Message-
From: Roland Asmann [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 5:56 AM
To: Maven Users List
Subject: Re: relase plugin, multimodule-project and internal
depenencies
Hi,
Nothing wrong, I have a similar problem myself. If you add the
release-plugin to your POM and tell it to run the targets 'clean install'
instead of 'clean intergration-test', everything will work fine.
On Friday 13 April 2007 13:46, Bleier Thomas wrote:
Hi everyone,
It seems that I've got some missunderstanding of the maven2
mechanisms, and I would be thankfull if someone could help me...
We have a maven project that consists of several modules. Some of
them depend on others. To clarify that, I'll try to sketch our
project
structure:
root
|--- pom.xml*1
|
|--- module1
|
| |--- pom.xml *2
|
|--- module2
|
| |--- pom.xml - depends on module1
...
*1 - packaging: pom, lists submodules in modules,
version1.12-SNAPSHOT/version, dependencyManagement entries for
the submodules using version${project.version}/version
*2 - packaging jar or whatever, parent references the above pom,
no version tag for project itself (inherited), dependencies listed
without version tags (- dependencyManagement)
When building the project during development I executed mvn install
in the root folder, and due to the ordering of the modules in the
parent pom maven builds one module after the other, installs it in
the local repository, and uses it to build the other modules.
Everything's fine until here.
Now when I use the maven-release plugin and execute release:prepare,
the plugin changes the version numbers from say 1.12-SNAPSHOT to
1.12 and then executes the build, but only up to the
integration-test lifecycle phase. module1 in my example builds
successfully, but the build of module2 fails since module1-1.12.jar
is obviously not available in the local repository.
What is wrong with my setup?
Best regards,
__
/homas Bleier
--
Thomas Bleier, DI
Information
RE: [M2] deploy-file with classifier not working
Setting packaging to java-source did the trick, and classifier is indeed useless). Thanks. -Original Message- From: Roland Asmann [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 10:27 AM To: Maven Users List Subject: Re: [M2] deploy-file with classifier not working Forgot to mention the most important thing: try packaging=java-source or java-sources... I believe it was something like that. On Friday 13 April 2007 16:19, Siegmann Daniel, NY wrote: I'm trying to deploy a 3rd party source jar, by setting the classifier when I use deploy:deploy-file, but it is being deployed without the classifier. It appears that the classifier is being ignored entirely. Probably I am just missing something small and stupid. Anyone see a problem: $M2_HOME/bin/mvn deploy:deploy-file -X -DgroupId=com.fja.pdfs \ -DartifactId=pdfs \ -Dversion=$PDFS_VER \ -Dpackaging=jar \ -Dfile=lib/pdfsSrc.jar \ -Dclassifier=sources \ -DgeneratePom=false \ -DrepositoryId=fja-internal-ftp \ -Durl=ftp://myserver.global.fjh.com; ... [DEBUG] Configuring mojo 'org.apache.maven.plugins:maven-deploy-plugin:2.1:deploy-file' -- [DEBUG] (f) artifactId = pdfs [DEBUG] (f) file = d:\projects\PDFSProjects\current\releases\3.2.1\lib\pdfsSrc.jar [DEBUG] (f) generatePom = false [DEBUG] (f) groupId = com.fja.pdfs [DEBUG] (s) localRepository = [local] - file://D:\Profiles\ME\.m2\repository [DEBUG] (f) packaging = jar [DEBUG] (f) repositoryId = fja-internal-ftp [DEBUG] (f) url = ftp://myserver.global.fjh.com [DEBUG] (f) version = 3.2.1.52 [DEBUG] -- end configuration -- ... Thanks, -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - 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: [M2] Native plugin and multi-platform C++ projects How-To
On 4/13/07, Rodrigo Ruiz [EMAIL PROTECTED] wrote: Hi all, I am trying to migrate a C++ project to Maven2, but I have troubles to find out the right way to go. The current project uses a Makefile for several Unix systems (custom, no automake used), and separate Visual Studio project files for Windows. The artifact to generate is a shared library. AFAICS, I have several options for the general project layout: - Use the antrun plugin to build the project using the already existent Makefile and VS project files. Surely, this is the fastest to implement and the best for a quick prototype, but I would prefer to keep a single build system. Right now, I see it more like a patch than a final solution. - Use the native plugin and, making extensive use of profiles, manage to get a single project that can be built in any platform. I am not sure that it would be feasible to make the packaging and classifier of the produced artifact reflect the library extension and the target OS/platform in the file name. - Using again the native plugin, create a multi-module project. The parent would contain the C++ source code, while each child module would be devoted to create a single OS/platform specific artifact. I use this option. However you still need to use profile to do debug/release type artifacts Which one do you think is the best? Is there any other way to do this? By the way, can native be used for C#, VB, Delphi, etc.? no, for .net check out maven for net under apache incubator There are more issues related to the same migration, but I think it is better to go step by step ;-) Please, any comment or advice would be very welcome! Cheers, -- --- GRID SYSTEMS, S.A. Rodrigo Ruiz Parc Bit - Edificio 17 Research Coordinator 07121 Palma de Mallorca Baleares - Spain http://www.gridsystems.com/ --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build error with weblogic-maven-plugin
Answer, you may need more dependencies than me...:
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdweblogic-maven-plugin/artifactId
version2.9.0-SNAPSHOT/version
configuration
inputArtifactPath${basedir}/../../jar/broker.war/inputArtifactPath
verbosetrue/verbose
/configuration
executions
execution
phasepackage/phase
goals
goalappc/goal
/goals
/execution
/executions
dependencies
dependency
groupIdweblogic/groupId
artifactIdxbean/artifactId
version9.2.0/version
/dependency
dependency
groupIdweblogic/groupId
artifactIdwlxbean/artifactId
version9.2/version
/dependency
dependency
groupIdweblogic/groupId
artifactIdweblogic-container-binding/artifactId
version9.2/version
/dependency
dependency
groupIdcom.sun/groupId
artifactIdtools/artifactId
version1.5.0/version
/dependency
/dependencies
/plugin
Doug Tanner
-Original Message-
From: Doug Tanner [mailto:[EMAIL PROTECTED]
Sent: Friday, April 13, 2007 7:09 AM
To: Maven Users List
Subject: RE: Build error with weblogic-maven-plugin
I found this issue,
http://jira.codehaus.org/browse/MOJO-585?page=com.atlassian.jira.plugin.
system.issuetabpanels:all-tabpanel, while researching my problem. I
have tried placing a dependency on the ${WL_HOME}/server/lib/xbean.jar
in my pom, scoped as both system and provided (yes it is in my local
repo), but I am still receiving the same error. I even see it in my
output classpath during compilation, so how can it still be throwing a
NoClassDefFoundError? Has anyone had success implementing the
weblogic-maven-plugin, specifically version 2.9.0-SNAPSHOT?
Thanks,
Doug Tanner
-Original Message-
From: Scott Ryan [mailto:[EMAIL PROTECTED] On Behalf Of Scott Ryan
Sent: Thursday, April 12, 2007 10:03 AM
To: Maven Users List
Subject: Re: Build error with weblogic-maven-plugin
Yes that is a bug I am working on. I have some free days over then
next week or so and hope to have a solution. There are many jars
that need to be included in the APPC and I am trying to find a good
way to include them all without forcing you to load all the jars to
your repository. I am also testing with 10 as well. I hope to
have
some good news later this week. Let me know if there is anything
else you need.
Scott
On Apr 12, 2007, at 7:36 AM, Doug Tanner wrote:
I am using the 2.9.0-SNAPSHOT. After building my war, I wish to
precompile all my JSPs for faster response times. As I understand
it,
the weblogic-maven-plugin goal weblogic:appc is what I need to use
to do
this. However, I am getting a no class def found error. From the
output of my build I get the following lines, edited to remove
non-essential information:
[INFO] Weblogic APPC processing beginning for artifact
c:\projects\trunk\4x\webapps\broker/../../jar/broker.war
[INFO] Detailed Appc settings information AppcMojo[
basicClientJar = false
forceGeneration = true
keepGenerated = true
lineNumbers = false
inputArtifactPath =
c:\projects\trunk\4x\webapps\broker/../../jar/broker.war
outputArtifactPath = null
artifacts = [..., bf.webapps:common:jar:SNAPSHOT:compile,...]
project Packaging = war
verbose = true]
[INFO] Using Classpath
...;\maven\localRepository\bf\webapps\common\SNAPSHOT\common-
SNAPSHOT.ja
r;...
Created working directory:
c:\DOCUME~1\dtanner\LOCALS~1\Temp\appcgen_broker.war
[ERROR] Exception encountered during APPC processing
weblogic.utils.compiler.ToolFailureException:
com/bea/xml/XmlException
This error does not show which file is causing the problem, so I
ran
java weblogic.appc broker.war from the command line and received
this
error:
There are 1 nested errors:
weblogic.servlet.internal.dd.compliance.ComplianceException: The
class
bf.web.c
ommon.ApplicationContextListener referred by the descriptor
element
listener
is not found. Please ensure that it is present in the
Re: Excluding certain modules in a profile
Ok I found it - although i'm not quite sure where the issue belongs: mvn or
antrun plugin. Here it is:
Using a project with multiple pom's the antrun plugin dependencies of the
first plugin declaration encountered will be used for all subsequent antrun
executions.
Codehaus Jira Issue updated.
takai wrote:
http://jira.codehaus.org/browse/MNG-2946
Thanks for validating this.
franz see wrote:
Good day,
Not really sure what's happening. But you may want to file a jira issue
for that :-)
Cheers,
Franz
takai wrote:
Exactly.
franz see wrote:
Good day,
Are you saying that you added plugin dependencies for your antrun, and
your antrun cannot see it if it's in the profile-added module?
Cheers,
Franz
takai wrote:
Hi Franz,
The profile-added module runs the integration tests. Usecase:
Developer usually wants to just build the project - not run the entire
integration test suite which takes a while. An explicit -P
integration call is needed to run them. The real reason i want to add
profile specific modules is to avoid cleaning them by default.
The profile-added module contains the antrun plugin. The plugin
dependencies are not accessible to the ant build files (and therefore,
i suppose, to the plugin).
Cheers,
Daniel
franz see wrote:
Good day,
Which project does not include its dependencies...the aggregating or
the profile-added module? ..And which classpath?
Cheers,
Franz
takai wrote:
This seems to work. However i found that putting modules in the
profile somehow breaks the dependency mechanism.
I use the antrun plugin in an integration module. When i execute
with a regular pom or just inside the integration module everything
works fine.
Once i use the aforementioned module by profile approch the plugin
does not include dependencies in the classpath.
Using Maven 2.0.6.
File an issue?
Daniel
Jonathan Anstey wrote:
Try this to set up a default profile:
profile
iddefault/id
activation
activeByDefaulttrue/activeByDefault
/activation
modules
...
/modules
/profile
Cheers,
Jon
Wayne Fay wrote:
I don't believe this is possible. Instead, I think you would need
to
set it up as follows:
parent/pom.xml
modules/
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
profile
iddefault/id
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
And then use some activation magic to decide when to turn on
default etc.
No guarantee this would work as I've never done it myself, but I'm
fairly certain your other proposed solution will not work, so give
this a try.
Wayne
On 2/7/07, Balasubramanian, Ravi Shankar
[EMAIL PROTECTED]
wrote:
Hi,
I am using maven 2.0.4 and I want to be excluding certain modules
while
building my project in a certain profile. Following is the
scenarion:
This is how my main pom looks like:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdcom.informatica.metadatarepository.qa/groupId
artifactIdmetamodels/artifactId
packagingpom/packaging
name${artifactId}/name
modules
modulemodule1/module
modulemodule2/module
modulemodule3/module
modulemodule4/module
/modules
profiles
profile
idcpp-qa/id
modules
modulemodule3/module
modulemodule4/module
/modules
/profile
/profiles
With the above pom, when I build the project activating the
profile
cpp-qa, all the four modules are being built. I want to be
building
only module3 and module4 using certain configurations in this
profile.
Is there a way by which I can accomplish this in maven2?
Thanks for any help,
Ravi.
Tough times never last, but tough men do...
-
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]
--
View this message in context:
http://www.nabble.com/Excluding-certain-modules-in-a-profile-tf3185303s177.html#a9982385
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[announce] TestNG 5.5 compatible surefire deployed / fixes for maven2 idea users
A new maven2 surefire release has been made which should let all TestNG maven2 users upgrade their version of TestNG to the latest 5.5 version. Major benefits to upgrade: -) You'll be able to use TestNG 5.5 with surefire finally. -) Some issues that have cropped up in the latest version of the idea TestNG plugin will also be fixed by upgrading your TestNG version to 5.5. This is a snapshot release so you'll need to use the version string 2.4-SNAPSHOT to get the right version. If you don't already have the apache maven snapshot repository configured for your project you'll need to add a section similar to the one below to your projects pom.xml file: pluginRepositories pluginRepository idapache.snapshots/id urlhttp://people.apache.org/repo/m2-snapshot-repository/url /pluginRepository /pluginRepositories -- View this message in context: http://www.nabble.com/-announce---TestNG-5.5-compatible-surefire-deployed---fixes-for-maven2-idea-users-tf3573007s177.html#a9983521 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 ear plugin doesn't pick up resources
Thanks for the suggestion. I did try it (using the default layout, omitting META-INF). Unfortunately, the xmi file still doesn't make it into the ear. Any other suggestions are appreciated. Johan Eltes Callista Enterprise AB Mobil: +46 (0)708-22 41 86 [EMAIL PROTECTED] http://www.callistaenterprise.se On 12 apr 2007, at 19.23, franz see wrote: Good day, If you're saying you have something like target/artifactName-version/classes/ibm-application-bnd.xmi Then I guess your resources are configured as follows project ... build ... resources ... resource directorysrc/main/resources/META-INF//directory /resource /resources /build /project If so, remove it or use the default project ... build ... resources ... resource directorysrc/main/resources//directory /resource /resources /build /project So that you will have something like target/artifactName-version/classes/META-INF/ibm-application- bnd.xmi But im just guessing here since I haven't tried that before with the ear plugin :-) Cheers, Franz Johan Eltes-3 wrote: I need to build an ear that - in addition to the generated application.xml - adds an existing vendor-specific deployment descriptor to the META-INF directory of the ear. I've tried the standard set-up: projectroot/scr/main/resources/META-INF/ibm-application-bnd.xmi When I invoke mvn install, the application.xml is generated and copied to ear/META-INF/ while ibm-application-bnd.xmi isn't. When looking into the target folder, I see the ibm-application-bnd.xmi has been copied into target/artifactName-version/classes/, but never made its way into the ear (or exploded ear). I see the same behavior on windows and Mac OS. Johan Eltes Callista Enterprise AB Mobil: +46 (0)708-22 41 86 [EMAIL PROTECTED] http://www.callistaenterprise.se - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Maven-2-ear- plugin-doesn%27t-pick-up-resources-tf3565230s177.html#a9964276 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: [M2] Native plugin and multi-platform C++ projects How-To
- Using again the native plugin, create a multi-module project. The parent would contain the C++ source code, while each child module would be devoted to create a single OS/platform specific artifact. I use this option. However you still need to use profile to do debug/release type artifacts I'm not so sure this is going to be as simple as that. C/C++ artifacts are not nearly as nice and tidy as java artifacts. A java artifact is essentially a single file, the .jar file. A C/C++ artifact will be at minimum two files: the library and the header file(s). In addition to that, you will likely need to know the exact compilation options used to compile the code and to link the shared object, so you can match these in your actual project build. The compilation will need to know about your local repository location and set multiple classpath type parameters to point to the right headers and libraries. It would be a great thing to have, but having spent a significant amount of time developing C/C++ build systems, I can guarantee some interesting challenges. I don't think that maven is quite up to it yet, but it is certainly an interesting approach to build avoidance. -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Native plugin and multi-platform C++ projects How-To
Hi Christian, you may have a look at http://java.freehep.org/freehep-nar-plugin it does quite a bit of what you suggest, though it is not perfect. Regards Mark Donszelmann On Apr 13, 2007, at 11:48 AM, Christian Goetze wrote: - Using again the native plugin, create a multi-module project. The parent would contain the C++ source code, while each child module would be devoted to create a single OS/platform specific artifact. I use this option. However you still need to use profile to do debug/release type artifacts I'm not so sure this is going to be as simple as that. C/C++ artifacts are not nearly as nice and tidy as java artifacts. A java artifact is essentially a single file, the .jar file. A C/C++ artifact will be at minimum two files: the library and the header file(s). In addition to that, you will likely need to know the exact compilation options used to compile the code and to link the shared object, so you can match these in your actual project build. The compilation will need to know about your local repository location and set multiple classpath type parameters to point to the right headers and libraries. It would be a great thing to have, but having spent a significant amount of time developing C/C++ build systems, I can guarantee some interesting challenges. I don't think that maven is quite up to it yet, but it is certainly an interesting approach to build avoidance. -- cg - 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]
[m2]HibernateDoclet example in XD2 for Maven2 please?
I have XD1 HibernateDoclet running fine, but want to switch to XD2 now. Can someone give me a working example please? -- --- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/djmick_dot_com http://www.myspace.com/sexybeotches http://www.thumpradio.com ---
How to set the Eclipse Java Compiler property JDK Compliance using the eclipse plugin?
I have set the compiler version for the maven-compiler-plugin, but that does not seem to affect the eclipse plugin. plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration verbosetrue/verbose forktrue/fork compilerVersion1.4/compilerVersion /configuration /plugin How do I set the Eclipse Java Compiler property JDK Compliance using the eclipse plugin? Paul Spencer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Native plugin and multi-platform C++ projects How-To
On 4/13/07, Mark Donszelmann [EMAIL PROTECTED] wrote: Hi Christian, you may have a look at http://java.freehep.org/freehep-nar-plugin it does quite a bit of what you suggest, though it is not perfect. That is pretty neat - but the devil is in the details :) For example, you'd want various variants of the same artifact (debug, optimized, profiled, quantified, instrumented in other ways) ... Not sure AOL cuts it. -- cg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release Notes generation
Hello, I'd like to generate release notes as a part of my mvn site command. If I annotate the site.xml with the following: menu name=Maven 2.0 item name=Introduction href=index.html/ item name=Download href=download.html/ item name=Release Notes href=release-notes.html / item name=General Information href=about.html/ item name=For Maven 1.0 Users href=maven1.html/ item name=Road Map href=roadmap.html / /menu It certainly creates the menu correctly. However, where is the plugin that will actually create the release-notes.html? I tried project-info-reports:scm but that looks like a dead-end to me as far as release note generation goes. Any help is appreciated. Thanks Pankaj -- View this message in context: http://www.nabble.com/Release-Notes-generation-tf3573934s177.html#a9986600 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release Notes generation
Pankaj Tandon wrote: Hello, I'd like to generate release notes as a part of my mvn site command. If I annotate the site.xml with the following: menu name=Maven 2.0 item name=Introduction href=index.html/ item name=Download href=download.html/ item name=Release Notes href=release-notes.html / item name=General Information href=about.html/ item name=For Maven 1.0 Users href=maven1.html/ item name=Road Map href=roadmap.html / /menu It certainly creates the menu correctly. However, where is the plugin that will actually create the release-notes.html? I tried project-info-reports:scm but that looks like a dead-end to me as far as release note generation goes. Any help is appreciated. Thanks Pankaj You might be looking for maven-changelog-plugin: http://maven.apache.org/plugins/maven-changelog-plugin/ -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Newbie Question: How do I represent my current Ant builds with Maven?
Hi, I've looked at Maven, read quite a bit of the documentation, and I can't figure out quite how to represent my current typical Ant build with Maven. Hopefully someone here can help me. I write a lot of console utilities in Java. These are comprised of the original code for the utility, that goes in a jar, 3rd-party libraries the utility uses, and ancillary files. Today, my typical folder structure for one of these projects looks like this: trunk (contains IDE project files, build.xml, build.properties) trunk/dist (contains content to be deployed 'as is') trunk/dist/doc (contains product documentation) trunk/dist/etc (configuration files read at runtime) trunk/dist/lib (holds 3rd-party jars) trunk/dist/... trunk/java (main source code) trunk/test (test source code) I have a 'deploy' target in my ant build that 1. copies the contents of 'dist' to a staging area for deployment 2. then compiles the java source into a jar 3. copies the jar to the staging area dist/lib directory 4. zips up the staging area The product is a zip file I can take to a client's site and deploy by unzipping and editing a few configuration files (which exist in their unedited state in trunk/dist/etc) and possibly batch files (which exist in their unedited state in trunk/dist). Everything I read about Maven suggests that there should be one build product per Maven project. Okay, I can see creating a project just for the jar holding the compiled Java code, but I can't quite wrap my head around what I'm 'supposed' to do here for the non-Java source files (the batch files, the configuration files, etc.) Switching to Maven becomes a non-starter because at a minimum I need to duplicate the functionality that is currently present in my ant builds. I would appreciate any guidance or advice you can offer. -- Danny MacMillan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Newbie Question: How do I represent my current Ant builds with Maven?
I'm far from the expert in dealing with this, but Maven's assembly plugin will do what you need: make your staging area, populate it, and zip it up in the end. We do something similar: I need to produce an autorun CD image: we build, with each jar having its own directory and maven pom, and then a packaging pom that just generates .war files, and then another packaging pom that generates a .zip of the CD image. (It's much more complex than that in sheer number of components, so I can't give you a sample directory structure easily, but I'm sure someone else will speak up :) Something like: Parent\pom.xml - placeholder, effectively jar1\pom.xml- generates your .jar war1\pom.xml- generates your .war dist1\pom.xml - generates an assembly putting all the pieces together dist1\dist.xml - descriptor (http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html) dist1\resources - flat files needed in your assembly, referred to in the pom Does that help? Dana Lacoste -Original Message- From: Danny MacMillan [mailto:[EMAIL PROTECTED] Sent: Friday, April 13, 2007 2:42 PM To: [EMAIL PROTECTED] Subject: Newbie Question: How do I represent my current Ant builds with Maven? Hi, I've looked at Maven, read quite a bit of the documentation, and I can't figure out quite how to represent my current typical Ant build with Maven. Hopefully someone here can help me. I write a lot of console utilities in Java. These are comprised of the original code for the utility, that goes in a jar, 3rd-party libraries the utility uses, and ancillary files. Today, my typical folder structure for one of these projects looks like this: trunk (contains IDE project files, build.xml, build.properties) trunk/dist (contains content to be deployed 'as is') trunk/dist/doc (contains product documentation) trunk/dist/etc (configuration files read at runtime) trunk/dist/lib (holds 3rd-party jars) trunk/dist/... trunk/java (main source code) trunk/test (test source code) I have a 'deploy' target in my ant build that 1. copies the contents of 'dist' to a staging area for deployment 2. then compiles the java source into a jar 3. copies the jar to the staging area dist/lib directory 4. zips up the staging area The product is a zip file I can take to a client's site and deploy by unzipping and editing a few configuration files (which exist in their unedited state in trunk/dist/etc) and possibly batch files (which exist in their unedited state in trunk/dist). Everything I read about Maven suggests that there should be one build product per Maven project. Okay, I can see creating a project just for the jar holding the compiled Java code, but I can't quite wrap my head around what I'm 'supposed' to do here for the non-Java source files (the batch files, the configuration files, etc.) Switching to Maven becomes a non-starter because at a minimum I need to duplicate the functionality that is currently present in my ant builds. I would appreciate any guidance or advice you can offer. -- Danny MacMillan - 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]
Parent-only plugin: is it possible?
Hello to all, I have been using Maven for two weeks now and I find it very good. It's an amazing piece of work, so congratulations on all the people that made it (and continue to make it) possible. I'm having an issue with it, which I'm sure somebody must have had, but I could not find anything on the past days. You see, I have a multi-project project called MyProject that has two subprojects: SubA and SubB. I just want to be able to execute a plugin at a given goal for MyProject, but prevent that goal from inheriting to SubA and SubB. I'm working with a custom plugin for testing purposes called SayHelloPlugin, that I have annotated with Inherit=false and also in MyProject's pom I have set the plugin to not inherit (via 'inherited'), but both SubA and SubB execute SayHelloPlugin nonetheles. Is there a way to do what I want? Can we restrict a plugin to the father of the projects? Thank you all for your support, Rodrigo Madera
Re: Newbie Question: How do I represent my current Ant builds with Maven?
Lacoste, Dana wrote: I'm far from the expert in dealing with this, but Maven's assembly plugin will do what you need: make your staging area, populate it, and zip it up in the end. We do something similar: I need to produce an autorun CD image: we build, with each jar having its own directory and maven pom, and then a packaging pom that just generates .war files, and then another packaging pom that generates a .zip of the CD image. (It's much more complex than that in sheer number of components, so I can't give you a sample directory structure easily, but I'm sure someone else will speak up :) Something like: Parent\pom.xml - placeholder, effectively jar1\pom.xml- generates your .jar war1\pom.xml- generates your .war dist1\pom.xml - generates an assembly putting all the pieces together dist1\dist.xml - descriptor (http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html) dist1\resources - flat files needed in your assembly, referred to in the pom Does that help? Dana Lacoste Yes, thanks. The assembly.html page you reference has certainly changed since the last time I looked at it. Last time I read it it seemed to suggest assemblies were for creating different 'views' of the same information (e.g. a source distribution, a binary distribution, etc.) Now it pretty plainly says it is the mechanism for doing exactly what I want :) The documentation on the page looks a lot more complete, too. I had considered the assembly plugin the last time I looked at this but I thought it would be counter to the design. It's good to have confirmation that this is indeed what others are using to achieve this goal. Would it be 'wrong' to merge the jar1 and dist1 folders (in your example) and their corresponding poms together? The rationale for this question is that the jar being produced is nothing on its own. It's not a library or a shared component of any kind. Its reason for being is to provide an executable, which by its nature requires the contents of the resources directory. My prejudicial response to what you outline is that it seems kind of complicated, but I'm open minded and happy to revise my opinion if I understand the value in the split. Thanks for your (astonishingly prompt) answer. -- Danny MacMillan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to get the active profiles in a maven plugin
Hi ! I have to write a Maven plugin and I need to access to the active profiles list. For example, if I execute the command line : mvn groupId:artifactId:goal -P profile-1,profile-2 ... I need to get in my java classes the list of active profiles (here profile-1 and profile-2) Does somebody know to do this or where I can found documentation about that ? Thanks ! Eric Lewandowski
