Jason van Zyl-2 wrote:
Sweet. We can look at the various platforms and see if we can apply this
option across the board. Even if it's only for linux we can add it there.
On Aug 19, 2010, at 9:06 AM, kristian wrote:
hi,
snip...
So can someone explain exactly what this flag is doing?
To sum up:
- Maven's JVM under 32-bits windows is not concerned. Hotspot always
defaults to client vm under Windows.
- Then for Linux or other platforms, with current typical machines, it's
very often defaulting to Server VM.
But it can vary, and is precisely explained in the link
On 08/23/2010 10:55 AM, Baptiste MATHUS wrote:
- Then for Linux or other platforms, with current typical machines, it's
very often defaulting to Server VM.
But it can vary, and is precisely explained in the link Hervé put (more
directly, see here :
have a look at some tips how to improve startup time for jruby and
some of it holds true for maven as well:
http://blog.headius.com/2010/03/jruby-startup-time-tips.html
with regards, Kristian
2010/8/23 Martin Schayna martin.scha...@abra.eu:
On 08/23/2010 10:55 AM, Baptiste MATHUS wrote:
Apache Commons NET currently uses the groupId commons-net. However, it
should really use the groupId org.apache.commons.
Is it possible to set up the Maven repos so that this change is
transparent to users?
Or does changing a groupId necessarily involve change for end-users?
==
AIUI, a
I think it could help you :
http://maven.apache.org/guides/mini/guide-relocation.html
Cheers
Arnaud
On Aug 23, 2010, at 2:20 PM, sebb wrote:
Apache Commons NET currently uses the groupId commons-net. However, it
should really use the groupId org.apache.commons.
Is it possible to set up
I have been unable to find a way to make a failure in an integration
test result in failing the overall build. I have failsafe:verify in
post-integration, and no joy.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
1. put failsafe:verify in verify where it's supposed to be
2. don't run mvn integration-test but run mvn verify (shorter to type too)
-Stephen
On 23 August 2010 14:28, Benson Margulies bimargul...@gmail.com wrote:
I have been unable to find a way to make a failure in an integration
test result
See: http://maven.apache.org/plugins/maven-failsafe-plugin/
The Maven lifecycle has four phases for running integration tests:
* pre-integration-test for setting up the integration test environment.
* integration-test for running the integration tests.
* post-integration-test for
Also there's about 10 gazillion times on the project site where we say to
run mvn verify... could you help us make this more clear?
-Stephen
On 23 August 2010 14:48, Stephen Connolly
stephen.alan.conno...@gmail.comwrote:
See: http://maven.apache.org/plugins/maven-failsafe-plugin/
The Maven
Hi there,
I'm running into trouble trying to configure my project, which depends on a
maven artifact living somewhere else. That other artifact has a (transitive)
dependency of type 'pom', with the scope set to 'import'.
For some reason, however, when I only add a direct dependency to the
Check out the suggested bindings at
http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing
Brett
On 8/23/10, Benson Margulies bimargul...@gmail.com wrote:
I have been unable to find a way to make a failure in an integration
test result in failing the overall build. I have
Apache Commons NET currently uses the groupId commons-net. However, it
should really use the groupId org.apache.commons.
Unless you're responsible for these artifacts (a member of the Apache
Commons NET PMC), you're going to have a lot of trouble doing anything
about this. Appeal to them. Make
The relocation poms will help prevent collisions of different
versions, but eventually the users would want to update to the new
groupId.
On Mon, Aug 23, 2010 at 8:20 AM, sebb seb...@gmail.com wrote:
Apache Commons NET currently uses the groupId commons-net. However, it
should really use the
I always run mvn install. But point 1 is probably my problem.
On Mon, Aug 23, 2010 at 9:46 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
1. put failsafe:verify in verify where it's supposed to be
2. don't run mvn integration-test but run mvn verify (shorter to type too)
-Stephen
Hello again list - was hoping to NOT be sending all these maven 3
questions...but.
So we have a parental pom that listed as the top module in the top level pom.
In maven 2, the build just chugs along successfully and handles this no problem.
In maven 3, however, somehow maven jumps right
On 23 August 2010 16:07, Brian Fox bri...@infinity.nu wrote:
The relocation poms will help prevent collisions of different
versions,
Help prevent collisions - is the collision detection the same, or is
it weakened by the change of groupId?
i.e. suppose one releases Net 2.2 as groupId
2010/8/23 Arnaud Héritier aherit...@gmail.com:
I think it could help you :
http://maven.apache.org/guides/mini/guide-relocation.html
Thanks - but it does not really cover the Apache case where a shared
repo is used.
Cheers
Arnaud
On Aug 23, 2010, at 2:20 PM, sebb wrote:
Apache Commons
On 23 August 2010 15:28, Wayne Fay wayne...@gmail.com wrote:
Apache Commons NET currently uses the groupId commons-net. However, it
should really use the groupId org.apache.commons.
Unless you're responsible for these artifacts (a member of the Apache
Commons NET PMC), you're going to have a
I am in verify, I mistyped:
execution
idverify/id
phaseverify/phase
goals
goalverify/goal
/goals
How about this: next time you make a release, publish both a dummy
version on the old groupId and the new one? That won't help people
whose dependency graph reaches both a 'live' version of the old one
and the new one, but it will help some people.
Other projects have switched and survived,
I'm reading the Nexus book. It describes how a given repository is
either for releases or snapshots. It says that the central maven repo
is a release repository. But then in the example for how to configure
a profile that will use the nexus served repository instead of
central, it shows
Your nexus is a proxy for releases from central
Your Nexus has a place to host third party libraries that can not be
distributed from Central due to licensing issues.
Your Nexus is a host for your releases
Your Nexus is a host for your SNAPSHOTs
When deploying you only deploy to the last 2
On Mon, Aug 23, 2010 at 1:09 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
So the client needs to configure 2 repositories- one for all the releases
and one for all the SNAPSHOTS.
You should be able to use a single repo url from the client -- the
repo managers have the concept of a
if you don't specify a phase then both executions will just go to the
correct place, e.g.
execution
goals
goalintegration-test/goal
goalverify/goal
/goals
/execution
is all you really need
On 23 August 2010 17:13, Benson Margulies bimargul...@gmail.com wrote:
I am in verify, I mistyped:
I have some scripts under src/main/resources/scripts. These scripts are
executables. But maven-jar-plugin is not preserving these file permissions.
Any suggestions?
--
View this message in context:
On 23/08/2010 1:15 PM, Wendy Smoak wrote:
On Mon, Aug 23, 2010 at 1:09 PM, Ron Wheeler
rwhee...@artifact-software.com wrote:
So the client needs to configure 2 repositories- one for all the releases
and one for all the SNAPSHOTS.
You should be able to use a single repo url from the client --
profiles
profile
idnexus/id
!--Enable snapshots for the built in central repo to direct --
!--all requests to nexus via the mirror --
repositories
repository
idcentral/id
urlhttp://central/url
releasesenabledtrue/enabled/releases
snapshotsenabledtrue/enabled/snapshots
/repository
This is a bit on the edge of Tomcat and Maven but I am hoping that
there is a Maven solution or some little trick that makes the problem go
away.
Our LMS portal consists of 60 separate modules that we build using
Maven. About 45 are webapps that we need to deploy to make a new
release.
finalName in your POM can be used to get a plainly-named version in
the target directory.
The maven assembly plugin could be use to collect all the war files
into a directory or tarball with their names changed following a
pattern.
the dependency plugin could be used to fetch them with their
I'm trying to use nexus to serve a 3rd party dependency. Following
the nexus book, I was able to upload the artifact with out incident.
I then tried to search for the dependency in the various interfaces of
m2eclipse: via add dependency on the pom.xml view, via the repository
view. In none of
I'm trying to use nexus to serve a 3rd party dependency. Following
the nexus book, I was able to upload the artifact with out incident.
Is there a reason you're posting these Nexus questions on the Maven
Users list instead of the proper forum?
Is there a reason you're posting these Nexus questions on the Maven
Users list instead of the proper forum?
I didn't know there was a nexus list. Thanks.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
I didn't know there was a nexus list. Thanks.
This happens often. I don't know why there is such confusion. Perhaps
the Sonatype folks need to make this more obvious somewhere on the
Nexus site?
Wayne
-
To unsubscribe,
On 8/23/10 2:42 PM, Ron Wheeler wrote:
This is a bit on the edge of Tomcat and Maven but I am hoping that
there is a Maven solution or some little trick that makes the problem go
away.
Our LMS portal consists of 60 separate modules that we build using
Maven. About 45 are webapps that we
-Original Message-
From: Ron Wheeler [mailto:rwhee...@artifact-software.com]
This is a bit on the edge of Tomcat and Maven but I am hoping that
there is a Maven solution or some little trick that makes the problem
go
away.
Our LMS portal consists of 60 separate modules that we build
-Original Message-
From: usammmy [mailto:mythreye...@gmail.com]
I have some scripts under src/main/resources/scripts. These scripts are
executables. But maven-jar-plugin is not preserving these file
permissions.
Any suggestions?
jar files don't support storing permissions.
Create a
The reason is simple:
Maven needs at least one snapshot repo configured, or it won't even
attempt to ask anyone (specifically Nexus via the mirrorOf * setting)
for any snapshots. Maven has built in an existing repository with the
ID central but it is enabled only for releases. We must do either:
You mean, like adding a project information page in the community
section with links to all the lists?
http://nexus.sonatype.org/project-information.html
;-p
On Mon, Aug 23, 2010 at 4:02 PM, Wayne Fay wayne...@gmail.com wrote:
I didn't know there was a nexus list. Thanks.
This happens
Yep, i'm still here. I see some people have patches for this and the
dependency plugin so I'll try to push out a release soonish.
On Fri, Aug 20, 2010 at 5:05 PM, Haszlakiewicz, Eric
ehas...@transunion.com wrote:
I been using the maven-enforcer-plugin a bit, and I've noticed that some
other
I think the issue is that the boundaries between maven, sonatype,
m2eclipse, nexus, etc. are a bit unclear to the unitiated, i.e. me.
On Mon, Aug 23, 2010 at 3:26 PM, Brian Fox bri...@infinity.nu wrote:
You mean, like adding a project information page in the community
section with links to all
On Mon, Aug 23, 2010 at 3:24 PM, Brian Fox bri...@infinity.nu wrote:
The reason is simple:
Simple, but not obvious ;)
Maven needs at least one snapshot repo configured, or it won't even
attempt to ask anyone (specifically Nexus via the mirrorOf * setting)
for any snapshots. Maven has built
On 23/08/2010 4:09 PM, Justin Edelson wrote:
On 8/23/10 2:42 PM, Ron Wheeler wrote:
This is a bit on the edge of Tomcat and Maven but I am hoping that
there is a Maven solution or some little trick that makes the problem go
away.
Our LMS portal consists of 60 separate modules that we build
If you set the relativePath element for the parent section, does it make a
difference?
/Anders
On Mon, Aug 23, 2010 at 18:03, EJ Ciramella ecirame...@casenetinc.comwrote:
Hello again list - was hoping to NOT be sending all these maven 3
questions...but.
So we have a parental pom that
Maven 3 defines a strict ordering of how agrregation and parents interact.
Benjamin might be able to recall the exact ordering rules as he implemented
them.
I suspect this is what it catching you out
-Stephen
On 23 August 2010 17:03, EJ Ciramella ecirame...@casenetinc.com wrote:
Hello again
45 matches
Mail list logo
