Hello, I'm using trying to create an archetype, and I want to use some
properties. However doesn't reference the included property
if it's already define, as I thought would be the norm. Here's an example:
[...]
${earname}
When I generate this project
2009/8/6 EJ Ciramella :
> That should be clarified in the documentation and in the error.
Agree concerning documentation.
>
> Saying it can't find the "document" element is NOT enough to diagnose this
> error.
We can only display the one coming from the xml parser...
>
> -Original Message
Thanks, Brett. That's exactly what the problem was. I found it about
an hour after I left the original email. I thought I had cleared all of
them out a week or two ago. Turns out that the branch was taken prior
to that. It certainly was not easy to spot.
Dave
Brett Randall wrote:
> On Thu, A
2009/8/5 David Weintraub :
> On Tue, Aug 4, 2009 at 6:57 PM, Alexander wrote:
>>
>> You could declare these documentaion as dependecy. Then use dependency
>> plugin for unpacking this module.
>> See http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
>>
>
> On Tue, Aug 4, 200
On Thu, Aug 6, 2009 at 5:53 AM, David C. Hicks wrote:
> I am getting this error when attempting to release:prepare from a branch:
>
>Unable to tag SCM
>Provider message:
>The svn tag command failed.
>Command output:
>svn: Commit failed (details follow):
>svn: Source url
>
That should be clarified in the documentation and in the error.
Saying it can't find the "document" element is NOT enough to diagnose this
error.
-Original Message-
From: Olivier Lamy [mailto:ol...@apache.org]
Sent: Wednesday, August 05, 2009 11:36 AM
To: Maven Users List
Subject: Re:
I have a Webstart application that I'm generating a WAR file to deploy on
JBoss using the Maven Webstart plugin.
I have included the JBoss client POM in my application POM to grab the JBoss
client dependencies for JNDI and EJB. When the plugin creates the WAR file,
it is including the POM with u
No, I'm actually looking at a deployed site.
mvn site site:deploy
There are simply no "index.html" files in any of the modules' directories.
Dennis Lundberg wrote:
> Are you running into this?
> http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and
Are you running into this?
http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site
David C. Hicks wrote:
> Is there some way to get the Site plugin to create an index.html if one
> is not supplied? I really don't want
Oh, already solved. [?]
2009/8/6 Alexander
> My project X have three modules A, B, C. Module C depends on A and B.
> I declared A, B, C pom files inherit X pom file.
> I declared A, B, C as modules in X pom file.
> Declared A and B as dependencies for C.
>
> Cant generate idea project with "mvn
Search around a lot for this type of functionality but I ended up writing my
own plugin to do this.
Murali Pottlapelli wrote:
>
> Hi All,
> While searching through mailing list I found "archetypes to add files to
> an existing project",
> http://www.nabble.com/Using-Archetypes-to-Add-to-an-E
I am getting this error when attempting to release:prepare from a branch:
Unable to tag SCM
Provider message:
The svn tag command failed.
Command output:
svn: Commit failed (details follow):
svn: Source url
'svn://svn.enttek.com/allureglobal/dm/branches/salient-0.9.22'
http://jira.codehaus.org/browse/MRELEASE-297
On Tue, Aug 4, 2009 at 10:45 PM, Brett Randall wrote:
> On Wed, Aug 5, 2009 at 12:21 PM, Brian Fox wrote:
>
>> That's an ld bug in the release plugin. It bumps the property to
>> the being released version but doesn't bump it to the next dev
>> ver
Is there some way to get the Site plugin to create an index.html if one
is not supplied? I really don't want to have to go set up src/site for
every module in my project, but it seems like the site that gets
generated won't work if I don't. When I click on one of the module
links, I'm taken to th
> >
I don't know if you are still looking for an answer to how to fix this
problem but what I found to fix the problem for me was to change the
maven-source-plugin goal from jar to jar-no-fork. I also had to add
2.1 as well. You may also need to change test-jar to
test-jar-no-fork.
The informa
I've updated the mavenVersion property on the 2.2.x branch.
-john
Brett Randall wrote:
On Wed, Aug 5, 2009 at 12:21 PM, Brian Fox wrote:
That's an ld bug in the release plugin. It bumps the property to
the being released version but doesn't bump it to the next dev
version.
On Tue, Aug 4
Sure namespace declaration is needed if you use validation.
2009/8/5 EJ Ciramella :
> Nope, is that needed? And if it is, that should be called out in the
> site output for the changes plugin...
>
> -Original Message-
> From: Olivier Lamy [mailto:ol...@apache.org]
> Sent: Wednesday, Augus
Nope, is that needed? And if it is, that should be called out in the
site output for the changes plugin...
-Original Message-
From: Olivier Lamy [mailto:ol...@apache.org]
Sent: Wednesday, August 05, 2009 11:28 AM
To: Maven Users List
Subject: Re: validate changes document
Hi,
Do you ha
Hi,
Do you have declared namespaces ?
As this :
http://maven.apache.org/changes/1.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/changes/1.0.0
http://maven.apache.org/xsd/changes-1.0.0.xsd";>
--
Olivier
2009/8/5 EJ Ciramella :
> Hello
Hello all - I'd like to leverage the "validate-changes" part of the
maven-changes-plugin, but no matter what I do, I get this:
Caused by:
org.apache.maven.plugin.changes.schema.SchemaValidatorException:
SAXException : cvc-elt.1: Cannot find the declaration of element
'document'.
Even when clear
Thanks. It was a version error. 2.3 did the trick.
Alexander wrote:
Oh, you right. But you already answered your question!
Use excludeDefaultDirectories. It works fine, really. Be sure you use
2.3 version of maven-clean-plugin. (as it mentioned in documentation
this option work only since 2.3
Maybe you sould try this
http://www.pohlidame.cz/insolvencni-rejstrik/maven-unzip-plugin.html?
2009/8/5 David Weintraub
> On Tue, Aug 4, 2009 at 6:57 PM, Alexander wrote:
>
>> You could declare these documentaion as dependecy. Then use dependency
>> plugin for unpacking this module. [?]
>> See
On Tue, Aug 4, 2009 at 6:57 PM, Alexander wrote:
> You could declare these documentaion as dependecy. Then use dependency
> plugin for unpacking this module. [?]
> See
> http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html
>
>
On Tue, Aug 4, 2009 at 8:39 PM, Brian Fox wrote:
Sorry — hit send by accident.
On 5 Aug 2009, at 14:43, Dominic Mitchell wrote:
On 5 Aug 2009, at 14:10, Stephen Connolly wrote:
if you think about this a bit more you will realise that what you
are asking
for does not make sense (unless you are trying to configure the
plugin that
you are
Hello,
I have the following use case:
1. artifact is packaging jar
2. jar plugin is configured to add classifier
3. install plugin is forced to version 2.3 because of known issue with
installing POMs and attached artifacts MINSTALL-41
4. use custom built 2.5 version of deploy plugin because of
On 5 Aug 2009, at 14:10, Stephen Connolly wrote:
if you think about this a bit more you will realise that what you
are asking
for does not make sense (unless you are trying to configure the
plugin that
you are executing.
if you specify a plugin:mojo, then only that plugin:mojo will get
if you think about this a bit more you will realise that what you are asking
for does not make sense (unless you are trying to configure the plugin that
you are executing.
if you specify a plugin:mojo, then only that plugin:mojo will get executed.
Adding other executions of other plugins to a prof
Hi,
You could activate a profile by -Pprofile flag in comman line. Wont help
you? [?]
2009/8/5 Dominic Mitchell
> Hi all,
>
> I'm wondering — is there a way to activate a profile based on the plugin
> specified on the command line?
>
> The reason for this is that I'm working with a cocoon proje
Hi all,
I'm wondering — is there a way to activate a profile based on the
plugin specified on the command line?
The reason for this is that I'm working with a cocoon project.
Normally, the cocoon plugin gets bound to compile:
org.apache.cocoon
cocoon-maven-plugin
It works now I declared a separate repository in archiva for plugins
snapshots.
Not sure it was from Archiva, maybe what was missing also is that it was not
declared as a "pluginRepository" in maven. BTW now as expected permissions
are managed the way I wanted by site plugin :)
--
View this messa
30 matches
Mail list logo
