upgrade between versions

Hi, I'm trying to upgrade my continuum from a version to another (1.1-alpha-2 to 1.1-beta-2). I don't want to re-create every projects and project groups. What is the best way to do it ? I tried to copy the 'data' directory but it seems that the db schema is not the same. A few weeks ago, I

Re: How to compile generated java code from test phase ?

I'm honestly not sure what the best/right approach would be in this situation. Off the top of my head, I have no idea if Maven can even handle your requirements, at least not with a single execution. But I can tell you what I might try... I would generate the java sources in the Maven test

Re: How to compile generated java code from test phase ?

I think the best way would be to create a plugin for your code generator and have it add the output directory to the test sources in the project object. On 8/19/07, Wayne Fay [EMAIL PROTECTED] wrote: I'm honestly not sure what the best/right approach would be in this situation. Off the top of

usefullness of the maven-eclipse-plugin

Hi, I was wondering what the use is of the eclipse plugin and mostly when it is usefull. I know it generates files for Eclipse but why /when would you use it? Most projects in our organization work with tools such as RSA or Eclipse with several project wizards. When they start developing

Re: Maven and macker plugin working??[UPDATES]

Hi Wayne, That's a great news for the community! Please let us informed ASAP when your M2 Macker plugin is available on the Mojo sandbox, and I'll try to give you some feedback of it. regards, Jeremy On 8/17/07, Wayne Fay [EMAIL PROTECTED] wrote: I've seen enough people asking for a M2 Macker

[Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)

Hi there, I have been reporting few weeks ago some VERY annoying warning like this one : [WARNING] POM for 'sapiens:SapiensCommonsCore:pom:2.6.0:test' is invalid. It will be ignored for artifact resolution. Reason: Failed to validate POM for project sapiens:SapiensCommonsCore at Artifact

testcompile: Nothing to compile - all classes are up to date (but they're not)

I had some suspious looking output: - I changed 1 test java file - I saved all files in eclipse - I ran mvn install, this is the output: [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date = ok [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes

Re: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)

Hi, is the parent pom referenced in the parent section producing the warning available in your local/corporate repository? -Tim Joel COSTIGLIOLA (Services DPT SYSTEME D INFORMATION METIER) schrieb: Hi there, I have been reporting few weeks ago some VERY annoying warning like this one :

Multi module project and maven-assembly-plugin

Hello, I have problem with attached goal. Parent POM: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion

Re: Multi module project and maven-assembly-plugin

lib-release.xml: ?xml version=1.0 encoding=UTF-8? assembly idlib-release/id formats formatzip/format /formats includeBaseDirectorytrue/includeBaseDirectory baseDirectory${artifactId}/baseDirectory moduleSets moduleSet includes

Question on maven-buildnumber-plugin

Hi, I'm using the maven-buildnumber--plugin version 0.9.5 It works but I would like to have both a timestamp and the build number from svn? Is this possible? Regards Gunnar - To unsubscribe, e-mail: [EMAIL PROTECTED] For

Make a Codehaus plugin works on a local configuration

Hi all, I need to use a plugin available from Codehaus sandbox (this plugin is http://mojo.codehaus.org/dashboard-maven-plugin/ dashboard-maven-plugin ). As explained in the plugin page, I need to add the following lines in my settings.xml file: Codehaus Snapshots

Re: HTML empty space in xdoc ...

The xdoc parser doesn't handle entities yet, as a workaround you can use character entities, ie use #160; instead of nbsp; HTH, -Lukas Giovanni Azua wrote: lol :))) Okay here it is the snippet: p a href=download.html img valign=top src=images/download.png border=0 alt=

Re: testcompile: Nothing to compile - all classes are up to date (but they're not)

2007/8/20, Geoffrey De Smet [EMAIL PROTECTED]: [INFO] [compiler:testCompile] [INFO] Nothing to compile - all classes are up to date = not ok No, it's normal. By default, eclipse compile your java source classe when you save it. Modify you test java file with an external editor or uncheck

Re: Make a Codehaus plugin works on a local configuration

- Sorry, my previous mail was not properly sent. Here is a clen version - Hi all, I need to use a plugin available from Codehaus sandbox (this plugin is dashboard-maven-plugin). As explained in the plugin page, I need to add the following lines in my settings.xml file: pluginRepositories

RE: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)

Hi Tim - thanks for replying :) I'm using dependencyManagement a lot to avoid duplicating dependency information, do you think the presence of SapiensCommonsCore this section causes the warning (I haven't got time to test that yet) Here's the parent pom (SocleSapiens) : project

Re: Generate Version class

How is this done? Can you please give an example. I can not get it working using filtering java files like filtering resources. bakito Andrew Williams-5 wrote: You could configure the filtering to filter your java code as well as standard resources, though I don't know if that is what

EJB3.0 maven eclipse

Can you please explain to me the following. Ok, I am trying to use EJB3.0. To build it I have to use plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ejb-plugin/artifactId

Eclipse PDE Problem

Hi, We are developing an Eclipse plug-in for our framework which is managed by maven. Plug-in requires some sub-projects of the framework. So we want to use maven to also manage Eclipse plug-in dependencies without generating a plug-in project to achieve integration. How could we define this

Re: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)

