xdoclet dependency
Hello! I have a trouble with the 'xdoclet' dependency. I generate a web app using 'genapp': maven genapp The web application is generated and I launch: maven It tries to download the dependency and fails to build: ---begin--- Tag library requested that is not present: 'maven' in plugin: 'maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- How can I complete the build process? -- Best regards, Dmitry mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet dependency
--- Dmitry Ochnev [EMAIL PROTECTED] wrote: Hello! I have a trouble with the 'xdoclet' dependency. I generate a web app using 'genapp': maven genapp The web application is generated and I launch: maven It tries to download the dependency and fails to build: ---begin--- Tag library requested that is not present: 'maven' in plugin: 'maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- How can I complete the build process? Aparently xjavadoc-1.0.2 is not available on ibiblio. YOu can compile it yourself, and place into your local maven repository. regards, [ Konstantin Pribluda http://www.pribluda.de ] Still using XDoclet 1.x? XDoclet 2 is released and of production quality. check it out: http://xdoclet.codehaus.org __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] error maven.repo.local property in the ant file
Yup,
This is hardcoded in the plugin. File an improvement in Jira please.
Cheers,
Stéphane
-Original Message-
From: flyisland [mailto:[EMAIL PROTECTED]
Sent: Monday, August 22, 2005 11:17 AM
To: users@maven.apache.org
Subject: [m2] error maven.repo.local property in the ant file
Hi All,
i used m2 ant:ant to create a ant build file, and found the following
line:
property name=maven.repo.local value=${user.home}/.m2/repository/
but i had changed the localRepository to another directory with the
settings.xml file, so i have to correct it manually!
--
-
空中的一小块陆地
E-mail: [EMAIL PROTECTED]
Blog : http://donews.net/flyisland
RSS : http://feeds.feedburner.com/flyisland
-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re[4]: xdoclet dependency
Hello Jörg, Monday, August 22, 2005, 12:31:21 PM, you wrote: The group id for xjavadoc is xjavadoc and not xdoclet I have replaced the group id xdoclet with xjavadoc. Now I get the following: ---begin--- Attempting to download xjavadoc-1.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.2.jar. Attempting to download xdoclet-web-module-1.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xdoclet-web-module-1.2.jar. Attempting to download xdoclet-ejb-module-1.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xdoclet-ejb-module-1.2.jar. Attempting to download maven-xdoclet-plugin-1.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download maven-xdoclet-plugin-1.2.jar. The build cannot continue because of the following unsatisfied dependencies: xjavadoc-1.2.jar xdoclet-web-module-1.2.jar xdoclet-ejb-module-1.2.jar maven-xdoclet-plugin-1.2.jar ---end--- I also removed such lines urlhttp://xdoclet.sf.net//url from the 'project.xml' after Maven complained it was unable to download from xdoclet.sf.net. As we can see it did not help. What's wrong? -- Best regards, Dmitrymailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Should I run maven on the Free Software Foundation's GCJ or Sun's java platform
On Mon, Aug 22, 2005 at 12:01:41PM +0800, bw t wrote: Hi all, Should I run maven on the Free Software Foundation's GCJ or Sun's java platform ? No idea about GCJ but I know that Maven 1 and 2 runs just fine on several free platforms. It's been verified that Maven 1 runs on Kaffe by Kaffe developers and see my blog entry for other platforms. [1]: http://blogs.codehaus.org/people/trygvis/archives/001150_maven_2_runs_on_a_free_runtime.html -- Trygve signature.asc Description: Digital signature
Re[6]: xdoclet dependency
Hello Jörg, Monday, August 22, 2005, 1:58:33 PM, you wrote: Attempting to download xjavadoc-1.2.jar. This does not exist. Latest release is 1.1. You should stay with the original version (or at least check, that your used version of XDoclet is compliant with the one of xjavadoc). Why then xdoclet-1.2.jar, xdoclet-ejb-module-1.2.jar, xdoclet-web-module-1.2.jar and xdoclet-xdoclet-module-1.2.jar exist on my machine in my local repository (c:\my_home_dir\.maven\repository\xdoclet)? Use correct versions ;-) I tried to replace 1.2 with 1.1 for the XDoclet dependencies in the 'project.xml' but it did not changed the situation. For example: dependency groupIdxjavadoc/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency replaced 1.2 with 1.1 in all elements of the XDoclet dependencies section. Is there another way to set the version I need? (any reference to the documentation?) P.S.: I did not write project.xml manually, it was generated by the genapp plugin. -- Best regards, Dmitrymailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re[6]: xdoclet dependency
Hi Dmitry, only for the xjavadoc jar, you should use a groupId of xjavadoc and version 1.1 for the xdoclet jars groupId=xdoclet and version=1.2 so: dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency etcetera... Dennis On 8/22/05, Dmitry Ochnev [EMAIL PROTECTED] wrote: Hello Jörg, Monday, August 22, 2005, 1:58:33 PM, you wrote: Attempting to download xjavadoc-1.2.jar. This does not exist. Latest release is 1.1. It does exist: http://www.ibiblio.org/maven/xdoclet/jars/ You should stay with the original version (or at least check, that your used version of XDoclet is compliant with the one of xjavadoc). What do you mean the original version? -- Best regards, Dmitry mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Recursive multiproject site
The way I get this to work is to set maven.multiproject.site.goals to multiproject:site in the sandbox project and to site in the mid-level projects (newproj, otherproj). Actually, I have a goal in the sandbox project called gendocs which has multiproject:site as a prerequisite but I don't think it is really necessary. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Sunday, August 21, 2005 23:46 To: Maven Users List Subject: Re: Recursive multiproject site From: Wendy Smoak [EMAIL PROTECTED] I have a multiproject site that goes three levels deep: site core sandbox newproj newproj-core newproj-example otherproj otherproj-core otherproj-example I have maven.multiproject.site.goals=multiproject in project.properties at the 'sandbox' and 'newproj' and 'otherproj' levels. When I run 'maven multiproject:site' from the 'site' subproject, all of the documentation *is* getting created. It looks good at (for example) the sandbox/newproj/target/docs level-- the core and example subproject docs are there. No, they're not. The multiproject:clean goal isn't descending past the 'sandbox' level, so there were old files lying around. If I cd to sandbox and run multiproject:site, THEN I get all the files (and the next time through, they'll get copied up.) So the problem is with running 'multiproject:site' *from* the 'site' subdirectory. It makes sense that this would call 'site' for each of the sub-projects. Okay so far... but now anything I try, such as (in 'sandbox' maven.xml): postGoal name=site attainGoal name=multiproject:site/ /postGoal causes an endless loop. I imagine the solution is *very* simple and I've just been staring at it too long. How do I get multiproject:site to descend all the way down to the bottom of the structure, and copy everything up into site/target/docs? Thanks, -- Wendy Smoak - 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: Re[6]: xdoclet dependency
Dmitry Ochnev wrote on Monday, August 22, 2005 12:51 PM: Hello Jörg, Monday, August 22, 2005, 1:58:33 PM, you wrote: Attempting to download xjavadoc-1.2.jar. This does not exist. Latest release is 1.1. It does exist: http://www.ibiblio.org/maven/xdoclet/jars/ As long as you insist on a wrong group id I cannot help you! You should stay with the original version (or at least check, that your used version of XDoclet is compliant with the one of xjavadoc). What do you mean the original version? Version numbers of xjavadoc and xdoclet are not in sync. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Spring Testing
Marcelo, I haven't answered your follow-up for two reasons: 1) You ask something I've already answered ...as this may have a big performance impact... 2) I do not like your tone. You have posted twice Where are you guys? In response to that I can tell you that I was on a flight from the US to Europe coming back from a very BIG project. Thomas On 8/21/05, Marcelo Alcantara [EMAIL PROTECTED] wrote: Hi Jason, I know...I have gotten very nice answers here in this list and people really seem to be cool. Just saw the Carlos oness that I didn´t know and it is very nice work too. We have a bit of stress today, but talked offline and everything went well in the end. :) A lot of misunderstanding from everybody. The question about genapp templates was already answered. What I asked latelly was about how maven decides what to load first when running tests. Carlos suggested me to have spring appcontext files with the same name, that the test ones would override the main ones. But I just wanted to make sure and understand how maven deals with it. Thanks for the attention. Maralc -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Spring Testing
Hey Thomas, As I said before, I asked that in a good way (Where are you guys). And the confusion between me and Craig was already solved. I didn´t intend to be aggressive. (But I know I was when answering to Craig). Don´t get me bad. Cheers Marcelo On 8/22/05, Thomas Van de Velde [EMAIL PROTECTED] wrote: Marcelo, I haven't answered your follow-up for two reasons: 1) You ask something I've already answered ...as this may have a big performance impact... 2) I do not like your tone. You have posted twice Where are you guys? In response to that I can tell you that I was on a flight from the US to Europe coming back from a very BIG project. Thomas On 8/21/05, Marcelo Alcantara [EMAIL PROTECTED] wrote: Hi Jason, I know...I have gotten very nice answers here in this list and people really seem to be cool. Just saw the Carlos oness that I didn´t know and it is very nice work too. We have a bit of stress today, but talked offline and everything went well in the end. :) A lot of misunderstanding from everybody. The question about genapp templates was already answered. What I asked latelly was about how maven decides what to load first when running tests. Carlos suggested me to have spring appcontext files with the same name, that the test ones would override the main ones. But I just wanted to make sure and understand how maven deals with it. Thanks for the attention. Maralc -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven/Spring Testing
Case closed ;-) On 8/22/05, Marcelo Alcantara [EMAIL PROTECTED] wrote: Hey Thomas, As I said before, I asked that in a good way (Where are you guys). And the confusion between me and Craig was already solved. I didn´t intend to be aggressive. (But I know I was when answering to Craig). Don´t get me bad. Cheers Marcelo On 8/22/05, Thomas Van de Velde [EMAIL PROTECTED] wrote: Marcelo, I haven't answered your follow-up for two reasons: 1) You ask something I've already answered ...as this may have a big performance impact... 2) I do not like your tone. You have posted twice Where are you guys? In response to that I can tell you that I was on a flight from the US to Europe coming back from a very BIG project. Thomas On 8/21/05, Marcelo Alcantara [EMAIL PROTECTED] wrote: Hi Jason, I know...I have gotten very nice answers here in this list and people really seem to be cool. Just saw the Carlos oness that I didn´t know and it is very nice work too. We have a bit of stress today, but talked offline and everything went well in the end. :) A lot of misunderstanding from everybody. The question about genapp templates was already answered. What I asked latelly was about how maven decides what to load first when running tests. Carlos suggested me to have spring appcontext files with the same name, that the test ones would override the main ones. But I just wanted to make sure and understand how maven deals with it. Thanks for the attention. Maralc -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Marcelo Alcantara Senior Developer/Architect [EMAIL PROTECTED] +55 11 81968823 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re[8]: xdoclet dependency
Hello Jörg, Monday, August 22, 2005, 3:08:47 PM, you wrote: What do you mean the original version? Version numbers of xjavadoc and xdoclet are not in sync. How can I know the correct combinations of versions of xjavadoc and xdoclet? -- Best regards, Dmitrymailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re[8]: xdoclet dependency
Hello Dennis, Monday, August 22, 2005, 3:01:35 PM, you wrote: only for the xjavadoc jar, you should use a groupId of xjavadoc and version 1.1 for the xdoclet jars groupId=xdoclet and version=1.2 so: dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency etcetera... Dennis It became better but it is still not working. Here is the part of the project.xml: ---begin--- !-- XDoclet dependencies -- dependency idxdoclet/id version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version typeplugin/type /dependency ---end--- And here is the output: ---begin--- Tag library requested that is not present: 'maven' in plugin: 'maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest2\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- Where is the error? -- Best regards, Dmitrymailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
includes tools.jar as dependency
I have a project generates code. In my tests, I want to verify that this code compile properly. I would like to use the tools.jar of the JDK in my tests to do that. How should I set the dependency with maven 2. I guess I should use the provided scope, but I didn't manage to find what group, artefact and version I should use. Can anyone help me? Thanks, Gilles Scokart
Re: Re[8]: xdoclet dependency
Dmitry, maven-xdoclet-plugin depends on xjavadoc-1.0.2 this file seems to have disappeared from ibiblio.org/mavenhttp://ibiblio.org/maven! i do not know how to get it back there... Dennis On 8/22/05, Dmitry Ochnev [EMAIL PROTECTED] wrote: Hello Dennis, Monday, August 22, 2005, 3:01:35 PM, you wrote: only for the xjavadoc jar, you should use a groupId of xjavadoc and version 1.1 for the xdoclet jars groupId=xdoclet and version=1.2 so: dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency etcetera... Dennis It became better but it is still not working. Here is the part of the project.xml: ---begin--- !-- XDoclet dependencies -- dependency idxdoclet/id version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version typeplugin/type /dependency ---end--- And here is the output: ---begin--- Tag library requested that is not present: 'maven' in plugin: ' maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest2\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- Where is the error? -- Best regards, Dmitry mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Standardized Maven Environment
Jared,
I've used the solution mentioned by Brett on large projects and it works
well. I also place a project.xml and project.properties in the Maven cvs/svn
module that holds configuration data common to all applications on a
project. Applications then extend this project-level pom with extends${
maven.home}/project.xml/extends
I would be interested to hear how this issue is being addressed with M2. One
solution would be to have a small M2 core that is used to bootstrap your
project's POM, which extends a POM located on a web server. E.g. extends
http://mylocalserver/projectX/project.xml/extends I believe this is a
feature request that has already been submitted for M1 but I am not sure how
this would work for associated project.properties files. With M2 this should
become simpler as all configuration data is stored in the POM. Please
correct me if I am wrong.
Thomas
On 8/22/05, Buntingster [EMAIL PROTECTED] wrote:
We are looking at standardizing our builds on Maven. We will have one
server performing builds for our official artifacts. However, all of
our developers will also need to be able to build locally for their own
purposes. We will be setting up an internal repository for our
libraries, and we will also have need to write several custom plugins
for some of our business requirements.
We will initially be using maven 1 - while we are definitely considering
maven 2, politics do not allow us to use an unreleased project, and we
are in desperate need of the dependency management features provided by
maven. So, hopefully my solution (at least conceptually) can be applied
to both maven 1 and maven 2.
My question is this: is there any good way to be sure that my developers
are running in the same maven environment as our build server? By this
I mean primarily the plugins (and their versions) that are installed.
This becomes especially critical when we have internal plugins that will
be modified on a more frequent basis.
My current thought is to publish the info available in maven -i on a
central web server, and then write a custom plugin (update-maven-env)
that our developers can run that will retrieve this information and
retrieve and update the appropriate plugins.
I was wondering if anyone has any thoughts on this, if there is already
a solution out there? Any assistance would be greatly appreciated.
Thanks.
-Jared
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet dependency
xjavadoc-1.0.* exists on ibiblio with groupId 'xdoclet' latter versions (1.1) are registered under groupId xjavadoc. Dennis Geurts a écrit : Dmitry, maven-xdoclet-plugin depends on xjavadoc-1.0.2 this file seems to have disappeared from ibiblio.org/mavenhttp://ibiblio.org/maven! i do not know how to get it back there... Dennis On 8/22/05, Dmitry Ochnev [EMAIL PROTECTED] wrote: Hello Dennis, Monday, August 22, 2005, 3:01:35 PM, you wrote: only for the xjavadoc jar, you should use a groupId of xjavadoc and version 1.1 for the xdoclet jars groupId=xdoclet and version=1.2 so: dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency etcetera... Dennis It became better but it is still not working. Here is the part of the project.xml: ---begin--- !-- XDoclet dependencies -- dependency idxdoclet/id version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version typeplugin/type /dependency ---end--- And here is the output: ---begin--- Tag library requested that is not present: 'maven' in plugin: ' maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest2\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- Where is the error? -- Best regards, Dmitry mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Standardized Maven Environment
On Mon, Aug 22, 2005 at 02:21:31PM +0200, Thomas Van de Velde wrote:
Jared,
I've used the solution mentioned by Brett on large projects and it works
well. I also place a project.xml and project.properties in the Maven cvs/svn
module that holds configuration data common to all applications on a
project. Applications then extend this project-level pom with extends${
maven.home}/project.xml/extends
I would be interested to hear how this issue is being addressed with M2. One
solution would be to have a small M2 core that is used to bootstrap your
project's POM, which extends a POM located on a web server. E.g. extends
http://mylocalserver/projectX/project.xml/extends I believe this is a
feature request that has already been submitted for M1 but I am not sure how
this would work for associated project.properties files. With M2 this should
become simpler as all configuration data is stored in the POM. Please
correct me if I am wrong.
In Maven 2 you have parent instead of extends like this:
parent
groupIdmy-group/groupId
artifactIdmy-parent/artifactId
version1.0/version
/parent
Which is a artifact which can be put in your normal Maven repository.
--
Trygve
signature.asc
Description: Digital signature
Re: Standardized Maven Environment
Sounds like a good tip trick for mavenbook.org http://mavenbook.org
On 8/22/05, Trygve Laugstøl [EMAIL PROTECTED] wrote:
On Mon, Aug 22, 2005 at 02:21:31PM +0200, Thomas Van de Velde wrote:
Jared,
I've used the solution mentioned by Brett on large projects and it works
well. I also place a project.xml and project.properties in the Maven
cvs/svn
module that holds configuration data common to all applications on a
project. Applications then extend this project-level pom with
extends${
maven.home}/project.xml/extends
I would be interested to hear how this issue is being addressed with M2.
One
solution would be to have a small M2 core that is used to bootstrap your
project's POM, which extends a POM located on a web server. E.g.
extends
http://mylocalserver/projectX/project.xml/extends I believe this is a
feature request that has already been submitted for M1 but I am not sure
how
this would work for associated project.properties files. With M2 this
should
become simpler as all configuration data is stored in the POM. Please
correct me if I am wrong.
In Maven 2 you have parent instead of extends like this:
parent
groupIdmy-group/groupId
artifactIdmy-parent/artifactId
version1.0/version
/parent
Which is a artifact which can be put in your normal Maven repository.
--
Trygve
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.4.1 (GNU/Linux)
iD8DBQFDCcT44EbM92cyCUURAv7cAJ0fzSCLcx5q9bdlPkA/wT2sKJGlDQCeNCv2
XX868RfFHFLPcx8eSs33p5c=
=hOhl
-END PGP SIGNATURE-
RE: Re[8]: xdoclet dependency
Dmitry Ochnev wrote on Monday, August 22, 2005 1:39 PM: [snip] It became better but it is still not working. Here is the part of the project.xml: ---begin--- !-- XDoclet dependencies -- dependency idxdoclet/id version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version typeplugin/type /dependency ---end--- And here is the output: ---begin--- Tag library requested that is not present: 'maven' in plugin: 'maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest2\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- Where is the error? This is what I mean with the *corresponding* version. The xdoclet-plugin defines the dependency to xjavadoc. Unfortunately xjavadoc-1.0.2 is not located at ibiblio, you must downloat it manually (remember the URL ;-) and install it into your local repo. Regards, Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re[10]: xdoclet dependency
Hello Jörg, Monday, August 22, 2005, 4:42:18 PM, you wrote: This is what I mean with the *corresponding* version. The xdoclet-plugin defines the dependency to xjavadoc. Unfortunately xjavadoc-1.0.2 is not located at ibiblio, you must downloat it manually (remember the URL ;-) and install it into your local repo. I placed 'xjavadoc-1.0.2.jar' to 'c:\my_home_dir\.maven\repository\xjavadoc'. Now it is working. -- Best regards, Dmitrymailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet dependency
ok nicolas, thanks for the info (is must have copied it 'eons' ago and forgot about it afterwards), seems that some alteration is in order; either move/ copy the xjavadoc-1.0.* to xjavadoc or the maven-xdoclet-plugin (version 1.2) should incorporate a correct dependency. I do not think it is a good programming practice to define an invalid dependency and subsequently requiring from the developer that it should copy the dependency from its (apparently) default location to some other undocumented location. any comments ?? dennis On 8/22/05, Nicolas De Loof [EMAIL PROTECTED] wrote: xjavadoc-1.0.* exists on ibiblio with groupId 'xdoclet' latter versions (1.1) are registered under groupId xjavadoc. Dennis Geurts a écrit : Dmitry, maven-xdoclet-plugin depends on xjavadoc-1.0.2 this file seems to have disappeared from ibiblio.org/maven http://ibiblio.org/mavenhttp://ibiblio.org/maven! i do not know how to get it back there... Dennis On 8/22/05, Dmitry Ochnev [EMAIL PROTECTED] wrote: Hello Dennis, Monday, August 22, 2005, 3:01:35 PM, you wrote: only for the xjavadoc jar, you should use a groupId of xjavadoc and version 1.1 for the xdoclet jars groupId=xdoclet and version=1.2 so: dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency etcetera... Dennis It became better but it is still not working. Here is the part of the project.xml: ---begin--- !-- XDoclet dependencies -- dependency idxdoclet/id version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version typeplugin/type /dependency ---end--- And here is the output: ---begin--- Tag library requested that is not present: 'maven' in plugin: ' maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest2\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- Where is the error? -- Best regards, Dmitry mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet dependency
For info, http://maven.ozacc.com/search?keyword=xjavadoc is very usefull for such broken-dependecy-search. Nico. Dennis Geurts a écrit : ok nicolas, thanks for the info (is must have copied it 'eons' ago and forgot about it afterwards), seems that some alteration is in order; either move/ copy the xjavadoc-1.0.* to xjavadoc or the maven-xdoclet-plugin (version 1.2) should incorporate a correct dependency. I do not think it is a good programming practice to define an invalid dependency and subsequently requiring from the developer that it should copy the dependency from its (apparently) default location to some other undocumented location. any comments ?? dennis On 8/22/05, Nicolas De Loof [EMAIL PROTECTED] wrote: xjavadoc-1.0.* exists on ibiblio with groupId 'xdoclet' latter versions (1.1) are registered under groupId xjavadoc. Dennis Geurts a écrit : Dmitry, maven-xdoclet-plugin depends on xjavadoc-1.0.2 this file seems to have disappeared from ibiblio.org/maven http://ibiblio.org/mavenhttp://ibiblio.org/maven! i do not know how to get it back there... Dennis On 8/22/05, Dmitry Ochnev [EMAIL PROTECTED] wrote: Hello Dennis, Monday, August 22, 2005, 3:01:35 PM, you wrote: only for the xjavadoc jar, you should use a groupId of xjavadoc and version 1.1 for the xdoclet jars groupId=xdoclet and version=1.2 so: dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency etcetera... Dennis It became better but it is still not working. Here is the part of the project.xml: ---begin--- !-- XDoclet dependencies -- dependency idxdoclet/id version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-web-module/artifactId version1.2/version /dependency dependency groupIdxdoclet/groupId artifactIdxdoclet-ejb-module/artifactId version1.2/version /dependency dependency groupIdxjavadoc/groupId artifactIdxjavadoc/artifactId version1.1/version /dependency dependency groupIdxdoclet/groupId artifactIdmaven-xdoclet-plugin/artifactId version1.2/version typeplugin/type /dependency ---end--- And here is the output: ---begin--- Tag library requested that is not present: 'maven' in plugin: ' maven-xdoclet-plugin-1.2' Attempting to download xjavadoc-1.0.2.jar. Response content length is not known Response content length is not known Response content length is not known WARNING: Failed to download xjavadoc-1.0.2.jar. BUILD FAILED File.. D:\apptest2\maven.xml Element... attainGoal Line.. 23 Column 43 The build cannot continue because of the following unsatisfied dependency: xjavadoc-1.0.2.jar ---end--- Where is the error? -- Best regards, Dmitry mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] This message contains information that may be privileged or confidential and is the property of the Capgemini Group. It is intended only for the person to whom it is addressed. If you are not the intended recipient, you are not authorized to read, print, retain, copy, disseminate, distribute, or use this message or any part thereof. If you receive this message in error, please notify the sender immediately and delete all copies of this message. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: jellybean awaits setter with File instead of String argument
Dion Gillard schrieb am 12.08.2005 23:53: What are the other methods on that class? I violated the bean specification, there was a getter returning File instead of String. And how do you know its passing in a File or expecting one to go to the class? Log message of the beanutils: copyProperty([EMAIL PROTECTED], testClasses, MARTIN) target propName=testClasses, type=class java.io.File, index=-1, key=null USING CONVERTER [EMAIL PROTECTED] Notice: type=class java.io.File Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to access default value of property of another plugin
Hello,
I need the value of the property maven.test.reportsDirectory in the
plugin.jelly of my plugin even if it is not set via a project.properties
file.
Regard this simple goal:
goal name=some:goal
echoValue of maven.test.reportsDirectory:
${maven.test.reportsDirectory}/echo
/goal
If I run this goal without setting the property in a project.properties,
it's output is just [echo] Value of maven.test.reportsDirectory:. If I
run maven test:compile some:goal, it's output is [echo] Value of
maven.test.reportsDirectory: some value
How can I access the default value of that property as defined in the
plugin.properties of the test-Plugin without running a test goal? Should
I set this property in the plugin.properties of my plugin? I think that
solution is not so good, because if that property's default value is
changed I will need to change my settings, too.
Can I load the default properties of another plugin in my plugin's jelly
file?
Regards,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
How do I package a Swing application in Maven?
I have many items I want to combine for a swing application using maven. I am just wondering what the best approach is to packaging the many libs I will be using. Thank You Mick Knutson Sr. Java/J2EE Consultant BASE logic, inc. (415) 648-1804 (S.F., CA) http://www.BASELogic.com HP Consulting Services (Walnut Creek, CA) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
plugins
Hello: I´m writing a plugin. This plugin works executing different tasks (goals) in each subproject of a project. My questions are: How I can change the pom referenced in each case? How I can invoke the plugins with a relative path? I´ve tried to adapting the multiproject plugin and to overwriting the properties (basedir, maven.base.dir, maven.build.dir) but it doesn't work. Regards. Jorge Mikitiuk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New PDF plugin SNAPSHOT
I found the solution by accident: you just have to remove the
'dir=${internal_pdf_workingDir}' option when you call fop in plugin.jelly.
Apparently a problem of relative url resolution (it only failed for svgs
containing relative url links within the same document, ie starting with
#, and only if they are not in the same directory as project.fo).
Cheers,
Lukas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: New PDF plugin SNAPSHOT
I found the solution by accident: you just have to remove the
'dir=${internal_pdf_workingDir}' option when you call fop
in plugin.jelly.
Apparently a problem of relative url resolution (it only
failed for svgs containing relative url links within the same
document, ie starting with #, and only if they are not in the
same directory as project.fo).
Cheers,
Lukas
Nothing more to say !
You're my god ;-)
Thanks a lot
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Maven 1 subversion repository
What's the path/url to the subversion repository for Maven plugins?
Re: Maven 1 subversion repository
Never mind. I got ot. On 8/22/05, Jon Strayer [EMAIL PROTECTED] wrote: What's the path/url to the subversion repository for Maven plugins?
searching the archives??
Greetings, At the risk of asking a dumb question, is users@maven.apache.org searchable?? When I go to the archives (http://mail-archives.apache.org/mod_mbox/maven-users/) I cannot see any mechanism to search. Am I missing something?? Thanks, -- Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
PDF plugin 2.4-SNAPSHOT available
A new snapshot is available. Changes in this version include: New Features: o Allow the pdf plugin to be added as a project's report. Issue: MPPDF-9. Thanks to Fabrizio Giustina. Fixed bugs: o sub-/superscripts do not work. Issue: MPPDF-43. Thanks to Lukas Theussl. o Error when logo locations are not set. Issue: MPPDF-42. Thanks to Lukas Theussl. o Suppress verbose output by default. Issue: MPPDF-41. Thanks to Lukas Theussl. o Missing patch for MPPDF-24 ( it defines a missing attribute for amp;lt;code style=indentamp;gt; tags and cleans up some layout issues with definition lists). Issue: MPPDF-39. Thanks to Lukas Theussl. o Standardize copyright notices. Issue: MPPDF-35. Thanks to Lukas Theussl. o Fix some contents overflows area errors. Issue: MPPDF-33. Thanks to Valerie Nyre. o Cannot use SVG images. (batik: java.lang.NoSuchMethodError.) Issue: MPPDF-32. Thanks to Lukas Theussl. o Can't insert the logo image described in the POM if its path begins with a slash (as it works for the xdoc plugin). Issue: MPPDF-31. Thanks to Lukas Theussl. o Allow copy and paste from pdf to text editor. Issue: MPPDF-22. Thanks to Lukas Theussl. o Add support for external imaging libraries like jimi and jai to use PNG images in generated pdf files. Issue: MPPDF-8. Thanks to Fabio Franco Uechi. o PDF generation doesn't use proxy settings for external resources. Issue: MPPDF-7. Changes: o Make the plugin compatible with maven 1.0 and jdk 1.3/1.4/1.5 or with maven 1.1 and jdk 1.4/1.5. To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-pdf-plugin -Dversion=2.4-SNAPSHOT Arnaud - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to access default value of property of another plugin
Martin,
This has been documented here:
http://maven.apache.org/tags.html#maven:pluginVar
e.g. *maven**:**pluginVar* var=reportsDir plugin='maven-test-plugin'
property='maven.test.reportsDirectory'/
Cheers,
Thomas
On 8/22/05, Martin Burger [EMAIL PROTECTED] wrote:
Hello,
I need the value of the property maven.test.reportsDirectory in the
plugin.jelly of my plugin even if it is not set via a project.properties
file.
Regard this simple goal:
goal name=some:goal
echoValue of maven.test.reportsDirectory:
${maven.test.reportsDirectory}/echo
/goal
If I run this goal without setting the property in a project.properties,
it's output is just [echo] Value of maven.test.reportsDirectory:. If I
run maven test:compile some:goal, it's output is [echo] Value of
maven.test.reportsDirectory: some value
How can I access the default value of that property as defined in the
plugin.properties of the test-Plugin without running a test goal? Should
I set this property in the plugin.properties of my plugin? I think that
solution is not so good, because if that property's default value is
changed I will need to change my settings, too.
Can I load the default properties of another plugin in my plugin's jelly
file?
Regards,
Martin
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: searching the archives??
Try http://marc.theaimsgroup.com/?l=turbine-maven-user Cheers, Thomas On 8/23/05, Chris Berry [EMAIL PROTECTED] wrote: Greetings, At the risk of asking a dumb question, is users@maven.apache.org searchable?? When I go to the archives (http://mail-archives.apache.org/mod_mbox/maven-users/) I cannot see any mechanism to search. Am I missing something?? Thanks, -- Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to access default value of property of another plugin
Maven:pluginVar is deprecated.
You must use maven:get
http://maven.apache.org/tags.html#maven:get
Arnaud
-Message d'origine-
De : Thomas Van de Velde [mailto:[EMAIL PROTECTED]
Envoyé : mardi 23 août 2005 00:46
À : Maven Users List
Objet : Re: How to access default value of property of another plugin
Martin,
This has been documented here:
http://maven.apache.org/tags.html#maven:pluginVar
e.g. *maven**:**pluginVar* var=reportsDir
plugin='maven-test-plugin'
property='maven.test.reportsDirectory'/
Cheers,
Thomas
On 8/22/05, Martin Burger [EMAIL PROTECTED] wrote:
Hello,
I need the value of the property
maven.test.reportsDirectory in the
plugin.jelly of my plugin even if it is not set via a
project.properties file.
Regard this simple goal:
goal name=some:goal
echoValue of maven.test.reportsDirectory:
${maven.test.reportsDirectory}/echo
/goal
If I run this goal without setting the property in a
project.properties, it's output is just [echo] Value of
maven.test.reportsDirectory:. If I run maven test:compile
some:goal, it's output is [echo] Value of
maven.test.reportsDirectory: some value
How can I access the default value of that property as
defined in the
plugin.properties of the test-Plugin without running a test goal?
Should I set this property in the plugin.properties of my plugin? I
think that solution is not so good, because if that
property's default
value is changed I will need to change my settings, too.
Can I load the default properties of another plugin in my plugin's
jelly file?
Regards,
Martin
-
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: searching the archives??
You can also try this one : http://www.mail-archive.com/users@maven.apache.org/index.html Arnaud -Message d'origine- De : Thomas Van de Velde [mailto:[EMAIL PROTECTED] Envoyé : mardi 23 août 2005 00:48 À : Maven Users List Objet : Re: searching the archives?? Try http://marc.theaimsgroup.com/?l=turbine-maven-user Cheers, Thomas On 8/23/05, Chris Berry [EMAIL PROTECTED] wrote: Greetings, At the risk of asking a dumb question, is users@maven.apache.org searchable?? When I go to the archives (http://mail-archives.apache.org/mod_mbox/maven-users/) I cannot see any mechanism to search. Am I missing something?? Thanks, -- Chris - 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] maven-antrun-plugin
Greetings, I am trying to get the m2 maven-antrun-plugin to run. I have gotten pretty far but now I'm stumped. First I downloaded the latest/greatest m2 from SVN. Then I pulled the maven-antrun-plugin code out and built it, after hacking a bit. I had to; 1) Change the pom.xml parent version 2) Grab the plexus-override-component-configurator 1.0-SNAPSHOT and install it After getting the plugin built, I then added the following to my little test project's pom.xml: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.0-alpha-1-SNAPSHOT/version executions execution phasevalidate/phase configuration tasks echo! I WAS HERE !!/echo /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin /plugins /build But when I run this, I get the following weird Exceptions (see below). And I'm stumped. Can anyone help me?? I searched the archives and found someone recently had this issue -- but there was no help given. Thanks, -- Chris 110] ~/work/m2-test3/my-app4$ m2 install INFO] INFO] Building Maven Test APP INFO] INFO] maven-resources-plugin: resolved to version 2.0-alpha-3 from local repository INFO] maven-compiler-plugin: resolved to version 2.0-alpha-3 from local repository INFO] maven-surefire-plugin: resolved to version 2.0-alpha-3 from local repository INFO] maven-jar-plugin: resolved to version 2.0-alpha-3 from local repository INFO] maven-source-plugin: resolved to version 2.0-alpha-2 from local repository INFO] maven-install-plugin: resolved to version 2.0-alpha-3 from local repository INFO] my-mojo: using locally installed snapshot INFO] maven-antrun-plugin: using locally installed snapshot INFO] ERROR] BUILD ERROR INFO] INFO] Diagnosis: Error looking up plugin: INFO] ERROR] Cause: rg.apache.maven.plugin.MojoExecutionException: Error looking up plugin: at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:382) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:169) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:143) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:129) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:103) at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:261) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:180) at org.apache.maven.cli.MavenCli.main(MavenCli.java:269) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303) at org.codehaus.classworlds.Launcher.launch(Launcher.java:243) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416) at org.codehaus.classworlds.Launcher.main(Launcher.java:363) aused by: org.codehaus.plexus.component.repository.exception.ComponentLookupException: Unable to lookup component 'org.apache.maven.plugin. ojoorg.apache.maven.plugins:maven-antrun-plugin:1.0-alpha-1-SNAPSHOT:run', it could not be started at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:315) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:416) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:495) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:373) ... 15 more aused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycleException: Error starting component at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:109) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getComponent(PerLookupComponentManager.java:48)
Disabling Deploy Task - Maven 2
I have a quick newbie question. In Maven 2, from the documention, it appears that the deploy lifecycle publishes a project to teh remote repository. For projects in which you don't want published to the remote ibiblio repository, it seems like you would want to disable this lifecycle phase, correct? Otherwise, it seems too easy to make a mistake and publish it. Can this be done easily or am I misunderstanding the documentation? Thanks.
[m1.1] JCoverage fails multiproject:site
All, How do I prevent that a failing JCoverage JUnit test fails the multiproject:site goal? Obviously fixing the test/code is one answer, but I am looking for the other one ;-) I have already tried to set the property maven.test.failure.ignore to true, but that didn't seem to help. Thanks, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disabling Deploy Task - Maven 2
It's just a matter of not running it. Since nothing comes after deploy, the only way it will run is if you run m2 deploy. - Brett On 8/23/05, Scott Goldstein [EMAIL PROTECTED] wrote: I have a quick newbie question. In Maven 2, from the documention, it appears that the deploy lifecycle publishes a project to teh remote repository. For projects in which you don't want published to the remote ibiblio repository, it seems like you would want to disable this lifecycle phase, correct? Otherwise, it seems too easy to make a mistake and publish it. Can this be done easily or am I misunderstanding the documentation? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant Tasks + Proxy
Do setting the standard Java system properties work? We do not yet handle NTLM configuration. - Brett On 8/23/05, Wyvis vis [EMAIL PROTECTED] wrote: I am doing an evaluation of the Maven2 Ant dependency management tasks and I am having a few problems getting them to work :-( I am sitting behind an NTLM proxy and, when using Maven 1, have to specify the maven.proxy.ntlm.host and maven.proxy.ntlm.domain properties in my build.properties file. I can't see any way to do this for the Maven2 Ant tasks -- can it be done? - Wyvis. _ Want to block unwanted pop-ups? Download the free MSN Toolbar now! http://toolbar.msn.co.uk/ - 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: Disabling Deploy Task - Maven 2
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 just FYI, if you don't specify a distributionManagement/ section, you won't have much luck deploying your project, even accidentally. ;-) - -john Scott Goldstein wrote: | I have a quick newbie question. In Maven 2, from the documention, it appears that the deploy lifecycle publishes a project to teh remote repository. For projects in which you don't want published to the remote ibiblio repository, it seems like you would want to disable this lifecycle phase, correct? Otherwise, it seems too easy to make a mistake and publish it. Can this be done easily or am I misunderstanding the documentation? | | Thanks. | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDCnSGK3h2CZwO/4URAhj+AKCijBogdnz+Fyg3e97uepz2i2hvgwCfaYi7 Svghya9e1YanDkMLdtqO8Go= =ObTD -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] deployment during integration-test lifecycle phase
Hello all - I have taken over a project that is being built on maven 1 and would like to move it on to maven 2 when it is released. Currently we do a lot of in-container testing on our ejbs which sounds like it would belong in the integration-test phase of the m2 lifecycle. The question is, what is the best way to deploy the ear that is built in the package phase to an app server so that we can run all of the in-container tests? My initial thought is this: I could write a plug-in that essentially wraps the shell script we currently use to deploy our applications. Then bind it and the surefire plug-in to the integration-test phase. I'm not exactly sure how to tell surefire which tests are unit tests and which ones are integration tests. Also I'm not sure how to change the bindings of an existing plug-in. It seems like this phase's existence would imply that these features will be needed by a lot of people. Is there another plug-in in the works that will address these issues or is there a solution already out there that I just don't know about? Any input would be much appreciated. Thanks, Mike - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 transitive dependencies and releasing with M1
All, I'm currently releasing Wicket and we have 2 projects: wicket and wicket-extensions. The extensions project has a dependency on wicket. When I create a new version of wicket, do I need to release a new, updated version of extensions as well? Or is this automatically resolved with m2? Martijn - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 transitive dependencies and releasing with M1
The way it works is that a version you give becomes a suggestion to m2, and depending on your conflict resolution strategy that version might be selected, or the latest release. We're still working on this, so we'll have it all set up by beta-1 to test fully and will get some docs together. Currently, the m1 - m2 conversion won't accommodate ranges (we'd need to let you add a new property to your m1 pom). - Brett On 8/23/05, Martijn Dashorst [EMAIL PROTECTED] wrote: All, I'm currently releasing Wicket and we have 2 projects: wicket and wicket-extensions. The extensions project has a dependency on wicket. When I create a new version of wicket, do I need to release a new, updated version of extensions as well? Or is this automatically resolved with m2? Martijn - 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] deployment during integration-test lifecycle phase
I know that someone else on this list is going to jump in and suggest the same thing... When they are ready, I'd suggest looking at the Cargo (http://cargo.codehaus.org) and Cactus (http://jakarta.apache.org/cactus) plugins. Evenif you don't use them directly, you could use them as inspiration for your own. - Brett On 8/23/05, Michael Deck [EMAIL PROTECTED] wrote: Hello all - I have taken over a project that is being built on maven 1 and would like to move it on to maven 2 when it is released. Currently we do a lot of in-container testing on our ejbs which sounds like it would belong in the integration-test phase of the m2 lifecycle. The question is, what is the best way to deploy the ear that is built in the package phase to an app server so that we can run all of the in-container tests? My initial thought is this: I could write a plug-in that essentially wraps the shell script we currently use to deploy our applications. Then bind it and the surefire plug-in to the integration-test phase. I'm not exactly sure how to tell surefire which tests are unit tests and which ones are integration tests. Also I'm not sure how to change the bindings of an existing plug-in. It seems like this phase's existence would imply that these features will be needed by a lot of people. Is there another plug-in in the works that will address these issues or is there a solution already out there that I just don't know about? Any input would be much appreciated. Thanks, Mike - 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] How does filtering resources work?
If I'm not the only one who thinks that filters directly defined at the resources is a good idea, I could try to develop a patch. Interested? Carsten Carsten Ziegeler wrote: Hi Brett, Brett Porter wrote: There was some hesitation to adding filtering in the first place - we added it as a parameter on the resources plugin because it was uncertain it would be retained in the POM. It now looks like it will, but we're wary of how it is used. It is important for Maven to work that the values filtered in are always the same if the artifact being built is the same. If you want to build 2 different artifacts, you use 2 profiles (or two projects), and provide different filters to each. Ok, agree. I'm curious why you need different filters for different sets of files - do they have changing values or is it just an optimisation? Kind of optimization and I don't want to filter binary files. So I thought of creating one resource set with ascii files and one for the binary files and apply filtering only to the first set to be sure that the binary files don't get corrupted. Also, it should be noted that Maven builds in a pom.properties file into META-INF as well as a copy of pom.xml so that you can retrieve such values at runtime if needed. Anyway, I'm happy to discuss what the filtering needs are and adjust accordingly. I'm still reluctant to promote filters to the resource element itself, but it can be considered again. I think it makes more sense to have it at the resources element because you define your resource sets and then you want to apply directly to this set some filtering (or not). If you separate this (resource set and plugin configuration) it's not that obvious what's really going on and it makes it imho harder to apply filtering than it should be. You loose the connection between the resource sets (or test resource sets) and the settings of the plugin. WDYT? Carsten -- Carsten Ziegeler - Open Source Group, SN AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
