You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@maven.apache.org by Ray Ward <wa...@gmail.com> on 2006/02/17 20:18:15 UTC
[m202] Linux oddity for accessing maven-architype-plugin?
I ran the Getting Started stuff on WinXP with no problems here.
But on a local Linux server, after downloading and installing, I get the
error:
The plugin 'org.apache.maven.plugins:maven-architype-plugin' does not exist
or no valid version could be found
And sure enough, there's no plugin JAR file. mvn -v works.
Anything extra need to be done for Linux as opposed to XP?
TIA,
Ray
Re: [m202] Linux oddity for accessing maven-architype-plugin?
Posted by Ray Ward <wa...@gmail.com>.
Duh! Kept reading what I *thought* I typed... Thanks!
On 2/17/06, Wendy Smoak <ws...@gmail.com> wrote:
>
> On 2/17/06, Ray Ward <wa...@gmail.com> wrote:
>
> > I ran the Getting Started stuff on WinXP with no problems here.
> >
> > But on a local Linux server, after downloading and installing, I get the
> > error:
> > The plugin 'org.apache.maven.plugins:maven-architype-plugin' does not
> exist
> > or no valid version could be found
> > And sure enough, there's no plugin JAR file. mvn -v works.
>
> Unless that's just a typo, the spelling should be 'archetype'.
>
> --
> Wendy
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package
name ..."
Posted by Jochen Wiedmann <jo...@gmail.com>.
Alexandre Poitras wrote:
> No I mean I put a name there and it is found, I can see it when the
> plugins is running. I checked the file path and it is correct. But I
> still end up with this exception.
Please run maven with the -X option and let me see the output.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package name ..."
Posted by Alexandre Poitras <al...@gmail.com>.
No I mean I put a name there and it is found, I can see it when the
plugins is running. I checked the file path and it is correct. But I
still end up with this exception.
On 2/21/06, Jochen Wiedmann <jo...@gmail.com> wrote:
> Alexandre Poitras wrote:
> > By the way, when I use the configuration element :
> > <schemas><value></value></schemas>
>
> That means, you are configuring absolutely no schemas, isn't it? The
> value should be something like src/schemas/*.xsd.
>
> > [WARNING] Schema specification returns no result
> > and no class are generated. It only works if I use the default
> > directory (src/jaxme) but I prefer to use (src/main/xsd).
>
> That's indeed what I would expect.
>
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package
name ..."
Posted by Jochen Wiedmann <jo...@gmail.com>.
Alexandre Poitras wrote:
> By the way, when I use the configuration element :
> <schemas><value></value></schemas>
That means, you are configuring absolutely no schemas, isn't it? The
value should be something like src/schemas/*.xsd.
> [WARNING] Schema specification returns no result
> and no class are generated. It only works if I use the default
> directory (src/jaxme) but I prefer to use (src/main/xsd).
That's indeed what I would expect.
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package name ..."
Posted by Alexandre Poitras <al...@gmail.com>.
By the way, when I use the configuration element :
<schemas><value></value></schemas>
The plugin seem to be able to find the result but I get a warning like this :
[WARNING] Schema specification returns no result
and no class are generated. It only works if I use the default
directory (src/jaxme) but I prefer to use (src/main/xsd).
On 2/21/06, Alexandre Poitras <al...@gmail.com> wrote:
> Thank you, I was referring to the schema/schemas problem and the
> package name bug. Thankf for the info.
>
> On 2/21/06, Jochen Wiedmann <jo...@gmail.com> wrote:
> >
> > Hi, Alexandre,
> >
> > Alexandre Poitras wrote:
> >
> > > The site looks complety out of date,
> >
> > I do not know, what site you are referring to.
> >
> > http://ws.apache.org/jaxme/mp/changes-report.html
> >
> > was updated just three days ago with the release of 1.0.3.
> >
> > > none of the properties specified seem to work.
> >
> > Indeed, the packageName property didn't work, but this was fixed in
> > 1.0.3. Additionally, the docs did contain the element name "schema",
> > rather than "schemas", but this has been fixed as well. For any other
> > problem, I'd ask you to contact the jaxme developers mailing list or
> > file an issue in Jira. (Please note, that "Project Info" does *not*
> > point you to the maven users list.)
> >
> >
> > Jochen
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> > For additional commands, e-mail: users-help@maven.apache.org
> >
> >
>
>
> --
> Alexandre Poitras
> Québec, Canada
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package name ..."
Posted by Alexandre Poitras <al...@gmail.com>.
Thank you, I was referring to the schema/schemas problem and the
package name bug. Thankf for the info.
On 2/21/06, Jochen Wiedmann <jo...@gmail.com> wrote:
>
> Hi, Alexandre,
>
> Alexandre Poitras wrote:
>
> > The site looks complety out of date,
>
> I do not know, what site you are referring to.
>
> http://ws.apache.org/jaxme/mp/changes-report.html
>
> was updated just three days ago with the release of 1.0.3.
>
> > none of the properties specified seem to work.
>
> Indeed, the packageName property didn't work, but this was fixed in
> 1.0.3. Additionally, the docs did contain the element name "schema",
> rather than "schemas", but this has been fixed as well. For any other
> problem, I'd ask you to contact the jaxme developers mailing list or
> file an issue in Jira. (Please note, that "Project Info" does *not*
> point you to the maven users list.)
>
>
> Jochen
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package
name ..."
Posted by Jochen Wiedmann <jo...@gmail.com>.
Hi, Alexandre,
Alexandre Poitras wrote:
> The site looks complety out of date,
I do not know, what site you are referring to.
http://ws.apache.org/jaxme/mp/changes-report.html
was updated just three days ago with the release of 1.0.3.
> none of the properties specified seem to work.
Indeed, the packageName property didn't work, but this was fixed in
1.0.3. Additionally, the docs did contain the element name "schema",
rather than "schemas", but this has been fixed as well. For any other
problem, I'd ask you to contact the jaxme developers mailing list or
file an issue in Jira. (Please note, that "Project Info" does *not*
point you to the maven users list.)
Jochen
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package name ..."
Posted by Alexandre Poitras <al...@gmail.com>.
The site looks complety out of date, none of the properties specified
seem to work. I'm gonna take a look in the source. In the mean time,
if you want to use it, you need to specify a "targetNamespace" on your
root element or use the jaxb:... elements inside your schema. By the
way, there is another JAXB plugin supposed to come out this week, hope
it will work better.
On 2/17/06, rgc <li...@yahoo.com> wrote:
> Hi,
> I´m new to Maven and this list, greetings. I´ve got 2 points to question:
> 1. The tag name that works for overiding schema directories in the
> maven-jaxme-plugin 1.0.1 is <schemas>, not <schema> as said in the url´s
> http://ws.apache.org/jaxme/mp/use.html and
> http://ws.apache.org/jaxme/mp/properties.html(how can someone correct this? or
> tell to the responsible for this documentation?). It took me a time to figure
> out, so it could be saved for others.
> 2. I can´t make the maven-jaxme-plugin 1.0.1 to recognize the tag
> <packageName>, so it keeps reporting the error: "Unable to derive package name
> from an empty namespace URI."
> Here´s the plugin section in my pom.xml:
> <plugin>
> <groupId>org.apache.ws.jaxme</groupId>
> <artifactId>maven-jaxme-plugin</artifactId>
> <configuration>
> <schemas>
> <value>src/xsd/*.xsd</value>
> </schemas>
> <packageName>com.myApp.jaxb</packageName>
> </configuration>
> <executions>
> <execution>
> <goals>
> <goal>jaxme</goal>
> </goals>
> </execution>
> </executions>
> </plugin>
>
> Does anyone can understand why the packageName has no effect in this case?
> Thanks
> Rommell G. Caixeta
> follows -X debug output:
>
> E:\projetosWTP\JAXB-Infoseg>mvn -X compile
> + Error stacktraces are turned on.
> [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
> Settin
> gs\rommell.caixeta\.m2\plugin-registry.xml'
> [DEBUG] Building Maven global-level plugin registry from:
> 'E:\ARQUIV~1\APACHE~1\
> MAVEN-~1.2\bin\..\conf\plugin-registry.xml'
> [INFO] Scanning for projects...
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Building Maven Quick Start Archetype
> [INFO] task-segment: [compile]
> [INFO]
> -------------------------------------------------------------------------
> ---
> [DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-resour
> ces-plugin:maven-plugin:2.1
> [DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-compil
> er-plugin:maven-plugin:2.0
> [DEBUG] maven-jaxme-plugin: resolved to version 1.0.1 from repository central
> [DEBUG] gov.infoseg.jaxbInfoseg:JAXB-Infoseg:jar:1.0-SNAPSHOT (selected for
> null
> )
> [DEBUG] junit:junit:jar:3.8.1 (selected for test)
> [DEBUG] org.apache.ws.jaxme:maven-jaxme-plugin:maven-plugin:1.0.1 (selected for
> runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> plexus:plexus-uti
> ls:jar:1.0.3
> [DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
> [DEBUG] org.apache.ws.jaxme:jaxme2:jar:0.5.1 (selected for runtime)
> [DEBUG] org.apache.ws.jaxme:jaxmeapi:jar:0.5.1 (selected for runtime)
> [DEBUG] org.apache.ws.jaxme:jaxmejs:jar:0.5.1 (selected for runtime)
> [DEBUG] org.apache.ws.jaxme:jaxmexs:jar:0.5.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-projec
> t:jar:2.0
> [DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
> [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
> (select
> ed for runtime)
> [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
> [DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> org.apache.maven:
> maven-artifact:jar:2.0
> [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> org.apache.maven:
> maven-model:jar:2.0
> [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> org.apache.maven:
> maven-artifact-manager:jar:2.0
> [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for
> runtim
> e)
> [DEBUG] Retrieving parent-POM from the repository for project:
> org.apache.maven:
> maven-repository-metadata:jar:2.0
> [DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for
> r
> untime)
> [DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5
> (selecte
> d for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> null:maven-profil
> e:jar:2.0
> [DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime)
> [DEBUG] Retrieving parent-POM from the repository for project:
> org.apache.maven:
> maven-plugin-api:jar:2.0
> [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime)
> [DEBUG] Configuring mojo 'org.apache.ws.jaxme:maven-jaxme-plugin:1.0.1:jaxme'
> --
> >
> [DEBUG] (f) classpathElements = [E:\projetosWTP\JAXB-Infoseg\target\classes]
> [DEBUG] (f) extension = false
> [DEBUG] (f) force = false
> [DEBUG] (f) packageName = gov.infoseg.jaxbInfoseg
> [DEBUG] (f) project = org.apache.maven.project.MavenProject@e84e3101
> [DEBUG] (f) readOnly = false
> [DEBUG] (f) removingOldOutput = false
> [DEBUG] (f) resourceTarget =
> E:\projetosWTP\JAXB-Infoseg\target/jaxme/resource
> s
> [DEBUG] (f) schemas = [Ljava.lang.String;@1bcdbf6
> [DEBUG] (f) srcTarget = E:\projetosWTP\JAXB-Infoseg\target/jaxme/java
> [DEBUG] (f) validating = false
> [DEBUG] -- end configuration --
> [INFO] [jaxme:jaxme {execution: default}]
> [DEBUG] Using classpath file:/E:/projetosWTP/JAXB-Infoseg/target/classes/
> [DEBUG] No produced files found, disabling uptodate check.
> [DEBUG] Schema reader class:
> org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaRea
> der
> [DEBUG] org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(File): ->,
> E:\
> projetosWTP\JAXB-Infoseg\src\xsd\sinivem\requisicao_dados_condutor.xsd
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse: ->,
> file:/
> E:/projetosWTP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.getSGFactory: ->
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.getSGFactory:
> Cre
> ated instance of org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.getSGFactory:
> <-,
> org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl@baa466
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse: Parser =
> o
> rg.apache.ws.jaxme.xs.jaxb.impl.JAXBParser@fdb00d, validating = false
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse: Schema =
> o
> rg.apache.ws.jaxme.xs.jaxb.impl.JAXBSchemaImpl@be41ec
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.init: ->
> [DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.init:
> Childorg.apache
> .ws.jaxme.xs.jaxb.impl.JAXBElementImpl@17ec9f7
> [DEBUG]
> org.apache.ws.jaxme.generator.sg.impl.JAXBObjectSG.<init>(XSObject,Conte
> xt): ->, parametrosRequisicaoDadosCondutor, null
> [INFO]
> -------------------------------------------------------------------------
> ---
> [ERROR] BUILD ERROR
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] At
> file:/E:/projetosWTP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_con
> dutor.xsd, line 3, column 56: Unable to derive package name from an empty
> namesp
> ace URI. Use the schemaBindings to specify a package name.
>
> [INFO]
> -------------------------------------------------------------------------
> ---
> [DEBUG] Trace
> org.apache.maven.lifecycle.LifecycleExecutionException: At
> file:/E:/projetosWTP/
> JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd, line 3, column 56:
> U
> nable to derive package name from an empty namespace URI. Use the
> schemaBindings
> to specify a package name.
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:472)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:451)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:303)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:270)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:139)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
>
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: At
> file:/E:/projetosW
> TP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd, line 3, column
> 56
> : Unable to derive package name from an empty namespace URI. Use the
> schemaBindi
> ngs to specify a package name.
> at
> org.apache.ws.jaxme.maven.plugins.JaxMeGoal.execute(JaxMeGoal.java:53
> 8)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:415)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:531)
> ... 16 more
> Caused by: org.apache.ws.jaxme.xs.parser.impl.LocSAXException: At
> file:/E:/proje
> tosWTP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd, line 3,
> colum
> n 56: Unable to derive package name from an empty namespace URI. Use the
> schemaB
> indings to specify a package name.
> at
> org.apache.ws.jaxme.generator.sg.impl.AbstractContext.getPackageNameF
> romURI(AbstractContext.java:129)
> at
> org.apache.ws.jaxme.generator.sg.impl.AbstractContext.getPackageName(
> AbstractContext.java:85)
> at
> org.apache.ws.jaxme.generator.sg.impl.GlobalContext.<init>(GlobalCont
> ext.java:68)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBObjectSG.<init>(JAXBObjectS
> G.java:105)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBObjectSG.<init>(JAXBObjectS
> G.java:70)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory.newObjectSG(JAXBS
> GFactory.java:127)
> at
> org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl.newObjectSG(SGFac
> toryImpl.java:65)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory.getObjectSG(JAXBS
> GFactory.java:133)
> at
> org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl.getObjectSG(SGFac
> toryImpl.java:69)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.getElement(JAXBSch
> emaSG.java:196)
> at
> org.apache.ws.jaxme.generator.sg.impl.SchemaSGImpl.getElement(SchemaS
> GImpl.java:51)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.init(JAXBSchemaSG.
> java:131)
> at
> org.apache.ws.jaxme.generator.sg.impl.SchemaSGImpl.init(SchemaSGImpl.
> java:127)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory.getSchemaSG(JAXBS
> GFactory.java:174)
> at
> org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl.getSchemaSG(SGFac
> toryImpl.java:57)
> at
> org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse(JAXBSche
> maReader.java:137)
> at
> org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(GeneratorIm
> pl.java:147)
> at
> org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(GeneratorIm
> pl.java:180)
> at
> org.apache.ws.jaxme.maven.plugins.JaxMeGoal.execute(JaxMeGoal.java:53
> 6)
> ... 18 more
> [INFO]
> -------------------------------------------------------------------------
> ---
> [INFO] Total time: 2 seconds
> [INFO] Finished at: Fri Feb 17 18:46:12 GMT 2006
> [INFO] Final Memory: 3M/5M
> [INFO]
> -------------------------------------------------------------------------
> ---
>
>
> __________________________________________________
> Do You Yahoo!?
> Tired of spam? Yahoo! Mail has the best spam protection around
> http://mail.yahoo.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
> For additional commands, e-mail: users-help@maven.apache.org
>
>
--
Alexandre Poitras
Québec, Canada
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: maven-jaxme-plugin 1.0.1 problem - "Unable to derive package name ..." [M202]
Posted by rgc <li...@yahoo.com>.
Just forgot to mention, I´m using maven 202
--- rgc <li...@yahoo.com> wrote:
> Hi,
> I´m new to Maven and this list, greetings. I´ve got 2 points to question:
> 1. The tag name that works for overiding schema directories in the
> maven-jaxme-plugin 1.0.1 is <schemas>, not <schema> as said in the url´s
> http://ws.apache.org/jaxme/mp/use.html and
...
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
maven-jaxme-plugin 1.0.1 problem - "Unable to derive package name ..."
Posted by rgc <li...@yahoo.com>.
Hi,
I´m new to Maven and this list, greetings. I´ve got 2 points to question:
1. The tag name that works for overiding schema directories in the
maven-jaxme-plugin 1.0.1 is <schemas>, not <schema> as said in the url´s
http://ws.apache.org/jaxme/mp/use.html and
http://ws.apache.org/jaxme/mp/properties.html(how can someone correct this? or
tell to the responsible for this documentation?). It took me a time to figure
out, so it could be saved for others.
2. I can´t make the maven-jaxme-plugin 1.0.1 to recognize the tag
<packageName>, so it keeps reporting the error: "Unable to derive package name
from an empty namespace URI."
Here´s the plugin section in my pom.xml:
<plugin>
<groupId>org.apache.ws.jaxme</groupId>
<artifactId>maven-jaxme-plugin</artifactId>
<configuration>
<schemas>
<value>src/xsd/*.xsd</value>
</schemas>
<packageName>com.myApp.jaxb</packageName>
</configuration>
<executions>
<execution>
<goals>
<goal>jaxme</goal>
</goals>
</execution>
</executions>
</plugin>
Does anyone can understand why the packageName has no effect in this case?
Thanks
Rommell G. Caixeta
follows -X debug output:
E:\projetosWTP\JAXB-Infoseg>mvn -X compile
+ Error stacktraces are turned on.
[DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and
Settin
gs\rommell.caixeta\.m2\plugin-registry.xml'
[DEBUG] Building Maven global-level plugin registry from:
'E:\ARQUIV~1\APACHE~1\
MAVEN-~1.2\bin\..\conf\plugin-registry.xml'
[INFO] Scanning for projects...
[INFO]
-------------------------------------------------------------------------
---
[INFO] Building Maven Quick Start Archetype
[INFO] task-segment: [compile]
[INFO]
-------------------------------------------------------------------------
---
[DEBUG] maven-resources-plugin: resolved to version 2.1 from repository central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-resour
ces-plugin:maven-plugin:2.1
[DEBUG] maven-compiler-plugin: resolved to version 2.0 from repository central
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-compil
er-plugin:maven-plugin:2.0
[DEBUG] maven-jaxme-plugin: resolved to version 1.0.1 from repository central
[DEBUG] gov.infoseg.jaxbInfoseg:JAXB-Infoseg:jar:1.0-SNAPSHOT (selected for
null
)
[DEBUG] junit:junit:jar:3.8.1 (selected for test)
[DEBUG] org.apache.ws.jaxme:maven-jaxme-plugin:maven-plugin:1.0.1 (selected for
runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
plexus:plexus-uti
ls:jar:1.0.3
[DEBUG] plexus:plexus-utils:jar:1.0.3 (selected for runtime)
[DEBUG] org.apache.ws.jaxme:jaxme2:jar:0.5.1 (selected for runtime)
[DEBUG] org.apache.ws.jaxme:jaxmeapi:jar:0.5.1 (selected for runtime)
[DEBUG] org.apache.ws.jaxme:jaxmejs:jar:0.5.1 (selected for runtime)
[DEBUG] org.apache.ws.jaxme:jaxmexs:jar:0.5.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-projec
t:jar:2.0
[DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime)
[DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8
(select
ed for runtime)
[DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime)
[DEBUG] junit:junit:jar:3.8.1 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:
maven-artifact:jar:2.0
[DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:
maven-model:jar:2.0
[DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:
maven-artifact-manager:jar:2.0
[DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for
runtim
e)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:
maven-repository-metadata:jar:2.0
[DEBUG] org.apache.maven:maven-repository-metadata:jar:2.0 (selected for
r
untime)
[DEBUG] org.apache.maven.wagon:wagon-provider-api:jar:1.0-alpha-5
(selecte
d for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
null:maven-profil
e:jar:2.0
[DEBUG] org.apache.maven:maven-profile:jar:2.0 (selected for runtime)
[DEBUG] Retrieving parent-POM from the repository for project:
org.apache.maven:
maven-plugin-api:jar:2.0
[DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 (selected for runtime)
[DEBUG] Configuring mojo 'org.apache.ws.jaxme:maven-jaxme-plugin:1.0.1:jaxme'
--
>
[DEBUG] (f) classpathElements = [E:\projetosWTP\JAXB-Infoseg\target\classes]
[DEBUG] (f) extension = false
[DEBUG] (f) force = false
[DEBUG] (f) packageName = gov.infoseg.jaxbInfoseg
[DEBUG] (f) project = org.apache.maven.project.MavenProject@e84e3101
[DEBUG] (f) readOnly = false
[DEBUG] (f) removingOldOutput = false
[DEBUG] (f) resourceTarget =
E:\projetosWTP\JAXB-Infoseg\target/jaxme/resource
s
[DEBUG] (f) schemas = [Ljava.lang.String;@1bcdbf6
[DEBUG] (f) srcTarget = E:\projetosWTP\JAXB-Infoseg\target/jaxme/java
[DEBUG] (f) validating = false
[DEBUG] -- end configuration --
[INFO] [jaxme:jaxme {execution: default}]
[DEBUG] Using classpath file:/E:/projetosWTP/JAXB-Infoseg/target/classes/
[DEBUG] No produced files found, disabling uptodate check.
[DEBUG] Schema reader class:
org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaRea
der
[DEBUG] org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(File): ->,
E:\
projetosWTP\JAXB-Infoseg\src\xsd\sinivem\requisicao_dados_condutor.xsd
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse: ->,
file:/
E:/projetosWTP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.getSGFactory: ->
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.getSGFactory:
Cre
ated instance of org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.getSGFactory:
<-,
org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl@baa466
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse: Parser =
o
rg.apache.ws.jaxme.xs.jaxb.impl.JAXBParser@fdb00d, validating = false
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse: Schema =
o
rg.apache.ws.jaxme.xs.jaxb.impl.JAXBSchemaImpl@be41ec
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.init: ->
[DEBUG] org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.init:
Childorg.apache
.ws.jaxme.xs.jaxb.impl.JAXBElementImpl@17ec9f7
[DEBUG]
org.apache.ws.jaxme.generator.sg.impl.JAXBObjectSG.<init>(XSObject,Conte
xt): ->, parametrosRequisicaoDadosCondutor, null
[INFO]
-------------------------------------------------------------------------
---
[ERROR] BUILD ERROR
[INFO]
-------------------------------------------------------------------------
---
[INFO] At
file:/E:/projetosWTP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_con
dutor.xsd, line 3, column 56: Unable to derive package name from an empty
namesp
ace URI. Use the schemaBindings to specify a package name.
[INFO]
-------------------------------------------------------------------------
---
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: At
file:/E:/projetosWTP/
JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd, line 3, column 56:
U
nable to derive package name from an empty namespace URI. Use the
schemaBindings
to specify a package name.
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
fecycle(DefaultLifecycleExecutor.java:472)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
ltLifecycleExecutor.java:451)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
dleFailures(DefaultLifecycleExecutor.java:303)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
ts(DefaultLifecycleExecutor.java:270)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
fecycleExecutor.java:139)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:249)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
sorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
Caused by: org.apache.maven.plugin.MojoExecutionException: At
file:/E:/projetosW
TP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd, line 3, column
56
: Unable to derive package name from an empty namespace URI. Use the
schemaBindi
ngs to specify a package name.
at
org.apache.ws.jaxme.maven.plugins.JaxMeGoal.execute(JaxMeGoal.java:53
8)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
nManager.java:415)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
ultLifecycleExecutor.java:531)
... 16 more
Caused by: org.apache.ws.jaxme.xs.parser.impl.LocSAXException: At
file:/E:/proje
tosWTP/JAXB-Infoseg/src/xsd/sinivem/requisicao_dados_condutor.xsd, line 3,
colum
n 56: Unable to derive package name from an empty namespace URI. Use the
schemaB
indings to specify a package name.
at
org.apache.ws.jaxme.generator.sg.impl.AbstractContext.getPackageNameF
romURI(AbstractContext.java:129)
at
org.apache.ws.jaxme.generator.sg.impl.AbstractContext.getPackageName(
AbstractContext.java:85)
at
org.apache.ws.jaxme.generator.sg.impl.GlobalContext.<init>(GlobalCont
ext.java:68)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBObjectSG.<init>(JAXBObjectS
G.java:105)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBObjectSG.<init>(JAXBObjectS
G.java:70)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory.newObjectSG(JAXBS
GFactory.java:127)
at
org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl.newObjectSG(SGFac
toryImpl.java:65)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory.getObjectSG(JAXBS
GFactory.java:133)
at
org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl.getObjectSG(SGFac
toryImpl.java:69)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.getElement(JAXBSch
emaSG.java:196)
at
org.apache.ws.jaxme.generator.sg.impl.SchemaSGImpl.getElement(SchemaS
GImpl.java:51)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaSG.init(JAXBSchemaSG.
java:131)
at
org.apache.ws.jaxme.generator.sg.impl.SchemaSGImpl.init(SchemaSGImpl.
java:127)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSGFactory.getSchemaSG(JAXBS
GFactory.java:174)
at
org.apache.ws.jaxme.generator.sg.impl.SGFactoryImpl.getSchemaSG(SGFac
toryImpl.java:57)
at
org.apache.ws.jaxme.generator.sg.impl.JAXBSchemaReader.parse(JAXBSche
maReader.java:137)
at
org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(GeneratorIm
pl.java:147)
at
org.apache.ws.jaxme.generator.impl.GeneratorImpl.generate(GeneratorIm
pl.java:180)
at
org.apache.ws.jaxme.maven.plugins.JaxMeGoal.execute(JaxMeGoal.java:53
6)
... 18 more
[INFO]
-------------------------------------------------------------------------
---
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Feb 17 18:46:12 GMT 2006
[INFO] Final Memory: 3M/5M
[INFO]
-------------------------------------------------------------------------
---
__________________________________________________
Do You Yahoo!?
Tired of spam? Yahoo! Mail has the best spam protection around
http://mail.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org
Re: [m202] Linux oddity for accessing maven-architype-plugin?
Posted by Wendy Smoak <ws...@gmail.com>.
On 2/17/06, Ray Ward <wa...@gmail.com> wrote:
> I ran the Getting Started stuff on WinXP with no problems here.
>
> But on a local Linux server, after downloading and installing, I get the
> error:
> The plugin 'org.apache.maven.plugins:maven-architype-plugin' does not exist
> or no valid version could be found
> And sure enough, there's no plugin JAR file. mvn -v works.
Unless that's just a typo, the spelling should be 'archetype'.
--
Wendy
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@maven.apache.org
For additional commands, e-mail: users-help@maven.apache.org