Re: run Archiva 1.0 as windows service??
good news, it works when archiva is configured to run under a known userid. -D On Dec 8, 2007 8:45 PM, Dan Tran [EMAIL PROTECTED] wrote: windows XP, of course I use the provided InstallService.bat. Al configurations look right I think it used to work in beta-2 where I first evaluated archiva. -D On Dec 8, 2007 7:41 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Dec 8, 2007 8:30 PM, Dan Tran [EMAIL PROTECTED] wrote: I can run archive from command line. I can register it as windows service I can start the service via the service control panel, no error detected, but archive http port is not in listening mode ( ie netstat -a | grep LIST does show the port ) and no logs found in logs directory either. Can some one confirm? or it is just me. What Windows version? How did you register it as a service? I see there's an InstallService.bata file, did you use that? -- Wendy
Re: Continuum Profile during release?
On Dec 6, 2007 8:44 AM, Wendy Smoak [EMAIL PROTECTED] wrote: If I define a Continuum Profile (CP) [1] for scheduled builds, for example to build with a different JDK than the one Continuum is running under, how do I make sure that CP is used when I release the project? Discussed with Olivier on irc, this isn't implemented. http://jira.codehaus.org/browse/CONTINUUM-1594 -- Wendy
Re: Optional Proxy Configuration
On Saturday 08 December 2007 08:35:07 Heinrich Nirschl wrote: On Dec 8, 2007 8:13 AM, Marco Bakera [EMAIL PROTECTED] wrote: Hello everybody. At work I need a proxy for maven to work while I don't need one at home. So I have to change my settings.xml back and forth during work at home and and at work. So is it possible to simply turn off the proxy server configuration with a command line option? The -s option allows you to use a different user settings file. Although this is possible I don't know whether it is the preferred way of doing, since I just want to turn off one part of the settings file while keeping the others as is. - Marco. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 maven-site-plugin site.xml target attribute no more working
In maven 1.x xdoc site documentation there could be the following for menus (navigation.xml): menu name=myMenu item name=Maven 1.x href=http://maven.apache.org/maven-1.x/; target=_new / ... (creates a link to maven 1.x in a new window or tab) In maven 2.x site.xml this doesn't work anymore. The target attribute will be ignored. Is this a bug? -- View this message in context: http://www.nabble.com/M2-maven-site-plugin-site.xml-target-attribute-no-more-working-tf4966309s177.html#a14226588 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: release of maven jar plugin 2.2 in the near future ?
On Dec 6, 2007 1:44 AM, Jerome Lacoste [EMAIL PROTECTED] wrote: Hei, The latest maven jar plugin release was in August 2006. Is there any plan to make a release this year ? :) http://jira.codehaus.org/browse/MJAR/fixforversion/12878 I see 5 issues still targeted for 2.2 (among which 2 MJAR-78, MJAR-84 have a patch). Olivier made some fixes and there are now only 2 remaining issues (that sound like new features to me). http://jira.codehaus.org/browse/MJAR/fixforversion/12878 Olivier, is your plan to fix the 2 remaining issues then call for a release ? If so, I can allocate some time tomorrow for them. If not, what will be the release plans for the plugin ? Cheers, Jerome
Re: Optional Proxy Configuration
On Dec 8, 2007 12:58 PM, Marco Bakera [EMAIL PROTECTED] wrote: On Saturday 08 December 2007 08:35:07 Heinrich Nirschl wrote: On Dec 8, 2007 8:13 AM, Marco Bakera [EMAIL PROTECTED] wrote: Hello everybody. At work I need a proxy for maven to work while I don't need one at home. So I have to change my settings.xml back and forth during work at home and and at work. So is it possible to simply turn off the proxy server configuration with a command line option? The -s option allows you to use a different user settings file. Although this is possible I don't know whether it is the preferred way of doing, since I just want to turn off one part of the settings file while keeping the others as is. Is this a serious problem? How often do you change the settings file? If you are *really* worried about inconsistencies you could even come up with a little transformation (e.g. in XSLT) that converts one setting file to the other. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
deploy goal not copyiing resources to deployment repository
I have a very basic pom
Code:
?xml version=1.0 encoding=UTF-8?
project
modelVersion4.0.0/modelVersion
groupIdenterra/groupId
artifactIdenterra-templates/artifactId
version0.0.1-SNAPSHOT/version
nameEnterra Templates/name
description
Coerced templates for the hibernate and spring cartridges
/description
packagingjar/packaging
distributionManagement
repository
identerra-plugin-snapshot-distro/id
urlhttp://intranet.enterrasolutions.com/artifactory/enterra-plugins-snapshots/url
uniqueVersionfalse/uniqueVersion
/repository
/distributionManagement
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-resources-plugin/artifactId
version2.2/version
configuration
sourceDirectorysrc/main/resources/sourceDirectory
outputDirectory
${env.M2_REPO}/${pom.groupId}/${pom.artifactId}/${pom.version}
/outputDirectory
/configuration
/plugin
/plugins
/build
/project
When I run mvn install it builds the following into my local repository
(M2_REPO):
Code:
M2_REPO
enterra
enterra-templates
0.0.1-PLUGIN
(enterra-templates-0.0.1-PLUGIN.jar)
(enterra-templates-0.0.1-PLUGIN.pom)
templates
hibernate
(HibernateEntity.vsl)
spring
(SpringDao.vsl)
(SpringGlobals.vm)
hibernate
(HibernateSearchProperties.vsl)
(SpringHibernateDaoBase.vsl)
(SpringHibernateDaoImpl.vsl)
(SpringHibernateDaoImplManual.vsl
When I run mvn deploy none of the templates directory structure is copied to
the deployment repository but the pom and jar are copied? What am I missing?
Thanks
Jerry
Dependency question
Is there a way to specify a dependency to be available for compilation and test running, but not have it packaged up? We have a situation where some older code that has been converted to maven2 uses a library (SAP JCo if anyone is familiar with it) that must be there to compile and also to run. Some of the tests were written to communicate with SAP, which requires the jar to be in the classpath at runtime. When the application is deployed the jar is provided via the container, so we need it available to run the tests, but don't want it packaged up with the application. Jason Porter O.C. Tanner Information Services Technical Specialist - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Launch a plugin after a site:stage call
Hi, I generate my report site by the maven-site-plugin ( mvn site:stage -DstagingDirectory=...), I would like to launch a plugin after this call. How can i do It ? This configuration do not work because site is a plugin and not a phase: ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId executions execution idjob-after-site-stage-call/id phasesite/phase configuration tasks Regards, Gerald Reinhart
Newbie Repository question
I've been looking into using maven to compile and run automated unit tests for a couple of projects I'm working on. I see a lot of potential for making this process more efficient with Maven. One project is compiling against standard hibernate jars that came with Jboss (4.2.0) and the Microsoft SQL server jdbc driver (sqljdbc.jar). I was able to find hibernate files in the global repository (hibernate/hibernate/version 3.0), but they seem really out of date and don't provide the same classes that the jboss files do. I did not see any hibernate sub-section underneath the jboss repository directories. I would like to set this up correctly, but another issue is most of jars we're using do not have any versioning associated with them. For example the cglib.jar in the jboss lib directory doesn't have a version as part of the filename. If I extract out the files, there doesn't seem to be a version for that file specifically, other than a jboss 4.2.0.GA in the manifest. What would be the correct maven way to place these files in the local repository? Should I place all of the files under a 'jboss' group, or should they be distributed to the hibernate/cglib/commons-collections, etc... stamped with a jboss version? It also seems that I should define dependencies someplace so the project pom file doesn't have to manually include each one. Is there a standard way of defining that as well? Sorry if these questions seem overly paranoid. I just don't want to make some bad decision at this early stage of using Maven and have to go back in the future and rework everything.
flat multi module, package only from top module possible?
Dear list, I created a flat multi module project as in http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html I can not initiate the build from a freshly checked out project (no jars from project in repository) from a child module. Then maven complains that the parent was not found. Reason: Cannot find parent etc Is this the expected behaviour? I would have thought that maven is smart enough to understand that it has to build the parent first. After building from the parent with package, there is of no problem to start a build in the child module. thank you very much, ido - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0.8 test resource loading
Hi!
I've read about the class path order changes in Maven 2.0.8 compared to earlier
releases and this is causing some issues in my builds so I wonder if there is a
best approach to this topic.
I've a class needing a resource file loaded from the class path. This file must
be a different one in the test scenario compared to the one when performing a
build.
To simplify, I've set up a small (web-)project simply holding a unitTest,
loading a resource from the classpath like this:
public void testResourceLoading(){
URL resURL =
TestClassLoading.class.getClassLoader().getResource(resource.txt);
assertNotNull(resURL);
System.out.println(ResURL: +resURL);
assertTrue(Haven't found the resource within test-classes!,
resURL.toString().endsWith(/target/test-classes/resource.txt));
}
When performing a mvn test with maven 2.0.7 the test passes, hence the
correct version of the file is loaded.
A test with maven 2.0.8 fails because the file in /target/classes/ is loaded.
I've read about the forkMode of the surefire plugin, so I tried to set this to
never, but then a test with maven 2.0.8 passes and the one with maven 2.0.7
fails!
Could anyone elaborate on how to deal with this situation?
Thanks in advance and best regards,
Kurt
Just for the sake of completeness, here's my pom.xml for this very simple
project:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdat.telbiomed.arc/groupId
artifactIdclassLoaderTest/artifactId
packagingwar/packaging
version1.0-SNAPSHOT/version
nameclassLoaderTest Maven Webapp/name
urlhttp://maven.apache.org/url
dependencies
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
/dependencies
build
finalNameclassLoaderTest/finalName
resources
resource
directorysrc/main/resources/package//directory
filteringfalse/filtering
includes
includeresource.txt/include
/includes
targetPath//targetPath
/resource
/resources
testResources
testResource
directorysrc/main/resources/test/directory
filteringfalse/filtering
includes
includeresource.txt/include
/includes
targetPath//targetPath
/testResource
/testResources
!-- the test fails with maven 2.0.7 if these settings will be used, otherwise
with 2.0.8
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
forkModenever/forkMode
/configuration
/plugin
/plugins
--
/build
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Respository
I did it myself : my server is a windows share (with Write access restrictions) and is used with URL file:/My_corporate_windows_server/Maven_repository 2007/12/8, James D Carroll [EMAIL PROTECTED]: Is it possible to set up a repository on a network drive without some kind of server acting as an intermediary? Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Optional Proxy Configuration
On Saturday 08 December 2007 13:40:25 Heinrich Nirschl wrote: On Dec 8, 2007 12:58 PM, Marco Bakera [EMAIL PROTECTED] wrote: On Saturday 08 December 2007 08:35:07 Heinrich Nirschl wrote: On Dec 8, 2007 8:13 AM, Marco Bakera [EMAIL PROTECTED] wrote: Hello everybody. At work I need a proxy for maven to work while I don't need one at home. So I have to change my settings.xml back and forth during work at home and and at work. So is it possible to simply turn off the proxy server configuration with a command line option? The -s option allows you to use a different user settings file. Although this is possible I don't know whether it is the preferred way of doing, since I just want to turn off one part of the settings file while keeping the others as is. Is this a serious problem? How often do you change the settings file? If you are *really* worried about inconsistencies you could even come up with a little transformation (e.g. in XSLT) that converts one setting file to the other. You are right, of course I'm not *really* worried about this procedure but just had the feeling of doing a hack (the xslt variant would be a hack too). So I have chosen to better ask for a better practice. :) If my setup is too special and therefore (currently) not supported I will do if with two setting.xml files. Anyhow, thanks for help and greetings, Marco Bakera. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release Plugin/SCM Scheme
On Dec 8, 2007 7:52 AM, Marco Bakera [EMAIL PROTECTED] wrote: Does really nobody have a clue on this question? Or has the mail been overseen due to Santa Claus happenings?! ;) You didn't provide enough information to enable anyone to help. What url are you trying to use? What documentation have you already looked at? I found this page: http://maven.apache.org/scm/cvs.html -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
continuum 1.1 and guest user
I would like to just have 1-2 admins and everyone else can be guest for continuum 1.1. This seemed possible in continuum 1.0, but I must be missing some step to know how to do it with continuum 1.1. After I log in the first time to set up admin, I'm still not understanding how to log in so as to become guest (as well as how to give guest more privs). Thanks!
Re: deploy jar with dependencies
FatJar Sonar, Nishant wrote: Hi I need to build on a machine and deploy the jar on another machine. Now there are dependencies in my jar are to be supplied with this jar, as it is no the build machine the classpath. How should I create a single distributable comprising all the jars? Like Myjar.jar |---com.myapp.app |---lib |--dependent jars Regards, Nishant Sonar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Craig Dickson is out of the office.
I will be out of the office starting 11/26/2007 and will not return until 02/18/2008. I will respond to your message when I return.
Craig Dickson is out of the office.
I will be out of the office starting 11/26/2007 and will not return until 02/18/2008. I will respond to your message when I return.
Re: Dependency question
As you said When the application is deployed the jar is provided via the container. So simply try the provided scope ! provided dependencies are commonly used for java API (servlet, jta ...) taht are part of the JEE server runtime BUT required to compile and test. Nico. 2007/12/7, Jason Porter [EMAIL PROTECTED]: Is there a way to specify a dependency to be available for compilation and test running, but not have it packaged up? We have a situation where some older code that has been converted to maven2 uses a library (SAP JCo if anyone is familiar with it) that must be there to compile and also to run. Some of the tests were written to communicate with SAP, which requires the jar to be in the classpath at runtime. When the application is deployed the jar is provided via the container, so we need it available to run the tests, but don't want it packaged up with the application. Jason Porter O.C. Tanner Information Services Technical Specialist - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release Plugin/SCM Scheme
Does really nobody have a clue on this question? Or has the mail been overseen due to Santa Claus happenings?! ;) On Thursday 06 December 2007 10:35:59 you wrote: Hey everybody, Mavens release plugin relies on the SCM element in the pom file for tagging the release. I'm using Eclipse with CVS, so CVS transport type is extssh. However this is not a legal scm transport specifier for CVS in scm. When using only ext (instead of extssh) Maven claims The scm url is invalid. - The connection string contains too few tokens. Any suggestions? Thanks and greetings, Marco. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: flat multi module, package only from top module possible?
On Dec 6, 2007 10:17 AM, Ido M. Tamir [EMAIL PROTECTED] wrote: I created a flat multi module project as in http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html I can not initiate the build from a freshly checked out project (no jars from project in repository) from a child module. Then maven complains that the parent was not found. Reason: Cannot find parent etc Is this the expected behaviour? How did you define the parent in the child that refuses to build? By default Maven looks one directory above for the parent (in ../pom.xml). If that's not where the parent is, try using the parent/relativePath element to point to it. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Respository
Is it possible to set up a repository on a network drive without some kind of server acting as an intermediary? Thanks, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: continuum 1.1 and guest user
On Dec 6, 2007 3:22 PM, deckrider+mvn [EMAIL PROTECTED] wrote: I would like to just have 1-2 admins and everyone else can be guest for continuum 1.1. This seemed possible in continuum 1.0, but I must be missing some step to know how to do it with continuum 1.1. After I log in the first time to set up admin, I'm still not understanding how to log in so as to become guest (as well as how to give guest more privs). Log in as admin, then click the Users button at the left, choose the guest user, and grant it the roles you want it to have. Guest is the unauthenticated user, so you don't log in to become guest. For example, if you make the guest user a global project developer, then anyone with access to the server will be able to add projects, kick off builds, etc. Is that what you want? -- Wendy
generating-sources missing resources
I'm trying to convert the source-generation of a legacy system into a mavenized project. Basically I need to run a couple of java classes from an already existing dependency (during the generate-sources phase I assume) which should populate my source directories. The problem I'm having is that it seems maven is ignoring my resource declarations during the generate-sources phase. Is this normal? To run the two java classes requried for source generation I'm using the exec-maven-plugin and it definitely doesn't find my declared resources on it's classpath.. I've managed to find some hacks around this, like telling the maven-resources-plugin to execute the 'resources' goal during generate-sources, but that doesn't seem so clean to me, as it's probably going to do it again during the generate-resources phase.. Any ideas?
Re: generating-sources missing resources
Tell me if I understand well : your code-generator has been packaged as a Mojo and is used in another project. It loads some config file from classpath to generate code. Maven plugins run in isolated classloaders, they have no acces to the current project classpath. First option (the maven way) is to rework the code generator to use a parametrized folder to load config files used in generation. You then just have to set a new @parameter in the Mojo. Second option - if changing the legacy code is too complex - is to setup a new URLClassloader with the plugin classloader as parent and add the project resources folder. You can the load the generator class using this classloader and invoke the generate() method by reflexion. Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: I'm trying to convert the source-generation of a legacy system into a mavenized project. Basically I need to run a couple of java classes from an already existing dependency (during the generate-sources phase I assume) which should populate my source directories. The problem I'm having is that it seems maven is ignoring my resource declarations during the generate-sources phase. Is this normal? To run the two java classes requried for source generation I'm using the exec-maven-plugin and it definitely doesn't find my declared resources on it's classpath.. I've managed to find some hacks around this, like telling the maven-resources-plugin to execute the 'resources' goal during generate-sources, but that doesn't seem so clean to me, as it's probably going to do it again during the generate-resources phase.. Any ideas?
Re: generating-sources missing resources
Thanks for the prompt reply. My code-generator (the java classes anyways) have been packaged as a regular jar artifact. I am using the Maven Exec Plug-In java goal, http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html. It states 'Executes the supplied java class in the current VM with the enclosing project's dependencies as classpath.' That is accurate, as the plugin has no problems finding the classes in the pom's dependencies. However it doesn't seem to include the enclosing POM's resources.. From the sounds of it this is likely an issue with the codehaus plugin more than a core maven issue. I'll pose this question on their mailing list also. Kal. On Dec 8, 2007 2:14 PM, nicolas de loof [EMAIL PROTECTED] wrote: Tell me if I understand well : your code-generator has been packaged as a Mojo and is used in another project. It loads some config file from classpath to generate code. Maven plugins run in isolated classloaders, they have no acces to the current project classpath. First option (the maven way) is to rework the code generator to use a parametrized folder to load config files used in generation. You then just have to set a new @parameter in the Mojo. Second option - if changing the legacy code is too complex - is to setup a new URLClassloader with the plugin classloader as parent and add the project resources folder. You can the load the generator class using this classloader and invoke the generate() method by reflexion. Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: I'm trying to convert the source-generation of a legacy system into a mavenized project. Basically I need to run a couple of java classes from an already existing dependency (during the generate-sources phase I assume) which should populate my source directories. The problem I'm having is that it seems maven is ignoring my resource declarations during the generate-sources phase. Is this normal? To run the two java classes requried for source generation I'm using the exec-maven-plugin and it definitely doesn't find my declared resources on it's classpath.. I've managed to find some hacks around this, like telling the maven-resources-plugin to execute the 'resources' goal during generate-sources, but that doesn't seem so clean to me, as it's probably going to do it again during the generate-resources phase.. Any ideas?
Re: generating-sources missing resources
Thank you, I've forwarded the discussion to the codehaus mailing list to see what their opinion is on the matter. On Dec 8, 2007 3:47 PM, nicolas de loof [EMAIL PROTECTED] wrote: enclosing project's dependencies as classpath does not mean enclosing project classpath. You have acces to all declared dependencies BUT not to the project classes/ressources. (this may be a valuale enhancement to the plugin). Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: Thanks for the prompt reply. My code-generator (the java classes anyways) have been packaged as a regular jar artifact. I am using the Maven Exec Plug-In java goal, http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html. It states 'Executes the supplied java class in the current VM with the enclosing project's dependencies as classpath.' That is accurate, as the plugin has no problems finding the classes in the pom's dependencies. However it doesn't seem to include the enclosing POM's resources.. From the sounds of it this is likely an issue with the codehaus plugin more than a core maven issue. I'll pose this question on their mailing list also. Kal. On Dec 8, 2007 2:14 PM, nicolas de loof [EMAIL PROTECTED] wrote: Tell me if I understand well : your code-generator has been packaged as a Mojo and is used in another project. It loads some config file from classpath to generate code. Maven plugins run in isolated classloaders, they have no acces to the current project classpath. First option (the maven way) is to rework the code generator to use a parametrized folder to load config files used in generation. You then just have to set a new @parameter in the Mojo. Second option - if changing the legacy code is too complex - is to setup a new URLClassloader with the plugin classloader as parent and add the project resources folder. You can the load the generator class using this classloader and invoke the generate() method by reflexion. Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: I'm trying to convert the source-generation of a legacy system into a mavenized project. Basically I need to run a couple of java classes from an already existing dependency (during the generate-sources phase I assume) which should populate my source directories. The problem I'm having is that it seems maven is ignoring my resource declarations during the generate-sources phase. Is this normal? To run the two java classes requried for source generation I'm using the exec-maven-plugin and it definitely doesn't find my declared resources on it's classpath.. I've managed to find some hacks around this, like telling the maven-resources-plugin to execute the 'resources' goal during generate-sources, but that doesn't seem so clean to me, as it's probably going to do it again during the generate-resources phase.. Any ideas?
Re: generating-sources missing resources
enclosing project's dependencies as classpath does not mean enclosing project classpath. You have acces to all declared dependencies BUT not to the project classes/ressources. (this may be a valuale enhancement to the plugin). Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: Thanks for the prompt reply. My code-generator (the java classes anyways) have been packaged as a regular jar artifact. I am using the Maven Exec Plug-In java goal, http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html. It states 'Executes the supplied java class in the current VM with the enclosing project's dependencies as classpath.' That is accurate, as the plugin has no problems finding the classes in the pom's dependencies. However it doesn't seem to include the enclosing POM's resources.. From the sounds of it this is likely an issue with the codehaus plugin more than a core maven issue. I'll pose this question on their mailing list also. Kal. On Dec 8, 2007 2:14 PM, nicolas de loof [EMAIL PROTECTED] wrote: Tell me if I understand well : your code-generator has been packaged as a Mojo and is used in another project. It loads some config file from classpath to generate code. Maven plugins run in isolated classloaders, they have no acces to the current project classpath. First option (the maven way) is to rework the code generator to use a parametrized folder to load config files used in generation. You then just have to set a new @parameter in the Mojo. Second option - if changing the legacy code is too complex - is to setup a new URLClassloader with the plugin classloader as parent and add the project resources folder. You can the load the generator class using this classloader and invoke the generate() method by reflexion. Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: I'm trying to convert the source-generation of a legacy system into a mavenized project. Basically I need to run a couple of java classes from an already existing dependency (during the generate-sources phase I assume) which should populate my source directories. The problem I'm having is that it seems maven is ignoring my resource declarations during the generate-sources phase. Is this normal? To run the two java classes requried for source generation I'm using the exec-maven-plugin and it definitely doesn't find my declared resources on it's classpath.. I've managed to find some hacks around this, like telling the maven-resources-plugin to execute the 'resources' goal during generate-sources, but that doesn't seem so clean to me, as it's probably going to do it again during the generate-resources phase.. Any ideas?
Re: generating-sources missing resources
I would go ahead and make your code generator a full-blown Maven plugin, as Nicolas assumed initially. I've done this myself a few times and it is pretty simple. Then use the @parameter to specify the location of your resources, and poof, you're done. Unless of course you have a good reason for not doing this. Wayne On 12/8/07, Kallin Nagelberg [EMAIL PROTECTED] wrote: Thank you, I've forwarded the discussion to the codehaus mailing list to see what their opinion is on the matter. On Dec 8, 2007 3:47 PM, nicolas de loof [EMAIL PROTECTED] wrote: enclosing project's dependencies as classpath does not mean enclosing project classpath. You have acces to all declared dependencies BUT not to the project classes/ressources. (this may be a valuale enhancement to the plugin). Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: Thanks for the prompt reply. My code-generator (the java classes anyways) have been packaged as a regular jar artifact. I am using the Maven Exec Plug-In java goal, http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html. It states 'Executes the supplied java class in the current VM with the enclosing project's dependencies as classpath.' That is accurate, as the plugin has no problems finding the classes in the pom's dependencies. However it doesn't seem to include the enclosing POM's resources.. From the sounds of it this is likely an issue with the codehaus plugin more than a core maven issue. I'll pose this question on their mailing list also. Kal. On Dec 8, 2007 2:14 PM, nicolas de loof [EMAIL PROTECTED] wrote: Tell me if I understand well : your code-generator has been packaged as a Mojo and is used in another project. It loads some config file from classpath to generate code. Maven plugins run in isolated classloaders, they have no acces to the current project classpath. First option (the maven way) is to rework the code generator to use a parametrized folder to load config files used in generation. You then just have to set a new @parameter in the Mojo. Second option - if changing the legacy code is too complex - is to setup a new URLClassloader with the plugin classloader as parent and add the project resources folder. You can the load the generator class using this classloader and invoke the generate() method by reflexion. Nico. 2007/12/8, Kallin Nagelberg [EMAIL PROTECTED]: I'm trying to convert the source-generation of a legacy system into a mavenized project. Basically I need to run a couple of java classes from an already existing dependency (during the generate-sources phase I assume) which should populate my source directories. The problem I'm having is that it seems maven is ignoring my resource declarations during the generate-sources phase. Is this normal? To run the two java classes requried for source generation I'm using the exec-maven-plugin and it definitely doesn't find my declared resources on it's classpath.. I've managed to find some hacks around this, like telling the maven-resources-plugin to execute the 'resources' goal during generate-sources, but that doesn't seem so clean to me, as it's probably going to do it again during the generate-resources phase.. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
JDK 1.5 java.lang.Enum Buid Failure using Maven 2.0.8
I am using JDK 1.5 / Maven 2.0.8 and am attempting mvn clean install on a
simple project that contains the following snippet:
...
public final Class? extends Enum? extends IDTOPhase
getDTOPhaseLifeCycleStrategy(){
return someEnumClass;
}
...
for(java.lang.Enum? extends IDTOPhase phase :
getDTOPhaseLifeCycleStrategy().getEnumConstants()){
...
}
...
The problem is that this compiles w/o a problem using ANT (or Eclipse build),
but fails using Maven. I get the error:
... incompatible types
found : java.lang.Enum? extends IDTOPhase
required : java.lang.Enum? extends IDTOPhase
I even set the maven-compiler-plugin to ensure compilation in 1.5
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
Any clue??? Thanks!
