Hello,
I have added a comment in the jira issue.
It sounds more reasonnable to have a new mojo for this with a more
simple syntax which could executed from the cli.
Feel free to add an other comment.
Thanks,
--
Olivier Lamy
http://twitter.com/olamy
http://www.linkedin.com/in/olamy
2011/1/13
Thanks Mike. Defining in a Parent POM was what i was thinking but am unsure
exactly how this might look.
I will have a play about with it and see how it goes.
Alan
--
View this message in context:
Here's one: Ditch the web server and get a real repo manager. I suggest
Nexus, but there others. They all have free OSS versions, so there is
absolutely no reason to not use them.
Ron (one guy on this list) can tell you how they lost two years not using
one. :-)
/Anders
On Thu, Jan 13, 2011 at
On 13 January 2011 08:58, Anders Hammar and...@hammar.net wrote:
Here's one: Ditch the web server and get a real repo manager. I suggest
Nexus, but there others. They all have free OSS versions, so there is
absolutely no reason to not use them.
Ron (one guy on this list) can tell you how they
Stephen Connolly wrote:
Because people who have not read and understood concurrency in
practice often do not understand how the synchronization points affect
jvm sequencing, people often wrongly suspect that result of
instrumented and non-instrumented code is the same.
I'm not sure, why
Hi,
I'm trying to build my first release of my multi-modules projects.
In my settings.xml :
server
idmy-releases/id
usernamedeployer/username
password123/password
On 13 January 2011 09:50, Stefan Schulze algr...@gmx.de wrote:
Stephen Connolly wrote:
Because people who have not read and understood concurrency in
practice often do not understand how the synchronization points affect
jvm sequencing, people often wrongly suspect that result of
instrumented
Stephen Connolly wrote:
[...]
Run the damn tests at least twice.
Ok, I see your point. But I never tried to run the tests only instrumented. I
just want to execute the more-likely-failing tests earlier in the lifecycle and
the not-so-likely-failing tests later.
So of course I want to
On 01/12/2011 09:57 PM, Olivier Lamy wrote:
Hello,
Have a look at http://jira.codehaus.org/browse/MRELEASE-457
That looks like what I want. Thanks.
Joachim
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For
On 01/12/2011 09:59 PM, Jon Paynter wrote:
Joachim,
ditto on the git-submodule support (but that goes in a different thread).
can you try running release:perform on the isolated submodule projects,
instead of the superproject?
I was doing it on the subproject.
I guess the
Hi,
I want to deploy the artifacts to JBoss AS using maven plug-in. I came across
two plug-in for this use case (Cargo Plug-in and Jboss-Maven-Plug-in from
Codehaus). Please suggest which one is best?
Regards,
Tirumal Reddy M
IMO solution is simple - discipline your developers to run verify
before commiting. CI should help you determine whom to blame when
build is broken and then you can apply disciplinary meassures.
Regards,
Stevo.
On Thu, Jan 13, 2011 at 11:24 AM, Stefan Schulze algr...@gmx.de wrote:
Stephen
Which car is the best, A or B?
What's your needs?
/Anders
On Thu, Jan 13, 2011 at 11:43, Tirumal Reddy Moolamalla
t.moolama...@zensar.com wrote:
Hi,
I want to deploy the artifacts to JBoss AS using maven plug-in. I came
across two plug-in for this use case (Cargo Plug-in and
You don't have access?
I suggest you have a look in the Nexus logs. It will tell you what it
doesn't like with your credentials.
/Anders
On Thu, Jan 13, 2011 at 10:54, jeb001 jeremy.jar...@gmail.com wrote:
Hi,
I'm trying to build my first release of my multi-modules projects.
In my
Hi all,
this might be a simple one and if there is documentation about it I'm happy to
read that.
Its a basic understanding question:
I have a maven project and do a release - lets say 1.1
The maven release plugin manipulates the poms and tags the software in the scm.
the trunk itself
Hum, ok... but, I'm using a distant nexus server.. I'm not administrator...
Is there a way for me to see those logs ?
thx
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3339723.html
Sent from the Maven - Users
Hi,
I guess one has to create a branch from the tagged version. Then the version
in the poms have to be set to 1.1.1-SNAPSHOT and then development starts.
Also don't forget to update the scm section of your pom.
Your description of the process is good, but I don't know if there is a fully
Am Donnerstag 13 Januar 2011, 13:42:01 schrieb mremerson...@aim.com:
Hi all,
this might be a simple one and if there is documentation about it I'm happy
to read that.
Its a basic understanding question:
I have a maven project and do a release - lets say 1.1
The maven release plugin
Hi Julien
Thanks for your mail.
You are right the scm section has to be changed too. I will just try with a
dummy project how release:branch works.
But its good to know that the release plugin then works fine
Cheers
-Original Message-
From: Julien HENRY henr...@yahoo.fr
Thanks for your reply.
Maybe I had misunderstood - the maven-deploy-plugin information I had read.
For example - chapter 2.14 in the book Java Power Tools.
I will have a look at Cargo.
Thanks for your help
Hi All,
With too much of tinkering I found out that nothing was wrong about using
apache server and I had to just specify my repository under
pluginRepositories section rather than repositories.
Problem solved.
Thanks to all.
On Thu, Jan 13, 2011 at 2:55 PM, Stephen Connolly
On 13/01/2011 4:25 AM, Stephen Connolly wrote:
On 13 January 2011 08:58, Anders Hammarand...@hammar.net wrote:
Here's one: Ditch the web server and get a real repo manager. I suggest
Nexus, but there others. They all have free OSS versions, so there is
absolutely no reason to not use them.
Hi there,
I would like to verride Maven's default logger with my own. How to do this?
I see that Mojo has a setLog() method, so I was thinking of making a
mojo that executes in the first phase (validate), it would set the log
with setLog()... and then all the other mojos that execute in the
Perhaps a different CI job structuring? This has worked well for me at many
customers: Have a CI job for only compile and unit tests - this maintains
the most important very fast turnaround. Have a second CI job for (longer
running) IT tests that only runs with success of the first. Have a
Nope. You need either os access or ui/rest access.
/Anders
On Thu, Jan 13, 2011 at 13:45, jeb001 jeremy.jar...@gmail.com wrote:
Hum, ok... but, I'm using a distant nexus server.. I'm not administrator...
Is there a way for me to see those logs ?
thx
--
View this message in context:
Jeff Jensen wrote:
Perhaps a different CI job structuring? This has worked well for me
at many
customers: Have a CI job for only compile and unit tests - this
maintains the most important very fast turnaround. Have a second CI
job for (longer
running) IT tests that only runs with
On OpenVMS, with JDK 1.5, and maven 3.0
I can download now perfectly forcing basic authentication toward our
proxy server.
But as downloading artefacts from repositories works now perfect, I want
to do bigger steps.
i.e. building the svnkit
so here we go
IA64mvn -Dhttp.auth.preference=Basic
Jeff Jensen wrote:
Perhaps a different CI job structuring? This has worked well
for me at many
customers: Have a CI job for only compile and unit tests -
this maintains the most important very fast turnaround. Have
a second CI job for (longer
running) IT tests that only runs with
Hi
I'm trying to write a plugin which does the following:
- Check the classes in the project and keep all classes that implement
interface X.
- For all X, get the fields, and if a field has a certain annotation, generate
a class containing some constant information.
Normally the plugin should
Maybe I had misunderstood - the maven-deploy-plugin information I had read.
For example - chapter 2.14 in the book Java Power Tools.
I found that book on Amazon and was able to dig inside it a little bit
to look at chapter 2.14.
You simply don't know/understand that the use of the word deploy
xdoclet is a tool for parsing java and also generate java, but
it is kind of old now
/Lucas
On 01/13/2011 04:48 PM, Lewis, Eric wrote:
Hi
I'm trying to write a plugin which does the following:
- Check the classes in the project and keep all classes
Thanks for your time much appreciated.
I am looking a Cargo but in the simple case I have the 'shared hosting'
remote server does not give me access to 'tomcat/manager' so I think this
will not work either but I have only just started looking.
-Original Message-
From: Wayne Fay
Does anyone install maven via macports???
If so you might be interested in some tickets I've just submitted:
#27944 - Upgrade maven3 to 3.0.2
#27946 - maven_select (similar to python_select, so you can easly
switch between maven2 and maven3)
#27947 - maven3 update to use maven_select
#27948 -
Hi,
You should try to use new JDK 1.6 annotation processor utilities. The only
constraint I see is that each class you want to parse must be annotated.
Regards,
Julien
- Message d'origine
De : Lewis, Eric eric.le...@ipi.ch
À : users@maven.apache.org users@maven.apache.org
Envoyé
On Thu, Jan 13, 2011 at 11:19 AM, Nigel Weinronk
nweinr...@btinternet.com wrote:
Thanks for your time much appreciated.
I am looking a Cargo but in the simple case I have the 'shared hosting'
remote server does not give me access to 'tomcat/manager' so I think this
will not work either but I
Sounds nice, but this doesn't meet my requirement, that the tests with
coverage-checks (and only one time, not twice) should run, when the developers
do mvn test.
It sounds like Maven cannot, for whatever reason, meet your requirement.
We have a quite small difference between
Thanks I will look at this.
-Original Message-
From: Wendy Smoak [mailto:wsm...@gmail.com]
Sent: 13 January 2011 16:50
To: Maven Users List
Subject: Re: Deploy .war to shared hosting 'remote server'
On Thu, Jan 13, 2011 at 11:19 AM, Nigel Weinronk
nweinr...@btinternet.com wrote:
Thanks
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-jar-plugin:2.3.1:jar (default-jar) on
project svnkit: Error assembling JAR: Failed to read filesystem
attributes for: /dkb3/sw-projekte/asf/svnkit/tags/1_3_3/pom.xml: Failed
to retrieve numeric file attributes using: '/bin/sh -c ls
Hi, Wayne; this has nothing to do with the JDK and everything to do with
Plexus.
http://plexus.codehaus.org/plexus-components/plexus-io/xref/org/codehaus/plexus/components/io/attributes/PlexusIoResourceAttributeUtils.html#255
Best,
Laird
On Thu, Jan 13, 2011 at 1:51 PM, Wayne Fay
No, ignore Maven 1.
/Anders
On Thu, Jan 13, 2011 at 17:24, John Patrick nhoj.patr...@gmail.com wrote:
Does anyone install maven via macports???
If so you might be interested in some tickets I've just submitted:
#27944 - Upgrade maven3 to 3.0.2
#27946 - maven_select (similar to
Olivier,
Not sure if you are being alerted of comments on the JIRA or not but in
case you are not I've commented in more detail there. Thanks for taking a
look!
-Ryan
On Jan 13, 2011 3:33 AM, Olivier Lamy ol...@apache.org wrote:
Hello,
I have added a comment in the jira issue.
It sounds more
On Thu, Jan 13, 2011 at 9:01 AM, Schulze, Stefan (EXTERN: CKC)
extern.stefan.schul...@volkswagen.de wrote:
Jeff Jensen wrote:
Perhaps a different CI job structuring? This has worked well
for me at many
customers: Have a CI job for only compile and unit tests -
this maintains the most
I need to modify the maven build for a large project
to skip certain steps during typical development builds (i.e. don't
build the *-source.jar files). I've searched for conditional
execution for maven, but haven't found anything.
A dev profile sounds like the intuitive way
Hi,
I’m trying to use Maven / Eclipse to build a skeleton Atlassian JIRA plugin and
I'm coming up against some errors. The ff. is what I get in the logs:
13/01/11 3:01:09 MST PM: Maven Builder: FULL_BUILD requireFullBuild
13/01/11 3:01:09 MST PM: [WARN]
13/01/11 3:01:09 MST PM: [WARN] Some
You might want to look in the list archives, there was a discussion in which I
learned a lot from others on the list about the pros and cons of using profiles
versus using separate (nearly identical) POMs. My takeaway was that if one
just jumps on profiles as the solution to every conditional
On Jan 13, 2011, at 5:10 PM, Dean Schulze wrote:
I need to modify the maven build for a large project
to skip certain steps during typical development builds (i.e. don't
build the *-source.jar files). I've searched for conditional
execution for maven, but haven't found
Has anyone done this before? Any tricks or hints? I was hoping to use
JaCoCo, but other tool ideas are welcome.
Links:
http://maven.apache.org/plugins/maven-invoker-plugin/examples/post-build-script.html
http://jacoco.org/jacoco/index.html
--
View this message in context:
Thanks Laird! I actually looked (very briefly) for this code but I was
looking in plexus-utils, not plexus-components, doh.
Surely there is a better way to implement this. I need to trace this
code around and figure out why its doing this and see if maybe we can
use another approach to get the
13/01/11 3:01:09 MST PM: [WARN] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 54, column
21
Honestly, read the error and then take a wild guess what this means,
and you are probably correct. (Here's a hint: open the project's
pom.xml
The antlr-3.1.3 depends on antlr-runtime-3.1.3, which depends on
stringtemplate-3.2, and stringtemplate depends on antlr-2.7.7; the
dependency scope is all compile.
I got two versions of antlr, when I using 'mvn
dependency:copy-dependencies'. I'm looking for a way to use only one
antlr by
http://maven.apache.org/guides/introduction/introduction-to-optional-and-excludes-dependencies.html#Dependency_Exclusions
You would then exclude antlr-2.7.7 as you don't want it.
I'm somewhat surprise of this problem though. I would expect that
antlr-3.1.3 would have this exclusion in place
Please also understand that having the sources jars for releases is actually
very good. Anyone using your artifacts would have great use of them when
debugging for example.
What is the actual problem? Is it that sources jars exist, or something
completely different (the build taking too long?)?
Hum... no other suggestions ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3340910.html
Sent from the Maven - Users mailing list archive at Nabble.com.
Go talk to your Nexus admins?
/Anders
On Fri, Jan 14, 2011 at 08:15, jeb001 jeremy.jar...@gmail.com wrote:
Hum... no other suggestions ?
--
View this message in context:
http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3340910.html
Sent from
I have looked at this code earlier, and it actually forks *2* shells to
get file attributes when creating any kind of xAR archive.
There is definitely room for improvement here, especially on the posix
implementation. The last time I googled this it
was not as trivial as one could think.
55 matches
Mail list logo