Here's an example from something I am playing with at home. It
generates both the ejb and client jars. I use the two properties at the
top just to simplify the stuff in the ejbdoclet definition:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:sche
To generate both jars, you need to tell the plugin that you want both of
them as follows:
...
...
...
org.apache.maven.plugins
maven-ejb-plugin
true
...
...
...
-Original Message---
You need to specify the "destdir" attribute of the
"deploymentDescriptor" subtask to point it to the correct location.
-Original Message-
From: Stefan Rademacher [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 05, 2006 08:12
To: users@maven.apache.org
Subject: Antw: RE: How can I create
I am trying to configure a plugin with dependencies.
According to the current project descriptor document
(http://maven.apache.org/maven-model/maven.html), I should do the
following:
Anybody have any idea what I am doing wrong?
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Friday, January 06, 2006 06:52
To: Maven Users List
Subject: [m201] Plugin Dependency Configuration
I am trying to configure a plugin with dependencies.
According to the
s.xml
LICENSE.txt
-Original Message-
From: Kees de Kooter [mailto:[EMAIL PROTECTED]
Sent: Monday, January 09, 2006 05:24
To: Maven Users List
Subject: Re: [m201] Plugin Dependency Configuration
On 1/9/06, Allison, Bob <[EMAIL P
Take a look at
http://maven.apache.org/guides/introduction/introduction-to-plugin-prefi
x-mapping.html
-Original Message-
From: Rice Yeh [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 10, 2006 04:29
To: Maven Users List
Subject: Re: unclear explanation in Guide to Developing Java Plugin
Yes. That does work.
For anyone following this thread, using Brett's suggestion involves
duplicating the stanza from the stanza so it is
under ; after copying the XML, remove the
section from the copy in and the
section from the copy in .
-Original Message-
From: Brett Porter [mailt
For an example, let's say you have a Java source at
src/main/java/com/junk/JunkBean.java
For it to compile correctly, it needs to have a "package com.junk;" in
it, right?
When XDoclet walks the source starting at "src/main", it find a source
file that identifies itself as being in package "com.ju
The XDoclet plugin for Maven expects to place the generated sources in
target/generated-sources/xdoclet and adds it to the compile source list.
If you are specifying a different destination, that may be part of the
problem if the plugin is not doing things quite right. Try changing
your output di
A repost from yesterday...
The XDoclet plugin for Maven expects to place the generated sources in
target/generated-sources/xdoclet and adds it to the compile source list.
If you are specifying a different destination, that may be part of the
problem if the plugin is not doing things quite right.
The normal way of handling this kind of dependency tree is to put the
common stuff (each service's interface and DTOs) is a separate project.
Then each service's project depends on this common stuff project.
Make sense?
-Original Message-
From: andrew cooke [mailto:[EMAIL PROTECTED]
Sent
By default (or maybe it is by design) the XDoclet plugin wants it
generated output to go in "target/generated-sources/xdoclet" and it
AUTOMATICALLY adds this path to the source directory list. It is bad
practice to have XDoclet (or any other code generator) place its output
under "src". In NetBea
Can you resolve the host name "repo1.maven.org" on the same machine but
outside of Continuum? This looks like a DNS configuration problem to
me.
-Original Message-
From: Christian Mouttet [mailto:[EMAIL PROTECTED]
Sent: Monday, January 16, 2006 10:45
To: continuum-users@maven.apache.org
No, there is no equivalent in Maven2. I wish there was since some of
the stuff I want to do would greatly benefit from this feature.
What are you trying to do that needs such properties?
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]
Sent: Monday, January 16, 2006
I upgraded to Maven 2.0.2 this morning, and started getting the problem
with the CheckStyle plugin and Jdk14Logger class (MCHECKSTYLE-24), so I
adjusted things to be able to use CheckStyle 2.0-beta-2-SNAPSHOT (added
the snapshot repository, updated the CheckStyle plugin version, etc.).
Now I get a
when I used a local snapshot of the site
plugin. Deleting maven-site-plugin in my local repo so it used the
latest release solved the problem.
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 17, 2006 12:27 PM
To: Maven Users List
Subject: Problem
: Tuesday, January 17, 2006 14:29
To: Maven Users List
Subject: Re: Problem With Maven 2.0.2
i got the same problem and defined a skin in my site.xml like
...
org.apache.maven.skins
maven-stylus-skin
1.0-SNAPSHOT
...
now it works
Allison, Bob wrote:
>I upgraded to Maven 2.0.2 t
said site.xml, not pom.xml.
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 17, 2006 1:47 PM
To: Maven Users List
Subject: RE: Problem With Maven 2.0.2
Since the skin tag does not appear in the documentation yet, where does
it belong? I tried
I am not sure what the problem is, but it is definitely an XDoclet problem, not
a Maven problem. You might get better answers on an XDoclet forum.
-Original Message-
From: Grégory Joseph [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 18, 2006 06:20
To: Maven Users List
Subject: Re:
January 18, 2006 08:14
To: Maven Users List
Subject: Re: Maven2 xdoclet jsptaglib How?
Allison, Bob napisał(a):
> I am not sure what the problem is, but it is definitely an XDoclet problem,
> not a Maven problem. You might get better answers on an XDoclet forum.
I am not sure.
xdoclet-maven-pl
Does anybody know of a means to do unit testing of web servlets which
are coded to the Servlet 2.4 specification and JSPs coded to the JSP 2.0
specification? Cactus doesn't seem to be there yet in any release I
could find and I have been unable to build Cactus in a manner which
would provide this
]
Sent: Monday, February 06, 2006 08:35
To: 'Maven Users List'
Subject: RE: Servlet 2.4/JSP 2.0 Testing
Hi Bob,
> -Original Message-
> From: Allison, Bob [mailto:[EMAIL PROTECTED]
> Sent: lundi 6 février 2006 14:04
> To: Maven Users List
> Subject: OT: Servlet 2.4
I have done the same thing in the past. Continuum does not display the
interpolated values on its web pages but it does end up using them during
operation.
-Original Message-
From: Michael Böckling [mailto:[EMAIL PROTECTED]
Sent: Thursday, February 09, 2006 06:03
To: continuum-users@ma
I have a development tree that looks like this:
toplevel
+-- pom.xml
+-- module1
+-- pom.xml
+-- module2
+-- pom.xml
I would like to make a release of module1. When I do "mvn
release:prepare", the POM is updated with the release version and
committed then I get the error "s
I want to create a web site that looks like this:
index.html
+--parent-1.0/index.html
+--proj1-1.0/index.html
+--proj1-1.1/index.html
+--proj2-1.0/index.html
and so on... Basically, I wanted each version of each project to deploy
its site to a different directory. This also means that SN
le links in the site generated for the parent are
wrong (in parent, the link to proj1 points to
"projects/parent-1.0/proj1/index.html" while the site is in
"projects/proj1-1.0/proj1/index.html").
-----Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: W
Question two also has a problem. If I put the URL in each subproject,
then the links in the web site are wrong because parent points to
"projects/parent-1.0/proj1/index.html" while proj1 is built to
"projects/proj1-1.0/index.html".
-Original Message-----
From: Allison
I believe the answer is that it will not unless the item to be renamed
is the item specified in the mapping. I would say to give it a try and
let me know if it works or doesn't work. If it works, I can add that
information to the docs; if it doesn't work, send me more info on what
you are doing
I am guessing that you need to specify the groupId and artifactId of the
RPM plugin in any project that uses it. I think you can only inherit
the version with the pluginManagement in the parent POM.
Of course, in the case of the RPM plugin, the configuration is likely to
be different for each pro
Bugs like this are one of the reasons the plugin is still alpha.
Although, I have to admit that I did not expect the plugin to get used
like this since I figured each project that wanted to be able to build
an RPM would need an individual configuration; I wasn't expecting anyone
to want to use an i
/etc/xinetd.d
755
../../micro_proxy
micro_proxy.xinetd
On 3/10/06, Allison, Bob <[EMAIL PROTECTED]> wrote:
>
> I believe the answer is that it will not unless the
The links on that page were automatically created from information
inherited from the sandbox parent. I think the sandbox parent was
updated since then to provide the correct links, but I haven't
regenerated the site since then.
I'll try to get this updated.
-Original Message-
From: Edwi
Actually, it is not just the JAR plugin. ALL plugins do this so that
Maven can find things in the Repository at a later date.
-Original Message-
From: Ruel Loehr [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 14, 2006 10:14
To: Maven Users List
Subject: RE: Plugin JAR : bug maven.jar.fin
The way we do this in Maven 1.0.2 is to define a set of build properties called
"lib..version" with the value of the property set to the version of
we are using. We then use these properties in place of the version
number in the project.xml files. Since we use to have a root
project for all
Would it be possible to extend the POM inheritance model currently used
for merging parent POMs to allow for merging arbitrary POMs? This would
allow the plugin configuration to be stored in a single place (possibly
retrieved by URL rather than file reference) and allow multiple project
trees to r
A much better choice would be to allow install:install-file to
optionally create a POM for the file it is installing.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 09:43
To: Maven Users List
Subject: Re: Installing Commercial Jars and missin
, where to find it, and how to
install it locally so that the plugin works.
-Original Message-
From: Wendy Smoak [mailto:[EMAIL PROTECTED]
Sent: Monday, October 24, 2005 09:55
To: Maven Users List
Subject: Re: Installing Commercial Jars and missing POM XML files
From: "Alliso
OK. I know I am weird because I use NetBeans instead of Eclipse, but...
The guide for using Maven 2 with NetBeans shows using the
netbeans-freeform plugin but does not indicate how to install the plugin
in the first place.
Not a major item, but it probably should be corrected.
-
n 10/24/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
>
> OK. I know I am weird because I use NetBeans instead of Eclipse,
but...
>
> The guide for using Maven 2 with NetBeans shows using the
> netbeans-freeform plugin but does not indicate how to install the
plugin
> in the
hortened to something like netbeans:netbeans to match the eclipse and
ide plugins..
Milos
On 10/24/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
>
> Built from SVN where?
>
> -Original Message-
> From: Milos Kleint [mailto:[EMAIL PROTECTED]
> Sent: Monday, October 24, 2005
I was trying to download the 1.0 final as documented on the web site.
None of the mirrors seem to have the distro, but they have the checksum
and PGP.
Am I jumping the gun or is there a permission problem keeping the
mirrors from collecting the distro?
One problem I have been having with maven-proxy is that I find that once a
jar's metadata is downloaded, it never seems to be updated. I noticed this
when Maven 2.0 was released. Soon after that, a few plugins had new versions
released but my Maven 2.0 never updated, even using -U and blasting
One place with a lot of source RPMs to browse is Fedora:
fedora.redhat.com
-Original Message-
From: Xavier Toth [mailto:[EMAIL PROTECTED]
Sent: Monday, October 31, 2005 09:48
To: Maven Users List
Subject: [m2] example source rpm spec file for maven built project
I've got to make a rpm (
It looks like there is a problem checking out your sources. Please make
sure that the SCM information in the project is correct and that you can
use the same information to check out the project from the command line.
-Original Message-
From: Malcolm Wong Ho [mailto:[EMAIL PROTECTED]
Sen
I'm using Linux, not Windows, so this may not be 100% correct. As I
recall, if you want to put the drive designator in the SCM URL, you need
to use something other than ':' as a delimiter. Try
scm|local|C:\Documents and
Settings\WongHoma\.m2\repository|status-change
-Original Message-
There are two different repositories you deal with in Maven:
-- The "local" repository is the one that is located in
${user.home}/.m2/repository by default. This is a place where artifacts needed
for the build are stored, and cannot be shared between users. When you do an
"install", the artif
You answered me to use
the install pugin. Why?
First install locally and the deploy remotely? In such a way?
I created my artifact (a jar file). I would like to share and reuse inside
other project. How can do it? If I read doc I have ti use deploy plugin.
Hope being clear :-)
Tnx,
Luca
-Origi
I am experimenting with a directory archiver for plexus, and built a new
snapshot version of the component. When I did a "mvn install" in that
directory, the install placed the jar where I expected it:
[INFO] [install:install]
[INFO] Installing
/net/home/allisord/src/plugins/plexus-archiver/targe
I figured out what caused this: A jar file listed as a plugin in your
POM that does not contain META-INF/maven/plugin.xml
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 03, 2005 11:09
To: Maven Users List
Subject: [m2] Strange Build Error
I am
, Allison, Bob <[EMAIL PROTECTED]> wrote:
> I figured out what caused this: A jar file listed as a plugin in your
> POM that does not contain META-INF/maven/plugin.xml
>
> -Original Message-----
> From: Allison, Bob [mailto:[EMAIL PROTECTED]
> Sent: Thursday, November 03
I just wanted to make sure that I am doing things correctly before I go
too far on the RPM plugin...
1) To build the RPM, I need to run the command "rpmbuild". Based on
what I saw in the release plugin, I am using classes in package
org.codehaus.plexus.util.cli (in org.codehaus.plexus:plexus-ut
Since you missed this in the SortedMap definition (which TreeMap
implements):
"A map that further guarantees that it will be in ascending key order,
sorted according to the natural ordering of its keys (see the Comparable
interface), or by a comparator provided at sorted map creation time.
This or
d in the parent POM followed by the ordering as
listed in the project POM (with any of the project-specified plugins
removed if they are covered by the parent's list).
..David..
-----Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 10, 2005 10:57
I am having some trouble executing a plugin I am building, and I'm not
sure where to look to find the problem. If anyone can provide some
pointers on what to examine, I would be very grateful.
I am building an RPM plugin with a single goal "rpm:rpm". The goal is
implemented by the class org.code
]
Maven plugin which assembles files into an RPM package for installation
On various target UNIX systems.
[2]
Maven plugin which assembles files into an RPM package
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Monday, November 14, 2005 09:20
To: Maven Users
There are two connections under the SCM tag (check the project model
documentation for more details):
-- "connection" is a read-only connection for getting the source updates
-- "developerConnection" is a read-write connection for making updates
I suspect you need to replicate the connection as
Those are the major ones. Because it is possible for a plugin to create
its own packaging, it might be rather difficult to have a list that
covers everything.
-Original Message-
From: Stephen Cowx [mailto:[EMAIL PROTECTED]
Sent: Monday, November 14, 2005 10:28
To: Maven Users List
Subjec
It looks like we have some problems with the contents of manifests in
jar files.
According to Sun's documentation
(http://java.sun.com/j2se/1.5.0/docs/guide/jar/jar.html), there are
three basic formatting rules which are not always being enforced:
1) All text must be UTF-8
2) Lines are limited t
The configuration should look like (assuming that your definition of
parameter directory is actually specified as "private String
directory"):
/a/b/c
/d/e/f
I don't think that the expressions and default values available in the
Mojo are available in the classes used in this
is case cleaner) if
Maven could process annotations on beans in collections that are defined
as Mojo parameters.
Thanks,
Richard Allen
Allison, Bob wrote:
>The configuration should look like (assuming that your definition of
>parameter directory is actually specified as "
I was trying to build some unit tests for the RPM plugin and am running
into a chicken-and-egg problem. To test the newly-compiled plugin, it
seems that I need to complete the install phase so that the plugin is
available for the tests to run. If I alter the configuration to skip
the unit tests,
rs List'
Subject: RE: Plugin Unit Tests?
Hi Bob,
To test a plugin the best solution is to use the it plugin in
components/sandbox/plugins.
It allows you to put test projects in src/test/it.
-Vincent
> -Original Message-
> From: Allison, Bob [mailto:[EMAIL PROTECTED]
>
oes not
have anything named "sandbox".
Please tell me what I am missing.
-Original Message-
From: Vincent Massol [mailto:[EMAIL PROTECTED]
Sent: Tuesday, November 15, 2005 10:19
To: 'Maven Users List'
Subject: RE: Plugin Unit Tests?
Bob,
> -Original Message-
&
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 am using is
| "http://svn.apache.org/repos/asf/maven/components/trunk"; (which is the
| URL s
Try
http://maven.apache.org/guides/introduction/introduction-to-dependency-m
echanism.html
-Original Message-
From: Serge Bogatyrjov [mailto:[EMAIL PROTECTED]
Sent: Thursday, November 17, 2005 11:27
To: users@maven.apache.org
Subject: MNG-1427 status
Hi
http://jira.codehaus.org/browse
ests?
Hi Bob,
I am trying to use your RPM plugin but can't find th code in svn and
the download link on the site doesn't work. Are you still working on
it?
Thx
On 15/11/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> That was it. Thanks!
>
> -Original Message
A couple questions:
Where does "BaseObject" come from? According to the error message, it
is not in the source tree and not on the class path. If should be in
the source tree, there is something wrong with that source file. If it
comes from Hibernate, you need to import the class (NOT the packa
.
Allison, Bob wrote:
>A couple questions:
>
>Where does "BaseObject" come from? According to the error message, it
>is not in the source tree and not on the class path. If should be in
>the source tree, there is something wrong with that source file. If it
>comes
I'm not really sure why the messages from XDoclet, since the classes
look fine. My guess is that XDoclet is ignoring abstract classes in
deciding if it can find the class. I think this is something you need
to take to the XDoclet list, since I don't think it is a maven problem.
-Original Mes
The tag "@requiresDependencyResolution" has to be on the class, not the
parameter.
-Original Message-
From: Wim Deblauwe [mailto:[EMAIL PROTECTED]
Sent: Monday, November 21, 2005 06:41
To: Maven Users List
Subject: Re: [m2] Copy the dependencies of a project in a custom plugin
The colle
Well, I see a couple problems with your configuration. As I read the
two mappings, they should do the following:
-- Install ${basedir}/src/main/bin/* at /usr/local (for example,
${basedir}/src/main/bin/myprog will be installed at /usr/local/myprog)
-- Install ${basedir}/target/*.jar at /usr/loca
CVS/*
*/*
Any ideas?
Thanks in advance
Regards
On 23/11/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> Well, I see a couple problems with your configuration. As I read the
> tw
-Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesday, November 23, 2005 13:36
To: Maven Users List
Subject: RE: RPM Plugin not cleaning its includes
I found the problem. Now I just need to figure out a solution. I'll
let you know when I get this figure
rom central
Could you zip the project for me and I'll build and install it locally?
Thx
On 24/11/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> I think I have the problem with the RPM plugin solved and I updated
the
> ZIP file[1]. Could you please download the current version,
How do I get access to the recent snapshot? The downloads on the download page
are from May and the CVS information doesn't work:
$ cvs -d :pserver:[EMAIL PROTECTED]:/scm/maven-proxy/ co maven-proxy
/scm/maven-proxy/: no such repository
-Original Message-
From: Jörg Schaible [mailto:[EM
version). There are no source files. Is something
missing in the repository?
-Original Message-
From: Jörg Schaible [mailto:[EMAIL PROTECTED]
Sent: Monday, November 28, 2005 08:12
To: Maven Users List
Subject: RE: [M2] Repository
Hi Bob,
Allison, Bob wrote on Monday, November 28, 2005
For anyone following this thread, the final correct command is:
cvs -d :pserver:[EMAIL PROTECTED]:/home/projects/maven-proxy/scm co maven-proxy
-Original Message-
From: Jörg Schaible [mailto:[EMAIL PROTECTED]
Sent: Monday, November 28, 2005 09:46
To: Maven Users List
Subject: RE: [M2] Re
IIRC, a serializable class which does not define its serialVersionUID
gets a new one every time it is compiled, regardless of what compiler is
being used.
What I had read as the correct solution is for the class to explicitly
define serialVersionUID. Of course, doing that means that you lose the
I am looking into Maven 2 to try to figure out how to reconfigure our
current build environment when we upgrade from v1.0.2. Our software
product consists of a number of web applications, portlets, EJBs, and
other jar files. Out current build tree is set up as follows:
-- The top directory conta
I am working on a multi-project which looks like this:
Project log4jext is an extension for log4j for our environment. Because
of the nature of extending log4j, I was unable to completely remove all
log4j classes from this project's API. Its dependencies look like:
log4j
log4j
andard pattern I can find
somewhere or is that an IoC artifact?
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Wednesday, August 17, 2005 22:18
To: Maven Users List
Subject: Re: [m2] Transitive Dependency Question
On 8/18/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
The way I get this to work is to set "maven.multiproject.site.goals" to
"multiproject:site" in the sandbox project and to "site" in the
mid-level projects (newproj, otherproj). Actually, I have a goal in the
sandbox project called "gendocs" which has "multiproject:site" as a
prerequisite but I don
I wonder if this could be related to the 503 (service unavailable) errors I
have been getting from ibiblio periodically while trying to bootstrap Maven2...
-Original Message-
From: Jeff Jensen [mailto:[EMAIL PROTECTED]
Sent: Saturday, August 27, 2005 15:51
To: 'Maven Users List'
Subject:
The way we share source code between projects is to put the common code in a
jar-producing project and use the jar as a dependency in other projects.
-Original Message-
From: Jamie Bisotti [mailto:[EMAIL PROTECTED]
Sent: Tuesday, August 30, 2005 09:06
To: Maven Users List
Subject: Re: [m
We have our entire project, including subprojects, in a single CVS module. The
directory at the top of the module contains the root POM, etc. Each subproject
is a subdirectory of that top level.
-Original Message-
From: news [mailto:[EMAIL PROTECTED] On Behalf Of Nelson Arape
Sent: Tue
Looks like the pom is now present. Go ahead and try again...
-Original Message-
From: Ashley Williams [mailto:[EMAIL PROTECTED]
Sent: Friday, September 16, 2005 09:05
To: Maven Users List
Subject: [m2] svn update breaks build
Just did an update and the build fails almost straight away.
Done. http://jira.codehaus.org/browse/MNG-971
-Original Message-
From: Brett Porter [mailto:[EMAIL PROTECTED]
Sent: Thursday, September 22, 2005 17:42
To: Maven Users List
Subject: Re: clean command
Hiram and I were discussing this yesterday. Vincent's explanation is
right.
I think we
I am trying to set up a schedule to run every 15 minutes. I am a little
confused about the current cron-style specification since, as written,
it indicates that the DEFAULT_SCHEDULE (0 0 * * *) should run only at
midnight. Is there some sort of disconnect between the text being
displayed and the
The repository that I deploy artifacts to is an NFS mount on my system.
Is there a way to specify the repository so that deploys just copy the
file like install does rather than needing an ssh connection?
-
To unsubscribe, e-mail:
I upgraded from -beta-1 to -beta-2 this morning. When I try to build a
site (m2 clean:clean site:site), I get the dump at the end of the
message. I tried flushing my local repository in case there was a
problem but the problem remains. I have also tried updating the site
plugin (m2 -U site:site)
particular isssue required an API breaking
change, unfortunately. Try m2 -U site:site once to see if it gets it.
I'll update the download page with a note.
- Brett
On 9/28/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> I upgraded from -beta-1 to -beta-2 this morning. When I t
Here is the pattern I was going to build:
Project proj-a creates a.jar which contains:
-- Interface A which is the API for the jar
-- Class AImpl which implements the API
-- Class AFactory which creates implementations of interface A
Project a-test creates a-test.jar which contains a MockObjects
I can't get this to work except in one of my projects, either. Using -npr or
--no-plugin-registry did not help. I also have maven-install-plugin
v2.0-beta-1 installed. The maven-metadata-central.xml in the repository shows
2.0-beta-1 as the only version.
Is there a form of this that can be u
t/resources). I find Spring quite handy for this
type of setup.
Also, you'd want to define your Mocks in Proj a-test in src/main/java, rather
than src/test/java otherwise they won't get exported.
Dave
-----Original Message-
From: Allison, Bob [mailto:[EMAIL PROTECTED]
Sent: Wednesd
I really dislike your suggestion for item 1, since that implies that if
I discover a problem with the release build and have to rebuild it, I
have to remember to manually remove the release build from the
repository first.
-Original Message-
From: David Jackman [mailto:[EMAIL PROTECTED]
S
List
Subject: Re: Release builds and continuous integration
My understanding is that if you are making changes to official release
you really should increment the version (and tag it in CVS/SVN).
Vitaliy
On 10/3/05, Allison, Bob <[EMAIL PROTECTED]> wrote:
> I really dislike your suggest
I am starting to look into building a plugin which will allow mock
objects (and other classes which are used for testing projects which use
the current project) to be built and packaged. I am looking at making a
tree called "src/usagetest" which mirrors "src/main" and "src/test" in
structure and u
I am trying to build my first plugin and having a problem.
I wrote a plugin which I can run as
sample.plugin:maven-hello-plugin:1.0-SNAPSHOT:sayhi and that works
perfectly.
I want to set things up so I can reference the goal as hello:sayhi but
can't seem to get it to work. I added "sample.plugin
I am making a start at the Plugin Development Guide as I am working on
my first plugin. You can find the current contents at
http://sd.no-ip.biz/maven2pdg/. I welcome any comments, corrections,
and suggestions. At this moment, I have a number of questions which I
have not been able to answer whi
1 - 100 of 136 matches
Mail list logo