Corrupt surefire booter?
Hello Apache Maven community, In a Maven 3.3.3 and surefire 2.19 build I got this build failure on a CI server: error 02-Feb-2016 01:20:27java.lang.NoClassDefFoundError: org/apache/maven/surefire/report/LegacyPojoStackTraceWriter error 02-Feb-2016 01:20:27at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:133) error 02-Feb-2016 01:20:27Caused by: java.lang.ClassNotFoundException: org.apache.maven.surefire.report.LegacyPojoStackTraceWriter error 02-Feb-2016 01:20:27at java.net.URLClassLoader$1.run(URLClassLoader.java:370) error 02-Feb-2016 01:20:27at java.net.URLClassLoader$1.run(URLClassLoader.java:362) error 02-Feb-2016 01:20:27at java.security.AccessController.doPrivileged(Native Method) error 02-Feb-2016 01:20:27at java.net.URLClassLoader.findClass(URLClassLoader.java:361) error 02-Feb-2016 01:20:27at java.lang.ClassLoader.loadClass(ClassLoader.java:424) error 02-Feb-2016 01:20:27at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) error 02-Feb-2016 01:20:27at java.lang.ClassLoader.loadClass(ClassLoader.java:357) error 02-Feb-2016 01:20:27... 1 more error 02-Feb-2016 01:20:27Caused by: java.util.zip.ZipException: error reading zip file error 02-Feb-2016 01:20:27at java.util.zip.ZipFile.read(Native Method) error 02-Feb-2016 01:20:27at java.util.zip.ZipFile.access$1400(ZipFile.java:61) error 02-Feb-2016 01:20:27at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717) error 02-Feb-2016 01:20:27at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:420) error 02-Feb-2016 01:20:27at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) error 02-Feb-2016 01:20:27at sun.misc.Resource.getBytes(Resource.java:124) error 02-Feb-2016 01:20:27at java.net.URLClassLoader.defineClass(URLClassLoader.java:462) error 02-Feb-2016 01:20:27at java.net.URLClassLoader.access$100(URLClassLoader.java:73) error 02-Feb-2016 01:20:27at java.net.URLClassLoader$1.run(URLClassLoader.java:368) error 02-Feb-2016 01:20:27... 7 more error 02-Feb-2016 01:20:27Exception in thread "main" java.lang.NoClassDefFoundError: org/apache/maven/surefire/booter/ForkedBooter$5 error 02-Feb-2016 01:20:27at org.apache.maven.surefire.booter.ForkedBooter.exit(ForkedBooter.java:217) error 02-Feb-2016 01:20:27at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:150) error 02-Feb-2016 01:20:27Caused by: java.lang.ClassNotFoundException: org.apache.maven.surefire.booter.ForkedBooter$5 error 02-Feb-2016 01:20:27at java.net.URLClassLoader$1.run(URLClassLoader.java:370) error 02-Feb-2016 01:20:27at java.net.URLClassLoader$1.run(URLClassLoader.java:362) error 02-Feb-2016 01:20:27at java.security.AccessController.doPrivileged(Native Method) error 02-Feb-2016 01:20:27at java.net.URLClassLoader.findClass(URLClassLoader.java:361) error 02-Feb-2016 01:20:27at java.lang.ClassLoader.loadClass(ClassLoader.java:424) error 02-Feb-2016 01:20:27at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:331) error 02-Feb-2016 01:20:27at java.lang.ClassLoader.loadClass(ClassLoader.java:357) error 02-Feb-2016 01:20:27... 2 more error 02-Feb-2016 01:20:27Caused by: java.util.zip.ZipException: error reading zip file error 02-Feb-2016 01:20:27at java.util.zip.ZipFile.read(Native Method) error 02-Feb-2016 01:20:27at java.util.zip.ZipFile.access$1400(ZipFile.java:61) error 02-Feb-2016 01:20:27at java.util.zip.ZipFile$ZipFileInputStream.read(ZipFile.java:717) error 02-Feb-2016 01:20:27at java.util.zip.ZipFile$ZipFileInflaterInputStream.fill(ZipFile.java:420) error 02-Feb-2016 01:20:27at java.util.zip.InflaterInputStream.read(InflaterInputStream.java:158) error 02-Feb-2016 01:20:27at sun.misc.Resource.getBytes(Resource.java:124) error 02-Feb-2016 01:20:27at java.net.URLClassLoader.defineClass(URLClassLoader.java:462) error 02-Feb-2016 01:20:27at java.net.URLClassLoader.access$100(URLClassLoader.java:73) error 02-Feb-2016 01:20:27at java.net.URLClassLoader$1.run(URLClassLoader.java:368) error 02-Feb-2016 01:20:27... 8 more Few other builds before and after broken one use clean workspace and so far didn't have this issue yet. I'd like to understand what could be root cause of the issue and if it is likely to occur in future, and how to fix/prevent it. So, what could cause this issue? I checked local repo on agent that ran the failed build, at least now, surefire-booter-2.19 jar itself is not corrupt there. If I
Re: Open Source Best Practices with Maven - distributionManagement
Hello Eric, I'd consider using Sonatype OSS with Sonatype OSS parent pom and everything that goes along (see more details at https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide) For OSS development maybe use private (and not local) Nexus as proxy only, with mirrors defined in local settings.xml, but publish both snapshots and releases to Sonatype OSS repositories which get synced to Maven Central. Why run Nexus on local machine? To control dependencies and their metada for yourself only? Still looks as overkill to me, if you're the sole user and plan on developing OSS. You already have local repository, and you should have same experience as your OSS users (so no custom local metadata of dependencies, depend only on stuff available on Maven Central, with metadata as it is published on Maven Central). Kind regards, Stevo Slavic On Wed, Mar 19, 2014 at 9:23 PM, Eric Kolotyluk eric.koloty...@gmail.comwrote: Does anyone know of any good documentation on 'Open Source Best Practices with Maven' For example, in my POM, I want to set up distributionManagement downloadUrlhttp://localhost:8081/nexus/content/groups/public /downloadUrl repository uniqueVersionfalse/uniqueVersion idnexus-kolotyluk/id nameLocal Release Repository/name urlhttp://localhost:8081/nexus/content/repositories/releases/url layoutdefault/layout /repository snapshotRepository idnexus-kolotyluk/id nameLocal Snapshot Repository/name urlhttp://localhost:8081/nexus/content/repositories/snapshots/url layoutdefault/layout /snapshotRepository /distributionManagement But that is my local repository on my development computer. If I want to push my project to Maven Central some day, I don't think I want this in my POM. Should I put this in a parent POM, or inside a profile of my settings.xml file? If I put it in a parent POM, then I need to push that to Maven Central too, so that does not sound like a good idea. Cheer, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: New Maven video course!
http://www.packtpub.com/getting-started-with-apache-maven/video On Wed, Oct 2, 2013 at 10:53 PM, John Dix john@amdocs.com wrote: Link? -Original Message- From: Russell Gold [mailto:r...@gold-family.us] Sent: Wednesday, October 02, 2013 3:36 AM To: Maven Users List Subject: New Maven video course! I'd like to mention the release of my video course, Getting Started with Apache Maven, now available from PackT publications. It's a bit over two hours long and takes the viewer from installation of the tool through development of multi-module projects and websites. Check it out! - Author, Getting Started with Apache Maven Come read my webnovel, Take a Lemon http://www.takealemon.com, and listen to the Misfile radio play http://www.fuzzyfacetheater.com/misfile/ ! This message and the information contained herein is proprietary and confidential and subject to the Amdocs policy statement, you may review at http://www.amdocs.com/email_disclaimer.asp - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Which minify plugin do you use?
https://code.google.com/p/wro4j/ https://code.google.com/p/wro4j/wiki/MavenPlugin On Mon, Sep 30, 2013 at 5:45 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: I use jszip.org but then I'm biased, and I have to put some cycles into getting it past -alpha- and ready for beta... and work has been distracting me for some time... should be getting some time shortly (though perhaps after the end of the month if I am realistic) On 30 September 2013 16:41, Peter Kahn citizenk...@gmail.com wrote: Hi all, Which plugin to use to minify javascript (reduce size, improve load times)? I found three candidates two of which seem inactive but I'm unsure if they are inactive because there's not much to do or because they were abandoned. What do you use? * http://mojo.codehaus.org/webminifier-maven-plugin/ (1.0.1 2012-05-15)*INACTIVE* * http://alchim.sourceforge.net/yuicompressor-maven-plugin/index.html(1.1 2010-09-22) *INACTIVE* * http://samaxes.github.io/minify-maven-plugin/ (1.7.2 2-13-09-08) *ACTIVE* Thanks Peter -- Peter Kahn citizenk...@gmail.com http://www.google.com/profiles/citizenkahn Awareness - Intention - Action
Re: [surefire] Combining test, runOrder and forkCount
Thanks Andreas,
Removing parallel=classes did the trick for timely console reporting.
Having parallel=classes didn't bother m-surefire-p in 2.15 and earlier.
With forkCount 1 and reuseForks = false, parallel=classes should just be
ignored. But, as long as there is solution, I'm fine.
IMO specifying test parameter shouldn't disable the ordering (runOrder),
since specifying test parameter (by docs) is equivalent to specifying
includes patterns in pom, and includes should be used only to filter
scanned test classes, ordering should be applied after scanning, and before
executing test classes.
I understand that there are no guarantees on order when only two test
classes are run in parallel with forkCount 1.
Still if runOrder is applied before forking VMs and forked VMs as you
describe poll for next test class to execute, and I run a dozen of tests
(specified with test parameter) each of which takes different number of
more than few seconds to finish, and I have forkCount set to 2, I'd expect
runOrder to be somewhat respected - for the first two tests which get run
it would be random, but for the rest it should be pretty much in specified
runOrder, until two finish at roughly same time and there is (again as on
beginning) concurrency which test class will run next. Do you agree?
I tried that (test specifying dozen of test classes, forkCount at 2,
reuseForks at false, and different runOrder settings), and still I don't
see runOrder being respected.
Btw my original suspicion, that the two of Apache Mahout tests do not run
well together, was wrong - failing test had a bug, it makes use of random
number generator, but didn't set test seed to make execution deterministic.
Kind regards,
Stevo Slavic.
On Fri, Aug 30, 2013 at 8:06 AM, Andreas Gudian andreas.gud...@gmail.comwrote:
I'll have to check the code, but I'm pretty sure that the order of the test
classes to be handed over to the forked VMs is supposed to be what was is
specified with runOrder.
However, using -Dtest= might disable the ordering - but again, I'd have to
check the code.
Bit there's more: when having two classes to test and two forked VMs, there
is no real way to tell which test comes first. Both VMs are started right
away and only when the are up and running and ready to execute a test, they
ask the main process for one test class. Which VM will be the first to get
a class is quite random.
For the delayed reporting to console, try removing parallel=classes from
the config. IThe classes-setting has no effect when forking to more than
one fork anyway. If the output is still delayed then, create a bug-report,
please.
Am Donnerstag, 29. August 2013 schrieb Stevo Slavić :
Hello Apache Maven community,
To reproduce random failing test issue, I'm trying to run two tests in
parallel, but start running them in specific order. Problem is that
runOrder (added via SUREFIRE-614) doesn't seem to be respected, at least
not when forkCount and/or test is specified as well.
When trying to run two tests from Apache Mahout core module (trunk), I
cannot get surefire to run them in reverse alphabetical order.
Regardless if I run:
mvn -Dtest=*KMeansTest -DrunOrder=reversealphabetical test
or
mvn -Dtest=*KMeansTest -DrunOrder=alphabetical test
the two tests which match the pattern always get run in alphabetical
order:
---
T E S T S
---
Running org.apache.mahout.clustering.streaming.cluster.BallKMeansTest
Running
org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 66.706
sec
- in org.apache.mahout.clustering.streaming.cluster.BallKMeansTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 82.15
sec -
in org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest
Results :
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
Surefire 2.15 is used, and configuration is:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
forkCount1.5C/forkCount
reuseForksfalse/reuseForks
threadCount1/threadCount
perCoreThreadCountfalse/perCoreThreadCount
parallelclasses/parallel
argLine-Xmx512m/argLine
testFailureIgnorefalse/testFailureIgnore
redirectTestOutputToFiletrue/redirectTestOutputToFile
systemPropertyVariables
mahout.test.directory${project.build.directory}/mahout.test.directory
/systemPropertyVariables
/configuration
/plugin
When I use latest surefire 2.16, outcome is even more odd - output that
any
of the tests is running takes longer to render, it seems to be rendered
together with info that test has completed, so by looking
[surefire] Combining test, runOrder and forkCount
Hello Apache Maven community,
To reproduce random failing test issue, I'm trying to run two tests in
parallel, but start running them in specific order. Problem is that
runOrder (added via SUREFIRE-614) doesn't seem to be respected, at least
not when forkCount and/or test is specified as well.
When trying to run two tests from Apache Mahout core module (trunk), I
cannot get surefire to run them in reverse alphabetical order.
Regardless if I run:
mvn -Dtest=*KMeansTest -DrunOrder=reversealphabetical test
or
mvn -Dtest=*KMeansTest -DrunOrder=alphabetical test
the two tests which match the pattern always get run in alphabetical order:
---
T E S T S
---
Running org.apache.mahout.clustering.streaming.cluster.BallKMeansTest
Running org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 66.706 sec
- in org.apache.mahout.clustering.streaming.cluster.BallKMeansTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 82.15 sec -
in org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest
Results :
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
Surefire 2.15 is used, and configuration is:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
forkCount1.5C/forkCount
reuseForksfalse/reuseForks
threadCount1/threadCount
perCoreThreadCountfalse/perCoreThreadCount
parallelclasses/parallel
argLine-Xmx512m/argLine
testFailureIgnorefalse/testFailureIgnore
redirectTestOutputToFiletrue/redirectTestOutputToFile
systemPropertyVariables
mahout.test.directory${project.build.directory}/mahout.test.directory
/systemPropertyVariables
/configuration
/plugin
When I use latest surefire 2.16, outcome is even more odd - output that any
of the tests is running takes longer to render, it seems to be rendered
together with info that test has completed, so by looking at build log
output it may appear as if tests were not running in parallel even though
they did:
---
T E S T S
---
Running org.apache.mahout.clustering.streaming.cluster.BallKMeansTest
Tests run: 3, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 59.347 sec
- in org.apache.mahout.clustering.streaming.cluster.BallKMeansTest
Running org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest
Tests run: 8, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 74.766 sec
- in org.apache.mahout.clustering.streaming.cluster.StreamingKMeansTest
Results :
Tests run: 11, Failures: 0, Errors: 0, Skipped: 0
Here is my mvn --version output:
[sslavic@laptop core]$ mvn --version
Apache Maven 3.1.0 (893ca28a1da9d5f51ac03827af98bb730128f9f2; 2013-06-28
04:15:32+0200)
Maven home: /home/sslavic/work/tools/apache-maven
Java version: 1.7.0_25, vendor: Oracle Corporation
Java home: /usr/java/jdk1.7.0_25/jre
Default locale: en_US, platform encoding: UTF-8
OS name: linux, version: 3.10.9-200.fc19.x86_64, arch: amd64, family:
unix
Am I doing something wrong or is this behavior bug (or two bugs) in
surefire?
Kind regards,
Stevo Slavic.
Re: Misisng apache-maven-3.0.5-bin.zip from archive.apache.org
It's synced now. Thanks Olivier! Am I right to assume that this duplication is not likely to be present in future and that Apache Maven binaries will be published only on new path/URL? Kind regards, Stevo Slavić. On Fri, May 24, 2013 at 3:59 PM, Olivier Lamy ol...@apache.org wrote: ok. I have copied the 3.0.5 files from http://archive.apache.org/dist/maven/maven-3/3.0.5/binaries/ to http://archive.apache.org/dist/maven/binaries/ I don't know how long it will take to be sync. (maybe not too long) 2013/5/24 Stevo Slavić ssla...@gmail.com: Clear, thanks Olivier! I see there are duplications of 3.0.4 release, it's present on both old and new path. Btw, that change broke Jenkins CI support for Apache Maven auto-installations (see https://issues.jenkins-ci.org/browse/JENKINS-17220). It needs to be extended to also support new path and new layout. Kind regards, Stevo Slavić. On Fri, May 24, 2013 at 3:21 PM, Olivier Lamy ol...@apache.org wrote: 2013/5/24 Stevo Slavić ssla...@gmail.com: Hello Apache Maven community, Does anyone know why is Apache maven 3.0.5 binary archive missing from archive.apache.org? All the previous releases can be found in http://archive.apache.org/dist/maven/binaries/ but not 3.0.5. see http://archive.apache.org/dist/maven/maven-3/ path has changed since 3.0.4 Kind regards, Stevo Slavić. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Misisng apache-maven-3.0.5-bin.zip from archive.apache.org
Hello Apache Maven community, Does anyone know why is Apache maven 3.0.5 binary archive missing from archive.apache.org? All the previous releases can be found in http://archive.apache.org/dist/maven/binaries/ but not 3.0.5. Kind regards, Stevo Slavić.
Re: Misisng apache-maven-3.0.5-bin.zip from archive.apache.org
Clear, thanks Olivier! I see there are duplications of 3.0.4 release, it's present on both old and new path. Btw, that change broke Jenkins CI support for Apache Maven auto-installations (see https://issues.jenkins-ci.org/browse/JENKINS-17220). It needs to be extended to also support new path and new layout. Kind regards, Stevo Slavić. On Fri, May 24, 2013 at 3:21 PM, Olivier Lamy ol...@apache.org wrote: 2013/5/24 Stevo Slavić ssla...@gmail.com: Hello Apache Maven community, Does anyone know why is Apache maven 3.0.5 binary archive missing from archive.apache.org? All the previous releases can be found in http://archive.apache.org/dist/maven/binaries/ but not 3.0.5. see http://archive.apache.org/dist/maven/maven-3/ path has changed since 3.0.4 Kind regards, Stevo Slavić. -- Olivier Lamy Ecetera: http://ecetera.com.au http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Importing poms and scoping dependencies
Hello Apache Maven community, Is there a way to import dependencies from dependencyManagement section of a pom artifact, but also configure default scope for all of the imported dependencies (without actually specifying all of them as dependencies)? Kind regards, Stevo.
Re: Getting name of POM file?
Hello Dreier, Maybe I missed something, but I couldn't find this in maven docs or sources. Nevertheless, it seems to me that you're trying to solve wrong problem. Why do you need this info? Couldn't a workaround with same property but different pom file specific value (one for regular, other for alternative pom file) be applicable in your use case? Kind regards, Stevo. On Wed, May 16, 2012 at 11:24 AM, Dreier Ruediger ruediger.dre...@bdal.dewrote: Hello! Is it somehow possible to get the name of the POM file (which might not be POM.xml if Maven was called with –f) inside a POM file (e.g. as parameter for other plugins)? Thanks for any help, i.A. Rüdiger Dreier Project Manager Bruker Daltonik GmbH Fahrenheitstr. 4 28359 Bremen, Germany Phone: +49 421 2205-393 Fax: +49 421 2205-3005 ruediger.dre...@bdal.demailto:ruediger.dre...@bdal.de www.bruker.comhttp://www.bruker.com/ Sitz der Gesellschaft / Registered Office Bremen; Handelsregister Amtsgericht Bremen HRB 8150 / Commercial Register District Court Bremen HRB 8150; Geschäftsführer / Managing Directors: Gerd Hülso, Sebastian Meyer-Plath, Stefan Ruge, Ian Sanders, Ph. D., Dr. Michael Schubert Haftungsausschluss: Die Bruker Daltonik GmbH ist nicht verantwortlich für die ordnungsgemäße, vollständige und verzögerungsfreie Übertragung der Nachricht. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er unsererseits durch einen Brief oder ein Fax entsprechend bestätigt wird. Disclaimer: Bruker Daltonik GmbH is not responsible for correct, complete and timely transmission of this message. The content of this e-mail, including any attachments, is only legally binding if confirmed by Bruker Daltonik GmbH by letter or fax
Re: Getting name of POM file?
Thanks Stephen,
So in pom.xml one can reference it using ${project.file}
That property is listed on
http://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuide but in one
of the user comments. Comment points to maven 2 resource as reference to
where the info was found, here is link to equivalent file in Maven 3
sources:
http://svn.apache.org/viewvc/maven/maven-3/trunk/maven-compat/src/main/resources/META-INF/maven/plugin-expressions/project.paramdoc.xml?view=markup
Kind regards,
Stevo.
2012/5/18 Stephen Connolly stephen.alan.conno...@gmail.com
MavenProject.getFile()
On Wednesday, 16 May 2012, Dreier Ruediger wrote:
Hello!
Is it somehow possible to get the name of the POM file (which might not
be
POM.xml if Maven was called with –f) inside a POM file (e.g. as parameter
for other plugins)?
Thanks for any help,
i.A. Rüdiger Dreier
Project Manager
Bruker Daltonik GmbH
Fahrenheitstr. 4
28359 Bremen, Germany
Phone: +49 421 2205-393
Fax: +49 421 2205-3005
ruediger.dre...@bdal.de javascript:;mailto:ruediger.dre...@bdal.de
javascript:;
www.bruker.comhttp://www.bruker.com/
Sitz der Gesellschaft / Registered Office Bremen; Handelsregister
Amtsgericht Bremen HRB 8150 / Commercial Register District Court Bremen
HRB
8150; Geschäftsführer / Managing Directors: Gerd Hülso, Sebastian
Meyer-Plath, Stefan Ruge, Ian Sanders, Ph. D., Dr. Michael Schubert
Haftungsausschluss: Die Bruker Daltonik GmbH ist nicht verantwortlich für
die ordnungsgemäße, vollständige und verzögerungsfreie Übertragung der
Nachricht. Der Inhalt der E-Mail ist nur rechtsverbindlich, wenn er
unsererseits durch einen Brief oder ein Fax entsprechend bestätigt wird.
Disclaimer: Bruker Daltonik GmbH is not responsible for correct, complete
and timely transmission of this message. The content of this e-mail,
including any attachments, is only legally binding if confirmed by Bruker
Daltonik GmbH by letter or fax
Re: module question
Hello Robert, My guess is that the other pom defines a repository which cannot be accessed (e.g. due to security constraints). Having failing build output, not to mention pom files themselves, would help a lot to better diagnose root cause. Regards, Stevo. On Apr 18, 2012 1:17 AM, Robert Egan robert.e...@aciworldwide.com wrote: I have a POM hat works correctly when it is the 'root' POM but fails to resolve a dependency when it is invoked as a module from another POM. How does one go about resolving an issue like this?
Disabling resolving test scoped dependencies when tests are skipped via maven.test.skip system property
Hello Maven community, Why does Maven (3.0.3) resolve test scoped dependencies when tests compilation and execution is skipped via maven.test.skip system property? I'm trying to achieve this by defining a profile with all test scope dependencies declared in it only. Profile is activated when maven.test.skip system property is not defined. Would be more precise if I could specify activation to be when that property is not defined or is set to false but that doesn't seem to be possible (no compound expressions in single property, no multiple properties in single activation) or am I missing something? Kind regards, Stevo.
Re: Disabling resolving test scoped dependencies when tests are skipped via maven.test.skip system property
OK, thanks for explaining! A module's tests are supposed to be run only by part of the team. For others not even test dependencies are accessible, so just disabling compiling and executing tests was not enough. Resolved this with a profile and putting dependencies of those tests there. Kind regards, Stevo. On Tue, Jan 17, 2012 at 5:06 PM, Olivier Lamy ol...@apache.org wrote: Hello, 2012/1/17 Stevo Slavić ssla...@gmail.com: Hello Maven community, Why does Maven (3.0.3) resolve test scoped dependencies when tests compilation and execution is skipped via maven.test.skip system property? That's something will happen with all maven 2.x or 3.x versions. Why because maven use something generic which is kind of plugin metadata which contains the dependencies level/scope needed. So at this stage when resolving dependencies for the plugin, maven core doesn't have any idea on any skip or other plugin parameters or what the plugin does. How does it work. See source http://svn.apache.org/repos/asf/maven/surefire/trunk/maven-surefire-plugin/src/main/java/org/apache/maven/plugin/surefire/SurefirePlugin.java You will see an annotation @requiresDependencyResolution test (this the metadata). So maven core only knows he need to resolve dependencies even if the mojo have a skip or a shutdownMachine :-) parameter I'm trying to achieve this by defining a profile with all test scope dependencies declared in it only. Profile is activated when maven.test.skip system property is not defined. Would be more precise if I could specify activation to be when that property is not defined or is set to false but that doesn't seem to be possible (no compound expressions in single property, no multiple properties in single activation) or am I missing something? Kind regards, Stevo. -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Project specific alternate settings.xml
Hello Maven users, Maven has notion of global (M2_HOME/conf/settings.xml), user settings (typically in ~/.m2/settings.xml), and build specific alternate settings (one specified in build command using -s switch). What does community think, should there be a convention automated in Maven logic of using project specific alternate settings? E.g. settings.xml if present in same path as pom.xml from where build is started could be used as alternate settings for that project build. Dunno about community, but lots of my projects use project specific Maven settings and repeating -s switch all the time is not nice, but also merging multiple different project settings into user settings.xml is even less desired - want to make sure that project will build not just for my environment but for other devs and CI too. Such project specific settings file could be used automatically buy CI servers as well, just by checking out source code with settings.xml included, and running Maven build. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Project specific alternate settings.xml
Server authentication for example, it can not be specified in pom. Projects use project/client specific repository or repositories - wouldn't like to mix settings of multiple projects in user settings, to minimize chance of accessing repositories and resolving dependencies from them in a project where they're not supposed to be used from. Same project specific settings file used by all developers on project, and CI, with credentials referenced via environment variables - each developer specifies his own credentials, works for CI build jobs. Another one is to be able to specify project specific local repository in project specific settings.xml, to minimize a chance of it works for me scenario, just because someone was building another project before build would pass for him but not for others. Regards, Stevo. On Tue, Oct 11, 2011 at 6:32 PM, Ron Wheeler rwhee...@artifact-software.com wrote: What sort of things do you want at the project level that can not be handled by a parent pom? Ron On 11/10/2011 9:56 AM, Stevo Slavić wrote: Hello Maven users, Maven has notion of global (M2_HOME/conf/settings.xml), user settings (typically in ~/.m2/settings.xml), and build specific alternate settings (one specified in build command using -s switch). What does community think, should there be a convention automated in Maven logic of using project specific alternate settings? E.g. settings.xml if present in same path as pom.xml from where build is started could be used as alternate settings for that project build. Dunno about community, but lots of my projects use project specific Maven settings and repeating -s switch all the time is not nice, but also merging multiple different project settings into user settings.xml is even less desired - want to make sure that project will build not just for my environment but for other devs and CI too. Such project specific settings file could be used automatically buy CI servers as well, just by checking out source code with settings.xml included, and running Maven build. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Ron Wheeler President Artifact Software Inc email: rwhee...@artifact-software.com skype: ronaldmwheeler phone: 866-970-2435, ext 102 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-assembly-plugin, built-in/shared descriptors and custom classifier
Hello Maven users, It seems that when using built-in descriptors there is no way to specify custom classifier for produced assembly. single mojo has classifier parameter but it is marked as deprecated. http://maven.apache.org/plugins/maven-assembly-plugin/single-mojo.html If this can not be overridden, then it impacts use of custom shared descriptors ( http://maven.apache.org/plugins/maven-assembly-plugin/examples/sharing-descriptors.html ) classifier seems to have been deprecated in favor of using assembly id but one can not specify assembly id of built-in or shared descriptors. Is there maybe a workaround to inherit somehow built-in or shared assembly descriptor? I know about component descriptors, but AFAIK assembly descriptors (built-in or shared) can not be referenced as component descriptors. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-release-plugin and tag content
Hello Maven users, Can prepare-mojo of maven-release-plugin be configured which files and/or directories to include and/or exclude from the (svn) tag? Just like with -N submodules can be excluded from the release build, I'd like to exclude them from the tag as well, or in other words include only current module files in the tag. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-release-plugin and tag content
/ M1/ pom.xml M11/ pom.xml M111/ pom.xml M M1112 M12 and M1 can reference M11 as submodule with module../M11/module in modules section. I knew before that M11 could reference M1 as parent using relativePath../M1/pom.xml/relativePath. Modules which are always released together are on same scm tree and this is in line with Maven assumptions. With this structure aggregation works and using -N switch could be enough to limit release process to current module (tree) only, with only downside being that maven module and scm hierarchy do not match, but that's a minor anyway, mitigated with module naming strategy. Any other known downsides of this flat structure organization? Hopefully there will be no issues with plugins and this structure. Regards, Stevo. On Fri, Sep 9, 2011 at 4:53 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: no. - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 9 Sep 2011 04:15, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, Can prepare-mojo of maven-release-plugin be configured which files and/or directories to include and/or exclude from the (svn) tag? Just like with -N submodules can be excluded from the release build, I'd like to exclude them from the tag as well, or in other words include only current module files in the tag. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
application.xml generated in src
Hello maven users, All the plugins which generate sources or resources do generate them in build output directory (target), and by convention it is typically a directory named by generator within target/generated-sources or target/generated-resources. Correct me if wrong, IMO it's bad practice to have sources and resources generated under src directory. I have maven-ear-plugin:2.6 with custom modules section (and earSourceExcludes) configured - all the rest is default, including generateApplicationXml and generatedDescriptorLocation configuration parameters. Problem is whenever I build the project, application.xml gets generated in src/main/application/META-INF directory. Whenever version changes of referenced modules that application.xml gets automatically updated. Anyone have any ideas who and why is generating this application.xml in src/main/application/META-INF? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: application.xml generated in src
Small correction, instead of All the plugins which generate sources or resources do generate them in build output directory (target) ... should be All the plugins which generate sources or resources do generate them in build directory (target) ... Regards, Stevo. On Mon, Sep 5, 2011 at 2:22 PM, Stevo Slavić ssla...@gmail.com wrote: Hello maven users, All the plugins which generate sources or resources do generate them in build output directory (target), and by convention it is typically a directory named by generator within target/generated-sources or target/generated-resources. Correct me if wrong, IMO it's bad practice to have sources and resources generated under src directory. I have maven-ear-plugin:2.6 with custom modules section (and earSourceExcludes) configured - all the rest is default, including generateApplicationXml and generatedDescriptorLocation configuration parameters. Problem is whenever I build the project, application.xml gets generated in src/main/application/META-INF directory. Whenever version changes of referenced modules that application.xml gets automatically updated. Anyone have any ideas who and why is generating this application.xml in src/main/application/META-INF? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: application.xml generated in src
OK, thanks! On Mon, Sep 5, 2011 at 2:42 PM, Anders Hammar and...@hammar.net wrote: Thinking about this some more, I think it might actually be the wtp-m2e eclipse plugin that does this. You should ask on the m2e mailing list and Fred (the author) could quickly answer if it has been fixed in newer versions of that plugin. /Anders On Mon, Sep 5, 2011 at 14:35, Anders Hammar and...@hammar.net wrote: Are you using Eclipse and m2eclipse? If so, I think it is WTP. If you only build from CLI you don't have this problem, right? /Anders On Mon, Sep 5, 2011 at 14:22, Stevo Slavić ssla...@gmail.com wrote: Hello maven users, All the plugins which generate sources or resources do generate them in build output directory (target), and by convention it is typically a directory named by generator within target/generated-sources or target/generated-resources. Correct me if wrong, IMO it's bad practice to have sources and resources generated under src directory. I have maven-ear-plugin:2.6 with custom modules section (and earSourceExcludes) configured - all the rest is default, including generateApplicationXml and generatedDescriptorLocation configuration parameters. Problem is whenever I build the project, application.xml gets generated in src/main/application/META-INF directory. Whenever version changes of referenced modules that application.xml gets automatically updated. Anyone have any ideas who and why is generating this application.xml in src/main/application/META-INF? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to use default layout repository with maven 1
Use repository manager like Sonatype Nexus to proxy repositories with Maven 1 legacy layout as Maven 2 repositories. Regards, Stevo. On Tue, Aug 16, 2011 at 10:43 AM, amaresh mourya amaresh.mou...@gmail.com wrote: Thanks All. On Tue, Aug 16, 2011 at 1:58 PM, Lukas Theussl ltheu...@apache.org wrote: Manfred Moser wrote: On Mon, August 15, 2011 12:13 pm, amaresh mourya wrote: Hi All, Can I use default layout repository with Maven 1? By specifying following in my POM? repository idmaven2-repository/id nameRepository for Maven/name urlhttp://abc.net/maven/2//**url layoutdefault/layout /repository Please.. do NOT use Maven 1 anymore. Upgrade to Maven 3 or at least the latest version of Maven 2... ... and the answer to the question is 'no': http://jira.codehaus.org/** browse/MAVEN-1694 http://jira.codehaus.org/browse/MAVEN-1694 -Lukas manfred --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org --**--**- To unsubscribe, e-mail: users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Plugin version reported as missing even when it's specified
Hello Maven users,
When performing release of a pom project with release plugin
(release:perform) and goals parameter set to deploy, release plugin
checkouts tag and runs a build on it.
During that inner deploy build, a warning gets printed that a
maven-javadoc-plugin version is missing (see [1]).
Later during the deploy build it can be seen that correct (as
specified in pom) version of javadoc plugin is used.
Attached is pom from checked-out tag, and as one can see there version
is specified as in new configuration example (
http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration
).
I first thought that example is wrong (see
http://jira.codehaus.org/browse/MSITE-539 )
I'm using maven 3.0.3
Can anybody reproduce this behavior?
If this is a bug, to which Jira project should I report it? (Maven
itself http://jira.codehaus.org/browse/MNG or release plugin
http://jira.codehaus.org/browse/MRELEASE or site plugin
http://jira.codehaus.org/browse/MSITE )
Regards,
Stevo.
[1] build output fragment
D:\work\foo.bar.maven.parentmvn release:perform -Dgoals=deploy
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building Maven Parent 16-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-release-plugin:2.1:perform (default-cli) @
foo.bar.maven.parent ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C svn --non-interactive checkout
https://svn.foo.bar/maven/parent/tags/releases/foo.bar.m
aven.parent-15 D:\work\foo.bar.maven.parent\target\checkout
[INFO] Working directory: D:\work\foo.bar.maven.parent\target
[INFO] Executing goals 'deploy'...
[WARNING] Maven will be executed in interactive mode, but no input
stream has been configured for this MavenInvoker inst
ance.
[INFO] [INFO] Scanning for projects...
[INFO] [WARNING]
[INFO] [WARNING] Some problems were encountered while building the
effective model for foo.bar.maven:foo.bar.maven.parent:
pom:15
[INFO] [WARNING] 'build.plugins.plugin.version' for
org.apache.maven.plugins:maven-javadoc-plugin is missing.
[INFO] [WARNING]
[INFO] [WARNING] It is highly recommended to fix these problems
because they threaten the stability of your build.
[INFO] [WARNING]
[INFO] [WARNING] For this reason, future Maven versions might no
longer support building such malformed projects.
[INFO] [WARNING]
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] Building Maven Parent 15
[INFO] [INFO]
[INFO] [INFO]
[INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce
(enforce-versions) @ foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.1.2:jar (attach-sources) @
foo.bar.maven.parent
[INFO] [INFO]
[INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce
(enforce-versions) @ foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] maven-source-plugin:2.1.2:jar (attach-sources) @
foo.bar.maven.parent
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @
foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.8:jar (attach-javadocs) @
foo.bar.maven.parent ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java
classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0-beta-3:attach-descriptor
(attach-descriptor) @ foo.bar.maven.parent ---
project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
nameCorporate Maven Parent/name
groupIdfoo.bar.maven/groupId
artifactIdfoo.bar.maven.parent/artifactId
version15/version
packagingpom/packaging
prerequisites
maven3.0/maven
/prerequisites
properties
maven.compiler.source1.6/maven.compiler.source
maven.compiler.target${maven.compiler.source}/maven.compiler.target
project.build.sourceEncodingUTF-8/project.build.sourceEncoding
project.reporting.outputEncodingUTF-8/project.reporting.outputEncoding
maven.surefire.version2.9/maven.surefire.version
/properties
scm
connectionscm:svn:https://svn.foo.bar/maven/parent/tags/releases/foo.bar.maven.parent-15/connection
developerConnectionscm:svn:https://svn.foo.bar/maven/parent/tags/releases/foo.bar.maven.parent-15/developerConnection
urlhttps://svn.foo.bar/viewvc/maven/parent/tags/releases/foo.bar.maven.parent-15/url
/scm
distributionManagement
repository
idfoo.bar.repo/id
urlhttps://repo.foo.bar/content/repositories/foo-bar-repo/url
/repository
snapshotRepository
idfoo.bar.repo.snapshots/id
urlhttps://repo.foo.bar/content/repositories/foo-bar-repo.snapshots/url
/snapshotRepository
site
idfoo.bar.site/id
Re: Plugin version reported as missing even when it's specified
True, even though I don't explicitly make use of javadoc plugin in the build other than for the site generation, it's implicitly used by release:perform. Default value of http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile is true, so by default release:perform will at least try to create javadoc (and sources) artifact for the module, as part of the attempt missing version warning will be reported, and then actual javadoc (and sources) plugin will skip generating javadocs since module has pom packaging. Will add maven-javadoc-plugin to pluginManagement, and extra property to keep plugin version DRY. Thanks Anders! Regards, Stevo. On Fri, Jun 24, 2011 at 9:37 PM, Anders Hammar and...@hammar.net wrote: Quickly browsing through the pom I don't see that you have locked down the version of the javadoc plugin. You have done it for the site generating, but not for the build. /Anders On Fri, Jun 24, 2011 at 16:14, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When performing release of a pom project with release plugin (release:perform) and goals parameter set to deploy, release plugin checkouts tag and runs a build on it. During that inner deploy build, a warning gets printed that a maven-javadoc-plugin version is missing (see [1]). Later during the deploy build it can be seen that correct (as specified in pom) version of javadoc plugin is used. Attached is pom from checked-out tag, and as one can see there version is specified as in new configuration example ( http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration ). I first thought that example is wrong (see http://jira.codehaus.org/browse/MSITE-539 ) I'm using maven 3.0.3 Can anybody reproduce this behavior? If this is a bug, to which Jira project should I report it? (Maven itself http://jira.codehaus.org/browse/MNG or release plugin http://jira.codehaus.org/browse/MRELEASE or site plugin http://jira.codehaus.org/browse/MSITE ) Regards, Stevo. [1] build output fragment D:\work\foo.bar.maven.parentmvn release:perform -Dgoals=deploy [INFO] Scanning for projects... [INFO] [INFO] [INFO] Building Maven Parent 16-SNAPSHOT [INFO] [INFO] [INFO] --- maven-release-plugin:2.1:perform (default-cli) @ foo.bar.maven.parent --- [INFO] Checking out the project to perform the release ... [INFO] Executing: cmd.exe /X /C svn --non-interactive checkout https://svn.foo.bar/maven/parent/tags/releases/foo.bar.m aven.parent-15 D:\work\foo.bar.maven.parent\target\checkout [INFO] Working directory: D:\work\foo.bar.maven.parent\target [INFO] Executing goals 'deploy'... [WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker inst ance. [INFO] [INFO] Scanning for projects... [INFO] [WARNING] [INFO] [WARNING] Some problems were encountered while building the effective model for foo.bar.maven:foo.bar.maven.parent: pom:15 [INFO] [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing. [INFO] [WARNING] [INFO] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [INFO] [WARNING] [INFO] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [INFO] [WARNING] [INFO] [INFO] [INFO] [INFO] [INFO] [INFO] Building Maven Parent 15 [INFO] [INFO] [INFO] [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-versions) @ foo.bar.maven.parent --- [INFO] [INFO] [INFO] [INFO] maven-source-plugin:2.1.2:jar (attach-sources) @ foo.bar.maven.parent [INFO] [INFO] [INFO] [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-versions) @ foo.bar.maven.parent --- [INFO] [INFO] [INFO] [INFO] maven-source-plugin:2.1.2:jar (attach-sources) @ foo.bar.maven.parent [INFO] [INFO] [INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ foo.bar.maven.parent --- [INFO] [INFO] [INFO] [INFO] --- maven-javadoc-plugin:2.8:jar (attach-javadocs) @ foo.bar.maven.parent --- [INFO] [INFO] Not executing Javadoc as the project is not a Java classpath-capable package [INFO] [INFO] [INFO] [INFO] --- maven-site-plugin:3.0-beta-3:attach-descriptor (attach-descriptor) @ foo.bar.maven.parent --- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
Archetype catalog purpose
Hello Maven users, What's the purpose of archetype-catalog.xml file (especially on central repo) except to fall out of sync with archetype artifacts in the repository and prevent them from being used (easily)? E.g. central now has several Cargo 1.1.0 archetypes but they can not be resolved from central as archetypes by maven archetype plugin 2.0 because they are not listed in archetype-catalog.xml (latest there is 1.0.6). To use these archetypes (in repo but not in catalog) one has to resolve them first as plain dependencies, have maven crawl local repo, and then use them as archetypes from local repo. Why couldn't archetype artifacts be treated as any other plain Maven artifacts, why do they need to be cataloged? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Plugin dependencies resolution - from repository or from pluginRepository?
Hello Maven users, Maven dependecy:resolve-plugins resolved plugin dependency from repository and not from pluginRepository. Isn't that a bug? Plugin used is http://code.google.com/p/maven-annotation-plugin/ , version 2.0.2. It's available at central but not all of it's dependencies are there (another failure of central repo policy just as repository declaration in plugin's pom but that's a different issue). That plugin has dependency to org.jfrog.maven.annomojo:maven-plugin-tools-anno:1.4.0 which can be found on http://repo.jfrog.org/artifactory/plugins-releases-local repository. When I added that repository as pluginRepository, maven would fail to resolve the plugin's dependencies, but when I added that repository as dependency repository, dependency:resolve-plugins would pass. I'm using Maven 3.0.3, and dependency plugin 2.1. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-3.0.2 + maven-site-plugin-3.0-beta-3 + multi module projects (can't resolve module dependencies)
I'm also affected by this issue, when releasing project using maven-release-plugin, prepare goes well, perform fails as it detects site in distributionManagement and default goals run are deploy site-deploy so maven tries to generate and deploy site, but since site plugin tries to resolve something that's not installed/deployed yet, release:perform fails. One workaround could be to configure prepare mojo's http://maven.apache.org/plugins/maven-release-plugin/prepare-mojo.html#preparationGoals to be clean install instead of default clean verify, install is after verify, if verification fails install will not be performed, if verification is successful install will be performed and artifacts will be available in local repository, so as long as release:perform is run on same node/machine by same user as release:prepare, site should be generated and deployed; deploy will install/overwrite artifacts again in local repo and deploy them to remote repo. Regards, Stevo. On Wed, Apr 13, 2011 at 9:17 AM, Lukas Theussl ltheu...@apache.org wrote: That's an old issue, see http://jira.codehaus.org/browse/MSITE-171 and related tickets. -Lukas Andrew Hughes wrote: Hi All, Before each of the following test, I delete my project/module artifacts from my local repo The following works :) *mvn clean install * *mvn site* The following fails :( *mvn clean install site* The following also fails :( *mvn clean install site:site* The error I consistently get is: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project acme-project: failed to get Reports: Failed to execute goal on project acme-project-d: Could not resolve dependencies for project com.acme.project:acme-project-module-d:ejb:5.1.0-SNAPSHOT: *Could not find artifact com.acme.project:acme-project-module-a:jar:5.1.0-SNAPSHOT* in archiva (http://acme.com/repository/all/) - [Help 1] ...site appears to be running on the incorrect phase or build lifecycle. Consequently, the (module) dependencies have not been install/deployed to my local repository yet. Any idea's how I can fix this??? Cheers. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Plugin for changing build output directory
Hello Maven users, Is there a plugin with a goal for changing build output directory? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin for changing build output directory
It is possible to change build output directory during the build. E.g. cobertura-maven-plugin and emma-maven-plugin both have instrument goal which as side-effect changes build output directory with something like project.getBuild().setOutputDirectory( %some_path% ); where project is reference to MavenProject being built. They do that, but do not support configuration option to disable that behavior. Configuring build path in pom.xml won't help. Regards, Stevo. On Thu, Mar 10, 2011 at 10:49 AM, Anders Hammar and...@hammar.net wrote: Don't think that is possible to do during the build. Why not just change it in the pom? /Anders On Thu, Mar 10, 2011 at 10:29, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, Is there a plugin with a goal for changing build output directory? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: changes:jira-report - No report for missing PID
When browsing your JIRA project just hower over or copy URL of almost any link, and there you will find project's pid. Although maven needs pid (JIRA APIs require it) and not shorthand human-readable code, when configuring issueManagement/url I typically leave both pid and shorthand code in URL like in issueManagement systemJIRA/system urlhttp://jira.codehaus.org/browse/MCHANGES?pid=11212/url /issueManagement So it's somewhat human-readable for developers and maven (plugins) can use it. Regards, Stevo On Tue, Mar 8, 2011 at 1:56 PM, mehtak komal.me...@hcl.com wrote: Hi, I am trying to generate a jira-report for my project. I do not know the 5 digit PID of my project. Thus I am getting an empty report as my site output. But I have specified a 5 chars valid project name ID, which works perfect on the jira..com Here is my POM. As a maven output I always get a BUILD SUCCESSFUL. But the jira-report.html file has following error message: An error occured that made it impossible to generate this report. Please check the console for information on what might be the cause of this. POM.xml ... maven-project-info-reports-plugin 2.3.1 summary org.apache.maven.plugins maven-changes-plugin 2.3 Fix Version,Type,Key,Summary,Resolution Closed Fix Version DESC, Type 1000 jira-report ... JIRA http://jira.company.com/browse/ABCDE xyz http://jira.company.com/browse/ABCDE Please help. Also what is the connection between a Project name ABCDE and the PID. Is PID a must param to fetch the jira report? thanks, Komal -- View this message in context: http://maven.40175.n5.nabble.com/changes-jira-report-No-report-for-missing-PID-tp3413891p3413891.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository is down ...
http://repo1.maven.org/maven2/ works for me Regards, Stevo. On Tue, Mar 8, 2011 at 3:23 PM, Marcin Kuthan marcin.kut...@gmail.com wrote: Hi, I checked from two different physical location. Central repo is not responding ... Does anyone could help? -- Marcin m4enterprise.googlecode.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot retrieve parent snapshot pom, but can depend on it - why?
I doubt it is intentional behavior. You didn't mention which version of maven are you using, or maven-dependency-plugin - like with any OSS project, latest maven is the greatest, and configure plugin version in pluginManagement section. You also didn't provide snapshots repository definition snippet - maybe you're affected by default daily updatePolicy for snapshots; configure always or use -U switch when building. Regards, Stevo. On Sun, Feb 27, 2011 at 2:44 AM, sebb seb...@gmail.com wrote: I uploaded commons-parent POM 19-SNAPSHOT to the snapshot repo [1], and then deleted it from my local repo (because I want to test how it will work for others). When I try to depend on it as a parent, i.e. parent groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId version19-SNAPSHOT/version /parent I get the following error: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT Reason: Cannot find parent: org.apache.commons:commons-parent for project: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT for project org.home.mvnsample:mvnsample:jar:1.0- SNAPSHOT Yet when the POM depends on it as a dependency, i.e. dependency groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId version19-SNAPSHOT/version typepom/type /dependency it is downloaded without a problem. It looks as though Maven does not check snapshot repositories for a parent POM dependency. Is this true, and if so is it intentional? [1] http://repository.apache.org/snapshots/org/apache/commons/commons-parent/19-SNAPSHOT/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Import-scope-like behavior for plugins
Hello Apache Maven users, Is there a way to achieve behavior similar to import scope for dependencies, but for plugins, without inheriting another project? Would like to create pom projects with set of plugins with latest versions configured, one for each frequently used plugin provider (e.g. pom for apache maven core plugins, another pom for codehaus maven mojos, etc.) and then import these poms in plugin management. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cannot retrieve parent snapshot pom, but can depend on it - why?
snapshotRepository element is available only in distributionManagement (see maven pom XSD here http://maven.apache.org/xsd/maven-4.0.0.xsd ) and in it you define destination repository where snapshots of your project should be released - it has nothing to do with resolving dependencies tho. For snapshot dependencies including parent pom references to be resolved you need to define a dependency repository with snapshots enabled. E.g. [1] worked for me with maven 3.0.2 and I'm pretty sure you won't have problems resolving dependencies (parent or regular) with this configuration with maven 2.2.1 either. Regards, Stevo. [1] pom.xml with apache.snapshots dependency repository defined project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion parent groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId version19-SNAPSHOT/version /parent groupIdfoo/groupId artifactIdbar/artifactId version0.0.1-SNAPSHOT/version repositories repository idapache.snapshots.https/id nameApache Development Snapshot Repository/name urlhttps://repository.apache.org/content/repositories/snapshots/url snapshots enabledtrue/enabled updatePolicyalways/updatePolicy /snapshots /repository /repositories /project On Sun, Feb 27, 2011 at 3:47 PM, sebb seb...@gmail.com wrote: On 27 February 2011 13:41, Stevo Slavić ssla...@gmail.com wrote: I doubt it is intentional behavior. You didn't mention which version of maven are you using, or maven-dependency-plugin - like with any OSS project, latest maven is the greatest, and configure plugin version in pluginManagement section. You also didn't provide snapshots repository definition snippet - maybe you're affected by default daily updatePolicy for snapshots; configure always or use -U switch when building. I'm using Maven 2.2.1 dependency plugin 2.0 Not sure how I can update the plugin version (there is a 2.2), as it appears that Maven tries to process the parent before it processes the pluginManagement section. snapshotRepository idapache.snapshots.https/id nameApache Development Snapshot Repository/name urlhttps://repository.apache.org/content/repositories/snapshots/url /snapshotRepository I don't think the update policy is relevant, otherwise why would a plain dependency work? Anyway, I have just tried -U and that did not help Here is the parent.xml file in case you want to try for yourself: project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion parent groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId version19-SNAPSHOT/version /parent groupIdorg.home.mvnsample/groupId artifactIdmvnsample/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namemvnsample/name urlhttp://maven.apache.org/url /project Regards, Stevo. On Sun, Feb 27, 2011 at 2:44 AM, sebb seb...@gmail.com wrote: I uploaded commons-parent POM 19-SNAPSHOT to the snapshot repo [1], and then deleted it from my local repo (because I want to test how it will work for others). When I try to depend on it as a parent, i.e. parent groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId version19-SNAPSHOT/version /parent I get the following error: [INFO] Scanning for projects... [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Error building POM (may not be this project's POM). Project ID: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT Reason: Cannot find parent: org.apache.commons:commons-parent for project: org.home.mvnsample:mvnsample:jar:1.0-SNAPSHOT for project org.home.mvnsample:mvnsample:jar:1.0- SNAPSHOT Yet when the POM depends on it as a dependency, i.e. dependency groupIdorg.apache.commons/groupId artifactIdcommons-parent/artifactId version19-SNAPSHOT/version typepom/type /dependency it is downloaded without a problem. It looks as though Maven does not check snapshot repositories for a parent POM dependency. Is this true, and if so is it intentional? [1] http://repository.apache.org/snapshots/org/apache/commons/commons-parent/19-SNAPSHOT/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users
Re: Configuring repositories
You can use a profile and configure corporate repo in it, this profile should not be active by default, activate that profile only when you're on corporate VPN, when corporate repo is accessible. You can find more details on activating profiles and build profiles in general here: http://maven.apache.org/guides/introduction/introduction-to-profiles.html Regards, Stevo. On Sat, Feb 26, 2011 at 12:56 PM, Brett Porter br...@apache.org wrote: On 26/02/2011, at 1:41 PM, Mark wrote: How can I configure maven to first check all the default repositories and if a jar is not found THEN check our corporate repo (Archiva)? I've added the following to settings.xml however It tries to connect to this repo first, not last. idFoo/id urlhttp://my.company.com:8080/archiva/repository/internal//url releases enabledtrue/enabled /releases snapshots enabledtrue/enabled /snapshots It depends where you've declared this, but generally due to inheritance rules this is going to take precedence over the built in ones. The only solution is to redeclare the default repository above the declaration you've given: repository idcentral/id urlhttp://repo1.maven.org/maven2/url ... /repository repository idFoo/id urlhttp://my.company.com:8080/archiva/repository/internal//url ... /repository A better solution is to run a copy of Archiva on your own machine, and point your builds there for everything. You can then use proxy rules to direct only requests for corporate artifacts to the corporate repository, and take that connector offline when you're not on the VPN (as well as controlling timeouts). This repo will also only be available if I am connected to our VPN. Is there also a way to configure a connect timeout so it doesn't hang for minutes when Im not connected to the VPN? https://brettporter.wordpress.com/2009/06/16/configuring-maven-http-connections/ Cheers, Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ http://au.linkedin.com/in/brettporter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-changes-plugin 2.4 and maven 3 compatibility
Hello maven users, Is anyone using maven changes plugin with maven 3? Version 2.4 of that plugin was recently released. Its usage page examples are using maven 2 reporting style (with reporting section in pom), and it's not listed on Maven 3 compatibility matrix wiki page ( https://cwiki.apache.org/MAVEN/maven-3x-plugin-compatibility-matrix.html ) Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 jar assembly: classpath in runnable jar manifest is missing
There's already a bug reported http://jira.codehaus.org/browse/MASSEMBLY-334 and there is ugly but functional workaround: use maven-war-plugin's manifest mojo to generate manifest file with classpath, and then configure archiver to use generated manifest ( see this example http://maven.apache.org/shared/maven-archiver/examples/manifestFile.html ) Regards, Stevo. On Mon, Feb 7, 2011 at 1:20 PM, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Kai Hackemesser wrote: In the project we try to build a runnable jar that depends on libraries that are assembled into a lib folder. Under Maven 2(.2.1) we have no problem with that, the runnable jar works as designed. The same project build under Maven 3.0.2 currently builds the project without complaints, but in our resulting jar's MANIFEST.MF file the Class-Path entry is missing completely. It's a bug in the Assembly Plugin, just tried plugin artifactIdmaven-assembly-plugin/artifactId version2.2/version executions execution iddeploy-assembly/id phaseinitialize/phase goals goalsingle/goal /goals configuration attachfalse/attach descriptorRefs descriptorRefjar-with-dependencies/descriptorRef /descriptorRefs archive manifest addClasspathtrue/addClasspath addExtensionsfalse/addExtensions /manifest /archive /configuration /execution /executions /plugin on a simple POM with one dependency and the resulting JAR also lacks the Class-Path manifest entry, regardless of the Maven version used. I.e. the plugin doesn't properly resolve dependencies but relies on other plugins to do so. Is this a known bug, is there a workaround known if so? Or do I need to modify something in the assembly for this? For now, your only option seems to be to fill a bug at http://jira.codehaus.org/browse/MASSEMBLY and wait for its fix. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 jar assembly: classpath in runnable jar manifest is missing
Doesn't work for me with
https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/maven-assembly-plugin/2.2.1-SNAPSHOT/maven-assembly-plugin-2.2.1-20110203.204308-1.jar
- classpath still nowhere to be seen. Checking out
maven-assembly-plugin trunk (r1068108), installing it, and making use
of it didn't help as well.
Regards,
Stevo.
On Mon, Feb 7, 2011 at 8:28 PM, Dennis Lundberg denn...@apache.org wrote:
On 2011-02-07 00:27, Kai Hackemesser wrote:
Hi there,
We try to migrate to Maven 3.0 here but one assembly causes us headache.
In the project we try to build a runnable jar that depends on libraries that
are assembled into a lib folder. Under Maven 2(.2.1) we have no problem with
that, the runnable jar works as designed. The same project build under Maven
3.0.2 currently builds the project without complaints, but in our resulting
jar's MANIFEST.MF file the Class-Path entry is missing completely.
Is this a known bug, is there a workaround known if so? Or do I need to
modify something in the assembly for this?
Can you please try with the latest 2.2.1-SNAPSHOT version of the
Assembly Plugin?
here's our plugin configuration:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2/version
executions
execution
iddeploy-assembly/id
phasepackage/phase
goals
goalsingle/goal
/goals
configuration
attachfalse/attach
descriptors
descriptorsrc/main/assembly/executable-assembly.xml/descriptor
/descriptors
archive
manifest
addDefaultImplementationEntriestrue/addDefaultImplementationEntries
mainClasscom.energyintellect.ecg.Application/mainClass
*addClasspathtrue/addClasspath*
addExtensionsfalse/addExtensions
/manifest
/archive
finalNameeig-${project.version}/finalName
/configuration
/execution
/plugin
and the assembly descriptor:
assembly xmlns=http://maven.apache.org/xsd/assembly-1.1.0; xmlns:xsi=
http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/xsd/assembly-1.1.0
http://maven.apache.org/xsd/assembly-1.1.0-SNAPSHOT.xsd;
idbin/id
formats
formatjar/format
/formats
includeBaseDirectoryfalse/includeBaseDirectory
dependencySets
dependencySet
useProjectArtifactfalse/useProjectArtifact
unpacktrue/unpack
scoperuntime/scope
includes
includecom.[...]/include
includecom.[...]/include
includecom.[...]/include
includecom.[...]/include
includecom.smardec:license4j/include
includenet.wimpi:modbus/include
/includes
/dependencySet
/dependencySets
fileSets
fileSet
directorytarget/classes/directory
outputDirectory/outputDirectory
/fileSet
/fileSets
/assembly
Cheers,
Kai
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-changes-plugin 2.4 and maven 3 compatibility
It works well thanks! Was checking plugin compatibility in wrong table - one with regular plugins and not in one with report plugins... Regards, Stevo. On Mon, Feb 7, 2011 at 1:07 PM, martib bruno.ma...@evard.ch wrote: Have you moved the plugin conf. to the 'build' section? see: https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html#Maven3.xandsiteplugin-Configurationformat. https://cwiki.apache.org/MAVEN/maven-3x-and-site-plugin.html#Maven3.xandsiteplugin-Configurationformat. -- View this message in context: http://maven.40175.n5.nabble.com/maven-changes-plugin-2-4-and-maven-3-compatibility-tp3373985p3374140.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3, and long build after switching mirror of central
Hello Maven users, User settings is configured to use a repository C1 on repo manager (Nexus) at H1 host as mirror of central. Local repo is clean. Project being built is a very simple maven project with pom packaging, which just lists latest versions of maven core plugins in pluginManagement section, and configures some of them. CLI build is started with package goal, Maven resolves/downloads plugins, build is successful. Then user settings are reconfigured so that repository C2 on repo manager (again Nexus) at H2 host is mirror of central. CLI build is started with clean package goals, Maven again resolves/downloads plugins, for every downloaded plugin 0 B at 0.0 KB/sec gets displayed, build is successful. This second build lasts almost five minutes (4:54.371s to be more precise). Is this normal? Project does not have any sources, code generation or anything similar, just plain pom file with core plugins. If it's likely repo manager (configuration) issue, will ask on Nexus mailing list. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3, and long build after switching mirror of central
Yes, that was it, the other proxy repo on H2 was clean. Thanks for helping me understand! Regards, Stevo. On Tue, Feb 8, 2011 at 2:44 AM, Wayne Fay wayne...@gmail.com wrote: started with clean package goals, Maven again resolves/downloads plugins, for every downloaded plugin 0 B at 0.0 KB/sec gets displayed, build is successful. This second build lasts almost five minutes (4:54.371s to be more precise). Is this normal? Project does not have any sources, code generation or anything similar, just plain pom file with core plugins. If it's likely repo manager (configuration) issue, will ask on Nexus mailing list. How long a given build will take while connecting to a given Nexus instance is highly (linearly) dependent on the state of cached artifacts in that particular Nexus instance. If H1 had all those Maven artifacts cached and H2 was empty, it may take 5 mins for H2 to download and store all the poms and jars etc that your build requires -- but then none got transferred to your local Maven build because you already had them all cached in your own local .m2 directory (thus the 0 B at 0.0 KB/sec -- if you were able to see the Nexus download monitor at the same time, it would show different numbers). By all means, forward this to the Nexus lists for verification and perhaps some suggestions on what logs to watch to debug this for yourself. But this explanation makes sense to me, and probably explains what you are seeing. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: archetype:create-from-project and excluding files from to-be-created archetype
Most effective route Wayne mentions doesn't have any effectiveness guarantees - ticket with by-the-book patch could be unresolved and unnoticed or without any feedback for ages just as any non-maintainer created ticket. On the bright side of things, with Apache v2 licensed projects if you're armed with a patch you can always fork or at least create your own custom release. Regards, Stevo. On Wed, Dec 1, 2010 at 5:29 PM, Wayne Fay wayne...@gmail.com wrote: I have the same needs. I'd like to exclude the .project when creating my archetype. Is it possible ? The most effective route to getting this kind of issue resolved is to just do it yourself and donate the code back to the project via Jira. Otherwise the issue will simply sit for another year until someone else wants it and does it for you. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven archive issue
Which version of maven-war-plugin are you using? Did you put maven-war-plugin declaration in pluginManagement? Regards, Stevo. On Fri, Jan 28, 2011 at 11:13 PM, sanju ssa...@yahoo.com wrote: I am trying to add archive configuration but that is not helping ( it is not adding/updating manifest file generated as part of the war). archive manifest addDefaultImplementationEntriestrue/addDefaultImplementationEntries addDefaultSpecificationEntriestrue/addDefaultSpecificationEntries /manifest /archive Can someone help me why it is not adding entry to manifest.mf ? -Sanju - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-jar-plugin manifest goal
Hello Maven users, maven-war-plugin has manifest goal for generating manifest file. Is there any reason why this should not be supported in maven-jar-plugin as well? IMO this goal would be useful. E.g. it would be nice workaround for issue http://jira.codehaus.org/browse/MASSEMBLY-334 with maven-assembly-plugin - assembly plugin does not generate class path element when generating manifest file for jar, so jar:manifest could be used to generate manifest file to be shared by main jar and assembled variants. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: create exec of swing maven application
Only non-deprecated goal, besides help goal is single - http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html Use single instead of attached. Use latest release (2.2), declare it first in pluginManagement. Regards, Stevo. On Mon, Jan 24, 2011 at 7:41 PM, Glenn Wybo glenn.w...@gmail.com wrote: Hi, I'm trying to create an executable jar from a swing application using maven and its maven-assembly-plugin. It builds ok, I saw in the jar it packs the dependent jars, but it contains non of my own programmed classes, resulting in a classnotfound exception when double clicking on the jar. Can anyone help me out? Is this the easiest way for creating an excecutable for a swing application or are there better ways? the configuration I used is: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId configuration descriptorRefs descriptorRefjar-with-dependencies/descriptorRef descriptorRefsrc/descriptorRef /descriptorRefs archive manifest mainClassbe.presentation.MyApp/mainClass /manifest /archive /configuration executions execution idattach-assembly-to-package/id phasepackage/phase goals goalattached/goal /goals /execution /executions /plugin This plugin is in the parent class containing the modules. It has 6 modules, from which the presentation module contains the main class. The other modules are dependencies of the presentation module. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
m2eclipse-subversive and Subversive Integration for the M2Eclipse relation
Hello Maven users, Jason van Zyl just announced m2eclipse-subversive http://twitter.com/#!/jvanzyl/status/29312097812750336 Does anyone know how is that project related to Subversive Integration for the M2Eclipse, Subversive plugin integration feature? Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-site-plugin 3.0-beta-3 and maven-checkstyle-plugin 2.6 gives Unable to instantiate PackageHtml
With new checkstyle, 5.x, some of the old checkstyle checks have been replaced with new ones. See checkstyle release notes http://checkstyle.sourceforge.net/releasenotes.html for details on new checks. Replace them accordingly in your custom checkstyle configuration. Regards, Stevo. On Fri, Jan 21, 2011 at 5:15 PM, Lucas Persson lucas.pers...@oracle.comwrote: Hi I am using maven 3.0.2 and I get an error like this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-site-plugin:3.0-beta-3:site (default-site) on project commons: Error during page generation: Error rendering Maven report: Failed during checkstyle configuration: cannot initialize module PackageHtml - Unable to instantiate PackageHtml: Unable to instantiate PackageHtmlCheck - [Help 1] when doing 'mvn site'. I have maven-site-plugin 3.0-beta-3 and maven-checkstyle-plugin 2.6 There seems to have been some issue around PackageHtmlCheck, see http://jira.codehaus.org/browse/SONAR-1545?page=com.atlassian.jira.plugin.system.issuetabpanels%3Achangehistory-tabpanel But I can not really understand what the trick is. And yes I have my own rules. Basically it is similar to the Sun one. Sure I can remove module name=PackageHtml/ but then I get Failed during checkstyle configuration: cannot initialize module TreeWalker - TreeWalker is not allowed as a parent of FileLength - [Help 1] Thanks Lucas -- [image: Oracle] http://www.oracle.com Lucas Persson | Principal Member of Technical Staff Phone: +4684773644 tel:+4684773644 | | | Mobile: +46730946656tel:+46730946656 Oracle Communications Platform ORACLE Sweden | Folkungagatan 122 | 116 30 Stockholm Oracle Svenska AB, Kronborgsgränd 17, S-164 28 KISTA, reg.no. 556254-6746 [image: Green Oracle] http://www.oracle.com/commitment Oracle is committed to developing practices and products that help protect the environment
Re: License collection
Maybe you'll find these plugins useful: http://code.google.com/p/maven-license-plugin/ http://community.jboss.org/wiki/Howtoaddlicenseinfotoprojects https://wiki.jasig.org/display/LIC/maven-notice-plugin Regards, Stevo. On Fri, Jan 21, 2011 at 7:30 PM, Wayne Fay wayne...@gmail.com wrote: I'm trying to automate licensing collection for my product. What I want is simple: collect (i.e. download) all licenses of my dependencies and store them in a folder. This is not as simple as you may think. How exactly do you plan to do this? Where will you download all licenses for your dependencies from? Hint: they are not necessarily stored in Central along with your jars -- this is pretty rare from what I've seen, unless they are packaged along with the jar file (which is also not particularly common). Does anyone know if there's a plugin that does what I'm trying to accomplish? I've heard about license-maven-plugin ( http://mojo.codehaus.org/license-maven-plugin/ ) but I couldn't even download it. This plugin is in the Sandbox, so you can't simply download and use it. Follow the directions on the Mojo site: http://mojo.codehaus.org/using-sandbox-plugins.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: General exclusion of a dependency
http://jira.codehaus.org/browse/MNG-1977 On Mon, Jan 17, 2011 at 10:49 AM, mremerson...@aim.com wrote: Hi, is it possible to exclude a dependency without specifying from which other dependency it might come from ? Like wherever depA is coming from, exclude it ? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: General exclusion of a dependency
I wouldn't recommended using provided scope as you or your fellow developers may unintentionally in development/compile time make use of some resource or type from dependency in provided scope, but then get a nasty surprise at runtime. Typically I'd use dependencyManagement at parent level, and exclude unwanted dependency as many times as needed. If that dependency set with exclusions repeats across several different projects, then define it once in a module with pom packaging, which gets imported (import scope) in different projects. Regards, Stevo. On Mon, Jan 17, 2011 at 1:59 PM, Jesse Farinacci jie...@gmail.com wrote: Hi, On Mon, Jan 17, 2011 at 4:49 AM, mremerson...@aim.com wrote: is it possible to exclude a dependency without specifying from which other dependency it might come from ? Like wherever depA is coming from, exclude it ? Until MNG-1977 is resolved, you can perform a simple work around. E.g. project build dependencies groupIdcommons-logging/groupId artifactIdcommons-logging/artifactId scopeprovided/scope /dependencies /build /project The scope=provided instructs Maven to not actually bring that dependency into the classpath, thus, it behaves as a global exclude. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Cobertura and Surefire
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 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 execute both uninstrumented _and_ instrumented tests. -- Neu: GMX De-Mail - Einfach wie E-Mail, sicher wie ein Brief! Jetzt De-Mail-Adresse reservieren: http://portal.gmx.net/de/go/demail - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven-changelog-plugin and submodule scm url
Hello Maven users, Is there a reason why maven-changelog-plugin (v2.2) appends submodule artifactId and not corresponding module name from submodule's aggregator modules list when constructing submodule scm (in my case svn) url? When module name and artifactId are different, generating changed sets for the report fails for me because of this behavior. Submodule artifactId contains groupId as prefix (e.g. foo.bar:foo.bar.module1), while module name in module aggregator contains just a name (module1) without a prefix. Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-changelog-plugin and submodule scm url
Thanks Luke, For pointing me to that issue. It's http://jira.codehaus.org/browse/MNG-4670 which is linked as related to http://jira.codehaus.org/browse/MNG-3244 I guess, at least temporarily, I'll have to use same module name in modules list as submodule artifactId. Regards, Stevo. On Thu, Jan 13, 2011 at 12:37 AM, lukewpatterson lukewpatter...@gmail.com wrote: Stevo Slavić wrote: ... appends submodule artifactId and not corresponding module name from submodule's aggregator modules list when constructing submodule scm ... Is it a different problem than the many-headed* http://jira.codehaus.org/browse/MNG-3244 ? * dive into the issue links section -- View this message in context: http://maven.40175.n5.nabble.com/maven-changelog-plugin-and-submodule-scm-url-tp3339077p3339098.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: persistence-api-2.0.jar ?
https://repository.jboss.org/nexus/content/groups/public/org/hibernate/javax/persistence/hibernate-jpa-2.0-api/1.0.0.Final/ Regards, Stevo. On Tue, Jan 4, 2011 at 1:24 PM, Antoine DESSAIGNE antoine.dessai...@gmail.com wrote: Hi everyone, I have a pretty simple question, is there a persistence-api-2.0 jar that defines the standard JPA 2 api somewhere ? I wasn't able to find it :/ Thanks a lot for your insights on this matter. Antoine. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3.0 doesn't update snapshot artifacts
Define update policy in your snapshots repository declaration: repository snapshots enabledtrue/enabled updatePolicyalways/updatePolicy /snapshots /repository Regards, Stevo. On Fri, Nov 26, 2010 at 11:20 AM, Moser, Christian c...@metrohm.com wrote: Posted my problem also in artifactory mailing list. @see http://forums.jfrog.org/artifactory-amp-maven-3-0-metadata-problem-td5776632.html - Chris -Ursprüngliche Nachricht- Von: Patrick Sansoucy [mailto:patrick.sanso...@gmail.com] Gesendet: Freitag, 26. November 2010 04:05 An: Maven Users List Betreff: Re: Maven 3.0 doesn't update snapshot artifacts We witnessed the same issue here at work. While the latest Maven 2 works properly, our developpers using Maven 3 had the problem and had to go through the same procedure of deleting the jar within the local repo. We, on the other hand, use archiva for our artifact deployement. It is a major blocker for our dev team to upgrade to M3. I don't know the culprit and I have not tried using the uniqueVersion toggle to timestamp the snapshot, since I need to discuss this change with our CM's. -Patrick On Tue, Nov 23, 2010 at 9:43 AM, Moser, Christian c...@metrohm.com wrote: I'm unable to download the newest artifacts (compiled jar) with maven 3.0 and 3.0.1-RC1 from cmd line. The artifacts were deployed to artifactory 2.3.1. After calling mvn -U on a dependend artifact, maven just updates the metadata, but doesn't override the old artifacts contained in the local repository. I have to delete the local repository to receive the newest artifacts from remote after calling mvn -U. the artifacts are all snapshots version. Is there another, new way to force update snapshots? -Chris - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Upload Requests separate binaries and sources jar restriction
Hello Apache Maven users, On Maven Upload Request http://jira.codehaus.org/browse/MAVENUPLOAD JIRA project summary page it is stated that All bundles submitted after February 23rd 2010 must have sources, javadocs and all artifacts accompanied by valid PGP signatures. Your bundles will be immediately rejected if you are missing any of these requirements.. I'd like to convince maintainer(s) of an open source project which is not built using Apache Maven to upload their artifact to Maven Central. Their distribution includes a jar file with binaries and source all together and not as two separate jars. Would it be acceptable for uploading to central to provide that single jar, pom, and signatures? Regards, Stevo.
Additional dependencies in assembly
Hello Apache Maven users, It seems it's not possible to introduce additional dependencies through assembly descriptor, one can only filter (include/exclude) dependencies defined in module pom. Can someone please verify this? Btw, current assembly plugin site documents that assembly descriptor schema v1.1.2 should be used for assembly plugin 2.2-beta-6 and higher (see herehttp://maven.apache.org/plugins/maven-assembly-plugin/#Assembly_Descriptor_Schemas_XSD), but there is no such assembly-1.1.2.xsdhttp://maven.apache.org/xsd/assembly-1.1.2.xsdfile. Link for that file on assembly plugin site points to v1.1.1 XSD. Maybe assembly-1.1.2.xsd exists in sources but it didn't get published with 2.2-beta-6 release. Regards, Stevo.
Re: ${version} in 3.0
Try
help:effective-pomhttp://maven.apache.org/plugins/maven-help-plugin/effective-pom-mojo.html
Regards,
Stevo.
On Sun, Oct 10, 2010 at 11:15 PM, Jason Chaffee jchaf...@ebates.com wrote:
I do have properties like this though:
spring.version
that I then use ${spring.version}
-Original Message-
From: Jason Chaffee [mailto:jchaf...@ebates.com]
Sent: Sun 10/10/2010 2:12 PM
To: Maven Users List; Maven Users List
Subject: RE: ${version} in 3.0
checked every file. It does no exist anywhere.
-Original Message-
From: Marshall Schor [mailto:m...@schor.com]
Sent: Sat 10/9/2010 7:18 PM
To: Maven Users List
Subject: Re: ${version} in 3.0
also check parent poms.
-Marshall Schor
On 10/9/2010 8:35 PM, Niall Pemberton wrote:
On Sun, Oct 10, 2010 at 1:18 AM, Jason Chaffee jchaf...@ebates.com
wrote:
I am getting this warning for every module, yet I am not using this
variable any of the poms. Some poms do have ${project.version} but some of
them don't have any variable expressions at all and it is still outputting
this warning.
Does this warning just get output regardless of what is the the pom?
[WARNING] The expression ${version} is deprecated. Please use
${project.version} instead.
What about other places like assembly plugin config files?
Niall
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2 3 + Hudson + Nexus
Check policy settings of any repository definition from where problematic (snapshot) dependency is supposed to be fetched from. Maybe you'll reproduce issue locally once you clean your local repository (probably dependency artifact is there so you can build locally but hudson can not access repository where dependency artifact resides). Also if you're using alternate settings.xml to configure repository access there's a known bughttp://issues.hudson-ci.org/browse/HUDSON-4693in hudson. Regards, Stevo. On Mon, Oct 4, 2010 at 10:16 PM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: On 4 October 2010 13:01, Anders Hammar and...@hammar.net wrote: Is it the snapshot metadata? Are you using Nexus 1.7.2 or earlier? If so, search the nexus mailing list for a patch or upgrade to Nexus 1.8.0. I'm not sure whether it's the snapshot metadata or not. I can't see anything special there. How can I tell? Like I said, Maven doesn't seem to be even asking Nexus for data. It just stops and complains it can't find the POM. I've already upgraded to Nexus 1.8.0. Hudson is 1.379. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2 3 + Hudson + Nexus
When I mentioned repository policy settings, I actually meant on repository definition in your pom.xml or settings.xml and it's update policy. By default it's daily. Have you tried forcing updating snapshots with -U switch? Regards, Stevo. On Tue, Oct 5, 2010 at 12:37 AM, Hilco Wijbenga hilco.wijbe...@gmail.comwrote: On 4 October 2010 14:57, Benjamin Bentmann benjamin.bentm...@udo.edu wrote: Hilco Wijbenga wrote: Any ideas how I can fix this? Any ideas as to what the problem is exactly? I personally find it helpful to start with a precise description of what the issue actually is before trying to solve it. After all, there's a reason why the build produces a log and even if you can't spot the relevant pieces in there, others might be able to. So sharing the log of the failing module would be a good start. And with log, I don't mean the single line that says [ERROR], I mean the entire log that shows the actions taken by Maven that eventually lead to the error and contribute to the context required to understand the issue. If the log cannot be attached to the mail, using pastebin.com or similar can help. Other things that are nice to know is the directory listing of the directory in the local repo that contains the POM in question. Last but not least, the contents of all maven-metadata-*.xml in that directory can help to troubleshoot that issue. Here you go. I didn't see anything useful in the log files but you're right of course, somebody else might. I've attached the results of running Maven 2.2.1 (maven2.txt) and the (partial, until just after the successful retrieval of the problematic POM) results of running Maven 3.0 (RC2) (maven3.txt). (The download link to RC3 is no longer valid so I have not been able to try it with RC3.) I've emptied the local repository directory with the problematic POM file so that Maven has to redownload it. So nothing useful there. (It stays empty because Maven 2 doesn't download anything.) After running Maven 3, I get: hi...@centaur $ ls ~/.m2/repository/com/xyz/test-dependencies-pom/5-SNAPSHOT/ _maven.repositories maven-metadata-all-mirror.xml maven-metadata-all-mirror.xml.sha1 resolver-status.properties test-dependencies-pom-5-20101004.184333-6.pom test-dependencies-pom-5-20101004.184333-6.pom.sha1 test-dependencies-pom-5-SNAPSHOT.pom The maven-metadata.xml that Nexus sees: metadata groupIdcom.igniteplay/groupId artifactIdtest-dependencies-pom/artifactId version5-SNAPSHOT/version versioning snapshot timestamp20101004.184333/timestamp buildNumber6/buildNumber /snapshot lastUpdated20101004184339/lastUpdated /versioning /metadata and the directory listing that Nexus sees: maven-metadata.xml maven-metadata.xml.md5 maven-metadata.xml.sha1 test-dependencies-pom-5-20101002.073647-5.pom test-dependencies-pom-5-20101002.073647-5.pom.sha1 test-dependencies-pom-5-20101004.184333-6.pom test-dependencies-pom-5-20101004.184333-6.pom.sha1 I hope that sheds some light on things. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: MASSEMBLY-445 now has patch /w tests
ping On Sun, Aug 29, 2010 at 9:19 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Apache Maven users, Can some Maven developer please mark MASSEMBLY-445http://jira.codehaus.org/browse/MASSEMBLY-445as issue with patch tests, if not have a look at it? Thanks in advance! Regards, Stevo.
MASSEMBLY-445 now has patch /w tests
Hello Apache Maven users, Can some Maven developer please mark MASSEMBLY-445http://jira.codehaus.org/browse/MASSEMBLY-445as issue with patch tests, if not have a look at it? Thanks in advance! Regards, Stevo.
Re: Reopen MECLIPSE-36
Great, thanks! Regards, Stevo. On Wed, Aug 25, 2010 at 6:39 AM, Barrie Treloar baerr...@gmail.com wrote: On Tue, Aug 24, 2010 at 6:28 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Apache Maven users, Can someone of the Apache Maven developers please reopen the MECLIPSE-36http://jira.codehaus.org/browse/MECLIPSE-36issue, it is still present (in maven-eclipse-plugin:2.8). I've duplicated this as http://jira.codehaus.org/browse/MECLIPSE-667 and marked it as a regression. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Reopen MECLIPSE-36
Hello Apache Maven users, Can someone of the Apache Maven developers please reopen the MECLIPSE-36http://jira.codehaus.org/browse/MECLIPSE-36issue, it is still present (in maven-eclipse-plugin:2.8). Thanks in advance! Regards, Stevo.
maven-changelog-plugin, svn encrypted passwords
Hello Maven users,
Has anyone tried to use maven-changelog-plugin configured with encrypted
password? Following reporting section configuration works if I use plain
text password and fails authentication if I use encrypted password:
...
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-changelog-plugin/artifactId
version2.2/version
configuration
username![CDATA[${env.SCM_USERNAME}]]/username
password![CDATA[${env.SCM_PASSWORD}]]/password
/configuration
/plugin
...
I couldn't find a ticket for this in maven-changelog-plugin's JIRA, so I
wanted to check with the community first (before venturing into plugin's
source code), could be I'm doing something wrong here. Not sure what
passphrase and passKey configuration parameters are used for (docs very thin
on this) or if they are related to this use case.
BTW some plugins, like maven-deploy-plugin, still document that Maven
doesn't support encrypted passwords yet...
Regards,
Stevo.
Re: How to build a module without the installation of dependent modules?
Hello Benyi, What's so wrong with having module-A installed in your local repository? Regards, Stevo. On Tue, Jun 22, 2010 at 12:29 AM, Benyi Wang bewang.t...@gmail.com wrote: I have a maven project like this: my-project module-A module-B two modules A and B are in the sibling folders with the parent my-project. Module B is a dependent of module A. If I run mvn test in my-project folder, it works fine. But if I run mvn test in module-B folder, it asks me to install module A in the repository. How can I build module B without the installation of module A? I tried reactor command line options and reactor plugins but not lucky. For example, in my-project folder, mvn --projects ../module-A returns an error saying cannot find /my-project/../module-A. mvn reactor:make -Dmake.artifacts=module-B didn't work too. Does somebody know the answer? Thanks a lot
Maven 3 webinar registration
Hello maven users, Registration for coming maven 3 webinarhttp://sonatype.com/webinars/register2010-01-20requires country selection, but not all countries are available for selection. I wonder whats the rationale behind this? Regards, Stevo.
Re: Running unit tests in a specific order
Use TestNG, it's @Test annotationhttp://testng.org/doc/documentation-main.html#annotationshas dependsOnMethods and dependsOnGroups attributes which allow you to express such test dependencies in tests themselves. Regards, Stevo. On Thu, Jan 7, 2010 at 1:07 PM, Entner Harald entner.har...@afb.de wrote: Hey Michael, Afaics there is no way to define the order of tests with the surefire plugin. Maybe another plugin could help you. But IMHO i would suggest to remove the dependencies of your tests. E.g. using the @Before annotation. Otherwise you can never be sure that your tests are working after changing one of your dependent tests. This is more an advice than an useful hint. But i'm pretty sure that the surefire plugin itself wont help you defining the order of your tests. Harald -Ursprüngliche Nachricht- Von: Michel Barakat [mailto:bmic...@gmail.com] Gesendet: Donnerstag, 7. Januar 2010 12:24 An: users@maven.apache.org Betreff: Running unit tests in a specific order Hey folks, I am using the surefire plugin to run through JUnit tests. I am facing some cross-test dependencies issues and thus would like to investigate how tests perform when ran in a specific order. I have tried using the' test' flag, as in: mvn -Dtest=ATest,BTest,CTest test However, this does not necessarily execute the tests in the specified order (eg. CTest is executed before ATest or BTest). Is it possible to specify a strict order, through which unit tests should be executed? Cheers Michel - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Optionally disable transitive dependencies in Maven
I'd suggest that you refactor projectB bits used by both projectB and projectA into a new projectC module and have it referenced as dependency from both projectA and projectB. Regards, Stevo. On Wed, Jan 6, 2010 at 10:57 AM, jaikiran jai_forums2...@yahoo.co.inwrote: Hello everyone, I am using Maven-2.0.9 and I have a project A which depends on a couple of classes from project B. So obviously, i have a dependency in my pom.xml as follows: dependency groupIdorg/groupId artifactIdprojectB/artifactId /dependency But the project B has a long list of transitive dependencies, none of which are required in project A. I was looking for a way to disable those transitive dependencies from being pulled into project A. One option would be to add numerous exclude elements to the dependency. But this is not practical, given the long list of transitive dependencies. I was looking for something like the following: dependency groupIdorg/groupId artifactIdprojectB/artifactId transitivefalse/transitive /dependency A transitive child element to the dependency element which can then be configured to disable transitive dependencies from being pulled in. From what i learn based on my discussion about this on #maven IRC, there's no technical reason why this can't be done/allowed. It would be useful to have this feature in Maven to disable transitive dependencies. Any thoughts? P.S: Is this the right list or should this be in maven-dev list? -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4259924.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Optionally disable transitive dependencies in Maven
http://jira.codehaus.org/browse/MNG-2315 http://stackoverflow.com/questions/547805/how-to-exclude-all-transitive-dependencies-of-a-maven-dependency Regards, Stevo. On Wed, Jan 6, 2010 at 11:45 AM, jaikiran jai_forums2...@yahoo.co.inwrote: I would have done that. But the project B is not in my control. It's a third party project. Stevo Slavić wrote: I'd suggest that you refactor projectB bits used by both projectB and projectA into a new projectC module and have it referenced as dependency from both projectA and projectB. Regards, Stevo. -- View this message in context: http://n2.nabble.com/Optionally-disable-transitive-dependencies-in-Maven-tp4259924p4260065.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Accessing MavenSession from a plugin component
Hello Maven users, Can anyone please point me to some docs or example on how one can access a maven session from a plugin plexus.component? Regards, Stevo.
Apache parent pom
Hello Maven users, Apache parent pom, like one for version 7 which is being voted on these days, contains apache.snapshots repository declaration. Why is that apache.snapshots repository definition needed? IMO it is in contradiction with rules for deploying artifacts on central repository, and it makes builds with dependencies report last longer than what's necessary. Regards, Stevo.
maven central archetype catalog
Hello Maven users, Why doesn't Maven central repo have archetype-catalog.xml ? Regards, Stevo.
Re: maven central archetype catalog
Found related issue here http://jira.codehaus.org/browse/ARCHETYPE-242. Regards, Stevo. On Fri, Dec 25, 2009 at 10:18 AM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, Why doesn't Maven central repo have archetype-catalog.xml ? Regards, Stevo.
maven-invoker-plugin, plugin testing, and IT's with plugin snapshot dependencies
Hello Maven users, If one installs a snapshot of a plugin (P1) in local repository, and for other plugin (P2) an IT, run using maven-invoker-plugin configured as recommended to use isolated local repository for integration tests, is a project which makes use of P1 snapshot, IT will fail since P1 snapshot is not available in IT local repository. Seems it's not currently (v1.5) possible to configure maven-invoker-plugin's install mojo to install given plugin artifacts into IT local repository. Regards, Stevo.
Re: Maven 3 deprecated properties
It works well, pom.name deprecation is reported as warning too; I believe it didn't initially because of parent POM resolutionhttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolutionissue project had. Regards, Stevo. On Sat, Dec 19, 2009 at 12:37 PM, Anders Hammar and...@hammar.net wrote: Stevo, I think it would be great if you could file a jira for the pom.nameproperty to be deprecated in Maven 3.0! /Anders On Sat, Dec 19, 2009 at 05:26, Brian Fox bri...@infinity.nu wrote: Yes, a long time ago. On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict pbened...@apache.org wrote: Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 deprecated properties
Maven properties guidehttp://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuideshould be updated to document that pom.* properties are deprecated. Regards, Stevo. On Sat, Dec 19, 2009 at 6:03 PM, Stevo Slavić ssla...@gmail.com wrote: It works well, pom.name deprecation is reported as warning too; I believe it didn't initially because of parent POM resolutionhttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-ParentPOMResolutionissue project had. Regards, Stevo. On Sat, Dec 19, 2009 at 12:37 PM, Anders Hammar and...@hammar.net wrote: Stevo, I think it would be great if you could file a jira for the pom.nameproperty to be deprecated in Maven 3.0! /Anders On Sat, Dec 19, 2009 at 05:26, Brian Fox bri...@infinity.nu wrote: Yes, a long time ago. On Fri, Dec 18, 2009 at 5:39 PM, Paul Benedict pbened...@apache.org wrote: Stevo, I thought all pom.* properties were gone. Weren't they replaced by project.* ? On Fri, Dec 18, 2009 at 4:35 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility notes http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 3 deprecated properties
Hello Maven users, When building project with Maven 3.0-alpha-5, warnings appear that pom.version and pom.artifactId properties have been deprecated in favor of their project.* variants. Is it same with pom.name property? I'm asking this because pom.name is not being reported as deprecated, but I expect it to be for consistency reason. Wish this deprecated stuff was listed in Maven 3 compatibility noteshttp://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html . Regards, Stevo.
Skip checking for parent pom using relativePath
Hello maven-users, Is there a way to configure project pom.xml or in any other way suggest maven to skip checking for parent pom using relativePath? E.g. by setting relativePath to _skip or something similar. Regards, Stevo.
Re: Maven Plugin to detect duplicate class files in a e.g. WAR
maven-shade-plugin's shade goalhttp://maven.apache.org/plugins/maven-shade-plugin/shade-mojo.htmlwill display warnings for duplicate classes when generating uber-jar. Stephen, maybe you can reuse some parts of the logic from there for the new mojo. Regards, Stevo. On Sat, Dec 12, 2009 at 9:13 PM, lukewpatterson lukewpatter...@gmail.comwrote: Mirko Friedenhagen wrote: goal to check classpath for duplicate resources/classes I haven't tried it yet, but recently I was looking for the same functionality and ran across JBoss' tattletale tool: http://www.jboss.org/tattletale http://www.jboss.org/tattletale JBoss Tattletale is a tool that can help you get an overview of the project you are working on or a product that you depend on. The tool will provide you with reports that can help you Identify dependencies between JAR files Find missing classes from the classpath Spot if a class/package is located in multiple JAR files Spot if the same JAR file is located in multiple locations With a list of what each JAR file requires and provides Verify the SerialVersionUID of a class Find similar JAR files that have different version numbers Find JAR files without a version number Find unused JAR archives Identify sealed / signed JAR archives Locate a class in a JAR file Get the OSGi status of your project Remove black listed API usage -- View this message in context: http://old.nabble.com/Maven-Plugin-to-detect-duplicate-class-files-in-a-e.g.-WAR-tp26658458p26760767.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: assembly is deprecated. What to use?
This help:describe issue is fixed for quite some time (see herehttp://jira.codehaus.org/browse/MPH-59) but version it is fixed for is not released yet. Plugins sites are updated with their release. In source veritas :) Regards, Stevo. On Tue, Dec 8, 2009 at 9:42 PM, Justin Edelson justinedel...@gmail.comwrote: That looks like a bug in the help plugin. On Tue, Dec 8, 2009 at 3:27 PM, Andrew Gaydenko a...@gaydenko.com wrote: On Tuesday 08 December 2009 23:09:27 Justin Edelson wrote: Not all, just some: http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html That page tells you which goals to use to replace the deprecated goals. Justin Justin, So the (trimmed) output shown below is a lie :-) I'm definitely frustrated - have thought mvn help:describe outputs most precision information... Where does the most official plugins information takes place? Andrew //- $ mvn help:describe -Dplugin=org.apache.maven.plugins:maven-assembly-plugin ... [INFO] org.apache.maven.plugins:maven-assembly-plugin:2.2-beta-4 ... assembly:assembly Deprecated. No reason given assembly:attached Deprecated. Use goal: 'assembly' (from the command line) or 'single' (from a lifecycle binding) instead. assembly:directory Deprecated. No reason given assembly:directory-inline Deprecated. Use goal: 'directory' (from the command line) or 'directory-single' (from a lifecycle binding) instead. assembly:directory-single Deprecated. No reason given assembly:help Deprecated. No reason given assembly:single Deprecated. No reason given assembly:unpack Deprecated. Use org.apache.maven.plugins:maven-dependency-plugin goal: unpack or unpack-dependencies instead. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Attaching source to artifact
Use the maven-release-plugin, by default it will add sources and javadoc to the released artifact (see herehttp://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html#useReleaseProfile ). Regards, Stevo. On Tue, Dec 8, 2009 at 11:16 PM, Qureshi,Shahzad [Ontario] shahzad.qure...@ec.gc.ca wrote: Ahh stupid me. All I've to do install or deploy it and maven automatically uploads all the jars Nevermind folks :) Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Environment Canada 416-739-4702 shahzad.qure...@ec.gc.ca -Original Message- From: Qureshi,Shahzad [Ontario] [mailto:shahzad.qure...@ec.gc.ca] Sent: Tuesday, December 08, 2009 5:10 PM To: Maven Users List Subject: RE: Attaching source to artifact Ya but the junit folks must've put the source jar somewhere on the net for the m2eclipse to find it (I do use m2eclipse). And how does m2eclipse know where to find the source from? I don't see anything in junit pom to say where to go look for the source Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Environment Canada 416-739-4702 shahzad.qure...@ec.gc.ca -Original Message- From: Todd Thiessen [mailto:thies...@nortel.com] Sent: Tuesday, December 08, 2009 5:08 PM To: Maven Users List Subject: RE: Attaching source to artifact If you use the m2eclipse plugin, it does all this automagically ;-). It's awesome to be able to step through the source of mockito or log4j without having to manually download a single thing ;-). --- Todd Thiessen -Original Message- From: Qureshi,Shahzad [Ontario] [mailto:shahzad.qure...@ec.gc.ca] Sent: Tuesday, December 08, 2009 4:58 PM To: Maven Users List Subject: Attaching source to artifact Hi all, One of our the modules that we've is a library which is used by other projects. So I've created the jar and the source jar for this module using the instructions here: http://maven.apache.org/plugin-developers/cookbook/attach-sour ce-javadoc-artifacts.html So now that I've the source jar, what do I do now? I can deploy the main artifact but where does the source go? I want the developers to have the ability like junit dependency provides where I can simply click on download source and I automagically get the source jar for junit from the net. How do I implement that functionality? I've the source jar and I've the main artifact jar Test-1.0.jar Test-1.0-sources.jar thanks Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Officer Branch | Direction générale du dirigeant principal de l'information Environment Canada | Environnement Canada shahzad.qure...@ec.gc.ca Telephone | Téléphone 416-739-4702 Government of Canada | Gouvernement du Canada Website | Site Web www.ec.gc.ca - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Warning while generating archetype
Probably thishttp://maven.apache.org/maven-archetype/archetype-common/xref/org/apache/maven/archetype/generator/DefaultFilesetArchetypeGenerator.htmlis archetype plugin code which logs these warning. Check, your archetype's archetype-metadata.xml I suspect there is one or more overlapping filesets, configured to copy same files into same location, or maybe same resources/files are listed twice in archetype.xml file. Regards, Stevo. On Fri, Dec 4, 2009 at 6:49 PM, Qureshi,Shahzad [Ontario] shahzad.qure...@ec.gc.ca wrote: Hi all, I used archetype:create-from-project goal to create an archetype from a project of mine, worked perfectly. Installed the archetype and used it to create a project, which all worked fine However, I get following warnings when I create a project using the above mentioned archetype and I can't find any reference or meaning to these warnings [WARNING] CP Don't override file C:\projects\test\my-test\src\main\resources\applicationContext.xml [WARNING] CP Don't override file C:\projects\test\my-test\src\main\resources\assemblies\bin.xml [WARNING] CP Don't override file C:\projects\test\my-test\src\main\resources\checkstyle.xml [WARNING] CP Don't override file C:\projects\test\my-test\src\main\resources\conf\application.properties [WARNING] CP Don't override file C:\projects\test\my-test\src\main\resources\conf\fileName.xml [WARNING] CP Don't override file C:\projects\test\my-test\src\main\resources\conf\log4j.properties These are the files that are part of my project and I get them copied to the folders mentioned above. I don't understand what the warning is about though and why is Maven warning me not to override these files? Any insight will be greatly appreciated thanks Shahzad Qureshi Systems Analyst/Programmer Applications Directorate | La direction générale des applications Chief Information Officer Branch | Direction générale du dirigeant principal de l'information Environment Canada | Environnement Canada shahzad.qure...@ec.gc.ca Telephone | Téléphone 416-739-4702 Government of Canada | Gouvernement du Canada Website | Site Web www.ec.gc.ca
Re: Possible to specify version from a properties file
AFAIK maven2 when processing module pom before anything else first resolves
any parent reference, so parent version has to be specified explicitly. To
have parent version explicitly specified and to easily update it,
maybe
thishttp://mojo.codehaus.org/versions-maven-plugin/examples/update-parent.htmlwill
work for you.
Regards,
Stevo.
On Fri, Dec 4, 2009 at 2:14 AM, Sony Antony sony.ant...@gmail.com wrote:
We have more than 100 modules in our project.
Each pom includes teh parent pom using the cordinates including teh version
number.
Is there any way to centralize the version number, maybe in a properties
file/profile/something.
So that if the version changes, this will be the only place where we need
to
change the version.
( Every pom would refer to this version number using some kind of
indirection - like ${project.version} )
We would liek to avoid having to put the version number in every pom.
--sony
Archetype plugin and package property as file path
Hello Maven users, When generating project from archetype in interactive mode user among other things provides package property. It would be handy if there was another property which would be generated from package property by replacing dots in package with directory separator, so that property could be referenced in filtered archetype resources (e.g. I'd like to reference resources from packaged filesets in assembly descriptor). Looking at archetype plugin docs and sources I can not find such behavior supported/implemented at the moment. Did I miss it? Or should I create a feature request? Regards, Stevo.
Re: Archetype plugin and package property as file path
Found it, packageInPathFormat. Wish there was archetype properties guide/doc similar to thishttp://docs.codehaus.org/display/MAVENUSER/MavenPropertiesGuideone. Regards, Stevo. On Tue, Dec 1, 2009 at 1:03 PM, Stevo Slavić ssla...@gmail.com wrote: Hello Maven users, When generating project from archetype in interactive mode user among other things provides package property. It would be handy if there was another property which would be generated from package property by replacing dots in package with directory separator, so that property could be referenced in filtered archetype resources (e.g. I'd like to reference resources from packaged filesets in assembly descriptor). Looking at archetype plugin docs and sources I can not find such behavior supported/implemented at the moment. Did I miss it? Or should I create a feature request? Regards, Stevo.
Re: Managing dependencies which are not in the Reposistory
Herehttp://jasperforge.org/plugins/espforum/view.php?group_id=112forumid=102topicid=45277you can find instructions on how to setup jasperreports maven repository. It seems 3.6.2 hasn't been published there yet, but 3.6.0 is and 3.6.2-snapshot too. You can use 3.6.0 and wait for official 3.6.2 to be published there, or download and install:install-file/deploy:deploy-file 3.6.2 to your local/corporate repository. In second case you have to provide 3.6.2 pom yourself, while maybe 3.6.2-snapshot pom and/or 3.6.2 release notes / documentation might be of some help. Regards, Stevo. On Mon, Nov 30, 2009 at 7:34 PM, Wayne Fay wayne...@gmail.com wrote: We need to use the latest release of Jasper Reports 3.2.6 However this library doesn't exist in a Maven Repository. How do we manage this dependency and all its transitive dependencies? Complain to the JasperReports people until they upload a proper pom for that version (and the jar). Alternatively, grab the previous version pom file, update the version tag, upload it to your corporate repo, and hope/pray you don't run into any conflicts or missing deps. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Invoke a different plugin goal based on profile
If you give same id to executions, regular one and one in the profile, when
profile is active it will override regular execution in its entirety (bound
phase, goals, configuration, ...)
Regards,
Stevo.
On Mon, Nov 30, 2009 at 9:08 PM, Jeff French j...@mdbconsulting.com wrote:
I have two related questions:
1. Can I define a profile that replaces the goal executed by a plugin,
rather than add to it?
2. Can I override the goal invoked for a plugin without duplicating the
entire plugin definition within a profile?
I'm using the assembly plugin (bound to the package phase) and a custom
descriptor to bundle a project's jar, startup script, etc. into a zip file
using assembly:single. That works fine.
During development we want to access the expanded contents of the zip file.
For that I can add the assembly:directory-single goal. Now I have both the
zip file and expanded directory. Rather than invoke both goals, however,
I'd
rather invoke assembly:single by default and assembly:directory-single
during development.
For question #1, I've gotten partially there by creating a 'dev' profile
that duplicates the default assembly (goal=single), but invokes a the
directory-single goal. This gives me only the zip file under normal
situations, but both when the profile is set to 'dev'.
For question #2, I tried using 'goal${assembly.goal}/goal' in my plugin
definition, setting a default value for the 'assembly.goal' property, and
changing the property's value in a profile. Unfortunately, Maven then gives
me the error:
LifecycleExecutionException: '${assembly.goal}' was specified in an
execution, but not found in the plugin
so it looks like the property is not expanded for the goal element.
Thanks for any pointers.
Jeff
--
View this message in context:
http://old.nabble.com/Invoke-a-different-plugin-goal-based-on-profile-tp26580967p26580967.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Problem with maven-release-plugin
Maybe this http://jira.codehaus.org/browse/MRELEASE-467 known issue is
related.
Regards,
Stevo.
On Thu, Nov 19, 2009 at 11:50 AM, Stephen Connolly
stephen.alan.conno...@gmail.com wrote:
Two options:
1. change your build so that it will work with clean verify whenyour
local repository has been blown away. Typically this is because you
are using goals like dependency:copy and not
dependency:copy-dependencies
2. change the preparation goals in the release plugin to clean install.
#2 is a hack, but may be necessary. In the long run #1 is to be preferred.
-Stephen
2009/11/19 Peter Niederwieser pnied...@gmail.com:
In my multi-module project, I have a Maven plugin A and a module B that
uses
version ${project.version} of A (all modules have the same version
number).
release:prepare changes version A from 0.3-SNAPSHOT to 0.3, but then
fails
while processing B because it cannot find version 0.3 of A. Any ideas how
to
solve this problem?
Cheers,
Peter
--
View this message in context:
http://old.nabble.com/Problem-with-maven-release-plugin-tp26421272p26421272.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
maven-assembly-plugin: referencing assembly id from component descriptor
Hello Maven users, Is there a way to reference assembly id from component descriptor? Is it exposed as some property? Regards, Stevo.
Re: Putting a Release in the Repository
http://weblogs.java.net/blog/2008/08/31/using-maven-release-plugin http://www.vineetmanohar.com/2009/10/23/how-to-automate-project-versioning-and-release-with-maven/ Regards, Stevo. On Thu, Nov 19, 2009 at 8:19 PM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: mvn release:perform after the prepare Sent from my [rhymes with tryPod] ;-) On 19 Nov 2009, at 19:11, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: I am using the prepare goal of the Maven Release Plugin to publish a release in SVN. The result of course is that the poms in the trunk and in my local copy are updated to the next version snapshot. What I want to do is to take the release in SVN and publish it to my local Nexus repository in the releases portion of the site. I am doing the same for snapshots by using the Maven Deploy Plugin. I suppose my question is how can I get the Maven Release and Deploy Plugins to work in tandem so that I can release something to SVN and then have it be deployed to my local Nexus repository. Thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
Likely because dependency plugin has bugs, and I'm suspecting that your issue is similar/related to this http://jira.codehaus.org/browse/MDEP-204one already reported. But it's odd that it doesn't fail for you at module mod_c, as build reactor should have ordered mod_c to be built/processed before mod_d. Just guessing, maybe this mojo doesn't use maven reactor at all, and probably mod_c is ordered in list of modules in your parent module after mod_d. Regards, Stevo. On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold jgold...@gmail.com wrote: Hi -- I'm trying to track down some other depdendency issues in my project using dependencies:tree, but am getting errors that a module isn't found. I have my project set up with a parent pom and a list of modules, each referencing the parent, etc. Essentially, I have this: pom.xml # parent, references mods a, b, c, d in modules mod_a/pom.xml # module, no module dependencies mod_b/pom.xml # module, no module dependencies mod_c/pom.xml # module, declared dependency on mod_b mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c From the root workspace directory, I can run things like 'compile' or 'jar:jar' just fine, but for some reason 'dependencies:tree' is failing when it gets to mod_d, complaining that it can't find mod_c. Any ideas what I'm doing wrong? jon - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Why would 'mvn dependencies:tree' fail while 'mvn compile' works?
You could try to install your project first, and after that run dependency:tree. Regards, Stevo. On Wed, Nov 18, 2009 at 7:05 PM, Jonathan Gold jgold...@gmail.com wrote: Thanks for the response. In fact, I have all of my modules listed in depdendency order in the parent pom, so it's quite odd indeed. Thanks for the tip -- I voted for the bug, for what it's worth. jon On Wed, Nov 18, 2009 at 06:59:41PM +0100, Stevo Slavić wrote: Likely because dependency plugin has bugs, and I'm suspecting that your issue is similar/related to this http://jira.codehaus.org/browse/MDEP-204one already reported. But it's odd that it doesn't fail for you at module mod_c, as build reactor should have ordered mod_c to be built/processed before mod_d. Just guessing, maybe this mojo doesn't use maven reactor at all, and probably mod_c is ordered in list of modules in your parent module after mod_d. Regards, Stevo. On Wed, Nov 18, 2009 at 6:37 PM, Jonathan Gold jgold...@gmail.com wrote: Hi -- I'm trying to track down some other depdendency issues in my project using dependencies:tree, but am getting errors that a module isn't found. I have my project set up with a parent pom and a list of modules, each referencing the parent, etc. Essentially, I have this: pom.xml # parent, references mods a, b, c, d in modules mod_a/pom.xml # module, no module dependencies mod_b/pom.xml # module, no module dependencies mod_c/pom.xml # module, declared dependency on mod_b mod_d/pom.xml # module, declared depdenency on mod_a, mod_b, mod_c From the root workspace directory, I can run things like 'compile' or 'jar:jar' just fine, but for some reason 'dependencies:tree' is failing when it gets to mod_d, complaining that it can't find mod_c. Any ideas what I'm doing wrong? jon - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [Maven Assembly Plugin] Deploy assembly
http://maven.apache.org/plugins/maven-assembly-plugin/plugin-info.html Regards, Stevo. On Fri, Nov 13, 2009 at 10:51 AM, rgubler2 rgub...@init-ka.de wrote: Anders Hammar wrote: A quick Internet search gives the answer: http://old.nabble.com/Maven-assembly-plug-in-and-deploy-not-happening--td18161292.html /Anders Hmm, I changed execution idmake-assembly/id phasepackage/phase goals goalassembly/goal /goals /execution to execution idmake-assembly/id phasepackage/phase goals goalattach/goal /goals /execution and get now the following error: 'attach' was specified in an execution, but not found in the plugin What's wrong? Yours Rüdiger -- View this message in context: http://old.nabble.com/-Maven-Assembly-Plugin--Deploy-assembly-tp26333720p26333970.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Using the Maven Deploy Plugin
http://maven.apache.org/pom.html#Repository Regards, Stevo. On Thu, Nov 12, 2009 at 9:30 PM, Neil Chaudhuri nchaudh...@potomacfusion.com wrote: We have an internal Maven repository that I can view in my browser at http://myserver:8081/nexus/content/repositories/myRepo/. I am simply trying to upload my generated WAR file to this repository. I have set up credentials in settings.xml, and my pom is set up as follows: repository idmy-maven-repo/id nameInternal Maven Repository/name urlfile://myserver:8081/nexus/content/repositories/myRepo//url /repository This work great and I get a BUILD SUCCESSFUL message. The problem is that when I go back to http://myserver:8081/nexus/content/repositories/myRepo/, I can't see it. Any ideas as to what is going on here? Thanks.
Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.1.2/version reportSets reportSet reports reportproject-team/report reportcim/report reportscm/report /reports /reportSet /reportSets /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6.1/version configuration !-- Default configuration for all reports -- detectOfflineLinkstrue/detectOfflineLinks !-- detectLinkstrue/detectLinks -- detectJavaApiLinktrue/detectJavaApiLink linksourcetrue/linksource useStandardDocletOptionstrue/useStandardDocletOptions charsetUTF-8/charset encodingUTF-8/encoding docencodingUTF-8/docencoding breakiteratortrue/breakiterator versiontrue/version
Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml
Hello Doug, Maybe I'm wrong but I have a feeling that you either haven't read completely my initial reply or didn't understand it. In that parent pom snippet you've configured maven-project-info-reports pluginhttp://maven.apache.org/plugins/maven-project-info-reports-plugin/not to generate index report, only cim, scm, and project-team reports. Regards, Stevo. 2009/11/12 Doug Daniels ddani...@webwars.com If I define a src/site/site.xml, and src/site/apt/index.apt in my parent and child projects, it will generate an index.html for all child subproject modules. I did have to do the workaround of defining a distributionManagement for each subproject module, but that's not that bad. -Original Message- From: Doug Daniels [mailto:ddani...@webwars.com] Sent: Wednesday, November 11, 2009 4:48 PM To: Maven Users List Subject: RE: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Sorry about that, you're correct, I had renamed some things in my pom.xml like my modules to make my example clearer and I forgot to rename that properly. I'm wondering if anyone knows of any issues with the site plugin and why my subproject modules would generate all the source files except for the index.html. I don't specify any src/site/ files like src/site/site.xml or src/site/apt/index.apt. -Original Message- From: Stevo Slavić [mailto:ssla...@gmail.com] Sent: Wednesday, November 11, 2009 4:30 PM To: Maven Users List Subject: Re: maven site plugin not deploying subprojects in a multimodule project or generating indexhtml Hello Doug, That modules section seems to be wrong, module../moduleA-common/module should probably be module../moduleA/module. Personally I prefer putting child module directories within parent - its natural, some plugins and tools used to have problems with relative paths, and you don't have to set relativePath in child modules. In maven-project-info-reports-plugin consider adding index report to the list. One more tip, specify site plugin version in pluginManagement for build to be reproducible - now it's not clear which version of the plugin you're using, it's determined by maven version which is also not known. Regards, Stevo. On Wed, Nov 11, 2009 at 10:07 PM, Doug Daniels ddani...@webwars.com wrote: I have a multimodule project that I want to deploy a site for, but it seems like my site deployment distributionManagement configuration is not being inherited by subproject child modules. parent - moduleA - moduleB They are located relative to each other /parent/ /moduleA/ /moduleB/ When I run: mvn site-deploy -P documentation My parent project is deployed properly to: scp://devServer/documentation/webwars/ But none of the subprojects like moduleA or module is deployed there as I'd expect if child modules inherit parent distributionManagement: scp://devServer/documentation/webwars/moduleA scp://devServer/documentation/webwars/moduleB Here's my parent pom.xml, I removed some extraneous details and report plugins (I included my javadoc plugin which is a bit funky using APIViz and aggregate to ensure aggregate parent javadocs and child javadocs use APIViz properly.): project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi= http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation= http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdcom.webwars/groupId artifactId parent/artifactId packagingpom/packaging version1.0-SNAPSHOT/version nameparent/name distributionManagement site idwebwarsDev.website/id urlscp://devServer/documentation/webwars//url /site /distributionManagement modules module../moduleA-common/module module../moduleB/module /modules profiles profile iddocumentation/id build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-pmd-plugin/artifactId executions execution idverify_pmd/id phaseverify/phase goals goalpmd/goal /goals configuration linkXreftrue/linkXref minimumTokens20/minimumTokens targetJdk1.6/targetJdk /configuration /execution
Configuring source plugin to skip execution
Hello Maven users, Is there a way to configure source plugin to skip execution for a single module, or at least not to fail build because module doesn't contain any sources? In my project source plugin is being run by release plugin's perform goal (with default useReleaseProfile=test parameter value), and it fails a build because a war module has no sources. That war module just depends on a jar module and is used to start spring application context from that jar in web application container. Temporary workaround was to set useReleaseProfile to false but this skips releasing source and javadoc for all modules. Not sure if configuring release plugin not to useReleaseProfile for that war module only would do the trick. Regards, Stevo.