I did a qick test using your parent pom and I'm getting the same warnings. They go away when I delete the two weblogic system scoped dependencies. I don't have this libraries on my system, so that makes sense. Could it be that ${bea.server.home} is just defined in your sapiens multi-build but

Re: usefullness of the maven-eclipse-plugin

http://m2eclipse.codehaus.org This is the right way to do it... it builds a classpath container from the dependencies in the pom, it resolves sources and javadocs for you. It means you can check in the .project and .classpath files and it just works for everyone. It works best with webdav and

how to enforce synchronization between source control and mvn deploy?

hi, because development team is working with eclipse i want to ensure that source control and contents of repository are synchronized. that means: 1) if someone does mvn:deploy, i want to display a warning, if working copy is not up to date to source control 2) if someone wants to do a commit

Re: Generate Version class

Create a new directory (for example 'src/main/classtemplates') and put you class template under the correct package directory in there. Then declare a additional resource in your pom: [...] resources resource directorysrc/main/classtemplates/directory

RE: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)

No, ${bea.server.home} is defined in the file settings.xml located in my .m2 directory so it should be available for all my maven project, right? Anyway, I will make couple tests to remove system scope dependencies to see if that was the cause of warnings. settings.xml contents (without

Re: how to enforce synchronization between source control and mvn deploy?

I don't have an answer (not an eclipse user), but I do have a note on 2): Don't force a deploy beforehand - the SCM might fail - you want to deploy after (assuming no conflicts). Andy On 20 Aug 2007, at 12:08, aldana wrote: hi, because development team is working with eclipse i want to

Re: Generate Version class

Though it is not exactly a best practice it is possible to filter the source in place using just a resources configuration similar to that posted (referencing src/main/java) - this would not require the buildhelper plugin. Andy On 20 Aug 2007, at 12:09, Tim Kettler wrote: Create a new

Maven Release Plugin - parameters: release version, release tag, new development version

Hi, By default, the release plugin will prompt for: - release version, - release tag, - new development version documentations says that the batch mode will use default values (based on the version that is specified in pom) but is there any way to explicitely specify those values in batch mode

webdav

Hello, why are not all the neccesary jars included in 2.0.7 to support deployment with web-dav? Regards, Borut

Eclipse Plugin Maven Integration...

I've posted but nobody answered for the problem. I will try to redefine the problem more clearly; There is an eclipse plug-in project which is dependent on other simple projects. At compile time, there is no problem but at run-time, plug-in project can not find the classes which are positioned in

Eclipse Plugin Problem

Hi, We are preparing a plugin project for our framework. This plugin uses other sub projects from framework. As a simple solution we bind other subprojects with existing plugin project to the eclipse. But we cannot intergrate this plugin project and other subprojects. When we run eclipse

Re: Generate Version class

You can load the pom properties off the class path so every maven built artifact in your class path has version information. Don't copy and paste this but it gives you the idea... InputStream in getClass().getResourceAsStream(META-INF/maven/path/to/pom.properties); Properties p = new

Re: Eclipse Plugin Maven Integration...

Hi, just a short recap to ensure I've understood you correctly: You have a couple of mavenized projects, one of them is a eclipse plugin. When you 'mvn package' on the plugin project everything is fine but when using the plugin in eclipse the classes from the dependencies are not found.

How can I generate a test client

Hi, I use the appassembler-maven-plugin to assemble a server application and it works fine. Now I would like to assemble a test client but I need to tell appassembler to include the test-classes. Is that possible and how should I do if it is? Regards Gunnar

Making resources separate dependencies

Hi all, I have a question: One of my projects needs a wsdl file resource from another project, but doesn't need anything else from this project. Is there a method to create some dependency (jar?) containing only that resource? Now I specify needed resources by pointing relative path to resource

When to use -SNAPSHOT when to use a build number

Just wondering, when should you convert from a -SNAPSHOT version to a fully fledge build number? When you convert to a build number, how does your build system update it internally? Does it edit/submit the pom(s)?

JDIC?

Can anyone tell me where I may find the JDIC libraries in a Maven-accessible repository? -- Vihung _ This e-mail may contain confidential information and/or copyright material. This e-mail is intended for the use of the addressee

Re: JDIC?

You should probably email the JDIC team and ask them if their jars are available in any Maven repos at this point, and if not, ask them to please consider submitting them. I checked www.mvnrepository.com and those jars do not appear to be available in the Central Maven repo at this time. Wayne

Re: [Maven2] : Failed to validate POM warnings (making a lot of really annoying logs !)

Eliminate the system scoped dependencies by using mvn install:install-file or mvn deploy:deploy-file to move those Weblogic files into the proper Maven repository structure. Then change scope system to scope compile, provided, runtime, or test as appropriate. See if that eliminates the annoying

Re: Eclipse Plugin Maven Integration...

Yes, You understood me correctly. We are trying to solve with your direction. When we overcome the exception, I will post the result... 2007/8/20, Tim Kettler [EMAIL PROTECTED]: Hi, just a short recap to ensure I've understood you correctly: You have a couple of mavenized projects, one

Re: When to use -SNAPSHOT when to use a build number

We go from SNAPSHOT to a real build number when we determine a build has sufficient functionality and stability to be considered for release. This is mostly objective but also a bit subjective in our process. You can use tools like Cobertura and Findbugs etc as well as your bug tracking system to

RE: When to use -SNAPSHOT when to use a build number

Once you have a tested stable version you do the release, and put it in a tag. You can then continue with the next snapshot. The Maven release plugin does edit the POMS, but I've yet to give it a go. The documentation would benefit from detailing the exact steps that occur. John -Original

Re: Making resources separate dependencies

A couple options: 1. This resource should live in its own artifact since it is a shared resource. So move it to its own project, and use maven-dependency-plugin:unpack mojo to make it available where it is needed (in both projects) at build time. 2. Copy this resource to a public webserver

RE: When to use -SNAPSHOT when to use a build number

I was afraid of the we manually build part, I kinda had a feeling. We have so many active branches at any time this would be nuts for us. I think I'll let CC continue to manage the versions. Another question I have is what is gained/lost from changing from a -SNAPSHOT version to a real version

Re: When to use -SNAPSHOT when to use a build number

Real version numbers are downloaded once. After you set a version number on an artifact, you can't change it. If you find a bug/issue, you must roll the version. Snapshots are checked for updates which are auto-downloaded. Wayne On 8/20/07, EJ Ciramella [EMAIL PROTECTED] wrote: I was afraid of

Re: webdav

You have to add an extension block in your POM to use webdav. http://maven.apache.org/guides/mini/guide-using-extensions.html -- Eric Redmond http://blog.propellors.net On 8/20/07, Borut Bolčina [EMAIL PROTECTED] wrote: Hello, why are not all the neccesary jars included in 2.0.7 to support

How to avoid hardcoding parent pom version in child poms?

I have a fairly large multi-project maven 2 project. All my child projects specify parent poms version using something like: parent artifactIdmyid/artifactId groupIda.b.c/groupId versionparent-pom-version/version /parent Every time I change parent pom's version I

Re: How to avoid hardcoding parent pom version in child poms?

If you use the release plugin, the change will be done automatically. Arnaud On 20/08/07, Farrukh Najmi [EMAIL PROTECTED] wrote: I have a fairly large multi-project maven 2 project. All my child projects specify parent poms version using something like: parent

Re: How to avoid hardcoding parent pom version in child poms?

Farrukh, Use the pluginManagement on your parent pom where you specify the version for a given plugin, then your child poms will inherit the version number.If you need to upgrade to a higher release, you simply have to change one pom file. Here's an example: Parent pom: pluginManagement

Re: How to avoid hardcoding parent pom version in child poms?

Hi Farrukh, The version for the parent pom is required, so you can't remove that from the child poms. Usually, you only change the version of your project when you release it. The maven release plugin already updates all the versions of the parent and child poms (in trunk) when it tags the

Re: How to avoid hardcoding parent pom version in child poms?

Oops, sorry pasted the wrong message on this thread. Anyway, take a look at the maven release plugin, it will update the versions for both parent and child pom files. Enrique Enrique

Re: How to globally set version of dependencies used commonly in child poms

Maria Odea Ching wrote: Hi Farrukh, The version for the parent pom is required, so you can't remove that from the child poms. Usually, you only change the version of your project when you release it. The maven release plugin already updates all the versions of the parent and child poms (in

Upgrade Strategy from 1.1-beta-1 to 1.1-beta-2

Hi, I would like to update my Continuum 1.1.beta-1 installation to the latest beta-2 release. I tried to locate upgrade information but could not find any. Could someone please point me to the document? In case there is none: What is the best or recommended strategy to upgrade and keep the

Re: How to globally set version of dependencies used commonly in child poms

This is basically the definition of dependencyManagement. Take a look at it, and add it to your parent pom. Wayne On 8/20/07, Farrukh Najmi [EMAIL PROTECTED] wrote: Maria Odea Ching wrote: Hi Farrukh, The version for the parent pom is required, so you can't remove that from the child

Re: How to globally set version of dependencies used commonly in child poms

Hi Wayne, I understand dependency management for most part. I want my dependencies in child poms to use property refs like: dependency groupIdcom.sun.xml.ws/groupId artifactIdjaxws-rt/artifactId version${jaxws.version}/version /dependency

Re: How to globally set version of dependencies used commonly in child poms

You asked for the best practice -- the answer is dependencyManagement. I just don't see any reason to use versions defined in properties like this when you can easily use depMgmt. Anyway, you could define your property in the top parent and then all the children should inherit it. Or simply

Re: How to globally set version of dependencies used commonly in child poms

Wayne Fay wrote: You asked for the best practice -- the answer is dependencyManagement. I just don't see any reason to use versions defined in properties like this when you can easily use depMgmt. Sorry for asking the question incorrectly. I guess the question is: What is the best practive

Re: webdav

I guess that isn't possible for deploy:deploy-file ? On 8/20/07, Eric Redmond [EMAIL PROTECTED] wrote: You have to add an extension block in your POM to use webdav. http://maven.apache.org/guides/mini/guide-using-extensions.html -- Eric Redmond http://blog.propellors.net On 8/20/07,

Re: How to globally set version of dependencies used commonly in child poms

Farrukh Najmi wrote: Sorry to ask a basic question on how best to set a property in top parent. If I set in in top parent's profiles.xml would it be inherited by child poms? Thanks again for your terrific help. According to: http://maven.apache.org/pom.html#Properties The way to specify

Re: How to globally set version of dependencies used commonly in child poms

The purpose of depMgmt is to set the dep versions in one place (the top parent for a given project) and then where you need the dep, you simply state the groupId, artifactId, and optionally scope and classifier. So you shouldn't have depMgmt in children poms. For best use (IMO), depMgmt should be

Re: webdav

On 8/20/07, Tom Huybrechts [EMAIL PROTECTED] wrote: I guess that isn't possible for deploy:deploy-file ? If there is a pom.xml file in the directory where you execute 'mvn deploy:deploy-file ..' Maven will pick it up (or you can use -f to point at a different one.) This is separate from the

Re: How to globally set version of dependencies used commonly in child poms

Hi Wayne, I thought I understood dependency management but now I am not too sure. As I understood your suggestion, if I define a dependency with a version in top level pom then if child pom specifies the same project as a dependency without a version then maven will use the version specified

Re: How to globally set version of dependencies used commonly in child poms

This is what I thought. You are simply using dependencies, not dependencyManagement... depMgmt is a completely separate xml node in the pom.xml file. http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html Wayne On 8/20/07, Farrukh Najmi [EMAIL PROTECTED] wrote:

Re: problem w/ remote deploy - Host key verification failed

OK, I seem to have found the problem - use of unqualified hostname in .ssh/known_hosts and fully-qualified name in the distributionManagement of POM. Contrary to other reports, I did not find that I needed to specify the username in a server section of the settings.xml -- john John

Re: problem w/ remote deploy - Host key verification failed

OK, I seem to have found the problem - use of unqualified hostname in .ssh/known_hosts and fully-qualified name in the distributionManagement of POM. Contrary to other reports, I did not find that I needed to specify the username in a server section of the settings.xml -- john John

Re: problem w/ remote deploy - Host key verification failed

OK, I seem to have found the problem - use of unqualified hostname in .ssh/known_hosts and fully-qualified name in the distributionManagement of POM. Contrary to other reports, I did not find that I needed to specify the username in a server section of the settings.xml -- john John

Re: problem w/ remote deploy - Host key verification failed

OK, I seem to have found the problem - use of unqualified hostname in .ssh/known_hosts and fully-qualified name in the distributionManagement of POM. Contrary to other reports, I did not find that I needed to specify the username in a server section of the settings.xml -- john John

Re: How to globally set version of dependencies used commonly in child poms

Thank you Wayne! I had completely missed this subtle but important distinction between dependencies and dependencyManagement.. So I tried this out. It seems to work but not for dependencies that are plugin dependencies in child poms. In my parent pom I specified dependencyManagement

Can Classpath sequence be controlled in JAR:JAR manifest generation?

Folks, 1) I am working with a set of 3Ps from BEA that unfortunately require sequencing (wlclient.jar must come before weblogic.jar). I know that's a whole heated issue right there, and of course, I know that is extremely bad practice to require that. However, that's what I'm stuck with for

