Re: m2eclipse error
Hi,
My Pom.xml contains
org.apache.maven.plugins
maven-compiler-plugin
C:\Produits\IBM\SDP70\jdk\bin\javac
1.5
1.5
1.5
Taht's works from command line but not with m2eclipseu
Regards
Philippe
Message du 05/01/10 22:48
De : Anders Hammar
A : Maven Users List , Philippe Couas
Copie à :
Objet : Re: m2eclipse error
The error message says it. You need to define source 1.5 for the compiler
plugin.
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
/Anders
On Tue, Jan 5, 2010 at 22:24, Philippe Couas
wrote:
Hi
When i launch m2eclipse 0.94 from RAD7, i have folloing error message.
I haven't this error message from MSDOS
How avoid it
ERROR]
Mojo:
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
FAILED for project:
com.p:WEB-ENLIGNE-WebService:war:1.0
Reason:
C:\Code\c3.java:[566,25] generics are not supported in -source 1.3
(try -source 1.5 to enable generics) ArrayList liste = new ArrayList();
C:\Code\ManagerImpl.java:[562,25] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
private ArrayList fillDocs(Document documentEntree, Z2) {
C:\Code\MessageException.java:[3,7] 'class' or 'interface' expected
no more tokens - could not parse error message:
C:\Code\MessageException.java:28: 'class' or 'interface' expected
^
C:\Code\AdministrationLog4jAction.java:[45,22] generics are not supported in
-source 1.3
(try -source 1.5 to enable generics)
Vector loggers = null;
Dans mon POM j'ai
org.apache.maven.plugins
maven-compiler-plugin
C:\Produits\IBM\SDP70\jdk\bin\javac
1.5
1.5
1.5
Regards
Philippe
Re: m2eclipse error
my experience is that I need to set the right compliance mode 1.5 or
1.6 for the eclipse project to work correctly with m2eclipse. the
'source' and 'target' of compile-plugin configuration inside pom.xml
had no influence on m2eclipse. maybe a bug though - I do not know.
with regards Kristian
On Wed, Jan 6, 2010 at 11:42 AM, Philippe Couas pco...@orange.fr wrote:
Hi,
My Pom.xml contains
org.apache.maven.plugins
maven-compiler-plugin
C:\Produits\IBM\SDP70\jdk\bin\javac
1.5
1.5
1.5
Taht's works from command line but not with m2eclipseu
Regards
Philippe
Message du 05/01/10 22:48
De : Anders Hammar
A : Maven Users List , Philippe Couas
Copie à :
Objet : Re: m2eclipse error
The error message says it. You need to define source 1.5 for the compiler
plugin.
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
/Anders
On Tue, Jan 5, 2010 at 22:24, Philippe Couas
wrote:
Hi
When i launch m2eclipse 0.94 from RAD7, i have folloing error message.
I haven't this error message from MSDOS
How avoid it
ERROR]
Mojo:
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
FAILED for project:
com.p:WEB-ENLIGNE-WebService:war:1.0
Reason:
C:\Code\c3.java:[566,25] generics are not supported in -source 1.3
(try -source 1.5 to enable generics) ArrayList liste = new ArrayList();
C:\Code\ManagerImpl.java:[562,25] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
private ArrayList fillDocs(Document documentEntree, Z2) {
C:\Code\MessageException.java:[3,7] 'class' or 'interface' expected
no more tokens - could not parse error message:
C:\Code\MessageException.java:28: 'class' or 'interface' expected
^
C:\Code\AdministrationLog4jAction.java:[45,22] generics are not supported in
-source 1.3
(try -source 1.5 to enable generics)
Vector loggers = null;
Dans mon POM j'ai
org.apache.maven.plugins
maven-compiler-plugin
C:\Produits\IBM\SDP70\jdk\bin\javac
1.5
1.5
1.5
Regards
Philippe
--
Kristian Meier + Saumya Sharma + Sanuka Meier
Vadakkethu House,
Edayanmula West PO - 689532,
Pathanamthitta District, Kerala, INDIA
tel: +91 468 2319577
protect your privacy while searching the net: www.ixquick.com
_=_
q(-_-)p
'_) (_`
/__/ \
_(_ / )_
(__\_\_|_/__)
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Optionally disable transitive dependencies in Maven
Hello everyone, I am using Maven-2.0.9 and I have a project A which depends on a couple of classes from project B. So obviously, i have a dependency in my pom.xml as follows: dependency groupIdorg/groupId artifactIdprojectB/artifactId /dependency But the project B has a long list of transitive dependencies, none of which are required in project A. I was looking for a way to disable those transitive dependencies from being pulled into project A. One option would be to add numerous exclude elements to the dependency. But this is not practical, given the long list of transitive dependencies. I was looking for something like the following: dependency groupIdorg/groupId artifactIdprojectB/artifactId transitivefalse/transitive /dependency A transitive child element to the dependency element which can then be configured to disable transitive dependencies from being pulled in. From what i learn based on my discussion about this on #maven IRC, there's no technical reason why this can't be done/allowed. It would be useful to have this feature in Maven to disable transitive dependencies. Any thoughts? P.S: Is this the right list or should this be in maven-dev list? -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4259924.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Optionally disable transitive dependencies in Maven
I'd suggest that you refactor projectB bits used by both projectB and projectA into a new projectC module and have it referenced as dependency from both projectA and projectB. Regards, Stevo. On Wed, Jan 6, 2010 at 10:57 AM, jaikiran jai_forums2...@yahoo.co.inwrote: Hello everyone, I am using Maven-2.0.9 and I have a project A which depends on a couple of classes from project B. So obviously, i have a dependency in my pom.xml as follows: dependency groupIdorg/groupId artifactIdprojectB/artifactId /dependency But the project B has a long list of transitive dependencies, none of which are required in project A. I was looking for a way to disable those transitive dependencies from being pulled into project A. One option would be to add numerous exclude elements to the dependency. But this is not practical, given the long list of transitive dependencies. I was looking for something like the following: dependency groupIdorg/groupId artifactIdprojectB/artifactId transitivefalse/transitive /dependency A transitive child element to the dependency element which can then be configured to disable transitive dependencies from being pulled in. From what i learn based on my discussion about this on #maven IRC, there's no technical reason why this can't be done/allowed. It would be useful to have this feature in Maven to disable transitive dependencies. Any thoughts? P.S: Is this the right list or should this be in maven-dev list? -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4259924.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Optionally disable transitive dependencies in Maven
I would have done that. But the project B is not in my control. It's a third party project. Stevo Slavić wrote: I'd suggest that you refactor projectB bits used by both projectB and projectA into a new projectC module and have it referenced as dependency from both projectA and projectB. Regards, Stevo. -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4260065.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Surefire and testSourceDirectory
This is simply not where testSourceDirectory goes in the pom. The
Surefire plugin does not look for this value where you've put it,
therefore it has no effect on your build which is correct.
[Marcin Kwapisz]
Why? This is parameter for surefire with default value set to
${project.build.testSourceDirectory}. The documentation for the surefire plugin
is very misleading, and I think testSourceDirectory should be removed from
required parameters (if it is ignored). I can set other parameters like
classesDirectory and testClassesDirectory in the surefire configuration and
they work. The description of these two parameters is identical to
testSourcesDirectory
Regards,
Marcin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Optionally disable transitive dependencies in Maven
http://jira.codehaus.org/browse/MNG-2315 http://stackoverflow.com/questions/547805/how-to-exclude-all-transitive-dependencies-of-a-maven-dependency Regards, Stevo. On Wed, Jan 6, 2010 at 11:45 AM, jaikiran jai_forums2...@yahoo.co.inwrote: I would have done that. But the project B is not in my control. It's a third party project. Stevo Slavić wrote: I'd suggest that you refactor projectB bits used by both projectB and projectA into a new projectC module and have it referenced as dependency from both projectA and projectB. Regards, Stevo. -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4260065.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Broken inter-module links in flat multi-module build
Hi all, I am using a flat multi-module layout for my build. Unfortunately, some (but not all!) inter-module links are broken on a site-deploy. Here is the simplest case that doesn't work, using the following (flat) directory layout: parent src/site site.xml pom.xml child src/site site.xml pom.xml Here's the parent project's POM: project modelVersion4.0.0/modelVersion groupIdorg.example/groupId artifactIdparent/artifactId version0.0.1-SNAPSHOT/version packagingpom/packaging nameParent Project/name modules !-- flat multi-module build -- module../child/module /modules distributionManagement site idtmp/id urlfile:///tmp/deploy/parent/url /site /distributionManagement build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.1/version /plugin /plugins /build /project And here's the child project's POM: project modelVersion4.0.0/modelVersion parent groupIdorg.example/groupId artifactIdparent/artifactId version0.0.1-SNAPSHOT/version /parent artifactIdchild/artifactId packagingpom/packaging nameChild Project/name distributionManagement site idtmp/id urlfile:///tmp/deploy/child/url /site /distributionManagement /project Both projects use an identical src/site/site.xml: project body menu ref=parent/ menu ref=modules/ /body /project Now, after a site-deploy /tmp/deploy contains two directories side-by-side, as expected per the distributionManagement element in the projects' POMs: /tmp/deploy/parent and /tmp/deploy/child. But the Modules link from the parent project to the child project points to file:///tmp/deploy/parent/child/index.html; thus, it is broken. :-( For some strange reason, however, the Parent Project link found in file:///tmp/deploy/child/index.html points to the correct page, namely file:///tmp/deploy/parent/index.html; not all parts of Maven seem to ignore my request for a flat multi-module layout. There is hope. ;-) So, hopefully, somebody can shed some light on what is going on and why Maven behaves the way it does. Best wishes, Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Broken inter-module links in flat multi-module build
My guess is that it is because none of the projects specify a url element in the POM. This element is used by the Site Plugin to calculate links between parent and child modules. Andreas Sewe wrote: Hi all, I am using a flat multi-module layout for my build. Unfortunately, some (but not all!) inter-module links are broken on a site-deploy. Here is the simplest case that doesn't work, using the following (flat) directory layout: parent src/site site.xml pom.xml child src/site site.xml pom.xml Here's the parent project's POM: project modelVersion4.0.0/modelVersion groupIdorg.example/groupId artifactIdparent/artifactId version0.0.1-SNAPSHOT/version packagingpom/packaging nameParent Project/name modules !-- flat multi-module build -- module../child/module /modules distributionManagement site idtmp/id urlfile:///tmp/deploy/parent/url /site /distributionManagement build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.1/version /plugin /plugins /build /project And here's the child project's POM: project modelVersion4.0.0/modelVersion parent groupIdorg.example/groupId artifactIdparent/artifactId version0.0.1-SNAPSHOT/version /parent artifactIdchild/artifactId packagingpom/packaging nameChild Project/name distributionManagement site idtmp/id urlfile:///tmp/deploy/child/url /site /distributionManagement /project Both projects use an identical src/site/site.xml: project body menu ref=parent/ menu ref=modules/ /body /project Now, after a site-deploy /tmp/deploy contains two directories side-by-side, as expected per the distributionManagement element in the projects' POMs: /tmp/deploy/parent and /tmp/deploy/child. But the Modules link from the parent project to the child project points to file:///tmp/deploy/parent/child/index.html; thus, it is broken. :-( For some strange reason, however, the Parent Project link found in file:///tmp/deploy/child/index.html points to the correct page, namely file:///tmp/deploy/parent/index.html; not all parts of Maven seem to ignore my request for a flat multi-module layout. There is hope. ;-) So, hopefully, somebody can shed some light on what is going on and why Maven behaves the way it does. Best wishes, Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem in site deployment
DebasisM wrote: Hi, I am generating a site and trying to deploy it.I am facing two problem. 1.i am having 8 modules.i am using pom aggregation for running install and deploy goal.but site i want to generate only for parent not for the child modules. how to prevent only for the site generation. Run 'mvn -N site-deploy' from the parent project. 2.for deployment of the site to the sever(windows not unix) .i am trying with ftp.error-unsupported protocol. The FTP protocol is not available in your version of Maven. You need to tell Maven to extend itself with a wagon that supports the FTP protocol. build extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-ftp/artifactId version1.0-beta-4/version /extension /extensions ... /build Thanks, Debasis -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Broken inter-module links in flat multi-module build
Dennis Lundberg wrote: My guess is that it is because none of the projects specify a url element in the POM. This element is used by the Site Plugin to calculate links between parent and child modules. Dennis, you saved my day. It works. :-) I am still curious as to the difference between /project/url (which seems to be called for here) and /project/distributionManagement/url. At least in my case both elements have the same content anywhere... That being said, unlike the latter element, the former seemed (to me at least) not directly related to site generation. Even the POM Reference makes it sound not a very important element: The URL, like the name, is not required. This is a nice gesture for projects users, however, so that they know where the project lives. So I was caught totally off-guard by its importance to site generation. :-( Best wishes, Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Broken inter-module links in flat multi-module build
Hi all, I am still curious as to the difference between /project/url (which seems to be called for here) and /project/distributionManagement/url. At least in my case both elements have the same content anywhere... forget it; I get it now: /project/url is the public-facing URL whereas /project/distributionManagement/url may very well we inivisible externally (think ~/public_html) or not a proper URL at all (AFAIK, scp: is not a registered URI scheme, but only indicates to Maven the protocol to use.) I just got confused because my simple test case uses the file: URI scheme, which works fine in either element. Best wishes, Andreas Sewe - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANNOUNCEMENT] - AspectJ compiler Maven Plugin 1.3 released
The AspectJ compiler Maven Plugin team is pleased to announce the aspectj-maven-plugin-1.3 release! Handles AspectJ usage within maven. Functionality provided is: weaving of aspects (or existing aspects from libraries) with the test and/or main classes, weaving of pre-existing jars and ajdoc reporting. Changes in this version include: Fixed Bugs: o Critical failures reported by ajc (e.g. reweaving already weaved code) are not handled by the plugin Issue: MASPECTJ-74. Changes: o Upgrade to aspectj 1.6.7 Issue: MASPECTJ-81. o Add support for relative paths like META-INF/aop-ajc-arguments.lst to the plugin property ajdtBuildDefFile Issue: MASPECTJ-76. o The plugin should be more verbose regarding compiling / weaving - similar to the Maven compiler plugin Issue: MASPECTJ-75. For a manual installation, you can download the aspectj-maven-plugin-1.3 here: http://mojo.codehaus.org/aspectj-maven-plugin Have fun! -AspectJ compiler Maven Plugin team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Multi-module site generation?
Hi, just wondering if you were successful in the end as I'm facing a similar problem, cheers newton.dave wrote: --- On Fri, 9/12/08, Dave Newton lied: Running site-deploy works, as long as I define a file URI that isn't broken. Which I couldn't. Turns out site:deploy works just fine too (once the sites have been generated, I mean). Spoke too soon; I thought it had worked at one point but now the module links it's creating point to the parent POM directory + parent artifactId. Ah; removing *all* the url elements seems to have fixed it; I think my root POM's url messed up all the others. Curious; I'll look into it again tomorrow. Thanks again, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/Multi-module-site-generation--tp19466376p27026924.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Error in assembly - META-INF/MANIFEST.MF not found
Just a gentle ping if anyone has any insight on why this would occur. Its wreaking havoc with my builds and any help is much appreciated. I checked the archives and saw one other person with this issue but the only response I saw was someone mentioning running an ls command. I can provide any additional info necessary if this issue is unclear. Hopefully someone knows what I'm doing wrong :) Thanks Mike Key On Jan 5, 2010, at 1:07 PM, Mike Key wrote: I am building an assembly from a war and when I build locally with maven it works fine, however when I build on a CentOS machine through Hudson I get the following error on initial build, if I restart the build it clears itself up, but on each checkin this error occurs. I have checked the war and META-INF/MANIFEST.MF DOES exist. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to create assembly: Error creating assembly archive distribution: Problem creating war: JAR entry META-INF/MANIFEST.MF not found in http://myhost/job/live-ensure-trunk/ws/trunk/services/live-identity-ws/target/live-identity-ws-3.0.0-SNAPSHOT.war Any help on clearing this up is much appreciated. Thanks in advance. Mike Key
[ANN] Maven Patch Plugin 1.1.1 Released
The Maven team is pleased to announce the release of the Maven Patch Plugin, version 1.1.1. This plugin is used to apply patches to source files. See the plugin's site for more details: http://maven.apache.org/plugins/maven-patch-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-patch-plugin/artifactId version1.1.1/version /plugin Release Notes - Maven 2.x Patch Plugin - Version 1.1.1 ** Bug * [MPATCH-11] - Plugin generates faulty command line when originalFile and destFile parameters are used Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m2eclipse error
The source and target are used to set the eclipse settings per project.
On Wed, Jan 6, 2010 at 4:49 AM, kristian m.krist...@web.de wrote:
my experience is that I need to set the right compliance mode 1.5 or
1.6 for the eclipse project to work correctly with m2eclipse. the
'source' and 'target' of compile-plugin configuration inside pom.xml
had no influence on m2eclipse. maybe a bug though - I do not know.
with regards Kristian
On Wed, Jan 6, 2010 at 11:42 AM, Philippe Couas pco...@orange.fr wrote:
Hi,
My Pom.xml contains
org.apache.maven.plugins
maven-compiler-plugin
C:\Produits\IBM\SDP70\jdk\bin\javac
1.5
1.5
1.5
Taht's works from command line but not with m2eclipseu
Regards
Philippe
Message du 05/01/10 22:48
De : Anders Hammar
A : Maven Users List , Philippe Couas
Copie à :
Objet : Re: m2eclipse error
The error message says it. You need to define source 1.5 for the compiler
plugin.
http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html
/Anders
On Tue, Jan 5, 2010 at 22:24, Philippe Couas
wrote:
Hi
When i launch m2eclipse 0.94 from RAD7, i have folloing error message.
I haven't this error message from MSDOS
How avoid it
ERROR]
Mojo:
org.apache.maven.plugins:maven-compiler-plugin:2.0.2:compile
FAILED for project:
com.p:WEB-ENLIGNE-WebService:war:1.0
Reason:
C:\Code\c3.java:[566,25] generics are not supported in -source 1.3
(try -source 1.5 to enable generics) ArrayList liste = new ArrayList();
C:\Code\ManagerImpl.java:[562,25] generics are not supported in -source 1.3
(try -source 1.5 to enable generics)
private ArrayList fillDocs(Document documentEntree, Z2) {
C:\Code\MessageException.java:[3,7] 'class' or 'interface' expected
no more tokens - could not parse error message:
C:\Code\MessageException.java:28: 'class' or 'interface' expected
^
C:\Code\AdministrationLog4jAction.java:[45,22] generics are not supported
in -source 1.3
(try -source 1.5 to enable generics)
Vector loggers = null;
Dans mon POM j'ai
org.apache.maven.plugins
maven-compiler-plugin
C:\Produits\IBM\SDP70\jdk\bin\javac
1.5
1.5
1.5
Regards
Philippe
--
Kristian Meier + Saumya Sharma + Sanuka Meier
Vadakkethu House,
Edayanmula West PO - 689532,
Pathanamthitta District, Kerala, INDIA
tel: +91 468 2319577
protect your privacy while searching the net: www.ixquick.com
_=_
q(-_-)p
'_) (_`
/__/ \
_(_ / )_
(__\_\_|_/__)
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Mojo properties inheritance
Hi All, I am developing a mojo A and I would like to extend it with a subclass mojo B. I declared the project property in A and when the mojo executes, the property is correctly set. I expected the same behaviour for B, but it looks like it does not work. If I do not declare the project field in B, the maven project object is not set. Is this the normal behaviour? Is there a way to inherit mojo configuration parameters? Thanks in advance. -- Ste - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven ejb plugin --- 2 client jars
Hi, We have an ejb jar with an ant script that produces 2 ejb-client jars. The maven ejb plugin indicates that to produce a client jar I should use this syntax: configuration !-- this is false by default -- generateClienttrue/generateClient /configuration Is there a way to have the plugin produce 2 client jars with different client includes or excludes for each artifact? Also, how would a consuming client use a classifier in the dependency declaration to pull down one client or the other? Seems like there is no way to do this? Regards, Eric -- View this message in context: http://old.nabble.com/maven-ejb-plugin-2-client-jars-tp27026965p27026965.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mojo properties inheritance
Are A and B in the same JAR file? If so, this should work. If you look at just about any core plugin, it depends upon this working. For example: http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/InstallMojo.java extends http://svn.apache.org/repos/asf/maven/plugins/trunk/maven-install-plugin/src/main/java/org/apache/maven/plugin/install/AbstractInstallMojo.java Justin On Wed, Jan 6, 2010 at 3:54 PM, Stefano Fornari stefano.forn...@gmail.comwrote: Hi All, I am developing a mojo A and I would like to extend it with a subclass mojo B. I declared the project property in A and when the mojo executes, the property is correctly set. I expected the same behaviour for B, but it looks like it does not work. If I do not declare the project field in B, the maven project object is not set. Is this the normal behaviour? Is there a way to inherit mojo configuration parameters? Thanks in advance. -- Ste - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: m2eclipse error
M2eclipse embedded Maven and command line Maven are not the same, so they apply different default settings, from here the discrepancy between the two behaviours. Possible solutions are: - explicitly set the source and target version as Anders Hammad said before or (better, after me) - configure m2eclipse to use the normal, not embedded, maven, to do that in eclipse: windows-preferences-maven-installations, add your maven install dir, and check it. regards, Andrea
