Re: Running ANT task before pulling down dependencies

Any reason why you're trying to build your own solution instead of going the Maven way by setting up a corporate repository populated with these artifacts? Not only would it be the right solution, my guess is that it would be so much easier than going against Maven. /Anders On Wed, Dec 2, 2009 at

Running ANT task before pulling down dependencies

Hi, Currently i am trying to get maven project setup which creates a jar artifact. I have setup the project structure. Unfortunately i we don't have the libraries in central repository as per maven layout and jars don't have version numbers. They are jars like product1.jar, product2.jar. These jars

Re: File system repo

> So I guess the question is, how then can you get a jar file, which is not > installed in any repository, onto the compile classpath then into your > ear/war file? You can't, at least, I don't know how to do it. Your original post said that you'd "prefer" not to install them into your repo. Mave

Re: Problem with changes-plugin and announcement-generate

I don't think it is a bug, but rather a configuration issue. Since we cant attach files on the user list, please open an issue in JIRA and attach your pom.xml file there. Sebastian Hoß wrote: > Hey there, > > when trying to run "mvn changes:announcement-generate" I get the > following stack trace

Re: File system repo

Either deploy this file in the "third-party" part of your maven repository manager, or just install it locally. (using deploy:deploy-file or install:install-file, or directly through the mrm artifact upload gui). Btw, the best choice is the first one : set up a mrm and deploy the jar you need. Che

Re: File system repo

So I guess the question is, how then can you get a jar file, which is not installed in any repository, onto the compile classpath then into your ear/war file? Wayne Fay wrote: > >> Hi Wayne.  I have my build working fine, it's just not including the >> system >> scoped jars in my war's WEB-INF/

Re: Can you assign a different name/id to an antrun goal?

Thanks for your suggestions everyone. I decided to go with the shell script approach. Jeff Stephen Connolly-2 wrote: > > unless your profile specifies a defaultGoal of validate and you bind > your execution to the validate phase (hack) > > Sent from my [rhymes with tryPod] ;-) > > On 1

RE: Automating dependencyManagement enforcement

From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of Anders Hammar Sent: Tuesday, December 01, 2009 4:27 AM To: Maven Users List Subject: Re: Automating dependencyManagement enforcement In Maven you can force a specific version to be used by adding square brackets: [1.0

RE: Automating dependencyManagement enforcement

>> Have you checked the possibility of using the enforcer plugin for your use case? It's a point. But really all that adds to this, that I can see, is the ability to fail the build, which is already easy to from within a plugin you're writing. >> This does something close: >> http://maven.apache.

Re: File system repo

> Hi Wayne.  I have my build working fine, it's just not including the system > scoped jars in my war's WEB-INF/lib directory.  It seems the system scope > does not include them.  Any idea how I can get them into the resulting > artifact? This is exactly how system scope is supposed to work -- it

Re: File system repo

Hi Wayne. I have my build working fine, it's just not including the system scoped jars in my war's WEB-INF/lib directory. It seems the system scope does not include them. Any idea how I can get them into the resulting artifact? Thanks, as always Wayne Fay wrote: > >>> System scope is/soon

Re: maven-war-plugin: including jars

Thanks for replying (again) Wayne. You seem to be here all the time. :) Alas, it was an oversight on my part. I had another entry with scope "provided" which was overriding. Thanks again. Wayne Fay wrote: > >> They are set to the default scope, which I believe is "compile".  The >> build >

Plug-in doesn't see configuration

Hi all, I have a project that I am trying to build, but one of the plug-ins can't read its configuration! When I build the project as a single project, everything is fine. This leads me to believe that the POM is actually correct. However, when I build the project as part of the larger group o

Problem with changes-plugin and announcement-generate

Hey there, when trying to run "mvn changes:announcement-generate" I get the following stack trace: [INFO] Creating announcement file from JIRA releases... [INFO] [ERROR] BUILD ERROR [INFO] ---

Re: maven-war-plugin: including jars

> They are set to the default scope, which I believe is "compile".  The build > runs without errors but only one is included in the resulting war.  Is there What does "mvn help:effective-pom" show? There may be a parent pom or depMgmt section that is preventing the axiom-api artifact from landing

Re: How to refer to project's classpath for plugin configuration?

