2009/5/13 Ramon Casha ramon.ca...@megabyte.net
Ah.
Ok, how about a Checkstyle 5 plugin for Maven in the meantime? :)
Ah-ha a different question that is... it requires a different response...
which version of Maven are you looking for a Checkstyle 5 plugin for Maven
for? ;-)
-Stephen
P.S.
Ah.
Ok, how about a Checkstyle 5 plugin for Maven in the meantime? :)
Ramon Casha
On Wed, 2009-05-13 at 06:39 +0100, Stephen Connolly wrote:
2009/5/12 Ramon Casha ramon.ca...@megabyte.net
Any chance of
It may help if you explicitly marked the dependency as being of type war,
since it looks like it's looking for a jar of the same group/artifactId.
On Tue, May 12, 2009 at 11:15 PM, KurtG ku...@serent.com wrote:
I did a 'mvn install' my web app module with no problems and my war file is
Maven = 2.1.0
Apparently the changes have happened in checkstyle though - the plugin
has some depenencies on a method loadModuleFactory which no longer
exists - it doesn't build against the latest checkstyle. I tried looking
for a replacement for that function but got lost.
I'm currently working
Just add typewar/type below the version tag in your dependency
On Tue, May 12, 2009 at 11:15 PM, KurtG ku...@serent.com wrote:
I did a 'mvn install' my web app module with no problems and my war file
is
definitely in my ~/.m2 repository. However, when I build my ear, I get
this:
I have written a couple of plugins to aid documentation that I would like to
make available. Both generate docbook documents, where one extracts
snippets from Java source code and the other is actually a JavaDoc Doclet
that extracts the comments and converts them to well formed XML. These
2009/5/12 Brad Harper brad.har...@epsiia.com:
I was hoping to hear someone say that the war file should generate an error
or fail.
In our case, we have multiple versions of a general 'platform', each
represented by a war artifact. Derivative wars artifacts are built with
customizations and
Harper, Brad wrote at Montag, 11. Mai 2009 21:55:
Is there a way to detect when the dependencies of two war artifacts are
inconsistent with respect to packaged jar versions?
E.g. a war depends on artifact abc-1.0.0.jar. An overlay is performed
where an inconsistent dependency on
On 13 May 2009, at 06:38, Stephen Connolly wrote:
have two profiles... first one active by default with all reports
defined
inside it. second profile is for your clients.
when you activate a profile from the cli, that will automatically
deactivate
any profiles which are active by default
Brian Fox schrieb:
On Mon, May 11, 2009 at 9:48 AM, Todd Thiessen thies...@nortel.com wrote:
Are there many cases where you want something for compilation
that isn't needed at runtime? I don't see them as being separate.
Really? I am surprised. Yes there is a relation between compile and
Hi Karthik,
Please switch to the Sonar user mailing list [1] in order to get the support
you need.
In few words, you can analyze a non-maven project which has multiple source
directories defined. But, as Kamlesh said, there is currently a limitation :
this mode is not compatible with findbugs, so
Hello Ramon,
Vote on this http://jira.codehaus.org/browse/MCHECKSTYLE-105 issue for
official maven checkstyle release with 5.0 checkstyle included, or you can
already use release in Atlassian public repo (see
Which JDK under what OS ?
2009/5/12 j_ri jochen.riedlin...@l-bank.de:
Hi,
I have problems with the compilation-time of some of our projects using java
6 (update 10 and 13) and maven (I tried with 2.0.7 and 2.1.0).
Compiling 806 source-files takes about 7 seconds using jdk 1.5. When
I tried with JDK 6 Update 10 and JDK 6 Update 13(with JDK 5 Update 11
everything was fine)
OS is Windows XP Pro SP2
I tried with Maven 2.0.7 and 2.1.0
--
View this message in context:
http://www.nabble.com/Slow-maven-compile-after-upgrading-JDK-from-1.5-to-1.6-tp23501164p23520344.html
What I would like to be able to do with Maven is:
Create an SVN tag, e.g. myproject-0.9-RC1 from current code in trunk
(or perhaps a branch)
Create and test the release candidate from the tag.
Publish the release candidate somewhere temporarily so others can
check if the release candidate is
I suppose you can use release:prepare and perform multiple times if you give
the RC version number when asked ?
http://maven.apache.org/guides/mini/guide-releasing.html
On Wed, May 13, 2009 at 8:55 AM, sebb seb...@gmail.com wrote:
What I would like to be able to do with Maven is:
Create an
I am curious about this too. I do know of the staging repository option
of the release plugin [1] but I have not actually used it yet. I don't
think it does everything you are looking for.
The pro version of Nexus has a staging suite [2] and this probably has
what you are looking for but isn't
Use the release:stage goal to create your release candidates. If you find a
bug, you just have to release:rollback and rename the tag from finalName
to finalName_RCx
2009/5/13 Fabien KRUBA fabien.kr...@gmail.com
I suppose you can use release:prepare and perform multiple times if you
give
the
So what is the extact work flow?
1. Run release:stage with a version like myproject-0.9-RC1
2. When problems are found, rollback, fix the problem and run
release:stage again, incrementing RC2, 3, etc
3. When no more problems are found with the RC, perform a rollback and
then a release:perform
1. release:stage with the target version 0.9 (renaming a released JAR may
have some strange side-effects)
test, test, test ..
-- all fine ? you've got it
-- some bugs : release:rollback , fix and back to step 1.
You only have to rename (or remove) the tag created in SCM for the release
Have you told your antivirus to trust the new install of java?
2009/5/13 j_ri jochen.riedlin...@l-bank.de
I tried with JDK 6 Update 10 and JDK 6 Update 13(with JDK 5 Update 11
everything was fine)
OS is Windows XP Pro SP2
I tried with Maven 2.0.7 and 2.1.0
--
View this message in
On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote:
Use the release:stage goal to create your release candidates. If you find a
bug, you just have to release:rollback and rename the tag from finalName
to finalName_RCx
So are you saying:
create tag myproject-0.9
...
rename tag to
From my understanding your steps would work if your staging repository
is the same as your release repository. But how about if they are
different? Are your proposing some kind of copying to the release repo
once you have determined a RC is fine?
---
Todd Thiessen
-Original Message-
On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote:
1. release:stage with the target version 0.9 (renaming a released JAR may
have some strange side-effects)
test, test, test ..
-- all fine ? you've got it
-- some bugs : release:rollback , fix and back to step 1.
You only
On 13-May-09, at 9:09 AM, Todd Thiessen wrote:
I am curious about this too. I do know of the staging repository
option
of the release plugin [1] but I have not actually used it yet. I don't
think it does everything you are looking for.
The pro version of Nexus has a staging suite [2] and
With this approach, all RC tags (and the final one) point to a source code
that generate the finalName artifact.
more complete sample
from trunk 1.0-SNAPSHOT
release:prepare version = 1.0
release:stage
-- tag = 1.0
-- artifact = foo-1.0.jar, deployed on staging repository
test, test, test BUG
Jeff Mutonho wrote:
Just add typewar/type below the version tag in your dependency
Thanks! That did it.
--
View this message in context:
http://www.nabble.com/Newbie---EAR-plugin-can%27t-find-my-war-file.-tp23510712p23522305.html
Sent from the Maven - Users mailing list archive at
Hmm. Doesn't renaming the tag mess up the tag? For instance the folder
name would be 1.0-RC1 but the POM for the project would say 1.0.
Something doesn't smell right with that ;-).
---
Todd Thiessen
-Original Message-
From: nicolas de loof [mailto:nicolas.del...@gmail.com]
Sent:
On 13-May-09, at 8:55 AM, sebb wrote:
What I would like to be able to do with Maven is:
Create an SVN tag, e.g. myproject-0.9-RC1 from current code in trunk
(or perhaps a branch)
Sure standard release:prepare from a trunk or more likely a branch.
For Maven itself we always use a branch,
Yes, the 1.0-RC1 tag generate a 1.0 artifact, don't you expect your RC to be
the EXACT artifact candidate ?
Doesn't smell right to me to test some 1.0-RCx jar and the rename it by
hand to 1.0. What to do if there is any side-effect ? Do I need to run all
my tests for second time ?
2009/5/13 Todd
On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote:
With this approach, all RC tags (and the final one) point to a source code
that generate the finalName artifact.
more complete sample
Yes, but AFAICS the tag 1.0 points to different code at different
times, so does not uniquely
On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote:
Yes, the 1.0-RC1 tag generate a 1.0 artifact, don't you expect your RC to be
the EXACT artifact candidate ?
I said to rename *if necessary*; I don't know how Maven derives the
artifact name so I don't know if it can drop the -RC
I would not recommend the release:stage or the release:perform with an
alternate repository. Maven used to do the latter which also required
the use of the stage plugin which is terrible (I know because I wrote
it).
If you are going to take something and potentially expose it to a
large
On 13-May-09, at 10:11 AM, sebb wrote:
On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote:
With this approach, all RC tags (and the final one) point to a
source code
that generate the finalName artifact.
more complete sample
Yes, but AFAICS the tag 1.0 points to different code
Hello,
I'd like to comment on this - maven is able to deal with cyclic
dependencies, but You have to do this cunningly.
It's not a good pattern, but it happens, and I would be willing to change
the statement that 'maven is not able to deal with cyclic'.
Here is how it goes:
project A - you
On 13/05/2009, Jason van Zyl jvan...@sonatype.com wrote:
On 13-May-09, at 10:11 AM, sebb wrote:
On 13/05/2009, nicolas de loof nicolas.del...@gmail.com wrote:
With this approach, all RC tags (and the final one) point to a source
code
that generate the finalName artifact.
more
No, our antivirus is configured to trust nothing;-) we didn't configure it to
trust the old java and so the new java isn't configured as trustet either.
But I'll try after I found an admin who does ist for me (I'm working in a
bank.)
Today we noticed while checking the log output of running
Try building them in the same reactor and Maven will say something like:
circular dependencies are not supported
2009/5/13 kretes kre...@gazeta.pl
Hello,
I'd like to comment on this - maven is able to deal with cyclic
dependencies, but You have to do this cunningly.
It's not a good
I didn't see one, so I added one. Refer to
http://jira.codehaus.org/browse/MWAR-194.
Thanks.
Brad
-Original Message-
From: Mark Hobson [mailto:markhob...@gmail.com]
Sent: Wednesday, May 13, 2009 3:37 AM
To: Maven Users List
Subject: Re: War Overlays and Conflicting Jars
2009/5/12 Brad
Hi All,
I am just wondering what is the best way to build a set of Eclipse
plugins using Maven? Via Google I discovered Tycho, but what I do not
like about Tycho is that it is essentially a separate, experimental
Maven 3 installation, rather than a plugin for Maven 2. Unfortunately
this
I have a project where my root project has child1, child2 etc... Each child
has child11, child12, child21 etc..
I would like to execute update-child-modules so versions across all child
projects are updated. Is this possible?
--
View this message in context:
just so you know what update-child-modules does...
if the child references the *wrong version of the parent* then
update-child-modules will fix your child poms for you.
it is just for fixing a broken reactor.
You are probably looking for update-properties as that is really the only
way
Actually, I am trying to use versions plugin to synchronize dependencies
across all projects in a hierarchy, since I wish to release all projects
with same version number.
update-child-modules works, but the only problem is that I have to execute
the goal on all parent poms.
Since I have a
Hello
I am using the Webstart plugin to distribute a Swing application. Works fine
untill I need to issue a new version of my application.
The application gets download onto the client machine correctly, but then
web start fails with the following message Error: JAR resources in JNLP
file are
Hi,
We use the war plugin in our build process and use the overlay mechanism to
merge the contents of some other war files to create the final deliverable.
I'm looking for a way to insert some steps that will run (as a maven plugin)
during the war plugin -- specifically, after the overlay steps
This bug describes the problem: http://jira.codehaus.org/browse/SUREFIRE-535
with the summary of surefire tries to treat nested classes, even anonymous
ones, as test classes?. I would encourage those who have trouble with this
issue to vote for that bug.
Apologies for re-awakening a dead
Hi,
I have a file put in resource like the following:
property name=hibernate.connection.url
value=jdbc:h2:tcp://localhost/${project.build.testOutputDirectory}/db/testdb
/
I use resource filtering to replaceing project.build.testOutputDirectory,
but the result becomes
property
Hi there
I am using Mavan 2.0.9 (although the problem occurs with older Maven
versions). I have a Maven-enabled project which uses Spring, Hibernate and
several Apache Commons libraries as well as Tomcat 5.5. I am using the
Eclipse IDE. I have followed the Maven installation instructions and
Hi,
I have created a maven plugin which uses another 2 plugins. I want to expose
another plugin's goal as my plugin goal, so that a user can access all goals of
the 2 plugins by just using my plugin.
For e.g.
pluginA - has goal generate
pluginB - has goal execute
I want to wrap pluginA and
49 matches
Mail list logo