Re: How to globally set version of dependencies used commonly in child poms

Farrukh, I think you'll require using the pluginManagement tag in the parent pom to achieve the same behaviour for plugins. Farhan. On 8/20/07, Farrukh Najmi [EMAIL PROTECTED] wrote: Thank you Wayne! I had completely missed this subtle but important distinction between dependencies and

Re: How to globally set version of dependencies used commonly in child poms

You also need to look at pluginManagement for the same effect for plugins. http://maven.apache.org/pom.html#Plugin%20Management -Matthew McCullough Ambient Ideas, LLC [EMAIL PROTECTED] Farrukh Najmi-2 wrote: Thank you Wayne! I had completely missed this subtle but important distinction

Re: How to globally set version of dependencies used commonly in child poms

Farrukh Najmi wrote: Thank you Wayne! I had completely missed this subtle but important distinction between dependencies and dependencyManagement.. So I tried this out. It seems to work but not for dependencies that are plugin dependencies in child poms. In my parent pom I specified

where to get xmldsig-1.0.jar

Hi, I'm trying to build an existing spring framework applictaion. It's trying to download xmldsig-1.0.jar from here http://download.java.net/maven/1//javax.xml.crypto/jars/ xmldsig-1.0.jar and here http://repo1.maven.org/maven2/javax/xml/crypto/xmldsig/1.0/ xmldsig-1.0.jar The jar is

