Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPWIZARD-3
Here is an overview of the issue:
-
Key:
Mmm, I'm afraid you didn't understand me or I didn't explained well.
I closed the issue for being more than ten months old, I have never tried to
reproduce it.
In a previous thread in the list we talked about closing old issues and
that's what I did.
If you know that the issue is still valid it can
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Mon, 26 Jul 2004 4:54 PM
Use
maven.compile.source=1.5
maven.compile.target=1.5
-
View the issue:
http://jira.codehaus.org/browse/MPJAVA-
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Mon, 26 Jul 2004 4:53 PM
Body:
Use
maven.compile.source=1.5
maven.compile.target=1.5
-
View this comment:
http://jira.codehaus.
On Mon, 26 Jul 2004 17:40:42 +0200, Carlos Sanchez
<[EMAIL PROTECTED]> wrote:
> IMHO
> I "cannot reproduce" because I've never tried, so people who see it will
> point out the steps to reproduce the issue (if it yet exists).
> "wont fix" means that I know the problem exists and that's not the case.
Brett,
On Monday 26 July 2004 14:15, Brett Porter wrote:
> Joachim, you've done most of the work on native now. If you'd like to
> submit patches for any issues that come up in JIRA for MPNATIVE and apply
> them, I'm happy to release them when you think it is reasonable. If you are
> interested on
Did you see this? ;-)
http://www.foolish.com/
--
Dennis Lundberg
[EMAIL PROTECTED] wrote:
carlos 2004/07/26 09:17:45
Added: linkcheck/src/plugin-test maven.xml .cvsignore
project.properties project.xml
linkcheck/src/plugin-test/xdocs nolink.html
carlos 2004/07/26 09:17:10
maven-plugins/linkcheck/src/plugin-test/xdocs/test1 - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
carlos 2004/07/26 09:17:09
maven-plugins/linkcheck/src/plugin-test/xdocs - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
carlos 2004/07/26 09:17:45
Added: linkcheck/src/plugin-test maven.xml .cvsignore
project.properties project.xml
linkcheck/src/plugin-test/xdocs nolink.html test.html
testExcludes.html
linkcheck/src/plugin-te
carlos 2004/07/26 09:17:09
maven-plugins/linkcheck/src/plugin-test/xdocs/test-resources/test1 - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
carlos 2004/07/26 09:17:08
maven-plugins/linkcheck/src/plugin-test - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
carlos 2004/07/26 09:17:09
maven-plugins/linkcheck/src/plugin-test/xdocs/test-resources - New directory
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
carlos 2004/07/26 09:16:35
Modified:linkcheck/xdocs properties.xml index.xml changes.xml
linkcheck/src/main/org/apache/maven/linkcheck/validation
LinkValidatorManager.java
linkcheck plugin.jelly plugin.properties project.xml
Okay, that seems like what I thought would work. From inside a plugin then
plugin.currentVersion does work fine. However, from outside:
Neither version is being set. It seems so easy, but hasn't been. Does any
one have any pointers to other jelly script I could look at?
Eric
>
IMHO
I "cannot reproduce" because I've never tried, so people who see it will
point out the steps to reproduce the issue (if it yet exists).
"wont fix" means that I know the problem exists and that's not the case.
but I have no problem to change it to whatever you prefer.
> -Original Message
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 26 Jul 2004 11:10 AM
Body:
They should be closed as WONT FIX with a comment (too old?) instead of UNABLE TO
REPRODUCE.
-
View
The following comment has been added to this issue:
Author: dion gillard
Created: Mon, 26 Jul 2004 11:07 AM
Body:
Really??
-
View this comment:
http://jira.codehaus.org/browse/MPXDOC-116?page=comments#action_2232
Quoting Heritier Arnaud <[EMAIL PROTECTED]>:
> Hello Brett (not gone !! ;-) )
Just a brief stop at "home" before heading out for the rest of the week. Don't worry,
I'll leave you all alone
now :)
> It is what I would like to propose to you ;-)
> I think that we can use the CCI project (if it i
plugin.currentVersion
inside the plugin, just like that. Outside, use in conjunction with maven:get
Quoting Eric Pugh <[EMAIL PROTECTED]>:
> Hi all,
>
> I have a report that runs that checks a plugin to see if there are newer
> versions, and if so, tells the user. I then saw the plugin-profile
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 26 Jul 2004 8:43 AM
Body:
Plugin releases are completely independant of Maven now.
And documentation changes are almost irrelevant for a release anyway - they are
immediate when the site is pub
Hello Brett (not gone !! ;-) )
>
> Yes, and webserver is awfully similar too.
>
> I think that there should just be a "server" plugin that does
> most of the shared stuff, then individual
> appservers should have their own plugin (like the Jetty one),
> that utilise that to do the configurati
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 26 Jul 2004 8:31 AM
Body:
the problem isn't really in Ant: they changed the classloader, it doesn't work the way
we use it. It's not a bug in the classloader, its just that it is completely diff
The following comment has been added to this issue:
Author: Brett Porter
Created: Mon, 26 Jul 2004 8:29 AM
Body:
Archimedas: yes, now it is maven.maven. Sorry, I was thinking in future-tense :)
Carlos: good point. To make it more clear, perhaps:
maven.override.jar.groupId.artifact
Yes, and webserver is awfully similar too.
I think that there should just be a "server" plugin that does most of the shared
stuff, then individual
appservers should have their own plugin (like the Jetty one), that utilise that to do
the configuration and
any common start/stop stuff.
We'll hol
It means that the plugin's CVS will still be available in maven-plugins-sandbox, and
old releases available
through plugin:download, but no new releases will be made and it will not be
distributed with Maven.
That is, until someone steps up to maintain it.
Joachim, you've done most of the work
Hi all,
I have a report that runs that checks a plugin to see if there are newer
versions, and if so, tells the user. I then saw the plugin-profile.xml
stuff in the main maven build, and thought that I could scroll through a
plugin profile to verify that I have all the plugins needed for a specif
Hi Nick,
We are only looking for the committers to step up here, but if you are able to submit
regular patches to
issues on the MPCHECKSTYLE project in JIRA, we'd really appreciate it.
Thanks,
Brett
Quoting Nick Bence <[EMAIL PROTECTED]>:
> I use checkstyle and would be happy to step in for V
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1406
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Mon, 26 Jul 2004 7:40 AM
Body:
This issue was closed because it's too old (as discussed in dev list)
If the problem persists it will be reopened
-
The following comment has been added to this issue:
Author: Guillaume Nodet
Created: Mon, 26 Jul 2004 7:27 AM
Body:
The patch i submitted is copied from the javadoc plugin. It should handle
sourceModifications, though i've tested it.
---
I use checkstyle and would be happy to step in for Vincent on this one.
I am new to open source development, please could somebody tell me what I need to
update on JIRA and where can I find out what the steps are for getting
fixes/enhancements in and released.
Nick
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1405
Here is an overview of the issue:
-
Key:
This is replaced by this one :
MAVEN-1400
Arnaud
On Mon, 26 Jul 2004 08:48:48 +0200, Peter Nabbefeld
<[EMAIL PROTECTED]> wrote:
> Hello,
>
> as resolution is set to DUPLICATE: From which issue this is a duplicate?
> If You're closing/resolving an issue as duplicate: Could You please add
> a com
The following comment has been added to this issue:
Author: Julien Kirch
Created: Mon, 26 Jul 2004 3:07 AM
Body:
For 5), read "Call a maven goal in debug mode in the inherited project, in the log I
have a :"
-
Vie
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1404
Here is an overview of the issue:
-
Key:
36 matches
Mail list logo
