Re: Dependencies - need help/advice: Getting the latest version of a specific (not all) dependencies
First, you are right... I misread. When I look at the maven plugins in pluginManagement I see v2 and v3: clean=3.1.0, compiler=3.8.1, surefire=2.22.1, jar=3.0.2, install=2.5.2, deploy=2.8.2, site=3.7.1, project-info-reports=3.0.0. Still, it is > 2.0 so LATEST is no longer supported as a version tag. Let's see if I can explain it better: - I emptied the local maven repository of every single one of my projects, literally went in the folder net/myorg and deleted everything from there. - Then I rebuilt in order. This included app1 and app2 (that has app1 as one of its dependencies) which showed up in the local repository folder. Obviously, both generated snapshot jars had a timestamp of yesterday. - Finally I opened app2-0.0.1-SNAPSHOT.jar and looked for the included app1-0.0.1-SNAPSHOT.jar file. I expected to see yesterday's timestamp on the JAR file since I had just done a maven clean install. Nope, it had a January timestamp, and the contents were old. So, it is clear that: (1) IntelliJ is caching the JARs it uses for a project somewhere. And giving it the commands to reload dependencies or the POM fail if the version number has not changed... since I am seeing a file from January. Also, the IntelliJ setting "Always update snapshots" fails as well. This may be an Maven issue or it might be a quirk of IntelliJ, my suspicion is that IntelliJ relied on the old 2.x maven behavior for that setting. Sadly I am not knowledgeable enough to know. (2) Looking for an alternative all I found for 3.0 and above Maven was the use of version ranges in the dependency entry of the app2 POM. That would require updating the version after even a tiny change in app1, but at least it would not require updating the version in the the pom of the myriad of "app2"s that we have, unless we wanted to. I suspect this is what versions-maven-plugin does but that I botched it when I tried to use it, as its documentation is very confusing for a beginner and they don't provide a single complete example of a POM that uses it. The symptom was an error popping up in the POM itself, long before trying to do a build. I think the error was either the "[0.0.1, 0.0.999)-SNAPSHOT" tag, or my missing something in plugin management. Conclusion: It seems that the cleanest way to solve this is to use the versions-maven-plugin, but I am not using it right. Any help on this would be great. A simple working example of a POM that uses version-maven-plugin with a version range would be ideal. On 9/23/2022 1:25 PM, Nils Breunese wrote: Hi Bruno, It’s not completely clear to me what your issue is exactly. Is ’the old cached version from January’ that you refer to an artifact with a snapshot version or a release version? If it is a snapshot version, it depends on the update policy whether Maven will use a locally cached snapshot or whether it will try to fetch an update from the the configured repository. If there is no explicit update policy configured, I believe the default is to look for updates once a day. You can force Maven to update snapshots by using the -U (or --update-snapshots) flag. If your dependency is a release version, then there can be only one artifact for that version and if you have it cached locally, it should be identical to that version of the artifact on the repository server. Maven 4 has not been released yet, are you sure you are (and should be) using that version? Version 3.8.6 is the current latest release [0]. To avoid having to manually update dependencies my team has a scheduled task to run Renovate [1] in our applications' CI pipelines to check for dependency updates. Renovate automatically creates a branch and a merge request whenever a dependency update is found. There are more tools like Renovate. For instance GitHub also provides Dependabot [2]. Maven Versions Plugin [3] can also be used to update dependencies. Nils. [0] https://maven.apache.org/download.cgi [1] https://github.com/renovatebot/renovate [2] https://docs.github.com/en/code-security/dependabot [3] https://www.mojohaus.org/versions-maven-plugin/ Op 23 sep. 2022, om 14:58 heeft Bruno het volgende geschreven: I apologize for the length of this email, I could not think of a shorter way to present the issue/questions that is clear enough. --- My environment involves the usual many open source dependencies (which I control by specifying the versions to use in a master POM), but also a large number of frequently changing internally built dependencies and a huge number of applications that rely on these dependencies. Changes on these internally built dependencies are carefully controlled so that they are always backwards compatible. In over a decade before we used maven we had a single instance of these dependencies and we never - not once - had a version conflict problem. But the default mode for Maven is to updat
Dependencies - need help/advice: Getting the latest version of a specific (not all) dependencies
I apologize for the length of this email, I could not think of a shorter way to present the issue/questions that is clear enough. --- My environment involves the usual many open source dependencies (which I control by specifying the versions to use in a master POM), but also a large number of frequently changing internally built dependencies and a huge number of applications that rely on these dependencies. Changes on these internally built dependencies are carefully controlled so that they are always backwards compatible. In over a decade before we used maven we had a single instance of these dependencies and we never - not once - had a version conflict problem. But the default mode for Maven is to update the version number even for a tiny change and then to manually update the version of the dependency in every single project that depends on it. Since we have a lot of those, this is a horribly error prone process leading to applications that crash because they are using the wrong version of a dependency. As an example... one of our crashing applications that was built yesterday was found to contain a dependency JAR from January!!! when it should have contained a JAR that was also built yesterday. Things that we tried: - Builds and executions *INSIDE* of IntelliJ work beautifully. It always finds the latest code and it always runs on the local integrated server perfectly. _The problem happens in the JARs/WARs of applications placed into the Maven local repository_. - In IntelliJ we tried checking Settings/Build,Execution,Deployment/BuildTools/Maven/"Always update snapshots" and not change the version number between releases so that it would include a fresh copy of the dependency during build, but even *completely wiping out* the local repository (the only one in use at this moment) it still used the old cached version from January. - Next I tried to use the LATEST syntax in the POM. But LATEST was removed after Maven 2 and we are using Maven 4. - Finally I tried to use [0.0.1, 0.0.999)-SNAPSHOT in the hope of simply updating the version number of the dependency during development/tests and only updating the formal dependency version to 1.0.0 at release time but Maven rejected the syntax. It is quite possible that the syntax I used is incorrect, but sadly the documentation is not very clear and provides no complete examples that I could inspect or duplicate. *QUESTIONS*: 1) Was one of the above methods supposed to work? If yes, what did I do wrong and how do I fix it? 2) If none of the above methods is supported anymore (Maven 4), what method should I be using? 3) Is there any other tool - besides Maven - that I should be using for these builds.
Maven Book recommendation
It became very clear to me that my current approach of googling tutorials, guides and solutions is a wildly inadequate approach to learn Maven. Mainly because all of those are either far too basic for "real life" projects, or because they assume prior knowledge that I don't yet have. So, I am looking to buy a good book to methodically learn all I need about Maven. Because of how I learn best I would like to find a book that uses the following as its presentation approach: * It must be gradual, starting from the assumption that I know nothing and only learn what is taught in the book. * New concepts must include sample code that I can type and test, either complete code or as an extension to a previous example. Absolutely no "loose snippets" that assume prior knowledge (for example this is what makes most formal Spring documentation completely useless to me, as I often can't follow it to a complete functioning solution, and I had similar but not as severe issues with the formal Apache Maven documentation). * The end of each chapter must have exercises that I can code and run to test my understanding, with the ability to download the solution from a website in those cases when my code fails to function correctly. * Not essential but it would be ideal if the book was available in electronic form and readable through an ebook reader that functions on a Microsoft Surface tablet (Windows 10/11) and remembers the last page I read (even better if position syncs between the tablet and my desktop so that I can continue reading on either). If _you learned Maven from a book that matches at least the first 3 criteria_, please recommend it. I'd greatly appreciate it.
Re: SOLVED: Strange ClassCastException during maven install
Thank you Nils, I apologize for my ignorance, as I am still fairly new to Maven. I understand the basics well enough but it is very obvious to me that there is a lot of specialized knowledge that is assumed and not well explained in most of the tutorials/guides I googled. My library is a primary component of an in-house framework like yours. I am at the start of modernizing and strengthening security of the framework and all of my older projects from plain Java 8+Spring to Maven, Java 17, Spring Boot, strong/secure authentication mechanisms, and relying on a vault. I am not *yet* migrating to Docker and Kubernetes (since my upper management did not approve it and also because it would be a steep learning curve on top of the other new things) but that seems to be a natural next step. I read that BOM article and many others that I googled. If I understood correctly, it seems that the ideal POM structure is: * To have a master BOM POM that specifies key library versions and pre-supplied BOMs (like spring-framework-bom) in the dependencyManagement section. * Maybe have a couple "parent" POMs for the different types of projects (like REST service, webapp) that inherit from the master BOM POM. * And finally inheriting from one of those parent POMs in the individual project POMs. *First question*: Is that correct? *Second question*: Where do I place the master BOM POM and the Parent POMs so that they end up in the local Maven repository and visible to project builds? I suspect that the answer might be to create a dummy Eclipse project with multiple POMs and no code, then use something like the following but I am not sure: |||<||parent||>| |||<||groupId||>com.mydomain| |||<||artifactId||>poms| |||<||version||>0.0.1-SNAPSHOT| |||<||relativePath||>bom-pom.xml| |||<||parent||>| |||<||groupId||>com.mydomain| |||<||artifactId||>poms| |||<||version||>0.0.1-SNAPSHOT| |||<||relativePath||>parent-rest-pom.xml| On 1/26/2022 5:26 AM, Nils Breunese wrote: Bruno Melloni wrote: If I understood the explanation, it seems that the spring boot starter (parent) defaults to slf4j and that the code above removes that support while replacing it with log4j2. I don’t know what your goals are for this library, but I do wonder if it’s a good idea to let a library depend on Spring Boot starters. I would expect that more gets pulled in than you actually want or need, as you’ve found. Spring Boot starters are just artifacts that depend on one ore more other artifacts and are generally meant to be used by applications. Libraries typically depend on one or more those ‘lower level’ artifacts directly to explicitly define what they depend on and not pull in too much. I maintain an in-house framework based on Spring Boot myself and I’d recommend importing the spring-boot-dependencies BOM of the Spring Boot version you’re targeting with your library into your library’s section. That will allow you to use any dependency managed by Spring Boot without having to specify its version. https://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html#bill-of-materials-bom-poms Nils. P.S. I notice your old POM uses Log4J 2.15.0, which is vulnerable to the pretty serious Log4Shell vulnerabilities.
SOLVED: Strange ClassCastException during maven install
Was tricky to find through google, but I found that replacing the log4j
entries in the new POM (bottom of the original email) with the following
will solve the issue:
org.springframework.boot
spring-boot-starter
org.springframework.boot
spring-boot-starter-logging
org.springframework.boot
spring-boot-starter-log4j2
If I understood the explanation, it seems that the spring boot starter
(parent) defaults to slf4j and that the code above removes that support
while replacing it with log4j2.
On 1/25/2022 11:33 AM, Bruno Melloni wrote:
I wrote and used a custom library that includes some log4j aware
classes. Was working perfectly when built as a standard Java JAR. I
am converting the POM to rely on a few Spring Boot starters as a way
to simplify it.
All went well until I run "Maven Install", when I got the following
ClassCastException even though my code never uses slf4j: "*class
org.apache.logging.slf4j.SLF4JLogger cannot be cast to class
org.apache.logging.log4j.core.Logger
(org.apache.logging.slf4j.SLF4JLogger and
org.apache.logging.log4j.core.Logger are in unnamed module of loader
'app')*"
The issue is probably trivial and I suspect that one or more of the
starters (possibly the TEST portion) relies on slf4j and I somehow
need to provide a library to accept slf4j and automatically convert to
log4j logging.
Can anybody see where I messed up, and know how to fix it?
*This is the old (good) POM*:
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
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
net.cndc
libCore
0.0.1-SNAPSHOT
5.8.2
org.apache.commons
commons-text
1.9
org.apache.logging.log4j
log4j-api
2.15.0
org.apache.logging.log4j
log4j-core
2.15.0
io.jsonwebtoken
jjwt
0.9.1
javax.xml.bind
jaxb-api
2.3.1
com.fasterxml.jackson.core
jackson-databind
2.12.5
org.apache.httpcomponents
httpclient
4.5.13
javax.servlet
javax.servlet-api
4.0.1
provided
org.springframework
spring-jdbc
5.3.9
org.springframework.security
spring-security-web
5.5.2
org.springframework.security
spring-security-core
5.5.2
org.springframework.security
spring-security-config
5.5.2
org.springframework
spring-jdbc
5.3.10
com.github.oshi
oshi-core
${oshi.version}
org.apache.commons
commons-lang3
3.12.0
junit
junit
4.13.2
test
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
15
*And this is the POM that causes the error*:
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
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.springframework.boot
spring-boot-starter-parent
2.6.3
net.cndc
core-lib
0.0.1-SNAPSHOT
core-lib
Core library for all CNDC apps
17
5.8.2
org.springframework.boot
spring-boot-starter-security
org.springframework.boot
spring-boot-starter-web
org.springframework.boot
spring-boot-starter-test
test
org.springframework.security
spring-security-test
test
org.apache.commons
commons-text
1.9
org.apache.commons
commons-lang3
org.apache.logging.log4j
log4j-api
org.apache.logging.log4j
log4j-core
com.github.oshi
oshi-core
${oshi.version}
com.fasterxml.jackson.core
jackson-databind
org.apache.httpcomponents
httpclient
org.springframework
spring-jdbc
org.springframework.boot
spring-boot-maven-plugin
Strange ClassCastException during maven install
I wrote and used a custom library that includes some log4j aware
classes. Was working perfectly when built as a standard Java JAR. I am
converting the POM to rely on a few Spring Boot starters as a way to
simplify it.
All went well until I run "Maven Install", when I got the following
ClassCastException even though my code never uses slf4j: "*class
org.apache.logging.slf4j.SLF4JLogger cannot be cast to class
org.apache.logging.log4j.core.Logger
(org.apache.logging.slf4j.SLF4JLogger and
org.apache.logging.log4j.core.Logger are in unnamed module of loader
'app')*"
The issue is probably trivial and I suspect that one or more of the
starters (possibly the TEST portion) relies on slf4j and I somehow need
to provide a library to accept slf4j and automatically convert to log4j
logging.
Can anybody see where I messed up, and know how to fix it?
*This is the old (good) POM*:
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
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
net.cndc
libCore
0.0.1-SNAPSHOT
5.8.2
org.apache.commons
commons-text
1.9
org.apache.logging.log4j
log4j-api
2.15.0
org.apache.logging.log4j
log4j-core
2.15.0
io.jsonwebtoken
jjwt
0.9.1
javax.xml.bind
jaxb-api
2.3.1
com.fasterxml.jackson.core
jackson-databind
2.12.5
org.apache.httpcomponents
httpclient
4.5.13
javax.servlet
javax.servlet-api
4.0.1
provided
org.springframework
spring-jdbc
5.3.9
org.springframework.security
spring-security-web
5.5.2
org.springframework.security
spring-security-core
5.5.2
org.springframework.security
spring-security-config
5.5.2
org.springframework
spring-jdbc
5.3.10
com.github.oshi
oshi-core
${oshi.version}
org.apache.commons
commons-lang3
3.12.0
junit
junit
4.13.2
test
org.apache.maven.plugins
maven-compiler-plugin
3.8.1
15
*And this is the POM that causes the error*:
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
https://maven.apache.org/xsd/maven-4.0.0.xsd";>
4.0.0
org.springframework.boot
spring-boot-starter-parent
2.6.3
net.cndc
core-lib
0.0.1-SNAPSHOT
core-lib
Core library for all CNDC apps
17
5.8.2
org.springframework.boot
spring-boot-starter-security
org.springframework.boot
spring-boot-starter-web
org.springframework.boot
spring-boot-starter-test
test
org.springframework.security
spring-security-test
test
org.apache.commons
commons-text
1.9
org.apache.commons
commons-lang3
org.apache.logging.log4j
log4j-api
org.apache.logging.log4j
log4j-core
com.github.oshi
oshi-core
${oshi.version}
com.fasterxml.jackson.core
jackson-databind
org.apache.httpcomponents
httpclient
org.springframework
spring-jdbc
org.springframework.boot
spring-boot-maven-plugin
Dumb question: How to deploy a command line app?
Given that the whole point of using Maven is to "not have to worry about dependencies" I am having the most ironic (and probably trivial) problem: - Using Maven in Eclipse. - I wrote a very simple utility. It builds as part of a JAR that will normally be used by other apps, but this utility can be executed from the command line. - So, to run the utility on a server I did a RunAs/Maven/Install. It placed the JAR in the expected .m2 location but... none of the JARs it depends on are there. How do I tell Eclipse to run a Maven Install that puts *everything* needed by the project to run in one folder or folder tree? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Best practice to update dependency versions for *many* projects to the current version
I have been developing in Java almost from the beginning, but have not used Maven for much more than a few personal test apps. I am now about to migrate nearly 100 applications to Maven and I am a bit concerned about how to manage dependency versions across that many projects in the future. For a single app it is simple, go into the POM, modify the version of the dependency, then verify that nothing broke due to newly unsupported methods and fix the issues. But if you have a lot of applications, the above method becomes very time consuming and manual. QUESTION: Is there a best practice (or perhaps tools that help) for how to handle updating the dependency versions for that many applications? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [VOTE] Retire Maven Ant Plugin
Non-binding vote: +1 On Tue, May 28, 2019 at 11:55 AM Robert Scholte wrote: > Hi, > > The Apache Maven project consist of about 100 (sub)projects. Due to the > small number of volunteers and the huge amount of code to maintain we're > missing enough space to make real progress on all these projects, including > our ambitious ideas for the next major version(s) of Maven itself. > To be able to gain more focus we need to criticize the current subprojects > and decide if it is worth maintaining. > > The goal of the Apache Maven Ant Plugin it to generate Ant build files > based on a pom.xml and was released for the last time in December 2014. Due > to the different ways that Ant and Maven work I don't think it makes > sense anymore to maintain a plugin to transform Maven files to Ant. > See https://maven.apache.org/plugins/maven-ant-plugin/ [ > https://maven.apache.org/plugins/maven-ant-plugin/] > > To be clear, this is NOT the plugin you can use to run Ant within Maven; > that's the maven-antrun-plugin. > > I therefore propose that we retire the maven-ant-plugin. > > I don't think it makes sense to do a final release. Instead we should > update the documentation and freeze the codebase. > > The process for retiring a plugin is described here: > https://maven.apache.org/developers/retirement-plan-plugins.html > > The vote is open for 72 hours. > [ ] +1 Yes, it's about time > [ ] -1 No, because...
Maven Archetype with defaults for version and package properties
Hi all,
I've been trying to define a Maven Archetype which would contain properties
`package` and `version` with default values:
Inside archetype-metadata.xml, I included the following:
${groupId}
1.0-SNAPSHOT
Despite this configuration, the generation fails:
[ERROR] Archetype IT 'basic' failed: Missing required properties in
archetype.properties: package, version
Any clue?
Bruno Borges
[image: https://]brunoborges.io
<https://brunoborges.io?promo=email_sig&utm_source=product&utm_medium=email_sig&utm_campaign=edit_panel&utm_content=plaintext>
How to activate proxy from settings.xml using CLI
Looking at docs for 3.3.9 [1], I noticed the following: proxies/proxy* List *(Many)* Configuration for different proxy profiles. Multiple proxy profiles might come in handy for anyone working from a notebook or other mobile platform, to enable easy switching of entire proxy configurations by simply specifying the profile id, again either from the command line or from the defaults section below. It says that I can activate a proxy defined in settings.xml using command-line, but there is no option when looking at *mvn -h. * Perhaps I didn't look well enough, but I couldn't find in docs how to activate a proxy using CLI. [1] https://maven.apache.org/ref/3.3.9/maven-settings/settings.html#class_settings *Bruno Borges* +1 (650) 454-9628 *www.brunoborges.com <http://www.brunoborges.com>*
help... i just wanted to download a library...
Hello! i wanted to download http://www.miglayout.com/mavensite/ to play with it, and got embarked into a horribly frustrating journey into unknown countries making me cry for forgotten times when you could simply download a piece of software to try it out... to get the latest version of that library (which coincides with the stuff as advertised by the doc, making thus the latest version an obligation) you need to get it through maven... well.. i managed to get maven installed... and then the problems began first i tryed it cvs like style: mvn http://www.miglayout.com/mavensite/ but it exploded in my face, so i went to read the doc about maven... reading through the documentation, i lost my afternoon reading a lot of stuff about how set up a project with maven, how mantain it and the philosophy behind maven, but the simple fact that i don't care at all about that stuff, and that i just want a piece of software only available through maven and how to get it, totally eluded me and before i go get my head banging against the next wall, maybe someone can point me out how to do this surely simple task? thanks a lot! -- ciao bboett == bbo...@adlp.org http://bboett.free.fr === - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to activate proxies
I see that there's an option for proxies under settings.xml... But how to toggle this flag through command-line interface? Thanks, *Bruno Borges* (21) 7672-7099 *www.brunoborges.com*
Using Tomcat plugin to run webapp in a production environment
Have anyone experienced running a WAR project in production based on the Maven Tomcat plugin? We are considering to use it as we think it is simpler than installing a whole Tomcat setup and deploying WAR files . Our usecase has only one project and no more modules are planned. Each one on its own VM at Amazon EC2. All the configuration can be passed on to the Tomcat Plugin through server.xml and context.xml. Any feedback, comments or critics are welcome. Best regards, Bruno Borges www.brunoborges.com.br +55 21 76727099 "The glory of great men should always be measured by the means they have used to acquire it." - Francois de La Rochefoucauld
Re: gpg:sign and repository:bundle-create produce bad signatures
On 08/06/10 16:52, Bruno Harbulot wrote: On 08/06/10 15:24, Bruno Harbulot wrote: I'm trying to follow the procedure for manual upload as described on this page: http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/ I've set up my GPG key and it seems to work mostly well, except that the .asc file produced by this is incorrect: $ mvn source:jar javadoc:jar package gpg:sign repository:bundle-create $ cd target $ gpg --verify jar.asc gpg: Signature made Tue 08 Jun 2010 15:17:32 BST using RSA key ID E39C0477 gpg: BAD signature from "..." In contrast, if I don't use repository:bundle-create, it works fine: $ mvn source:jar javadoc:jar package gpg:sign $ cd target $ gpg --verify jar.asc gpg: Signature made Tue 08 Jun 2010 15:19:25 BST using RSA key ID E39C0477 gpg: Good signature from "..." Any idea what I might be doing wrong? I've tried with and without the explicit plugin settings in the POM file as described on this page, but this doesn't change the outcome: http://www.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/ I've looked a bit further into this problem. It looks like repository:bundle-create modifies the content of the jar file it bundles (not the bundle, but the artifact bundled). The only modifications I can see in the jar is the change of timestamp of this file (and containing directories): META-INF/maven///pom.properties and META-INF/maven/remote-resources.xml The actual content is unchanged. However insignificant, these changes modify the jar file and thus breaks the signature. It seems to be due to the fact repository:bundle-create runs jar:jar again. Is it possible to tell it to skip it when running repository:bundle-create? I've worked around the problem by putting this in the POM: performRelease true org.apache.maven.plugins maven-gpg-plugin package sign Then, I've used this, without gpg:sign: mvn -DperformRelease=true clean source:jar javadoc:jar install repository:bundle-create After that, the upload to oss.sonatype.org worked just fine! Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: gpg:sign and repository:bundle-create produce bad signatures
On 08/06/10 15:24, Bruno Harbulot wrote: I'm trying to follow the procedure for manual upload as described on this page: http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/ I've set up my GPG key and it seems to work mostly well, except that the .asc file produced by this is incorrect: $ mvn source:jar javadoc:jar package gpg:sign repository:bundle-create $ cd target $ gpg --verify jar.asc gpg: Signature made Tue 08 Jun 2010 15:17:32 BST using RSA key ID E39C0477 gpg: BAD signature from "..." In contrast, if I don't use repository:bundle-create, it works fine: $ mvn source:jar javadoc:jar package gpg:sign $ cd target $ gpg --verify jar.asc gpg: Signature made Tue 08 Jun 2010 15:19:25 BST using RSA key ID E39C0477 gpg: Good signature from "..." Any idea what I might be doing wrong? I've tried with and without the explicit plugin settings in the POM file as described on this page, but this doesn't change the outcome: http://www.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/ I've looked a bit further into this problem. It looks like repository:bundle-create modifies the content of the jar file it bundles (not the bundle, but the artifact bundled). The only modifications I can see in the jar is the change of timestamp of this file (and containing directories): META-INF/maven///pom.properties and META-INF/maven/remote-resources.xml The actual content is unchanged. However insignificant, these changes modify the jar file and thus breaks the signature. It seems to be due to the fact repository:bundle-create runs jar:jar again. Is it possible to tell it to skip it when running repository:bundle-create? Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
gpg:sign and repository:bundle-create produce bad signatures
Hello, I'm trying to follow the procedure for manual upload as described on this page: http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/ I've set up my GPG key and it seems to work mostly well, except that the .asc file produced by this is incorrect: $ mvn source:jar javadoc:jar package gpg:sign repository:bundle-create $ cd target $ gpg --verify jar.asc gpg: Signature made Tue 08 Jun 2010 15:17:32 BST using RSA key ID E39C0477 gpg: BAD signature from "..." In contrast, if I don't use repository:bundle-create, it works fine: $ mvn source:jar javadoc:jar package gpg:sign $ cd target $ gpg --verify jar.asc gpg: Signature made Tue 08 Jun 2010 15:19:25 BST using RSA key ID E39C0477 gpg: Good signature from "..." Any idea what I might be doing wrong? I've tried with and without the explicit plugin settings in the POM file as described on this page, but this doesn't change the outcome: http://www.sonatype.com/people/2010/01/how-to-generate-pgp-signatures-with-maven/ Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
On 19/05/2010 00:41, Brian Fox wrote: The MAVENUPLOAD issue you refer to was processed by hand. This is something we've worked to stop and automate, so it's not really relevant what happened it was 2 years ago. That said, I don't know if LICENSE.txt inside the new bundle format would be handled any differently because LICENSE.txt is not a proper maven artifact. foo-1.0-licence.txt is another story. Put that inside a bundle and it will be preserved. Any solution that includes the license as a file inside the m2 namespace will have to follow the m2 namespace conventions. Maven Central gets all of its artifacts via rsync connections to various repos. If developers put stuff without the license in their sync source, well then it won't have it when we sync it. The rsyncs as I mentioned before is something we are actively working on winding down, but we can't just flip the switch overnite, projects need time to update to a forge and to update their process. This is an iterative process, I'd love to flip a switch tomorrow and have all artifacts subject to a new standard but it's not practical. I understand it's not easy. That's great work and I appreciate the effort. It's been an ongoing battle just getting basic validation and gpg signatures. Indeed, trust management and validation are always problematic. All that said, I don't know how beneficial the addition of a license as a file in the repo really is. Instead the license inside the pom should be validated, and if appropriate included inside the jars. We _do not_ modify artifacts that are uploaded, and I'll make sure our automated approach rejects jars that have files with non-conforming files in them. Unfortunately this means a bundle with LICENSE inside it will be rejected, but then you would at least know to use foo-xx-license.txt instead if you want it to be included with your artifacts. Ah great, so sorry, that's what I didn't really understand and was asking clarifications about in the first place. I guess that's mainly a documentation issue then, considering the blog entry you sent wasn't clearly linked from the maven.apache.org site (as far as I could tell) and that I couldn't work out how "Sonatype [would] perform some due diligence to make sure that the artifact has a license compatible with unrestricted distribution." For my next release which I'm planning to bundle over the next few days, I've put the licence within the comments element: http://jsslutils.googlecode.com/svn/trunk/jsslutils/pom.xml Does that follow more or less the new guidelines? Are you saying that I should have jsslutils-1.0-licence.txt next to the other jars in the bundle instead (sorry, I can't see licence files in the screenshots on that blog entry). Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
On 18/05/2010 20:45, Ron Wheeler wrote:
On 18/05/2010 2:52 PM, Bruno Harbulot wrote:
But how is a repository to know
1) Who is allowed to upload?
2) What, if any, license scheme the person uses. I can make up my own
license and I don't think that copyright or any law depends on a copy of
the license being included.
3) Does the committer have all the contributor licenses for the stuff
that they uploading that they did not write personally.
Sure, that can be tricky. I'm not suggesting there will be a perfect
solution. Cases where there's foul play will always be a problem.
It's for cases where everyone's trying to play fairly that I think the
default mechanism should make things go more smoothly.
I reckon that Maven's success is based on the fact that it's a model for
distributing software (that's at least a key element of the mechanism)
and that most of the software is open-source and falls broadly into
Apache, GPL, LGPL, MIT, BSD licences. Considering that all these have in
common some terms regarding the distribution of the software
("redistribution", "conveying", "distributing", I'm not a lawyer, but
the ideas seems fairly clear), it just seems surprising that having a
mechanism that enables all parties involved (in particular software
publishers and repositories) to respect those licences seems to have
come as an after-thought.
On 18/05/2010 19:52, Bruno Harbulot wrote:
On 18/05/2010 18:33, Ron Wheeler wrote:
1) If people are distributing their own software in violation of their
own licensing, it is their problem.
2) If people are distributing other people's software in violation of
the licencing, they should stop.
Hard to see how this is a Maven problem or how Maven could fix it. Case
#1 is clearly the prerogative of the owner of the software.
True.
Actually, I think I got that bit wrong, sorry. If the copyright holder
of some software publishes it without a licence or copyright notice,
they can. However, I don't think this grants any right to whoever gets
it, maybe using it, but almost definitely not redistributing it.
On 18/05/2010 20:33, Justin Edelson wrote:
Clarification of the documentation and/or mechanisms on how to
> redistribute the licences properly with the software is what I'm
> suggesting. In terms of core Maven mechanism, that could consist of an
> improvement with respect to the convention over configuration principle
> that Maven follows.
I agree that the documentation can be improved with respect to this. You
can certainly submit some documentation patches on this point. I'm not
sure what "core" changes would be involved. There's probably some
possible enforcer plugin, but ultimately it's not Maven's job to
interpret the semantics of a license - that's something developers need
to be responsible for.
That's exactly the point: saying it's someone else's problem is just
denial of the problem. A publisher's omission to include a licence
doesn't grant whoever gets hold of that software a licence to
redistribute unconditionally.
The problem with most OSS licences (as I was saying above), is that a
developer's mistake ends up putting the burden on the distributors.
Since the Maven system overall relies on the tool, the repository and
owners (or people allowed to distribute) to publish their software, this
is a problem that has to be considered as a whole, I think.
I'm not arguing for perfection, just convenience in what I think are the
common cases. Assuming that developers might be a little bit lazy
sometimes and that most OSS software do have a least a requirement of
quoting their licence with their copies, if a developer/publisher
follows the default layout (that is, LICENSE.txt next pom.xml according
to the documentation), this licence should end up automatically in
what's going to be fetched by the tool when a user puts it as a
dependency in their own software, unlike what happens at the moment.
(I guess including some licence text could easily apply to
closed/proprietary software too.)
I think that would be a more sensible default behaviour for the whole
workflow, and that's what makes it a problem for the "core" Maven.
Best wishes,
Bruno.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
On 18/05/2010 18:33, Ron Wheeler wrote: 1) If people are distributing their own software in violation of their own licensing, it is their problem. 2) If people are distributing other people's software in violation of the licencing, they should stop. Hard to see how this is a Maven problem or how Maven could fix it. Case #1 is clearly the prerogative of the owner of the software. True. Case#2 would be hard to detect without having a big investigation for every package being uploaded to be sure that it is a violation before rejecting it. Very difficult to automate. I'm not saying that the central repo should investigate each and every case to check that it's indeed true, but it should make it mandatory to have a licence at least so as to avoid to put software that is mistakenly unattributed (and thus often in breach of the licence). There's a shortcoming in terms of mechanism in place. It is the responsibility of whoever's hosting a Maven repository (in particular the central repository) to check that they redistribute software under the suitable licence. The central repository clearly fails in that respect. Once again, I don't see why people don't seem to realise that the central repository is redistributing software. Isn't that obvious? I would like Maven (documentation or design) to have more guidance or an in-built mechanism to help publishers and more often distributors not to break those licences. (Some convention over configuration would be good here.) As a publisher of a piece of software, I did put the LICENSE.txt file in my bundle linked from <http://jira.codehaus.org/browse/MAVENUPLOAD-2293> (via the default settings of maven-repository-plugin 2.0 at the time), having the expectation that it would be distributed along with the artifacts in the bundle. While I'm not expecting the central repository a big investigation to find that licence, I would expect the bare minimum of using what was automatically bundled when following the official guidelines, more so considering that including that LICENSE.txt file was mandatory with the maven-repository-plugin version at the time. The content of the bundle did end up in the central repository, except the licence. Subsequently, when people put this artifact's ID in their POM and that Maven downloads it from the central repository, the central repository redistribute those files without the licence: that's a breach of the licence. The point here is that I'm not really arguing there should be a better system to protect our interests, I'm arguing there should be a better system to protect Maven repositories, especially the central one: they're the ones redistributing software and they're the ones at fault. Lots of projects have lots of committers and who owns an open source project would be more a question of ego than law in many cases. (True, but that's what contributor licence agreements are for.) Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
On 18/05/2010 18:25, Justin Edelson wrote: I thought it was well-established that you should include the license inside binary and source artifacts. What exactly is your reason for thinking this isn't a good idea? Saying that it isn't "obvious" doesn't really count IMHO as this is highly subjective. I'm not sure if that's well-established. There are a number of artifacts in the central repository that clearly don't, so that's subjective too. You're right, the only reason I think it's better outside the jar itself is to make it a bit more visible. Whether the licence is within the jar's META-INF or next to the jar is a minute detail indeed. Having it within the jar would make it distributed with the jar of course (which is a good thing). Clarification of the documentation and/or mechanisms on how to redistribute the licences properly with the software is what I'm suggesting. In terms of core Maven mechanism, that could consist of an improvement with respect to the convention over configuration principle that Maven follows. Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
Hi, I've just submitted this issue: http://jira.codehaus.org/browse/MNG-4680 However, I'm told this wasn't the right place to submit. I'm not sure. To me, one of the key features of Apache Maven (if not the main feature) is its repository mechanism. This makes the redistribution of software via those repository a core function of Maven. In addition, Maven's success is largely based on its central repository I think (would anyone disagree?), which distributes mostly open-source software, which in turn has licences that apply to its redistribution in most cases. In appears that the distribution model hasn't fully taken into consideration the problem of licences. Considering that the central repository is in breach of a number of such OSS licences, I'd say there's something wrong with the model in that respect (hence filing the issue with the core framework MNG). On 16/05/10 02:00, Brian Fox wrote: What I meant by usually was that if someone wants to include the license text, it's done inside the archives. Take a look at any recent apache jar for example and you'll find LICENSE and NOTICE prominently included. Indeed, some projects have it in the META-INF directory, even with the binary distribution. (It's not bad, but it's not an obvious place. Putting them along with the POM would make it a bit clearer.) There is definitely something wrong with the "convention over configuration" aspect. Whether that's strictly MNG domain or not is debatable indeed. However, if you follow the guidelines in the guides (e.g. licence placed as described in [1]), the licence doesn't end up either in META-INF or anywhere in the repository. Is it just a documentation shortcoming, or is it a flaw in the architecture of Maven? There definitely is a flaw in the central repository, since it's clearly redistributing some software without the adequate licence. I think these things are definitely fixable, and I'm not after an immediate fix, but I think the issue needs more consideration w.r.t. documentation or design of Maven, rather than saying it's the packager's or the repository's problem. Best wishes, Bruno. [1] http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
On 16/05/2010 02:00, Brian Fox wrote: On Sat, May 15, 2010 at 4:56 PM, Benson Margulies wrote: Yes, these are good ideas. Well, I'm not sure this is just about "good ideas", it sounds more like a legal requirement. This being said, I'm not a lawyer, it's just the way I interpret the BSD licence (for example) when I read it. We currently require that the license be specified in the pom but aren't validating that it is correct automatically. As far as I know, only the licence name is required, for example BSD. I've been saying this in this thread before, but that's just a *type* of licence, not an actual licence. What would be the point of the BSD licence otherwise? Self-propagation of its own terms? The important part is the acknowledgement of the copyright holder. Anyway, pending further development of the plugin and repository management, for my next release, I'll put the text full text of the licence in the element within the POM file (it's only about 30 lines). It seems reasonable. Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
On 15/05/2010 21:56, Benson Margulies wrote: I think that perhaps there's an important distinction being missed here. Central doesn't vacuum up artifacts from unsuspecting authors. Other people put them there. If the authors of code choose to deposit jar files on central, then it's not central who is 'distributing' them -- it's the authors. In this case, it's people who download from central and then repackage on their own who are responsible for worrying about tracking down and including licenses. The tricky case here is the non-author publishers, as with the recently-announced mechanism. If I take a jar of OSS from its author's distro, and push it to central without a license file, I am probably violating the license. It's not clear to me that Sonatype is. Thus, what I take from this thread is that it would be a kindness for Sonatype to add a feature to the new publication mechanism to upload the actual license. It could then be added to META-INF or just published as an accompanying artifact, either way, and then no one would have anything to complain about. I don't think I would have made the publisher/distributor distinction in that order. If a publisher publishes a book, bookshops are the ones distributing it. You are certainly right there's a grey area there, though. To some extent, the central repository situation may be similar to other services that host content (and practically, they can't always check everything indeed, in my opinion). This being said, I'm not sure it makes sense to argue that the central repository does not distribute software; to me it clearly does. I also think that it's not sufficient to say that because the authors are the ones asking for it to be distributed, it's OK. It's not always all the authors or all the copyright holders. Pieces of OSS often include other pieces of OSS, from other projects, that may have been included under the same or other licences. The full list of copyright holders that may extend beyond the list of people being involved in a particular project. Coming back to a case I know well: http://jira.codehaus.org/browse/MAVENUPLOAD-2293 Admittedly, it's a small drop in the ocean of open-source software. Nevertheless, the bundle linked from the JIRA entry (jsslutils-0.5.1-bundle.jar), which was produced with maven-repository-plugin-2.0 did include a LICENSE.txt file (made mandatory by that version of the plugin). (a) This licence file never made it to the central repository. (b) This feature was removed from maven-repository-plugin-2.1 and following versions: LICENSE.txt files and no longer included in the bundles as far as I can tell. I'm allowed by my management to release this software under a BSD-style licence, but the copyright holder still is my institution: the institution is licensing users to do what the licence say they can do, not me as an individual. One of the reasons I'm allowed to publish this code and ask to have it placed in the Maven repository, is that there's an expectation that the licence will be respected. The problem is that, when copyright holders (individual or institution) realise that the OSS licence they've granted isn't respected, they might be less keen to publish OSS again. It might be worth doing this just to avoid those voices in the wide world who like to write alarmist postings about Maven distribution (e.g. Saxon's author). (Sorry, I'm not aware of the postings you're referring to.) Don't get me wrong, I'm very happy to have the software I write distributed on the central repository, and I'm happy to use the content of the repository too. Maven isn't perfect, but it's very useful. One of the main reasons it's useful is the amount of software available in the central repository. It's a system that's good for authors (it makes it easy to encourage usage of their work), good for whoever promotes Maven (presumably Sonatype) and of course good for its users. What I'd like to see is a bit more action towards the respect of the licence, which is what makes OSS work in the end. I'd therefore like Sonatype to improve the publication of licenses as they were bundled and to put that feature (or something similar) back in the following versions of the plugin. Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Central repository, bundle-create and distribution of licenses
Usually? I'm not sure really. NOTICE and LICENSE files are fine in source bundles, but they don't seem to be put into the source jars with the current bundling process. They probably don't belong to the binary jars anyway (unless perhaps in the META-INF directory, somewhere?). Anyway, I don't really have to look far for counter-examples, where this notice isn't present. Just taking the first one in alphabetical order <http://repo2.maven.org/maven2/abbot/abbot/0.13.0/>: - No mention of licence - No reference to the original project - No licence file in the jar file itself After looking it up on Google, it looks like this project's licence is this: <http://abbot.sourceforge.net/doc/CPL.html>. I'll draw you attention to section 3, which maven.org seems to infringe on: there are no disclaimers or information on how to get the source are present, as required. I haven't looked through all of them, but it's not an isolated case. I think the bundling process should make sure the licences are there, but it currently isn't. Even when the licence is referenced, as I was saying, putting the licence type isn't enough. For example, "BSD" really means "BSD-style"; not all software released under a BSD-style licence has the "Regents of the University of California" as copyright holders. What you find here <http://www.opensource.org/licenses/bsd-license.php> for example is a template, not the actual licence. I don't think it's realistic to expect Sonatype to go through all the jars to make sure there's a licence file somewhere. The practicality of Maven is something that I really enjoy, and I wouldn't like to see this practicality affected. However, what could be done to make things clearer is to enable (and perhaps force) the inclusion of a LICENSE file (or similar) during the bundling process, so as to make sure it's published in Maven repositories. Otherwise, people who redistribute software by providing the central Maven repository (and mirrors) are in breach of those licences. Again, the blog post you mentioned talks about "unrestricted distribution". No OSS is strictly compatible with "unrestricted distribution" except when it's in the public domain. All have restrictions stating that distribution must at least comply with their licence (which most of the time requires to quote the licence itself). All I'm suggesting is to have a mechanism to improve that in Maven. I have no doubt that what's being done now is done in good faith with the reasonable expectations that people can Google to find the actual project page, but this situation could be made right, I think. Best wishes, Bruno. On 15/05/2010 03:17, Brian Fox wrote: Usually this is handled by inserting NOTICE and LICENSE into the jar files themselves. In theory you could attach the license file to the main artifact using the "license" classifier but normally this isn't done. On Fri, May 14, 2010 at 7:20 PM, Bruno Harbulot wrote: Thanks for the link. Perhaps someone could put it on this page: http://maven.apache.org/guides/mini/guide-central-repository-upload.html Nevertheless, this doesn't really answer my question. The point I was making was that, with the current model, licences are missing in most projects as far as I can tell. There's often at best a URL to a licence file hosted elsewhere than the repository. Most OSS licences are fairly clear: the licence must be distributed along with the software, whether in binary or source form (depending on the content of the licence). The fact that "Sonatype will perform some due diligence to make sure that the artifact has a license compatible with unrestricted distribution, and we will then promote the uploaded artifacts to the Central Maven repository." [from your link] doesn't make the text of those licences appear from thin air, and the bundling process doesn't seem to bundle those files. 'BSD' often doesn't refer to the actual same licence for example. The copyright holder will be different from one project to another, and redistributing software released under such a licence, but without it, is effectively in breach of this licence (and there are plenty of those in the central repository). One of the main point of OSS licences is to acknowledge the copyright holders, at the very least. I suppose one way to solve it would be to put the actual text within the element of the element in the POM file that's with the jars in the repository. I'm just suggesting there should be, along with the POM file and the jars, a place for a LICENSE.txt (and perhaps NOTICE.txt as some licences use) to make this clearer. (Downloading them along with the artifacts would be a plus, again, for the sake of abiding by these licences.) Does th
Re: Central repository, bundle-create and distribution of licenses
Thanks for the link. Perhaps someone could put it on this page: http://maven.apache.org/guides/mini/guide-central-repository-upload.html Nevertheless, this doesn't really answer my question. The point I was making was that, with the current model, licences are missing in most projects as far as I can tell. There's often at best a URL to a licence file hosted elsewhere than the repository. Most OSS licences are fairly clear: the licence must be distributed along with the software, whether in binary or source form (depending on the content of the licence). The fact that "Sonatype will perform some due diligence to make sure that the artifact has a license compatible with unrestricted distribution, and we will then promote the uploaded artifacts to the Central Maven repository." [from your link] doesn't make the text of those licences appear from thin air, and the bundling process doesn't seem to bundle those files. 'BSD' often doesn't refer to the actual same licence for example. The copyright holder will be different from one project to another, and redistributing software released under such a licence, but without it, is effectively in breach of this licence (and there are plenty of those in the central repository). One of the main point of OSS licences is to acknowledge the copyright holders, at the very least. I suppose one way to solve it would be to put the actual text within the element of the element in the POM file that's with the jars in the repository. I'm just suggesting there should be, along with the POM file and the jars, a place for a LICENSE.txt (and perhaps NOTICE.txt as some licences use) to make this clearer. (Downloading them along with the artifacts would be a plus, again, for the sake of abiding by these licences.) Does this mechanism already exist? How is it done? Best wishes, Bruno. On 14/05/2010 22:39, Brian Fox wrote: http://www.sonatype.com/people/2010/04/uploading-artifacts-to-the-central-maven-repository-diy/ On Fri, May 14, 2010 at 11:46 AM, Bruno Harbulot wrote: Hello, Is there a way to prepare a bundle to be uploaded to the central repository so that it also contains the licence file? Ideally, I'd like a licence file along these files, for example: http://repo1.maven.org/maven2/org/jsslutils/jsslutils/0.5.1/ My POM contains this: BSD LICENSE.txt repo The licence file is next to the POM in the source tree, but it's never included in the bundle or any of its inner jar files. I guess it could be an absolute URL that points to it, but it would be good to have a licence file bundled and uploaded with the other files, at least to respect the terms of the licence itself. Best wishes, Bruno. - 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
Central repository, bundle-create and distribution of licenses
Hello, Is there a way to prepare a bundle to be uploaded to the central repository so that it also contains the licence file? Ideally, I'd like a licence file along these files, for example: http://repo1.maven.org/maven2/org/jsslutils/jsslutils/0.5.1/ My POM contains this: BSD LICENSE.txt repo The licence file is next to the POM in the source tree, but it's never included in the bundle or any of its inner jar files. I guess it could be an absolute URL that points to it, but it would be good to have a licence file bundled and uploaded with the other files, at least to respect the terms of the licence itself. Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: findbugs-plugin: Premature end of file.
Perhaps I found the problem. It seems the reports gets generated twice. I had following configuration of the site plugin: org.apache.maven.plugins maven-site-plugin 2.0.1 true de, en When I change to only one locales de everthing things works fine. Also Findbugs-Plugin 2.2/2.1/2.0.1 org.apache.maven.plugins maven-site-plugin 2.0.1 true de duality72 wrote: > > I'm having the same problem today. Looks like the findbugs plugin has been > updated to version 2.2 and is causing the problem. Reverting to version > 2.0.1 has removed the problem. > -- View this message in context: http://old.nabble.com/findbugs-plugin%3A-Premature-end-of-file.-tp26421353p26438771.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
findbugs-plugin: Premature end of file.
I'm getting an error in maven-findbugs-plugin on site generation: Environment: win xp, java 1.6.0_16, maven 2.2.1, findbugs-plugin 2.2/2.1/2.0.1 [INFO] Generating "FindBugs Report" report. [INFO] Plugin Artifacts to be added ->[org.apache.maven.reporting:maven-reporting-impl:jar:2.0:runtime, org.codehaus.plexus:plexus-utils:jar:1.5.1:runtime, commons-validator:commons-validator:jar:1.1.4:runtime, oro:oro:jar:2.0.7:runtime, doxia:doxia-core:jar:1.0-alpha-4:runtime, org.apache.maven.shared:maven-doxia-tools:jar:1.0:runtime, commons-io:commons-io:jar:1.4:runtime, org.apache.maven.doxia:doxia-decoration-model:jar:1.0-alpha-11:runtime, org.codehaus.plexus:plexus-i18n:jar:1.0-beta-7:runtime, com.google.code.findbugs:findbugs-ant:jar:1.3.9:runtime, com.google.code.findbugs:findbugs:jar:1.3.9:runtime, com.google.code.findbugs:bcel:jar:1.3.9:runtime, com.google.code.findbugs:jsr305:jar:1.3.9:runtime, com.google.code.findbugs:jFormatString:jar:1.3.9:runtime, com.google.code.findbugs:annotations:jar:1.3.9:runtime, dom4j:dom4j:jar:1.6.1:runtime, xml-apis:xml-apis:jar:1.0.b2:runtime, jaxen:jaxen:jar:1.1.1:runtime, jdom:jdom:jar:1.0:runtime, xerces:xercesImpl:jar:2.6.2:runtime, xom:xom:jar:1.0:runtime, xerces:xmlParserAPIs:jar:2.6.2:runtime, xalan:xalan:jar:2.6.0:runtime, com.ibm.icu:icu4j:jar:2.6.1:runtime, asm:asm:jar:3.1:runtime, asm:asm-analysis:jar:3.1:runtime, asm:asm-tree:jar:3.1:runtime, asm:asm-commons:jar:3.1:runtime, asm:asm-util:jar:3.1:runtime, asm:asm-xml:jar:3.1:runtime, commons-lang:commons-lang:jar:2.4:runtime, jgoodies:plastic:jar:1.2.0:runtime, org.codehaus.groovy.maven:gmaven-mojo:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-api:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.feature:gmaven-feature-api:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-default:jar:1.0-rc-3:runtime, org.slf4j:slf4j-api:jar:1.5.0:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-1.5:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.feature:gmaven-feature-support:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven.runtime:gmaven-runtime-support:jar:1.0-rc-3:runtime, org.codehaus.groovy.maven:gmaven-common:jar:1.0-rc-3:runtime, com.thoughtworks.qdox:qdox:jar:1.6.3:runtime, org.codehaus.groovy:groovy-all-minimal:jar:1.5.6:runtime, org.apache.ant:ant:jar:1.7.1:runtime, org.apache.ant:ant-launcher:jar:1.7.1:runtime, jline:jline:jar:0.9.94:runtime, org.codehaus.plexus:plexus-resources:jar:1.0-alpha-4:runtime, org.apache.maven.reporting:maven-reporting-api:jar:2.0.8:runtime] [INFO] AuxClasspath is ->C:\ProgrammeWEB\.m2\repository\org\apache\maven\reporting\maven-reporting-impl\2.0\maven-reporting-impl-2.0.jar;C:\ProgrammeWEB\.m2\repository\org\codehaus\plexus\plexus-utils\1.5.1\plexus-utils-1.5.1.jar;C:\ProgrammeWEB\.m2\repository\commons-validator\commons-validator\1.1.4\commons-validator-1.1.4.jar;C:\ProgrammeWEB\.m2\repository\oro\oro\2.0.7\oro-2.0.7.jar;C:\ProgrammeWEB\.m2\repository\doxia\doxia-core\1.0-alpha-4\doxia-core-1.0-alpha-4.jar;C:\ProgrammeWEB\.m2\repository\org\apache\maven\shared\maven-doxia-tools\1.0\maven-doxia-tools-1.0.jar;C:\ProgrammeWEB\.m2\repository\commons-io\commons-io\1.4\commons-io-1.4.jar;C:\ProgrammeWEB\.m2\repository\org\apache\maven\doxia\doxia-decoration-model\1.0-alpha-11\doxia-decoration-model-1.0-alpha-11.jar;C:\ProgrammeWEB\.m2\repository\org\codehaus\plexus\plexus-i18n\1.0-beta-7\plexus-i18n-1.0-beta-7.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\findbugs-ant\1.3.9\findbugs-ant-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\findbugs\1.3.9\findbugs-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\bcel\1.3.9\bcel-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\jsr305\1.3.9\jsr305-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\jFormatString\1.3.9\jFormatString-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\com\google\code\findbugs\annotations\1.3.9\annotations-1.3.9.jar;C:\ProgrammeWEB\.m2\repository\dom4j\dom4j\1.6.1\dom4j-1.6.1.jar;C:\ProgrammeWEB\.m2\repository\xml-apis\xml-apis\1.0.b2\xml-apis-1.0.b2.jar;C:\ProgrammeWEB\.m2\repository\jaxen\jaxen\1.1.1\jaxen-1.1.1.jar;C:\ProgrammeWEB\.m2\repository\jdom\jdom\1.0\jdom-1.0.jar;C:\ProgrammeWEB\.m2\repository\xerces\xercesImpl\2.6.2\xercesImpl-2.6.2.jar;C:\ProgrammeWEB\.m2\repository\xom\xom\1.0\xom-1.0.jar;C:\ProgrammeWEB\.m2\repository\xerces\xmlParserAPIs\2.6.2\xmlParserAPIs-2.6.2.jar;C:\ProgrammeWEB\.m2\repository\xalan\xalan\2.6.0\xalan-2.6.0.jar;C:\ProgrammeWEB\.m2\repository\com\ibm\icu\icu4j\2.6.1\icu4j-2.6.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm\3.1\asm-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-analysis\3.1\asm-analysis-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-tree\3.1\asm-tree-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-commons\3.1\asm-commons-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-util\3.1\asm-util-3.1.jar;C:\ProgrammeWEB\.m2\repository\asm\asm-xml\3.1\asm-xml-3.1.jar;
Re: M2 site-plugin: Roadmap for 2.2
Oops, sorry meant 2.1. Hope it coming soon ltheussl wrote: > > > You really mean 2.2 or 2.1? The roadmap is here: > > http://jira.codehaus.org/browse/MSITE?report=com.atlassian.jira.plugin.system.project:roadmap-panel > > and 2.1 will include doxia 1.1.2. Timeline there is none. > > You might also have a look at the related Doxia release plan: > http://docs.codehaus.org/display/MAVEN/Doxia+Release+Plan > > HTH, > -Lukas > > > Bruno Marti wrote: >> Which is the roadmap/timeline for release 2.2? >> And will Doxia 1.1.2 be included? >> http://jira.codehaus.org/browse/MSITE-419 >> http://jira.codehaus.org/browse/MSITE-419 > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/M2-site-plugin%3A-Roadmap-for-2.2-tp25270282p25291423.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
M2 site-plugin: Roadmap for 2.2
Which is the roadmap/timeline for release 2.2? And will Doxia 1.1.2 be included? http://jira.codehaus.org/browse/MSITE-419 http://jira.codehaus.org/browse/MSITE-419 -- View this message in context: http://www.nabble.com/M2-site-plugin%3A-Roadmap-for-2.2-tp25270282p25270282.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: Maven java.lang.OutOfMemoryError
It's MAVEN_OPTS Cheers, Bruno 2009/8/13 kopemor : > > Hello, > > I am getting "java.lang.OutOfMemoryError: Java heap space" exception when I > compile my project using Maven. I have tried several options: > > 1. Setting variable: export MAVEN_OPT=-Xmx1024m > > 2. Using Maven compile plugin: > > org.apache.maven.plugins > maven-compiler-plugin > > 1.5 > 1.5 > UTF-8 > -Xms512m > -Xmx1024m > true > > > > I have even tried to put max heap size to 4094, the result is the same. > > Any help? > > -- > View this message in context: > http://www.nabble.com/Maven-java.lang.OutOfMemoryError-tp24952498p24952498.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
Providing external jar file as part of a larger project
Hello, Is there a way to provide a jar file that is not available in a Maven repository as part of a multi-module project? For example, if in a multi-module project (groupId=example,artifactId=exampleroot), a sub-module (groupId=example,artifactId=mainapp) depends on a jar that's not available in any repository -- the dependency being expressed as (groupId=example,artifactId=extlib), it's possible to resolve this dependency using "mvn install:install-file -DgroupId=example -DartifactId=extlib ..." beforehand. However, I wonder if there would be a way to provide this jar within a sub-module, without having to use "mvn install:install-file" manually, so that "mvn clean package" works from the top of the multi-module project directly. The structure would be like this: |-- pom.xml (groupId=example,artifactId=exampleroot) |-- mainapp |-- pom.xml (groupId=example,artifactId=mainapp) |-- src ... |-- extlib |-- pom.xml (groupId=example,artifactId=extlib) |-- lib |-- extlib.jar One way to solve this could be to unjar extlib.jar into extlib/target/classes during its 'compile' phase, but this doesn't seem very clean. Any better solution? Best wishes, Bruno. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re: Possible problem when multiple developers depend on SNAPSHOT versions
+1 Communication: the only solution that fits into any case. Get used to it. :-) On Mar 25, 2009 4:36pm, Heinrich Nirschl wrote: On Wed, Mar 25, 2009 at 8:10 PM, Trevor Harmon tre...@vocaro.com> wrote: > What can be done to prevent Bob's problem? An easy solution is: When Alice prepares the release, she says "Hey Bob, I'm doing a release of Foo". Henry - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[m2] release-plugin skips parent build plugins configuration
I've got a parent pom which defines several project-wide build-plugins in pluginManagement and the build section. The normal build clean install works fine (compilation of code is for version 1.5) but in release-plugin the pluginManagement and build section is completely missing in pom-release.xml or in reactor build (and compilation of code is version 1.3, causes an error on Enumeration objects). It makes no difference if of release-plugin is set or not. (windows xp, maven-2.0.9, release-plugin 2.0-beta-8) Sample: Parent.pom ... ... basis_maven_pom 1 pom org.apache.maven.plugins maven-compiler-plugin 2.0.2 true 1.5 1.5 org.apache.maven.plugins maven-compiler-plugin true 1.5 1.5 ... MyModule.pom ... ... basis_maven_pom 1 ch.visana.rin.ieu.web myModule 1.2.2-SNAPSHOT jar NOTHING DEFINED HERE, ALL COMES FROM BASIS_MAVEN_POM ... Is this a bug or what I'm doing wrong -> mvn clean install (works) -> mvn release:prepare (compiler error) -- View this message in context: http://www.nabble.com/-m2--release-plugin-skips-parent-build-plugins-configuration-tp22180870p22180870.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
maven-javadoc-plugin adding too many parameters for non default doclet
when using the maven-javadoc-plugin with a non standard doclet there are 'options' that are added to the @options file that are only available in the standard doclet ... -author -bottom -charset -d -docencoding -doctitle -use -version -windowtitle i dont find any way to turn these off ? bruno
maven-javadoc-plugin and dependencies
I created my own Doclet that uses freemarker as a template engine.
I tried adding it to another project to generated my own javadocs from it
org.apache.maven.plugins
maven-javadoc-plugin
myPackage.BlockDoclet
${project.build.directory}/blockdocs
${project.groupId}
myPackage.blockdoc
${project.version}
i thought that using the 'docletArtifact' would wire the dependencies that
project has to the -classpath option of javadoc
but it results in my doclet not finding freemarker ...
1 error
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An error has occurred in JavaDocs report generation:Exit code: 1 -
java.l
ang.NoClassDefFoundError: freemarker/template/TemplateException
at java.lang.Class.getDeclaredMethods0(Native Method)
When i browsed the mailinglist i found suggestions to adding a dependency
like this :
org.apache.maven.plugins
maven-javadoc-plugin
org.freemarker
freemarker
2.3.15
but that doesn't change my error.
any idea what i need to do to get this running ? even a workaround ?
thanks in advance
Bruno
[M2] maven-plugin-plugin does not compile with goal helpmojo
I've created a ant plugin on base of http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html. I updated the latest plugin version for usage with executions-goal = helpmojo: - maven-script-ant:2.1.0-M1 - maven-plugin-plugin:2.4.3 It compiles, but if I add: generate-helpmojo helpmojo I'm getting a compiler error: ..\target\generated-sources\plugin\m2-plugin-ant\build\HelpMojo.java:[1,7] expected There is a wrong package defintion on line 1: package /m2-plugin-ant.build; Is ther a way to define the package-separator char '.' or want I'm doing wrong? see: http://www.nabble.com/file/p21615272/m2-plugin-ant.rar m2-plugin-ant.rar -- View this message in context: http://www.nabble.com/-M2--maven-plugin-plugin-does-not-compile-with-goal-helpmojo-tp21615272p21615272.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 commons-net ftp jar as a dependency
What is the problem of depending on that artifact having the effect of depending on other jars? The commons-net-2.0-ftp.jar is created not because of some maven convention. Actually, the Commons-Net creates that jar just to separate classes. The right way of doing that would be using separated modules, but they are not doing that. My suggestion? Keep that dependency and let your project with whatever comes from that. Regards, Bruno On Nov 12, 2008 1:47pm, Steven Jardine <[EMAIL PROTECTED]> wrote: I have a project that uses the commons-net package. Well it actually uses only the commons-net-2.0-ftp.jar file found at http://repo1.maven.org/maven2/commons-net/commons-net/2.0/commons-net-2.0-ftp.jar. It there a way for me to have my project depend on only this jar file not the whole commons-net project. My current dependency is commons-net commons-netartifactId> 2.0 compile Thanks, Steve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Re: Different checkstyle config for main and test?
One can define a specific profile to be activated when one wants to test. For example: $ mvn -Denv-test test On Nov 10, 2008 2:29pm, Wim Deblauwe <[EMAIL PROTECTED]> wrote: I have used profiles before, I don't think you can use that. How would you do this? 2008/11/10 > I think you can use profiles for that. > > bruno > > > On Nov 10, 2008 11:43am, Wim Deblauwe wrote: > >> Hi, >> >> >> >> is it possible to define a different checkstyle configuration in maven for >> >> the main and the tests? I want to allow underscores in method names, but >> >> only in my test source directory. >> >> >> >> regards, >> >> >> >> Wim >> >>
Re: Different checkstyle config for main and test?
I think you can use profiles for that. bruno On Nov 10, 2008 11:43am, Wim Deblauwe <[EMAIL PROTECTED]> wrote: Hi, is it possible to define a different checkstyle configuration in maven for the main and the tests? I want to allow underscores in method names, but only in my test source directory. regards, Wim
Re: [SURVEY] How does your team retrieve artifacts?
[X ] Our team uses HTTP to retrieve our artifacts 2008/5/21 Marat Radchenko <[EMAIL PROTECTED]>: > [X] Our team uses HTTP to retrieve our artifacts > > On 5/21/08, Jason van Zyl <[EMAIL PROTECTED]> wrote: >> Hi, >> >> I'm just trying to get some data on what protocol is used to retrieve >> artifacts. This question strictly relates to what you use for retrieval. >> Most people I have seen use a web server or a shared network drive, but I'd >> like to get some feedback. >> >> [ ] Our team uses HTTP to retrieve our artifacts >> [ ] Our team intends to use HTTP to retrieve our artifacts >> [ ] Our team uses the filesystem >> [ ] Our team does not use HTTP or the filesystem because please say >> what protocol you use and the reason >> >> Thanks, >> >> Jason >> >> -- >> Jason van Zyl >> Founder, Apache Maven >> jason at sonatype dot com >> -- >> >> A language that doesn't affect the way you think about programming is not >> worth knowing. >> >> — Alan Perlis >> >> >> >> >> - >> To unsubscribe, e-mail: [EMAIL PROTECTED] >> For additional commands, e-mail: [EMAIL PROTECTED] >> >> > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Properties.
Remove all your neurons first and then use: mvn invest:property :D (sorry)
Re: Maven Jetty Plugin and filtered resources
I have the same problem as explained below. Does someone know of a solution or alternative? Thanks, Bruno On 26/10/2006, Martin Gilday <[EMAIL PROTECTED]> wrote: > Hi, > I am trying to use the Jetty plugin for Maven but have my web.xml > filtered with properties. This is mainly as I have a "sandbox" profile > which when active would change the spring config file being used. > > I have tried using the WAR plugin to define some filtered resources > > > > org.apache.maven.plugins > maven-war-plugin > 2.0 > > > > src/main/webapp > true > > > > > > > When I use "mvn package" the web.xml is filtered correctly, for both > profiles. However when I use "mvn jetty:run" the properties are not > substituted. > > Is it possible to do this? > > Thanks, > Martin. > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Plugin dependencies updating
Hi guys, I have a pom with this structure: ... group artifact generate group anotherArtifact 1.1-SNAPSHOT ... Because this plugin has to use a file of the other module, we need to specify a dependency for the plugin. Both plugin and dependency were done in the project. When we run the release build, all the SNAPSHOTs are updated except plugin dependencies. Leading to inconsistent versions! Is this a bug or a feature of the release? How to you suggest to solve this issue? Cheers, Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: M2 maven-site-plugin site.xml target attribute no more working
New issue posted in JIRA: http://jira.codehaus.org/browse/MSITE-278 http://jira.codehaus.org/browse/MSITE-278 Dennis Lundberg-2 wrote: > > Bruno Marti wrote: >> In maven 1.x xdoc site documentation there could be the following for >> menus >> (navigation.xml): >> >> http://maven.apache.org/maven-1.x/"; >> target="_new" /> >> ... >> (creates a link to maven 1.x in a new window or tab) >> >> In maven 2.x site.xml this doesn't work anymore. The target attribute >> will >> be ignored. >> Is this a bug? > > Yes or rather a request for a new feature. Please post it in JIRA: > >http://jira.codehaus.org/browse/MSITE > > > -- > Dennis Lundberg > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/M2-maven-site-plugin-site.xml-target-attribute-no-more-working-tp14226588s177p14248503.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
M2 maven-site-plugin site.xml target attribute no more working
In maven 1.x xdoc site documentation there could be the following for menus (navigation.xml): http://maven.apache.org/maven-1.x/"; target="_new" /> ... (creates a link to maven 1.x in a new window or tab) In maven 2.x site.xml this doesn't work anymore. The target attribute will be ignored. Is this a bug? -- View this message in context: http://www.nabble.com/M2-maven-site-plugin-site.xml-target-attribute-no-more-working-tf4966309s177.html#a14226588 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Bug: offline build not running, when having SNAPSHOT dependencies
And does it happen too with 2.0.8? Cheers, Bruno On 07/12/2007, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > ok, did this: > > http://jira.codehaus.org/browse/MNG-3314 > > On Dec 6, 2007 5:47 PM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > and... for some reasons, sometimes, > > it just downloads a new SNAPSHOT. > > > > That is a pain, when you are "maintaining" the same snapshot on your > > box, but the build just goes ahead and actually downloads a version.. > > > > Thx, > > Matthias > > > > > > On Dec 6, 2007 9:37 AM, Matthias Wessendorf <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > > > I am having troubles with > > > mvn ... -o > > > (with maven 2.0.7) > > > > > > says not able to download (but, really, the file is in my local repo) > > > The dependency is a -SNAPSHOT (for what's worth) > > > > > > Luckily, when traveling by train, I had maven 2.0.4 on my box as well. > > > A change to use 2.0.4 works fine. > > > > > > So, is this an already know bug in 2.0.7 ? > > > To my understanding it is a bug, since offline just shouldn't try to get > > > a newer > > > SNAPSHOT, perhaps I am wrong. > > > > > > I know that relying on SNAPSHOTs can be dangerous, but from -o I would > > > expect > > > just not checking for new stuff. > > > > > > Thanks! > > > Matthias > > > > > > -- > > > Matthias Wessendorf > > > > > > further stuff: > > > blog: http://matthiaswessendorf.wordpress.com/ > > > sessions: http://www.slideshare.net/mwessendorf > > > mail: matzew-at-apache-dot-org > > > > > > > > > > > -- > > Matthias Wessendorf > > > > further stuff: > > blog: http://matthiaswessendorf.wordpress.com/ > > sessions: http://www.slideshare.net/mwessendorf > > mail: matzew-at-apache-dot-org > > > > > > -- > Matthias Wessendorf > > further stuff: > blog: http://matthiaswessendorf.wordpress.com/ > sessions: http://www.slideshare.net/mwessendorf > mail: matzew-at-apache-dot-org > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Which technology stack are you using?
On 06/07/07, Wendy Smoak <[EMAIL PROTECTED]> wrote: Maven. Subversion. Continuum. Archiva. Naturally. :) IDEA + mvn idea:idea (no real desire for "IDE integration") I use this same combination. And by the way, the latest builds for IDEA 7 (aka Selena) have maven integrated and looks promissing, Cheers, Bruno (Have you asked on the continuum-user llist? Maven 2 + Subversion is what Continuum is best at...) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: using zip assembly for GWTCompile output
On 6/5/07, Bruno Waes <[EMAIL PROTECTED]> wrote:
I want to keep my webapp (created with "mvn archetype:create
-DarchetypeArtifactId=maven-archetype-
webapp") as clean as possible and only have Spring config files,
Freemarker templates, web.xml ... files there, and no actual code.
Ok, i actually found out how to do it after a few more hours digging into
it.
First of all in my assembly file i got rid of the id-tag
zip
false
/target/projectname-1.0-SNAPSHOT
/
the id tag was showing up in the filename in the repo
${artifactId}-${version}-${Id}.zip , so just removing the tag resulted
in a nice clean zip, with the same basename as the jar in my repo.
So i got it in my repository, now i have to get it out in my webapp project.
Therefor i added this plugin to the plugins section of the build section of
my webapp pom.xml file:
org.codehaus.mojo
dependency-maven-plugin
unzip-gwt
generate-resources
unpack
my.group.id
myprojectgwt
1.0-SNAPSHOT
zip
${project.build.directory}/${project.name
}
The groupId, artifactId and version are just the same as i use in the
dependencies section, to include my jar, the type-tag lets it take the zip
instead.
So thats it.
With a "mvn install" in my gwt project, two artifacts get uploaded into my
REPO, the jar file with the classes, and the zip with the GWTCompile output
(the html and the js files)
In my webapp project the jar is added as a dependency and the zip is fetched
and unziped into my target directory and included when the war package is
build.
Thought i d post the result on the list because i think its a nice and clean
way to integrate your GWTCompiled output in your webapp.
Bruno
using zip assembly for GWTCompile output
I want to keep my webapp (created with "mvn archetype:create -DarchetypeArtifactId=maven-archetype- webapp") as clean as possible and only have Spring config files, Freemarker templates, web.xml ... files there, and no actual code. So as i want to integrate GWT into my application i made a separate project "mvn archetype:create" that has my GWT classes (the client and server classes go into src/main/java, the *.gwt.xml files go into /src/main/resources). "mvn install" nicely sends my jar into my repo. Now installed gwt-maven plugin (http://code.google.com/p/gwt-maven/ 2.x) and it nicely does the GWTCompile with output into my /target/projectname- 1.0-SNAPSHOT/ directory. Now my idea whas to have this project next to the jar also put a zip file of this output into the repository. I accomplished that by adding this: maven-assembly-plugin src/assemble/gwt.xml make-assembly package attached with gwt.xml containing: gwt zip false /target/projectname-1.0-SNAPSHOT / When i do a "mvn install" and i check my repo i see that zip file added. Now is my question how i get my webapp to have that zip as a dependency so it pulls that zip file from the repo and unzips it, and it eventually will end up as part of the war file from that webapp? If this way of working that i had in mind is totally 'not done', please tell me, i am still quite new to Maven. Thanks, Bruno
RE: Release with perforce and multi-module: parent pom cannot be updated
Yes the file is here, but it is read-only. At the start of the process, the file is in read-write mode (it is checked out, i.e., editable for perforce). The release-prepare version: - modifies the file (to set the appropriate version), - submits it (which makes it read-only) When trying to modify it again, it fails. When releasing simple projects, it works fine. I imagine that the pom file is checked out again in the simple project case, to make it read-write. But with multiple modules, it doesn't seem to be the case. A user specifically mentioned in another post that his SCM information was present in the parent and the child poms. It is not the case with me. Should I add SCM information everywhere? The release plugin version is 2.0-beta-4. Bruno -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: mardi 3 avril 2007 11:56 To: Maven Users List Subject: Re: Release with perforce and multi-module: parent pom cannot be updated With your logs, it seems to be there, because the prepare goal run 'mvn clean integration-test --no-plugin-updates' on it but the release plugin can't modify it, maybe it is read only. What is your release plugin version? Emmanuel Bruno Dumant a écrit : > Hi, > > > > I have a problem with the release plugin when using it with perforce in > a multi-module environment. Everything works fine (including tagging the > release) until the "update pom" phase: the parent POM cannot be > modified (apparently, it is not checked out before trying to update it). > > > > Environment: > > * Windows 2003 server / Java 1.6 > * Maven 2.0.6 (I had the problem with 2.0.4 as well) > o I tried using the 2.0-beta-5 release plugin with no success > * Perforce Server version: P4D/LINUX24X86/2005.2/95346 (2006/04/10) > > > > Please see the files attached: the parent and child poms (self > sufficient) and the command output. > > > > Thanks for your help, > > > > Bruno > > > > > + Error stacktraces are turned on. > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT > [INFO] Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT > [INFO] Searching repository for plugin with prefix: 'release'. > [INFO] > > [INFO] Building Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT > [INFO]task-segment: [release:prepare] (aggregator-style) > [INFO] > > [INFO] [release:prepare] > [INFO] Verifying that there are no local modifications... > [INFO] Checking dependencies and plugins for snapshots ... > What is the release version for "Unnamed - > bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTest) 1.0.0: > : What is the release version for "Unnamed - > bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTestApp) > 1.0.0: : What is SCM release tag or label for "Unnamed - > bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTest) > MultiModuleTest-1.0.0: : What is the new development version for "Unnamed - > bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTest) > 1.0.1-SNAPSHOT: : What is the new development version for "Unnamed - > bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTestApp) > 1.0.1-SNAPSHOT: : [INFO] Transforming 'Unnamed - > bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT'... > [INFO] Transforming 'Unnamed - > bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT'... > [INFO] Executing preparation goals 'clean integration-test'... > [INFO] Executing: mvn clean integration-test --no-plugin-updates > [INFO] Scanning for projects... > [INFO] Reactor build order: > [INFO] Unnamed - bdumant:MultiModuleTest:pom:1.0.0 > [INFO] Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0 > [INFO] > > [INFO] Building Unnamed - bdumant:MultiModuleTest:pom:1.0.0 > [INFO]task-segment: [clean, integration-test] > [INFO] > > [INFO] [clean:clean] > [INFO] Deleting directory > d:\dev\perforce\experiments\bdumant\MultiModuleTest\target > [INFO] Deleting directory > d:\dev\perforce\experiments\bdumant\MultiModuleTest\target\classes > [INFO
Release with perforce and multi-module: parent pom cannot be updated
Hi, I have a problem with the release plugin when using it with perforce in a multi-module environment. Everything works fine (including tagging the release) until the "update pom" phase: the parent POM cannot be modified (apparently, it is not checked out before trying to update it). Environment: * Windows 2003 server / Java 1.6 * Maven 2.0.6 (I had the problem with 2.0.4 as well) * I tried using the 2.0-beta-5 release plugin with no success * Perforce Server version: P4D/LINUX24X86/2005.2/95346 (2006/04/10) Please see the files attached: the parent and child poms (self sufficient) and the command output. Thanks for your help, Bruno + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT [INFO] Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT [INFO] Searching repository for plugin with prefix: 'release'. [INFO] [INFO] Building Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT [INFO]task-segment: [release:prepare] (aggregator-style) [INFO] [INFO] [release:prepare] [INFO] Verifying that there are no local modifications... [INFO] Checking dependencies and plugins for snapshots ... What is the release version for "Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTest) 1.0.0: : What is the release version for "Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTestApp) 1.0.0: : What is SCM release tag or label for "Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTest) MultiModuleTest-1.0.0: : What is the new development version for "Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTest) 1.0.1-SNAPSHOT: : What is the new development version for "Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT"? (bdumant:MultiModuleTestApp) 1.0.1-SNAPSHOT: : [INFO] Transforming 'Unnamed - bdumant:MultiModuleTest:pom:1.0.0-SNAPSHOT'... [INFO] Transforming 'Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0-SNAPSHOT'... [INFO] Executing preparation goals 'clean integration-test'... [INFO] Executing: mvn clean integration-test --no-plugin-updates [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] Unnamed - bdumant:MultiModuleTest:pom:1.0.0 [INFO] Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0 [INFO] [INFO] Building Unnamed - bdumant:MultiModuleTest:pom:1.0.0 [INFO]task-segment: [clean, integration-test] [INFO] [INFO] [clean:clean] [INFO] Deleting directory d:\dev\perforce\experiments\bdumant\MultiModuleTest\target [INFO] Deleting directory d:\dev\perforce\experiments\bdumant\MultiModuleTest\target\classes [INFO] Deleting directory d:\dev\perforce\experiments\bdumant\MultiModuleTest\target\test-classes [INFO] [site:attach-descriptor] [INFO] [INFO] Building Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0 [INFO]task-segment: [clean, integration-test] [INFO] [INFO] [clean:clean] [INFO] Deleting directory d:\dev\perforce\experiments\bdumant\MultiModuleTest\APP\target [INFO] Deleting directory d:\dev\perforce\experiments\bdumant\MultiModuleTest\APP\target\classes [INFO] Deleting directory d:\dev\perforce\experiments\bdumant\MultiModuleTest\APP\target\test-classes [INFO] [site:attach-descriptor] [INFO] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Unnamed - bdumant:MultiModuleTest:pom:1.0.0 ... SUCCESS [1.328s] [INFO] Unnamed - bdumant:MultiModuleTestApp:pom:1.0.0 SUCCESS [0.000s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 1 second [INFO] Finished at: Tue Apr 03 11:04:53 CEST 2007 [INFO] Final Memory: 3M/7M [INFO] [INFO] Checking in modified POMs... [INFO] Tagging release with the label MultiMod
NullPointerException when junit dependency missing
Hi, I've catched a NullPointerException error message without any explicit information about the cause of the error. This error happened because the JUnit dependency in the POM descriptor was missing by mistake. Since the JUnit dependency is required by default shouldn't the error be more explicit? More details on the command line error follow. Regards, Bruno Basílio C:\bbasilio\alpr\alpr-standalone\alpr-standalone\controller>mvn -e package + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] - --- [INFO] Building Alpr Facade Controller [INFO]task-segment: [package] [INFO] - --- [INFO] [resources:resources] [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] [resources:testResources] [INFO] Using default encoding to copy filtered resources. [INFO] [compiler:testCompile] [INFO] No sources to compile [INFO] [surefire:test] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] null [INFO] [INFO] Trace java.lang.NullPointerException at org.apache.maven.plugin.surefire.SurefirePlugin.constructSurefireBooter(SurefirePlugin.java:594) at org.apache.maven.plugin.surefire.SurefirePlugin.execute(SurefirePlugin.java:391) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) [INFO] [INFO] Total time: 16 seconds [INFO] Finished at: Wed Mar 28 15:05:02 BST 2007 [INFO] Final Memory: 5M/10M [INFO]
RE: using Maven SCM with Perforce
Hi, I am using the scm plugin with perforce every day with no problem. I do NOT configure maven-scm-plugin in the plugins list. Maven seems to find the appropriate plugin by itself. My connection configuration looks like that: scm:perforce::1971:// scm:perforce::1971:// I don't specify any user name or password in the pom: I have set a default workspace using the P4 tools, and thus do not need to do so. Note that it makes the POM user independent. When defining a workspace, do not define the 'Host'. Another remark: if you still want to use snapshot plugins (sometimes, you have no choice: see the maven-dependency plugin, for instance), you need to specify a specific repository in your POM, like this: apache-snapshots-repository http://people.apache.org/repo/m2-snapshot-repository true Hope this helps, Bruno From: Anirudh Chandrakant [mailto:[EMAIL PROTECTED] Sent: lundi 11 décembre 2006 19:30 To: [EMAIL PROTECTED] Subject: using Maven SCM with Perforce Hi, I am a beginner with maven and maven SCM. i tried to use Maven SCM with Perforce. My pom.xml looks like this: 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";> 4.0.0 com.test withPerforce jar 1.0-SNAPSHOT withPerforce http://maven.apache.org scm:perforce:[EMAIL PROTECTED] :3023://depot/myProj org.apache.maven.plugins maven-scm-plugin 1.0-SNAPSHOT connection junit junit 3.8.1 test But, when i attempt to execute any scm command, i get the following error: Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-scm-plugin:pom:1.0-SNAPSHOT My configuration file is configured right, it can download the other plugins required from the repository. Could you please let me know if i am doing anything wrong or have i missed out on any configuration step. Thanks in advance, Anirudh
Problem checking-in files with perforce
Hi, I cannot succeed in submitting anything on perforce using maven. This is what I get when I running release:prepare: [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-commit-release' [INFO] Checking in modified POMs... [DEBUG] Executing p4 -H : submit - i [DEBUG] Sending changelist: Change: new Description: [maven-release-plugin] prepare release Labs.GraphicsMasher-1.3.3 Files: //labs/GraphicsServer/Stable/GraphServer/masher/pom.xml [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: Unable to submit Command output: [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: Unable to submit Command output: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: Unable to submit Command output: at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe leaseMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more I have the same kind of output when I just try to commit a file. What is strange is that updates (scm:update) correctly work: in particular, a client spec is properly created and everything runs smoothly. When trying to submit files, no client spec seems to be created. Is it the normal behaviour? Thanks for any hint! Bruno
Problem checking-in files with perforce
Hi, I cannot succeed in submitting anything on perforce using maven. This is what I get when I running release:prepare: [INFO] [release:prepare] [INFO] Resuming release from phase 'scm-commit-release' [INFO] Checking in modified POMs... [DEBUG] Executing p4 -H <my server>:<my port> submit - i [DEBUG] Sending changelist: Change: new Description: [maven-release-plugin] prepare release Labs.GraphicsMasher-1.3.3 Files: //labs/GraphicsServer/Stable/GraphServer/masher/pom.xml [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: Unable to submit Command output: [INFO] [DEBUG] Trace org.apache.maven.BuildFailureException: Unable to commit files Provider message: Unable to submit Command output: at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:555) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:488) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:458) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:306) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:219) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:140) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115) at org.apache.maven.cli.MavenCli.main(MavenCli.java:256) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoFailureException: Unable to commit files Provider message: Unable to submit Command output: at org.apache.maven.plugins.release.PrepareReleaseMojo.execute(PrepareRe leaseMojo.java:114) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:412) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:534) ... 16 more I have the same kind of output when I just try to commit a file. What is strange is that updates (scm:update) correctly work: in particular, a client spec is properly created and everything runs smoothly. When trying to submit files, no client spec seems to be created. Is it the normal behaviour? Thanks for any hint! Bruno
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
The community itself is the community control. See your case. It is the user that reports if something fails, and maybe suggests/provides a patch or has the patience to let other do it. Here, there is no such a master-slave relationship where someone tells the changes and others do. If you need something, you can do it yourself. All the users/experts around here are the QA. And I assure you that it cannot be a better QA... Bruno On 9/20/06, Markus KARG <[EMAIL PROTECTED]> wrote: So since bugs once released cannot get fixed without changing the version (what is problematic with FOP as we have discussed today), this is one more reason for not let anybody upload things without doing quality control. :-) Wayne Fay schrieb: > Yes, this is the point of the discussion. Please search this mail list > (Nabble etc) and Maven Dev to see the entire history of this issue. > > Increment version by one, upload it, and allow Maven to find the > updated version the next time your build runs, it will automatically > find and use it. > > Wayne > > On 9/20/06, Markus KARG <[EMAIL PROTECTED]> wrote: > >> So the policy is "A bug cannot be fixed"?! >> >> Jochen Wiedmann schrieb: >> >> > Markus KARG wrote: >> > >> >> If Carlos is able to upload it while I seem not to be, he actually is >> >> in the role of the maintainer. >> >> Where am I going wrong with that assumption? >> > >> > >> > Your assumption is, that he is able to change files in the repository. >> > The answer is he isn't. Ok, he may be able to do that technically, but >> > the policy is clearly that already released files are left unchanged - >> > forever. >> > >> > >> > Jochen >> > >> > >> > - >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> >> >> >> - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
A released jar cannot be modified. A bug can be fixed, but in the next version/bugfix of the artifact (and maybe you could provide such a fixed artifact). All this is a community effort where everyone can participate. It is not right to change anything in a released artifact, because you are never sure that the bug you are fixing will cause other bugs... Bruno On 9/20/06, Markus KARG <[EMAIL PROTECTED]> wrote: So the policy is "A bug cannot be fixed"?! Jochen Wiedmann schrieb: > Markus KARG wrote: > >> If Carlos is able to upload it while I seem not to be, he actually is >> in the role of the maintainer. >> Where am I going wrong with that assumption? > > > Your assumption is, that he is able to change files in the repository. > The answer is he isn't. Ok, he may be able to do that technically, but > the policy is clearly that already released files are left unchanged - > forever. > > > Jochen > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Who is the maintainer of the fop:fop project found on repo1.maven.org?
Well, probably the development community of the Apache Fop project can help you. Check the project site [1]. Cheers, Bruno [1] http://xmlgraphics.apache.org/fop/ On 9/19/06, Markus KARG <[EMAIL PROTECTED]> wrote: Carlos, actually the repo MUST be changes since the jar IS WRONG. So if there is no maintainer and no JIRA: WHOM TO TELL ABOUT THE BUG NOW ? Markus Carlos Sanchez schrieb: > I don't think the repo needs to be changed to meet your requirements. > And it's a collective effort, there's no mantainer. > > On 9/19/06, Markus KARG <[EMAIL PROTECTED]> wrote: > >> I need to find out the maintainer of the fop:fop project on >> repo1.maven.org. >> There is a severe bug in the published JAR that prevents referencing >> this project from own projects. >> >> Please either fix the bug or tell me the name of the maintainer so I can >> ask him to fix it! >> >> As there is no JIRA group for that project, I also cannot file a JIRA >> issue. >> >> It's all about the fop plugin (groupId: fop, artifactId: fop). The >> current version is 0.20.5. That version's pom.xml found on >> repo1.maven.org contains a dependency on "xml-apis-1.0.b2.jar" >> (xml-apis, version 1.0.b2), which should result in "Class-Path: >> xml-apis-1.0.b2.jar" to be written in the main artifact >> "fop-0.20.5.jar". >> Actually the "fop-0.20.5.jar" found on repo1.maven.org doesn't contain >> "Class-Path: xml-apis-1.0.b2.jar" but "Class-Path: xml-apis.jar" which >> results in a class path resolving problem at run time in any project >> using FOP 0.20.5! >> >> The same problem not only happens with "xml-apis" but with nearly ALL >> dependencies of fop-0.20.5 (e. g. also with "batik")! >> >> This has to be fixed ASAP to make those projects work! >> The fix is quite easy, just modify the Class-Path: entry or do "mvn >> clean deploy" to push another copy to repo1.maven.org. >> >> The problem is really urgent since we need this and we do not have write >> access to that folder on of repo1.maven.org. >> >> Thanks >> Markus >> >> >> > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problem with repositories that not contain some artifacts
Hi there, I have a pom with two repositories. One is the maven repository at the apache foundation and the other is an internal repository at my institution. When my pom goes to fetch the pom's it first check in the internal repo. This repo returns a "missing page" if the artifact does not exist (an apache artifact, for instance), but maven things it has got "something" and tries to download that. Then it fails and blacklists the repository and does not try to fetch the file in the apache repo. So the result is that neither the dependencies from apache nor the ones at my internal repo are fetched. Any ideas? Thanks! Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Add timestamp to properties file using filtering
Hi, Is there a way to put a timestamp in a properties file? I am thinking in filtering, but is there a pom variable that returns the timestamp or current date? Thanks! Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Not Resolving Dependencies
is UIComponentBase a class of yours? or for some JAR of which you depend? Because if it is a class of your project you may have put it outside the standard maven directory for source code, and maven is not compiling it. Eclipse source folders and where maven expects to find the sources are places not related. Maven's compile plugin does not read the Eclipse project to gather information. On 5/16/06, Ole Ersoy <[EMAIL PROTECTED]> wrote: Hi, I'm running Maven 2.0.3 and I'm having problems compiling. I first run the eclipse plugin and eclipse is able to load the dependencies. I then attempt to install, and the maven compiler gives me messages like this: /home/ole/workspaces/current/UIShowOneComponent/src/main/java/TestComponent.java:[1,29] package javax.faces.component does not exist /home/ole/workspaces/current/UIShowOneComponent/src/main/java/TestComponent.java:[3,35] cannot find symbol symbol: class UIComponentBase So eclipse sees the dependencies in the repository, but maven does not. Any ideas? Thanks in advance! Cheers, - Ole __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: http://bpfurtado.net software development blog: http://bpfurtado.livejournal.com
Re: Multi modules: project-jar and project-obfuscated-jar help
I'll help you with what I can :) On 5/16/06, Dave Comeau <[EMAIL PROTECTED]> wrote: I'm trying to design a multi-module project to do a variety of steps that I currently do in my existing Ant build system, and was previously given some advice to setup one module to create the standard jar artifact, and then create another module (which has a dependency on the jar module) to create the obfuscated jar. Being new to Maven, I can't see how to do this. In theory I will want the project-ofuscated-jar to access (and unpackage?) the project-jar's freshly created jar file and then obfuscate the classes using antrun or a custom plugin. I'm hoping someone can shed some light on how this is actually done. I can't find any documentation on multi-modules that explains the relationship between modules in the context that I need. Here are my questions: 1) I assume that by M2 design, project-obfuscated-jar should not directly access the classes/ in project-jar. Instead it should access the project-jar JAR artifact. Is this correct? 2) Would project-jar's jar artifact first need to be deployed to the repository before the project-obfuscated-jar can access it? You just deploy a artifact to a given repository to other developers, whose projects depend on it, obtain its latest version. The deploy operation is only related to Maven Repositories and their sole purpose (as I've understood) is to keep artifacts and its versions in a central place for developers to download (using maven obviously) through the dependency declaration. 3) Assume that project-obfuscated-jar uses antrun to feed the classes produced by project-jar into the obfuscator. How do I directly reference project-jar's JAR file? 4) Is it bad practice to reference peer projects/modules using "../.." type references? 5) Is there any documentation/references on multi-modules outside of the typical use cases where a multi-module project is just a set of projects each with their own source tree? I feel I am trying to apply the multi-module functionality to a more specialized use case that is certainly within the capabilities of Maven, but it's not typical and the documentation hasn't expanded beyond the mainstream use cases yet. Thank you for your help DaveC -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: http://bpfurtado.net software development blog: http://bpfurtado.livejournal.com
[m2] jdepend plugin?
Hi! I recall that there was a jdepend plugin in the past somewhere, but I cannot find it. Any ideas? Regards, Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Local copy for the metadata of a repository wrong
Sorry, a correction to the repositories section (missed a change when writing the mail). Any help is appreciated! central-repo Ibiblio repository http://www.ibiblio.org/maven2 my-repo My repository http://www.ebi.ac.uk/~maven/m2repo and the deploy-file command: mvn deploy:deploy-file -DpomFile=artifactName-1.0-SNAPSHOT.pom -Dfile=.artifactName.jar -DrepositoryId=my-repo -Durl=scp://localhost/homes/maven/public_html/m2repo -DuniqueVersion=false (just changed ebi-repo to my-repo, for example purposes) Bruno On 5/10/06, Bruno Aranda <[EMAIL PROTECTED]> wrote: Hi all, I have an internal repository and I have deployed a snapshot version of a jar to it, using the deploy-file goal: mvn deploy:deploy-file -DpomFile=artifactName-1.0-SNAPSHOT.pom -Dfile=.artifactName.jar -DrepositoryId=ebi-repo -Durl=scp://localhost/homes/maven/public_html/m2repo -DuniqueVersion=false Everything is created fine in the repository, as I can see the files and the pom is correct. The problem is that when I have another pom that depends on that artifact, I get this error message: [INFO] Error building POM (may not be this project's POM). Project ID: myGroupId:artifactName Reason: Error getting POM for 'myGroupId:artifactName' from the repository: Unable to read local copy of metadata: Cannot read metadata from '~/.m2/repository/myGroupId/1.0-SNAPSHOT/maven-metadata-my-repo.xml': end tag name must be the same as start tag from line 47 (position: TEXT seen ... src = "http://www.ebi.ac.uk/include/master.js";>\n... @49:8) myGroupId:artifactName:pom:1.0-SNAPSHOT And this is due to the fact that the maven-metadata-my-repo.xml file contains the html code of the page that appears in my institution when the servers returns a 404 (page not found). I have this configuration in my pom: central-repo Ibiblio repository http://www.ibiblio.org/maven2 ebi-repo The EBI internal repository http://www.ebi.ac.uk/~maven/m2repo I have put the central-repo explicitly so it is the first server checked (otherwise for jars not present in the internal jar, but present in the central repo I got an error, due to the fact that the 404 html page appear when asking to the internal repo. With released artifacts (not snapshots) everything seems to be working fine... Any ideas? Thanks! Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Local copy for the metadata of a repository wrong
Hi all, I have an internal repository and I have deployed a snapshot version of a jar to it, using the deploy-file goal: mvn deploy:deploy-file -DpomFile=artifactName-1.0-SNAPSHOT.pom -Dfile=.artifactName.jar -DrepositoryId=ebi-repo -Durl=scp://localhost/homes/maven/public_html/m2repo -DuniqueVersion=false Everything is created fine in the repository, as I can see the files and the pom is correct. The problem is that when I have another pom that depends on that artifact, I get this error message: [INFO] Error building POM (may not be this project's POM). Project ID: myGroupId:artifactName Reason: Error getting POM for 'myGroupId:artifactName' from the repository: Unable to read local copy of metadata: Cannot read metadata from '~/.m2/repository/myGroupId/1.0-SNAPSHOT/maven-metadata-my-repo.xml': end tag name must be the same as start tag from line 47 (position: TEXT seen ... src = "http://www.ebi.ac.uk/include/master.js";>\n... @49:8) myGroupId:artifactName:pom:1.0-SNAPSHOT And this is due to the fact that the maven-metadata-my-repo.xml file contains the html code of the page that appears in my institution when the servers returns a 404 (page not found). I have this configuration in my pom: central-repo Ibiblio repository http://www.ibiblio.org/maven2 ebi-repo The EBI internal repository http://www.ebi.ac.uk/~maven/m2repo I have put the central-repo explicitly so it is the first server checked (otherwise for jars not present in the internal jar, but present in the central repo I got an error, due to the fact that the 404 html page appear when asking to the internal repo. With released artifacts (not snapshots) everything seems to be working fine... Any ideas? Thanks! Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Downloading local cached jars
Hi folks, I have a few 3rd party jars installed into my local repository, but each time I call the maven install plugin the output tells me maven is downloading the jars (and it takes some time to 'download' each jar). Am I missing some point here? Is maven looking for this artifacts at the web repositories? One of my theories is that if I had a intranet maven repository properly configured maven would look for this artifacts there, it would see that there are no new versions and quickly would keep using the local cache. Is this right? -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: http://bpfurtado.net software development blog: http://bpfurtado.livejournal.com
Re: deploy: invalid private key
The identity file permissions are correct, my guess is about the format of my identity file, I've encripted my private key using the RSA algorithm, because in my intranet the network admins configured the SSH version 1. Could the classes in the project com.jcraft.jsch. have some problem with it? Should I send some command line arguments, or use some conversion tool to have a separete private key in the expected format? On 3/24/06, Arnaud Bailly <[EMAIL PROTECTED]> wrote: > > Hi, > May be you can have a lot more debugging info by passing the > environnemnet variable -Djavax.net.ssl=debug (or > -Djavax.net.debug=ssl, I'm never sure :-)). > Aren't there any issue regarding rights on your file ? In ssh2 for > example, keys are not used if they don't have 0600 rights. > > Regards, > -- > Arnaud Bailly, Dr. - Ingénieur de Recherche > NORSYS > 1, rue de la Cense des Raines > ZAC du Moulin > 59710 ENNEVELIN > Tel : (33) 3 28 76 56 76 > Mob : (33) 6 17 12 19 78 > Fax : (33) 3 28 76 57 00 > Web : http://www.norsys.fr > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: http://bpfurtado.net software development blog: http://bpfurtado.livejournal.com
Re: deploy: invalid private key
h.JSch.addIdentity(Unknown Source) at org.apache.maven.wagon.providers.ssh.AbstractSshWagon.openConnection( AbstractSshWagon.java:150) ... 23 more On 3/22/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > > Ok. So, outside of Maven, you can ssh using that username and > passphrase. And you're certain that the private key is located at > "/.ssh/identity"? Normally it is "/.ssh/id_dsa" > or "/.ssh/id_rsa". Finally, could you go ahead and send > the error message you get? > > -Stephen > > On 3/22/06, Bruno Patini Furtado <[EMAIL PROTECTED]> wrote: > > The settings.xml has the real values. My mistake in using different > > notations. > > > > On 3/21/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > > > > > > Where you have $user_name and $usr_home do you have in your actual > > > settings.xml the real values? Wasn't clear since you used > > > later to represent a value actually replaced in your > > > files... > > > > > > -Stephen > > > > > > On 3/21/06, Bruno Patini Furtado <[EMAIL PROTECTED]> wrote: > > > > Hi folks, > > > > I'm trying to deploy a artifact to a local intranet repository using > > > SCP, I > > > > can establish a ssh session using my pass phrase as expected, but > I'm > > > having > > > > to success in configuring maven to make it. > > > > > > > > My settings.xml servers tag goes like this: > > > > > > > > ssh-repository > > > > $user_name > > > > $usr_home/.ssh/identity > > > > > > > > > > > > > > > > My pom.xml distributionManagement tag: > > > > > > > > > > > > ssh-repository > > > > scp:/// > > > > > > > > > > > > > > > > I'm not using putty, which I've read has a key format issue and a > key > > > > converter. > > > > I've looked a lot at the mailing list archives and in the maven > > > > documentation site. > > > > Any help in any page will be most appreciated :) > > > > > > > > > > > > -- > > > > "Minds are like parachutes, they work best when open." > > > > > > > > Bruno Patini Furtado > > > > Software Developer > > > > webpage: www.bpfurtado.net > > > > software development blog: http://bpfurtado.livejournal.com > > > > > > > > > > > > > > > > > -- > > > Stephen Duncan Jr > > > www.stephenduncanjr.com > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > "Minds are like parachutes, they work best when open." > > > > Bruno Patini Furtado > > Software Developer > > webpage: www.bpfurtado.net > > blog: http://bpfurtado.livejournal.com > > > > > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: http://bpfurtado.net software development blog: http://bpfurtado.livejournal.com
Re: deploy: invalid private key
The settings.xml has the real values. My mistake in using different notations. On 3/21/06, Stephen Duncan <[EMAIL PROTECTED]> wrote: > > Where you have $user_name and $usr_home do you have in your actual > settings.xml the real values? Wasn't clear since you used > later to represent a value actually replaced in your > files... > > -Stephen > > On 3/21/06, Bruno Patini Furtado <[EMAIL PROTECTED]> wrote: > > Hi folks, > > I'm trying to deploy a artifact to a local intranet repository using > SCP, I > > can establish a ssh session using my pass phrase as expected, but I'm > having > > to success in configuring maven to make it. > > > > My settings.xml servers tag goes like this: > > > > ssh-repository > > $user_name > > $usr_home/.ssh/identity > > > > > > > > My pom.xml distributionManagement tag: > > > > > > ssh-repository > > scp:/// > > > > > > > > I'm not using putty, which I've read has a key format issue and a key > > converter. > > I've looked a lot at the mailing list archives and in the maven > > documentation site. > > Any help in any page will be most appreciated :) > > > > > > -- > > "Minds are like parachutes, they work best when open." > > > > Bruno Patini Furtado > > Software Developer > > webpage: www.bpfurtado.net > > software development blog: http://bpfurtado.livejournal.com > > > > > > > -- > Stephen Duncan Jr > www.stephenduncanjr.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net blog: http://bpfurtado.livejournal.com
Re: deploy: invalid private key
Anyone has experienced this problem? On 3/21/06, Bruno Patini Furtado <[EMAIL PROTECTED]> wrote: > > I'm using GNU/Linux, Ubuntu 5.10 distro :) > > > On 3/21/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > What operating system? > > > > "Not using putty" -- well what ARE you using? > > > > Wayne > > > > On 3/21/06, Bruno Patini Furtado <[EMAIL PROTECTED]> wrote: > > > Hi folks, > > > I'm trying to deploy a artifact to a local intranet repository using > > SCP, I > > > can establish a ssh session using my pass phrase as expected, but I'm > > having > > > to success in configuring maven to make it. > > > > > > My settings.xml servers tag goes like this: > > > > > > ssh-repository > > > $user_name > > > $usr_home/.ssh/identity > > > > > > > > > > > > My pom.xml distributionManagement tag: > > > > > > > > > ssh-repository > > > scp:/// > > > > > > > > > > > > I'm not using putty, which I've read has a key format issue and a key > > > converter. > > > I've looked a lot at the mailing list archives and in the maven > > > documentation site. > > > Any help in any page will be most appreciated :) > > > > > > > > > -- > > > "Minds are like parachutes, they work best when open." > > > > > > Bruno Patini Furtado > > > Software Developer > > > webpage: www.bpfurtado.net > > > software development blog: http://bpfurtado.livejournal.com > > > > > > > > > > > > -- > > "Minds are like parachutes, they work best when open." > > Bruno Patini Furtado > Software Developer > webpage: www.bpfurtado.net > blog: http://bpfurtado.livejournal.com > -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net blog: http://bpfurtado.livejournal.com
Re: deploy: invalid private key
I'm using GNU/Linux, Ubuntu 5.10 distro :) On 3/21/06, Wayne Fay <[EMAIL PROTECTED]> wrote: > > What operating system? > > "Not using putty" -- well what ARE you using? > > Wayne > > On 3/21/06, Bruno Patini Furtado <[EMAIL PROTECTED]> wrote: > > Hi folks, > > I'm trying to deploy a artifact to a local intranet repository using > SCP, I > > can establish a ssh session using my pass phrase as expected, but I'm > having > > to success in configuring maven to make it. > > > > My settings.xml servers tag goes like this: > > > > ssh-repository > > $user_name > > $usr_home/.ssh/identity > > > > > > > > My pom.xml distributionManagement tag: > > > > > > ssh-repository > > scp:/// > > > > > > > > I'm not using putty, which I've read has a key format issue and a key > > converter. > > I've looked a lot at the mailing list archives and in the maven > > documentation site. > > Any help in any page will be most appreciated :) > > > > > > -- > > "Minds are like parachutes, they work best when open." > > > > Bruno Patini Furtado > > Software Developer > > webpage: www.bpfurtado.net > > software development blog: http://bpfurtado.livejournal.com > > > > > -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net blog: http://bpfurtado.livejournal.com
deploy: invalid private key
Hi folks, I'm trying to deploy a artifact to a local intranet repository using SCP, I can establish a ssh session using my pass phrase as expected, but I'm having to success in configuring maven to make it. My settings.xml servers tag goes like this: ssh-repository $user_name $usr_home/.ssh/identity My pom.xml distributionManagement tag: ssh-repository scp:/// I'm not using putty, which I've read has a key format issue and a key converter. I've looked a lot at the mailing list archives and in the maven documentation site. Any help in any page will be most appreciated :) -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net software development blog: http://bpfurtado.livejournal.com
Re: Installing artifacts into a local repository
Thanks a lot, that worked. On 3/17/06, Wilfred Springer <[EMAIL PROTECTED]> wrote: > > > That should be 'mvn deploy'. > > 'mvn install' installs stuff in your local repository cache > 'mvn deploy' deploys it to a repository > > mvn deploy will give you what you need. > > -Original Message- > From: Bruno Patini Furtado [mailto:[EMAIL PROTECTED] > Sent: Fri 3/17/2006 7:25 PM > To: users@maven.apache.org > Subject: Installing artifacts into a local repository > > I´m using the install plugin to install a artifact into my intranet > repository. I´ve seen in some recent thread a example of the > distributionManagement configuration that uses the file:// URL protocol. > > My pom goes like this: > > > > mycompany-repository > MyCompany Repository > file://c:/tools/maven-repo > > > > But after running maven install I´ve noted that it only installed the > artifact into my ~/.m2/repository > > [INFO] Installing c:\\target\-2.0.jar to > \.m2\repository\\\2.0\- > 2.0.jar > > Am I missing something? > > Thanks in advance. > > -- > "Minds are like parachutes, they work best when open." > > Bruno Patini Furtado > Software Developer > webpage: www.bpfurtado.net > blog: http://bpfurtado.livejournal.com > > > -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net blog: http://bpfurtado.livejournal.com
Installing artifacts into a local repository
I´m using the install plugin to install a artifact into my intranet repository. I´ve seen in some recent thread a example of the distributionManagement configuration that uses the file:// URL protocol. My pom goes like this: mycompany-repository MyCompany Repository file://c:/tools/maven-repo But after running maven install I´ve noted that it only installed the artifact into my ~/.m2/repository [INFO] Installing c:\\target\-2.0.jar to \.m2\repository\\\2.0\- 2.0.jar Am I missing something? Thanks in advance. -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net blog: http://bpfurtado.livejournal.com
Newbie Local Repository Question
Hi folks, I´m starting to use maven now (never used version 1.x.x) and have some doubts about Maven´s repositories. How could I set a local intranet Maven repository to our company´s projects components? How does maven lives with the Internet repositories and local ones? Where I can find documentation on how to install artifacts to a specific local repo and not the other ones. I had this first idea that settings.xml´s local Repository element referred to a simple single user cache of the JARs used. But I´m starting to think that´s not the case. Any page describing this concepts? Any help will be most appreciated! Regards. -- "Minds are like parachutes, they work best when open." Bruno Patini Furtado Software Developer webpage: www.bpfurtado.net software development blog: http://bpfurtado.livejournal.com
Migrating site from forrest to maven
Hi! I'd like to know if there is some kind of tool or previous experiences to share in the migration of documentation from a project that is using forrest to maven (apt format or one of the others), before I start doing it by hand :-) TIA, Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: RE : RE : Problems with special characters in APT format (latin-1 and copyright symbol)
I can confirm that it works on Linux (FC3) and without having to set
the LANG environment variable (which currently is 'es_ES.UTF-8').
Thanks,
Bruno
2005/12/16, Olivier Lamy <[EMAIL PROTECTED]>:
> I have added this workaround in :
> http://docs.codehaus.org/display/MAVENUSER/FAQs#FAQs-Handlespecialcharac
> tersinsite
>
> It could be adding in
> http://maven.apache.org/guides/mini/guide-site.html (to help
> french/others guys how use specials characters). (let me know if you
> want a patch on it ?)
>
> I have tested this solution on a solaris machine and on a windows/cygwin
> and it's ok.
> Probably It works too for others *n*x systems.
>
> - Olivier
>
> -Message d'origine-
> De : Olivier Lamy [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 16 décembre 2005 09:38
> À : 'Maven Users List'
> Objet : RE : Problems with special characters in APT format (latin-1 and
> copyright symbol)
>
>
> Hi,
> I have try some workarounds and I have fine one to correctly display
> specials characters (french accents).
>
> In my eclipse.ini :
> Adding -Dfile.encoding=ISO-8859-1
>
> If using xmlbuddy with eclipse to edit xdoc files set the encoding
> Honor encoding
> Default to ISO-8859-1
>
> Configuration in pom
>
> org.apache.maven.plugins
> maven-site-plugin
>
> UTF-8
>
>
>
> On the solaris machine
> In $HOME/.profile
> MAVEN_OPTS="-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1" (mx/ms not
> mandatory for m2 but for m1). LANG=en_US.ISO8859-15
>
> And surprise it's fine ;-))
>
> But not for surefire report when log contains special characters. I look
> at
> http://svn.apache.org/viewcvs.cgi/maven/surefire/trunk/surefire/src/main
> /java/org/apache/maven/surefire/report/XMLReporter.java?rev=353853&view=
> markup
>
> And I see (I'm not really sure if this is using) : writer.write(" version=\"1.0\" encoding=\"UTF-8\" ?>\n");
>
> Could it be in the configuration or using something like
> http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/Strin
> gEscapeUtils.html#escapeXml(java.lang.String)
>
> Because as I see, the following is not probably not enough : message =
> StringUtils.replace( report.getThrowable().getMessage(), "<", "<" );
> message = StringUtils.replace( message, ">", ">" ); message =
> StringUtils.replace( message, "\"", """ );
>
>
> - Olivier
>
> -Message d'origine-
> De : Bruno Aranda [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 16 décembre 2005 09:25
> À : Maven Users List
> Objet : Re: Problems with special characters in APT format (latin-1 and
> copyright symbol)
>
>
> Nobody knows this? Has someone used accents in the apt format? Should I
> try an alternative approach? thanks!
>
> Bruno
>
> 2005/12/12, Bruno Aranda <[EMAIL PROTECTED]>:
> > Hi there,
> >
> > I am trying to just the APT format but I cannot output some special
> > symbols using unicode, such as the copyritght and latin-1 special
> > characters (accents). I am following the APT guide [1], but when using
>
> > the copyright symbol I get this in the screen:
> >
> > Â(c)
> >
> > There is a strange character before the copyright. I've tried \251,
> > \xA9, \u00a9 ... I have similar results for other unicode characters.
> > Do I have to change the encoding somewhere? I am running a linux box.
> >
> > Regards,
> >
> > Bruno
> >
> > [1] http://maven.apache.org/guides/mini/guide-apt-format.html
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> This e-mail, any attachments and the information contained therein
> ("this message") are confidential and intended solely for the use of the
> addressee(s). If you have received this message in error please send it
> back to the sender and delete it. Unauthorized publication, use,
> dissemination or disclosure of this message, either in whole or in part
> is strictly prohibited.
> **
> Ce message électronique et tous les fichiers joints ainsi que les
> informations contenues dans ce message ( ci après "le message" ), sont
> confidentiels et destinés exclusivement à l'usage de la personne à
> laquelle ils sont adressés. Si vous avez reçu ce message par erreur,
Re: RE : Problems with special characters in APT format (latin-1 and copyright symbol)
Thanks Olivier, that worked!
Bruno
2005/12/16, Olivier Lamy <[EMAIL PROTECTED]>:
> Hi,
> I have try some workarounds and I have fine one to correctly display
> specials characters (french accents).
>
> In my eclipse.ini :
> Adding -Dfile.encoding=ISO-8859-1
>
> If using xmlbuddy with eclipse to edit xdoc files set the encoding
> Honor encoding
> Default to ISO-8859-1
>
> Configuration in pom
>
> org.apache.maven.plugins
> maven-site-plugin
>
> UTF-8
>
>
>
> On the solaris machine
> In $HOME/.profile
> MAVEN_OPTS="-Xmx512m -Xms512m -Dfile.encoding=ISO-8859-1" (mx/ms not
> mandatory for m2 but for m1).
> LANG=en_US.ISO8859-15
>
> And surprise it's fine ;-))
>
> But not for surefire report when log contains special characters.
> I look at
> http://svn.apache.org/viewcvs.cgi/maven/surefire/trunk/surefire/src/main
> /java/org/apache/maven/surefire/report/XMLReporter.java?rev=353853&view=
> markup
>
> And I see (I'm not really sure if this is using) :
> writer.write("\n");
>
> Could it be in the configuration or using something like
> http://jakarta.apache.org/commons/lang/api/org/apache/commons/lang/Strin
> gEscapeUtils.html#escapeXml(java.lang.String)
>
> Because as I see, the following is not probably not enough :
> message = StringUtils.replace( report.getThrowable().getMessage(), "<",
> "<" );
> message = StringUtils.replace( message, ">", ">" );
> message = StringUtils.replace( message, "\"", """ );
>
>
> - Olivier
>
> -Message d'origine-
> De : Bruno Aranda [mailto:[EMAIL PROTECTED]
> Envoyé : vendredi 16 décembre 2005 09:25
> À : Maven Users List
> Objet : Re: Problems with special characters in APT format (latin-1 and
> copyright symbol)
>
>
> Nobody knows this? Has someone used accents in the apt format? Should I
> try an alternative approach? thanks!
>
> Bruno
>
> 2005/12/12, Bruno Aranda <[EMAIL PROTECTED]>:
> > Hi there,
> >
> > I am trying to just the APT format but I cannot output some special
> > symbols using unicode, such as the copyritght and latin-1 special
> > characters (accents). I am following the APT guide [1], but when using
>
> > the copyright symbol I get this in the screen:
> >
> > Â(c)
> >
> > There is a strange character before the copyright. I've tried \251,
> > \xA9, \u00a9 ... I have similar results for other unicode characters.
> > Do I have to change the encoding somewhere? I am running a linux box.
> >
> > Regards,
> >
> > Bruno
> >
> > [1] http://maven.apache.org/guides/mini/guide-apt-format.html
> >
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
>
> This e-mail, any attachments and the information contained therein ("this
> message") are confidential and intended solely for the use of the
> addressee(s). If you have received this message in error please send it back
> to the sender and delete it. Unauthorized publication, use, dissemination or
> disclosure of this message, either in whole or in part is strictly prohibited.
> **
> Ce message électronique et tous les fichiers joints ainsi que les
> informations contenues dans ce message ( ci après "le message" ), sont
> confidentiels et destinés exclusivement à l'usage de la personne à laquelle
> ils sont adressés. Si vous avez reçu ce message par erreur, merci de le
> renvoyer à son émetteur et de le détruire. Toutes diffusion, publication,
> totale ou partielle ou divulgation sous quelque forme que se soit non
> expressément autorisées de ce message, sont interdites.
> **
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems with special characters in APT format (latin-1 and copyright symbol)
Nobody knows this? Has someone used accents in the apt format? Should I try an alternative approach? thanks! Bruno 2005/12/12, Bruno Aranda <[EMAIL PROTECTED]>: > Hi there, > > I am trying to just the APT format but I cannot output some special > symbols using unicode, such as the copyritght and latin-1 special > characters (accents). I am following the APT guide [1], but when using > the copyright symbol I get this in the screen: > > Â(c) > > There is a strange character before the copyright. I've tried \251, > \xA9, \u00a9 ... I have similar results for other unicode characters. > Do I have to change the encoding somewhere? I am running a linux box. > > Regards, > > Bruno > > [1] http://maven.apache.org/guides/mini/guide-apt-format.html > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems with special characters in APT format (latin-1 and copyright symbol)
Hi there, I am trying to just the APT format but I cannot output some special symbols using unicode, such as the copyritght and latin-1 special characters (accents). I am following the APT guide [1], but when using the copyright symbol I get this in the screen: Â(c) There is a strange character before the copyright. I've tried \251, \xA9, \u00a9 ... I have similar results for other unicode characters. Do I have to change the encoding somewhere? I am running a linux box. Regards, Bruno [1] http://maven.apache.org/guides/mini/guide-apt-format.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Latin characters in apt format
Hi all, I read from the docs [1] that to use latin characters in the apt format you have to use special notation. Latin characters are considered "special characters" when they are very common in latin languages ;-). Readability of the file is decreased, so this can be rather annoying. Is there any solution to that or something planned? Or should I use other formats (which are more cumbersone than the apt)? Regards, Bruno [1] http://maven.apache.org/guides/mini/guide-apt-format.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Jars inside ear as java modules in the application.xml
BrunoNeuronException :-) I've found the page googleing. Poor me :-) And I've just read the warModule configuration but, as I am doing 2000 things at the same time, I haven't got further :p thanks anyway! Bruno 2005/11/30, Stephane Nicoll <[EMAIL PROTECTED]>: > Hey bruno, > > Well have you tried to read the doc first? :p > > http://maven.apache.org/plugins/maven-ear-plugin/howto.html (end of the > page) > > > > On 11/30/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: > > > > I've found the solution myself googleing and looking to the source code > > :-) > > > > You have to use a javaModule inside the configuration of the > > maven-ear-plugin with the artifact information and the > > includeInApplicationXml set to true: > > > > > > maven-ear-plugin > > > > > > > >ebiointel-bionary > > bionary > > true > > > > > > > > > > true > > > > > > > > > > > > Regards, > > > > Bruno > > > > 2005/11/30, Bruno Aranda <[EMAIL PROTECTED]>: > > > Hi all, > > > > > > I wonder if it is possible to configure the ear plugin somehow to put > > > some of the jar dependencies inside the application.xml file as > > > myFile.jar, as it is actually done with > > > ejb's and webapps... > > > I need this because I have a par (ejb3) that depends on a jar and in > > > order to make this work I also need that jar in the application.xml > > > file... > > > > > > Regards, > > > > > > Bruno > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .::You're welcome ::. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Jars inside ear as java modules in the application.xml
I've found the solution myself googleing and looking to the source code :-) You have to use a javaModule inside the configuration of the maven-ear-plugin with the artifact information and the includeInApplicationXml set to true: maven-ear-plugin ebiointel-bionary bionary true true Regards, Bruno 2005/11/30, Bruno Aranda <[EMAIL PROTECTED]>: > Hi all, > > I wonder if it is possible to configure the ear plugin somehow to put > some of the jar dependencies inside the application.xml file as > myFile.jar, as it is actually done with > ejb's and webapps... > I need this because I have a par (ejb3) that depends on a jar and in > order to make this work I also need that jar in the application.xml > file... > > Regards, > > Bruno > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Jars inside ear as java modules in the application.xml
Hi all, I wonder if it is possible to configure the ear plugin somehow to put some of the jar dependencies inside the application.xml file as myFile.jar, as it is actually done with ejb's and webapps... I need this because I have a par (ejb3) that depends on a jar and in order to make this work I also need that jar in the application.xml file... Regards, Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
War phases, binding a custom plugin to the war creation
Hi all, I would like to know what phase I have to use to bind a plugin to the war creation (war:war). my.groupId maven-myPlugin-plugin WHAT TO PUT HERE myPluginGoal It works ok for the process-resources and package phases, but the first is too early, and the other is too late. I am trying to copy some JSP pages in a specific way to the exploded war folder before creating the war file, TIA, Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Bootstrap Maven Source Code does not build on Linux
The day this thread was begun I did use the bootstrap in a FC3 and maven built without problems... Regards, Bruno 2005/11/22, Brett Porter <[EMAIL PROTECTED]>: > Odd... > > can you edit the BootstrapInstaller.java and add "-X" as an optional > in runMaven() ? > > I'd like to know what the plexus dependencies are when these tests are run. > > - Brett > > On 11/22/05, Peter A. Pilgrim <[EMAIL PROTECTED]> wrote: > > Unfortunately I am still getting this error. > > I remove the files from repository codebase and even tried a re-checkout > > from SVN, > > > > Help! > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] creating a par package and including it in an ear
Thanks Stéphane! I've finally got it working... I've checked out the current SVN maven, and maven ear plugin and rebuilt everything. I've used the maven-par-plugin from the mojo codehaus sandbox. After building everything I reproduced an issue discussed some days ago in this mailing list [1], where it is said that ejb3 and pars do not expose its classes to the classpath in order to be used by other modules. I've created a JIRA for that [2] and attached the plugin there with the solution proposed by Thomas Marek, in order to be available in the next release. Now, everything is working as expected, Thanks, Bruno [1] http://mail-archives.apache.org/mod_mbox/maven-users/200511.mbox/[EMAIL PROTECTED] [2] http://jira.codehaus.org/browse/MNG-1620 2005/11/17, Stephane Nicoll <[EMAIL PROTECTED]>: > Bruno, > > Yes but you need to use latest SVN et rebuild the maven ear plugin. It works > but it's not released yet. Regarding the lifecyle, same answer, it's applied > to maven core but not as part of the 2.0 release. > > Hope it helps, > Stéphane > > On 11/17/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: > > > > Thanks, I know, to summarise, my question was if someone has > > successfully included a par generated with that plugin inside an > > ear... > > > > Thanks, > > > > Bruno > > > > 2005/11/17, Arik Kfir <[EMAIL PROTECTED]>: > > > I think you need to use the 'maven-par-plugin' (in the mojo project, > > > at http://mojo.codehaus.org/) > > > > > > However, AFAIK its not released yet. > > > > > > On 11/17/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > > > > > I am doing my first steps with maven... I have a multi-module setup > > > > that involves the creation of jars, wars, pars and an ear with > > > > everything inside. I've been told to use a plugin to create the par > > > > file [1]. However, when the par is set as a dependency in the pom.xml > > > > file to create the ear, a jar (with the same name of the par) is > > > > included in the ear instead. I do not know anything about the maven > > > > insights so I am not able right now to modify the code in order to see > > > > what fails now, although I could do an ant task to rename again the > > > > jar file to par inside the ear. But that will be the last solution... > > > > I've seen that there is also a maven-par-plugin in the sandbox and > > > > I've tried to use it. Then I got this exception: Cannot find lifecycle > > > > mapping for packaging: 'par'. > > > > I've compared the two plugins and I've seen than the plugin from JIRA > > > > contains a components.xml file, so I've copied that file to the > > > > sandbox plugin and I've installed it again (yeah, you now, trial and > > > > error). The lifecycle seems ok now, but I keep getting this exception > > > > > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Error > > assembling PAR > > > > ... > > > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > > > Caused by: org.apache.maven.plugin.MojoExecutionException: Error > > assembling PAR > > > > at org.apache.maven.plugin.par.ParMojo.execute(ParMojo.java:161) > > > > at org.apache.maven.plugin.DefaultPluginManager.executeMojo( > > DefaultPluginManager.java:399) > > > > at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals( > > DefaultLifecycleExecutor.java:519) > > > > ... 16 more > > > > Caused by: java.lang.NullPointerException > > > > at org.apache.maven.plugin.par.ParMojo.execute(ParMojo.java:151) > > > > ... 18 more > > > > > > > > Any tips will be appreciated, > > > > > > > > Thanks! > > > > > > > > Bruno > > > > > > > > [1] http://jira.codehaus.org/browse/MOJO-98 > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .::You're welcome ::. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] building from svn and/or snapshots available
I've used the bootstrap script following the instructions in the README file and the building went ok... Bruno 2005/11/18, Bruno Aranda <[EMAIL PROTECTED]>: > Hi all, > > I've checked out the maven sources following the instructions on the > web site and now I am trying to build everything, using the 'mvn > assembly:assembly' command. I keep getting this build failure: > > [INFO] [jar:jar] > [INFO] Building jar: > /data/src/maven/temp/maven-site/maven-script/maven-script-beanshell/target/maven-script-beanshell-2.0.1-SNAPSHOT.jar > [INFO] [assembly:assembly] > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] You must specify descriptor or descriptorId > [INFO] > > [INFO] Trace > org.apache.maven.BuildFailureException: You must specify descriptor or > descriptorId >at > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:540) > ... > > I am not sure what is the reason for this exception as I don't still > have enough experience with maven. Any help? > > BTW, are there any maven 2 nightly builds that I can download? I don't > find them... sorry :-) > > Regards, > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] building from svn and/or snapshots available
Hi all, I've checked out the maven sources following the instructions on the web site and now I am trying to build everything, using the 'mvn assembly:assembly' command. I keep getting this build failure: [INFO] [jar:jar] [INFO] Building jar: /data/src/maven/temp/maven-site/maven-script/maven-script-beanshell/target/maven-script-beanshell-2.0.1-SNAPSHOT.jar [INFO] [assembly:assembly] [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] You must specify descriptor or descriptorId [INFO] [INFO] Trace org.apache.maven.BuildFailureException: You must specify descriptor or descriptorId at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:540) ... I am not sure what is the reason for this exception as I don't still have enough experience with maven. Any help? BTW, are there any maven 2 nightly builds that I can download? I don't find them... sorry :-) Regards, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Where is the tomcat plugin?
Hi Wendy, it is on the sandbox of the Mojo codehaus. Check it out with svn: http://svn.mojo.codehaus.org/trunk/mojo/mojo-sandbox/maven-tomcat-plugin/ Regards, Bruno 2005/11/17, Wendy Smoak <[EMAIL PROTECTED]>: > There is a Tomcat plugin on the matrix, and some projects using m2 > refer to it, but I can't find it. > > Where is the Maven 2 Tomcat Plugin? > > Thanks, > Wendy > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2 webapp support
Hi Natahniel, put the sources in src/main/java and then execute mvn compile war:war (or mvn install). The issue is that with mvn war:war the sources are not being compiled... Regards, Bruno 2005/11/17, Nathaniel G. Auvil <[EMAIL PROTECTED]>: > > So i have to manually create and specify where all the directories are? I > thought maven would do this? I dont mean to offend anyone, but if i have to > manually do this, why not just use Ant by itelf? > > Maybe i am confused in what Maven does? I thought Maven provides a > project structure such that i can create x number of projects and they all > have the same directory structures, build files, etc out of the box. > Then i can of course, enhance those defaults with additional plug-ins and > options. Is this an incorrect assumption? > > > John Casey <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > src/main/webapps, IIRC. > > You might check out http://maven.apache.org/plugins/maven-war-plugin/ > for more information. > > - -j > > Nathaniel G. Auvil wrote: > | i am having problems trying to create a new web application. I > searched the documentation and found a reference to building a web > application project. I run the command and it builds a webapp. But i > have no idea where i should stick my java source files so that when i > do a "mvn war:war", it builds them and places them in "WEB-INF/classes" > | > | Can anyone tell me how to do this? > | > | > | > | - > | Yahoo! FareChase - Search multiple travel sites in one click. > -BEGIN PGP SIGNATURE- > Version: GnuPG v1.2.6 (GNU/Linux) > > iD8DBQFDfNThK3h2CZwO/4URAqzPAJ96vKssDbu3jFtK43rSWqB3TjY4TwCfVrFS > RH/vLn+vaIcRY36U9fZFIZY= > =YM4O > -END PGP SIGNATURE- > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > Yahoo! FareChase - Search multiple travel sites in one click. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] creating a par package and including it in an ear
Thanks, I know, to summarise, my question was if someone has successfully included a par generated with that plugin inside an ear... Thanks, Bruno 2005/11/17, Arik Kfir <[EMAIL PROTECTED]>: > I think you need to use the 'maven-par-plugin' (in the mojo project, > at http://mojo.codehaus.org/) > > However, AFAIK its not released yet. > > On 11/17/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: > > Hi all, > > > > I am doing my first steps with maven... I have a multi-module setup > > that involves the creation of jars, wars, pars and an ear with > > everything inside. I've been told to use a plugin to create the par > > file [1]. However, when the par is set as a dependency in the pom.xml > > file to create the ear, a jar (with the same name of the par) is > > included in the ear instead. I do not know anything about the maven > > insights so I am not able right now to modify the code in order to see > > what fails now, although I could do an ant task to rename again the > > jar file to par inside the ear. But that will be the last solution... > > I've seen that there is also a maven-par-plugin in the sandbox and > > I've tried to use it. Then I got this exception: Cannot find lifecycle > > mapping for packaging: 'par'. > > I've compared the two plugins and I've seen than the plugin from JIRA > > contains a components.xml file, so I've copied that file to the > > sandbox plugin and I've installed it again (yeah, you now, trial and > > error). The lifecycle seems ok now, but I keep getting this exception > > > > org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling PAR > > ... > > at org.codehaus.classworlds.Launcher.main(Launcher.java:375) > > Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling > > PAR > > at org.apache.maven.plugin.par.ParMojo.execute(ParMojo.java:161) > > at > > org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) > > at > > org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) > > ... 16 more > > Caused by: java.lang.NullPointerException > > at org.apache.maven.plugin.par.ParMojo.execute(ParMojo.java:151) > > ... 18 more > > > > Any tips will be appreciated, > > > > Thanks! > > > > Bruno > > > > [1] http://jira.codehaus.org/browse/MOJO-98 > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: m2 webapp support
You have to put your source files in the src/main/java folder. Regards, Bruno 2005/11/17, Nathaniel G. Auvil <[EMAIL PROTECTED]>: > i am having problems trying to create a new web application. I searched the > documentation and found a reference to building a web application project. > I run the command and it builds a webapp. But i have no idea where i should > stick my java source files so that when i do a "mvn war:war", it builds them > and places them in "WEB-INF/classes" > > Can anyone tell me how to do this? > > > > - > Yahoo! FareChase - Search multiple travel sites in one click. > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] creating a par package and including it in an ear
Hi all, I am doing my first steps with maven... I have a multi-module setup that involves the creation of jars, wars, pars and an ear with everything inside. I've been told to use a plugin to create the par file [1]. However, when the par is set as a dependency in the pom.xml file to create the ear, a jar (with the same name of the par) is included in the ear instead. I do not know anything about the maven insights so I am not able right now to modify the code in order to see what fails now, although I could do an ant task to rename again the jar file to par inside the ear. But that will be the last solution... I've seen that there is also a maven-par-plugin in the sandbox and I've tried to use it. Then I got this exception: Cannot find lifecycle mapping for packaging: 'par'. I've compared the two plugins and I've seen than the plugin from JIRA contains a components.xml file, so I've copied that file to the sandbox plugin and I've installed it again (yeah, you now, trial and error). The lifecycle seems ok now, but I keep getting this exception org.apache.maven.lifecycle.LifecycleExecutionException: Error assembling PAR ... at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Error assembling PAR at org.apache.maven.plugin.par.ParMojo.execute(ParMojo.java:161) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:399) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:519) ... 16 more Caused by: java.lang.NullPointerException at org.apache.maven.plugin.par.ParMojo.execute(ParMojo.java:151) ... 18 more Any tips will be appreciated, Thanks! Bruno [1] http://jira.codehaus.org/browse/MOJO-98 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Creating a par package (for ejb3)
Hi *, I am new to this list and maybe I am asking something that has been asked many times before (but I haven't found an answer in the archive). I wonder if it is possible to create a par package... I've seen in another thread someone is using a maven-par-plugin, but I don't find that. Any help? Regards, Bruno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] creating jars+pars+war+ear
Thanks Stephan! :-) Bruno 2005/11/16, Stephane Nicoll <[EMAIL PROTECTED]>: > Bruno, > > Check this: > http://jira.codehaus.org/browse/ARCHETYPE-8 > > Hope it helps, > Stéphane > > On 11/16/05, Bruno Aranda <[EMAIL PROTECTED]> wrote: > > > > Hi *, > > > > I've searched through the mailing list without success. I have an > > application that generates several jars, some pars (ejb3 persistence > > packages), a war and a ear with everything inside. > > I've just tried to create the ear archetype using archetype:create, > > following the instructions in the maven2 site [1], but it seems that > > the archetypeArtifactId=maven-archetype-ear does not exist. Maybe it > > is not possible to create ears this way yet... > > Maybe a good way to learn should be able to look on how existing > > projects manage similar situations. It would be really helpful if > > someone could tell me about an open-source project that is already > > using maven 2 and creating jars+war+ear... > > > > Thanks in anticipation, > > > > Regards, > > > > Bruno > > > > [1] http://maven.apache.org/guides/mini/guide-ear.html > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > .::You're welcome ::. > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] creating jars+pars+war+ear
Hi *, I've searched through the mailing list without success. I have an application that generates several jars, some pars (ejb3 persistence packages), a war and a ear with everything inside. I've just tried to create the ear archetype using archetype:create, following the instructions in the maven2 site [1], but it seems that the archetypeArtifactId=maven-archetype-ear does not exist. Maybe it is not possible to create ears this way yet... Maybe a good way to learn should be able to look on how existing projects manage similar situations. It would be really helpful if someone could tell me about an open-source project that is already using maven 2 and creating jars+war+ear... Thanks in anticipation, Regards, Bruno [1] http://maven.apache.org/guides/mini/guide-ear.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Parent POM Properties
Jason van Zyl wrote:
What is it concretely you are trying to do. Often users give us
solutions to their problems without actually telling us what the problem
is. We really need to know what you're trying to do first. We definitely
don't want duplication and is something we try to avoid so we need more
details.
I'll try again with an example:
Given a project with three subprojects, I want to use a checkstyle definition
that is valid for all three subprojects. (The checkstyle definition itself
differs from project to project since it mostly depends on the style used by
the customer.)
+- toplevel/
|
+- pom.xml
+- src/
| |
| +- java/
| |
| +- resources/
||
|+- checkstyle.xml
|
+- subproj1/
| |
| +- pom.xml
| +- src/
| +- ...
|
+- subproj2/
|
+- pom.xml
+- src/
+- ...
Now, if I want to include a checkstyle configuration like the following in
toplevel/pom.xml so that it is picked up by all subprojects:
...
${topdir}/src/java/resources/checkstyle.xml
...
I cannot use ${basedir} since this always yields the base directory of the
subproject being built. What I want is to access resources relative to the
toplevel directory.
I don't want to use a fixed URL for the location since I want to have versioning
for the file and I also need it to be in a relative location since a customer
will build the project in a location that may not even have access to the
fixed URL (even though I could work around this using a profile).
Cheers,
// Bruno
PS: I am aware that I cannot currently set the checkstyle configuration, see
http://jira.codehaus.org/browse/MNG-587 and
http://jira.codehaus.org/browse/MNG-1113
(I have a local copy that allows me to do anyway until an official solution is
out).
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
