Re: [Spam] Re: release plugin (scm via cvs)
On Friday 04 May 2007 14:24, Stephane Nicoll wrote: On 5/4/07, David Corbin [EMAIL PROTECTED] wrote: On Friday 04 May 2007 13:56, Emmanuel Venisse wrote: What is your directory structure? inventory.ws com.enttek.concessions-master com.enttek.concessions.common com.enttek.concessions.homeoffice Flat directories aren't supported. Right. Unfortunately, Eclipse *only* supports flat directories. 2 workarounds: 1. you can add a pom under /home/dcorbin/workspace/inventory.ws/ and do the release on it The problem with this is that directory is not under CVS. You are missing an important concet of the release plugin. If the plugin acts on something it should tag everything since release:perform will do a checkout of the tag created during release:prepare (in another directory). No, I didn't miss it. That's why I called workaround #1 a problem. It calls for me to have a critical file NOT in source control, and this won't work. I can see no technical reason that the release plugin cannot support sibling modules. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Spam] Re: release plugin (scm via cvs)
On Friday 04 May 2007 14:43, Roland Asmann wrote: On Friday 04 May 2007 20:16, David Corbin wrote: On Friday 04 May 2007 13:56, Emmanuel Venisse wrote: Flat directories aren't supported. Right. Unfortunately, Eclipse *only* supports flat directories. That depends. It is possible to import the sub-dirs as seperate projects in Eclipse. That way you can work on all modules as if they were in a flat structure. We've been doing that around here for quite some time! That sound suspiciously like you've got a lot of duplication going on. Fundamentally, Eclipse does NOT support heirarchies. I don't think you can map a heiarchy to a flat model and maintain a one-to-one copy. Just run the eclipse:eclipse plugin on your projects and import the projects. Be carefull, this needs eclipse 3.1.x or newer (if I remember correctly), because you need to tell eclipse to NOT copy the project to the workspace. So, from what you say, If I have 3 layers in my heirarchy, Eclipse is going to perceive 3 copies of every file in my bottom-most tier. -- David Corbin Games, Gamers, Gaming - a blog - http://dcorbin.com/blogs/g3 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Signed jars in the repository
We're building a webstart application. For this, we have to sign jars. We use the webstart-maven-plugin, and it does the job well enough. However, we spend a lot of time re-signing the same unchanged jars (various third-party dependencies). They get resigned as a consequence of a clean. This is particularly annoying because we're stuck with java 1.4.2 which signs really slow compare to 1.5 What I'd really like to do, is have signed jars in the repository (local or corporate). Unfortunately, we have some test tools that don't play well with signed jars, so it's not a question of sign them once and manually install them in place of the original jar. What I think I want to do is use a classifier. I can see three strategies for this: Both strategies involve changing the webstart plugin to ask for jars classified with signed-by-foo. The question then becomes the best way to install them: A) in a caching-proxy repo, when asked for a jar with classifier signed-by-foo, it returns the one it has, or it signs it on the fly, caches it and returns it. B) When the plugin cannot get the signed artifact, get the unsigned one, sign it, and install it with the appropriate classifier. There may be elements here that belong in the jar plugin. C) Just do it manually. We're probably talking about 20 third-party jars. If not found the plugin could continue and sign a local copy to use (which would cover the signing for OUR jars) This is really going to get worse as actually have multiple webstart parts (but only 1 is under maven). When we're fully mavened, we'll be signing the same jars over and over in one build. Basically, I'm seeing comments and suggestions on my proposal(s). Many thanks. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
need help with a maven 2 plugin
I would like to create a build-report-plugin that is able to report on the versions, timestamps, artifact types, build numbers, and so on. I can write my own custom code to do all of this, but there there has to be an easier way to reuse the code/components that maven is already using to download/upload the metadata files. It seems logical from an OO perspective that the MavenProject object would have a method that could do something like this, but I could not find one. Does anyone know how what objects to use and how to get a reference to them in the plugin itself? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Spam] Re: release plugin (scm via cvs)
David Corbin a écrit : On Friday 04 May 2007 14:43, Roland Asmann wrote: On Friday 04 May 2007 20:16, David Corbin wrote: On Friday 04 May 2007 13:56, Emmanuel Venisse wrote: Flat directories aren't supported. Right. Unfortunately, Eclipse *only* supports flat directories. That depends. It is possible to import the sub-dirs as seperate projects in Eclipse. That way you can work on all modules as if they were in a flat structure. We've been doing that around here for quite some time! That sound suspiciously like you've got a lot of duplication going on. Fundamentally, Eclipse does NOT support heirarchies. I don't think you can map a heiarchy to a flat model and maintain a one-to-one copy. You can use hierarchies for your maven projects, then when you run mvn eclipse:eclipse command, the plugin won't create eclipse projects for project with pom packaging. So you can import hierarchical maven project to eclipse. All projects under maven umbrella are hierarchical and developers works well with eclipse. Just run the eclipse:eclipse plugin on your projects and import the projects. Be carefull, this needs eclipse 3.1.x or newer (if I remember correctly), because you need to tell eclipse to NOT copy the project to the workspace. So, from what you say, If I have 3 layers in my heirarchy, Eclipse is going to perceive 3 copies of every file in my bottom-most tier. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Spam] Re: release plugin (scm via cvs)
On Sunday 06 May 2007 16:39, David Corbin wrote: That sound suspiciously like you've got a lot of duplication going on. Fundamentally, Eclipse does NOT support heirarchies. I don't think you can map a heiarchy to a flat model and maintain a one-to-one copy. No. The plugin I pointed you to (and eclipse 3.1.x as well -- although it's not the default!) will not copy the directories, they will only link them! People have been able to do something like this for a pretty long time on *nix already, but it works fine on Win as well. The only problem you'll have is when deleting files in eclipse... Eclipse will recognize deletion ONLY on the project where you deleted! This means that you must synchronize that project seperately. Example: You have a parent-project A, with 2 sub-projects B and C. When you delete files in C, you must synchronize (and delete) these files from that project with your CVS. If you synchronize the project from A, eclipse will tell you that your SCM has newer versions for the deleted files! It has something to do with the internal remembering of deletions in eclipse, it is not an SCM-thing. So, from what you say, If I have 3 layers in my heirarchy, Eclipse is going to perceive 3 copies of every file in my bottom-most tier. No, you will have your project checked out only once, and eclipse references ONLY the java-type projects. If you have more than 1 layer, you will probably have 2 layers with POM-projects and 1 with actual Java-projects. The plugin will then only reference these projects, but leave the actual source-code in the original tree. -- 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: Version number propogation
On Sunday 06 May 2007 17:30, Howard Lewis Ship wrote:
I have a project with multiple modules.
I'm keeping the version numbers synced.
This ends up with a lot of repetition of the version number:
artifactIdtapestry-core/artifactId
packagingjar/packaging
version5.0.5-SNAPSHOT/version
parent
groupIdorg.apache.tapestry/groupId
artifactIdtapestry-project/artifactId
version5.0.5-SNAPSHOT/version
relativePath../tapestry-project/pom.xml/relativePath
/parent
Worse yet, those same version numbers are creeping into documentation and
into project archetypes.
How would I go about externalizing the version number so that it appears
just once? I'd love to have something like I used to do in Ant ... a
build.properties file that defines the version number.
Also, is there a general way to include POM properties inside APT documents
and/or site.xml?
What we do here, is define a parent-POM which holds the version-number. All
child-projects to this POM, must at least define the version for the
parent-project, but from there on, you don't need to define them anymore.
Example:
project
parent
groupIdmy.group/groupId
artifactIdparent-artifact/artifactId
version0.0.1-SNAPSHOT/version
/parent
artifactIdartifact/artifactId
dependencies
dependency
groupId${groupId}/groupId
artifactIdanother-artifact/artifactId
version${project.version}/version
/dependency
/dependencies
/project
This project references the parent over a version, inherits that version as
its own version and even uses it to reference another child-project as a
dependency (with that same version again).
Now, if you were to use the release-plugin, you'd never have to change
anything here (unless you explicitly want to use another version of a
parent/dependency).
--
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: Version number propogation
On Sunday 06 May 2007 19:20, Bryan Loofbourrow wrote: I believe that you are correct about not being able to parameterize the project parent tag, or so a co-worker tells me. He conjectures that the parent resolution is required before resolution of property names. That makes sense, since, in general, the value you're looking for could be defined in the parent pom, But when I provide a relativePath tag in parent declaration, that should allow be enough. In fact, if I provide rrelativePath all the artifact information provided should just be a safety check. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multi-module project with Aggregation and SCM
Hi all, I was wondering if it is possible the following procedure: I have a multi-module maven project that has, lets say, 3 modules: Project - Module1 - Module2 - Module3 In the top-level pom I state that there are several modules aggregated: modules moduleModule1/module moduleModule2/module moduleModule3/module /modules Now, I was wondering if is there a way that I can get maven to, and given only the root pom, fetch the submodules from a SCM URL (different for each module). $ ls -la pom.xml $ mvn ... ... $ ls Module1 Module2 Module3 pom.xml -- Luís Soares * [EMAIL PROTECTED] * http://gsd.di.uminho.pt/members/los * * gpg: C55B F036 E664 AFD3 40C8 7322 1978 6C65 E678 C223 * signature.asc Description: This is a digitally signed message part
Re: Multi-module project with Aggregation and SCM
You can define relative paths to your modules' directories from the parent POM's directory: modules module../Module1/module module../../Other/Module2/module moduleModule3/module /modules -Olivier Luís Soares wrote: Hi all, I was wondering if it is possible the following procedure: I have a multi-module maven project that has, lets say, 3 modules: Project - Module1 - Module2 - Module3 In the top-level pom I state that there are several modules aggregated: modules moduleModule1/module moduleModule2/module moduleModule3/module /modules Now, I was wondering if is there a way that I can get maven to, and given only the root pom, fetch the submodules from a SCM URL (different for each module). $ ls -la pom.xml $ mvn ... ... $ ls Module1 Module2 Module3 pom.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
depenedency:analyze and JSP compilation ?
Hi, How can I get the dependency:analyze goal to include the class files that result from the compilation of the JSPs in the actual analysis? Is there a configuration parameter to indicate additional target directories to look into? Am I missing something? Thanks in advance for sharing your experience with this. -Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multi-module project with Aggregation and SCM
Hi all, I was wondering if it is possible the following procedure: I have a multi-module maven project that has, lets say, 3 modules: Project - Module1 - Module2 - Module3 In the top-level pom I state that there are several modules aggregated: modules moduleModule1/module moduleModule2/module moduleModule3/module /modules Now, I was wondering if is there a way that I can get maven to, and given only the root pom, fetch the submodules from a SCM URL (different for each module). $ ls -la pom.xml $ mvn ... ... $ ls Module1 Module2 Module3 pom.xml -- Luís Soares * [EMAIL PROTECTED] * http://gsd.di.uminho.pt/members/los * * gpg: C55B F036 E664 AFD3 40C8 7322 1978 6C65 E678 C223 * signature.asc Description: This is a digitally signed message part
axistools-maven-plugin question
Hi Everyone, Can you add a jar to the axistools-maven-plugin's classpath? I need to run the java2wsdl command and I have a dependency on one of my app's jar in a separate maven project. The plugin is telling me that it can't find the class. When I look at mvn -X logs, it shows the axistools-maven-plugin's classpath the target/classes directory. Thanks for your help, David Williams
Maven for XSLT/XML project
Hi all! I want to use Maven 2 to manage a project which consists of a XSLT-library and modules of XML-files using it. E.g., I have a module core containing several XSLT-files to transform a special XML-format into HTML and some CSS/Image-files needed for further styling. Then, I have some other modules, each containing a set of those XML-files, depending on the core module and its stylesheets. What I want Maven to do here is to manage downloading and providing the scripts in core to each of the dependent modules and maybe the transformation and packaging process itself, but for this I could call an Ant-task. I couldn't find any information on this subject, and would like to know details like which directory structure to use for Maven in this case (or whether that does not matter), and if there exists already some best practice for such an usage of Maven. I hope I made clear what I need, but if not, I'll try to explain further details. Many thanks in advance, Daniel Kraft *** The information in this email is confidential and may be legally privileged Access to this email by anyone other than the intended addressee is unauthorized. If you are not the intended recipient of this message, any review, disclosure, copying, distribution, retention, or any action taken or omitted to be taken in reliance on it is prohibited and may be unlawful. If you are not the intended recipient, please reply to or forward a copy of this message to the sender and delete the message, any attachments, and any copies thereof from your system. *** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Multi-module project with Aggregation and SCM
If your complete project is build as a tree (parent contains the modules as directories), that is no problem at all. In fact, that's the default that Maven will do when checking out your project. In your example, it appears your directory-structur is okay, so you should be ready to go! Take a look at the scm-plugin (http://maven.apache.org/scm/plugins/) for the command to checkout your project from SCM. On Monday 07 May 2007 13:19, Luís Soares wrote: Hi all, I was wondering if it is possible the following procedure: I have a multi-module maven project that has, lets say, 3 modules: Project - Module1 - Module2 - Module3 In the top-level pom I state that there are several modules aggregated: modules moduleModule1/module moduleModule2/module moduleModule3/module /modules Now, I was wondering if is there a way that I can get maven to, and given only the root pom, fetch the submodules from a SCM URL (different for each module). $ ls -la pom.xml $ mvn ... ... $ ls Module1 Module2 Module3 pom.xml -- 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: Multi-module project with Aggregation and SCM
On Monday 07 May 2007 15:32, Luís Soares wrote: First, Thanks for replying. Second, I am not a maven2 guru, but judging from your words, I would have to have a full maven tree (and their corresponding poms) in the source code management repository. That is precisely what I want to avoid. Notice that I wish to: 1. checkout a maven2 (meta-)project using my favorite SCM. No problem here, this should work. 2. use maven and the information in the root pom, checked out in 1., to build its project tree (which, obviously includes creating the sub-modules directories and checking out their sources and poms from their correspondent SCMs locations). I think the problem will be to locate the sub-modules in your SCM... For creating new projects, you could use the archetype-plugin, but checking out modules that are in different locations will not work. It might be worth a try though, to define the modules in the same way as your projects are found in your SCM (../module or ../../project/module), although I have never tried something like that, and Maven surely wasn't thought for that... But give it a try and see what happens... And report back to us, so we know if it can be done! ;-) If it works, I do fear that the modules will not be found under the current project though. I believe the ../-prefixes will be set on the modules as well.. They have to be though, since Maven will look for the modules at those locations... Good luck (and sorry to be of so little help)! -- 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: Usage of ${appserver.home} in ~/.m2/archiva.xml
I have set both properties through CATALINA_OPTS, here is how I start Tomcat
on a win32 machine!
@set CATALINA_OPTS=-Dappserver.home=d:\temp\home
-Dappserver.base=d:\temp\base
@cd d:\temp\apache-tomcat-5.5.23
@mkdir d:\temp\home\
@mkdir d:\temp\base\logs
@d:\temp\apache-tomcat-5.5.23\bin\startup.bat
The appserver.home property is accepted, archiva creates a repository named
internal inside this directory. However, the appserver.base is
particularly ignored, the archiva.log file is going to this path BUT still
the TOMCAT_HOME/${appserver.base}\logs folder is created and it contains the
file audit.log
For comparing this I have also deployed continuum and noticed a similar
behaviour, TOMCAT_HOME/${appserver.base}\logs folder is created but stays
empty!
Hope this helps to diagnose and fix! I mean it's not a major issue but
strange!
Thanks
Martin
Emmanuel Venisse wrote:
You must create a directory (for example, 'appserver_base' or something
else) where you want on your disk.
Then you set the CATALINA_OPTS env var like that:
set CATALINA_OPTS=-Dappserver.base=/path/to/appserver_base/directory
Then you restart your tomcat.
Emmanuel
--
View this message in context:
http://www.nabble.com/Usage-of-%24%7Bappserver.home%7D-in-%7E-.m2-archiva.xml-tf3696110.html#a10358139
Sent from the archiva-users mailing list archive at Nabble.com.
Eclipse maven project with WTP enabled
Hi, I followed: http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html to mark my project as a WTP project: mvn -Dwtpversion=1.5 eclipse:eclipse but nothing changed (I cannot deploy my project, nor select a server). I did it after creating submodules etc. should I have done it before? Or doesn't it matter? I'm a complete maven newbie, so every held is appreciated. Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Tip to invoke maven from an ant build script
Hi all :-) Is it possible to invoke maven from an ant build script, such as a mvn custom task ? Is this the right approach to perform that ? Thank you very much -- Marcos H. W. Softing Systems Systems Analyst +55 11 38770360 /** * @see https://jaxb2-commons.dev.java.net */ /** * ...Use the Force ...;-) */ * * @see http://www.gentoo.org/ */ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please help - why doesn't my index.html get generated when generating my site?
Hi Ian, I think (though you haven't said anything about your setup) that you don't have a site descriptor, the default location for which is src/site/site.xml. See http://maven.apache.org/guides/mini/guide-site.html for info about what can go in there. Here's a quick vanilla site descriptor that should get you started: ?xml version=1.0? project name=My Project bannerLeft nameMy Project/name /bannerLeft body menu ref=reports/ /body /project Hope it helps, Steve Ian Rowlands wrote: I'm using Maven 2.0.5. My sites have no customisation (which I won't do until I get this to work). I am getting the following generated: Apart from subdirectories, I get: checkstyle.html (plus checkstyle.rss) cpd.html and cpd.xml dependencies.html integration.html issue-tracking.html jdepend-report.html pmd.html and pmd.xml project-info.html project-reports.html surefire-report.html I'm using version 2.0-beta-5 of the web site plugin. I have been told that an index.html should be generated, and it is not. This is an issue because it is a multi-module project, and links on the parent project all link to the index.html of the sub-projects. So without the index.html nobody can navigate the site correctly. Any suggestions? Regards, Ian Rowlands Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected ( administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. - 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: axistools-maven-plugin question
There is a dependencies/ node inside the plugin/ node you can use to specify this. Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi Everyone, Can you add a jar to the axistools-maven-plugin's classpath? I need to run the java2wsdl command and I have a dependency on one of my app's jar in a separate maven project. The plugin is telling me that it can't find the class. When I look at mvn -X logs, it shows the axistools-maven-plugin's classpath the target/classes directory. Thanks for your help, David Williams - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with downloading project specific jars from remote repository. plz help
Hello, Could u plz help me out in solving this error : C:\Workspaces\Copy of RS_latestmvn install [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] EDMS RS migration to OD [INFO] EDMS RS migration to OD [INFO] EDMS RS migration to OD [INFO] EDMS RS migration to OD [INFO] [INFO] Building EDMS RS migration to OD [INFO]task-segment: [install] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://phildcdv07.us.hsbc:8080/repository/proxy/repos/HTSU/Artifact%20Repository/es-presentation/es-taglib/2.1.4/es-taglib-2.1.4.pom Downloading: http://phildcdv07.us.hsbc:8080/repository/proxy/repos/HTSU/Artifact%20Repository/es-presentation/es-taglib/2.1.4/es-taglib-2.1.4.jar [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. Missing: -- 1) es-presentation:es-taglib:jar:2.1.4 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=es-presentation -DartifactId=es-taglib \ -Dversion=2.1.4 -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) com.hsbc.rcc:edmsrc:jar:1.0-edmsrcc 2) es-presentation:es-taglib:jar:2.1.4 -- 1 required artifact is missing. for artifact: com.hsbc.rcc:edmsrc:jar:1.0-edmsrcc from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Mon May 07 20:20:08 GMT+05:30 2007 [INFO] Final Memory: 3M/6M Thanks, Kiran Kodlady -- View this message in context: http://www.nabble.com/Problem-with-downloading-project-specific-jars-from-remote-repository.-plz-help-tf3704188s177.html#a10358772 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: Tip to invoke maven from an ant build script
Maven Tasks for Ant http://maven.apache.org/ant-tasks.html Wayne On 5/7/07, Marcos [EMAIL PROTECTED] wrote: Hi all :-) Is it possible to invoke maven from an ant build script, such as a mvn custom task ? Is this the right approach to perform that ? Thank you very much -- Marcos H. W. Softing Systems Systems Analyst +55 11 38770360 /** * @see https://jaxb2-commons.dev.java.net */ /** * ...Use the Force ...;-) */ * * @see http://www.gentoo.org/ */ - 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: axistools-maven-plugin question
Wayne, Are you saying that I can pass a dependencies tag under the plugin in the pom? Thanks, David Williams Software Configuration Engineer 205-271-6159
Clearcase history shows limited information in build results
History on the build result only shows file modified, but not the revision number, comment and who changed it. I think the problem might be that the call to get history is executed from the top directory working-directory and not the subdirectory that contains the pom.xml. Does anyone else see this problem? Peter Hayes Architecture Shared Technology Services | Fidelity Investments Management Technology
Re: Clearcase history shows limited information in build results
I can't say that I've already seen this pb because I don't use Clearcase, but we need to update Continuum to run commands from the subdirectory. Emmanuel Hayes, Peter a écrit : History on the build result only shows file modified, but not the revision number, comment and who changed it. I think the problem might be that the call to get history is executed from the top directory working-directory and not the subdirectory that contains the pom.xml. Does anyone else see this problem? Peter Hayes Architecture Shared Technology Services | Fidelity Investments Management Technology
what's the right way to recombine several jars?
Anyone know how I'd unpack a couple of jars and recombine them with my source as an artifact? 1. unpack foo.jar 2. compile my code 3. include foo/bar/... with my code as end.jar -- Peter Kahn [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED] http://kahnstipation.blogspot.com | http://analogoustendencies.blogspot.com/ Awareness - Intention - Action
Re: axistools-maven-plugin question
Yes, see the POM Reference: http://maven.apache.org/pom.html#Plugins Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Wayne, Are you saying that I can pass a dependencies tag under the plugin in the pom? Thanks, David Williams Software Configuration Engineer 205-271-6159 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: what's the right way to recombine several jars?
maven-dependency-plugin and / or maven-assembly-plugin Both are well documented on the Maven site. Wayne On 5/7/07, Peter Kahn [EMAIL PROTECTED] wrote: Anyone know how I'd unpack a couple of jars and recombine them with my source as an artifact? 1. unpack foo.jar 2. compile my code 3. include foo/bar/... with my code as end.jar -- Peter Kahn [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED] http://kahnstipation.blogspot.com | http://analogoustendencies.blogspot.com/ Awareness - Intention - Action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integration tests in Maven 2
Thank you, much appreciated. I will use the solution in the post. Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
Re: Integration tests in Maven 2
Because we need to define the test source code location in one place,
testSourceDirectory, in the POM, will adding both a unit tests
location and an integration tests location in a testResources element
work to include both the unit tests and integration tests source code,
like shown below? Thank you.
testSourceDirectory${basedir}/src/alltests/testSourceDirectory
testResources
testResource
directory${basedir}/src/alltests/unittests/directory
/testResource
testResource
directory${basedir}/src/alltests/integrationtests/directory
/testResource
/testResources
This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law. If
you are not the intended recipient, you should delete this message.
Any disclosure, copying, or distribution of this message, or the taking of any
action based on it, is strictly prohibited. [v.E.1]
Assembly problem: Error Not a v4.0.0 POM
I have an error that I don't understand. I have a maven 1 project that builds a jar file called pps-3.0.2.jar. The jar (and it's pom) are moved into my legacy style repository. I have a maven 2 project that depends on pps-3.0.2. It compiles and tests the code fine. During the assembly it is suppose to creates a directory of dependent jar files and it blows up with the message: - Error building POM (may not be this project's POM). Project ID: ebs:pps POM Location: /home/chelck/.m2/repository/ebs/pps/3.0.2/pps-3.0.2.pom Reason: Not a v4.0.0 POM. --- Running with -X doesn't supply any more usefull info. In a sense the error is correct: pps-3.0.2.pom is not v4.0.0 -- it's legacy. So why is mvn trying to build it's POM and why doesn't it realize it's a legacy pom? Thanks, Christopher Helck ** This communication and all information (including, but not limited to, market prices/levels and data) contained therein (the Information) is for informational purposes only, is confidential, may be legally privileged and is the intellectual property of ICAP plc and its affiliates (ICAP) or third parties. No confidentiality or privilege is waived or lost by any mistransmission. The Information is not, and should not be construed as, an offer, bid or solicitation in relation to any financial instrument or as an official confirmation of any transaction. The Information is not warranted, including, but not limited, as to completeness, timeliness or accuracy and is subject to change without notice. ICAP assumes no liability for use or misuse of the Information. All representations and warranties are expressly disclaimed. The Information does not necessarily reflect the views of ICAP. Access to the Information by anyone else other than the recipient is unauthorized and any disclosure, copying, distribution or any action taken or omitted to be taken in reliance on it is prohibited. If you receive this message in error, please immediately delete it and all copies of it from your system, destroy any hard copies of it and notify the sender. **
Maven vs. Scripted Build Systems
How does maven's declarative convention over configuration stack up against scripted solutions like buildr, groovy/ant or scons when it comes to maintenance costs for large projects? Is there anyone out there who is involved with a large complex project who can weigh in on how sustainable maven has been and how much work it has required to keep bit rot at bay? I have a project with 20+ sub-projects which I'm planning to convert from a home grown maven like system written in shell scripts and ant to maven. It seemed like a no brainer, the system's process matched maven's model quite well. Then I read these two pieces and while I disagree with them I need to ask... how sustainable is maven for large scale projects http://blog.labnotes.org/2007/04/18/introducing-buildr-or-how-we-cured-our-maven-blues/ http://blog.labnotes.org/2007/05/03/buildr-or-when-ruby-is-faster-than-java/ Scripted solution can be much more concise than declarative, but they can also become very complex very quickly. I'm of the belief that I can use or misuse any technology and create a smoothly running system or a maintenance nightmare. I just want reassurance that maven doesn't have some hidden cost, or how best to avoid the pitfalls if it does. FYI, I already know about the Better Builds with Maven and the sonatype books and am working my way through them. Thanks for the help... -- Peter Kahn [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED] http://kahnstipation.blogspot.com | http://analogoustendencies.blogspot.com/ Awareness - Intention - Action
Re: Filtering resources into a directory other than classes for a webapp?
I was looking for the same solution, and the war-plugin seemed right.
But my config files were always put in the war root instead of the folder i
specified.
The solution for me was to use the 2.0.2 version of the war-plugin instead
of 2.0.
Heinrich Nirschl wrote:
On Fri, 2007-04-27 at 15:17 -0400, Jared Blitzstein wrote:
Thanks, I've read that as well as http://maven.apache.org/guides/
getting-started/index.html#How%20do%20I%20filter%20resource%20files
and it's basically the same thing as the WAR plugin...I believe.
Since I need this on both the WAR and the exploded app for jetty, I'm
not sure if the war plugin is what I need to be using. But the files
are actually being filtered, it's just they're not ending up in /WEB-
INF/config/ like I want. They're going to /WEB-INF/classes/WEB-INF/
config/. Here is the snippet from my pom
filters
filtersrc/main/filters/${env}.var/filter
/filters
resources
resource
directorysrc/main/webapp/WEB-INF/config/directory
filteringtrue/filtering
targetPathWEB-INF/config//targetPath
/resource
/resources
Any ideas?
I have not tried this, but according to the documentation a
configuration similar to this for the war plugin should work:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
filters
filtersrc/main/filters/${env}.var/filter
/filters
webResources
resource
!-- the config files you want to filter should be in this
directory --
directoryconfigurations/directory
targetPathWEB-INF/config/targetPath
!-- enable filtering --
filteringtrue/filtering
/resource
/webResources
/configuration
/plugin
- Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Filtering-resources-into-a-directory-other-than-classes-for-a-webapp--tf3658613s177.html#a10360724
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: axistools-maven-plugin question
Wayne, Thanks for your help. That got me pass my first error. Below is the error I got when I tried again. For some reason, it doesn't like the extraClasses entry. Do you have any thoughts? Failed to configure plugin parameters for: org.codehaus.mojo:axistools-maven-plugin:1.0 (found static expression: 'classname' which may act as a default value). Cause: Cannot assign configuration entry 'extraClasses' to 'class java.util.ArrayList' from 'classname', which is of type class java.lang.String Thanks, David Wayne Fay [EMAIL PROTECTED] 05/07/2007 10:24 AM Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: axistools-maven-plugin question Yes, see the POM Reference: http://maven.apache.org/pom.html#Plugins Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Wayne, Are you saying that I can pass a dependencies tag under the plugin in the pom? Thanks, David Williams Software Configuration Engineer 205-271-6159 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you.
Trunk is missing files
The trunk is missing admin files for networkProxy, database, and others in the WEB-INF/jsp/admin folder... Could this get updated so the latest code can be used? Thanks!
Re: axistools-maven-plugin question
Please send your complete plugin/ configuration so we can look at it, but no guarantees as I don't use that plugin myself. There is a decent chance you will need to receive support on this specific issue from the author of the axistools-m-p Mojo itself. Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Wayne, Thanks for your help. That got me pass my first error. Below is the error I got when I tried again. For some reason, it doesn't like the extraClasses entry. Do you have any thoughts? Failed to configure plugin parameters for: org.codehaus.mojo:axistools-maven-plugin:1.0 (found static expression: 'classname' which may act as a default value). Cause: Cannot assign configuration entry 'extraClasses' to 'class java.util.ArrayList' from 'classname', which is of type class java.lang.String Thanks, David Wayne Fay [EMAIL PROTECTED] 05/07/2007 10:24 AM Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: axistools-maven-plugin question Yes, see the POM Reference: http://maven.apache.org/pom.html#Plugins Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Wayne, Are you saying that I can pass a dependencies tag under the plugin in the pom? Thanks, David Williams Software Configuration Engineer 205-271-6159 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] _ CONFIDENTIALITY: This email (including any attachments) may contain confidential, proprietary and privileged information, and unauthorized disclosure or use is prohibited. If you received this email in error, please notify the sender and delete this email from your system. Thank you. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven vs. Scripted Build Systems
I had worked before extensively with Ant, and I create a complete end-to-end build system. When I started to work with Maven, I noticed that I was able to version dependencies in a more organized manner, and that I was able to establish a folder structure which all projects shared. The site creation mechanism of Maven is more standardized than what needs to be done in Ant to create project websites. Also, if you ever need to use any Ant code in a Maven project, you could place the Ant code in the maven-antrun-plugin. Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not the intended recipient, you should delete this message. Any disclosure, copying, or distribution of this message, or the taking of any action based on it, is strictly prohibited. [v.E.1]
axis2-wsdl2code-maven-plugin not working for me
Hello, I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Any help would be appreciated. Regards Jaish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Version number propogation
The relative path doesn't necessarily work once deployed. And its not guaranteed to be true -- you could checkout just the module rather than the entire project, and suddenly Maven can't find that parent since the relativePath is no longer accurate. If anything, I'd argue that relativePath should perhaps be removed. Wayne On 5/7/07, David Corbin [EMAIL PROTECTED] wrote: On Sunday 06 May 2007 19:20, Bryan Loofbourrow wrote: I believe that you are correct about not being able to parameterize the project parent tag, or so a co-worker tells me. He conjectures that the parent resolution is required before resolution of property names. That makes sense, since, in general, the value you're looking for could be defined in the parent pom, But when I provide a relativePath tag in parent declaration, that should allow be enough. In fact, if I provide rrelativePath all the artifact information provided should just be a safety check. David - 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: axis2-wsdl2code-maven-plugin not working for me
This plugin is a product of the Apache Axis group. Please direct support requests to them. Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Any help would be appreciated. Regards Jaish - 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: axis2-wsdl2code-maven-plugin not working for me
Thanks Wayne. Does Mavne provide any plug-in for Axis2. I could get the plug in for Axis 1 but not for axis 2 for building web service client. Or if some one can help me to suggest Mavnen plug in for axis2 Thanks Jaish -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 11:42 AM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me This plugin is a product of the Apache Axis group. Please direct support requests to them. Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Any help would be appreciated. Regards Jaish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: This plugin is a product of the Apache Axis group. Please direct support requests to them. Wayne, what you possibly don't know: I am the plugins author and I am not reading the Axis mailing lists. (Too much traffic.) Thanks, Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Use the -X option and let's see a stack trace or whatever useful information you can provide. -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin not working for me
Apologies. ;-) I clicked over to the Axis1 and Axis2 sites and it seems like they have (their own?) Maven plugins. So I figured this was the same one (??). Or not? Wayne On 5/7/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: This plugin is a product of the Apache Axis group. Please direct support requests to them. Wayne, what you possibly don't know: I am the plugins author and I am not reading the Axis mailing lists. (Too much traffic.) Thanks, Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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: axis2-wsdl2code-maven-plugin not working for me
Thanks for looking into Jochen. I am getting following error: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/neethi/Policy [INFO] [DEBUG] Trace java.lang.NoClassDefFoundError: org/apache/neethi/Policy at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) at org.apache.axis2.maven2.wsdl2code.WSDL2CodeMojo.execute(WSDL2CodeMojo.ja va:396) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:48 0) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.jav a:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Here is the plug-in details I am using. Let me know if I am missing something here? plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId executions execution goals goalwsdl2code/goal /goals /execution /executions configuration generateServerSidetrue/generateServerSide generateServerSideInterfacetrue/generateServerSideInterface generateAllClassestrue/generateAllClasses generateServiceXmltrue/generateServiceXml generateTestcasetrue/generateTestcase packageNamesome.package/packageName namespaceToPackagessome.package=some.package/namespaceToPackages wsdlFileC:\test.wsdl/wsdlFile outputDirectorysrc/main/outputDirectory syncModeboth/syncMode databindingNamexmlbeans/databindingName languagejava/language /configuration /plugin -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 11:54 AM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Use the -X option and let's see a stack trace or whatever useful information you can provide. -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: I clicked over to the Axis1 and Axis2 sites and it seems like they have (their own?) Maven plugins. So I figured this was the same one (??). Or not? The Axis 2 plugins are part of the Axis 2 project, because they are closely coupled with the Axis 2 libraries. Whether this decision made or makes sense, is questionable, of course, but to me it seemed the best way. Nevertheless, I am maintaining them here, because this is a list I am watching anyways. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin not working for me
I Jaish, I once saw that error in an attempt to try axis2. axis2 comes with a bunch of dependencies that i didn't find in the maven repository, Check in your downloaded axis2 zip file. I then uploaded each in my personnal 3rdparty repo. Raphaël PS, Maybe thoses dependencies are foundable in another repo, which i don't know about yet 2007/5/7, [EMAIL PROTECTED] [EMAIL PROTECTED]: Thanks for looking into Jochen. I am getting following error: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/neethi/Policy [INFO] [DEBUG] Trace java.lang.NoClassDefFoundError: org/apache/neethi/Policy at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) at org.apache.axis2.maven2.wsdl2code.WSDL2CodeMojo.execute(WSDL2CodeMojo.ja va:396) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:48 0) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.jav a:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Here is the plug-in details I am using. Let me know if I am missing something here? plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId executions execution goals goalwsdl2code/goal /goals /execution /executions configuration generateServerSidetrue/generateServerSide generateServerSideInterfacetrue/generateServerSideInterface generateAllClassestrue/generateAllClasses generateServiceXmltrue/generateServiceXml generateTestcasetrue/generateTestcase packageNamesome.package/packageName namespaceToPackagessome.package=some.package/namespaceToPackages wsdlFileC:\test.wsdl/wsdlFile outputDirectorysrc/main/outputDirectory syncModeboth/syncMode databindingNamexmlbeans/databindingName languagejava/language /configuration /plugin -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 11:54 AM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Use the -X option and let's see a stack trace or whatever useful information you can provide. -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: [INFO] org/apache/neethi/Policy [INFO] [DEBUG] Trace java.lang.NoClassDefFoundError: org/apache/neethi/Policy at Please create a Jira issue at http://issues.codehaus.org/jira in the Axis2 project, component tools. Attach the complete log file there and let me know the issue number. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin not working for me
Try adding a dependency on (below) inside the plugin: plugin ... dependencies dependency groupIdorg.apache.ws.commons.neethi/groupId artifactIdneethi/artifactId version2.0/version /dependency /dependencies /plugin I found this by entering the class identified by the NoClassDef into www.mvnrepository.com. Not sure if it will solve all your problems. Wayne On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Thanks for looking into Jochen. I am getting following error: [INFO] [ERROR] FATAL ERROR [INFO] [INFO] org/apache/neethi/Policy [INFO] [DEBUG] Trace java.lang.NoClassDefFoundError: org/apache/neethi/Policy at org.apache.axis2.wsdl.codegen.CodeGenerationEngine.init(CodeGeneration Engine.java:103) at org.apache.axis2.maven2.wsdl2code.WSDL2CodeMojo.execute(WSDL2CodeMojo.ja va:396) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginMa nager.java:443) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Default LifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(DefaultLifecycleExecutor.java:48 0) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultL ifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle Failures(DefaultLifecycleExecutor.jav a:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifec ycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] Here is the plug-in details I am using. Let me know if I am missing something here? plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId executions execution goals goalwsdl2code/goal /goals /execution /executions configuration generateServerSidetrue/generateServerSide generateServerSideInterfacetrue/generateServerSideInterface generateAllClassestrue/generateAllClasses generateServiceXmltrue/generateServiceXml generateTestcasetrue/generateTestcase packageNamesome.package/packageName namespaceToPackagessome.package=some.package/namespaceToPackages wsdlFileC:\test.wsdl/wsdlFile outputDirectorysrc/main/outputDirectory syncModeboth/syncMode databindingNamexmlbeans/databindingName languagejava/language /configuration /plugin -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 11:54 AM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I still some help to use the axis2 plug in. Looks like this plug in is missing some of the dependency and I am not sure of it. Use the -X option and let's see a stack trace or whatever useful information you can provide. -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
Re: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: Try adding a dependency on (below) inside the plugin: This might be a possible workaround, but - Neethi is a transitive dependency of the plugin. It should be present. If not, there's most possibly an error in the POM files, which should be cured. - Axis is extremely sensitive with version numbers. Whether 2.0 is fine, depends clearly on the plugin version. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: axis2-wsdl2code-maven-plugin not working for me
My understanding is that plug in POM should have all the possible dependency defined for it what ever is required? And it should be downloaded automatically to local repository when do the build. -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 12:26 PM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: Try adding a dependency on (below) inside the plugin: This might be a possible workaround, but - Neethi is a transitive dependency of the plugin. It should be present. If not, there's most possibly an error in the POM files, which should be cured. - Axis is extremely sensitive with version numbers. Whether 2.0 is fine, depends clearly on the plugin version. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: My understanding is that plug in POM should have all the possible dependency defined for it what ever is required? And it should be downloaded automatically to local repository when do the build. You are right - if the POM is alright. And that is exactly what I am guessing. For example, I know of at least one POM file from Axis 2 1.1 that had problems. Which is why I would like to see the complete log with all version numbers. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: axis2-wsdl2code-maven-plugin not working for me
Understood. I won't interfere any more in this thread -- I've done enough already. ;-) Wayne On 5/7/07, Jochen Wiedmann [EMAIL PROTECTED] wrote: On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: Try adding a dependency on (below) inside the plugin: This might be a possible workaround, but - Neethi is a transitive dependency of the plugin. It should be present. If not, there's most possibly an error in the POM files, which should be cured. - Axis is extremely sensitive with version numbers. Whether 2.0 is fine, depends clearly on the plugin version. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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]
Getting maven to run a file after install
Hello, Is it possible to have maven execute a bash file after it finished installing (compiling)? I have mavenide in NetBeans, and i'd like it to run a bash script that deploys the project. I'm not sure how to make it run that bash script after install...or anywhere from netbeans. Thanks -- View this message in context: http://www.nabble.com/Getting-maven-to-run-a-file-after-install-tf3705879s177.html#a10364078 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: Getting maven to run a file after install
Are you using Mevenide2-Netbeans (and hence Maven 2.0.X)? If so, you can use the exec-maven-plugin[1], bound (in pom.xml) to the install (compile) phase to achieve what you want. If you're using Mevenide for Maven 1.X, you could set up a pre-goal to do what you want, in maven.xml. Hope it helps, Steve [1] http://mojo.codehaus.org/exec-maven-plugin/ Arrowx7 wrote: Hello, Is it possible to have maven execute a bash file after it finished installing (compiling)? I have mavenide in NetBeans, and i'd like it to run a bash script that deploys the project. I'm not sure how to make it run that bash script after install...or anywhere from netbeans. Thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: axis2-wsdl2code-maven-plugin not working for me
I am sure Neethi is not there in the POM for axis2 plugin What version of plug in you suggest which is more stable? I was trying with 1.1.1 Also where to find which version of dependency(Neethi) should be used for 1.1.1? FYI, I already added wsdl4j dependency in the POM. Regards Jaish -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 12:26 PM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me On 5/7/07, Wayne Fay [EMAIL PROTECTED] wrote: Try adding a dependency on (below) inside the plugin: This might be a possible workaround, but - Neethi is a transitive dependency of the plugin. It should be present. If not, there's most possibly an error in the POM files, which should be cured. - Axis is extremely sensitive with version numbers. Whether 2.0 is fine, depends clearly on the plugin version. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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: [ANN] Maven Release Plugin 2.0-beta-5 Released
Thanks for the release, Stephane. After I upgraded, however, I noticed
the release:perform task no longer honors the executable permission bit
set on my some of my files. My SCM is CVS. I looked in Jira but
couldn't find a bug for it, though something makes me think it's a known
problem with the SCM plugin. Though something else makes me think the
previous release plugin version checked the file out correctly, i.e.
with the exec bit set.
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent with
updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots, causing
problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's value
during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for
modules
* [MRELEASE-122] - Versionless Extension causes NullPointerException
in release:prepare
* [MRELEASE-128] - SCM properties being replaced during
release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with ${pom.groupId}
not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same
parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects'
subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency snapshot
check
* [MRELEASE-197] - Release plugin documentation on maven.apache.org
has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are not
updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after
release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor
environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots of the release plugin
* [MRELEASE-145] - release:prepare requires all modules to be
SNAPSHOTS
* [MRELEASE-183] - should report all unresolved dependencies, not just
the first encountered.
* [MRELEASE-208] - Support for ClearCase, and other SCMs that do
checkout projects to subdirectories of the checkout directory
* [MRELEASE-214] - scm:tag with scmCommentPrefix
* [MRELEASE-220] - Add property to keep released versions for
dependencies
** New Feature
* [MRELEASE-130] - Create a model for a release
* [MRELEASE-157] - Share version for multi-module releases
* [MRELEASE-169] - Provide a mechanism to undo the effects of prepare
** Task
* [MRELEASE-141] - Review Plugin Documentation
* [MRELEASE-162] - Move all release core code in maven/shared
Enjoy!
- The Maven Team
-
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: [ANN] Maven Release Plugin 2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I noticed
the release:perform task no longer honors the executable permission bit
set on my some of my files. My SCM is CVS. I looked in Jira but
couldn't find a bug for it, though something makes me think it's a known
problem with the SCM plugin. Though something else makes me think the
previous release plugin version checked the file out correctly, i.e.
with the exec bit set.
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent with
updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots, causing
problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's value
during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for
modules
* [MRELEASE-122] - Versionless Extension causes NullPointerException
in release:prepare
* [MRELEASE-128] - SCM properties being replaced during
release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with ${pom.groupId}
not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same
parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects'
subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency snapshot
check
* [MRELEASE-197] - Release plugin documentation on maven.apache.org
has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are not
updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after
release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor
environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots of the release plugin
* [MRELEASE-145] - release:prepare requires all modules to be
SNAPSHOTS
* [MRELEASE-183] - should report all unresolved dependencies, not just
the first encountered.
* [MRELEASE-208] - Support for ClearCase, and other SCMs that do
checkout projects to subdirectories of the checkout directory
* [MRELEASE-214] - scm:tag with scmCommentPrefix
* [MRELEASE-220] - Add property to keep released versions for
dependencies
** New Feature
* [MRELEASE-130] - Create a model for a release
* [MRELEASE-157] - Share version for multi-module releases
* [MRELEASE-169] - Provide a mechanism to undo the effects of prepare
** Task
* [MRELEASE-141] - Review Plugin Documentation
* [MRELEASE-162] - Move all release core code in maven/shared
Enjoy!
- The Maven Team
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL
Re: Maven vs. Scripted Build Systems
Hello, I have been using maven for several years now, and switch from custom grown ant scripts to maven1.0 in 200? (can't recall exactly the year). The reason we switched is the usual one: - growing complexity and fragmentation of scripts - uniformity and industrialisation - standard way of building, structuring and documenting projects. - reporting This was true in maven1.X and is all the more so in maven2. I have set up maven on a project with +50 sub projects using custom archetype: maven is great for industrializing development, when you have a base project and several different modules that are built the same. The profile system is extremely flexible and allows you to write in a single place configurations for different environments (eg. development, testing, production). The greatest feature, in my opinion, is the reporting system. It can be somewhat tricky to put at work, but when properly configured, it generates consistent information on your system, centralizes documentation, project management info and quality reports. With continuum and (hopefully) archiva maturing, this makes for a complete production system. There are drawbacks to maven's approach: lack of flexibility, tricky configuration, centralized process, uniform way of building; and not all plugins/components work as advertized but the list is responsive. My 50 cents -- OQube software engineering \ génie logiciel Arnaud Bailly, PhD \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven Release Plugin 2.0-beta-5 Released
So is there no way to make the Java client honor exec permissions? Any
recommended best practice for a workaround?
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:45 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I
noticed the release:perform task no longer honors the executable
permission bit set on my some of my files. My SCM is CVS. I looked
in Jira but couldn't find a bug for it, though something makes me
think it's a known problem with the SCM plugin. Though something else
makes me think the previous release plugin version checked the file out
correctly, i.e.
with the exec bit set.
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent with
updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots, causing
problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's
value during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for
modules
* [MRELEASE-122] - Versionless Extension causes NullPointerException
in release:prepare
* [MRELEASE-128] - SCM properties being replaced during
release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with
${pom.groupId} not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same
parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects'
subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency snapshot
check
* [MRELEASE-197] - Release plugin documentation on maven.apache.org
has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are not
updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after
release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor
environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots of the release plugin
* [MRELEASE-145] - release:prepare requires all modules to be
SNAPSHOTS
* [MRELEASE-183] - should report all unresolved dependencies, not
just the first encountered.
* [MRELEASE-208] - Support for ClearCase, and other SCMs that do
checkout projects to subdirectories of the checkout directory
* [MRELEASE-214] - scm:tag with scmCommentPrefix
* [MRELEASE-220] - Add property to keep released versions for
dependencies
** New Feature
* [MRELEASE-130] - Create a model for a release
* [MRELEASE-157] - Share version for multi-module releases
* [MRELEASE-169] - Provide a mechanism to undo the effects of
prepare
** Task
* [MRELEASE-141] - Review Plugin Documentation
* [MRELEASE-162] - Move all release core code in maven/shared
Enjoy!
Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
I don't think, but you can use your cvs executable by adding a system property
on the command line:
mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare
mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:perform
I'll try to improve it in the next version.
Emmanuel
Crossley, Jim a écrit :
So is there no way to make the Java client honor exec permissions? Any
recommended best practice for a workaround?
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:45 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I
noticed the release:perform task no longer honors the executable
permission bit set on my some of my files. My SCM is CVS. I looked
in Jira but couldn't find a bug for it, though something makes me
think it's a known problem with the SCM plugin. Though something else
makes me think the previous release plugin version checked the file out correctly, i.e.
with the exec bit set.
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven Release
Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent with
updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots, causing
problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's
value during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for
modules
* [MRELEASE-122] - Versionless Extension causes NullPointerException
in release:prepare
* [MRELEASE-128] - SCM properties being replaced during
release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with
${pom.groupId} not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same
parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects'
subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency snapshot
check
* [MRELEASE-197] - Release plugin documentation on maven.apache.org
has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are not
updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after
release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor
environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots of the release plugin
* [MRELEASE-145] - release:prepare requires all modules to be
SNAPSHOTS
* [MRELEASE-183] - should report all unresolved dependencies, not
just the first encountered.
* [MRELEASE-208] - Support for ClearCase, and other SCMs that do
checkout projects to subdirectories of the checkout directory
* [MRELEASE-214] - scm:tag with scmCommentPrefix
* [MRELEASE-220] - Add property to keep released versions for
dependencies
** New Feature
* [MRELEASE-130] - Create a model for a release
* [MRELEASE-157] - Share
RE: [ANN] Maven Release Plugin 2.0-beta-5 Released
Thanks Emmanuel,
To save me some typing, could I also put that in the pom? Something like this?
properties
maven.scm.provider.cvs.implementationcvs_native/maven.scm.provider.cvs.implementation
/properties
Or do I need it in a configuration element of either the release or the scm
plugin?
Thanks,
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:55 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
I don't think, but you can use your cvs executable by adding a system property
on the command line:
mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare mvn
-Dmaven.scm.provider.cvs.implementation=cvs_native release:perform
I'll try to improve it in the next version.
Emmanuel
Crossley, Jim a écrit :
So is there no way to make the Java client honor exec permissions? Any
recommended best practice for a workaround?
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:45 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I
noticed the release:perform task no longer honors the executable
permission bit set on my some of my files. My SCM is CVS. I looked
in Jira but couldn't find a bug for it, though something makes me
think it's a known problem with the SCM plugin. Though something
else makes me think the previous release plugin version checked the file out
correctly, i.e.
with the exec bit set.
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent
with updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots,
causing problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's
value during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for
modules
* [MRELEASE-122] - Versionless Extension causes
NullPointerException in release:prepare
* [MRELEASE-128] - SCM properties being replaced during
release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with
${pom.groupId} not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same
parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects'
subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency
snapshot check
* [MRELEASE-197] - Release plugin documentation on maven.apache.org
has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are
not updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after
release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor
environment
** Improvement
* [MRELEASE-112] - release plugin should
Re: axis2-wsdl2code-maven-plugin not working for me
On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am sure Neethi is not there in the POM for axis2 plugin That's fine, Neethi is a transitive dependency, inherited from axis2-kernel or whatever. What version of plug in you suggest which is more stable? I was trying with 1.1.1 Current version is 1.2. As I wrote, please create a bug report and attach the complete log file. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
It isn't possible yet.
Crossley, Jim a écrit :
Thanks Emmanuel,
To save me some typing, could I also put that in the pom? Something like this?
properties
maven.scm.provider.cvs.implementationcvs_native/maven.scm.provider.cvs.implementation
/properties
Or do I need it in a configuration element of either the release or the scm
plugin?
Thanks,
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:55 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
I don't think, but you can use your cvs executable by adding a system property
on the command line:
mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare mvn
-Dmaven.scm.provider.cvs.implementation=cvs_native release:perform
I'll try to improve it in the next version.
Emmanuel
Crossley, Jim a écrit :
So is there no way to make the Java client honor exec permissions? Any
recommended best practice for a workaround?
Jim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: Monday, May 07, 2007 4:45 PM
To: Maven Users List
Subject: Re: [ANN] Maven Release Plugin 2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I
noticed the release:perform task no longer honors the executable
permission bit set on my some of my files. My SCM is CVS. I looked
in Jira but couldn't find a bug for it, though something makes me
think it's a known problem with the SCM plugin. Though something
else makes me think the previous release plugin version checked the file out correctly, i.e.
with the exec bit set.
Obviously, this problem only applies on *nix systems.
Jim
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
Behalf Of Stephane Nicoll
Sent: Friday, May 04, 2007 2:09 PM
To: Maven Users List
Subject: [ANN] Maven Release Plugin 2.0-beta-5 Released
The Maven team is pleased to announce the release of the Maven
Release Plugin, version 2.0-beta-5
http://maven.apache.org/plugins/maven-release-plugin/
Release Notes - Maven 2.x Release Plugin - Version 2.0-beta-5
** Bug
* [MRELEASE-3] - release:prepare should not require multimodule
artifacts to be in the local repository
* [MRELEASE-6] - Multiproject Release: No check in
* [MRELEASE-16] - release-pom is changed too much
* [MRELEASE-35] - release plugin doesn't tag correctly with
svn+ssh when remote and local username don't match
* [MRELEASE-90] - Exception if version is SNAPSHOT
* [MRELEASE-91] - Updating of dependencyManagement inconsistent
with updating of dependencies with regard to SNAPSHOTs
* [MRELEASE-94] - Modified Parent POM is not commited
* [MRELEASE-107] - scm.url gets translated incorrectly during release
* [MRELEASE-110] - release:prepare generates tags with dots,
causing problems with CVS
* [MRELEASE-114] - ${project.artifactId} was replaced with it's
value during release:perform
* [MRELEASE-115] - Issue URL on pom is incorrect
* [MRELEASE-116] - Wrong SCM info put by the release plugin for
modules
* [MRELEASE-122] - Versionless Extension causes
NullPointerException in release:prepare
* [MRELEASE-128] - SCM properties being replaced during
release:perform
* [MRELEASE-131] - release:prepare failed in 'cvs ... commit'
phase for multi-module build
* [MRELEASE-137] - proposed SCM release tag or label in multiproject
* [MRELEASE-142] - Batch mode release plugin uses an invalid tag
* [MRELEASE-144] - Release plugin did not ask for a Subversion tag
* [MRELEASE-147] - Version number for a dependency with
${pom.groupId} not updated in multi-module.
* [MRELEASE-151] - All child modules are forced to share the same
parent POM
* [MRELEASE-160] - The next snapshot version is not used un submodules
* [MRELEASE-168] - All submodule projects must be from the same
subversion repository
* [MRELEASE-180] - Rewritten poms loose comments
* [MRELEASE-190] - scmTagPhase scm comment when creating the
branch/tag directory uses the prefix [maven-scm]
* [MRELEASE-191] - Certain tests fail when checked-out in 'projects'
subdir
* [MRELEASE-194] - SNAPSHOT as property bypasses dependency
snapshot check
* [MRELEASE-197] - Release plugin documentation on maven.apache.org
has broken link to release:rollback
* [MRELEASE-202] - snapshot versions in dependencyManagement are
not updated
* [MRELEASE-209] - Snapshot versions are not restored correctly on
next development version
* [MRELEASE-219] - Spurious warnings given when a release contains
subversion externals
* [MRELEASE-221] - XML header missing in modified POM after
release:prepare
* [MRELEASE-222] - Wrong default tag name when used in a reactor
environment
** Improvement
* [MRELEASE-112] - release plugin should have option to ignore
snapshots
Creating WebSphere Specific Config Files
Hello, I would like to create WebSphere specific application.xml and related ibm-application-bnd.xmi and MANIFEST.MF files. How do I this achieve this with maven? I tried maven-ear-plugin but unable to create the WebSphere specific files. Also I'm thinking of using some copy plugins (if one available) but not sure whether it's an appropriate way to do it. Any thoughts/suggestions are appreciated. Bala.
Re: Creating WebSphere Specific Config Files
are you just trying to include the xmi file and application.xml after you edit it? If so, just add those files into your ./module/src/main/resources directory You can then also filter some properties at build time. On 5/7/07, Bala Rajamani [EMAIL PROTECTED] wrote: Hello, I would like to create WebSphere specific application.xml and related ibm-application-bnd.xmi and MANIFEST.MF files. How do I this achieve this with maven? I tried maven-ear-plugin but unable to create the WebSphere specific files. Also I'm thinking of using some copy plugins (if one available) but not sure whether it's an appropriate way to do it. Any thoughts/suggestions are appreciated. Bala. -- --- 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 ---
Snapshot repository
What's the difference between a regular repository and a snapshot repository as specified under distributionManagement? I've tried using both types, but I didn't see any difference... Also, does ending the version number of a file in SNAPSHOT have something to do with this? Is it okay to end a version number with SNAPSHOT in a regular repository, or end without SNAPSHOT in a snapshot repository...? Thanks. -- View this message in context: http://www.nabble.com/Snapshot-repository-tf3706438s177.html#a10366009 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven Embedder Example?
Does anyone have a Maven Embedder example that runs archetype:create? I'd like to create an archetype, run a plugin and verify that files are created in the new project. I could run the archetype creation and plugin with Ant, but that doesn't seem to be a very good way to test the code generation plugin I'm writing. Thanks, Matt -- View this message in context: http://www.nabble.com/Maven-Embedder-Example--tf3706476s177.html#a10366156 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: Snapshot repository
Generally people don't like to mix SNAPSHOT artifacts with released artifacts. So the Snapshot repo and version number stuff just helps organize/manage that. You can *do* whatever you want -- its just not necessarily a build management best practice. I just would advise you to think long and hard about what you're about to do before doing it, though. Wayne On 5/7/07, lightbulb432 [EMAIL PROTECTED] wrote: What's the difference between a regular repository and a snapshot repository as specified under distributionManagement? I've tried using both types, but I didn't see any difference... Also, does ending the version number of a file in SNAPSHOT have something to do with this? Is it okay to end a version number with SNAPSHOT in a regular repository, or end without SNAPSHOT in a snapshot repository...? Thanks. -- View this message in context: http://www.nabble.com/Snapshot-repository-tf3706438s177.html#a10366009 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: Snapshot repository
lightbulb432 wrote: Also, does ending the version number of a file in SNAPSHOT have something to do with this? Reading this, I don't think you know what a SNAPSHOT version means. A SNAPSHOT is every build between two released versions. This way, you can never be sure, that a new SNAPSHOT of a dependency or a plugin wouldn't break your build. (Normally a bad thing) Also, every SNAPSHOT build you deploy is put into the repository. (Snapshot repository). After a release, you can remove all the old SNAPSHOT versions. When separating SNAPSHOT builds and releases in different repositories, it is easier to keep watch on them. Hth, Nick Stolwijk Is it okay to end a version number with SNAPSHOT in a regular repository, or end without SNAPSHOT in a snapshot repository...? Thanks. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Please help - why doesn't my index.html get generated when generating my site?
No, I don't have a site descriptor. But I have been told that I don't need one for the index.html to be generated, yet I don't have one generated. Is this the case, or is a site descriptor required? If not, can anybody suggest why it isn't being generated? Thanks, Ian To: Maven Users List users@maven.apache.org Subject Re: Please help - why doesn't my index.html get generated when : generating my site? Hi Ian, I think (though you haven't said anything about your setup) that you don't have a site descriptor, the default location for which is src/site/site.xml. See http://maven.apache.org/guides/mini/guide-site.html for info about what can go in there. Here's a quick vanilla site descriptor that should get you started: ?xml version=1.0? project name=My Project bannerLeft nameMy Project/name /bannerLeft body menu ref=reports/ /body /project Hope it helps, Steve Ian Rowlands wrote: I'm using Maven 2.0.5. My sites have no customisation (which I won't do until I get this to work). I am getting the following generated: Apart from subdirectories, I get: checkstyle.html (plus checkstyle.rss) cpd.html and cpd.xml dependencies.html integration.html issue-tracking.html jdepend-report.html pmd.html and pmd.xml project-info.html project-reports.html surefire-report.html I'm using version 2.0-beta-5 of the web site plugin. I have been told that an index.html should be generated, and it is not. This is an issue because it is a multi-module project, and links on the parent project all link to the index.html of the sub-projects. So without the index.html nobody can navigate the site correctly. Any suggestions? Regards, Ian Rowlands Disclaimer: The information transmitted is intended only for the person or entity to which it is addressed and may contain confidential and/or privileged material. Any review, retransmission, dissemination or other use of, or taking of any action in reliance upon, this information by persons or entities other than the intended recipient is prohibited. If you received this in error, please contact the sender and delete the material from your computer. Privacy: If you are responding to this email or providing personal information to the SRO for the purposes of one of the Acts it administers, such information is used only for the purpose for which it was collected ( administration of SRO legislation ) and is protected by the Information Privacy Act 2000 and secrecy provisions contained in legislation administered by SRO. It is not disclosed otherwise than in accordance with the law. If you would like a copy of the SRO Privacy Policy please refer to SRO website (www.sro.vic.gov.au) or contact SRO on 9628 0556 and request a copy. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
EJB 3.0 + Maven 2.0 + maven-ejb-plugin + glassfish
I have a simple EJB 3.0 project with a stateless bean as follows:
The remote interface:
@Remote
public interface IssueBeanRemote {
public void createIssue();
}
The stateless EJB 3.0 bean:
@Stateless(mappedName = ejb/IssueBean)
public class IssueBean implements IssueBeanRemote {
public void createIssue() {
...
..
}
}
I checked out and installed the latest maven-ejb-plugin as shown here:
http://mail-archives.apache.org/mod_mbox/maven-users/200609.mbox/[EMAIL
PROTECTED]
I have the following in my pom.xml:
modelVersion4.0.0/modelVersion
groupIdmy.ejb/groupId
artifactIdcomponent/artifactId
version0.0.1/version
packagingejb/packaging
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
ejbVersion3.0/ejbVersion
/configuration
/plugin
..
mvn package cmopiles without any error messages. But when I deploy the
jar file into Glassfish I get the following error message:
[#|2007-05-07T17:22:54.542-0500|SEVERE|sun-appserver9.1|javax.enterprise.system.tools.deployment|_ThreadID=25;_ThreadName=Thread-47;_RequestID=3a898218-6f83-4579-b28d-5829b7e0ec01;|Exception
occured in J2EEC Phasejava.lang.IllegalArgumentException: Invalid ejb
jar
[/opt/glassfish/glassfish-v2-b42/domains/domain1/applications/j2ee-modules/my-ejb-component]:
it contains zero ejb.
I'd appreciate any help getting this deployment to work.
Thanks in advance.
-sud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Passing maven variables
We are currently passing the -Dserver= variable on the mvn command line.
This variable is referenced in the pom in the following manor.
resource
directorysrc/main/${server}/resources/directory
filteringtrue/filtering
/resource
Is it possible to set this variable in the settings.xml file and pass it
to the pom?
Thanks,
David Williams
Software Configuration Engineer
205-271-6159
RE: axis2-wsdl2code-maven-plugin not working for me
1.2 is not working is the syntex below is correct? groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.2/version Regards Jaish -Original Message- From: Jochen Wiedmann [mailto:[EMAIL PROTECTED] Sent: Monday, May 07, 2007 2:04 PM To: Maven Users List Subject: Re: axis2-wsdl2code-maven-plugin not working for me On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: I am sure Neethi is not there in the POM for axis2 plugin That's fine, Neethi is a transitive dependency, inherited from axis2-kernel or whatever. What version of plug in you suggest which is more stable? I was trying with 1.1.1 Current version is 1.2. As I wrote, please create a bug report and attach the complete log file. Jochen -- My cats know that I am a loser who goes out for hunting every day without ever returning as much as a single mouse. Fortunately, I've got a wife who's a real champ: She leaves the house and returns within half an hour, carrying whole bags full of meal. - 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: Maven Embedder Example?
I figured out how to generate an archetype programmatically (see code below).
Now I'm trying to execute goals w/in that project using MavenEmbedder. It
seems to *almost* works, except that a plugin with
extensionstrue/extensions is failing. Does the MavenEmbedder not
support plugins with extensions?
Thanks,
Matt
protected void createTestProject(String archetypeArtifactId, String
archetypeVersion) throws Exception {
MavenProject project = getMavenProject();
FileUtils.deleteDirectory(getTestFile(target/ +
project.getArtifactId()));
MapString, String parameters = new HashMapString, String();
parameters.put(groupId, project.getGroupId());
parameters.put(artifactId, project.getArtifactId());
parameters.put(version, 1.0-SNAPSHOT);
parameters.put(basedir, getTestFile(target).getAbsolutePath());
Archetype archetype = (Archetype) lookup(Archetype.ROLE);
ArtifactRepositoryLayout layout =
(ArtifactRepositoryLayout)
container.lookup(ArtifactRepositoryLayout.ROLE, default);
String mavenRepoLocal = project.getRepositories().get(0).toString();
ArtifactRepository localRepository = new
DefaultArtifactRepository(local, mavenRepoLocal, layout);
ListArtifactRepository remoteRepositories = new
ArrayListArtifactRepository();
String mavenRepoRemote = http://static.appfuse.org/repository;;
ArtifactRepository remoteRepository = new
DefaultArtifactRepository(remote, mavenRepoRemote, layout);
remoteRepositories.add(remoteRepository);
String archetypeGroupId = org.appfuse;
archetype.createArchetype(archetypeGroupId, archetypeArtifactId,
archetypeVersion, localRepository,
remoteRepositories, parameters);
}
mraible wrote:
Does anyone have a Maven Embedder example that runs archetype:create? I'd
like to create an archetype, run a plugin and verify that files are
created in the new project. I could run the archetype creation and plugin
with Ant, but that doesn't seem to be a very good way to test the code
generation plugin I'm writing.
Thanks,
Matt
--
View this message in context:
http://www.nabble.com/Maven-Embedder-Example--tf3706476s177.html#a10367706
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: Passing maven variables
I'd be more inclined to set it in profiles.xml, but sure, you can set
it in settings.xml if you want.
Read this for more details on profiles:
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
Wayne
On 5/7/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
We are currently passing the -Dserver= variable on the mvn command line.
This variable is referenced in the pom in the following manor.
resource
directorysrc/main/${server}/resources/directory
filteringtrue/filtering
/resource
Is it possible to set this variable in the settings.xml file and pass it
to the pom?
Thanks,
David Williams
Software Configuration Engineer
205-271-6159
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
problem with war plugin
hey.. cud u plz help me in solving this error.. The plugin 'org.apache.maven.plugins:maven-war-plugin' does not exist or no valid version could be found Thanks, KK -- View this message in context: http://www.nabble.com/problem-with-war-plugin-tf3707831s177.html#a10370291 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
