Hi
I am looking to work on patches for JellySwt to be able to use it.
T do that I try to understand how Maven and Jelly interact.
Maven use jelly to process some Xml tags
and Jelly use Maven to be compiled.
I looked in Maven code (very nice).
And I arrived to JellyScriptHousing.java.
I saw that in
On Tue, 2004-10-19 at 02:53, Brett Porter wrote:
>
>
> Convenient :)
As I said, you need to update the war (ok, you could usen maven console
for that, but it's not the same). What about:
(+ a maven.xml goal that copies all the dependencies on WEB-INF/lib and
maven.compile.target=${maven.war.
> What do you mean stay as it is? Does it means no plugin should have the
> .final.name (relying only on maven.final.name) or leaving it in the
> current inconsistent way (where some plugins have the property but some
> others don't)?. Or are you just talking about the specific
> maven.war.fina
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 18 Oct 2004 11:54 PM
Body:
John, do you have any code for this or is it a feature request?
-
View this comment:
http://jira.c
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-32
Here is an overview of the issue:
-
Key: M
On Tue, 19 Oct 2004 06:47:53 +1000, Brett Porter <[EMAIL PROTECTED]> wrote:
> It's for this reason that it may stay as it is for now. The repository
What do you mean stay as it is? Does it means no plugin should have the
.final.name (relying only on maven.final.name) or leaving it in the cu
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJDIFF-6
Here is an overview of the issue:
-
Key:
It's for this reason that it may stay as it is for now. The repository
is king, and it will always have a version when it gets there.
Generating it in target without it is not ideal, but is convenient and
backwards compatible. I don't see any issue with it.
That said, for consistency - how abou
Felipe Leme wrote:
> Hi Jason,
>
> On 18 Oct 2004 13:51:40 -0400, Jason van Zyl <[EMAIL PROTECTED]> wrote:
>
>> It's still valid, it gives the user the only way to change the resultant
>> name of the generated artifact. It is highly recommended not to change
>> this but people still need to do i
I agree with Jason - if you really need the WAR withouth the version, than just
overwrite the property in your project.
Besides, the war is deployed/installed with the version in the name anyway, so the
plugin is already inconsistent.
What about a [VOTE] message to decide the final answer?
-- F
Hi all!
I'm a maven user who want's to contribute to the project as many
others (I guess) I've found that it's quite hard to compile maven from
CVS. On many ocassions I've found that it was due to some failing
plugin that the hole build abotrted. I was wondering:
Would it be posssible make
On Mon, 2004-10-18 at 23:46, Michal Maczka wrote:
> This is something which has a very long history.
>
> I change in many months ago but it was reverted back to use
> ${pom.artifactId}.war
> simply becouse some people just want to take war produced by maven in
> target directory
> and use it wi
I'm asking because I don't want to fix this bug leaving some plugins
inconsistent. For instance, maven-war sets:
maven.war.final.name = ${pom.artifactId}.war
Why on earth does that not have the version in it?
This is something which has a very long history.
I change in many months ago b
On Mon, 2004-10-18 at 14:20, Felipe Leme wrote:
> Hi Jason,
> I've asked the same question (see
> http://jira.codehaus.org/browse/MPJAVA-8#action_23633), but nobody answered .
> So, I'd say we are 2x0 for changing these 2 properties and if nobody gives a good
> reason for keeping them as is, I w
Hi Jason,
On 18 Oct 2004 13:51:40 -0400, Jason van Zyl <[EMAIL PROTECTED]> wrote:
> It's still valid, it gives the user the only way to change the resultant
> name of the generated artifact. It is highly recommended not to change
> this but people still need to do it for some reason.
Ok, I will
On Mon, 2004-10-18 at 13:13, Felipe Leme wrote:
> Hi all,
>
> I've started fixing MPJAVA-8, and have a question: is the propertie
> maven.final.name still valid or is it deprecated and I should just use
> pom.artifactId instead? And if it is still valid, where is it defined?
It's still valid, it
felipeal2004/10/18 10:45:10
Modified:war/src/plugin-test .cvsignore maven.xml project.xml
Added: war/src/plugin-test/test01 maven.xml project.properties
project.xml
war/src/plugin-test/test01/src MANIFEST.MF
war/src/plugin-tes
felipeal2004/10/18 10:43:37
maven-plugins/war/src/plugin-test/test01/src/webapp - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
felipeal2004/10/18 10:42:24
maven-plugins/war/src/plugin-test/test01/src - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
felipeal2004/10/18 10:42:10
maven-plugins/war/src/plugin-test/test01 - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
felipeal2004/10/18 10:19:31
Added: jar/src/plugin-test .cvsignore maven.xml project.xml
jar/src/plugin-test/test01 .cvsignore maven.xml
project.properties project.xml
Log:
MPJAR-38: added property maven.jar.final.name
Revision Changes
felipeal2004/10/18 10:19:07
Modified:jar plugin.jelly plugin.properties project.xml
jar/xdocs changes.xml properties.xml
Log:
MPJAR-38: added property maven.jar.final.name
Revision ChangesPath
1.44 +5 -5 maven-plugins/jar/plugin.jelly
In
Hi all,
I've started fixing MPJAVA-8, and have a question: is the propertie
maven.final.name still valid or is it deprecated and I should just use
pom.artifactId instead? And if it is still valid, where is it defined?
I'm asking because I don't want to fix this bug leaving some plugins
inconsiste
felipeal2004/10/18 10:14:53
maven-plugins/jar/src/plugin-test/test01 - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
felipeal2004/10/18 09:58:26
Modified:plugin-parent project.xml
Log:
added myself as developer
Revision ChangesPath
1.7 +11 -0 maven-plugins/plugin-parent/project.xml
Index: project.xml
===
Message:
The following issue has been reopened.
Reopener: Felipe Leme
Date: Mon, 18 Oct 2004 12:55 PM
I'm re-openning this issue, as it has affects more than the plugins I created
sub-issues for.
-
View the issue:
felipeal2004/10/18 07:12:02
Modified:ear project.xml
war project.xml
Log:
added my timezone
Revision ChangesPath
1.37 +1 -0 maven-plugins/ear/project.xml
Index: project.xml
=
The following comment has been added to this issue:
Author: MitchMattek
Created: Mon, 18 Oct 2004 10:11 AM
Body:
Ok, I found why it does this. In the plugin.properties of the scm plugin
(http://cvs.apache.org/viewcvs.cgi/maven-plugins/scm/plugin.properties?view=markup)
# Director
Message:
The following issue has been closed.
Resolver: Arnaud HERITIER
Date: Mon, 18 Oct 2004 10:04 AM
patch applied and site updated.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1473
Here is an over
aheritier2004/10/18 07:02:37
Modified:.project.xml
Log:
Add myself
Revision ChangesPath
1.25 +9 -0 maven-plugins/project.xml
Index: project.xml
===
RCS file: /home/cvs/maven-plugins
aheritier2004/10/18 07:01:30
Modified:xdocsindex.xml
Log:
MAVEN-1473 : add maven-xsddoc-plugin to the reference list of maven plugins
Revision ChangesPath
1.7 +4 -0 maven-plugins/xdocs/index.xml
Index: index.xml
==
The following comment has been added to this issue:
Author: Marcin Gurbisz
Created: Mon, 18 Oct 2004 9:57 AM
Body:
It is with Maven 1.0
-
View this comment:
http://jira.codehaus.org/browse/MPCRUISECONTROL-13?page
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-31
Here is an overview of the issue:
-
Key: M
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 18 Oct 2004 8:03 AM
Body:
activation:activation
-
View this comment:
http://jira.codehaus.org/browse/MAVEN-1472?page=comments
The following issue has been updated:
Updater: Kurt Riede (mailto:[EMAIL PROTECTED])
Date: Mon, 18 Oct 2004 8:00 AM
Comment:
Patch to add macen-xsddoc-plugin to the reference list of maven plugins.
Changes:
Attachment changed to maven-plugins-xsddoc.patch
--
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1473
Here is an overview of the issue:
-
Key:
Thank's Eric
Is it the same for JellySwing ?
Because I have also problems to run demos.
I am looking to find the right tool to generate large UI (many forms)
from XML.
Somebody send me to Jelly and Maven.
Is it another similar tool around maven ?
Thanks.
Andre
Eric Pugh wrote:
I'll be honest.. I
I'll be honest.. I think JellySWT was someone playing around with Jelly and
see what could be done. I think you need to balance the relative maturity
of JellySWT, and how deeply involved you want to be in using it. At a
minimum, I would suggest that you'll really need to start supply patches for
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1472
Here is an overview of the issue:
-
Key:
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1471
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Håvard Bjåstad
Created: Mon, 18 Oct 2004 4:07 AM
Body:
I get this same error, is there anyone working on a resolution?
-
View this comment:
http://jira.
41 matches
Mail list logo
