maven-assembly-plugin and file filter.properties problem
With maven-assembly-plugin I can't filter files using a filter.properties
file
(note that it works with pom built-in properties e.g. ${project.groupId} or
propertiestotoproperties)
I've created a small project using mvn archetype:create and inserted the
assembly configuration (see below)
Everything works fine, except the file filter.properties usage. It looks
like it is completely ignored
(even if this file is not present I dont get any error message from
assembly)
any hint ?
Thanks,
Christian-Luc
plugin
artifactIdmaven-assembly-plugin/artifactId
configuration
filters
filter
src/main/assembly/dev/filter.properties
/filter
/filters
descriptors
descriptor
src/main/assembly/dev/packaging_descriptor.xml
/descriptor
/descriptors
/configuration
executions
execution
idmake-assembly/id
phasepackage/phase
goals
goaldirectory-inline/goal
goalattached/goal
/goals
/execution
/executions
/plugin
--
View this message in context:
http://www.nabble.com/maven-assembly-plugin-and-file-filter.properties-problem-tf3690454s177.html#a10317652
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Question: rpm-maven-plugin and /usr/lib/rpm/check-files
Hi, We use rpm-maven-plugin version 2.0-alpha-3-SNAPSHOT. We found that during its work, the /usr/lib/rpm/check-files run and and it generate the rpm first to /var/tmp Is there an option to configure a different location to generate this rmp-temp file? Thanks, Erez. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2-Plugin Development: Reading POM programmatically
Hello Mark, thanks a lot - where do you get such information from? From my point of view maven is not well documentated, isn't it? can i get your shared component somewhere before it's submitted and is there already a jira entry to vote for it? greetings Martin Mark Hobson schrieb: On 03/05/07, Martin Bengl [EMAIL PROTECTED] wrote: hello folks, I use following solution (with maven 2.0.4) to create a MavenProject at runtime to extract informations like artifactId and groupid - this could be also done by manually parsing the xml file - but i think its a better way to use the maven classes. File pomFile = new File(pom.xml); MavenProjectBuilder projectBuilder; ArtifactRepository localRepository; MavenProject pom = projectBuilder.build(pomFile, localRepository, (ProfileManager)null ); My Question is: From which object can I receive a profileManager instance? (the projectBuilder and localRepository are defined as plexus components, the profileManager isn't!) To simply parse the pom into a MavenProject, use something like: MavenXpp3Reader reader = new MavenXpp3Reader(); Model model = reader.read(myreader); MavenProject project = new MavenProject(model); I've got a shared component to help with introspecting the Maven environment, as you describe, which I'm hoping to submit when I get a chance. Cheers, Mark - 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 Community news @ blog.octo.com
Hi Henry, Effectively, as Stephane said, you replied on the mailing list, thus I'll reply in english ;-) On 03/05/07, Stephane Nicoll [EMAIL PROTECTED] wrote: Howdy, Comments inline. Writing in English would have been more appropriate but I guess you just send the mail to the wrong recipient :) On 5/2/07, Henri Tremblay [EMAIL PROTECTED] wrote: Salut, Dommage, en fait c'était pour la mailing list, je croyais que j'avais reçu le mail personnellement. ;-) I preferred to announce it on the mailing list to be sure to not forget a maven user ;-) Je voulais envoyer un message à la liste mais puisque je t'ai sous la main, je me pose des questions sur l'avenir de maven. En fait j'ai dû mener un dur combat contre certaine limitation et je me demande ce qui est prévu. Si je te saoule, prière de m'en avertir, je referai en anglais sur la mailing list. Mais comme d'habitude les gens d'Octo sont sympas :-) Thanks. There's no problem. I always reply, not always quickly, but I reply. En fait c'est concernant les plugins. J'aimerai pouvoir faire les choses suivantes: 1- Pouvoir retirer des plugins et configurations dans des poms enfants. À priori les poms s'agrègent mais il est impossible d'en enlever des morceaux. That's an issue indeed. You can reconfigure the plugin or set the inherited flag to false to avoid spreading the config the the children. The only solution is actually to configure them in the pluginsManagement part of the pom and stop the inheritence where you want in the parent. The problem is that you have to be able to edit the parent pom. It's not possible in a child to say that it musn't use settings coming from the parent for a given plugin. 2- Avoir un certain déterminisme sur l'ordre d'exécution des plugins / exécutions. Il peut arriver que je veuille faire un antrun suivi d'un minijar suivi d'un antrun et je n'arrive pas à faire respecter cet ordre. This is scheduled for Maven 2.1 Maven 2.1-alpha-1 should be available in some weeks (we hope) 3- Pouvoir détacher un plugin d'une phase auquel il est attaché par défaut You need to create a custom lifecycle for that. This is not certainly ideal from your point's of view but it works. Some Mojos have a skip attribute which can be set to true to ... well ... skip its execution. This can maybe generalized. 4- Avoir plus clairement les versions des documentations des plugins online et les release notes en chaque version pour limiter les confusions. We're busy configuring the projects to deploy the site in a separate space per version. Not sure how far we are, Wendy might answer that. I just see, that Wendy replied. 5- Aussi, avoir des archetypes de projects: webapp, ejb, applet (en particulier applet m'intrigue) Archetype is completely re-written at the moment. As soon as it's done I'm pretty sure that we will have many archetypes available. Not sure I understand what applet means in this context. The problem with the applet must be to correctly setup the assembly (and certainly some others stuffs) to put all libraries in a given directory and create the code for the html page. 6- Connais-tu un exemple d'utilisation des phases de test d'intégration? Check the Cargo's plugin which shows how you can start/stop a container and run integration tests on them. Yes, that's also, the only one I know actually... HTH, Stéphane Arnaud Merci pour toute réponse, Henri On 5/2/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi everybody, FYI, I publish each month in French a list of news about the maven community : http://blog.octo.com/ If you are not speaking french you can however easily understand the list of releases. If I forgot something, do not hesitate to tell me. Best Regards Arnaud - 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] -- .. Arnaud Héritier OCTO Technology [EMAIL PROTECTED] .. 50, Avenue des Champs-Elysées 75008 Paris Tél : (33) 1 58 56 10 00 Fax : (33) 1 58 56 10 01 GSM : (33) 6 03 52 71 31 www.octo.com | blog.octo.com ...
Re: M2-Plugin Development: Reading POM programmatically
Hi Martin, On 04/05/07, Martin Bengl [EMAIL PROTECTED] wrote: Hello Mark, thanks a lot - where do you get such information from? From my point of view maven is not well documentated, isn't it? Mainly from digging around the source code. I do agree writing and publishing some javadoc would lessen the learning curve.. can i get your shared component somewhere before it's submitted and is there already a jira entry to vote for it? I'll try to submit an initial version shortly via JIRA and will send an announcement to the dev list. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-surefire-plugin 2.2 ignoring skipExec
Is anyone else having issues with surefire plugin ignoring configuration. According to http://maven.apache.org/plugins/maven-surefire-plugin/test-mojo.html the configuration value of skipExec is valid and will compile but not execute tests. skiptrue/skip works skipExectrue/skipExec doesn't work I've tried 2.0, 2.1.x and 2.2 and they all ignore skipExec. I'm maintaining a multi module project and the root pom has configuration for the surefire plugin. I just want to temporarily get a few modules to not execute their tests. Any ideas? John
DBUnit and table list
Hi there, 1) Firstly I've noticed there appears to be two DBUnit plugins, not sure which is best : http://mojo.codehaus.org/dbunit-maven-plugin http://maven-plugins.sourceforge.net 2) I'm trying to use the codehaus DBUnit plugin to export some data, but one table is giving me an error so I thought I'd provide a list of tables to export to the plugin configuration but not sure how to :- The docs says there is a configurable :- tables Table[] List of DbUnit's Table. See DbUnit's JavaDoc for details I have tried :- tables tabletable1/table tabletable2/table /tables and tablestable1,table2tables all inside the plugin's configuration. The plugin requires org.dbunit.ant.Table but looks like the Strings don't get converted to this. Cannot assign configuration entry 'table' to 'class org.dbunit.ant.Table' from 'acl_object_identity', which is of type class java.lang.String Help ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DBUnit and table list
On 5/4/07, Pete [EMAIL PROTECTED] wrote: Hi there, 1) Firstly I've noticed there appears to be two DBUnit plugins, not sure which is best : http://mojo.codehaus.org/dbunit-maven-plugin maven 2.x http://maven-plugins.sourceforge.net maven 1.x 2) I'm trying to use the codehaus DBUnit plugin to export some data, but one table is giving me an error so I thought I'd provide a list of tables to export to the plugin configuration but not sure how to :- The docs says there is a configurable :- tables Table[] List of DbUnit's Table. See DbUnit's JavaDoc for details I have tried :- tables tabletable1/table tabletable2/table /tables and tablestable1,table2tables all inside the plugin's configuration. The plugin requires org.dbunit.ant.Table but looks like the Strings don't get converted to this. Cannot assign configuration entry 'table' to 'class org.dbunit.ant.Table' from 'acl_object_identity', which is of type class java.lang.String Help ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
A project with two parents, a reasonable idea or a bad idea?
Can someone let me know what's the common pattern for dealing with an artifact that is really a child of two projects? This kind of thing smells like an opportunity for refactoring and I feel like I should break the child artifact into multiple projects. I'm trying to convert a few products to use maven as their build system they both rely on a commons project, but each builds it slightly differently. Here's the pseudo example - Foo and Bar both both depend on commons. - Foo builds commons/src/commons and commons/src/foo. - Bar build commons/src/commons and commons/src/bar. To me it looks like a straight forward refactoring case. Commons need to be split into commons-base, commons-foo and commons-bar projects with the dependencies looking like this: - Foo - commons-foo - commons-base - Bar - commons-bar - commons-base or commons-foo and commons-bar could be named differently or moved into Foo and Bar respectively. Is this the right pattern or am I missing some maven nuance that would allow for another way of arranging things? -- Peter Kahn [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] http://analogoustendencies.blogspot.com/ Awareness - Intention - Action
maven MsDev/DevStudio
Does anyone know if there are plugins for building devstudio solutions and/or projects? Specifically for building projects from project definitions of msdev6.0 through visualstudio8 (2005). It looks like theirs a nmaven incubation project and I've seen some mention of projects, but it looks like people just use ant in as task or ant as a plugin. I'm leaning towards making my own ant plugin since I already have stable ant code to handle this task. -- Peter Kahn [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED] http://analogoustendencies.blogspot.com/ Awareness - Intention - Action
Passing in maven_opts at run time?
Is there a way to pass in maven_opts at run time? I have the environment variable set and it works when I run maven from my console, but I'm using a build manager and it seems to be calling maven and it's ignoring the environment variable some how. I was wondering if there was a way I could call maven and specify -Xmx384m -Xms256m -XX:MaxPermSize=256m -verbose:gc via the command line to ensure it's using those. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Conditional Dependencies?
Hello, Is there a way to have conditional dependencies based on custom properties, including artifacts and/or their versions? Many thanks, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
One profile activate another
I would like to have two profiles. One profile can be called by itself. The second one should activate the first one so that the configuration of the first is included. Is this possible? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generating ejb-client jar using ejb 3.0??
Hy everyone, Is there any way to generate an ejb-client jar with EJB 3.0? I have tried these following configuration using the maven-ejb-plugin 2.1-Snapshotwithout success : Note that I have a dependency on javax.ejb. Thanks in advance! Copernic ... dependency groupIdjavax.ejb/groupId artifactIdejb/artifactId version3.0/version /dependency build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId version2.1-SNAPSHOT/version configuration ejbVersion3.0/ejbVersion generateClienttrue/generateClient /configuration /plugin /build
Re: pom.xml URL - CVS access
Hi Martin... THX very much for your answer, I don't know how I've miss that we could use the file protocol. Regards, Rodrigo. Martin Hoeller wrote: Am Freitag, 27. April 2007 16:24 schrieb Rodrigo Gonçalves: Hi Thierry... Thx for your answer, but the Upload POM is not an option!! Because when you do that continuum does not update the pom.xml file when someone modify the file and commit the changes on CVS. Besides, the POM upload works only for a single projects without modules. That's not completely correct. You can upload local POMs by enabling the file:// protocol (see [0]) and specifying a POM in the URL-input field like file:///path/to/my/pom.xml. This way continuum adds submodules recursively. hth, - martin [0] http://maven.apache.org/continuum/faqs.html
Re: A project with two parents, a reasonable idea or a bad idea?
That is the refactoring I would expect, and the correct Maven approach to the situation. Wayne On 5/4/07, Peter Kahn [EMAIL PROTECTED] wrote: Can someone let me know what's the common pattern for dealing with an artifact that is really a child of two projects? This kind of thing smells like an opportunity for refactoring and I feel like I should break the child artifact into multiple projects. I'm trying to convert a few products to use maven as their build system they both rely on a commons project, but each builds it slightly differently. Here's the pseudo example - Foo and Bar both both depend on commons. - Foo builds commons/src/commons and commons/src/foo. - Bar build commons/src/commons and commons/src/bar. To me it looks like a straight forward refactoring case. Commons need to be split into commons-base, commons-foo and commons-bar projects with the dependencies looking like this: - Foo - commons-foo - commons-base - Bar - commons-bar - commons-base or commons-foo and commons-bar could be named differently or moved into Foo and Bar respectively. Is this the right pattern or am I missing some maven nuance that would allow for another way of arranging things? -- Peter Kahn [EMAIL PROTECTED] [EMAIL PROTECTED], [EMAIL PROTECTED], [EMAIL PROTECTED] http://analogoustendencies.blogspot.com/ Awareness - Intention - Action - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conditional Dependencies?
The only way I've seen of making dependencies conditional is via profiles. What exactly are you trying to do? Wayne On 5/4/07, Manos Batsis [EMAIL PROTECTED] wrote: Hello, Is there a way to have conditional dependencies based on custom properties, including artifacts and/or their versions? Many thanks, Manos - 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]
Maven 2.0.6 using JDK 1.3
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
Re: Maven 2.0.6 using JDK 1.3
Add this to your POM.xml:
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
/plugin
/plugins
/build
Best regards!
Copernic
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
Re: One profile activate another
Not that I'm aware of. But what's stopping you from simply specifying 2 profiles in the command line ie: mvn -P abc, xyz package See more information here: http://maven.apache.org/guides/introduction/introduction-to-profiles.html Wayne On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote: I would like to have two profiles. One profile can be called by itself. The second one should activate the first one so that the configuration of the first is included. Is this possible? Thanks! - 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 2.0.6 using JDK 1.3
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Conditional Dependencies?
Wayne Fay wrote: The only way I've seen of making dependencies conditional is via profiles. That would create too many profiles for me. Suppose an EAR parent's POM, where the EAR can have multiple modules one can choose from and configure. For example struts 1.x or 2.x based web module, ejb 2.1 or 3.0 module, use of HDIV [1] in the web module and so on and so forth. I'm trying to figure the best way to go about this for my md4j [2] quickstarter project. [1] http://www.hdiv.org/ [2] http://dev.abiss.gr/md4j/ Cheers, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: DBUnit and table list
I've never used the DBUnit plugin myself, but as Greg mentioned, the Codehaus plugin is for M2 while the other one is for M1. If you don't get the answers you seek here, send your email to the Mojo-User list at Codehaus. Wayne On 5/4/07, Gregory Kick [EMAIL PROTECTED] wrote: On 5/4/07, Pete [EMAIL PROTECTED] wrote: Hi there, 1) Firstly I've noticed there appears to be two DBUnit plugins, not sure which is best : http://mojo.codehaus.org/dbunit-maven-plugin maven 2.x http://maven-plugins.sourceforge.net maven 1.x 2) I'm trying to use the codehaus DBUnit plugin to export some data, but one table is giving me an error so I thought I'd provide a list of tables to export to the plugin configuration but not sure how to :- The docs says there is a configurable :- tables Table[] List of DbUnit's Table. See DbUnit's JavaDoc for details I have tried :- tables tabletable1/table tabletable2/table /tables and tablestable1,table2tables all inside the plugin's configuration. The plugin requires org.dbunit.ant.Table but looks like the Strings don't get converted to this. Cannot assign configuration entry 'table' to 'class org.dbunit.ant.Table' from 'acl_object_identity', which is of type class java.lang.String Help ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gregory Kick http://kickstyle.net/ - 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: Conditional Dependencies?
If you can't/won't create the various profiles to support this functionality, I think you're going to need to write a plugin (or two) to do all this. Its just not supported in the core, and I don't see it being added any time soon, so a plugin seems the only way forward. Wayne On 5/4/07, Manos Batsis [EMAIL PROTECTED] wrote: Wayne Fay wrote: The only way I've seen of making dependencies conditional is via profiles. That would create too many profiles for me. Suppose an EAR parent's POM, where the EAR can have multiple modules one can choose from and configure. For example struts 1.x or 2.x based web module, ejb 2.1 or 3.0 module, use of HDIV [1] in the web module and so on and so forth. I'm trying to figure the best way to go about this for my md4j [2] quickstarter project. [1] http://www.hdiv.org/ [2] http://dev.abiss.gr/md4j/ Cheers, Manos - 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 2.0.6 using JDK 1.3
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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: DBUnit and table list
Could you checkout the src/example in the source tree at mojo? http://svn.codehaus.org/mojo/trunk/mojo/dbunit-maven-plugin/src/example/ -D On 5/4/07, Pete [EMAIL PROTECTED] wrote: Hi there, 1) Firstly I've noticed there appears to be two DBUnit plugins, not sure which is best : http://mojo.codehaus.org/dbunit-maven-plugin http://maven-plugins.sourceforge.net 2) I'm trying to use the codehaus DBUnit plugin to export some data, but one table is giving me an error so I thought I'd provide a list of tables to export to the plugin configuration but not sure how to :- The docs says there is a configurable :- tables Table[] List of DbUnit's Table. See DbUnit's JavaDoc for details I have tried :- tables tabletable1/table tabletable2/table /tables and tablestable1,table2tables all inside the plugin's configuration. The plugin requires org.dbunit.ant.Table but looks like the Strings don't get converted to this. Cannot assign configuration entry 'table' to 'class org.dbunit.ant.Table' from 'acl_object_identity', which is of type class java.lang.String Help ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.6 using JDK 1.3
I totally agree with Paul here, any one else?
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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 2.0.6 using JDK 1.3
+1
Dan Tran wrote:
I totally agree with Paul here, any one else?
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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: Maven 2.0.6 using JDK 1.3
I believe the reason for this is as follows:
jdk3 is the lowest common denominator
pom.xml is supposedly the one true source for all data you need to
know about a project, and builds are supposed to be
repeatable/reproducible using only this information
automatically picking up and using the current jvm version would mean
that some important information about the project is not contained in
the pom
thus, the default is jdk3, and if you need anything else, you must
specify it explicitly
Another thing to remember is that Maven produces artifacts which are
not necessarily used under the same JVM that constructed them.
Everyone is OK with jdk3 jars (even older app servers) but not
everyone is OK with jdk5 jars, so the default is jdk3, and if you know
you can/should be targeting a newer jvm, then you need to explicitly
configure it as such.
I'm not 100% positive that is the reason, but this is my take on it,
and it doesn't sound completely crazy... to me at least. ;-)
Wayne
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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 : Maven 2.0.6 using JDK 1.3
If I'm working on a project with the jdk 1.5 (using maven) and during my
development period, I want to make a rapid update to an old jdk 1.3 based
project from the svn including compiling == re-jaring and so on...
do I have to reinstall my old jdk for a 30min dev ?
-1
Nawfel BERAICH
www.ilem.ma
- Message d'origine
De : Dan Tran [EMAIL PROTECTED]
À : Maven Users List users@maven.apache.org
Envoyé le : Vendredi, 4 Mai 2007, 15h52mn 07s
Objet : Re: Maven 2.0.6 using JDK 1.3
I totally agree with Paul here, any one else?
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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]
___
Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions !
Profitez des connaissances, des opinions et des expériences des internautes sur
Yahoo! Questions/Réponses
http://fr.answers.yahoo.com
Re: Problem with maven-archetype-quickstart Reason: Unable to determine the release version
venky4m wrote: ... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.archetypes ArtifactId: maven-archetype-quickstart Version: RELEASE Reason: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.archetypes -DartifactId=maven-arch etype-quickstart \ -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file org.apache.maven.archetypes:maven-archetype-quickstart:jar:RELEASE ... Hi, I guess you have to specify the version of the maven-archetype-quickstart jar. mvn -DarchetypeArtifactId=maven-archetype-quickstart -DarchetypeVersion=version-of-the-jar ... Take a look at http://maven.apache.org/plugins/maven-archetype-plugin/examples/archetype.html http://maven.apache.org/plugins/maven-archetype-plugin/examples/archetype.html section 4: Install and run the archetype -- View this message in context: http://www.nabble.com/Problem-with-maven-archetype-quickstart-%3E-Reason%3A-Unable-to-determine-the-release-version-tf3590702s177.html#a10323966 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: One profile activate another
This is not possible, however a workaround exists! You can set the first profile to be activated when a certain property is set, and the second one when it is set to a specific value. That way, if the value is 'correct', both profiles will be activated. On Friday 04 May 2007 16:37, Paul Gier wrote: I would like to have two profiles. One profile can be called by itself. The second one should activate the first one so that the configuration of the first is included. Is this possible? Thanks! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.6 using JDK 1.3
I think the fact maven-2.x is written in Java should be treated just as an implementation detail, not as something to be relied upon. Hypothetically, someone could re-implement maven in something else, and no Java version would be available from which to infer the version. So I don't think the java compiler source level should be inferred at build time. Also, not specifying the version needed hides information that may be necessary to have a reproducible build. OTOH, I would be in favor of such a default being inferred by an archetype. At archetype:create time, the compiler source level configuration would be inserted into the created pom.xml. This could work regardless of the maven implementation language by using the first found version of Java found by some search alorithm (i.e., $JAVA_HOME, then $PATH, then /usr/bin, then default to 1.3) -Al On Fri, May 04, 2007 at 08:52:07AM -0700, Dan Tran spake thus: I totally agree with Paul here, any one else? On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote: It seems like a better default behavior for the compiler plugin would be to use the current jvm version. If I'm running maven with jdk1.5 I would expect the compiler plugin to default to source level 1.5. Is there a reason that it can't work like that? *snip* -- :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: Alan D. Salewski Software Developer Health Market Science, Inc. :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: :: - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.0.6 using JDK 1.3
That makes perfect sense.
On 5/4/07, Wayne Fay [EMAIL PROTECTED] wrote:
I believe the reason for this is as follows:
jdk3 is the lowest common denominator
pom.xml is supposedly the one true source for all data you need to
know about a project, and builds are supposed to be
repeatable/reproducible using only this information
automatically picking up and using the current jvm version would mean
that some important information about the project is not contained in
the pom
thus, the default is jdk3, and if you need anything else, you must
specify it explicitly
Another thing to remember is that Maven produces artifacts which are
not necessarily used under the same JVM that constructed them.
Everyone is OK with jdk3 jars (even older app servers) but not
everyone is OK with jdk5 jars, so the default is jdk3, and if you know
you can/should be targeting a newer jvm, then you need to explicitly
configure it as such.
I'm not 100% positive that is the reason, but this is my take on it,
and it doesn't sound completely crazy... to me at least. ;-)
Wayne
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed -
com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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: Maven 2.0.6 using JDK 1.3
Nope, that doesn't sound crazy at all. Both of your points make perfect sense.
I retract my earlier +1 :-)
One minor quip - the docs should be updated to state the default is 1.3...
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#target
Wayne Fay wrote:
I believe the reason for this is as follows:
jdk3 is the lowest common denominator
pom.xml is supposedly the one true source for all data you need to
know about a project, and builds are supposed to be
repeatable/reproducible using only this information
automatically picking up and using the current jvm version would mean
that some important information about the project is not contained in
the pom
thus, the default is jdk3, and if you need anything else, you must
specify it explicitly
Another thing to remember is that Maven produces artifacts which are
not necessarily used under the same JVM that constructed them.
Everyone is OK with jdk3 jars (even older app servers) but not
everyone is OK with jdk5 jars, so the default is jdk3, and if you know
you can/should be targeting a newer jvm, then you need to explicitly
configure it as such.
I'm not 100% positive that is the reason, but this is my take on it,
and it doesn't sound completely crazy... to me at least. ;-)
Wayne
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
plexus-bootstrap error
Hi friends, while trying to run a process-resources goal for a project through the maven integration plug-in for (my)eclipse I get this error : [INFO] Scanning for projects... [ERROR] reactor-execute : C:\works\workspaceM2\myProject-v1.3 Diagnosis: The internal default plexus-bootstrap.xml is missing. This is highly irregular, your plexus JAR is most likely corrupt. Realms: null.child-container[extensions] parent=null (null) plexus.core [EMAIL PROTECTED] (jar:file:/C:/devTools/MyEclipse%205.5%20M2/eclipse/configuration/org.eclipse.osgi/bundles/516/1/.cp/lib/maven-embedder-2.1.0.v20070110-2115-dep.jar!/org/codehaus/plexus/plexus-bootstrap.xml) FATAL ERROR: Error executing Maven for a project [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The internal default plexus-bootstrap.xml is missing. This is highly irregular, your plexus JAR is most likely corrupt. Realms: null.child-container[extensions] parent=null (null) plexus.core [EMAIL PROTECTED] (jar:file:/C:/devTools/MyEclipse%205.5%20M2/eclipse/configuration/org.eclipse.osgi/bundles/516/1/.cp/lib/maven-embedder-2.1.0.v20070110-2115-dep.jar!/org/codehaus/plexus/plexus-bootstrap.xml) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri May 04 15:59:06 GMT 2007 [INFO] Final Memory: 1M/3M [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Fri May 04 15:59:06 GMT 2007 [INFO] Final Memory: 1M/3M [INFO] can someone tell me what's happening ? :-) Peace Nawfel ___ Découvrez une nouvelle façon d'obtenir des réponses à toutes vos questions ! Profitez des connaissances, des opinions et des expériences des internautes sur Yahoo! Questions/Réponses http://fr.answers.yahoo.com
meta-meta information in the POM (was Re: RequireMavenVersion failed)
On 5/3/07, A. Kevin Baynes [EMAIL PROTECTED] wrote: Brian, you're right : there's a comment in the POM.xml also (found it later), so the developers did a good job of trying to warn me... No besmirchment of the Apache FTP team intended. That's something I miss from maven: meta-meta data. Often I take a decision that I will comment in the POM. E.g. the reason why we choose a particular dependency version, etc... This information is not available to the user nor the generated report, forcing to read the POM. It would be great if there was a way to comment any element in the POM in such a way that these comments become available to the plugins. Maybe something like: node comment=/node ? Cheers, Jerome - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release plugin (scm via cvs)
I'm trying to use the release plugin. When I do release:prepare it fails when it tries to commit the pom.xml files with this error: [INFO] Checking in modified POMs... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the checkin process: /home/dcorbin/workspace/inventory.ws/com.enttek.concessions.common/pom.xml was not contained in /home/dcorbin/workspac e/inventory.ws/com.enttek.concessions-master The error statement is correct. my master pom is a physical (on disk) sibling it's two children. I've run it with -X, with native CVS and with cvs tracing turned on (I think - I never saw any evidence). There was no addiational information or change in behavior? What can I do that does not involve changing the directory structure to make this work? David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: release plugin (scm via cvs)
What is your directory structure? Flat directories aren't supported. 2 workarounds: 1. you can add a pom under /home/dcorbin/workspace/inventory.ws/ and do the release on it 2. release your parent and children independently Emmanuel David Corbin a écrit : I'm trying to use the release plugin. When I do release:prepare it fails when it tries to commit the pom.xml files with this error: [INFO] Checking in modified POMs... [INFO] [ERROR] BUILD ERROR [INFO] [INFO] An error is occurred in the checkin process: /home/dcorbin/workspace/inventory.ws/com.enttek.concessions.common/pom.xml was not contained in /home/dcorbin/workspac e/inventory.ws/com.enttek.concessions-master The error statement is correct. my master pom is a physical (on disk) sibling it's two children. I've run it with -X, with native CVS and with cvs tracing turned on (I think - I never saw any evidence). There was no addiational information or change in behavior? What can I do that does not involve changing the directory structure to make this work? 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]
[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]
Re: [Spam] Re: release plugin (scm via cvs)
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. 2. release your parent and children independently Well, this would work, but the parent (in -master) is where the version is. Any plans to suppor this in the future? In general, maven seems to do fine with this. David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Spam] Re: release plugin (scm via cvs)
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). Stéphane 2. release your parent and children independently Well, this would work, but the parent (in -master) is where the version is. Any plans to suppor this in the future? In general, maven seems to do fine with this. 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: [Spam] Re: release plugin (scm via cvs)
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! 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. When you have lots of sub-projects, you might also want to check out the multi-project importer (http://eclipse-tools.sourceforge.net/projecttransfer/index.html), which you just point to your root and it'll recursively find all projects to import into eclipse (except for POM-packaging, but that's the fault of the eclipse:eclipse!). -- 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: [Spam] Re: release plugin (scm via cvs)
On Friday 04 May 2007 20: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! 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. Just read the web-page again, it seems that it'll work on 2.1 as well! When you have lots of sub-projects, you might also want to check out the multi-project importer (http://eclipse-tools.sourceforge.net/projecttransfer/index.html), which you just point to your root and it'll recursively find all projects to import into eclipse (except for POM-packaging, but that's the fault of the eclipse:eclipse!). -- 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]
build plugin order in same phase
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, it seems to be impossible with maven 2.0.x to specify the order of plugins in the build process that are attached to the same phase (please corret me if I am wrong). The order in the POM does NOT matter. Is this feature available in (or planned for) maven 2.1? Are there any workarounds? Regards Jörg -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.5 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFGO5gsmPuec2Dcv/8RAtQjAJ9S0aEvMzca01WcHtYy8SVNOpe3kgCgh4M1 R3niwC5fb7w7Y2sTLdt8Iq4= =Ne0I -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build plugin order in same phase
On 5/4/07, Joerg Hohwiller [EMAIL PROTECTED] wrote: it seems to be impossible with maven 2.0.x to specify the order of plugins in the build process that are attached to the same phase (please corret me if I am wrong). The order in the POM does NOT matter. Is this feature available in (or planned for) maven 2.1? http://jira.codehaus.org/browse/MNG-2258 Are there any workarounds? Sometimes you can work around it by shifting an execution to the phase before or after. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to use axis2-wsdl2code:wsdl2code?
Hello, Can some help me to get the proper implementation for axis2-wsdl2code:wsdl2code? I don't know If there is bug in this? What dependency I need to put for using the plug in? I remember I need to add wsdl dependency in plug-in pom. Is it really required. Thanks Jaish
Re: Maven 2.0.6 using JDK 1.3
1.3 has been end-of-lifed. Any reason not to make 1.4 the minimum base version?
James
On 04/05/07, Ian Springer [EMAIL PROTECTED] wrote:
Nope, that doesn't sound crazy at all. Both of your points make perfect sense.
I retract my earlier +1 :-)
One minor quip - the docs should be updated to state the default is 1.3...
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#source
http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html#target
Wayne Fay wrote:
I believe the reason for this is as follows:
jdk3 is the lowest common denominator
pom.xml is supposedly the one true source for all data you need to
know about a project, and builds are supposed to be
repeatable/reproducible using only this information
automatically picking up and using the current jvm version would mean
that some important information about the project is not contained in
the pom
thus, the default is jdk3, and if you need anything else, you must
specify it explicitly
Another thing to remember is that Maven produces artifacts which are
not necessarily used under the same JVM that constructed them.
Everyone is OK with jdk3 jars (even older app servers) but not
everyone is OK with jdk5 jars, so the default is jdk3, and if you know
you can/should be targeting a newer jvm, then you need to explicitly
configure it as such.
I'm not 100% positive that is the reason, but this is my take on it,
and it doesn't sound completely crazy... to me at least. ;-)
Wayne
On 5/4/07, Paul Gier [EMAIL PROTECTED] wrote:
It seems like a better default behavior for the compiler plugin would be
to use the current jvm version.
If I'm running maven with jdk1.5 I would expect the compiler plugin to
default to source level 1.5.
Is there a reason that it can't work like that?
Wayne Fay wrote:
This is one of the most common questions on this list...
It has been answered repeatedly -- check the archives at Nabble.
Also it is very well documented on the Maven website -- both in the
FAQ and in the Maven Compiler plugin docs.
Google also has numerous links when you search for maven generics.
Wayne
On 5/4/07, David Smith [EMAIL PROTECTED] wrote:
I'm having a problem compiling my project with maven 2.0.6. Maven is
using JDK 1.3 to compile the java files that contain generics. The
build fails with an error stating that 1.3 does not support generics.
How do I switch JDKs so that maven will use 1.5 instead of 1.3? My
classpath and path variables both point to 1.5.
---
[INFO] Building Unnamed - com.javaworld.hotels:HotelDatabase:jar:0.0.1
[INFO]task-segment: [package]
[INFO]
-
---
[INFO] [resources:resources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:compile]
Compiling 2 source files to
C:\workspace.3.2.2\HotelDatabase\target\classes
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] Compilation failure
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[22,19] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
public ListHotel findHotelsByCity(String city){
C:\workspace.3.2.2\HotelDatabase\src\main\java\com\javaworld\hotels\mode
l\HotelM
odel.java:[24,32] for-each loops are not supported in -source 1.3
(try -source 1.5 to enable for-each loops)
for(Hotel hotel : hotels){
-
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]
-
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 Community news @ blog.octo.com
I'm starting a trend... Mailing to the complete mailing list... I did this twice in two weeks... Good thing I'm going in holidays. Sorry for the french spam. :-) And thanks for the answers. :-) - Henri On 5/4/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi Henry, Effectively, as Stephane said, you replied on the mailing list, thus I'll reply in english ;-) On 03/05/07, Stephane Nicoll [EMAIL PROTECTED] wrote: Howdy, Comments inline. Writing in English would have been more appropriate but I guess you just send the mail to the wrong recipient :) On 5/2/07, Henri Tremblay [EMAIL PROTECTED] wrote: Salut, Dommage, en fait c'était pour la mailing list, je croyais que j'avais reçu le mail personnellement. ;-) I preferred to announce it on the mailing list to be sure to not forget a maven user ;-) Je voulais envoyer un message à la liste mais puisque je t'ai sous la main, je me pose des questions sur l'avenir de maven. En fait j'ai dû mener un dur combat contre certaine limitation et je me demande ce qui est prévu. Si je te saoule, prière de m'en avertir, je referai en anglais sur la mailing list. Mais comme d'habitude les gens d'Octo sont sympas :-) Thanks. There's no problem. I always reply, not always quickly, but I reply. En fait c'est concernant les plugins. J'aimerai pouvoir faire les choses suivantes: 1- Pouvoir retirer des plugins et configurations dans des poms enfants. À priori les poms s'agrègent mais il est impossible d'en enlever des morceaux. That's an issue indeed. You can reconfigure the plugin or set the inherited flag to false to avoid spreading the config the the children. The only solution is actually to configure them in the pluginsManagement part of the pom and stop the inheritence where you want in the parent. The problem is that you have to be able to edit the parent pom. It's not possible in a child to say that it musn't use settings coming from the parent for a given plugin. 2- Avoir un certain déterminisme sur l'ordre d'exécution des plugins / exécutions. Il peut arriver que je veuille faire un antrun suivi d'un minijar suivi d'un antrun et je n'arrive pas à faire respecter cet ordre. This is scheduled for Maven 2.1 Maven 2.1-alpha-1 should be available in some weeks (we hope) 3- Pouvoir détacher un plugin d'une phase auquel il est attaché par défaut You need to create a custom lifecycle for that. This is not certainly ideal from your point's of view but it works. Some Mojos have a skip attribute which can be set to true to ... well ... skip its execution. This can maybe generalized. 4- Avoir plus clairement les versions des documentations des plugins online et les release notes en chaque version pour limiter les confusions. We're busy configuring the projects to deploy the site in a separate space per version. Not sure how far we are, Wendy might answer that. I just see, that Wendy replied. 5- Aussi, avoir des archetypes de projects: webapp, ejb, applet (en particulier applet m'intrigue) Archetype is completely re-written at the moment. As soon as it's done I'm pretty sure that we will have many archetypes available. Not sure I understand what applet means in this context. The problem with the applet must be to correctly setup the assembly (and certainly some others stuffs) to put all libraries in a given directory and create the code for the html page. 6- Connais-tu un exemple d'utilisation des phases de test d'intégration? Check the Cargo's plugin which shows how you can start/stop a container and run integration tests on them. Yes, that's also, the only one I know actually... HTH, Stéphane Arnaud Merci pour toute réponse, Henri On 5/2/07, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi everybody, FYI, I publish each month in French a list of news about the maven community : http://blog.octo.com/ If you are not speaking french you can however easily understand the list of releases. If I forgot something, do not hesitate to tell me. Best Regards Arnaud - 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] -- .. Arnaud Héritier OCTO Technology [EMAIL PROTECTED] .. 50, Avenue des Champs-Elysées 75008 Paris Tél : (33) 1 58 56 10 00 Fax : (33) 1 58 56 10 01 GSM : (33) 6 03 52 71 31 www.octo.com | blog.octo.com ... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
maven-remote-resources-plugin/apache-jar-resource-bundle hints
Hi, I have 2 wishes related to this plugin, and I hope you have some hints for me ;-) 1) I create source:jar and javadoc:jar using the source and javadoc plugins. Is there a way to include the NOTICE/LICENSE from remote resources into this jars too? 2) I configured my assembly descriptors so to take NOTICE/LICENSE from the target/maven-shared-archive-resources while composing my binary.zip distrubution and source.zip distribution. The problem is that the SOURCE distribution also contains COMPILE and TEST dependencies and I have to make sure that also that dependencies are included in the NOTICE list. I have not found a way to do this: is there a way to declare what scope I'm interested in? Is there a way to have different NOTICE created for different packages? Stefano - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
