What do you mean noone knows how it got there?
[EMAIL PROTECTED] maven]$ ls -la | grep taglibs
drwxrwsr-x6 vmassol maven4096 Oct 8 2003 taglibs
[EMAIL PROTECTED] maven]$
[EMAIL PROTECTED] taglibs]$ cd jars
[EMAIL PROTECTED] jars]$ ls -la
total 1124
drwxrwsr-x2 vmassol maven
The following comment has been added to this issue:
Author: dion gillard
Created: Fri, 30 Jul 2004 11:12 PM
Body:
It makes sense to use the maven properties, IMHO
-
View this comment:
http://jira.codehaus.org/bro
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJETTY-2
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Dennis Lundberg
Created: Fri, 30 Jul 2004 4:13 PM
Body:
To solve 2 the patch "Repository.java.patch" needs to be applied to Maven and the
patch "cvs-usage.xml.patch" needs to be applied to the xdoc plugin.
I can make an
This is now an issue in JIRA http://jira.codehaus.org/browse/MAVEN-1410.
--
Dennis Lundberg
Emmanuel Venisse wrote:
- Original Message -
From: "Dennis Lundberg" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, July 30, 2004 12:54 PM
Subject: Re: pom.id vers
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1410
Here is an overview of the issue:
-
Key:
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Fri, 30 Jul 2004 3:59 PM
Body:
I agree with you.
But the question is : can we consider to use maven properties in an Ant script?
Shouldn't we use separate properties (ant.proxy...) ??
-
The following comment has been added to this issue:
Author: Arnaud HERITIER
Created: Fri, 30 Jul 2004 3:55 PM
Body:
You can find it here :
http://www.ibiblio.org/maven/commons-jelly/jars/commons-jelly-tags-xml-20040613.030723.jar
But I'm not sure if it can't create a problem becau
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPANT-18
Here is an overview of the issue:
-
Key: M
The following comment has been added to this issue:
Author: patrick chanezon
Created: Fri, 30 Jul 2004 3:25 PM
Body:
what this feature generates is
with the values of my proxy settings.
I would prefer to have references to the properties this settings were set fr
I am also confused as to how goals are determined to be run. I thought it would be
like ant where a goal would only be run once. Could someone explain how this is
possible and if not why?
> -Original Message-
> From: Carlos Sanchez [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 30, 200
I personally run site with junit, clover and jcoverage reports and would be
difficult to skip test:test.
I see it more a general question for all plugins. Maven should keep track of
goals run and don't run again them. Plugins should be able to override that,
e.g. clover could set test:test as "not
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MAVEN-1409
Here is an overview of the issue:
-
Key:
The following issue has been updated:
Updater: Brant Gurganus (mailto:[EMAIL PROTECTED])
Date: Fri, 30 Jul 2004 2:36 PM
Comment:
Patch that adds a description.
Changes:
Attachment changed to maven_bootstrap.patch
-
evenisse2004/07/30 09:54:35
Modified:src/java/org/apache/maven/util Tag: MAVEN-1_0-BRANCH
HttpUtils.java
Log:
Use Locale.US as date format for If-Modified-Since header tag because it fails when
server doesn't understand date in other format than english forma
The following comment has been added to this issue:
Author: Emmanuel Venisse
Created: Fri, 30 Jul 2004 12:10 PM
Body:
No, the défault port is 2401 and not 2410
-
View this comment:
http://jira.codehaus.org/browse
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 30 Jul 2004 11:55 AM
Body:
Sorry, I thought it was the default port.
Could you run maven with -X and post the relevany output?
-
The following comment has been added to this issue:
Author: Maciejowski
Created: Fri, 30 Jul 2004 11:51 AM
Body:
I succeed in checking out the project directly with CVS using its command:
cvs -d:pserver:[EMAIL PROTECTED]:2410/prod/cvs/data/repository/dev -q checkout -P
redouteSimb
IMHO as the package is javax.* they should be in another group and not under
taglibs.
> -Original Message-
> From: Felipe Leme [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 30, 2004 4:28 PM
> To: Maven Developers List
> Subject: RE: Taglibs repository
>
> Hi Carlos,
>
> Actually, they
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Fri, 30 Jul 2004 11:24 AM
Seems a bug in the JDK
-
View the issue:
http://jira.codehaus.org/browse/MPLINKCHECK-3
Here is an overview of
Message:
The following issue has been reopened.
-
View the issue:
http://jira.codehaus.org/browse/MPLINKCHECK-3
Here is an overview of the issue:
-
Ok, no problem, I've changed it.
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: Friday, July 30, 2004 5:12 PM
> To: Maven Developers List
> Subject: Re: [jira] Commented: (MPLINKCHECK-3) The linkcheck
> plugin seems to hang indefinitely and sometime even cras
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 30 Jul 2004 11:20 AM
Body:
Try
cvs -d:pserver:[EMAIL PROTECTED]:2410/prod/cvs/data/repository/dev -q checkout -P
redouteSimbocoSptvteWeb
if that doesn't work the problem is not maven
I think
Looking at the bug report, it appears it was a bug in The Apple JDK, in which case
WON'T FIX is
appropriate.
I agree with Dion, WON'T FIX is better than CANNOT REPRODUCE. And we should not close
bugs that we
know are still in existence and not superseded, nor should we close feeature requests
The following comment has been added to this issue:
Author: Maciejowski
Created: Fri, 30 Jul 2004 10:51 AM
Body:
here is the repository tag used in my pom:
scm:cvs:pserver:[EMAIL
PROTECTED]:2410/prod/cvs/data/repository/dev:redouteSimbocoSptvteWeb
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 30 Jul 2004 10:45 AM
Body:
A bit of debug info
See the line "running script null", is that ok?
Getting URL:
http://cvs.apache.org/repository/maven/plugins/maven-war-plugin-1.7-SNAPSHOT.jar
R
On Fri, 30 Jul 2004 13:37:39 +0200, "Emmanuel Venisse"
<[EMAIL PROTECTED]> wrote:
> What??? ;-)
It shouldn't be hard to port the current site, as most of documention is
alrady in xdoc. I mean, it would be nice to use (and even improve) the
taglib plugin to generate that stuff, but meanwhile we
Hi Carlos,
Actually, they are generated by the Jakarta Standard Taglib project,
which is JSTL's reference implementation (in fact, I copied the JARs
from Standard dists).
Felipe
On Fri, 30 Jul 2004 16:22:10 +0200, "Carlos Sanchez"
<[EMAIL PROTECTED]> wrote:
> I took a look to the standard/jars
Hi Felipe,
I took a look to the standard/jars dir and saw the jstl-xxx files.
I think they should be in the jstl group as they are not made by the taglibs
project.
Regards
Carlos Sanchez
A Coruña, Spain
Oness Project
http://oness.sourceforge.net
> -Original Message-
> From: Emmanuel
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 30 Jul 2004 10:16 AM
Body:
You should post the repository info in your pom to check where's the error
-
View this comment:
The following comment has been added to this issue:
Author: Brett Porter
Created: Fri, 30 Jul 2004 10:18 AM
Body:
Assuming the patch works, I'm happy for it to be applied as-is to Maven 1.0.1. The
Project will be overhauled in Maven 1.1.
---
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 30 Jul 2004 10:11 AM
Body:
It doesn't sound good to me.
If you don't want to mix your test classes create another project and use it as a
dependency.
-
Message:
The following issue has been closed.
-
View the issue:
http://jira.codehaus.org/browse/MPCONSOLE-9
Here is an overview of the issue:
-
Key
Message:
The following issue has been reopened.
-
View the issue:
http://jira.codehaus.org/browse/MPCONSOLE-9
Here is an overview of the issue:
-
K
Message:
The following issue has been closed.
Resolver: Carlos Sanchez
Date: Fri, 30 Jul 2004 10:02 AM
Use
maven.uberjar.main=com.example.MyMain
-
View the issue:
http://jira.codehaus.org/browse/MPCONSOLE-9
Her
The following comment has been added to this issue:
Author: Carlos Sanchez
Created: Fri, 30 Jul 2004 9:47 AM
Body:
What is this attachment?
-
View this comment:
http://jira.codehaus.org/browse/MAVEN-1407?page=com
The following issue has been updated:
Updater: Anatol Pomozov (mailto:[EMAIL PROTECTED])
Date: Fri, 30 Jul 2004 8:48 AM
Comment:
Changed files:
maven-plugins/idea/src/plugin-resources/templates/v4/module.jelly
Changes:
Attachment changed to module.jelly
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPIDEA-8
Here is an overview of the issue:
-
Key: M
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPSCM-21
Here is an overview of the issue:
-
Key: M
Attach your patch to Jira please.
http://jira.codehaus.org/browse/MPIDEA
Emmanuel
- Original Message -
From: "Anatol Pomozov" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, July 30, 2004 1:44 PM
Subject: Maven plugin for IDEA enhancements
> Hello mave
Ooops.
Seems firewall blocked attached file.
You can find it here http://kanguroo.org/maven/module.jelly
--
Best regards,
Anatol
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Hello maven developers,
I played a little with maven IDEA plugin. And I made some enhancements.
There is a list of changes
1) Added 'target' dir to exluded folders list (?? Is it reasonable)
2) Replace invalid $MODULE_DIR$ tokens with $$MODULE_DIR$$
3) Check if unit tests present then add JUnit l
- Original Message -
From: "Felipe Leme" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, July 30, 2004 12:58 PM
Subject: Re: Taglibs repository
> On Fri, 2004-07-30 at 07:59, Emmanuel Venisse wrote:
> > Ok, you can use your sructure.
>
> Cool.
>
> > Can
- Original Message -
From: "Dennis Lundberg" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, July 30, 2004 12:54 PM
Subject: Re: pom.id versus pom.artifactId - which is correct?
> Thanks for your reply. I a have few follow-ups:
>
> In which version of M
On Fri, 2004-07-30 at 07:59, Emmanuel Venisse wrote:
> Ok, you can use your sructure.
Cool.
> Can you add poms files with this infos :
Nope, they were not built with Maven :-(
I'm planning to mavenize the project, but that's gonna take a while...
-- Felipe
Thanks for your reply. I a have few follow-ups:
In which version of Maven was pom.id deprecated?
Is there a timeframe/version when pom.id will be removed? 1.0.1, 1.1 or 2.0?
When will pom.artifactId be added to the XML schema? POM version 4?
Which version of Maven will use POM version 4?
The reason
Ok, you can use your sructure.
Can you add poms files with this infos :
- groupId
- artifactId
- name
- currentVersion
- dependencies
Emmanuel
- Original Message -
From: "Felipe Leme" <[EMAIL PROTECTED]>
To: "Maven Developers List" <[EMAIL PROTECTED]>
Sent: Friday, July 30, 2004 12:
On Fri, 2004-07-30 at 04:17, Emmanuel Venisse wrote:
> Structure is correct, but I prefer this:
> taglibs
> jars
> all jars
The problem with that structure is that the project has many taglibs, so
the directory will be too packed (right now, for instance, there are 35
jars, 87 tlds and
Message:
A new issue has been created in JIRA.
-
View the issue:
http://jira.codehaus.org/browse/MPJAR-34
Here is an overview of the issue:
-
Key: M
The following comment has been added to this issue:
Author: David Eric Pugh
Created: Fri, 30 Jul 2004 4:25 AM
Body:
Also, if it fails, can you drill down to the individual subproject? I had a situation
where it failed because I overrode in another plugin the cruisecontrol.jsl fil
Message:
The following issue has been closed.
Resolver: David Eric Pugh
Date: Fri, 30 Jul 2004 4:24 AM
I have fixed it by tweaking the .jsl file. However, I am not sure why this failed. I
am going to close it, however, if it fails again, can you provide more details on your
envi
epugh 2004/07/30 01:21:10
Modified:cruisecontrol/src/plugin-test/cvs-scm maven.xml
project.properties
cruisecontrol/src/plugin-resources cruisecontrol.jsl
Log:
MPCRUISECONTROL-10 Unit tests failing due to build status log element not being
c
pom.id is deprecated, you must use pom.artifactId.
Emmanuel
- Original Message -
From: "Dennis Lundberg" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, July 29, 2004 10:58 PM
Subject: pom.id versus pom.artifactId - which is correct?
> Hello
>
> I have noticed that the XML
Structure is correct, but I prefer this:
taglibs
jars
all jars
licenses
all licenses
tlds
all tlds
war
all wars
and there are already a directory group taglibs on ibiblio.
It's more usable if we have only one group by project.
Emmanuel
- Origi
54 matches
Mail list logo
