Hello,
I know that profiles get discussed here all the time, but I just wanted to
confirm that the feature I want really doesn't exist. I want to create two
mutually-exclusive profiles. To build the project successfully, you must
activate one of these profiles. Therefore they should be in the
Ah, thank you. The key is right here:
activation
property
name!jsf/name
/property
/activation
I didn't know you could activate a profile based on an *unset* property. But
that gives me just what I need.
Thanks again,
Paul
--
View this message in context:
Hello,
I hit that error once! It is very confusing, but it means that the resulting
tarball (or whatever) would be empty. In other words, Maven isn't finding
any files to include in the assembly. I guess there is something wrong with
your moduleSet, but I don't know; I haven't used this plugin
Hi Larry,
I'm doing this, too. I think you'll need to create your own assembly
descriptor. Here is mine:
assembly
idbin/id
formats
formattar.gz/format
formatzip/format
/formats
fileSets
fileSet
directorytarget/directory
this in your project?
Larry
On 11/20/06, pjungwir [EMAIL PROTECTED] wrote:
Hi Larry,
I'm doing this, too. I think you'll need to create your own assembly
descriptor. Here is mine:
assembly
idbin/id
formats
formattar.gz/format
formatzip/format
/formats
I'm not positive, but it is probably something like what I've got for
wagon-ftp in one of my projects:
project
...
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ftp/artifactId
version1.0-beta-1/version
Hi Deluigi,
You can solve your second problem by adding this below plugin:
inheritedfalse/inherited
I'm not sure about problem 1.
Paul
Deluigi Marcus wrote:
Hi
I have the following scenario:
I have a project with several modules.
One of the modules starts a container with
Hi Francois,
I'm not sure about the password prompt, but the file permissions problem
looks like another case of this:
http://jira.codehaus.org/browse/MASSEMBLY-153
Paul
Francois Le Fevre wrote:
Dear all,
I am using maven 2 on a linux OS
I want to deploy my project.
I have 2
I think forked lifecycles are often too helpful, like Clippy the Paperclip.
If you can't find a real solution, you could patch the plugin. Give it a new
Mojo that just calls the original, and put different annotations on the new
mojo so it doesn't fork a lifecycle. That seems to be roughly how
Why not limit your plugin to generating the sources, and use the existing
plugins for compiling and packaging? This is likely to be more flexible,
plus it's a lot less work.
If you want different artifactIds for each bundle, you should use a separate
module for each. But you could also put them
I think you have the right approach, but there are two missing bits:
- make sure the assembly plugin doesn't attach its result.
- make sure the last step does attach its result.
An attached file is one that maven considers an artifact and will upload
when you run install/deploy/etc. By
not know what the assembly plugin
produced.
I guess I'm missing something, can you explain perhaps with more detail.
thanks,
Mikko
pjungwir wrote:
I think you have the right approach, but there are two missing bits:
- make sure the assembly plugin doesn't attach its result
Why do you have an asterisk after @parameter? Shouldn't you have a quote mark
after =?
Paul
M Campbell wrote:
I need my plugin to make an arraylist out of the modules in the parent
pom.
I'm creating a List out of them. I'm trying
[EMAIL PROTECTED] expression=${project.modules}
But
Please post the jar plugin section from your pom.
Barbier-Accary Aurélien wrote:
Hello,
I obtain an internal error when I try « mvn package » or « mvn install »
for a « jar » project. The trace is:
[INFO] Internal error in the plugin manager executing goal
If you're installing the artifact every build, you might want to use a
-SNAPSHOT version.
Paul
Arne Saeten wrote:
Hi,
I have the same problem. Any solutions out there?
Thanks,
Arne
-
To unsubscribe,
Hi Joachim,
Some methods on MavenProject are deliberately limited to what you see in the
pom, and others contain computed values. getDependencies() and
getDependencyArtifacts() are the former type. Probably you want
getArtifacts(). That will give you a Set of Artifact objects which should
have
I believe that dependencyManagement does not actually add dependencies. It
just specifies which version should be used if a child adds that dependency.
So instead of using dependencyManagement, perhaps you should try
dependencies.
Paul
Joachim Van der Auwera wrote:
Thanks for the help.
Hi Ste,
I'm not sure how to get a s4j extension. You could rename the file, but then
it wouldn't be an attached artifact, so things like deploy would break.
To get rid of the top-level directory, put this in your assembly descriptor:
includeBaseDirectoryfalse/includeBaseDirectory
Paul
Suppose you say this:
mvn test mvn site
That gives you a failure but not a site. And if you say this:
mvn test; mvn site
you get a site but not a failure.
So what if you wrote a quick plugin that checks for errors in the surefire
reports? Then you could say:
mvn test; mvn site; mvn
Oh, I'm sorry, I thought you were saying that the Class-Path entry in the
manifest couldn't refer to non-jar items. It's very easy to set the
Class-Path entry using either the jar plugin or the assembly plugin. In the
configuration section, specify an archive element. The jar plugin has
pretty
Are you writing a plugin? In that case, declare a parameter of type
org.apache.maven.project.MavenProject and give it these javadoc annotations:
@parameter default-value=${project}
@required
@readonly
You can call methods as shown here:
I don't understand. 2.2 is the plugin version, not the maven version, right?
That appears to be released. For me, it's what maven just uses; I didn't do
anything special.
Paul
Syvalta wrote:
pjungwir wrote:
Syvalta wrote:
But that doesn't work for me, see:
http
/06, pjungwir [EMAIL PROTECTED] wrote:
Hi Jeff,
What is the benefit of loading wagon-ftp in a profile? That extensions
block doesn't per se do anything; it just makes wagon-ftp available. I
guess
you're loading it for the sake of the sftp:// repository in the top-level
POM? Then why not just
Hello,
@execute means that when the mojo is run, it should spawn a separate
lifecycle and run everything up to the given phase before running itself.
It's useful for running a mojo from the command line like mvn plugin:mojo,
but it's problematic when you want to bind the mojo to a phase.
In
Hi Mohan,
There is an integration-test phase that comes after package. But if you
really want to test inside a container, you probably want to use a
continuous-build system, unless you tell maven to deploy to the app server
during package.
Paul
Mohan Gopal wrote:
Hi,
I have been trying to
is filed against windows
Paul
Syvalta wrote:
pjungwir wrote:
I don't understand. 2.2 is the plugin version, not the maven version,
right? That appears to be released. For me, it's what maven just uses; I
didn't do anything special.
Yes, the version of jar-plugin. To my knowledge
Are you sure that documentation wasn't talking about applets? I've run
executable jars with Class-Path manifest entries referencing the filesystem
many times.
Paul
berndq wrote:
SingleShot wrote:
I am building an executable JAR that depends on a handful of other JARs
and a
few config
Someone yesterday mentioned running mvn -o to prevent updating snapshots.
Of course you must already have them, but this will apparently prevent maven
from failing trying to get newer ones.
Paul
--
View this message in context:
classpath. I tried adding this to
the beginning of tasks:
typedef
resource=org/apache/maven/artifact/ant/antlib.xml
uri=urn:maven-artifact-ant
classpath
pathelement
location=/home/pjungwir/maven
Hi Dave,
Is wagon-file even necessary? I used a file-based repository for a while,
and I didn't even mention wagon. I just had a urlfile:////url in my
/project/distributionManagement/repository section. But maybe wagon-file was
used implicitly.
I wonder if the problem is related to windows
Hi Jeff,
What is the benefit of loading wagon-ftp in a profile? That extensions
block doesn't per se do anything; it just makes wagon-ftp available. I guess
you're loading it for the sake of the sftp:// repository in the top-level
POM? Then why not just put extensions up there, too (with no
${basedir} :-)
Technically, this gives the directory where the pom is located, not the
directory from which you run mvn.
Paul
EJ Ciramella-2 wrote:
Is there some property readily available that represents the directory
from which maven was run from?
Something like ${basedir} in ant?
?
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 2:35 PM
To: users@maven.apache.org
Subject: Re: basedir
${basedir} :-)
Technically, this gives the directory where the pom is located, not the
directory from which you run mvn.
Paul
does you pom look like, and what results are you
seeing?
Paul
EJ Ciramella-2 wrote:
Ahh - I'm not talking about having it IN a resource, I'm talking about
having it in the resource mapping in the POM file.
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent
talking about
having it in the resource mapping in the POM file.
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Wednesday, October 25, 2006 3:31 PM
To: users@maven.apache.org
Subject: RE: basedir
Hmm. It works for me in a plain, single-module setup. You may need
I'm not sure how to fix your problem, but if you're really stuck, you could
go back to your build.xml script and call it from maven by using the antrun
plugin with just tasksant antfile=build.xml//tasks. That might be
give you more control over your classpath by letting you handle taskdefing
.
Paul
dan tran wrote:
see if this helps
http://www.nabble.com/M2-antrun-plugin-problem-tf1400135.html#a5892203
-D
On 10/25/06, pjungwir [EMAIL PROTECTED] wrote:
Hello,
This is kind of a weird question. Suppose I'm writing a tasks block for
maven-antrun-plugin. Now suppose I
listed:
[echo] maven.dependency.classpath =
/home/pjungwir/src/ant-test/junit:/home/pjungwir/src/ant-test/jar:/home/pjungwir/src/ant-test/3.8.1:/home/pjungwir/src/ant-test/test
That can't be right. The other four maven.*.classpath refids come out
correct. I looked through MANTRUN on jira
I just noticed that the resources plugin supports an outputDirectory
configuration element. So you could try a relative targetPath and an
absolute outputDirectory. Note that the former is on the resource
itself; the latter, on the plugin's configuration.
Paul
--
View this message in context:
Hello,
Could you please post your MANIFEST.MF file so we can see what royally
screwed up means?
Thanks,
Paul
Alexander Sack-3 wrote:
Hi Everybody,
I did check the email archives on this one and I'm not sure what's what...
If I specify a manifest entry such as:
archive
Syvalta wrote:
But that doesn't work for me, see:
http://jira.codehaus.org/browse/MJAR-60.
I didn't get any error with a trailing slash inside Class-Path. JIRA says
this is fixed against 2.2. I'm not sure why the bug is still open in that
case. . . .
Paul
--
View this message in
Yeah, I wish maven wouldn't wrap the Class-Path entry, too.
I'm pretty new to maven myself, so I haven't tried out multi-module builds
or J2EE builds. But I think you have the right idea. Marking things provided
is the surest way I know to keep transitive dependencies out of your
artifacts.
Hi Jeff,
Could you please post your whole pom, and also the version of maven you're
running?
Thanks,
Paul
Jeff Mutonho wrote:
On 10/23/06, Wayne Fay [EMAIL PROTECTED] wrote:
Fair enough, I hadn't noticed that.
I've only ever used extensions inside a plugin so I figured this
was the
There were a variety of servers out yesterday. This one still isn't
responding.
--
View this message in context:
http://www.nabble.com/cvs.apache.org-connection-problems-tf2499791.html#a6975473
Sent from the Maven - Users mailing list archive at Nabble.com.
I think by default stacktraces do not appear. To see them, you have to add
this to the maven-surefire-plugin section of your pom:
configuration
useFilefalse/useFile
/configuration
Have you done that? If so, then removing it should get you what you want.
Paul
--
View this message in
Hello,
First, the Dojo zip file must be in a maven remote repository somewhere. If
it isn't, you could just put it in private remote repository and point your
project at it using the repositories element. There are lots of docs on
setting up your own repository. It's just a directory structure
Well, this isn't a NoClassDefFoundError, so perhaps we're making progress.
Now java is returning a 1. It would help if you could see stdout, but I'm
not sure how to do that. Perhaps Eclipse is running but complaining about
your arguments. That would make sense, because it looks like you have an
Daniel Serodio-2 wrote:
I'm using the assembly plugin to generate a jar with dependencies, so
the MANIFEST.MF is static (not generated dinamically); how can I add
the scm.revision to such a jar?
When you say static, do you mean that you have a MANIFEST.MF sitting on
your filesystem, and
Hello,
Compile scope doesn't mean compile-time only. In fact, it is the broadest of
maven's scopes. Here is what the scopes mean (as far as I can tell):
compile available when compiling, testing, and running
runtime available when testing and running
provided available when compiling and
Snapshots live in a separate repository. See here for information on
obtaining snapshots:
http://maven.apache.org/guides/development/guide-plugin-snapshot-repositories.html
HTH,
Paul
--
View this message in context:
I think perhaps your post had a typo, because you can't be switching from
wagon-ftp to wagon-ftp. What transport are you using now that's giving you
this error?
Paul
--
View this message in context:
Hello,
I just finished a launch4j plugin. You can find info on it here:
http://9stmaryrd.com/tools/launch4j-maven-plugin/
Paul
--
View this message in context:
http://www.nabble.com/-M2--Ant-based-plugin-and-target-classpath-tf2485665.html#a6960634
Sent from the Maven - Users mailing list
It appears to me from that schema that extensions is also a valid child of
build. This is where I'm using it, and it seems to work fine. Perhaps the
problem is using extensions in a module?
Paul
--
View this message in context:
Yep, I agree. At least it's already filed! :-)
Paul
--
View this message in context:
http://www.nabble.com/-maven2--subversion-revision-in-MANIFEST-file-tf2485250.html#a6961406
Sent from the Maven - Users mailing list archive at Nabble.com.
This refers to the files being tarred?
If so, it's because different versions of tar support long filenames in
different ways. A good explanation is in the Ant user manual, under Core
Tasks : Tar. Because of the frames, I can't give a direct link, but here is
the manual:
Cheers,
Martin
http://el4j.sf.net
-Original Message-
From: pjungwir [mailto:[EMAIL PROTECTED]
Sent: Mittwoch, 18. Oktober 2006 22:46
To: users@maven.apache.org
Subject: Re: ftp-wagon NullPointerException
Ah, there is a beta-1. I tried that, but I still get the same problem
Hello,
The problem appears to be this line:
argumentorg.eclipse.core.launcher.Main -application
org.eclipse.ant.core.antRunner -f
${ECLIPSE_HOME}/plugins/org.eclipse.pde.build_3.2.1.r321_v20060823/scripts/build.xml/argument
That is all one argument, which is not what you intend. Take a look at
You can get the plugin's model class by declaring a property set to
${project.build.plugins}. It will be a Collection of
org.apache.maven.model.Plugin objects. Iterate it until you find your plugin
(using groupId and artifactId). I'm sorry; that's the best way I know in a
mojo to do ${this}. The
Hello,
I'm trying to use ftp-wagon to deploy a plugin to my remote repository, as
described on page 69 of the BBWM book. Here is my POM:
. . .
extensions
extension
groupIdorg.apache.maven.wagon/groupId
artifactIdwagon-ftp/artifactId
I should add that I tried searching around http://maven.apache.org/wagon/,
but almost all the links are 404s.
Paul
--
View this message in context:
http://www.nabble.com/ftp-wagon-NullPointerException-tf2469460.html#a6885299
Sent from the Maven - Users mailing list archive at Nabble.com.
Ah, there is a beta-1. I tried that, but I still get the same problem.
--
View this message in context:
http://www.nabble.com/ftp-wagon-NullPointerException-tf2469460.html#a6885414
Sent from the Maven - Users mailing list archive at Nabble.com.
Hello,
I'm using maven to generate a website for my plugin. I would like the About
page of my site to show a link. The text for this page is based on the
projectdescription element of the POM, so I tried this:
description![CDATA[This plugin creates Windows executables from Java
jar files
Hello,
I am trying to generate some site files using the .apt format. (I'm not
wedded to that format, but I'm starting there since it's the easiest.) I was
hoping to do something like this:
${project.name}
${project.description}
But that doesn't work. The curly braces disappear, but
Hello,
Maven will use known hosts from the user's .ssh directory if available, so
after the first connection these questions won't appear. Please see:
http://www.nabble.com/How-to-prevent-Maven%27s-questions--tf2465228.html
Paul
--
View this message in context:
Hello,
How complicated is your ant script? If it's simple, you might consider
replacing it with a bonafide plugin. That way you should be able to query
the API for modules and only operate on the web ones.
Sorry I don't know an ant-based solution.
Paul
--
View this message in context:
Just a wild guess, but could this be a matter of / vs. \? I see you're
running on windows; maybe java isn't parsing the classpath as you think it
is. When you're sharing a directory with argparser.jar, try -cp
argparser.jar instead of -cp ./argparser.jar.
Paul
--
View this message in context:
I've finished work on the launch4j plugin. Besides the core plugin artifact,
there are four attached artifacts, named with classifiers: one for each
platform that l4j supports. The plugin uses the maven apis to download and
unpack one if necessary.
Here is some more info on the plugin:
I wrote
Hi,
Are you creating your plugin using assembly, or are you running assembly in
the project that uses your plugin?
I doubt you can run a plugin from outside ~/.m2, because maven has to load
the info from somewhere. As long as your plugin has a packaging type of
maven-plugin, it should be
This plugin is online now. Instructions are here:
http://9stmaryrd.com/tools/launch4j-maven-plugin/
The source bundle is here:
http://www.9stmaryrd.com/shared/launch4j/launch4j-maven-plugin-1.0.tar.gz
The maven repository I'm using for now is here:
http://www.9stmaryrd.com/maven
I'd like to
Hello,
Is there an easy way for a plugin to get its own version? I can't just do a
property set to ${project.version}, because that will get the version of the
user's project. So far, the easiest thing I've come up with is to write
${project.version} to a filtered resource file, but that seems
By the way, what are the get/setPluginContext methods on AbstractMojo for?
When I look in the Map, it is empty. Is this a way to pass information to
your plugin from the plugin's pom? Maybe I could use this for what I want.
--
View this message in context:
Hello,
Is it possible for a plugin to tell maven that other plugins must be run
prior to itself? All I see for this is the @execute goal annotation. But
if I do that, how do I pass configuration to that goal? Can I set it up in
the plugin, or does the user have to set it up? Can specify two
Hi Dan, you're coding on a Saturday, too?
dan tran wrote:
use project to browse the user pom which for sure has your plugin.
I was hoping nobody would suggest this! :-) But I'm giving it a try. I get
all the artifacts via project.getPluginArtifacts().
But when I find my own, I can only
pjungwir wrote:
I see that ArtifactVersion (from getSelectedVersion()) has the major/minor
numbers. Do I have to patch these together myself?
Actually, these are all set to zero
--
View this message in context:
http://www.nabble.com/getting-a-plugin%27s-own-version--tf2443270.html
Oh, that is much better! Thank you.
--
View this message in context:
http://www.nabble.com/getting-a-plugin%27s-own-version--tf2443270.html#a6813179
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To
Hello, I'm trying to use xstream 1.1.3 by thoughtworks in my project. It is
here:
http://repo1.maven.org/maven2/com/thoughtworks/xstream/xstream/1.1.3/
I can get the dependency all right, but I get a warning every time I compile
because the pom isn't there:
Downloading:
Hello,
I noticed that when I run my tests, the classpath includes all my
provided-scope dependencies. The docs online don't say they should be there,
but I guess it makes sense, right? Provided scope means I need them to run,
but they'll be available after I deploy. Therefore maven needs to
I rigged up a test. The chart is accurate, but the behavior seems wrong to
me. Could someone please explain why dropping that dependency is the right
thing to do?
Just to repeat, here is the setup:
Project depends on A with test scope.
A depends on B with provided scope.
When I run A's tests,
ir. ing. Jan Dockx wrote:
http://cvs.peopleware.be/training/maven/maven2/buildLifecyclePhases.html
hope this helps.
Thanks. That is the best table I've seen so far. I eventually figured this
out by looking here:
Hello,
I'm writing a plugin, and I would like to accept configuration xml like
this:
someOption
anotherOption
var
var
var
... [more vars] ...
Is this possible without wrapping the var tags inside a container like
vars? In the docs, all the examples have a wrapper tag for lists and
arrays.
I
Hello,
The plugin I'm writing wants some configuration xml like this:
configuration
...
classPath
mainClasscom.whatever.Main/mainClass
cpthis.jar;that.jar/cp
/classPath
...
/configuration
The classPath element is required, and the mainClass element is also
dan tran wrote:
Not that I know of, you will need to validate it your self.
but you can file a JIRA against MNG for this feature enhancement
Hi Dan, thanks for your reply (this one and the many others!). I've been
thinking about filing a jira, and maybe starting on a patch. I think the
Hello,
I'm writing a plugin for the launch4j tool. This tool wraps jar files in
windows executables so you don't have to deal with finding a jre, setting
your classpath, etc. The distribution is a little bit different depending on
whether you're running on linux, windows, solaris, or os x. I
Hello again,
Is it possible to create an artifact that, once retrieved to your local
~/.m2 repository, automatically unarchives itself and becomes a little
directory there?
Thanks,
Paul
--
View this message in context:
dan tran wrote:
sorry it is for maven1.
What the technical difficulty prevent you from having only 1 plugin to
handle all support platforms?
Thank you for pointing me to that other plugin! I just emailed the author. I
did search for such a thing before I started my work, but I didn't
dan tran wrote:
does the build need to stay on the supported platform to build the
executable?
I'm not exactly sure what you're asking. But if your project uses a solaris
launch4j plugin, then you checkout the project on mas os x, building the exe
will fail. I had envisioned people using
dan tran wrote:
I think this plugin is more like a assembly plugin with launch4j
specifics.
am i wrong?
I intend to use it in conjunction with the assembly plugin. I'll generate an
exe file to wrap my jar, then I'll use the assembly plugin to tar up my exe
along with docs, a lib
Hi Dan,
Ask all the questions you like. :-)
Only grabbing the necessary binary bundle is a nice idea. I'll think about
that one. So that means the plugin would have a variable dependency based on
platform. I'm not sure how to do that, but it sounds fun to figure out.
Profiles? I need an excuse
Ah, thanks, that sounds like a good pointer. I'll take a look at the
dependency plugin. I agree, querying java properties is the way to go.
I'm not religious about licenses. :-) If necessary, I can host the plugin
myself.
Paul
--
View this message in context:
dan tran wrote:
You can ping list about their licence policy. But I am sure we allow to
load
GPL artifacts onto maven central. We just never load a bundle before
I don't understand--what is the difference between an artifact and a bundle?
--
View this message in context:
Hello,
I'm developing a plugin in maven 2.0.4. My plugin has a property annotated
like this:
/**
* @parameter default-value=${artifactId}.exe
*/
private File outfile;
When I use the plugin, outfile is set to /home/pjungwir/src/encc/null.exe.
But suppose I use this javadoc instead
dan tran wrote:
inconsistency i guess, I suggest to always start with ${project}
I'm surprised at the implication: different code handles variable
replacement here vs. there.
Inconsistencies like this can be maddening. Could I file this as a jira?
Maybe I'll even supply a patch. :-)
dan tran wrote:
when you are in pom.xml, ${someVar} means a reference of a variable under
root of the pom
Ah, so within the pom, the project. prefix is optional. It looks like it
is also optional when filtering resource files. But not when annotating
plugins. That's still a little
Hi Satish,
Maven expects to find a pom.xml in the current directory. That message means
there isn't one there. I don't know what daytrader is. Are you trying to
build it from source?
Paul
Satish Gupta wrote:
I am just starting to learn Maven. I am trying to follow the instrucations
in
Hmm, I think these directories should already have pom.xml files of their
own. If you copy pom.xmls from other projects, you're probably going to get
errors. I'm not sure about the Cannot find parent error, but perhaps these
foreign poms are the cause?
I agree, the documentation for maven is
Jacek Laskowski-4 wrote:
On 10/9/06, Andr?s [EMAIL PROTECTED] wrote:
I don't know about such a pre-site phase. Indeed, I think there's no
site phase either. Is it a typo, or I'm missing something?.
It's executed right before the 'site' phase. Run 'mvn site' and see
what happens.
I went
Hello,
The Better Builds with Maven book says that you can get any element from the
POM with a property like ${project.foo.bar.baz}. Is there a more general
naming convention for properties used by plugins? I see that the
maven-surefire-plugin has configuration elements with these property
Hello,
I'm sorry for such a noobie question, but what is the reactor? I keep seeing
references to it, but I don't know what it is. Googling just turns up more
references, but no definition. Is this a maven 1 thing? I found this:
Hello,
I tried binding the assembly plugin to the package phase, so it would just
be part of my regular build. Here is what my pom says:
plugin
artifactIdmaven-assembly-plugin/artifactId
executions
execution
Eric Redmond wrote:
Does it run twice in a row? When you run package, Maven will print out
all
of the goals executed, one by one. Can you list them please?
Hi, thanks for replying! Here is what I see:
$ mvn clean package
[INFO] [clean:clean]
[INFO] [resources:resources]
[INFO]
1 - 100 of 104 matches
Mail list logo