I had not, but I have now, and that doesn't help, either. I've got a similar post on the Liquibase list to see if anyone there can help. Ryan Connolly wrote: > Did you try maven.compile.classpath instead of project.classpath? > > On 12/1/09, David C. Hicks wrote: > >> I'm having a problem with

Re: How do you include classes from a WAR as a dependency?

I just discovered there is a "" element as part of the "" tag. So in my test folder, I made the my webapp's java folder, where the .java files are contained. Is this the conventional way of doing it? That prevents me from having to make a JAR file out of my WAR's classes, but maybe I'm misunde

RE: 403 errors

Thank you very much! I'm working with our networking team on issues we're having and now that we can get past that wget issue we can figure out what the real issue is. Keith Treague Ext.1564 -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: Tuesday, December 01, 200

maven-war-plugin: including jars

I am trying to include several jars into my war file's WEB-INF/lib directory. They are set to the default scope, which I believe is "compile". The build runs without errors but only one is included in the resulting war. Is there something similar to or I should be using? My understanding is

Re: 403 errors

> We're seeing some 403 errors when trying to connect to repo2 at > maven.org. Has anyone seen these issues before? > > wget http://repo2.maven.org/maven2 wget is blocked at Central. I'm not surprised you're getting 403s. Wayne

Re: How to refer to project's classpath for plugin configuration?

Did you try maven.compile.classpath instead of project.classpath? On 12/1/09, David C. Hicks wrote: > I'm having a problem with the Liquibase plugin. A custom change set is > unable to find a classpath resource in target/classes. I think it could > be that the plugin isn't using the correct cla

Re: How do you include classes from a WAR as a dependency?

On Tue, Dec 1, 2009 at 8:10 AM, laredotornado wrote: > I'm using Maven 2.2.  I think I read somewhere that you cannot have a WAR as > a dependency because maven doesn't know how to read the WEB-INF/classes > directory. This isn't Maven related, it's a Java thing. Try compiling code at the comma

How to refer to project's classpath for plugin configuration?

I'm having a problem with the Liquibase plugin. A custom change set is unable to find a classpath resource in target/classes. I think it could be that the plugin isn't using the correct classpath. So, I'd like to configure it by hand. How can I refer to the Maven classpath for the project/modul

How do you include classes from a WAR as a dependency?

Hi, I'm using Maven 2.2. I think I read somewhere that you cannot have a WAR as a dependency because maven doesn't know how to read the WEB-INF/classes directory. I am finding this to be true because I have this dependency in my test project ... myco.galc.capitol.tours myc

403 errors

We're seeing some 403 errors when trying to connect to repo2 at maven.org. Has anyone seen these issues before? wget http://repo2.maven.org/maven2 --09:37:58-- http://repo2.maven.org/maven2 => `maven2' Resolving repo2.maven.org... 38.97.124.18 Connecting to repo2.maven.org|38.97.124.

RE: jaxb2-maven-plugin : Two declarations cause a collision

>I would really like to know what the "offical" jaxb maven plugin really is Official is probably not exact expression, but it is updated often and it is hosted on java.net https://maven-jaxb2-plugin.dev.java.net/docs/guide.html as jaxb is. I've found it much more feature complete then codehause'

Re: Problem running unit tests from maven (JPA related)

Thank you for that, I totally agree. Yesterday I still had some problems because my persistence module has some session beans. All problems where solved when org.apache.openejb javaee-api dependency rather then the javaee javaee-api I used before. thanks again. Stephen Connolly-2 wrote: > > 2

Re: jaxb2-maven-plugin : Two declarations cause a collision

I added a simple xjb and reduced the number of collisions. Regardless of the executions or plugin selected - the work is all done underneath by xjc. Customizing the bindings externally via *.xjb files seems to be the solution. I would really like to know what the "offical" jaxb maven plugin really

RE: jaxb2-maven-plugin : Two declarations cause a collision

Try to run it with standard jaxb xjc tool pointed on "master" ogckml22.xsd https://jaxb.dev.java.net/nonav/2.2-ea/docs/xjc.html If even this does not work, you have to provide collision resolution https://jaxb.dev.java.net/guide/Dealing_with_errors.html#Two_declarations_cause_a_collision_in_the_O

AW: jaxb2-maven-plugin : Two declarations cause a collision

No, i don't think so. In my opinion the problem occurs, because two object factories are generated under the same package. That is obviously not possible, as both factories create different classes but will have the same name. So this is a collision. Try to put the xsd's under different subdirec

