Re: How do I change the default goal in Continuum
It's hardcoded for the moment in continuum-core, so you can't modify it. The only solution I can see, is to update all build definitions manually or directly in the database Emmanuel Thomas Boyles a écrit : Greetings. We'd like to change the global default goal for Maven 2.0 projects. I don't see this as a param in the application.xml. Any help would be appreciated. *Thomas Boyles* *Production / Release Engineer* Mobile - 415.624.7496 Home - 415.738.8733
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
Request: I want to ask to add the following line: JEE / javax.jee / jee Justification: Since Version 1.5 of the Java Enterprise Edition, the 2 is removed. The specification officially is called Java Enterprise Edition (JEE). The maven repository should take respect of this decision and add the above line. Regards Markus smime.p7s Description: S/MIME Cryptographic Signature
Java EE 5 available on central repository soon!
Dear Maven Community, Today I asked the Glassfish community (= Java EE 5 Reference Implementation) to publish a j2ee.jar (= Java EE 5 APIs) on the Maven 2 central repository to allow coders to easily use the Java EE technology with Maven, without the need to download the complete SDK manually. A few minutes later Bill SHANNON (= Java EE 5 Specification Lead) answered me that in fact they are working on this issue and he will try to speed up this process! :-) So soon the days will be gone where we all need to download the Java EE 5 SDK just to get the APIs. Soon it will be possible to just add a dependency on Sun's MVN2 repository to get the complete Java EE 5 APIs downloaded automatically when compiling an EJB3 project... :-) Have lots of fun! Markus smime.p7s Description: S/MIME Cryptographic Signature
EJB3 Packaging is not working a told on the Maven web site
Dear Maven Community, Today I have seen on the Maven web site (http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html) that the ejb plugin is able to package EJB3 compliant JARs. So I wanted to try that out and have set up a sample project. Unfortunately it seems it is not working as expected actually. On the web site it is told that once ejbVersion is set to 3.0 then the ejb-jar.xml would be optional. In fact, when setting the ejbVersion to 3.0, the plugin still complains about the missing ejb-jar.xml and fails to build: Embedded error: /home/markus/.eclipse/sample-ejb/target/classes/META-INF/ejb-jar.xml isn't a file. The pom.xml is attached below, it is written according to the documentation found on the web site. So is this a bug in the plugin or a bug on the web site? Thanks Markus project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdlocal.sample/groupId artifactIdsample-ejb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version nameSample :: EJB/name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration ejbVersion3.0/ejbVersion /configuration /plugin /plugins /build dependencies dependency groupIdjavax.javaee/groupId artifactIdjavaee/artifactId version1.5/version scopeprovided/scope /dependency /dependencies /project smime.p7s Description: S/MIME Cryptographic Signature
Re: EJB3 Packaging is not working a told on the Maven web site
Hi Markus, What version of the plugin are you using? Also, a dump of the complete error might be useful too. On Sat, 2006-09-16 at 11:22 +0200, Markus KARG wrote: Dear Maven Community, Today I have seen on the Maven web site (http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html) that the ejb plugin is able to package EJB3 compliant JARs. So I wanted to try that out and have set up a sample project. Unfortunately it seems it is not working as expected actually. On the web site it is told that once ejbVersion is set to 3.0 then the ejb-jar.xml would be optional. In fact, when setting the ejbVersion to 3.0, the plugin still complains about the missing ejb-jar.xml and fails to build: Embedded error: /home/markus/.eclipse/sample-ejb/target/classes/META-INF/ejb-jar.xml isn't a file. The pom.xml is attached below, it is written according to the documentation found on the web site. So is this a bug in the plugin or a bug on the web site? Thanks Markus project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdlocal.sample/groupId artifactIdsample-ejb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version nameSample :: EJB/name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration ejbVersion3.0/ejbVersion /configuration /plugin /plugins /build dependencies dependency groupIdjavax.javaee/groupId artifactIdjavaee/artifactId version1.5/version scopeprovided/scope /dependency /dependencies /project
exporting Database
hi all i want to export a database table from mySql on one machine to another MySql instance . can anyone tell me how to carry on the proceedings. currently i am working with Maven torque plugin but finding difficulty. if anyone knows about it please reply thanks in advance Manoj Kaushik
Re: J2EE Client Application JAR is not detected as J2EE module
I stand corrected. Never used this feature. Alright, but from reading the 1.4 spec, it seems that this jar is deployed outside the app server as a CLIENT. The client application.xml file is deployed within a JAR a read by another container than your main EAR application, no? So what do you expect the EAR plugin to do exactly? -aps On 9/16/06, Markus KARG [EMAIL PROTECTED] wrote: Alexander, please read J2EE 1.4 specification: The J2EE Client Application Descriptor is a mandatory part of J2EE 1.4. It is no BEA invention. Quoted from Java(tm) 2 Platform Enterprise Edition Specification, v1.4 chapter 9.7 J2EE Application Client XML Schema: J2EE.9.7 J2EE Application Client XML Schema The XML grammar for a J2EE application client deployment descriptor is defined by the J2EE application-client schema. The root element of the deployment descriptor for an application client is application-client. The content of the XML elements is in general case sensitive. This means, for example, that res- authContainer/res-auth must be used, rather than res-authcontainer/ res-auth. All valid application-client deployment descriptors must conform to the following XML Schema definition, or to a DTD definition from a previous version of this specification. (See Appendix J2EE.A, Previous Version DTDs.) The deployment descriptor must be named META-INF/application-client.xml in the application client's .jar file. Note that this name is case-sensitive. So there is actually no room for interpretation. You might want to read J2EE 1.4 spec chapter 9 Application Clients. Markus Alexander Sack wrote: I'm pretty sure the J2EE client application descriptor you speak of is a BEA only primitive and not generic enough to be included in the EAR plugin (please correct me if I'm wrong, I don't remember ever seeing this in the J2EE spec). With that said a light bult has sort of went off and perhaps the EAR plugin should have a PLATFORM identifier that can fine tune the packaging based on Java EE app server. As anyone who has worked with more than one app server knows, the spec has A LOT of room for interpretation and some platforms just aren't compliant (either they choose to be or are catching up). Good idea, bad idea? -aps On 9/15/06, Wayne Fay [EMAIL PROTECTED] wrote: If the current release of the EAR plugin does not support the functionality you desire, you have a few options: 1. Complain about missing functionality on the Maven User list. 2. File a JIRA Enhancement report and hope someone looks at your issue and decides it is worth spending some time to implement for you. 3. Write the code yourself, then file a JIRA with your changes attached and wait for it to be incorporated into the released code which will take some time to actually land in a non-snapshot repo (several weeks at a minimum). Pick one from above and do it. In the mean time, if you want things to work, you will need to be practical about things -- simply add the entry into the application.xml (or whatever file, I'm not familiar with J2EE Client Apps) manually or in the pom.xml and move on with life. Wayne On 9/15/06, Markus KARG [EMAIL PROTECTED] wrote: No I do not mean ejb-client but J2EE Client Application: What you mean is a JAR containing the interfaces of the EJBs, but what I mean is a standalone (Swing) application that is to be run inside of a J2EE Client Container. I have seen that EJB-JARs are enlistet in the EAR's application.xml automatically, and we want this to happen with the J2EE Client Application also, without adding it to the EAR's pom.xml manually. This should be possible since a J2EE Client Application always contains a file named META-INF\client-application-xml, so the EAR task just need to look into the JAR to find out about its type. I do not understand why this has to be specified manually. Thanks Markus Stephane Nicoll schrieb: you mean ejb-client? Your dependency should be 'ejb-client' not 'jar'. Anyhow, if you want a jar to be included in the application.xml, just configure the plugin acccordingly (includeInApplicationXml) [1] Cheers, Stéphane [1] http://maven.apache.org/plugins/maven-ear-plugin/howto.html On 9/15/06, Markus KARG [EMAIL PROTECTED] wrote: I am using the EAR packaging to let Mvn2 create an .ear file plus automatically create an application.xml inside of it. It detects all my EJB modules, but it doesn't detect that one of the included JARs is not a utility JAR but in fact a J2EE Client Application JAR. Maybe the packaging type I have used for that JAR is wrong (I used JAR since I thought the EAR packager will detect the contained client-application.xml file). So what is the correct way to specify J2EE Client Application JAR packaging instead of simple utility JAR packaging? Thanks a lot! Markus
Re: EJB3 Packaging is not working a told on the Maven web site
Arik, I have not customized the version of the plugin in any way, I just installed Maven 2.0.4 and let it do what it likes to. As I found out, it is pulling version 2.0 automatically, which seems a bit out of age. Unfortunately, it seems to be the latest published, while the ejbVersion feature was introduced in 2.1-SNAPSHOT which is not yet published. Is that right? When will 2.1 be released? Markus Arik Kfir wrote: Hi Markus, What version of the plugin are you using? Also, a dump of the complete error might be useful too. On Sat, 2006-09-16 at 11:22 +0200, Markus KARG wrote: Dear Maven Community, Today I have seen on the Maven web site (http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html) that the ejb plugin is able to package EJB3 compliant JARs. So I wanted to try that out and have set up a sample project. Unfortunately it seems it is not working as expected actually. On the web site it is told that once ejbVersion is set to 3.0 then the ejb-jar.xml would be optional. In fact, when setting the ejbVersion to 3.0, the plugin still complains about the missing ejb-jar.xml and fails to build: Embedded error: /home/markus/.eclipse/sample-ejb/target/classes/META-INF/ejb-jar.xml isn't a file. The pom.xml is attached below, it is written according to the documentation found on the web site. So is this a bug in the plugin or a bug on the web site? Thanks Markus project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdlocal.sample/groupId artifactIdsample-ejb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version nameSample :: EJB/name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration ejbVersion3.0/ejbVersion /configuration /plugin /plugins /build dependencies dependency groupIdjavax.javaee/groupId artifactIdjavaee/artifactId version1.5/version scopeprovided/scope /dependency /dependencies /project smime.p7s Description: S/MIME Cryptographic Signature
Re: EJB3 Packaging is not working a told on the Maven web site
I recommend you build the plugin from source (until a newer version is properly released) and test it. If it does work, than all you need to do is wait for the release (or keep working with the version you built). If it still doesn't work, then that means there really is a bug and you should open a JIRA ticket for it. To build the plugin from source, you need to: 1. checkout the code from SVN (see http://maven.apache.org/plugins/maven-ejb-plugin/source-repository.html) 2. build the plugin (issue a mvn clean install inside its directory) 3. rebuild your project and see if it works Good luck! On Sat, 2006-09-16 at 16:38 +0200, Markus KARG wrote: Arik, I have not customized the version of the plugin in any way, I just installed Maven 2.0.4 and let it do what it likes to. As I found out, it is pulling version 2.0 automatically, which seems a bit out of age. Unfortunately, it seems to be the latest published, while the ejbVersion feature was introduced in 2.1-SNAPSHOT which is not yet published. Is that right? When will 2.1 be released? Markus Arik Kfir wrote: Hi Markus, What version of the plugin are you using? Also, a dump of the complete error might be useful too. On Sat, 2006-09-16 at 11:22 +0200, Markus KARG wrote: Dear Maven Community, Today I have seen on the Maven web site (http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html) that the ejb plugin is able to package EJB3 compliant JARs. So I wanted to try that out and have set up a sample project. Unfortunately it seems it is not working as expected actually. On the web site it is told that once ejbVersion is set to 3.0 then the ejb-jar.xml would be optional. In fact, when setting the ejbVersion to 3.0, the plugin still complains about the missing ejb-jar.xml and fails to build: Embedded error: /home/markus/.eclipse/sample-ejb/target/classes/META-INF/ejb-jar.xml isn't a file. The pom.xml is attached below, it is written according to the documentation found on the web site. So is this a bug in the plugin or a bug on the web site? Thanks Markus project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdlocal.sample/groupId artifactIdsample-ejb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version nameSample :: EJB/name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration ejbVersion3.0/ejbVersion /configuration /plugin /plugins /build dependencies dependency groupIdjavax.javaee/groupId artifactIdjavaee/artifactId version1.5/version scopeprovided/scope /dependency /dependencies /project
Re: J2EE Client Application JAR is not detected as J2EE module
Sorry, wrong, once more. ;-) The J2EE specification says that an EAR contains not only EJB, WAR, RAR and other modules, but also one or more Client Application Modules. When deploying the EAR on the server, it's the server's job to publish the client to the client machines. For example, SAS9 is using JNLP / WebStart to support this demand. I want the EAR plugin to detect that a dependency is not an EJB, WAR or RAR but such a Client Application Module (by inspecting whether the JAR contains a /META-INF/application-client.xml file). Such a JAR is not only to be contained in the EAR (is it is as any JAR is), but also add an javaxyz.jar/java entry to the automatically generated application.xml file that the EAR plugin creates and puts into the EAR (as it does it with EJB, WAR or RAR modules already). In fact from the view of the J2EE 1.4 specification, a client-application JAR is to be treated as an EJB, WAR or RAR is treated: Detect that it is a module, detect the type of the module, contain it in the EAR, add an entry to the application.xml file. Everything is done by the EAR plugin correctly but not the last step: The EAR plugin currently detects the type of module (it needs to know the type to know what to write into the application.xml) by mapping file extensions to module types. For EJB, WAR or RAR this is sufficient. But to support client applications, the EAR plugin must learn to differenciate between utility JARs and client application JARs (since both share the extension of .jar, so the type detection is not possible). To learn this, the work is easy: For each .jar file found in the dependencies that is to be added to the EAR, check whether there is a file called /META-INF/application-client.xml found inside of that JAR. If true, the type of this jar is not JAR but application-client, and such an entry to the EAR's automatically generated application.xml file has to be added using the java type of module tag. That's all to be found inside of the J2EE specification, most of it in chapter 9, but also in the chapter on the application.xml schema (look at the declaration of module and you will find java). So actually the EAR plugin can be extended to support this essential part of J2EE 1.4 within one or two code lines. Can anybody please add that? :-) Thanks! Markus Alexander Sack wrote: I stand corrected. Never used this feature. Alright, but from reading the 1.4 spec, it seems that this jar is deployed outside the app server as a CLIENT. The client application.xml file is deployed within a JAR a read by another container than your main EAR application, no? So what do you expect the EAR plugin to do exactly? -aps On 9/16/06, Markus KARG [EMAIL PROTECTED] wrote: Alexander, please read J2EE 1.4 specification: The J2EE Client Application Descriptor is a mandatory part of J2EE 1.4. It is no BEA invention. Quoted from Java(tm) 2 Platform Enterprise Edition Specification, v1.4 chapter 9.7 J2EE Application Client XML Schema: J2EE.9.7 J2EE Application Client XML Schema The XML grammar for a J2EE application client deployment descriptor is defined by the J2EE application-client schema. The root element of the deployment descriptor for an application client is application-client. The content of the XML elements is in general case sensitive. This means, for example, that res- authContainer/res-auth must be used, rather than res-authcontainer/ res-auth. All valid application-client deployment descriptors must conform to the following XML Schema definition, or to a DTD definition from a previous version of this specification. (See Appendix J2EE.A, Previous Version DTDs.) The deployment descriptor must be named META-INF/application-client.xml in the application client's .jar file. Note that this name is case-sensitive. So there is actually no room for interpretation. You might want to read J2EE 1.4 spec chapter 9 Application Clients. Markus Alexander Sack wrote: I'm pretty sure the J2EE client application descriptor you speak of is a BEA only primitive and not generic enough to be included in the EAR plugin (please correct me if I'm wrong, I don't remember ever seeing this in the J2EE spec). With that said a light bult has sort of went off and perhaps the EAR plugin should have a PLATFORM identifier that can fine tune the packaging based on Java EE app server. As anyone who has worked with more than one app server knows, the spec has A LOT of room for interpretation and some platforms just aren't compliant (either they choose to be or are catching up). Good idea, bad idea? -aps On 9/15/06, Wayne Fay [EMAIL PROTECTED] wrote: If the current release of the EAR plugin does not support the functionality you desire, you have a few options: 1. Complain about missing functionality on the Maven User list. 2. File a JIRA Enhancement report and hope someone looks at your issue and decides it is worth spending some
Re: EJB3 Packaging is not working a told on the Maven web site
Arik, thank you so much for your kind short introduction into pulling down and compiling SNAPSHOTs of ejb plugin. In fact, it solved my problem. Once I had built and installed the 2.1-SNAPSHOT, I was able to package my EJB3 module without any problem using my pom.xml shown below. In fact, it seems the EJB3 support is well done, but actually I have to check whether the built EJB-JAR is working actually in my application server. Thanks a lot! :-) Markus Arik Kfir wrote: I recommend you build the plugin from source (until a newer version is properly released) and test it. If it does work, than all you need to do is wait for the release (or keep working with the version you built). If it still doesn't work, then that means there really is a bug and you should open a JIRA ticket for it. To build the plugin from source, you need to: 1. checkout the code from SVN (see http://maven.apache.org/plugins/maven-ejb-plugin/source-repository.html) 2. build the plugin (issue a mvn clean install inside its directory) 3. rebuild your project and see if it works Good luck! On Sat, 2006-09-16 at 16:38 +0200, Markus KARG wrote: Arik, I have not customized the version of the plugin in any way, I just installed Maven 2.0.4 and let it do what it likes to. As I found out, it is pulling version 2.0 automatically, which seems a bit out of age. Unfortunately, it seems to be the latest published, while the ejbVersion feature was introduced in 2.1-SNAPSHOT which is not yet published. Is that right? When will 2.1 be released? Markus Arik Kfir wrote: Hi Markus, What version of the plugin are you using? Also, a dump of the complete error might be useful too. On Sat, 2006-09-16 at 11:22 +0200, Markus KARG wrote: Dear Maven Community, Today I have seen on the Maven web site (http://maven.apache.org/plugins/maven-ejb-plugin/ejb-mojo.html) that the ejb plugin is able to package EJB3 compliant JARs. So I wanted to try that out and have set up a sample project. Unfortunately it seems it is not working as expected actually. On the web site it is told that once ejbVersion is set to 3.0 then the ejb-jar.xml would be optional. In fact, when setting the ejbVersion to 3.0, the plugin still complains about the missing ejb-jar.xml and fails to build: Embedded error: /home/markus/.eclipse/sample-ejb/target/classes/META-INF/ejb-jar.xml isn't a file. The pom.xml is attached below, it is written according to the documentation found on the web site. So is this a bug in the plugin or a bug on the web site? Thanks Markus project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdlocal.sample/groupId artifactIdsample-ejb/artifactId packagingejb/packaging version1.0-SNAPSHOT/version nameSample :: EJB/name build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId configuration ejbVersion3.0/ejbVersion /configuration /plugin /plugins /build dependencies dependency groupIdjavax.javaee/groupId artifactIdjavaee/artifactId version1.5/version scopeprovided/scope /dependency /dependencies /project smime.p7s Description: S/MIME Cryptographic Signature
When will maven-ejb-plugin get released?
I am currently using the ejb-plugin 2.1-SNAPSHOT since I am using EJB3. Is there a planned release date for that plugin? Also I like to know when will there be an EAR plugin release that supports automatic detection of EJB 3 modules. Currently those are not detected automatically but need to added to the pom.xml as modules manually. smime.p7s Description: S/MIME Cryptographic Signature
EAR plugin says my module is no dependancy...?
I have used the 2.1-SNAPSHOT of the ejb task to create EJB3 JAR. Since the EAR plugins at the moment doesn't automatically add a ejbModule entry for EJB3 JARs (I hope this gets fixed in the next release), I added the module manually in the pom.xml of my EAR. But now MVN2 crashes with stack trace and complains about my module not beeing a dependency (what is false, because if I remove the ejbModule I am getting an EAR created containing the dependency JAR... I this bug already known to the EAR team and where (and when) can I obtain a fixed EAR plugin? Thanks for all! Maven is great! Markus smime.p7s Description: S/MIME Cryptographic Signature
Re: http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html
better yet, open a jira and submit a patch On 9/16/06, Markus KARG [EMAIL PROTECTED] wrote: Request: I want to ask to add the following line: JEE / javax.jee / jee Justification: Since Version 1.5 of the Java Enterprise Edition, the 2 is removed. The specification officially is called Java Enterprise Edition (JEE). The maven repository should take respect of this decision and add the above line. Regards Markus
Re: J2me maven plugin
Frank Seidinger wrote: Vandermi Joao da Silva wrote: Is there some plugin for J2ME? If that exist plugin ,is possible create a file jad to project J2me? I see one plugin in mojo site but the URL is down. Dear Vandermi, I've created a j2me plugin for maven2. Actually it does excactly what your are looking for. It preverifies your classes and creates a java descriptor after packaging your jar. The manifest entries are generated through configuration. The plugin is currently in the mojo-sandbox on the codehaus site. You can find the plugins documentation at: http://mojo.codehaus.org/j2me-maven-plugin If you have any questions regarding the plugin, please feel free email or post me, Kind regards, Frank Seidinger Hi Frank, I've noticed that the netbeas IDE now features some sort of a preprocessor that allows multiple jar file outputs (in order to tackle the device fragmentation issue). Can your plugin use this preprocessor (I don't know if it's a part of the standard j2me sdk)? If so how do you tackle the one artifact per module issue as effectually one source code base could generate more then one artifact? Thanks, Srgjan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Managing Repositories
Hi, I am struggling with the question on how to maintain a controlled internal repository with Maven 2. We want to have full control over the downloaded dependencies and configured Maven to use as central repository our internal repository server. With this configuration no external repository is used. In my settings.xml file I have configured Ibiblio as external repository server and activate the profile whenever I have to use components with dependencies that are not in our internal repository. The problem I have is that getting the internal/central repository updated with the new dependencies is rather a tedious and time intensive task, especially if for example a maven plug-in is added that comes with lots of transient dependencies. My question is: Ho do other teams deal with that problem? Are there tools that list differences between two different repositories (local and internal)? I used Maven Archiva as proxy repository but that does not give us the control over what gets added to the repository. Thanks in advance for any hint and suggestion. Andreas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
GWT Toolkit Plugin
I was starting to use the GWT plugin in the Mojo sandbox, and find that it doesn't work the way I expected. I have been rewriting it to work the way I expect it, and am wondering if I am doing something strange. My expectation of the plugin is to be part of a build for a WAR. The toolkit is used to compile the user interface of the application into JavaScript which is then included in the WAR as it is assembled. It looks like the plugin was written with the expectation of the GWT-derived stuff being in a separate project from the WAR (or whatever is using the pages). I was wondering if anyone else is using the plugin and how they are arranging their projects to use it. This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Installing a File From a Plugin
I am working with a plugin which connects Maven to a third-party tool kit (GWT) that the user must download separately. I would like to write a Mojo that takes the directory where the kit was installed and the version of the kit and installs the required jars into the Maven repository (or maybe deploys to a corporate one). The basic operation of the Mojo would be as a script which does mvn install:install-file on the jars in the installation directory when the user enters the command mvn gwt:install. Anybody have a good idea or two on how to accomplish this task? This communication is the property of Qwest and may contain confidential or privileged information. Unauthorized use of this communication is strictly prohibited and may be unlawful. If you have received this communication in error, please immediately notify the sender by reply e-mail and destroy all copies of the communication and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven2 Ant Tasks : is there a task to find a project build order from a parent POM
Hi, I am currently evaluating several dependency/repository managements solutions. Among the possible choices, we are looking at sticking with ant but using the maven2 antlib for repository management, including writing POMs. Is there an Ant task available which can determine a build order from a parent pom ? The class org.apache.maven.project.ProjectSorter in maven-artifact-ant-2.0.4-dep.jar seems to be doing what we need, but I don't know whether this class has an Ant facade. If there is no such task, I will open a JIRA issue to create one. I will be grateful for all feedback from the Maven developers. Regards, Antoine - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
