FWIW, IMO introducing Spring and OSGI to replace a number of the
choices in Maven is a good start; these are excellent frameworks with
excellent documentation, excellent communities, and a lot of
experienced developers - something that simply cannot be said of
Plexus, "XBR", Classworlds - and that
On Feb 4, 2008 5:14 PM, Dan Fabulich <[EMAIL PROTECTED]> wrote:
> Jan Nielsen wrote:
>
> > Finding the definitive help information for a plugin should be
> > absolutely trivial and built-in; having the CLI option which give the
> > code-you-are-executing-right-
FWIW, I (and probably 99.9% of the Maven user-base) have desired just
this kind of option for plugins for a l o o o n g time. Something
like:
mvn nifty help
mvn nifty -h
mvn nifty --help
mvn nifty:help
mvn nifty:option
mvn nifty
and if you do:
mvn nifty:invalid
you just get the
Looks great, Emmanuel. There's a typo ("jdbc/continuuù") here:
http://maven.apache.org/continuum/documentation/1_1/installation/tomcat.html#Tomcat_6.0.x_Specifics
-Jan
On Nov 12, 2007 5:42 AM, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I documented Continuum installation on Tomcat,
roups you have defined, then
> maven, then codehaus.
>
> -Original Message-----
> From: Jan Nielsen [mailto:[EMAIL PROTECTED]
> Sent: Saturday, October 20, 2007 10:44 AM
> To: Maven Developers List
> Subject: Re: Plugin Resolution Bug?
>
> Yes; thanks, Wayne - Marco
these lines:
> mvn clean triemax:jalopy-maven-plugin:1.0:format
>
> If you couldn't tell, that's groupId:artifactId:version:mojo.
>
> Wayne
>
> On 10/17/07, Jan Nielsen <[EMAIL PROTECTED]> wrote:
> > I have configured our local repository as a single r
BUG] Building Maven user-level plugin registry from: 'C:\Documents
and Settings\Jan Nielsen\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'C:\maven-2.0.7\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO]
s
foo-bar\src\site\xdoc
The functional tests are not currently in a separate module, though
that is something we are considering. Is there an advantage to this?
Thanks,
-Jan
On 10/12/07, Wendy Smoak <[EMAIL PROTECTED]> wrote:
> On 10/12/07, Jan Nielsen <[EMAIL PROTECTED]> wrote
We are new to Maven and Selenium. We are developing a set of portlets
and have chosen to use Selenium to test the functionality of these
web-applications (each portlet is a web-application). To be tested,
the portlets must be compiled, packaged into a WAR, and deployed to
our portal. Then the Selen
A
Rationale: my expectation, and I suspect most developers'
expectations, is that when I build my product with a tool and my
source does not change and I do not explicitly install a new version
of my tool, that my resulting binary does not change either. With
dynamic downloads of plug-ins (i.e., d
Very nice, Cédric! This will be very useful.
-Jan
On 7/26/07, Cédric Vidal <[EMAIL PROTECTED]> wrote:
> Hi Guys,
>
> I would like to announce a new Apache licensed Maven 2 related tool called
> Mavenizer:
> http://mavenizer.sourceforge.net/
>
> I've been heavily using Maven for a long time and ju
roleManager = (RoleManager) lookup( RoleManager.ROLE, "default" );
}
To save me a bit of digging, does anyone know how this is supposed to work?
Thanks,
-Jan
On 5/16/07, Jan Nielsen <[EMAIL PROTECTED]> wrote:
Hi Joakim, et al.:
My apologies - I should have included m
FWIW, this sounds good to me, Jeremy.
-Jan
Jan Nielsen * System Architect * SunGard Higher Education * Tel +1 801 257
4155 * Fax +1 801 485 6606 * [EMAIL PROTECTED] * www.sungardhe.com
* 90 South 400 West, Suite 500, Salt Lake City, UT USA
CONFIDENTIALITY: This email (including any
guessed, each of our builds is a "release" which enables
us after QC completes to define build 12345 as "Release 1.0" (and once the
release has been defined, you could go back and "tag" each file in the
build with the release moniker if you really want the SCM to h
with JDK 1.3
constructs. My test code needs to test both modes of operation, i.e., JDK
1.3 environments and JDK 5 environments so my unit tests for this library
must be executed twice, once in each environment, and my code must be
compiled in JDK 1.3. Does that make sense?
Any thoughts?
Jolly good idea.
-Jan
Brett Porter <[EMAIL PROTECTED]>
02/21/2006 07:11 PM
Please respond to
"Maven Developers List"
To
Maven Developers List
cc
Subject
sending JIRA mail to commits@maven.apache.org
What do folks think of doing this to make the dev traffic a bit
friendlier to the p
16 matches
Mail list logo