(Simple) POM in YAML

Write a POM in 1/3 the lines with YAML. Not suggested for beginners - this is just a fun experiment. http://blog.propellors.net/2007/08/maven-less-ugly.html I wouldn't normally condone replacing your pom.xml with pom.yml files - but it's a simple way to get moving fast - which I always condone

Re: where to get xmldsig-1.0.jar

Jacques Couzteau wrote: Hi, I'm trying to build an existing spring framework applictaion. It's trying to download xmldsig-1.0.jar from here http://download.java.net/maven/1//javax.xml.crypto/jars/xmldsig-1.0.jar and here

Re: How to globally set version of dependencies used commonly in child poms

Ultimately, you're still using this property substitution thing, which I think is screwing things up. Please try it with properly declared versions in the depMgmt section. If that works, then you know you're simply having troubles with the property substitution. If it doesn't work, then you've

Re: Maven and macker plugin working??[UPDATES]

Jeremy et al, I just checked in the first rough draft of macker-maven-plugin v1.0.0-SNAPSHOT into Mojo sandbox. Please grab the source, mvn -U install site, take a look at the site docs to figure out how to use/configure it, and give it a try. You can use mvn macker:macker package to test it on

Re: where to get xmldsig-1.0.jar

Farrukh Najmi wrote: Jacques Couzteau wrote: Hi, I'm trying to build an existing spring framework applictaion. It's trying to download xmldsig-1.0.jar from here http://download.java.net/maven/1//javax.xml.crypto/jars/xmldsig-1.0.jar and here

