generate PDF site
For Maven 1, there was the PDF-plugin to export the site into PDF-format. What is the replacement for Maven 2? The Doxia-docs are not very straightforward... -- View this message in context: http://www.nabble.com/generate-PDF-site-tp20575798p20575798.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven copy jars from one folder to other apart using ant-plugin as i have already usedHi,
hi,
i have already used ant-run plugin a folloed
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idprepare-dependencies-repackage-copy/id
phasegenerate-resources/phase
goals
goalrun/goal
/goals
configuration
tasks
echoPartha88-${eim_home}/echo
copy todir=${project.build.directory}/dependency
overwrite=true
fileset dir=${eim_home} includes=*.xml /
/copy
copy..another copy function for some
jars/copy
/tasks
/configuration
/execution
/executions
/plugin
again i want to do some coy task after some command execution
(process-resource of dependancy and then war:war , and then want to do copy
task) . so if i am writting another ant plugin then it is not executing the
task. so i want another plug in which will do copy functionality.
or can we sub task generate-resources , so that i can execute multiple
commands using generate-resources. if yes then whta is the syntax ?
--
View this message in context:
http://www.nabble.com/maven-copy-jars-from-one-folder-to-other-apart-using-ant-plugin--as-i-have-already-usedHi%2C-tp20573263p20576179.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven copy jars from one folder to other apart using ant-plugin as i have already usedHi,
hi,
i have already used ant-run plugin a followed
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idprepare-dependencies-repackage-copy/id
phasegenerate-resources/phase
goals
goalrun/goal
/goals
configuration
tasks
echoPartha88-${eim_home}/echo
copy todir=${project.build.directory}/dependency
overwrite=true
fileset dir=${eim_home} includes=*.xml /
/copy
copy..another copy function for some
jars/copy
/tasks
/configuration
/execution
/executions
/plugin
again i want to do some coy task after some command execution
(process-resource of dependancy and then war:war , and then want to do copy
task) . so if i am writting another ant plugin then it is not executing the
task. so i want another plug in which will do copy functionality.
or can we sub task generate-resources , so that i can execute multiple
commands using generate-resources. if yes then whta is the syntax ?
--
View this message in context:
http://www.nabble.com/maven-copy-jars-from-one-folder-to-other-apart-using-ant-plugin--as-i-have-already-usedHi%2C-tp20573263p20576213.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why does Maven supress com.sun.image.codec.jpeg?
Hi, thanks for the replies. I checked the command On 19.11.2008, at 08:43, Geoffrey Wiseman [EMAIL PROTECTED] wrote: On Tue, Nov 18, 2008 at 6:59 AM, Juergen Lorenz Simon [EMAIL PROTECTED] wrote: the underlined fail. What drives me insane is, that all of those classes reside in the java version's classes.jar. So why the extra treatment for the com.sun.XY classes? Fail in the Maven command-line, or somewhere else? Using Maven, Eclipse and m2eclipse, i've seen that happen and can talk about it, but if you're experiencing it at the Maven command-line compilation, then it's something different. - Geoffrey -- Geoffrey Wiseman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why does Maven supress com.sun.image.codec.jpeg?
Hi, thanks for the replies. I checked the command line and it worked out alright. So I went back to Eclipse and tried more things. After removing the JRE library and re-adding it, the problem vanished. I'm confused... Thanks :-) On 19.11.2008, at 08:43, Geoffrey Wiseman [EMAIL PROTECTED] wrote: On Tue, Nov 18, 2008 at 6:59 AM, Juergen Lorenz Simon [EMAIL PROTECTED] wrote: the underlined fail. What drives me insane is, that all of those classes reside in the java version's classes.jar. So why the extra treatment for the com.sun.XY classes? Fail in the Maven command-line, or somewhere else? Using Maven, Eclipse and m2eclipse, i've seen that happen and can talk about it, but if you're experiencing it at the Maven command-line compilation, then it's something different. - Geoffrey -- Geoffrey Wiseman - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven copy jars from one folder to other apart using ant-plugin as i have already usedHi,
use multiple executions
2008/11/19 partha_ctc [EMAIL PROTECTED]
hi,
i have already used ant-run plugin a followed
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-antrun-plugin/artifactId
version1.1/version
executions
execution
idprepare-dependencies-repackage-copy/id
phasegenerate-resources/phase
goals
goalrun/goal
/goals
configuration
tasks
echoPartha88-${eim_home}/echo
copy todir=${project.build.directory}/dependency
overwrite=true
fileset dir=${eim_home} includes=*.xml /
/copy
copy..another copy function for some
jars/copy
/tasks
/configuration
/execution
/executions
/plugin
again i want to do some coy task after some command execution
(process-resource of dependancy and then war:war , and then want to do copy
task) . so if i am writting another ant plugin then it is not executing the
task. so i want another plug in which will do copy functionality.
or can we sub task generate-resources , so that i can execute multiple
commands using generate-resources. if yes then whta is the syntax ?
--
View this message in context:
http://www.nabble.com/maven-copy-jars-from-one-folder-to-other-apart-using-ant-plugin--as-i-have-already-usedHi%2C-tp20573263p20576213.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Build error at site-plugin = The skin does not exist
I get this error if the central repository is not available when running the site command. In our environment, we use Artifactory with the mirrors setting. We have also disabled the central repository that is defined in the super pom. This prevents our builds from ever needing to go to the Internet for anything. Everything goes through Artifactory. For some reason I don't understand if you disable Central, this error occurs when running the maven site command. It's documented here: http://jira.codehaus.org/browse/MNG-3139 -Original Message- From: Ole Laurisch [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 8:59 AM To: users@maven.apache.org Subject: Build error at site-plugin = The skin does not exist Hi, I get this error today while making a build with the site plugin. Some Google search leads me to similar problems where it is said that a possible solution (or workaround) would be to add a site directory with a site.xml specifying the skin version. The thing is, that I don't have any site plugin customization. The site goal worked perfectly well for weeks and our pom.xml is unchanged since October 9th. Do you habe any idea what the cause of the problem is and how I can handle it? Thanks in advance, Ole Maven trace: [INFO] [site:site] [WARNING] No URL defined for the project - decoration links will not be resolved [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE -- Kommen Sie uns besuchen: Vom 18.-21.11. 2008 wird engram auf der Innovationsfläche des IT-Forums der Finanz Informatik in Frankfurt als Aussteller innovative Lösungen im Bereich IT vorstellen. Interessenten finden engram in der Halle 4.2, Frankfurter Messe. Wir freuen uns auf Ihren Besuch! engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using an internal central repository without changing settings.xml
Hello, We aren't using Eclipse, but we solved a similar problem by explicitly disabling Central, and enabling our own local repository in the project pom. Example below. repositories !-- Override and disable super-pom Central repository -- repository releases enabledfalse/enabled /releases snapshots enabledfalse/enabled /snapshots idcentral/id nameMaven Repository Switchboard/name urlhttp://repo1.maven.org/maven2/url /repository !-- Our Artifactory -- repository releases enabledtrue/enabled updatePolicyalways/updatePolicy /releases snapshots enabledtrue/enabled updatePolicyalways/updatePolicy /snapshots idour.artifactory/id nameOur Repository/name urlhttp://our/artifactory/repo//url /repository /repositories pluginRepositories !-- Override and disable super-pom Central repository -- pluginRepository releases enabledfalse/enabled /releases snapshots enabledfalse/enabled /snapshots idcentral/id nameMaven Plugin Repository/name urlhttp://repo1.maven.org/maven2/url /pluginRepository !-- Our Artifactory -- pluginRepository releases enabledtrue/enabled updatePolicyalways/updatePolicy /releases snapshots enabledtrue/enabled updatePolicyalways/updatePolicy /snapshots idour.artifactory/id nameOur Artifactory/name urlhttp://our/artifactory/repo//url /pluginRepository /pluginRepositories -Original Message- From: Todd Thiessen [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 11, 2008 12:27 PM To: users@maven.apache.org Subject: Using an internal central repository without changing settings.xml I have been looking into this for a couple of days and can't find the answer. I suspect it isn't possible but I think it will be best to ask those who can tell me definitively. I want to be able to define a project which only has access to an internally defined repository. Note I said project not user. Using the settings.xml to define my interal repository as the mirror to external ones I don't think is the right thing to do. Doing this makes the project unportable since all developers on the project would have to share the same settings.xml file. Bad mojo. I have tried modifying my POM file such that it overrides the central repo... like this: repositories repository idcentral/id urlhttp://myinteralrepo/url /repository /repositories pluginRepositories pluginRepository idcentral/id urlhttp://myinteralrepo/url /pluginRepository /pluginRepositories However, this does not seem to be sufficient. Most dependencies are coming from my local repo but not all and I can't figure out why some are not. Here is a snippet of maven output. url = http://myinteralrepo Downloading: http://myinteralrepo/org/apache/maven/plugins/maven-resources-plugin/2.2 /maven-resources-plugin-2.2.pom url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugins/1/m aven-plugins-1.pom 3K downloaded url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-parent/1/maven-pare nt-1.pom 6K downloaded What is special about the first artifact, maven-resources-pluggin-2.2, such that it comes from my internal repo but the others come from maven central? The only way that I have been completely successful in ensuring that all artifacts come from my internal repo is by making the appropriate changes to my settings.xml file. But as I have already mentioned, I don't wish to do this. Thoughts? --- Todd Thiessen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven copy jars from one folder to other apart using ant-plugin as i have already usedHi,
Hi , i have already using multiple executions. 1) ant-plugin phasegenerate-resources goalrun/goal executions execution-1 task copy jars/task taskcopy xml/task /execution execution-2 task copy war and properties file/task /execution if we have several execution statement , can i control the execution. /executions c:/ mvn i) generate-resources ,ii) process-resources , iii)war:war , iv)generate-resources = in this way i want to execute. comma(,) is given to distinguish between the commands. c:/ mvn generate-resources( it should execute execution1, not execute2 , here it will execute all execution tag) process-resources generate-resources( it will only do execution-2 , not again exection-1) , if i can control it in command prompt then ok. you might tell if we give package in another execution then it is ok , but if i give package in command it executes total pom.( so not using package goal). so , is their any other plugin then i can use it latter in stead of generate-resources or can i call a particular execution in generate-resources ? if yes then how ?( only for copy function i want in differnt plugin) i want to execute in command and one by one so that i get my target. i.s at last the created war should be copied to another location as i have to copy it using differnet plugin. is while dong step iv) above. -- View this message in context: http://www.nabble.com/maven-copy-jars-from-one-folder-to-other-apart-using-ant-plugin--as-i-have-already-usedHi%2C-tp20573263p20578130.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
modifying goals executed during release
Hi, Is there a mechanism to modify the goals executed during release:perform? We use the release plugin to manage regular builds to our QA environments, the release process itself is excellent however we'd like to remove documentation generation and deployment from these builds. For our more complex projects, the build time slows from 5 mins for install to 40 mins during release largely due to multi-module documentation generation. cheers, Nathan - Nathan Coast Global Rates Technology Deutsche Bank London Tel:+44 (0)20 754 70639 Mob: +44 (0)7910 639 627 - --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Why does Maven supress com.sun.image.codec.jpeg?
On Wed, Nov 19, 2008 at 4:52 AM, Juergen Lorenz Simon [EMAIL PROTECTED]wrote: Hi, thanks for the replies. I checked the command line and it worked out alright. So I went back to Eclipse and tried more things. After removing the JRE library and re-adding it, the problem vanished. I'm confused... Thanks :-) I haven't looked into it in great detail, but when a project is configured, it can have a JRE system library or an 'Execution Environment' system library. The latter comes with a lot of exclusions to remove the hidden elements. Beyond that, I can't tell you much - except that somehow you ended up with the execution environment system library. I did read a little about these but I've forgotten what I read, so I'll let you research them for yourself if you're interested. -- Geoffrey Wiseman
Re: maven copy jars from one folder to other apart using ant-plugin as i have already usedHi,
I'm sorry, I can neither decipher nor decode your use of grammar. -Stephen 2008/11/19 partha_ctc [EMAIL PROTECTED] Hi , i have already using multiple executions. 1) ant-plugin phasegenerate-resources goalrun/goal executions execution-1 task copy jars/task taskcopy xml/task /execution execution-2 task copy war and properties file/task /execution if we have several execution statement , can i control the execution. /executions c:/ mvn i) generate-resources ,ii) process-resources , iii)war:war , iv)generate-resources = in this way i want to execute. comma(,) is given to distinguish between the commands. c:/ mvn generate-resources( it should execute execution1, not execute2 , here it will execute all execution tag) process-resources generate-resources( it will only do execution-2 , not again exection-1) , if i can control it in command prompt then ok. you might tell if we give package in another execution then it is ok , but if i give package in command it executes total pom.( so not using package goal). so , is their any other plugin then i can use it latter in stead of generate-resources or can i call a particular execution in generate-resources ? if yes then how ?( only for copy function i want in differnt plugin) i want to execute in command and one by one so that i get my target. i.s at last the created war should be copied to another location as i have to copy it using differnet plugin. is while dong step iv) above. -- View this message in context: http://www.nabble.com/maven-copy-jars-from-one-folder-to-other-apart-using-ant-plugin--as-i-have-already-usedHi%2C-tp20573263p20578130.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven metadata documentation
Hello all, I would like to know if there is an official documentation about the format of the maven repositories, especially (and almost) regarding the format of the maven-metadata.xml files. best regards, Thierry Boileau - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Includes files in a war
Hello,
It's works with maven-dependency-plugin.
http://www.developpez.net/forums/d645553/java/edi-outils-java/maven/include-fichiers-war/#post3795257
plugin
artifactIdmaven-dependency-plugin/artifactId
version2.0/version
executions
execution
idcopy/id
phaseprepare-package/phase
goals
goalcopy/goal
/goals
configuration
artifactItems
artifactItem
groupIdfr.xxx/groupId
artifactIdactiClient/artifactId
version2.1.1.1/version
typejar/type
overWritetrue/overWrite
destFileNameactiClient.jar/destFileName
/artifactItem
/artifactItems
outputDirectory${project.build.directory}/${name}-${version}/lib/outputDirectory
/configuration
/execution
/executions
/plugin
Rémy.
Walid quot;joquot; Gedeon wrote:
Hello Rémy,
Take a look at this link from the maven-war-plugin site examples section:
http://maven.apache.org/plugins/maven-war-plugin/examples/adding-filtering-webresources.html
HTH --w
On Tue, Nov 18, 2008 at 2:54 PM, Rémy [EMAIL PROTECTED] wrote:
Hi,
I generate war files with Maven. I want to include jar files (applets) in
a
lib folder in the base repository. I don't know how doing that.
I've got this project structure :
|-- pom.xml
|-- lib
|`-- I want to put here the applets
`-- WEB-INF
|-- web.xml
`-- lib
I try with the antrun plugin, but I dont know how to acces the artefact
(applets) in the Maven repository.
I think it's possible doing that with war overlays, but isn't a shame to
generate a war with the applets.
Thanks.
Rémy.
--
View this message in context:
http://www.nabble.com/Includes-files-in-a-war-tp20560039p20560039.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Includes-files-in-a-war-tp20560039p20577430.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Antwort: RE: Build error at site-plugin = The skin does not exist
I don't know exactly why, but the problem has disappeared as silent as it came. We are using nexus as a repository manager and yesterday I had another problem with its repositories. Maybe the fix of that problem has fixed the build problem too. Von: Vogelsang, Jeff [EMAIL PROTECTED] An: Maven Users List users@maven.apache.org Datum: 19.11.2008 12:32 Betreff: RE: Build error at site-plugin = The skin does not exist I get this error if the central repository is not available when running the site command. In our environment, we use Artifactory with the mirrors setting. We have also disabled the central repository that is defined in the super pom. This prevents our builds from ever needing to go to the Internet for anything. Everything goes through Artifactory. For some reason I don't understand if you disable Central, this error occurs when running the maven site command. It's documented here: http://jira.codehaus.org/browse/MNG-3139 -Original Message- From: Ole Laurisch [mailto:[EMAIL PROTECTED] Sent: Monday, November 17, 2008 8:59 AM To: users@maven.apache.org Subject: Build error at site-plugin = The skin does not exist Hi, I get this error today while making a build with the site plugin. Some Google search leads me to similar problems where it is said that a possible solution (or workaround) would be to add a site directory with a site.xml specifying the skin version. The thing is, that I don't have any site plugin customization. The site goal worked perfectly well for weeks and our pom.xml is unchanged since October 9th. Do you habe any idea what the cause of the problem is and how I can handle it? Thanks in advance, Ole Maven trace: [INFO] [site:site] [WARNING] No URL defined for the project - decoration links will not be resolved [INFO] artifact org.apache.maven.skins:maven-default-skin: checking for updates from central [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE -- Kommen Sie uns besuchen: Vom 18.-21.11. 2008 wird engram auf der Innovationsfläche des IT-Forums der Finanz Informatik in Frankfurt als Aussteller innovative Lösungen im Bereich IT vorstellen. Interessenten finden engram in der Halle 4.2, Frankfurter Messe. Wir freuen uns auf Ihren Besuch! engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Kommen Sie uns besuchen: Vom 18.-21.11. 2008 wird engram auf der Innovationsfläche des IT-Forums der Finanz Informatik in Frankfurt als Aussteller innovative Lösungen im Bereich IT vorstellen. Interessenten finden engram in der Halle 4.2, Frankfurter Messe. Wir freuen uns auf Ihren Besuch! engram GmbH Konsul-Smidt-Straße 8r 28217 Bremen Germany Tel.: +49-[0]421-620298-0 Fax: +49-[0]421-620298-999 Handelsregister Bremen HRB 20782 Geschäftsführer: Jens Wünderlich Aufsichtsratsvorsitzender: Ralf Paslack
RE: modifying goals executed during release
Did you read the documentation for the perform goal (http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html)? From: Nathan Coast [mailto:[EMAIL PROTECTED] Sent: Wed 11/19/2008 7:42 AM To: users@maven.apache.org Subject: modifying goals executed during release Hi, Is there a mechanism to modify the goals executed during release:perform? We use the release plugin to manage regular builds to our QA environments, the release process itself is excellent however we'd like to remove documentation generation and deployment from these builds. For our more complex projects, the build time slows from 5 mins for install to 40 mins during release largely due to multi-module documentation generation. cheers, Nathan - Nathan Coast Global Rates Technology Deutsche Bank London Tel:+44 (0)20 754 70639 Mob: +44 (0)7910 639 627 - --- This e-mail may contain confidential and/or privileged information. If you are not the intended recipient (or have received this e-mail in error) please notify the sender immediately and delete this e-mail. Any unauthorized copying, disclosure or distribution of the material in this e-mail is strictly forbidden. Please refer to http://www.db.com/en/content/eu_disclosures.htm for additional EU corporate and regulatory disclosures. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: specifying latest for a dependency
Hi Todd, SNAPSHOT is different from latest, because a SNAPSHOT is unstable, pre-alpha stuff, not the latest known working released version. This is a critical distinction, many projects use and publish SNAPSHOTS for internal use (for example, if I have three modules, they all evolve simultaneously, so they depend on the snapshot of each other until we arrive to a release). To get the latest one, simply put no upper bound to a version range. This will avoid SNAPSHOTS, and get the highest available version. And yes, only the first three are considered numbers. Obviously this is not perfect, because every organization can setup a standard with one, two, three, four or one hundred numbers. Anyway the three numbers are quite considered a de-facto standard, and used in 90% of software development. So, I would suggest to stick with 3 (major, minor, rev) number, and use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI timestamp), remembering that if your development practice often brings you to RC10 or above, you should number them 01, 02 etc... Simone Todd Thiessen wrote: Snapshot versions work this way. Perhaps this is what you are looking for. I was confused by this too btw. I think snapshot would of been better named as lastest. I don't know if you can do this with release versions though. It would be nice to always get the latest release. --- Todd Thiessen -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 12:31 PM To: users@maven.apache.org Subject: specifying latest for a dependency I know this has been discussed time and time again, but I can't seem to combine the right google keywords to find what I'm looking for. How do you specify latest for a dependency? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven-site-plugin-doxia-beta-1 fails to build
I am trying to get a PDF-export of the site runing.
I built maven-2.0.11-trunk and checked out doxia-beta1 from
https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-doxia-beta-1
Unfortunately I cannot build the plugin, even not with maven-2.0.11-trunk:
[INFO] [invoker:run {execution: integration-test}]
[WARNING] File encoding has not been set, using platform encoding Cp1252,
i.e. build is platform dependent!
[WARNING] Filtering of parent/child POMs is not supported without cloning
the projects
[INFO] Building: MSITE-265\pom.xml
[INFO] ...FAILED. The build exited with code 1. See
c:\working\azcommons_head\maven-site-plugin-doxia-beta-1\src\it\MSITE-265\build.log
for details.
[INFO] ---
[INFO] Execution Summary:
[INFO] Builds Passing: 0
[INFO] Builds Failing: 1
[INFO] ---
[ERROR] The following builds failed:
[ERROR] * MSITE-265\pom.xml
[INFO] ---
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] : [EMAIL PROTECTED]
Could some developer please give us a hint how to get the PDF-export working
again. It used to work fine with Maven1 pdf-plugin. What I see on the
mailing lists there is a whole crowd of people waiting for the PDF-export.
--
View this message in context:
http://www.nabble.com/maven-site-plugin-doxia-beta-1-fails-to-build-tp20582066p20582066.html
Sent from the Doxia - Users mailing list archive at Nabble.com.
Re: generate PDF site
There is a pdf plugin in the sandbox [1] but it only works (or worked, I haven't tested) with doxia-beta-1 which is still not released, and probably won't work with any published version of maven anyway. It's been a while since I worked on it, and a lot of stuff has changed since on maven trunk, so I'd need to check and update some things. A doxia release would certainly help... Cheers, -Lukas [1] http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-pdf-plugin/ Marc Lustig wrote: For Maven 1, there was the PDF-plugin to export the site into PDF-format. What is the replacement for Maven 2? The Doxia-docs are not very straightforward... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven-site-plugin-doxia-beta-1 fails to build
Marc Lustig wrote:
I am trying to get a PDF-export of the site runing.
I built maven-2.0.11-trunk and checked out doxia-beta1 from
https://svn.apache.org/repos/asf/maven/plugins/branches/maven-site-plugin-doxia-beta-1
Unfortunately I cannot build the plugin, even not with maven-2.0.11-trunk:
[INFO] [invoker:run {execution: integration-test}]
[WARNING] File encoding has not been set, using platform encoding Cp1252,
i.e. build is platform dependent!
[WARNING] Filtering of parent/child POMs is not supported without cloning
the projects
[INFO] Building: MSITE-265\pom.xml
[INFO] ...FAILED. The build exited with code 1. See
c:\working\azcommons_head\maven-site-plugin-doxia-beta-1\src\it\MSITE-265\build.log
for details.
[INFO] ---
[INFO] Execution Summary:
[INFO] Builds Passing: 0
[INFO] Builds Failing: 1
[INFO] ---
[ERROR] The following builds failed:
[ERROR] * MSITE-265\pom.xml
[INFO] ---
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] : [EMAIL PROTECTED]
Could some developer please give us a hint how to get the PDF-export working
again. It used to work fine with Maven1 pdf-plugin. What I see on the
mailing lists there is a whole crowd of people waiting for the PDF-export.
I just sent the link to the pdf sandbox plugin [1] to the user list.
I don't quite understand though why you are trying to build
maven-site-plugin-doxia-beta-1, this has nothing to do with the pdf
functionality. It was just a testing branch to prepare for the
doxia-beta-1 release, to check if the site plugin works with
doxia-beta-1. That said, it should build still...
cheers,
-Lukas
PS If there is a whole crowd of people waiting then get some of them to
work on it! ;)
[1]
http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-pdf-plugin/
RE: specifying latest for a dependency
Thanks for the reply. I do understand that SNAPSHOT is meant for developers only. I did read here: http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0 e9801 that LATEST means the latest SNAPSHOT or RELEASED version and a version of RELEASED means the latest RELEASED version. I tried playing with these as version values but the artifact couldn't be found. I did have success using no upper bound on range however. I think my biggest confusion was the naming convension here. The term SNAPSHOT typically means a fixed state of something at a particular point in time. However, in Maven it isn't fixed at all. It is in constant flux. A better name for SNAPSHOT would of been something like LATEST-DEV. --- Todd Thiessen -Original Message- From: Simone Gianni [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 9:19 AM To: Maven Users List Subject: Re: specifying latest for a dependency Hi Todd, SNAPSHOT is different from latest, because a SNAPSHOT is unstable, pre-alpha stuff, not the latest known working released version. This is a critical distinction, many projects use and publish SNAPSHOTS for internal use (for example, if I have three modules, they all evolve simultaneously, so they depend on the snapshot of each other until we arrive to a release). To get the latest one, simply put no upper bound to a version range. This will avoid SNAPSHOTS, and get the highest available version. And yes, only the first three are considered numbers. Obviously this is not perfect, because every organization can setup a standard with one, two, three, four or one hundred numbers. Anyway the three numbers are quite considered a de-facto standard, and used in 90% of software development. So, I would suggest to stick with 3 (major, minor, rev) number, and use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI timestamp), remembering that if your development practice often brings you to RC10 or above, you should number them 01, 02 etc... Simone Todd Thiessen wrote: Snapshot versions work this way. Perhaps this is what you are looking for. I was confused by this too btw. I think snapshot would of been better named as lastest. I don't know if you can do this with release versions though. It would be nice to always get the latest release. --- Todd Thiessen -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 12:31 PM To: users@maven.apache.org Subject: specifying latest for a dependency I know this has been discussed time and time again, but I can't seem to combine the right google keywords to find what I'm looking for. How do you specify latest for a dependency? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer http://www.simonegianni.it/ - 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: specifying latest for a dependency
Those special values, AFAIK are for plugin versions only and are depricated 2008/11/19 Todd Thiessen [EMAIL PROTECTED] Thanks for the reply. I do understand that SNAPSHOT is meant for developers only. I did read here: http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0 e9801http://books.sonatype.com/maven-book/reference/pom-relationships.html#d0e9801 that LATEST means the latest SNAPSHOT or RELEASED version and a version of RELEASED means the latest RELEASED version. I tried playing with these as version values but the artifact couldn't be found. I did have success using no upper bound on range however. I think my biggest confusion was the naming convension here. The term SNAPSHOT typically means a fixed state of something at a particular point in time. However, in Maven it isn't fixed at all. It is in constant flux. A better name for SNAPSHOT would of been something like LATEST-DEV. --- Todd Thiessen -Original Message- From: Simone Gianni [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 9:19 AM To: Maven Users List Subject: Re: specifying latest for a dependency Hi Todd, SNAPSHOT is different from latest, because a SNAPSHOT is unstable, pre-alpha stuff, not the latest known working released version. This is a critical distinction, many projects use and publish SNAPSHOTS for internal use (for example, if I have three modules, they all evolve simultaneously, so they depend on the snapshot of each other until we arrive to a release). To get the latest one, simply put no upper bound to a version range. This will avoid SNAPSHOTS, and get the highest available version. And yes, only the first three are considered numbers. Obviously this is not perfect, because every organization can setup a standard with one, two, three, four or one hundred numbers. Anyway the three numbers are quite considered a de-facto standard, and used in 90% of software development. So, I would suggest to stick with 3 (major, minor, rev) number, and use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI timestamp), remembering that if your development practice often brings you to RC10 or above, you should number them 01, 02 etc... Simone Todd Thiessen wrote: Snapshot versions work this way. Perhaps this is what you are looking for. I was confused by this too btw. I think snapshot would of been better named as lastest. I don't know if you can do this with release versions though. It would be nice to always get the latest release. --- Todd Thiessen -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 12:31 PM To: users@maven.apache.org Subject: specifying latest for a dependency I know this has been discussed time and time again, but I can't seem to combine the right google keywords to find what I'm looking for. How do you specify latest for a dependency? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer http://www.simonegianni.it/ - 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: specifying latest for a dependency
Maven supports the idea of latest if you use version ranges no? So at least for a given milestone you can grab the latest release of a given component. == Curtis Yanko Application Developer Infrastructure Services Source-Build-Deploy W: 860.702.9059 M: 860.881.2050 -Original Message- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 11:08 AM To: Maven Users List Subject: Re: specifying latest for a dependency Those special values, AFAIK are for plugin versions only and are depricated 2008/11/19 Todd Thiessen [EMAIL PROTECTED] Thanks for the reply. I do understand that SNAPSHOT is meant for developers only. I did read here: http://books.sonatype.com/maven-book/reference/pom-relationships.html# d0 e9801http://books.sonatype.com/maven-book/reference/pom-relationships .html#d0e9801 that LATEST means the latest SNAPSHOT or RELEASED version and a version of RELEASED means the latest RELEASED version. I tried playing with these as version values but the artifact couldn't be found. I did have success using no upper bound on range however. I think my biggest confusion was the naming convension here. The term SNAPSHOT typically means a fixed state of something at a particular point in time. However, in Maven it isn't fixed at all. It is in constant flux. A better name for SNAPSHOT would of been something like LATEST-DEV. --- Todd Thiessen -Original Message- From: Simone Gianni [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 9:19 AM To: Maven Users List Subject: Re: specifying latest for a dependency Hi Todd, SNAPSHOT is different from latest, because a SNAPSHOT is unstable, pre-alpha stuff, not the latest known working released version. This is a critical distinction, many projects use and publish SNAPSHOTS for internal use (for example, if I have three modules, they all evolve simultaneously, so they depend on the snapshot of each other until we arrive to a release). To get the latest one, simply put no upper bound to a version range. This will avoid SNAPSHOTS, and get the highest available version. And yes, only the first three are considered numbers. Obviously this is not perfect, because every organization can setup a standard with one, two, three, four or one hundred numbers. Anyway the three numbers are quite considered a de-facto standard, and used in 90% of software development. So, I would suggest to stick with 3 (major, minor, rev) number, and use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI timestamp), remembering that if your development practice often brings you to RC10 or above, you should number them 01, 02 etc... Simone Todd Thiessen wrote: Snapshot versions work this way. Perhaps this is what you are looking for. I was confused by this too btw. I think snapshot would of been better named as lastest. I don't know if you can do this with release versions though. It would be nice to always get the latest release. --- Todd Thiessen -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 12:31 PM To: users@maven.apache.org Subject: specifying latest for a dependency I know this has been discussed time and time again, but I can't seem to combine the right google keywords to find what I'm looking for. How do you specify latest for a dependency? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer http://www.simonegianni.it/ - 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] This e-mail, including attachments, may include confidential and/or proprietary information, and may be used only by the person or entity to which it is addressed. If the reader of this e-mail is not the intended recipient or his or her authorized agent, the reader is hereby notified that any dissemination, distribution or copying of this e-mail is prohibited. If you have received this e-mail in error, please notify the sender by replying to this message and delete this e-mail immediately. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: specifying latest for a dependency
En l'instant précis du 19/11/08 17:01, Todd Thiessen s'exprimait en ces termes: I think my biggest confusion was the naming convension here. The term SNAPSHOT typically means a fixed state of something at a particular point in time. However, in Maven it isn't fixed at all. It is in constant flux. A better name for SNAPSHOT would of been something like LATEST-DEV. I see no confusion. More over, snapshot are fixed. What you did not fix however, in your pom it which snapshot to use, so maven choose to download the latest snapshot. SNAPSHOT is a good term for an automated daily build. LATEST-DEV would be more, to me, like asking maven to connect to version control an do a build from it. Example of using a fixed snapshot: version1.0-beta-3-20080505.072643-6/version This will fix dependency to that explicit snapshot made on 05/05/2008 of 1.0-beta3 while version1.0-beta3-SNAPSHOT/version will point always to latest snapshot of 1.0-beta3 -- David Delbecq ICT Institut Royal Météorologique Ext:557 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: generate PDF site
The build fails due to missing artifact org.apache.maven.doxia:doxia-doc-renderer:jar:1.0-beta-1-SNAPSHOT Do you know where to get this snapshot? Lukas Theussl-3 wrote: There is a pdf plugin in the sandbox [1] but it only works (or worked, I haven't tested) with doxia-beta-1 which is still not released, and probably won't work with any published version of maven anyway. It's been a while since I worked on it, and a lot of stuff has changed since on maven trunk, so I'd need to check and update some things. A doxia release would certainly help... Cheers, -Lukas [1] http://svn.apache.org/repos/asf/maven/sandbox/trunk/plugins/maven-pdf-plugin/ Marc Lustig wrote: For Maven 1, there was the PDF-plugin to export the site into PDF-format. What is the replacement for Maven 2? The Doxia-docs are not very straightforward... - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/generate-PDF-site-tp20575798p20583502.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: specifying latest for a dependency
Well, all builds are fixed. Thus all builds are snapshots, including released builds. There is nothing intrinsic in the definition of the word snapshot which indicates that it is meant for developers only. I am sure you are used to it by now, but I have little doubt that this is a source of confusion to new users of maven. --- Todd Thiessen -Original Message- From: David Delbecq [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 11:17 AM To: Maven Users List Subject: Re: specifying latest for a dependency En l'instant précis du 19/11/08 17:01, Todd Thiessen s'exprimait en ces termes: I think my biggest confusion was the naming convension here. The term SNAPSHOT typically means a fixed state of something at a particular point in time. However, in Maven it isn't fixed at all. It is in constant flux. A better name for SNAPSHOT would of been something like LATEST-DEV. I see no confusion. More over, snapshot are fixed. What you did not fix however, in your pom it which snapshot to use, so maven choose to download the latest snapshot. SNAPSHOT is a good term for an automated daily build. LATEST-DEV would be more, to me, like asking maven to connect to version control an do a build from it. Example of using a fixed snapshot: version1.0-beta-3-20080505.072643-6/version This will fix dependency to that explicit snapshot made on 05/05/2008 of 1.0-beta3 while version1.0-beta3-SNAPSHOT/version will point always to latest snapshot of 1.0-beta3 -- David Delbecq ICT Institut Royal Météorologique Ext:557 - 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: specifying latest for a dependency
OK, I'll clarify want I meant. There are two special version numbers: LATEST and RELEASE. AFAIK Where LATEST corresponds to the latest version according to the Maven Repository Metadata (and I don't mind snapshots) and RELEASE corresponds to the latest released version according to the Maven Repository Metadata. Furthermore, AFAIK, these _magic_ versions only work when specifying the version of a plugin (as you are not allowed to use version ranges in specifying the version of a plugin) The _magic_ version strings do not work in the version section of a dependency, as you can use version ranges there. On top of all of that, you would not want to use these magic strings anyway, as the Maven Repository Metadata thinks that the latest version is the last one that was deployed... so if you publish foo-maven-plugin versions 1.0, 2.0, 1.1 in order then RELEASE will correspond to 1.1 and not the 2.0 that you think it does!!! ;-) -Stephen 2008/11/19 Yanko, Curtis [EMAIL PROTECTED] Maven supports the idea of latest if you use version ranges no? So at least for a given milestone you can grab the latest release of a given component. == Curtis Yanko Application Developer Infrastructure Services Source-Build-Deploy W: 860.702.9059 M: 860.881.2050 -Original Message- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 11:08 AM To: Maven Users List Subject: Re: specifying latest for a dependency Those special values, AFAIK are for plugin versions only and are depricated 2008/11/19 Todd Thiessen [EMAIL PROTECTED] Thanks for the reply. I do understand that SNAPSHOT is meant for developers only. I did read here: http://books.sonatype.com/maven-book/reference/pom-relationships.html# d0 e9801http://books.sonatype.com/maven-book/reference/pom-relationships .html#d0e9801 that LATEST means the latest SNAPSHOT or RELEASED version and a version of RELEASED means the latest RELEASED version. I tried playing with these as version values but the artifact couldn't be found. I did have success using no upper bound on range however. I think my biggest confusion was the naming convension here. The term SNAPSHOT typically means a fixed state of something at a particular point in time. However, in Maven it isn't fixed at all. It is in constant flux. A better name for SNAPSHOT would of been something like LATEST-DEV. --- Todd Thiessen -Original Message- From: Simone Gianni [mailto:[EMAIL PROTECTED] Sent: Wednesday, November 19, 2008 9:19 AM To: Maven Users List Subject: Re: specifying latest for a dependency Hi Todd, SNAPSHOT is different from latest, because a SNAPSHOT is unstable, pre-alpha stuff, not the latest known working released version. This is a critical distinction, many projects use and publish SNAPSHOTS for internal use (for example, if I have three modules, they all evolve simultaneously, so they depend on the snapshot of each other until we arrive to a release). To get the latest one, simply put no upper bound to a version range. This will avoid SNAPSHOTS, and get the highest available version. And yes, only the first three are considered numbers. Obviously this is not perfect, because every organization can setup a standard with one, two, three, four or one hundred numbers. Anyway the three numbers are quite considered a de-facto standard, and used in 90% of software development. So, I would suggest to stick with 3 (major, minor, rev) number, and use the fourth if needed for stuff like ALPHA, BETA, RC1, RC2 (or OSGI timestamp), remembering that if your development practice often brings you to RC10 or above, you should number them 01, 02 etc... Simone Todd Thiessen wrote: Snapshot versions work this way. Perhaps this is what you are looking for. I was confused by this too btw. I think snapshot would of been better named as lastest. I don't know if you can do this with release versions though. It would be nice to always get the latest release. --- Todd Thiessen -Original Message- From: EJ Ciramella [mailto:[EMAIL PROTECTED] Sent: Tuesday, November 18, 2008 12:31 PM To: users@maven.apache.org Subject: specifying latest for a dependency I know this has been discussed time and time again, but I can't seem to combine the right google keywords to find what I'm looking for. How do you specify latest for a dependency? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Simone GianniCEO Semeru s.r.l. Apache Committer http://www.simonegianni.it/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands,
Assembly plugin not filtering parent.parent-version
Hi,
I have a file in a project which contains the following:
projectname--${parent.parent.version}
The project structure is the following:
main (packaging:pom)
dev (packaging:pom)
project-where-the-file-is-located (packaging:jar)
other-project (packaging:jar)
war-project (packaging:war)
When I run mvn clean install, the version string is replaced correctly,
however when I run assembly:assembly it doesn't worki,
Any ideas why this happens? I'm using the latest plugin version
Thanks in advance.
Regards.
Re: generate PDF site
You can check out Doxia from https://svn.apache.org/repos/asf/maven/doxia/trunks The doxia-doc-renderer module is under doxia-sitetools. If you need help building it (and better, if you want to help Lukas fix it!) please join us on the development mailing list. :) -- Wendy On Wed, Nov 19, 2008 at 9:27 AM, Marc Lustig [EMAIL PROTECTED] wrote: The build fails due to missing artifact org.apache.maven.doxia:doxia-doc-renderer:jar:1.0-beta-1-SNAPSHOT Do you know where to get this snapshot? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Interjectign a plugin in a life-cycle phase
Hello, I'd like to interject a plugin in a certain phase (say validate) that is always executed for all developers who use maven within the enterprise. To achieve this, should I create a enterprise level POM and have all developers extend it? I have an enterprise-wide setting.xml file. Can I somehow use the settings.xml file to enforce the use of this enterprise-wide POM that I created (and in which I have specified my plugin)? Thanks Pankaj -- View this message in context: http://www.nabble.com/Interjectign-a-plugin-in-a-life-cycle-phase-tp20586481p20586481.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Not happy with maven
Hi everybody! I've been using Maven 2 for a few projects now, and found that, although it provides some nice features, it doesn't seem to be the right tool for most of my applications. I'll write down some of my experiences here, so that they might help improving development tools in general. I'm an individual Java programmer interested in developing open source applications. I don't work for any company, therefore copany repositories don't apply to me. Most of my projects are swing GUI applications intended to be run by users on their local computers, so integration tests are mostly irrelevant, and the possibilities for automatic testing are limited as well. This mail is not intended to start a flame war. I know there are people using maven and happy with it, and for good reasons. I might even continue using it for my library projects. I guess many of the issues I don't like about maven could be helped with more knowledge about Maven, customized plugins, hackish workarounds, or any other kind of additional work. It's the sum of all together and the amount of work required which lead me away from Maven. I list these issues in no particular order. MAVEN REPOSITORY AS ONLY SOURCE OF DEPENDENCIES While the large repository used by maven is a great thing, one of the most prominent advantages of Maven, it is in no way complete. Whenever I want to make use of some library not available in a common repository, I first have to get it into some repository I control, then have to get that repository into the pom of my project, and at some point have to grant public access to that repository if I want to share with other developers. I would much prefer some kind of lib directory, where I could simply drop the library and start using it, to see if it is fit for the job I want to use it for in the first place. Then if I decide to keep it, I would rather add some instructions to my repository about how to get this library from its official source. Such instructions might involve downloading some bundle, checking its md5sum in case its file name contains no version number, extracting it, maybe running some installer and interactively accepting some license, stuff like that. I'd rather include such descriptions with the dependency than have an extra file that describes how to set things up for maven. ORDER OF TASKS The maven POM seems to lack a clear concept of task order. This seems especially important in the packaging phase. Suppose I produce a jar which I want to pack200, jarsign, gpgsign, include in an assembly, and gpgsign that assembly again. Clearly order matters a lot. While I believe it might be possible to get the order correct in Maven as well, there is no intuitive way to express this order when conceptually all you do is load a bunch of plugins. TOO SLOW Maven is simply to slow, especially while starting up. WHile developing, I often want to edit the code, compile the code, and run the code, all in a tight loop. When over 50% of the time is spent starting that maven monster, that's no efficient use of time. As Maven seems to lack a simple run target, running the code usually means either some complicated java invocation, or a packaged jart with the dependencies included in its Classpath, which means executing the package phase and before that the test phase, leading to even longer build times. SECURITY CONCERNS Maven does a lot of things automatically. While this is a good thing if I simply want to grab a piece of code and build it, it can be annoying under security aspects. I can't specify repositories for specific artifacts only. So whenever I want to grab a dependency from a given repository, I'll have to include it in the POM, and it will be queried for every artifact Maven wants to download or update. So a malicious repository could introduce malicious artifacts into my local repository, affecting all my other projects as well. Another aspect of this security issue is the fact that there seems to be no way to ask the user for a password for e.g. jarsigner and hand that to jarsigner by some means other than a command line argument. On a multi-user *nix machine, users can see what commands other users are running, and I don't like them seeing my keystore passphrase. And storing these passphrases in a file for maven seems comparably evil. TERRIBLE COMMAND LINE INTERFACE I know, many developers are using IDEs and probably wouldn't even notice such issues. But I still prefer to edit my source code in an editor and build its artefacts from the command line. If I do so with maven I find the output from the help commands which might be good for machines to read, but is plainly annoying to me. I find all messages preceeded by the message category and thus hard to read. I find absolute file names all over the place, leading to excessively long lines. On the whole, maven doesn't look well suited to command line operations. When I compare this to command line tools like e.g. bzr, where I can
Re: Not happy with maven
Martin von Gagern wrote: On the whole, I spent way too much time tweaking Maven, time I'd rather spend working on my project code. One of the most fundamental things about maven that you need to do to have a pleasant user experience, is to submit to maven. In other words, you shouldn't spend time tweaking maven, you should rather spend time tweaking your project to work using the standard way maven works. This is a big ask for many people I know, people come to maven going but I want it to work like this, and maven won't let me. Standardisation means that if you follow the standards, there is a whole class of problems that are already solved. If your code is in a standard place, you no longer need to tell anybody, whether a computer or a human, where your code is, they already know. If your release procedures are standardised, you no longer need to tell anybody, whether a computer or a human, how to release your code or where it lives, they already know. Standardisation however doesn't help you if you want to invent your own standard. If you invent your own standard, you have to write the code yourself, and for me personally, rewriting your own standard is a waste of time and money. I now decided to abandon maven, at least for my end user applications. I'm not sure what I'll be using instead. Maybe some form of ant, with or without ivy, with or without build files generated from xslt. So you replace an exercise in messing around with maven with an exercise in messing around with ant. I don't see how that will help you focus on development. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Not happy with maven
Just my pesonnal conviction : Maven is not the golden bullet tool. It has many issues (some you describe), and can't cover all requirements. Many project choosed some complex building (like the sign / assembly process you describe) that does not match maven conventions. Maven is a toll for project that can share some basic convention, and then get benefict for many other tool to plug naturally in project structure. For this reason, it works fine for business projects where same conventions on all project = more productivity. Just my 2 cents, Anyway, thanks for your feedback, Nicolas. 2008/11/19 Martin von Gagern [EMAIL PROTECTED] Hi everybody! I've been using Maven 2 for a few projects now, and found that, although it provides some nice features, it doesn't seem to be the right tool for most of my applications. I'll write down some of my experiences here, so that they might help improving development tools in general. I'm an individual Java programmer interested in developing open source applications. I don't work for any company, therefore copany repositories don't apply to me. Most of my projects are swing GUI applications intended to be run by users on their local computers, so integration tests are mostly irrelevant, and the possibilities for automatic testing are limited as well. This mail is not intended to start a flame war. I know there are people using maven and happy with it, and for good reasons. I might even continue using it for my library projects. I guess many of the issues I don't like about maven could be helped with more knowledge about Maven, customized plugins, hackish workarounds, or any other kind of additional work. It's the sum of all together and the amount of work required which lead me away from Maven. I list these issues in no particular order. MAVEN REPOSITORY AS ONLY SOURCE OF DEPENDENCIES While the large repository used by maven is a great thing, one of the most prominent advantages of Maven, it is in no way complete. Whenever I want to make use of some library not available in a common repository, I first have to get it into some repository I control, then have to get that repository into the pom of my project, and at some point have to grant public access to that repository if I want to share with other developers. I would much prefer some kind of lib directory, where I could simply drop the library and start using it, to see if it is fit for the job I want to use it for in the first place. Then if I decide to keep it, I would rather add some instructions to my repository about how to get this library from its official source. Such instructions might involve downloading some bundle, checking its md5sum in case its file name contains no version number, extracting it, maybe running some installer and interactively accepting some license, stuff like that. I'd rather include such descriptions with the dependency than have an extra file that describes how to set things up for maven. ORDER OF TASKS The maven POM seems to lack a clear concept of task order. This seems especially important in the packaging phase. Suppose I produce a jar which I want to pack200, jarsign, gpgsign, include in an assembly, and gpgsign that assembly again. Clearly order matters a lot. While I believe it might be possible to get the order correct in Maven as well, there is no intuitive way to express this order when conceptually all you do is load a bunch of plugins. TOO SLOW Maven is simply to slow, especially while starting up. WHile developing, I often want to edit the code, compile the code, and run the code, all in a tight loop. When over 50% of the time is spent starting that maven monster, that's no efficient use of time. As Maven seems to lack a simple run target, running the code usually means either some complicated java invocation, or a packaged jart with the dependencies included in its Classpath, which means executing the package phase and before that the test phase, leading to even longer build times. SECURITY CONCERNS Maven does a lot of things automatically. While this is a good thing if I simply want to grab a piece of code and build it, it can be annoying under security aspects. I can't specify repositories for specific artifacts only. So whenever I want to grab a dependency from a given repository, I'll have to include it in the POM, and it will be queried for every artifact Maven wants to download or update. So a malicious repository could introduce malicious artifacts into my local repository, affecting all my other projects as well. Another aspect of this security issue is the fact that there seems to be no way to ask the user for a password for e.g. jarsigner and hand that to jarsigner by some means other than a command line argument. On a multi-user *nix machine, users can see what commands other users are running, and I don't like them seeing my keystore passphrase. And storing these
Re: Not happy with maven
I guess many of the issues I don't like about maven could be helped with more knowledge about Maven, customized plugins, hackish workarounds, or any other kind of additional work. It's the sum of all together and the amount of work required which lead me away from Maven. I list these issues in no particular order. We see rants like this every few months from someone. And the fact that this is your 4th email to this group suggests that you have generally been going it alone rather than leaning on this group as needed for help. (Note: this is not an open call for n00bs to blast this list with the most basic of queries.) Obviously, the documentation etc can only take you so far. While this users list cannot answer every question you may have, I think your overall experience with Maven would have been improved if you had sent some of these questions/issues to this list previously looking for help rather than letting it all boil up for months and eventually releasing it in this email. Regarding writing your own build tool -- I think this is probably a bad idea, but of course, you are welcome to disagree. If you have decided to abandon Maven, perhaps take a look at buildr and other tools (you already mentioned ivy) that have taken ideas from Maven and incorporated the Central repository as a source of dependency artifacts etc. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Interjectign a plugin in a life-cycle phase
To achieve this, should I create a enterprise level POM and have all developers extend it? Yes, this pom would be the parent for all projects in your organization. I have an enterprise-wide setting.xml file. Can I somehow use the settings.xml file to enforce the use of this enterprise-wide POM that I created (and in which I have specified my plugin)? No, this is not possible. At least, I'm not aware of any way to do this. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not happy with maven
Wayne Fay wrote: Regarding writing your own build tool -- I think this is probably a bad idea, but of course, you are welcome to disagree. There is a contingent at my office that believes they should write their own build system. They manage a HUGE project using a directory full of Ant scripts. It's insane. I came along and started using Maven for the projects I was leading up. Folks are beginning to take notice that, Hey, he's getting builds to run smoothly without a ton of effort. What's that all about? Of course, I am of the don't re-invent the wheel school of thought. I'm not going to waste my own time writing something that a lot of other really bright people have already put a lot of thought and effort into. I don't see how I could possibly compete with that on my own. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
A question about -DarchetypeArtifactId=maven-archetype-webapp
Hi all, I use the following mvn command to create a web project, but the generaed web.xml uses web-app_2_3.dtd. But what I want is web-app_2_4.xsd or even web-app_2_5.xsd. Someone knows is there a new maven artifact to do so? Regards Thomas -- View this message in context: http://www.nabble.com/A-question-about-%22-DarchetypeArtifactId%3Dmaven-archetype-webapp%22-tp20588259p20588259.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: A question about -DarchetypeArtifactId=maven-archetype-webapp
Archetype's are just a very simple starting point. I suggest if you are doing this frequently, you create your own that has more than just the standard web.xml in it anyway. Cheers, Brett On 20/11/2008, at 7:11 AM, thomas2004 wrote: Hi all, I use the following mvn command to create a web project, but the generaed web.xml uses web-app_2_3.dtd. But what I want is web-app_2_4.xsd or even web-app_2_5.xsd. Someone knows is there a new maven artifact to do so? Regards Thomas -- View this message in context: http://www.nabble.com/A-question-about-%22-DarchetypeArtifactId%3Dmaven-archetype-webapp%22-tp20588259p20588259.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: A question about -DarchetypeArtifactId=maven-archetype-webapp
For example? :-) brettporter wrote: Archetype's are just a very simple starting point. I suggest if you are doing this frequently, you create your own that has more than just the standard web.xml in it anyway. Cheers, Brett On 20/11/2008, at 7:11 AM, thomas2004 wrote: Hi all, I use the following mvn command to create a web project, but the generaed web.xml uses web-app_2_3.dtd. But what I want is web-app_2_4.xsd or even web-app_2_5.xsd. Someone knows is there a new maven artifact to do so? Regards Thomas -- View this message in context: http://www.nabble.com/A-question-about-%22-DarchetypeArtifactId%3Dmaven-archetype-webapp%22-tp20588259p20588259.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/A-question-about-%22-DarchetypeArtifactId%3Dmaven-archetype-webapp%22-tp20588259p20588456.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: A question about -DarchetypeArtifactId=maven-archetype-webapp
On 20/11/2008, at 7:21 AM, thomas2004 wrote: For example? :-) anything you need... set the web descriptor to the version you want, add any filters or other elements you use on every project. Add your organisational POM to the POM template as a parent. Add dependencies on standard frameworks, and so on. Cheers, Brett brettporter wrote: Archetype's are just a very simple starting point. I suggest if you are doing this frequently, you create your own that has more than just the standard web.xml in it anyway. Cheers, Brett On 20/11/2008, at 7:11 AM, thomas2004 wrote: Hi all, I use the following mvn command to create a web project, but the generaed web.xml uses web-app_2_3.dtd. But what I want is web-app_2_4.xsd or even web-app_2_5.xsd. Someone knows is there a new maven artifact to do so? Regards Thomas -- View this message in context: http://www.nabble.com/A-question-about-%22-DarchetypeArtifactId%3Dmaven-archetype-webapp%22-tp20588259p20588259.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/A-question-about-%22-DarchetypeArtifactId%3Dmaven-archetype-webapp%22-tp20588259p20588456.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: A question about -DarchetypeArtifactId=maven-archetype-webapp
anything you need... set the web descriptor to the version you want, add any filters or other elements you use on every project. Add your organisational POM to the POM template as a parent. Add dependencies on standard frameworks, and so on. If this wasn't clear, Brett is suggesting that you create your own archetype. This process is pretty well-documented in the Maven website so I'm not going in to details here. If you create a useful archetype, feel free to contribute it back to the Maven project (eg m-a-webapp-2.4 or -2.5). You may also want to look at the appfuse archetypes. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How does maven-compiler-plugin choose its defaults?
On Nov 18, 2008, at 4:50 PM, Stephen Connolly wrote: 1.3 Ah... There is indeed a file in the Maven sources, JavacCompiler.java, that sets -source to 1.3 and -target to 1.1. It is in a bootstrap package, but I assume it somehow propagates to maven-compiler-plugin as well. Thanks for the pointer. Trevor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not happy with maven (suggestion)
You have put a lot of effort into this email and its really important to spread the ideas around, could you put these issues into jira with suggested solutions? To give more visiblity. cheers -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Help creating Multi-Module Project
Hi to all maven users!
I thank you for your help in advance, I am a relatively inexperienced Maven
user, so I apologize for any questions that may have been advanced. I
created a multi-module project from the command line the following manner:
1. Created a directory named maven-multi.
2. cd maven-multi
3. created a parent pom in this directory that was basically the following:
modelVersion4.0.0/modelVersion
groupIdus.holdinghands.template/groupId
artifactIdmulti/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
nameMulti Module Pom/name
4. mvn archetype:create \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DgroupId=us.holdinghands.template \
-DartifactId=model -DpackageName=us.holdinghands.model (ran 3 times)
changing model (2 times in the command line) to business and persist each
time..
This creates 3 subprojects within the directory listed in the top pom as
modules..
4. mvn archetype:create \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DarchetypeArtifactId=maven-archetype-webapp \
-DgroupId=us.holdinghands.template \
-DartifactId=creditapp
ran once to create creditapp web application once that is also a module
in parent pom.
5. Changed pom.xml in persist to show dependency:
dependency
groupId${project.groupId}/groupId
artifactIdmodel/artifactId
version${product.version}/version
/dependency
on the model and added JUnit dependecy on test scope in parent pom.
6. Ran mvn install at top level directory (maven-multi) , it failed with
error message can not change name of directory c:\ ...\...\maven-multi ,
I am not sure of what I did wrong, I set this up to use m2Eclispe to work
out dependencies and THEN switch to Intellij..
Thanks again for any help
--
View this message in context:
http://www.nabble.com/Help-creating-Multi-Module-Project-tp20589965p20589965.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not happy with maven (suggestion)
Michael McCallum wrote: You have put a lot of effort into this email and its really important to spread the ideas around, could you put these issues into jira with suggested solutions? To give more visiblity. I might, for some of them, if I find the time. I guess some of my ideas concern things very basic to Maven, so I see little chance to get them addressed. I'll think about that when I go over the list again. Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help creating Multi-Module Project
Your steps look correct. Can you paste the exact error you got in step
6?
Thanks,
Brett
On 20/11/2008, at 8:46 AM, msclovis wrote:
Hi to all maven users!
I thank you for your help in advance, I am a relatively
inexperienced Maven
user, so I apologize for any questions that may have been advanced. I
created a multi-module project from the command line the following
manner:
1. Created a directory named maven-multi.
2. cd maven-multi
3. created a parent pom in this directory that was basically the
following:
modelVersion4.0.0/modelVersion
groupIdus.holdinghands.template/groupId
artifactIdmulti/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
nameMulti Module Pom/name
4. mvn archetype:create \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DgroupId=us.holdinghands.template \
-DartifactId=model -DpackageName=us.holdinghands.model (ran 3 times)
changing model (2 times in the command line) to business and persist
each
time..
This creates 3 subprojects within the directory listed in the top
pom as
modules..
4. mvn archetype:create \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DarchetypeArtifactId=maven-archetype-webapp \
-DgroupId=us.holdinghands.template \
-DartifactId=creditapp
ran once to create creditapp web application once that is also a
module
in parent pom.
5. Changed pom.xml in persist to show dependency:
dependency
groupId${project.groupId}/groupId
artifactIdmodel/artifactId
version${product.version}/version
/dependency
on the model and added JUnit dependecy on test scope in parent pom.
6. Ran mvn install at top level directory (maven-multi) , it failed
with
error message can not change name of directory c:\ ...\...\maven-
multi ,
I am not sure of what I did wrong, I set this up to use m2Eclispe
to work
out dependencies and THEN switch to Intellij..
Thanks again for any help
--
View this message in context:
http://www.nabble.com/Help-creating-Multi-Module-Project-tp20589965p20589965.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Not happy with maven
Wayne Fay wrote: We see rants like this every few months from someone. And the fact that this is your 4th email to this group suggests that you have generally been going it alone rather than leaning on this group as needed for help. (Note: this is not an open call for n00bs to blast this list with the most basic of queries.) Obviously, the documentation etc can only take you so far. While this users list cannot answer every question you may have, I think your overall experience with Maven would have been improved if you had sent some of these questions/issues to this list previously looking for help rather than letting it all boil up for months and eventually releasing it in this email. Maybe. My previous posts mentioned a few of these issues. For others I found a way to hack things together, only didn't like its hackish nature. For some more, I wrote patches or feature requests for jira. Regarding writing your own build tool -- I think this is probably a bad idea, but of course, you are welcome to disagree. If you have decided to abandon Maven, perhaps take a look at buildr and other tools (you already mentioned ivy) that have taken ideas from Maven and incorporated the Central repository as a source of dependency artifacts etc. Thanks, I will. Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven - clearcase integration with release:perform
Hi All, I am getting a peculiar problem with running mvn release:perform i have my scm url configured to clearcase snapshotview. release:prepare is working successfully and even clearcase is showing the tag i provide during prepare phase. the pom files in my project are getting updated successfully; so also teh local m2 repository is getting the latest pom files there. I would like to know if there is any solution to this problem. Maven clearcase reference also talks of this problem, but it does not indicate any solution to it: http://maven.apache.org/scm/clearcase.html http://maven.apache.org/scm/clearcase.html (cleartool: Error: A registry entry already exists for johndoe-mymachine-maven-myproject.) i tried to remove the clearcase view but even that does not help. Thanks and Regards, -Amit
Re: Help creating Multi-Module Project
Brett,
Thanks for the quick reply.. The errors are different depending on what
you do.
1. Command line mvn install.
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) us.holdinghands.template:model:jar:${product.version}
Try downloading the file manually from the project website.
Then, install it using the command:
mvn install:install-file -DgroupId=us.holdinghands.template
-DartifactId=m
odel -Dversion=${product.version} -Dpackaging=jar -Dfile=/path/to/file
Alternatively, if you host your own repository you can deploy the file
there:
This makes sense..
2. using m2Eclipse and import of project by pointing it at to directory,
allowing it to see all the poms,
I get Pop-up in eclipse that reads...'Importing Maven projects' has
encountered an problem. Can't rename C:/MikeWorkDir/JavaProjs/maven-multi
if you hit details it says...
Can't rename C:\mikeWorkDir\JavaProjs\maven-multi
That's all I got so far..
brettporter wrote:
Your steps look correct. Can you paste the exact error you got in step
6?
Thanks,
Brett
On 20/11/2008, at 8:46 AM, msclovis wrote:
Hi to all maven users!
I thank you for your help in advance, I am a relatively
inexperienced Maven
user, so I apologize for any questions that may have been advanced. I
created a multi-module project from the command line the following
manner:
1. Created a directory named maven-multi.
2. cd maven-multi
3. created a parent pom in this directory that was basically the
following:
modelVersion4.0.0/modelVersion
groupIdus.holdinghands.template/groupId
artifactIdmulti/artifactId
version1.0-SNAPSHOT/version
packagingpom/packaging
nameMulti Module Pom/name
4. mvn archetype:create \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DgroupId=us.holdinghands.template \
-DartifactId=model -DpackageName=us.holdinghands.model (ran 3 times)
changing model (2 times in the command line) to business and persist
each
time..
This creates 3 subprojects within the directory listed in the top
pom as
modules..
4. mvn archetype:create \
-DarchetypeGroupId=org.apache.maven.archetypes \
-DarchetypeArtifactId=maven-archetype-webapp \
-DgroupId=us.holdinghands.template \
-DartifactId=creditapp
ran once to create creditapp web application once that is also a
module
in parent pom.
5. Changed pom.xml in persist to show dependency:
dependency
groupId${project.groupId}/groupId
artifactIdmodel/artifactId
version${product.version}/version
/dependency
on the model and added JUnit dependecy on test scope in parent pom.
6. Ran mvn install at top level directory (maven-multi) , it failed
with
error message can not change name of directory c:\ ...\...\maven-
multi ,
I am not sure of what I did wrong, I set this up to use m2Eclispe
to work
out dependencies and THEN switch to Intellij..
Thanks again for any help
--
View this message in context:
http://www.nabble.com/Help-creating-Multi-Module-Project-tp20589965p20589965.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Help-creating-Multi-Module-Project-tp20589965p20590515.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Help creating Multi-Module Project
On Wed, Nov 19, 2008 at 2:46 PM, msclovis [EMAIL PROTECTED] wrote:
5. Changed pom.xml in persist to show dependency:
dependency
groupId${project.groupId}/groupId
artifactIdmodel/artifactId
version${product.version}/version
/dependency
Unless you've introduced a property somewhere, do you mean
${project.version} instead of 'product' ?
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
error into pom.xml file into one spring webapp. SOS
Hello
i have one great problem with my maven. i am working into one eclipse and
maven.
i am trying to create one web proyect (basic spring archetype) but always
into the pom file appears the same error.
During 5 days i am trying to solve this problen an i dont solve it.
Can you help me?
1.rs appears one error that says that is not posible to resolve prescanned
pluging artifact.
if i comment the line appearts other error whith the:
version${appfuse.version}/version
I dont know how to solve this.
can you help me for wirtting one pom file for one spring webapp?
thanks
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdorg/groupId
artifactIdeKirolWeb/artifactId
packagingwar/packaging
version0.0.1-SNAPSHOT/version
nameAppFuse Spring MVC Application/name
urlhttp://www.mycompany.com/url
parent
artifactIdekirol/artifactId
groupIdorg/groupId
version0.0.1-SNAPSHOT/version
/parent
prerequisites
maven2.0.9/maven
/prerequisites
licenses
license
name/name
url/url
/license
/licenses
scm
connection/connection
developerConnection/developerConnection
url/url
/scm
issueManagement
system/system
url/url
/issueManagement
developers
developer
id/id
name/name
email/email
timezone/timezone
/developer
/developers
build
defaultGoalinstall/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdappfuse-maven-plugin/artifactId
version${appfuse.version}/version
configuration
genericCore${amp.genericCore}/genericCore
fullSource${amp.fullSource}/fullSource
/configuration
!-- Dependency needed by appfuse:gen-model to connect to
database. --
!-- See http://issues.appfuse.org/browse/APF-868 to learn
more.--
dependencies
dependency
groupId${jdbc.groupId}/groupId
artifactId${jdbc.artifactId}/artifactId
version${jdbc.version}/version
/dependency
/dependencies
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdaspectj-maven-plugin/artifactId
version1.0-beta-2/version
configuration
source1.5/source
verbosetrue/verbose
complianceLevel1.5/complianceLevel
showWeaveInfotrue/showWeaveInfo
aspectLibraries
aspectLibrary
groupIdorg.springframework/groupId
artifactIdspring-aspects/artifactId
/aspectLibrary
/aspectLibraries
/configuration
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
/plugin
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.4/version
configuration
additionalProjectnatures
projectnatureorg.springframework.ide.eclipse.core.springnature/projectnature
/additionalProjectnatures
additionalBuildcommands
buildcommandorg.springframework.ide.eclipse.core.springbuilder/buildcommand
/additionalBuildcommands
downloadSourcestrue/downloadSources
downloadJavadocstrue/downloadJavadocs
wtpversion1.5/wtpversion
/configuration
/plugin
plugin
artifactIdmaven-idea-plugin/artifactId
version2.1/version
configuration
downloadSourcestrue/downloadSources
downloadJavadocstrue/downloadJavadocs
dependenciesAsLibrariestrue/dependenciesAsLibraries
useFullNamesfalse/useFullNames
/configuration
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
Re: Help creating Multi-Module Project
Wendy,
Thanks for catching my typo...
I also now see the issue.. In step ONE .. I needed to create a project using
a mvn archetype:create command (in this case with archetypeId=multi)
It would have created DIRECTORY named multi and pom.. , then I should change
that packaging from jar to pom and proceed from there...
When I then import using m2Eclipse all goes well...
If I may I now have a second question..
I unfortunately (due to IMPORT) have in essence 2 maven projects together.
One was open in workspace before. Is there a way to import project USING pom
and have a new project?
Thanks in advance.
Wendy Smoak-3 wrote:
On Wed, Nov 19, 2008 at 2:46 PM, msclovis [EMAIL PROTECTED] wrote:
5. Changed pom.xml in persist to show dependency:
dependency
groupId${project.groupId}/groupId
artifactIdmodel/artifactId
version${product.version}/version
/dependency
Unless you've introduced a property somewhere, do you mean
${project.version} instead of 'product' ?
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
View this message in context:
http://www.nabble.com/Help-creating-Multi-Module-Project-tp20589965p20590836.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: error into pom.xml file into one spring webapp. SOS
Koxkorrita.. You are using the AppFuse archetypes. (obviously). I have used
them successfully. But if I remember properly there were some issues at
first. What was the error that you were getting?
(You may also want to start this on another thread) or see the AppFuse forum
specifically for issues. But I will try to help.
Mike
Koxkorrita wrote:
Hello
i have one great problem with my maven. i am working into one eclipse and
maven.
i am trying to create one web proyect (basic spring archetype) but always
into the pom file appears the same error.
During 5 days i am trying to solve this problen an i dont solve it.
Can you help me?
1.rs appears one error that says that is not posible to resolve prescanned
pluging artifact.
if i comment the line appearts other error whith the:
version${appfuse.version}/version
I dont know how to solve this.
can you help me for wirtting one pom file for one spring webapp?
thanks
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdorg/groupId
artifactIdeKirolWeb/artifactId
packagingwar/packaging
version0.0.1-SNAPSHOT/version
nameAppFuse Spring MVC Application/name
urlhttp://www.mycompany.com/url
parent
artifactIdekirol/artifactId
groupIdorg/groupId
version0.0.1-SNAPSHOT/version
/parent
prerequisites
maven2.0.9/maven
/prerequisites
licenses
license
name/name
url/url
/license
/licenses
scm
connection/connection
developerConnection/developerConnection
url/url
/scm
issueManagement
system/system
url/url
/issueManagement
developers
developer
id/id
name/name
timezone/timezone
/developer
/developers
build
defaultGoalinstall/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdappfuse-maven-plugin/artifactId
version${appfuse.version}/version
configuration
genericCore${amp.genericCore}/genericCore
fullSource${amp.fullSource}/fullSource
/configuration
!-- Dependency needed by appfuse:gen-model to connect to
database. --
!-- See http://issues.appfuse.org/browse/APF-868 to learn
more.--
dependencies
dependency
groupId${jdbc.groupId}/groupId
artifactId${jdbc.artifactId}/artifactId
version${jdbc.version}/version
/dependency
/dependencies
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdaspectj-maven-plugin/artifactId
version1.0-beta-2/version
configuration
source1.5/source
verbosetrue/verbose
complianceLevel1.5/complianceLevel
showWeaveInfotrue/showWeaveInfo
aspectLibraries
aspectLibrary
groupIdorg.springframework/groupId
artifactIdspring-aspects/artifactId
/aspectLibrary
/aspectLibraries
/configuration
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
/plugin
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.4/version
configuration
additionalProjectnatures
projectnatureorg.springframework.ide.eclipse.core.springnature/projectnature
/additionalProjectnatures
additionalBuildcommands
buildcommandorg.springframework.ide.eclipse.core.springbuilder/buildcommand
/additionalBuildcommands
downloadSourcestrue/downloadSources
downloadJavadocstrue/downloadJavadocs
wtpversion1.5/wtpversion
/configuration
Re: Not happy with maven
Regarding writing your own build tool -- I think this is probably a bad idea, but of course, you are welcome to disagree. If you have decided to abandon Maven, perhaps take a look at buildr and other tools (you already mentioned ivy) that have taken ideas from Maven and incorporated the Central repository as a source of dependency artifacts etc. Of course, you can stick with Maven where it works and then invoke ant for those areas that maven doesn't yet support (or do well). E.g. the signing of artifacts in a specified order should be a simple thing for ant to do. For jars that are not in the repository you could store them in the projects lib/ directory and define a system scope with corresponding systemPath. This practice is discouraged and you would be better off to submit the artifact for inclusion on the central repository and/or convince the project maintainers to do this. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: error into pom.xml file into one spring webapp. SOS
Hi Koxkorrita,
have you tried to build the project from the command line instead? I
have seen this problem other times when creating projects inside
eclipse, seems like from inside eclipse it is not downloading some
plugins. But after you run it from outside eclipse, maven will download
the plugin correctly and eclipse will stop giving this error when it is
restarted. I don't know if this is exactly your problem, but it happened
to me a couple of times and it disappeared after a successful
command-line build.
Hope this helps,
Simone
Koxkorrita wrote:
Hello
i have one great problem with my maven. i am working into one eclipse
and maven.
i am trying to create one web proyect (basic spring archetype) but
always into the pom file appears the same error.
During 5 days i am trying to solve this problen an i dont solve it.
Can you help me?
1.rs appears one error that says that is not posible to resolve
prescanned pluging artifact.
if i comment the line appearts other error whith the:
version${appfuse.version}/version
I dont know how to solve this.
can you help me for wirtting one pom file for one spring webapp?
thanks
?xml version=1.0 encoding=UTF-8?
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdorg/groupId
artifactIdeKirolWeb/artifactId
packagingwar/packaging
version0.0.1-SNAPSHOT/version
nameAppFuse Spring MVC Application/name
urlhttp://www.mycompany.com/url
parent
artifactIdekirol/artifactId
groupIdorg/groupId
version0.0.1-SNAPSHOT/version
/parent
prerequisites
maven2.0.9/maven
/prerequisites
licenses
license
name/name
url/url
/license
/licenses
scm
connection/connection
developerConnection/developerConnection
url/url
/scm
issueManagement
system/system
url/url
/issueManagement
developers
developer
id/id
name/name
email/email
timezone/timezone
/developer
/developers
build
defaultGoalinstall/defaultGoal
plugins
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdappfuse-maven-plugin/artifactId
version${appfuse.version}/version
configuration
genericCore${amp.genericCore}/genericCore
fullSource${amp.fullSource}/fullSource
/configuration
!-- Dependency needed by appfuse:gen-model to connect
to database. --
!-- See http://issues.appfuse.org/browse/APF-868 to
learn more.--
dependencies
dependency
groupId${jdbc.groupId}/groupId
artifactId${jdbc.artifactId}/artifactId
version${jdbc.version}/version
/dependency
/dependencies
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdaspectj-maven-plugin/artifactId
version1.0-beta-2/version
configuration
source1.5/source
verbosetrue/verbose
complianceLevel1.5/complianceLevel
showWeaveInfotrue/showWeaveInfo
aspectLibraries
aspectLibrary
groupIdorg.springframework/groupId
artifactIdspring-aspects/artifactId
/aspectLibrary
/aspectLibraries
/configuration
executions
execution
goals
goalcompile/goal
/goals
/execution
/executions
/plugin
plugin
artifactIdmaven-compiler-plugin/artifactId
version2.0.2/version
configuration
source1.5/source
target1.5/target
/configuration
/plugin
plugin
artifactIdmaven-eclipse-plugin/artifactId
version2.4/version
configuration
additionalProjectnatures
projectnatureorg.springframework.ide.eclipse.core.springnature/projectnature
/additionalProjectnatures
additionalBuildcommands
buildcommandorg.springframework.ide.eclipse.core.springbuilder/buildcommand
/additionalBuildcommands
downloadSourcestrue/downloadSources
Re: Not happy with maven
On Nov 19, 2008, at 1:44 PM, Martin von Gagern wrote: I would much prefer some kind of lib directory, where I could simply drop the library and start using it, to see if it is fit for the job I want to use it for in the first place. You can accomplish that by specifying the dependency with a system scope. You'd tell Maven about your lib directory using systemPath. The maven POM seems to lack a clear concept of task order. This seems especially important in the packaging phase. Suppose I produce a jar which I want to pack200, jarsign, gpgsign, include in an assembly, and gpgsign that assembly again. Clearly order matters a lot. I've had the exact same concern. Anyone have an answer for this? Another aspect of this security issue is the fact that there seems to be no way to ask the user for a password for e.g. jarsigner and hand that to jarsigner by some means other than a command line argument. On a multi-user *nix machine, users can see what commands other users are running, and I don't like them seeing my keystore passphrase. One way to handle this is with the antrun plugin. You can use the input task to prompt for a password and assign it to a property: input message=Password? addproperty=jarsigner.password / Why do I need to configure it again and again for every plugin that operates on source files, instead of specifying it once and for all, with the possibility to override it on a per-file and per-plugin basis if need be? Yes, I can have some common ancestor configure the plugins and use a common property name for the encoding, but this kind of hacks seems to go against the whole idea of POMs describing projects. I'm a little confused. You say you want to specify file encoding in one place, but you don't want to specify it in a common ancestor. How do you envision this working? And interdependence between artifacts (like one containing the other) are not expressed either. Isn't that what modules express? I guess I would prefer clean instructions, like these source files are processed by these build tools in order to produce these artifacts. But that is precisely what a POM is. It defines what source files are to be processed, what build tools to use, and the artifacts that will be produced. It may not be explicit, instead defined in a parent POM or the Super POM, but that's only to eliminate redundancy. You just have to learn how to read a POM file. So I'd like to compile all my code using the latest javac, but substutute the bootclasspath of a different Java API version when compiling the main project code, along with providing the appropriate -source and -target switches. Not possible in Maven, afaik. How about using the compiler plugin's bootclasspath compiler argument? Trevor - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
maven and jboss
hello i am trying to deploy one app into one jboss. my jboss is into c:\jboss can anybody helps me for stating jboss and deploying one app using maven? thanks - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: generate PDF site
I just re-uploaded all our doxia artefacts in the SNAPSHOTs repository Arnaud On Wed, Nov 19, 2008 at 7:23 PM, Wendy Smoak [EMAIL PROTECTED] wrote: You can check out Doxia from https://svn.apache.org/repos/asf/maven/doxia/trunks The doxia-doc-renderer module is under doxia-sitetools. If you need help building it (and better, if you want to help Lukas fix it!) please join us on the development mailing list. :) -- Wendy On Wed, Nov 19, 2008 at 9:27 AM, Marc Lustig [EMAIL PROTECTED] wrote: The build fails due to missing artifact org.apache.maven.doxia:doxia-doc-renderer:jar:1.0-beta-1-SNAPSHOT Do you know where to get this snapshot? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: maven and jboss
can anybody helps me for stating jboss and deploying one app using maven? thanks The cargo plugin was made for exactly this purpose. Google it. Wayne - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
ordering of tasks in profiles and build
Hello maven users, User wsmoak on irc, after helping me to solve this issue, asked me to share my little story with you guys. Basically we have some documentation that is maintained in a wiki, and we want to include it in plain text in our software distribution. So I put a section in build that uses the exec-maven-plugin to run lynx -dump on the url during the package phase, and placed it above the maven-assembly-plugin bit that builds the tar.gz so that it ran first and would be included in the distro. That worked fine. Except that we need the build to work if the system doesn't have lynx. So I moved the lynx piece to a profile with activationfileexists/usr/bin/lynx/exists/file/activation. However, even though I put the profiles section above the build section, the tar.gz was getting built before lynx -dump ran. I noticed in the docs that maven 2.1.x has a prepare-package phase which should solve everything. But I'm stuck on 2.0, so what I did to get around this build order problem was to put the .tar.gz assembly piece in a profile with a contrived activation that always succeeds (*not* the confusingly named activeByDefault), and place that profile below the lynx one. That seems to work. So it seems that executions in profiles are executed after those in build. Perhaps this (or whatever the actual behavior really is) could be documented. Noah - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Missing resource error
Thanks actually i had not given proxy settings in setting.xml, now it's working vdk Walid quot;joquot; Gedeon wrote: Hello vdk, 1) Can you try checking the network connectivity from where you're running maven to the repository? For example: wgedeon:~$ ping repo1.maven.org PING repo1.maven.org (38.97.124.18): 56 data bytes 64 bytes from 38.97.124.18: icmp_seq=0 ttl=53 time=359.066 ms 64 bytes from 38.97.124.18: icmp_seq=1 ttl=53 time=351.119 ms 64 bytes from 38.97.124.18: icmp_seq=2 ttl=53 time=349.108 ms ^C --- repo1.maven.org ping statistics --- 3 packets transmitted, 3 packets received, 0% packet loss round-trip min/avg/max/stddev = 349.108/353.098/359.066/4.299 ms or wgedeon:~$ telnet repo1.maven.org 80 Trying 38.97.124.18... Connected to repo1.maven.org. Escape character is '^]'. ^ZConnection closed by foreign host. 2) Do you connect to the internet using a proxy? If so, you must put the proxy settings in your settings.xml file [1]. --w [1] http://maven.apache.org/ref/2.0.8/maven-settings/settings.html On Tue, Nov 18, 2008 at 11:30 AM, vdk [EMAIL PROTECTED] wrote: I am also hitting the same error and below is the stacktrace, + Error stacktraces are turned on. Maven version: 2.0.9 Java version: 1.5.0_14 OS name: linux version: 2.6.9-55.0.0.0.2.elsmp arch: i386 Family: unix [DEBUG] Building Maven user-level plugin registry from: '/home/label/.m2/plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: '/home/label/apache-maven-2.0.9/conf/plugin-registry.xml' [INFO] Scanning for projects... [INFO] [INFO] Building qa-framework [INFO]task-segment: [clean, install] [INFO] [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [DEBUG] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2) [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [DEBUG] Unable to get resource 'org.apache.maven.plugins:maven-clean-plugin:pom:2.2' from repository central (http://repo1.maven.org/maven2) [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-clean-plugin Version: 2.2 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-clean-plugin:pom:2.2 from the specified remote repositories: central (http://repo1.maven.org/maven2) - vdk Jon Strayer-2 wrote: Is anyone else seeing errors like this? The clean plugin pom url is good. The jar is in the directory. I'm baffled. Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.2/maven-clean-plugin-2.2.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to resolve artifact. GroupId: org.apache.maven.plugins ArtifactId: maven-clean-plugin Version: 2.2 Reason: Unable to download the artifact from any repository org.apache.maven.plugins:maven-clean-plugin:pom:2.2 from the specified remote repositories: central (http://repo1.maven.org/maven2), gwt-ext (http://www.gwt-ext.com/maven2), java.net (http://download.java.net/maven/1), gwt-maven (http://gwt-maven.googlecode.com/svn/trunk/mavenrepo), mygwt (http://mygwt-maven-repo.googlecode.com/svn/trunk), maven2-repository.dev.java.net (http://download.java.net/maven/2), fusionsoftllc-mirror (http://softapp01:8889/nexus/content/groups/public), fusionsoftllc-third-party ( http://softapp01:8889/nexus/content/repositories/thirdparty) -- Esse Quam Videre To Be, rather than to Seem -- View this message in context: http://www.nabble.com/Missing-resource-error-tp20382936p20556973.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Missing-resource-error-tp20382936p20595595.html Sent from the Maven - Users mailing list archive at Nabble.com.
why my own plugin's version cant be SNAPSHOT?
My plugin run without pom, and I use this command to run it:mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec here is the error message: GroupId: com.mycompany.maven.plugins ArtifactId: maven-myplugin-plugin Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository com.mycompany.maven.plugins:maven-myplugin-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: tbmirror-central (http://192.168.207.161:8081/artifactory/repo) but if I upgrade the version to 1.0,and it works!! mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec here is the Message: [INFO] Scanning for projects... Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom [INFO] [ERROR] BUILD ERROR [INFO] I am sure the Maven Core wont download my plugin when the version is 1.0-SNAPSHOT, can throw a Unable to download exception, Maybe you should try the two command in your own machine: mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec you Will see the second one, the Maven will try to download the plugin,but the first one,it do nothing, that's ridiculous!
Re: why my own plugin's version cant be SNAPSHOT?
is the pluginrepository section of your settings.XML restricting tge repo to releases only? Sent from my iPod On 20 Nov 2008, at 06:01, sean.chen(陈思淼) [EMAIL PROTECTED] wrote: My plugin run without pom, and I use this command to run it: mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec here is the error message: GroupId: com.mycompany.maven.plugins ArtifactId: maven-myplugin-plugin Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository com.mycompany.maven.plugins:maven-myplugin-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: tbmirror-central (http://192.168.207.161:8081/artifactory/repo) but if I upgrade the version to 1.0,and it works!! mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec here is the Message: [INFO] Scanning for projects... Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom [INFO] --- - [ERROR] BUILD ERROR [INFO] --- - I am sure the Maven Core wont download my plugin when the version is 1.0-SNAPSHOT, can throw a Unable to download exception, Maybe you should try the two command in your own machine: mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec you Will see the second one, the Maven will try to download the plugin,but the first one,it do nothing, that's ridiculous! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: why my own plugin's version cant be SNAPSHOT?
Im sure not config plugin management segment. 2008/11/20 Stephen Connolly [EMAIL PROTECTED] is the pluginrepository section of your settings.XML restricting tge repo to releases only? Sent from my iPod On 20 Nov 2008, at 06:01, sean.chen(陈思淼) [EMAIL PROTECTED] wrote: My plugin run without pom, and I use this command to run it:mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec here is the error message: GroupId: com.mycompany.maven.plugins ArtifactId: maven-myplugin-plugin Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository com.mycompany.maven.plugins:maven-myplugin-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: tbmirror-central (http://192.168.207.161:8081/artifactory/repo) but if I upgrade the version to 1.0,and it works!! mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec here is the Message: [INFO] Scanning for projects... Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom [INFO] [ERROR] BUILD ERROR [INFO] I am sure the Maven Core wont download my plugin when the version is 1.0-SNAPSHOT, can throw a Unable to download exception, Maybe you should try the two command in your own machine: mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec you Will see the second one, the Maven will try to download the plugin,but the first one,it do nothing, that's ridiculous! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: why my own plugin's version cant be SNAPSHOT?
In ~/.m2/settings.xml settings xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; ... profiles profile ... repositories ... /repositories pluginRepositories pluginRepository idcodehausSnapshots/id nameCodehaus Snapshots/name releases enabledfalse/enabled updatePolicyalways/updatePolicy checksumPolicywarn/checksumPolicy /releases snapshots enabledtrue/enabled updatePolicynever/updatePolicy checksumPolicyfail/checksumPolicy /snapshots urlhttp://snapshots.maven.codehaus.org/maven2/url layoutdefault/layout /pluginRepository /pluginRepositories ... /profile /profiles ... /settings If you don't have snapshots enabled for your plugin repository, maven will not see any snapshots in that repository 2008/11/20 sean.chen(陈思淼) [EMAIL PROTECTED] Im sure not config plugin management segment. 2008/11/20 Stephen Connolly [EMAIL PROTECTED] is the pluginrepository section of your settings.XML restricting tge repo to releases only? Sent from my iPod On 20 Nov 2008, at 06:01, sean.chen(陈思淼) [EMAIL PROTECTED] wrote: My plugin run without pom, and I use this command to run it:mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec here is the error message: GroupId: com.mycompany.maven.plugins ArtifactId: maven-myplugin-plugin Version: 1.0-SNAPSHOT Reason: Unable to download the artifact from any repository com.mycompany.maven.plugins:maven-myplugin-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: tbmirror-central (http://192.168.207.161:8081/artifactory/repo) but if I upgrade the version to 1.0,and it works!! mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec here is the Message: [INFO] Scanning for projects... Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom Downloading: http://192.168.207.161:8081/artifactory/repo/com/mycompany/maven/plugins/maven-myplugin-plugin/1.0/maven-myplugin-plugin-1.0.pom [INFO] [ERROR] BUILD ERROR [INFO] I am sure the Maven Core wont download my plugin when the version is 1.0-SNAPSHOT, can throw a Unable to download exception, Maybe you should try the two command in your own machine: mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0-SNAPSHOT:exec mvn com.mycompany.maven.plugins:maven-myplugin-plugin:1.0:exec you Will see the second one, the Maven will try to download the plugin,but the first one,it do nothing, that's ridiculous! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
