Ant tasks for Maven and java.net dependencies
Hi, I am trying to use the Ant task for Maven with the root Maven POM for the Castor project for download the dependencies and place them into a lib directory. What I have observed is that there's a few dependencies missing when I run the corresponding Ant target. But if I use Maven for the build process, the missing JARs are downloaded as well and placed into my local repository. I have tried to define remoteRepository entries for the java.net and the Maven 2 java.net repositories (where e.g. java.transaction:jta:1.1.1B resides), but this does not make a difference. Any idea what I could try in addition ? Having said that, all other dependencies are resolved and copied without any problems. It looks like it's just the dependencies that are not synced globally that create a problem. Regards Werner Castor, committer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [Maven Ant Tasks] Can't load dependencies
No problem here with Maven Ant Tasks 2.0.6. What version of Maven Ant Tasks are you using? "Result of execution is that artifact can't be loaded." What is the symptom? Could you provide the output? Does it happen only with commons-logging-1.0.1 or with any artifact? Le lundi 4 juin 2007, Oleg Yavorsky a écrit : > I try to get dependencies using next task: > url="http://repo1.maven.org/maven2";> > > > > > > artifactId="commons-logging" version="1.0.1" /> > > Result of execution is that artifact can't be loaded. I tried different > artifacts without much success. It works only when artifact already exists > in local repository. > > I've checked proxy settings and they are correct. Also I was able to > download artifacts by hand from repository (I thought it could be down) . > Did someone have same problems and found reason? > > - > Вы уже с Yahoo!? > Испытайте обновленную и улучшенную Yahoo! Почту! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] pde-maven-plugin fails during release
I am aware about there are some badly coded Java programs that cannot
deal with spaces in Windoze paths... Therefore I am using only the short
DOS notation (PROGRA~1 instead of "Program Files").
I have only one feature -- its pom.xml is appended below.
I moved the checkout directory from ./${basedir}/target to . (so it is
now at the same depth as ${basedir}). Did a mvn package and the build
succeeds! My conclusion, is that the problem arises from those relative
paths in the build.xml file below.
Adrian.
Here is the feature's pom.xml:
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";>
4.0.0
com.acme.lang.eclipse
acme-lang-eclipse
1.0-alpha-1
com.acme.lang.eclipse.feature
acme-lang-eclipse-feature
1.0-alpha-1-SNAPSHOT
zip
acme Language Feature for Eclipse
Integrates acme projects into the Eclipse IDE.
scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
scm:svn:https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
https://someserver.com:443/acme/lang/trunk/eclipse/features/com.acme.lang.eclipse.feature
hosted-projects.com
Central acme Repository
https://someserver.com:443/dav/acme/repository
true
false
[EMAIL PROTECTED]
Central acme Repository
https://someserver.com:443/dav/acme/snapshots
false
true
org.codehaus.mojo
pde-maven-plugin
true
${eclipse.home}
org.apache.maven.plugins
maven-eclipse-plugin
true
org.eclipse.pde.FeatureNature
org.eclipse.pde.FeatureBuilder
Dan Tran wrote:
how many features you do you have? could you post the pom on for the
feature?
I see you are using Program Files on your path , this make me nervous, even
thou it should work :-)
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.ui_3.2.0.I20060605-
1400.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
> and you have no problem during normal build?
>
> what does your projects structure look like?
>
> -D
>
>
> On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
>>
>> Hi all,
>>
>> I am trying to release my Eclipse plugins and I am getting lots of
"The
>> import some.eclipse.package cannot be resolved" compilation errors
>> during the release:perform goal.
>>
>> I have tried to run mvn package on the target/checkout directory and I
>> am getting the same errors... It seems that the build.xml file cannot
be
>> run outside of the ${basedir} directory...
>>
>> Any workaround for this situation?
>> How about tweaking the release:perform goal?
>>
>> Adrian.
>>
>>
>> -
>> 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: [hibernate-dev] docbook + maven
Mark and I already discussed this. But its a different discussion, since he does not deal with pre-packaged styles... On Mon, 2007-06-04 at 21:38 +0200, Max Rydahl Andersen wrote: > one thing is for sure, the current image location in our docbook is > annoying ;( > > It is not relative to where the xml files are and hence it does not show up > in e.g. xmlmind. > > What makes most sense to me is that the images is located > relative/correctly based > on the actual xml they are referred in. > > I know Marc Proctor solved this (at least he claims so) - but I don't know > how so > I cc'ed him in ;) > > /max > > > > > As part of migrating Hibernate to use Maven, one of the big issues I ran > > into was the current state of DocBook plugins for Maven. The current > > mojo-codehaus hosted plugin is insufficient. There is another more > > widely used one done by one Wilfred Springer as part of something called > > "agilejava". The "agilejava" one is fairly full featured, but is really > > pretty bare bones in terms of configuration (its is mainly a simplistic > > wrapper around the defined DocBook xslt parameters). > > > > In my estimation the, "agilejava" one was closer to usability, but Mr. > > Springer did not seem interested in accepting my volunteer to help > > improve his plugin. So I began implementing my own. > > > > It works off of a slightly different approach than the other two. The > > biggest difference being that custom stylesheets are packaged as > > separate projects and included via the Maven dependency mechanism. This > > allows true reuse of the stylesheets across projects. The other is > > planned better support of translations which is important for Hibernate, > > and most projects using DocBook. > > > > This however led to a conceptual question regarding how to best handle > > image references. As background, in DocBook, the way images normally > > get resolved is as via xslt templates. The DocBook supplied templates > > do a hard file lookup relative to a xslt parameter named 'img.src.path' > > if it is set; and really this is format specific as well. Regardless, > > though, I need a mechanism to access the image files from these "style > > projects" and be able to resolve reference to them from the DocBook > > source or xsl stylesheets. I have identified a few potential approaches > > to achieve that: > > 1) force separation of (a) xslt and (b) resources like images/css into > > separate projects. Specifically, #b would need a custom packaging which > > would allow me to find resources and unarchive them locally into a > > staging dir for use in 'img.src.path'. A variation on this would be to > > bundle them together with a custom packaging and somehow extract just > > the "resources". > > 2) Apply custom graphics resolution templates to the built xsl > > transformers, hoping that the custom xslt does not itself do this. > > > > I'm not (necessarily) looking for volunteers (although certainly that is > > welcome). More I just need people's thoughts on the various approaches, > > especially those using or familiar with DocBook. > > > > Thanks, > > Steve > > > > ___ > > hibernate-dev mailing list > > [EMAIL PROTECTED] > > https://lists.jboss.org/mailman/listinfo/hibernate-dev > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [hibernate-dev] docbook + maven
yes I raised that with steve, after being abused for some time, I think I eventually persuaded him to include the properties necessary for this. Mark Max Rydahl Andersen wrote: one thing is for sure, the current image location in our docbook is annoying ;( It is not relative to where the xml files are and hence it does not show up in e.g. xmlmind. What makes most sense to me is that the images is located relative/correctly based on the actual xml they are referred in. I know Marc Proctor solved this (at least he claims so) - but I don't know how so I cc'ed him in ;) /max As part of migrating Hibernate to use Maven, one of the big issues I ran into was the current state of DocBook plugins for Maven. The current mojo-codehaus hosted plugin is insufficient. There is another more widely used one done by one Wilfred Springer as part of something called "agilejava". The "agilejava" one is fairly full featured, but is really pretty bare bones in terms of configuration (its is mainly a simplistic wrapper around the defined DocBook xslt parameters). In my estimation the, "agilejava" one was closer to usability, but Mr. Springer did not seem interested in accepting my volunteer to help improve his plugin. So I began implementing my own. It works off of a slightly different approach than the other two. The biggest difference being that custom stylesheets are packaged as separate projects and included via the Maven dependency mechanism. This allows true reuse of the stylesheets across projects. The other is planned better support of translations which is important for Hibernate, and most projects using DocBook. This however led to a conceptual question regarding how to best handle image references. As background, in DocBook, the way images normally get resolved is as via xslt templates. The DocBook supplied templates do a hard file lookup relative to a xslt parameter named 'img.src.path' if it is set; and really this is format specific as well. Regardless, though, I need a mechanism to access the image files from these "style projects" and be able to resolve reference to them from the DocBook source or xsl stylesheets. I have identified a few potential approaches to achieve that: 1) force separation of (a) xslt and (b) resources like images/css into separate projects. Specifically, #b would need a custom packaging which would allow me to find resources and unarchive them locally into a staging dir for use in 'img.src.path'. A variation on this would be to bundle them together with a custom packaging and somehow extract just the "resources". 2) Apply custom graphics resolution templates to the built xsl transformers, hoping that the custom xslt does not itself do this. I'm not (necessarily) looking for volunteers (although certainly that is welcome). More I just need people's thoughts on the various approaches, especially those using or familiar with DocBook. Thanks, Steve ___ hibernate-dev mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/hibernate-dev -- Registered Address: Red Hat UK Ltd, Amberley Place, 107-111 Peascod Street, Windsor, Berkshire, SI4 1TE, United Kingdom. Registered in UK and Wales under Company Registration No. 3798903 Directors: Michael Cunningham (USA), Charlie Peters (USA) and David Owens (Ireland) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Surefire 2.4-SNAPSHOT errors
On 4 Jun 07, at 11:14 PM 4 Jun 07, Brett Porter wrote: Yep, no problems there. What we are primarily encountering are platform differences, or regressions in TestNG (since we don't have ITs for that - yet). Cool, I just wanted to make sure base stuff was still all good. - Brett On 05/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: Brett, Have you run the new surefire with the ITs? That would probably be a good baseline to make sure the old functionality works. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven tweak install goal
Use maven-dependency-plugin:copy and bind it to the install phase (user bound plugins will execute after the default ones, so will happen after the install plugin) -Original Message- From: Alessandro Ferrucci [mailto:[EMAIL PROTECTED] Sent: Sunday, June 03, 2007 7:59 PM To: users@maven.apache.org Subject: Maven tweak install goal hey guys, here's the use case, I wanna be able to copy a set of jars to some directory after maven has created and installed them in the m2 repo. Can anyone give me any hints or flat out solution to this problem? thanks a lot alessandro ferrucci =] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Surefire 2.4-SNAPSHOT errors
Yep, no problems there. What we are primarily encountering are platform differences, or regressions in TestNG (since we don't have ITs for that - yet). - Brett On 05/06/07, Jason van Zyl <[EMAIL PROTECTED]> wrote: Brett, Have you run the new surefire with the ITs? That would probably be a good baseline to make sure the old functionality works. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant's Java task in Maven?
Thank you, Jo and Markku! It is working now... What about if I have mulitple main Java classes? With Ant, I used to have different tasks to execute different Java classes: On 6/4/07, Markku Saarela <[EMAIL PROTECTED]> wrote: Use Maven Exec Plugin http://mojo.codehaus.org/exec-maven-plugin/ - markku hezjing wrote: > Hi Jo > > I hope I can do this the "Maven's way" without using the Antrun plugin. > > Any better idea? > > > On 6/4/07, Jo Vandermeeren <[EMAIL PROTECTED]> wrote: >> You can call your Ant task with the maven-antrun-plugin: >> http://maven.apache.org/plugins/maven-antrun-plugin/ >> >> On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: >> > >> > Hi! >> > >> > With Ant, we have Java task to execute a main Java class. >> > >> > How can I do this with Maven? >> > >> > >> > -- >> > >> > Hez >> > >> > - >> > 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] -- Hez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven not respecting order of profiles passed in on the command line
On 6/4/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: Please enlighten me - how do you avoid using profiles entirely? You will need to describe your use case. Basically a profile should only be used to either a) externalise OS dependent settings, e.g. location of eclipse installation. In general for all most all maven plugins you never need to do this b) to turn on additional plugins that you dont want include in the default build, e.g. an integration test suite run. You are using -Ppersonal,StackDefaults,ca-lime,root which just feels wrong. Why are you having to select these values? Why are they not the defined defaults? There was a discussion a while ago about multiple build for different configurations, e.g. Tomcat/War, JBoss/Ear, etc. I can't recall the result of the discussion. But if you always want to build each of these configurations then you may want to consider creating a module per configuration that has all the correct settings defined for that build. e.g. Root + configurationA (contains A's specific configurationd details) + configurationB (contains B's specific configurationd details) + module1 + ... where all configurations depend upon independent artifacts. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Preflight check for 2.0.7
I have built a snapshot for 2.0.7 and put it here: http://people.apache.org/~jvanzyl/ I figure folks are going to try and squeeze in more issues so what I plan is let people state their case for issues and I'll slot those into 2.0.8. I'll look those over and push whatever I can into 2.0.7 but I would like to call for vote on Wednesday let people mess around and release it on Monday. And you can see the roadmap here: http://jira.codehaus.org/browse/MNG? report=com.atlassian.jira.plugin.system.project:roadmap-panel Thanks, Jason -- Jason van Zyl Founder and PMC Chair, Apache Maven jason at sonatype dot com -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven One Plugin 1.1 Released
The Maven team is pleased to announce the release of Maven One Plugin, version 1.1. http://maven.apache.org/plugins/maven-one-plugin/ Release Notes - Maven 2.x One Plugin - Version 1.1 ** Bug * [MONE-1] - building an m1 plugin inside the reactor doesn't include the plugin.jelly and properties files * [MONE-8] - The goal one:convert is not implemented in version 1.0 although it is documented and should work. ** New Feature * [MONE-7] - Add the ability to convert a pom from M1 to M2 ** Task * [MONE-4] - Review Plugin Documentation Enjoy! - The Maven Team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-release-plugin: Unable to find the mojo perform
Hi The .rip files that you see are created by maven-stage-plugin, which is used to transfer Maven releases from a staging area into the real repository. The .rip files are normally removed after a successful transfer, so I'm guessing that something went wrong here. You can safely remove the .rip files from your local repository. Graham Leggett wrote: Hi all, I am suddenly getting the following exception below when attempting to perform a release of our project using maven v2.0.4 on Windows. I see there is a directory within the repository called 2.0-beta-6.rip - is this somehow relevant? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable to find the mojo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plugin 'org.apache.maven.plugins:maven-release-plugin' org/jdom/filter/Filter [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable to find the mojo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plugin 'org.apache.maven.plugins:maven-release-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:538) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mo jo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plu gin 'org.apache.maven.plugins:maven-release-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul tPluginManager.java:533) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupExc eption: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven .plugins:maven-release-plugin:2.0-beta-6:perform', it could not be started at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:339) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul tPluginManager.java:524) ... 18 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycle Exception: Error starting component at org.codehaus.plexus.component.manager.AbstractComponentManager.startC omponentLifecycle(AbstractComponentManager.java:109) at org.codehaus.plexus.component.manager.AbstractComponentManager.create ComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo mponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:331) ... 20 more Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecution Exception: Error composing component at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPha se.execute(CompositionPhase.jav
Re: [m2] pde-maven-plugin fails during release
how many features you do you have? could you post the pom on for the
feature?
I see you are using Program Files on your path , this make me nervous, even
thou it should work :-)
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
> and you have no problem during normal build?
>
> what does your projects structure look like?
>
> -D
>
>
> On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
>>
>> Hi all,
>>
>> I am trying to release my Eclipse plugins and I am getting lots of "The
>> import some.eclipse.package cannot be resolved" compilation errors
>> during the release:perform goal.
>>
>> I have tried to run mvn package on the target/checkout directory and I
>> am getting the same errors... It seems that the build.xml file cannot
be
>> run outside of the ${basedir} directory...
>>
>> Any workaround for this situation?
>> How about tweaking the release:perform goal?
>>
>> Adrian.
>>
>>
>> -
>> 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: Surefire 2.4-SNAPSHOT errors
Brett, Have you run the new surefire with the ITs? That would probably be a good baseline to make sure the old functionality works. On 4 Jun 07, at 8:29 AM 4 Jun 07, Brett Porter wrote: I've just reopened SUREFIRE-316 for re-examination since reports have resurfaced. - Brett On 04/06/07, Joel Wiegman <[EMAIL PROTECTED]> wrote: Anyone else getting this issue now? I included the --debug flag in my trace. [INFO] [surefire:test] [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire::2.4-SNAPSHOT for project: null:surefire-booter:jar:null from the repository. [DEBUG] surefire: resolved to version 2.4-20070604.115837-15 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: org.apache.maven.surefire:surefire:pom:2.4-SNAPSHOT from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Adding managed depedendencies for unknown:surefire-booter [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4-SNAPSHOT [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4-SNAPSHOT [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7 [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT:runtime (selected for runtime) [DEBUG] commons-lang:commons-lang:jar:2.1:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1- SNAPSHOT:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0- alpha-7:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.4.1-SNAPSHOT) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.2:runtime (removed - nearer found: 1.4.1-SNAPSHOT) [DEBUG] surefire-api: resolved to version 2.4-20070604.114301-7 from repository apache.snapshots [DEBUG] plexus-utils: resolved to version 1.4.1-20070327.212230-12 from repository codehaus.snapshots [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus- archiver\1.0 -alpha-7\plexus-archiver-1.0-alpha-7.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus- container-de fault\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\classworlds\classworlds\1.1- alpha-2\cla ssworlds-1.1-alpha-2.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\apache\maven\surefire \surefire-boot er\2.4-SNAPSHOT\surefire-booter-2.4-SNAPSHOT.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\commons-lang\commons-lang\2.1 \commons-l ang-2.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-utils \1.4.1- SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\apache\maven\surefire \surefire-api\ 2.4-SNAPSHOT\surefire-api-2.4-SNAPSHOT.jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] org.testng:testng:jar:jdk15:5.5:test (selected for test) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\testng\testng\5.5\testng-5.5- jdk15. jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Skipping disabled repository central [DEBUG] surefire-testng: resolved to version 2.4-20070604.114301-6 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire-providers::2.4-SNAPSHOT for project: null:surefire-testng:jar:null from the repository. [DEBUG] Skipping disabled repository central [DEBUG] surefire-providers: resolved to version 2.4-20070604.114301-7 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire::2.4-SNAPSH
Re: Inclusions of test classes not inherited by TestCase
Two options: 1. Name your files differently. ThisIsNotATestFile.java falls out of the regexp. 2. Use excludes: http://maven.apache.org/plugins/maven-surefire-plugin/examples/inclusion-exclusion.html Wayne On 6/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Hi *, I'm new to maven 2 and the surefire plugin and I am irritated about the inclusions of tests. The doc says: By default, the surefire plugin will automatically include all test classes with the following wildcard patterns: "**/Test*.java" - includes all of its subdirectory and all java filenames that start with "Test". "**/*Test.java" - includes all of its subdirectory and all java filenames that end with "Test". "**/*TestCase.java" - includes all of its subdirectory and all java filenames that end with "TestCase". Why is the superclass of a test not considered for this? It seems that a class named MyTest that extends java.lang.Object is executed when running surefire:test, which does not make any sense. Regards, -- Martin Pt! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger - 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: Inclusions of test classes not inherited by TestCase
Hi, Martin, you're the former Exolution employee, aren't you? If so, greetings from Stuttgart. :-) On 6/4/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Why is the superclass of a test not considered for this? It seems that a class named MyTest that extends java.lang.Object is executed when running surefire:test, which does not make any sense. I do believe, that the surefire plugin (or JUnit, don't know exactly which) does consider the superclass, or at least factors like whether a class is abstract or not. For example, I definitely do have projects with classes like "AbstractFooTestCase" and the surefire plugin doesn't run them. The wildcard patterns are, IMO, only describing a set of classes, which are considered for running as tests. Jochen -- Women have the ability to wind you round their little finger. Daughters can use all of the fingers together. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Enable file protocol for adding Maven 2.0.x projects in 1.1-alpha-2
In 1.0.3, there was a section in apps\continuum\conf\application.xml to allow the file protocol to add a project to continuum. How do I go about enabling this in 1.1-alpha-2? Thanks, Peter Hayes Architecture & Shared Technology Services | Fidelity Investments Management Technology
docbook + maven
As part of migrating Hibernate to use Maven, one of the big issues I ran into was the current state of DocBook plugins for Maven. The current mojo-codehaus hosted plugin is insufficient. There is another more widely used one done by one Wilfred Springer as part of something called "agilejava". The "agilejava" one is fairly full featured, but is really pretty bare bones in terms of configuration (its is mainly a simplistic wrapper around the defined DocBook xslt parameters). In my estimation the, "agilejava" one was closer to usability, but Mr. Springer did not seem interested in accepting my volunteer to help improve his plugin. So I began implementing my own. It works off of a slightly different approach than the other two. The biggest difference being that custom stylesheets are packaged as separate projects and included via the Maven dependency mechanism. This allows true reuse of the stylesheets across projects. The other is planned better support of translations which is important for Hibernate, and most projects using DocBook. This however led to a conceptual question regarding how to best handle image references. As background, in DocBook, the way images normally get resolved is as via xslt templates. The DocBook supplied templates do a hard file lookup relative to a xslt parameter named 'img.src.path' if it is set; and really this is format specific as well. Regardless, though, I need a mechanism to access the image files from these "style projects" and be able to resolve reference to them from the DocBook source or xsl stylesheets. I have identified a few potential approaches to achieve that: 1) force separation of (a) xslt and (b) resources like images/css into separate projects. Specifically, #b would need a custom packaging which would allow me to find resources and unarchive them locally into a staging dir for use in 'img.src.path'. A variation on this would be to bundle them together with a custom packaging and somehow extract just the "resources". 2) Apply custom graphics resolution templates to the built xsl transformers, hoping that the custom xslt does not itself do this. I'm not (necessarily) looking for volunteers (although certainly that is welcome). More I just need people's thoughts on the various approaches, especially those using or familiar with DocBook. Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [hibernate-dev] docbook + maven
one thing is for sure, the current image location in our docbook is annoying ;( It is not relative to where the xml files are and hence it does not show up in e.g. xmlmind. What makes most sense to me is that the images is located relative/correctly based on the actual xml they are referred in. I know Marc Proctor solved this (at least he claims so) - but I don't know how so I cc'ed him in ;) /max As part of migrating Hibernate to use Maven, one of the big issues I ran into was the current state of DocBook plugins for Maven. The current mojo-codehaus hosted plugin is insufficient. There is another more widely used one done by one Wilfred Springer as part of something called "agilejava". The "agilejava" one is fairly full featured, but is really pretty bare bones in terms of configuration (its is mainly a simplistic wrapper around the defined DocBook xslt parameters). In my estimation the, "agilejava" one was closer to usability, but Mr. Springer did not seem interested in accepting my volunteer to help improve his plugin. So I began implementing my own. It works off of a slightly different approach than the other two. The biggest difference being that custom stylesheets are packaged as separate projects and included via the Maven dependency mechanism. This allows true reuse of the stylesheets across projects. The other is planned better support of translations which is important for Hibernate, and most projects using DocBook. This however led to a conceptual question regarding how to best handle image references. As background, in DocBook, the way images normally get resolved is as via xslt templates. The DocBook supplied templates do a hard file lookup relative to a xslt parameter named 'img.src.path' if it is set; and really this is format specific as well. Regardless, though, I need a mechanism to access the image files from these "style projects" and be able to resolve reference to them from the DocBook source or xsl stylesheets. I have identified a few potential approaches to achieve that: 1) force separation of (a) xslt and (b) resources like images/css into separate projects. Specifically, #b would need a custom packaging which would allow me to find resources and unarchive them locally into a staging dir for use in 'img.src.path'. A variation on this would be to bundle them together with a custom packaging and somehow extract just the "resources". 2) Apply custom graphics resolution templates to the built xsl transformers, hoping that the custom xslt does not itself do this. I'm not (necessarily) looking for volunteers (although certainly that is welcome). More I just need people's thoughts on the various approaches, especially those using or familiar with DocBook. Thanks, Steve ___ hibernate-dev mailing list [EMAIL PROTECTED] https://lists.jboss.org/mailman/listinfo/hibernate-dev -- -- Max Rydahl Andersen callto://max.rydahl.andersen Hibernate [EMAIL PROTECTED] http://hibernate.org JBoss a division of Red Hat [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven tweak install goal
hey guys, here's the use case, I wanna be able to copy a set of jars to some directory after maven has created and installed them in the m2 repo. Can anyone give me any hints or flat out solution to this problem? thanks a lot alessandro ferrucci =]
Re: Ant's Java task in Maven?
Use Maven Exec Plugin http://mojo.codehaus.org/exec-maven-plugin/ - markku hezjing wrote: Hi Jo I hope I can do this the "Maven's way" without using the Antrun plugin. Any better idea? On 6/4/07, Jo Vandermeeren <[EMAIL PROTECTED]> wrote: You can call your Ant task with the maven-antrun-plugin: http://maven.apache.org/plugins/maven-antrun-plugin/ On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: > > Hi! > > With Ant, we have Java task to execute a main Java class. > > How can I do this with Maven? > > > -- > > Hez > > - > 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: Can a POM import a profile from anothe POM?
I wanted to throw a comment into this discussion... Please keep in mind that this level of build reproducibility is not *necessarily* a good thing. The particular issue I have with the reproducibility is actually the testing side of it (functional/integration testing). I would love to use profiles in a drop-in fashion specifically to alter the reproducibility of the builds *from a test perspective*. However, that would mean use of either profiles.xml or profiles in settings.xml, neither of which is allowed to change either of the two things which would be needed, in the name of reproducibility: dependencies and testResources. So I would argue that the notion of "build reproducibility" should be limited to not cover test related concerns. On Sat, 2007-06-02 at 15:09 -0500, Jeff Jensen wrote: > I agree! This I said: "if they truly all have the same profiles and profile > deps", which in your case fails - they share some, but not all share the > same ones. > > In the spirit of idea exchange...if you really don't want poms having > duplicate deps, profiles, etc., I would consider using multiple parent poms. > > One of the things I've done for my current customer is multiple "base poms". > There is the master base pom that they all use eventually extend from, and > every component uses every dependency in that top base pom. I'm sure you > can imagine the next tier or two having one or a few poms. Each component's > pom extends from the correct parent pom so it has only the deps necessary > from the lineage. Component specific info is in its own pom. There are > only a handful of parent poms, so it is not unwieldy. The thing I like is > the "change it in one place". It's just like a class hierarchy in the end, > but pom info instead :-). It is a very large system (approaching 12,000 > classes) and many components (jars, wars, ear - web apps and batches), and > this structure helps us ensure all components have the same dep versions per > release as we need. > > This still has the inconvenience of new versions for _all_ poms when the > top-level master changes, but it is fine for me (and a smaller impact when a > different parent pom changes). Things usually change when many components > are in development mode; hence they are all in SNAPSHOT versions anyway. > > I would appreciate a "better way" suggestion or two if someone has any > ideas. This is what works well for us. > > > -Original Message- > From: Paul Spencer [mailto:[EMAIL PROTECTED] > Sent: Saturday, June 02, 2007 2:15 PM > To: Maven Users List > Subject: Re: Can a POM import a profile from anothe POM? > > Jeff, > My projects fit into the following groups: > o jars containing business logic > o jars containing common utilities > o wars for specific application servers > > All of the above may share a parent POM, but why should a project that > produces a "jars containing business logic" be affected when a profile > that it does not use, like "cargo_tomcat_test", is updated? > > Like you, I am just sharing my thoughts. The more we understand how > something is used, the better decision we can make. Worse yet, we may > learn something new in the process :) > > Paul Spencer > > Jeff Jensen wrote: > > Hi Paul, > > > > Indeed, yes. My comment on lack of build reproducibility was addressing > the > > "shared resource" approach (and you did not suggest), which is usually not > > reproducible unless steps are deliberately made to source control the > shared > > resource in a correct manner (in the codelines of all its dependents); > > apologies for not making that clear! :-) > > > > By the fact that your deps & profiles are in the pom, which is versioned > of > > its own series, the profiles have the build reproducibility. > > > > I also was commenting on the "weigh the effort for the benefit" of holding > > profiles in a parent pom, which you commented was impractical, but the > > benefit of reuse may outweigh the inconvenience, if they truly all have > the > > same profiles and profile deps. That is kind of stating the obvious, but > > wanted to share the thought that it does have value even though I agree it > > can be inconvenient... :-) > > > > > > -Original Message- > > From: Paul Spencer [mailto:[EMAIL PROTECTED] > > Sent: Saturday, June 02, 2007 12:59 PM > > To: Maven Users List > > Subject: Re: Can a POM import a profile from anothe POM? > > > > Jeff, > > I believe I address your concern, which I share, of build > > reproducibility by including a version number on the imported profile's > > artifact, essentially making it behave like a dependency. > > > > Below is the example, which was in my original post. > > *** > > * POM of project which imports the profiles cargo_tomcat_remote and > > * cargo_jetty_remote and selenium-integration-test. > > *** > > > >... > >com.foo.applications > >webapp_1 > >... > > > > > >cargo_tomcat_remote > >com.fo
Inclusions of test classes not inherited by TestCase
Hi *, I'm new to maven 2 and the surefire plugin and I am irritated about the inclusions of tests. The doc says: By default, the surefire plugin will automatically include all test classes with the following wildcard patterns: "**/Test*.java" - includes all of its subdirectory and all java filenames that start with "Test". "**/*Test.java" - includes all of its subdirectory and all java filenames that end with "Test". "**/*TestCase.java" - includes all of its subdirectory and all java filenames that end with "TestCase". Why is the superclass of a test not considered for this? It seems that a class named MyTest that extends java.lang.Object is executed when running surefire:test, which does not make any sense. Regards, -- Martin Pt! Schon vom neuen GMX MultiMessenger gehört? Der kanns mit allen: http://www.gmx.net/de/go/multimessenger - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[Maven Ant Tasks] Can't load dependencies
I try to get dependencies using next task: http://repo1.maven.org/maven2";> Result of execution is that artifact can't be loaded. I tried different artifacts without much success. It works only when artifact already exists in local repository. I've checked proxy settings and they are correct. Also I was able to download artifacts by hand from repository (I thought it could be down) . Did someone have same problems and found reason? - Вы уже с Yahoo!? Испытайте обновленную и улучшенную. Yahoo! Почту!
Re: [m2] pde-maven-plugin fails during release
Hi Dan, and thanks for the fast reply!
I have followed the project structure from the pde-maven-plugin guide:
parent
+features
some.feature
+plugins
some.plugin
another.plugin
I have no problems during normal builds. The artifact is created and I
can deploy and run it under an Eclipse instance -- great!
I am looking in the ${basedir}/build.xml file and I see this section:
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.ui_3.2.0.I20060605-1400.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.runtime_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.osgi_3.2.0.v20060601.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.equinox.common_3.2.0.v20060603.jar"/>
path="../../../../../../../../PROGRA~1/Java/eclipse/plugins/org.eclipse.core.jobs_3.2.0.v20060603.jar"/>
The relative paths here are causing the problem... Is there some way to
regenerate the build.xml during Maven builds? Any other solution?...
Adrian.
Dan Tran wrote:
and you have no problem during normal build?
what does your projects structure look like?
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
during the release:perform goal.
I have tried to run mvn package on the target/checkout directory and I
am getting the same errors... It seems that the build.xml file cannot be
run outside of the ${basedir} directory...
Any workaround for this situation?
How about tweaking the release:perform goal?
Adrian.
-
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: User Interface Performance of 1.1
Hi, Is it just me or anyone else experience the same, alpha-2 does not seem to perform any faster than alpha-1 Thanks. LJ On 5/22/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Performance are fixed in alpha-2 that will be available in few days. Emmanuel Shaun Barriball a écrit : > Are there any known ways to improve the performance of Continuum - as per > the issue below? > >> Issue 2 - Performance >> -- >> Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For >> example, it takes 30 secs+ after I click "MyBigProject" to display the >> contents of the Project Group which has 10 Projects. >> >> Are there any logging settings/go faster buttons that would help >> improve performance? > > > Regards, > Shaun. > > > >
Re: [m2] pde-maven-plugin fails during release
and you have no problem during normal build?
what does your projects structure look like?
-D
On 6/4/07, Adrian Herscu <[EMAIL PROTECTED]> wrote:
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
during the release:perform goal.
I have tried to run mvn package on the target/checkout directory and I
am getting the same errors... It seems that the build.xml file cannot be
run outside of the ${basedir} directory...
Any workaround for this situation?
How about tweaking the release:perform goal?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin shorthand not working as expected
I fixed some code related to the plugin prefixes in http://jira.codehaus.org/browse/MNG-2926. This is currently in 2.0.7-SNAPSHOT, I wonder if it might be fixed at the same time. --Brian -Original Message- From: ertnutler [mailto:[EMAIL PROTECTED] Sent: Friday, June 01, 2007 6:40 AM To: users@maven.apache.org Subject: plugin shorthand not working as expected I've read through and followed this: http://maven.apache.org/guides/introduction/introduction-to-plugin-prefi x-mapping.html I have a custom plugin whose groupId I've configured in a custom pluginGroup in my /conf/settings.xml like so: com.mycompany.maven.plugin In the generated plugin.xml, I have promotion and promote. The problem is that unless I install this file to my local repo by building it locally, I can't use the shorthand notation to invoke it. In other words, when I install the plugin to my local repo, this command works fine: mvn promotion:promote But when I delete the artifact from my local repo and run the same command, I get the following output. (Using the fully qualified notation results in the plugin being invoked as normal, so I know that the plugin is in my central repo.) Here's the relevant output: [INFO] Searching repository for plugin with prefix: 'promotion'. [INFO] com.mycompany.maven.plugin: check for updates from central [INFO]-- - [ERROR] BUILD ERROR [INFO]-- - [INFO] The plugin 'org.apache.maven.plugins:maven-promotion-plugin' does not exist' It appears that the is being resolved, but I can't figure out why Maven doesn't resolve the shorthand unless I install locally. Any ideas? -- View this message in context: http://www.nabble.com/plugin-shorthand-not-working-as-expected-tf3851536 s177.html#a10910448 Sent from the Maven - Users mailing list archive at Nabble.com. - 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]
dummy dependency on surefire 2.4
Hello, according to the mailing list, there are some troubles with the surefire 2.4 plugin. However, there is still more problems: the 'dummy' artifact seems to rely on this version of surefire anyhow, which makes the whole maven building process abort. Does anyone knows whether: - this is easy to patch by hand - or the surefire 2.4 version will soon be available - or some stable version of surefire 2.4 is available somewhere for manual install - or can someone releave the dependency to the faulty plugin and make that the 'dummy' artifact does not prevent maven from building project ? thanks. Following are the trace of the error I get, best regards, Pierre [INFO] Failed to resolve artifact. Missing: -- 1) org.apache.maven.surefire:surefire-junit:jar:2.4-collab-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.surefire -DartifactId=surefire-junit \ -Dversion=2.4-collab-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Path to dependency: 1) dummy:dummy:jar:1.0 2) org.apache.maven.surefire:surefire-junit:jar:2.4-collab-SNAPSHOT -- 1 required artifact is missing. for artifact: dummy:dummy:jar:1.0 -- Pierre Parrend Ph.D. Student, Teaching Assistant INRIA-INSA Lyon, France [EMAIL PROTECTED] web : www.rzo.free.fr - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] pde-maven-plugin fails during release
Hi all,
I am trying to release my Eclipse plugins and I am getting lots of "The
import some.eclipse.package cannot be resolved" compilation errors
during the release:perform goal.
I have tried to run mvn package on the target/checkout directory and I
am getting the same errors... It seems that the build.xml file cannot be
run outside of the ${basedir} directory...
Any workaround for this situation?
How about tweaking the release:perform goal?
Adrian.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: "mvn site" error? 'VM_global_library.vm' ???
2 Andy It is very strange to read "it should" without context ;) 2 Baz Try to set JAVA_HOME=%JAVA5_HOME% it was helfull workaround for my JVM @see http://jira.codehaus.org/browse/MSITE-142 http://jira.codehaus.org/browse/MSITE-233 http://jira.codehaus.org/browse/MNG-2910 Andrew Williams-5 wrote: > > No, it should still be fine - are you getting nothing at all, or is > it just index.html that is missing? > Have you tried using "mvn site:run" to see if anything is being > rendered? > > Andy > > On 25 May 2007, at 23:09, Baz wrote: > >> So i also see the following errors during nunit, does it stop me >> using "mvn >> site"? >> >> [INFO] Velocimacro : initialization starting. >> [INFO] Velocimacro : adding VMs from VM library template : >> VM_global_library.vm >> [ERROR] ResourceManager : unable to find resource >> 'VM_global_library.vm' in >> any resource loader. >> [INFO] Velocimacro : error using VM library template >> VM_global_library.vm : >> org.apache.velocity.exception.ResourceNotFoundException: Unable to >> find >> resource 'VM_global_library.vm' >> [INFO] Velocimacro : VM library template macro registration complete. >> [INFO] Velocimacro : allowInline = true : VMs can be defined inline in >> templates >> [INFO] Velocimacro : allowInlineToOverride = false : VMs defined >> inline may >> NOT replace previous VM definitions >> [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline >> will be >> global in scope if allowed. >> [INFO] Velocimacro : initialization complete. >> [INFO] Velocity successfully started. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/%22mvn-site%22-error--%27VM_global_library.vm%27-tf3813466s177.html#a10956000 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: Programmatically finding dependencies
We can retrieve all dependencies in project using el ${project.dependencies},
but how can we get the full path of each dependency? (for classpath issues).
On 6/4/07, Mark Hobson <[EMAIL PROTECTED]> wrote:
On 04/06/07, Roland Asmann <[EMAIL PROTECTED]> wrote:
> Hi all,
>
> I'm writing a plugin here and want to figure out how to get hold of the
> dependencies as defined in the POM for my plugin.
> I'm currently using the ArtifactCollector, but it resolves transitive
> dependencies as well... I only want to have the dependencies that are
> DIRECTLY defined inside the POM-file.
>
> Any hints on how to do this?
${project.dependencies} ?
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Paulo Cesar Silva Reis
---
Powered by GMAIL
Re: m2: add new project to scm:svn
Hello Steve, Thanks for the help, I'm looking into Eclipse's svn plugin, looks like I'll be using that one instead. Kind Regards, Robert Den 2007-06-04 19:44:29 skrev Steven Rowe <[EMAIL PROTECTED]>: Hi Robert, I don't directly use the scm plugin, but Subversion's usage model requires you to "add" things before you can "checkin" them. So maybe what you're looking for is "scm:add"?: http://maven.apache.org/scm/plugins/add-mojo.html Why aren't you using the subversion executable directly, instead of going through Maven? Steve Robert Blixt wrote: Hi, I'm trying to get maven2 and subversion to work. But I've stumbled upon a problem. I have created my project locally with a pom.xml (which includes the scm with all needed subtags). Now I would like to add this project to subversion source control. I thought that all I would need to do was to launch: mvn -Dmessage="Initial commit." scm:checkin But this won't work, I get the following error: [ERROR] svn: Commit failed (details follow): svn: File not found: transaction '49-1', path '/trunk/myProject/.classpath' What should I do to add my maven2 project to Subversion? Kind Regards, Robert - 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-release-plugin: Unable to find the mojo perform
Hi Graham, I'm guessing that the exception started soon after you upgraded the version of the release plugin installed in your local repository (probably via mvn -U or -cpu). Wierdnesses like this seem to often have at their root a corrupted local repository. Have you tried removing your local repo, then letting Maven rebuild it? Steve Graham Leggett wrote: > Hi all, > > I am suddenly getting the following exception below when attempting to > perform a release of our project using maven v2.0.4 on Windows. > > I see there is a directory within the repository called 2.0-beta-6.rip - > is this somehow relevant? > > [INFO] > > [ERROR] BUILD ERROR > [INFO] > > [INFO] Internal error in the plugin manager executing goal > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable > to find the mojo > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the > plugin 'org.apache.maven.plugins:maven-release-plugin' > org/jdom/filter/Filter > [INFO] > > [INFO] Trace > org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in > the plugin manager executing goal > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable > to find the mojo > 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the > plugin 'org.apache.maven.plugins:maven-release-plugin' > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:538) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone > Goal(DefaultLifecycleExecutor.java:488) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau > ltLifecycleExecutor.java:458) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan > dleFailures(DefaultLifecycleExecutor.java:306) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen > ts(DefaultLifecycleExecutor.java:219) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi > fecycleExecutor.java:140) > at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) > at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) > at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at > sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. > java:39) > at > sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces > sorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:585) > at > org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) > at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) > at > org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find > the mo > jo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in > the plu > gin 'org.apache.maven.plugins:maven-release-plugin' > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul > tPluginManager.java:533) > at > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi > nManager.java:390) > at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa > ultLifecycleExecutor.java:534) > ... 16 more > Caused by: > org.codehaus.plexus.component.repository.exception.ComponentLookupExc > eption: Unable to lookup component > 'org.apache.maven.plugin.Mojoorg.apache.maven > .plugins:maven-release-plugin:2.0-beta-6:perform', it could not be started > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai > ner.java:339) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai > ner.java:440) > at > org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul > tPluginManager.java:524) > ... 18 more > Caused by: > org.codehaus.plexus.component.repository.exception.ComponentLifecycle > Exception: Error starting component > at > org.codehaus.plexus.component.manager.AbstractComponentManager.startC > omponentLifecycle(AbstractComponentManager.java:109) > at > org.codehaus.plexus.component.manager.AbstractComponentManager.create > ComponentInstance(AbstractComponentManager.java:95) > at > org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo > mponent(PerLookupComponentManager.java:48) > at > org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai > ner.java:331) > ... 20 more > Cause
[released] continuum-1.1-alpha-2
Highlights are:
* revamped xml-rpc support
* converted to use rebranded plexus-security, aka redback
* continuum maven plugin
* many bug fixes and ui improvements.
You can grab the latest release from:
http://maven.apache.org/continuum/download.html
Next up we are going to have another alpha release in a month, or
ideally a beta release that is feature complete for this version
around the beginning of July.
Anyway, below is the jira release notes for this release.
Release Notes - Continuum - Version 1.1-alpha-2
** Bug
* [CONTINUUM-620] - Changes section in Continuum build result and
build e-mail only show blank columns and file names
* [CONTINUUM-684] - Access to Continuum using XML-RPC is not authenticated.
* [CONTINUUM-1229] -
com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Invalid default
value for 'SCM_USE_CACHE'
* [CONTINUUM-1269] - Recforing of the XMLRPC server, must be a
servlet on the same port used by the webapp instead of a specific port
* [CONTINUUM-1275] - Project Group Name that contains only spaces
can be added.
* [CONTINUUM-1276] - Error in editing the Project name using spaces only
* [CONTINUUM-1282] - Adding or editing a Project Build Definition
can accept spaces in pom file name
* [CONTINUUM-1289] - Sorting Usernames in Build Management's
Project Group member list does not work in Firefox 2
* [CONTINUUM-1290] - Project ID is not validated when adding a Project Group
* [CONTINUUM-1292] - Error when clicking build icon in Project
Build Definitions summary
* [CONTINUUM-1293] - Hitting 'Add' button repetitively in adding
an Ant, Shell and Schedule using empty string only accumulates
validation prompts
* [CONTINUUM-1294] - Adding a Schedule, Ant/ Shell Projects can
accept spaces
** Improvement
* [CONTINUUM-1035] - Dependent builds not triggered via XMLRPC
* [CONTINUUM-1186] - Application should unpack to continuum-${version}
* [CONTINUUM-1297] - update to redback from plexus-security
** New Feature
* [CONTINUUM-683] - Implement a "ping" service that XML-RPC
clients can use to test connection.
** Task
* [CONTINUUM-1242] - Update Continuum Model
--
jesse mcconnell
[EMAIL PROTECTED]
Re: m2: add new project to scm:svn
Hi Robert, I don't directly use the scm plugin, but Subversion's usage model requires you to "add" things before you can "checkin" them. So maybe what you're looking for is "scm:add"?: http://maven.apache.org/scm/plugins/add-mojo.html Why aren't you using the subversion executable directly, instead of going through Maven? Steve Robert Blixt wrote: > > Hi, > > I'm trying to get maven2 and subversion to > work. But I've stumbled upon a problem. > > I have created my project locally with a > pom.xml (which includes the scm with all needed > subtags). > > Now I would like to add this project to subversion > source control. I thought that all I would need > to do was to launch: > > mvn -Dmessage="Initial commit." scm:checkin > > But this won't work, I get the following error: > [ERROR] svn: Commit failed (details follow): > svn: File not found: transaction '49-1', path '/trunk/myProject/.classpath' > > What should I do to add my maven2 project to Subversion? > > > Kind Regards, > Robert > > - > 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: disabling tests
thanks guys -- View this message in context: http://www.nabble.com/disabling-tests-tf3865503s177.html#a10953710 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: Overriding Plugin settings in a child POM
Hi Jerome, This JIRA issue looks like it's related (suggestion of adding a section to the POM): http://jira.codehaus.org/browse/MNG-1931 Steve Jerome Thibaud wrote: > Hi All, > > using: Maven 2.0.4 > > I defined the checkstyle reporting plugin in my parent pom, and for a > specific child project I want to skip the generation of this report. > I tried this: > > parent pom: > > > >... > >org.apache.maven.plugins >maven-checkstyle-plugin > > ... > > > > and in the child pom > > > > >org.apache.maven.plugins >maven-checkstyle-plugin > > true > > > > > > > hoping that this would override the parent settings but it persists to > generate the report. > > Any idea ? > > regards > > Jerome T. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
MojoFailureException v. MojoExecutionException
MojoFailureException or MojoExecutionException I am wondering what the difference is between these two exception types? The javadocs are identical. I am guessing the types are "markers", but this doesn't appear to be documented - or perhaps it is and I have missed it? TIA
Re: transitive "provided" dependency
That right, I don't want those javax.* jars to be bundled in my war. according to maven doc : http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html, It is expected to be transitive anyway. 2007/6/4, Jo Vandermeeren <[EMAIL PROTECTED]>: Hi Nicolas, Apparently you have indeed missed a bit ;) The URL you pasted mentions: *provided* - this is much like compile, but indicates you expect the JDK or a container to provide it. It is only available on the compilation classpath, and is not transitive. This means that they were needed to compile the project on which your project depends, but are expected to be provided by the environment in which the code is going to be executed. You don't want the dependency in your war/ear, neither do you want to force them on dependent projects. Cheers Jo On 6/4/07, nicolas de loof <[EMAIL PROTECTED]> wrote: > > Hello, > > My POM declares a dependency on a library that itself has dependency on > JEE > apis (jca, jms) declared as "provided". > Those dependencies are not set in my classpath by the eclipse plugin, > neither get include during compile. > > According to > > http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html > , > provided dependencies should be set as "provided" in the target project. > > Did I miss something ? >
Re: Specifying inclusions/exclusions from filtering resources
Hi Jo, Thanks for the advice. Works perfectly for me. Cheers, Kevin "Jo Vandermeeren" <[EMAIL PROTECTED]> 04/06/2007 16:30 Please respond to "Maven Users List" To "Maven Users List" cc Subject Re: Specifying inclusions/exclusions from filtering resources Hi Kevin, You can define separate sets for resources that need to be filtered. More on includes/excludes here: http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html Example.. src/main/resources WeOnlyWantToFilterThis.properties src/main/resources WeOnlyWantToFilterThis.properties true Resource filtering is nothing more than applying a parameter map to a velocity template. So if you want to prevent a specific value inside the resource from being filtered, use velocity escaping.. Cheers Jo On 6/4/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote: > > Hi all, > Is there a way to specify that only some files within a given directory > hierarchy get filtered when resources are copied? > And what about specifically including or excluding certain properties from > being filtered? > > Cheers, > Kevin > > > --- > > This e-mail may contain confidential and/or privileged information. If you > are not the intended recipient (or have received this e-mail in error) > please notify the sender immediately and destroy this e-mail. Any > unauthorized copying, disclosure or distribution of the material in this > e-mail is strictly forbidden. --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: transitive "provided" dependency
Hi Nicolas, Apparently you have indeed missed a bit ;) The URL you pasted mentions: *provided* - this is much like compile, but indicates you expect the JDK or a container to provide it. It is only available on the compilation classpath, and is not transitive. This means that they were needed to compile the project on which your project depends, but are expected to be provided by the environment in which the code is going to be executed. You don't want the dependency in your war/ear, neither do you want to force them on dependent projects. Cheers Jo On 6/4/07, nicolas de loof <[EMAIL PROTECTED]> wrote: Hello, My POM declares a dependency on a library that itself has dependency on JEE apis (jca, jms) declared as "provided". Those dependencies are not set in my classpath by the eclipse plugin, neither get include during compile. According to http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html , provided dependencies should be set as "provided" in the target project. Did I miss something ?
Re: Specifying inclusions/exclusions from filtering resources
Hi Kevin, You can define separate sets for resources that need to be filtered. More on includes/excludes here: http://maven.apache.org/plugins/maven-resources-plugin/examples/include-exclude.html Example.. src/main/resources WeOnlyWantToFilterThis.properties src/main/resources WeOnlyWantToFilterThis.properties true Resource filtering is nothing more than applying a parameter map to a velocity template. So if you want to prevent a specific value inside the resource from being filtered, use velocity escaping.. Cheers Jo On 6/4/07, Kevin Stembridge <[EMAIL PROTECTED]> wrote: Hi all, Is there a way to specify that only some files within a given directory hierarchy get filtered when resources are copied? And what about specifically including or excluding certain properties from being filtered? Cheers, Kevin --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
transitive "provided" dependency
Hello, My POM declares a dependency on a library that itself has dependency on JEE apis (jca, jms) declared as "provided". Those dependencies are not set in my classpath by the eclipse plugin, neither get include during compile. According to http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html, provided dependencies should be set as "provided" in the target project. Did I miss something ?
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
I still find it hard to understand how maven is denying me the flexibility of me saying I wish to use 1.2.1 jars instead of the new 1.2.3 xdoclet jars. Seems the patience has finally paid off.All it took was just configuring the plugin as follows : hbm-generation-with-xdoclet generate-sources target/classes xdoclet xdoclet xdoclet-hibernate-module 1.2.1 -- "Don't take the name of root in vain." Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Specifying inclusions/exclusions from filtering resources
Hi all, Is there a way to specify that only some files within a given directory hierarchy get filtered when resources are copied? And what about specifically including or excluding certain properties from being filtered? Cheers, Kevin --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden.
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote: On 05/06/2007, at 12:08 AM, Jeff Mutonho wrote: > On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote: >> On 04/06/2007, at 10:48 PM, Jeff Mutonho wrote:> >> If so, does the mapping file have a DOCTYPE? The "lazy" attribute >> appears in the Hibernate 2.0 DTD, so it should be OK. > > Yes it does.It's like this : > > > > "-//Hibernate/Hibernate Mapping DTD 2.0//EN" >"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";> > > > >name="za.co.telkom.portal.Person" >lazy="true" >> > You have an XML parser error on line 58 according to your stack trace. That seems to be way after this. You've probably got some Hibernate 3.0 markup in your Person class and it has sneaked into the mapping file. Do you have a validating xml editor than you can check the mapping file with? If you can find the bad xml, you will be able to locate the associated bean markup and fix it, instead of continuing to hide it. > > The 1.2.1 version looks like this : > > > "-//Hibernate/Hibernate Mapping DTD 2.0//EN" >"http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";> > > >name="za.co.telkom.portal.Person" >dynamic-update="false" >dynamic-insert="false" >> > > Isn't it possible to get Maven xdoclet plugin to use work with the > 1.2.1 jars at runtime instead of the 1.2.3? Anything's possible, but it won't be easy. Fix the markup in your java classes instead. Steve Coy Thanx Steve for your help.Its a bit tricky for me to sort out the java classes instead due to redtape in convincing the powers that be why we need to get rid of the lazy="true" ...more so due the fact that a pre-existing build.xml file that uses the 1.2.1 jars does not have the same issues the maven xdoclet plugin had I still find it hard to understand how maven is denying me the flexibility of me saying I wish to use 1.2.1 jars instead of the new 1.2.3 xdoclet jars. "Don't take the name of root in vain." Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Programmatically finding dependencies
On 04/06/07, Roland Asmann <[EMAIL PROTECTED]> wrote:
Hi all,
I'm writing a plugin here and want to figure out how to get hold of the
dependencies as defined in the POM for my plugin.
I'm currently using the ArtifactCollector, but it resolves transitive
dependencies as well... I only want to have the dependencies that are
DIRECTLY defined inside the POM-file.
Any hints on how to do this?
${project.dependencies} ?
Mark
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Programmatically finding dependencies
Hi Roland, Hmm.. I guess you could let the dependencies get resolved transitively, and then parse the pom.xml yourself to get a more restrictive list of dependencies. Dependency details could have been defined at a parent level, so enrich the data in your parsed list with the information that is available in the artifact collector, and you're there. The maven project reader that is available won't do you any good either, because it also resolves the parent poms. Cheers Jo On 6/4/07, Roland Asmann <[EMAIL PROTECTED]> wrote: Hi all, I'm writing a plugin here and want to figure out how to get hold of the dependencies as defined in the POM for my plugin. I'm currently using the ArtifactCollector, but it resolves transitive dependencies as well... I only want to have the dependencies that are DIRECTLY defined inside the POM-file. Any hints on how to do this? -- 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-release-plugin: Unable to find the mojo perform
On Mon, June 4, 2007 4:11 pm, Graham Leggett wrote: > I am suddenly getting the following exception below when attempting to > perform a release of our project using maven v2.0.4 on Windows. Upgrading to v2.0.6 hasn't made a difference, there is however what looks like a whole lot of debugging statements that get printed before the error: Can anyone confirm whether the release plugin still works on Windows? I have it running without a problem on a Linux machine under maven v2.0.4. [INFO] - --- [INFO] Building Alchemy II Native [INFO]task-segment: [release:perform] (aggregator-style) [INFO] - --- - this realm = app0.child-container[org.apache.maven.plugins:maven-release-plugin] urls[0] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/plugins/maven-release-plugin/2.0-beta-6/maven-release-plugin-2.0-beta-6.jar urls[1] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-api/1.0/maven-scm-api-1.0.jar urls[2] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvsexe/1.0/maven-scm-provider-cvsexe-1.0.jar urls[3] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/netbeans/lib/cvsclient/20060125/cvsclient-20060125.jar urls[4] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-manager-plexus/1.0/maven-scm-manager-plexus-1.0.jar urls[5] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/codehaus/plexus/plexus-utils/1.1/plexus-utils-1.1.jar urls[6] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-bazaar/1.0/maven-scm-provider-bazaar-1.0.jar urls[7] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-hg/1.0/maven-scm-provider-hg-1.0.jar urls[8] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-starteam/1.0/maven-scm-provider-starteam-1.0.jar urls[9] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvsjava/1.0/maven-scm-provider-cvsjava-1.0.jar urls[10] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-svnexe/1.0/maven-scm-provider-svnexe-1.0.jar urls[11] = file:/C:/WINNT/profiles/leggettg/.m2/repository/jaxen/jaxen/1.1-beta-8/jaxen-1.1-beta-8.jar urls[12] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-synergy/1.0/maven-scm-provider-synergy-1.0.jar urls[13] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-clearcase/1.0/maven-scm-provider-clearcase-1.0.jar urls[14] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-svn-commons/1.0/maven-scm-provider-svn-commons-1.0.jar urls[15] = file:/C:/WINNT/profiles/leggettg/.m2/repository/ch/ethz/ganymed/ganymed-ssh2/build210/ganymed-ssh2-build210.jar urls[16] = file:/C:/WINNT/profiles/leggettg/.m2/repository/jdom/jdom/1.0/jdom-1.0.jar urls[17] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-perforce/1.0/maven-scm-provider-perforce-1.0.jar urls[18] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/scm/maven-scm-provider-cvs-commons/1.0/maven-scm-provider-cvs-commons-1.0.jar urls[19] = file:/C:/WINNT/profiles/leggettg/.m2/repository/regexp/regexp/1.3/regexp-1.3.jar urls[20] = file:/C:/WINNT/profiles/leggettg/.m2/repository/org/apache/maven/release/maven-release-manager/1.0-alpha-3/maven-release-manager-1.0-alpha-3.jar Number of imports: 4 import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] this realm = plexus.core urls[0] = file:/C:/java/maven-2.0.6/lib/maven-core-2.0.6-uber.jar Number of imports: 4 import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] import: [EMAIL PROTECTED] - [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable to find the mojo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plugin 'org.apache.maven.plugins:maven-release-plugin' org/jdom/filter/Filter [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 11 seconds [INFO] Finished at: Mon Jun 04 16:34:32 CAT 2007 [INFO] Final Memory: 6M/11M [INFO] Regards,
[Maven Ant Tasks] Can't load dependencies
I try to get dependencies using next task: http://repo1.maven.org/maven2";> Result of execution is that artifact can't be loaded. I tried different artifacts without much success. It works only when artifact already exists in local repository. I've checked proxy settings and they are correct. Also I was able to download artifacts by hand from repository (I thought it could be down) . Did someone have same problems and found reason? - Вы уже с Yahoo!? Испытайте обновленную и улучшенную Yahoo! Почту!
Re: disabling tests
Hi, > How do I disable tests in a maven project? I'm running a mavenide2 plugin > for netbeans. http://maven.apache.org/general.html#skip-test HTH Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: disabling tests
En l'instant précis du 04/06/07 16:18, Arrowx7 s'exprimait en ces termes: > Hello, > How do I disable tests in a maven project? I'm running a mavenide2 plugin > for netbeans. > > Thanks. > maven.test.skip=true - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven not respecting order of profiles passed in on the command line
Please enlighten me - how do you avoid using profiles entirely? -Original Message- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Saturday, June 02, 2007 8:29 PM To: Maven Users List Subject: Re: Maven not respecting order of profiles passed in on the command line On 6/3/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: > On 6/2/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > > > I hate to bump my original email - but can someone from the dev side > > please let me know what to expect here? > > > > We're 100% wedged at this point. > > The issue you linked to [1] is marked fixed for 2.1-alpha-1, which has > not yet been released. > > The dev list is a better place to ask about whether it will be fixed > in 2.0 (I assume not, or else the issue would have been left open,) > and about the status of Maven 2.1 development. > > [1] http://jira.codehaus.org/browse/MNG-2309 Why are you relying on profile order anyway? You should be able to avoid using profiles. - 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: xdoclet-maven-plugin generating incorrect hbm.xml file
On 05/06/2007, at 12:08 AM, Jeff Mutonho wrote: On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote: On 04/06/2007, at 10:48 PM, Jeff Mutonho wrote:> If so, does the mapping file have a DOCTYPE? The "lazy" attribute appears in the Hibernate 2.0 DTD, so it should be OK. Yes it does.It's like this : http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";> You have an XML parser error on line 58 according to your stack trace. That seems to be way after this. You've probably got some Hibernate 3.0 markup in your Person class and it has sneaked into the mapping file. Do you have a validating xml editor than you can check the mapping file with? If you can find the bad xml, you will be able to locate the associated bean markup and fix it, instead of continuing to hide it. The 1.2.1 version looks like this : http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";> Isn't it possible to get Maven xdoclet plugin to use work with the 1.2.1 jars at runtime instead of the 1.2.3? Anything's possible, but it won't be easy. Fix the markup in your java classes instead. Steve Coy My attempt to alter/edit the xdoclet-maven-plugin-1.0-alpha-1.pom backfired and I ended up with a corrupt repository. - 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 not respecting order of profiles passed in on the command line
The bug says this also: Affects versions: 2.0, 2.0.1, 2.0.3, 2.0.2, 2.0.4 2.0.5/6 are both absent from that list. At the bottom of the page, I also see this: Fixed in trunk revision 408021. Merged in 2.0.x branch in revision 408023. So I'm not sure where/how this is really fixed. -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Saturday, June 02, 2007 1:40 PM To: Maven Users List Subject: Re: Maven not respecting order of profiles passed in on the command line On 6/2/07, EJ Ciramella <[EMAIL PROTECTED]> wrote: > I hate to bump my original email - but can someone from the dev side > please let me know what to expect here? > > We're 100% wedged at this point. The issue you linked to [1] is marked fixed for 2.1-alpha-1, which has not yet been released. The dev list is a better place to ask about whether it will be fixed in 2.0 (I assume not, or else the issue would have been left open,) and about the status of Maven 2.1 development. [1] http://jira.codehaus.org/browse/MNG-2309 -- Wendy - 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]
disabling tests
Hello, How do I disable tests in a maven project? I'm running a mavenide2 plugin for netbeans. Thanks. -- View this message in context: http://www.nabble.com/disabling-tests-tf3865503s177.html#a10950703 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-release-plugin: Unable to find the mojo perform
Hi all, I am suddenly getting the following exception below when attempting to perform a release of our project using maven v2.0.4 on Windows. I see there is a directory within the repository called 2.0-beta-6.rip - is this somehow relevant? [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable to find the mojo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plugin 'org.apache.maven.plugins:maven-release-plugin' org/jdom/filter/Filter [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Internal error in the plugin manager executing goal 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform': Unable to find the mojo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plugin 'org.apache.maven.plugins:maven-release-plugin' at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:538) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.PluginManagerException: Unable to find the mo jo 'org.apache.maven.plugins:maven-release-plugin:2.0-beta-6:perform' in the plu gin 'org.apache.maven.plugins:maven-release-plugin' at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul tPluginManager.java:533) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:390) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLookupExc eption: Unable to lookup component 'org.apache.maven.plugin.Mojoorg.apache.maven .plugins:maven-release-plugin:2.0-beta-6:perform', it could not be started at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:339) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:440) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Defaul tPluginManager.java:524) ... 18 more Caused by: org.codehaus.plexus.component.repository.exception.ComponentLifecycle Exception: Error starting component at org.codehaus.plexus.component.manager.AbstractComponentManager.startC omponentLifecycle(AbstractComponentManager.java:109) at org.codehaus.plexus.component.manager.AbstractComponentManager.create ComponentInstance(AbstractComponentManager.java:95) at org.codehaus.plexus.component.manager.PerLookupComponentManager.getCo mponent(PerLookupComponentManager.java:48) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContai ner.java:331) ... 20 more Caused by: org.codehaus.plexus.personality.plexus.lifecycle.phase.PhaseExecution Exception: Error composing component at org.codehaus.plexus.personality.plexus.lifecycle.phase.CompositionPha se.execute(CompositionPhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(Abstract LifecycleHandler.java:101) at org.codehaus.plexus.component.manager.AbstractComponentManager.startC omponentLifecycle(AbstractComponentManager.java:105) ... 23 more Caused by: org.codehaus.plexus.component.composition.CompositionException: Compo sition failed
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote: On 04/06/2007, at 10:48 PM, Jeff Mutonho wrote:> If so, does the mapping file have a DOCTYPE? The "lazy" attribute appears in the Hibernate 2.0 DTD, so it should be OK. Yes it does.It's like this : http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";> The 1.2.1 version looks like this : http://hibernate.sourceforge.net/hibernate-mapping-2.0.dtd";> Isn't it possible to get Maven xdoclet plugin to use work with the 1.2.1 jars at runtime instead of the 1.2.3? My attempt to alter/edit the xdoclet-maven-plugin-1.0-alpha-1.pom backfired and I ended up with a corrupt repository. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Assembly plugin - break up into phases
Hi,
You actually can bind the assembly plugin to two different phases of
the lifecycle, or even twice to the same phase. The key is to use the
block, rather than re-declare the plugin
again. Below, you have two executions declared...you just need to put
them in the same plugin section, and move the
blocks into their corresponding section.
One thing I will say, though, is that it may make more sense to wrtie
a custom plugin that would use Maven to resolve the dependencies and
inject them into your plugin, then iterate through them, grabbing any
embedded resources that you need along the way. Then, when you've got
all of the resources aggregated and ready to go, you can use the
assembly plugin to package it all up. FWIW, I've been thinking for
awhile now about creating some formal extension points in the
assembly plugin, that would allow you to do this sort of aggregation
during the normal course of the assembly process. Unfortunately, it's
not in place yet. :-(
HTH,
-john
On Jun 4, 2007, at 5:53 AM, James Abley wrote:
On 04/06/07, James Abley <[EMAIL PROTECTED]> wrote:
Hi,
I am trying to create an assembly that I can deploy to our
internal repository.
The envisaged steps in this process are:
1) Get all of the dependencies.
2) Do some final packaging; e.g. consolidate all SQL creation scripts
into a single script.
3) Create a zip file ready for deployment.
I'm trying to work out the best way of structuring the module
responsible for doing this.
Can I do it all in a single module, by binding different plugins to
the appropriately sequenced phase?
e.g.
1) Use maven-assembly-plugin bound to compile to create a temporary
working directory of all of the dependencies.
2) Use maven-antrun-plugin bound to test to do the final packaging.
3) Use the maven-assembly-plugin bound to package to create a zip
file.
Does this sound reasonable / feasible, should I be looking at
multiple
modules straight away or some other approach?
It doesn't look like I can do this in one step. I can't declare the
maven-assembly-plugin twice in the same pom - it doesn't see the
second assembly descriptor.
maven-assembly-plugin
false
src/main/assembly/dep.xml
create-directories
compile
directory-inline
maven-antrun-plugin
test
run
antfile="${basedir}/src/main/ant/
ddl.xml"
inheritRefs="true">
name="mpinstall.dependencies.dir"
value="${project.build.directory}/${project.build.finalName}.dir" />
org.apache.ant
ant-nodeps
1.7.0
maven-assembly-plugin
src/main/assembly/package.xml
make-assembly
package
attached
The second use of the maven-assembly-plugin shows that it is using the
descriptor src/main/assembly/dep.xml again, which isn't what I want.
That means that it misses out the changes done in the ANT target which
is the point of splitting out the process into more steps.
If I don't declare the plugin twice and instead specify two
descriptors in the single maven-assembly-plugin declaration, how do I
ensure that the correct descriptor is used at the correct time?
So I tried the other way of splitting it out into multiple modules:
I have one module that draws in all the dependencies and does the
inline-directory thing prior to using ANT to do some other stuff, and
then have a second module which uses a fileset to reference the
artifacts generated by the first assembly plugin / ANT combination.
This seems to do more or less what I want, but the baseDirector
isXX vs getXX- Plugin tag is not read
Hello again,
here is plugin Tag from my .pom file:
com.sun.tools.xjc.maven2
maven-jaxb-plugin
generate
src/main/xsd
Order/CustomerOrder.xsd
Order/CustomerAs.xsd
-Xboolean-getter
${xml-catalog-file}
true
jaxb2_commons
booleangetter
1.0
Any help
Thanks,
Ned
--- Begin Message ---
Hello,
similar as plug-in from:
http://fisheye5.cenqua.com/browse/~raw,r=1.1/jaxb2-commons/www/boolean-getter/index.html
does
I have the following problem:
Oracle SOA-OC4J expects getXX method to perform data binding
and JAXB uses isXX. and I use Maven to compile/deploy services
Is there similar funcional solution for Maven/Jaxb/OC4J?
Thanks
Ned
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--- End Message ---
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Programmatically finding dependencies
Hi all, I'm writing a plugin here and want to figure out how to get hold of the dependencies as defined in the POM for my plugin. I'm currently using the ArtifactCollector, but it resolves transitive dependencies as well... I only want to have the dependencies that are DIRECTLY defined inside the POM-file. Any hints on how to do this? -- 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: Newbie question 1
I guess from the trunk: archiva-1.0-alpha-1-SNAPSHOT.
-Chris
-Original Message-
From: Maria Odea Ching [mailto:[EMAIL PROTECTED]
Sent: Sunday, June 03, 2007 11:39 PM
To: [EMAIL PROTECTED]
Subject: Re: Newbie question 1
Hi,
Which version of archiva are you using?
archiva-0.9-alpha-2 or did you build from trunk?
-Deng
Chris Helck wrote:
> Hi,
>
> I'm confused. I've added a managed repository that points to one of
> our in house repos. I delete my .m2/repository and was able to rebuild
> a project. Yet, if I click on the "scan repository now" button it says
> that it has zero files. I assumed that archiva would cache stuff that
> it downloads. Also, browse shows nothing and Search doesn't ever find
> anything.
>
> Thanks,
> Christopher Helck
>
>
> **
> This communication and all information (including, but not limited to,
> market prices/levels and data) contained therein (the "Information")
> is for informational purposes only, is confidential, may be legally
> privileged and is the intellectual property of ICAP plc and its
> affiliates
> ("ICAP") or third parties. No confidentiality or privilege is waived
> or lost by any mistransmission. The Information is not, and should
> not be construed as, an offer, bid or solicitation in relation to any
> financial instrument or as an official confirmation of any
transaction.
> The Information is not warranted, including, but not limited, as to
> completeness, timeliness or accuracy and is subject to change without
> notice. ICAP assumes no liability for use or misuse of the
> Information. All representations and warranties are expressly
> disclaimed. The Information does not necessarily reflect the views of
> ICAP. Access to the Information by anyone else other than the
> recipient is unauthorized and any disclosure, copying, distribution or
> any action taken or omitted to be taken in reliance on it is
> prohibited. If you receive this message in error, please immediately
> delete it and all copies of it from your system, destroy any hard
> copies of it and notify the sender.
> **
>
>
>
**
This communication and all information (including, but not limited to,
market prices/levels and data) contained therein (the "Information") is
for informational purposes only, is confidential, may be legally
privileged and is the intellectual property of ICAP plc and its affiliates
("ICAP") or third parties. No confidentiality or privilege is waived or
lost by any mistransmission. The Information is not, and should not
be construed as, an offer, bid or solicitation in relation to any
financial instrument or as an official confirmation of any transaction.
The Information is not warranted, including, but not limited, as to
completeness, timeliness or accuracy and is subject to change
without notice. ICAP assumes no liability for use or misuse of the
Information. All representations and warranties are expressly
disclaimed. The Information does not necessarily reflect the views of
ICAP. Access to the Information by anyone else other than the
recipient is unauthorized and any disclosure, copying, distribution or
any action taken or omitted to be taken in reliance on it is prohibited. If
you receive this message in error, please immediately delete it and all
copies of it from your system, destroy any hard copies of it and
notify the sender.
**
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
On 04/06/2007, at 10:48 PM, Jeff Mutonho wrote: On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote: On 04/06/2007, at 9:43 PM, Jeff Mutonho wrote: Anyway, I would not mind betting that your bean has been marked up with something like: @hibernate.class lazy="true" Correct. Are you worried about the markup differences or something else? Well , when I deploy ear file , I get an exception that relates to "lazy=true".The actual exception is Error creating bean with name 'mySessionFactory' defined in ServletContext resource [/WEB-INF/appcontext/databaseContext.xml]: Initialization of bean failed; nested exception is net.sf.hibernate.MappingException: invalid mapping Caused by: org.xml.sax.SAXParseException: : Does this point at: ? If so, does the mapping file have a DOCTYPE? The "lazy" attribute appears in the Hibernate 2.0 DTD, so it should be OK. The other alternative is to remove the markup from the java class/es because xdoclet 1.2.1 was ignoring it anyway. Steve Coy XML-20137: (Error) Attribute 'lazy' used but not declared. at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java: 441) at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:303) at oracle.xml.parser.v2.NonValidatingParser.parseDocument (NonValidatingParser.java:290) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:196) at org.dom4j.io.SAXReader.read(SAXReader.java:465) at net.sf.hibernate.cfg.Configuration.addInputStream (Configuration.java:283) - 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: xdoclet-maven-plugin generating incorrect hbm.xml file
On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote: On 04/06/2007, at 9:43 PM, Jeff Mutonho wrote: Anyway, I would not mind betting that your bean has been marked up with something like: @hibernate.class lazy="true" Correct. Are you worried about the markup differences or something else? Well , when I deploy ear file , I get an exception that relates to "lazy=true".The actual exception is Error creating bean with name 'mySessionFactory' defined in ServletContext resource [/WEB-INF/appcontext/databaseContext.xml]: Initialization of bean failed; nested exception is net.sf.hibernate.MappingException: invalid mapping Caused by: org.xml.sax.SAXParseException: : XML-20137: (Error) Attribute 'lazy' used but not declared. at oracle.xml.parser.v2.XMLError.flushErrorHandler(XMLError.java:441) at oracle.xml.parser.v2.XMLError.flushErrors1(XMLError.java:303) at oracle.xml.parser.v2.NonValidatingParser.parseDocument(NonValidatingParser.java:290) at oracle.xml.parser.v2.XMLParser.parse(XMLParser.java:196) at org.dom4j.io.SAXReader.read(SAXReader.java:465) at net.sf.hibernate.cfg.Configuration.addInputStream(Configuration.java:283) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Surefire 2.4-SNAPSHOT errors
I've just reopened SUREFIRE-316 for re-examination since reports have resurfaced. - Brett On 04/06/07, Joel Wiegman <[EMAIL PROTECTED]> wrote: Anyone else getting this issue now? I included the --debug flag in my trace. [INFO] [surefire:test] [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire::2.4-SNAPSHOT for project: null:surefire-booter:jar:null from the repository. [DEBUG] surefire: resolved to version 2.4-20070604.115837-15 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: org.apache.maven.surefire:surefire:pom:2.4-SNAPSHOT from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Adding managed depedendencies for unknown:surefire-booter [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4-SNAPSHOT [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4-SNAPSHOT [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7 [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT:runtime (selected for runtime) [DEBUG] commons-lang:commons-lang:jar:2.1:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.4.1-SNAPSHOT) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.2:runtime (removed - nearer found: 1.4.1-SNAPSHOT) [DEBUG] surefire-api: resolved to version 2.4-20070604.114301-7 from repository apache.snapshots [DEBUG] plexus-utils: resolved to version 1.4.1-20070327.212230-12 from repository codehaus.snapshots [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0 -alpha-7\plexus-archiver-1.0-alpha-7.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-container-de fault\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\classworlds\classworlds\1.1-alpha-2\cla ssworlds-1.1-alpha-2.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\apache\maven\surefire\surefire-boot er\2.4-SNAPSHOT\surefire-booter-2.4-SNAPSHOT.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\commons-lang\commons-lang\2.1\commons-l ang-2.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1- SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\apache\maven\surefire\surefire-api\ 2.4-SNAPSHOT\surefire-api-2.4-SNAPSHOT.jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] org.testng:testng:jar:jdk15:5.5:test (selected for test) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\testng\testng\5.5\testng-5.5-jdk15. jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Skipping disabled repository central [DEBUG] surefire-testng: resolved to version 2.4-20070604.114301-6 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire-providers::2.4-SNAPSHOT for project: null:surefire-testng:jar:null from the repository. [DEBUG] Skipping disabled repository central [DEBUG] surefire-providers: resolved to version 2.4-20070604.114301-7 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire::2.4-SNAPSHOT for project: null:surefire-providers:pom:null from the repository. [DEBUG] surefire: resolved to version 2.4-20070604.115837-15 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for proje
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
On 04/06/2007, at 9:43 PM, Jeff Mutonho wrote:
On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote:
Jeff,
Are you really still using Hibernate 2.0?
100%.I've searched my repository and the only hibernate jar present is
hibernate-2.0.0.jar
Sorry, that was kind of a rhetorical question.
Anyway, I would not mind betting that your bean has been marked up
with something like:
@hibernate.class
lazy="true"
because that is the only way that this
>name="za.co.telkom.portal.Person"
>lazy="true"
>>
would have been generated. xdoclet 1.2.1 does not support this
attribute.
Also xdoclet 1.2.1 always generates
>dynamic-update="false"
>dynamic-insert="false"
xdoclet 1.2.3 only generates this markup if the corresponding java
class has been marked up as well. Note that "false" is the default
value and the fact that these values are missing from your maven
build has the same meaning as far as Hibernate is concerned.
Are you worried about the markup differences or something else?
I just happen to have the source code for both versions of xdoclet on
hand, and I know more or less how it works. So it's not too hard for
me to explain any differences that you're experiencing.
Steve Coy
Cheers,
Steve Coy
On 04/06/2007, at 8:18 PM, Jeff Mutonho wrote:
> I'm using the xdoclet-maven-plugin to generate my hibernate mapping
> files and I configured the plugin as follows :
>
>
> org.codehaus.mojo
> xdoclet-maven-plugin
>
>
> hbm-generation-with-xdoclet
> generate-sources
>
>
> excludedtags="@version,@author,@todo">
>
>
>
>
>
>
>
>
> target/classes generatedSourcesDirectory>
>
>
> xdoclet
>
>
>
>
>
>
> However the generated hbm.xml are incorrect and they do not
match what
> I get when I used Ant to generate the same hbm.xml files.Eg for
one of
> my classes Person .java
>
> Maven generate this :
> ===
> >
>name="za.co.telkom.portal.Person"
>lazy="true"
>>
>
> and
>
> Ant generates this :
>
>
>name="za.co.telkom.portal.Person"
>dynamic-update="false"
>dynamic-insert="false"
>>
>
>
> The Ant one works at deployment time.The Ant task used is :
>
>
>classname="xdoclet.modules.hibernate.HibernateDocletTask">
>
>
>destdir="${ant.common.eportal.domain.dir}/src" force="false"
> excludedtags="@version,@author,@todo">
>
>
>
>
>
>
>
>
>
>
>
> I'm using the same xdoclet-1.2.1.jar
> ,xdoclet-hibernate-module-1.2.1.jar and
> xdoclet-xdoclet-module-1.2.1.jar both in Ant and I've noticed that
> Maven is using
> xdoclet-hibernate-module-1.2.3.jar , which I suspect to be the
src of
> the inconsistency.How do I prevent Maven from using this
> xdoclet-hibernate-module-1.2.3.jar?
>
> Please help me , as I'm really stuck here.
>
>
> --
>
> "Don't take the name of root in vain."
>
> Jeff Mutonho
> Cape Town
> South Africa
>
> GoogleTalk : ejbengine
> Skype: ejbengine
> Registered Linux user number 366042
>
>
-
> 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]
--
"Don't take the name of root in vain."
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042
-
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: Surefire 2.4-SNAPSHOT errors
Anyone else getting this issue now? I included the --debug flag in my trace. [INFO] [surefire:test] [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire::2.4-SNAPSHOT for project: null:surefire-booter:jar:null from the repository. [DEBUG] surefire: resolved to version 2.4-20070604.115837-15 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: org.apache.maven.surefire:surefire:pom:2.4-SNAPSHOT from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: org.apache.maven:maven-parent:pom:5 from the repository. [DEBUG] Adding managed depedendencies for unknown:surefire-booter [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4-SNAPSHOT [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4-SNAPSHOT [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7 [DEBUG] org.apache.maven.surefire:surefire-booter:jar:2.4-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.apache.maven.surefire:surefire-api:jar:2.4-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT:runtime (selected for runtime) [DEBUG] commons-lang:commons-lang:jar:2.1:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.4.1-SNAPSHOT:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-7:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4:runtime (removed - nearer found: 1.4.1-SNAPSHOT) [DEBUG] junit:junit:jar:3.8.1:runtime (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2:runtime (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.2:runtime (removed - nearer found: 1.4.1-SNAPSHOT) [DEBUG] surefire-api: resolved to version 2.4-20070604.114301-7 from repository apache.snapshots [DEBUG] plexus-utils: resolved to version 1.4.1-20070327.212230-12 from repository codehaus.snapshots [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-archiver\1.0 -alpha-7\plexus-archiver-1.0-alpha-7.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-container-de fault\1.0-alpha-8\plexus-container-default-1.0-alpha-8.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\classworlds\classworlds\1.1-alpha-2\cla ssworlds-1.1-alpha-2.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\apache\maven\surefire\surefire-boot er\2.4-SNAPSHOT\surefire-booter-2.4-SNAPSHOT.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\commons-lang\commons-lang\2.1\commons-l ang-2.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\codehaus\plexus\plexus-utils\1.4.1- SNAPSHOT\plexus-utils-1.4.1-SNAPSHOT.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\apache\maven\surefire\surefire-api\ 2.4-SNAPSHOT\surefire-api-2.4-SNAPSHOT.jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] org.testng:testng:jar:jdk15:5.5:test (selected for test) [DEBUG] junit:junit:jar:3.8.1:test (selected for test) [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\junit\junit\3.8.1\junit-3.8.1.jar [DEBUG] Adding to surefire booter test classpath: C:\Documents and Settings\jwiegman\.m2\repository\org\testng\testng\5.5\testng-5.5-jdk15. jar [DEBUG] dummy:dummy:jar:1.0 (selected for null) [DEBUG] Skipping disabled repository central [DEBUG] surefire-testng: resolved to version 2.4-20070604.114301-6 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire-providers::2.4-SNAPSHOT for project: null:surefire-testng:jar:null from the repository. [DEBUG] Skipping disabled repository central [DEBUG] surefire-providers: resolved to version 2.4-20070604.114301-7 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven.surefire:surefire::2.4-SNAPSHOT for project: null:surefire-providers:pom:null from the repository. [DEBUG] surefire: resolved to version 2.4-20070604.115837-15 from repository apache.snapshots [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: org.apache.maven.surefire:surefire:pom:2.4-SNAPSHOT from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::3 for project: org.a
Error with maven-antrun-plugin :Can't create a hibernate element under hibernatedoclet.
I'm now trying to run Xdoclet using using using maven-antrun-plugin ,
I keep getting an error message saying :
"Embedded error: Can't create a hibernate element under
hibernatedoclet. Make sure the jar file containing the corresponding
subtask class is on the classpath specified in the that
defined {2}."
I've added all the dependencies that I think are needed.What am I missing ?
Here's my configuration :
===
maven-antrun-plugin
generate-sources
run
xdoclet
xdoclet
1.2.1
xdoclet
xdoclet-hibernate-module
1.2.1
xdoclet
xdoclet-xdoclet-module
1.2.1
apache
xjavadoc
1.0.3
commons-collections
commons-collections
3.2
commons-logging
commons-logging
1.0.4
--
"Don't take the name of root in vain."
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Project summary (web) for different repositories
Hi, We have different svn repositories - is it possible to generate a common project-website for every project in the repository? Jan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
On 6/4/07, Stephen Coy <[EMAIL PROTECTED]> wrote:
Jeff,
Are you really still using Hibernate 2.0?
100%.I've searched my repository and the only hibernate jar present is
hibernate-2.0.0.jar
Cheers,
Steve Coy
On 04/06/2007, at 8:18 PM, Jeff Mutonho wrote:
> I'm using the xdoclet-maven-plugin to generate my hibernate mapping
> files and I configured the plugin as follows :
>
>
> org.codehaus.mojo
> xdoclet-maven-plugin
>
>
> hbm-generation-with-xdoclet
> generate-sources
>
>
> excludedtags="@version,@author,@todo">
>
>
>
>
>
>
>
>
> target/classes generatedSourcesDirectory>
>
>
> xdoclet
>
>
>
>
>
>
> However the generated hbm.xml are incorrect and they do not match what
> I get when I used Ant to generate the same hbm.xml files.Eg for one of
> my classes Person .java
>
> Maven generate this :
> ===
> >
>name="za.co.telkom.portal.Person"
>lazy="true"
>>
>
> and
>
> Ant generates this :
>
>
>name="za.co.telkom.portal.Person"
>dynamic-update="false"
>dynamic-insert="false"
>>
>
>
> The Ant one works at deployment time.The Ant task used is :
>
>
>classname="xdoclet.modules.hibernate.HibernateDocletTask">
>
>
>destdir="${ant.common.eportal.domain.dir}/src" force="false"
> excludedtags="@version,@author,@todo">
>
>
>
>
>
>
>
>
>
>
>
> I'm using the same xdoclet-1.2.1.jar
> ,xdoclet-hibernate-module-1.2.1.jar and
> xdoclet-xdoclet-module-1.2.1.jar both in Ant and I've noticed that
> Maven is using
> xdoclet-hibernate-module-1.2.3.jar , which I suspect to be the src of
> the inconsistency.How do I prevent Maven from using this
> xdoclet-hibernate-module-1.2.3.jar?
>
> Please help me , as I'm really stuck here.
>
>
> --
>
> "Don't take the name of root in vain."
>
> Jeff Mutonho
> Cape Town
> South Africa
>
> GoogleTalk : ejbengine
> Skype: ejbengine
> Registered Linux user number 366042
>
> -
> 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]
--
"Don't take the name of root in vain."
Jeff Mutonho
Cape Town
South Africa
GoogleTalk : ejbengine
Skype: ejbengine
Registered Linux user number 366042
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: xdoclet-maven-plugin generating incorrect hbm.xml file
Jeff, This is really an xdoclet issue. The hibernate module in particular has dramatically increased functionality between xdoclet 1.2.1 and 1.2.3. I would need to see the bean markup to be able to comment on why you are getting different results here. I've used the maven xdoclet plugin extensively with Hibernate and have not had any problems of this kind. Are you really still using Hibernate 2.0? Cheers, Steve Coy On 04/06/2007, at 8:18 PM, Jeff Mutonho wrote: I'm using the xdoclet-maven-plugin to generate my hibernate mapping files and I configured the plugin as follows : org.codehaus.mojo xdoclet-maven-plugin hbm-generation-with-xdoclet generate-sources target/classesgeneratedSourcesDirectory> xdoclet However the generated hbm.xml are incorrect and they do not match what I get when I used Ant to generate the same hbm.xml files.Eg for one of my classes Person .java Maven generate this : === and Ant generates this : The Ant one works at deployment time.The Ant task used is : I'm using the same xdoclet-1.2.1.jar ,xdoclet-hibernate-module-1.2.1.jar and xdoclet-xdoclet-module-1.2.1.jar both in Ant and I've noticed that Maven is using xdoclet-hibernate-module-1.2.3.jar , which I suspect to be the src of the inconsistency.How do I prevent Maven from using this xdoclet-hibernate-module-1.2.3.jar? Please help me , as I'm really stuck here. -- "Don't take the name of root in vain." Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - 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: Site Distribution URL
Remove the ${project.artifactId} from your configuration. This
is automatically appended when the site is being deployed.
The hierarchy is also maintained, so you cannot get artifactId
conflicts.
Andy
On 31 May 2007, at 18:09, Ben Tatham wrote:
I am having difficulty understanding how the site-deploy decides
what url to use for the site deployment...
I have my parent pom of all my projects set up like this:
penguin
Nanometrics Software Website
scp://penguin/disk1/software/sites/${project.artifactId}/
But when the deploy actually happens, I get the following behaviour:
1) For the parent pom itelf (artifactId=common-pom), I get the
correct directory: /disk1/software/sites/common-pom/
2) For child projects (artifactId=range), I get /disk1/software/
sites/range/range/
3) For another project which itself a pom (artifactId=web-common-
pom), it deploys to /disk1/software/sites/web-common-pom/web-common-
pom/
4) For child projects of the 2nd level parent pom
(artifactId=configuration), it deploys to /disk1/software/sites/
configuration/web-common-pom/configuraion/
Very strange. Any idea why the ${project.artifactId} is not
working properly, or is it the site plugin doing something funny to
modify the url setting? For the #2 case, it would seem that the
site plugin automatically appends the artifactId to the URL, but it
does not happen for the pom project itself. Not consistent at all.
Thanks in advance,
Ben
-
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: Require particular JDK version
Hi David, Yes.. Have a look at the enforcer plugin: http://maven.apache.org/plugins/maven-enforcer-plugin/ Cheers Jo On 6/4/07, David Corbin <[EMAIL PROTECTED]> wrote: Is it possible to have the build fail if a particular version of the JDK is not being used? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Require particular JDK version
Is it possible to have the build fail if a particular version of the JDK is not being used? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
xdoclet-maven-plugin generating incorrect hbm.xml file
I'm using the xdoclet-maven-plugin to generate my hibernate mapping files and I configured the plugin as follows : org.codehaus.mojo xdoclet-maven-plugin hbm-generation-with-xdoclet generate-sources target/classes xdoclet However the generated hbm.xml are incorrect and they do not match what I get when I used Ant to generate the same hbm.xml files.Eg for one of my classes Person .java Maven generate this : === and Ant generates this : The Ant one works at deployment time.The Ant task used is : I'm using the same xdoclet-1.2.1.jar ,xdoclet-hibernate-module-1.2.1.jar and xdoclet-xdoclet-module-1.2.1.jar both in Ant and I've noticed that Maven is using xdoclet-hibernate-module-1.2.3.jar , which I suspect to be the src of the inconsistency.How do I prevent Maven from using this xdoclet-hibernate-module-1.2.3.jar? Please help me , as I'm really stuck here. -- "Don't take the name of root in vain." Jeff Mutonho Cape Town South Africa GoogleTalk : ejbengine Skype: ejbengine Registered Linux user number 366042 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Plugin development
Hi,
I added some functionality to the deploy phase of one of my projects
that allowed me to scp the assembly to a target host, and then ssh to
the host to run a command that deploys it.
This is really useful, but now I'd like to package it up so it can
easily be added other projects.
In the pom in which it gets used, I'll need to supply the distribution
name, the target directory.
Although I've written a java plugin, what I think I need here is
essentially a plugin with no code.
Thanks in advance for any guidance given.
This is what I've got in the project:
uat
maven-server-plugin
org.apache.maven.plugins
deploy-uat-sftp
deploy
uat
${basedir}/target
${distFilename}
${remoteDir}
sftp
deploy-uat-untar
deploy
uat
${command}
exec
Regards,
Ian Orford.
--
This e-mail is confidential and the information contained in it may be
privileged. It should not be read, copied or used by anyone other than the
intended recipient. If you have received it in error, please contact the
sender immediately by telephoning +44 (0)20 7623 8000 or by return email, and
delete the e-mail and do not disclose its contents to any person. We believe,
but do not warrant, that this e-mail and any attachments are virus free, but
you must take full responsibility for virus checking. Please refer to
http://www.dresdnerkleinwort.com/disc/email/ and read our e-mail disclaimer
statement and monitoring policy.
Dresdner Kleinwort is the trading name of the investment banking division of
Dresdner Bank AG, and operates through Dresdner Bank AG, Dresdner Kleinwort
Limited, Dresdner Kleinwort Securities Limited and their affiliated or
associated companies. Dresdner Bank AG is a company incorporated in Germany
with limited liability and registered in England (registered no. FC007638,
place of business 30 Gresham Street, London EC2V 7PG), and is authorised by the
German Federal Financial Supervisory Authority and by the Financial Services
Authority ('FSA') and regulated by the FSA for the conduct of designated
business in the UK. Dresdner Kleinwort Limited is a company incorporated in
England (registered no. 551334, registered office 30 Gresham Street, London
EC2V 7PG), and is authorised and regulated by the FSA. Dresdner Kleinwort
Securities Limited is a company incorporated in England (registered no.
1767419, registered office 30 Gresham Street, London EC2V 7PG), and is
authorised and regulated by the FSA.
Re: site:deploy works deploy:deploy hangs
apologies - had a typo in the server id - all works perfectly now. thanks, Nathan "Antonio Petrelli" <[EMAIL PROTECTED]> wrote on 04/06/2007 10:13:31: > 2007/6/4, Nathan Coast <[EMAIL PROTECTED]>: > > > > Hi Antonio, > > > > thanks for the reply, I'm a bit confused here, I would have thought that > > passphrase would have been for using public / private keys? We're not > > using keys to access this server. Or are you suggesting using the > > password for the passphrase. > > > > The deploy task deploys in the Maven repository. You have to sign artifacts > (usually using GPG) to deploy them. > If you try to run "mvn deploy" you probably will notice a prompt asking for > a passphrase, but the release plugin does not like prompts :-) > > Antonio --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: CVS Local checkout
Ah! I see, I'd assumed that the 'local' meant that it was using file based CVS
access rather than pserver / ext etc.
Thanks for the help!
- Tim
-Original Message-
From: Emmanuel Venisse [mailto:[EMAIL PROTECTED]
Sent: 01 June 2007 19:22
To: [EMAIL PROTECTED]
Subject: Re: CVS Local checkout
oh, I didn't see you use the local provider and not the cvs provider.
The local provider copy files and it is independant of cvs or other scm
providers.
Your scm url is totally wrong for cvs: http://maven.apache.org/scm/cvs.html
Emmanuel
Lee, Tim a écrit :
> Hi,
>
> I'm using an Scm Url of : scm:local:: - when I run the
> build I get the following output:
>
> 609392 [SocketListener0-1] INFO org.apache.maven.continuum.Continuum -
> Enqueuing 'test' (Build definition id=1).
> 610460 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
> Checking out project: 'test', id: '1' to
> '/continuum/../continuum_writable/apps/continuum/working-directory/1'.
> 610557 [Thread-2] INFO org.apache.maven.scm.manager.ScmManager - Checking
> out '/' to
> '/continuum/../continuum_writable/apps/continuum/working-directory/1'.
> 635518 [Thread-2] INFO org.apache.maven.continuum.scm.ContinuumScm -
> Checked out 754 files.
>
> Note : Path & module names changed to protect the innocent :)
>
> When I look at the working-directory/1 folder I see the CVS repository files
> ("build.xml,v" for example) rather than the checked-out version I would
> normally expect "build.xml". Is this normal behaviour? Because the shell
> script I'm attempting to invoke is failing.
>
> Thanks!
>
> Tim
>
>
>
Re: [m2] Assembly plugin - break up into phases
On 04/06/07, James Abley <[EMAIL PROTECTED]> wrote: Hi, I am trying to create an assembly that I can deploy to our internal repository. The envisaged steps in this process are: 1) Get all of the dependencies. 2) Do some final packaging; e.g. consolidate all SQL creation scripts into a single script. 3) Create a zip file ready for deployment. I'm trying to work out the best way of structuring the module responsible for doing this. Can I do it all in a single module, by binding different plugins to the appropriately sequenced phase? e.g. 1) Use maven-assembly-plugin bound to compile to create a temporary working directory of all of the dependencies. 2) Use maven-antrun-plugin bound to test to do the final packaging. 3) Use the maven-assembly-plugin bound to package to create a zip file. Does this sound reasonable / feasible, should I be looking at multiple modules straight away or some other approach? It doesn't look like I can do this in one step. I can't declare the maven-assembly-plugin twice in the same pom - it doesn't see the second assembly descriptor. maven-assembly-plugin false src/main/assembly/dep.xml create-directories compile directory-inline maven-antrun-plugin test run org.apache.ant ant-nodeps 1.7.0 maven-assembly-plugin src/main/assembly/package.xml make-assembly package attached The second use of the maven-assembly-plugin shows that it is using the descriptor src/main/assembly/dep.xml again, which isn't what I want. That means that it misses out the changes done in the ANT target which is the point of splitting out the process into more steps. If I don't declare the plugin twice and instead specify two descriptors in the single maven-assembly-plugin declaration, how do I ensure that the correct descriptor is used at the correct time? So I tried the other way of splitting it out into multiple modules: I have one module that draws in all the dependencies and does the inline-directory thing prior to using ANT to do some other stuff, and then have a second module which uses a fileset to reference the artifacts generated by the first assembly plugin / ANT combination. This seems to do more or less what I want, but the baseDirectory of the resulting zip is not what is required. e.g. MyProject module containing MyProject-dependencies and MyProject-packaging modules. ls MyProject-dependencies/target/MyProject-dependencies-finalName wars db docs (Looks good.) unzip -l MyProjectp-packaging/target/MyProject-packaging-finalName.zip ../MyProject-dependencies/target/MyProject-dependencies-finalName/wars ./MyProject-dependencies/target/MyProject-dependencies-finalName/db ./MyProject-dependencies/target/MyProject-dependencies-finalName/docs (I don't want that MyProject-dependencies/target prefix here!) How best to get rid of the ../MyProject-dependencies/target directory? My initial reaction is to use another ANT task before the final zip to copy the content into MyProject-packaging, maybe do the zip in ANT if I need that level of control and use a element in the assembly descriptor. That would seem like not the Maven way. Any other suggestions? Cheers, James Cheers, James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven antrun plugin
On 6/4/07, merlin <[EMAIL PROTECTED]> wrote: [WARNING] repository metadata for: 'snapshot org.geoserver:web:1.6-SNAPSHOT' could not be retrieved from repository: codehaus.org due to an error: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav [INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find wagon which supports the requested protocol: dav This has nothing to do with binding the antrun plugin to the deploy phase. The error you get is because webdav deployment is not configured correctly. Add this extension to your pom to make your project aware of the fact that you want to use WebDAV: ... ... org.apache.maven.wagon wagon-webdav 1.0-beta-2 ... Then try a "mvn deploy" without any extra plugin executions bound to the deploy phase. If that works, the extra plugin execution should work as well. Cheers Jo
Re: maven antrun plugin
sorry for the mistake ... I 've just forgotten to write in english..
So the problem is that:
if I bind this plugin to the install phase , it 's ok , the files are
copyied and the process ends with success,
but if I bind it to the deploy phase , I 've got an error , I don't know
why..
here is the error details:
[INFO] [deploy:deploy]
altDeploymentRepository = null
[INFO] Retrieving previous build number from codehaus.org
[WARNING] repository metadata for: 'snapshot org.geoserver:web:1.6-SNAPSHOT'
could not be retrieved from repository: codehaus.org due to an
error: Unsupported Protocol: 'dav': Cannot find wagon which supports the
requested protocol: dav
[INFO] Repository 'codehaus.org' will be blacklisted
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Unsupported Protocol: 'dav': Cannot find
wagon which supports the requested protocol: dav
Component descriptor cannot be found in the component repository:
org.apache.maven.wagon.Wagondav.
thanks for your help.
Jo Vandermeeren wrote:
>
> First off, this is an English speaking mailing list..
> So ask your questions in plain English.
>
> You can indeed bind a plugin execution to a certain phase.
> What is the content of the error message you mentioned?
>
> Cheers
> Jo
>
> On 6/4/07, merlin < [EMAIL PROTECTED]> wrote:
>>
>>
>> dans la documentation maven j ai trouvé le plugin suivant qui me permet
>> de
>> copier quelques fichiers ds un repertoire cible.
>>
>> de la maniere suivante:
>>
>>
>> org.apache.maven.plugins
>> maven-antrun-plugin
>>
>>
>> install
>>
>>
>> ${ exo.directory.base
>> }
>> ${exo.directory.v2.x
>> }
>>
>> ${exo.directory.working}
>> > todir="${exo.directory.working}/exo-tomcat/webapps">
>> > dir="${exo.directory.v2.x}/geoserver/web/target">
>>
>>
>>
>>
>>
>>
>> run
>>
>>
>>
>>
>>
>> cela marche tres bien tel quel ("mvn install" entraine la copie des
>> fichiers
>> et se termine avec succes ) sauf que je souhaite que ca se fasse pendant
>> la
>> phase de deploiement. or si je change install par
>> deploy , lors du "mvn deploy " j obtiens alors un msg d
>> erreur.
>>
>> est ce que quelqun en connaitrait la cause?
>> --
>> View this message in context:
>> http://www.nabble.com/maven-antrun-plugin-tf3863830s177.html#a10945960
>>
>> Sent from the Maven - Users mailing list archive at Nabble.com.
>>
>>
>> -
>> To unsubscribe, e-mail: [EMAIL PROTECTED]
>> For additional commands, e-mail: [EMAIL PROTECTED]
>>
>>
>
>
--
View this message in context:
http://www.nabble.com/maven-antrun-plugin-tf3863830s177.html#a10946557
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: site:deploy works deploy:deploy hangs
2007/6/4, Nathan Coast <[EMAIL PROTECTED]>: Hi Antonio, thanks for the reply, I'm a bit confused here, I would have thought that passphrase would have been for using public / private keys? We're not using keys to access this server. Or are you suggesting using the password for the passphrase. The deploy task deploys in the Maven repository. You have to sign artifacts (usually using GPG) to deploy them. If you try to run "mvn deploy" you probably will notice a prompt asking for a passphrase, but the release plugin does not like prompts :-) Antonio
Re: maven antrun plugin
First off, this is an English speaking mailing list..
So ask your questions in plain English.
You can indeed bind a plugin execution to a certain phase.
What is the content of the error message you mentioned?
Cheers
Jo
On 6/4/07, merlin < [EMAIL PROTECTED]> wrote:
dans la documentation maven j ai trouvé le plugin suivant qui me permet de
copier quelques fichiers ds un repertoire cible.
de la maniere suivante:
org.apache.maven.plugins
maven-antrun-plugin
install
${ exo.directory.base
}
${exo.directory.v2.x
}
${exo.directory.working}
run
cela marche tres bien tel quel ("mvn install" entraine la copie des
fichiers
et se termine avec succes ) sauf que je souhaite que ca se fasse pendant
la
phase de deploiement. or si je change install par
deploy , lors du "mvn deploy " j obtiens alors un msg d
erreur.
est ce que quelqun en connaitrait la cause?
--
View this message in context:
http://www.nabble.com/maven-antrun-plugin-tf3863830s177.html#a10945960
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: site:deploy works deploy:deploy hangs
Hi Antonio, thanks for the reply, I'm a bit confused here, I would have thought that passphrase would have been for using public / private keys? We're not using keys to access this server. Or are you suggesting using the password for the passphrase. cheers, Nathan "Antonio Petrelli" <[EMAIL PROTECTED]> wrote on 04/06/2007 09:47:00: > 2007/6/4, Nathan Coast <[EMAIL PROTECTED]>: > > > > Hi all, > > > > trying to understand what I might be doing wrong, AFAICT the site and repo > > settings are the same. I have also checked the file permissions on > > /spool/grimis/synergy/development/... site:deploy works but > > deploy:deploy (executed as part of release:perform) hangs. > > > > I had a similar problem and I solved setting the "gpg.passphrase" property. > Add it in your settings.xml, or by using > -Dgpg.passphrase=blahblah > > HTH > Antonio --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and destroy this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven antrun plugin
dans la documentation maven j ai trouvé le plugin suivant qui me permet de
copier quelques fichiers ds un repertoire cible.
de la maniere suivante:
org.apache.maven.plugins
maven-antrun-plugin
install
${exo.directory.base}
${exo.directory.v2.x}
${exo.directory.working}
run
cela marche tres bien tel quel ("mvn install" entraine la copie des fichiers
et se termine avec succes ) sauf que je souhaite que ca se fasse pendant la
phase de deploiement. or si je change install par
deploy , lors du "mvn deploy " j obtiens alors un msg d
erreur.
est ce que quelqun en connaitrait la cause?
--
View this message in context:
http://www.nabble.com/maven-antrun-plugin-tf3863830s177.html#a10945960
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
m2: add new project to scm:svn
Hi, I'm trying to get maven2 and subversion to work. But I've stumbled upon a problem. I have created my project locally with a pom.xml (which includes the scm with all needed subtags). Now I would like to add this project to subversion source control. I thought that all I would need to do was to launch: mvn -Dmessage="Initial commit." scm:checkin But this won't work, I get the following error: [ERROR] svn: Commit failed (details follow): svn: File not found: transaction '49-1', path '/trunk/myProject/.classpath' What should I do to add my maven2 project to Subversion? Kind Regards, Robert - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site:deploy works deploy:deploy hangs
2007/6/4, Nathan Coast <[EMAIL PROTECTED]>: Hi all, trying to understand what I might be doing wrong, AFAICT the site and repo settings are the same. I have also checked the file permissions on /spool/grimis/synergy/development/... site:deploy works but deploy:deploy (executed as part of release:perform) hangs. I had a similar problem and I solved setting the "gpg.passphrase" property. Add it in your settings.xml, or by using -Dgpg.passphrase=blahblah HTH Antonio
site:deploy works deploy:deploy hangs
Hi all,
trying to understand what I might be doing wrong, AFAICT the site and repo
settings are the same. I have also checked the file permissions on
/spool/grimis/synergy/development/... site:deploy works but
deploy:deploy (executed as part of release:perform) hangs.
[INFO] [site:deploy]
scp://longmdappu4.uk.db.com/spool/grimis/synergy/development/projects/GMRiskCrypto
- Session: Opened
Executing command: mkdir -p
/spool/grimis/synergy/development/projects/GMRiskCrypto/.
Executing command: mkdir -p
/spool/grimis/synergy/development/projects/GMRiskCrypto/.
...
...
executing as part of release:perform
[INFO] [deploy:deploy]
altDeploymentRepository = null
*hangs here*
Configs are the same in pom.xml and settings.xml
pom
gmris.dev.docs
scp://longmdappu4.uk.db.com/spool/grimis/synergy/development/projects/${pom.artifactId}
grimis.dev.repo
scp://longmdappu4.uk.db.com/spool/grimis/synergy/development/maven
settings
X
X
gmris.dev.docs
X
X
gmris.dev.repo
---
This e-mail may contain confidential and/or privileged information. If you
are not the intended recipient (or have received this e-mail in error)
please notify the sender immediately and destroy this e-mail. Any
unauthorized copying, disclosure or distribution of the material in this
e-mail is strictly forbidden.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Assembly plugin - break up into phases
Hi, I am trying to create an assembly that I can deploy to our internal repository. The envisaged steps in this process are: 1) Get all of the dependencies. 2) Do some final packaging; e.g. consolidate all SQL creation scripts into a single script. 3) Create a zip file ready for deployment. I'm trying to work out the best way of structuring the module responsible for doing this. Can I do it all in a single module, by binding different plugins to the appropriately sequenced phase? e.g. 1) Use maven-assembly-plugin bound to compile to create a temporary working directory of all of the dependencies. 2) Use maven-antrun-plugin bound to test to do the final packaging. 3) Use the maven-assembly-plugin bound to package to create a zip file. Does this sound reasonable / feasible, should I be looking at multiple modules straight away or some other approach? Cheers, James - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant's Java task in Maven?
On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: I want to excute a Java class, similar to Ant's Java task (http://ant.apache.org/manual/CoreTasks/java.html). Then use the exec plugin I mentioned in the previous post: http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html. The project's runtime classpath will be used to execute your main class.
[m2] site:stage
Hello, is it possible to clean an staging directory via maven ? regards, jens
Re: profile activation based on property <=> in POM
Thanks for this detailled reply. I'll have to find an alternative to profiles. Ability to activate parent-POM profiles from a POM would be really nice as it would enable pulling up lot's of common configuration to corporate POMs. For now, I'll use an archetype to add all the profiles to the generated project POM with activation based on , so that projects can easily enable/disable some configuration. Nico. 2007/6/3, John Casey <[EMAIL PROTECTED]>: Unfortunately, this doesn't work in Maven 2.0.x. The reason is that the profile activator actually uses System.getProperty( "project.target.jre" ), not project.getProperties ().getProperty( "project.target.jre" ). It's actually a fairly involved process to check the POM for properties during profile activation (you probably wouldn't think so...). I've added the technical ability to do this in Maven trunk (2.1.x), but it still requires a custom profile activator. If you look at the c-builds code in the native-mojo project: http://svn.codehaus.org/native-mojo/c-builds/trunk you should see a directory called: plugins/cbuild-profile-activators This contains an example of precisely the type of profile activation you're trying to accomplish, but it only works on Maven trunk (which is currently pre-alpha). Sorry for any confusion. -john On May 28, 2007, at 5:03 AM, nicolas de loof wrote: > Hello, > > I'd like to have a set of profiles in my corporate parent POM for > various > maven usage. To enable them depending on projects I'd like to set a > in the project POM to enable the profile : > > example : > - corporate parent pom : > > >Java5 > > >project.target.jre >java5 > > > >1.5 >1.5 > ... > > - project POM : > > >java5 > > > > This doesn't work as I expected. Is there any way to enable a > profile in > parent POM from a child POM ? > > Nico. --- John Casey Committer and PMC Member, Apache Maven mail: jdcasey at commonjava dot org blog: http://www.ejlife.net/blogs/john
Re: Ant's Java task in Maven?
I want to excute a Java class, similar to Ant's Java task (http://ant.apache.org/manual/CoreTasks/java.html). On 6/4/07, Jo Vandermeeren <[EMAIL PROTECTED]> wrote: On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: > > Hi Jo > > I hope I can do this the "Maven's way" without using the Antrun plugin. What exactly do you want to do? Any better idea? > If you just want to execute a main class, the maven-exec-plugin might be what you are looking for. It's on the codehaus: http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html Cheers Jo -- Hez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant's Java task in Maven?
On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: Hi Jo I hope I can do this the "Maven's way" without using the Antrun plugin. What exactly do you want to do? Any better idea? If you just want to execute a main class, the maven-exec-plugin might be what you are looking for. It's on the codehaus: http://mojo.codehaus.org/exec-maven-plugin/java-mojo.html Cheers Jo
Re: Ant's Java task in Maven?
Hi Jo I hope I can do this the "Maven's way" without using the Antrun plugin. Any better idea? On 6/4/07, Jo Vandermeeren <[EMAIL PROTECTED]> wrote: You can call your Ant task with the maven-antrun-plugin: http://maven.apache.org/plugins/maven-antrun-plugin/ On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: > > Hi! > > With Ant, we have Java task to execute a main Java class. > > How can I do this with Maven? > > > -- > > Hez > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Hez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ant's Java task in Maven?
You can call your Ant task with the maven-antrun-plugin: http://maven.apache.org/plugins/maven-antrun-plugin/ On 6/4/07, hezjing <[EMAIL PROTECTED]> wrote: Hi! With Ant, we have Java task to execute a main Java class. How can I do this with Maven? -- Hez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ant's Java task in Maven?
Hi! With Ant, we have Java task to execute a main Java class. How can I do this with Maven? -- Hez - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