Re: Problem with the release:perform

Please retry with -e -X additional options to have more verbose output. Cheers. 2009/11/30 Jouko Johansson > Hi, > > > I tried to execute the release:perform goal. When the execution reaches to > deploy -task segment, there's a error. > > INFO] [ERROR] BUILD ERROR > [INFO] [INFO] >

Re: jaxb2-maven-plugin : Two declarations cause a collision

Could it possibly be that I need to use xjb's to resolve the collision and not plugin configuration? On Tue, Dec 1, 2009 at 11:32 PM, Andrew Hughes wrote: > Thanks Again! > > You are correct, ogckml22.xsd does import atom-author-link.xsd. Initially I > was only running a single for ogckml22.xs

Re: jaxb2-maven-plugin : Two declarations cause a collision

Thanks Again! You are correct, ogckml22.xsd does import atom-author-link.xsd. Initially I was only running a single for ogckml22.xsd. I switched to two because the FAQ said that's how to resolve the collision. I've still got no idea how to f

AW: jaxb2-maven-plugin : Two declarations cause a collision

Hi Andrew, it looks like that ogckml22.xsd File imports the atom-author-link.xsd File. So isn't it sufficient to run the jaxb plugin for ogckml22.xsd only? -Ursprüngliche Nachricht- Von: Andrew Hughes [mailto:ahhug...@gmail.com] Gesendet: Dienstag, 1. Dezember 2009 13:29 An: Maven Use

Re: Archetype plugin and package property as file path

Found it, packageInPathFormat. Wish there was archetype properties guide/doc similar to thisone. Regards, Stevo. On Tue, Dec 1, 2009 at 1:03 PM, Stevo Slavić wrote: > Hello Maven users, > > When generating project from archetype

Re: jaxb2-maven-plugin : Two declarations cause a collision

Hi Entner - THANK YOU for the reply and suggestion. I am still encountering the same problem :'( I'm not sure what to do here because as far as I can tell this should work. I have tried this with and without the packageName (as below): org.codehaus.mojo jaxb2-maven-plugin 1.2 ogckml22 ogckm

Re: Automating dependencyManagement enforcement

In Maven you can force a specific version to be used by adding square brackets: [1.0] By doing so you'll make sure Maven doesn't override your version of choice. However, this will impact projects depending on your artifacts. Normally the version defined closest to the level you're building has pre

Archetype plugin and package property as file path

Hello Maven users, When generating project from archetype in interactive mode user among other things provides package property. It would be handy if there was another property which would be generated from package property by replacing dots in package with directory separator, so that property co

Re: Automating dependencyManagement enforcement

Have you checked the possibility of using the enforcer plugin for your use case? This does something close: http://maven.apache.org/enforcer/enforcer-rules/bannedDependencies.html or you could try creating a custom rule: http://maven.apache.org/enforcer/enforcer-api/writing-a-custom-rule.html A

Re: Managing dependencies which are not in the Reposistory

Ah cool, thanks very much for that. Andy 2009/11/30 Stevo Slavić : > Hereyou > can find instructions on how to setup jasperreports maven repository. > It > seems 3.6.2 hasn't been published there yet, but 3.6.

AW: jaxb2-maven-plugin : Two declarations cause a collision

Hi Andrew, try removing the packageName in the pom.xml file. -Ursprüngliche Nachricht- Von: Andrew Hughes [mailto:ahhug...@gmail.com] Gesendet: Dienstag, 1. Dezember 2009 12:13 An: Maven Users List Betreff: jaxb2-maven-plugin : Two declarations cause a collision Hi All, I am trying to

jaxb2-maven-plugin : Two declarations cause a collision

Hi All, I am trying to generate classes for the Google/OGC KML 2.2 XSD's with the jaxb2-maven-plugin (http://mojo.codehaus.org/jaxb2-maven-plugin/index.html). - http://schemas.opengis.net/kml/2.2.0/ogckml22.xsd - http://schemas.opengis.net/kml/2.2.0/atom-author-link.xsd Both XSD's have an

Automating dependencyManagement enforcement

I'm hoping for advice about the best way to accomplish something in Maven. I am willing to write a plugin if that's the right answer. Here's the thing I want to accomplish: Given a Maven project that builds an ear/war, and which contains a dependencyManagement section, generally inherited