Maven plugin testing
Hi all, I am developing a plugin that copies some dependencies to a directory. I'm doing this because I need to setup a server by copying some JARs to a deployment directory. I am having lots of problems understanding the different plugin testing methods described on the page : http://maven.apache.org/plugin-developers/plugin-testing.html Are there any definitions for the different types of tests ? Basically all I need to do is to launch my plugin so that I can validate the code I'm developing, and make sure everything is correct, preferably using a test pom. Any help with this would be greatly appreciated. Regards, Serge Huber.
Re: Shared dependencies deployment to Tomcat 5.5 or 6.0 + other servers
Hi Adam, Sorry I missed your reply, only saw it now. Basically my requirements is that I'm am developing APIs that will be shared across different WARs, along with an integration with Pluto & J2 that needs it's JARs deployed to the shared classloader. I want to avoid manual copy as I want to automate this for building fully functional deployments for QA and distribution. We have this process running fine in Maven 1, but I must admit it is a hard transition for me to Maven 2. In Maven 1 I simply used dependency properties to mark the libraries as "shared", and had to be careful to maintain version consistency. In Maven 2 I am cleaning this process by using a top project for these dependencies, but I'm still running into the problem of packaging these dependencies properly, and only these. Ideally I would like to have something like this : appserver:deploy-shared-libs And this would automatically deploy shared libraries into Tomcat 5.5, Tomcat 6, Websphere and Weblogic. Any assistance on this topic would be really welcome. I hope it is clearer. Regards, Serge Huber. On Dec 22, 2007 8:53 PM, Adam Hardy <[EMAIL PROTECTED]> wrote: > Hi Serge, > > it's a bit unclear what your aim is here, or rather your requirements. > > You have one project or more? When running a deploy to the server, m2 > would > generally speaking just deploy a WAR file to the server's deploy > directory, e.g. > webapps in tomcat 5 & 6. > > If you are building several projects which would need to share jars that > you > want to put in a webserver's common directory, then do it manually. What > reason > do you have to redeploy such common jars? If they are dependencies of > several > projects, then it seems you require maven to maintain version consistency > across > several projects and to determine what versions of projects were already > deployed, which seems unreasonably complicated. I doubt there is a plugin > which > does such a thing. > > Regards > Adam > > Serge Huber on 20/12/07 14:54, wrote: > > Hi all, > > > > I am in the process of converting a rather complex project from Maven 1 > to > > Maven 2, and despite my best attempts at googling for these answers, I > have > > only been able to go so far. I've also been looking at some projects, > like > > Jetspeed 2, that seems to be doing some rather advanced stuff with Maven > 2. > > > > Anyway, in our existing Maven 1 project, we use Jelly scripts to perform > > deployment of "common" resources to our Tomcat server. The problem is > that > > Tomcat has been moving around things in the latest versions, and > deployment > > of common resources is different between Tomcat 5.5 and 6. In Tomcat 5.5we > > would copy the required dependencies manually to tomcat/shared/lib, but > I > > didn't really think this was the cleanest way of doing this. > > > > As I am re-organizing our project structure for Maven 2, I was building > a > > "common" sub-project with all the dependencies, which is cleaner than > what > > we use to do, but I know have no idea how best to deploy these, > especially > > based on the different locations for different Tomcat versions. Should I > use > > the tomcat-maven-plugin ? Should I use Cargo ? Which one of the two has > the > > biggest community ? If I should build my own Mojo, is there a > recommended > > way to build deployment plugins, using maybe profiles to make it as > server > > independent as possible ? Lots of questions as you can see :) > > > > I really hope someone out there can help, because I can't believe I'm > the > > only one having this issue :) > > > > cheers, > > Serge... > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Shared dependencies deployment to Tomcat 5.5 or 6.0 + other servers
Hi all, I am in the process of converting a rather complex project from Maven 1 to Maven 2, and despite my best attempts at googling for these answers, I have only been able to go so far. I've also been looking at some projects, like Jetspeed 2, that seems to be doing some rather advanced stuff with Maven 2. Anyway, in our existing Maven 1 project, we use Jelly scripts to perform deployment of "common" resources to our Tomcat server. The problem is that Tomcat has been moving around things in the latest versions, and deployment of common resources is different between Tomcat 5.5 and 6. In Tomcat 5.5 we would copy the required dependencies manually to tomcat/shared/lib, but I didn't really think this was the cleanest way of doing this. As I am re-organizing our project structure for Maven 2, I was building a "common" sub-project with all the dependencies, which is cleaner than what we use to do, but I know have no idea how best to deploy these, especially based on the different locations for different Tomcat versions. Should I use the tomcat-maven-plugin ? Should I use Cargo ? Which one of the two has the biggest community ? If I should build my own Mojo, is there a recommended way to build deployment plugins, using maybe profiles to make it as server independent as possible ? Lots of questions as you can see :) I really hope someone out there can help, because I can't believe I'm the only one having this issue :) cheers, Serge...
Shared dependencies deployment to Tomcat 5.5 or 6.0 + other servers
Hi all, I am in the process of converting a rather complex project from Maven 1 to Maven 2, and despite my best attempts at googling for these answers, I have only been able to go so far. I've also been looking at some projects, like Jetspeed 2, that seems to be doing some rather advanced stuff with Maven 2. Anyway, in our existing Maven 1 project, we use Jelly scripts to perform deployment of "common" resources to our Tomcat server. The problem is that Tomcat has been moving around things in the latest versions, and deployment of common resources is different between Tomcat 5.5 and 6. In Tomcat 5.5 we would copy the required dependencies manually to tomcat/shared/lib, but I didn't really think this was the cleanest way of doing this. As I am re-organizing our project structure for Maven 2, I was building a "common" sub-project with all the dependencies, which is cleaner than what we use to do, but I know have no idea how best to deploy these, especially based on the different locations for different Tomcat versions. Should I use the tomcat-maven-plugin ? Should I use Cargo ? Which one of the two has the biggest community ? If I should build my own Mojo, is there a recommended way to build deployment plugins, using maybe profiles to make it as server independent as possible ? Lots of questions as you can see :) I really hope someone out there can help, because I can't believe I'm the only one having this issue :) cheers, Serge...
[ANN] MevenIDE for JBuilder 0.2 released
The mevenide team is pleased to announce the JBuilder Maven OpenTool 0.2 release! http://mevenide.codehaus.org/mevenide-ui-jbuilder This project integrates Maven with the JBuilder IDE. The features include goal launching from IDE, integration of goals in build process and project dependency integration. Changes in this version include: Fixed bugs: o MEVENIDE-162 : Applied patch created by George Lindholm to allow for spaces in MAVEN_HOME property o Made OpenTool compatible with JBuilder 2005 Have fun! -The mevenide team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven roadmap - should i stay or should i go
Gosh this Maven 2 is beginning to sound really good !
Now the waiting will be even harder :)
cheers,
Serge...
Brett Porter wrote:
Will there be a facility in the new (maven 2) POM to specify the default
goals required to build the artifact (either fully stated ${pom.goals}
or determined by some other variable ${pom.type}?).
The latter, yes. We may add a default to the POM later.
Also will there be
a means to specify plugins and their minimum version requirements
in the dependencies?
yes
I think I caught talk about even specifying the
difference in dependencies between build/run/test/cactus/integration time,
is this categorization the ability I'm looking for?
yes
Cheers,
Brett
-
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 roadmap - should i stay or should i go
Brett Porter wrote: http://maven.apache.org/using/bestpractices.html#Scripting Oops sorry... I didn't check out the new content yet :) Regards, Serge Huber. On Thu, 24 Mar 2005 15:02:15 +0100, Serge Huber <[EMAIL PROTECTED]> wrote: I once got the great advice from a MevenIDE developer that I should keep the maven.xml file to a strict minimum, and develop plugins mostly using Java classes. I've used that advice well, and it looks like at least for me, migrating to Maven 2 wouldn't be too much of a problem. Maybe this should be on a page somewhere, in order for people to prepare for Maven 2 ? Basically telling them that in order to build scripts & plugins that are compatible with Maven 2, they should follow these two guidelines as much as possible ? Regards, Serge Huber. Brett Porter wrote: Huh... Exactly how much trouble are we talking about to switch custom plugins and such??? Is Jelly replaced? Yes, though we are trying hard to put in a replacement that can transparently run old Jelly scripts with minimal changes. Part of the problem is that people have come to rely on bugs in Jelly/Jexl/Maven for their scripts to work. And if so, with what and why? Speed and memory usage are a big factor. In Maven 2.x, most plugins are written in pure Java, though theoretically adapters can be written for any scripting language. There will be an XML scripting language present for the benefit of users who want to interface with Ant tasks, though it won't at all be necessary to use it day to day. Does it mean all the custom stuff I'm currently implementing will be thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to be in production for more than a couple of months... Maven 1.x is not going to disappear - if your investment outweighs the benefit, then stick with it. More information will be available as the first releases draw near. For now - Maven 1.1 and its plugins continue to be developed. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven roadmap - should i stay or should i go
I once got the great advice from a MevenIDE developer that I should keep the maven.xml file to a strict minimum, and develop plugins mostly using Java classes. I've used that advice well, and it looks like at least for me, migrating to Maven 2 wouldn't be too much of a problem. Maybe this should be on a page somewhere, in order for people to prepare for Maven 2 ? Basically telling them that in order to build scripts & plugins that are compatible with Maven 2, they should follow these two guidelines as much as possible ? Regards, Serge Huber. Brett Porter wrote: Huh... Exactly how much trouble are we talking about to switch custom plugins and such??? Is Jelly replaced? Yes, though we are trying hard to put in a replacement that can transparently run old Jelly scripts with minimal changes. Part of the problem is that people have come to rely on bugs in Jelly/Jexl/Maven for their scripts to work. And if so, with what and why? Speed and memory usage are a big factor. In Maven 2.x, most plugins are written in pure Java, though theoretically adapters can be written for any scripting language. There will be an XML scripting language present for the benefit of users who want to interface with Ant tasks, though it won't at all be necessary to use it day to day. Does it mean all the custom stuff I'm currently implementing will be thrown out if I upgrade to 2.x when it comes out? I'd like my stuff to be in production for more than a couple of months... Maven 1.x is not going to disappear - if your investment outweighs the benefit, then stick with it. More information will be available as the first releases draw near. For now - Maven 1.1 and its plugins continue to be developed. - Brett - 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 roadmap - should i stay or should i go
Brett Porter wrote: Vincent has pretty well summed it up. I will try to clarify the document. Though the basic concepts are the same, Maven 2.x is really quite different, and it will require some work to move a project over to it. How much depends on how heavily you customise your Maven 1.x project - if you stick to the defaults and don't use Jelly, then it should be quite simple. Maven 1.x will still be developed until Maven 2.x is production ready (which is not going to be until later this year). Arg I want Maven 2 now :) Just kidding, keep up the great work guys, but it's a long wait to Maven 2 it seems. Can you enlighten us as to the major road blocks you're encountering with Maven 2 ? Regards, Serge Huber. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mevenide with JBuilder 2005
Hi Andrew, Here you are : http://mevenide.codehaus.org/mail-lists.html Regards, Serge Huber. Andrew Watters wrote: Hi Serge Thanks for your reply. I did look for a mevenide list but couldn't find one. Could you point me in the right direction please? Thanks Andrew Serge Huber wrote: Hi Andew, You might want to move this question to the MevenIDE lists. Anyway I have found a bug in my class loading code because JBuilder 2005 did some last minute changes before release. It will be corrected in the next release. Regards, Serge Huber. Andrew Watters wrote: Has anybody succeeded in getting the mevenide working with JBuilder 2005? I have put the mevenide jar into JBuilders lib\ext folder and added project.xml to my JBuilder project but I get absolutely nothing. JBuilder sees project.xml as any other XML file. Please help! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mevenide with JBuilder 2005
Hi Andew, You might want to move this question to the MevenIDE lists. Anyway I have found a bug in my class loading code because JBuilder 2005 did some last minute changes before release. It will be corrected in the next release. Regards, Serge Huber. Andrew Watters wrote: Has anybody succeeded in getting the mevenide working with JBuilder 2005? I have put the mevenide jar into JBuilders lib\ext folder and added project.xml to my JBuilder project but I get absolutely nothing. JBuilder sees project.xml as any other XML file. Please help! - 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: I am surprised that no one replied to the question I posted yesterday!!
This is not a commercial support mailing list. No guarantees are given as to response times, nor are any guarantees given to an actual response. People that post in this mailing list do so mostly out of good will. Regards, Serge Huber. Sachin Bansal wrote: Guys, I posted this message yesterday and I have not heard from anyone. Does that mean Maven DOES NOT have any solution to my *simple* problem? I have the following structure (my project is creating an eclipse plugin for xml editor) : myProject com.abc.def.A com.abc.def.B com.abc.def.C com.abc.def.D com.abc.def.E com.abc.def.F There are interdependencies among the projects. They all produce jar files. A depends on B, C and D B depends on E consequently I would to first build E, then B, C and D. Finally I would like Maven to build A The depenedency as declared in the project file of project A is as myProject com.abc.def.B 1.0 myProject com.abc.def.C 1.0 myProject com.abc.def.D 1.0 I DO NOT want maven to search for the com.abc.def.C-1.0.jar or com.abc.def.B-1.0.jar in the maven repository in order to build com.abc.def.A-1.0.jar. I want maven to first build project E, then B and then build project C, D and finally A. I want maven to figure this out dynamically, figuring it out from dependency File that it should first build project B and for that it will have to first build project E(just as Ant does, using depends target, or the sequence of execution) Adam Fisk suggested that calling multiproject:install does it automatically, but it does not work. Everytime it looks for the *.B-1.0.jar or *.C-1.0.jar to be there in my repository and complains when it does not find those jar files. Please help. Sachin [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]
Using and classLoaders
Hi all, I'm having some trouble using the Jelly define tags. Basically what I'm trying to do is define a jellyBean tag to use the Jasper compiler on a Tomcat version of my choice. So far I have tried something along the lines of : but this doesn't work because I can't reference the Ant refid in the classloader tag. Also it seems the classLoader tag only accepts a SINGLE URL as a parameter, not a collection of them (I looked at the source code for this tag and this was my understanding). I know that I can use the dependency classpath to define all I need, but that means hardcoding the Tomcat version I can use this tag with, which is what I'm trying to undo. I've searched all over Google, Maven and Jelly websites and I must say I'm at a loss here. Any help would be greatly appreciated ! Regards, Serge Huber. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Plugin to generate JBuilder OpenTool 0.1 (initial release)
The mevenide team is pleased to announce the Maven JBuilder Opentool Plugin 0.1 release! This new Maven plugin eases the creation of JBuilder OpenTool extensions, and is used to build the new JBuilder Maven OpenTool, that integrates Maven and JBuilder. For more information about this Maven plugin, you can visit the following site : http://mevenide.codehaus.org/maven-jbuilder-opentool-plugin/index.html Changes in this version include: New Features: o Generates 3 types of OpenTool packages : standalone JAR, .config file that points to Maven repository, .config file that points to subdirectory. To automatically install the plugin, add the http://mevenide.codehaus.org/repository to your maven.repo.remote parameter. Then type the following on a single line: maven plugin:download -DgroupId=mevenide -DartifactId=maven-jbuilder-opentool-plugin -Dversion=0.1 For a manual installation, you can download the plugin here: http://mevenide.sourceforge.net/repository/mevenide/plugins/maven-jbuilder-opentool-plugin-0.1.jar Have fun! -The mevenide team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Iterating through directories
How does one iterate through directories in a Maven Jelly script ? I found the following resource to iterate through FILES in a directory : http://wiki.astrogrid.org/bin/view/Astrogrid/UsefulMavenNotes#Iterating_through_a_list_of_file but what I need to do is simply get the list of subdirectories for a given parent directory, and then iterate through them using a tag. I've tried replacing the in the above resource with a but it seems that the doesn't allow this. Or maybe I'm completely off and there is a way to do this with Jelly instead of Ant ? Regards, Serge Huber. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Ann: Mavenzilla
Another feature that would be cool is to support "download location" for libraries that cannot be stored in repositories because of licenses. Basically if there was a way for example to retrieve the javamail distrib on java.sun.com, *going* through the license agreement and everything, and then putting it in the user's local repository. Regards, Serge Huber. Moritz Petersen wrote: Mavenzilla is a browser for Maven repositories. http://jface.sourceforge.net/mavenzilla/ To be honest: it is currently in a very early development stage, and more a prototype than a real application. The question is: is a repository browser neccessary / useful, or am I missing a point with Maven? Often, I browse the ibiblio repository, to take a look at the latest version of a dependency. I would be interested to know the experiences / practices of other users when working with maven. How do you determine the version you will use in your project? Thank you, Moritz. - 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: Codeczar Maven Tomcat Plugin improvements suggestions
Hi Nathan,
I realized that my suggestion for the fragment replacement wasn't good, as
I used a jelly expression.
So instead of :
we should use something like :
or anything else that doesn't include ${} format.
Also if I can help with the Tomcat plugin I'd be interested, provided I
have the time and knowledge. Let me know.
Regards,
Serge Huber.
At 00:09 13.09.2004, you wrote:
thanks Serge,
your suggestions are all good. I was sure the plugin compiled the
generated java sources too - I'll check. I've collected a number of other
suggestions for improvements to the plugin. I hope to have an improved
version available some time in the next few weeks.
cheers
Nathan
Serge Huber wrote:
Hi all,
First of all thanks to the guys at codeczar for their plugin. It's really
helpful.
I've recently started using the tomcat:jspc goal and I've had a few
problems. First of all it fails if I don't declare a maven.war.src
directory explicitely in my project.properties. This might be due to the
final version of the WAR plugin that I'm using with Maven 1.0 final.
Also, the JSP are translated into Java source code, but there is no
target to compile the source code which I find a shame.
Last but not least the
@maven.tomcat.generated@
to be inserted in the web.xml file is not very elegant because if we
don't execute the merge, we will end up with an invalid web.xml file. I
suggest to use something like this :
I have very limited knowledge of Jelly so I'm not sure how I can help do
all these changes. I am showing below some goals that do implement all
the stuff I've talked about, but they are not integrated with the Tomcat
plugin. The following code has been tested with Tomcat 5.0.18 only.
Regards,
Serge Huber.
project.xml (extract & the same as the Tomcat plugin) :
---
tomcat
catalina-ant
5.0.18
root
tomcat
jasper-compiler
5.0.18
tomcat
jasper-runtime
5.0.18
commons-logging
commons-logging
1.0.3
commons-el
commons-el
1.0
root
servletapi
servlet-api
2.4-20040521
jar
jspapi
jsp-api
2.0-20040521
root
jar
project.properties :
# Set to true if you want JSP precompilation to happen after war:webapp goal
precompile.jsp=true
maven.xml :
---
xmlns:j="jelly:core"
xmlns:define="jelly:define"
xmlns:util="jelly:util"
xmlns:jasper="jasper"
xmlns:ant="jelly:ant">
name="JspC"
className="org.apache.jasper.JspC"
method="execute"
/>
- -- --- -=[ shuber2 at jahia dot com ]= --- -- -
www.jahia.org : A collaborative source CMS and Portal Server
-
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]
- -- --- -=[ shuber2 at jahia dot com ]= --- -- -
www.jahia.org : A collaborative source CMS and Portal Server
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Accessing Maven properties from a Jelly Bean ?
Hi Stefan, Thanks for the quick answer, it helped a lot ! Regards, Serge Huber. At 20:10 14.08.2004, you wrote: Hi Serge, just a short sample how i accessed simple properties: Hope this helps, -Stefan > -Original Message- > From: Serge Huber [mailto:[EMAIL PROTECTED] > Sent: Saturday, August 14, 2004 7:27 PM > To: Maven Users List > Subject: Accessing Maven properties from a Jelly Bean ? > > > > Hi all, > > I'm a beginner, trying to develop my first Maven plugin, and I'm a > little lost :) > > I need to develop some functionality through a Jelly Bean, but I also > need to access some Maven properties (especially POM properties) from > the bean. Basically what I need to access in my Jelly Bean is : > > - the POM's dependencies > - other project related properties. > > I understand that I can pass parameters through to the JellyBean via > XML attributes, but can I pass a list of dependencies or > something like > that ? What is the recommended way of developing this functionality ? > > Thanks a lot, >Serge Huber. > > > - > 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] - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Accessing Maven properties from a Jelly Bean ?
Ok thanks, I have been developing a tag library over the week-end and it does work the way you specified. I just didn't believe Jelly could be that powerful ! Regards, Serge Huber. At 08:39 15.08.2004, you wrote: On Sat, 14 Aug 2004 19:26:48 +0200, Serge Huber <[EMAIL PROTECTED]> wrote: > - the POM's dependencies Following on, 'pom' is the project.xml as an object. > I understand that I can pass parameters through to the JellyBean via > XML attributes, but can I pass a list of dependencies or something like > that ? What is the recommended way of developing this functionality ? Use a bean. -- http://www.multitask.com.au/people/dion/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Accessing Maven properties from a Jelly Bean ?
Hi all, I'm a beginner, trying to develop my first Maven plugin, and I'm a little lost :) I need to develop some functionality through a Jelly Bean, but I also need to access some Maven properties (especially POM properties) from the bean. Basically what I need to access in my Jelly Bean is : - the POM's dependencies - other project related properties. I understand that I can pass parameters through to the JellyBean via XML attributes, but can I pass a list of dependencies or something like that ? What is the recommended way of developing this functionality ? Thanks a lot, Serge Huber. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Improvements suggestion for WAR plugin
The goal I proposed is completely optional, and I don't think it
conflicts with the specification. The packaging just puts all the
*.class files into a JAR under WEB-INF/lib instead of leaving them in
WEB-INF/classes.
Anyway I checked the Servlet Spec 2.4 and I found the following under
SRV 9.5 Directory Structure :
"The contents of the WEB-INF directory are:
• The/WEB-INF/web.xmldeployment descriptor.
• The/WEB-INF/classes/ directory for servlet and utility classes. The
classes in this directory must be available to the application class
loader.
• The/WEB-INF/lib/*.jar area for Java Archive files. These files
contain servlets, beans, and other utility classes useful to the Web
application. The Web application class loader must be able to load
classes from any of these archive files.
The Web application class loader must load classes from the
WEB-INF/classes directory first, and then from library JARs in the
WEB-INF/lib directory. Also, any requests from the client to access the
resources in WEB-INF/ directory must be returned with
aSC_NOT_FOUND(404) response. "
It seems therefore allowed to put servlets and other resources in JARs
and even have an empty WEB-INF/classes directory.
However I fully understand that this patch might not have it's place in
the WAR plugin although I think it might (I don't really see where else
to put it), but I was just proposing it in case somebody was interested
in this functionality.
Regards,
Serge Huber.
On Aug 12, 2004, at 6:58 PM, Carlos Sanchez wrote:
Hi,
You can raise a feature request in JIRA, but IMHO this patch is not a
good
idea as including *.class in /WEB-INF/classes just follows the webapp
specification.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
-Original Message-
From: Serge Huber [mailto:[EMAIL PROTECTED]
Sent: Thursday, August 12, 2004 5:41 PM
To: [EMAIL PROTECTED]
Subject: Improvements suggestion for WAR plugin
Hi all,
Here is a quick & dirty suggestion for the WAR plugin for
those of you who don't want to package WAR files with tons of
stuff in the WEB-INF/classes directory. This little preGoal
will allow you to package either just the *.class files into
a JAR, or the whole content of the WEB-INF/classes directory.
First of all here are the properties :
# set to true if you want the contents of WEB-INF/classes to
be packaged into a JAR in WEB-INF/lib
maven.war.jarclasses=true # the name of the JAR in
WEB-INF/lib
maven.war.jarclasses.name=${pom.artifactId}-${pom.currentVersion}.jar
# set to true if you only want the *.class files in the JAR,
false will include the whole contents of WEB-INF/classes
maven.war.jarclasses.justclasses=true
Here is the preGoal :
basedir="${maven.build.dir}/${pom.artifactId}/WEB-INF/classes"
includes="**/*.class"
/>
basedir="${maven.build.dir}/${pom.artifactId}/WEB-INF/classes"
includes="**/*"
/>
I hope this could be included into the WAR plugin as it is
very useful to me and maybe to others. How should this
happen, can someone take this up or should I try to modify
the plugin myself. Please be informed my Jelly knowledge is
*very* limited.
Regards,
Serge Huber.
- -- --- -=[ shuber2 at jahia dot com ]= --- -- -
www.jahia.org : A collaborative source CMS and Portal Server
-
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]
Improvements suggestion for WAR plugin
Hi all,
Here is a quick & dirty suggestion for the WAR plugin for those of you who
don't want to package WAR files with tons of stuff in the WEB-INF/classes
directory. This little preGoal will allow you to package either just the
*.class files into a JAR, or the whole content of the WEB-INF/classes
directory.
First of all here are the properties :
# set to true if you want the contents of WEB-INF/classes to be packaged
into a JAR in WEB-INF/lib
maven.war.jarclasses=true
# the name of the JAR in WEB-INF/lib
maven.war.jarclasses.name=${pom.artifactId}-${pom.currentVersion}.jar
# set to true if you only want the *.class files in the JAR, false will
include the whole contents of WEB-INF/classes
maven.war.jarclasses.justclasses=true
Here is the preGoal :
basedir="${maven.build.dir}/${pom.artifactId}/WEB-INF/classes"
includes="**/*.class"
/>
basedir="${maven.build.dir}/${pom.artifactId}/WEB-INF/classes"
includes="**/*"
/>
I hope this could be included into the WAR plugin as it is very useful to
me and maybe to others. How should this happen, can someone take this up or
should I try to modify the plugin myself. Please be informed my Jelly
knowledge is *very* limited.
Regards,
Serge Huber.
- -- --- -=[ shuber2 at jahia dot com ]= --- -- -
www.jahia.org : A collaborative source CMS and Portal Server
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Codeczar Maven Tomcat Plugin improvements suggestions
Hi all, First of all thanks to the guys at codeczar for their plugin. It's really helpful. I've recently started using the tomcat:jspc goal and I've had a few problems. First of all it fails if I don't declare a maven.war.src directory explicitely in my project.properties. This might be due to the final version of the WAR plugin that I'm using with Maven 1.0 final. Also, the JSP are translated into Java source code, but there is no target to compile the source code which I find a shame. Last but not least the @maven.tomcat.generated@ to be inserted in the web.xml file is not very elegant because if we don't execute the merge, we will end up with an invalid web.xml file. I suggest to use something like this : I have very limited knowledge of Jelly so I'm not sure how I can help do all these changes. I am showing below some goals that do implement all the stuff I've talked about, but they are not integrated with the Tomcat plugin. The following code has been tested with Tomcat 5.0.18 only. Regards, Serge Huber. project.xml (extract & the same as the Tomcat plugin) : --- tomcat catalina-ant 5.0.18 root tomcat jasper-compiler 5.0.18 tomcat jasper-runtime 5.0.18 commons-logging commons-logging 1.0.3 commons-el commons-el 1.0 root servletapi servlet-api 2.4-20040521 jar jspapi jsp-api 2.0-20040521 root jar project.properties : # Set to true if you want JSP precompilation to happen after war:webapp goal precompile.jsp=true maven.xml : --- - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ibiblio central repository
At 14:13 01.04.2004, you wrote: It's interesting to use maven-proxy for private company repos. If you want to create a public repo, it's preferrable to put in it only yours jars if you don't use a rsync with ibiblio. http://www.bluesunrise.com/maven used by the jetspeed project is an example of a bad repository. Am I understanding this right : it's a bad repository because it duplicates the content without sync ? I myself want to learn to do this right, so that's why I'm asking all these newbie questions :) Some projects doesn't use the SNAPSHOT extension and put their files on a repo but this jars doesn't the a complete release(beta, rc, final). If you don't use the snapshot extension and you put a jar in a repo with another extension (for example -dev), the jar file will be download one times by users, and only one. If the jar file change, it will be never re-downloaded by maven because it's in local repo of users and it isn't a snapshot. Yep I'm aware of that. I saw that others use dates coded such as 20040401, maybe that's a better way to use snapshots if one wants to avoid breaking the build all the time ? The torque plugin can be put (snapshot and final version) in ibiblio directly by the torque team (it's the same for all apache projects) . I perfectly understand that the will is to have a central repository much in the same way as Debian has. But in order to get there, for practical reasons, people need intermediate repositories to work on a day-to-day basis (like the "right away" example I was giving). What would be great is to have a way to create an entry in a "personal" repository, and then use a maven plugin to submit it for inclusion into the ibiblio repository. So basically what I would do is : 1. insert the entry into my "personal repository", maven jar:deploy 2. send a submission for my JAR to the central repository maven jar:submit 3. remove the jar from my "personal repository" once it has been inserted into ibiblio : maven jar:sync or something. Is this already available ? As I said, I'm a newcomer eager to learn, sorry if this is the twentieth time this is answered, just point me to an existing reply would do the tick :) Regards, Serge Huber. - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ibiblio central repository
At 13:40 01.04.2004, you wrote: There are mirrors of ibiblio. Planet Mirror is one. SunSource is another from memory (not sure). Ok, wasn't aware of them... Maybe they should be listed on the Maven web site ? Whatever the companies require. We use the maven-proxy from CodeHaus to host our repos, that way if we don't have a jar, it'll go get it from our defined remote repos. Thanks for the tip, I'll have a look at it, it seems like an interesting plugin. > 3. Another advantage of a "personal" remote repository is the possibility > to instantly add JARs you require, since even despite the really good > efforts by Maven committers, it will take time, and sometimes you just want > things "right away". What is the best practice in such cases ? Local Repo -> Company Repos -> Optional Regional Mirrors -> ibiblio. Ok makes sense... Again something nice for the Maven site I would guess :) Thanks for your quick answer, Regards, Serge Huber. - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: ibiblio central repository
At 13:39 01.04.2004, you wrote: > 1. What happens if ibiblio suddenly becomes unavailable ? Shouldn't Maven > have a mirroring system the same way Debian repositories have ? It should, and I think someday in the future it might. However, ibiblio's aim is to be a library for the internet, so we can hope it stays up. I didn't mean down like removed, but simply temporarily (a few days maybe) unreachable.. That would be problematic for all the people trying to reach the default remote repository. If you are deploying a single project that has very specific dependencies, then sure, put them in your own repository. However, if your project depends on artifacts made by others then it helps to get them up on ibiblio because it reduces load on your servers and others can use them as well in there projects. Ok that makes sense. Most plugins where bundled in with the maven install. Over time, plugins have been broken out, like Torque, and returned to the project they came from. However, many of them, like Torque, are waiting for their next release to be cut to be put online at ibiblio. I think over time you will see more plugins on ibiblio. Over time ok, but what if I had a dependence on it, worked fine with RC 1, and suddenly stops working with RC 2 ? I guess this is where my "personal remote repository" comes into place... Thanks for the very quick answers ! Regards, Serge Huber. - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven JBuilder OpenTool
At 13:25 01.04.2004, you wrote: > > Hi all, > > I'd like to announce a preview version of my Maven JBuilder OpenTool. So Awesome! Thanks, I put some hard hours of work into it, and had to fumble through a lot of undocumented calls to get it working. Fortunately it now uses only 100% documented JBuilder APIs so I'm quite confident that it should be portable. I forgot to give the features of the plugin, here is basically what it's able to do : - Same level of integration into JBuilder as Ant (well almost) - Integration in project tree of all plugins and goals associated with a maven.xml file so it's easy to launch a goal - Goals may be configured to be launched just before running a program, for example to launch a Maven goal for deployment and then launch the program (I use this almost every 5 minutes :)) - Automatic creation of a JBuilder library called MavenAutoUpdated that contains all the dependencies for the project associated with the current maven.xml (searches in the same directory for a project.xml file). You can then add this library to your project (or not, you have the choice !) and automagically all your dependencies are added to your project. The dependencies point to your local repository so make sure you have launched Maven previously on your project so that you have a complete set on your machine. Known limits are : - only one Maven per project, just add more projects if you need to handle more Maven files. This limit might be removed in the future if it becomes a problem Here are some screenshots that illustrate the integration : http://www.jahia.org/~loom/maven_jbuilder_opentool1.gif Note the left project view with the maven.xml file and all the plugins and goals available. http://www.jahia.org/~loom/maven_jbuilder_opentool2.gif An example of launching the catalina:deploy-shared goal http://www.jahia.org/~loom/maven_jbuilder_opentool3.gif An example of setting a Maven goal to be executed just before launching an application http://www.jahia.org/~loom/maven_jbuilder_opentool4.gif The settings dialog accessible by right-clicking the maven.xml file and selecting "Properties..." Regards, Serge Huber. - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven JBuilder OpenTool
Hi all, I'd like to announce a preview version of my Maven JBuilder OpenTool. So far I have tested it on JBuilder X (Foundation through Enterprise), but it might also work on previous versions, although I can't guarantee anything. It still has some rough edges, so make sure you read the HTML file included, that includes all the steps required for installation and configuration. You may find it here : http://www.jahia.org/~loom/mevenide-ui-jbuilder-20040401.zip I hope to commit it into the MevenIDE project (mevenide.sourceforge.net), but in the meantime I welcome all the feedback possible. I have started using this plugin in production two days ago for my work, so I think it should be useful to some other people. Regards, Serge Huber. - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ibiblio central repository
Hi all, First of all big thanks to all Maven developers, it's a really great tool, and despite some occasional quirks it works great ! Anyway, I have just converted a reasonably large project to Maven, and I'm still in the process of getting all the dependencies together. The problem is that I am having trouble understanding some of the reasoning behind the central repository, and therefore have more trouble explaining it to my fellow developpers. Here are some of the questions I got which I must say I am unable to answer with confidence. 1. What happens if ibiblio suddenly becomes unavailable ? Shouldn't Maven have a mirroring system the same way Debian repositories have ? 2. A lot of companies use their own remote repository. What should be in there, only what's not on ibiblio ? What about the failure case in question 1 ? 3. Another advantage of a "personal" remote repository is the possibility to instantly add JARs you require, since even despite the really good efforts by Maven committers, it will take time, and sometimes you just want things "right away". What is the best practice in such cases ? 4. For open source projects, such as the Apache developers, what are the best practices to ensure *coherent* JAR dependencies ? Because here I have of people that had either non-working SNAPSHOTs, or old ones, etc... 5. Why are there so little plugins on ibiblio ? For example the Torque plugin was removed from RC2 but isn't available on ibiblio. Is this normal ? As you can see, all my questions relate to the central repository. I am convinced that Maven is a great tool, but frankly I'm not sure how to answer any of these questions and I am sure that many of you have see and answered these a few times. Maybe I missed some explanation on the web page somewhere, if that is the case, thanks for pointing me to it. Regards, Serge Huber. - -- --- -=[ shuber2 at jahia dot com ]= --- -- - www.jahia.org : A collaborative source CMS and Portal Server - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
