Re: Release notification
The changes plugin supports email: http://maven.apache.org/plugins/maven-changes-plugin/usage.html However, it's not triggered by a release but you need to run it separately. I guess you could bind it to the deploy phase, but I'm not sure you want to do this. Normally you would go through staging first and then, if ok, announce. /Anders On Thu, Feb 25, 2010 at 08:58, langlois yan langlois_...@yahoo.fr wrote: Hi, Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Yan Langlois.
Re: Release notification
You can however change the release plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId configuration preparationGoalsclean verify changes:announcement-generate/preparationGoals goalsdeploy changes:announcement-mail/goals /configuration /plugin Mark -- Pull me down under... On Thu, Feb 25, 2010 at 9:47 PM, Anders Hammar and...@hammar.net wrote: The changes plugin supports email: http://maven.apache.org/plugins/maven-changes-plugin/usage.html However, it's not triggered by a release but you need to run it separately. I guess you could bind it to the deploy phase, but I'm not sure you want to do this. Normally you would go through staging first and then, if ok, announce. /Anders On Thu, Feb 25, 2010 at 08:58, langlois yan langlois_...@yahoo.fr wrote: Hi, Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Yan Langlois. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: having problems with the scm plugin
According to the docs, the project.scm.connection element is used by
default. Keep username and password in the plugin configuration and make
sure that the project.scm.connection is correct.
If you want to use developerConnection instead that's påossible to configure
on the scm plugin, see the docs.
http://maven.apache.org/scm/plugins/usage.html
/Anders
On Thu, Feb 25, 2010 at 01:52, Grant Lewis ukchuckt...@gmail.com wrote:
The line breaks aren't the problem. I made some progress. I'm still a
little confused by connectionUrl versus developerConnectionUrl but the
following in my parent POM file finally worked for me. I never got
developerConnectionUrl to work and I'm honestly not sure how the property is
used by the plugin.
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-scm-plugin/artifactId
version1.3/version
configuration
connectionUrlscm:svn:
https://10.6.22.11/svn/icfdev/NE-FIMS/trunk/${project.artifactId}https://10.6.22.11/svn/icfdev/NE-FIMS/trunk/$%7Bproject.artifactId%7D
/connectionUrl
username${svn.username}/username
password${svn.password}/password
/configuration
/plugin
/plugins
On Feb 24, 2010, at 6:51 PM, Bastian Spanneberg wrote:
Grant Lewis schrieb:
As far as I can tell my configuration is correct, using Maven 2.2.1, scm
1.3 and OS X 10.6.2. The relevant parts of my POM file are included. The
tags are in my parent POM file so I expect the child project to inherit. I
don't really understand the difference between connection and
developerConnection so I set them both.
When I try to run mvn scm:checkout on a child project I observe the
error shown below from the plug-in. I also tried adding connectionUrl in
the configuration for the plugin but that didn't help, same error. Anyone
have some ideas? I'm not having any problems with command-line svn, only the
Maven svn integration. Thanks.
are these line breaks also in your pom, or just in this mail ? i remember
i've got problems once with a similar situation, just cannot remember if it
was with a scm connection url.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Release notification
Yes, unless you want to do staging first... /Anders On Thu, Feb 25, 2010 at 09:52, Mark Derricutt m...@talios.com wrote: You can however change the release plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId configuration preparationGoalsclean verify changes:announcement-generate/preparationGoals goalsdeploy changes:announcement-mail/goals /configuration /plugin Mark -- Pull me down under... On Thu, Feb 25, 2010 at 9:47 PM, Anders Hammar and...@hammar.net wrote: The changes plugin supports email: http://maven.apache.org/plugins/maven-changes-plugin/usage.html However, it's not triggered by a release but you need to run it separately. I guess you could bind it to the deploy phase, but I'm not sure you want to do this. Normally you would go through staging first and then, if ok, announce. /Anders On Thu, Feb 25, 2010 at 08:58, langlois yan langlois_...@yahoo.fr wrote: Hi, Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Yan Langlois. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Generics 5 - unexpected type, found: java.lang.Object expected: reference
Thanks guys, I wasn't aware of eclipse and its' compile routines. milan On 24/02/10 19:11, Wayne Fay wrote: In fact I can compile it in eclipse with java 5, so this problem appears only when compiling with maven. ... I don't get this error under eclipse(neither under jd5 or jdk6) only when building with maven Maven uses the compiler in your JDK while Eclipse uses its own compiler. This is not a Maven issue but rather a difference between the Eclipse compiler and Sun's compiler. if((Object)stack.getBean() instanceof String) Then it compiles OK both with jdk5 and jdk6. but this is both ugly and dirty I'd do this if it works. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Med vennlig hilsen/Regards, Milan Chudík Fjøsangerveien 50 5892 Bergen Norway Mob. : +47 90094542 Tel. : +47 55209617 e-mail : milan.chu...@delfidata.no - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Checkstyle and multi module
Hi, I have a multi module project with this layout Base |-- pom.xml |-- build-tools | |-- src | | `-- main | | `-- resources | | `-- org | | `-- project | | `-- checkstyle.xml | `-- pom.xml |-- parent |-- module1 |-- module2 `-- modulen Everything is like it is described in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html with one exception: The Base/pom.xml is not the parent module pom but Base/parent/pom.xml is. After following the guide above I can run mvn checkstyle:checkstyle fine on all modules and it uses the checkstyle.xml from the build-tools module. Just mvn site will not work with this error: [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Failed during checkstyle execution Could not find resource 'org/project/checkstyle.xml'. Why does it work with checkstyle:checkstyle and not with site? Thanks Thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re : Release notification
Ok, thank you. yan. De : Anders Hammar and...@hammar.net À : Maven Users List users@maven.apache.org Envoyé le : Jeu 25 Février 2010, 9 h 56 min 16 s Objet : Re: Release notification Yes, unless you want to do staging first... /Anders On Thu, Feb 25, 2010 at 09:52, Mark Derricutt m...@talios.com wrote: You can however change the release plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId configuration preparationGoalsclean verify changes:announcement-generate/preparationGoals goalsdeploy changes:announcement-mail/goals /configuration /plugin Mark -- Pull me down under... On Thu, Feb 25, 2010 at 9:47 PM, Anders Hammar and...@hammar.net wrote: The changes plugin supports email: http://maven.apache.org/plugins/maven-changes-plugin/usage.html However, it's not triggered by a release but you need to run it separately. I guess you could bind it to the deploy phase, but I'm not sure you want to do this. Normally you would go through staging first and then, if ok, announce. /Anders On Thu, Feb 25, 2010 at 08:58, langlois yan langlois_...@yahoo.fr wrote: Hi, Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Yan Langlois. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ant , maven , antrun , ddlutils
Hi Venkatram,
I think we would need some more information
+) what would you like to do with DDLUtils?
+) why are you triggering DDLUtils in multiple M2 projects - I have my
DB stuff usually in one subproject
+) do you have a copy of Database.properties in all subprojects?
+) how are you invoking the Ant tasks - embedded in the pom.xml or a
seperate build.xml?
Thanks in advance
Siegfried Goeschl
On 25.02.10 07:29, Stephen Connolly wrote:
please try with maven 3.0-alpha-6.
maven 2's plugin classloader only loads a plugin once during a reactor
build, so if you try to change the plugin's dependencies mid reactor,
it will blow up in your face... which _could_ look similar to your
issue... this would be the quickest way to confirm (maven 3 has fixed
it IIRC)
if your build works with 3.0-a-6 and fails with 2.2.1 then this is the
problem and we can tell you how to fix it... otherwise it's a
different problem, and we can ask you more questions
Sent from my [rhymes with tryPod] ;-)
On 25 Feb 2010, at 00:30, venkatRAM venkatram.akkin...@gmail.com wrote:
Hello everyone
I have posted this on the ant forum. The reason for this post on
maven forum
is that I am not sure where the problem is originating from. I am
trying to
use ddlutils with maven. No ready ddlutils plugin available for
maven. So I
am working with ant-run plugin. When I run the maven pom file, I get the
following output. You can notice here that the echo statement echoes the
driver value from the properties file first time and then after that
it does
not. I am not sure why this is happening. Could somebody throw
somelight on
this.
Thanks
Venkat
My config:
property file=./resources/ddlutils/Database.properties prefix=db /
echo${db.driver}/echo
taskdef
classname=org.apache.ddlutils.task.DatabaseToDdlTask
name=databaseToDdl
classpathref=maven.compile.classpath /
databaseToDdl
usedelimitedsqlidentifiers=true modelname=lean verbosity=DEBUG
database
driverclassname=org.postgresql.Driver url=${db.url}
username=${db.username} password=${db.password} /
writeschematofile
outputfile=./resources/database/schema-lean.xml /
/databaseToDdl
Error Stack Trace:
ven...@ubuntu:~/leanpm/implementation$ sudo mvn -e install
+ Error stacktraces are turned on.
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] LeanPM
[INFO] Applications
[INFO] LeanPM parent
[INFO] LeanPMJAR
[INFO] LeanPMWAR
[INFO] LeanPMEAR
[INFO] AllModules
[INFO] BuildTools
[INFO] Delivery
[INFO]
[INFO] Building LeanPM
[INFO]task-segment: [install]
[INFO]
[INFO] [antrun:run {execution: ddlutils-compile}]
[INFO] Executing tasks
[echo] org.postgresql.Driver
Borrowed connection
org.apache.commons.dbcp.poolableconnect...@19abd2b from
data source
Returning connection
org.apache.commons.dbcp.poolableconnect...@19abd2b to
data source.
Remaining connections: None
Written schema to
/home/venkat/leanpm/implementation/resources/database/schema-lean.xml
[INFO] Executed tasks
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing /home/venkat/leanpm/implementation/pom.xml to
/.m2/repository/com/oniryx/leanPM/LeanPM/0.1-SNAPSHOT/LeanPM-0.1-SNAPSHOT.pom
[INFO]
[INFO] Building Applications
[INFO]task-segment: [install]
[INFO]
[INFO] [antrun:run {execution: ddlutils-compile}]
[INFO] Executing tasks
[echo] ${db.driver}
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] An Ant BuildException has occured: Could not read the schema
from the
specified database: Could not get a connection from the datasource
No suitable driver
[INFO]
[INFO] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: An Ant
BuildException has occured: Could not read the schema from the specified
database: Could not get a connection from the datasource
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:583)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at
verifying artifact on deployment
Hi, we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. It there any way to 1. automatically test the integrity of an uploaded artefact by comparing it's generated hash with the hash of the local repo (from where it's deployed) 2. force the deploy-plugin to throw an ERROR in case the hashes do not match ? I think this is a very common and essential feature, and there should a solution to it. Regards Marc -- View this message in context: http://old.nabble.com/verifying-artifact-on-deployment-tp27714420p27714420.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
problem attaching non-archived files with maven-assembly-plugin
I am trying to deploy plain-text files (specifically, a WSDL and XSD) as part of a project with pom packaging. I would like other developers to be able to directly reference the WSDL as deployed in our local Nexus repository. I have no difficulty deploying these with the zip format. However, the dir format always seems to result in something like: [WARNING] Assembly file: C:\workspace\webservice-java-example\contract\target\contract-1.0.0- -SNAPSHOT-webservice-java-example-contracts is not a regular file (it may be a directory). It cannot be attached to the project build for installation or deployment. If I am interpreting the assembly plugin documentation properly, it would seem to suggest that this is possible. Here is what I have been doing ... plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-assembly-plugin/artifactId version2.2-beta-5/version configuration descriptors descriptorsrc/main/assembly/contracts.xml/descriptor /descriptors /configuration executions execution phasepackage/phase goals goalsingle/goal /goals /execution /executions /plugin assembly idwebservice-java-example-contracts/id formats formatdir/format /formats includeBaseDirectoryfalse/includeBaseDirectory fileSets fileSet directorysrc/main/resources/directory includes includeexample.xsd/include includeexample.wsdl/include /includes outputDirectory/outputDirectory /fileSet /fileSets /assembly -Steve Maring Tampa, FL
Re: problem attaching non-archived files with maven-assembly-plugin
Hi Steven, Maring, Steven wrote at Donnerstag, 25. Februar 2010 14:29: I am trying to deploy plain-text files (specifically, a WSDL and XSD) as part of a project with pom packaging. I would like other developers to be able to directly reference the WSDL as deployed in our local Nexus repository. [snip] Use the attach-artifact goal of the build-helper plugin: === % = plugin groupIdorg.codehaus.mojo/groupId artifactIdbuild-helper-maven-plugin/artifactId executions execution idxml-schema/id goals goalattach-artifact/goal /goals configuration artifacts artifact filesrc/main/xsd/my.xsd/file typexsd/type /artifact /artifacts /configuration /execution /executions /plugin === % = It shares the GAV of the pom. The nice thing is, you can now address it as dep of type xsd and you have on top a direct URL where it is accessible in the Maven repo. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: verifying artifact on deployment
On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig m...@marclustig.com wrote: we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. You can configure the checksum policy to fail when Maven _downloads_ an artifact if the checksum doesn't match. If you're having trouble with checksums when deploying to Archiva, it would probably be best to ask on the Archiva users list. If artifacts are getting added with the wrong checksum, that's probably a bug. It does have some 'repository health' reports that might help find the problems after the fact. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: verifying artifact on deployment
On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig m...@marclustig.com wrote: we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. You can configure the checksum policy to fail when Maven _downloads_ an artifact if the checksum doesn't match. If you're having trouble with checksums when deploying to Archiva, it would probably be best to ask on the Archiva users list. If artifacts are getting added with the wrong checksum, that's probably a bug. Could it be one of these? http://jira.codehaus.org/browse/MNG-4301 http://jira.codehaus.org/browse/MNG-4235 It does have some 'repository health' reports that might help find the problems after the fact. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: verifying artifact on deployment
thanks for the swift response. First I also thought it's an Archiva issue, but basically Maven is talking to the Repo Manager, right? So Maven defines the contract, and Archiva can only respond to the contract. We are still investigating the issue and try to reproduce different scenarios. For now, the question for us is whether Maven has the concept of artifact-verification by using hash-codes at all. Any input on this matter? 2010/2/25 Brett Porter br...@apache.org On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig m...@marclustig.com wrote: we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. You can configure the checksum policy to fail when Maven _downloads_ an artifact if the checksum doesn't match. If you're having trouble with checksums when deploying to Archiva, it would probably be best to ask on the Archiva users list. If artifacts are getting added with the wrong checksum, that's probably a bug. Could it be one of these? http://jira.codehaus.org/browse/MNG-4301 http://jira.codehaus.org/browse/MNG-4235 It does have some 'repository health' reports that might help find the problems after the fact. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Custom Archetype configuration
I have a multi-module maven project. The sub modules are pluggable apps that can be loaded in the application framework at runtime. I have created a custom archetype for creating such a new app. Since these apps run in the context of an enterprise framework, I need to enforce certain properties like the groupId and the packages name. How do I go about locking down these properties? The archetype plugin always allows the end user to override the default properties. Any help is appreciated. I apologize if this has been answered in any previous threads. I searched but could not find anything. Thanks. -- View this message in context: http://old.nabble.com/Custom-Archetype-configuration-tp27714453p27714453.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
Java.net Maven Repository Rescue Mission
As Maven users if you care about the quality of the Maven Repositories at Java.net then please help support us in our effort to get Snorcle to help fix the situation. Sonatype is going to try and help by dedicating staff on March 5th to help Java.net projects transition over to a healthy Maven repository infrastructure: http://www.sonatype.com/people/2010/02/java-net-maven-repository-rescue-mission-on-march-5th/ We already have support from Jean-Francois Arcand: http://weblogs.java.net/blog/jfarcand/archive/2010/02/25/pain-over-javanets-maven-artifacts Please show your support by voting on the DZone article here, which seems to draw attention: http://www.dzone.com/links/javanet_maven_repository_rescue_mission_on_march.html It's all about visibility and if we have enough users in the Maven community raise this as a concern then maybe we'll get somewhere this time. And if you're a project at Java.net please let us help you on March 5th! Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: Ant , maven , antrun , ddlutils
The expression ${db.driver} is getting resolved. But in your actual database
connection definition you have hard coded the driver class name. So the
driver cannot be the problem. From the stacktrace it looks like the schema
name is not getting resolved. It could be because your db.url or username or
password is not getting resolved or is plain wrong. Make sure they are
getting resolved and that you can connect to the database using those
credentials and the url from outside of your build script.
--
View this message in context:
http://old.nabble.com/Ant-%2C-maven-%2C-antrun-%2C-ddlutils-tp27714325p27714459.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: Java.net Maven Repository Rescue Mission
Jason- As I commented on your blog entry, what I think would be most useful is to handle the currently deployed javax.* artifacts. Don't get me wrong, dealing with the current/new releases will be helpful. Would Sonatype be willing to accept a list of artifact submissions from the community and then proactively work with the responsible project teams? For anyone running an caching MRM, it should be trivial to look in the cache for the java.net repo. Culling this list should be fairly straight forward. If the goal is to eliminiate (not just reduce) the dependency on the java.net repo, I'm pretty sure something like the above will need to be done. Justin On 2/25/10 10:15 AM, Jason van Zyl wrote: As Maven users if you care about the quality of the Maven Repositories at Java.net then please help support us in our effort to get Snorcle to help fix the situation. Sonatype is going to try and help by dedicating staff on March 5th to help Java.net projects transition over to a healthy Maven repository infrastructure: http://www.sonatype.com/people/2010/02/java-net-maven-repository-rescue-mission-on-march-5th/ We already have support from Jean-Francois Arcand: http://weblogs.java.net/blog/jfarcand/archive/2010/02/25/pain-over-javanets-maven-artifacts Please show your support by voting on the DZone article here, which seems to draw attention: http://www.dzone.com/links/javanet_maven_repository_rescue_mission_on_march.html It's all about visibility and if we have enough users in the Maven community raise this as a concern then maybe we'll get somewhere this time. And if you're a project at Java.net please let us help you on March 5th! Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ant , maven , antrun , ddlutils
Hello Golgradio
Well I was able to figure it out last night didn't have time to post the
reply. But here is goes. You were right about the db.url , username and
password not getting resolved. The reason was that this part of root POM was
being called multiple times worse yet from different locations. So my guess
was that Maven cannot find the .properties file. So I hardcoded the file
location into POM file. It ran like a charm.
Also I did not need this to be called multiple times. So I moved the code
into the Delivery module of the application. This solved the issue.
Once again thanks for your reply
Venkat
golfradio wrote:
The expression ${db.driver} is getting resolved. But in your actual
database connection definition you have hard coded the driver class name.
So the driver cannot be the problem. From the stacktrace it looks like the
schema name is not getting resolved. It could be because your db.url or
username or password is not getting resolved or is plain wrong. Make sure
they are getting resolved and that you can connect to the database using
those credentials and the url from outside of your build script.
--
View this message in context:
http://old.nabble.com/Ant-%2C-maven-%2C-antrun-%2C-ddlutils-tp27714325p27714463.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: Java.net Maven Repository Rescue Mission
Justin, Yes we would but obviously the license on those binaries is important. Some of the original binaries couldn't be redistributed which is why they were pulled from central years ago. On Thu, Feb 25, 2010 at 10:28 AM, Justin Edelson justinedel...@gmail.com wrote: Jason- As I commented on your blog entry, what I think would be most useful is to handle the currently deployed javax.* artifacts. Don't get me wrong, dealing with the current/new releases will be helpful. Would Sonatype be willing to accept a list of artifact submissions from the community and then proactively work with the responsible project teams? For anyone running an caching MRM, it should be trivial to look in the cache for the java.net repo. Culling this list should be fairly straight forward. If the goal is to eliminiate (not just reduce) the dependency on the java.net repo, I'm pretty sure something like the above will need to be done. Justin On 2/25/10 10:15 AM, Jason van Zyl wrote: As Maven users if you care about the quality of the Maven Repositories at Java.net then please help support us in our effort to get Snorcle to help fix the situation. Sonatype is going to try and help by dedicating staff on March 5th to help Java.net projects transition over to a healthy Maven repository infrastructure: http://www.sonatype.com/people/2010/02/java-net-maven-repository-rescue-mission-on-march-5th/ We already have support from Jean-Francois Arcand: http://weblogs.java.net/blog/jfarcand/archive/2010/02/25/pain-over-javanets-maven-artifacts Please show your support by voting on the DZone article here, which seems to draw attention: http://www.dzone.com/links/javanet_maven_repository_rescue_mission_on_march.html It's all about visibility and if we have enough users in the Maven community raise this as a concern then maybe we'll get somewhere this time. And if you're a project at Java.net please let us help you on March 5th! Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ant , maven , antrun , ddlutils
Always a pleasure to help
Siegfried Goeschl
On 25.02.10 16:32, venkatRAM wrote:
Hello Golgradio
Well I was able to figure it out last night didn't have time to post the
reply. But here is goes. You were right about the db.url , username and
password not getting resolved. The reason was that this part of root POM was
being called multiple times worse yet from different locations. So my guess
was that Maven cannot find the .properties file. So I hardcoded the file
location into POM file. It ran like a charm.
Also I did not need this to be called multiple times. So I moved the code
into the Delivery module of the application. This solved the issue.
Once again thanks for your reply
Venkat
golfradio wrote:
The expression ${db.driver} is getting resolved. But in your actual
database connection definition you have hard coded the driver class name.
So the driver cannot be the problem. From the stacktrace it looks like the
schema name is not getting resolved. It could be because your db.url or
username or password is not getting resolved or is plain wrong. Make sure
they are getting resolved and that you can connect to the database using
those credentials and the url from outside of your build script.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Java.net Maven Repository Rescue Mission
Hi, On Thu, Feb 25, 2010 at 10:36 AM, Brian Fox bri...@infinity.nu wrote: Justin, Yes we would but obviously the license on those binaries is important. Some of the original binaries couldn't be redistributed which is why they were pulled from central years ago. Well, one thing that could be done to help this problem is to locate all projects which depend on the unfriendly licenses and convert them to use the Geronimo specification packages instead. Once those (superficial?) changes had been completed, there would be little stopping them from being deployed into Central. Can such a query be crafted--to locate all of the projects which depend on Sun/Oracle javax.*? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Java.net Maven Repository Rescue Mission
On 2/25/10 10:36 AM, Brian Fox wrote: Justin, Yes we would but obviously the license on those binaries is important. Some of the original binaries couldn't be redistributed which is why they were pulled from central years ago. ...obligatory IANAL... My understanding, and I could be wrong about this, is that these artifacts were pulled because there was no way to have the user accept the license agreement before downloading. However, Sun/Oracle distributes these artifacts (via the java.net repo) without this pre-download requirement. This doesn't necessarily mean that redistribution via central is ok, but it does suggest that it is at least worth having the conversation. (Furthermore, the JTA JAR on the java.net repository has *no* license information, so it's not like they're being diligent about this kind of thing.) Perhaps I should have written legal teams instead of project teams below. Justin On Thu, Feb 25, 2010 at 10:28 AM, Justin Edelson justinedel...@gmail.com wrote: Jason- As I commented on your blog entry, what I think would be most useful is to handle the currently deployed javax.* artifacts. Don't get me wrong, dealing with the current/new releases will be helpful. Would Sonatype be willing to accept a list of artifact submissions from the community and then proactively work with the responsible project teams? For anyone running an caching MRM, it should be trivial to look in the cache for the java.net repo. Culling this list should be fairly straight forward. If the goal is to eliminiate (not just reduce) the dependency on the java.net repo, I'm pretty sure something like the above will need to be done. Justin On 2/25/10 10:15 AM, Jason van Zyl wrote: As Maven users if you care about the quality of the Maven Repositories at Java.net then please help support us in our effort to get Snorcle to help fix the situation. Sonatype is going to try and help by dedicating staff on March 5th to help Java.net projects transition over to a healthy Maven repository infrastructure: http://www.sonatype.com/people/2010/02/java-net-maven-repository-rescue-mission-on-march-5th/ We already have support from Jean-Francois Arcand: http://weblogs.java.net/blog/jfarcand/archive/2010/02/25/pain-over-javanets-maven-artifacts Please show your support by voting on the DZone article here, which seems to draw attention: http://www.dzone.com/links/javanet_maven_repository_rescue_mission_on_march.html It's all about visibility and if we have enough users in the Maven community raise this as a concern then maybe we'll get somewhere this time. And if you're a project at Java.net please let us help you on March 5th! Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Java.net Maven Repository Rescue Mission
On Feb 25, 2010, at 10:56 AM, Justin Edelson wrote: On 2/25/10 10:36 AM, Brian Fox wrote: Justin, Yes we would but obviously the license on those binaries is important. Some of the original binaries couldn't be redistributed which is why they were pulled from central years ago. ...obligatory IANAL... My understanding, and I could be wrong about this, is that these artifacts were pulled because there was no way to have the user accept the license agreement before downloading. It was actually Apache that made me pull them off. Sun didn't care and weren't going to sue us. But that was the Sun Binary License and that's not used anymore. At least I haven't seen any artifacts of late using that license. All seems to be CDDL. However, Sun/Oracle distributes these artifacts (via the java.net repo) without this pre-download requirement. This doesn't necessarily mean that redistribution via central is ok, but it does suggest that it is at least worth having the conversation. (Furthermore, the JTA JAR on the java.net repository has *no* license information, so it's not like they're being diligent about this kind of thing.) Perhaps I should have written legal teams instead of project teams below. Justin On Thu, Feb 25, 2010 at 10:28 AM, Justin Edelson justinedel...@gmail.com wrote: Jason- As I commented on your blog entry, what I think would be most useful is to handle the currently deployed javax.* artifacts. Don't get me wrong, dealing with the current/new releases will be helpful. Would Sonatype be willing to accept a list of artifact submissions from the community and then proactively work with the responsible project teams? For anyone running an caching MRM, it should be trivial to look in the cache for the java.net repo. Culling this list should be fairly straight forward. If the goal is to eliminiate (not just reduce) the dependency on the java.net repo, I'm pretty sure something like the above will need to be done. Justin On 2/25/10 10:15 AM, Jason van Zyl wrote: As Maven users if you care about the quality of the Maven Repositories at Java.net then please help support us in our effort to get Snorcle to help fix the situation. Sonatype is going to try and help by dedicating staff on March 5th to help Java.net projects transition over to a healthy Maven repository infrastructure: http://www.sonatype.com/people/2010/02/java-net-maven-repository-rescue-mission-on-march-5th/ We already have support from Jean-Francois Arcand: http://weblogs.java.net/blog/jfarcand/archive/2010/02/25/pain-over-javanets-maven-artifacts Please show your support by voting on the DZone article here, which seems to draw attention: http://www.dzone.com/links/javanet_maven_repository_rescue_mission_on_march.html It's all about visibility and if we have enough users in the Maven community raise this as a concern then maybe we'll get somewhere this time. And if you're a project at Java.net please let us help you on March 5th! Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl -- - 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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Re: Java.net Maven Repository Rescue Mission
On 2/25/10 10:47 AM, Jesse Farinacci wrote: Hi, On Thu, Feb 25, 2010 at 10:36 AM, Brian Fox bri...@infinity.nu wrote: Justin, Yes we would but obviously the license on those binaries is important. Some of the original binaries couldn't be redistributed which is why they were pulled from central years ago. Well, one thing that could be done to help this problem is to locate all projects which depend on the unfriendly licenses and convert them to use the Geronimo specification packages instead. Once those (superficial?) changes had been completed, there would be little stopping them from being deployed into Central. Unless these artifacts are going to be deployed as javax.something, this would require changing poms which have already deployed to Central: http://repo1.maven.org/maven2/log4j/log4j/1.2.15/log4j-1.2.15.pom There are a few open feature requests for global exclusions and artifact replacement strategies. Those would enable the wholesale replacement of javax for geronimo packages. Justin Can such a query be crafted--to locate all of the projects which depend on Sun/Oracle javax.*? -Jesse - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Eclipse Plugin 2.8 Released
The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.8. This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. Please see the plugin's site for details: http://maven.apache.org/plugins/maven-eclipse-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.8/version /plugin To use the updated plugin from command line, add the flag -U the next time you invoke mvn eclipse:eclipse in order to have Maven check for the update and download it. Release Notes - Maven 2.x Eclipse Plugin - Version 2.8 ** Bug * [MECLIPSE-368] - Dependency configuration in DependencyManagement with exclusions is ignored * [MECLIPSE-492] - Maven Eclipse Plugin does not take dependencyManagement excludes into account when building eclipse CP configuration. * [MECLIPSE-558] - Ignoring listed AspectJ dependencies * [MECLIPSE-568] - Some compile dependencies are not added to .classpath since 2.6 * [MECLIPSE-569] - eclipse:eclipse does not add all libraries to .classpath * [MECLIPSE-584] - No eclipse classpath entries generated for aspectj dependencies * [MECLIPSE-603] - Exclusions are not applied on transitive dependencies * [MECLIPSE-631] - [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml * [MECLIPSE-633] - [Maven 3] j2ee-simple integration test fails * [MECLIPSE-637] - mvn eclipse:to-maven deploy to nexus fails if nexus security is active ** New Feature * [MECLIPSE-156] - Plugin should support setting file encoding * [MECLIPSE-178] - symbolic links need to able to be specified in the pom ** Task * [MECLIPSE-594] - set AJDT version parameter to none by default * [MECLIPSE-632] - Add markers in the generated project files that can identify them as being created by the maven-eclipse-plugin Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Eclipse Plugin 2.8 Released
I just went to the link below to look for an update site, but found none Can you pass it on here? Thanks, and good work! On Thu, Feb 25, 2010 at 9:46 AM, Benjamin Bentmann bentm...@apache.orgwrote: The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.8. This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. Please see the plugin's site for details: http://maven.apache.org/plugins/maven-eclipse-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.8/version /plugin To use the updated plugin from command line, add the flag -U the next time you invoke mvn eclipse:eclipse in order to have Maven check for the update and download it. Release Notes - Maven 2.x Eclipse Plugin - Version 2.8 ** Bug * [MECLIPSE-368] - Dependency configuration in DependencyManagement with exclusions is ignored * [MECLIPSE-492] - Maven Eclipse Plugin does not take dependencyManagement excludes into account when building eclipse CP configuration. * [MECLIPSE-558] - Ignoring listed AspectJ dependencies * [MECLIPSE-568] - Some compile dependencies are not added to .classpath since 2.6 * [MECLIPSE-569] - eclipse:eclipse does not add all libraries to .classpath * [MECLIPSE-584] - No eclipse classpath entries generated for aspectj dependencies * [MECLIPSE-603] - Exclusions are not applied on transitive dependencies * [MECLIPSE-631] - [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml * [MECLIPSE-633] - [Maven 3] j2ee-simple integration test fails * [MECLIPSE-637] - mvn eclipse:to-maven deploy to nexus fails if nexus security is active ** New Feature * [MECLIPSE-156] - Plugin should support setting file encoding * [MECLIPSE-178] - symbolic links need to able to be specified in the pom ** Task * [MECLIPSE-594] - set AJDT version parameter to none by default * [MECLIPSE-632] - Add markers in the generated project files that can identify them as being created by the maven-eclipse-plugin Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- - Ed
Re: [ANN] Maven Eclipse Plugin 2.8 Released
This is not M2Eclipse, it's not an Eclipse plugin what got released is a Maven plugin. I think you're looking for: http://m2eclipse.sonatype.org/sites Which is where all the update sites are. On Feb 25, 2010, at 12:36 PM, Ed Young wrote: I just went to the link below to look for an update site, but found none Can you pass it on here? Thanks, and good work! On Thu, Feb 25, 2010 at 9:46 AM, Benjamin Bentmann bentm...@apache.orgwrote: The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.8. This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. Please see the plugin's site for details: http://maven.apache.org/plugins/maven-eclipse-plugin/ To use the updated plugin in your projects, you need to add the following snippet to the plugins or plugin management section of your POM: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.8/version /plugin To use the updated plugin from command line, add the flag -U the next time you invoke mvn eclipse:eclipse in order to have Maven check for the update and download it. Release Notes - Maven 2.x Eclipse Plugin - Version 2.8 ** Bug * [MECLIPSE-368] - Dependency configuration in DependencyManagement with exclusions is ignored * [MECLIPSE-492] - Maven Eclipse Plugin does not take dependencyManagement excludes into account when building eclipse CP configuration. * [MECLIPSE-558] - Ignoring listed AspectJ dependencies * [MECLIPSE-568] - Some compile dependencies are not added to .classpath since 2.6 * [MECLIPSE-569] - eclipse:eclipse does not add all libraries to .classpath * [MECLIPSE-584] - No eclipse classpath entries generated for aspectj dependencies * [MECLIPSE-603] - Exclusions are not applied on transitive dependencies * [MECLIPSE-631] - [Maven 3] Integration test project-44 fails with Unable to resolve resource location: /checkstyle-config.xml * [MECLIPSE-633] - [Maven 3] j2ee-simple integration test fails * [MECLIPSE-637] - mvn eclipse:to-maven deploy to nexus fails if nexus security is active ** New Feature * [MECLIPSE-156] - Plugin should support setting file encoding * [MECLIPSE-178] - symbolic links need to able to be specified in the pom ** Task * [MECLIPSE-594] - set AJDT version parameter to none by default * [MECLIPSE-632] - Add markers in the generated project files that can identify them as being created by the maven-eclipse-plugin Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- - Ed Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl --
Maven release plugin and multi VOB (Clearcase) project
Hi, I am working with a multi module Maven structure which spans several Clearcase VOBs. I am using an aggregator POM which builds all the modules across the different VOBs. When I issue a 'mvn release:prepare' command, the project verifies correctly, all POMs are correctly updated and checked in, in all of the different VOBs. Only problem is that the plugin has only tagged/labeled the code in the main VOB rather than in all of the VOBs I am using. That is, it correctly updates the dependencies and checks the POMs in but does not tag the code in the VOBs the other POMs are located in. I have verified that my scm element is correctly specified in each POM so I don't think that is the problem, furthermore the plugin is checking the code into the different VOBs, just not tagging. Thank-you for any suggestions, work around or patch suggested. $ mvn.bat -version Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700) Java version: 1.6.0_17 Java home: C:\Program Files\Java\jdk1.6.0_17\jre Default locale: en_US, platform encoding: Cp1252 OS name: windows xp version: 5.1 arch: x86 Family: windows plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration allowTimestampedSnapshotstrue/allowTimestampedSnapshots /configuration /plugin Cheers, Bernard - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Release notification
Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Seems like a feature I'd expect to get from an MRM (Nexus, Artifactory, Archiva) rather than from Maven itself. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Release notification
We use Nexus for RSS feeds, it has a built-in feed for releases. Kalle On Thu, Feb 25, 2010 at 10:06 AM, Wayne Fay wayne...@gmail.com wrote: Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Seems like a feature I'd expect to get from an MRM (Nexus, Artifactory, Archiva) rather than from Maven itself. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Custom Archetype configuration
custom archetype for creating such a new app. Since these apps run in the context of an enterprise framework, I need to enforce certain properties like the groupId and the packages name. I'm not aware of any way to lock down these properties. You could file an issue in Jira so someone could consider adding it in a future release. Perhaps this could be managed in your MRM (Nexus, Archiva, etc) instead? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Re : Release notification
If you use Staging in Nexus, you can get emails when a release is staged and optionally also when it is later promoted. You can see these emails on the maven-dev list anytime we stage a release. On Thu, Feb 25, 2010 at 1:30 PM, Kalle Korhonen kalle.o.korho...@gmail.com wrote: We use Nexus for RSS feeds, it has a built-in feed for releases. Kalle On Thu, Feb 25, 2010 at 10:06 AM, Wayne Fay wayne...@gmail.com wrote: Is there a way to add notifications (email, RSS, etc.) when a release is performed ? Seems like a feature I'd expect to get from an MRM (Nexus, Artifactory, Archiva) rather than from Maven itself. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ejb3 jboss persistence problem
Hi,
I want to develop an EJB3 application with maven but I have any problem on
library such as jboss-ejb3-all and thirdparty-all into dependance, I display
my pom.xml it'is possible to help me to improve this pom:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdfr.auction/groupId
artifactIdcaveatemptor-jpa/artifactId
packagingwar/packaging
version1.0/version
namecaveatemptor-jpa Maven Webapp/name
urlhttp://maven.apache.org/url
build
finalNamecaveatemptor-jpa/finalName
sourceDirectorysrc/main/java/sourceDirectory
testSourceDirectorysrc/test/java/testSourceDirectory
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
groupIdorg.jboss.aop/groupId
artifactIdjboss-aop/artifactId
version${version.jboss.aop}/version
/plugin
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
ejbVersion3.0/ejbVersion
/configuration
/plugin
/plugins
/build
dependencies
dependency
groupIdjavax.persistence/groupId
artifactIdpersistence-api/artifactId
version1.0/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-annotations/artifactId
version3.3.0.ga/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate/artifactId
version3.2.5.ga/version
exclusions
exclusion
groupIdjavax.transaction/groupId
artifactIdjta/artifactId
/exclusion
/exclusions
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-tools/artifactId
version3.2.0.ga/version
/dependency
dependency
groupIdorg.hibernate/groupId
artifactIdhibernate-entitymanager/artifactId
version3.3.2.GA/version
/dependency
dependency
groupIdorg.dbunit/groupId
artifactIddbunit/artifactId
version2.2.3/version
scopetest/scope
/dependency
dependency
groupIdjunit/groupId
artifactIdjunit/artifactId
version3.8.1/version
scopetest/scope
/dependency
dependency
groupIdorg.testng/groupId
artifactIdtestng/artifactId
version5.8/version
scopetest/scope
classifierjdk15/classifier
/dependency
/dependencies
/project
neo anderson wrote:
Previously I successfully build ejb3 example with jboss version 4.2.2 by
specifying jboss library in the 'systempath'. Now I want to make use of
the maven (jboss) repository. So I change to use the dependency section of
pom.xml, modifying repository and dependency section; it is as follow:
repositories
repository
idjboss-maven2/id
urlhttp://repository.jboss.com/url
/repository
/repositories
...
dependency
groupIdjboss/groupId
artifactIdjboss-persistence-api/artifactId
version3.0.0-SNAPSHOT/version
/dependency
dependency
groupIdjboss/groupId
artifactIdjboss-ejb-api/artifactId
version4.2.0.GA/version
/dependency
But maven returns message like
Missing:
--
1) jboss:jboss-persistence-api:jar:3.0.0-SNAPSHOT
Try downloading the file manually from the project website.
I am able to to see the jar file located in the
http://repository.jboss.com/jboss/jboss-persistence-api/ (The dependency
for jboss-ejb-api works fine.) How to solve this error without downing/
installing the jar manually?
Thanks for help,
--
View this message in context:
http://old.nabble.com/ejb3-jboss-persistence-problem-tp16653034p27714503.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: verifying artifact on deployment
It does on download not on upload. Nexus Staging has the ability to validate artifacts before being allowed to be staged, things like pom criteria, pgp sigs etc. We don't have a hash rule but its trivial to add. On Thu, Feb 25, 2010 at 10:02 AM, Marc Lustig arin...@googlemail.com wrote: thanks for the swift response. First I also thought it's an Archiva issue, but basically Maven is talking to the Repo Manager, right? So Maven defines the contract, and Archiva can only respond to the contract. We are still investigating the issue and try to reproduce different scenarios. For now, the question for us is whether Maven has the concept of artifact-verification by using hash-codes at all. Any input on this matter? 2010/2/25 Brett Porter br...@apache.org On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig m...@marclustig.com wrote: we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. You can configure the checksum policy to fail when Maven _downloads_ an artifact if the checksum doesn't match. If you're having trouble with checksums when deploying to Archiva, it would probably be best to ask on the Archiva users list. If artifacts are getting added with the wrong checksum, that's probably a bug. Could it be one of these? http://jira.codehaus.org/browse/MNG-4301 http://jira.codehaus.org/browse/MNG-4235 It does have some 'repository health' reports that might help find the problems after the fact. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.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
Unexpected behavior in parsing modelVersion element (mvn 2.2.x)
I'm using 2.2.x and was surprised to find that, while valid XML, the following
are not valid in a pom.xml:
modelVersion 4.0.0 /modelVersion
or
modelVersion
4.0.0
/modelVersion
I had expected that the maven xml parser would be normalizing the whitespace,
but looked in
maven-2.2.x/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
and found this in readModel(), line 1609:
if ( modelSource.indexOf( modelVersion + MAVEN_MODEL_VERSION ) 0 )
{
throw new InvalidProjectModelException( projectId, pomLocation,
Not a v + MAVEN_MODEL_VERSION + POM. );
}
Why is the parser hand-parsing this piece of the XML instead of looking at the
child content and normalizing/trimming whitespace? It's counterintuitive to me
as a user, since the POM XSD decalres modelVersion to be xs:string and there is
no mention anywhere that I'm not allowed to use whitespace.
jon
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Multiple active profiles issue
Hello all, I'm having a little problem with profiles that I can't quite seem to figure out. I have a pom that has 3 profiles defined in it. 2 active by default and one active if a env var is set (BUILD_TAG). My little test pom is below. Now, when I do not set BUILD_TAG, it works as I expect. [INFO] [help:active-profiles] [INFO] Active Profiles for Project 'test:test:pom:0.1': The following profiles are active: - win32 (source: pom) - win64 (source: pom) - profile-1 (source: settings.xml) But as soon as I set the env var, the win32 and win64 profiles go away: [INFO] [help:active-profiles] [INFO] Active Profiles for Project 'test:test:pom:0.1': The following profiles are active: - hudson (source: pom) - profile-1 (source: settings.xml) We typically use Maven 2.1.0 but I have also tested Maven 2.2.1. I tried Maven 3.0 and that ignores the env var all together. Any ideas on what I may be doing wrong in my pom? -Jim ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdtest/artifactId packagingpom/packaging version0.1/version profiles profile idwin32/id activation activeByDefaulttrue/activeByDefault /activation /profile profile idwin64/id activation activeByDefaulttrue/activeByDefault /activation /profile profile idhudson/id activation activeByDefaultfalse/activeByDefault property nameenv.BUILD_TAG/name /property /activation /profile /profiles /project - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: verifying artifact on deployment
Artifactory 2.2.2 (the upcoming minor release) already has configurable checksum verification for _uploaded_ artifacts too. FYI. On Thu, Feb 25, 2010 at 5:02 PM, Marc Lustig arin...@googlemail.com wrote: thanks for the swift response. First I also thought it's an Archiva issue, but basically Maven is talking to the Repo Manager, right? So Maven defines the contract, and Archiva can only respond to the contract. We are still investigating the issue and try to reproduce different scenarios. For now, the question for us is whether Maven has the concept of artifact-verification by using hash-codes at all. Any input on this matter? 2010/2/25 Brett Porter br...@apache.org On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig m...@marclustig.com wrote: we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. You can configure the checksum policy to fail when Maven _downloads_ an artifact if the checksum doesn't match. If you're having trouble with checksums when deploying to Archiva, it would probably be best to ask on the Archiva users list. If artifacts are getting added with the wrong checksum, that's probably a bug. Could it be one of these? http://jira.codehaus.org/browse/MNG-4301 http://jira.codehaus.org/browse/MNG-4235 It does have some 'repository health' reports that might help find the problems after the fact. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Multiple active profiles issue
To answer my own question (talking to myself in public... sheesh), I fixed it well enough for me (see pom below). I also think it turns out as working as designed. Apparently if any activation element comes up true, it overrides all activeByDefault elements [1]. I guess I assumed that meant it was active unless deactivated via cli. Live and learn. -Jim [1] http://maven.apache.org/guides/introduction/introduction-to-profiles.html (search for activeByDefault) ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdtest/artifactId packagingpom/packaging version0.1/version profiles profile idwin32/id activation activeByDefaulttrue/activeByDefault property nameenv.BUILD_TAG/name /property /activation /profile profile idwin64/id activation activeByDefaulttrue/activeByDefault property nameenv.BUILD_TAG/name /property /activation /profile profile idhudson/id activation activeByDefaultfalse/activeByDefault property nameenv.BUILD_TAG/name /property /activation /profile /profiles /project -Original Message- From: Jim McCaskey [mailto:jim.mccas...@pervasive.com] Sent: Thursday, February 25, 2010 2:41 PM To: 'users@maven.apache.org' Subject: Multiple active profiles issue Hello all, I'm having a little problem with profiles that I can't quite seem to figure out. I have a pom that has 3 profiles defined in it. 2 active by default and one active if a env var is set (BUILD_TAG). My little test pom is below. Now, when I do not set BUILD_TAG, it works as I expect. [INFO] [help:active-profiles] [INFO] Active Profiles for Project 'test:test:pom:0.1': The following profiles are active: - win32 (source: pom) - win64 (source: pom) - profile-1 (source: settings.xml) But as soon as I set the env var, the win32 and win64 profiles go away: [INFO] [help:active-profiles] [INFO] Active Profiles for Project 'test:test:pom:0.1': The following profiles are active: - hudson (source: pom) - profile-1 (source: settings.xml) We typically use Maven 2.1.0 but I have also tested Maven 2.2.1. I tried Maven 3.0 and that ignores the env var all together. Any ideas on what I may be doing wrong in my pom? -Jim ?xml version=1.0 encoding=UTF-8? project modelVersion4.0.0/modelVersion groupIdtest/groupId artifactIdtest/artifactId packagingpom/packaging version0.1/version profiles profile idwin32/id activation activeByDefaulttrue/activeByDefault /activation /profile profile idwin64/id activation activeByDefaulttrue/activeByDefault /activation /profile profile idhudson/id activation activeByDefaultfalse/activeByDefault property nameenv.BUILD_TAG/name /property /activation /profile /profiles /project - 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
Grails plugin initialization error
I get this error after following: http://www.grails.org/Maven+Integration * WARNINGS module not found: org.hibernate#hibernate-commons-annotations; 3.3.0.ga grailsPlugins: tried -- artifact org.hibernate#hibernate-commons-annotations;3.3.0.ga !hibernate-commons-annotations.jar: /Users/mickknutson/svnworkspaces/DIVR2/lib/hibernate-commons-annotations-3.3.0.ga.jar /Users/mickknutson/svnworkspaces/DIVR2/plugins/hibernate-1.2.0/lib/hibernate-commons-annotations-3.3.0.ga.jar module not found: javassist#javassist;3.8.0.GA grailsPlugins: tried -- artifact javassist#javassist;3.8.0.GA!javassist.jar: /Users/mickknutson/svnworkspaces/DIVR2/lib/javassist-3.8.0.GA.jar /Users/mickknutson/svnworkspaces/DIVR2/plugins/hibernate-1.2.0/lib/javassist-3.8.0.GA.jar :: :: UNRESOLVED DEPENDENCIES :: :: :: org.hibernate#hibernate-commons-annotations;3.3.0.ga: not found :: javassist#javassist;3.8.0.GA: not found :: Failed to install plugin [hibernate-1.2.0]. Plugin has missing JAR dependencies. [delete] Deleting directory /Users/mickknutson/svnworkspaces/DIVR2/plugins/hibernate-1.2.0 * --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://www.baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com ---
Re: Checkstyle and multi module
Which version of the Checkstyle Plugin are you using? On 2010-02-25 12:05, Thomas Scheffler wrote: Hi, I have a multi module project with this layout Base |-- pom.xml |-- build-tools | |-- src | | `-- main | | `-- resources | | `-- org | | `-- project | | `-- checkstyle.xml | `-- pom.xml |-- parent |-- module1 |-- module2 `-- modulen Everything is like it is described in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html with one exception: The Base/pom.xml is not the parent module pom but Base/parent/pom.xml is. After following the guide above I can run mvn checkstyle:checkstyle fine on all modules and it uses the checkstyle.xml from the build-tools module. Just mvn site will not work with this error: [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Failed during checkstyle execution Could not find resource 'org/project/checkstyle.xml'. Why does it work with checkstyle:checkstyle and not with site? Thanks Thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
FW: [Maven2] Blacklisted by repo1?
Does anyone have any guidance on how to find out if some of my company’s IPs are being blocked access to repo1? Perhaps this is a Nexus forum question, so I am cross posting. Anyways, I would like to proactively work with someone at Sonatype to avoid being blacklisted. · I have already distributed a standard settings.xml with a mirrors that directs everyone to our corporate repo · Communicated that we are not to hit repo1 directly Thanks, Ronak ___ Maven2 mailing list mav...@listmgr.mv.intuit.com http://listmgr.mv.intuit.com/mailman/listinfo/maven2 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unexpected behavior in parsing modelVersion element (mvn 2.2.x)
That would be a bug. Please file it at http://jira.codehaus.org/browse/MNG.
On 26/02/2010, at 5:13 AM, Jonathan Gold wrote:
I'm using 2.2.x and was surprised to find that, while valid XML, the following
are not valid in a pom.xml:
modelVersion 4.0.0 /modelVersion
or
modelVersion
4.0.0
/modelVersion
I had expected that the maven xml parser would be normalizing the whitespace,
but looked in
maven-2.2.x/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
and found this in readModel(), line 1609:
if ( modelSource.indexOf( modelVersion + MAVEN_MODEL_VERSION ) 0
)
{
throw new InvalidProjectModelException( projectId, pomLocation,
Not a v + MAVEN_MODEL_VERSION + POM. );
}
Why is the parser hand-parsing this piece of the XML instead of looking at the
child content and normalizing/trimming whitespace? It's counterintuitive to me
as a user, since the POM XSD decalres modelVersion to be xs:string and there
is
no mention anywhere that I'm not allowed to use whitespace.
jon
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Brett Porter
br...@apache.org
http://brettporter.wordpress.com/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: [nexus-user] FW: [Maven2] Blacklisted by repo1?
Nevermind, we have Maven support purchased and I believe that would be the right way to go about this issue. From: Rahman, Ronak [mailto:ronak_rah...@intuit.com] Sent: Thursday, February 25, 2010 5:03 PM To: Maven Users List; nexus-u...@sonatype.org Subject: [nexus-user] FW: [Maven2] Blacklisted by repo1? Does anyone have any guidance on how to find out if some of my company’s IPs are being blocked access to repo1? Perhaps this is a Nexus forum question, so I am cross posting. Anyways, I would like to proactively work with someone at Sonatype to avoid being blacklisted. · I have already distributed a standard settings.xml with a mirrors that directs everyone to our corporate repo · Communicated that we are not to hit repo1 directly Thanks, Ronak
Re: FW: [Maven2] Blacklisted by repo1?
Forwarding to the right list repo-maintain...@maven.apache.org On Thu, Feb 25, 2010 at 3:02 PM, Rahman, Ronak ronak_rah...@intuit.com wrote: Does anyone have any guidance on how to find out if some of my company’s IPs are being blocked access to repo1? Perhaps this is a Nexus forum question, so I am cross posting. Anyways, I would like to proactively work with someone at Sonatype to avoid being blacklisted. · I have already distributed a standard settings.xml with a mirrors that directs everyone to our corporate repo · Communicated that we are not to hit repo1 directly Thanks, Ronak ___ Maven2 mailing list mav...@listmgr.mv.intuit.com http://listmgr.mv.intuit.com/mailman/listinfo/maven2 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: assembly and including a test-jar
Thanks for the reply. I'm not sure how to select the correct file for inclusion in the assembly, but I tried many different combinations in the include tags: includecom.comcast.vodauto:vodtest:*:test/include ... includecom.comcast.vodauto:vodtest:*:test-jar/include ... The assembly plugin always includes the wrong file. On Wed, Feb 24, 2010 at 5:58 AM, Karl Heinz Marbaise k...@soebes.de wrote: Hi, i assume your problem is due to the includes you have defined... Edderd wrote: includecom.comcast.vodauto:vodmain/include includecom.comcast.vodauto:vodtest/include http://maven.apache.org/plugins/maven-assembly-plugin/examples/single/including-and-excluding-artifacts.html You could use includegroupId:artifactId:type:classifier/include format to include a particular type... may be includecom.comcast.vodauto:vodtest:*:test/include instead would help ? Kind regards Karl Heinz Marbaise -- View this message in context: http://old.nabble.com/assembly-and-including-a-test-jar-tp27712959p27714192.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 -- - Ed
Re: verifying artifact on deployment
On 26/02/2010, at 2:02 AM, Marc Lustig wrote: thanks for the swift response. First I also thought it's an Archiva issue, but basically Maven is talking to the Repo Manager, right? So Maven defines the contract, and Archiva can only respond to the contract. We are still investigating the issue and try to reproduce different scenarios. For now, the question for us is whether Maven has the concept of artifact-verification by using hash-codes at all. Any input on this matter? Maven can't really do anything without either having a specific relationship with a repository manager (requesting it send back the checksum of an actual file, not the checksum it just sent), or redownloading the entire file. It is better for the repository manager to deal with uploads that don't match their checksum and give Maven back an HTTP error at the conclusion of the upload. Currently, Archiva is only checking the content length matches on upload to prevent partial upload corruption, and filing problem reports for mismatches with checksums from misbehaving clients as Wendy said. Please let us know if we can help diagnose the issue if it's not as simple as avoiding the scenarios in the two issues I listed. Thanks, Brett 2010/2/25 Brett Porter br...@apache.org On 26/02/2010, at 1:30 AM, Wendy Smoak wrote: On Thu, Feb 25, 2010 at 8:10 AM, Marc Lustig m...@marclustig.com wrote: we had a number of cases when the artifact in our central-repo (Archiva-based) was not consistent with the corresponding hash. You can configure the checksum policy to fail when Maven _downloads_ an artifact if the checksum doesn't match. If you're having trouble with checksums when deploying to Archiva, it would probably be best to ask on the Archiva users list. If artifacts are getting added with the wrong checksum, that's probably a bug. Could it be one of these? http://jira.codehaus.org/browse/MNG-4301 http://jira.codehaus.org/browse/MNG-4235 It does have some 'repository health' reports that might help find the problems after the fact. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Checkstyle and multi module
Am 25.02.2010 23:01, schrieb Dennis Lundberg: Which version of the Checkstyle Plugin are you using? First I tried it with version 2.5 and later with 2.4. I had no luck with that either so I didn't tried any older version. Thomas On 2010-02-25 12:05, Thomas Scheffler wrote: Hi, I have a multi module project with this layout Base |-- pom.xml |-- build-tools | |-- src | | `-- main | | `-- resources | | `-- org | | `-- project | | `-- checkstyle.xml | `-- pom.xml |-- parent |-- module1 |-- module2 `-- modulen Everything is like it is described in http://maven.apache.org/plugins/maven-checkstyle-plugin/examples/multi-module-config.html with one exception: The Base/pom.xml is not the parent module pom but Base/parent/pom.xml is. After following the guide above I can run mvn checkstyle:checkstyle fine on all modules and it uses the checkstyle.xml from the build-tools module. Just mvn site will not work with this error: [ERROR] BUILD ERROR [INFO] [INFO] Error during page generation Embedded error: Error rendering Maven report: Failed during checkstyle execution Could not find resource 'org/project/checkstyle.xml'. Why does it work with checkstyle:checkstyle and not with site? Thanks Thomas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Thomas Scheffler Friedrich-Schiller-Universität Jena Thüringer Universitäts- und Landesbibliothek Bibliotheksplatz 2 07743 Jena Phone: ++49 3641 940027 FAX: ++49 3641 940022 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
