Hi all,
Can I get some testers out there to retry this functionality using a
fresh build from:
http://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/
It should be fixed now.
Thanks,
John
Jens Zastrow wrote:
In Maven 2.0 the value containes the whole absolute path to the ta
Sorry, for those who don't have it, the URL for this issue is:
http://jira.codehaus.org/browse/MNG-1927
Thanks,
John
John Casey wrote:
Hi all,
Can I get some testers out there to retry this functionality using a
fresh build from:
http://svn.apache.org/repos/asf/maven/components/bra
Sorry to top-reply, but I'd like to address the original question. Maven
2.0.1 and later should support OS-shell environment variable references
from settings.xml and pom.xml using the following syntax:
If you would use "echo $HOME" in your shell script, you would use
${env.HOME} in your pom.x
There are two requirements for versioning in this case:
1. The parent POM has to have a valid element (no expressions
here).
2. Each child POM must specify a element that refers to the
parent POM explicitly, including the version declared in the parent POM
(again, no expressions here).
O
if you're talking about m2, then it's simple enough (I'm assuming you're
working on the plugin, not using it?):
for each parameter you want to provide command-line support, make it
look like this:
/**
* @parameter expression="${param}" ...
* ...
*/
private String param;
The 'expression="$
Well, looking at the jar plugin, it seems that it doesn't allow
inclusions/exclusions to be specified.
I guess my question is, what are you trying to accomplish? Are these
classes unit tests or something?
-john
Karthik V wrote:
there seems to be one (
http://maven.apache.org/plugins/maven-c
You probably want to update your maven version, not the plugin
version... DiagnosisUtils is in the core.
We have an RC of 2.0.2 which will most likely be promoted to the final
release, if you'd like to use that.
It's at:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-200
Hmm, sounds a little hackish, but you might try using the expression
${jlinks} instead, as model (and project) properties are consulted for
parameter injection when other things fall through.
HTH,
john
Michael Böckling wrote:
Hi,
this is the last one for today, I hope. :-)
I wonder, now th
One other note: if your mojos live within the same plugin, you can use:
AbstractMojo.getContext(): Map
to pass context information. It's a little cleaner for intra-plugin
communications.
-j
Michael Böckling wrote:
Hi,
this is the last one for today, I hope. :-)
I wonder, now that I have a
You've bound the configuration of the antrun plugin to an execution,
which is bound to the test lifecycle phase. This is a good thing.
However, you won't be able to use the configuration within an execution
from a direct, command-line invocation like `mvn antrun:run`.
Instead, try running `mv
I *think* you could use a ${project} parameter, which will return an
instance of org.apache.maven.project.MavenProject (artifactId:
maven-project), and then use something like:
MavenProject.setArtifacts(..) or something (the exact API here escapes
me, but a good IDE should help you). You'll ha
This just means that you could create a couple of "orchestration only"
poms, each with a war project and its dependency components specified as
modules...and with a packaging of "pom" which means it'll organize the
submodules (war and components) according to dependencies, and then
build them.
I think you want the tag. See:
http://maven.apache.org/maven-model/maven.html#class_scm
-john
Dave Hoffer wrote:
I am getting a POM parse error when I add the following section.
scm:starteam:X:[EMAIL PROTECTED]:49201/Components/view
Looks like you need to get the latest maven-plugin-plugin version. You
can do this by issuing the following on your plugin project:
mvn -U package
The -U flag will force an update check for the plugin-plugin.
HTH,
john
Guo, Jiaqi wrote:
I used to work on a maven project with several java goa
since that time, so the changelog for Maven 2.0.1 should contain a full
accounting of fixes included in this release of the maven-plugin-plugin.
Enjoy.
John Casey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Not sure what the end goal is here, but I assume you're saying you're
trying to do something like:
some.group.id
some-artifact
1.1.1.1
pom
Other than playing the trick of having that POM's dependencies all
included in the core classloader of Maven, I'm
You could probably use the appxml attribute, like this:
...
maven-ear-plugin
/path/to/META-INF/application.xml
...
-john
[EMAIL PROTECTED] wrote:
Hi ,
I'm getting the following warning when creating the ear file ,
application.xml is not ge
Unfortunately, there seems to be an open TODO in the code for that.
Off the top of my head, I can't imagine how you'd adjust it to work with
the packaging of the project...at least, not easily. If you'd like to
take a look at the source, it's here:
http://svn.apache.org/repos/asf/maven/plugin
When designing Maven 2, we found a need for metadata beyond the POM.
This metadata has to be merged from multiple repositories, so the build
can take the appropriate actions as if there were only one repository.
This leads to a difference between the notion of a local repository
(which really i
hieve this...
Thanks,
Sandeep
-Original Message-----
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Monday, February 06, 2006 4:53 PM
To: Maven Users List
Subject: Re: Using
Not sure what the end goal is here, but I assume you're saying you're
trying
This is probably going to be *a lot* easier for you:
http://maven.apache.org/guides/mini/guide-assemblies.html
Cheers,
John
Stefan Podkowinski wrote:
Hello
Whats the best way to distribute your project if you need to provide
all artifacts incl. dependencies with your release? E.g. if you wan
can you post a copy of your POM?
Jason Chaffee wrote:
If I try to add a dependency of type war to my pom, I get the following
Error (note: I can remove war and it doesn’t fail):
[ERROR] FATAL ERROR
[INFO]
-
---
[
You can run maven in batch mode (-B), which is non-interactive. From
that point, you'd have to specify a few command-line system properties
to push in the answers to the questions it asks...I think it'd bump the
version in the manner you're asking for, but it's going to need some
testing. :)
You should read these:
* http://maven.apache.org/guides/mini/guide-configuring-plugins.html
* http://maven.apache.org/plugins/maven-compiler-plugin/howto.html
That last one contains something like this:
maven-compiler-plugin
1.5
1.5
-john
parent distributionProject pom, I am inheriting the common
dependencies.
Thanks,
Sandeep
-Original Message-
From: John Casey [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 07, 2006 10:48 AM
To: Maven Users List
Subject: Re: Using
In general, Maven follows the Java-ish single
Try:
${build.sourceDirectory}
**/*.properties
...and if you wanted to do the same thing for test-resources, you'd have
an additional section of the form
[]+ in your build section.
-john
Kevin Galligan wrote:
I know that we should use the resourc
ut I really wonder why I have to
setup my own remote repo and - even worse - why everyone else who
likes to work on the sources will have as well, just to keep some
control over artifacts.
On 2/7/06, John Casey <[EMAIL PROTECTED]> wrote:
This is probably going to be *a lot* easier for
try re-installing it with the following command line option:
-DupdateReleaseInfo=true
That will update the RELEASE metadata. It would seem that there should
be a way to specify the archetype-artifact's version, though...
-john
Trent Rosenbaum wrote:
Hi there,
Can anyone offer any thoughts
after making
sure all the files were deleted.
I have gone back to the file maven-metadata-central.xml and this still has
the same information inside it.
The archetype plugin can now use this archetype without any issues, so what
have I updated if it is not this file?
Trent
On 08/02/06, John Casey &l
can you verify that the path:
org/apache/maven/plugins/maven-plugin-parent/2.0/maven-plugin-parent-2.0.pom
exists in your local repository? If not, then -o won't help you. I
suspect it's a problem with traffic on ibiblio, but I dunno for sure. I
can reach the URL given in that trace below..
actually, that's where offline mode is helpful. Of course, if you don't
have all the artifacts/poms cached in your local repository, it won't do
you much good...
-john
Joern Huxhorn wrote:
[EMAIL PROTECTED] wrote:
Maven is not working anymore, I was trying to add a regular Manifest
fil into
if you've setup this repository within a profile in your settings.xml,
is that profile in the list of in that settings.xml
config? I'm not sure whether this profile will ever be applied if there
isn't a project to apply it to...
Can you verify that you have activated that profile, and that it
Maybe I'm missing something, but why not simply leave off the child-POM
version element? It will inherit the one specified in the parent
section. If the parent POM doesn't exist in the repository, you could
always use the element in the parent section to specify
where the parent POM is relativ
Where is this active profile defined? I think you can mark it as
true, and when any other profile is
activated this one will be deactivated...
That may be too simplistic...
-j
dan tran wrote:
Can i deactivate an active profile?
I have a default profile,.. but when a condition met, I would l
um,
someartifact
...
you might have a look at
http://maven.apache.org/guides/getting-started/index.html
-john
Martin Gainty wrote:
Good Morning All-
Stupid question but I have to ask
where are the POM attributes set?
more specifically how and where is the pom.artifactId set?
Thanks,
M
ebug;
inside your native plugin...
-john
dan tran wrote:
the profile is in the pom. I need to create a profile for
native-maven-plugin.
where by default it builds nondebug artifact. When user passed in -Ddebug,
the need to activate the configururation that has debug flags.
-Dan
On 2/
We are pleased to announce the 2.1 release of the maven-clean-plugin for
Maven 2.x.
This release includes:
* Support for following symbolic links (or NOT following them)
To follow symbolic links when running the clean mojo, use:
true
* Support for additional file-sets mar
We are pleased to announce the 1.0 release of the file-management
utility library.
GroupId: org.apache.maven.shared
ArtifactId: file-management
Version: 1.0
This library provides simple functions surrounding file-sets, including:
* Model for defining FileSet instances
* Included/Excluded file s
difference
between the below and the FileSet classes in Ant?
On 2/20/06, John Casey <[EMAIL PROTECTED]> wrote:
We are pleased to announce the 1.0 release of the file-management
utility library.
GroupId: org.apache.maven.shared
ArtifactId: file-management
Version: 1.0
This library provides
BTW, I'm working on publishing the javadocs, etc. for this
project...I'll follow up when I get it done.
-j
Dion Gillard wrote:
Given no URLs to read in the announcement, what is the difference
between the below and the FileSet classes in Ant?
On 2/20/06, John Casey <[EMAIL PROT
Inside your task, you'll need to use
getProject().getReference("org.apache.maven.project.MavenProjectHelper")
IIRC.
If that doesn't work, let me know, and I'll dig around in the code.
-john
Martin van der Plas wrote:
Hi,
According to
http://maven.apache.org/guides/plugin/guide-ant-plugin-de
Can you re-run it with the '-e' option? This should output a stack trace
that you can paste here...it'll make debugging a bit easier.
-john
jdoody wrote:
I'm trying to create a maven project structure using the mvn archetype:create
command. Following is a section of the command output:
[INF
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi, Chris. :)
Comments inline.
Chris Berry wrote:
| Greetings,
| I have found that one could easily produce a generic build system in m1
| using the import statement from jelly:core inside of the maven.xml
file. I.e
| .
|
|
|
| where the file; myb
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The general pattern we've adopted with Maven 2.0 is that of binding your
custom behavior to the appropriate place in an absolute lifecycle,
rather than relative to some other plugin's execution. The problem with
specifying a pre/postGoal is that the r
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try adding the class-level annotation:
@aggregator
to your mojo. This will tell the mojo to only execute at the top level.
If you need access to the List of project instances in the current
build, use the following:
/**
~ * @parameter default-value
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
One point of confusion which comes from our development approach up to
recently is the release cycle for plugins vs. that of the core. Going
forward, plugins will each have their own release cycle, which is not
meshed (except roughly) with releas
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Then eclipse plugin handles source downloads natively now. Source
artifacts are attached to any release deployment by default, IIRC, and
they are stored alongside the main artifact in the repository. So,
adding source downloads to your eclipse pl
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Local repository is an environment-specific setting, and is only
specified two ways: (a) settings.xml, and (b) command-line, via
- -Dmaven.repo.local=/path/to/repo. Putting the local repository in the
POM would break portability for that project. If,
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The part that will be tricky is having a project in the build that
doesn't have anything to deliver in the install process. You'd almost
need to configure the install and deploy plugins within that POM ONLY to
flag them as disabled or something...
Is
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You might want to see the FAQ entry on proxy setup on the Maven website.
You need an entry in ~/.m2/settings.xml to tell what the proxy settings
are...
http://maven.apache.org/guides/mini/guide-proxies.html
HTH,
john
Roberto Castro wrote:
| Hi, Lu
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Basically, the best way to address this (at least so far) is to file a
MEV issue with the fixes for that POM.
http://jira.codehaus.org/browse/MEV
It's going to take awhile to get the repository completely cleaned up,
particularly since it's metadata
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sorry, I'm tracking a little behind on the list. ;)
Just for completeness, I should mention that it *is* possible to write a
plugin which is *not* inherited by default. When this is the case, the
user can still override this by specifying:
true
ins
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The POM is most likely wrong. If you have time, it would be a great help
if you could file a JIRA issue at:
http://jira.codehaus.org/browse/MEV
Please include a list of dependencies you believe to be correct, or as
close as you can get (it'll help u
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What specifically is it trying to retrieve from the server?
- -john
Brian Bonner wrote:
| I have a bundle setup in my local repository. When I try to do a:
|
| mvn -o install
|
| at a location where I don't have internet access, it fails because it
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My initial guess is that since you have set to true, it's not
accessing any remote repositories at all, regardless of whether it's got
a local mirror. Have you tried with the local mirror and offline==false?
What files did you copy over? Did you get
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'd say that the javadoc:jar mojo needs to detect its environment just
as the javadoc:javadoc mojo does. That's a bug IMO.
FWIW,
john
David Jackman wrote:
| Here's what I'd like to do: For our product, we have a number of Maven
| projects, most of
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg Schaible wrote:
|
| Thanks. So there's no possibility to include modules with poms with
other names ... ?
Not currently. If you need it, submit your use case to jira, and we'll
talk about putting it in 2.1 (or 2.0.1, perhaps).
Cheers,
joh
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Oscar Picasso wrote:
| Hi,
|
| With maven 2.0 there is a problem when build a site for a multi-modules
| project.
|
| The individual modules sites are properly build but not the links
between the
| root project and its modules (see
| http://www.mail-a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
"normal" expressions traverse some part of the runtime build model, like
MavenProject, Settings, etc. Component expressions are a special syntax
which causes the expression evaluator to resolve the expression by
looking up the component's role in the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Profiles are a little strange, in that there are two different types.
The profiles specified in the POM are allowed to modify many, many
things, but are specific to that POM. They are also inextricably linked
to that POM, obviously.
The profiles spec
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Not currently. You could patch the maven-artifact/maven-jar-plugin
classes that handle it, if you want... ;)
- -j
Anuerin Diaz wrote:
| hi,
|
| is there a way to exclude the pom.properties and pom.xml files in
| the resulting artifact jar file? i
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
BTW, before you perform an actual release, you can still share these
deployed snapshot artifacts. Maven uses a metadata file in the
repository to maintain a logical pointer for what 1.0-SNAPSHOT actually
refers to on that repository, and when it was l
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
One such failure is normal (yeah, I know it's strange)...but the
bootstrap should continue, and the plugin-plugin will be rebuilt along
with the rest of maven-plugins in the next step. Do you find that this
is not happening?
- -j
Janecek Jan wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
sorry, this message was off my screen when I read your original post. ;)
Nitko2 wrote:
| Please ignore this post, I found a reason for this in "Introduction to
| build profiles".
|
| ---
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I don't think filtering currently handles resolving system properties,
but it's likely there is a jira issue for that already. If not, would
you like to file one? I agree that this is important for filtering.
As for POM values, allowing interpolation
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
you have the dependency scoped as 'test' and you're depending on it in
your main source tree...test scope is only used when compiling the test
source tree, normally in src/test/java...
Aaron Stromas wrote:
| Hi,
|
| I'm new to Maven and Maven 2 (I'm
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you just leave it off, it'll default to compile, which
is the 'normal' level for most project dependencies to use.
Aaron Stromas wrote:
| Thanks. What should it be? I'm a novice...
|
| -a
|
| On 11/11/05, John Casey <[
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
if you're using the actual svn executable from subversion.tigris.org
(not javaSVN) - as it looks like you're doing here? - then you might
want to check out http://svnbook.red-bean.org
Other than that, I'm no SVN expert...I only know *just* enough to
d that environment variables would clash with
| properties, then why not make the environment variables use a different
| syntax than the ${property} syntax?
|
| I'll look to see if there is a JIRA issue related to this topic.
|
| Thanks,
| Richard Allen
|
|
| John Casey wrote:
|
| I don&#x
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
The sandbox got moved out of /components/trunk... :-)
New URL is:
https://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-it-plugin/
HTH,
- -john
Allison, Bob wrote:
| OK. Maybe I'm not checking out the correct maven2 trunk.
|
| The URL I a
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
'clean' is actually a phase in another lifecycle, so binding to
clean should work, I think. Try it and let us know!
If it doesn't work, it probably should.
Cheers,
john
Wim Deblauwe wrote:
| Sorry about that, but looking closer, it seems that clea
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try this:
~
~
~ maven-antrun-plugin
~
~
~ test
~
~
~
~
~
~
~run
~
~
~
~
~
If you want to reference the pr
bc-or-something
~ 1.0
~
~
This should inject the driver artifact into the plugin's classpath.
Good luck,
john
John Casey wrote:
| Try this:
|
|
| ~
| ~
| ~ maven-antrun-plugin
| ~
| ~
| ~
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You're looking for the assembly plugin:
http://maven.apache.org/plugins/maven-assembly-plugin/
That's linked off the main page under the "Available Plugins" section of
the left navigation, btw.
- -j
[EMAIL PROTECTED] wrote:
| are there any maven2 p
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
it's actually still there...lurking. It's on the list to get it all
cleaned up and bug-free for 2.0.1.
They're right about , it should enable usage of this
feature, and the file will be in ~/.m2/plugin-registry.xml.
Cheers,
John
John Tolentino wro
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There are two general things that go in that directory: plugin
descriptors, and POM information.
For the former, we need some way of describing a Maven plugin to the
system, to determine how to startup the plugin and execute it.
For the latter, we w
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
David Sag wrote:
|
| I am writing the unit tests for a simple xml transformer and want to
| know 2 things.
|
| 1) where is the maven2 approved place to put the test xml and xslt
| files? If I put them in src/test/resources then they end up in a jar
|
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You're defining this components.xml in a plugin, right? Do you have
true defined in the plugin reference within
your plugin-user POM? If not, it will use a default artifact handler
that has the same type as your packaging, and the same extension as yo
? I'm not sure whether it's in there
right now or now, so you might do a cursory search first...
Cheers,
John
Julien Stern wrote:
| On Thu, Nov 17, 2005 at 10:39:40AM -0500, John Casey wrote:
|
|>-BEGIN PGP SIGNED MESSAGE-
|>Hash: SHA1
|>
|>There are two general
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
src/main/webapps, IIRC.
You might check out http://maven.apache.org/plugins/maven-war-plugin/
for more information.
- -j
Nathaniel G. Auvil wrote:
| i am having problems trying to create a new web application. I
searched the documentation and fou
;s reading it as there is also a
| LifecycleMapping which is being used correctly.
|
| Are the private member variables supposed to get read set by some
| persistence mechanism from the configuration node ?
|
|
| On 11/17/05, John Casey <[EMAIL PROTECTED]> wrote:
|
| You're defining this comp
You say you defined the snapshot repository (for resolution) in a
profile within the dependent project's POM? How are you activating that
profile? Is there a reason you're not defining the repository directly
in the POM itself? Anything that can be defined in a profile can also be
defined in th
At times, there are heavy loads on the ibiblio repository that prevent
Maven from downloading the metadata it requires to determine plugin
versions (not to mention artifacts themselves). The best thing I can
tell you right now is to either configure a mirror of the repository in
your settings.x
The Apache Maven team is proud to announce the release of Maven 2.0.1.
Maven is a build system that provides software project management and
dependency comprehension. Based on the concept of a project object model
(POM), Maven manages a project's build, reporting and documentation from
a centr
NOTE: This didn't go out as planned because of a technicality in my
From: address. Sorry for the delay...
-j
The Apache Maven team is proud to announce the release of Maven 2.0.1.
Maven is a build system that provides software project management and
dependency comprehension. Based on the conc
Unfortunately, that's a bug which got introduced when adding envar
substitution support for the pom, settings, and profiles.xml. IIRC, it
should only happen when you have an environment variable set that
doesn't contain '=', as in HOME=/path/to/my/home.
At any rate, it's fixed for both version
We already have some default "standards" for generation of code. First,
code should be generated into:
${project.build.directory}/generated-sources/${plugin-prefix}
Correspondingly, generated resources would go in:
${project.build.directory}/generated-resources/${plugin-prefix}
This accommoda
That particular bug should have been fixed in the 2.0.1 release of Maven
(The NPE in the DiagnosisUtils, I mean). The checkstyle plugin fix has
been patched, and I'll apply it within the next day or so, if it hasn't
already been applied. However, unless you've configured a
pluginRepository poin
Dumb question, but you have:
4.0.0 in your POM, right?
See:
jvm 1| org.apache.maven.project.InvalidProjectModelException: Invalid POM
(not v4.0.0 modelVersion)
-john
Actually, an even better thing to do would be to participate in the
design for 2.1. The page for some of this discussion is at:
http://docs.codehaus.org/pages/viewpage.action?pageId=32108
Cheers,
John
Allan Ramirez wrote:
Please file a jira issue for this http://jira.codehaus.org/browse/MNG
Plugin releases are on the way. The surefire plugin was released today,
and we're getting ready to do the ear, checkstyle, javadoc, and eclipse
plugins Real Soon Now.
-john
Andreas Lemke wrote:
Hi,
I'm currently evaluating maven2 for our company since about a week.
My understanding has grown
ext
one on the list, and the fix will be released with 2.0.2.
Sorry for the inconvenience,
John Casey
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
IIRC, it's src/main/webapp, but check:
http://maven.apache.org/plugins/maven-war-plugin/war-mojo.html
for more info.
hth,
john
Law Green-A20134 wrote:
> Thank you, Maria!
>
> Then do you have any suggestions for WebApp site location and script location?
>
> Add one more question, is there m2
Actually, if I remember correctly, this outputDirectory is read-only in
the compiler plugin. This means that you have to change the setting
indirectly, in this case by configuring:
target/classes
See: http://maven.apache.org/maven-model/maven.html
for more information.
HTH,
John
Edwin
It might be timing out...just a guess. Can you reach that URL
consistently from your browser?
-j
Law Green-A20134 wrote:
> Exactly, I am behind NTLM proxy. No idea how to workaround it.
>
> Edwin, I am generating site for maven project.
>
> Regards,
> Green
>
> -Original Message-
> Fro
First of all, thanks for the contribution!
Please file a JIRA issue against the ear plugin if you have not already
done so, and attach that patch. As for the SAR plugin, you should email
the [EMAIL PROTECTED] mailing list to see what kind of interest you
can drum up there. Our first preference
This issue is being tracked as MNG-1851
(http://jira.codehaus.org/browse/MNG-1851), and I think I've got it fixed.
I've deployed a snapshot of the ant tasks with dependencies, here:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/maven-artifact-ant/2.0.2-SNAPSHOT/
Would you mi
ere:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/reporting/maven-reporting-impl/2.0.2-SNAPSHOT/
If all goes well with testing these and nothing else comes up, we'll
probably release 2.0.2 early next week.
Thanks,
John
John Casey wrote:
Hi everyone,
I wanted to ta
Just checking quickly, but is the --offline switch still problematic in
2.0.1? I applied a patch that fixed the missing pom problem (or so I
thought), and this should have made it into the release...I'll need to
look at it again if not.
Thanks,
John
Chris Berry wrote:
Inline. Cheers,
-- Chr
looks like you had a DNS failure...can you open a browser and verify
that you're able to see:
http://repo1.maven.org/maven2/org/apache/maven/
NOTE: It could have been a temporary DNS failure, so retrying might help...
HTH,
John
Reinke, Curtis (C.J.) wrote:
I'll preface this with, "I am a n
1 - 100 of 591 matches
Mail list logo
