RE: j2ee sdk in repositories?
Hi Rick, You might be interested in http://mavenbook.xwiki.com/xwiki/bin/view/Main/J2eeDependencies Thanks -Vincent -Original Message- From: Rick Mann [mailto:[EMAIL PROTECTED] Sent: vendredi 26 août 2005 01:43 To: Maven Users List Subject: Re: j2ee sdk in repositories? On Aug 25, 2005, at 4:33 PM, dan tran wrote: you need to install that on your own remote repo. Sun License does not allow to install their j2ee files (jta, jdbc, jca,etc ) on ibiliio Thanks for the response. I figured it might be something like this. I don't suppose anyone's tried to convince Sun to host their own repo? (Which brings up a question I have not yet researched...is there a way to specify that certain repos are to be used for certain groupIds? In ant?) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] problem with plug-in auto-download
-Original Message- From: berndq [mailto:[EMAIL PROTECTED] Sent: vendredi 26 août 2005 10:13 To: Maven Users List Subject: Re: [m1] problem with plug-in auto-download Brett Porter wrote: That hasn't made it to the errata yet, maybe you could submit it? done Thanks a lot Bernd and sorry for the typo (it was my fault!). It'll be fixed in the next reprint. -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven EJB Plugin 1.7 released
We are pleased to announce the Maven EJB Plugin 1.7 release! http://maven.apache.org/reference/plugins/ejb/ EJB Plugin for Maven Changes in this version include: Fixed bugs: o Make the ejb creation work even if there are not sources. o Fixed default property values in the web site documentation. Issue: MPEJB-12. o EJB client jar can now be generated and deployed/installed automatically by the standard goals ( ejb, ejb:ejb, ejb:installand ejb:deploy). Previous goals dedicated to ejb client have been deprecated. There is a new property maven.ejb.client.generatewhich decides whether or not to generate the ejb client jar. It defaults to true. Issue: MPEJB-2. o Added new EJB type handler that supports ejband ejb-clienttypes. This fixes the bug with ejb:install/deploy-clientnot uploading the client jar. Issue: MPEJB-16. Thanks to H�¯�¿�½vard Bj�¯�¿�½stad. Changes: o By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common. To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven, http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-ejb-plugin -Dversion=1.7 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-ejb-plugin-1.7.jar Have fun! -The Maven EJB Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven 1 or 2 with J2EE/Hibernate/Jboss project ?
HOFLACK Alexandre on 25/08/05 08:49, wrote: Q1 : I initiate a Hibernate/jboss project. So, newbie with maven, i understand utility of maven. Could you explain me how to work with maven and hibernate, best practise to develop on eclipse ? Could you give me a link on a good example whicj i can download to start? Q2 : do i prefer maven 1 or 2 to begin ? It depends how complex your Hibernate implementation is going to be. If you can keep it really simple, then you could start with Maven 2. Remember though it is in alpha stage still. Beta stage is coming soon. So if you want to make use of much advanced functionality, it will take you much more time with M2 because it is not as well documented. For instance, what artifacts are you going to build? Is it all going to be package in a war file? Or do you need EJBs? If you use Maven 1.x, it will be quicker to implement because of the greater amount of docs and examples - check the website. However at some stage you will want to move to Maven 2 and then you will have to rewrite your maven config. Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Nightly Build
These builds are pretty handy, but they only consist of m2 core - what about the plugins? It appears you still need to bootstrap m2 to obtain the latest versions of these in your local repo. Mark On 19/08/05, Kevin McNamee [EMAIL PROTECTED] wrote: OK. Just what I need. Thanks. Could you add this link to the Downloads page at Maven 2? http://maven.apache.org/maven2/download.html I couldn't even find this link when googling maven2 nightly build Perhaps the Continuum should also be included? Much appreciated, Kevin -Original Message- From: Trygve Laugstøl [mailto:[EMAIL PROTECTED] Sent: 19 August 2005 14:38 To: Maven Users List Subject: Re: [m2] Nightly Build On Fri, Aug 19, 2005 at 02:34:57PM +0200, Kevin McNamee wrote: Hi, Is there somewhere I can download a nightly build of M2? We're building a new distribution on every commit. http://maven.zones.apache.org/~maven/builds/ -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Installing plugins
I've got a custom m2 plugin which I install successfully using the normal m2 install, but when I go to use the plugin I get the error below. If I copy the 'maven-tomcat-plugin-LATEST.version.txt' file to an identical parallel 'maven-tomcat-plugin-RELEASE.version.txt' file then everything works as expected - am I missing anything here? Cheers, Mark [INFO] Using local copy of plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' from: C:\Documents and Settings\mark\.m2\repository\org\apache\maven\plugins\plugins.xml [INFO] maven-tomcat-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-tomcat-plugin Downloading: http://repo1.maven.org/maven2/plugins/org/apache/maven/plugins/maven-tomcat-plugin/RELEASE/maven-tomcat-plugin-RELEASE.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins [WARNING] * Using defaults for missing POM org.apache.maven.plugins:maven-tomcat-plugin:pom:RELEASE * Downloading: http://repo1.maven.org/maven2/plugins/org/apache/maven/plugins/maven-tomcat-plugin/RELEASE/maven-tomcat-plugin-RELEASE.jar [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins [INFO] Cannot find mojo descriptor for: 'tomcat:undeploy' - Treating as non-aggregator. [INFO] [INFO] Building AWM CMS [INFO]task-segment: [tomcat:undeploy] [INFO] Downloading: http://repo1.maven.org/maven2/plugins/org/apache/maven/plugins/maven-tomcat-plugin/RELEASE/maven-tomcat-plugin-RELEASE.jar [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Main Error: Mojo could not be found - check that the goal name is correct org.apache.maven.plugins:maven-tomcat-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins Root error: Unable to download the artifact from any repository [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sat Aug 27 18:10:48 BST 2005 [INFO] Final Memory: 1M/3M [INFO] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Nightly Build
On Sat, Aug 27, 2005 at 06:04:41PM +0100, Mark Hobson wrote: These builds are pretty handy, but they only consist of m2 core - what about the plugins? It appears you still need to bootstrap m2 to obtain the latest versions of these in your local repo. That is true. We figured that most people that would like to try the latest Maven from the Subversion repository would do a normal checkout and built it themselfs. If there's a general demand for the same process for the plugin we might do it but since there's a significat job we won't do it without a real demand for it. -- Trygve signature.asc Description: Digital signature
Re: [m2] Nightly Build
On 27/08/05, Trygve Laugstøl [EMAIL PROTECTED] wrote: That is true. We figured that most people that would like to try the latest Maven from the Subversion repository would do a normal checkout and built it themselfs. If there's a general demand for the same process for the plugin we might do it but since there's a significat job we won't do it without a real demand for it. Sure no probs, it's just the overhead of getting a development team all building their own m2 rather than using a distributable. This won't be an issue once beta-1 is out (because naturally that will be bug-free ;) Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Nightly Build
On Sat, Aug 27, 2005 at 06:24:51PM +0100, Mark Hobson wrote: On 27/08/05, Trygve Laugstøl [EMAIL PROTECTED] wrote: That is true. We figured that most people that would like to try the latest Maven from the Subversion repository would do a normal checkout and built it themselfs. If there's a general demand for the same process for the plugin we might do it but since there's a significat job we won't do it without a real demand for it. Sure no probs, it's just the overhead of getting a development team all building their own m2 rather than using a distributable. This won't be an issue once beta-1 is out (because naturally that will be bug-free ;) Hopefully we'll get Continuum set up to build all the plugins continuously soon. -- Trygve signature.asc Description: Digital signature
[m2] CLI equivalent of @requiresDependencyResolution
I was wondering if there's any command-line equivalent of the @requiresDependencyResolution MOJO annotation? i.e. something like m2 -d compile to resolve all compile-scoped dependencies. This would be handy for downloading a project's dependencies when importing into eclipse. I understand executing a goal like eclipse:eclipse would achieve the same effect, but it'd be nice to do this directly. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] CLI equivalent of @requiresDependencyResolution
On Sat, Aug 27, 2005 at 06:33:50PM +0100, Mark Hobson wrote: I was wondering if there's any command-line equivalent of the @requiresDependencyResolution MOJO annotation? i.e. something like m2 -d compile to resolve all compile-scoped dependencies. This would be handy for downloading a project's dependencies when importing into eclipse. I understand executing a goal like eclipse:eclipse would achieve the same effect, but it'd be nice to do this directly. Yep we agree on that. I was sure that it was filed in JIRA already but it I was not able to find it right now, feel free to add it. -- Trygve signature.asc Description: Digital signature
Re: [m2] CLI equivalent of @requiresDependencyResolution
Cool, it's here for future reference: http://jira.codehaus.org/browse/MNG-799 Mark On 27/08/05, Trygve Laugstøl [EMAIL PROTECTED] wrote: On Sat, Aug 27, 2005 at 06:33:50PM +0100, Mark Hobson wrote: I was wondering if there's any command-line equivalent of the @requiresDependencyResolution MOJO annotation? i.e. something like m2 -d compile to resolve all compile-scoped dependencies. This would be handy for downloading a project's dependencies when importing into eclipse. I understand executing a goal like eclipse:eclipse would achieve the same effect, but it'd be nice to do this directly. Yep we agree on that. I was sure that it was filed in JIRA already but it I was not able to find it right now, feel free to add it. -- Trygve -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.1 (GNU/Linux) iD8DBQFDEKcE4EbM92cyCUURAli2AJ0dYhe0LWYPT3eXPDEyrCAAle1VXgCdE2W2 M7kZcuUiPt9iEG31Db4cBWs= =0A9/ -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m1] bootstrap build error
I have just removed all files and started from scratch. The same problems exist. Do any of the committers use bootstrap? This problem has existed for at least 3 weeks (I have been sporadically trying it). I recognize something could be wrong in my environment, but I have successfully been bootstrapping since pre-beta 1.1 days. I have been building with Java 1.5.0_04, if that matters (hasn't previously). -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 12:06 AM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error Hi Jeff, Yes it was these files ;-( The download of dependencies was broken. I had your problem some days ago, which was the use of a bad release of the maven model in the ejb plugin. But it was fixed :-( Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 03:21 À : 'Maven Users List' Objet : RE: [m1] bootstrap build error Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\Abstra ctArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec]
RE: [m1] bootstrap build error
I wonder if this could be related to the 503 (service unavailable) errors I have been getting from ibiblio periodically while trying to bootstrap Maven2... -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 15:51 To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I have just removed all files and started from scratch. The same problems exist. Do any of the committers use bootstrap? This problem has existed for at least 3 weeks (I have been sporadically trying it). I recognize something could be wrong in my environment, but I have successfully been bootstrapping since pre-beta 1.1 days. I have been building with Java 1.5.0_04, if that matters (hasn't previously). -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 12:06 AM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error Hi Jeff, Yes it was these files ;-( The download of dependencies was broken. I had your problem some days ago, which was the use of a bad release of the maven model in the ejb plugin. But it was fixed :-( Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 03:21 À : 'Maven Users List' Objet : RE: [m1] bootstrap build error Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\Abstra ctArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: class org.apache.maven.ejb.EJBArtifactTypeHandler [exec] [javac] public String constructRepositoryDirectoryPath(String type, Project project) throws MavenException [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav
RE: [m1] bootstrap build error
Are you having compile errors too, or something different like unable to download dependencies, or other? I'm getting compile errors on cant find classes (even though they exist!). -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 4:54 PM To: Maven Users List Subject: RE: [m1] bootstrap build error I wonder if this could be related to the 503 (service unavailable) errors I have been getting from ibiblio periodically while trying to bootstrap Maven2... -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 15:51 To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I have just removed all files and started from scratch. The same problems exist. Do any of the committers use bootstrap? This problem has existed for at least 3 weeks (I have been sporadically trying it). I recognize something could be wrong in my environment, but I have successfully been bootstrapping since pre-beta 1.1 days. I have been building with Java 1.5.0_04, if that matters (hasn't previously). -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 12:06 AM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error Hi Jeff, Yes it was these files ;-( The download of dependencies was broken. I had your problem some days ago, which was the use of a bad release of the maven model in the ejb plugin. But it was fixed :-( Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 03:21 À : 'Maven Users List' Objet : RE: [m1] bootstrap build error Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\Abstra ctArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:40: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac]
maven 2.0: scripting languages supported in xdoc files?
Hello I am currently using maven 2.0. I like to use for my project doumentation (site, xdoc) some scripting language. Is there a way to realiste that? I have read on the homepage that maven 2.0 supports beanshell or marmelade for scripting. Unfortunately I did not found any example for using scripts? May be you can show me such an example or how a preprocessing of the xdoc files can be done? thanks Joes - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Installing plugins
You can use --check-plugin-latest (I thought this was the default...) - Brett On 8/28/05, Mark Hobson [EMAIL PROTECTED] wrote: I've got a custom m2 plugin which I install successfully using the normal m2 install, but when I go to use the plugin I get the error below. If I copy the 'maven-tomcat-plugin-LATEST.version.txt' file to an identical parallel 'maven-tomcat-plugin-RELEASE.version.txt' file then everything works as expected - am I missing anything here? Cheers, Mark [INFO] Using local copy of plugins.xml (plugin mappings) for group: 'org.apache.maven.plugins' from: C:\Documents and Settings\mark\.m2\repository\org\apache\maven\plugins\plugins.xml [INFO] maven-tomcat-plugin: checking for updates from central-plugins [INFO] Retrieving release information for maven-tomcat-plugin Downloading: http://repo1.maven.org/maven2/plugins/org/apache/maven/plugins/maven-tomcat-plugin/RELEASE/maven-tomcat-plugin-RELEASE.pom [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins [WARNING] * Using defaults for missing POM org.apache.maven.plugins:maven-tomcat-plugin:pom:RELEASE * Downloading: http://repo1.maven.org/maven2/plugins/org/apache/maven/plugins/maven-tomcat-plugin/RELEASE/maven-tomcat-plugin-RELEASE.jar [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins [INFO] Cannot find mojo descriptor for: 'tomcat:undeploy' - Treating as non-aggregator. [INFO] [INFO] Building AWM CMS [INFO]task-segment: [tomcat:undeploy] [INFO] Downloading: http://repo1.maven.org/maven2/plugins/org/apache/maven/plugins/maven-tomcat-plugin/RELEASE/maven-tomcat-plugin-RELEASE.jar [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Main Error: Mojo could not be found - check that the goal name is correct org.apache.maven.plugins:maven-tomcat-plugin:RELEASE:maven-plugin from the specified remote repositories: http://repo1.maven.org/maven2/plugins Root error: Unable to download the artifact from any repository [INFO] [INFO] Total time: 1 second [INFO] Finished at: Sat Aug 27 18:10:48 BST 2005 [INFO] Final Memory: 1M/3M [INFO] - 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: [m1] bootstrap build error
Fixed. The recent changes to the EJB plugin worked for 1.0 and 1.1 at runtime, but only for 1.0 at build time. - Brett On 8/28/05, Jeff Jensen [EMAIL PROTECTED] wrote: Are you having compile errors too, or something different like unable to download dependencies, or other? I'm getting compile errors on can't find classes (even though they exist!). -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 4:54 PM To: Maven Users List Subject: RE: [m1] bootstrap build error I wonder if this could be related to the 503 (service unavailable) errors I have been getting from ibiblio periodically while trying to bootstrap Maven2... -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 15:51 To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I have just removed all files and started from scratch. The same problems exist. Do any of the committers use bootstrap? This problem has existed for at least 3 weeks (I have been sporadically trying it). I recognize something could be wrong in my environment, but I have successfully been bootstrapping since pre-beta 1.1 days. I have been building with Java 1.5.0_04, if that matters (hasn't previously). -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 12:06 AM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error Hi Jeff, Yes it was these files ;-( The download of dependencies was broken. I had your problem some days ago, which was the use of a bad release of the maven model in the ejb plugin. But it was fixed :-( Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 03:21 À : 'Maven Users List' Objet : RE: [m1] bootstrap build error Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\Abstra ctArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:31: cannot find symbol [exec] [javac] symbol: class ArtifactTypeHandler [exec] [javac] public class EJBArtifactTypeHandler implements ArtifactTypeHandler [exec] [javac]
RE: [m1] bootstrap build error
Success! Thank you Brett. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 11:03 PM To: Maven Users List Subject: Re: [m1] bootstrap build error Fixed. The recent changes to the EJB plugin worked for 1.0 and 1.1 at runtime, but only for 1.0 at build time. - Brett On 8/28/05, Jeff Jensen [EMAIL PROTECTED] wrote: Are you having compile errors too, or something different like unable to download dependencies, or other? I'm getting compile errors on can't find classes (even though they exist!). -Original Message- From: Allison, Bob [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 4:54 PM To: Maven Users List Subject: RE: [m1] bootstrap build error I wonder if this could be related to the 503 (service unavailable) errors I have been getting from ibiblio periodically while trying to bootstrap Maven2... -Original Message- From: Jeff Jensen [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 15:51 To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I have just removed all files and started from scratch. The same problems exist. Do any of the committers use bootstrap? This problem has existed for at least 3 weeks (I have been sporadically trying it). I recognize something could be wrong in my environment, but I have successfully been bootstrapping since pre-beta 1.1 days. I have been building with Java 1.5.0_04, if that matters (hasn't previously). -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Thursday, August 25, 2005 12:06 AM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error Hi Jeff, Yes it was these files ;-( The download of dependencies was broken. I had your problem some days ago, which was the use of a bad release of the maven model in the ejb plugin. But it was fixed :-( Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : jeudi 25 août 2005 03:21 À : 'Maven Users List' Objet : RE: [m1] bootstrap build error Thanks Arnaud. These are the new files pulled down: C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/core/trunk maven-1/core/trunk U maven-1\core\trunk\src\java\org\apache\maven\repository\Abstra ctArtifact.jav a U maven-1\core\trunk\src\bin\maven.bat U maven-1\core\trunk Checked out revision 239972. C:\devroot\reference\mavensvn co http://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk maven-1/plugins/trunk U maven-1\plugins\trunk\javadoc\xdocs\changes.xml U maven-1\plugins\trunk\pdf\xdocs\changes.xml Checked out revision 239972. And I get the same build errors. -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: Wednesday, August 24, 2005 6:30 PM To: 'Maven Users List' Subject: RE: [m1] bootstrap build error I fixed some errors on the core. If you can update it and re-launch the bootstrap. Arnaud -Message d'origine- De : Jeff Jensen [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 août 2005 14:36 À : 'Maven Users List' Objet : [m1] bootstrap build error I have been attempting to build m1 via bootstrap again, and have the following compile errors. I did not find the cause from a quick review, and am wondering if this is a known bootstrap problem before I spend more time with it. I have verified the classes exist, visual inspection found no problems. I am wondering about bootstrap classpath, etc.? From revision 239628. [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:20: cannot find symbol [exec] [javac] symbol : class MavenException [exec] [javac] location: package org.apache.maven [exec] [javac] import org.apache.maven.MavenException; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:21: cannot find symbol [exec] [javac] symbol : class Project [exec] [javac] location: package org.apache.maven.project [exec] [javac] import org.apache.maven.project.Project; [exec] [javac] ^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav en\ejb\EJBArtifactTypeHandler.java:22: package org.apache.maven.repository does not exist [exec] [javac] import org.apache.maven.repository.ArtifactTypeHandler; [exec] [javac]^ [exec] [javac] C:\devroot\reference\maven\maven-1\plugins\trunk\ejb\src\main\ org\apache\mav
