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 you:
http://maven.apache.org/guides/mini/guide
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
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:
build
extensions
extension
groupIdsome.group.id/groupId
artifactIdsome-artifact/artifactId
version1.1.1.1/version
typepom/type
/extension
/extensions
/build
I think you want the scm/ 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.
repository
connection
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
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
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
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.
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
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
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 (
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:
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/branches
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
There are two requirements for versioning in this case:
1. The parent POM has to have a valid version/ element (no expressions
here).
2. Each child POM must specify a parent/ element that refers to the
parent POM explicitly, including the version declared in the parent POM
(again, no
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,
--
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
The Apache Maven team is pleased to announce the 2.1 release of the RAR
plugin for Maven 2. This plugin release fixes a few critical bugs that
were previously blocking usage.
Bugs fixed:
o MNG-1681: Maven-rar-plugin cannot install generated rar file to the
local repository
o MNG-1296: does
The Apache Maven team is pleased to announce the 2.0-beta-3 release of
the Javadoc plugin for Maven 2. This is primarily a bugfix release,
addressing the following issues:
o MNG-1257: does not work on war projects
o MNG-1464: executes for non-java projects
o MNG-1510: site-embedded report
The Apache Maven team is pleased to announce the 2.1 release of the EAR
plugin for Maven 2. This release includes a number of bugfixes, along
with some new features and improvements.
Specifically, it includes the following:
Bug Fixes
o MNG-1296: does not check optional
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
://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 take a second
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:
build
outputDirectorytarget/classes/outputDirectory
/build
See: http://maven.apache.org/maven-model/maven.html
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-
From: John
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
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
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
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
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
Dumb question, but you have:
modelVersion4.0.0/modelVersion 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
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
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
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
-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
-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
extensionstrue/extensions 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
? 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 things that go in that directory
-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
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 components.xml in a plugin, right? Do you have
-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
-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 usePluginRegistry/, it should enable usage of this
feature, and the file will be in ~/.m2/plugin-registry.xml.
Cheers,
John
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
'clean' is actually a phase in another lifecycle, so binding to
phaseclean/phase 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Try this:
build
~ plugins
~plugin
~ artifactIdmaven-antrun-plugin/artifactId
~ executions
~execution
~ phasetest/phase
~ configuration
~tasks
~sql
~dependency
~ groupIddont.know.the.groupId/groupId
~ artifactIdojdbc-or-something/artifactId
~ version1.0/version
~/dependency
~ /dependencies
/plugin
This should inject the driver artifact into the plugin's classpath.
Good luck,
john
John Casey wrote:
| Try this:
|
| build
-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
-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
-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
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
-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 scopecompile/scope, 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 [EMAIL PROTECTED
-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
} syntax?
|
| I'll look to see if there is a JIRA issue related to this topic.
|
| Thanks,
| Richard Allen
|
|
| John Casey wrote:
|
| 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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jörg Schaible wrote:
snip/
|
| 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).
-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
|
-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
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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
My initial guess is that since you have offline/ 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?
-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
-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
-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:
-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
-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...
-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
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
| .
|
| j:import inherit='true'
-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
-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
-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
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Are you sure that the child pom.xml files declare a parent of the
top-level pom? You should refer to the parent pom by groupId,
artifactId, and version. Maven will automatically search for ../pom.xml
if you only build a child project, or you have the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You should be able to specify a profile in a pom and NOT have to use
activeProfiles/ in the settings.xml - that section is only for
profiles defined in the settings file.
Since you have activeByDefault specified, you should be able to run the
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
you're certain that there isn't a file alongside the jar named something
similar to:
artifactId-version.pom
If that's missing, there's a problem. 'm2 install' should handle
installing the primary artifact, attached artifacts, and metadata -
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Typically, these kinds of non-code jar resources are kept separately
under src/main/resources, but you can also specify the following:
project
...
~ build
~ ...
~resources
~ resource
~directorysrc/main/java/directory
~
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
We've sort of informally identified this as a need already, and I've
started writing an API that will help with this. Ideally, the user would
be able to issue something like:
m2 projecthelp:supported-parameters -DparameterPattern=project.*
and have
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Sounds like a bug in the maven-eclipse-plugin...can you file a jira at
http://jira.codehaus.org/Browse/MNG and make sure you specify it as
being a problem with the eclipse plugin? It should be in the modules list.
Thanks,
john
Daniel Krisher
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
You might give commons-exec a spin...
- -john
Ashley Williams wrote:
| I'm writing a plugin that needs to call java -jar in the execute
| method. Is there an api I should use as I don't wish to use the java
| Runtime class to do this. I've had a
just had a document that list these (can be
| generated from modello, if needed).
|
| - Brett
|
| On 10/4/05, John Casey [EMAIL PROTECTED] wrote:
|
| We've sort of informally identified this as a need already, and I've
| started writing an API that will help with this. Ideally, the user would
| be able
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
There will actually be one glaring problem with rewriting the SCM URL
during the release process. This plugin is currently only geared for SVN
use, so it expects /trunk/ and so forth...but this is *not* the way it
*should* be...it's more a function
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
If you specify these two dependencies directly in your own dependency
set, and set their scope to provided, it should work.
FYI, DependencyManagement information is only triggered on demand. That
is, the info in the DependencyManagement section will
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Unfortunately, the quality of the repository is somewhat in the hands of
all users. This is especially true when you consider that those of us
who don't use a particular library - whether we are maven devs or not -
will not have the knowledge and/or
| address is left so that all issues raised against that component can
| easily
| find their rightful owner.
|
| All of which is easy from up here in the commentary box!
|
| On 29 Sep 2005, at 15:25, John Casey wrote:
|
| Unfortunately, the quality of the repository is somewhat in the hands of
| all
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I'm unable to replicate this behavior on my local working copy. Can you
try running with the '--no-plugin-registry' to see if this helps? You
may have an older version of the plugin which may have been created with
a faulty plugin-plugin version...
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
one thing that springs to mind is to create an aggregator plugin that
you can bind into the lifecycle, which will call each of these mojos in
order...beyond that, it *may* work to add them in the order you desire
within an execution section under the
the setters, then call
execute.
Does that make sense?
- -john
dohadwala, moiz wrote:
| Thanks, John.
|
| Is there an example of such a plugin in the maven codebase? I need to put
| this together quickly to demo a proof-of-concept project
|
| -Moiz
|
| -Original Message-
| From: John Casey [mailto
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
doesn't look like it, from a quick read of the code. It's not using a
stale source scanner like the compiler plugin is...
HTH,
john
John Fallows wrote:
| When filtering is disabled, are resources and testResources copied
| incrementally?
|
| For
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
I know that many people are keen to have Ant supported as a plugin
language in Maven 2.0. To this end, I'm working on adding native support
for Ant, but I need some feedback on the approach I'm taking for binding
the script into the M2 system.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
this should work now (committed it this afternoon). However, I should
note that in Chris' email he was using model properties (POM-level
properties) to set the version of the POM...to me, this has a bad smell,
since the project version may be
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
try the following:
m2 deploy -DupdateReleaseInfo=true
This will prompt maven to update the release metadata for that artifact,
~ and *should* result in the plugin being found. You might need to remove
the plugin from the plugin-registry.xml...but
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
yeah, good point. since on the mac, tools.jar is available from the
bootclasspath, I guess I can just leave the dep out on osx rather than
trying to redefine the system path for it...good call. I'll fix that
way, and figure out the toolsJar internal
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
What about a plugin that generates those pom files somehow? you'd need a
map of interdependencies, I guess...but rather than instantiating a
bunch of 'ghost' POMs on the fly, a generator plugin could give you
something to put in version control and
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Thanks for the brainwave! MNG-869 is fixed for os x now...
- -john
Ashley Williams wrote:
| Ah Mr Casey, just noticed you're taking a look at the integration test
| failure it0063 again! Don't know if you read my previous post, but I
| did find
...
|
| On 21 Sep 2005, at 18:16, John Casey wrote:
|
| Thanks for the brainwave! MNG-869 is fixed for os x now...
|
| -john
|
| Ashley Williams wrote:
| | Ah Mr Casey, just noticed you're taking a look at the integration
| test
| | failure it0063 again! Don't know if you read my previous post
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Comments are inline. Please bear with me, I think my responses are as
lengthy as your original email! :(
Cheers,
John
Ashley Williams wrote:
| Sincere apologies to the dev team if this email seems like a troll, I
| absolutely don't mean it to be.
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
System vars are accessed implicitly in m2...try:
configuration
~ debug${build.debug}/debug
~ source${build.jdk}/source
~ target${build.jdk}/target
/configuration
Cheers,
john
David Pick wrote:
| Hi,
|
| I have the following section in a parent
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
I've actually done something just like this in the past, in order to
call a Make-based build. IMO, you want to wrap a command line call in a
plugin, to formalize the parameters - required and optional - which
constitutes a valid invocation of that
301 - 400 of 565 matches
Mail list logo
