Hi there I am one of the eXist developers.
We certainly are interested in what our users want, but as yet we have
only had 2 or 3 express an interest in using Maven it is unfortunately
not a top priority for us at the present time.
I myself am a big fan of Maven, and would love to do a port of
About the enforcer problem that you can see in the console: I don't if
you're having the very same one, but there're many bugs that were fixed in
the recent m2e versions.
M2E 0.10 fixed a lot of issues and uses a more recent maven3 version. If
you're not using it, you should really give it a try.
Ok, I checked JIRA and found
http://jira.codehaus.org/browse/MENFORCER-74
http://jira.codehaus.org/browse/MENFORCER-75
http://jira.codehaus.org/browse/MENFORCER-72 (seems to be the same as 75)
So, from
groupId:artifactId:packaging:classifier:version
everything except packaging would be done if
I'm looking for a plugin which has a fail goal, something like:
mvn fail-maven-plugin:fail -Dfail.maven.plugin.message=you failed!
I've seen how enforcer or antrun can fail on-demand, but I'm looking for
something I can fully configure from the command line
Thanks
--
View this message in
This works! Thanks a lot!
/close
2010/5/27 Stephen Connolly stephen.alan.conno...@gmail.com
define a profile for deploying your app with cargo:deploy bound to the
install phase in module A... you can even define defaultGoals in the
profile
so that all you need to type is
mvn
I'm looking for a plugin which has a fail goal, something like:
mvn fail-maven-plugin:fail -Dfail.maven.plugin.message=you failed!
Never seen one or needed one myself, but it would be super trivial to
build yourself. If you had a good justification for it, you could
maybe get it added to the
You could use the enforcer always fail rule in a profile of its own, and then
activate from the command line with something like
mvn -P alwaysFailProfile enforcer:enforce
or even with profile activation using properties, something like:
profiles
profile
idalwaysFailProfile /id
I myself am a big fan of Maven, and would love to do a port of eXist
from Ant (we are heavily invested), over to Maven. Unfortunately I just
don't have enough hours in the day at present to undertake this.
You do realize that simply uploading your artifacts (built by Ant,
Eclipse, Netbeans,
Adam,
I work on the struts project here at apache, but I am getting pretty
good with maven ;)
I'd like to help you guys port to maven... I don't use exist, but came
across it recently and was very interested. If you don't mind, I'll
start perusing the source and send you questions off-list. Is
Is there a separate list for m2eclipse questions? Got m2eclipse
properly building my aar services, but I get an annoying error on
startup.
An internal error occurred during: Repository registry initialization.
The repositoryId cannot be null when creating new repository!
Here is my
I am using CVS for my SCM. I have one repository that is version 1.11.14
and one that is 1.12.12.
When I try to do a release using the 1.12.12 CVS repository I get the
error Received unknown response from server.
But when I use the 1.11.14 repository it works.
Is there a CVS plugin that will
See info here:
http://m2eclipse.sonatype.org/project-information.html
/Anders
On Fri, May 28, 2010 at 15:56, Meeusen, Christopher W.
meeusen.christop...@mayo.edu wrote:
Is there a separate list for m2eclipse questions? Got m2eclipse
properly building my aar services, but I get an annoying
Good Afternoon Adam
before you take long holiday could you offer any information on which MVC
framework eXist 1.4 will be supporting?
Martin
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
Diese Nachricht ist
Dan,
On Fri, May 28, 2010 at 8:18 AM, Daniel Hoffmann
biggibig...@googlemail.com wrote:
This works! Thanks a lot!
define a profile for deploying your app with cargo:deploy bound to the
install phase in module A... you can even define defaultGoals in the
profile
so that all you need to type
I'm working on Mavenizing a small project. In the current project,
there are three source directories.
The Main source, the JUnit test source and a dir called
test_informal that contains some helper classes for doing
interactive testing...
In a maven project, where would one put that type of
My advice is to fit your needs into Maven's standard directory layout
(project structure).
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
Your main source and junit source will fit well there. Unsure how your
helper classes fit in but it seems to
On Fri, May 28, 2010 at 1:43 PM, Steve Francolla sfranco...@gmail.com wrote:
My advice is to fit your needs into Maven's standard directory layout
(project structure).
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
Your main source and junit
My experience has consistently been that if I adapt my projects to Maven
instead of vice-versa, life is just peachy. Have yet to come across a
circumstance in Maven that hasn't already been solved for. Just go with it.
On Fri, May 28, 2010 at 2:04 PM, Greg Akins angryg...@gmail.com wrote:
On
one is re-factoring your ANT taskdef class into a Mojo
path of least resistance is to stick with antrun
http://maven.apache.org/plugins/maven-antrun-plugin/
Martin Gainty
__
Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité
The Maven team is pleased to announce the release of the Maven Doxia and
Maven Doxia Site Tools, version 1.1.3
http://maven.apache.org/doxia/
Release Notes - Maven Doxia - Version 1.1.3
** Bug
* [DOXIA-370] - Confluence module cannot parse horizontal separator
* [DOXIA-374] - Xdoc:
Put your tests in src/test/java as normal.
If your helper classes are to be used by multiple projects, create a new
project just for the helper classes, call it foo-test or something. Put the
helper classes in src/main/java in the foo-test project, not src/test/main.
Then you can create a
The Maven team is pleased to announce the release of the Maven Antrun Plugin,
version 1.4
This plugin allows Ant tasks to be run inside a Maven build. See the plugin's
site for more details:
http://maven.apache.org/plugins/maven-antrun-plugin/
You should specify the version in your project's
If you don't use that little trick, project B cannot depend on project
A for it's test classes because the final artifacts never contain test
classes.
That is one way to do it... but I'd suggest the test-jar approach:
http://maven.apache.org/guides/mini/guide-attached-tests.html
Wayne
23 matches
Mail list logo
