On 12/20/2012 12:19 PM, cowwoc wrote:
[…] in a clustered environment all my configuration sits inside Jenkins. Having
to configure each node before I can use Jenkins on it adds a lot of work.
[…] I favor adding command-line options to configuration files.
I agree that for cases like this it wo
ean up s and s
- use 3.6 plugin
- do not override splash & icon branding
Enjoy,
The Mojo team.
- Jesse Glick
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
On Sun, Apr 10, 2011 at 11:08 PM, Brinker, Don-NONEMP
I was HOPING generate would match the archetypeCatalog URL to the URL of a
repository in my settings, but no luck.
On 04/11/2011 01:40 PM, Wendy Smoak wrote:
It doesn't match by url, it matches by repository id. Is there a way to send a
The Mojo team is pleased to announce new releases of various archetypes in the
group org.codehaus.mojo.archetypes related to NetBeans, OSGi, and Java EE:
netbeans-platform-app-archetype 1.9
nbm-archetype 1.8
nbm-suite-root 1.5
osgi-archetype 1.3
webapp-j2ee13 1.1
webapp-j2ee14 1.2
webapp-jee5
On 02/15/2011 11:35 PM, Stephen Connolly wrote:
there are enough people out there who
use mvn exec:exec to run their swing apps
Do you mean exec:java? (exec:exec -Dexec.executable="java" would be unaffected.) It's not a very good idea to run an arbitrary app this way, since there are plenty of
On 02/13/2011 04:54 PM, Benson Margulies wrote:
It seems to me that it might be a legitimate idea for maven itself to
just set headless, at least when invoked from the shell.
So long as this is done from the CLI entry point classes, or bin/mvn, and not in core classes where it could cause probl
On 11/09/2010 06:43 PM, Benjamin Bentmann wrote:
Not possible.
Thanks, at least I will not waste more time trying.
usually accomplished by an artifact
handler for the dependency type in question which sets
includesDependencies=true like for WAR artifacts.
Interesting, did not think to look
I am interested in experimenting with whether a plugin running in Maven 3 and declared as a build extension can *replace* a standard service. In particular, I would like
to replace DefaultProjectDependenciesResolver with a variant that behaves specially on certain kinds of dependency artifacts (do
New versions of the Java EE 6-related archetypes (WAR, EJB-JAR, EAR) were released. The major change from the previous versions is a different handling of the endorsed
classpath override - the new POM strategy is simpler and should be more portable, and ensures that the endorsed API JAR is downloa
