Hi,
* exclude matches folder name abc. In your old configuration you forced
to skip directory deletion.
2009/8/26 grumpypuppy nantana...@gmail.com
Thank you. It works.
I went back to my configuration, it also works as soon as I took out
excludes tag.
So, just curious, the plugin get
Hi Jörg,
never thought of that, thanks.
Didn't have any problems so far, though.
-Sven
2009/8/26 Jörg Schaible joerg.schai...@gmx.de
Hi Sven,
Sven Preßler wrote:
You might want to take a look at the maven-inherit-plugin:
I use xmlbeans plugin in my maven project. When running mvn
xmlbeans:xmlbeans, it will generate a jar file in target directory. How
can I let my application depend on the xmlbeans generated jar file?
--
View this message in context:
If we're talking about the Codehaus mojo, it should generate source/class
files as well. I suggest you first bind the plugin to the build process by
adding it to the build part of your pom. Most likely it will make things
work, but if not have a look at the configuration details:
This is my pom file. My application should depend on the output jar,
configuration.jar. How can I let my application depends on this jar file?
How can I add the generated classes file on the dependency node?
plugin
groupIdorg.codehaus.mojo/groupId
2009/8/25 Anders Hammar and...@hammar.net:
Ok, so you want to keep the transitive dependencies of a dependency, but
exclude the actual dependency?
Exactly :)
Sorry, I don't understand what your trying to do. You need to explain more
in detail what your doing; possibly your
confusing
OK, that's probably not the way to go. Why not just generate source code
which you use in your project like if you've developed it by hand?
Or, if you absolutely have to have the xmlbeans generated code in a separate
artifact, I suggest you move the xsd (and the plugin configuration) to a
separate
Do you mean I generate the source code to src/main/java directory?
In this way, I add this configuration:
sourceGenerationDirectorysrc/main/java/sourceGenerationDirectory
Anders Hammar wrote:
OK, that's probably not the way to go. Why not just generate source code
which you use in your
Nope, everything that's generated should go in the target dir (I would say
this goes for everything in Maven). This is the default for this plugin.
Best practice is to always go with the default, unless you absolutely need
to change that. If you must change, think twice about that.
/Anders
On
You have to have a main pom having two modules: the first one installs
your configure.jar as an artefact in your local repository. The second one
is the one you've showed, to which you add a dependency to the previous
generated artefact.
Nicolas
Dan/Subir,
thanks for the great plugins. I went with the build-helper and
buildnumber to generate my WiX version number. When I was looking for a
plugin to help, build-helper was not one I had investigate as my vision
was narrow on the single task I had of - remove SNAPSHOT from my version
umm, build-helper can breakup the version into multiple properties and
you can can reassemble it yourself to remove SNAPSHOT
http://mojo.codehaus.org/build-helper-maven-plugin/usage.html
-D
On Wed, Aug 26, 2009 at 7:15 AM, mfr...@fftw.com wrote:
Dan/Subir,
thanks for the great plugins. I
2009/8/25 Alexander the.malk...@gmail.com:
Jar file comes from some dependency, right?
Yep, it comes with actual dependency.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Yes, that is what I did. I dropped the qualifier for my version and then
generated a build number by using the subversion revision number. The
buildnumber I mentioned is another plugin from codehaus (that part was not
very clear).
Dan Tran dant...@gmail.com
08/26/2009 10:30 AM
Please
Is there an existing way to dynamically add code to a java class when
creating from an archetype? What I would like to do is have the user pass
me a properties file with entries like
name=String
age=Integer
?=?
And then for the MyBean.java class put in the getters and setters for it. I
Hi all,
I get this error when I try to use subArray in the latest Maven builds of
2.8.0 (updated an hour ago),
val arr = Array(2, 3, 4)
arr.subArray(0, 3)
exception when typing line1$object.$iw.$iw.arr().subArray
value subArray is not a member of scala.runtime.BoxedArray in file console
Hello,
I get this every time I do just about anything with my project:
Downloading:
http://repo1.maven.org/maven2/net/sf/gsa-japi/gsa-japi/1.10/gsa-japi-1.10.pom
[INFO] Unable to find resource 'net.sf.gsa-japi:gsa-japi:pom:1.10' in
repository central (http://repo1.maven.org/maven2)
This
Solved.
I re-installed the artifact using -DgeneratePom=true and it no longer
bugs me. Apparently generatePom does *not* default to true when there's
no POM in the repo.
Sorry for wasting everyone's time...
-Chris
On 08/26/2009 03:00 PM, Chris Bredesen wrote:
Hello,
I get this every
Hi,
Maven tells you there is no POM-file. In your ls-command, you also only return
a JAR... Is this a copy-paste error or is the POM really missing?
If you deployed the artifact yourself, add a POM to it. If it came from some
repository, redownload the POM.
Hope this helps!
On Wednesday 26
Create a minimal POM and deposit it.
On Wed, Aug 26, 2009 at 3:00 PM, Chris Bredesencbrede...@redhat.com wrote:
Hello,
I get this every time I do just about anything with my project:
Downloading:
http://repo1.maven.org/maven2/net/sf/gsa-japi/gsa-japi/1.10/gsa-japi-1.10.pom
[INFO] Unable to
Sorry, didn't read until the end...
Create your own POM for this artifact. Either deploy it in a
company-repository (deploy:deploy-file) or if you're a single user in your
local repo (install:install-file).
Just look at the documentation for the respective plugin (install or deploy)
on how to
caner kaplica wrote:
Hi,
I want to get the issues related with only the current version without any
filtering.But when i try onlyCurrentVersiontrue/onlyCurrentVersion,i get
no results.When i use fixVersionID21312/fixVersionId (lets say 21312 is
the current version),it works.The version value
I'm new to Maven, and I am struggling to figure out how to get it to do
packaging in accordance with the standards at my work place. Suppose I have
an ejb called project-ejb, that depends on a library called caf-3.1.0.jar.
How do I setup my project to package this dependency at the ear level
Hello,
I guess this is very elementary question, here it is.
I have two projects, Project A (war type) and Project B (jar type). Project
A is dependent on Project B. So, in Project A's pom.xml I mention Project B
as dependent. Now, Project B has just pom.xml and has no jar file generated.
How
I'm trying to set up a script to handle an automated release process.
I'm using the releaseVersion and developmentVersion properties to
give me some flexibility with respect to the assigned versions.
However, they don't seem to be sticking.
For instance, my current version is 0.9.27-SNAPSHOT.
Should I specify it as a dependency of the ear with a scope of compile, and
then also specify it as a dependency of the ejb with a scope of provided?
This is what I have done in past EJB-packaged-inside-WAR projects with
Maven. It is possible there is a newer/better best practice today, as
I
Unfortunately you have encountered Maven's achilles heel (It's
fantastic at nearly everything else). Managing ejb/ear dependencies is
still basically a manual process.
In general, what I do is:
introduce a pom project that lists all the dependencies that you
expect to be placed in
If I keep the default value, how can I let my project depends on the
generated source code or jar file?
Anders Hammar wrote:
Nope, everything that's generated should go in the target dir (I would say
this goes for everything in Maven). This is the default for this plugin.
Best practice is
How can I create the first module? Do you mean I run the command mvn
install on the configure.jar file?
If so, every time the xsd file changed, I have to install the cnofigure.jar
file manually.
Nicolas Duminil wrote:
You have to have a main pom having two modules: the first one installs
I have two projects, Project A (war type) and Project B (jar type). Project
A is dependent on Project B. So, in Project A's pom.xml I mention Project B
as dependent. Now, Project B has just pom.xml and has no jar file generated.
How could I run Project B's pom.xml from Project A's pom.xml, so
if the schema changes.. the encompassing wsdl would change
the service classes would need to be re'gened
an example of schema encompassed in a wsdl:
ping-modified.wsdl contents:
types
s:schema
s:import
namespace=http://xmlsoap.org/Ping;
Read the part about multi-module non-interactive releases:
http://maven.apache.org/plugins/maven-release-plugin/examples/non-interactive-release.html.
I have not tried overriding versions, but I do most of my multi-module
release in batch mode. I always specify autoVersionSubmodules=true (in
the
I had already gone through that page. It was just not real clear to me
if one must really specify the version for each module in a multi-module
batch build. At your suggestion, I added autoVersionSubmodules to my
command line, but that didn't have any noticeable effect on the result.
The new
I'd rather suggest the newer book Maven: The definitive Guide by Sonatype.
Better and newer...
And yes, it's free. You can find it here:
http://www.sonatype.com/documentation/books
/Anders
On Thu, Aug 27, 2009 at 03:29, Wayne Fay wayne...@gmail.com wrote:
I have two projects, Project A (war
34 matches
Mail list logo