javadoc error from 2.0.4 to 2.0.6/2.0.7

I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO] [ERROR] FATAL ERROR [INFO]

Re: where to get xmldsig-1.0.jar

Great! Thanks Farrukh. -j On 20.08.2007, at 21:04, Farrukh Najmi wrote: Farrukh Najmi wrote: Jacques Couzteau wrote: Hi, I'm trying to build an existing spring framework applictaion. It's trying to download xmldsig-1.0.jar from here

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

What JDK and what OS? Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has anyone seen this error before? Thanks. LJ [INFO] [javadoc:javadoc] [INFO]

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Hi Wayne, It is jdk1.4 on AIX. Thanks. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: What JDK and what OS? Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote: I run mvn javadoc:javadoc with 2.0.6 and 2.0.7, both give me the following error. It works fine if I use 2.0.4. Has

Maven 2 Classpath

Is it possible to set the order of the JAR's added to the classpath of a Maven project? If yes, how is this is done? Thank you. This message (including any attachments) contains confidential information intended for a specific individual and purpose, and is protected by law. If you are not

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

It seems like the newer versions of javadoc plugin are trying to parse version information out of your javadoc tool, and your tool is responding with fewer string tokens than is expected, resulting in the error below. I strongly doubt the Maven team tests on AIX much less with jdk4 on AIX, so it

