Re: Creating WebSphere Specific Config Files
XDoclet works ok for Websphere 6.0. XDoclet 2 seems to be a no go with Websphere --at least for a while -- unless they have hidden the documentation really well. The ejbs and mdb's we built give us no trouble under WAS 6.0. XDoclet does have trouble with multi-module builds as it seems to use the same directory for generated sources as it uses the first time it runs. You can work around this by hooking into the maven lifecycle with : true maven-antrun-plugin process-classes run and the xdoclet plugin config: true org.codehaus.mojo xdoclet-maven-plugin generate-sources xdoclet On 5/9/07, David J. M. Karlsen <[EMAIL PROTECTED]> wrote: Bala Rajamani skrev: > Hello, > > > > I would like to create WebSphere specific application.xml and related > ibm-application-bnd.xmi and MANIFEST.MF files. How do I this achieve this > with maven? The IBM specific deploymentfiles (sigh) can be generated by the xdoclet plugin, sadly xdoclet does not seem to be maintained anymore. It covers support for was 5.x fairly well, but not 6.1. You might be lucky with xdoclet2 also - but I have no was-expirience with this. Good luck - if you find any good solutions - please post back on the list. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven dependency question
I did it this way. The classpath gets generated with the jars for the war
but no jar files get added to the lib directory
org.apache.maven.plugins
maven-war-plugin
2.0.1
${basedir}/../target/${artifactId}
WEB-INF/lib/*.jar
false
true
On 11/15/06, Wayne Fay <[EMAIL PROTECTED]> wrote:
Incorrect, Lee M. responded to you earlier...
-- Forwarded message --
From: Lee Meador <[EMAIL PROTECTED]>
Date: Nov 14, 2006 3:17 PM
Subject: Re: Maven dependency question
To: Maven Users List
What I do is put the utility jar in my dependency for the war as compile.
Then I put an exclude in the pom for the war that tells it to leave out
the
jar and not put it into the war. The classloader for your application
server
should cause the war to have access to the jar since it is in the ejb
jar's
classpath. This has to do with the nesting of the classloaders. Some app
servers let you change the way that works though.
-- Lee
On 11/14/06, Enrique Gaona <[EMAIL PROTECTED]> wrote:
>
>
>
> I posted this message earlier and didnt get any replies. Anyone know the
answer:) Thanks.
>
> Enrique
>
> Enrique Gaona/Austin/[EMAIL PROTECTED]
>
>
>
>
>
>
>
> Enrique Gaona/Austin/[EMAIL PROTECTED]
>
> 11/14/2006 01:33 PM
>
> Please respond to
> "Maven Users List"
>
>
> To
> users@maven.apache.org
>
>
> cc
>
>
>
> Subject
> Maven dependency question
>
>
>
>
> Hi folks,
>
> We have a J2EE application project (ear) which contains one Web project
> (war), one EJB project and one utilities java project.
> The war and EJB jar projects depends from the same utilities project.
> We included the WEB, EJB and utilities projects as dependencies into the
> ear pom file, so all three output files are included into ear file.
> EJB project works as expected it only adds Class-Path: entry into its
> Manifest.MF class
>
> The problem with the Web project, it adds the common utility jar file
into
> its WEB-INF/lib directory. We tried to change the dependency scope from
> "compile" to "provided". In this case neither the jar was added nor the
> Class-Path: entry.
>
> How can we specify dependency from the common utility jar file in the
war's
> pom file?
>
> Any help is appreciated. Thanks
>
> Enrique
>
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Has anyone been able to get the java2wsdl plugin to work?
If someone couuld include a pom fragment or pom where they got this plugin to work it would be *most* helplful. TIA Eric
Re: Has anyone been able to get the java2wsdl plugin to work?
sorry - -stupid me -- the maven 2 axis 2 plugin. Serves me right for trying to get something real accomplished in an otherwise BS day On 11/17/06, Jochen Wiedmann <[EMAIL PROTECTED]> wrote: On 11/17/06, Eric Helfrich <[EMAIL PROTECTED]> wrote: > If someone couuld include a pom fragment or pom where they got this plugin > to work it would be *most* helplful. Which java2wsdl plugin? -- My wife Mary and I have been married for forty-seven years and not once have we had an argument serious enough to consider divorce; murder, yes, but divorce, never. (Jack Benny) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
references to resources in parent project site
How do I configure my site.vm file to create links to resources in the parent site? I don't want to copy these resources to each project.
Re: POM inheritance works but site inheritance does not
Don't know if this helps any but here is how I worked around the links not working issue -- its ugly: maven-antrun-plugin pre-site run On 12/15/06, Yann Albou <[EMAIL PROTECTED]> wrote: I had a similar issue: I set up to the url tag : http://yoururl in my pom parent. (I don't know why but you cannot use relative url) Yann Breddy wrote: > Group, > > I have a POM that inherits from another using a relative path that looks > something like ../parent-pom-dir/pom.xml. All POM inheritance features work > and I can see in the debug logs that the parent POM is found and invoked. > I'm using Maven 2.0.4 and have done -cpu to ensure all plugins are current. > > I have a site.xml in the parent project that contains a inherit="bottom"> element that no longer shows up in the child project's > site. This worked at one point but I cannot seem to track down what changed > to break the inheritance. Links do not inherit either. There's no info in > the debug logs that would give me a clue about what's going on (no mention > of site inheritance at all). > > Existing posts to the mailing list seem to deal with scenarios in which the > user has incorrectly referenced the parent POM, not the case in my project. > I'm out of ideas. > > Any guidance is appreciated! > > Thanks, > > Chris - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Xdoclet plugin and multi module projects
Has anyone been able to get this to work correctly? Hibernate doclet and ejbdoclet do not work correctly -- ejb doclet generates all files in the generated sources directory of the first project it runs. Hibernate doclet does not seem to find the source files at all when run from a parent project which defines the plugin - -but works fine if generate-sources is run on the sub project. Any ideas? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Xdoclet plugin and multi module projects
that would work -- except I am pulling in a legacy build system here and would rather not have to start moving code around at that level On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: I use hibernate doclet, and it acts the same for me. I just have my 1st module is my common-jar that gets added to all my modules anyways. Works fine even though it is strange... On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > Has anyone been able to get this to work correctly? Hibernate doclet > and ejbdoclet do not work correctly -- ejb doclet generates all files > in the generated sources directory of the first project it runs. > Hibernate doclet does not seem to find the source files at all when > run from a parent project which defines the plugin - -but works fine > if generate-sources is run on the sub project. Any ideas? > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- --- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/djmick_dot_com http://www.thumpradio.com --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Xdoclet plugin and multi module projects
Yes it would work -- and is probably better from a resource point of view anyway. On the other hand, that won't work for the ejbdoclet issues. On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: Just add a common jar as the 1st module, and add that jar to your legacy code. Would that work? On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > that would work -- except I am pulling in a legacy build system here > and would rather not have to start moving code around at that level > > > On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > I use hibernate doclet, and it acts the same for me. > > I just have my 1st module is my common-jar that gets added to all my > modules > > anyways. Works fine even though it is strange... > > > > > > On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > > > > > Has anyone been able to get this to work correctly? Hibernate doclet > > > and ejbdoclet do not work correctly -- ejb doclet generates all files > > > in the generated sources directory of the first project it runs. > > > Hibernate doclet does not seem to find the source files at all when > > > run from a parent project which defines the plugin - -but works fine > > > if generate-sources is run on the sub project. Any ideas? > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > --- > > Thanks, > > Mick Knutson > > > > http://www.baselogic.com > > http://www.blincmagazine.com > > http://www.djmick.com > > http://www.myspace.com/djmick_dot_com > > http://www.thumpradio.com > > --- > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- --- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/djmick_dot_com http://www.thumpradio.com ---
Re: Xdoclet plugin and multi module projects
I don't think that putting everything that gets xdocleted in a common jar is an ideal solution -- one of the reasons for breaking you code up into projects is to separate functionality -- and one of the reasons to use Maven is to support that flexibility -- not limit it. Thanks for the suggestion though. On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: Why, the ejbs will be in the common-jar and they can be added the same way. On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > Yes it would work -- and is probably better from a resource point of view > anyway. On the other hand, that won't work for the ejbdoclet issues. > > On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > > Just add a common jar as the 1st module, and add that jar to your legacy > > code. Would that work? > > > > > > > > On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > > > > > that would work -- except I am pulling in a legacy build system here > > > and would rather not have to start moving code around at that level > > > > > > > > > On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > > I use hibernate doclet, and it acts the same for me. > > > > I just have my 1st module is my common-jar that gets added to all my > > > modules > > > > anyways. Works fine even though it is strange... > > > > > > > > > > > > On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > > > > > > > > > Has anyone been able to get this to work correctly? Hibernate > > doclet > > > > > and ejbdoclet do not work correctly -- ejb doclet generates all > > files > > > > > in the generated sources directory of the first project it runs. > > > > > Hibernate doclet does not seem to find the source files at all > when > > > > > run from a parent project which defines the plugin - -but works > fine > > > > > if generate-sources is run on the sub project. Any ideas? > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > --- > > > > Thanks, > > > > Mick Knutson > > > > > > > > http://www.baselogic.com > > > > http://www.blincmagazine.com > > > > http://www.djmick.com > > > > http://www.myspace.com/djmick_dot_com > > > > http://www.thumpradio.com > > > > --- > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > --- > > Thanks, > > Mick Knutson > > > > http://www.baselogic.com > > http://www.blincmagazine.com > > http://www.djmick.com > > http://www.myspace.com/djmick_dot_com > > http://www.thumpradio.com > > --- > > > -- --- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/djmick_dot_com http://www.thumpradio.com ---
Re: Xdoclet plugin and multi module projects
I realize the suggestion was meant to be helpful -- I think it has to do with properties being immutable in ant and xdoclet1 being dependent on ant. I am working with a substantial base of code and to attempt to reorg it efficiently at this point would be difficult. XD2 doesn't rely on ant -- but I haven't been successful in getting it set up. I may put a bit more effort into it now. In the meantime another solution would be to call out to an ant task using ant run and have that task run in its own process. That is my fallback if xd2 isn't ready yet. On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: The suggestion was not as what is best, but rather what is possible right now as I have also encountered the same issue you where facing. Maybe XD2 fixes this? On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > I don't think that putting everything that gets xdocleted in a common jar > is > an ideal solution -- one of the reasons for breaking you code up into > projects is to separate functionality -- and one of the reasons to use > Maven > is to support that flexibility -- not limit it. Thanks for the suggestion > though. > > On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > > Why, the ejbs will be in the common-jar and they can be added the same > > way. > > > > On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > > > > > Yes it would work -- and is probably better from a resource point of > > view > > > anyway. On the other hand, that won't work for the ejbdoclet issues. > > > > > > On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > > > > > > Just add a common jar as the 1st module, and add that jar to your > > legacy > > > > code. Would that work? > > > > > > > > > > > > > > > > On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > > > > > > > > > that would work -- except I am pulling in a legacy build system > here > > > > > and would rather not have to start moving code around at that > level > > > > > > > > > > > > > > > On 2/16/07, Mick Knutson <[EMAIL PROTECTED]> wrote: > > > > > > I use hibernate doclet, and it acts the same for me. > > > > > > I just have my 1st module is my common-jar that gets added to > all > > my > > > > > modules > > > > > > anyways. Works fine even though it is strange... > > > > > > > > > > > > > > > > > > On 2/16/07, Eric Helfrich <[EMAIL PROTECTED]> wrote: > > > > > > > > > > > > > > Has anyone been able to get this to work correctly? Hibernate > > > > doclet > > > > > > > and ejbdoclet do not work correctly -- ejb doclet generates > all > > > > files > > > > > > > in the generated sources directory of the first project it > runs. > > > > > > > Hibernate doclet does not seem to find the source files at all > > > when > > > > > > > run from a parent project which defines the plugin - -but > works > > > fine > > > > > > > if generate-sources is run on the sub project. Any ideas? > > > > > > > > > > > > > > > > > > > - > > > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > -- > > > > > > --- > > > > > > Thanks, > > > > > > Mick Knutson > > > > > > > > > > > > http://www.baselogic.com > > > > > > http://www.blincmagazine.com > > > > > > http://www.djmick.com > > > > > > http://www. . /djmick_dot_com > > > > > > http://www.thumpradio.com > > > > > > --- > > > > > > > > > > > > > > > > > > - > > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > -- > > > > --- > > > > Thanks, > > > > Mick Knutson > > > > > > > > http://www.baselogic.com > > > > http://www.blincmagazine.com > > > > http://www.djmick.com > > > > http://www. . /djmick_dot_com > > > > http://www.thumpradio.com > > > > --- > > > > > > > > > > > > > > > -- > > --- > > Thanks, > > Mick Knutson > > > > http://www.baselogic.com > > http://www.blincmagazine.com > > http://www.djmick.com > > http://www. . /djmick_dot_com > > http://www.thumpradio.com > > --- > > > -- --- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www. . /djmick_dot_com http://www.thumpradio.com ---
Maven 2 compile and IBM javac
I am getting the following error with maven 2 configured to use ibm
1.4. When I switch back to the sun jdk I get no error. Any ideas how
I can get this to give me more info?
Here is the relevant section of my pom:
in properties
c:/was6/java/bin/javac
org.apache.maven.plugins
maven-compiler-plugin
true
true
${ibm-jdk-path}
1.4
the ibm java info
java version "1.4.2"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2)
Classic VM (build 1.4.2, J2RE 1.4.2 IBM Windows 32 build
cn142-20050609 (JIT enabled: jitc))
[exec] [INFO]
[exec] [ERROR] BUILD FAILURE
[exec] [INFO]
[exec] [INFO] Compilation failure
[exec] Failure executing javac, but could not parse the error:
[exec] [INFO]
[exec] [INFO] Trace
[exec] org.apache.maven.BuildFailureException: Compilation failure
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:555)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
[exec] at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
[exec] at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
[exec] at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
[exec] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[exec] at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[exec] at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[exec] at java.lang.reflect.Method.invoke(Method.java:585)
[exec] at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
[exec] at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
[exec] at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
[exec] at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[exec] Caused by:
org.apache.maven.plugin.CompilationFailureException: Compilation
failure
[exec] at
org.apache.maven.plugin.AbstractCompilerMojo.execute(AbstractCompilerMojo.java:505)
[exec] at
org.apache.maven.plugin.CompilerMojo.execute(CompilerMojo.java:111)
[exec] at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
[exec] at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
[exec] ... 16 more
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
