If i have to repeatedly doing the same thing every day maven
plugin is a way to go since I can run it any where i like as long as
maven installed and point to our central maven repo.
-D
On Thu, Mar 1, 2012 at 11:57 PM, Anders Hammar and...@hammar.net wrote:
Sonatype do some black magic for
Hi All
I have created a maven archetype using mvn:create-from-project.
I dont wan't the plugin to modify the java file hierarchy but it seems
it shortens the java package hierarchy and prefixes the base package
with ${package} inside files. I tried adding packaged=false to the
filesets in
On 02/03/2012 1:32 AM, Markku Saarela wrote:
Hi,
Developing with Eclipse IDE and JavaEE server using
maven-eclipse-plugin you have to use profiles, because Eclipse does
not isolate test code and test resources.
Eclipse does
/src/main/ code
/src/test ... test code and resources
You
Hi,
I build a automated setup for an Webapplication including GlassFish
configuration, DB setup and configuration and deployment of the
application itself.
I have choosen Ant as tool for this and I use Maven via the Ant Maven
Task to handle all dependency related stuff and it works great.
On Thu, Mar 01, 2012 at 11:16:34AM -0800, offbyone wrote:
Ok, I hear you, profiles are evil. BUT I still don't understand the
alternative so let me give a specific and tangible example and maybe you can
explain a specific alternative.
I am currently deploying my product in a tomcat/linux
Just a general musing on some of the recent conversations.
A recent discussion included the admonition to Walk before you run.
I just came across a quote from Knuth that relates very well to some of
issues raised by new Maven users.
Premature optimization is the root of all evil (or at least
Hi,
You don't understand how Eclipse IDE works. Eclipse does not have
different classpaths for testing and actual runtime. So Eclipse basic
design is faulty. There is bug open since 2008 to provide means to tell
Eclipse that which are test sources and not include them to runtime
classpath.
1)I keep getting this error in reference to the generic-war project:
'packaging' with value 'war' is invalid. Aggregator projects
require 'pom' as packaging.
I tried to changing it to pom but that doesn't seem right. Is an
Aggregator any project with sub modules?
Read my post again.
We have been developing and maintaining a large portal application with
over 70 WAR files in Eclipse with Maven since 2007 and several smaller
portals and standalone applications. We have not had this problem.
That is not to say that I am an expert in Eclipse but we know enough to
make it
You don't understand how Eclipse IDE works. Eclipse does not have different
classpaths for testing and actual runtime. So Eclipse basic design is
faulty. There is bug open since 2008 to provide means to tell Eclipse that
...
Of course NetBeans and IntelliJ has correct way to do things but they
We are deploying to artifactory.
Please suggest.
These sound like questions that are better asked on the Artifactory list.
Wayne
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail:
Please discard my last comment, wrong topic.
-D
On Fri, Mar 2, 2012 at 12:17 AM, Dan Tran dant...@gmail.com wrote:
If i have to repeatedly doing the same thing every day maven
plugin is a way to go since I can run it any where i like as long as
maven installed and point to our central
If i have to repeatedly doing the same thing every day maven
plugin is a way to go since I can run it any where i like as long as
maven installed and point to our central maven repo.
-D
On Thu, Mar 1, 2012 at 7:59 PM, Terence Stephens
terence.steph...@gmail.com wrote:
Thanks for all the
In multi-module project i hit the same problem with m2e and
maven-eclipse-plugin. Are you saying not to import multi-module projects
into Eclipse, instead every module separately? Or you don't use server
plugins to deploy application instead you deploy outside Eclipse and use
remote
I am not sure if this directly answers your question but perhaps a bit
of background helps.
We use Eclipse STS which comes with Maven support built in. We used to
waste so much time upgrading Eclipse and getting everyone configured in
the same way.
Now it is a single download (BIG) to get
Our releases do not have any configuration files in artifact's, instead
manifest classpaths has directory name to point directory that has those
files. We use separate build to assembly different configurations into
different environments putting configurations in place.
I like to use Eclipse
I have a wait test that I expect to fail on occasion because the test threads
get too out of sync. So, using TestNG, I'm setting the successPercentage and
invocationCount to handle the occasional acceptable failure. If the code's
broken, none of the invocations will pass.
When I run the test
I think a much better solution than relying on the build tool (maven
profiles or on war overlays) is to use environment variables and bundle all
the LookAndFeel.xml in your war
I would use spring 3.1 and use the environment profiles feature.
On Fri, Mar 2, 2012 at 7:19 AM, Wayne Fay wayne...@gmail.com wrote:
1)I keep getting this error in reference to the generic-war project:
'packaging' with value 'war' is invalid. Aggregator projects
require 'pom' as packaging.
I tried to changing it to pom but that doesn't seem
One thing that also caught me off guard is it appears that I have to
reference the clienta-war and clientb-war as modules in my main project
pom. Is that correct?
Yes, that is correct. If a project is not a module (directly as
children or as grandchildren etc) of the project you are executing
I would also recommend gradle for your circumstances. If you were thinking
of using ant, all the ant tasks are available for your in gradle but it has
maven's style of convention over configuration for the part's like building
Java code which have a well-defined lifecycle.
Cheers, Paul.
On Thu,
21 matches
Mail list logo
