[ http://jira.codehaus.org/browse/SCM-160?page=all ]
Torbjørn EIkli Smørgrav updated SCM-160:
Attachment: MNG-160_2-maven-scm-test.patch
> Refactored tck tests, added changelog tck test and added changelog, diff test
> for the bazaar provider
>
[ http://jira.codehaus.org/browse/MAVEN-1742?page=comments#action_58576 ]
Aditya Gupta commented on MAVEN-1742:
-
Hi,
Regarding *java.lang.ClassNotFoundException: velocity* that exists in my
stack trace , I was wondering if theres a way to *specify th
Hi,
Please tell me which jar do i have to import to use the below given import
I tried to find Interface Plugin in most of the jars it is not present in
maven-plugin-api-2.0.jar
import org.apache.maven.plugin.Plugin;
import org.apache.maven.plugin.PluginExecutionRequest;
import org.apache.maven
Hi,
I am Ravikumar. I came to get help form you. That is :
I have four projects in my workspace. Three of them have
sub projects also.
I done successfully building the four projects individually with
multiproject plugin.
But my goal is:
Not a valid plugin file
---
Key: MAVEN-1743
URL: http://jira.codehaus.org/browse/MAVEN-1743
Project: Maven
Type: Bug
Environment: win xp
Reporter: atie
org.apache.maven.MavenException: Not a valid plugin file: C:\Documents and Setti
ngs\ci
[
http://jira.codehaus.org/browse/MAVENUPLOAD-741?page=comments#action_58573 ]
Daniel Brolund commented on MAVENUPLOAD-741:
Hmm, you got a point...
We're developing it on sourceforge, but we put our name to it and the
package structure. You could
[ http://jira.codehaus.org/browse/MEV-296?page=all ]
Edwin Punzalan updated MEV-296:
---
Attachment: MEV-296-activemq.patch
> Activemq-core (and other activemq projects) 3.2.1 have unexpanded variables
> ---
[ http://jira.codehaus.org/browse/MNG-1996?page=all ]
Allan Ramirez closed MNG-1996:
--
Resolution: Fixed
Applied Patch with small modification.. Thanks
> Enhance "Guide to Configuring Plug-ins" to include effects of configuration
> inside/outside exec
[ http://jira.codehaus.org/browse/MAVEN-1742?page=all ]
Lukas Theussl updated MAVEN-1742:
-
Fix Version: (was: 1.0.2)
Summary:
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
was:
Could not find th
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
[ http://jira.codehaus.org/browse/MAVEN-1742?page=comments#action_58570 ]
L
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
[ http://jira.codehaus.org/browse/MAVEN-1742?page=comments#action_58569 ]
A
Brett Porter wrote:
I guess they make a big difference - either way is fine. But if it isn't
working, probably best to leave it out until it is?
It turned out that the layout problems I experienced in some projects
were due to an organization logo that was too big. That had the strange
ef
[ http://jira.codehaus.org/browse/MNG-2070?page=all ]
Brett Porter closed MNG-2070:
-
Assign To: Brett Porter
Resolution: Duplicate
> systemPath is needed for tests as well as compile time scope
>
[ http://jira.codehaus.org/browse/MEV-308?page=all ]
Edwin Punzalan closed MEV-308:
--
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours for the fix to reach central repo.
> dom4j-1.4-dev8 has an invalid pom
> -
>
>
systemPath is needed for tests as well as compile time scope
Key: MNG-2070
URL: http://jira.codehaus.org/browse/MNG-2070
Project: Maven 2
Type: Improvement
Components: Dependencies
Environment: n/a
[ http://jira.codehaus.org/browse/MEV-302?page=all ]
Edwin Punzalan closed MEV-302:
--
Resolution: Fixed
Patch applied. Thanks.
NOTE: May take up to 4 hours for the patch to reach central repo.
> Invalid m2 pom for joda-time-hibernate-0.8
> ---
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060214.030001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060214.030001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060214.024501.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060214.024501.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MEV-309?page=all ]
Edwin Punzalan closed MEV-309:
--
Resolution: Fixed
Fixed... Removed the logo tags and also the package tag.
NOTE: May take up to 4 hours for the fix to reach central repo.
> PicoContainer 1.0 POM in
[ http://jira.codehaus.org/browse/MEV-312?page=all ]
Edwin Punzalan closed MEV-312:
--
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours to reach central repo.
> tag is misspelled in maven2 ant-optional-1.5.3-1.pom
> --
[ http://jira.codehaus.org/browse/MRM-58?page=all ]
Maria Odea Ching updated MRM-58:
Due Date: 17/Feb/06 (was: 15/Feb/06)
> create a search result class for returning from search
> --
>
> Key:
[ http://jira.codehaus.org/browse/MRM-57?page=all ]
Maria Odea Ching updated MRM-57:
Due Date: 16/Feb/06
Remaining Estimate: 9 hours (was: 0 minutes)
> ability to retrieve matched portion of classes, packages and files fields
> ---
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060214.013002.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060214.013002.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[ http://jira.codehaus.org/browse/MRM-57?page=all ]
Maria Odea Ching reopened MRM-57:
-
When org.apache is searched in "query everything", and a match was found in a
package name, the search results should know that it was a package that was
found.
>
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060214.01.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060214.01.txt
I guess they make a big difference - either way is fine. But if it isn't
working, probably best to leave it out until it is?
- Brett
Lukas Theussl wrote:
>
>
> Brett Porter wrote:
>> Please *don't* use it by default. In fact, I see no reason why this
>> should have been included in the xdoc pl
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060214.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Brett Porter wrote:
Please *don't* use it by default. In fact, I see no reason why this
should have been included in the xdoc plugin.
Is there a particular reason not to include it? I thought, since we have
it already, we might as well use it and make it available. I am not in
favor of maki
Please *don't* use it by default. In fact, I see no reason why this
should have been included in the xdoc plugin.
It's for the Maven site. While I'd be happy with a "similar but
different" style being included and made default, I like that the Maven
site is still recognisable from the rest.
In m2
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060214.003001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060214.003001.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MRM-57?page=all ]
Maria Odea Ching closed MRM-57:
---
Resolution: Fixed
The current searcher already handles this type of search.
> ability to retrieve matched portion of classes, packages and files fields
> ---
[ http://jira.codehaus.org/browse/MEV-318?page=all ]
Edwin Punzalan closed MEV-318:
--
Resolution: Fixed
Fixed.
NOTE: May take up to 4 hours for the fix to reach central repo.
> Dependencies for Axion
> --
>
> Key: MEV-318
I am seeing some weird layout problems when using stylus with some of my
custom projects, until I don't understand where that comes from, I
prefer not to use it by default.
I don't know what you mean with 'cleanup our project.css', we are not
using any project.css files?
-Lukas
Arnaud HER
[ http://jira.codehaus.org/browse/MPXDOC-191?page=all ]
Lukas Theussl closed MPXDOC-191:
Resolution: Fixed
> Include dependencies' scope in dependencies page
>
>
> Key: MPXDOC-191
>
[ http://jira.codehaus.org/browse/MEV-316?page=all ]
Carlos Sanchez closed MEV-316:
--
Resolution: Won't Fix
Will be fixed in next versions, not in 1.2.6
> spring-support should have all dependencies be optional
> ---
[ http://jira.codehaus.org/browse/MWAR-21?page=comments#action_58549 ]
Eugene Kuleshov commented on MWAR-21:
-
It looks like there is a missing dependency scope. The one that is required for
compilation but not in the runtime.
> Need a way to include lim
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060214.01.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Can we use it by default ?
Can we cleanup our project.css. We only have to keep our custom header
settings ?
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[ http://jira.codehaus.org/browse/MPXDOC-190?page=all ]
Lukas Theussl closed MPXDOC-190:
Resolution: Fixed
> Include the new maven-stylus.css theme
> --
>
> Key: MPXDOC-190
> URL: http://jira.cod
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060213.234500.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060213.234500.txt
-
To unsubscribe, e-mai
I also updated our roadmap for plugins to bundle in maven 1.1 beta 3 :
http://docs.codehaus.org/display/MAVEN/Maven+1.1+plugins
Arnaud
On 2/14/06, Arnaud HERITIER <[EMAIL PROTECTED]> wrote:
> Following this vote [1], I just decommissioned in sandbox these plugins :
> - abbot
> - castor
> - hibern
Following this vote [1], I just decommissioned in sandbox these plugins :
- abbot
- castor
- hibernate
- j2ee
- jboss
- jbuilder
- jcoverage
- jetty
- jnlp
- release
- repository
- uberjar
[1]http://www.mail-archive.com/dev@maven.apache.org/msg52811.html
Arnaud
--
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060213.233001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060213.233001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Hi All,
I simplified the POMs in M1 plugins, moving all informations about
their storing information (Bundled with core, sandbox) in the
plugins-parent project.
It makes easier the move of plugins between this two areas.
The problem is that, due to a bug in Jelly, you can't use maven
1.0.X t
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060213.230001.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060213.230001.txt
ok, thx
On 2/13/06, Lukas Theussl <[EMAIL PROTECTED]> wrote:
> I have put my comments into the README.txt files.
>
> Basically, I think we should keep the schema files of published versions
> in src/dtd/maven-xdoc-{version}.dtd, while the current development
> version is src/plugin-resources/dtd/m
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060213.223000.txt
I have put my comments into the README.txt files.
Basically, I think we should keep the schema files of published versions
in src/dtd/maven-xdoc-{version}.dtd, while the current development
version is src/plugin-resources/dtd/maven-xdoc.dtd. I don't think it is
abolutely necessary but it could
Hi Lukas,
Thx for the cleanup,
Finally, do you think that it is useful to keep the plugin release
number in the schema filename ?
Arnaud
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTEC
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060213.22.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060213.22.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
Distribution:
http://maven.zones.apache.org/~continuum/builds/trunk/continuum-20060213.22.war
Log:
http://maven.zones.apache.org/~continuum/logs/trunk/continuum-build-log-20060213.22.txt
Log:
http://maven.zones.apache.org/~continuum/logs/branches/continuum-1.0.x/continuum-build-log-20060213.213001.txt
Distribution:
http://maven.zones.apache.org/~maven/builds/branches/maven-2.0.x/m2-20060213.211502.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/branches/maven-2.0.x/m2-build-log-20060213.211502.txt
-
To unsubscribe, e-mai
[ http://jira.codehaus.org/browse/MASSEMBLY-64?page=comments#action_58541 ]
Emil A. Lefkof III commented on MASSEMBLY-64:
-
Can you please post the exact example how to get around this? I have the exact
same problem.
> jar-with-dependencies has
Distribution:
http://maven.zones.apache.org/~maven/builds/trunk/m2-20060213.190001.tar.gz
Log:
http://maven.zones.apache.org/~maven/logs/trunk/m2-build-log-20060213.190001.txt
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For addit
[
http://jira.codehaus.org/browse/MAVENUPLOAD-742?page=comments#action_58540 ]
Carlos Sanchez commented on MAVENUPLOAD-742:
Done, but I think we'll need the maven-metadata.xml files, can you deploy to a
directory in SF and we'll sync from there?
[
http://jira.codehaus.org/browse/MAVENUPLOAD-739?page=comments#action_58539 ]
Carlos Sanchez commented on MAVENUPLOAD-739:
Is it ok to sync from SF?
please check components\maven-meeper\src\bin\m2-sync\displaytag-m2-sync.sh
Also does spring-san
[ http://jira.codehaus.org/browse/MAVENUPLOAD-740?page=all ]
Carlos Sanchez closed MAVENUPLOAD-740:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> Upload Joda-Time 1.2.1
> --
>
> Key: MAVENUPLOAD-740
>
[
http://jira.codehaus.org/browse/MAVENUPLOAD-741?page=comments#action_58537 ]
Carlos Sanchez commented on MAVENUPLOAD-741:
has to be removed when using groupId and artifactId
If you want to use group com.agical.rmock you have to provide proof
Include the new maven-stylus.css theme
--
Key: MPXDOC-190
URL: http://jira.codehaus.org/browse/MPXDOC-190
Project: maven-xdoc-plugin
Type: Improvement
Environment: m11b3
Reporter: Lukas Theussl
Priority: Minor
Fix Fo
Include dependencies' scope in dependencies page
Key: MPXDOC-191
URL: http://jira.codehaus.org/browse/MPXDOC-191
Project: maven-xdoc-plugin
Type: Improvement
Reporter: Lukas Theussl
Priority: Minor
Fix Fo
[
http://jira.codehaus.org/browse/MAVENUPLOAD-743?page=comments#action_58536 ]
Carlos Sanchez commented on MAVENUPLOAD-743:
We don't upload snapshots to ibiblio
> Rio bundle
> --
>
> Key: MAVENUPLOAD-743
> URL: http://j
[ http://jira.codehaus.org/browse/MEV-332?page=all ]
Carlos Sanchez closed MEV-332:
--
Assign To: Carlos Sanchez
Resolution: Fixed
> hibernate-3.1.2.pom has wrong version
> -
>
> Key: MEV-332
> U
[ http://jira.codehaus.org/browse/MEV-310?page=all ]
Carlos Sanchez closed MEV-310:
--
Resolution: Fixed
I have moved the changes to hivemind group.
We can't relocate it yet as it comes from apache auto sync'ed, sorry about that
> POMs for hivemind:hive
Thanks, in the future I'll use JIRA as you have suggested.
Sean
On 2/13/06, Carlos Sanchez <[EMAIL PROTECTED]> wrote:
> It's done now and will propagate to ibiblio in the next 8 hours.
>
> Maybe a issue in jira.codehaus.org/browse/MEV assigned to me would be better.
>
> On 2/13/06, Sean Schofield
It's done now and will propagate to ibiblio in the next 8 hours.
Maybe a issue in jira.codehaus.org/browse/MEV assigned to me would be better.
On 2/13/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> Just a reminder that we are still waiting on these jars to be synched
> in ibiblio.
>
> Sean
>
> p
[ http://jira.codehaus.org/browse/MNG-1931?page=comments#action_58533 ]
John Allen commented on MNG-1931:
-
Any thoughts re moving this up the priority ladder? After all one of the key
benefits of using maven is the reduction in duplicated configs and current
[ http://jira.codehaus.org/browse/MRM-58?page=all ]
John Tolentino updated MRM-58:
--
Due Date: 15/Feb/06
Remaining Estimate: 6 hours
Original Estimate: 6 hours
> create a search result class for returning from search
>
Rio bundle
--
Key: MAVENUPLOAD-743
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-743
Project: maven-upload-requests
Type: Task
Reporter: Jerome Bernard
Attachments: rio-3.2-SNAPSHOT-bundle.jar, rio-tools-3.2-SNAPSHOT-bundle.jar
Provides a bundle for
[ http://jira.codehaus.org/browse/MRM-38?page=comments#action_58529 ]
John Tolentino commented on MRM-38:
---
Created a components.xml based on the one existing in Continuum. This
components.xml uses org.codehaus.plexus.scheduler.Scheduler with
DefaultSchedu
[ http://jira.codehaus.org/browse/MNGECLIPSE-74?page=all ]
Eugene Kuleshov closed MNGECLIPSE-74:
-
Resolution: Duplicate
Fix Version: (was: 1.0.0)
> Support profiles for Maven 2 repository management
> ---
Support profiles for Maven 2 repository management
--
Key: MNGECLIPSE-74
URL: http://jira.codehaus.org/browse/MNGECLIPSE-74
Project: Maven 2.x Extension for Eclipse
Type: New Feature
Components: Repository Management
improve convergence report
--
Key: MPIR-28
URL: http://jira.codehaus.org/browse/MPIR-28
Project: Maven 2.x Project Info Reports Plugin
Type: Improvement
Reporter: Brett Porter
Assigned to: Brett Porter
Fix For: 2.0
things to impr
Please upload maven-qalab-plugin
Key: MAVENUPLOAD-742
URL: http://jira.codehaus.org/browse/MAVENUPLOAD-742
Project: maven-upload-requests
Type: Task
Reporter: Dave Sag
Attachments: maven-qalab-plugin-2.0-bundle.jar
this plugin
create pmd:cpd-check goal
-
Key: MPMD-14
URL: http://jira.codehaus.org/browse/MPMD-14
Project: Maven 2.x Pmd Plugin
Type: New Feature
Reporter: Brett Porter
Assigned to: Brett Porter
Fix For: 2.0-beta-2
--
This message is auto
when creating a new module inside a directory with a pom that has ,
update
-
Key: ARCHETYPE-28
URL: http://jira.codehaus.org/browse/ARCHETYPE-28
Project: Maven Archetype
Typ
create simpler site archetype
-
Key: ARCHETYPE-27
URL: http://jira.codehaus.org/browse/ARCHETYPE-27
Project: Maven Archetype
Type: New Feature
Components: maven-archetype-plugin
Reporter: Brett Porter
Assigned to: Brett Porter
[ http://jira.codehaus.org/browse/MJAVADOC-33?page=all ]
Brett Porter updated MJAVADOC-33:
-
Fix Version: 2.0
> Provide new javadoc:aggregate goal to perform javadoc operation on project
> and subprojects.
> --
[ http://jira.codehaus.org/browse/MJAVADOC-33?page=all ]
Brett Porter updated MJAVADOC-33:
-
Remaining Estimate: 4 hours
Original Estimate: 4 hours
> Provide new javadoc:aggregate goal to perform javadoc operation on project
> and subprojects.
> ---
Just a reminder that we are still waiting on these jars to be synched
in ibiblio.
Sean
ps. Is a JIRA issue better for this type of request?
On 2/11/06, Sean Schofield <[EMAIL PROTECTED]> wrote:
> Please also published the newly relesed (this morning) myfaces-commons
> stuff. Its in the maven-re
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
In-Reply-To: <[EMAIL PROTECTED]>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
[ http://jira.codehaus.org/browse/MAVEN-1742?page=comments#action_58509 ]
A
[ http://jira.codehaus.org/browse/MNG-2068?page=comments#action_58508 ]
Brian Fox commented on MNG-2068:
No, it still fails. You must build from "sample-project2" to see this problem.
If you build from the root or from sample-jar it works fine. The trouble i
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Could not find the class:
org.apache.commons.jelly.tags.velocity.VelocityTagLibrary
ary
---
hibernate-3.1.2.pom has wrong version
-
Key: MEV-332
URL: http://jira.codehaus.org/browse/MEV-332
Project: Maven Evangelism
Type: Bug
Components: Invalid POM
Reporter: Juha Komulainen
POM has the line:
3.1.1
which is
Allow Interactive Prompting to Set Values
-
Key: ARCHETYPE-26
URL: http://jira.codehaus.org/browse/ARCHETYPE-26
Project: Maven Archetype
Type: New Feature
Components: maven-archetype-plugin
Reporter: Stephen Duncan Jr
[ http://jira.codehaus.org/browse/MPJDEPEND-7?page=comments#action_58494 ]
stephane bouchet commented on MPJDEPEND-7:
--
Well, i have downloaded the snapshot and it worked !
thanks for the patch.
Stéphane
> Cannot generate report without component
[ http://jira.codehaus.org/browse/MNG-2068?page=comments#action_58488 ]
Grzegorz Slowikowski commented on MNG-2068:
---
Add:
junit
junit
3.8.1
test
to pom.xml and good-example will work.
I use Maven 2.0.2
> Mu
87 matches
Mail list logo
