Re: Deleted files in beaver at codehaus
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 IIRC we moved the syncopate stuff to repository-tools. Not sure about the rest... Brett Porter wrote: | That was me. Sorry about that! | | I thought repository-tools/bin was a full copy of files (from | maven-meeper). I think that'd be the best place to keep everything. | | - Brett | | Carlos Sanchez wrote: | | |>Hi, |> |>The directory ~/repository is missing at beaver. Was it deleted on |>purpose, accidentally,... ? |> |>The upload scripts were under ~/repository/bin, now I see what it |>seems a copy at |>mavenuser/maven-components/maven-meeper/src/bin, but it's not updated. |>Should I update and use this? |> |>Also the syncopate conf files were under |>~/repository/bin/syncopate/conf, and I'm not sure if the copies under |>source control were up to date. |> |>Regards |> |>- |>To unsubscribe, e-mail: [EMAIL PROTECTED] |>For additional commands, e-mail: [EMAIL PROTECTED] |> |> |> | | | - | To unsubscribe, e-mail: [EMAIL PROTECTED] | For additional commands, e-mail: [EMAIL PROTECTED] | | | -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDFAKSK3h2CZwO/4URAgTsAJ0ajN5UgYjeDsWeSWO7/fjDMX2nigCgmfm0 SPsbzi/XTLEpAH5dEQ1M55o= =Egdo -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN Build Error
Ok, this is probably just a misconfiguration. It is downloaded (it is testing that plugin downloads work), but it is downloaded from repo1.maven.org/maven2/plugins (extra plugins path). You probably need to add this as an additional repository. - Brett Allison, Bob wrote: >I set up maven-proxy and have made a couple attempts now to rebuild >Maven2 using the proxy as a mirror of "central" and "snapshots". My >problem is that I have four integration tests failing (8, 9, 45, and >46); they all seem to be related to trying to download an artifact from >codehaus (actually from my mirror) that looks like it should have just >been created during the build (maven-core-it-plugin:1.0-SNAPSHOT plugin, >maven-core-it-plugin:RELEASE plugin, and maven-core-it-plugin-RELEASE >POM). Is this normal or do I have something messed up in my mirror? > >-Original Message- >From: Allison, Bob >Sent: Sunday, August 28, 2005 15:27 >To: 'Maven Developers List' >Subject: RE: SVN Build Error > >[snip] > >I have no idea why I am getting 503 errors either. I ran a wget session >to mirror the entire ibiblio maven2 repository overnight. I got to >downloading the stuff in servicemix before I stopped it. In running for >almost 24 hours it had no problems (shoot, I just realized it was FTP, >not http). With the mirror you suggested, the entire build went without >a hitch. As far as I know I do not have a proxy in use, but I don't >know if my company has a transparent proxy in my way. Is there a good >way to do a mirror of the ibiblio stuff using http to check to see if I >am having problems in general or if it is a problem in the build >process? > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deleted files in beaver at codehaus
That was me. Sorry about that! I thought repository-tools/bin was a full copy of files (from maven-meeper). I think that'd be the best place to keep everything. - Brett Carlos Sanchez wrote: >Hi, > >The directory ~/repository is missing at beaver. Was it deleted on >purpose, accidentally,... ? > >The upload scripts were under ~/repository/bin, now I see what it >seems a copy at >mavenuser/maven-components/maven-meeper/src/bin, but it's not updated. >Should I update and use this? > >Also the syncopate conf files were under >~/repository/bin/syncopate/conf, and I'm not sure if the copies under >source control were up to date. > >Regards > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Deleted files in beaver at codehaus
It's just that we need to moderate your messages because you certainly didn't subscribe with this address. Arnaud > -Message d'origine- > De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] De la > part de Carlos Sanchez > Envoyé : mardi 30 août 2005 04:20 > À : Maven Developers List > Objet : Deleted files in beaver at codehaus > > I'm sending again this message beacuse seems that the mailing > list software don't work very well with the new gmail feature > of sending emails with another From address. > > Hi, > > The directory ~/repository is missing at beaver. Was it > deleted on purpose, accidentally,... ? > > The upload scripts were under ~/repository/bin, now I see > what it seems a copy at > mavenuser/maven-components/maven-meeper/src/bin, but it's not updated. > Should I update and use this? > > Also the syncopate conf files were under > ~/repository/bin/syncopate/conf, and I'm not sure if the > copies under source control were up to date. > > Regards > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] For > additional commands, e-mail: [EMAIL PROTECTED] > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVEN-1677) "No directory specified for fileset" when debugging for org.apache.commons.jelly.tags.ant.AntTag on
"No directory specified for fileset" when debugging for
org.apache.commons.jelly.tags.ant.AntTag on
---
Key: MAVEN-1677
URL: http://jira.codehaus.org/browse/MAVEN-1677
Project: Maven
Type: Bug
Components: jelly/ant integration
Versions: 1.1-beta-1
Environment: OS X 10.4.2, java version "1.5.0_02"
Reporter: Scott Lamb
Priority: Minor
I've been trying to debug problems by specifying an alternate
log4j.configuration:
$ MAVEN_OPTS="-Dlog4j.configuration=file:$HOME/log4j.properties" maven
In the process, I discovered that when the level for
org.apache.commons.jelly.tags.ant.AntTag is set to DEBUG, maven yields this
error:
File.. ${1}
Element... ant:fileset
Line.. 49
Column 45
No directory specified for fileset.
When logging for that class is at INFO level, this error does not occur.
This happens on the "java:compile" goal of even the simplest project. I can
attach full exception info, the project I used, and the log4j config file I
used if desired.
I'd like to figure out what jelly file this occurred in. The file "${1}" is not
too helpful, though.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Deleted files in beaver at codehaus
I'm sending again this message beacuse seems that the mailing list software don't work very well with the new gmail feature of sending emails with another From address. Hi, The directory ~/repository is missing at beaver. Was it deleted on purpose, accidentally,... ? The upload scripts were under ~/repository/bin, now I see what it seems a copy at mavenuser/maven-components/maven-meeper/src/bin, but it's not updated. Should I update and use this? Also the syncopate conf files were under ~/repository/bin/syncopate/conf, and I'm not sure if the copies under source control were up to date. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-497) ASM 2.1
ASM 2.1 --- Key: MAVENUPLOAD-497 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-497 Project: maven-upload-requests Type: Task Reporter: Eugene Kuleshov Attachments: asm-2.1.bundle.zip http://www.md.pp.ru/~eu/11/asm-2.1.bundle.zip http://asm.objectweb.org/ http://asm.objectweb.org/team.html ASM is a Java bytecode manipulation framework. Groovy team had requested version 2.1 on Ibiblio. Please upload entire bundle (8 artifacts): asm-2.1.jar asm-2.1.pom asm-all-2.1.jar asm-all-2.1.pom asm-analysis-2.1.jar asm-analysis-2.1.pom asm-attrs-2.1.jar asm-attrs-2.1.pom asm-commons-2.1.jar asm-commons-2.1.pom asm-tree-2.1.jar asm-tree-2.1.pom asm-util-2.1.jar asm-util-2.1.pom asm-xml-2.1.jar asm-xml-2.1.pom LICENSE.txt -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - checkout] Tue Aug 30 00:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050830.003000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050830.003000.txt
[maven2 build - SUCCESS - checkout] Tue Aug 30 00:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050830.001500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050830.001500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Tue Aug 30 00:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050830.00.txt
svn commit: r264656 - /maven/maven-1/plugins/trunk/rar/src/plugin-test/project.xml
Author: aheritier
Date: Mon Aug 29 16:31:12 2005
New Revision: 264656
URL: http://svn.apache.org/viewcvs?rev=264656&view=rev
Log:
Fix exception java.lang.StringIndexOutOfBoundsException from
org.apache.commons.jexl.ExpressionImpl when running maven plugins:test-all
pom.siteDirectory mustn't be empty because in the maven-plugins root project we
have :
maven.site.stage.directory=/home/brett/public_html/maven-stage-site/${pom.siteDirectory.substring(22)}
Modified:
maven/maven-1/plugins/trunk/rar/src/plugin-test/project.xml
Modified: maven/maven-1/plugins/trunk/rar/src/plugin-test/project.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/rar/src/plugin-test/project.xml?rev=264656&r1=264655&r2=264656&view=diff
==
--- maven/maven-1/plugins/trunk/rar/src/plugin-test/project.xml (original)
+++ maven/maven-1/plugins/trunk/rar/src/plugin-test/project.xml Mon Aug 29
16:31:12 2005
@@ -16,8 +16,6 @@
* limitations under the License.
*/
-->
-
-
3
Test project for Maven Rar Plugin
@@ -34,7 +32,7 @@
http://bugzilla
www.fooserver.org
-
+ /www/maven.apache.org/reference/plugins/rar/
scm:cvs:pserver:[EMAIL
PROTECTED]:/home/cvspublic:maven
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-802) Clarify SUN's jar distribution policy on site and in Maven so users know to install those files in their own remote repo
[ http://jira.codehaus.org/browse/MNG-802?page=comments#action_45442 ] Carlos Sanchez commented on MNG-802: Links don't work > Clarify SUN's jar distribution policy on site and in Maven so users know to > install those files in their own remote repo > > > Key: MNG-802 > URL: http://jira.codehaus.org/browse/MNG-802 > Project: Maven 2 > Type: Improvement > Components: repository-tools, maven-project, documentation > Versions: 2.0-alpha-3 > Reporter: Natalie Burdick > Priority: Minor > > > refer to: > http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL > PROTECTED] > http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL > PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-804) Maven.jar.overrid
Maven.jar.overrid - Key: MNG-804 URL: http://jira.codehaus.org/browse/MNG-804 Project: Maven 2 Type: Sub-task Components: documentation Reporter: Natalie Burdick Priority: Minor refer to: http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL PROTECTED] to document that unlike m1, m2 no longer allow jar overrides via the maven.jar.override property -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-803) Document of Detailed Changes between M1/M2
Document of Detailed Changes between M1/M2 -- Key: MNG-803 URL: http://jira.codehaus.org/browse/MNG-803 Project: Maven 2 Type: Task Components: documentation Versions: 2.0-alpha-3 Reporter: Natalie Burdick Parent Task will include sub-tasks for specific changes from M1 to M2 that need to be documented -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPXDOC-88) Tables can extend out of window
[ http://jira.codehaus.org/browse/MPXDOC-88?page=all ] Lukas Theussl closed MPXDOC-88: --- Resolution: Fixed Duplicate of MPXDOC-86 > Tables can extend out of window > --- > > Key: MPXDOC-88 > URL: http://jira.codehaus.org/browse/MPXDOC-88 > Project: maven-xdoc-plugin > Type: Bug > Environment: IE 5.5 > Reporter: Dale King > > > This may be a duplication of issue 86, but it has no details. > I notice in a lot of the generated documentation there are tables and those > tables actually extend beyond the browser window and require scrolling to see > the rest of the table. It makes no difference how big the window is. > A good example is the mailing lists page for maven itself: > http://maven.apache.org/mail-lists.html > What I see at the bottom of the page is the table with List Name, Subscribe, > and Unsubscribe, but the Archive column is off to the right and the only way > to see it is to scroll with the horizontal scroll bar. Resizing the window > has no effect on this. > I think what happens is that it says that the table should take 100% of the > page width, but that doesn't take into account the navigation bar. So if the > window width is 600 the table takes 600 but then is moved to the right by the > navigation bar. > This also seems to cause the tables to be pushed down below the navigation > bar. > This affects a lot of the generated documentation. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MNG-802) Clarify SUN's jar distribution policy on site and in Maven so users know to install those files in their own remote repo
Clarify SUN's jar distribution policy on site and in Maven so users know to install those files in their own remote repo Key: MNG-802 URL: http://jira.codehaus.org/browse/MNG-802 Project: Maven 2 Type: Improvement Components: repository-tools, maven-project, documentation Versions: 2.0-alpha-3 Reporter: Natalie Burdick Priority: Minor refer to: http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL PROTECTED] http://mail-archives.apache.org/mod_mbox/maven-users/200508.mbox/[EMAIL PROTECTED] -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Mon Aug 29 22:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050829.223000.txt
[jira] Closed: (MPXDOC-113) Logo relative path not correct
[ http://jira.codehaus.org/browse/MPXDOC-113?page=all ] Lukas Theussl closed MPXDOC-113: Resolution: Fixed Duplicate of MPXDOC-115 > Logo relative path not correct > -- > > Key: MPXDOC-113 > URL: http://jira.codehaus.org/browse/MPXDOC-113 > Project: maven-xdoc-plugin > Type: Bug > Versions: 1.7.1 > Reporter: Matt Read > > > The documentation states that both elements can contain relative or > absolute paths. I'm using the following: > > Concise > http://lee/ > /images/logos/concise.gif > > > /images/logos/corppay.gif > Which gets rendered in the HTML as: > > and > > respectively. > Obviously this is fine on the home page but incorrect on all pages in > directories below the root. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Mon Aug 29 22:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050829.22.txt
[jira] Commented: (MEV-66) cglib 2.1_2 should depend on asm 1.5.3, not 2.0
[ http://jira.codehaus.org/browse/MEV-66?page=comments#action_45437 ] Chris Nokleberg commented on MEV-66: Just wanted to confirm that it should be 1.5.3. Sorry for the confusion! > cglib 2.1_2 should depend on asm 1.5.3, not 2.0 > --- > > Key: MEV-66 > URL: http://jira.codehaus.org/browse/MEV-66 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Ralph Poellath > > > cglib 2.1_2 has a dependency on asm 2.0, with which it is incompatible. > A mailing list discussion on the subject starts at > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112498159906141&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPXDOC-131) allow i18n links
[ http://jira.codehaus.org/browse/MPXDOC-131?page=comments#action_45436 ] Lukas Theussl commented on MPXDOC-131: -- Ignacio, I have checked your latest patch (hrefkey.patch). Unless I'm missing something, the test that you attached does not produce the desired result (an element empty document is generated instead of http://mysite1.com";>empty document) . If you could fix that we'll include it in our next release. > allow i18n links > > > Key: MPXDOC-131 > URL: http://jira.codehaus.org/browse/MPXDOC-131 > Project: maven-xdoc-plugin > Type: Improvement > Reporter: Ignacio G. Mac Dowell > Attachments: hrefkey.patch, last.cumulative.patch, last.docs.patch, > last.main.patch, last.test.patch, plugin.jelly.patch, plugin.properties.patch > > > Currently, we can't directly use the pom or velocity in user-documentation. > JSL is applied to the user-docs as-is. I suggest having a property called > maven.docs.src.templates (defaults to false) that when set to true treats > user-docs as templates. > Then, slightly modify the goal xdoc:jelly-transform. > We need to var's: > > > If both evaluate to true then velocity:merge the user docs before doing jsl. > If they evaluate to false do as before. > It would probably be nice to be able to use jelly as well as user-supplied > docs. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-66) cglib 2.1_2 should depend on asm 1.5.3, not 2.0
[ http://jira.codehaus.org/browse/MEV-66?page=comments#action_45435 ] Ralph Poellath commented on MEV-66: --- The wrong version number in the POM has just been confirmed by a cglib team member. The dependency should definitely be on asm 1.5.3. > cglib 2.1_2 should depend on asm 1.5.3, not 2.0 > --- > > Key: MEV-66 > URL: http://jira.codehaus.org/browse/MEV-66 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Ralph Poellath > > > cglib 2.1_2 has a dependency on asm 2.0, with which it is incompatible. > A mailing list discussion on the subject starts at > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112498159906141&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Mon Aug 29 21:30:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050829.213000.txt
[jira] Commented: (MNG-785) m2 tomcat plugin
[ http://jira.codehaus.org/browse/MNG-785?page=comments#action_45434 ]
Trygve Laugstol commented on MNG-785:
-
We'll figure something out but make sure we don't release it until it's been
resolved.
> m2 tomcat plugin
>
>
> Key: MNG-785
> URL: http://jira.codehaus.org/browse/MNG-785
> Project: Maven 2
> Type: New Feature
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Attachments: maven-tomcat-plugin.tar.gz, maven-tomcat-plugin.zip
>
>
> See attached for an initial stab at a m2 Tomcat plugin. The plugin provides
> the following goals:
> tomcat:deploy
> tomcat:undeploy
> tomcat:reload
> tomcat:start
> tomcat:stop
> It's geared towards Tomcat 5.5 in which the install/remove commands are
> depreciated in preference of deploy/undeploy. It shouldn't be much work to
> add these for Tomcat 5.0 users if necessary.
> I tried to keep the config to a minimum since the vast number of deployment
> options that Tomcat provides tends to complicate plugins. The core config
> params for all tasks are:
> url - the Tomcat manager URL (default = "http://localhost:8080/manager";)
> username - the Tomcat manager username (default = "admin")
> password - the Tomcat manager password (default = "")
> charset - the Tomcat manager request URL encoding charset (default =
> "ISO-8859-1")
> path - the web context path (default = "/${project.build.finalName}")
> The tomcat:deploy goal requires further parameters to customise the type of
> deployment. After considering the various deployment methods supported by
> manager, I decided that the project-centric ones applicable to a m2 plugin
> come down to three modes of operation:
> remote
> - the war is deployed via a HTTP PUT to manager
> - war plugin mode must be "normal" (i.e. not exploded)
> - suitable for cross-network
> local
> - the war is deployed by supplying a path to the war file/dir
> - the war plugin mode config param determines whether the war is deployed as
> a file or as a dir
> - suitable for localhost tomcat
> inplace
> - the war is deployed via a context.xml file that refers to the war dir
> - the war plugin mode must be exploded
> - suitable for dev
> The other Tomcat deployment methods didn't seem too useful for
> project-orientation deployment - they are summarised here:
> http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path
> So the tomcat:deploy specific config params are:
> mode - "remote", "local" or "inplace" (default = "remote")
> war - the war file path (default =
> "${project.build.directory}/${project.build.finalName}.war")
> warDir - the war dir path (default =
> "${project.build.directory}/${project.build.finalName}")
> config - the context.xml path (default =
> "${project.build.directory}/${project.build.finalName}/META-INF/context.xml")
> update - whether to undeploy before deploying (default = false)
> When deploying inplace the context.xml Context/@docBase attribute needs to be
> set to the war dir. I noticed the discussion on the m2 mailing list
> regarding resource filtering, so hopefully that can perform this task pre-war.
> The code is inspired by the Tomcat Ant tasks, but rewritten for m2. This is
> my first m2 plugin so any constructive comments are welcome! In particular,
> feedback on the following would be appreciated:
> - opinions on the remote/local/inplace mode of operations
> - any config options I've missed
> - is the method of introspecting the war plugin config the norm, or is there
> a nicer way?
> You're welcome to the code & I'm happy to adopt this plugin time-permitting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-496) Upload wicket-1.0.3-bundle.jar
Upload wicket-1.0.3-bundle.jar -- Key: MAVENUPLOAD-496 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-496 Project: maven-upload-requests Type: Task Reporter: Martijn Dashorst http://wicket.sourceforge.net/downloads/wicket-1.0.3-bundle.jar http://wicket.sourceforge.net http://wicket.sourceforge.net/team-list.html Wicket is a Java web application framework that takes simplicity, separation of concerns and ease of development to a whole new level. Wicket pages can be mocked up, previewed and later revised using standard WYSIWYG HTML design tools. Dynamic content processing and form handling is all handled in Java code using a first-class component model backed by POJO data beans that can easily be persisted using your favourite technology. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - FAILED - update] Mon Aug 29 21:00:00 GMT 2005
Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050829.21.txt
[jira] Closed: (CONTINUUM-298) Upgrade to JPOX 1.1-beta-4
[ http://jira.codehaus.org/browse/CONTINUUM-298?page=all ] Emmanuel Venisse closed CONTINUUM-298: -- Resolution: Fixed Fixed. > Upgrade to JPOX 1.1-beta-4 > -- > > Key: CONTINUUM-298 > URL: http://jira.codehaus.org/browse/CONTINUUM-298 > Project: Continuum > Type: Task > Components: continuum-core > Reporter: Trygve Laugstol > Assignee: Emmanuel Venisse > Fix For: 1.0-alpha-4 > > Original Estimate: 30 minutes >Time Spent: 30 minutes > Remaining: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
svn commit: r264637 - in /maven/maven-1/plugins/trunk/xdoc/src/plugin-test: maven.xml test01/project.xml
Author: aheritier Date: Mon Aug 29 13:40:23 2005 New Revision: 264637 URL: http://svn.apache.org/viewcvs?rev=264637&view=rev Log: Fix plugin tests Modified: maven/maven-1/plugins/trunk/xdoc/src/plugin-test/maven.xml maven/maven-1/plugins/trunk/xdoc/src/plugin-test/test01/project.xml Modified: maven/maven-1/plugins/trunk/xdoc/src/plugin-test/maven.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/plugin-test/maven.xml?rev=264637&r1=264636&r2=264637&view=diff == --- maven/maven-1/plugins/trunk/xdoc/src/plugin-test/maven.xml (original) +++ maven/maven-1/plugins/trunk/xdoc/src/plugin-test/maven.xml Mon Aug 29 13:40:23 2005 @@ -17,11 +17,11 @@ --> - + + - + + Modified: maven/maven-1/plugins/trunk/xdoc/src/plugin-test/test01/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/xdoc/src/plugin-test/test01/project.xml?rev=264637&r1=264636&r2=264637&view=diff == --- maven/maven-1/plugins/trunk/xdoc/src/plugin-test/test01/project.xml (original) +++ maven/maven-1/plugins/trunk/xdoc/src/plugin-test/test01/project.xml Mon Aug 29 13:40:23 2005 @@ -16,11 +16,9 @@ * limitations under the License. */ --> - - 3 - test-maven-xdoc-plugin + test-maven-xdoc-plugin-01 Maven Xdoc Plugin 01 maven 1.0 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-785) m2 tomcat plugin
[ http://jira.codehaus.org/browse/MNG-785?page=comments#action_45432 ]
Mark Hobson commented on MNG-785:
-
Wahey! Thanks for that. Regarding isWarExploded(), yeah I thought that was
pretty dirty but couldn't find any other examples of plugins introspecting
other plugin's configurations. I'm happy to change it if anyone knows of a
better way.
> m2 tomcat plugin
>
>
> Key: MNG-785
> URL: http://jira.codehaus.org/browse/MNG-785
> Project: Maven 2
> Type: New Feature
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Attachments: maven-tomcat-plugin.tar.gz, maven-tomcat-plugin.zip
>
>
> See attached for an initial stab at a m2 Tomcat plugin. The plugin provides
> the following goals:
> tomcat:deploy
> tomcat:undeploy
> tomcat:reload
> tomcat:start
> tomcat:stop
> It's geared towards Tomcat 5.5 in which the install/remove commands are
> depreciated in preference of deploy/undeploy. It shouldn't be much work to
> add these for Tomcat 5.0 users if necessary.
> I tried to keep the config to a minimum since the vast number of deployment
> options that Tomcat provides tends to complicate plugins. The core config
> params for all tasks are:
> url - the Tomcat manager URL (default = "http://localhost:8080/manager";)
> username - the Tomcat manager username (default = "admin")
> password - the Tomcat manager password (default = "")
> charset - the Tomcat manager request URL encoding charset (default =
> "ISO-8859-1")
> path - the web context path (default = "/${project.build.finalName}")
> The tomcat:deploy goal requires further parameters to customise the type of
> deployment. After considering the various deployment methods supported by
> manager, I decided that the project-centric ones applicable to a m2 plugin
> come down to three modes of operation:
> remote
> - the war is deployed via a HTTP PUT to manager
> - war plugin mode must be "normal" (i.e. not exploded)
> - suitable for cross-network
> local
> - the war is deployed by supplying a path to the war file/dir
> - the war plugin mode config param determines whether the war is deployed as
> a file or as a dir
> - suitable for localhost tomcat
> inplace
> - the war is deployed via a context.xml file that refers to the war dir
> - the war plugin mode must be exploded
> - suitable for dev
> The other Tomcat deployment methods didn't seem too useful for
> project-orientation deployment - they are summarised here:
> http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path
> So the tomcat:deploy specific config params are:
> mode - "remote", "local" or "inplace" (default = "remote")
> war - the war file path (default =
> "${project.build.directory}/${project.build.finalName}.war")
> warDir - the war dir path (default =
> "${project.build.directory}/${project.build.finalName}")
> config - the context.xml path (default =
> "${project.build.directory}/${project.build.finalName}/META-INF/context.xml")
> update - whether to undeploy before deploying (default = false)
> When deploying inplace the context.xml Context/@docBase attribute needs to be
> set to the war dir. I noticed the discussion on the m2 mailing list
> regarding resource filtering, so hopefully that can perform this task pre-war.
> The code is inspired by the Tomcat Ant tasks, but rewritten for m2. This is
> my first m2 plugin so any constructive comments are welcome! In particular,
> feedback on the following would be appreciated:
> - opinions on the remote/local/inplace mode of operations
> - any config options I've missed
> - is the method of introspecting the war plugin config the norm, or is there
> a nicer way?
> You're welcome to the code & I'm happy to adopt this plugin time-permitting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r264636 - in /maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr: CodeTransformTest.java JxrBeanTest.java
Author: aheritier
Date: Mon Aug 29 13:37:55 2005
New Revision: 264636
URL: http://svn.apache.org/viewcvs?rev=264636&view=rev
Log:
Fix junit tests (ressources paths) when launched in the reactor
Modified:
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/CodeTransformTest.java
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/JxrBeanTest.java
Modified:
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/CodeTransformTest.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/CodeTransformTest.java?rev=264636&r1=264635&r2=264636&view=diff
==
---
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/CodeTransformTest.java
(original)
+++
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/CodeTransformTest.java
Mon Aug 29 13:37:55 2005
@@ -6,30 +6,35 @@
import org.apache.maven.jxr.pacman.PackageManager;
-public class CodeTransformTest extends TestCase {
+public class CodeTransformTest
+extends TestCase
+{
private CodeTransform codeTransform;
private PackageManager packageManager;
-protected void setUp() throws Exception {
+protected void setUp()
+throws Exception
+{
super.setUp();
packageManager = new PackageManager();
-codeTransform = new CodeTransform(packageManager);
+codeTransform = new CodeTransform( packageManager );
}
-public void testTransform() throws Exception {
-File sourceFile = new File(
-"src/test/org/apache/maven/jxr/CodeTransformTest.java");
-assertTrue(sourceFile.exists());
-codeTransform.transform(sourceFile.getAbsolutePath(),
-"target/CodeTransformTest.html", "en", "ISO-8859-1",
-"ISO-8859-1", "", "");
-//sourceFile = new
File("src/test/org/apache/maven/jxr/package-info.java");
-//assertTrue(sourceFile.exists());
-//codeTransform.transform(sourceFile.getAbsolutePath(),
-//"target/pakage-info.html", "en", "ISO-8859-1", "ISO-8859-1",
-//"", "");
+public void testTransform()
+throws Exception
+{
+File sourceFile = new File( System.getProperty( "basedir" )
++ "/src/test/org/apache/maven/jxr/CodeTransformTest.java" );
+assertTrue( sourceFile.exists() );
+codeTransform.transform( sourceFile.getAbsolutePath(),
System.getProperty( "basedir" )
++ "/target/CodeTransformTest.html", "en", "ISO-8859-1",
"ISO-8859-1", "", "" );
+//sourceFile = new
File("src/test/org/apache/maven/jxr/package-info.java");
+//assertTrue(sourceFile.exists());
+//codeTransform.transform(sourceFile.getAbsolutePath(),
+//"target/pakage-info.html", "en", "ISO-8859-1",
"ISO-8859-1",
+//"", "");
}
}
Modified:
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/JxrBeanTest.java
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/JxrBeanTest.java?rev=264636&r1=264635&r2=264636&view=diff
==
---
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/JxrBeanTest.java
(original)
+++
maven/maven-1/plugins/trunk/jxr/src/test/org/apache/maven/jxr/JxrBeanTest.java
Mon Aug 29 13:37:55 2005
@@ -2,25 +2,31 @@
import junit.framework.TestCase;
-public class JxrBeanTest extends TestCase {
+public class JxrBeanTest
+extends TestCase
+{
private JxrBean jxrBean;
-protected void setUp() throws Exception {
+protected void setUp()
+throws Exception
+{
super.setUp();
jxrBean = new JxrBean();
-jxrBean.setSourceDir("src/test");
-jxrBean.setDestDir("target");
-jxrBean.setInputEncoding("ISO-8859-1");
-jxrBean.setOutputEncoding("ISO-8859-1");
-jxrBean.setTemplateDir("src/plugin-resources/templates");
-jxrBean.setJavadocDir("");
-jxrBean.setWindowTitle("title");
-jxrBean.setDocTitle("title");
-jxrBean.setBottom("copyright");
+jxrBean.setSourceDir( System.getProperty( "basedir" ) + "/src/test" );
+jxrBean.setDestDir( System.getProperty( "basedir" ) + "/target" );
+jxrBean.setInputEncoding( "ISO-8859-1" );
+jxrBean.setOutputEncoding( "ISO-8859-1" );
+jxrBean.setTemplateDir( System.getProperty( "basedir" ) +
"/src/plugin-resources/templates" );
+jxrBean.setJavadocDir( "" );
+jxrBean.setWindowTitle( "title" );
+jxrBean.setDocTitle( "title" );
+jxrBean.setBottom( "copyright" );
}
-public void testXref() throws Exception {
+public void testXref()
+
svn commit: r264635 - /maven/maven-1/plugins/trunk/jxr/
Author: aheritier Date: Mon Aug 29 13:36:32 2005 New Revision: 264635 URL: http://svn.apache.org/viewcvs?rev=264635&view=rev Log: update ignored files (eclipse, temporary junit properties, ...) Modified: maven/maven-1/plugins/trunk/jxr/ (props changed) Propchange: maven/maven-1/plugins/trunk/jxr/ -- --- svn:ignore (original) +++ svn:ignore Mon Aug 29 13:36:32 2005 @@ -1,11 +1,4 @@ -target -velocity.log -maven.log .classpath .project -build.properties .settings -*.iml -*.ipr -*.iws -project.xml.backup +junit*.properties - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPXDOC-161) Tabbed browsing for multiprojects (this change involves both the multiproject plugin and xdoc)
[ http://jira.codehaus.org/browse/MPXDOC-161?page=comments#action_45431 ] Arnaud Heritier commented on MPXDOC-161: did you test if there's no side effect for sites without tabs ? If you send us the patch we'll try to commit it for the next main release (1.10) of the xdoc plugin (and for the multiproject plugin). Please, if you want, send us 2 patches (xdoc + multiproject) and we'll add a link between the 2 issues. > Tabbed browsing for multiprojects (this change involves both the multiproject > plugin and xdoc) > -- > > Key: MPXDOC-161 > URL: http://jira.codehaus.org/browse/MPXDOC-161 > Project: maven-xdoc-plugin > Type: New Feature > Versions: 1.9.1 > Reporter: Ignacio G. Mac Dowell > Attachments: tabbed.jpg > > > Currently only aggregate navigation is possible on the top level project. It > would be nice to be able to generate tabbed browsing. I have successfully > done this with only a few changes to both plugins. I have attached a > screenshot to see the benefits. If this sounds interesting I'll send the > patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (CONTINUUM-298) Upgrade to JPOX 1.1-beta-4
[ http://jira.codehaus.org/browse/CONTINUUM-298?page=all ] Emmanuel Venisse reopened CONTINUUM-298: Upgrading jpox dep in continuum root fail the build. > Upgrade to JPOX 1.1-beta-4 > -- > > Key: CONTINUUM-298 > URL: http://jira.codehaus.org/browse/CONTINUUM-298 > Project: Continuum > Type: Task > Components: continuum-core > Reporter: Trygve Laugstol > Assignee: Emmanuel Venisse > Fix For: 1.0-alpha-4 > > Original Estimate: 30 minutes >Time Spent: 30 minutes > Remaining: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MNG-785) m2 tomcat plugin
[ http://jira.codehaus.org/browse/MNG-785?page=comments#action_45428 ]
Trygve Laugstol commented on MNG-785:
-
Go fetch!
svn co
https://svn.codehaus.org/mojo/trunk/mojo/mojo-sandbox/maven-tomcat-plugin/
> m2 tomcat plugin
>
>
> Key: MNG-785
> URL: http://jira.codehaus.org/browse/MNG-785
> Project: Maven 2
> Type: New Feature
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Attachments: maven-tomcat-plugin.tar.gz, maven-tomcat-plugin.zip
>
>
> See attached for an initial stab at a m2 Tomcat plugin. The plugin provides
> the following goals:
> tomcat:deploy
> tomcat:undeploy
> tomcat:reload
> tomcat:start
> tomcat:stop
> It's geared towards Tomcat 5.5 in which the install/remove commands are
> depreciated in preference of deploy/undeploy. It shouldn't be much work to
> add these for Tomcat 5.0 users if necessary.
> I tried to keep the config to a minimum since the vast number of deployment
> options that Tomcat provides tends to complicate plugins. The core config
> params for all tasks are:
> url - the Tomcat manager URL (default = "http://localhost:8080/manager";)
> username - the Tomcat manager username (default = "admin")
> password - the Tomcat manager password (default = "")
> charset - the Tomcat manager request URL encoding charset (default =
> "ISO-8859-1")
> path - the web context path (default = "/${project.build.finalName}")
> The tomcat:deploy goal requires further parameters to customise the type of
> deployment. After considering the various deployment methods supported by
> manager, I decided that the project-centric ones applicable to a m2 plugin
> come down to three modes of operation:
> remote
> - the war is deployed via a HTTP PUT to manager
> - war plugin mode must be "normal" (i.e. not exploded)
> - suitable for cross-network
> local
> - the war is deployed by supplying a path to the war file/dir
> - the war plugin mode config param determines whether the war is deployed as
> a file or as a dir
> - suitable for localhost tomcat
> inplace
> - the war is deployed via a context.xml file that refers to the war dir
> - the war plugin mode must be exploded
> - suitable for dev
> The other Tomcat deployment methods didn't seem too useful for
> project-orientation deployment - they are summarised here:
> http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path
> So the tomcat:deploy specific config params are:
> mode - "remote", "local" or "inplace" (default = "remote")
> war - the war file path (default =
> "${project.build.directory}/${project.build.finalName}.war")
> warDir - the war dir path (default =
> "${project.build.directory}/${project.build.finalName}")
> config - the context.xml path (default =
> "${project.build.directory}/${project.build.finalName}/META-INF/context.xml")
> update - whether to undeploy before deploying (default = false)
> When deploying inplace the context.xml Context/@docBase attribute needs to be
> set to the war dir. I noticed the discussion on the m2 mailing list
> regarding resource filtering, so hopefully that can perform this task pre-war.
> The code is inspired by the Tomcat Ant tasks, but rewritten for m2. This is
> my first m2 plugin so any constructive comments are welcome! In particular,
> feedback on the following would be appreciated:
> - opinions on the remote/local/inplace mode of operations
> - any config options I've missed
> - is the method of introspecting the war plugin config the norm, or is there
> a nicer way?
> You're welcome to the code & I'm happy to adopt this plugin time-permitting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-785) m2 tomcat plugin
[ http://jira.codehaus.org/browse/MNG-785?page=comments#action_45427 ]
Trygve Laugstol commented on MNG-785:
-
Imported into the Mojo repository.
Fixed some minor stuff
- Moved to the org.codehaus.mojo.tomcat package
- Changed the copyright years to "2005", changed copyright to "Mark Hobson".
You wrote it after all, you should get the credit/blame :) If you've taken
parts of Apache code there please include the original Apache license there
aswell
- Ran the IDEA autoformatter over the code
The isWarExploded method in the deploy mojo is pretty nasty, we need to find a
better way to do that.
> m2 tomcat plugin
>
>
> Key: MNG-785
> URL: http://jira.codehaus.org/browse/MNG-785
> Project: Maven 2
> Type: New Feature
> Components: maven-plugins
> Versions: 2.0-beta-1
> Reporter: Mark Hobson
> Attachments: maven-tomcat-plugin.tar.gz, maven-tomcat-plugin.zip
>
>
> See attached for an initial stab at a m2 Tomcat plugin. The plugin provides
> the following goals:
> tomcat:deploy
> tomcat:undeploy
> tomcat:reload
> tomcat:start
> tomcat:stop
> It's geared towards Tomcat 5.5 in which the install/remove commands are
> depreciated in preference of deploy/undeploy. It shouldn't be much work to
> add these for Tomcat 5.0 users if necessary.
> I tried to keep the config to a minimum since the vast number of deployment
> options that Tomcat provides tends to complicate plugins. The core config
> params for all tasks are:
> url - the Tomcat manager URL (default = "http://localhost:8080/manager";)
> username - the Tomcat manager username (default = "admin")
> password - the Tomcat manager password (default = "")
> charset - the Tomcat manager request URL encoding charset (default =
> "ISO-8859-1")
> path - the web context path (default = "/${project.build.finalName}")
> The tomcat:deploy goal requires further parameters to customise the type of
> deployment. After considering the various deployment methods supported by
> manager, I decided that the project-centric ones applicable to a m2 plugin
> come down to three modes of operation:
> remote
> - the war is deployed via a HTTP PUT to manager
> - war plugin mode must be "normal" (i.e. not exploded)
> - suitable for cross-network
> local
> - the war is deployed by supplying a path to the war file/dir
> - the war plugin mode config param determines whether the war is deployed as
> a file or as a dir
> - suitable for localhost tomcat
> inplace
> - the war is deployed via a context.xml file that refers to the war dir
> - the war plugin mode must be exploded
> - suitable for dev
> The other Tomcat deployment methods didn't seem too useful for
> project-orientation deployment - they are summarised here:
> http://jakarta.apache.org/tomcat/tomcat-5.5-doc/manager-howto.html#Deploy%20A%20New%20Application%20from%20a%20Local%20Path
> So the tomcat:deploy specific config params are:
> mode - "remote", "local" or "inplace" (default = "remote")
> war - the war file path (default =
> "${project.build.directory}/${project.build.finalName}.war")
> warDir - the war dir path (default =
> "${project.build.directory}/${project.build.finalName}")
> config - the context.xml path (default =
> "${project.build.directory}/${project.build.finalName}/META-INF/context.xml")
> update - whether to undeploy before deploying (default = false)
> When deploying inplace the context.xml Context/@docBase attribute needs to be
> set to the war dir. I noticed the discussion on the m2 mailing list
> regarding resource filtering, so hopefully that can perform this task pre-war.
> The code is inspired by the Tomcat Ant tasks, but rewritten for m2. This is
> my first m2 plugin so any constructive comments are welcome! In particular,
> feedback on the following would be appreciated:
> - opinions on the remote/local/inplace mode of operations
> - any config options I've missed
> - is the method of introspecting the war plugin config the norm, or is there
> a nicer way?
> You're welcome to the code & I'm happy to adopt this plugin time-permitting.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPXDOC-119) and - functionality + docs
[ http://jira.codehaus.org/browse/MPXDOC-119?page=all ] Lukas Theussl closed MPXDOC-119: Resolution: Won't Fix The element should go into the of navigation.xml (it is in a element in your source code). The element is not recognized in xdocs (where did you see that documented?). The element should go into a element of the source xdoc files (not navigation.xml). Let us know if this doesn't resolve your problems and we'll reopen the issue. > and - functionality + docs > --- > > Key: MPXDOC-119 > URL: http://jira.codehaus.org/browse/MPXDOC-119 > Project: maven-xdoc-plugin > Type: Wish > Versions: 1.8 > Environment: Linux rama.paneris.org 2.4.20-8 > Java HotSpot(TM) Client VM (build 1.4.2-b28, mixed mode) > 5968458 Jul 13 15:19 maven-1.0.tar.gz > 156115 Jul 13 14:20 maven/plugins/maven-xdoc-plugin-1.8.jar > Reporter: Peter Kehl > > > Dear colleagues, > we have a 2/3 maven-enabled projects: http://spindent.paneris.net and > http://melati.org; this is issue happened at spindent.paneris.net. > Basically, and don't work - no new HTML > elements are created when I run "maven site". Maybe isn't supposed > to work - I don't know how it got there. Xdocs used are in CVS (online). > Generally, it would help if Maven and Maven's plugins were better documented, > especially their all XML tags. Otherwise it's a powerful tool but its power > is kept secret. It would help to have user and tag documentation more > structured and available direct online - that's what users need first. > - > xdocs/navigation.xml: > > > rest of xdocs/*.xml: > > > > Source code indentation. > > > > > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MAVENUPLOAD-495) Please upload DWR 1.0
Please upload DWR 1.0 - Key: MAVENUPLOAD-495 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-495 Project: maven-upload-requests Type: Task Reporter: Julien Dubois This is the final 1.0 release of DWR, after MAVENUPLOAD-433 and MAVENUPLOAD-477. Thank you! Julien Dubois. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Deleted files in beaver at codehaus
Hi, The directory ~/repository is missing at beaver. Was it deleted on purpose, accidentally,... ? The upload scripts were under ~/repository/bin, now I see what it seems a copy at mavenuser/maven-components/maven-meeper/src/bin, but it's not updated. Should I update and use this? Also the syncopate conf files were under ~/repository/bin/syncopate/conf, and I'm not sure if the copies under source control were up to date. Regards - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-479) This is the spellchecker component of Lucene as described in http://wiki.apache.org/jakarta-lucene/SpellChecker.
[ http://jira.codehaus.org/browse/MAVENUPLOAD-479?page=all ] Carlos Sanchez closed MAVENUPLOAD-479: -- Assign To: Carlos Sanchez Resolution: Incomplete > This is the spellchecker component of Lucene as described in > http://wiki.apache.org/jakarta-lucene/SpellChecker. > > > Key: MAVENUPLOAD-479 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-479 > Project: maven-upload-requests > Type: Wish > Reporter: Chris Kimm > Assignee: Carlos Sanchez > > > The "mis-spelling" of spellcheker-1.1 is intentional. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-492) Nees to upload a slf4j beta7 jar
[ http://jira.codehaus.org/browse/MAVENUPLOAD-492?page=all ] Carlos Sanchez closed MAVENUPLOAD-492: -- Assign To: Carlos Sanchez Resolution: Duplicate MAVENUPLOAD-494 > Nees to upload a slf4j beta7 jar > > > Key: MAVENUPLOAD-492 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-492 > Project: maven-upload-requests > Type: Task > Reporter: Jeff Genender > Assignee: Carlos Sanchez > > > http://people.apache.org/~jgenender/slf4j-simple-1.0-beta7-bundle.jar > http://www.slf4j.org -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MAVENUPLOAD-493) Upload request for NLOG4J 1.2.17 and SLF4J 1.0-beta7
[ http://jira.codehaus.org/browse/MAVENUPLOAD-493?page=all ] Carlos Sanchez closed MAVENUPLOAD-493: -- Assign To: Carlos Sanchez Resolution: Duplicate MAVENUPLOAD-494 > Upload request for NLOG4J 1.2.17 and SLF4J 1.0-beta7 > > > Key: MAVENUPLOAD-493 > URL: http://jira.codehaus.org/browse/MAVENUPLOAD-493 > Project: maven-upload-requests > Type: Task > Reporter: Ceki Gulcu > Assignee: Carlos Sanchez > Attachments: nlog4j-1.2.17.jar, slf4j-jdk14-1.0-beta7-bundle.jar, > slf4j-jdk14-1.0-beta7.jar, slf4j-nop-1.0-beta7-bundle.jar, > slf4j-nop-1.0-beta7.jar, slf4j-simple-1.0-beta7-bundle.jar, > slf4j-simple-1.0-beta7.jar > > > The SLF4J project recently released version 1.0beta7 of the SLF4J API as well > as version 1.2.17 of NLOG4J. The POM files for a previous version of SLF4J > already exist. > Could you please upload the attached jar files to maven? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (CONTINUUM-298) Upgrade to JPOX 1.1-beta-4
[ http://jira.codehaus.org/browse/CONTINUUM-298?page=all ] Emmanuel Venisse closed CONTINUUM-298: -- Resolution: Fixed Done. > Upgrade to JPOX 1.1-beta-4 > -- > > Key: CONTINUUM-298 > URL: http://jira.codehaus.org/browse/CONTINUUM-298 > Project: Continuum > Type: Task > Components: continuum-core > Reporter: Trygve Laugstol > Assignee: Emmanuel Venisse > Fix For: 1.0-alpha-4 > > Original Estimate: 30 minutes >Time Spent: 30 minutes > Remaining: 0 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-298) Upgrade to JPOX 1.1-beta-4
[ http://jira.codehaus.org/browse/CONTINUUM-298?page=all ] Emmanuel Venisse updated CONTINUUM-298: --- Assign To: Emmanuel Venisse Remaining Estimate: 30 minutes Original Estimate: 1800 > Upgrade to JPOX 1.1-beta-4 > -- > > Key: CONTINUUM-298 > URL: http://jira.codehaus.org/browse/CONTINUUM-298 > Project: Continuum > Type: Task > Components: continuum-core > Reporter: Trygve Laugstol > Assignee: Emmanuel Venisse > Fix For: 1.0-alpha-4 > > Original Estimate: 30 minutes > Remaining: 30 minutes > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
RE: SVN Build Error
I set up maven-proxy and have made a couple attempts now to rebuild Maven2 using the proxy as a mirror of "central" and "snapshots". My problem is that I have four integration tests failing (8, 9, 45, and 46); they all seem to be related to trying to download an artifact from codehaus (actually from my mirror) that looks like it should have just been created during the build (maven-core-it-plugin:1.0-SNAPSHOT plugin, maven-core-it-plugin:RELEASE plugin, and maven-core-it-plugin-RELEASE POM). Is this normal or do I have something messed up in my mirror? -Original Message- From: Allison, Bob Sent: Sunday, August 28, 2005 15:27 To: 'Maven Developers List' Subject: RE: SVN Build Error [snip] I have no idea why I am getting 503 errors either. I ran a wget session to mirror the entire ibiblio maven2 repository overnight. I got to downloading the stuff in servicemix before I stopped it. In running for almost 24 hours it had no problems (shoot, I just realized it was FTP, not http). With the mirror you suggested, the entire build went without a hitch. As far as I know I do not have a proxy in use, but I don't know if my company has a transparent proxy in my way. Is there a good way to do a mirror of the ibiblio stuff using http to check to see if I am having problems in general or if it is a problem in the build process? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[continuum build - SUCCESS - update] Mon Aug 29 12:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050829.123000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050829.123000.txt
[jira] Deleted: (CONTINUUM-282) use build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-282?page=all ] Emmanuel Venisse deleted CONTINUUM-282: --- > use build definitions > - > > Key: CONTINUUM-282 > URL: http://jira.codehaus.org/browse/CONTINUUM-282 > Project: Continuum > Type: New Feature > Reporter: Brett Porter > Assignee: Emmanuel Venisse > Priority: Blocker > > Time Spent: 4 hours >Remaining: 5 hours > > we need to write these into the web interface so that we have the > functionality from alpha-3 > http://people.apache.org/~brett/white-site/viewProject.html > http://people.apache.org/~brett/white-site/addBuildDef.html > just use default schedules and profiles to begin with. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-299) use build definitions
use build definitions - Key: CONTINUUM-299 URL: http://jira.codehaus.org/browse/CONTINUUM-299 Project: Continuum Type: New Feature Components: continuum-web Reporter: Emmanuel Venisse Assigned to: Emmanuel Venisse Priority: Blocker Fix For: 1.0-alpha-4 we need to write these into the web interface so that we have the functionality from alpha-3 http://people.apache.org/~brett/white-site/viewProject.html http://people.apache.org/~brett/white-site/addBuildDef.html just use default schedules and profiles to begin with. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MEV-66) cglib 2.1_2 should depend on asm 1.5.3, not 2.0
[ http://jira.codehaus.org/browse/MEV-66?page=comments#action_45398 ]
Joerg Schaible commented on MEV-66:
---
public void testCGLib() throws Exception {
assertNotNull(new Enhancer());
}
throws with cglib-2.1_2 and asm-2.0:
%<
java.lang.NoClassDefFoundError: org/objectweb/asm/CodeVisitor
at
net.sf.cglib.core.KeyFactory$Generator.generateClass(KeyFactory.java:165)
at
net.sf.cglib.core.DefaultGeneratorStrategy.generate(DefaultGeneratorStrategy.java:25)
at
net.sf.cglib.core.AbstractClassGenerator.create(AbstractClassGenerator.java:215)
at net.sf.cglib.core.KeyFactory$Generator.create(KeyFactory.java:145)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:117)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:108)
at net.sf.cglib.core.KeyFactory.create(KeyFactory.java:104)
at net.sf.cglib.proxy.Enhancer.(Enhancer.java:69)
at demo.CGLibTest.testCGLib(CGLibTest.java:33)
Exception in thread "main"
%<
Works with cglib-2.1_2 and asm-1.5.3 or with cglib-nodeps-2.1_2 alone. There is
no org.objectweb.asm.CodeVisitor anymore in asm-2.0:
http://asm.objectweb.org/current/doc/javadoc/user/index.html
> cglib 2.1_2 should depend on asm 1.5.3, not 2.0
> ---
>
> Key: MEV-66
> URL: http://jira.codehaus.org/browse/MEV-66
> Project: Maven Evangelism
> Type: Bug
> Components: Dependencies
> Reporter: Ralph Poellath
>
>
> cglib 2.1_2 has a dependency on asm 2.0, with which it is incompatible.
> A mailing list discussion on the subject starts at
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112498159906141&w=2
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-57) Invalid commons-beanutils:commons-beanutils versions
[ http://jira.codehaus.org/browse/MEV-57?page=comments#action_45397 ] Yann Le Du commented on MEV-57: --- Not sure on what to elaborate but... what I meant is (e.g. for the 1st one) : http://www.ibiblio.org/maven2/commons-beanutils/commons-beanutils/1.4/commons-beanutils-1.4.pom contains 1.0-dev ...while Maven would have expected : * either to have 1.4 instead * or to have the POM placed in directory 1.0-dev Hope it is clear enough - now :) > Invalid commons-beanutils:commons-beanutils versions > > > Key: MEV-57 > URL: http://jira.codehaus.org/browse/MEV-57 > Project: Maven Evangelism > Type: Bug > Components: Invalid POM > Reporter: Yann Le Du > > > 1.4 : 1.0-dev > 1.4.1 : 1.0-dev > 1.6 : 1.6-dev > 1.6.1 : 1.7-dev -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Retrieving test dependencies in junit tests?
Trygve Laugstøl wrote: >I'm pretty sure that he was refering to the Modello build itself where we >generate source code and use the Plexus compilers to compile the generated >sources and test them[1]. Now I just realized that we're not doing that >anymore, but I think we used to set that property there. > >Anyway, the Modello build show how we're using the local repository and >the Maven components to get access to artifacts in the repository. > >[1]: >http://svn.modello.codehaus.org/trunk/modello/modello-test/src/main/java/org/codehaus/modello/AbstractModelloGeneratorTest.java?rev=430&view=auto > >[snip] > > > Right... my memory failed me. Actually, we have a reusable library for this: http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-artifact-test/src/main/java/org/apache/maven/artifact/test/ArtifactTestCase.java?rev=191634&view=markup It does depend on plexus though. - Brett - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MPECLIPSE-99) documentation on http://mevenide.codehaus.org/mevenide-ui-eclipse/user-guide/conf.html incomplete
[ http://jira.codehaus.org/browse/MPECLIPSE-99?page=all ] Trygve Laugstol closed MPECLIPSE-99: Resolution: Won't Fix This is the wrong project to file this issue under, this is for the Maven Eclipse Plug-in, not the MevenIDE project. http://jira.codehaus.org/browse/MEVENIDE is probably the correct project for creating mevenide issues. > documentation on > http://mevenide.codehaus.org/mevenide-ui-eclipse/user-guide/conf.html > incomplete > - > > Key: MPECLIPSE-99 > URL: http://jira.codehaus.org/browse/MPECLIPSE-99 > Project: maven-eclipse-plugin > Type: Improvement > Versions: 1.9 > Environment: all > Reporter: Ron Wheeler > > > The documentation does not describe the locations pane except to say that it > is the locations pane. > It needs to describe the fields in it and what they should point to. > In the short term it also should emphasize that the installation does not > fill in the correct values into these fields and that the should start with > "file://" if the locationis a local file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-66) cglib 2.1_2 should depend on asm 1.5.3, not 2.0
[ http://jira.codehaus.org/browse/MEV-66?page=comments#action_45395 ] Ralph Poellath commented on MEV-66: --- Could you provide a test case? > cglib 2.1_2 should depend on asm 1.5.3, not 2.0 > --- > > Key: MEV-66 > URL: http://jira.codehaus.org/browse/MEV-66 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Ralph Poellath > > > cglib 2.1_2 has a dependency on asm 2.0, with which it is incompatible. > A mailing list discussion on the subject starts at > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112498159906141&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MPECLIPSE-98) Default locations not formatted correctly out of the box
[ http://jira.codehaus.org/browse/MPECLIPSE-98?page=comments#action_45394 ] Trygve Laugstol commented on MPECLIPSE-98: -- What are Eclipse expecting? Whatever the plugin is generating seems to be working for most people. Which version of eclipse are you using? > Default locations not formatted correctly out of the box > > > Key: MPECLIPSE-98 > URL: http://jira.codehaus.org/browse/MPECLIPSE-98 > Project: maven-eclipse-plugin > Type: Bug > Versions: 1.9 > Environment: Windows 2000 Eclipse 3.1 java 1.5 > Reporter: Ron Wheeler > > > The locations seem to need start "file://" but they are not setup that way > when maven-eclipse is installed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPECLIPSE-99) documentation on http://mevenide.codehaus.org/mevenide-ui-eclipse/user-guide/conf.html incomplete
documentation on http://mevenide.codehaus.org/mevenide-ui-eclipse/user-guide/conf.html incomplete - Key: MPECLIPSE-99 URL: http://jira.codehaus.org/browse/MPECLIPSE-99 Project: maven-eclipse-plugin Type: Improvement Versions: 1.9 Environment: all Reporter: Ron Wheeler The documentation does not describe the locations pane except to say that it is the locations pane. It needs to describe the fields in it and what they should point to. In the short term it also should emphasize that the installation does not fill in the correct values into these fields and that the should start with "file://" if the locationis a local file. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPECLIPSE-98) Default locations not formatted correctly out of the box
Default locations not formatted correctly out of the box Key: MPECLIPSE-98 URL: http://jira.codehaus.org/browse/MPECLIPSE-98 Project: maven-eclipse-plugin Type: Bug Versions: 1.9 Environment: Windows 2000 Eclipse 3.1 java 1.5 Reporter: Ron Wheeler The locations seem to need start "file://" but they are not setup that way when maven-eclipse is installed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-66) cglib 2.1_2 should depend on asm 1.5.3, not 2.0
[ http://jira.codehaus.org/browse/MEV-66?page=comments#action_45393 ] Joerg Schaible commented on MEV-66: --- So I advice any of those "cglib team members" at least to try to use cglib-2.1_2 with asm-2.0. If *I* do I get always a lot of NoClassDefFoundError exceptions. They do not happen if you run it with asm-1.x and another indication is, that cglib-nodeps-2.1_2 contain the asm-1.x sources with a different package name! > cglib 2.1_2 should depend on asm 1.5.3, not 2.0 > --- > > Key: MEV-66 > URL: http://jira.codehaus.org/browse/MEV-66 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Ralph Poellath > > > cglib 2.1_2 has a dependency on asm 2.0, with which it is incompatible. > A mailing list discussion on the subject starts at > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112498159906141&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MEV-66) cglib 2.1_2 should depend on asm 1.5.3, not 2.0
[ http://jira.codehaus.org/browse/MEV-66?page=comments#action_45391 ] Ralph Poellath commented on MEV-66: --- I contacted a cglib team member, and he said that cglib 2.1_2 in fact does depend on asm 2.0 (the dependencies listed on the cglib website are outdated), and is of course compatible. I assume this issue should be closed. > cglib 2.1_2 should depend on asm 1.5.3, not 2.0 > --- > > Key: MEV-66 > URL: http://jira.codehaus.org/browse/MEV-66 > Project: Maven Evangelism > Type: Bug > Components: Dependencies > Reporter: Ralph Poellath > > > cglib 2.1_2 has a dependency on asm 2.0, with which it is incompatible. > A mailing list discussion on the subject starts at > http://marc.theaimsgroup.com/?l=turbine-maven-user&m=112498159906141&w=2 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Retrieving test dependencies in junit tests?
On Mon, Aug 29, 2005 at 11:25:45AM +0200, Vincent Massol wrote:
[snip]
> > That said, we are currently setting and using the system property
> > ${maven.repo.local} in unit tests for modello. I'd considered that an
> > "undocumented" feature (as in deliberately undocument, unlike most of
> > the features which we intend to document :)
>
> I don't understand why you mention modello. If you're setting the property
> in the model unit tests then how do you get the value in the first place?
>
> I've tried doing a System.getProperty( "maven.repo.local" ) in my unit test
> and it returns null. So I'm not sure it is set anywhere in m2.
>
> Is the local repo available as property in the POM? If so, I could use it
> and pass it to surefire using a system property?
I'm pretty sure that he was refering to the Modello build itself where we
generate source code and use the Plexus compilers to compile the generated
sources and test them[1]. Now I just realized that we're not doing that
anymore, but I think we used to set that property there.
Anyway, the Modello build show how we're using the local repository and
the Maven components to get access to artifacts in the repository.
[1]:
http://svn.modello.codehaus.org/trunk/modello/modello-test/src/main/java/org/codehaus/modello/AbstractModelloGeneratorTest.java?rev=430&view=auto
[snip]
--
Trygve
signature.asc
Description: Digital signature
RE: [m2] Retrieving test dependencies in junit tests?
> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: lundi 29 août 2005 03:53
> To: Maven Developers List
> Subject: Re: [m2] Retrieving test dependencies in junit tests?
>
> We had an open issue for this and decided to push it off for now. In our
> use case, there isn't really a good way for m2 to propogate information
> to JUnit without some intervening tool library, or system properties
> which are obviously limited.
>
> The problem with knowing the local repository location is that you must
> also know the path structure. While I don't envisage this changing from
> the new format any time soon it'd be good to be able to have that freedom.
>
> The preferred way would be to use ${localRepository} in a plugin and get
> localRepository.pathOf( artifact ).
I find it a bit awkward to have to develop a plugin and to host it alongside
project sources. Actually I've never seen this done so far probably for the
reason that anytime there was a need it found its way into m2 proper.
> That said, we are currently setting and using the system property
> ${maven.repo.local} in unit tests for modello. I'd considered that an
> "undocumented" feature (as in deliberately undocument, unlike most of
> the features which we intend to document :)
I don't understand why you mention modello. If you're setting the property
in the model unit tests then how do you get the value in the first place?
I've tried doing a System.getProperty( "maven.repo.local" ) in my unit test
and it returns null. So I'm not sure it is set anywhere in m2.
Is the local repo available as property in the POM? If so, I could use it
and pass it to surefire using a system property?
Thanks
-Vincent
> Vincent Massol wrote:
>
> >Hi,
> >
> >I'm continuing my quest to convert the m1 Cargo build into m2. Thanks to
> >John and his implementation for inheriting properties I have now reached
> the
> >next level.
> >
> >The Cargo functional test subprojects depend on some other subprojects
> which
> >produce J2EE modules (WAR, EAR, etc). Those are used for testing
> deployment
> >to a container.
> >
> >Thus, I need to get the file path of those dependencies from within a
> JUnit
> >TestCase class. How can I implement this?
> >
> >In m1, the way I had implemented it was a bit hacky:
> >- There was a property: cargo.testdata.dir =
> >${maven.repo.local}/${pom.groupId}
> >- The path to the J2EE module in the local repository was computed within
> >the TestCase
> >
> >Is there a property pointing to the local repo location that I could use
> in
> >the pom.xml file (same as ${maven.repo.local} is used in m1)?
> >
> >Obviously I'd rather not have to write a plugin for such a use case... I
> >think there's a potential need to gather all kind of information about
> the
> >POM in a JUnit TestCase and it might be interesting to implement this in
> a
> >generic way. WDYT?
> >
> >Thanks
> >-Vincent
___
Appel audio GRATUIT partout dans le monde avec le nouveau Yahoo! Messenger
Téléchargez cette version sur http://fr.messenger.yahoo.com
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-720) short commandline options are not parsed
[ http://jira.codehaus.org/browse/MNG-720?page=comments#action_45390 ] Brett Porter commented on MNG-720: -- because it is superseded by an alternative solution. I didn't know this bug was here when I filed it... > short commandline options are not parsed > > > Key: MNG-720 > URL: http://jira.codehaus.org/browse/MNG-720 > Project: Maven 2 > Type: Bug > Components: maven-core > Versions: 2.0-beta-1 > Reporter: Kenney Westerhof > Assignee: Brett Porter > Priority: Minor > > > The short commandline options displayed in the usage of m2 --help don't get > parsed: > m2 -npl install > Unable to parse command line options: Unrecognized option: -n > usage: maven [options] [goal [goal2 [goal3] ...]] > I've checked commons-cli and there's a fix for this in cvs/svn: > http://cvs.apache.org/viewcvs.cgi/jakarta-commons/cli/src/java/org/apache/commons/cli/PosixParser.java > see version 1.16 comments. > I've tried bumping commons-cli to 1.0, but this fix apparently isn't in there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (CONTINUUM-298) Upgrade to JPOX 1.1-beta-4
Upgrade to JPOX 1.1-beta-4 -- Key: CONTINUUM-298 URL: http://jira.codehaus.org/browse/CONTINUUM-298 Project: Continuum Type: Task Components: continuum-core Reporter: Trygve Laugstol Fix For: 1.0-alpha-4 -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
Re: Complex single field configuration for mojo
oh mine!! you are my hero!! Big thanks -Dan On 8/29/05, Kenney Westerhof <[EMAIL PROTECTED]> wrote: > On Mon, 29 Aug 2005, dan tran wrote: > > > Hello, the maven-native-plugin needs this configuration > > > > > > > > dir1 > > > > filename1.c > > filename2.cpp > > > > > > > > dir2 > > > > filename3.c > > filename4.c > > > > > > > > > > dir3 > > > > > > > > > > > > How do I implement this using one mojo field? a pointer to some > > similar source is greatly appreaciated. > > Each tag corresponds to a class. Check for instante maven-jar-plugin. > > Here's how you do it: > > - Create a 'Source.java' in the same dir as your mojo; > - Make a field: >/** > * @parameter > */ >private Source [] sources; > (usually 'List' instead of 'Source []' is preferred by others; doing it > like this doesn't require you to have 'Source' in the same package as the > mojo, or even to have it caled 'Source'.). > > Your Source.java has 1 field 'private String dir;' (no @parameter > required, it's only for Mojo's, but you knew that, right?), > and a 'private String [] filenames;' (Again, if you want to use List, > you would have to change the config to: > > >foo > ). > > I'll make some documentation on this for on the maven site (soon!) :) > > HTH, > >Kenney > > > > Thanks > > > > -Dan > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > -- > Kenney Westerhof > http://www.neonics.com > GPG public key: http://www.gods.nl/~forge/kenneyw.key > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Complex single field configuration for mojo
On Mon, 29 Aug 2005, dan tran wrote: > Hello, the maven-native-plugin needs this configuration > > > > dir1 > > filename1.c > filename2.cpp > > > > dir2 > > filename3.c > filename4.c > > > > > dir3 > > > > > > How do I implement this using one mojo field? a pointer to some > similar source is greatly appreaciated. Each tag corresponds to a class. Check for instante maven-jar-plugin. Here's how you do it: - Create a 'Source.java' in the same dir as your mojo; - Make a field: /** * @parameter */ private Source [] sources; (usually 'List' instead of 'Source []' is preferred by others; doing it like this doesn't require you to have 'Source' in the same package as the mojo, or even to have it caled 'Source'.). Your Source.java has 1 field 'private String dir;' (no @parameter required, it's only for Mojo's, but you knew that, right?), and a 'private String [] filenames;' (Again, if you want to use List, you would have to change the config to: foo ). I'll make some documentation on this for on the maven site (soon!) :) HTH, Kenney > > Thanks > > -Dan > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Kenney Westerhof http://www.neonics.com GPG public key: http://www.gods.nl/~forge/kenneyw.key - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Complex single field configuration for mojo
Hello, the maven-native-plugin needs this configuration dir1 filename1.c filename2.cpp dir2 filename3.c filename4.c dir3 How do I implement this using one mojo field? a pointer to some similar source is greatly appreaciated. Thanks -Dan - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-720) short commandline options are not parsed
[ http://jira.codehaus.org/browse/MNG-720?page=comments#action_45387 ] Kenney Westerhof commented on MNG-720: -- Why is this set to "won't fix" ? I can understand that upgrading commons-cli is a problem, but then at least the short options that don't work (those with more than one letter) should disappear from the help, or other letters should be assigned. I don't think it's a good idea to release something where you know the first thing people try, (m2 --help), already contains errors. > short commandline options are not parsed > > > Key: MNG-720 > URL: http://jira.codehaus.org/browse/MNG-720 > Project: Maven 2 > Type: Bug > Components: maven-core > Versions: 2.0-beta-1 > Reporter: Kenney Westerhof > Assignee: Brett Porter > Priority: Minor > > > The short commandline options displayed in the usage of m2 --help don't get > parsed: > m2 -npl install > Unable to parse command line options: Unrecognized option: -n > usage: maven [options] [goal [goal2 [goal3] ...]] > I've checked commons-cli and there's a fix for this in cvs/svn: > http://cvs.apache.org/viewcvs.cgi/jakarta-commons/cli/src/java/org/apache/commons/cli/PosixParser.java > see version 1.16 comments. > I've tried bumping commons-cli to 1.0, but this fix apparently isn't in there. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Created: (MPXDOC-161) Tabbed browsing for multiprojects (this change involves both the multiproject plugin and xdoc)
Tabbed browsing for multiprojects (this change involves both the multiproject plugin and xdoc) -- Key: MPXDOC-161 URL: http://jira.codehaus.org/browse/MPXDOC-161 Project: maven-xdoc-plugin Type: New Feature Versions: 1.9.1 Reporter: Ignacio G. Mac Dowell Attachments: tabbed.jpg Currently only aggregate navigation is possible on the top level project. It would be nice to be able to generate tabbed browsing. I have successfully done this with only a few changes to both plugins. I have attached a screenshot to see the benefits. If this sounds interesting I'll send the patch. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
