svn commit: r263840 - in /maven/maven-1/plugins/tags/MAVEN_EJB_1_7_1: ./ project.xml xdocs/changes.xml
Author: vmassol Date: Sat Aug 27 23:56:34 2005 New Revision: 263840 URL: http://svn.apache.org/viewcvs?rev=263840&view=rev Log: [maven-scm] copy for tag MAVEN_EJB_1_7_1 Added: maven/maven-1/plugins/tags/MAVEN_EJB_1_7_1/ - copied from r263837, maven/maven-1/plugins/trunk/ejb/ maven/maven-1/plugins/tags/MAVEN_EJB_1_7_1/project.xml - copied unchanged from r263839, maven/maven-1/plugins/trunk/ejb/project.xml maven/maven-1/plugins/tags/MAVEN_EJB_1_7_1/xdocs/changes.xml - copied unchanged from r263839, maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r263839 - in /maven/maven-1/plugins/trunk/ejb: project.xml xdocs/changes.xml
Author: vmassol Date: Sat Aug 27 23:56:19 2005 New Revision: 263839 URL: http://svn.apache.org/viewcvs?rev=263839&view=rev Log: [maven-scm-plugin] prepare release 1.7.1 Modified: maven/maven-1/plugins/trunk/ejb/project.xml maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Modified: maven/maven-1/plugins/trunk/ejb/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/project.xml?rev=263839&r1=263838&r2=263839&view=diff == --- maven/maven-1/plugins/trunk/ejb/project.xml (original) +++ maven/maven-1/plugins/trunk/ejb/project.xml Sat Aug 27 23:56:19 2005 @@ -22,7 +22,7 @@ 3 maven-ejb-plugin Maven EJB Plugin - 1.7.1-SNAPSHOT + 1.7.1 EJB Plugin for Maven EJB Plugin for Maven http://maven.apache.org/reference/plugins/ejb/ @@ -59,6 +59,11 @@ 1.7 MAVEN_EJB_1_7 + + 1.7.1 + 1.7.1 + MAVEN_EJB_1_7_1 + @@ -89,7 +94,7 @@ - HÃÆÃÂ¥vard BjÃÆÃÂ¥stad + HÃÆÃâÃâÃÂ¥vard BjÃÆÃâÃâÃÂ¥stad Modified: maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml?rev=263839&r1=263838&r2=263839&view=diff == --- maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Sat Aug 27 23:56:19 2005 @@ -23,11 +23,8 @@ Nathan Coast - - -Update dependency to Maven Model v3.0.0 final (it was previously depending -on 3.0.0 SNAPSHOT). - + + Update dependency to Maven Model v3.0.0 final (it was previously depending on 3.0.0 SNAPSHOT). By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common. @@ -40,7 +37,7 @@ ejb:deploy). Previous goals dedicated to ejb client have been deprecated. There is a new property maven.ejb.client.generatewhich decides whether or not to generate the ejb client jar. It defaults to true. - Added new EJB type handler that supports + Added new EJB type handler that supports ejband ejb-clienttypes. This fixes the bug with ejb:install/deploy-clientnot uploading the client jar. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r263838 - /maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml
Author: vmassol Date: Sat Aug 27 23:47:11 2005 New Revision: 263838 URL: http://svn.apache.org/viewcvs?rev=263838&view=rev Log: Added a change matching Brett's fix: upgrade to Maven Model 3.0.0 final. Modified: maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Modified: maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml?rev=263838&r1=263837&r2=263838&view=diff == --- maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Sat Aug 27 23:47:11 2005 @@ -2,7 +2,7 @@
[jira] Updated: (MNG-800) Many duplicate entries in ~/.m2/plugin-registry.xml
[ http://jira.codehaus.org/browse/MNG-800?page=all ] Brett Porter updated MNG-800: - Fix Version: (was: 2.0-beta-1) 2.0-beta-2 > Many duplicate entries in ~/.m2/plugin-registry.xml > > > Key: MNG-800 > URL: http://jira.codehaus.org/browse/MNG-800 > Project: Maven 2 > Type: Bug > Components: maven-plugin-descriptor > Versions: 2.0-beta-1 > Environment: xp, rehdat > Reporter: Dan Tran > Fix For: 2.0-beta-2 > > > I see many duplicate entries in plugin-registry.xml and it is growing -- 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-800) Many duplicate entries in ~/.m2/plugin-registry.xml
Many duplicate entries in ~/.m2/plugin-registry.xml Key: MNG-800 URL: http://jira.codehaus.org/browse/MNG-800 Project: Maven 2 Type: Bug Components: maven-plugin-descriptor Versions: 2.0-beta-1 Environment: xp, rehdat Reporter: Dan Tran Fix For: 2.0-beta-1 I see many duplicate entries in plugin-registry.xml and it is growing -- 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: r263810 - in /maven/maven-1/plugins/trunk/ejb: project.properties project.xml
Author: brett
Date: Sat Aug 27 20:50:50 2005
New Revision: 263810
URL: http://svn.apache.org/viewcvs?rev=263810&view=rev
Log:
fix the m1.1 build
Modified:
maven/maven-1/plugins/trunk/ejb/project.properties
maven/maven-1/plugins/trunk/ejb/project.xml
Modified: maven/maven-1/plugins/trunk/ejb/project.properties
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/project.properties?rev=263810&r1=263809&r2=263810&view=diff
==
--- maven/maven-1/plugins/trunk/ejb/project.properties (original)
+++ maven/maven-1/plugins/trunk/ejb/project.properties Sat Aug 27 20:50:50 2005
@@ -17,3 +17,6 @@
# ---
# P R O J E C T P R O P E R T I E S
# ---
+
+maven.jar.override=on
+maven.jar.maven=${maven.home}/lib/maven.jar
Modified: maven/maven-1/plugins/trunk/ejb/project.xml
URL:
http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/project.xml?rev=263810&r1=263809&r2=263810&view=diff
==
--- maven/maven-1/plugins/trunk/ejb/project.xml (original)
+++ maven/maven-1/plugins/trunk/ejb/project.xml Sat Aug 27 20:50:50 2005
@@ -22,7 +22,7 @@
3
maven-ejb-plugin
Maven EJB Plugin
- 1.7
+ 1.7.1-SNAPSHOT
EJB Plugin for Maven
EJB Plugin for Maven
http://maven.apache.org/reference/plugins/ejb/
@@ -112,7 +112,7 @@
maven
maven-model
- 3.0.0-SNAPSHOT
+ 3.0.0
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Closed: (MNG-799) CLI equivalent of @requiresDependencyResolution
[ http://jira.codehaus.org/browse/MNG-799?page=all ] Brett Porter closed MNG-799: Assign To: Brett Porter Resolution: Duplicate > CLI equivalent of @requiresDependencyResolution > --- > > Key: MNG-799 > URL: http://jira.codehaus.org/browse/MNG-799 > Project: Maven 2 > Type: Improvement > Components: maven-core > Versions: 2.0-beta-1 > Reporter: Mark Hobson > Assignee: Brett Porter > Priority: Minor > > > Add a command-line equivalent of the @requiresDependencyResolution MOJO > annotation - i.e. something like > "m2 -d compile" to resolve all compile-scoped dependencies. -- 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] Sun Aug 28 00:30:00 GMT 2005
Distribution: http://maven.zones.apache.org/~continuum/builds/continuum-20050828.003000.tar.gz Log: http://maven.zones.apache.org/~continuum/logs/continuum-build-log-20050828.003000.txt
[jira] Commented: (MNG-799) CLI equivalent of @requiresDependencyResolution
[ http://jira.codehaus.org/browse/MNG-799?page=comments#action_45351 ] Brett Porter commented on MNG-799: -- this would need to cover all plugins to allow you to go offline > CLI equivalent of @requiresDependencyResolution > --- > > Key: MNG-799 > URL: http://jira.codehaus.org/browse/MNG-799 > Project: Maven 2 > Type: Improvement > Components: maven-core > Versions: 2.0-beta-1 > Reporter: Mark Hobson > Priority: Minor > > > Add a command-line equivalent of the @requiresDependencyResolution MOJO > annotation - i.e. something like > "m2 -d compile" to resolve all compile-scoped dependencies. -- 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]
[maven2 build - SUCCESS - checkout] Sun Aug 28 00:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050828.001500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050828.001500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN Build Error
Ok, this is quite strange. As I said with the ci script - it does clean builds every day and is going along ok. What settings.xml do you have? Any mirrors, proxies, etc? Any local changes to the source code? Did you end up cleaning out the repository? Did it help? - Brett Allison, Bob wrote: >Using the bootstrap script is the only way I know to get a build. > >-Original Message- >From: Brett Porter [mailto:[EMAIL PROTECTED] >Sent: Saturday, August 27, 2005 08:00 >To: Maven Developers List >Subject: Re: SVN Build Error > > >How are you attempting to build this? It looks like you are using old >code with new code - are you using the bootstrap? > >- Brett > >Allison, Bob wrote: > > > >>Tried it again before cleaning out the repository and got: >> >> >> >> > > >- >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] > > > > - 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_45350 ]
Mark Hobson commented on MNG-785:
-
I've javadoc'd and licenced the code - see maven-tomcat-plugin.tar.gz. I
wasn't sure whether the plugin should be in the apache or codehaus package
structure (the mojo.codehaus plugins seem to be a mixture of both), so I left
it in the apache package. Let me know if I've missed anything.
> 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] Updated: (MNG-785) m2 tomcat plugin
[ http://jira.codehaus.org/browse/MNG-785?page=all ]
Mark Hobson updated MNG-785:
Attachment: maven-tomcat-plugin.tar.gz
mojo.codehaus.org submission
> 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: (MNG-799) CLI equivalent of @requiresDependencyResolution
CLI equivalent of @requiresDependencyResolution --- Key: MNG-799 URL: http://jira.codehaus.org/browse/MNG-799 Project: Maven 2 Type: Improvement Components: maven-core Versions: 2.0-beta-1 Reporter: Mark Hobson Priority: Minor Add a command-line equivalent of the @requiresDependencyResolution MOJO annotation - i.e. something like "m2 -d compile" to resolve all compile-scoped dependencies. -- 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]
[maven2 build - SUCCESS - update] Sat Aug 27 18:15:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050827.181500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.181500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r240444 - /maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
Author: vsiveton
Date: Sat Aug 27 11:16:19 2005
New Revision: 240444
URL: http://svn.apache.org/viewcvs?rev=240444&view=rev
Log:
Cleaning up the code a bit: replace static array of all reports file name
generated by Maven by a list (more dynamic); the first token in the locales
variable is the default locale (set in the VM); create
createDuplicateExceptionMsg() to handle the exception msg when some files are
duplicated; move code to generate reports in a new method called
generateReportsPages(); improve logging.
Modified:
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
Modified:
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java?rev=240444&r1=240443&r2=240444&view=diff
==
---
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
(original)
+++
maven/components/trunk/maven-plugins/maven-site-plugin/src/main/java/org/apache/maven/doxia/DoxiaMojo.java
Sat Aug 27 11:16:19 2005
@@ -77,10 +77,9 @@
private static final String DEFAULT_TEMPLATE = RESOURCE_DIR +
"/maven-site.vm";
/**
- * OutputName of all project info report files generated by Maven
+ * OutputName of all reports files generated by Maven
*/
-private static final String[] PROJECT_INFO_FILES = new
String[]{"integration", "dependencies", "issue-tracking",
-"license", "mail-lists", "source-repository", "team-list"};
+private static List generatedReportsFileName = new ArrayList();
/**
* Patterns which should be excluded by default.
@@ -160,7 +159,7 @@
* default-value="ISO-8859-1"
*/
private String outputEncoding;
-
+
/**
* @parameter
expression="${component.org.codehaus.plexus.siterenderer.Renderer}"
* @required
@@ -259,14 +258,19 @@
}
else
{
+// The first token is the default locale
StringTokenizer st = new StringTokenizer( locales, "," );
while ( st.hasMoreTokens() )
{
localesList.add( new Locale( st.nextToken().trim() ) );
}
+
+defaultLocale = (Locale) localesList.get( 0 );
}
+Locale.setDefault( defaultLocale );
+
for ( Iterator iterator = localesList.iterator();
iterator.hasNext(); )
{
Locale locale = (Locale) iterator.next();
@@ -279,84 +283,18 @@
localeOutputDirectory.mkdirs();
}
-//Generate reports
-if ( reports != null )
-{
-for ( Iterator j = reports.iterator(); j.hasNext(); )
-{
-MavenReport report = (MavenReport) j.next();
-
-getLog().info( "Generate \"" + report.getName( locale
) + "\" report." );
-
-report.setReportOutputDirectory( localeOutputDirectory
);
-
-String outputFileName = report.getOutputName() +
".html";
-
-SiteRendererSink sink = siteRenderer.createSink( new
File( siteDirectory ), outputFileName,
-
getSiteDescriptor( reports, locale ) );
-
-report.generate( sink, locale );
-
-if ( !report.isExternalReport() )
-{
-File outputFile = new File( localeOutputDirectory,
outputFileName );
-
-if ( !outputFile.getParentFile().exists() )
-{
-outputFile.getParentFile().mkdirs();
-}
-
-siteRenderer.generateDocument( new
OutputStreamWriter( new FileOutputStream( outputFile ),
-
outputEncoding ), template,
- attributes, sink,
locale );
-}
-}
-}
-
-//Generate overview pages
-if ( projectInfos.size() > 0 )
-{
-try
-{
-generateProjectInfoPage( getSiteDescriptor( reports,
locale ), locale );
-}
-catch ( Exception e )
-{
-throw new MojoExecutionException( "An error is
occurred in project info page generation.", e );
-}
-}
-
-i
[jira] Commented: (MNG-785) m2 tomcat plugin
[ http://jira.codehaus.org/browse/MNG-785?page=comments#action_45347 ]
Trygve Laugstol commented on MNG-785:
-
Basically make a source tarball with license and the whole shebang and we'll
commit it in the mojo sandbox. You can keep on submitting patches on the plugin
and if the code is the way we like it and you're showing comittment to
maintaining the plugin we might give you commit.
> 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.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_45346 ]
Mark Hobson commented on MNG-785:
-
Cheers for the feedback Trygve & Vincent. I've mailed the Cargo dev list to
start discussing how we could incorporate this code into a generic container
Cargo m2 plugin.
In the meantime I'm happy to move this code into mojo.codehaus.org for people
to start using immediately - my company has a strong need for the Tomcat plugin
and it makes sense to centralise it somewhere rather than keeping it in-house.
How would I proceed to submit this code?
> 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.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]
RE: SVN Build Error
Using the bootstrap script is the only way I know to get a build. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Saturday, August 27, 2005 08:00 To: Maven Developers List Subject: Re: SVN Build Error How are you attempting to build this? It looks like you are using old code with new code - are you using the bootstrap? - Brett Allison, Bob wrote: >Tried it again before cleaning out the repository and got: > > - 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: [M2] How to turn off transitive dependencies?
Brett Porter wrote: > Carsten Ziegeler wrote: > > >>1) Avalon framework. Up to version 4.1.0 (or something) Avalon had one >>big jar: the avalon framework. Then starting with 4.1.1 they splitt this >>into two jar files: api and impl. But for convenience they provide both >>versions, so for example, you have >> >> > > Yep, I understand this is the case here. We're actually planning a > "supercedes" attribute in a future version so that both api and impl can > declare that they shold block an earlier version of just "framework". > Hmm, ok, this works for new releases; but I'm wondering if really all old poms will be converted and corrected. > > Absolutely - we've got the solutions in there in the cases where they > are needed, I'd just advocate considering your position first and using > them as a last resort. I think this is especially important for projects > like Cocoon where you are depended upon by lots of projects, as the > quality of your POMs affects everyone else. For example, if you block > out dependencies you think are optional but which aren't under certain > circumstances then that will affect other projects. > :) Yes, Cocoon depends on more than 130 jars; I'm trying to migrate the core of Cocoon to m2 and the core uses only about 40 jars and we are affected by several "wrong" poms. It will take ages to correct them all. As we are currently using Ant to build Cocoon, today we know exactly which libs are requried in what version - and of course Cocoon runs fine :). With m2 we loose this power. Now, don't get me wrong I really like this transitive dependency handling and it will be a great improvement, but I don't get Cocoon running just because of this :( - and we all agree that poms can always be "wrong" in one way or the other. > Anyway, I hope we've got everything necessary to help you along with this. Hmm, so what can I do today? We currently have the three problems described (avalon, servletapi and ant). Thanks Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Sat Aug 27 15:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050827.154500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.154500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-788) Proposal for improved resource filtering
[ http://jira.codehaus.org/browse/MNG-788?page=comments#action_45345 ] Carsten Ziegeler commented on MNG-788: -- Sigh, and I thought this topic was easy... Anyway, it seems that we all agree to have a filtering "instruction" for a resource which turns on filtering. So what about just adding the simple element to the resource section. If the element is available the resources are filtered, if not they are not filtered. We could do this for beta-1 and can then think about how to add more instructions, either the way Brett wants it, with specifying the properties file or any other way. BUT PLEASE, let's make it configurable NOW if a resource should be filtered or not. > Proposal for improved resource filtering > > > Key: MNG-788 > URL: http://jira.codehaus.org/browse/MNG-788 > Project: Maven 2 > Type: Improvement > Components: maven-plugins > Versions: 2.0-beta-1 > Reporter: Carsten Ziegeler > Fix For: 2.0-beta-2 > > > The current resource filtering has to be configured at the resource plugin > configuration. This issue is about making resource filtering more > user-friendly. > There are the following requirements: > 1) being able to split resources up into two groups: the filtered-on-copy >group and the 'just-copy' group. > 2) being able to specify multiple properties files / having a default file > so users can override. Much like project.properties/build.properties > in maven1. > 3) being able to specify different filter properties using profiles > The last item 3) is already working, so this is about 1) and 2). > What about adding the following XML to the resource section of the POM: > > > > > And this configuration to the resource plugin > > > src/build.properties.sample > failOnError="false">src/build.properties > > > From the following list a) and b) address item 1) while c) addresses item 2): > a) As soon as a filtering section is available on a resource, it is filtered. > b) Usually you have in a single resource directory resources that you want to > filter and resources that shouldn't be filtered like images etc. One solution > to address this is to specify two resource sets in the POM with different > include and exlucde filters and turn on/off filtering accordingly. > I think a more elegant way is to say, this is my resource set and filter only > these files in this resource set. That's why I added the filterIncludes and > filterExcludes section. We can also define default filterExcludes like images > etc. On the one hand this is imho a more natural way of defining filtering > and on the other hand, this should increase performance. The resource tree > has only to be scanned once. With two resources, the tree is scanned twice. > Especially if you have big resource trees (e.g. for webapps) this should > increase performance noticeably. > c) You can specify several property files at the resource plugin. This files > are read in the order of appearance and if a token is defined twice, the last > definition read wins. In addition you can set the failOnError flag on a > property file, so if this file is missing no error occurs. > I could imagine these optional additions: > 4) Defining the tokens in the pom so the plugin >could check which ones are missing and you have an overview of >all the configuration settings used in all the resource files >(the latter being more important). >So, we could add this XML to the filtering section in the POM: > > tokenname > anothertokenname > > If the section is missing all tokens are replaced by default. > 5) Define properties directly without a property file. >We could add this to the resource plugin configuration: > > > aToken > someValue > > ... > -- 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: (MNG-717) dependency doesn't allow dependencyManagement to provide scope
[ http://jira.codehaus.org/browse/MNG-717?page=all ] John Casey closed MNG-717: -- Resolution: Fixed > dependency doesn't allow dependencyManagement to provide scope > -- > > Key: MNG-717 > URL: http://jira.codehaus.org/browse/MNG-717 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Reporter: Brett Porter > Assignee: John Casey > Fix For: 2.0-beta-1 > > Original Estimate: 3 hours >Time Spent: 2 hours > Remaining: 0 minutes > > By design, DependencyManagement values are only used if the local POM doesn't > provide values. In this way, if DependencyManagement provides a scope == > 'test' for junit, and the local POM doesn't specify a scope for junit, junit > should have the scope 'test' assigned to it when the depMgmt is injected. > HOWEVER, since the default value for Dependency.scope appears to be 'compile' > it always has a value, and the DependencyManagement value can never take > effect. > The solution is to allow a null scope in the Dependency, and apply the > default scope value later, either in the Artifact creation process, or during > transitive resolution. -- 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: r240428 - in /maven/components/trunk: maven-model/maven.mdo maven-project/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java maven-project/src/test/java/org/apache/maven/project/TestArtifactResolver.java
Author: jdcasey
Date: Sat Aug 27 08:44:48 2005
New Revision: 240428
URL: http://svn.apache.org/viewcvs?rev=240428&view=rev
Log:
Resolving: MNG-717
o Dependencies don't have a default scope value, to allow DependencyManagement
to set the scope if null...then, the metadata source sets the scope to
'compile' when it constructs the artifacts from deps that still have a null
scope. Oh, and it will at that point back-propagate the 'compile' scope to
these dependency instances, for later reference...
Modified:
maven/components/trunk/maven-model/maven.mdo
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java
maven/components/trunk/maven-project/src/test/java/org/apache/maven/project/TestArtifactResolver.java
Modified: maven/components/trunk/maven-model/maven.mdo
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-model/maven.mdo?rev=240428&r1=240427&r2=240428&view=diff
==
--- maven/components/trunk/maven-model/maven.mdo (original)
+++ maven/components/trunk/maven-model/maven.mdo Sat Aug 27 08:44:48 2005
@@ -1248,7 +1248,10 @@
http://maven.apache.org/maven2/dependencies.html";>Dependency
Mechanism.]]>
String
- compile
+
+
exclusions
Modified:
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java?rev=240428&r1=240427&r2=240428&view=diff
==
---
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java
(original)
+++
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/artifact/MavenMetadataSource.java
Sat Aug 27 08:44:48 2005
@@ -36,6 +36,7 @@
import org.apache.maven.project.MavenProjectBuilder;
import org.apache.maven.project.ProjectBuildingException;
import org.codehaus.plexus.logging.AbstractLogEnabled;
+import org.codehaus.plexus.util.StringUtils;
import java.util.ArrayList;
import java.util.Collections;
@@ -235,11 +236,20 @@
for ( Iterator i = dependencies.iterator(); i.hasNext(); )
{
Dependency d = (Dependency) i.next();
+
+String scope = d.getScope();
+
+if ( StringUtils.isEmpty( scope ) )
+{
+scope = Artifact.SCOPE_COMPILE;
+
+d.setScope( scope );
+}
VersionRange versionRange = VersionRange.createFromVersionSpec(
d.getVersion() );
Artifact artifact = artifactFactory.createDependencyArtifact(
d.getGroupId(), d.getArtifactId(),
versionRange, d.getType(), d.getClassifier(),
-
d.getScope(), inheritedScope );
+
scope, inheritedScope );
if ( artifact != null && ( dependencyFilter == null ||
dependencyFilter.include( artifact ) ) )
{
Modified:
maven/components/trunk/maven-project/src/test/java/org/apache/maven/project/TestArtifactResolver.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-project/src/test/java/org/apache/maven/project/TestArtifactResolver.java?rev=240428&r1=240427&r2=240428&view=diff
==
---
maven/components/trunk/maven-project/src/test/java/org/apache/maven/project/TestArtifactResolver.java
(original)
+++
maven/components/trunk/maven-project/src/test/java/org/apache/maven/project/TestArtifactResolver.java
Sat Aug 27 08:44:48 2005
@@ -38,6 +38,7 @@
import org.codehaus.plexus.context.ContextException;
import org.codehaus.plexus.personality.plexus.lifecycle.phase.Contextualizable;
import org.codehaus.plexus.util.IOUtil;
+import org.codehaus.plexus.util.StringUtils;
import org.codehaus.plexus.util.xml.pull.XmlPullParserException;
import java.io.File;
@@ -144,10 +145,19 @@
{
Dependency d = (Dependency) i.next();
+String scope = d.getScope();
+
+if ( StringUtils.isEmpty( scope ) )
+{
+scope = Artifact.SCOPE_COMPILE;
+
+d.setScope( scope );
+}
+
VersionRange versionRange =
VersionRange.createFromVersionSpec( d.getVersion() );
Artifact artifact = artifactFactory.createDependencyArtifact(
d.getGroupId(), d.getArtifactId(),
[jira] Updated: (MEV-72) relaxngDatatype-1.6
[ http://jira.codehaus.org/browse/MEV-72?page=all ] Adam Hardy updated MEV-72: -- Attachment: relaxngDatatype-1.6.pom > relaxngDatatype-1.6 > --- > > Key: MEV-72 > URL: http://jira.codehaus.org/browse/MEV-72 > Project: Maven Evangelism > Type: Improvement > Components: Invalid POM > Reporter: Adam Hardy > Attachments: relaxngDatatype-1.6.pom > > > This is provided by the JWSDP. The current one in > relaxngDatatype/relaxngDatatype/20020414 is out-of-date and uses the > deprecated directory naming scheme. -- 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] Updated: (MEV-71) jaxb-xjc-1.0.5
[ http://jira.codehaus.org/browse/MEV-71?page=all ] Adam Hardy updated MEV-71: -- Attachment: jaxb-xjc-1.0.5.pom > jaxb-xjc-1.0.5 > -- > > Key: MEV-71 > URL: http://jira.codehaus.org/browse/MEV-71 > Project: Maven Evangelism > Type: Improvement > Components: Missing POM > Reporter: Adam Hardy > Attachments: jaxb-xjc-1.0.5.pom > > > JAXB Java code generator for beans based on XML schemas -- 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] Updated: (MEV-70) jaxb-libs
[ http://jira.codehaus.org/browse/MEV-70?page=all ] Adam Hardy updated MEV-70: -- Attachment: jaxb-libs-1.0.5.pom > jaxb-libs > - > > Key: MEV-70 > URL: http://jira.codehaus.org/browse/MEV-70 > Project: Maven Evangelism > Type: Improvement > Components: Missing POM > Reporter: Adam Hardy > Attachments: jaxb-libs-1.0.5.pom > > > JAXB libraries -- 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] Updated: (MEV-69) jaxb-impl-1.0.5
[ http://jira.codehaus.org/browse/MEV-69?page=all ] Adam Hardy updated MEV-69: -- Attachment: jaxb-impl-1.0.5.pom > jaxb-impl-1.0.5 > --- > > Key: MEV-69 > URL: http://jira.codehaus.org/browse/MEV-69 > Project: Maven Evangelism > Type: Improvement > Components: Missing POM > Reporter: Adam Hardy > Attachments: jaxb-impl-1.0.5.pom > > -- 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]
[ANN] Maven EJB Plugin 1.7 released
We are pleased to announce the Maven EJB Plugin 1.7 release! http://maven.apache.org/reference/plugins/ejb/ EJB Plugin for Maven Changes in this version include: Fixed bugs: o Make the ejb creation work even if there are not sources. o Fixed default property values in the web site documentation. Issue: MPEJB-12. o EJB client jar can now be generated and deployed/installed automatically by the standard goals ( ejb, ejb:ejb, ejb:installand ejb:deploy). Previous goals dedicated to ejb client have been deprecated. There is a new property maven.ejb.client.generatewhich decides whether or not to generate the ejb client jar. It defaults to true. Issue: MPEJB-2. o Added new EJB type handler that supports ejband ejb-clienttypes. This fixes the bug with ejb:install/deploy-clientnot uploading the client jar. Issue: MPEJB-16. Thanks to H�¯�¿�½vard Bj�¯�¿�½stad. Changes: o By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common. To automatically install the plugin, type the following on a single line: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven, http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-ejb-plugin -Dversion=1.7 For a manual installation, you can download the plugin here: http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-ejb-plugin-1.7.jar Have fun! -The Maven EJB Plugin development team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r240422 - in /maven/maven-1/plugins/tags/MAVEN_EJB_1_7: ./ project.xml xdocs/changes.xml
Author: vmassol Date: Sat Aug 27 07:17:50 2005 New Revision: 240422 URL: http://svn.apache.org/viewcvs?rev=240422&view=rev Log: [maven-scm] copy for tag MAVEN_EJB_1_7 Added: maven/maven-1/plugins/tags/MAVEN_EJB_1_7/ - copied from r234453, maven/maven-1/plugins/trunk/ejb/ maven/maven-1/plugins/tags/MAVEN_EJB_1_7/project.xml - copied unchanged from r240421, maven/maven-1/plugins/trunk/ejb/project.xml maven/maven-1/plugins/tags/MAVEN_EJB_1_7/xdocs/changes.xml - copied unchanged from r240421, maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r240421 - in /maven/maven-1/plugins/trunk/ejb: project.xml xdocs/changes.xml
Author: vmassol Date: Sat Aug 27 07:17:36 2005 New Revision: 240421 URL: http://svn.apache.org/viewcvs?rev=240421&view=rev Log: [maven-scm-plugin] prepare release 1.7 Modified: maven/maven-1/plugins/trunk/ejb/project.xml maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Modified: maven/maven-1/plugins/trunk/ejb/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/project.xml?rev=240421&r1=240420&r2=240421&view=diff == --- maven/maven-1/plugins/trunk/ejb/project.xml (original) +++ maven/maven-1/plugins/trunk/ejb/project.xml Sat Aug 27 07:17:36 2005 @@ -17,13 +17,12 @@ * limitations under the License. */ --> - ../plugin-parent/project.xml 3 maven-ejb-plugin Maven EJB Plugin - 1.7-SNAPSHOT + 1.7 EJB Plugin for Maven EJB Plugin for Maven http://maven.apache.org/reference/plugins/ejb/ @@ -55,6 +54,11 @@ 1.6 MAVEN_EJB_1_6 + + 1.7 + 1.7 + MAVEN_EJB_1_7 + @@ -85,7 +89,7 @@ - HÃÂ¥vard BjÃÂ¥stad + HÃÆÃÂ¥vard BjÃÆÃÂ¥stad Modified: maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml?rev=240421&r1=240420&r2=240421&view=diff == --- maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml (original) +++ maven/maven-1/plugins/trunk/ejb/xdocs/changes.xml Sat Aug 27 07:17:36 2005 @@ -17,59 +17,41 @@ * limitations under the License. */ --> - Changes Nathan Coast - - -By default do not generate client EJB. I believe this is a more common -default that generating as generation of client EJBs is only required -for distributed apps which are not so common. - - -Make the ejb creation work even if there are not sources. - - -Fixed default property values in the web site documentation. - - -EJB client jar can now be generated and deployed/installed -automatically by the standard goals (ejb, ejb:ejb, -ejb:install and ejb:deploy). Previous goals -dedicated to ejb client have been deprecated. There is a new -property maven.ejb.client.generate which decides whether or -not to generate the ejb client jar. It defaults to true. - - -Added new EJB type handler that supports ejb and -ejb-client types. This fixes the bug with -ejb:install/deploy-client not uploading the client -jar. + + By default do not generate client EJB. I believe this is a more common default that generating as generation of client EJBs is only required for distributed apps which are not so common. + Make the ejb creation work even if there are not sources. + Fixed default property values in the web site documentation. + EJB client jar can now be generated and deployed/installed automatically by the standard goals ( +ejb, +ejb:ejb, +ejb:installand +ejb:deploy). Previous goals dedicated to ejb client have been deprecated. There is a new property +maven.ejb.client.generatewhich decides whether or not to generate the ejb client jar. It defaults to true. + + Added new EJB type handler that supports +ejband +ejb-clienttypes. This fixes the bug with +ejb:install/deploy-clientnot uploading the client jar. - -Added new maven.ejb.build.dir property that specifies the -location where the EJBs are generated. - - -Modified existing maven.ejb.final.name property (and -exposed it as a public property) so that it doesn't include the path -(the path is now provided by the new maven.ejb.build.dir -property). This allows aligning the WAR and EJB plugin properties. -Note: This is a breaking change for all those using the -maven.ejb.final.name property (which was not a public -property). + Added new +maven.ejb.build.dirproperty that specifies the location where the EJBs are generated. - -Made the maven.ejb.final.name property public as it is -required by several other plugins and before this change the only -way is for these plugins was to call the non-public -ejb:init goal. + Modified existing +maven.ejb.final.nameproperty (and exposed it as a public property) so that it doesn't include the path (the path is now provided by the new +maven.ejb.build.dirproperty). This allows aligning the WAR and EJB plugin properties. Note: This is a breaking change for all those using the +maven.ejb.final.nameproperty (which was not a public property). + + Made the +maven.e
[jira] Updated: (MPPDF-34) Problem Embedding Arial Font
[ http://jira.codehaus.org/browse/MPPDF-34?page=all ] Valerie Nyre updated MPPDF-34: -- Attachment: MavenIssue_MPPDF-34_CannotReproduce_FuturaNotEmbedded.zip In the attachment, a quick attempt to reproduce the problem (see the readme.txt) Summary: I cannot reproduce the problem. Embedding a base font like Arial, however, seems to make no sense. The other problem which I cannot solve is: My licensed Futura is not embedded - nor do I see any message informing me about the reason. My regards, Valerie > Problem Embedding Arial Font > > > Key: MPPDF-34 > URL: http://jira.codehaus.org/browse/MPPDF-34 > Project: maven-pdf-plugin > Type: Bug > Versions: 2.2 > Environment: Windows 2000, Maven 1.0.2, PDF-Plugin 2.2.1, JDK 1.4 > (j2sdk1.4.2_06) > Reporter: Valerie Nyre > Attachments: MavenIssue_MPPDF-34_CannotReproduce_FuturaNotEmbedded.zip > > > --- > What the TTF Reader says... > --- > > The TTFReader explicitly mentions that there are no restrictions to embedding > the font: > J:\MAAS\02WORK\02MAAS_WORK_MAVEN\NYRE_WORK>java -cp > I:\MAVENLOCALREPO\.maven\repository\fop\jars\fop-0.20.5.jar;I:\MAVENLOCALREPO\.maven\repository\avalon-framework\jars\avalon-framework-4.1.5.jar > org.apache.fop.fonts.apps.TTFReader -enc ansi > I:\MAVENLOCALREPO\.maven\cache\maven-pdf-plugin-2.2.1\plugin-resources\fonts\arial.ttf > > I:\MAVENLOCALREPO\.maven\cache\maven-pdf-plugin-2.2.1\plugin-resources\fonts\arial.xml > > TTF Reader v1.1.1 > Reading > I:\MAVENLOCALREPO\.maven\cache\maven-pdf-plugin-2.2.1\plugin-resources\fonts\arial.ttf... > Number of glyphs in font: 1296 > Creating xml font file... > Creating WinAnsi encoded metrics > Writing xml font file > I:\MAVENLOCALREPO\.maven\cache\maven-pdf-plugin-2.2.1\plugin-resources\fonts\arial.xml... > This font contains no embedding license restrictions > > --- > And yet the font is not embedded? > --- > Running the maven goal pdf, the last messages are issued: > > > [java] [ERROR] Failed to embed fontfile: > file:/I:/MAVENLOCALREPO/maasintern/NYRETEST/target/pdf/arial.ttf > [java] [ERROR] Failed to embed fontfile: > file:/I:/MAVENLOCALREPO/maasintern/NYRETEST/target/pdf/arial.ttf > --- > In my userconfig.xml > --- > > I have to repeat entries for the same fontmetrics file > Why this ? To suppress the messages that the font is not known. > I assume just because my styles use the same font with different weights: > embed-file="arial.ttf"> > > > embed-file="arial.ttf"> > > > embed-file="arialbi.ttf"> > > > embed-file="arialbd.ttf"> > > > embed-file="ariblk.ttf"> > > -- 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: r240420 - /maven/maven-1/plugins/trunk/ejb/project.xml
Author: vmassol Date: Sat Aug 27 07:05:26 2005 New Revision: 240420 URL: http://svn.apache.org/viewcvs?rev=240420&view=rev Log: MPEJB-20: Hopefully fix encoding that does not work with Maven 1.0.2. Thanks to Fredrik Vraalsen. Modified: maven/maven-1/plugins/trunk/ejb/project.xml Modified: maven/maven-1/plugins/trunk/ejb/project.xml URL: http://svn.apache.org/viewcvs/maven/maven-1/plugins/trunk/ejb/project.xml?rev=240420&r1=240419&r2=240420&view=diff == --- maven/maven-1/plugins/trunk/ejb/project.xml (original) +++ maven/maven-1/plugins/trunk/ejb/project.xml Sat Aug 27 07:05:26 2005 @@ -85,7 +85,7 @@ - Håvard Bjåstad + HÃÂ¥vard BjÃÂ¥stad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Sat Aug 27 13:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050827.13.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.13.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r240415 - /maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/metadata/SnapshotArtifactMetadata.java
Author: brett
Date: Sat Aug 27 06:00:33 2005
New Revision: 240415
URL: http://svn.apache.org/viewcvs?rev=240415&view=rev
Log:
trim metadata file
Modified:
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/metadata/SnapshotArtifactMetadata.java
Modified:
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/metadata/SnapshotArtifactMetadata.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/metadata/SnapshotArtifactMetadata.java?rev=240415&r1=240414&r2=240415&view=diff
==
---
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/metadata/SnapshotArtifactMetadata.java
(original)
+++
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/metadata/SnapshotArtifactMetadata.java
Sat Aug 27 06:00:33 2005
@@ -68,7 +68,7 @@
protected void setContent( String content )
{
-Matcher matcher = Artifact.VERSION_FILE_PATTERN.matcher( content );
+Matcher matcher = Artifact.VERSION_FILE_PATTERN.matcher(
content.trim() );
if ( matcher.matches() )
{
timestamp = matcher.group( 2 );
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r240414 - /maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java
Author: brett
Date: Sat Aug 27 05:48:12 2005
New Revision: 240414
URL: http://svn.apache.org/viewcvs?rev=240414&view=rev
Log:
use the correct repository for finding the original snapshot data
Modified:
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java
Modified:
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java?rev=240414&r1=240413&r2=240414&view=diff
==
---
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java
(original)
+++
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/deployer/DefaultArtifactDeployer.java
Sat Aug 27 05:48:12 2005
@@ -35,10 +35,12 @@
implements ArtifactDeployer
{
private WagonManager wagonManager;
-
+
private ArtifactTransformationManager transformationManager;
-/** @deprecated we want to use the artifact method only, and ensure
artifact.file is set correctly. */
+/**
+ * @deprecated we want to use the artifact method only, and ensure
artifact.file is set correctly.
+ */
public void deploy( String basedir, String finalName, Artifact artifact,
ArtifactRepository deploymentRepository,
ArtifactRepository localRepository )
throws ArtifactDeploymentException
@@ -54,7 +56,7 @@
{
try
{
-transformationManager.transformForDeployment( artifact,
localRepository );
+transformationManager.transformForDeployment( artifact,
deploymentRepository );
// Copy the original file to the new one if it was transformed
File artifactFile = new File( localRepository.getBasedir(),
localRepository.pathOf( artifact ) );
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: SVN Build Error
How are you attempting to build this? It looks like you are using old code with new code - are you using the bootstrap? - Brett Allison, Bob wrote: >Tried it again before cleaning out the repository and got: > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: SVN Build Error
Tried it again before cleaning out the repository and got: Downloading: http://repo1.maven.org/maven2/plugins/org/codehaus/modello/modello-plugi n-jpox/1.0-alpha-3/modello-plugin-jpox-1.0-alpha-3.jar [WARNING] Unable to get resource from repository http://repo1.maven.org/maven2/plugins Downloading: http://repo1.maven.org/maven2/org/codehaus/modello/modello-plugin-jpox/1 .0-alpha-3/modello-plugin-jpox-1.0-alpha-3.jar 11K downloaded [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Diagnosis: Error configuring plugin for execution of 'modello:xpp3-writer'. [INFO] [ERROR] Cause: org.apache.maven.plugin.MojoExecutionException: Error configuring plugin for execution of 'modello:xpp3-writer'. at org.apache.maven.plugin.DefaultPluginManager.executeMojo(Lorg.apache.mav en.project.MavenProject;Lorg.apache.maven.plugin.MojoExecution;Lorg.apac he.maven.execution.MavenSession;)V(DefaultPluginManager.java:342) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Ljava.u til.List;Lorg.apache.maven.execution.MavenSession;Lorg.apache.maven.proj ect.MavenProject;)V(DefaultLifecycleExecutor.java:478) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifec ycle(Ljava.lang.String;Lorg.apache.maven.execution.MavenSession;Ljava.ut il.Map;Lorg.apache.maven.project.MavenProject;)V(DefaultLifecycleExecuto r.java:451) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Ljava.la ng.String;Lorg.apache.maven.execution.MavenSession;Lorg.apache.maven.pro ject.MavenProject;)V(DefaultLifecycleExecutor.java:437) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments( Ljava.util.List;Lorg.apache.maven.execution.ReactorManager;Lorg.apache.m aven.execution.MavenSession;Lorg.apache.maven.project.MavenProject;Lorg. apache.maven.monitor.event.EventDispatcher;)V(DefaultLifecycleExecutor.j ava:273) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(Lorg.apache. maven.execution.MavenSession;Lorg.apache.maven.execution.ReactorManager; Lorg.apache.maven.monitor.event.EventDispatcher;)Lorg.apache.maven.execu tion.MavenExecutionResponse;(DefaultLifecycleExecutor.java:131) at org.apache.maven.DefaultMaven.execute(Lorg.apache.maven.execution.MavenE xecutionRequest;)Lorg.apache.maven.execution.MavenExecutionResponse;(Def aultMaven.java:186) at org.apache.maven.cli.MavenCli.main([Ljava.lang.String;Lorg.codehaus.clas sworlds.ClassWorld;)I(MavenCli.java:316) at jrockit.reflect.NativeMethodInvoker.invoke0(Ljava.lang.Object;ILjava.lan g.Object;[Ljava.lang.Object;)Ljava.lang.Object;(Unknown Source) at jrockit.reflect.NativeMethodInvoker.invoke(Ljava.lang.Object;[Ljava.lang .Object;)Ljava.lang.Object;(Unknown Source) at java.lang.reflect.Method.invoke(Ljava.lang.Object;[Ljava.lang.Object;I)L java.lang.Object;(Unknown Source) at org.codehaus.classworlds.Launcher.launchEnhanced([Ljava.lang.String;)V(L auncher.java:315) at org.codehaus.classworlds.Launcher.launch([Ljava.lang.String;)V(Launcher. java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode([Ljava.lang.String;)I (Launcher.java:430) at org.codehaus.classworlds.Launcher.main([Ljava.lang.String;)V(Launcher.ja va:375) Caused by: org.apache.maven.plugin.PluginConfigurationException: Cannot resolve plugin dependencies at org.apache.maven.plugin.DefaultPluginManager.ensurePluginContainerIsComp lete(Lorg.apache.maven.plugin.descriptor.PluginDescriptor;Lorg.codehaus. plexus.PlexusContainer;Lorg.apache.maven.project.MavenProject;Lorg.apach e.maven.execution.MavenSession;)V(DefaultPluginManager.java:581) at org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(Lorg.apac he.maven.plugin.descriptor.MojoDescriptor;Lorg.apache.maven.execution.Ma venSession;Lorg.codehaus.plexus.util.xml.Xpp3Dom;Lorg.apache.maven.proje ct.MavenProject;Z)Lorg.apache.maven.plugin.Mojo;(DefaultPluginManager.ja va:482) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(Lorg.apache.mav en.project.MavenProject;Lorg.apache.maven.plugin.MojoExecution;Lorg.apac he.maven.execution.MavenSession;)V(DefaultPluginManager.java:337) ... 14 more Caused by: org.apache.maven.artifact.resolver.ArtifactResolutionException: Error transferring file org.codehaus.modello:modello-plugin-jpox:1.0-alpha-3:jar from the specified remote repositories: http://snapshots.maven.codehaus.org/maven2/plugins, http://repo1.maven.org/maven2/plugins, http://repo1.maven.org/maven2 Path to dependency: 1) org.codehaus.modello:modello-maven-plugin:maven-plugin:1.0-alpha-3 2) org.codehaus.modello:modello-plugin-jpox:jar:1.0-alpha-3 at org.apache.maven.artifact.resolver.Defaul
[jira] Updated: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
[ http://jira.codehaus.org/browse/MNG-775?page=all ] Brett Porter updated MNG-775: - Assign To: (was: John Casey) Fix Version: (was: 2.0-beta-1) 2.0-beta-2 > Reissue of MNG-251: maven-archiver should be able to include the snapshot > version/build number > -- > > Key: MNG-775 > URL: http://jira.codehaus.org/browse/MNG-775 > Project: Maven 2 > Type: New Feature > Components: maven-archiver > Versions: 2.0-alpha-3 > Reporter: John Casey > Fix For: 2.0-beta-2 > > Original Estimate: 6 hours >Time Spent: 6 hours > Remaining: 0 minutes > > From MNG-251: > bit of a chicken and egg problem under the current arch. I want to include: > - the build number as a separate manifest entry > - the correct version in the manifest and META-INF/maven/pom.xml > However, the snapshot is only determined when the artifact is transformed for > install - which comes after package. > I think this may need to be a phase before package, or part of an existing > phase, or that packaging actually does the version assignment, and > install/deploy just utilises it. > More thinking required. -- 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]
[maven2 build - SUCCESS - update] Sat Aug 27 11:45:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050827.114500.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.114500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Reopened: (MNG-775) Reissue of MNG-251: maven-archiver should be able to include the snapshot version/build number
[ http://jira.codehaus.org/browse/MNG-775?page=all ] Brett Porter reopened MNG-775: -- rolled back. wasn't working. due to low priority, we'll leave this for later. > Reissue of MNG-251: maven-archiver should be able to include the snapshot > version/build number > -- > > Key: MNG-775 > URL: http://jira.codehaus.org/browse/MNG-775 > Project: Maven 2 > Type: New Feature > Components: maven-archiver > Versions: 2.0-alpha-3 > Reporter: John Casey > Assignee: John Casey > Fix For: 2.0-beta-1 > > Original Estimate: 6 hours >Time Spent: 6 hours > Remaining: 0 minutes > > From MNG-251: > bit of a chicken and egg problem under the current arch. I want to include: > - the build number as a separate manifest entry > - the correct version in the manifest and META-INF/maven/pom.xml > However, the snapshot is only determined when the artifact is transformed for > install - which comes after package. > I think this may need to be a phase before package, or part of an existing > phase, or that packaging actually does the version assignment, and > install/deploy just utilises it. > More thinking required. -- 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: r240405 - in /maven/components/trunk: maven-archiver/src/main/java/org/apache/maven/archiver/ maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/ maven-artifact/src/main/java/org/apache/maven/artifact/repository/metada...
Author: brett
Date: Sat Aug 27 04:42:30 2005
New Revision: 240405
URL: http://svn.apache.org/viewcvs?rev=240405&view=rev
Log:
repair snapshot build numbering (previous code makes it get stuck at 1).
Modified:
maven/components/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/DefaultArtifactTransformationManager.java
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/SnapshotTransformation.java
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/repository/metadata/RepositoryMetadata.java
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/transform/ArtifactTransformationManager.java
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/DefaultMavenProjectBuilder.java
maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/MavenProject.java
Modified:
maven/components/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java?rev=240405&r1=240404&r2=240405&view=diff
==
---
maven/components/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java
(original)
+++
maven/components/trunk/maven-archiver/src/main/java/org/apache/maven/archiver/MavenArchiver.java
Sat Aug 27 04:42:30 2005
@@ -63,6 +63,7 @@
Artifact projectArtifact = project.getArtifact();
+/* TODO: rethink this, it wasn't working
if ( projectArtifact.isSnapshot() )
{
Manifest.Attribute buildNumberAttr = new Manifest.Attribute(
"Build-Number", "" +
@@ -70,6 +71,7 @@
m.addConfiguredAttribute( buildNumberAttr );
}
+*/
if ( config.getPackageName() != null )
{
Manifest.Attribute packageAttr = new Manifest.Attribute(
"Package", config.getPackageName() );
@@ -231,7 +233,7 @@
if ( workingProject.getArtifact().isSnapshot() )
{
-workingProject.setVersion(
workingProject.getSnapshotDeploymentVersion() );
+workingProject.setVersion(
workingProject.getArtifact().getVersion() );
}
String groupId = workingProject.getGroupId();
Modified:
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/DefaultArtifactTransformationManager.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/DefaultArtifactTransformationManager.java?rev=240405&r1=240404&r2=240405&view=diff
==
---
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/DefaultArtifactTransformationManager.java
(original)
+++
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/DefaultArtifactTransformationManager.java
Sat Aug 27 04:42:30 2005
@@ -12,7 +12,7 @@
{
private List artifactTransformations;
-
+
private SnapshotTransformation snapshotTransformation;
public void transformForResolve( Artifact artifact, List
remoteRepositories, ArtifactRepository localRepository )
@@ -43,21 +43,6 @@
ArtifactTransformation transform = (ArtifactTransformation)
i.next();
transform.transformForDeployment( artifact, remoteRepository );
}
-}
-
-public String getSnapshotDeploymentTimestamp()
-{
-return snapshotTransformation.getDeploymentTimestamp();
-}
-
-public int getSnapshotDeploymentBuildNumber( Artifact artifact )
-{
-return snapshotTransformation.getDeploymentBuildNumber( artifact);
-}
-
-public String getSnapshotDeploymentVersion( Artifact snapshotArtifact )
-{
-return snapshotTransformation.getDeploymentVersion( snapshotArtifact );
}
}
Modified:
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/SnapshotTransformation.java
URL:
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/SnapshotTransformation.java?rev=240405&r1=240404&r2=240405&view=diff
==
---
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/SnapshotTransformation.java
(original)
+++
maven/components/trunk/maven-artifact-manager/src/main/java/org/apache/maven/artifact/transform/SnapshotTransformation.java
Sat Aug 27 04:42:30 2005
@@ -17,7 +17,6 @@
*/
import org.apache.maven.artifact.Artif
RE: SVN Build Error
My typo. 8-( The build that prompted that message was complaining about the xdoc module. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, August 26, 2005 17:59 To: Maven Developers List Subject: Re: SVN Build Error Can you confirm if there is a typo below? (xds vs xsd) If it's xds in the code, that'd explain it :) - Brett Allison, Bob wrote: >It has happened again... > >-Original Message- >From: Allison, Bob >Sent: Friday, August 26, 2005 07:04 >To: 'Maven Developers List' >Subject: SVN Build Error > > >I am trying to rebuild m2 from SVN updated this morning. > >When I run the bootstrap script, it dies while rebuilding the assembly >plugin because it is unable to download >http://repo1.maven.org/maven2/plugins/org/codehaus/modello/modello-plug i >n-xsd/1.0-alpha-3/modello-plugin-xds-1.0-alpha-3.jar > >Just above that, it complained about not being able to download a number >of modello POMs. > >It looks like the modello repository on maven.org got trashed. > >- >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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - SUCCESS - update] Sat Aug 27 11:00:00 GMT 2005
Distribution: http://maven.zones.apache.org/~maven/builds/m2-20050827.110001.tar.gz Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.110001.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 10:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.104500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 10:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.103000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 10:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.101500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 09:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.094500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 09:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.093000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 09:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.091500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 08:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.084500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 08:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.083000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 08:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.081500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Commented: (MNG-792) Can't ctrl-C m2 under cygwin
[ http://jira.codehaus.org/browse/MNG-792?page=comments#action_45330 ] Vincent Massol commented on MNG-792: FWIW ctrl-c also doesn't work for me in m2. I'm not running under cygwin but direclty under the dos prompt. This is quite annoying when you make a mistake and want to cancel the build. It's probably something in the .bat file but I haven't checked. > Can't ctrl-C m2 under cygwin > > > Key: MNG-792 > URL: http://jira.codehaus.org/browse/MNG-792 > Project: Maven 2 > Type: Bug > Versions: 2.0-beta-1 > Environment: Windows XP, Cygwin > Reporter: Mark Hobson > Assignee: Brett Porter > > > Under cygwin you can't ctrl-C to interrupt the process when running m2. This > used to work under 2.0-alpha-3. -- 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]
[maven2 build - FAILED - update] Sat Aug 27 08:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.08.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[jira] Updated: (MNG-639) examine impact of multiple repositories on metadata
[ http://jira.codehaus.org/browse/MNG-639?page=all ] Brett Porter updated MNG-639: - Remaining Estimate: 1 hour Original Estimate: 3600 > examine impact of multiple repositories on metadata > --- > > Key: MNG-639 > URL: http://jira.codehaus.org/browse/MNG-639 > Project: Maven 2 > Type: Bug > Components: maven-artifact > Reporter: Brett Porter > Assignee: Brett Porter > Priority: Critical > Fix For: 2.0-beta-1 > > Original Estimate: 1 hour > Remaining: 1 hour > > recently introduced metadata could be problematic when there is more than one > remote repository, as it is compared to only the single local repository copy: > - latest > - release > - plugins.xml -- 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]
[maven2 build - FAILED - update] Sat Aug 27 07:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.074500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 05:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.054500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [vote] Lukas Theussl as a maven plugins committer
> -Original Message- > From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] > Sent: jeudi 25 août 2005 23:52 > To: 'Maven Developers List' > Subject: [vote] Lukas Theussl as a maven plugins committer > > Hi all, > > I would like to nominate Lukas as a committer to the plugins for m1 and > m2. +1 -Vincent - 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_45329 ]
Vincent Massol commented on MNG-785:
Hi Mark and Trygve,
Obviously I'd love to have this in Cargo... ATM Cargo supports some part of
this but not all. However we are *very* open to include all those features in
and Mark will always be welcome in Cargo land :-)
We currently do not have a m2 plugin. However it would be very easy to create
one as Cargo offers a Java API for all container manipulation.
Mark, if you're interested in discussing specifics and what exists/does exist
in Cargo vs your plugin, please talk to us in the Cago dev mailing list
(http://archive.codehaus.org/cargo/).
> 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.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]
[maven2 build - FAILED - update] Sat Aug 27 07:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.073000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
svn commit: r240396 - /maven/components/trunk/maven-plugin-mapping/src/main/mdo/plugins.mdo
Author: brett Date: Fri Aug 26 22:47:24 2005 New Revision: 240396 URL: http://svn.apache.org/viewcvs?rev=240396&view=rev Log: remove unused field Modified: maven/components/trunk/maven-plugin-mapping/src/main/mdo/plugins.mdo Modified: maven/components/trunk/maven-plugin-mapping/src/main/mdo/plugins.mdo URL: http://svn.apache.org/viewcvs/maven/components/trunk/maven-plugin-mapping/src/main/mdo/plugins.mdo?rev=240396&r1=240395&r2=240396&view=diff == --- maven/components/trunk/maven-plugin-mapping/src/main/mdo/plugins.mdo (original) +++ maven/components/trunk/maven-plugin-mapping/src/main/mdo/plugins.mdo Fri Aug 26 22:47:24 2005 @@ -53,16 +53,6 @@ 1.0.0 The plugin artifactId - - - packagingHandlers - 1.0.0 - A list of the packaging types supported by this plugin. - -String -* - - - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 06:30:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.063000.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 07:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.071500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] How to turn off transitive dependencies?
Carsten Ziegeler wrote: > 1) Avalon framework. Up to version 4.1.0 (or something) Avalon had one > big jar: the avalon framework. Then starting with 4.1.1 they splitt this > into two jar files: api and impl. But for convenience they provide both > versions, so for example, you have > avalon-framework-4.2.0.jar > avalon-framework-api-4.2.0.jar > avalon-framework-impl-4.2.0.jar > > Now Cocoon depends on 4.2.0 api and impl which of course works fine. We > use several other projects, that depend on avalon-framework-4.1.5. As > this is a different identifier for the jar we end up with > avalon-framework-4.1.5 and api/impl from 4.2.0 resulting in errors as > 4.1.5 is loaded before the other two jars! (Compilation works fine of > course). > All poms are imho correct. And there are several projects having these > different dependencies. So everywhere specifying exclude statements > can't be the solution. > Just in addition, a similar problem exists with Ant. Up to 1.5.x Ant provided two jars, ant and ant-optional. From 1.6 Ant splitted up the optinal jar into several ones. Now if your project depends on ant 1.6.5 and let's say ant-optional-trax-1.6.5 while a project you depend on, depends on ant-optional.1.5.3 again you have all three jars resulting in errors at runtime. Carsten -- Carsten Ziegeler - Open Source Group, S&N AG http://www.s-und-n.de http://www.osoco.org/weblogs/rael/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 06:15:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.061500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 06:45:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.064500.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[maven2 build - FAILED - update] Sat Aug 27 07:00:00 GMT 2005
Log: http://maven.zones.apache.org/~maven/logs/m2-build-log-20050827.07.txt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
