new to maven
Hi I am new to Maven 2. I have been converting an application consisting of 4 eclipse projects, 3 producing library jars the the final one running the application. I have got to the stage where every thing now compiles and the 3 jar files are deployed in my repository (I am using artifactory). My application also compiles. My issues is that despite a lot of reading I still can not work out how to run my application! There are external jars required, these are set as dependencies in the POM. What I would like to achieve is to be able to run the application from within the eclipse debug environment. To do this I need to get not only the generated jar files but also the library jars and the XML configuration files on the class path. Ideally also in a directory so that I can copy it and run the application on another machine. I am sure this is not difficult to do but at this moment in time I am unable to work it out. Ian ___ Want ideas for reducing your carbon footprint? Visit Yahoo! For Good http://uk.promotions.yahoo.com/forgood/environment.html
Common configuration for a set of projects / inheritance from super-pom
Hello, I would like to separate the reporting section for all of our projects in a common configuration file or pom to keep the projects pom as simple as possible. I already created a hierarchy of poms (java-pom, maven-plugin-pom and so on) for the different project types to externalize common settings for similar projects. But the section included in my java-pom isn't inherited by my java projects. Searching the Internet I found out this is the expected behaviour. But how do you solve the problem of a central reporting configuration? Do you repeat the configuration in every project pom? Greetings, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problems using a customized javadoc plugin from custom repository
Vincent Siveton wrote:
> Hi,
>
> Try to remove your repo, specially:
> ${user.home}/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin
Vincent, I already did that, and even tried compiling with an empty
local repo: still the same error.
-dirk
> 2007/10/24, Dirk Olmes <[EMAIL PROTECTED]>:
>> Hi,
>>
>> I'm trying to work around http://jira.codehaus.org/browse/MJAVADOC-157
>> so I have checked out the maven-javadoc-plugin sources and tweaked it so
>> it works for building my site. I have added the necessary into to deploy
>> my patched m-j-p to my custom repo and deployed it.
>>
>> The site runs on our CI server which must be able to download the
>> patched m-j-p from our custom repo. This works fine but when I run the
>> site, I get the following error message:
>>
>> [INFO]
>>
>> [ERROR] BUILD ERROR
>> [INFO]
>>
>> [INFO] Error getting reports from the plugin
>> 'org.apache.maven.plugins:maven-javadoc-plugin': Unable to find the mojo
>> 'org.apache.maven.plugins:maven-javadoc-plugin:2.4-MULE-586296:javadoc'
>> in the plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
>> org/apache/maven/doxia/siterenderer/RendererException
>>
>> No, running with -X -e does not come up with any more helpful info either.
>>
>> I have searched the archive and found various threads with "unable to
>> find the mojo" which generally seems to be solved by removing the plugin
>> in question from the local repo. I did this and I even ran the build
>> with a fresh local repo: the error remains the same.
>>
>> Any idea what could be wrong here?
>>
>> -dirk
>>
>> -
>> 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: Is there a way to redirect the output of maven-exec plugin to a file?
If its not obvious in the docs, it probably does not exist. Feel free to add the functionality you need and contribute it back. Wayne On 10/24/07, Yan Huang <[EMAIL PROTECTED]> wrote: > Hello, > > Quick question: is there a way to direct the execution log of maven-exec > plugin (on the fly) to a file rather than the console? I think all Mojo is > using log4j property for the logging. However, if I want it to dump the log > of whatever it invokes, how can i do it? It seems to me that > the exec plugin does not provide this option? > > Thanks > Yan > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Is there a way to redirect the output of maven-exec plugin to a file?
Hello, Quick question: is there a way to direct the execution log of maven-exec plugin (on the fly) to a file rather than the console? I think all Mojo is using log4j property for the logging. However, if I want it to dump the log of whatever it invokes, how can i do it? It seems to me that the exec plugin does not provide this option? Thanks Yan
Re: jgoodies
If you do a search on jgoodies on mvnrepository.com, you see that the latest version of com.jgoodies.forms is 1.0.7 and com.jgoodies.looks is on 2.1.4. If you want the newest version of them uploaded to the central repository, show the page on maven.apache.org to the jgoodies developers[1]. Hth, Nick Stolwijk [1] http://maven.apache.org/guides/mini/guide-central-repository-upload.html Brandon Enochs wrote: Does anybody know if the latest version of forms (1.1.0) and looks (2.1.4) are part of the maven repository? - 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]
jgoodies
Does anybody know if the latest version of forms (1.1.0) and looks (2.1.4) are part of the maven repository? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: unpackOptions tag has no effect
I'm not using excludes in unpackOptions myself, but make sure:
1. This functionality is available in a public release, and not just a snapshot
2. You've specified the a release version that has this functionality
in your pom declaration
Many times I've seen people add a pom snippet from the mailing list,
Jira, or even the plugin documentation without realizing that it won't
necessarily work since that functionality is not yet available in a
released plugin version. Check the @since tag in the plugin docs.
Wayne
On 10/24/07, Arik Kfir <[EMAIL PROTECTED]> wrote:
> Hi,
>
> I have a multi-module project, where one of the modules is a WAR, with
> several dependencies
> packaged in its WEB-INF/lib directory. The top-level project builds an
> assembly, which needs
> to contain the WAR in an unpacked form.
>
> I used the true and tags to make sure the
> WAR is unpacked AND to exclude its "WEB-INF/lib" directory.
>
> The problem is that the excludes in 'unpackOptions' doesn't seem to affect
> the assembly; my JARs
> are still unpacked from the WAR and stored in my assembly.
>
> POM structure is:
>
> myproject ("pom" packaging, does NOT extend parent)
> |
> +---parent module ("pom" packaging, others extend this one)
> |
> +---war module ("war" packaging, extends parent)
> |
> +---other modules...
>
>
> The assembly descriptor is as follows (created on the 'package' phase of the
> lifecycle):
> =
>
>slim-application
>
>tar.gz
>zip
>
>false
>
>
>
>org.myproject:war:*:*
>
>
>
>
>application
>
>true
>
>
>false
>
>
>true
>
>
>
>
>**/*.jar
>
>
>
>
>
>
>...
>...(irrelevant to this mail)
>...
>
>
>
> Note that instead of "**/*.jar" I have also tried "/WEB-INF/lib/*.jar",
> "/WEB-INF/lib", and similar combinations, but to no avail.
>
> If anyone has encountered anything like that, or if you spot something I'm
> doing wrong here - I'd appreciate your help.
> Thanks,
> Arik Kfir.
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
unpackOptions tag has no effect
Hi,
I have a multi-module project, where one of the modules is a WAR, with
several dependencies
packaged in its WEB-INF/lib directory. The top-level project builds an
assembly, which needs
to contain the WAR in an unpacked form.
I used the true and tags to make sure the
WAR is unpacked AND to exclude its "WEB-INF/lib" directory.
The problem is that the excludes in 'unpackOptions' doesn't seem to affect
the assembly; my JARs
are still unpacked from the WAR and stored in my assembly.
POM structure is:
myproject ("pom" packaging, does NOT extend parent)
|
+---parent module ("pom" packaging, others extend this one)
|
+---war module ("war" packaging, extends parent)
|
+---other modules...
The assembly descriptor is as follows (created on the 'package' phase of the
lifecycle):
=
slim-application
tar.gz
zip
false
org.myproject:war:*:*
application
true
false
true
**/*.jar
...
...(irrelevant to this mail)
...
Note that instead of "**/*.jar" I have also tried "/WEB-INF/lib/*.jar",
"/WEB-INF/lib", and similar combinations, but to no avail.
If anyone has encountered anything like that, or if you spot something I'm
doing wrong here - I'd appreciate your help.
Thanks,
Arik Kfir.
Re: release:prepare failure during scm-tag : Server certificate verification failed: issuer is not trusted
Anyone have any ideas on why this would happen? Any help is appreciated. Thanks. -- Jason Jason Mihalick wrote: > > I've been searching the groups, the web, and the doc and I've not been > able to find a solution to this. Any help you can offer is much > appreciated. > > I have successfully executed half of a release:prepare. The version > numbers in my all of my POMs were successfully updated and maven > successfully committed them to my scm repository. We are using subversion > over https. I've added the SSL certificate for the site to my keystore > (at both the JVM level and in a .keystore in my home directory). I have > also checked that the fingerprint for the cert was added to > ~/.subversion/auth/svn.ssl.server. The release:prepare is failing with > this error when it attempts to create the tag for the release: > > [INFO] [release:prepare] > [INFO] Resuming release from phase 'scm-tag' > [INFO] Tagging release with the label datamanager-1.0... > [INFO] Executing: svn --non-interactive copy --file > /tmp/maven-scm-2112306694.commit . > https://www..com/svn/tags//datamanager-1.0 > [INFO] Working directory: /Users/jason/projects/DataManager-trunk > [INFO] > > [ERROR] BUILD FAILURE > [INFO] > > [INFO] Unable to tag SCM > Provider message: > The svn tag command failed. > Command output: > svn: PROPFIND request failed on '/svn/tags//datamanager-1.0' > svn: PROPFIND of '/svn/tags//datamanager-1.0': Server > certificate verification failed: issuer is not trusted > (https://www..com) > > Why would the commit to the same SCM succeed, while the tag operation > fails with this error? I'm baffled. > > Thanks for the help, > Jason > -- View this message in context: http://www.nabble.com/release%3Aprepare-failure-during-scm-tag-%3A---Server-certificate-verification-failed%3A-issuer-is-not-trusted-tf4678454s177.html#a13394158 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: Newbie question on deployment strategy
Generally yes this means a complete undeploy plus deploy of the new war, unless you've got some special J2EE server that does it another way. Schedule downtime or find a low-usage time to push your WARs, just like everybody else. Ideally you're not pushing updates out to Prod on a daily basis but instead using your Dev and Test/QA environments for those types of builds, and then pushing bigger updates or emergency bugfixes out to Prod. Wayne On 10/24/07, Ross Mcdonald <[EMAIL PROTECTED]> wrote: > Hi, > > thanks for that, I am trying to get my head into this method of > working.. I am just a little worried about having to reload a war each > time, doesn't that require complete reloading of the war in the web > server, which is perhaps too much of an interruption to a production > application in some cases ? > > Regards, > > Ross > > > Nick Stolwijk wrote: > > Normally, even with a few updated files, you would release your > > project again. Then it will create a new version number, a tag and the > > final artifacts, like jars and wars. This has nothing to do with how > > you deploy it to production. The deployment Maven talks about is > > deploying the artifacts to a Maven repository. > > > > The deployment to production will be the full war file again. This > > way, you can reproduce the deployment. (Changing some files on your > > production server is not a good idea.) Also, often these new artifacts > > will have to go through testing and acceptance again, before making it > > to a production server. (Our development cycle is Development, Test, > > Acceptance, Production) > > > > I hope this clears things up a bit. > > > > With regards, > > > > Nick Stolwijk > > > > Ross Mcdonald wrote: > >> Hi all, > >> > >> I am a newbie to this, carefully considering bringing Maven in house > >> to our small company to improve a number of different systems. I > >> have downloaded a couple of ebooks which are great, and I see many > >> ways in which Maven will make life easier, I am however finding it > >> difficult to track down information in the books and with the help of > >> google on deployment strategies for live setups. > >> > >> > >> I see the use of creating a war for initial deployment, but what > >> about later when just want to send a few updated files across to a > >> production server? I say there is a distributionManagement element, > >> which can use a number of different protocols to send files, but I > >> cannot see any real world examples, or find documentation with enough > >> detail. Can anyone point me towards some nice easy examples on this > >> topic? > >> > >> Thankyou in advance for your help. > >> > >> Regards, > >> > >> Ross > >> > >> > >> - > >> 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Newbie question on deployment strategy
Hi, thanks for that, I am trying to get my head into this method of working.. I am just a little worried about having to reload a war each time, doesn't that require complete reloading of the war in the web server, which is perhaps too much of an interruption to a production application in some cases ? Regards, Ross Nick Stolwijk wrote: Normally, even with a few updated files, you would release your project again. Then it will create a new version number, a tag and the final artifacts, like jars and wars. This has nothing to do with how you deploy it to production. The deployment Maven talks about is deploying the artifacts to a Maven repository. The deployment to production will be the full war file again. This way, you can reproduce the deployment. (Changing some files on your production server is not a good idea.) Also, often these new artifacts will have to go through testing and acceptance again, before making it to a production server. (Our development cycle is Development, Test, Acceptance, Production) I hope this clears things up a bit. With regards, Nick Stolwijk Ross Mcdonald wrote: Hi all, I am a newbie to this, carefully considering bringing Maven in house to our small company to improve a number of different systems. I have downloaded a couple of ebooks which are great, and I see many ways in which Maven will make life easier, I am however finding it difficult to track down information in the books and with the help of google on deployment strategies for live setups. I see the use of creating a war for initial deployment, but what about later when just want to send a few updated files across to a production server? I say there is a distributionManagement element, which can use a number of different protocols to send files, but I cannot see any real world examples, or find documentation with enough detail. Can anyone point me towards some nice easy examples on this topic? Thankyou in advance for your help. Regards, Ross - 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: Release and Changes plugin
Did anyone ever answer this?
On 5/10/07, Chris Helck <[EMAIL PROTECTED]> wrote:
>
> Hi,
>
> I've started using the changes plugin. Does it integrate with the
> release plugin? What I mean is if changes.xml contains a line like:
>
>
>
> When I run release:prepare, release:peform I'd like the line to be
> changed to reflect the real version number:
>
>
>
>
> Is this possible?
>
> Thanks,
> Christopher Helck
>
>
> **
> This communication and all information (including, but not limited to,
> market prices/levels and data) contained therein (the "Information") is
> for informational purposes only, is confidential, may be legally
> privileged and is the intellectual property of ICAP plc and its affiliates
> ("ICAP") or third parties. No confidentiality or privilege is waived or
> lost by any mistransmission. The Information is not, and should not
> be construed as, an offer, bid or solicitation in relation to any
> financial instrument or as an official confirmation of any transaction.
> The Information is not warranted, including, but not limited, as to
> completeness, timeliness or accuracy and is subject to change
> without notice. ICAP assumes no liability for use or misuse of the
> Information. All representations and warranties are expressly
> disclaimed. The Information does not necessarily reflect the views of
> ICAP. Access to the Information by anyone else other than the
> recipient is unauthorized and any disclosure, copying, distribution or
> any action taken or omitted to be taken in reliance on it is prohibited.
> If
> you receive this message in error, please immediately delete it and all
> copies of it from your system, destroy any hard copies of it and
> notify the sender.
> **
>
>
--
Esse Quam Videre
To Be, rather than to Seem
Re: Trying to setup a Maven Shared Repository
Hello, well yes. you'd need to change your settings.xml in your .m2 directory to point to your machine i m sure in artifactory website there's an example, .. i'll send you an example tomorrow from work of a settings.xml and an artifactory config file.. regards marco On 10/24/07, charliec <[EMAIL PROTECTED]> wrote: > > > I downloaded 1.2.2-rc0 and I can browse > http://:8081/artifactory. But > I still receive the same error through Maven. Is there any other > configuration that needs to be done through the tool or Maven besides > modifying the mirror settings in Maven's settings.xml. > > > Yoav Landman wrote: > > > > The URL that should be browsable from the UI with the out-of-the-box > > installation is: http://:8081/artifactory > > I'd also suggest you use 1.2.5-rc1, instead of rc-0. > > You might want to take this to the artifactory-users list... > > > > > > charliec wrote: > >> > >> Hello, > >> I downloaded artifactory and executed the batch script artifactory.batto > >> start it. I added the following to the settings.xml file: > >> > >> artifactory > >> * > >> http://:8081/artifactory/repo > >> Artifactory > >> > >> However, when I execute Maven, I still receive the following error: > >> Caused by: java.io.IOException: Server returned HTTP response code: 503 > >> for URL: > >> > >> > http://:8081/artifactory/repo/org/apache/maven/plugins/maven-resource > >> s-plugin/maven-metadata.xml > >> > >> I noticed the machine that when I try to bring up > >> http://:8081 on the machine that has artifactory > installed, > >> I receive the following message: > >> > >> No context on this server matched or handled this request. > >> Contexts known to this server are: > >> /artifactory ---> > >> [EMAIL PROTECTED] > /artifactory,jar:file:/D:/artifactory-1.2.5-rc0/webapps/artifactory.war!/} > >> > >> The documentation for artifactory says to set up maven to use > artifactory > >> proxy, just configure a maven repository with the following URL: > >> http://[your server name]:[port]/artifactory/repo > >> > >> What do I need to accomplish this? Thanks. > >> > >> > >> > >> mmistroni wrote: > >>> > >>> Hello, > >>> i m trying to do same with artifactory.. worked fine so far.. i > >>> recommend u > >>> have a look at that > >>> > >>> regards > >>> marco > >>> > >>> On 10/23/07, Wayne Fay <[EMAIL PROTECTED]> wrote: > > Simply putting an HTTP server on top of your personal .m2 directory > (local repo cache) is not sufficient. The metadata in a real Maven > repo is different than what is in your private local repo cache. > > Please look at Archiva, Proximity, Artifactory, etc for a "real" > Maven > repo solution. > > Wayne > > On 10/23/07, charliec <[EMAIL PROTECTED]> wrote: > > > > Hello, > > I'm trying to setup a shared repository that mirrors the central > repository > > so other team members can download from this repository instead of > accessing > > the central. I've created a Virtaul Directory in IIS that points > to > my > .m2 > > repository. I can access this repostory on another machine via the > browser > > using url such as the following: http:///repository. > On > the > > other machine, I added the following to my pom.xml file: > > > > > > central > > http:///repository > > name>Maven Repository Manager running on > repo.company.com > > > > > > > > > > >central > >IMaven Repository Manager running on repo.company.com > > >http:///repository > > > > > > > > When I run mvn install, I receive the error below. It doesn't > even > try > to > > access the shared repository. Please help. Any assistance would > be > greatly > > appreciated. Thanks. > > > > > > + Error stacktraces are turned on. > > Maven version: 2.0.7 > > Java version: 1.5.0_12 > > OS name: "windows xp" version: "5.1" arch: "x86" > > [DEBUG] Building Maven user-level plugin registry from: > 'C:\Documents > and > > Settin > > gs\COSS\.m2\plugin-registry.xml' > > [DEBUG] Building Maven global-level plugin registry from: > > 'C:\maven-2.0.7\conf\p > > lugin-registry.xml' > > [INFO] Scanning for projects... > > [INFO] > > > > - > > --- > > [INFO] Building my-app > > [INFO]task-segment: [install] > > [INFO] > > > > - > > --- > > [INFO] artifact > org.apache.maven.plugins:maven-resources-plugin:checking > > for up > > dates from central > > [WARNING] repository metadata for: 'artifact > >
Re: Problems using a customized javadoc plugin from custom repository
Hi,
Try to remove your repo, specially:
${user.home}/.m2/repository/org/apache/maven/plugins/maven-javadoc-plugin
Cheers,
Vincent
2007/10/24, Dirk Olmes <[EMAIL PROTECTED]>:
> Hi,
>
> I'm trying to work around http://jira.codehaus.org/browse/MJAVADOC-157
> so I have checked out the maven-javadoc-plugin sources and tweaked it so
> it works for building my site. I have added the necessary into to deploy
> my patched m-j-p to my custom repo and deployed it.
>
> The site runs on our CI server which must be able to download the
> patched m-j-p from our custom repo. This works fine but when I run the
> site, I get the following error message:
>
> [INFO]
>
> [ERROR] BUILD ERROR
> [INFO]
>
> [INFO] Error getting reports from the plugin
> 'org.apache.maven.plugins:maven-javadoc-plugin': Unable to find the mojo
> 'org.apache.maven.plugins:maven-javadoc-plugin:2.4-MULE-586296:javadoc'
> in the plugin 'org.apache.maven.plugins:maven-javadoc-plugin'
> org/apache/maven/doxia/siterenderer/RendererException
>
> No, running with -X -e does not come up with any more helpful info either.
>
> I have searched the archive and found various threads with "unable to
> find the mojo" which generally seems to be solved by removing the plugin
> in question from the local repo. I did this and I even ran the build
> with a fresh local repo: the error remains the same.
>
> Any idea what could be wrong here?
>
> -dirk
>
> -
> 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: Newbie question on deployment strategy
Normally, even with a few updated files, you would release your project again. Then it will create a new version number, a tag and the final artifacts, like jars and wars. This has nothing to do with how you deploy it to production. The deployment Maven talks about is deploying the artifacts to a Maven repository. The deployment to production will be the full war file again. This way, you can reproduce the deployment. (Changing some files on your production server is not a good idea.) Also, often these new artifacts will have to go through testing and acceptance again, before making it to a production server. (Our development cycle is Development, Test, Acceptance, Production) I hope this clears things up a bit. With regards, Nick Stolwijk Ross Mcdonald wrote: Hi all, I am a newbie to this, carefully considering bringing Maven in house to our small company to improve a number of different systems. I have downloaded a couple of ebooks which are great, and I see many ways in which Maven will make life easier, I am however finding it difficult to track down information in the books and with the help of google on deployment strategies for live setups. I see the use of creating a war for initial deployment, but what about later when just want to send a few updated files across to a production server? I say there is a distributionManagement element, which can use a number of different protocols to send files, but I cannot see any real world examples, or find documentation with enough detail. Can anyone point me towards some nice easy examples on this topic? Thankyou in advance for your help. Regards, Ross - 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]
Regarding ${reactorProjects}
Hello,
I'm wondering if there is any example of pom.xml that is using the reference
variable ${reactorProjects} to navigate the project instances which are
processed as part of current build? or any technical reference doc for that
variable?
Thanks
Yan
Re: Changing the default local repository
If you look at the Settings Object Model[1], you'll see the following tag:
/settings/localRepository.
That's the one you're looking for.
Hth,
Nick Stolwijk
[1] http://maven.apache.org/ref/2.0.7/maven-settings/settings.html
[EMAIL PROTECTED] wrote:
I 've looked thru the FAQ of POM as well as settings and was unable to
find an answer.
How do I change the default local repository from ${user.home}/.m2
to something else?
Regards,
/U
-
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 Create Path
I hope this thread demonstrates the utility of telling the list what you're really trying to do, rather than simply asking how to do a particular thing you can't figure out. ;-) Wayne On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> wrote: > Thanks! > > -Original Message- > From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart > McCulloch > Sent: Wednesday, October 24, 2007 1:21 PM > To: Maven Users List > Subject: Re: Maven Create Path > > On 24/10/2007, Damien Lecan <[EMAIL PROTECTED]> wrote: > > > > Don't loose time doing that by hand > > > > Use this Apache Felix plugin : > > http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html > > > FYI, this is the latest, up-to-date page: > > http://felix.apache.org/site/maven-bundle-plugin-bnd.html > > look for the "Embedding Dependencies" section for some tips > if you have any questions, just email [EMAIL PROTECTED] > > HTH > > Good luck > > > > Damien > > > > 2007/10/24, Roshan A. Punnoose <[EMAIL PROTECTED]>: > > > Well I am trying to bundle an osgi bundle. And it needs a > > > Bundle-Classpath entry in the Manifest. This entry has to be a > > > comma-separated list of all the jars needed by the osgi bundle. I > have > > > these jars downloaded using the > > > maven-dependency-plugin:copy-dependencies, but I cannot seem to > figure > > > out how to get the path created. > > > > > > Roshan > > > > > > -Original Message- > > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > > Sent: Wednesday, October 24, 2007 10:49 AM > > > To: Maven Users List > > > Subject: Re: Maven Create Path > > > > > > What are you trying to do that Maven isn't doing/can't do for you? > > > There may be a better way to approach this from a Maven perspective. > > > > > > Wayne > > > > > > On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> > > > wrote: > > > > Hi, > > > > > > > > In Ant, I was able to take a directory and create a full path > defining > > > > all the entries in that directory. For example, in directory lib, > I > > > have > > > > jars: > > > > -test1.jar > > > > -test2.jar > > > > -test3.jar. I want to be able to create a path and set it as a > > > property > > > > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > > > > > > > Is this possible in Maven? > > > > > > > > Roshan > > > > > > > > > - > > > > 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] > > > > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Cheers, Stuart > > - > 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]
Changing the default local repository
I 've looked thru the FAQ of POM as well as settings and was unable to
find an answer.
How do I change the default local repository from ${user.home}/.m2
to something else?
Regards,
/U
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Newbie question on deployment strategy
Hi all, I am a newbie to this, carefully considering bringing Maven in house to our small company to improve a number of different systems. I have downloaded a couple of ebooks which are great, and I see many ways in which Maven will make life easier, I am however finding it difficult to track down information in the books and with the help of google on deployment strategies for live setups. I see the use of creating a war for initial deployment, but what about later when just want to send a few updated files across to a production server? I say there is a distributionManagement element, which can use a number of different protocols to send files, but I cannot see any real world examples, or find documentation with enough detail. Can anyone point me towards some nice easy examples on this topic? Thankyou in advance for your help. Regards, Ross - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven Create Path
Thanks! -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Stuart McCulloch Sent: Wednesday, October 24, 2007 1:21 PM To: Maven Users List Subject: Re: Maven Create Path On 24/10/2007, Damien Lecan <[EMAIL PROTECTED]> wrote: > > Don't loose time doing that by hand > > Use this Apache Felix plugin : > http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html FYI, this is the latest, up-to-date page: http://felix.apache.org/site/maven-bundle-plugin-bnd.html look for the "Embedding Dependencies" section for some tips if you have any questions, just email [EMAIL PROTECTED] HTH Good luck > > Damien > > 2007/10/24, Roshan A. Punnoose <[EMAIL PROTECTED]>: > > Well I am trying to bundle an osgi bundle. And it needs a > > Bundle-Classpath entry in the Manifest. This entry has to be a > > comma-separated list of all the jars needed by the osgi bundle. I have > > these jars downloaded using the > > maven-dependency-plugin:copy-dependencies, but I cannot seem to figure > > out how to get the path created. > > > > Roshan > > > > -Original Message- > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, October 24, 2007 10:49 AM > > To: Maven Users List > > Subject: Re: Maven Create Path > > > > What are you trying to do that Maven isn't doing/can't do for you? > > There may be a better way to approach this from a Maven perspective. > > > > Wayne > > > > On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> > > wrote: > > > Hi, > > > > > > In Ant, I was able to take a directory and create a full path defining > > > all the entries in that directory. For example, in directory lib, I > > have > > > jars: > > > -test1.jar > > > -test2.jar > > > -test3.jar. I want to be able to create a path and set it as a > > property > > > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > > > > > Is this possible in Maven? > > > > > > Roshan > > > > > > - > > > 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] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Create Path
On 24/10/2007, Damien Lecan <[EMAIL PROTECTED]> wrote: > > Don't loose time doing that by hand > > Use this Apache Felix plugin : > http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html FYI, this is the latest, up-to-date page: http://felix.apache.org/site/maven-bundle-plugin-bnd.html look for the "Embedding Dependencies" section for some tips if you have any questions, just email [EMAIL PROTECTED] HTH Good luck > > Damien > > 2007/10/24, Roshan A. Punnoose <[EMAIL PROTECTED]>: > > Well I am trying to bundle an osgi bundle. And it needs a > > Bundle-Classpath entry in the Manifest. This entry has to be a > > comma-separated list of all the jars needed by the osgi bundle. I have > > these jars downloaded using the > > maven-dependency-plugin:copy-dependencies, but I cannot seem to figure > > out how to get the path created. > > > > Roshan > > > > -Original Message- > > From: Wayne Fay [mailto:[EMAIL PROTECTED] > > Sent: Wednesday, October 24, 2007 10:49 AM > > To: Maven Users List > > Subject: Re: Maven Create Path > > > > What are you trying to do that Maven isn't doing/can't do for you? > > There may be a better way to approach this from a Maven perspective. > > > > Wayne > > > > On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> > > wrote: > > > Hi, > > > > > > In Ant, I was able to take a directory and create a full path defining > > > all the entries in that directory. For example, in directory lib, I > > have > > > jars: > > > -test1.jar > > > -test2.jar > > > -test3.jar. I want to be able to create a path and set it as a > > property > > > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > > > > > Is this possible in Maven? > > > > > > Roshan > > > > > > - > > > 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] > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cheers, Stuart
Re: Gentoo Linux init.d script?
Definitely not Gentoo init script... V On 10/24/07, Hilco Wijbenga <[EMAIL PROTECTED]> wrote: > > Oops... > > I just realised I have changed the OS on my Maven/Continuum/Archiva > box ... it's no longer Gentoo but CentOS (the company uses RedHat by > default). So the init script I sent is for CentOS, not Gentoo. > > My apologies, I'll try to create an init script for Gentoo. > > Cheers, > Hilco >
release plugin and antrun task
hi, i want to use the release plugin like this: org.apache.maven.plugins maven-release-plugin antrun:run maven-antrun-plugin run hallo of course the ant task is something different in reality. It runs like this and doesn't execute the task: [...] [INFO] Executing: mvn antrun:run --no-plugin-updates -P production -DperformRelease=true ... [INFO]task-segment: [antrun:run] [INFO] [INFO] [antrun:run] [INFO] Executing tasks [INFO] Executed tasks [INFO] [INFO] BUILD SUCCESSFUL ... I guess i got to bind my antrun task to a special lifecycle, but which lifecycle? please help me. kind regards, janning - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [maven-idea-plugin] incorrect jar created after downloading test sources
Seems like you've found a few bugs. Check JIRA and if they are not
already posted, please do so. (The tests vs test one I've heard of so
it may already be posted.)
Thanks for your contributions.
Wayne
On 10/24/07, GONNOT boris <[EMAIL PROTECTED]> wrote:
> Hi guys,
>
> We have found two issues regarding the download of test sources from the
> remote repository.
>
> 1. "test vs tests" artifact source classifier for test
>
> This first issue actually involves several maven plugins whilst
> deploying an artifact.
>
> First of all, the maven-jar-plugin generates into the remote repository
> a file named xxx-tests.jar.
>
> Then the maven-source-plugin generates another file named
> xxx-test-sources.jar (notice that test doesn't ends with "s")
>
> Finally, the maven-idea-plugin tries to download the artifact called
> xxx-tests-sources.jar (which doesn't exist in the remote repository)
>
> It seems to us that there is a bit of confusion with the suffix of the
> classifier (test vs tests).
>
> Have you guys already noticed such behaviour?
>
>
> 2. Incorrect artifact sources download
>
> Once we have noticed the issue explained above, we have tried to fix by
> renaming the xxx-test-sources.jar into xxx-tests-sources.jar but the
> maven-idea-plugin downloaded the xxx-test-sources.jar with the contents
> of the actual sources from the artifact (xxx-sources.jar)
>
> The bug is located in the metod resolveClassifiedArtifact from the class
> IdeaModuleMojo. Below our fix to the problem (see the dirty fix line):
>
> Thanks
>
> Boris and Fede
>
> private String resolveClassifiedArtifact( Artifact artifact, String
> classifier )
> {
> String basePath = artifact.getFile().getAbsolutePath().replace(
> '\\', '/' );
> int delIndex = basePath.indexOf( ".jar" );
> if ( delIndex < 0 )
> {
> return null;
> }
>
> List remoteRepos =
> executedProject.getRemoteArtifactRepositories();
> try
> {
> // Dirty fix AGF: the classifier contains "tests-sources",
> we change it by "test-sources"
> String remoteClassifier = classifier;
> if ("tests".equals(artifact.getClassifier())) {
> remoteClassifier = "test-sources";
> delIndex -= 1; // remove s of 'tests'
> }
> Artifact classifiedArtifact =
> artifactFactory.createArtifactWithClassifier( artifact.getGroupId(),
>
> artifact.getArtifactId(),
>
> artifact.getVersion(),
>
> artifact.getType (),
>
> remoteClassifier );
> String dstFilename = basePath.substring( 0, delIndex ) + '-'
> + classifier + ".jar";
> // End of Dirty fix AGF
> File dstFile = new File( dstFilename );
> classifiedArtifact.setFile( dstFile );
> //this check is here because wagonManager does not seem to
> check if the remote file is newer
> //or such feature is not working
> if ( !dstFile.exists() )
> {
> wagonManager.getArtifact( classifiedArtifact,
> remoteRepos );
> }
> return dstFile.getAbsolutePath().replace( '\\', '/' );
> }
> catch ( TransferFailedException e )
> {
> getLog().debug( e );
> return null;
> }
> catch ( ResourceDoesNotExistException e )
> {
> getLog().debug( e );
> return null;
> }
> }
>
>
>
>
> --
> Ce message est protege par les regles relatives au secret des
> correspondances; il peut en outre contenir des informations a caractere
> confidentiel ou protegees par differentes regles et notamment le secret des
> affaires; il est etabli a destination exclusive de son destinataire. Toute
> divulgation, utilisation, diffusion ou reproduction (totale ou partielle) de
> ce message, ou des informations qu'il contient, doit etre prealablement
> autorisee.
> Tout message electronique est susceptible d'alteration et son integrite ne
> peut etre assuree. Les AGF declinent toute responsabilite au titre de ce
> message s'il a ete modifie ou falsifie.
> Si vous n'etes pas destinataire de ce message, merci de le detruire
> immediatement et d'avertir l'expediteur de l'erreur de distribution et de la
> destruction du message.
> This message is protected by the secrecy of correspondence rules;
> furthermore it may contain privileged or confidential information that is
> protected by law, notably by the secrecy of business relations rule; it is
> intended solely for the attention of the addressee. Any disclosure, use,
> dissemination or reproduction (either whole or partial) of this message or
> the information contained herein is strictly prohibited without prior
> consent.
> Any electronic message is susceptible to alteration and its integrity can
> not be assured. AGF declines any responsibility for this message in the
> event of alteration or falsification.
> If you are not th
Re: Gentoo Linux init.d script?
Oops... I just realised I have changed the OS on my Maven/Continuum/Archiva box ... it's no longer Gentoo but CentOS (the company uses RedHat by default). So the init script I sent is for CentOS, not Gentoo. My apologies, I'll try to create an init script for Gentoo. Cheers, Hilco
[maven-idea-plugin] incorrect jar created after downloading test sources
Hi guys,
We have found two issues regarding the download of test sources from the
remote repository.
1. "test vs tests" artifact source classifier for test
This first issue actually involves several maven plugins whilst
deploying an artifact.
First of all, the maven-jar-plugin generates into the remote repository
a file named xxx-tests.jar.
Then the maven-source-plugin generates another file named
xxx-test-sources.jar (notice that test doesn't ends with "s")
Finally, the maven-idea-plugin tries to download the artifact called
xxx-tests-sources.jar (which doesn't exist in the remote repository)
It seems to us that there is a bit of confusion with the suffix of the
classifier (test vs tests).
Have you guys already noticed such behaviour?
2. Incorrect artifact sources download
Once we have noticed the issue explained above, we have tried to fix by
renaming the xxx-test-sources.jar into xxx-tests-sources.jar but the
maven-idea-plugin downloaded the xxx-test-sources.jar with the contents
of the actual sources from the artifact (xxx-sources.jar)
The bug is located in the metod resolveClassifiedArtifact from the class
IdeaModuleMojo. Below our fix to the problem (see the dirty fix line):
Thanks
Boris and Fede
private String resolveClassifiedArtifact( Artifact artifact, String
classifier )
{
String basePath = artifact.getFile().getAbsolutePath().replace(
'\\', '/' );
int delIndex = basePath.indexOf( ".jar" );
if ( delIndex < 0 )
{
return null;
}
List remoteRepos =
executedProject.getRemoteArtifactRepositories();
try
{
// Dirty fix AGF: the classifier contains "tests-sources",
we change it by "test-sources"
String remoteClassifier = classifier;
if ("tests".equals(artifact.getClassifier())) {
remoteClassifier = "test-sources";
delIndex -= 1; // remove s of 'tests'
}
Artifact classifiedArtifact =
artifactFactory.createArtifactWithClassifier( artifact.getGroupId(),
artifact.getArtifactId(),
artifact.getVersion(),
artifact.getType (),
remoteClassifier );
String dstFilename = basePath.substring( 0, delIndex ) + '-'
+ classifier + ".jar";
// End of Dirty fix AGF
File dstFile = new File( dstFilename );
classifiedArtifact.setFile( dstFile );
//this check is here because wagonManager does not seem to
check if the remote file is newer
//or such feature is not working
if ( !dstFile.exists() )
{
wagonManager.getArtifact( classifiedArtifact,
remoteRepos );
}
return dstFile.getAbsolutePath().replace( '\\', '/' );
}
catch ( TransferFailedException e )
{
getLog().debug( e );
return null;
}
catch ( ResourceDoesNotExistException e )
{
getLog().debug( e );
return null;
}
}
--
Ce message est protege par les regles relatives au secret des correspondances;
il peut en outre contenir des informations a caractere confidentiel ou
protegees par differentes regles et notamment le secret des affaires; il est
etabli a destination exclusive de son destinataire. Toute divulgation,
utilisation, diffusion ou reproduction (totale ou partielle) de ce message, ou
des informations qu'il contient, doit etre prealablement autorisee.
Tout message electronique est susceptible d'alteration et son integrite ne peut
etre assuree. Les AGF declinent toute responsabilite au titre de ce message
s'il a ete modifie ou falsifie.
Si vous n'etes pas destinataire de ce message, merci de le detruire
immediatement et d'avertir l'expediteur de l'erreur de distribution et de la
destruction du message.
This message is protected by the secrecy of correspondence rules; furthermore
it may contain privileged or confidential information that is protected by law,
notably by the secrecy of business relations rule; it is intended solely for
the attention of the addressee. Any disclosure, use, dissemination or
reproduction (either whole or partial) of this message or the information
contained herein is strictly prohibited without prior consent.
Any electronic message is susceptible to alteration and its integrity can not
be assured. AGF declines any responsibility for this message in the event of
alteration or falsification.
If you are not the intended recipient, please destroy it immediately and notify
the sender of the wrong delivery and the mail deletion.
--
Maven profile properties
I am trying to get my profiles to use the properties specified by the
POM. Is this possible? I have a POM that looks like:
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";>
...
scripts/myScript.js
ruby
javascriptEngine
engine
javascript
jrubyEngine
engine
ruby
...
For some reason the jrubyEngine profile does not get activated. (I can
tell by which dependencies get copied) Do I have to use this syntax:
${project.properties.engine}?
Roshan
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: @requiresDependencyResolution, multi-project and reactor dependencies - a bug?
http://jira.codehaus.org/browse/MNG-2277 i unfortunately know it well. -Original Message- From: Alfie Kirkpatrick [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 10:23 AM To: users@maven.apache.org Subject: @requiresDependencyResolution, multi-project and reactor dependencies - a bug? Hi, we're using Maven 2.0.7 (same problem also seems to exist on 2.0.4). This seems like something so basic I'm hoping there is a simple explanation/workaround. What we're seeing is that some multi-project configurations succeed on 'mvn package' but fail on 'mvn generate-sources'. They are failing when one project in the reactor references another project in the reactor which is not installed in the local repo. It seems that the referenced project has not quite "made it" into the reactor this early in the phase lifecycle. But it does work correctly if you target a later phase at the outset which I find really confusing (my understanding was that Maven executes the phases in order, so the final phase chosen should not affect the execution of earlier phases??). The problem only occurs when a plugin binds itself to the generate-sources phase and has @requiresDependencyResolution, presumably because this is what triggers resolution of the referenced dependency too early in the lifecycle, and hence the error. We are seeing this problem when trying to run 'mvn eclipse:eclipse' because this only executes the generate-sources phase by default and we have other mojos which genuinely do generate source, such as java2wsdl. A workaround is to always run 'mvn install' before 'mvn eclipse:eclipse' to get all projects into the local repo. Another workaround is to run 'mvn package eclipse:eclipse' (voodoo!!). I have a sample multi-project and mojo to demonstrate this behaviour but you can see it easily with the antrun mojo and many others. Is this a bug - should I raise a JIRA on it? Many thanks, Alfie. Communications on or through ioko's computer systems may be monitored or recorded to secure effective system operation and for other lawful purposes. Unless otherwise agreed expressly in writing, this communication is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this communication, please contact the sender immediately. No employee is authorised to conclude any binding agreement on behalf of ioko with another party by e-mail without prior express written confirmation. ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Can't create global eclipse files with eclipse plugin for project with modules
Dear Jim, Probably didn't explain my problem correctly. In order to get an eclipse project as you say for the modules, you only need to invoke on command line: mvn eclipse:eclipse on the root project. My question is concerning to generate the eclipse configuration files for my root project that will contain the modules. You can do it by hand or using an Maven Eclipse Plugin (for eclipse IDE). My question is how to get this configuration using the given maven plugin. Hope now I have explained better, Thank any way, David - Original Message From: Jim Sellers <[EMAIL PROTECTED]> To: Maven Users List Sent: Wednesday, October 24, 2007 2:51:27 PM Subject: Re: Can't create global eclipse files with eclipse plugin for project with modules I don't think that you can create a "global eclipse project". For each of your modules you can make it look like a "project" in eclipse by going 1) right click 2) import 3) General / Existing Projects into Workspace 4) browse to your module 5) ** THIS IS THE IMPORTANT STEP** Make sure the "Copy projects into workspace" is NOT checked 6) finish This way you'll be able to work in the "eclipse way" and the "maven way". HTH Jim On 10/23/07, David <[EMAIL PROTECTED]> wrote: > > Dear members, > > I have the following directory structure: > project > --module1 > pom.xml > --module2 > pom.xml > --module3 > pom.xml > pom.xml > > when I run mvn eclipse:eclipse it generates eclipse files for each > submodule. Looking into the documentation of this plugins: > > http://maven.apache.org/plugins/maven-eclipse-plugin/ > > I don't see the way to configurate this behaviour. ¿Is there any shortcut > to create a global Eclipse project too? > > Thanks in advance, > > David > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Create Path
There are osgi plugins for Maven that you should probably look at before attempting to implement everything yourself manually. Google for "maven felix" and "maven osgi" to find them. Wayne On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> wrote: > Well I am trying to bundle an osgi bundle. And it needs a > Bundle-Classpath entry in the Manifest. This entry has to be a > comma-separated list of all the jars needed by the osgi bundle. I have > these jars downloaded using the > maven-dependency-plugin:copy-dependencies, but I cannot seem to figure > out how to get the path created. > > Roshan > > -Original Message- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 24, 2007 10:49 AM > To: Maven Users List > Subject: Re: Maven Create Path > > What are you trying to do that Maven isn't doing/can't do for you? > There may be a better way to approach this from a Maven perspective. > > Wayne > > On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > In Ant, I was able to take a directory and create a full path defining > > all the entries in that directory. For example, in directory lib, I > have > > jars: > > -test1.jar > > -test2.jar > > -test3.jar. I want to be able to create a path and set it as a > property > > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > > > Is this possible in Maven? > > > > Roshan > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Create Path
Don't loose time doing that by hand Use this Apache Felix plugin : http://cwiki.apache.org/FELIX/bundle-plugin-for-maven-bnd.html Good luck Damien 2007/10/24, Roshan A. Punnoose <[EMAIL PROTECTED]>: > Well I am trying to bundle an osgi bundle. And it needs a > Bundle-Classpath entry in the Manifest. This entry has to be a > comma-separated list of all the jars needed by the osgi bundle. I have > these jars downloaded using the > maven-dependency-plugin:copy-dependencies, but I cannot seem to figure > out how to get the path created. > > Roshan > > -Original Message- > From: Wayne Fay [mailto:[EMAIL PROTECTED] > Sent: Wednesday, October 24, 2007 10:49 AM > To: Maven Users List > Subject: Re: Maven Create Path > > What are you trying to do that Maven isn't doing/can't do for you? > There may be a better way to approach this from a Maven perspective. > > Wayne > > On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> > wrote: > > Hi, > > > > In Ant, I was able to take a directory and create a full path defining > > all the entries in that directory. For example, in directory lib, I > have > > jars: > > -test1.jar > > -test2.jar > > -test3.jar. I want to be able to create a path and set it as a > property > > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > > > Is this possible in Maven? > > > > Roshan > > > > - > > 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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
@requiresDependencyResolution, multi-project and reactor dependencies - a bug?
Hi, we're using Maven 2.0.7 (same problem also seems to exist on 2.0.4). This seems like something so basic I'm hoping there is a simple explanation/workaround. What we're seeing is that some multi-project configurations succeed on 'mvn package' but fail on 'mvn generate-sources'. They are failing when one project in the reactor references another project in the reactor which is not installed in the local repo. It seems that the referenced project has not quite "made it" into the reactor this early in the phase lifecycle. But it does work correctly if you target a later phase at the outset which I find really confusing (my understanding was that Maven executes the phases in order, so the final phase chosen should not affect the execution of earlier phases??). The problem only occurs when a plugin binds itself to the generate-sources phase and has @requiresDependencyResolution, presumably because this is what triggers resolution of the referenced dependency too early in the lifecycle, and hence the error. We are seeing this problem when trying to run 'mvn eclipse:eclipse' because this only executes the generate-sources phase by default and we have other mojos which genuinely do generate source, such as java2wsdl. A workaround is to always run 'mvn install' before 'mvn eclipse:eclipse' to get all projects into the local repo. Another workaround is to run 'mvn package eclipse:eclipse' (voodoo!!). I have a sample multi-project and mojo to demonstrate this behaviour but you can see it easily with the antrun mojo and many others. Is this a bug - should I raise a JIRA on it? Many thanks, Alfie. Communications on or through ioko's computer systems may be monitored or recorded to secure effective system operation and for other lawful purposes. Unless otherwise agreed expressly in writing, this communication is to be treated as confidential and the information in it may not be used or disclosed except for the purpose for which it has been sent. If you have reason to believe that you are not the intended recipient of this communication, please contact the sender immediately. No employee is authorised to conclude any binding agreement on behalf of ioko with another party by e-mail without prior express written confirmation. ioko365 Ltd. VAT reg 656 2443 31. Reg no 3048367. All rights reserved.
RE: Maven Create Path
Well I am trying to bundle an osgi bundle. And it needs a Bundle-Classpath entry in the Manifest. This entry has to be a comma-separated list of all the jars needed by the osgi bundle. I have these jars downloaded using the maven-dependency-plugin:copy-dependencies, but I cannot seem to figure out how to get the path created. Roshan -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 10:49 AM To: Maven Users List Subject: Re: Maven Create Path What are you trying to do that Maven isn't doing/can't do for you? There may be a better way to approach this from a Maven perspective. Wayne On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> wrote: > Hi, > > In Ant, I was able to take a directory and create a full path defining > all the entries in that directory. For example, in directory lib, I have > jars: > -test1.jar > -test2.jar > -test3.jar. I want to be able to create a path and set it as a property > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > Is this possible in Maven? > > Roshan > > - > 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]
mvn dependency:unpack ignoring outputdirectory
I'm having trouble getting "mvn dependency:unpack" to use the outputDirectory I specify. The zip file is being unpacked but in a dependency subdirectory. I can get the outputdirectory to work fine for regular files with mvn dependency:copy. Is this something that just doesn't work or am I doing it wrong? --- Cynthia Libby Senior SCM Engineer 5601 Headquarters Drive Plano, TX 75024-2262 214-387-2573 x72573 [EMAIL PROTECTED]
Re: Need to remove $USER_HOME\.m2 in order to work
Next time you get that error message, instead of deleting your .m2 directory, try adding -U to your mvn call eg mvn -U package. Wayne On 10/24/07, Java World <[EMAIL PROTECTED]> wrote: > Hi, > > Most of the time when i working wit maven2 it says it cand find plug-ins > (like org.apache.maven.plugins:maven-compiler-plugin' does not exist or no > valid version could be found. etc ) No firewall. But when i remove > $USER_HOME\.m2 it works fine by downloding plug-ins. Can anyone tell me why > this happens? > > Thanks & BRegards > Chandana. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven Create Path
What are you trying to do that Maven isn't doing/can't do for you? There may be a better way to approach this from a Maven perspective. Wayne On 10/24/07, Roshan A. Punnoose <[EMAIL PROTECTED]> wrote: > Hi, > > In Ant, I was able to take a directory and create a full path defining > all the entries in that directory. For example, in directory lib, I have > jars: > -test1.jar > -test2.jar > -test3.jar. I want to be able to create a path and set it as a property > like: lib/test1.jar, lib/test2.jar, lib/test3.jar. > > Is this possible in Maven? > > Roshan > > - > 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: RE: Protection of Already Deploy Artifacts
This is at least a prospect. I thought somebody else should also have this problem. Thank you, Leslie -Original Message- From: ext Brian E. Fox [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 2:27 PM To: Maven Users List Subject: RE: Protection of Already Deploy Artifacts There is work occurring on the deploy plugin to not overwrite existing release artifacts by default. -Original Message- From: Nicole Lacoste [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 8:21 AM To: Maven Users List Subject: Re: Protection of Already Deploy Artifacts You might want to look into cutting a real release. You only have your artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release plugin to cut release in non snapshot version (1.0). The release prepare goal creates the 1.0 version and tags the source code in your scm. You then create the 1.0 version using the perform goal. You can repeat the perform goal as many times as you like, which means even if someone deletes 1.0 or corrupts it some other way you can always re-perform the release. Niki On 24/10/2007, Olivier Dehon <[EMAIL PROTECTED]> wrote: > You can set the files to read-only in the file system. > > -Olivier > > Leder, Leslie (NSN - DE/Greifswald) wrote: > > Hello, > > assume there is a module A already deployed in version 1.0. Now somebody > > changed the code of module A but forgot to increment the version so it > > still is 1.0. > > So the second version of component A is definitely not ok. But how can I > > protect the correct version 1.0 of component A than? The way it works I > > know is that the deploy plugin would just overwrite the correct artifact > > by the newer but incorrect one. Is this really ok. This would double me > > fault score to two. Now I haven't only an attempted version 1.1 but I > > also haven't a real 1.0 anymore. > > Is there any chance to let Maven2 check if the artifact that is > > currently to be deployed differs in size and/or checksum to an already > > deployed artifact in the target repository with exactly the same Maven > > coordinates (groupId, artifactId, classifier, version, type). > > > > Thanks, > > Leslie > > > > > > > - > 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]
Maven Create Path
Hi, In Ant, I was able to take a directory and create a full path defining all the entries in that directory. For example, in directory lib, I have jars: -test1.jar -test2.jar -test3.jar. I want to be able to create a path and set it as a property like: lib/test1.jar, lib/test2.jar, lib/test3.jar. Is this possible in Maven? Roshan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: RE: Protection of Already Deploy Artifacts
I know this one. But for that I would need to change a lot in the SVN structure which is currently standard conform. Probably this is a fault. But at the end it is somehow like saying: Don't deal with the fault but uses this tool that prevents you from making this fault. There is always somebody in the project who does it in the wrong way. And than there is a hidden fault which could be there for quite a while until discovery. -Original Message- From: ext Nicole Lacoste [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 2:21 PM To: Maven Users List Subject: Re: Protection of Already Deploy Artifacts You might want to look into cutting a real release. You only have your artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release plugin to cut release in non snapshot version (1.0). The release prepare goal creates the 1.0 version and tags the source code in your scm. You then create the 1.0 version using the perform goal. You can repeat the perform goal as many times as you like, which means even if someone deletes 1.0 or corrupts it some other way you can always re-perform the release. Niki On 24/10/2007, Olivier Dehon <[EMAIL PROTECTED]> wrote: > You can set the files to read-only in the file system. > > -Olivier > > Leder, Leslie (NSN - DE/Greifswald) wrote: > > Hello, > > assume there is a module A already deployed in version 1.0. Now somebody > > changed the code of module A but forgot to increment the version so it > > still is 1.0. > > So the second version of component A is definitely not ok. But how can I > > protect the correct version 1.0 of component A than? The way it works I > > know is that the deploy plugin would just overwrite the correct artifact > > by the newer but incorrect one. Is this really ok. This would double me > > fault score to two. Now I haven't only an attempted version 1.1 but I > > also haven't a real 1.0 anymore. > > Is there any chance to let Maven2 check if the artifact that is > > currently to be deployed differs in size and/or checksum to an already > > deployed artifact in the target repository with exactly the same Maven > > coordinates (groupId, artifactId, classifier, version, type). > > > > Thanks, > > Leslie > > > > > > > - > 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: Re: Protection of Already Deploy Artifacts
I thought about this also. But this is where story becomes more complicated. Actualy the module is part of a multi-module project. As long as the code does not change the result hopefully will also not change. Repeated build and deployment in the context of an multi-module project is fine so far als long as code and version change consistently. But this is a bit error prone. It's quite easy to forget to update one out of many modules versions. for example: my project has module A-1.0 and B-1.0 without dependencies step1: deploy A-1.0, B-1.0 step2: change B-1.0 to B-1.1 and keep A-1.0 unchanged step3: deploy A-1.0 (again but ok), B-1.1 setp4: change B-1.1 to B-1.2 and modify A-1.0 but forget to update the version step5: deploy A-1.0 (again but this is not ok because the intended A-1.1 is currupt), B-1.2 So I could not protect the artifact by just make it readonly. Because in case it is exactly the same it should be redeployed or skipped. In case it is different but has identical coordinats it should not be deployed. Leslie -Ursprüngliche Nachricht- Von: ext Olivier Dehon [mailto:[EMAIL PROTECTED] Gesendet: Wednesday, October 24, 2007 2:05 PM An: Maven Users List Betreff: Re: Protection of Already Deploy Artifacts You can set the files to read-only in the file system. -Olivier Leder, Leslie (NSN - DE/Greifswald) wrote: > Hello, > assume there is a module A already deployed in version 1.0. Now somebody > changed the code of module A but forgot to increment the version so it > still is 1.0. > So the second version of component A is definitely not ok. But how can I > protect the correct version 1.0 of component A than? The way it works I > know is that the deploy plugin would just overwrite the correct artifact > by the newer but incorrect one. Is this really ok. This would double me > fault score to two. Now I haven't only an attempted version 1.1 but I > also haven't a real 1.0 anymore. > Is there any chance to let Maven2 check if the artifact that is > currently to be deployed differs in size and/or checksum to an already > deployed artifact in the target repository with exactly the same Maven > coordinates (groupId, artifactId, classifier, version, type). > > Thanks, > Leslie > > - 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: Can't create global eclipse files with eclipse plugin for project with modules
I don't think that you can create a "global eclipse project". For each of your modules you can make it look like a "project" in eclipse by going 1) right click 2) import 3) General / Existing Projects into Workspace 4) browse to your module 5) ** THIS IS THE IMPORTANT STEP** Make sure the "Copy projects into workspace" is NOT checked 6) finish This way you'll be able to work in the "eclipse way" and the "maven way". HTH Jim On 10/23/07, David <[EMAIL PROTECTED]> wrote: > > Dear members, > > I have the following directory structure: > project > --module1 > pom.xml > --module2 > pom.xml > --module3 > pom.xml > pom.xml > > when I run mvn eclipse:eclipse it generates eclipse files for each > submodule. Looking into the documentation of this plugins: > > http://maven.apache.org/plugins/maven-eclipse-plugin/ > > I don't see the way to configurate this behaviour. ¿Is there any shortcut > to create a global Eclipse project too? > > Thanks in advance, > > David > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
RE: Protection of Already Deploy Artifacts
There is work occurring on the deploy plugin to not overwrite existing release artifacts by default. -Original Message- From: Nicole Lacoste [mailto:[EMAIL PROTECTED] Sent: Wednesday, October 24, 2007 8:21 AM To: Maven Users List Subject: Re: Protection of Already Deploy Artifacts You might want to look into cutting a real release. You only have your artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release plugin to cut release in non snapshot version (1.0). The release prepare goal creates the 1.0 version and tags the source code in your scm. You then create the 1.0 version using the perform goal. You can repeat the perform goal as many times as you like, which means even if someone deletes 1.0 or corrupts it some other way you can always re-perform the release. Niki On 24/10/2007, Olivier Dehon <[EMAIL PROTECTED]> wrote: > You can set the files to read-only in the file system. > > -Olivier > > Leder, Leslie (NSN - DE/Greifswald) wrote: > > Hello, > > assume there is a module A already deployed in version 1.0. Now somebody > > changed the code of module A but forgot to increment the version so it > > still is 1.0. > > So the second version of component A is definitely not ok. But how can I > > protect the correct version 1.0 of component A than? The way it works I > > know is that the deploy plugin would just overwrite the correct artifact > > by the newer but incorrect one. Is this really ok. This would double me > > fault score to two. Now I haven't only an attempted version 1.1 but I > > also haven't a real 1.0 anymore. > > Is there any chance to let Maven2 check if the artifact that is > > currently to be deployed differs in size and/or checksum to an already > > deployed artifact in the target repository with exactly the same Maven > > coordinates (groupId, artifactId, classifier, version, type). > > > > Thanks, > > Leslie > > > > > > > - > 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]
Need to remove $USER_HOME\.m2 in order to work
Hi, Most of the time when i working wit maven2 it says it cand find plug-ins (like org.apache.maven.plugins:maven-compiler-plugin' does not exist or no valid version could be found. etc ) No firewall. But when i remove $USER_HOME\.m2 it works fine by downloding plug-ins. Can anyone tell me why this happens? Thanks & BRegards Chandana. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Protection of Already Deploy Artifacts
You might want to look into cutting a real release. You only have your artifacts in snapshot versions (1.0-SNAPSHOT) and use the maven release plugin to cut release in non snapshot version (1.0). The release prepare goal creates the 1.0 version and tags the source code in your scm. You then create the 1.0 version using the perform goal. You can repeat the perform goal as many times as you like, which means even if someone deletes 1.0 or corrupts it some other way you can always re-perform the release. Niki On 24/10/2007, Olivier Dehon <[EMAIL PROTECTED]> wrote: > You can set the files to read-only in the file system. > > -Olivier > > Leder, Leslie (NSN - DE/Greifswald) wrote: > > Hello, > > assume there is a module A already deployed in version 1.0. Now somebody > > changed the code of module A but forgot to increment the version so it > > still is 1.0. > > So the second version of component A is definitely not ok. But how can I > > protect the correct version 1.0 of component A than? The way it works I > > know is that the deploy plugin would just overwrite the correct artifact > > by the newer but incorrect one. Is this really ok. This would double me > > fault score to two. Now I haven't only an attempted version 1.1 but I > > also haven't a real 1.0 anymore. > > Is there any chance to let Maven2 check if the artifact that is > > currently to be deployed differs in size and/or checksum to an already > > deployed artifact in the target repository with exactly the same Maven > > coordinates (groupId, artifactId, classifier, version, type). > > > > Thanks, > > Leslie > > > > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > >
Re: XML-RPC 1.1: getProjects/getAllProjectGroupsWithProjects vs getProject
Banck, Arent-Jan a écrit : Hi, Trying out the XML-RPC client from the trunk. When using XML-RPC API getAllProjectGroupsWithProjects and getProjects, the projects returned do not have al fields set. Parent, dependencies, developers, notifiers are null. the projects list returned by getAllProjectGroupsWithProjects and getProjects is a List, if you use a List, it is normal to have some null values because all datas of Project class aren't populated. Not sure what it should be: Either this is a bug and these fields should be set, or these methods have incorrect names and should be something like getProjectSummaries / getAllProjectGroupsWithProjectSummaries yes, maybe we'll need to rename them or use java5 type notation in the client. There is a method called getProjectWithAllDetails, this is also confusing: If I don't want details I would use getProjectSummaries. The difference between a project-without-details and a project-summary is unclear to me. a project summary is a project without details (notifiers, dependencies, parent, build results, build definitions) Emmanuel What is the intended design for this API in this area? Regards, Arent-Jan
Re: Protection of Already Deploy Artifacts
You can set the files to read-only in the file system. -Olivier Leder, Leslie (NSN - DE/Greifswald) wrote: Hello, assume there is a module A already deployed in version 1.0. Now somebody changed the code of module A but forgot to increment the version so it still is 1.0. So the second version of component A is definitely not ok. But how can I protect the correct version 1.0 of component A than? The way it works I know is that the deploy plugin would just overwrite the correct artifact by the newer but incorrect one. Is this really ok. This would double me fault score to two. Now I haven't only an attempted version 1.1 but I also haven't a real 1.0 anymore. Is there any chance to let Maven2 check if the artifact that is currently to be deployed differs in size and/or checksum to an already deployed artifact in the target repository with exactly the same Maven coordinates (groupId, artifactId, classifier, version, type). Thanks, Leslie - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: adding a maven 2.0 project to continuum
Ionut S a écrit : Then maybe I'm doing something wrong, cause I just downloaded a clean 1.0.3 version and, after I added the pom.xml file continuum created me all the subprojects in it.. As I explained in my previous mail, it's in 1.1, not 1.0.3, that you can add only the parent project. Anyway.. is there a place where I can see a usual procedure for branching a project ? I googled for a while, but couldn't find something relevant. To add a project from a branch is similar to add a project from a trunk in continuum. Modify all versions in your branch, set correctly the scm URLs and add your project in continuum Emmanuel Emmanuel Venisse <[EMAIL PROTECTED]> wrote: With 1.0.3, all projects are added as single project and the build definition is configured to run in non recursive mode. - Remove all your sub projects in Continuum - Update the build definition of your parent project by removing the non recursive parameter In 1.1, we have an option the don't add sub-modules in the Add Project page Emmanuel Ionut S a écrit : Hi guys, I'm trying to add a maven 2.0 project to continuum 1.0.3. First I gave it a link to my pom.xml file (which contains modules) and it created projects for each module inside my pom. This was correct although not what I wanted (I learned that the hard way - when I read the documentation later I found out it was supposed to do that). Anyway, what I want is a single project which builds all the modules, not a project for each module.. Can you let me know how to do that, please ? I looked for some documentation but couldn't find anything.. Also, we are trying to understand how to handle branches within continuum.. Can anyone point me to a documentation, please ? Thank you. __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Re: Gentoo Linux init.d script?
http://people.apache.org/~evenisse/continuum_1.1_site/documentation/1_1/installation/standalone.html#In_a_Gentoo_system I think we need more informations like the chkconfig command or something else. Can you provide the text or create a patch? The source of this page is there: http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site/src/site/apt/documentation/1_1/installation/standalone.apt Emmanuel Hilco Wijbenga a écrit : On 10/23/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: I'll create a page for the site with your script. you'll can review it? Sure, just let me know where and when.
Re: Trying to setup a Maven Shared Repository
I downloaded 1.2.2-rc0 and I can browse http://:8081/artifactory. But I still receive the same error through Maven. Is there any other configuration that needs to be done through the tool or Maven besides modifying the mirror settings in Maven's settings.xml. Yoav Landman wrote: > > The URL that should be browsable from the UI with the out-of-the-box > installation is: http://:8081/artifactory > I'd also suggest you use 1.2.5-rc1, instead of rc-0. > You might want to take this to the artifactory-users list... > > > charliec wrote: >> >> Hello, >> I downloaded artifactory and executed the batch script artifactory.bat to >> start it. I added the following to the settings.xml file: >> >> artifactory >> * >> http://:8081/artifactory/repo >> Artifactory >> >> However, when I execute Maven, I still receive the following error: >> Caused by: java.io.IOException: Server returned HTTP response code: 503 >> for URL: >> >> http://:8081/artifactory/repo/org/apache/maven/plugins/maven-resource >> s-plugin/maven-metadata.xml >> >> I noticed the machine that when I try to bring up >> http://:8081 on the machine that has artifactory installed, >> I receive the following message: >> >> No context on this server matched or handled this request. >> Contexts known to this server are: >> /artifactory ---> >> [EMAIL >> PROTECTED]/artifactory,jar:file:/D:/artifactory-1.2.5-rc0/webapps/artifactory.war!/} >> >> >> The documentation for artifactory says to set up maven to use artifactory >> proxy, just configure a maven repository with the following URL: >> http://[your server name]:[port]/artifactory/repo >> >> What do I need to accomplish this? Thanks. >> >> >> >> mmistroni wrote: >>> >>> Hello, >>> i m trying to do same with artifactory.. worked fine so far.. i >>> recommend u >>> have a look at that >>> >>> regards >>> marco >>> >>> On 10/23/07, Wayne Fay <[EMAIL PROTECTED]> wrote: Simply putting an HTTP server on top of your personal .m2 directory (local repo cache) is not sufficient. The metadata in a real Maven repo is different than what is in your private local repo cache. Please look at Archiva, Proximity, Artifactory, etc for a "real" Maven repo solution. Wayne On 10/23/07, charliec <[EMAIL PROTECTED]> wrote: > > Hello, > I'm trying to setup a shared repository that mirrors the central repository > so other team members can download from this repository instead of accessing > the central. I've created a Virtaul Directory in IIS that points to my .m2 > repository. I can access this repostory on another machine via the browser > using url such as the following: http:///repository. On the > other machine, I added the following to my pom.xml file: > > > central > http:///repository > name>Maven Repository Manager running on repo.company.com > > > > >central >IMaven Repository Manager running on repo.company.com >http:///repository > > > > When I run mvn install, I receive the error below. It doesn't even try to > access the shared repository. Please help. Any assistance would be greatly > appreciated. Thanks. > > > + Error stacktraces are turned on. > Maven version: 2.0.7 > Java version: 1.5.0_12 > OS name: "windows xp" version: "5.1" arch: "x86" > [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and > Settin > gs\COSS\.m2\plugin-registry.xml' > [DEBUG] Building Maven global-level plugin registry from: > 'C:\maven-2.0.7\conf\p > lugin-registry.xml' > [INFO] Scanning for projects... > [INFO] > - > --- > [INFO] Building my-app > [INFO]task-segment: [install] > [INFO] > - > --- > [INFO] artifact org.apache.maven.plugins:maven-resources-plugin:checking > for up > dates from central > [WARNING] repository metadata for: 'artifact > org.apache.maven.plugins:maven-reso > urces-plugin' could not be retrieved from repository: central due to an > error: E > rror transferring file > [INFO] Repository 'central' will be blacklisted > [DEBUG] Exception > org.apache.maven.wagon.TransferFailedException: Error transferring file > at > org.apache.maven.wagon.providers.http.LightweightHttpWagon.fillInputD > ata(LightweightHttpWagon.java:104) > at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:68) > at > org.apache.maven.arti
Re: Protection of Already Deploy Artifacts
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi, I don't think this is currently possible; I would investigate using the release plugin though, as this ensures that versions are always incremented. Cheers, Johan Leder, Leslie (NSN - DE/Greifswald) wrote: > Hello, > assume there is a module A already deployed in version 1.0. Now somebody > changed the code of module A but forgot to increment the version so it > still is 1.0. > So the second version of component A is definitely not ok. But how can I > protect the correct version 1.0 of component A than? The way it works I > know is that the deploy plugin would just overwrite the correct artifact > by the newer but incorrect one. Is this really ok. This would double me > fault score to two. Now I haven't only an attempted version 1.1 but I > also haven't a real 1.0 anymore. > Is there any chance to let Maven2 check if the artifact that is > currently to be deployed differs in size and/or checksum to an already > deployed artifact in the target repository with exactly the same Maven > coordinates (groupId, artifactId, classifier, version, type). > > Thanks, > Leslie > - -- you too? -BEGIN PGP SIGNATURE- Version: GnuPG v1.4.6 (GNU/Linux) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org iD8DBQFHHyst1Tv8wj7aQ34RApX8AKCPYxQQDllYI/h2+Z+39sf9qYGVJgCcCuv4 qAqtVt8fYksX8/3dKil6Rks= =AgME -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: adding a maven 2.0 project to continuum
Then maybe I'm doing something wrong, cause I just downloaded a clean 1.0.3 version and, after I added the pom.xml file continuum created me all the subprojects in it.. Anyway.. is there a place where I can see a usual procedure for branching a project ? I googled for a while, but couldn't find something relevant. Emmanuel Venisse <[EMAIL PROTECTED]> wrote: With 1.0.3, all projects are added as single project and the build definition is configured to run in non recursive mode. - Remove all your sub projects in Continuum - Update the build definition of your parent project by removing the non recursive parameter In 1.1, we have an option the don't add sub-modules in the Add Project page Emmanuel Ionut S a écrit : > Hi guys, > I'm trying to add a maven 2.0 project to continuum 1.0.3. First I gave it a > link to my pom.xml file (which contains modules) and it created projects for > each module inside my pom. This was correct although not what I wanted (I > learned that the hard way - when I read the documentation later I found out > it was supposed to do that). > > Anyway, what I want is a single project which builds all the modules, not a > project for each module.. Can you let me know how to do that, please ? I > looked for some documentation but couldn't find anything.. > > Also, we are trying to understand how to handle branches within continuum.. > Can anyone point me to a documentation, please ? > > Thank you. > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com
Protection of Already Deploy Artifacts
Hello, assume there is a module A already deployed in version 1.0. Now somebody changed the code of module A but forgot to increment the version so it still is 1.0. So the second version of component A is definitely not ok. But how can I protect the correct version 1.0 of component A than? The way it works I know is that the deploy plugin would just overwrite the correct artifact by the newer but incorrect one. Is this really ok. This would double me fault score to two. Now I haven't only an attempted version 1.1 but I also haven't a real 1.0 anymore. Is there any chance to let Maven2 check if the artifact that is currently to be deployed differs in size and/or checksum to an already deployed artifact in the target repository with exactly the same Maven coordinates (groupId, artifactId, classifier, version, type). Thanks, Leslie
[ANN] Maven War Plugin 2.1-alpha-1 released!
The Maven team is pleased to announce the release of the Maven WAR Plugin, version 2.1 alpha 1. This release brings a significant refactoring of the packaging codebase with an improved overlay handling (both zip and war artifacts are now handled). For more information, check the web site: http://maven.apache.org/plugins/maven-war-plugin/ Release Notes - Maven 2.x War Plugin - Version 2.1-alpha-1 ** Bug * [MWAR-66] - No control over war overlay order * [MWAR-69] - Secondary artifacts aren't being attached * [MWAR-72] - Need ability to protect (or exclude) resource from being destroyed during war overlay. * [MWAR-75] - Documentation bugs on http://maven.apache.org/plugins/maven-war-plugin/usage.html * [MWAR-78] - War overlay can overwrite files in dependant war artifact * [MWAR-79] - copy fails in a multi-project build * [MWAR-88] - typos in documentation * [MWAR-90] - Documentation has a typo. * [MWAR-91] - Dependency as type=test-jar and scope=compile not included in WEB-INF/lib on packaging. * [MWAR-92] - Bad xml in sample documentation on website * [MWAR-122] - tests failing in trunk on windows * [MWAR-123] - filtering with @ is working randomly ** Improvement * [MWAR-104] - handle zip dependencies in war plugin * [MWAR-119] - Update plexus-utils to 1.2 ** New Feature * [MWAR-93] - Add the ability to provide a mapping for libraries copied in WEB-INF/lib (outputFileNameMapping) * [MWAR-97] - War plugin and Overlays handling ** Wish * [MWAR-76] - Allow Axis2 archives (.aar files) to be imported into WEB-INF/services directory We expect to release other alphas in the coming week so stay tuned. Enjoy! - The Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dependency understanding problem
Michael McCallum-3 wrote: > > I think the ultimate goal is that any artifact should be able to be > checked > out and built without the need to install anything... > That's my goal exactly. I'm trying to figure out if I can get maven to build every module by automatically installing/updating all other modules it depends on. My question is: is it possible to compile and build single modules just by specifying dependencys on other modules/projects? Or do these other modules have to be jar-packaged first? Because it seems to me that all dependencies have to be given in the form of jar's. Wayne Fay wrote: > > If these are all part of the same larger project, then you should > probably have a parent pom with specified. Then when you > build from the top parent, Maven figures out the correct build graph > and things Just Work. > I go that going, but the project is rather large and I'm trying to avoid having to build the whole project every time I change a single module. thanx for your replies Michael McCallum-3 wrote: > > I think the ultimate goal is that any artifact should be able to be > checked > out and built without the need to install anything... > > that provides the least cost entry point for a new developer to being able > to > participate in a systems development... > > look at the way the xorg project has broken itself down... kde too... they > are > moving in the oposite direction from monolithic build... you want to allow > a > developer to pickup a small well defined piece of code and be able to fix > it/change it test it and verify it without having to necessarily have a > full > understanding of the system > > On Wednesday 24 October 2007 04:31, Wayne Fay wrote: >> You've got to start at the beginning. Go to the simplest jar that has >> the fewest dependencies, build it, and install it (mvn install). >> >> Then go to the next one (that probably has a dependency on the first >> one) and do the same. Rinse and repeat until all jars build and are >> installed. >> >> If these are all part of the same larger project, then you should >> probably have a parent pom with specified. Then when you >> build from the top parent, Maven figures out the correct build graph >> and things Just Work. >> >> Wayne >> >> On 10/23/07, Danni <[EMAIL PROTECTED]> wrote: >> > Hi All, >> > I am new to maven. I want to use it to get some kind of versioning >> system >> > going for our multi-project application. >> > So far everything went smooth, but now i'm getting to the point where i >> > want to build jars for single projects which depend on other projects. >> My >> > question is: >> > >> > how do i declare a dependency on another project instead of on a >> > jar-file? >> > >> > it seems to me maven is always looking for jars, which cant be built >> > because other jars are missing to compile and package them: >> > >> > Compiler output: >> > Missing: >> > -- >> > 1) net.tvrl.:burancore2:jar:0.1.1.1 >> > >> > >> > with POM entry: >> > >> > >> > net.tvrl >> > burancore2 >> > 0.1.1.1 >> > >> > >> > >> > Of Course the Compiler cant find that jar, because it hasnt been >> created >> > yet. To create it, the burancore is dependent on other jars, which >> > themselves don't exist. >> > frustrating. >> > Can anyone help? >> > >> > Thx >> > >> > >> > -- >> > View this message in context: >> > >> http://www.nabble.com/Dependency-understanding-problem-tf4677961s177.html >> >#a13365897 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] > > -- > Michael McCallum > Enterprise Engineer > mailto:[EMAIL PROTECTED] > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > > -- View this message in context: http://www.nabble.com/Dependency-understanding-problem-tf4677961s177.html#a13380702 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Problems using a customized javadoc plugin from custom repository
Hi, I'm trying to work around http://jira.codehaus.org/browse/MJAVADOC-157 so I have checked out the maven-javadoc-plugin sources and tweaked it so it works for building my site. I have added the necessary into to deploy my patched m-j-p to my custom repo and deployed it. The site runs on our CI server which must be able to download the patched m-j-p from our custom repo. This works fine but when I run the site, I get the following error message: [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error getting reports from the plugin 'org.apache.maven.plugins:maven-javadoc-plugin': Unable to find the mojo 'org.apache.maven.plugins:maven-javadoc-plugin:2.4-MULE-586296:javadoc' in the plugin 'org.apache.maven.plugins:maven-javadoc-plugin' org/apache/maven/doxia/siterenderer/RendererException No, running with -X -e does not come up with any more helpful info either. I have searched the archive and found various threads with "unable to find the mojo" which generally seems to be solved by removing the plugin in question from the local repo. I did this and I even ran the build with a fresh local repo: the error remains the same. Any idea what could be wrong here? -dirk - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