Re: Maven 2 Classpath

This is not an uncommon question. The answer is no. Wayne On 8/20/07, Morgovsky, Alexander (US - Glen Mills) [EMAIL PROTECTED] wrote: Is it possible to set the order of the JAR's added to the classpath of a Maven project? If yes, how is this is done? Thank you. This message (including

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Thanks Wayne, Looks like the maven-javadoc-plugin 2.2 works with my maven 2.0.6 on AIX but 2.3 does not. I run the following, and it works. /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.0-beta-2:javadoc But if I run the following, it gives me the

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Correction, I ran /usr/bin/maven-2.0.6/bin/mvn org.apache.maven.plugins:maven-javadoc-plugin:2.2:javadoc, not maven-javadoc-plugin:2.0-beta-2. On 8/20/07, L. J. [EMAIL PROTECTED] wrote: Thanks Wayne, Looks like the maven-javadoc-plugin 2.2 works with my maven 2.0.6 on AIX but 2.3 does not.

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

You can try locking the version to 2.2 with [2.2] in the version tag. But ideally, you'd file the bug and help fix the issue. ;-) Eventually you will need a feature of javadoc-2.4 or 2.5 and it will still have this bug since it was never dealt with. Wayne On 8/20/07, L. J. [EMAIL PROTECTED]

