Re: trouble adding Maven 2.0 pom
I got SVN installed locally and set up my POM to use its repository. Continuum can now get the files and build but I get an error about compiling with generics. I says use -source 5 or higher to enable generics but I don't know where to put -source 5 hmmm progress! :) ,chris On Nov 15, 2007 12:35 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote: 1. you need a real scm defined in your pom, Continuum use it to checkout/update the working copy and to build the project 2. if your scm is svn, svn must be in your PATH Emmanuel Christofer Jennings a écrit : I take it back. Continuum is not happy. Each build results in ... pre Provider message: The svn command failed. Command output: --- 'svn' is not recognized as an internal or external command, operable program or batch file. --- /pre So I guess I need a real SCM to run Continuum. ,chris On Nov 15, 2007 12:00 PM, Christofer Jennings [EMAIL PROTECTED] wrote: Thanks Emmanuel, Ah, the FAQ. But of course :) ... sorry for that. The app I'm trying continuum has no SCM. I know. Bad Idea. But it's just a little thing for messing around in. So, for what it's worth, I copied the SCM settings verbatim from here: http://maven.apache.org/pom.html#SCMand continuum is happy now. ,chris On Nov 15, 2007 11:44 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Christofer Jennings a écrit : Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7 pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. file protocol isn't allowed by default. Activation is explain in FAQs ( http://maven.apache.org/continuum/faqs.html) If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. You must add the scm part in your pom. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
[maven-eclipse-plugin] is workspaceCodeStylesURL still supported ?
I'v found some POMs that use maven-eclipse-plugin 2.5-SNAPSHOT with workspaceCodeStylesURL I can't find documentation of this attribute on http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html Is this still supported ?
Error in tutorial 'Using maven to develop jbi applications'
Hello, Because I'm new to Maven, Java, serviceMix etc, I'm doing the tutorial on http://servicemix.apache.org/2-beginner-using-maven-to-develop-jbi-applications.html. Someway or another I don't succeed in passing step 2.5. When I run the command 'mvn jbi:projectDeploymvn jbi:projectDeploy' it always ends with the error locmessageUnable to find suitable deployer for Service Unit 'tutorial-file-su'/loc-message in the service Mix console. I'm using ServiceMix 3.2 and maven 2.0.7. Can someone help me? Regards, Jan Reynaerts -- View this message in context: http://www.nabble.com/Error-in-tutorial-%27Using-maven-to-develop-jbi-applications%27-tf4810376s177.html#a13763351 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: [maven-eclipse-plugin] is workspaceCodeStylesURL still supported ?
Thanks for the info. Is there no support for same feature on a per-project basis ? 2007/11/15, Dan Tran [EMAIL PROTECTED]: it is in 2.5-SNAPSHOT and in the new configure-workspace's mojo. You will need to build the site your self to see the doc -D On Nov 14, 2007 11:53 PM, nicolas de loof [EMAIL PROTECTED] wrote: I'v found some POMs that use maven-eclipse-plugin 2.5-SNAPSHOT with workspaceCodeStylesURL I can't find documentation of this attribute on http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html Is this still supported ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Building Eclipse plugins with Maven 2
Yes, I confirm that it works. Thanks a lot 2007/11/14, eSonic [EMAIL PROTECTED]: Sebastien Arbogast wrote: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Internal error in the plugin manager executing goal 'org.apache.maven.plu gins:maven-psteclipse-plugin:1.1.0:testPackage': Unable to find the mojo 'org.ap ache.maven.plugins:maven-psteclipse-plugin:1.1.0:testPackage' in the plugin 'org .apache.maven.plugins:maven-psteclipse-plugin' org/codehaus/plexus/archiver/ArchiverException Hmm, I might have the step to help. Go to your local Maven repository, the directory where the psteclipse plugin stays (org/apache/maven/plugins/maven-psteclipse-plugin/version/), open the file with the .pom extension and add these: dependencies dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-archiver/artifactId version2.2/version /dependency /dependencies I might have been too optimistic when writing how to install the psteclipse plugin and I thinkg the automatic pom generation doesn't create these by default. Let me know if this works and I'll update the article. -- Michal -- View this message in context: http://www.nabble.com/Building-Eclipse-plugins-with-Maven-2-tf4675721s177.html#a13749166 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Sébastien Arbogast http://www.sebastien-arbogast.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Getting access to the versions in a POM
The mojo developer cookbook has part of this info. Feel free to add more...
http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook
Tom
On Nov 14, 2007 5:11 PM, Mark Russell [EMAIL PROTECTED] wrote:
Wayne:
Thanks That should get me started. I'll do some searching and then post back
any resources I find.
Wayne Fay wrote:
In your mojo, you'll need:
* @requiresDependencyResolution
* @requiresProject
And then:
/**
* iMaven Internal/i: Project to interact with.
*
* @parameter expression=${project}
* @required
* @readonly
*/
private MavenProject project;
Then you can navigate around in the MavenProject object to find the
dependencies and their versions etc. I assume this is on the web
somewhere but I'm not sure where, perhaps Wiki? Or Plugin Dev Center?
Wayne
On 11/14/07, Mark Russell [EMAIL PROTECTED] wrote:
I am writing an internal plugin for maven 2 for our company. One of the
things I need to do is to get access to the dependency
information that is configured in the pom. Is there a way to do that? I
have done several web searches but can not come up
with the correct string to get me an answer.
Please point me to a web page that will help me.
Thanks in advance :-
--
Mark Russell
Instantiations, Inc.
724-368-3331 (land line)
http://www.instantiations.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Mark Russell
Instantiations, Inc.
724-368-3331 (land line)
http://www.instantiations.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to control versioning across multiple POMs?
Do you use release plugin?
The release plugin should increment the version of the parent pom and the
pom itself for you.
If you mean this one:
http://maven.apache.org/plugins/maven-release-plugin/index.html
No. I had a hard time understanding what it actually does from the
docs and it seems like I would need commit access to all the
sub-projects (which I do not have).
If you have dependencies to sibling pom in your dependencies declaration,
I'd use version${project.version}/version to get around the problem that
the release tag won't increment the version back to snapshot.
What do you mean? Where would I specify this property? In the master
POM? Is this a special property in maven2?
I have a series of 3 POMs and I need to be able to control versioning
across them. They are arranged like so:
master POM (parent of) base POM (parent of) project POM
There is one master and one base POM but there are many many project
POMs, roughly 50+ currently with new ones being added
The master POM has a version (as it seems all children must specify
the version of the parent correctly in the parent tag). The base POM
has no version as it inherits from the master. The problem here is
that we want to upgrade the overall version... except that every
project POM specifies the version of either the master or base POM (in
the parent tag). It means we have to somehow coordinate among 50+
projects (which are controlled by various people/groups) and tell them
to all change the version of the parent.
This is not ideal at all and I suspect we are just doing something
dumb or completely wrong. So, how can we control the overall version
for all the projects without having to change all of the POMs?
You can view the source here if you like:
master: https://source.sakaiproject.org/svn/master/trunk/pom.xml
base: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml
sample project:
https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml
-AZ
--
Aaron Zeckoski ([EMAIL PROTECTED])
Senior Research Engineer - CARET - Cambridge University
[http://bugs.sakaiproject.org/confluence/display/~aaronz/]
Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
##
DISCLAIMER:
This email and any attachment may contain confidential information.
If you are not the intended recipient you are not authorized to copy
or disclose all or any part of it without the prior written consent
of Toyota.
Opinions expressed in this email and any attachments are those of the
sender and not necessarily the opinions of Toyota.
Please scan this email and any attachment(s) for viruses.
Toyota does not accept any responsibility for problems caused by
viruses, whether it is Toyota's fault or not.
##
--
Aaron Zeckoski ([EMAIL PROTECTED])
Senior Research Engineer - CARET - Cambridge University
[http://bugs.sakaiproject.org/confluence/display/~aaronz/]
Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] jaxws-maven-plugin vs. ant-task using wsgen
hi dan,
thx for your reply.
i currently use version 1.7.
but i'm not sure if i have the correct repository:
this one is from the jaxws example:
repository
idjava.net/id
urlhttps://maven-repository.dev.java.net/nonav/repository//url
layoutlegacy/layout
/repository
but i only found actual versions here, but they couldn't be resolved from
there
http://download.java.net/maven/2
maybe you have the correct url for the java.net repo for me?
according jaxws-api-2.1.1, i added this dependency:
dependency
groupIdjavax.xml.ws/groupId
artifactIdjaxws-api/artifactId
version2.1.1/version
/dependency
but couldn't find the release version 2.1.1 anywhere.
(only release version i could find was version 2.1)
adding jaxws-api 2.1 as dependency didn't help either, still getting the
same error.
thx 4 help
R.C.
Dan Tran wrote:
what version of jaxws-plugin do you use? Try the released version at
java.net
also, you must use jaxws-api-2.1.1
-D
On Nov 14, 2007 7:44 AM, Wayne Fay [EMAIL PROTECTED] wrote:
You should probably also post this request on the jaxws plugin
users/dev list. Since there is a lower chance that someone here is
using jaxws and will respond, but a very high chance that someone on
that list is using jaxws.
Wayne
On 11/14/07, CodingPlayer [EMAIL PROTECTED] wrote:
Hi There,
I'm an absolute noob to webservices, who is currently trying to compile
a
webservice annotated class, with the actual jaxws-maven-plugin.
i already lost 3 days, and still didn't find a way to get it running
properly.
to find the error i stepped back, and simply tried to get the wsgen
example
running:
https://jax-ws-commons.dev.java.net/source/browse/*checkout*/jax-ws-commons/trunk/jaxws-maven-plugin/src/it/wsgen/pom.xml?content-type=text%2Fplainrev=110
after removing the version (which points to a SNAPSHOT which can't be
downloaded) i have the following pom.xml:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdorg.codehaus.mojo.jaxws.it/groupId
artifactIdhelloworldws/artifactId
version1.0-SNAPSHOT/version
packagingwar/packaging
namehelloworld/name
dependencies
dependency
groupIdcom.sun.xml.ws/groupId
artifactIdjaxws-rt/artifactId
version2.1/version
/dependency
/dependencies
!-- temporary only until java.net maven2 repo is ready--
repositories
repository
idjava.net/id
urlhttps://maven-repository.dev.java.net/nonav/repository//url
layoutlegacy/layout
/repository
/repositories
build
finalName${artifactId}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
executions
execution
idcompile/id
goals
goalcompile/goal
/goals
phaseinitialize/phase
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
goals
goalwsgen/goal
/goals
phasegenerate-sources/phase
configuration
seiorg.codehaus.mojo.jaxws.it.HelloWorldImpl/sei
genWsdltrue/genWsdl !-- for demo purpose only,
the
wepapp does not need those the generated wsdl files--
keeptrue/keep
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.0.1/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
contextPath//contextPath
!--jettyEnvXml${basedir}/src/jetty-env.xml/jettyEnvXml--
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port9090/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
/plugin
/plugins
/build
/project
when running 'mvn install -X -e' from the command line i get the
following
error:
[DEBUG] jaxws:wsgen args: [-keep, -d,
C:\projects\jax-ws\target\classes,
-cp, C:\projects\jax-ws\target\classes;D:\data
Re: [M2] jaxws-maven-plugin vs. ant-task using wsgen
hi wayne,
thx for your hint.
just posted the thread at the users forum.
but since i couldn't find any users forum / mailing list (at java.net) i
decided to post it to the (old) codehaus mailinglist.
best regards
R.C.
Wayne Fay wrote:
You should probably also post this request on the jaxws plugin
users/dev list. Since there is a lower chance that someone here is
using jaxws and will respond, but a very high chance that someone on
that list is using jaxws.
Wayne
On 11/14/07, CodingPlayer [EMAIL PROTECTED] wrote:
Hi There,
I'm an absolute noob to webservices, who is currently trying to compile a
webservice annotated class, with the actual jaxws-maven-plugin.
i already lost 3 days, and still didn't find a way to get it running
properly.
to find the error i stepped back, and simply tried to get the wsgen
example
running:
https://jax-ws-commons.dev.java.net/source/browse/*checkout*/jax-ws-commons/trunk/jaxws-maven-plugin/src/it/wsgen/pom.xml?content-type=text%2Fplainrev=110
after removing the version (which points to a SNAPSHOT which can't be
downloaded) i have the following pom.xml:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdorg.codehaus.mojo.jaxws.it/groupId
artifactIdhelloworldws/artifactId
version1.0-SNAPSHOT/version
packagingwar/packaging
namehelloworld/name
dependencies
dependency
groupIdcom.sun.xml.ws/groupId
artifactIdjaxws-rt/artifactId
version2.1/version
/dependency
/dependencies
!-- temporary only until java.net maven2 repo is ready--
repositories
repository
idjava.net/id
urlhttps://maven-repository.dev.java.net/nonav/repository//url
layoutlegacy/layout
/repository
/repositories
build
finalName${artifactId}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
executions
execution
idcompile/id
goals
goalcompile/goal
/goals
phaseinitialize/phase
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
goals
goalwsgen/goal
/goals
phasegenerate-sources/phase
configuration
seiorg.codehaus.mojo.jaxws.it.HelloWorldImpl/sei
genWsdltrue/genWsdl !-- for demo purpose only, the
wepapp does not need those the generated wsdl files--
keeptrue/keep
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.0.1/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
contextPath//contextPath
!--jettyEnvXml${basedir}/src/jetty-env.xml/jettyEnvXml--
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port9090/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
/plugin
/plugins
/build
/project
when running 'mvn install -X -e' from the command line i get the
following
error:
[DEBUG] jaxws:wsgen args: [-keep, -d, C:\projects\jax-ws\target\classes,
-cp, C:\projects\jax-ws\target\classes;D:\data
Maven_repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;D:\data\Maven_repository\javax\xml\ws\jaxws-api\2.1\jaxws
api-2.1.jar;D:\data\Maven_repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;D:\data\Maven_repository\com\sun\xml\
essaging\saaj\saaj-impl\1.3\saaj-impl-1.3.jar;D:\data\Maven_repository\com\sun\xml\stream\buffer\streambuffer\0.4\strea
buffer-0.4.jar;D:\data\Maven_repository\com\sun\xml\stream\sjsxp\1.0\sjsxp-1.0.jar;D:\data\Maven_repository\com\sun\xml
bind\jaxb-impl\2.1.2\jaxb-impl-2.1.2.jar;D:\data\Maven_repository\com\sun\xml\ws\jaxws-rt\2.1\jaxws-rt-2.1.jar;D:\data\
aven_repository\javax\xml\stream\stax-api\1.0\stax-api-1.0.jar;D:\data\Maven_repository\javax\activation\activation\1.1
activation-1.1.jar;D:\data\Maven_repository\org\jvnet\staxex\stax-ex\1.0\stax-ex-1.0.jar,
-wsdl, -r, C:\projects\jax-ws
target\jaxws\wsgen\wsdl, org.codehaus.mojo.jaxws.it.HelloWorldImpl]
[INFO]
[ERROR] BUILD ERROR
[INFO]
Re: How to control versioning across multiple POMs?
Looking into your POMs, I think you should start using the release-plugin (is you aren't already). Your only problem is that the 'master'-POM doesn't know the 'base'-POM. (Seeing there's only 1 of both, why not merge them?). When you use the 'modules'-tag in Maven, the versions are normally updated by the release-plugin. So, I suggest you either add the 'base' as a module in the 'master', or add a version-tag to the 'base', which can then be easily released by Maven. In this last case however, you do need to update the version of the 'master' inside the 'base' manually. It's the same case we have here in my company, we have a company-wide master, which is not allowed to know all projects. If this POM gets updated, we must manually update out projects. However, we do not HAVE to do this, since some changes to the master might be irrelevant for some projects. Therefor we stick with this method and let projects decide whether or not to update. We do however send all employees a release-mail, so they at least know there's a new version. Updating is then discussed and decided within the projects. On Wednesday 14 November 2007 23:44, Aaron Zeckoski wrote: I have a series of 3 POMs and I need to be able to control versioning across them. They are arranged like so: master POM (parent of) base POM (parent of) project POM There is one master and one base POM but there are many many project POMs, roughly 50+ currently with new ones being added The master POM has a version (as it seems all children must specify the version of the parent correctly in the parent tag). The base POM has no version as it inherits from the master. The problem here is that we want to upgrade the overall version... except that every project POM specifies the version of either the master or base POM (in the parent tag). It means we have to somehow coordinate among 50+ projects (which are controlled by various people/groups) and tell them to all change the version of the parent. This is not ideal at all and I suspect we are just doing something dumb or completely wrong. So, how can we control the overall version for all the projects without having to change all of the POMs? You can view the source here if you like: master: https://source.sakaiproject.org/svn/master/trunk/pom.xml base: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml sample project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Mvn2
Ok, I understand now your point of view. It's link to the important reproducibility topic. One (common ?) way is to just use release version. Your proposition is more radical. So you have to don't use any snapshot pluginRepositroies and repositories (not just apache.snapshots). Rémy
Re: [maven-eclipse-plugin] is workspaceCodeStylesURL still supported ?
it is in 2.5-SNAPSHOT and in the new configure-workspace's mojo. You will need to build the site your self to see the doc -D On Nov 14, 2007 11:53 PM, nicolas de loof [EMAIL PROTECTED] wrote: I'v found some POMs that use maven-eclipse-plugin 2.5-SNAPSHOT with workspaceCodeStylesURL I can't find documentation of this attribute on http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html Is this still supported ? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2 way parent-module POM dependency required?
No, this is not a must... You can link either way if you want, but there's several things you have to consider: If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs have to know about each other. This seems to be what the docs indicate but I might misunderstand. Are we doing something dumb here? Sample parent here: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml Sample child here: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml Thanks for the help! -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2 way parent-module POM dependency required?
If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Yeah, we want to be able to build from either the parent (and build everything) or from the child (and just build the child) but we need the information in the parent when the child is being built. As a result, it looks like we are stuck with the 2-way dependency (at least according to what I could understand from the maven site and the maven book). In maven1 we created a plugin which would walk the source tree so that the parents did not have to know about the children. The nice thing about this is that you could drop a new project in the source tree and it would get picked up and built automatically. All the children only knew about one single master POM which provided them with a set of properties and shared dependencies. I think we are going to have to just be stuck with the tight coupling in maven 2 though. I would be happy to know I am wrong on this though so feel free to correct me. :-) -AZ Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs have to know about each other. This seems to be what the docs indicate but I might misunderstand. Are we doing something dumb here? Sample parent here: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml Sample child here: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml Thanks for the help! -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Aaron Zeckoski ([EMAIL PROTECTED]) Senior Research Engineer - CARET - Cambridge University [http://bugs.sakaiproject.org/confluence/display/~aaronz/] Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
Re: triggering profiles without using command line and without running the default profile?
We do need a way to have a default profile OR simply a way so that each project can be built using mvn clean install and still work without the base. I also wanted to have it able to run when the same property is set a certain way as well. In other words, if the property is set to core then the default profile should run and if no properties are set (mvn clean install) then the default profile should still run. For example: profile !-- default profile for sakai core -- idsakai/id activation activeByDefaulttrue/activeByDefault property namesakai.distribution/name valuecore/value /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module modulealias-tool/tool/module /modules /profile profile Is it possible to combine them and have come up with something like this? (probably not) activation property namesakai.distribution/name valuecore/value /property property name!sakai.distribution/name /property /activation I will experiment a bit and see what happens. Thanks! -AZ On Nov 15, 2007 10:51 AM, Roland Asmann [EMAIL PROTECTED] wrote: Do you need the default-profile? If not, remove the tag 'activateByDefault'. Or you can try setting it to run when your property is NOT set/a certain value is NOT set: property name!property/name /property or property nameproperty/name value!value/value /property On Wednesday 14 November 2007 23:29, Aaron Zeckoski wrote: Yes... I did that. This is not a newbie question (though I wish it were). The default profile is still running unless I do something like mvn install -Pkernel Here are the poms: Parent: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml (this sets a property) Project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml (this one has the default profile getting activated even though another profile is activated via a property) So, the question is, how do I get the same effect as running mvn install -Pkernel (which is to not run the default profile anymore and only run the profile that I wanted)? -AZ On Nov 14, 2007 5:40 PM, Roland Asmann [EMAIL PROTECTED] wrote: Check the profile-documentation and use the property-activation. On Wednesday 14 November 2007 18:02, Aaron Zeckoski wrote: I need to be able to trigger a specific profile WITHOUT executing the default profile AND without having to use the -P command line option. Ideally I want to trigger it using some setting in a POM file but any method where the user who is building the code can still type mvn clean build is fine. Can anyone help? Thanks -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Aaron Zeckoski ([EMAIL PROTECTED]) Senior Research Engineer - CARET - Cambridge University [http://bugs.sakaiproject.org/confluence/display/~aaronz/] Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
Re: use a particular timestamp of a SNAPSHOT
On Thu, 2007-11-15 at 08:43 +0100, nicolas de loof wrote: Hello, Can I configure a dependency to use a particular timestamp version of a SNAPSHOT ? For example, the 20070606.164150-5 of maven-surefire-plugin 2.3.1-SNAPSHOT Yes you can. You have to be careful though that this particular snapshot does not get purged away on the central repository, or else other developers might not be able to build your project after a while. -Olivier - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: 2 way parent-module POM dependency required?
How about re-writing the plugin to Maven2? Then you can at least remove the 'modules'-part in your base-POM... Otherwise I'm afraid you're indeed stuck with the 2-way dependency. On Thursday 15 November 2007 12:34, Aaron Zeckoski wrote: If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Yeah, we want to be able to build from either the parent (and build everything) or from the child (and just build the child) but we need the information in the parent when the child is being built. As a result, it looks like we are stuck with the 2-way dependency (at least according to what I could understand from the maven site and the maven book). In maven1 we created a plugin which would walk the source tree so that the parents did not have to know about the children. The nice thing about this is that you could drop a new project in the source tree and it would get picked up and built automatically. All the children only knew about one single master POM which provided them with a set of properties and shared dependencies. I think we are going to have to just be stuck with the tight coupling in maven 2 though. I would be happy to know I am wrong on this though so feel free to correct me. :-) -AZ Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs have to know about each other. This seems to be what the docs indicate but I might misunderstand. Are we doing something dumb here? Sample parent here: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml Sample child here: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml Thanks for the help! -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: triggering profiles without using command line and without running the default profile?
I'm afraid that combination will not work. Worst case scenario: you define two the same profiles, one that is activated when the property is not set, the other when it has the value 'core'. On Thursday 15 November 2007 12:13, Aaron Zeckoski wrote: We do need a way to have a default profile OR simply a way so that each project can be built using mvn clean install and still work without the base. I also wanted to have it able to run when the same property is set a certain way as well. In other words, if the property is set to core then the default profile should run and if no properties are set (mvn clean install) then the default profile should still run. For example: profile !-- default profile for sakai core -- idsakai/id activation activeByDefaulttrue/activeByDefault property namesakai.distribution/name valuecore/value /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module modulealias-tool/tool/module /modules /profile profile Is it possible to combine them and have come up with something like this? (probably not) activation property namesakai.distribution/name valuecore/value /property property name!sakai.distribution/name /property /activation I will experiment a bit and see what happens. Thanks! -AZ On Nov 15, 2007 10:51 AM, Roland Asmann [EMAIL PROTECTED] wrote: Do you need the default-profile? If not, remove the tag 'activateByDefault'. Or you can try setting it to run when your property is NOT set/a certain value is NOT set: property name!property/name /property or property nameproperty/name value!value/value /property On Wednesday 14 November 2007 23:29, Aaron Zeckoski wrote: Yes... I did that. This is not a newbie question (though I wish it were). The default profile is still running unless I do something like mvn install -Pkernel Here are the poms: Parent: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml (this sets a property) Project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml (this one has the default profile getting activated even though another profile is activated via a property) So, the question is, how do I get the same effect as running mvn install -Pkernel (which is to not run the default profile anymore and only run the profile that I wanted)? -AZ On Nov 14, 2007 5:40 PM, Roland Asmann [EMAIL PROTECTED] wrote: Check the profile-documentation and use the property-activation. On Wednesday 14 November 2007 18:02, Aaron Zeckoski wrote: I need to be able to trigger a specific profile WITHOUT executing the default profile AND without having to use the -P command line option. Ideally I want to trigger it using some setting in a POM file but any method where the user who is building the code can still type mvn clean build is fine. Can anyone help? Thanks -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: triggering profiles without using command line and without running the default profile?
OK, when I use this and run mvn clean install profiles profile !-- default profile for sakai core-- idsakai/id activation property name!sakai.distribution/name /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module modulealias-tool/tool/module /modules /profile profile !-- kernel (services + utils only) -- idkernel/id activation property namesakai.distribution/name valuekernel/value /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module /modules /profile ... I get the following error (see below). I am not confused about what the error is. That is perfectly clear. I AM confused about why it is happening. That tool bit is only defined in the top profile and the property IS set in the base POM (where the mvn is being run) to cause that NOT to run like so: properties sakai.distributionkernel/sakai.distribution /properties Any ideas? -AZ [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) 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: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.project.ProjectBuildingException: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1383) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:477) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:527) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:527) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more Caused by: java.io.FileNotFoundException: /opt/kernel/alias/alias-tool/tool/pom.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileReader.init(FileReader.java:55) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenProjectBuilder.java:1378) ... 18 more On Nov 15, 2007 10:51 AM, Roland Asmann [EMAIL PROTECTED] wrote: Do you need the default-profile? If not, remove the tag 'activateByDefault'. Or you can try setting it to run when your property is NOT set/a certain value is NOT set: property name!property/name /property or property nameproperty/name value!value/value /property On Wednesday 14 November 2007 23:29, Aaron Zeckoski wrote: Yes... I did that. This is not a newbie question (though I wish it were). The default profile is still running unless I do something like mvn install -Pkernel Here are the poms: Parent: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml (this sets a property) Project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml (this one has the default profile getting activated even though another profile is activated via a property) So, the question is, how do I get the same effect as running mvn install -Pkernel (which is to not run the default profile anymore and only run
Re: How to control versioning across multiple POMs?
Well, I read in one of your other messages that you don't have access to the other projects and therefor can't use the release-plugin... I'm afraid that means you're pretty much stuck with manually updating these versions. A possible work-around could be to write a Maven-plugin that updates all the versions... On Thursday 15 November 2007 12:28, Aaron Zeckoski wrote: Currently the master POM keeps track of things like properties and a large set of shared dependencies (among other things). The base POM mostly maintains the set of modules (this POM is swapped out depending on what kind of release we are doing). The project POMs are effectively standalone except that they need the properties and shared dependencies from the master POM. Do you still think we should put the base and master together (based on what I said above)? The key issue here is that the projects need to be able to evolve separately and we want to be able to create different kinds of releases. A full release which includes all the projects, a partial release which includes roughly half of the projects, and mini release which includes the minimum set of projects for the system to run. Ideally each release has a separate version number. Currently, we are handling the multiple types of releases with new base POMs but we have no way to handle the versioning. I am open to completely changing things around as long as we can get the multiple types of releases and can control the versions. What is the most maintainable way to handle this? Thanks! -AZ On Nov 15, 2007 10:58 AM, Roland Asmann [EMAIL PROTECTED] wrote: Looking into your POMs, I think you should start using the release-plugin (is you aren't already). Your only problem is that the 'master'-POM doesn't know the 'base'-POM. (Seeing there's only 1 of both, why not merge them?). When you use the 'modules'-tag in Maven, the versions are normally updated by the release-plugin. So, I suggest you either add the 'base' as a module in the 'master', or add a version-tag to the 'base', which can then be easily released by Maven. In this last case however, you do need to update the version of the 'master' inside the 'base' manually. It's the same case we have here in my company, we have a company-wide master, which is not allowed to know all projects. If this POM gets updated, we must manually update out projects. However, we do not HAVE to do this, since some changes to the master might be irrelevant for some projects. Therefor we stick with this method and let projects decide whether or not to update. We do however send all employees a release-mail, so they at least know there's a new version. Updating is then discussed and decided within the projects. On Wednesday 14 November 2007 23:44, Aaron Zeckoski wrote: I have a series of 3 POMs and I need to be able to control versioning across them. They are arranged like so: master POM (parent of) base POM (parent of) project POM There is one master and one base POM but there are many many project POMs, roughly 50+ currently with new ones being added The master POM has a version (as it seems all children must specify the version of the parent correctly in the parent tag). The base POM has no version as it inherits from the master. The problem here is that we want to upgrade the overall version... except that every project POM specifies the version of either the master or base POM (in the parent tag). It means we have to somehow coordinate among 50+ projects (which are controlled by various people/groups) and tell them to all change the version of the parent. This is not ideal at all and I suspect we are just doing something dumb or completely wrong. So, how can we control the overall version for all the projects without having to change all of the POMs? You can view the source here if you like: master: https://source.sakaiproject.org/svn/master/trunk/pom.xml base: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml sample project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail:
Re: 2 way parent-module POM dependency required?
On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote: True. One question though: why do you use the 'relativePath'-attribute? This shouldn't be really necessary, or am I missing something here? say you've just checked out a fresh project tree from svn - it's not yet been released to any remote repository, and you have a clean local repository. if you went to a sub-folder and tried mvn install it would complain about not finding the parent POM (because it's not the same as the containing .. POM) the relativePath attribute tells Maven where to find the POM if it can't find it in the local or remote repositories - note that if the parent is the same as the containing POM then you shouldn't need to use relativePath http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Example_2 HTH On Thursday 15 November 2007 14:35, Stuart McCulloch wrote: On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote: How about re-writing the plugin to Maven2? Then you can at least remove the 'modules'-part in your base-POM... Otherwise I'm afraid you're indeed stuck with the 2-way dependency. also note the parent doesn't have to be the same as the 'containing' POM (ie. the one with the modules) for example, some projects place settings like dependencyManagement, pluginManagement, etc. in a separate POM (say inside a 'poms' directory) and have all sub-projects use this as their parent, and have module POMs just to support building from the root, not for inheriting settings. ie: pom.xml (has modules: poms, A, B) \__ poms / pom.xml \__ A / pom.xml (has poms as parent, relativePath ../poms) \__ B / pom.xml (has poms as parent, relativePath ../poms) this can be really useful when you have various project types inside a single tree, because each sub-project can inherit settings from a different parent, and they won't disturb each other. the only tricky part is keeping the relativePath up-to-date, so that builds can work from any part of a check-out project tree... (I use my own plugin for this) On Thursday 15 November 2007 12:34, Aaron Zeckoski wrote: If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Yeah, we want to be able to build from either the parent (and build everything) or from the child (and just build the child) but we need the information in the parent when the child is being built. As a result, it looks like we are stuck with the 2-way dependency (at least according to what I could understand from the maven site and the maven book). In maven1 we created a plugin which would walk the source tree so that the parents did not have to know about the children. The nice thing about this is that you could drop a new project in the source tree and it would get picked up and built automatically. All the children only knew about one single master POM which provided them with a set of properties and shared dependencies. I think we are going to have to just be stuck with the tight coupling in maven 2 though. I would be happy to know I am wrong on this though so feel free to correct me. :-) -AZ Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs have to know about each other. This seems to be what the docs indicate but I might misunderstand. Are we doing something dumb here? Sample parent here: https://source.sakaiproject.org/contrib/caret/kernel/pom.xmlSample child here: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml Thanks for the help! -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.:
Re: 2 way parent-module POM dependency required?
True. One question though: why do you use the 'relativePath'-attribute? This shouldn't be really necessary, or am I missing something here? On Thursday 15 November 2007 14:35, Stuart McCulloch wrote: On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote: How about re-writing the plugin to Maven2? Then you can at least remove the 'modules'-part in your base-POM... Otherwise I'm afraid you're indeed stuck with the 2-way dependency. also note the parent doesn't have to be the same as the 'containing' POM (ie. the one with the modules) for example, some projects place settings like dependencyManagement, pluginManagement, etc. in a separate POM (say inside a 'poms' directory) and have all sub-projects use this as their parent, and have module POMs just to support building from the root, not for inheriting settings. ie: pom.xml (has modules: poms, A, B) \__ poms / pom.xml \__ A / pom.xml (has poms as parent, relativePath ../poms) \__ B / pom.xml (has poms as parent, relativePath ../poms) this can be really useful when you have various project types inside a single tree, because each sub-project can inherit settings from a different parent, and they won't disturb each other. the only tricky part is keeping the relativePath up-to-date, so that builds can work from any part of a check-out project tree... (I use my own plugin for this) On Thursday 15 November 2007 12:34, Aaron Zeckoski wrote: If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Yeah, we want to be able to build from either the parent (and build everything) or from the child (and just build the child) but we need the information in the parent when the child is being built. As a result, it looks like we are stuck with the 2-way dependency (at least according to what I could understand from the maven site and the maven book). In maven1 we created a plugin which would walk the source tree so that the parents did not have to know about the children. The nice thing about this is that you could drop a new project in the source tree and it would get picked up and built automatically. All the children only knew about one single master POM which provided them with a set of properties and shared dependencies. I think we are going to have to just be stuck with the tight coupling in maven 2 though. I would be happy to know I am wrong on this though so feel free to correct me. :-) -AZ Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs have to know about each other. This seems to be what the docs indicate but I might misunderstand. Are we doing something dumb here? Sample parent here: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml Sample child here: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml Thanks for the help! -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f,
Re: triggering profiles without using command line and without running the default profile?
Run 'mvn help:active-profiles' to see which profiles are activated. Seems like the property is not handed down or something... On Thursday 15 November 2007 14:18, Aaron Zeckoski wrote: OK, when I use this and run mvn clean install profiles profile !-- default profile for sakai core-- idsakai/id activation property name!sakai.distribution/name /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module modulealias-tool/tool/module /modules /profile profile !-- kernel (services + utils only) -- idkernel/id activation property namesakai.distribution/name valuekernel/value /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module /modules /profile ... I get the following error (see below). I am not confused about what the error is. That is perfectly clear. I AM confused about why it is happening. That tool bit is only defined in the top profile and the property IS set in the base POM (where the mvn is being run) to cause that NOT to run like so: properties sakai.distributionkernel/sakai.distribution /properties Any ideas? -AZ [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp l.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.project.ProjectBuildingException: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenP rojectBuilder.java:1383) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInte rnal(DefaultMavenProjectBuilder.java:477) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProje ctBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:527) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:527) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more Caused by: java.io.FileNotFoundException: /opt/kernel/alias/alias-tool/tool/pom.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileReader.init(FileReader.java:55) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMavenP rojectBuilder.java:1378) ... 18 more On Nov 15, 2007 10:51 AM, Roland Asmann [EMAIL PROTECTED] wrote: Do you need the default-profile? If not, remove the tag 'activateByDefault'. Or you can try setting it to run when your property is NOT set/a certain value is NOT set: property name!property/name /property or property nameproperty/name value!value/value /property On Wednesday 14 November 2007 23:29, Aaron Zeckoski wrote: Yes... I did that. This is not a newbie question (though I wish it were). The default profile is still running unless I do something like mvn install -Pkernel Here are the poms: Parent: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml (this sets a property) Project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml (this one has the default profile getting activated even though another
Re: triggering profiles without using command line and without running the default profile?
If this triggers the same exception, add the tool-project shortly, just to make sure you can run this command! On Thursday 15 November 2007 15:08, Roland Asmann wrote: Run 'mvn help:active-profiles' to see which profiles are activated. Seems like the property is not handed down or something... On Thursday 15 November 2007 14:18, Aaron Zeckoski wrote: OK, when I use this and run mvn clean install profiles profile !-- default profile for sakai core-- idsakai/id activation property name!sakai.distribution/name /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module modulealias-tool/tool/module /modules /profile profile !-- kernel (services + utils only) -- idkernel/id activation property namesakai.distribution/name valuekernel/value /property /activation modules modulealias-api/api/module modulealias-impl/impl/module modulealias-impl/pack/module /modules /profile ... I get the following error (see below). I am not confused about what the error is. That is perfectly clear. I AM confused about why it is happening. That tool bit is only defined in the top profile and the property IS set in the base POM (where the mvn is being run) to cause that NOT to run like so: properties sakai.distributionkernel/sakai.distribution /properties Any ideas? -AZ [INFO] Error building POM (may not be this project's POM). Project ID: unknown Reason: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown [INFO] [INFO] Trace org.apache.maven.reactor.MavenExecutionException: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:290) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125) at org.apache.maven.cli.MavenCli.main(MavenCli.java:280) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java :3 9) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorI mp l.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.project.ProjectBuildingException: Could not find the model file '/opt/kernel/alias/alias-tool/tool/pom.xml'. for project unknown at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMave nP rojectBuilder.java:1383) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileIn te rnal(DefaultMavenProjectBuilder.java:477) at org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenPro je ctBuilder.java:200) at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:553) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:467) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:527) at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:527) at org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:364) ... 11 more Caused by: java.io.FileNotFoundException: /opt/kernel/alias/alias-tool/tool/pom.xml (No such file or directory) at java.io.FileInputStream.open(Native Method) at java.io.FileInputStream.init(FileInputStream.java:106) at java.io.FileReader.init(FileReader.java:55) at org.apache.maven.project.DefaultMavenProjectBuilder.readModel(DefaultMave nP rojectBuilder.java:1378) ... 18 more On Nov 15, 2007 10:51 AM, Roland Asmann [EMAIL PROTECTED] wrote: Do you need the default-profile? If not, remove the tag 'activateByDefault'. Or you can try setting it to run when your property is NOT set/a certain value is NOT set: property name!property/name /property or property nameproperty/name value!value/value /property On Wednesday 14 November 2007 23:29, Aaron Zeckoski wrote: Yes... I did that. This is not a newbie question (though I wish it were). The default profile is still running unless I do something like mvn install -Pkernel Here are the poms:
Re: how to use profiles exclusively? (HELP!)
You activate the release-profile yourself by setting the property to the
expected value!
Remove the properties-tag from the profile and everything should work just
fine!
On Wednesday 14 November 2007 23:46, dev dev wrote:
I have defined 2 project profiles (below) and the goal is to be able
to run in exclusively in devel or release environment (and not both).
However, when i run mvn help:active-profiles, i got the below message.
It should be just release and NOT both (devel and release). What did
you do wrong, is this a bug in Maven2?
Active Profiles for Project
'com.mycompany.myproject:myproject-web:pom:1.0.0-SNAPSHOT':
The following profiles are active:
- devel (source: pom)
- release (source: pom)
+++
project
...
profile
idrelease/id
properties
environment.typerelease/environment.type
/properties
activation
property
nameenvironment.type/name
valuerelease/value
/property
/activation
/profile
profile
iddevel/id
activation
property
name!environment.type/name !--This profile
is activated when no ${environment.type} property is set. --
/property
/activation
/profile
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Roland Asmann
CFC Informationssysteme Entwicklungsgesellschaft m.b.H
Bäckerstrasse 1/2/7
A-1010 Wien
FN 266155f, Handelsgericht Wien
Tel.: +43/1/513 88 77 - 27
Fax.: +43/1/513 88 62
Email: [EMAIL PROTECTED]
Web: www.cfc.at
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to control versioning across multiple POMs?
Currently the master POM keeps track of things like properties and a large set of shared dependencies (among other things). The base POM mostly maintains the set of modules (this POM is swapped out depending on what kind of release we are doing). The project POMs are effectively standalone except that they need the properties and shared dependencies from the master POM. Do you still think we should put the base and master together (based on what I said above)? The key issue here is that the projects need to be able to evolve separately and we want to be able to create different kinds of releases. A full release which includes all the projects, a partial release which includes roughly half of the projects, and mini release which includes the minimum set of projects for the system to run. Ideally each release has a separate version number. Currently, we are handling the multiple types of releases with new base POMs but we have no way to handle the versioning. I am open to completely changing things around as long as we can get the multiple types of releases and can control the versions. What is the most maintainable way to handle this? Thanks! -AZ On Nov 15, 2007 10:58 AM, Roland Asmann [EMAIL PROTECTED] wrote: Looking into your POMs, I think you should start using the release-plugin (is you aren't already). Your only problem is that the 'master'-POM doesn't know the 'base'-POM. (Seeing there's only 1 of both, why not merge them?). When you use the 'modules'-tag in Maven, the versions are normally updated by the release-plugin. So, I suggest you either add the 'base' as a module in the 'master', or add a version-tag to the 'base', which can then be easily released by Maven. In this last case however, you do need to update the version of the 'master' inside the 'base' manually. It's the same case we have here in my company, we have a company-wide master, which is not allowed to know all projects. If this POM gets updated, we must manually update out projects. However, we do not HAVE to do this, since some changes to the master might be irrelevant for some projects. Therefor we stick with this method and let projects decide whether or not to update. We do however send all employees a release-mail, so they at least know there's a new version. Updating is then discussed and decided within the projects. On Wednesday 14 November 2007 23:44, Aaron Zeckoski wrote: I have a series of 3 POMs and I need to be able to control versioning across them. They are arranged like so: master POM (parent of) base POM (parent of) project POM There is one master and one base POM but there are many many project POMs, roughly 50+ currently with new ones being added The master POM has a version (as it seems all children must specify the version of the parent correctly in the parent tag). The base POM has no version as it inherits from the master. The problem here is that we want to upgrade the overall version... except that every project POM specifies the version of either the master or base POM (in the parent tag). It means we have to somehow coordinate among 50+ projects (which are controlled by various people/groups) and tell them to all change the version of the parent. This is not ideal at all and I suspect we are just doing something dumb or completely wrong. So, how can we control the overall version for all the projects without having to change all of the POMs? You can view the source here if you like: master: https://source.sakaiproject.org/svn/master/trunk/pom.xml base: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml sample project: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Aaron Zeckoski ([EMAIL PROTECTED]) Senior Research Engineer - CARET - Cambridge University [http://bugs.sakaiproject.org/confluence/display/~aaronz/] Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
Re: Is http://mirrors.ibiblio.org/pub/mirrors/maven2 down?
The ibiblio mirror is not run by the Maven team. You'd have to contact the folks at ibiblio if you want to know when they will be fixing it. Kohsuke Kawaguchi wrote: The central repository http://repo1.maven.org/maven2/ appears to be up, but the ibiblio mirror seems to be down since this morning. Is the maven team aware of the issue? Is this going to be fixed some time soon? -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Error in tutorial 'Using maven to develop jbi applications'
You should post this question on the ServiceMix Users list, since they are the authors of that tutorial as well as the plugin you're attempting to use. Wayne On 11/15/07, JanReynaerts [EMAIL PROTECTED] wrote: Hello, Because I'm new to Maven, Java, serviceMix etc, I'm doing the tutorial on http://servicemix.apache.org/2-beginner-using-maven-to-develop-jbi-applications.html. Someway or another I don't succeed in passing step 2.5. When I run the command 'mvn jbi:projectDeploymvn jbi:projectDeploy' it always ends with the error locmessageUnable to find suitable deployer for Service Unit 'tutorial-file-su'/loc-message in the service Mix console. I'm using ServiceMix 3.2 and maven 2.0.7. Can someone help me? Regards, Jan Reynaerts -- View this message in context: http://www.nabble.com/Error-in-tutorial-%27Using-maven-to-develop-jbi-applications%27-tf4810376s177.html#a13763351 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: Two jars, one pom...
2007/11/13, Hirn, Joseph [EMAIL PROTECTED]: If there is a third way I would appreciate the recommendation. I also would like to hear thoughts on my two approaches and if anyone has had to deal with separating out things in this manner. Possibly the solution could be to separate these jars into atomic modules (i.e. that they do not need to be separated anymore) and then aggregating them in an all jar using the assembly plugin: http://maven.apache.org/plugins/maven-assembly-plugin/ This is in some way how Spring 2 is packaged: they provide modular jars for Maven, but they also provide a spring-all jar containing all the Spring. Ciao Antonio - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven's included with Leopard (Mac OS 10.5)
Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Nov 15, 2007, at 9:53 AM, Lally Singh wrote: Just fyi: [EMAIL PROTECTED] ~]$ uname -a Darwin hc65210f0.dhcp.vt.edu 9.0.0 Darwin Kernel Version 9.0.0: Tue Oct 9 21:35:55 PDT 2007; root:xnu-1228~1/RELEASE_I386 i386 [EMAIL PROTECTED] ~]$ which mvn /usr/bin/mvn [EMAIL PROTECTED] ~]$ mvn --version Maven version: 2.0.6 [EMAIL PROTECTED] ~]$ I only noticed this when I upgraded and noticed my build failing (I needed 2.0.7 :-) ). Congrats! -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - 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: Two jars, one pom...
We have a similar situation where we build a jar that goes into a rar file but we need a client jar as well. We build one of the files with an ant task (after maven has done all the compiling and such) and use the build-helper plugin to add the extra resulting artifact file to the list of things to install and deploy. Works like a charm. It's similar to the situation where the ejb plugin generates an ejb jar and a client jar too. The difference is that the ejb plugin adds its own support for having two artifacts as a result. -- Lee On Nov 13, 2007 4:47 PM, Hirn, Joseph [EMAIL PROTECTED] wrote: I am helping someone implement Maven in their project and looking for the best way to go about generating two jars from the same source base. They did this previously via two ant targets. Please note we are retrofitting this codebase to Maven so it was not originally structured with Maven's project structure in mind. The option to break up the project into two separate projects seems like the ideal way. They need an ALL jar and a client jar for distribution. From what was explained, it might need to be three components where there are server, client, and shared code. This would result in three POMS and three jars which does not simplify distribution as they would like a single ALL jar rather than having three separate artifacts. The other option would be to have a separate profile which compiles the client jar but that doesn't seem mavenish, and I'm not 1000% sure it can be supported . If there is a third way I would appreciate the recommendation. I also would like to hear thoughts on my two approaches and if anyone has had to deal with separating out things in this manner. Thanks so much. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- -- Lee Meador Sent from gmail. My real email address is lee AT leemeador.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: maven jetty plugin
Thanks, but is that possible using the Mavenide? I'd like to be able to easy run jetty with or without debug, the control being in a profile. TIA John -Original Message- From: Hugo Palma [mailto:[EMAIL PROTECTED] Sent: 14 November 2007 17:27 To: Maven Users List Subject: Re: maven jetty plugin Just provide those parameters to the maven JVM and jetty will use them. I usually just set the env variable MAVEN_OPTS with: MAVEN_OPTS=-Xdebug -Xrunjdwp:transport=dt_socket,server=y,suspend=n,address=5005 and then just run: mvn jetty:run John Coleman wrote: Hi, How do I run the jetty goal with jetty configured with a debug socket? I need to pass -Xdebug and other properties to jetty. TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - 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 - pluginManagement - best practices?
If you run your build with the -X option and redirect the output to a file, you can search through it for plugin and get a list of the plugins you use along with the current versions it is using. I use this as a start in building the pluginManagement section. Then you have to do a little research to find out if these versions are the ones you want. I have not found a good way to do that. I start by looking on the maven web site at the list of plugins. This page will list many of the current release versions. Then I search through the mailing list to find any complaints about those plugin versions. (There is a lot of clutter/static doing it this way.) If the complaint is justified and I find it to be relevant to my build, I might back off a version on that plugin and, of course, repeat the research. I suspect there is some way to use the list of Jira issues to help with this process. Does anyone have some ideas here for how to find out the best plugin version to use. Additionally, this means that as your project progresses you may need to move to new plugin versions. This comes into play, particularly, if you add some features to your application that require adding features to your build and you find you run up against a bug in a plugin. You can get problems like one I have now. I have to comment out my proxy entry in settings.xml when I am deploying my site (via SCP) because it always uses the proxy and I am SCPing it to a non-proxy location. Then I have to put the proxy back in settings.xml when I build with the dashboard plugin because that plugin comes from the codehaus snapshot repo which I don't don't include in things managed by Proximity. Now, this is a minor problem effecting only the building and deploying of the site. Its not really part of building the application and it doesn't happen on my build server (trust me, I don't want to explain it). But the same sort of stuff can pop up as relates to your build now and then. You can sometimes get rid of the problem by backing off the plugin versions. Thanks. -- Lee On Nov 14, 2007 10:12 PM, Kalle Korhonen [EMAIL PROTECTED] wrote: Parent poms with versions set in their pluginManagement section makes absolute sense. Of course no list is complete, and it needs to be maintained, but in most cases you are better off using an old version of a plugin than using an unknown latest version. Here's what I have in one parent pom: pluginManagement plugins plugin artifactIdmaven-antrun-plugin/artifactId version1.1/version dependencies dependency groupIdant/groupId artifactIdant-nodeps/artifactId version1.6.5/version /dependency dependency groupIdant/groupId artifactIdant-optional/artifactId version1.5.3-1/version /dependency dependency groupIdant-contrib/groupId artifactIdant-contrib/artifactId version1.0b2/version /dependency /dependencies /plugin plugin artifactIdmaven-assembly-plugin/artifactId version2.2-beta-1/version /plugin plugin artifactIdmaven-clean-plugin/artifactId version2.1/version /plugin plugin artifactIdmaven-checkstyle-plugin/artifactId version2.1/version /plugin plugin artifactIdmaven-compiler-plugin/artifactId version2.0.1/version /plugin plugin artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin plugin artifactIdmaven-deploy-plugin/artifactId version2.3/version /plugin plugin artifactIdmaven-install-plugin/artifactId version2.1/version /plugin plugin artifactIdmaven-jar-plugin/artifactId version2.1/version /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.0/version /plugin plugin artifactIdmaven-release-plugin/artifactId version2.0-beta-7/version /plugin plugin
Maven's included with Leopard (Mac OS 10.5)
Just fyi: [EMAIL PROTECTED] ~]$ uname -a Darwin hc65210f0.dhcp.vt.edu 9.0.0 Darwin Kernel Version 9.0.0: Tue Oct 9 21:35:55 PDT 2007; root:xnu-1228~1/RELEASE_I386 i386 [EMAIL PROTECTED] ~]$ which mvn /usr/bin/mvn [EMAIL PROTECTED] ~]$ mvn --version Maven version: 2.0.6 [EMAIL PROTECTED] ~]$ I only noticed this when I upgraded and noticed my build failing (I needed 2.0.7 :-) ). Congrats! -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2 tomcat plugin fatal error java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64
That is very odd, considering the plugin declares a dependency on commons-codec v1.3. Can you show us the rest of your pom? Are you using commons-codec yourself, perhaps a different version? Wayne On 11/15/07, Jimbog [EMAIL PROTECTED] wrote: Hi, I am trying to use the tomcat plugin to do a mvn tomcat:deploy, and get the below stack trace.. I notice this was rased a bug against version 1.0-20061203.210544-5. http://jira.codehaus.org/browse/MOJO-812 But has been marked as fixed in 1.0-alpha-1, I am using 1.0-alpha-1, and still get it. Does anyone have a work around for this? [ERROR] FATAL ERROR [INFO] [INFO] org/apache/commons/codec/binary/Base64 [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 at org.codehaus.mojo.tomcat.TomcatManager.toAuthorization(TomcatManager. java:699) at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:610) at org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java: 680) at org.codehaus.mojo.tomcat.TomcatManager.deploy(TomcatManager.java:302) at org.codehaus.mojo.tomcat.DeployMojo.deployWar(DeployMojo.java:84) at org.codehaus.mojo.tomcat.AbstractDeployMojo.invokeManager(AbstractDep loyMojo.java:83) at org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalin aMojo.java:132) at org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarC atalinaMojo.java:59) -- View this message in context: http://www.nabble.com/Maven-2-tomcat-plugin-fatal-error-java.lang.NoClassDefFoundError%3A-org-apache-commons-codec-binary-Base64-tf4814577s177.html#a13773524 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: Maven's included with Leopard (Mac OS 10.5)
symlink usr/share/maven to whichever install you want to use. On Nov 15, 2007 5:00 PM, Ryan Scott [EMAIL PROTECTED] wrote: Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Nov 15, 2007, at 9:53 AM, Lally Singh wrote: Just fyi: [EMAIL PROTECTED] ~]$ uname -a Darwin hc65210f0.dhcp.vt.edu 9.0.0 Darwin Kernel Version 9.0.0: Tue Oct 9 21:35:55 PDT 2007; root:xnu-1228~1/RELEASE_I386 i386 [EMAIL PROTECTED] ~]$ which mvn /usr/bin/mvn [EMAIL PROTECTED] ~]$ mvn --version Maven version: 2.0.6 [EMAIL PROTECTED] ~]$ I only noticed this when I upgraded and noticed my build failing (I needed 2.0.7 :-) ). Congrats! -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - 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]
Maven 2 tomcat plugin fatal error java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64
Hi, I am trying to use the tomcat plugin to do a mvn tomcat:deploy, and get the below stack trace.. I notice this was rased a bug against version 1.0-20061203.210544-5. http://jira.codehaus.org/browse/MOJO-812 But has been marked as fixed in 1.0-alpha-1, I am using 1.0-alpha-1, and still get it. Does anyone have a work around for this? [ERROR] FATAL ERROR [INFO] [INFO] org/apache/commons/codec/binary/Base64 [INFO] [INFO] Trace java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64 at org.codehaus.mojo.tomcat.TomcatManager.toAuthorization(TomcatManager. java:699) at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:610) at org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java: 680) at org.codehaus.mojo.tomcat.TomcatManager.deploy(TomcatManager.java:302) at org.codehaus.mojo.tomcat.DeployMojo.deployWar(DeployMojo.java:84) at org.codehaus.mojo.tomcat.AbstractDeployMojo.invokeManager(AbstractDep loyMojo.java:83) at org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalin aMojo.java:132) at org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarC atalinaMojo.java:59) -- View this message in context: http://www.nabble.com/Maven-2-tomcat-plugin-fatal-error-java.lang.NoClassDefFoundError%3A-org-apache-commons-codec-binary-Base64-tf4814577s177.html#a13773524 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Cant the release plugin to tag only modules?
Currently one of my projects looks like `-- parent |-- module1 |-- module2 `-- module3 When I mvn release:prepare I get in svn `-- tags `-- parent-1.0.0 |-- module1 |-- module2 `-- module3 But I want `-- tags |-- module1-1.0.0 |-- module2-1.0.0 `-- module3-1.0.0 Or at best `-- tags |-- parent-1.0.0 |-- module1-1.0.0 |-- module2-1.0.0 `-- module3-1.0.0 Can this be done without releasing every module individually? Thank - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven's included with Leopard (Mac OS 10.5)
Can't you just set MVN_HOME to what you want and put your maven 2.0.7 in, say, /opt/maven? I am not running Leopard on my dev machine, only on my play machine. I've noticed some slowness launching some Java apps, but nothing else. I've heard there are more problems. -K On Nov 15, 2007, at 12:53 PM, Ryan Scott wrote: I have tried many things but i keep getting patch updates from Apple that overwrites my changes. It is not really unix if you can't run any version of Java you want lol. Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Nov 15, 2007, at 10:02 AM, Graham Leggett wrote: On Thu, November 15, 2007 7:00 pm, Ryan Scott wrote: Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? What's wrong with putting v2.0.7 ahead of v2.0.6 on the PATH? Leopard is a unix machine, after all. Regards, Graham -- - 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: Maven 2 tomcat plugin fatal error java.lang.NoClassDefFoundError: org/apache/commons/codec/binary/Base64
I extracted pom.xml from the jar file and renamed it to tomcat-maven-plugin-1.0-alpha-1.pom and put this file in .m2\repository\org\codehaus\mojo\tomcat-maven-plugin\1.0-alpha-1. That fixed that problem. I now get [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Java heap space [INFO] [INFO] Trace java.lang.OutOfMemoryError: Java heap space at java.io.ByteArrayOutputStream.write(ByteArrayOutputStream.java:95) at sun.net.www.http.PosterOutputStream.write(PosterOutputStream.java:61) at java.io.BufferedOutputStream.flushBuffer(BufferedOutputStream.java:65 ) Ive given more memory to tomcat and maven. It deploys the tomcat samle.war fine, but the webapp im trying to deploy is 20MB because maven adds add the dependency jars despite them having provided scope. Can Maven run the Tomcat manager tasks? Hot deploying wars using ant takes a few mins to set up. -- View this message in context: http://www.nabble.com/Maven-2-tomcat-plugin-fatal-error-java.lang.NoClassDefFoundError%3A-org-apache-commons-codec-binary-Base64-tf4814577s177.html#a13778444 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
trouble adding Maven 2.0 pom
Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7 pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
Re: trouble adding Maven 2.0 pom
Christofer Jennings a écrit : Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7 pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. file protocol isn't allowed by default. Activation is explain in FAQs (http://maven.apache.org/continuum/faqs.html) If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. You must add the scm part in your pom. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
Re: Maven/Hibernate error / anyone has find similar?
Hello, mm not really :) found out that i had a clash between followign dependencies - hibernate 3.2.x - asm-all -cglib - spring ? i am trying to move my project from ant to maven, and we are using hibernate spring, cglib and asm libraries when i downloaded them from web, i got error, when instead i pointed to version installed on my local machine (teh one i m using with ant) everythign worked fine i'll need toinvestigate more as this may cause us problems if we update any versions of spring or hibernate i'll report back here my findings once i proceed with my investigation regards marco On Nov 14, 2007 9:04 PM, Wayne Fay [EMAIL PROTECTED] wrote: Take a look at your applicationContext.xml file, apparently you have an issue with how you've defined your sessionFactory bean (??). org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError Caused by: java.lang.NoClassDefFoundError at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:107) Wayne On 11/14/07, Marco Mistroni [EMAIL PROTECTED] wrote: hi all, i am trying to port an app from ant to maven , but it looks like i am having troubles iwth dependencies. has anyone ever found the error below? i attach my dependencies at the end of message, hope someone can sort me out Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.39 sec FAILURE! testGetBSDRBondIdsReturnsBondIds(com.bnpparibas.risk.collateralrisk.dao.IssueDaoIntegrationTest) Time elapsed: 0.359 sec ERROR! org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError Caused by: java.lang.NoClassDefFoundError at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIBLazyInitializer.java:107) at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBProxyFactory.java:43) - 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]
Maven Release Plugin Question
Can the maven release plugin deploy the war file to external application service/Tomcat after it is finished. The extra goals are added to the goal configuration parameter on the sub-module pom.xml, but the release plugin does not seem to be call the extra goals configured in the module's pom.xml. Ravi -- View this message in context: http://www.nabble.com/Maven-Release-Plugin-Question-tf4816868s177.html#a13780801 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: [M2] jaxws-maven-plugin vs. ant-task using wsgen
jaxws-api 2.2-1 is at
http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1-1/
the plugin is at http://download.java.net/maven/2
The rest of required artifacts are at the java.net maven.1 legacy repo
http://download.java.net/maven/1
So you need 2 maven2 repos and 1 maven repo to get it to work :-)
-D
On Nov 15, 2007 2:14 AM, CodingPlayer [EMAIL PROTECTED] wrote:
hi wayne,
thx for your hint.
just posted the thread at the users forum.
but since i couldn't find any users forum / mailing list (at java.net)
https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/mail-lists.html
i decided to post it to the (old) codehaus mailinglist.
http://mojo.codehaus.org/jaxws-maven-plugin/mail-lists.html
best regards
R.C.
Wayne Fay wrote:
You should probably also post this request on the jaxws plugin
users/dev list. Since there is a lower chance that someone here is
using jaxws and will respond, but a very high chance that someone on
that list is using jaxws.
Wayne
On 11/14/07, CodingPlayer [EMAIL PROTECTED] wrote:
Hi There,
I'm an absolute noob to webservices, who is currently trying to compile a
webservice annotated class, with the actual jaxws-maven-plugin.
i already lost 3 days, and still didn't find a way to get it running
properly.
to find the error i stepped back, and simply tried to get the wsgen
example
running:
https://jax-ws-commons.dev.java.net/source/browse/*checkout*/jax-ws-commons/trunk/jaxws-maven-plugin/src/it/wsgen/pom.xml?content-type=text%2Fplainrev=110
after removing the version (which points to a SNAPSHOT which can't be
downloaded) i have the following pom.xml:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdorg.codehaus.mojo.jaxws.it/groupId
artifactIdhelloworldws/artifactId
version1.0-SNAPSHOT/version
packagingwar/packaging
namehelloworld/name
dependencies
dependency
groupIdcom.sun.xml.ws/groupId
artifactIdjaxws-rt/artifactId
version2.1/version
/dependency
/dependencies
!-- temporary only until java.net maven2 repo is ready--
repositories
repository
idjava.net/id
urlhttps://maven-repository.dev.java.net/nonav/repository//url
layoutlegacy/layout
/repository
/repositories
build
finalName${artifactId}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
executions
execution
idcompile/id
goals
goalcompile/goal
/goals
phaseinitialize/phase
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
goals
goalwsgen/goal
/goals
phasegenerate-sources/phase
configuration
seiorg.codehaus.mojo.jaxws.it.HelloWorldImpl/sei
genWsdltrue/genWsdl !-- for demo purpose only, the
wepapp does not need those the generated wsdl files--
keeptrue/keep
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.0.1/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
contextPath//contextPath
!--jettyEnvXml${basedir}/src/jetty-env.xml/jettyEnvXml--
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port9090/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
/plugin
/plugins
/build
/project
when running 'mvn install -X -e' from the command line i get the
following
error:
[DEBUG] jaxws:wsgen args: [-keep, -d, C:\projects\jax-ws\target\classes,
-cp, C:\projects\jax-ws\target\classes;D:\data
Maven_repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;D:\data\Maven_repository\javax\xml\ws\jaxws-api\2.1\jaxws
api-2.1.jar;D:\data\Maven_repository\javax\xml\soap\saaj-api\1.3\saaj-api-1.3.jar;D:\data\Maven_repository\com\sun\xml\
essaging\saaj\saaj-impl\1.3\saaj-impl-1.3.jar;D:\data\Maven_repository\com\sun\xml\stream\buffer\streambuffer\0.4\strea
Re: trouble adding Maven 2.0 pom
I take it back. Continuum is not happy. Each build results in ... pre Provider message: The svn command failed. Command output: --- 'svn' is not recognized as an internal or external command, operable program or batch file. --- /pre So I guess I need a real SCM to run Continuum. ,chris On Nov 15, 2007 12:00 PM, Christofer Jennings [EMAIL PROTECTED] wrote: Thanks Emmanuel, Ah, the FAQ. But of course :) ... sorry for that. The app I'm trying continuum has no SCM. I know. Bad Idea. But it's just a little thing for messing around in. So, for what it's worth, I copied the SCM settings verbatim from here: http://maven.apache.org/pom.html#SCMand continuum is happy now. ,chris On Nov 15, 2007 11:44 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Christofer Jennings a écrit : Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7 pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. file protocol isn't allowed by default. Activation is explain in FAQs ( http://maven.apache.org/continuum/faqs.html) If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. You must add the scm part in your pom. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
Re: Maven's included with Leopard (Mac OS 10.5)
On 11/15/07, Graham Leggett [EMAIL PROTECTED] wrote: On Thu, November 15, 2007 7:00 pm, Ryan Scott wrote: Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? What's wrong with putting v2.0.7 ahead of v2.0.6 on the PATH? Leopard is a unix machine, after all. Seriously. That's all I do. Latest maven, etc go in /usr/local/dist. Then links to /usr/local/dist/maven-2.0.7/bin/* go in /usr/local/bin. In my ~/.bashrc: export PATH=/usr/local/bin:$PATH This works perfectly fine, never gets hit by an Apple update. -- H. Lally Singh Ph.D. Candidate, Computer Science Virginia Tech - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven's included with Leopard (Mac OS 10.5)
I have tried many things but i keep getting patch updates from Apple that overwrites my changes. It is not really unix if you can't run any version of Java you want lol. Scott Ryan CTO Soaring Eagle L.L.C. Denver, Co. 80129 www.soaringeagleco.com www.theryansplace.com (303) 263-3044 [EMAIL PROTECTED] On Nov 15, 2007, at 10:02 AM, Graham Leggett wrote: On Thu, November 15, 2007 7:00 pm, Ryan Scott wrote: Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? What's wrong with putting v2.0.7 ahead of v2.0.6 on the PATH? Leopard is a unix machine, after all. Regards, Graham -- - 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] jaxws-maven-plugin vs. ant-task using wsgen
Wow, that is really painful...
Wayne
On 11/15/07, Dan Tran [EMAIL PROTECTED] wrote:
jaxws-api 2.2-1 is at
http://repo1.maven.org/maven2/javax/xml/ws/jaxws-api/2.1-1/
the plugin is at http://download.java.net/maven/2
The rest of required artifacts are at the java.net maven.1 legacy repo
http://download.java.net/maven/1
So you need 2 maven2 repos and 1 maven repo to get it to work :-)
-D
On Nov 15, 2007 2:14 AM, CodingPlayer [EMAIL PROTECTED] wrote:
hi wayne,
thx for your hint.
just posted the thread at the users forum.
but since i couldn't find any users forum / mailing list (at java.net)
https://jax-ws-commons.dev.java.net/jaxws-maven-plugin/mail-lists.html
i decided to post it to the (old) codehaus mailinglist.
http://mojo.codehaus.org/jaxws-maven-plugin/mail-lists.html
best regards
R.C.
Wayne Fay wrote:
You should probably also post this request on the jaxws plugin
users/dev list. Since there is a lower chance that someone here is
using jaxws and will respond, but a very high chance that someone on
that list is using jaxws.
Wayne
On 11/14/07, CodingPlayer [EMAIL PROTECTED] wrote:
Hi There,
I'm an absolute noob to webservices, who is currently trying to compile a
webservice annotated class, with the actual jaxws-maven-plugin.
i already lost 3 days, and still didn't find a way to get it running
properly.
to find the error i stepped back, and simply tried to get the wsgen
example
running:
https://jax-ws-commons.dev.java.net/source/browse/*checkout*/jax-ws-commons/trunk/jaxws-maven-plugin/src/it/wsgen/pom.xml?content-type=text%2Fplainrev=110
after removing the version (which points to a SNAPSHOT which can't be
downloaded) i have the following pom.xml:
?xml version=1.0 encoding=UTF-8 ?
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
groupIdorg.codehaus.mojo.jaxws.it/groupId
artifactIdhelloworldws/artifactId
version1.0-SNAPSHOT/version
packagingwar/packaging
namehelloworld/name
dependencies
dependency
groupIdcom.sun.xml.ws/groupId
artifactIdjaxws-rt/artifactId
version2.1/version
/dependency
/dependencies
!-- temporary only until java.net maven2 repo is ready--
repositories
repository
idjava.net/id
urlhttps://maven-repository.dev.java.net/nonav/repository//url
layoutlegacy/layout
/repository
/repositories
build
finalName${artifactId}/finalName
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-compiler-plugin/artifactId
configuration
source1.5/source
target1.5/target
/configuration
executions
execution
idcompile/id
goals
goalcompile/goal
/goals
phaseinitialize/phase
/execution
/executions
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
goals
goalwsgen/goal
/goals
phasegenerate-sources/phase
configuration
seiorg.codehaus.mojo.jaxws.it.HelloWorldImpl/sei
genWsdltrue/genWsdl !-- for demo purpose only, the
wepapp does not need those the generated wsdl files--
keeptrue/keep
/configuration
/execution
/executions
/plugin
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdmaven-jetty-plugin/artifactId
version6.0.1/version
configuration
scanIntervalSeconds10/scanIntervalSeconds
contextPath//contextPath
!--jettyEnvXml${basedir}/src/jetty-env.xml/jettyEnvXml--
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port9090/port
maxIdleTime6/maxIdleTime
/connector
/connectors
/configuration
/plugin
/plugins
/build
/project
when running 'mvn install -X -e' from the command line i get the
following
error:
[DEBUG] jaxws:wsgen args: [-keep, -d, C:\projects\jax-ws\target\classes,
-cp, C:\projects\jax-ws\target\classes;D:\data
Maven_repository\javax\xml\bind\jaxb-api\2.1\jaxb-api-2.1.jar;D:\data\Maven_repository\javax\xml\ws\jaxws-api\2.1\jaxws
Re: trouble adding Maven 2.0 pom
Thanks Emmanuel, Ah, the FAQ. But of course :) ... sorry for that. The app I'm trying continuum has no SCM. I know. Bad Idea. But it's just a little thing for messing around in. So, for what it's worth, I copied the SCM settings verbatim from here: http://maven.apache.org/pom.html#SCMand continuum is happy now. ,chris On Nov 15, 2007 11:44 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Christofer Jennings a écrit : Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. file protocol isn't allowed by default. Activation is explain in FAQs ( http://maven.apache.org/continuum/faqs.html) If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. You must add the scm part in your pom. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
Re: trouble adding Maven 2.0 pom
Continuum may not know where or see your svn command line client binaries. Make sure the system path has directory location of your svn executable in the path. Johnathan On Thu, Nov 15, 2007 at 2:06 PM, in message [EMAIL PROTECTED], Christofer Jennings [EMAIL PROTECTED] wrote: I take it back. Continuum is not happy. Each build results in ... pre Provider message: The svn command failed. Command output: --- 'svn' is not recognized as an internal or external command, operable program or batch file. --- /pre So I guess I need a real SCM to run Continuum. ,chris On Nov 15, 2007 12:00 PM, Christofer Jennings [EMAIL PROTECTED] wrote: Thanks Emmanuel, Ah, the FAQ. But of course :) ... sorry for that. The app I'm trying continuum has no SCM. I know. Bad Idea. But it's just a little thing for messing around in. So, for what it's worth, I copied the SCM settings verbatim from here: http://maven.apache.org/pom.html#SCMand continuum is happy now. ,chris On Nov 15, 2007 11:44 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Christofer Jennings a écrit : Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7 pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. file protocol isn't allowed by default. Activation is explain in FAQs ( http://maven.apache.org/continuum/faqs.html) If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. You must add the scm part in your pom. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
Re: trouble adding Maven 2.0 pom
1. you need a real scm defined in your pom, Continuum use it to checkout/update the working copy and to build the project 2. if your scm is svn, svn must be in your PATH Emmanuel Christofer Jennings a écrit : I take it back. Continuum is not happy. Each build results in ... pre Provider message: The svn command failed. Command output: --- 'svn' is not recognized as an internal or external command, operable program or batch file. --- /pre So I guess I need a real SCM to run Continuum. ,chris On Nov 15, 2007 12:00 PM, Christofer Jennings [EMAIL PROTECTED] wrote: Thanks Emmanuel, Ah, the FAQ. But of course :) ... sorry for that. The app I'm trying continuum has no SCM. I know. Bad Idea. But it's just a little thing for messing around in. So, for what it's worth, I copied the SCM settings verbatim from here: http://maven.apache.org/pom.html#SCMand continuum is happy now. ,chris On Nov 15, 2007 11:44 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Christofer Jennings a écrit : Hi, I'm trying continuum-1.1-beta-4 and having trouble adding a maven 2.0.7 pom. I haven't used continuum for a while, so I'm basically a newbee. If I put in a pom url like this: file:///C:/wicket/wickety/pom.xml I get this message: The specified resource isn't a file or the protocol used isn't allowed. file protocol isn't allowed by default. Activation is explain in FAQs ( http://maven.apache.org/continuum/faqs.html) If I try to upload a pom with a path like this: C:\wicket\wickety\pom.xml I get this message: Missing 'scm' element in the POM. You must add the scm part in your pom. The pom is a single module project. And I didn't change any other fields from their defaults. Any ideas? Thanks in advance, chris
Re: Maven's included with Leopard (Mac OS 10.5)
On Thu, November 15, 2007 7:00 pm, Ryan Scott wrote: Does anyone know how to fix this? I tried using darwin ports to upgrade but leopard keeps overlaying the install with 2.0.6 which does not work for my application. What were they thinking baking this into the operating system. This is almost as bad as the Java Story. Are they trying to drive developers away from Apple on purpose? What's wrong with putting v2.0.7 ahead of v2.0.6 on the PATH? Leopard is a unix machine, after all. Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Release Plugin Question
Your should add the goal to the release plugin ,configuration area like this: goalssite,site:deploy,deploy or whateveryourdeploygoal:is/goals then it gets kicked off when u run release:perform Cheers On Thu, 2007-11-15 at 12:17 -0800, Ravi_116 wrote: Can the maven release plugin deploy the war file to external application service/Tomcat after it is finished. The extra goals are added to the goal configuration parameter on the sub-module pom.xml, but the release plugin does not seem to be call the extra goals configured in the module's pom.xml. Ravi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: trouble adding Maven 2.0 pom
On Nov 15, 2007 2:49 PM, Christofer Jennings [EMAIL PROTECTED] wrote: I got SVN installed locally and set up my POM to use its repository. Continuum can now get the files and build but I get an error about compiling with generics. I says use -source 5 or higher to enable generics but I don't know where to put -source 5 hmmm See if this helps... http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html (You may also need to configure the Javadoc plugin.) -- Wendy
Re: 2 way parent-module POM dependency required?
On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote: How about re-writing the plugin to Maven2? Then you can at least remove the 'modules'-part in your base-POM... Otherwise I'm afraid you're indeed stuck with the 2-way dependency. also note the parent doesn't have to be the same as the 'containing' POM (ie. the one with the modules) for example, some projects place settings like dependencyManagement, pluginManagement, etc. in a separate POM (say inside a 'poms' directory) and have all sub-projects use this as their parent, and have module POMs just to support building from the root, not for inheriting settings. ie: pom.xml (has modules: poms, A, B) | \__ poms / pom.xml | \__ A / pom.xml (has poms as parent, relativePath ../poms) | \__ B / pom.xml (has poms as parent, relativePath ../poms) this can be really useful when you have various project types inside a single tree, because each sub-project can inherit settings from a different parent, and they won't disturb each other. the only tricky part is keeping the relativePath up-to-date, so that builds can work from any part of a check-out project tree... (I use my own plugin for this) On Thursday 15 November 2007 12:34, Aaron Zeckoski wrote: If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Yeah, we want to be able to build from either the parent (and build everything) or from the child (and just build the child) but we need the information in the parent when the child is being built. As a result, it looks like we are stuck with the 2-way dependency (at least according to what I could understand from the maven site and the maven book). In maven1 we created a plugin which would walk the source tree so that the parents did not have to know about the children. The nice thing about this is that you could drop a new project in the source tree and it would get picked up and built automatically. All the children only knew about one single master POM which provided them with a set of properties and shared dependencies. I think we are going to have to just be stuck with the tight coupling in maven 2 though. I would be happy to know I am wrong on this though so feel free to correct me. :-) -AZ Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs have to know about each other. This seems to be what the docs indicate but I might misunderstand. Are we doing something dumb here? Sample parent here: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml Sample child here: https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml Thanks for the help! -AZ -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: [EMAIL PROTECTED] Web: www.cfc.at - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cheers, Stuart
Re: How to control versioning across multiple POMs?
Sorry Arron, I have missed that section of your mail. Yes you do need
commit access across all project. I think it is reasonable that if you
don't have commit access to all the projects then you need to manually
coordinate the change with everyone. It is a pain so commit access can
solve the problem very easily. If it is a politically sensitive thing to
gain this access you could try to configure your source control to only
give you access to pom.xml.
Also, looking at your poms, I think you have a very non conventional
setup. You have alot of dependencies setup in the parent pom with provided
scope - those dependencies also seems to be artifacts of your child
projects. To be honest, I'm really confused about the structure of your
poms. Have you converted this Maven project structure from Ant? How have
you managed to perform a release of your software without a the use of
release plugin? I can't imagine how your build will work as it is like
chicken and egg problem - i.e., you need all the artifacts of the 50+
modules before you even get to build all of them.
The release tag helps you to increment -SNAPSHOT version to non snapshot.
It then tag the code and pull the code out for a clean build which it's
artifacts then gets deployed to the repository. The pom version and parent
pom version is then incremented back to the next -SNAPSHOT ready for
development again. Basically it automates the manual work of tagging,
incrementing version numbers, commiting to source control and releasing
your software version.
${project.version} just refers to the version of the pom - this is a
built-in facility of Maven to reference various element value with the
pom.
Cheers,
rOnn c.
Aaron Zeckoski [EMAIL PROTECTED]
11/15/2007 08:27 PM
Please respond to
Maven Users List users@maven.apache.org
To
[EMAIL PROTECTED]
cc
Maven Users List users@maven.apache.org
Subject
Re: How to control versioning across multiple POMs?
Do you use release plugin?
The release plugin should increment the version of the parent pom and
the
pom itself for you.
If you mean this one:
http://maven.apache.org/plugins/maven-release-plugin/index.html
No. I had a hard time understanding what it actually does from the
docs and it seems like I would need commit access to all the
sub-projects (which I do not have).
If you have dependencies to sibling pom in your dependencies
declaration,
I'd use version${project.version}/version to get around the problem
that
the release tag won't increment the version back to snapshot.
What do you mean? Where would I specify this property? In the master
POM? Is this a special property in maven2?
I have a series of 3 POMs and I need to be able to control versioning
across them. They are arranged like so:
master POM (parent of) base POM (parent of) project POM
There is one master and one base POM but there are many many project
POMs, roughly 50+ currently with new ones being added
The master POM has a version (as it seems all children must specify
the version of the parent correctly in the parent tag). The base POM
has no version as it inherits from the master. The problem here is
that we want to upgrade the overall version... except that every
project POM specifies the version of either the master or base POM (in
the parent tag). It means we have to somehow coordinate among 50+
projects (which are controlled by various people/groups) and tell them
to all change the version of the parent.
This is not ideal at all and I suspect we are just doing something
dumb or completely wrong. So, how can we control the overall version
for all the projects without having to change all of the POMs?
You can view the source here if you like:
master: https://source.sakaiproject.org/svn/master/trunk/pom.xml
base: https://source.sakaiproject.org/contrib/caret/kernel/pom.xml
sample project:
https://source.sakaiproject.org/contrib/caret/kernel/alias/pom.xml
-AZ
--
Aaron Zeckoski ([EMAIL PROTECTED])
Senior Research Engineer - CARET - Cambridge University
[http://bugs.sakaiproject.org/confluence/display/~aaronz/]
Sakai Fellow - [http://aaronz-sakai.blogspot.com/]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
##
DISCLAIMER:
This email and any attachment may contain confidential information.
If you are not the intended recipient you are not authorized to copy
or disclose all or any part of it without the prior written consent
of Toyota.
Opinions expressed in this email and any attachments are those of the
sender and not necessarily the opinions of Toyota.
Please scan this email and any attachment(s) for viruses.
Toyota does not accept any responsibility for problems caused by
viruses, whether it is Toyota's fault or not.
Proximity AccessManager
Hello, I'm configuring Proximity as an option for corporate, internal Maven repository. Currently, I'm investigating on the AccessManager feature of Proximity, specifically on the Affirmative AccessManager. In this moment, I'm configuring a file for the SimplePropertiesFileUsernameBasedAccessDecisionVoter, however I'm always receiving an error message saying: 2007-11-14 16:27:48,211 INFO [org.abstracthorizon.proximity.webapp.controllers.RepositoryController] - Access forbidden to /inhouse.snapshot for 127.0.0.1 Access to resource / has been forbidden because:org.abstracthorizon.proximity.AccessDeniedException: Voter org.abstracthorizon.proximity.access.SimplePropertiesFileUsernameBasedAccessDecisionVoter has voted against access. The contents of my simple properties file is: inhouse.snapshot=ejoszep I'm not really sure how if the format of the user name is correct. I'm running proximity on Tomcat 6 on Windows, and my user is part of a Windows domain. I would really appreciate any help if any of you have had experiences on this subject. Thanks, Alejandro Uriza -- View this message in context: http://www.nabble.com/Proximity-AccessManager-tf4817898s177.html#a13784096 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: Is http://mirrors.ibiblio.org/pub/mirrors/maven2 down?
I already contacted them, forgot to copy this list On Nov 15, 2007 11:55 PM, Dennis Lundberg [EMAIL PROTECTED] wrote: The ibiblio mirror is not run by the Maven team. You'd have to contact the folks at ibiblio if you want to know when they will be fixing it. Kohsuke Kawaguchi wrote: The central repository http://repo1.maven.org/maven2/ appears to be up, but the ibiblio mirror seems to be down since this morning. Is the maven team aware of the issue? Is this going to be fixed some time soon? -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: trouble adding Maven 2.0 pom
Thanks Wendy! That did the trick. No complaints about the javadoc plugin that I see so far. Thanks all for your guidance. ,chris On Nov 15, 2007 1:57 PM, Wendy Smoak [EMAIL PROTECTED] wrote: On Nov 15, 2007 2:49 PM, Christofer Jennings [EMAIL PROTECTED] wrote: I got SVN installed locally and set up my POM to use its repository. Continuum can now get the files and build but I get an error about compiling with generics. I says use -source 5 or higher to enable generics but I don't know where to put -source 5 hmmm See if this helps... http://maven.apache.org/plugins/maven-compiler-plugin/examples/set-compiler-source-and-target.html (You may also need to configure the Javadoc plugin.) -- Wendy
Re: 2 way parent-module POM dependency required?
Understood, but if you have dependencies to you sibling-modules, you'd have the same problem... So, I'd personally always build from the root-project after a fresh check-out... And from then on it wouldn't be necessary to use the relativePath. Still, I understand your reasoning and I agree it's probably the best solution in your scenario. On Thursday 15 November 2007 15:25, Stuart McCulloch wrote: On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote: True. One question though: why do you use the 'relativePath'-attribute? This shouldn't be really necessary, or am I missing something here? say you've just checked out a fresh project tree from svn - it's not yet been released to any remote repository, and you have a clean local repository. if you went to a sub-folder and tried mvn install it would complain about not finding the parent POM (because it's not the same as the containing .. POM) the relativePath attribute tells Maven where to find the POM if it can't find it in the local or remote repositories - note that if the parent is the same as the containing POM then you shouldn't need to use relativePath http://maven.apache.org/guides/introduction/introduction-to-the-pom.html#Ex ample_2 HTH On Thursday 15 November 2007 14:35, Stuart McCulloch wrote: On 15/11/2007, Roland Asmann [EMAIL PROTECTED] wrote: How about re-writing the plugin to Maven2? Then you can at least remove the 'modules'-part in your base-POM... Otherwise I'm afraid you're indeed stuck with the 2-way dependency. also note the parent doesn't have to be the same as the 'containing' POM (ie. the one with the modules) for example, some projects place settings like dependencyManagement, pluginManagement, etc. in a separate POM (say inside a 'poms' directory) and have all sub-projects use this as their parent, and have module POMs just to support building from the root, not for inheriting settings. ie: pom.xml (has modules: poms, A, B) \__ poms / pom.xml \__ A / pom.xml (has poms as parent, relativePath ../poms) \__ B / pom.xml (has poms as parent, relativePath ../poms) this can be really useful when you have various project types inside a single tree, because each sub-project can inherit settings from a different parent, and they won't disturb each other. the only tricky part is keeping the relativePath up-to-date, so that builds can work from any part of a check-out project tree... (I use my own plugin for this) On Thursday 15 November 2007 12:34, Aaron Zeckoski wrote: If you build the 'parent' and it does not contain the 'modules'-tag, the children DO NOT get build. Yeah, we want to be able to build from either the parent (and build everything) or from the child (and just build the child) but we need the information in the parent when the child is being built. As a result, it looks like we are stuck with the 2-way dependency (at least according to what I could understand from the maven site and the maven book). In maven1 we created a plugin which would walk the source tree so that the parents did not have to know about the children. The nice thing about this is that you could drop a new project in the source tree and it would get picked up and built automatically. All the children only knew about one single master POM which provided them with a set of properties and shared dependencies. I think we are going to have to just be stuck with the tight coupling in maven 2 though. I would be happy to know I am wrong on this though so feel free to correct me. :-) -AZ Just play around with it a bit, Maven is very flexible in this way. I do however believe it is described in the documentation, and pretty extensive if I recall correctly... On Wednesday 14 November 2007 23:51, Aaron Zeckoski wrote: Is the 2-way parent/module dependency actually the right way to link children and parent POMs? This is what we currently have: The parent includes definition of a module (or group of modules) like so: ... groupIdorg.sakaiproject/groupId artifactIdbase/artifactId packagingpom/packaging ... modules modulealias/module /modules ... Then the child defines a parent like so: ... parent artifactIdbase/artifactId groupIdorg.sakaiproject/groupId versionM2/version relativePath../pom.xml/relativePath /parent ... As a result, we end up with this 2-way linkage bewteen these POMs which ends up not being very flexible since all of the POMs
Re: Maven's included with Leopard (Mac OS 10.5)
Ryan Scott wrote: I have tried many things but i keep getting patch updates from Apple that overwrites my changes. It is not really unix if you can't run any version of Java you want lol. You mean to say that Apple is updating your .bash_profile file? Works fine for me here, unless this is a Leopard thing. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: automate localhost deploy
Cargo would be your best bet...http://cargo.codehaus.org/ Cheers, Henry On 11/16/07, mitch [EMAIL PROTECTED] wrote: Hello, I'm using maven2 (and the m2eclipse integration plugin) and am able to use the deploy goal successfully to deploy to a remote repository. But I wonder what the easiest way is to automate my manual steps of deploying to my localhost tomcat (including stopping and starting the container). Any idea how I could automate these steps? The steps would be: - stop tomcat - delete old war and app in my tomcat/webapps - rename the new war in my eclipse project /target dir - deploy the new war from my eclipse project /target dir to my localhost tomcat/webapps dir - start tomcat Thx for any help!
automate localhost deploy
Hello, I'm using maven2 (and the m2eclipse integration plugin) and am able to use the deploy goal successfully to deploy to a remote repository. But I wonder what the easiest way is to automate my manual steps of deploying to my localhost tomcat (including stopping and starting the container). Any idea how I could automate these steps? The steps would be: - stop tomcat - delete old war and app in my tomcat/webapps - rename the new war in my eclipse project /target dir - deploy the new war from my eclipse project /target dir to my localhost tomcat/webapps dir - start tomcat Thx for any help!
no net in java.library.path
I am very new to Maven. When first compiling my project and generating files, everything worked fine. I then tried to run run mvn clean and mvn idea:idea and got the following error message: no net in java.library.path Would anyone know why my copy of maven wouldn't be able to access its repository for updates? Thanks, Matt -- View this message in context: http://www.nabble.com/no-net-in-java.library.path-tf4818939s177.html#a13786816 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: no net in java.library.path
I think there must be something else going on with your system... What OS? What Java JDK version? What Maven version? Can you try running mvn with the -X parameter, to capture the full debug output? Wayne On 11/15/07, ozymandias [EMAIL PROTECTED] wrote: I am very new to Maven. When first compiling my project and generating files, everything worked fine. I then tried to run run mvn clean and mvn idea:idea and got the following error message: no net in java.library.path Would anyone know why my copy of maven wouldn't be able to access its repository for updates? Thanks, Matt -- View this message in context: http://www.nabble.com/no-net-in-java.library.path-tf4818939s177.html#a13786816 Sent from the Maven - Users mailing list archive at Nabble.com. - 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: Maven/Hibernate error / anyone has find similar?
http://opensource.atlassian.com/projects/hibernate/browse/HHH- perchance? On Thursday 15 November 2007 02:30:56 pm Marco Mistroni wrote: Hello, mm not really :) found out that i had a clash between followign dependencies - hibernate 3.2.x - asm-all -cglib - spring ? i am trying to move my project from ant to maven, and we are using hibernate spring, cglib and asm libraries when i downloaded them from web, i got error, when instead i pointed to version installed on my local machine (teh one i m using with ant) everythign worked fine i'll need toinvestigate more as this may cause us problems if we update any versions of spring or hibernate i'll report back here my findings once i proceed with my investigation regards marco On Nov 14, 2007 9:04 PM, Wayne Fay [EMAIL PROTECTED] wrote: Take a look at your applicationContext.xml file, apparently you have an issue with how you've defined your sessionFactory bean (??). org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError Caused by: java.lang.NoClassDefFoundError at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGLIB LazyInitializer.java:107) Wayne On 11/14/07, Marco Mistroni [EMAIL PROTECTED] wrote: hi all, i am trying to port an app from ant to maven , but it looks like i am having troubles iwth dependencies. has anyone ever found the error below? i attach my dependencies at the end of message, hope someone can sort me out Tests run: 1, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.39 sec FAILURE! testGetBSDRBondIdsReturnsBondIds(com.bnpparibas.risk.collateralrisk.dao .IssueDaoIntegrationTest) Time elapsed: 0.359 sec ERROR! org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'sessionFactory' defined in class path resource [applicationContext.xml]: Invocation of init method failed; nested exception is java.lang.NoClassDefFoundError Caused by: java.lang.NoClassDefFoundError at org.hibernate.proxy.pojo.cglib.CGLIBLazyInitializer.getProxyFactory(CGL IBLazyInitializer.java:107) at org.hibernate.proxy.pojo.cglib.CGLIBProxyFactory.postInstantiate(CGLIBP roxyFactory.java:43) - 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] -- Steve Ebersole Hibernate Project Lead http://hibernate.org Principal Software Engineer http://redhat.com http://jboss.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
both idlj and jacorb
I'm a looking to convert a project to maven. This project currently produces two jar files from the same IDL source, by generating first from idlj and then again from jacorb. For instance, jacorb-foo.jar and idlj-foo.jar. Is there some way of setting up my pom.xml so that this can still happen? Or what is the best way forward with maven to achieve this? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
