Re: Are group/artifact IDs case sensitive to maven?
Hi Yan, Do you mean the paths (groupId/artifactId/version) and the filename of the artifact? In that context, I believe it depends on your OS.. in Linux it is case-sensitive while in Windows it isn't. HTH, Deng Yan Huang wrote: Hello, Are group/artifact IDs case sensitive to maven? I did a small experiment by compiling offline after manipulating group ID and it seems that maven does care about that ... Please confirm. Thanks Yan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Plugin to verify generated artifact structure?
Quoting Wendy Smoak [EMAIL PROTECTED]: On 10/6/07, Manos Batsis [EMAIL PROTECTED] wrote: ... maybe based on an XML descriptor or something? Or even ideas on what to reuse here? I really need this (I keep messing around with my builds, breaking my distributions along the way) and will probably write it if not available. Any suggestions welcome. What problem are you trying to solve? Making sure that certain files exist in certain places in the main artifact (jar, war etc.)? Exactly. I'm really missing something here right? Thanks, Manos - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: release/buildnumber plugin
I used the release plugin a few weeks back and it worked fine for me. Have you tried release:clean, then release:perform again? -Deng John Coleman wrote: Hi, I just did a release:perform today and it failed. We have done a few before fine. The buildnumber plugin throws an error due to local modifications, however the local mods are in fact the pom.xml, it's tag version and the release backup file, all of which one would expect to be changed/new during a build and should be ignored by the buildnumber plugin? Any ideas? Has the plugin been changed in the last few weeks with respect to this? TIA John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Menu element for modules getting removed from site.xml
I have a master pom with a companion src/site/site.xml. When I
install or deploy the pom, the site.xml file also gets put in the
local or remote repo.
... except that the menu ref=modules / tag is *not* in the deployed site.xml.
I've changed other things, such as misspelling 'parent' in the menu
ref=parent / element to make sure it's really deploying the file
from src/site/site.xml, and it seems to be.
I also tried adding ${modules} and that also got removed.
Can someone confirm that I am not imagining this? Is there a reason for it?
I'd really like projects that use this master pom as their parent to
have links to their sub-modules on their websites by default.
--
Wendy
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Menu element for modules getting removed from site.xml
On 10/7/07, Wendy Smoak [EMAIL PROTECTED] wrote:
I have a master pom with a companion src/site/site.xml. When I
install or deploy the pom, the site.xml file also gets put in the
local or remote repo.
... except that the menu ref=modules / tag is *not* in the deployed
site.xml.
I've changed other things, such as misspelling 'parent' in the menu
ref=parent / element to make sure it's really deploying the file
from src/site/site.xml, and it seems to be.
I also tried adding ${modules} and that also got removed.
Can someone confirm that I am not imagining this? Is there a reason for it?
I'd really like projects that use this master pom as their parent to
have links to their sub-modules on their websites by default.
I checked some of my projects, the menu ref=modules / gets expanded
to a list of all modules. Do you have modules defined in your pom? If not, this
may explain why it disappears.
- Henry
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Menu element for modules getting removed from site.xml
On 10/7/07, Heinrich Nirschl [EMAIL PROTECTED] wrote: I checked some of my projects, the menu ref=modules / gets expanded to a list of all modules. Do you have modules defined in your pom? If not, this may explain why it disappears. Does this happen in site.xml in the repository?Or are you talking about the website itself? (No, the master pom does not have modules.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Fw: Suggested best practice for arranging projects
Hello, Not sure about point 2. but what about collecting the wsdl and API part of the web services in a single project that will be depended upon by the other ones ? This is the standard approach for non J2EE projects and more generally an application of the old segragation of interface and implementation rule. Regards, PS: maybe I missed the point. The answer seems so obvious... -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Site generation with modello fails
I looked at Modello code (and fixed the elememt typo :) )
It seems you didn't define any class as root element, ie a class with
rootElement=true: this root element is not necessary to generate classes,
but it is used by xdoc generation to know which class to set at the top of
the XML document.
Do you confirm?
Hervé
Le samedi 6 octobre 2007, Jörg Schaible a écrit :
Hi folks,
for whatever reason my site generation for a plugin with modello
documentation fails. install works fine, so there is no general problem
with the definitions in the mdo, but site generation is borked:
% ==
[EMAIL PROTECTED] ~/src/BerliOS/JsUnit/maven2 $ mvn -X site
+ Error stacktraces are turned on.
Maven version: 2.0.5
[DEBUG] Building Maven user-level plugin registry
from: '/home/joehni/.m2/plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry
from: '/usr/share/maven-bin-2.0/conf/plugin-registry.xml'
[INFO] Scanning for projects...
[DEBUG] Searching for parent-POM:
de.berlios.jsunit:jsunit-parent::1.3-SNAPSHOT of project:
null:jsunit-maven2-plugin:maven-plugin:null in relative path: ../pom.xml
[DEBUG] Using parent-POM from the project hierarchy at: '../pom.xml' for
project: null:jsunit-maven2-plugin:maven-plugin:null
[INFO]
---
- [INFO] Building JsUnit Maven2 Plugin
[INFO]task-segment: [site]
[INFO]
---
-
...
[INFO] Velocity successfully started.
[DEBUG] Configuring
mojo 'org.codehaus.modello:modello-maven-plugin:1.0-alpha-11:xdoc' --
[DEBUG] (s) basedir = /home/joehni/src/BerliOS/JsUnit/maven2
[DEBUG] (s) model = src/main/mdo/jsunit.mdo
[DEBUG] (s) outputDirectory
= /home/joehni/src/BerliOS/JsUnit/maven2/target/generated-site/xdoc
[DEBUG] (s) packageWithVersion = false
[DEBUG] (s) project = [EMAIL PROTECTED]
[DEBUG] (s) version = 1.0.0
[DEBUG] -- end configuration --
[INFO] [modello:xdoc {execution: jsunit-site}]
[INFO]
outputDirectory:
/home/joehni/src/BerliOS/JsUnit/maven2/target/generated-site/xdoc [INFO]
[ERROR] FATAL ERROR
[INFO]
[INFO] There aren't root elememt for version 1.0.0.
[INFO]
[DEBUG] Trace
org.codehaus.modello.ModelloRuntimeException: There aren't root elememt for
version 1.0.0.
at org.codehaus.modello.model.Model.getRoot(Model.java:107)
at
org.codehaus.modello.plugin.xdoc.XdocGenerator.generateXdoc(XdocGenerator.j
ava:127) at
org.codehaus.modello.plugin.xdoc.XdocGenerator.generate(XdocGenerator.java:
62) at
org.codehaus.modello.core.DefaultModelloCore.generate(DefaultModelloCore.ja
va:277) at
org.codehaus.modello.maven.AbstractModelloGeneratorMojo.execute(AbstractMod
elloGeneratorMojo.java:165) at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManag
er.java:420) at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLif
ecycleExecutor.java:539) at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycl
e(DefaultLifecycleExecutor.java:480) at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLife
cycleExecutor.java:459) at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFai
lures(DefaultLifecycleExecutor.java:311) at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(Def
aultLifecycleExecutor.java:278) at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycl
eExecutor.java:143) at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at
org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at
org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:3
9) at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImp
l.java:25) at java.lang.reflect.Method.invoke(Method.java:324)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
[INFO]
% ==
I've compared my mdo with others in the Maven source and I found no
difference. Here's the declaration in the POM:
% ==
build
plugins
plugin
groupIdorg.codehaus.modello/groupId
artifactIdmodello-maven-plugin/artifactId
Re: Simple WAR file question
Anyone have any idea on this one? -- View this message in context: http://www.nabble.com/Simple-WAR-file-question-tf4573507s177.html#a13088353 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Repository Central is blacklisted?
I'm trying to follow the instructions at http://cocoon.apache.org/2.2/1159_1_1.html Am I doing something wrong? Why would central be blacklisted? Thanks, Siegfried -bash-3.2$ pwd /usr/bin -bash-3.2$ cd c\:/dev/sandboxes/ -bash-3.2$ mkdir cocoon -bash-3.2$ mvn archetype:create -DarchetypeGroupId=org.apache.cocoon -DarchetypeArtifactId=cocoon-22-archetype-block -DarchetypeVersion=1.0.0-RC1 -DgroupId=com.mycompany -DartifactId=myBlock1 [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] org.apache.maven.plugins: checking for updates from central [WARNING] repository metadata for: 'org.apache.maven.plugins' could not be retrieved from repository: central due to an error: Error transferring file [INFO] Repository 'central' will be blacklisted [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-archetype-plugin' does not exist or no valid version could be found [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 23 seconds [INFO] Finished at: Sun Oct 07 21:23:40 MDT 2007 [INFO] Final Memory: 1M/4M [INFO] -bash-3.2$