Re: Can Classpath sequence be controlled in JAR:JAR manifest generation?

As far as I know, this is not possible. Your only option is to write your own MANIFEST.MF file (with the proper order) and provide it to Maven rather than asking Maven to generate one for you. Wayne On 8/20/07, programr [EMAIL PROTECTED] wrote: Folks, 1) I am working with a set of 3Ps from

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Thanks. issue/bug is filed. LJ On 8/20/07, Wayne Fay [EMAIL PROTECTED] wrote: You can try locking the version to 2.2 with [2.2] in the version tag. But ideally, you'd file the bug and help fix the issue. ;-) Eventually you will need a feature of javadoc-2.4 or 2.5 and it will still have

RE: Upgrade Strategy from 1.1-beta-1 to 1.1-beta-2

Hi, Actually, data-management tools doesn't really work as expected. This could be a real improvment for next versions. But you can have a look at the brett's notes [1]. -- Olivier [1] http://www.nabble.com/brief-notes%3A-upgrading-1.1-beta-1-to-1.1-beta-2-tf4283770.html -Message

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

L. J. schrieb: However, even I put the maven-javadoc-plugin version number 2.2 in the pom.xml as below, maven 2.0.6 still uses 2.3. groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.2/version What would be the best way/workaround, any suggestion? Using

Re: usefullness of the maven-eclipse-plugin

maarten roosendaal wrote: I was wondering what the use is of the eclipse plugin and mostly when it is usefull. I know it generates files for Eclipse but why /when would you it detects if modules are available as eclipse project and sets references instead of dependencies. WTP detection is

Re: usefullness of the maven-eclipse-plugin

m2eclipse, AFAIK, doesn't support WTP and it's very annoying if your are developing JEE applications. maven-eclipse-plugin does. Arnaud On 20/08/07, Jan Torben Heuer [EMAIL PROTECTED] wrote: maarten roosendaal wrote: I was wondering what the use is of the eclipse plugin and mostly when it

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Using versionx.y.z/version does not necessarily mean you're going to get x.y.z. If you absolutely must only get version 2.2, and nothing newer/older is acceptable, then you should use [2.2] to lock down the version. Wayne On 8/20/07, Michael Meyer [EMAIL PROTECTED] wrote: L. J. schrieb:

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Ok, I try to lock it down, but it give me the error as below: [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-javadoc-plugin Version: [2.2] Reason: Unable to download the artifact from any repository

Re: javadoc error from 2.0.4 to 2.0.6/2.0.7

Using [2.2] requires that 2.2 is a valid version. Check Central and see, I'm not sure off the top of my head. You said 2.3 and 2.2 before in this thread, so I assume they both exist. If not, you also said something about 2.0-beta-2, so try that. Wayne On 8/20/07, L. J. [EMAIL PROTECTED] wrote:

artifactory - maintaining a public-repo cache

Dear All, I have setup a maven public repository cache so as to maintain the artifacts used commonly (within the organization) and hence not require a download everytime from a maven public repository and btw i am using Artifactory as the Repository Manager. So in order to achieve the above i

Re: artifactory - maintaining a public-repo cache

You need to make Artifactory either a mirror or a replacement for the repo1 central repository by following a simple Maven configuration. See: http://www.jfrog.org/sites/artifactory/latest/maven.html mfs wrote: Dear All, I have setup a maven public repository cache so as to maintain the

Re: artifactory - maintaining a public-repo cache

Hi Yoav, Thanks for the quick follow..so basically among the two approaches suggested, the first is the one i have opted, and have defined the maven-public-repository-cache in the parent pom as it states (instead of settings.xml)..or am i still missing something.. Farhan. On 8/20/07, Yoav

Re: artifactory - maintaining a public-repo cache

The repository id must be central to override repo1 (for releases, or snapshots to override it for snapshots). If you wish to use a different id, then you have to use mirroring in settings.xml. HTH mfs wrote: Hi Yoav, Thanks for the quick follow..so basically among the two approaches

  1   2   >