Flaw in maven-scm-api command line expansion

[dan tran]

Folks,

Most of maven-scm-api commands like checkin, add, tag, changelog has a
ScmFileSet argument which ultimately expands into a list of individual
files on a command line.  The finally command line becomes very long,
huge, so huge
for a larget project (like my legacy project).

I know for sure, it will break on windows and could be on unixes.

May this is the main reason, why a number of implementations just
simply ignore the ScmFileSet, and goes for the default which
most SCM systems consider as ${basedir}


Any thought?

-Dan

[maven2 build - SUCCESS] Fri May 27 02:07:01 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050527.020701.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050527.020701.txt

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r178751 - /maven/components/trunk/maven-site/src/site/xdoc/getting-started.xml

[brett]

Author: brett
Date: Thu May 26 22:25:38 2005
New Revision: 178751

URL: http://svn.apache.org/viewcvs?rev=178751&view=rev
Log:
correct the getting started guide in light of alpha-2

Modified:
maven/components/trunk/maven-site/src/site/xdoc/getting-started.xml

Modified: maven/components/trunk/maven-site/src/site/xdoc/getting-started.xml
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-site/src/site/xdoc/getting-started.xml?rev=178751&r1=178750&r2=178751&view=diff
==
--- maven/components/trunk/maven-site/src/site/xdoc/getting-started.xml 
(original)
+++ maven/components/trunk/maven-site/src/site/xdoc/getting-started.xml Thu May 
26 22:25:38 2005
@@ -61,7 +61,7 @@
   src/test/java directory containing a trivial unit test.
 
 
-  Let's try a few things...
+  Let's now change into the project's directory and try a few things...
 
   
   
@@ -132,20 +132,77 @@
   been done.
 
   
+  
+
+  What if you would like to customise whether a plugins is enabled, or 
how a plugin operates? 
+  In Maven 1.0, you would have added some preGoal to 
maven.xml and some
+  entries to project.properties. Here, it is a little 
different.
+
+
+  For this example, we will configure the Java compiler to allow JDK 
5.0 sources. This is as simple as
+  adding this to your POM:
+
+
+
+  You'll notice that all plugins in Maven 2.0 look much like a 
dependency - and in some ways they are.
+  This plugin will be automatically downloaded and used - including a 
specific version if you request it
+  (the default is to use the latest available).
+
+
+  The configuration element applies the given parameters 
to every goal from the compiler plugin.
+  It is possible to change a parameter just for an individual goal as 
well - for example, to change the
+  debug flag for test sources:
+
+
+
+  To find out what configuration is available for a plugin, you can 
see the Plugins List
+  and navigate to the plugin and goal you are using.
+
+  
   
 
-  Note that the lifecycle applies to any project type. For example, we 
can create a simple web application:
+  Note that the lifecycle applies to any project type. For example, 
back in the base direcotry we can create a simple web application:
 
 
-m2 archetype:create
-   -DgroupId=com.mycompany.app -DartifactId=my-webapp
+m2 archetype:create \
+   -DgroupId=com.mycompany.app -DartifactId=my-webapp \
-DarchetypeArtifactId=maven-archetype-webapp
 
   Note that these must all be on a single line. This will create a 
directory
   my-webapp and the following
   project descriptor:
 
-
+]]>
 
   Note the
-   element - this tells Maven to build 
as a WAR. Again, try:
+   element - this tells Maven to build 
as a WAR. Change into the webapp project's directory and try:
 
 m2 clean:clean package
 
   You'll see
   target/my-webapp.war is built, and that all the normal 
steps were executed.
 
-
-  What is the
-  plugins section all about? Well, this is how plugins 
are configured in Maven 2.0.
-  It is analogous to the
-  project.properties file in Maven 1.0. You may note that 
it looks more
-  verbose - but you'll see over time that it should be required much 
less, and is capable of much more powerful
-  configuration than it's Maven 1.0 counterpart. In addition, we hope 
the burden of editing the POM will be
-  eased by the availability of tools in the near future.
-
-
-  Note that this section is not required to build a WAR - if you omit 
it, the project will still build a WAR,
-  but the default output name of
-  my-webapp-1.0-SNAPSHOT.war will be used instead. In 
fact... go ahead
-  and try that now!
-
   
   
 
@@ -215,7 +249,7 @@
 
   The POM file you'll create should contain the following:
 
-
+]]>
 
   We'll need a dependency on the JAR from the webapp, so add this to
   my-webapp/pom.xml:
@@ -245,11 +279,11 @@
 .]]>
 
   Finally, add the following
-   element to both of the other
   pom.xml files
   in the subdirectories:
 
-

Re: svn commit: r178734 - /maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt

[Brett Porter]

[EMAIL PROTECTED] wrote:


+[ ] 4. Change plugin inheritance to be enabled, cumulatively
+
+   -> Alternately, we could inherit all plugins, but only APPLY/EXECUTE the
+  ones where inherit=true...that would keep the phases of the build
+  process essentially unchanged, but could result in quite a bit of 
+  useless overhead as we calculate/inject plugin configurations which 
+  will not be inherited/used. The problem here is knowing which ones 
+  actually were inherited and should have the inherit=true test 
+  applied, and which ones are supplying inherit=true|false but were 
+  specified at this level.
 

I think this is the solution. The model inheritence should do what they 
do without interference, the lifecycle executor determine what to execute.


The way this could be applied is by having an "applied" flag behind the 
scenes. When the model inheritence is assembled, if 
false was given, then it is not inherited at all to 
the children. Therefore, its existence in the child indicates that it 
was directly given, inherit was true, or inherit was not given. In the 
first two cases, during assembly, applied can be set to "true", in the 
last case, applied can be set to "false".


When it comes to the lifecycle executor, the test it does is:
if ( mojoDescriptor.isInhertByDefault() || mojo.isApplied() ) {
 // bind to the lifecycle
}

Does this make sense?


+
+[ ] 5. Add profiles, defined in POM, ${basedir}/profiles.xml, and settings.xml
+
+   -> Different validation rules for allowed elements in each, to maintain 
+  portability.
 

Not sure what you mean here? The things used in here should be a base 
class of Model. ie maven.mdo should have SharedProfileModel 
(settings.xml) -> ProfileModel (profiles.xml) -> Model (pom.xml) as the 
extends order. I wonder, can maven-settings import part of an mdo, or 
will it need to be reproduced? For now, I think the latter, because of 
the need to be able to generate the docs, etc properly, but try and 
enable it later.


+
+   -> Info in profiles will be applied AFTER all assembly, but BEFORE cli 
+  values (what cli values are we using??)
 

Yes, this is actually done that way anyway. The profiles are like 
another inheritence step (I think it happens before interpolation too). 
The CLI only comes into affect when resolving expressions, which is done 
at runtime.


+
+   -> Profiles can be ordered
+
+   * settings.xml: 
+   

+
+   * profiles.xml: 
+   ..

+
+   * pom.xml: {see profiles.xml}
 

Yep, lists should suffice, I think the ordering of assembly will make 
sure they go in the right order...



+
+[ ] 6. Add --show-profiles execution mode for maven, storage of 
+   profiles-in-effect in MavenSession for later access?
 

I listed this as a nice to have, so unless it costs nothing to do, you 
can leave it out for now.


Thanks for this.

Cheers,
Brett

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[maven2 build - SUCCESS] Fri May 27 00:07:01 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050527.000701.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050527.000701.txt

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 0 (0 including POMs).
building file list ... done
last-sync.txt
wrote 639782 bytes  read 42 bytes  6917.02 bytes/sec
total size is 2634333842  speedup is 4117.28
building file list ... done
.index.txt
last-sync.txt
wrote 1106303 bytes  read 64 bytes  2669.16 bytes/sec
total size is 3631904991  speedup is 3282.73

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: maven.zones.apache.org upgraded

[Brett Porter]

This is now running CI for Continuum, Plexus utils/containers and Maven 
1's core.


I've filed for all the problems I had. I had to do far too much server 
side diddling, but we'll get there... I've now got all the m2 stuff in 
the continuum install symlinked to where exec'd m2 puts them because it 
was getting quite confused.


- Brett

Brett Porter wrote:


... to maven alpha2, continuum alpha2. Looking nice. Filing bugs :)

- Brett

[continuum] BUILD SUCCESSFUL: Continuum Plexus Application

[[EMAIL PROTECTED]]

Build statistics:
  State: Ok
  Previous State: Failed
  Started at: Fri, 27 May 2005 03:32:59 +
  Finished at: Fri, 27 May 2005 03:33:17 +
  Total time: 18s
  Building machine hostname: maven.zones.apache.org



Standard output:

[INFO] continuum-parent: using locally installed snapshot
[INFO] 

[INFO] Building Continuum Plexus Application
[INFO] 

[INFO] maven-jar-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] maven-clean-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] [clean:clean]
[INFO] maven-resources-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-compiler-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-surefire-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-install-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] [resources:resources]
[INFO] continuum-web: using locally installed snapshot
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-service-xmlrpc/1.0-alpha-2/plexus-service-xmlrpc-1.0-alpha-2.pom
1/1K
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-service-xmlrpc/1.0-alpha-2/plexus-service-xmlrpc-1.0-alpha-2.pom.md5
0/0K
0K downloaded
[INFO] continuum-xmlrpc: using locally installed snapshot
Downloading: 
http://repo1.maven.org/maven2/jetty/org.mortbay.jetty/4.2.22/org.mortbay.jetty-4.2.22.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/jetty/org.mortbay.jetty/4.2.22/org.mortbay.jetty-4.2.22.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/geronimo-spec/geronimo-spec-jsp/2.0-rc4/geronimo-spec-jsp-2.0-rc4.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/geronimo-spec/geronimo-spec-jsp/2.0-rc4/geronimo-spec-jsp-2.0-rc4.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/tomcat/jasper-compiler/4.1.30/jasper-compiler-4.1.30.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/tomcat/jasper-compiler/4.1.30/jasper-compiler-4.1.30.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/tomcat/jasper-runtime/4.1.30/jasper-runtime-4.1.30.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/tomcat/jasper-runtime/4.1.30/jasper-runtime-4.1.30.pom.md5
0/0K
0K downloaded
[INFO] plexus-formica: resolved to version 1.0-beta-4-20050527.015415-1 from 
local repository
[INFO] continuum-model: using locally installed snapshot
[INFO] continuum-core: using locally installed snapshot
[INFO] continuum-api: using locally installed snapshot
Downloading: 
http://repo1.maven.org/maven2/tomcat/jasper-compiler/4.1.30/jasper-compiler-4.1.30.jar
2/177K
6/177K
6/177K
10/177K
11/177K
15/177K
15/177K
18/177K
22/177K
23/177K
25/177K
27/177K
31/177K
35/177K
37/177K
41/177K
43/177K
47/177K
51/177K
54/177K
58/177K
61/177K
65/177K
67/177K
71/177K
75/177K
79/177K
83/177K
86/177K
90/177K
94/177K
95/177K
99/177K
103/177K
107/177K
111/177K
115/177K
119/177K
122/177K
126/177K
129/177K
133/177K
137/177K
139/177K
143/177K
147/177K
151/177K
154/177K
158/177K
161/177K
163/177K
167/177K
170/177K
174/177K
177/177K
177K downloaded
Downloading: 
http://repo1.maven.org/maven2/tomcat/jasper-compiler/4.1.30/jasper-compiler-4.1.30.jar.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-service-jetty/1.0-alpha-1/plexus-service-jetty-1.0-alpha-1.jar
3/1142K
7/1142K
11/1142K
15/1142K
19/1142K
23/1142K
27/1142K
31/1142K
32/1142K
36/1142K
40/1142K
44/1142K
45/1142K
49/1142K
52/1142K
56/1142K
59/1142K
63/1142K
66/1142K
70/1142K
73/1142K
77/1142K
78/1142K
80/1142K
84/1142K
88/1142K
92/1142K
96/1142K
99/1142K
103/1142K
106/1142K
110/1142K
113/1142K
117/1142K
120/1142K
124/1142K
127/1142K
131/1142K
134/1142K
136/1142K
140/1142K
144/1142K
147/1142K
151/1142K
154/1142K
156/1142K
160/1142K
164/1142K
167/1142K
171/1142K
174/1142K
178/1142K
181/1142K
185/1142K
188/1142K
192/1142K
192/1142K
196/1142K
199/1142K
203/1142K
207/1142K
211/1142K
214/1142K
218/1142K
221/1142K
225/1142K
228/1142K
232/1142K
235/1142K
236/1142K
240/1142K
244/1142K
248/1142K
251/1142K
255/1142K
258/1142K
262/1142K
265/1142K
269/1142K
272/1142K
276/1142K
279/1142K
283/1142K
284/1142K
288/1142K
291/1142K
295/1142K
298/1142K
302/1142K
305/1142K
309/1142K
312/1142K
316/1142K
319/1142K
323/1142K
326/1142K
328/1142K
332/1142K
335/1142K
339/1142K
342/1142K
346/1142K
349/1142K
353/1142K
356/1142K
360/1142K
363/1142K
367/1142K
371/1142K
375/1142K
375/1142K
379/1142K
382/1142K
386/1142K
389/1142K
393/1142K
396/1142K
400/

[continuum] BUILD SUCCESSFUL: Continuum Web

[[EMAIL PROTECTED]]

Build statistics:
  State: Ok
  Previous State: Failed
  Started at: Fri, 27 May 2005 03:32:27 +
  Finished at: Fri, 27 May 2005 03:32:49 +
  Total time: 22s
  Building machine hostname: maven.zones.apache.org



Standard output:

[INFO] continuum-parent: using locally installed snapshot
[INFO] 

[INFO] Building Continuum Web
[INFO] 

[INFO] maven-jar-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] maven-clean-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] [clean:clean]
[INFO] Deleting directory 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/6/target
[INFO] maven-resources-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-compiler-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-surefire-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-install-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] [resources:resources]
[INFO] plexus-formica: checking for updates from central
[INFO] Retrieving snapshot information for plexus-formica 1.0-beta-4-SNAPSHOT
[INFO] plexus-formica: resolved to version 1.0-beta-4-20050527.015415-1 from 
repository central
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-formica/1.0-beta-4-SNAPSHOT/plexus-formica-1.0-beta-4-20050527.015415-1.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-formica/1.0-beta-4-SNAPSHOT/plexus-formica-1.0-beta-4-20050527.015415-1.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/servletapi/servletapi/2.3/servletapi-2.3.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/servletapi/servletapi/2.3/servletapi-2.3.pom.md5
0/0K
0K downloaded
[INFO] continuum-model: using locally installed snapshot
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-i18n/1.0-beta-4/plexus-i18n-1.0-beta-4.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-i18n/1.0-beta-4/plexus-i18n-1.0-beta-4.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-summit/1.0-beta-4/plexus-summit-1.0-beta-4.pom
1/1K
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-summit/1.0-beta-4/plexus-summit-1.0-beta-4.pom.md5
0/0K
0K downloaded
Downloading: http://repo1.maven.org/maven2/ognl/ognl/2.5.1/ognl-2.5.1.pom
0/0K
0K downloaded
Downloading: http://repo1.maven.org/maven2/ognl/ognl/2.5.1/ognl-2.5.1.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-fileupload/commons-fileupload/1.0/commons-fileupload-1.0.pom
2/4K
4/4K
4K downloaded
Downloading: 
http://repo1.maven.org/maven2/commons-fileupload/commons-fileupload/1.0/commons-fileupload-1.0.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-formica-web/1.0-alpha-1/plexus-formica-web-1.0-alpha-1.pom
1/1K
1K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-formica-web/1.0-alpha-1/plexus-formica-web-1.0-alpha-1.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-log4j-logging/1.0/plexus-log4j-logging-1.0.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-log4j-logging/1.0/plexus-log4j-logging-1.0.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-logging/1.0/plexus-logging-1.0.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-logging/1.0/plexus-logging-1.0.pom.md5
0/0K
0K downloaded
[INFO] continuum-core: using locally installed snapshot
Downloading: 
http://repo1.maven.org/maven2/geronimo-spec/geronimo-spec-servlet/2.4-rc4/geronimo-spec-servlet-2.4-rc4.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/geronimo-spec/geronimo-spec-servlet/2.4-rc4/geronimo-spec-servlet-2.4-rc4.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-servlet/1.0-beta-2/plexus-servlet-1.0-beta-2.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-servlet/1.0-beta-2/plexus-servlet-1.0-beta-2.pom.md5
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-action/1.0-alpha-1/plexus-action-1.0-alpha-1.pom
0/0K
0K downloaded
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-action/1.0-alpha-1/plexus-action-1.0-alpha-1.pom.md5
0/0K
0K downloaded
[INFO] continuum-api: using locally installed snapshot
Downloading: http://repo1.maven.org/maven2/ognl/ognl/2.5.1/ognl-2.5.1.jar
2/145K
6/145K
6/145K
10/145K

[continuum] BUILD FAILURE: Continuum Plexus Application

[[EMAIL PROTECTED]]

Build statistics:
  State: Failed
  Previous State: Error
  Started at: Fri, 27 May 2005 03:31:43 +
  Finished at: Fri, 27 May 2005 03:31:45 +
  Total time: 2s
  Building machine hostname: maven.zones.apache.org



Standard output:

[INFO] continuum-parent: using locally installed snapshot
[INFO] 

[INFO] Building Continuum Plexus Application
[INFO] 

[INFO] maven-jar-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] maven-clean-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] [clean:clean]
[INFO] maven-resources-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-compiler-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-surefire-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-install-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] [resources:resources]
Downloading: 
http://repo1.maven.org/maven2/org/apache/maven/continuum/continuum-web/1.0-alpha-3-SNAPSHOT/continuum-web-1.0-alpha-3-SNAPSHOT.pom
[WARNING] Unable to get resource from repository http://repo1.maven.org/maven2
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Main Error:
  Unable to download the artifact from any repository
  org.apache.maven.continuum:continuum-web:1.0-alpha-3-SNAPSHOT:pom

from the specified remote repositories:
  http://repo1.maven.org/maven2

Root error:
  Unable to download the artifact from any repository
[INFO] 

[INFO] Total time: 1 second
[INFO] Finished at: Fri May 27 03:31:45 GMT+00:00 2005
[INFO] Final Memory: 3M/266M
[INFO] 




There was no content on standard error.

[continuum] BUILD FAILURE: Continuum Web

[[EMAIL PROTECTED]]

Build statistics:
  State: Failed
  Previous State: Error
  Started at: Fri, 27 May 2005 03:31:39 +
  Finished at: Fri, 27 May 2005 03:31:41 +
  Total time: 2s
  Building machine hostname: maven.zones.apache.org



Standard output:

[INFO] continuum-parent: using locally installed snapshot
[INFO] 

[INFO] Building Continuum Web
[INFO] 

[INFO] maven-jar-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] maven-clean-plugin: resolved to version 2.0-alpha-2 from local repository
[INFO] [clean:clean]
[INFO] Deleting directory 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/6/target
[INFO] maven-resources-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-compiler-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-surefire-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] maven-install-plugin: resolved to version 2.0-alpha-2 from local 
repository
[INFO] [resources:resources]
Downloading: 
http://repo1.maven.org/maven2/plexus/plexus-formica/1.0-beta-4-SNAPSHOT/plexus-formica-1.0-beta-4-SNAPSHOT.pom
[WARNING] Unable to get resource from repository http://repo1.maven.org/maven2
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Main Error:
  Unable to download the artifact from any repository
  plexus:plexus-formica:1.0-beta-4-SNAPSHOT:pom

from the specified remote repositories:
  http://repo1.maven.org/maven2

Root error:
  Unable to download the artifact from any repository
[INFO] 

[INFO] Total time: 1 second
[INFO] Finished at: Fri May 27 03:31:41 GMT+00:00 2005
[INFO] Final Memory: 2M/245M
[INFO] 




There was no content on standard error.

[continuum] BUILD ERROR: Continuum Plexus Application

[[EMAIL PROTECTED]]

Build statistics:
  State: Error
  Previous State: Error
  Started at: Fri, 27 May 2005 03:29:46 +
  Finished at: Fri, 27 May 2005 03:29:46 +
  Total time: 0s
  Building machine hostname: maven.zones.apache.org


There was no content on standard output.

There was no content on standard error.

[continuum] BUILD ERROR: Continuum Web

[[EMAIL PROTECTED]]

Build statistics:
  State: Error
  Previous State: Error
  Started at: Fri, 27 May 2005 03:29:43 +
  Finished at: Fri, 27 May 2005 03:29:43 +
  Total time: 0s
  Building machine hostname: maven.zones.apache.org


There was no content on standard output.

There was no content on standard error.

svn commit: r178734 - /maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt

[jdcasey]

Author: jdcasey
Date: Thu May 26 20:29:54 2005
New Revision: 178734

URL: http://svn.apache.org/viewcvs?rev=178734&view=rev
Log:
adding my notes for implementing plugin inheritance and build profiles. delete 
if not needed.

Added:

maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt
   (with props)

Added: 
maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt?rev=178734&view=auto
==
--- 
maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt
 (added)
+++ 
maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt
 Thu May 26 20:29:54 2005
@@ -0,0 +1,64 @@
+marching orders:
+===
+
+[X] 1. Add concept of inherit=(true|false) for plugins at plugin/goal levels
+
+[X] 2. Add is|setInheritedByDefault methods to MojoDescriptor to support 
setting
+   the default inheritance behavior per mojo.
+
+[X] 3. Add annotation for @inheritedByDefault (true|false).
+
+[ ] 4. Change plugin inheritance to be enabled, cumulatively
+
+   -> Not sure how best to do this. 
+
+  It cannot happen in the MavenProjectBuilder, since no plugins have 
+  been resolved at this point, and we cannot know what the default 
+  inheritance semantics are for a particular plugin.
+
+  If this happens at the DefaultLifecycleExecutor, we've dragged the
+  Profiles assembly and injection out of the assembly code and into the
+  build-execution code (that is, out of maven-project and into 
+  maven-core). This has implications for people using maven-project
+  outside of m2 itself.
+
+   -> Possibly we need to move plugin verification outside of the lifecycle
+  executor to a post-MavenProjectBuilder phase, which would also
+  take place before injection of Profile values. This is complicated, 
as
+  it would leave maven-project in an incomplete state (plugin 
+  inheritance wouldn't be part of the basic MavenProjectBuilder, since 
+  the plugin manager is part of maven-core). Since Profiles must be 
+  applied after inheritance is finished, it also means that Profiles 
+  cannot be applied as part of the maven-project API as accessed 
+  through the MavenProjectBuilder
+
+   -> Alternately, we could inherit all plugins, but only APPLY/EXECUTE the
+  ones where inherit=true...that would keep the phases of the build
+  process essentially unchanged, but could result in quite a bit of 
+  useless overhead as we calculate/inject plugin configurations which 
+  will not be inherited/used. The problem here is knowing which ones 
+  actually were inherited and should have the inherit=true test 
+  applied, and which ones are supplying inherit=true|false but were 
+  specified at this level.
+
+[ ] 5. Add profiles, defined in POM, ${basedir}/profiles.xml, and settings.xml
+
+   -> Different validation rules for allowed elements in each, to maintain 
+  portability.
+
+   -> Info in profiles will be applied AFTER all assembly, but BEFORE cli 
+  values (what cli values are we using??)
+
+   -> Profiles can be ordered
+
+   * settings.xml: 
+   
+
+   * profiles.xml: 
+   ..
+
+   * pom.xml: {see profiles.xml}
+
+[ ] 6. Add --show-profiles execution mode for maven, storage of 
+   profiles-in-effect in MavenSession for later access?
+

Propchange: 
maven/components/trunk/plugin-inheritance-and-profiles-notes-jdcasey-20050526.txt
--
svn:keywords = "Date Rev Author"



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

svn commit: r178733 - /maven/components/trunk/maven-core/src/main/java/org/apache/maven/project /maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance /maven/components/trunk/maven-model /maven/components/trunk/maven-plugin-descriptor/src/main/java/org/apache/maven/plugin/descriptor /maven/components/trunk/maven-plugin-tools/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator /maven/components/trunk/maven-plugin-tools/maven-plugin-tools-java/src/main/java/org/apache/maven/tools/plugin/extractor/java /maven/components/trunk/maven-project/src/main/java/org/apache/maven/project /maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/injection

[jdcasey]

Author: jdcasey
Date: Thu May 26 20:27:55 2005
New Revision: 178733

URL: http://svn.apache.org/viewcvs?rev=178733&view=rev
Log:
o Added inherited field to the Plugin and Goal classes in maven.mdo
o Added annotation inheritedByDefault (looks like: @inheritedByDefault 
true|false) for java mojos
o Added support for inheritedByDefault to MojoDescriptor, descriptor generator 
and builder
o Factored the plugin combinatorial logic into ModelUtils in o.a.m.project, for 
later reuse in a plugin-aware model inheritance builder
o Refactored the DefaultModelDefaultsInjector to use the new ModelUtils for 
plugin merging (this is factored into a utility for reuse in inheritance 
assembly)

Added:
maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/

maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance/

maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance/PluginAwareModelInheritanceAssembler.java
   (with props)

maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/ModelUtils.java
   (with props)
Modified:
maven/components/trunk/maven-model/maven.mdo

maven/components/trunk/maven-plugin-descriptor/src/main/java/org/apache/maven/plugin/descriptor/MojoDescriptor.java

maven/components/trunk/maven-plugin-descriptor/src/main/java/org/apache/maven/plugin/descriptor/PluginDescriptorBuilder.java

maven/components/trunk/maven-plugin-tools/maven-plugin-tools-api/src/main/java/org/apache/maven/tools/plugin/generator/PluginDescriptorGenerator.java

maven/components/trunk/maven-plugin-tools/maven-plugin-tools-java/src/main/java/org/apache/maven/tools/plugin/extractor/java/JavaMojoDescriptorExtractor.java

maven/components/trunk/maven-project/src/main/java/org/apache/maven/project/injection/DefaultModelDefaultsInjector.java

Added: 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance/PluginAwareModelInheritanceAssembler.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance/PluginAwareModelInheritanceAssembler.java?rev=178733&view=auto
==
--- 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance/PluginAwareModelInheritanceAssembler.java
 (added)
+++ 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/project/inheritance/PluginAwareModelInheritanceAssembler.java
 Thu May 26 20:27:55 2005
@@ -0,0 +1,74 @@
+package org.apache.maven.project.inheritance;
+
+import org.apache.maven.model.Build;
+import org.apache.maven.model.Model;
+import org.apache.maven.model.Plugin;
+import org.apache.maven.plugin.PluginManager;
+import org.apache.maven.project.ModelUtils;
+
+import java.util.Iterator;
+import java.util.List;
+import java.util.Map;
+
+/*
+ * Copyright 2001-2005 The Apache Software Foundation.
+ *
+ * Licensed under the Apache License, Version 2.0 (the "License");
+ * you may not use this file except in compliance with the License.
+ * You may obtain a copy of the License at
+ *
+ *  http://www.apache.org/licenses/LICENSE-2.0
+ *
+ * Unless required by applicable law or agreed to in writing, software
+ * distributed under the License is distributed on an "AS IS" BASIS,
+ * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+ * See the License for the specific language governing permissions and
+ * limitations under the License.
+ */
+
+public class PluginAwareModelInheritanceAssembler
+extends DefaultModelInheritanceAssembler
+{
+
+//private PluginManager pluginManager;
+//
+//public void assembleModelInheritance( Model child, Model parent )
+//{
+//super.assembleModelInheritance( child, parent );
+//
+//Build parentBuild = parent.getBuild();
+//Build childBuild = child.getBuild();
+//
+//if(parentBuild != null)
+//{
+//List parentPlugins = parentBuild.getPlugins();
+//
+//if( childBuild == null )
+//{
+//childBuild = new Build();
+//child.setBuild(childBuild);
+//}
+//
+//Map childPluginMap = childBuild.getPluginsAsMap();
+//
+//for ( Iterator it = parentPlugins.iterator(); it.hasNext(); )
+//{
+//Plugin parentPlugin = (Plugin) it.next();
+//
+//String inherited = parentPlugin.getInherited();
+//
+//if( inherited != null )
+//{
+//
+//}
+//else
+//{
+//// determine from the plugin descriptor what the default 
behavior is...
+//PluginDescriptor pluginDescriptor = 
pluginManager.verifyPlugin(parentPlugin.getGroupId(), 

[continuum] BUILD ERROR: Continuum Plexus Application

[[EMAIL PROTECTED]]

Build statistics:
  State: Error
  Previous State: Failed
  Started at: Fri, 27 May 2005 03:24:08 +
  Finished at: Fri, 27 May 2005 03:24:08 +
  Total time: 0s
  Building machine hostname: maven.zones.apache.org


There was no content on standard output.

There was no content on standard error.

[continuum] BUILD ERROR: Continuum Web

[[EMAIL PROTECTED]]

Build statistics:
  State: Error
  Previous State: Error
  Started at: Fri, 27 May 2005 03:24:05 +
  Finished at: Fri, 27 May 2005 03:24:05 +
  Total time: 0s
  Building machine hostname: maven.zones.apache.org


There was no content on standard output.

There was no content on standard error.

[continuum] BUILD ERROR: Continuum Web

[[EMAIL PROTECTED]]

Build statistics:
  State: Error
  Previous State: Error
  Started at: Fri, 27 May 2005 03:20:19 +
  Finished at: Fri, 27 May 2005 03:20:19 +
  Total time: 0s
  Building machine hostname: maven.zones.apache.org


There was no content on standard output.

There was no content on standard error.

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 2 (4 including POMs).
building file list ... done
jpox/poms/
last-sync.txt
struts/jars/
struts/jars/struts-1.2.7.jar
struts/jars/struts-el-1.2.7.jar
wrote 1395415 bytes  read 74 bytes  36246.47 bytes/sec
total size is 2634333842  speedup is 1887.75
building file list ... done
./
.index.txt
last-sync.txt
ojdbc/
ojdbc/ojdbc/
ojdbc/ojdbc/14/
ojdbc/ojdbc/14/ojdbc-14.pom
org/apache/maven/continuum/continuum-parent/
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/continuum-parent-1.0-alpha-3-20050527.024032-1.pom
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/continuum-parent-1.0-alpha-3-20050527.024032-1.pom.md5
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/continuum-parent-1.0-alpha-3-20050527.024032-1.pom.sha1
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/continuum-parent-1.0-alpha-3-SNAPSHOT.version.txt
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/continuum-parent-1.0-alpha-3-SNAPSHOT.version.txt.md5
org/apache/maven/continuum/continuum-parent/1.0-alpha-3-SNAPSHOT/continuum-parent-1.0-alpha-3-SNAPSHOT.version.txt.sha1
org/apache/maven/continuum/continuum-parent/continuum-parent-RELEASE.version.txt
org/apache/maven/continuum/continuum-parent/continuum-parent-RELEASE.version.txt.md5
org/apache/maven/continuum/continuum-parent/continuum-parent-RELEASE.version.txt.sha1
plexus/plexus-container-artifact/
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-20050527.013505-1.jar
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-20050527.013505-1.jar.md5
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-20050527.013505-1.jar.sha1
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-20050527.013505-1.pom
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-20050527.013505-1.pom.md5
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-20050527.013505-1.pom.sha1
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-SNAPSHOT.version.txt
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-SNAPSHOT.version.txt.md5
plexus/plexus-container-artifact/1.0-alpha-4-SNAPSHOT/plexus-container-artifact-1.0-alpha-4-SNAPSHOT.version.txt.sha1
plexus/plexus-container-artifact/plexus-container-artifact-RELEASE.version.txt
plexus/plexus-container-artifact/plexus-container-artifact-RELEASE.version.txt.md5
plexus/plexus-container-artifact/plexus-container-artifact-RELEASE.version.txt.sha1
plexus/plexus-container-default/
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-20050527.012752-1.jar
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-20050527.012752-1.jar.md5
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-20050527.012752-1.jar.sha1
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-20050527.012752-1.pom
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-20050527.012752-1.pom.md5
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-20050527.012752-1.pom.sha1
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-SNAPSHOT.version.txt
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-SNAPSHOT.version.txt.md5
plexus/plexus-container-default/1.0-alpha-4-SNAPSHOT/plexus-container-default-1.0-alpha-4-SNAPSHOT.version.txt.sha1
plexus/plexus-container-default/plexus-container-default-RELEASE.version.txt
plexus/plexus-container-default/plexus-container-default-RELEASE.version.txt.md5
plexus/plexus-container-default/plexus-container-default-RELEASE.version.txt.sha1
plexus/plexus-containers/
plexus/plexus-containers/1.0/
plexus/plexus-containers/1.0/plexus-containers-1.0.pom
plexus/plexus-containers/1.0/plexus-containers-1.0.pom.md5
plexus/plexus-containers/1.0/plexus-containers-1.0.pom.sha1
plexus/plexus-containers/plexus-containers-RELEASE.version.txt
plexus/plexus-containers/plexus-containers-RELEASE.version.txt.md5
plexus/plexus-containers/plexus-containers-RELEASE.version.txt.sha1
plexus/plexus-formica/
plexus/plexus-formica/1.0-beta-4-SNAPSHOT/
plexus/plexus-formica/1.0-beta-4-SNAPSHOT/plexus-formica-1.0-beta-4-20050527.015415-1.jar
plexus/plexus-formica/1.0-beta

[jira] Created: (MNG-432) install:install-file relies on a project when it shouldn't need to

[Brett Porter (JIRA)]

install:install-file relies on a project when it shouldn't need to
--

 Key: MNG-432
 URL: http://jira.codehaus.org/browse/MNG-432
 Project: Maven 2
Type: Bug
Reporter: Brett Porter
 Fix For: 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]

[continuum] BUILD ERROR: Continuum Web

[[EMAIL PROTECTED]]

Build statistics:
  State: Error
  Previous State: Error
  Started at: Fri, 27 May 2005 02:47:26 +
  Finished at: Fri, 27 May 2005 02:47:26 +
  Total time: 0s
  Building machine hostname: maven.zones.apache.org


There was no content on standard output.

There was no content on standard error.

[continuum] BUILD SUCCESSFUL: Maven

[[EMAIL PROTECTED]]

Build statistics:
  State: Ok
  Previous build: No previous build.
  Started at: Fri, 27 May 2005 02:44:26 +
  Finished at: Fri, 27 May 2005 02:44:53 +
  Total time: 27s
  Building machine hostname: maven.zones.apache.org



Standard output:

 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.2

Attempting to download commons-jelly-1.0-RC2-SNAPSHOT.jar.
Attempting to download commons-jelly-tags-ant-1.1-SNAPSHOT.jar.
Attempting to download commons-jelly-tags-xml-1.1-SNAPSHOT.jar.
Attempting to download maven-model-3.0.0-SNAPSHOT.jar.
build:start:

clean:clean:

java:prepare-filesystem:
[mkdir] Created dir: 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes

java:compile:
[echo] Compiling to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes
[echo] 
==

  NOTE: Targetting JVM 1.5, classes
  will not run on earlier JVMs

==
  
[javac] Compiling 116 source files to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes

java:jar-resources:
Copying 1 file to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes/META-INF
Copying 1 file to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes
Copying 4 files to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes
Copying 10 files to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/classes/org/apache/maven/messages

test:prepare-filesystem:
[mkdir] Created dir: 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/test-classes
[mkdir] Created dir: 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/test-reports

test:test-resources:

test:compile:
[javac] Compiling 22 source files to 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/test-classes

test:test:
[junit] Running org.apache.maven.jelly.tags.maven.RootRelativePathTagTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.277 sec
[junit] Running org.apache.maven.jelly.tags.maven.DependencyResolverTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.383 sec
[junit] Running org.apache.maven.werkz.ProjectTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.356 sec
[junit] Running org.apache.maven.werkz.GoalTest
[junit] Tests run: 28, Failures: 0, Errors: 0, Time elapsed: 0.367 sec
[junit] Running org.apache.maven.project.ProjectInheritanceTest
[junit] Tests run: 2, Failures: 0, Errors: 0, Time elapsed: 0.759 sec
[junit] Running org.apache.maven.project.LegacyIdTest
[junit] Tests run: 11, Failures: 0, Errors: 0, Time elapsed: 0.681 sec
[junit] Running org.apache.maven.project.BasedirTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.608 sec
[junit] Running org.apache.maven.util.DVSLPathToolTest
[junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 0.288 sec
[junit] Running org.apache.maven.util.StringToolTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.269 sec
[junit] Running org.apache.maven.util.MavenToolTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.267 sec
[junit] Running org.apache.maven.util.MD5SumTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.503 sec
[junit] Running org.apache.maven.util.EnhancedStringTokenizerTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.262 sec
[junit] Running org.apache.maven.util.DVSLFormatterTest
[junit] Tests run: 3, Failures: 0, Errors: 0, Time elapsed: 0.348 sec
[junit] Running org.apache.maven.util.InsertionOrderedSetTest
[junit] Tests run: 6, Failures: 0, Errors: 0, Time elapsed: 0.272 sec
[junit] Running org.apache.maven.plugin.PluginManagerTest
[junit] Tests run: 7, Failures: 0, Errors: 0, Time elapsed: 1.403 sec
[junit] Running org.apache.maven.plugin.PluginCacheManagerTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.434 sec
[junit] Running org.apache.maven.MavenUtilsTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.471 sec

jar:jar:
[jar] Building jar: 
/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/maven.jar
Copying: from 
'/export/home/continuum/continuum-1.0-alpha-2/apps/continuum/temp/11/target/maven.jar'
 to: 
'/export/home/continuu

Re: Sun POMs

[Carlos Sanchez]

I meant deploying to m2 repo so everything in the m1 gets autogenerated.

- sync'ed repos should go to a temp folder and converted to m2 repo
- each upload bundle should be converted to m2 and deployed in the m2
repo, and not i the m1 one

then all the m2 repo would be converted to m1.

This has sense for you? I'm not sure if now it's possible but seems
that at some point this is the way to go.


On 5/26/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Carlos Sanchez wrote:
> 
> >At some point we definitely want to make changes to maven2 repo and
> >automatically generate the maven1 as there's much more information in
> >m2 poms wich can't be captured in m1 poms.
> >
> >For achieving that we need:
> >- tool to convert m2 repo to m1
> >
> >
> at the moment we are doing it all in the other direction. m1 doesn't
> care about the poms, so we just put the m2 poms in the m1 layout
> 
> >- tool to convert m1 upload requests poms to m2 poms, so people keep
> >uploading m1 bundles that actually will go to m2 repo
> >
> >
> already happening
> 
> >- process the sync'ed repos to convert m1 poms to m2
> >
> >
> already happening
> 
> >I don't know the status of all this so maybe it's too soon to try it,
> >in that case I will keep uploading bundles to m1 and solving pom
> >related issues in m1 repo when possible.
> >
> >
> Yep, that's the approach. m2 poms can go in directly too, and in fact
> would be better.
> 
> >does the m1 to m2 convert tool override existing m2 poms?
> >
> >
> >
> yes, which is a problem. Bug already filed.
> 
> - Brett
> 
> 
> -
> 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: Sun POMs

[Brett Porter]

Carlos Sanchez wrote:


At some point we definitely want to make changes to maven2 repo and
automatically generate the maven1 as there's much more information in
m2 poms wich can't be captured in m1 poms.

For achieving that we need:
- tool to convert m2 repo to m1
 

at the moment we are doing it all in the other direction. m1 doesn't 
care about the poms, so we just put the m2 poms in the m1 layout



- tool to convert m1 upload requests poms to m2 poms, so people keep
uploading m1 bundles that actually will go to m2 repo
 


already happening


- process the sync'ed repos to convert m1 poms to m2
 


already happening


I don't know the status of all this so maybe it's too soon to try it,
in that case I will keep uploading bundles to m1 and solving pom
related issues in m1 repo when possible.
 

Yep, that's the approach. m2 poms can go in directly too, and in fact 
would be better.



does the m1 to m2 convert tool override existing m2 poms?

 


yes, which is a problem. Bug already filed.

- Brett


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Moved: (MRM-6) validator: report if artifacts are out of place

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MRM-6?page=all ]

Brett Porter moved MNG-200 to MRM-6:


 Component: (was: repository-tools)
Issue Type: New Feature  (was: Improvement)
   Key: MRM-6  (was: MNG-200)
   Project: Maven Repository Manager  (was: Maven 2)

> validator: report if artifacts are out of place
> ---
>
>  Key: MRM-6
>  URL: http://jira.codehaus.org/browse/MRM-6
>  Project: Maven Repository Manager
> Type: New Feature
> Reporter: Brett Porter
> Priority: Trivial

>
>
> report if artifacts are out of place. you can tell this because in m2
> the POM is packaged with the artifact in META-INF/maven/pom.xml so with
> that information you can assess weather the artifact is in the right
> location. this should not happen if tools are being used to deploy but
> it would be a good check to have.

-- 
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] Moved: (MRM-5) repository tools don't convert RELEASE files

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MRM-5?page=all ]

Brett Porter moved MNG-381 to MRM-5:


Fix Version: (was: 2.0-alpha-3)
  Component: (was: repository-tools)
 repository-converter
Key: MRM-5  (was: MNG-381)
Project: Maven Repository Manager  (was: Maven 2)

> repository tools don't convert RELEASE files
> 
>
>  Key: MRM-5
>  URL: http://jira.codehaus.org/browse/MRM-5
>  Project: Maven Repository Manager
> Type: Bug
>   Components: repository-converter
> Reporter: Brett Porter

>
>


-- 
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] Moved: (MRM-4) repoclean overwrites valid poms with dummy poms when there was none in m1 repo

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MRM-4?page=all ]

Brett Porter moved MNG-394 to MRM-4:


Component: (was: repository-tools)
   repository-converter
  Key: MRM-4  (was: MNG-394)
  Project: Maven Repository Manager  (was: Maven 2)

> repoclean overwrites valid poms with dummy poms when there was none in m1 repo
> --
>
>  Key: MRM-4
>  URL: http://jira.codehaus.org/browse/MRM-4
>  Project: Maven Repository Manager
> Type: Bug
>   Components: repository-converter
> Reporter: Brett Porter

>
>
> I copied the wagon JARs from the m2 repo to the m1 repo so that m1 users 
> could access them. However, repoclean detected they were newer and 
> "converted" them, copying the JARs back to the original location where they 
> already resided, and overwriting valid m2 poms with dummy groupId/artifactId 
> only POMs because there were none in the m1 repo.

-- 
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] Moved: (MRM-3) NPE in repoclean

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MRM-3?page=all ]

Brett Porter moved MNG-430 to MRM-3:


  Version: (was: 2.0-alpha-3)
Component: (was: repository-tools)
   repository-converter
  Key: MRM-3  (was: MNG-430)
  Project: Maven Repository Manager  (was: Maven 2)

> NPE in repoclean
> 
>
>  Key: MRM-3
>  URL: http://jira.codehaus.org/browse/MRM-3
>  Project: Maven Repository Manager
> Type: Bug
>   Components: repository-converter
> Reporter: Anatol Pomozov
>  Attachments: artifact.patch
>
>
> There was wrong logic in 
> src/main/java/org/apache/maven/tools/repoclean/artifact/metadata/ProjectMetadata.java
>  it returns null and it causes NPE. It should return information from 
> artifact. 
> Simple patch fixed this bug.

-- 
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] Moved: (MRM-2) repository: transitive dependency report

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MRM-2?page=all ]

Brett Porter moved MNG-201 to MRM-2:


 Component: (was: repository-tools)
Issue Type: New Feature  (was: Improvement)
   Key: MRM-2  (was: MNG-201)
   Project: Maven Repository Manager  (was: Maven 2)

> repository: transitive dependency report
> 
>
>  Key: MRM-2
>  URL: http://jira.codehaus.org/browse/MRM-2
>  Project: Maven Repository Manager
> Type: New Feature
> Reporter: Brett Porter

>
>
> repository tool to ensure that transitive dependencies will work. 
> we basically need to know that every artifact that
> is referenced in one POM is actually in the repository along with its
> POM. We need to know that the dependency relationships among
> all artifacts in the repository form a closed set. otherwise the
> transitive dependency mechanism in m2 will break and we need to be wary
> of this. eventually i would like to create graphical representations of
> the dependencies amongst projects but this can come later. 

-- 
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: (WAGONSSH-3) Doesn't appear that directories are being created correctly in all cases

[Jason van Zyl (JIRA)]

Doesn't appear that directories are being created correctly in all cases


 Key: WAGONSSH-3
 URL: http://jira.codehaus.org/browse/WAGONSSH-3
 Project: wagon-ssh
Type: Bug
Reporter: Jason van Zyl
 Fix For: 1.0-alpha-3


[ERROR] BUILD ERROR
[INFO] 

[ERROR] Cause:
org.apache.maven.plugin.MojoExecutionException: Error deploying artifact
at 
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:145)
at 
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:415)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.processGoals(DefaultLifecycleExecutor.java:169)
at 
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:90)
at org.apache.maven.DefaultMaven.processProject(DefaultMaven.java:253)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:167)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
at org.codehaus.classworlds.Launcher.main(Launcher.java:363)
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException: 
Error deploying artifact:
at 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:100)
at 
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:139)
... 14 more
Caused by: org.apache.maven.wagon.TransferFailedException: Resource to deploy 
not found:
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:192)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:96)
at 
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:86)
... 15 more
Caused by: org.apache.maven.wagon.ResourceDoesNotExistException: scp: 
/home/projects/maven/repository-staging/to-ibiblio/maven2//plexus/plexus-containers/1.0/plexus-containers-1.0.pom:
 No such file or directory

at 
org.apache.maven.wagon.providers.ssh.ScpWagon.checkAck(ScpWagon.java:646)
at org.apache.maven.wagon.providers.ssh.ScpWagon.put(ScpWagon.java:298)
at 
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:160)
... 17 more
[INFO] 

[INFO] Total time: 6 seconds
[INFO] Finished at: Thu May 26 20:20:00 GMT-05:00 2005
[INFO] Final Memory: 1M/3M
[INFO] 



-- 
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] Moved: (MEV-21) pom changes for basic hibernate project

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-21?page=all ]

Brett Porter moved MNG-387 to MEV-21:
-

 Component: (was: repository-tools)
Dependencies
Issue Type: Task  (was: Bug)
   Key: MEV-21  (was: MNG-387)
   Project: Maven Evangelism  (was: Maven 2)

> pom changes for basic hibernate project
> ---
>
>  Key: MEV-21
>  URL: http://jira.codehaus.org/browse/MEV-21
>  Project: Maven Evangelism
> Type: Task
>   Components: Dependencies
> Reporter: Ryan Sonnek

>
>
> it seems as if the current m2 repository has some invalid poms.  I'm assuming 
> this is because the m2 pom's were automatically generated from the m1 pom's.  
> Here is a list of changes that were required in my local repository to get a 
> very basic hibernate project up and going.
> change dom4j-1.6.pom stax dependencies to these:
> 
>   stax
>   stax-api
>   1.0
> 
> 
>   stax
>   stax
>   1.1-dev
> 
> remove this dependency from stax-1.1-dev.pom:
> 
>   xmlbeans-jsr173-api
>   xmlbeans-jsr173-api
>   2.0-dev
> 
> manually install geronimo servlet-api as servlet api
> remove two dependencies from xom-1.0b3.pom:
> 
>   icu4j
>   icu4j
>   2.6.1
> 
> 
>   tagsoup
>   tagsoup
>   0.9.7
> 
> manually install empty jdbc-2.0.jar
> can these pom's be scrubbed, or move these dependencies to the m2 repository?

-- 
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] Moved: (MEV-20) clean up bad IDs in the repository

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-20?page=all ]

Brett Porter moved MNG-402 to MEV-20:
-

Fix Version: (was: 2.0-beta-1)
  Component: (was: repository-tools)
Key: MEV-20  (was: MNG-402)
Project: Maven Evangelism  (was: Maven 2)

> clean up bad IDs in the repository
> --
>
>  Key: MEV-20
>  URL: http://jira.codehaus.org/browse/MEV-20
>  Project: Maven Evangelism
> Type: Task
> Reporter: Brett Porter

>
>
> some projects seem to have been filed with the wrong/multiple artifact and 
> group IDs.
> This is to track what they are and get them in order. Document correct IDs, 
> but leave the old ones alone so as not to break builds. A richer repository 
> may later be able to give deprecation warnings on requesting the old JARs.
> This will also assist in making a future transition to a new layout easier.

-- 
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: (MRM-1) commons-lang 1.0-b1 not converted

[Brett Porter (JIRA)]

commons-lang 1.0-b1 not converted
-

 Key: MRM-1
 URL: http://jira.codehaus.org/browse/MRM-1
 Project: Maven Repository Manager
Type: Bug
  Components: repository-converter  
Reporter: Brett Porter
 Assigned to: John Casey 




-- 
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-8) Upload Sun POMs for non redistributable jars

[David Jencks (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39773 ]
 
David Jencks commented on MEV-8:


Since there are non-sun freely available implementations of many of these specs 
I would prefer to see the provenance (Sun) for these particular implementations 
clearly visible in the groupId/artifactId.  I don't know but there may be 
additional non-freely available implementations from IBM and/or BEA.

> Upload Sun POMs for non redistributable jars
> 
>
>  Key: MEV-8
>  URL: http://jira.codehaus.org/browse/MEV-8
>  Project: Maven Evangelism
> Type: Task
> Reporter: Carlos Sanchez
> Assignee: Carlos Sanchez

>
>
> activation
> ejb-3.0
> jaxrpc
> jsp api
> servlet api
> jms
> javamail

-- 
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-8) Upload Sun POMs for non redistributable jars

[Trygve Laugstol (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39772 ]
 
Trygve Laugstol commented on MEV-8:
---

I'd also like to see all of these under the "java." or 
"javax." groupIds. With this it will follow our own guidelines for 
groupId naming.

> Upload Sun POMs for non redistributable jars
> 
>
>  Key: MEV-8
>  URL: http://jira.codehaus.org/browse/MEV-8
>  Project: Maven Evangelism
> Type: Task
> Reporter: Carlos Sanchez
> Assignee: Carlos Sanchez

>
>
> activation
> ejb-3.0
> jaxrpc
> jsp api
> servlet api
> jms
> javamail

-- 
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-8) Upload Sun POMs for non redistributable jars

[Carlos Sanchez (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39771 ]
 
Carlos Sanchez commented on MEV-8:
--

I'd like to see the APIs under the same group, something like "sun" for sun 
created jars or "jcp" for jsrs, instead of having one group for each api which 
will be a pain.
Anyway for m2 it shouldn't matter as they will be under javax.whatever (package 
name), am I right ?

> Upload Sun POMs for non redistributable jars
> 
>
>  Key: MEV-8
>  URL: http://jira.codehaus.org/browse/MEV-8
>  Project: Maven Evangelism
> Type: Task
> Reporter: Carlos Sanchez
> Assignee: Carlos Sanchez

>
>
> activation
> ejb-3.0
> jaxrpc
> jsp api
> servlet api
> jms
> javamail

-- 
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]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 2 (4 including POMs).
building file list ... done
jmock/distributions/
jmock/jars/
jmock/jars/jmock-20031129.200437.jar
jmock/jars/jmock-SNAPSHOT.jar
last-sync.txt
wrote 670385 bytes  read 1646 bytes  7265.20 bytes/sec
total size is 2633578377  speedup is 3918.83
building file list ... done
./
.index.txt
jaas/
jaas/jaas/
jaas/jaas/1.0.1/
jaas/jaas/1.0.1/jaas-1.0.1.pom
jaf/
jaf/activation/
jaf/activation/1.0.2/
jaf/activation/1.0.2/activation-1.0.2.pom
jca/
jca/jca/
jca/jca/1.0.0/
jca/jca/1.0.0/jca-1.0.0.pom
jca/jca/1.5/
jca/jca/1.5/jca-1.5.pom
jdbc/
jdbc/jdbc-stdext/
jdbc/jdbc-stdext/2.0/
jdbc/jdbc-stdext/2.0/jdbc-stdext-2.0.pom
jdo/
jdo/jdo/
jdo/jdo/1.0.1/
jdo/jdo/1.0.1/jdo-1.0.1.pom
jmock/jmock/20031129.200437/jmock-20031129.200437.jar
jmock/jmock/20031129.200437/jmock-20031129.200437.jar.md5
jmock/jmock/20031129.200437/jmock-20031129.200437.jar.sha1
jmock/jmock/20031129.200437/jmock-20031129.200437.pom
jmock/jmock/20031129.200437/jmock-20031129.200437.pom.md5
jmock/jmock/20031129.200437/jmock-20031129.200437.pom.sha1
jmock/jmock/SNAPSHOT/jmock-SNAPSHOT.jar
jmock/jmock/SNAPSHOT/jmock-SNAPSHOT.jar.md5
jmock/jmock/SNAPSHOT/jmock-SNAPSHOT.jar.sha1
jmock/jmock/SNAPSHOT/jmock-SNAPSHOT.pom
jmock/jmock/SNAPSHOT/jmock-SNAPSHOT.pom.md5
jmock/jmock/SNAPSHOT/jmock-SNAPSHOT.pom.sha1
jta/
jta/jta/
jta/jta/1.0.1b/
jta/jta/1.0.1b/jta-1.0.1b.pom
last-sync.txt
wrote 1140458 bytes  read 1994 bytes  1498.30 bytes/sec
total size is 3630800773  speedup is 3178.08

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MEV-8) Upload Sun POMs for non redistributable jars

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-8?page=comments#action_39766 ]
 
Brett Porter commented on MEV-8:


I have done:
activation
javamail
jdo
jca
jdbc-stdext
jta


> Upload Sun POMs for non redistributable jars
> 
>
>  Key: MEV-8
>  URL: http://jira.codehaus.org/browse/MEV-8
>  Project: Maven Evangelism
> Type: Task
> Reporter: Carlos Sanchez
> Assignee: Carlos Sanchez

>
>
> activation
> ejb-3.0
> jaxrpc
> jsp api
> servlet api
> jms
> javamail

-- 
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: (MEV-18) m2 activation pom should have groupid of jaf

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MEV-18?page=all ]
 
Brett Porter closed MEV-18:
---

Resolution: Fixed

renamed since the original pom was broken

> m2 activation pom should have groupid of jaf
> 
>
>  Key: MEV-18
>  URL: http://jira.codehaus.org/browse/MEV-18
>  Project: Maven Evangelism
> Type: Task
>   Components: Invalid POM
> Reporter: Mark Hobson

>
>
> As detailed here:
> http://maven.apache.org/reference/standard-sun-jar-names.html
> Activation should have groupId 'jaf' and artifactId 'activation'.  Also, 
> although the POM is in activation/activation, it actually has groupId and 
> artifactId of 'javamail' declared in the POM.
> Javamail will also need it's dependency updated accordingly.

-- 
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: (MAVEN-1609) touchstone test with external entities in maven.xml fails

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MAVEN-1609?page=all ]

Brett Porter updated MAVEN-1609:


Fix Version: 1.1-beta-1

> touchstone test with external entities in maven.xml fails
> -
>
>  Key: MAVEN-1609
>  URL: http://jira.codehaus.org/browse/MAVEN-1609
>  Project: maven
> Type: Bug
>   Components: core
> Versions: 1.1-beta-1
>  Environment: Maven 1.1, Win XP SP2, 
> java version "1.4.2_05"
> Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
> Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
> Reporter: Arnaud HERITIER
>  Fix For: 1.1-beta-1

>
>
> As mentioned in this thread 
> (http://marc.theaimsgroup.com/?t=11169980201&r=1&w=2) the maven 1.1 
> bootstrap fails because of a test failure in touchstone with external 
> entities in maven.xml
> The log :
> D:\Work\Dev\apache-maven-1.1\core\trunk\src\test\touchstone-build>maven -e 
> test-entity-goal
>  __  __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. @pom.currentVersion@
> DEPRECATED: the default goal should be specified in the  section of 
> project.xml instead of maven.xml
> Tentative de tÚlÚchargement de maven-model-3.0.0-SNAPSHOT.jar.
> Tentative de tÚlÚchargement de touchstone-SNAPSHOT.jar.
> Tentative de tÚlÚchargement de test-SNAPSHOT.war.
> Tentative de tÚlÚchargement de maven-model-3.0.0-SNAPSHOT.jar.
> Tentative de tÚlÚchargement de commons-jelly-tags-xml-1.1-SNAPSHOT.jar.
> Tentative de tÚlÚchargement de maven-model-3.0.0-SNAPSHOT.jar.
> DEPRECATED: the default goal should be specified in the  section of 
> project.xml instead of maven.xml
> LA CONSTRUCTION A ╚CHOU╚
> org.apache.maven.MavenException: Error reading plugin script
> at 
> org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:169)
> at 
> org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:177)
> at 
> org.apache.maven.plugin.PluginManager.readMavenXml(PluginManager.java:524)
> at 
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:596)
> at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
> at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:82)
> at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
> at 
> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
> at 
> org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109)
> at org.apache.maven.werkz.Goal.fire(Goal.java:656)
> at org.apache.maven.werkz.Goal.attain(Goal.java:592)
> at 
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693)
> at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
> at org.apache.maven.cli.App.doMain(App.java:511)
> at org.apache.maven.cli.App.main(App.java:1258)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:551)
> at com.werken.forehead.Forehead.main(Forehead.java:581)
> --- Nested Exception ---
> java.net.MalformedURLException: no protocol: entity/entity.xml
> at java.net.URL.(URL.java:537)
> at java.net.URL.(URL.java:434)
> at java.net.URL.(URL.java:383)
> at 
> org.apache.crimson.parser.ExternalEntity.getInputSource(ExternalEntity.java:92)
> at org.apache.crimson.parser.Parser2.pushReader(Parser2.java:3327)
> at 
> org.apache.crimson.parser.Parser2.externalParsedEntity(Parser2.java:3013)
> at 
> org.apache.crimson.parser.Parser2.expandEntityInContent(Parser2.java:2739)
> at 
> org.apache.crimson.parser.Parser2.maybeReferenceInContent(Parser2.java:2606)
> at org.apache.crimson.parser.Parser2.content(Parser2.java:2017)
> at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
> at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
> at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
> at 
> org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
> at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
> at 
> org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:157)
> at 
> org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:177)
> at 
> org.apache.maven.plugin.PluginManager.readMavenXml(P

[jira] Closed: (MNG-431) Error check for old style pom dependency declarations

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-431?page=all ]
 
Brett Porter closed MNG-431:


Resolution: Duplicate

> Error check for old style pom dependency declarations
> -
>
>  Key: MNG-431
>  URL: http://jira.codehaus.org/browse/MNG-431
>  Project: Maven 2
> Type: Improvement
> Versions: 2.0-alpha-2
> Reporter: Hiram Chirino

>
>
> had a dependency like:
> 
>   springframework
>   spring
>   1.1
> 
> Maven barfed like:
> java.lang.NullPointerException
> at 
> org.apache.maven.artifact.DefaultArtifact.hashCode(DefaultArtifact.java:197)
> at java.util.HashMap.hash(HashMap.java:264)
> at java.util.HashMap.put(HashMap.java:382)
> at java.util.HashSet.add(HashSet.java:194)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.createArtifacts(DefaultMavenProjectBuilder.java:475)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:283)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:237)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:153)
> at 
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:142)
> at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:314)
> at 
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:203)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:111)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:585)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
> at 
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:363)

-- 
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: (MAVEN-1609) touchstone test with external entities in maven.xml fails

[Arnaud HERITIER (JIRA)]

touchstone test with external entities in maven.xml fails
-

 Key: MAVEN-1609
 URL: http://jira.codehaus.org/browse/MAVEN-1609
 Project: maven
Type: Bug
  Components: core  
Versions: 1.1-beta-1
 Environment: Maven 1.1, Win XP SP2, 
java version "1.4.2_05"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
Reporter: Arnaud HERITIER


As mentioned in this thread 
(http://marc.theaimsgroup.com/?t=11169980201&r=1&w=2) the maven 1.1 
bootstrap fails because of a test failure in touchstone with external entities 
in maven.xml

The log :

D:\Work\Dev\apache-maven-1.1\core\trunk\src\test\touchstone-build>maven -e 
test-entity-goal
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. @pom.currentVersion@

DEPRECATED: the default goal should be specified in the  section of 
project.xml instead of maven.xml
Tentative de tÚlÚchargement de maven-model-3.0.0-SNAPSHOT.jar.
Tentative de tÚlÚchargement de touchstone-SNAPSHOT.jar.
Tentative de tÚlÚchargement de test-SNAPSHOT.war.
Tentative de tÚlÚchargement de maven-model-3.0.0-SNAPSHOT.jar.
Tentative de tÚlÚchargement de commons-jelly-tags-xml-1.1-SNAPSHOT.jar.
Tentative de tÚlÚchargement de maven-model-3.0.0-SNAPSHOT.jar.
DEPRECATED: the default goal should be specified in the  section of 
project.xml instead of maven.xml

LA CONSTRUCTION A ╚CHOU╚
org.apache.maven.MavenException: Error reading plugin script
at 
org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:169)
at 
org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:177)
at 
org.apache.maven.plugin.PluginManager.readMavenXml(PluginManager.java:524)
at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:596)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:82)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95)
at 
org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78)
at 
org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109)
at org.apache.maven.werkz.Goal.fire(Goal.java:656)
at org.apache.maven.werkz.Goal.attain(Goal.java:592)
at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.cli.App.doMain(App.java:511)
at org.apache.maven.cli.App.main(App.java:1258)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:324)
at com.werken.forehead.Forehead.run(Forehead.java:551)
at com.werken.forehead.Forehead.main(Forehead.java:581)
--- Nested Exception ---
java.net.MalformedURLException: no protocol: entity/entity.xml
at java.net.URL.(URL.java:537)
at java.net.URL.(URL.java:434)
at java.net.URL.(URL.java:383)
at 
org.apache.crimson.parser.ExternalEntity.getInputSource(ExternalEntity.java:92)
at org.apache.crimson.parser.Parser2.pushReader(Parser2.java:3327)
at 
org.apache.crimson.parser.Parser2.externalParsedEntity(Parser2.java:3013)
at 
org.apache.crimson.parser.Parser2.expandEntityInContent(Parser2.java:2739)
at 
org.apache.crimson.parser.Parser2.maybeReferenceInContent(Parser2.java:2606)
at org.apache.crimson.parser.Parser2.content(Parser2.java:2017)
at org.apache.crimson.parser.Parser2.maybeElement(Parser2.java:1691)
at org.apache.crimson.parser.Parser2.parseInternal(Parser2.java:667)
at org.apache.crimson.parser.Parser2.parse(Parser2.java:337)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLReaderImpl.java:448)
at javax.xml.parsers.SAXParser.parse(SAXParser.java:345)
at 
org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:157)
at 
org.apache.maven.plugin.JellyScriptHousing.parse(JellyScriptHousing.java:177)
at 
org.apache.maven.plugin.PluginManager.readMavenXml(PluginManager.java:524)
at 
org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:596)
at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
at org.apache.maven.jelly.tags.maven.MavenTag.doTag(MavenTag.java:82)
at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247)
at org.apache.commons.

[maven2 build - SUCCESS] Thu May 26 18:07:04 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050526.180704.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050526.180704.txt

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: HSQLDB locking when using tomcat plugin

[Carlos Sanchez]

Try adding root under properties.
And if it works read http://maven.apache.org/faq.html#classloader-property

On 5/26/05, Sebastien Arbogast <[EMAIL PROTECTED]> wrote:
> > Have you added the hsql driver jar to project.xml?
> 
> Yep :
> 
> 
> hsqldb
> hsqldb
> 1.7.3.3
> jar
> 
> true
> 
> 
> 
> --
> Sebastien ARBOGAST
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: HSQLDB locking when using tomcat plugin

[Carlos Sanchez]

Have you added the hsql driver jar to project.xml?

On 5/26/05, Sebastien Arbogast <[EMAIL PROTECTED]> wrote:
> > I think so, but probably the hsql server is not listening for
> > conections after tomcat is stopped.
> 
> Right. Si I tried to configure it as a preGoal for tomcat:stop :
> 
> 
>  url="jdbc:hsqldb:file:C:\dev\myapp/target/webapp/WEB-INF/db/myappdb"
> userid="sa" password=""> SHUTDOWN; 
> 
> 
> But then I got the following exception when executing "maven tomcat:stop" :
> 
> C:\dev\pfe\schaman>maven tomcat:stop
>  __  __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
> 
> [echo] Found context file C:\dev\myapp/target/webapp/META-INF/context.
> xml
> [echo] /myapp file:C:\dev\myapp/target/webapp/META-INF/context.xml
> 
> BUILD FAILED
> File.. C:\dev\myapp\maven.xml
> Element... sql
> Line.. 128
> Column 28
> Class Not Found: JDBC driver org.hsqldb.jdbcDriver could not be loaded
> Total time: 5 seconds
> Finished at: Thu May 26 17:44:29 CDT 2005
> 
> Any idea ? (I knew it could eventually fall back to a Maven issue :-P)
> 
> --
> Sebastien ARBOGAST
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: HSQLDB locking when using tomcat plugin

[Carlos Sanchez]

I think so, but probably the hsql server is not listening for
conections after tomcat is stopped.

On 5/26/05, Sebastien Arbogast <[EMAIL PROTECTED]> wrote:
> 2005/5/26, Carlos Sanchez <[EMAIL PROTECTED]>:
> > You can write a Maven goal in maven.xml that issues the SHUTDOWN
> > command to the database (see sql ant task) , so you can call maven
> > shutdown and close the db.
> >
> >  > driver="org.database.jdbcDriver"
> > url="jdbc:database-url"
> > userid="sa"
> > password="pass"
> > >
> > SHUTDOWN;
> > 
> >
> 
> Oh Carlos you give me hope again ! Is it possible to configure that as
> a postGoal for tomcat:stop for example ?
> 
> --
> Sebastien ARBOGAST
>

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MNG-431) Error check for old style pom dependency declarations

[Hiram Chirino (JIRA)]

Error check for old style pom dependency declarations
-

 Key: MNG-431
 URL: http://jira.codehaus.org/browse/MNG-431
 Project: Maven 2
Type: Improvement
Versions: 2.0-alpha-2
Reporter: Hiram Chirino


had a dependency like:

  springframework
  spring
  1.1

Maven barfed like:
java.lang.NullPointerException
at 
org.apache.maven.artifact.DefaultArtifact.hashCode(DefaultArtifact.java:197)
at java.util.HashMap.hash(HashMap.java:264)
at java.util.HashMap.put(HashMap.java:382)
at java.util.HashSet.add(HashSet.java:194)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.createArtifacts(DefaultMavenProjectBuilder.java:475)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:283)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:237)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFile(DefaultMavenProjectBuilder.java:153)
at 
org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:142)
at org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:314)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:203)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:111)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:246)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at 
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at 
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:303)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:243)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:416)
at org.codehaus.classworlds.Launcher.main(Launcher.java:363)


-- 
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: r178691 - /maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java

[jdcasey]

Author: jdcasey
Date: Thu May 26 14:12:06 2005
New Revision: 178691

URL: http://svn.apache.org/viewcvs?rev=178691&view=rev
Log:
added null checks for everything that's in the hashCode() method, to try to 
avoid cryptic errors, at least until the xml validation improves.

Modified:

maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java

Modified: 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java?rev=178691&r1=178690&r2=178691&view=diff
==
--- 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java
 (original)
+++ 
maven/components/trunk/maven-artifact/src/main/java/org/apache/maven/artifact/DefaultArtifact.java
 Thu May 26 14:12:06 2005
@@ -71,10 +71,27 @@
 throw new NullPointerException( "Artifact type cannot be null." );
 }
 
+if( groupId == null )
+{
+throw new NullPointerException( "Artifact groupId cannot be null." 
);
+}
+
 this.groupId = groupId;
+
 
+if( artifactId == null )
+{
+throw new NullPointerException( "Artifact artifactId cannot be 
null." );
+}
+
 this.artifactId = artifactId;
+
 
+if( version == null )
+{
+throw new NullPointerException( "Artifact version cannot be null." 
);
+}
+
 this.version = version;
 
 this.type = type;



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 0 (0 including POMs).
building file list ... done
last-sync.txt
wrote 639735 bytes  read 42 bytes  5222.67 bytes/sec
total size is 2633573959  speedup is 4116.39
building file list ... done
.index.txt
last-sync.txt
wrote 1104661 bytes  read 58 bytes  1867.66 bytes/sec
total size is 3630792898  speedup is 3286.62

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Created: (MPECLIPSE-92) Setting relative path value to "maven.eclipse.output.dir" generates wrong absolute classpath entry

[Yang Li (JIRA)]

Setting relative path value to "maven.eclipse.output.dir" generates wrong 
absolute classpath entry
--

 Key: MPECLIPSE-92
 URL: http://jira.codehaus.org/browse/MPECLIPSE-92
 Project: maven-eclipse-plugin
Type: Bug
Versions: 1.9
Reporter: Yang Li


In a J2EE project environment, the master project is "sample-project", the web 
project is "sample-project-web"

If set the property
maven.eclipse.output.dir=web-content/WEB-INF/classes 
in the sample-project-web project

The result .classpath created by the Eclipse plugin has the following entry:

  
  

This is wrong. The path value should be a relative path.

Solution:

change the following line in the classpath.jelly 

from:

  
  
  
  
  
  
  Setting default output directory to ${outputDir}

to

  
  
  

  
  
  Setting default output directory to ${outputDir}

With a requirement that the maven.eclipse.output.dir should always be set as a 
relative path. This requirement should be put in the plugin properties doc.


-- 
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: PVCS and Maven

[Richardson, Simon (Treasury)]

Dan

I'm new to maven + svn.  I do have http access, so wondered if you could
help with command to issue?

I've tried:

maven -e scm:checkout-project -Dmaven.repo.local=h:\.maven\repository
-Dmaven.scm.url=scm:svn:http://svn.apache.org/repos/asf/maven/scm/trunk 

And I am getting the following exception:

You must specify maven.scm.cvs.module

Can't understand why it states I need the "cvs" module?

Regards

Simon

> -Original Message-
> From: dan tran [mailto:[EMAIL PROTECTED]
> Sent: 26 May 2005 17:31
> To: scm-dev@maven.apache.org
> Subject: Re: PVCS and Maven
> 
> 
> Richard,
> 
> svn uses http protocol, so if your comp allows internet 
> access you should be
> able to retreive the source.
> 
> About doc, I see none, but api is quite clean.  If you are familiar
> with either CVS and SVN, looking at the provider implementation will
> give you some starting point.
> 
> 

"MMS " made the following annotations.
--
For more information on HBOS Treasury Services, please visit 
http://www.HBOSTS.com

Or for details of our online FX & Deposit services, please go to 
http://www.HBOSdeal.com

HBOS Treasury Services plc is part of the HBOS Group, which also includes 
Halifax plc and Bank of Scotland.
Registered Office: 33 Old Broad Street, London EC2N 1HZ. Registered No. 
2692890. Registered in England.
Authorised and regulated by the Financial Services Authority.

The information contained in this message is confidential and is intended for 
the addressee only. If you have received this message in error or there are any 
problems please notify the originator immediately. The unauthorised use, 
disclosure, copying or alteration of this message is strictly forbidden. This 
mail and any attachments have been scanned for viruses prior to leaving the 
HBOS Treasury Services plc network. HBOS Treasury Services plc will not be 
liable for direct, special, indirect or consequential damages arising from 
alteration of the contents of this message by a third party or as a result of 
any virus being passed on.

HBOS Treasury Services plc reserves the right to monitor and record e-mail 
messages sent to and from this address for the purposes of investigating or 
detecting any unauthorised use of its system and ensuring its effective 
operation.
==

Re: starteam changelog's dateformat issue

[dan tran]

It looks to me StarTeam does not like the default format of en_US
(M/d/yy h:mm a) and decide to change to "M/d/yy h:mm:ss a z" which is
the correct approach.


-D

On 5/26/05, Trygve Laugstøl <[EMAIL PROTECTED]> wrote:
> On Wed, May 25, 2005 at 08:59:23PM -0700, dan tran wrote:
> > Folks,
> >
> > starteam history command ouput has unexpected date format
> > which the default SimpleDateTimeFormat() not able to handle it
> >
> > here is a sample output
> >
> > History for: project.xml
> > Description:
> > Locked by:
> > Status: Modified
> > 
> > Revision: 2 View: driver Branch Revision: 1.1
> > Author: build Date: 5/25/05 4:53:18 PM PDT
> >
> >
> > If If I hardcode a SimpleDateTimeFormat according to this format, it
> > will work, but affraid it may break on other locale
> >
> > Any suggestion?
> 
> The date is really necessary information so we need to be able to read it.
> It's easy to make SimpleDateFormat not use the system locale but rather
> som other hardcoded version but it's possible that starteam is using the 
> system
> local so the format can change on evey platform.
> 
> If so we need to start gathering this information so we can map the format
> starteam is using to a Java locale.
> 
> >
> >
> > -Dan
> 
> 
> BodyID:26041251.2.n.logpart (stored separately)
> 
>

Re: Design Get Together - Thu May 26 12:00 UTC - All Welcome

[Brett Porter]

http://docs.codehaus.org/display/MAVEN/IRC+Log+Design+Discussion+26+May+2005

There's about 3 hours worth there, and we got through half the topics. 
All will be incorporated into the design docs, so there is no need to 
trawl this unless you are particularly interested in the decision making 
process. The main documents should also capture some of the reasoning 
certain choices were made.


Thanks to everyone who dropped in and listened in - it was great to see 
there was some interest. We will do this again for the remaining 
documents in the very near future.


- Brett

Brett Porter wrote:

We're there now, if anyone wants to join in. It is available over HTTP 
also:

http://irc.codehaus.org/
in
#maven.

Logs to follow.

- Brett




-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Updated: (MNG-430) NPE in repoclean

[Anatol Pomozov (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-430?page=all ]

Anatol Pomozov updated MNG-430:
---

Attachment: artifact.patch

> NPE in repoclean
> 
>
>  Key: MNG-430
>  URL: http://jira.codehaus.org/browse/MNG-430
>  Project: Maven 2
> Type: Bug
>   Components: repository-tools
> Versions: 2.0-alpha-3
> Reporter: Anatol Pomozov
>  Attachments: artifact.patch
>
>
> There was wrong logic in 
> src/main/java/org/apache/maven/tools/repoclean/artifact/metadata/ProjectMetadata.java
>  it returns null and it causes NPE. It should return information from 
> artifact. 
> Simple patch fixed this bug.

-- 
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-430) NPE in repoclean

[Anatol Pomozov (JIRA)]

NPE in repoclean


 Key: MNG-430
 URL: http://jira.codehaus.org/browse/MNG-430
 Project: Maven 2
Type: Bug
  Components: repository-tools  
Versions: 2.0-alpha-3
Reporter: Anatol Pomozov
 Attachments: artifact.patch

There was wrong logic in 
src/main/java/org/apache/maven/tools/repoclean/artifact/metadata/ProjectMetadata.java
 it returns null and it causes NPE. It should return information from artifact. 
Simple patch fixed this bug.

-- 
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]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 0 (0 including POMs).
building file list ... done
last-sync.txt
wrote 639735 bytes  read 42 bytes  12924.79 bytes/sec
total size is 2633573959  speedup is 4116.39
building file list ... done
.index.txt
last-sync.txt
wrote 1104661 bytes  read 58 bytes  5482.48 bytes/sec
total size is 3630792898  speedup is 3286.62

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 0 (0 including POMs).
building file list ... done
last-sync.txt
wrote 639735 bytes  read 42 bytes  3143.87 bytes/sec
total size is 2633573959  speedup is 4116.39
building file list ... done
.index.txt
last-sync.txt
wrote 1104661 bytes  read 70 bytes  1141.84 bytes/sec
total size is 3630792898  speedup is 3286.59

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[maven2 build - SUCCESS] Thu May 26 08:07:00 EDT 2005

[jvanzyl]

Distribution:
http://www.codehaus.org/~maven/m2/m2-20050526.080700.tar.gz

Log:
http://www.codehaus.org/~maven/m2-build-logs/m2-build-log-20050526.080700.txt

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: JIRA proposal for plugins

[Jason van Zyl]

On Thu, 2005-05-26 at 16:32 +1000, Brett Porter wrote:
> Hi,
> 
> Given the resounding mess that resulted from giving each plugin its own 
> project in JIRA for m1, I'd like to propose the following for m2:
> 
> - create a maven-plugins project
> - add new plugins as components
> - add a "component version" field that is free text.
> 
> Upside:
> - more manageable
> - can still query per plugin/per version as long as the text is well formed
> 
> Downside:
> - can't use roadmap etc
> - can't bulk change version for scheduling
> 
> In general, I don't think this is a problem - I think that plugins tend 
> to have very few bugs assigned to them at any given time if they are 
> being looked after (xdoc is an exception as it is basically a product 
> unto itself in m1).
> 
> Thoughts? Should we move towards this in m1 too, or just let them wind 
> down over time?

We could also just get our own instance of JIRA. I'm sure we could swing
that.

> - Brett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

happiness is like a butterfly: the more you chase it, the more it will
elude you, but if you turn your attention to other things, it will come
and sit softly on your shoulder ...

 -- Thoreau 


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: Design Get Together - Thu May 26 12:00 UTC - All Welcome

[Brett Porter]

We're there now, if anyone wants to join in. It is available over HTTP also:
http://irc.codehaus.org/
in
#maven.

Logs to follow.

- Brett

Brett Porter wrote:


Hello Maven folks,

We're about to finalise the major design tasks for Maven 2.0 so that 
we can freeze the feature set and charge toward an August release.


To that end, we will be holding an IRC discussion on #maven at 
irc.codehaus.org to work through them one by one in real time. Anyone 
interested in the development of Maven is welcome to come along and 
listen in, or give feedback. The discussion will be logged and posted 
afterwards for the benefit of those that can't make it.


All documents have been drafted here:
http://docs.codehaus.org/display/MAVEN/Maven+2.0+Design+Documents
Please feel free to read and comment on them in advance.

We will probably need to have another go at this at a later time, but 
this should give it a decent start.


To get the meeting time in your local time:
http://www.timeanddate.com/worldclock/fixedtime.html?year=2005&month=5&day=26&hour=12&min=0&sec=0 



Cheers,
Brett


-
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]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 14 (28 including POMs).
building file list ... done
./
last-sync.txt
org.apache.maven.scm/
org.apache.maven.scm/jars/
org.apache.maven.scm/jars/maven-scm-api-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-client-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-provider-clearcase-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-provider-cvs-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-provider-local-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-provider-perforce-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-provider-starteam-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-provider-svn-1.0-alpha-1.jar
org.apache.maven.scm/jars/maven-scm-test-1.0-alpha-1.jar
org.apache.maven.scm/poms/
org.apache.maven.scm/poms/maven-scm-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-api-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-client-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-provider-clearcase-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-provider-cvs-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-provider-local-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-provider-perforce-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-provider-starteam-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-provider-svn-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-providers-1.0-alpha-1.pom
org.apache.maven.scm/poms/maven-scm-test-1.0-alpha-1.pom
servicemix/distributions/
servicemix/poms/
servicemix/poms/servicemix-1.0-SNAPSHOT.pom
xdoclet-plugins/jars/
xdoclet-plugins/jars/xdoclet-plugin-hibernate-1.0.1-SNAPSHOT.jar
wrote 1026809 bytes  read 2710 bytes  7487.41 bytes/sec
total size is 2633573959  speedup is 2558.06
building file list ... done
.index.txt
last-sync.txt
org/apache/maven/scm/maven-scm/
org/apache/maven/scm/maven-scm-api/1.0-alpha-1/maven-scm-api-1.0-alpha-1.jar
org/apache/maven/scm/maven-scm-api/1.0-alpha-1/maven-scm-api-1.0-alpha-1.jar.md5
org/apache/maven/scm/maven-scm-api/1.0-alpha-1/maven-scm-api-1.0-alpha-1.jar.sha1
org/apache/maven/scm/maven-scm-api/1.0-alpha-1/maven-scm-api-1.0-alpha-1.pom
org/apache/maven/scm/maven-scm-api/1.0-alpha-1/maven-scm-api-1.0-alpha-1.pom.md5
org/apache/maven/scm/maven-scm-api/1.0-alpha-1/maven-scm-api-1.0-alpha-1.pom.sha1
org/apache/maven/scm/maven-scm-client/1.0-alpha-1/maven-scm-client-1.0-alpha-1.jar
org/apache/maven/scm/maven-scm-client/1.0-alpha-1/maven-scm-client-1.0-alpha-1.jar.md5
org/apache/maven/scm/maven-scm-client/1.0-alpha-1/maven-scm-client-1.0-alpha-1.jar.sha1
org/apache/maven/scm/maven-scm-client/1.0-alpha-1/maven-scm-client-1.0-alpha-1.pom
org/apache/maven/scm/maven-scm-client/1.0-alpha-1/maven-scm-client-1.0-alpha-1.pom.md5
org/apache/maven/scm/maven-scm-client/1.0-alpha-1/maven-scm-client-1.0-alpha-1.pom.sha1
org/apache/maven/scm/maven-scm-provider-clearcase/1.0-alpha-1/maven-scm-provider-clearcase-1.0-alpha-1.jar
org/apache/maven/scm/maven-scm-provider-clearcase/1.0-alpha-1/maven-scm-provider-clearcase-1.0-alpha-1.jar.md5
org/apache/maven/scm/maven-scm-provider-clearcase/1.0-alpha-1/maven-scm-provider-clearcase-1.0-alpha-1.jar.sha1
org/apache/maven/scm/maven-scm-provider-clearcase/1.0-alpha-1/maven-scm-provider-clearcase-1.0-alpha-1.pom
org/apache/maven/scm/maven-scm-provider-clearcase/1.0-alpha-1/maven-scm-provider-clearcase-1.0-alpha-1.pom.md5
org/apache/maven/scm/maven-scm-provider-clearcase/1.0-alpha-1/maven-scm-provider-clearcase-1.0-alpha-1.pom.sha1
org/apache/maven/scm/maven-scm-provider-cvs/1.0-alpha-1/maven-scm-provider-cvs-1.0-alpha-1.jar
org/apache/maven/scm/maven-scm-provider-cvs/1.0-alpha-1/maven-scm-provider-cvs-1.0-alpha-1.jar.md5
org/apache/maven/scm/maven-scm-provider-cvs/1.0-alpha-1/maven-scm-provider-cvs-1.0-alpha-1.jar.sha1
org/apache/maven/scm/maven-scm-provider-cvs/1.0-alpha-1/maven-scm-provider-cvs-1.0-alpha-1.pom
org/apache/maven/scm/maven-scm-provider-cvs/1.0-alpha-1/maven-scm-provider-cvs-1.0-alpha-1.pom.md5
org/apache/maven/scm/maven-scm-provider-cvs/1.0-alpha-1/maven-scm-provider-cvs-1.0-alpha-1.pom.sha1
org/apache/maven/scm/maven-scm-provider-local/1.0-alpha-1/maven-scm-provider-local-1.0-alpha-1.jar
org/apache/maven/scm/maven-scm-provider-local/1.0-alpha-1/maven-scm-provider-local-1.0-alpha-1.jar.md5
org/apache/maven/scm/maven-scm-provider-local/1.0-alpha-1/maven-scm-provider-local-1.0-alpha-1.jar.sha1
org/apache/maven/scm/maven-scm-provider-local/1.0-alpha-1/maven-scm-provider-local-1.0-alpha-1.pom
org/apache/maven/scm/maven-scm-provider-local/1.0-alpha-1/maven-scm-provider-local-1.0-alpha-1.pom.md5
org/apache/maven/scm/maven-scm-provider-local/1.0-alpha-1/maven-scm-provider-local-1.0-alpha-1.pom.sha1
org/apache/maven/scm/maven-scm-provider-perforce/1.0-alpha-1/maven-scm-provider-perforce-1.0-alpha-1.jar
org/apache/maven/scm/maven-scm-provider-perforce/1.0-alpha-1/

Re: starteam changelog's dateformat issue

[Trygve =?iso-8859-1?Q?Laugst=F8l?=]

On Wed, May 25, 2005 at 08:59:23PM -0700, dan tran wrote:
> Folks,
> 
> starteam history command ouput has unexpected date format
> which the default SimpleDateTimeFormat() not able to handle it
> 
> here is a sample output
> 
> History for: project.xml
> Description:
> Locked by:
> Status: Modified
> 
> Revision: 2 View: driver Branch Revision: 1.1
> Author: build Date: 5/25/05 4:53:18 PM PDT
> 
> 
> If If I hardcode a SimpleDateTimeFormat according to this format, it
> will work, but affraid it may break on other locale
> 
> Any suggestion?

The date is really necessary information so we need to be able to read it.
It's easy to make SimpleDateFormat not use the system locale but rather
som other hardcoded version but it's possible that starteam is using the system
local so the format can change on evey platform. 

If so we need to start gathering this information so we can map the format
starteam is using to a Java locale.

> 
> 
> -Dan


signature.asc
Description: Digital signature

[jira] Created: (CONTINUUM-165) goal null after editing a project

[=?ANSI_X3.4-1968?Q?Aleksander_Blomsk=3Fld_=28JIRA=29?=]

goal null after editing a project
-

 Key: CONTINUUM-165
 URL: http://jira.codehaus.org/browse/CONTINUUM-165
 Project: Continuum
Type: Bug
Versions: 1.0-alpha-2
Reporter: Aleksander Blomskøld


If I go to the edit-page and press submit (I don't really need to edit 
anything) this error is printed at console:

2005-05-26 11:29:45,085 [PoolThread-0] ERROR VelocityComponent - RHS of #set 
statement is null. Context will not be modified. screens/Summary.vm [line 1, 
column 1]

A null-goal (which is not visible at the edit page) is added when I try to 
build the project:

2005-05-26 11:36:12,167 [Thread-4] INFO  ShellCommandHelper - Executing: maven 
null clean:clean jar:install


-- 
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: (MPDASHBOARD-26) JUnit pass rate no longer showing

[Vincent Massol (JIRA)]

 [ http://jira.codehaus.org/browse/MPDASHBOARD-26?page=all ]

Vincent Massol updated MPDASHBOARD-26:
--

Version: (was: 1.9)
 1.8

> JUnit pass rate no longer showing
> -
>
>  Key: MPDASHBOARD-26
>  URL: http://jira.codehaus.org/browse/MPDASHBOARD-26
>  Project: maven-dashboard-plugin
> Type: Bug
> Versions: 1.8
>  Environment: Maven 1.0.2
> Dashboard 1.9
> Reporter: Wim Deblauwe
> Priority: Blocker

>
>
> JUnit passrates are no longer showing when using dashboard version
> 1.9. I traced the problem down to the JUnit aggregator. It contains
> these linen:
>  
>
>nr of tests: ${nbTests}
>
>  
>  
>%
>
>
>  
>
>  
> The problem is that the xml file is being parsed after the nr of unit
> tests has been calculated (using the $doc variable, but it is not
> initialized yet). The solution: move the parsing of the xml file
> higher, like this:
>  
>  
>
>nr of tests: ${nbTests}
>
>  
>%
>
>
>  
>
>  

-- 
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: (MPDASHBOARD-26) JUnit pass rate no longer showing

[Wim Deblauwe (JIRA)]

JUnit pass rate no longer showing
-

 Key: MPDASHBOARD-26
 URL: http://jira.codehaus.org/browse/MPDASHBOARD-26
 Project: maven-dashboard-plugin
Type: Bug
Versions: 1.9
 Environment: Maven 1.0.2
Dashboard 1.9
Reporter: Wim Deblauwe
Priority: Blocker


JUnit passrates are no longer showing when using dashboard version
1.9. I traced the problem down to the JUnit aggregator. It contains
these linen:

 
   
   nr of tests: ${nbTests}
   
 
 
   %
   
   
 
   
 

The problem is that the xml file is being parsed after the nr of unit
tests has been calculated (using the $doc variable, but it is not
initialized yet). The solution: move the parsing of the xml file
higher, like this:

 
 
   
   nr of tests: ${nbTests}
   
 
   %
   
   
 
   
 

-- 
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: (CONTINUUM-154) set expiry on pages

[Trygve Laugstol (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-154?page=comments#action_39747 
]
 
Trygve Laugstol commented on CONTINUUM-154:
---

This is probably related to using GET requests, POST should probably improve 
this. But this issue is still something that we should think about in Summit.

> set expiry on pages
> ---
>
>  Key: CONTINUUM-154
>  URL: http://jira.codehaus.org/browse/CONTINUUM-154
>  Project: Continuum
> Type: Improvement
>   Components: continuum-web
> Reporter: Brett Porter
>  Fix For: 1.0-beta-1

>
>
> maybe I'm imagining it, but it seems some pages are not always coming back 
> with the right info (eg, hitting build came back with checking out again, 
> refresh showed build)
> NEed to send back expiry and cache control headers for the dynamic pages?

-- 
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: (MEV-19) Missing pom for servletapi:servlet:2.4

[Anatol Pomozov (JIRA)]

Missing pom for servletapi:servlet:2.4
--

 Key: MEV-19
 URL: http://jira.codehaus.org/browse/MEV-19
 Project: Maven Evangelism
Type: Bug
Reporter: Anatol Pomozov


Downloading: 
http://repo1.maven.org/maven2/servletapi/servlet/2.4/servlet-2.4.pom
[WARNING] Unable to get resource from repository http://repo1.maven.org/maven2
[INFO] 

[INFO] BUILD FAILURE
[INFO] 

[INFO] Main Error:
  Unable to download the artifact from any repository
  servletapi:servlet:2.4:pom

from the specified remote repositories:
  http://repo1.maven.org/maven2

Root error:
  Unable to download the artifact from any repository

-- 
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]

results of synchronize

[maven]

Syncing Apache Software Foundation
Syncing Codehaus
Syncing Maven Plugins @ SourceForge
Syncing Mortbay Consulting
Syncing Open Symphony
Syncing OS Java
[INFO] Actual number of artifacts rewritten: 5 (10 including POMs).
building file list ... done
activemq/distributions/
last-sync.txt
wrote 639006 bytes  read 42 bytes  4190.48 bytes/sec
total size is 2633366423  speedup is 4120.76
building file list ... done
.index.txt
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.pom
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.pom.md5
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.pom.sha1
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.zip
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.zip.md5
activemq/activemq-jmeter/3.1-SNAPSHOT/activemq-jmeter-3.1-SNAPSHOT.zip.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.tar.gz
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.tar.gz.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.tar.gz.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.zip
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.zip.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT-src.zip.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.pom
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.pom.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.pom.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.tar.gz
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.tar.gz.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.tar.gz.sha1
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.zip
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.zip.md5
activemq/activemq/3.1-SNAPSHOT/activemq-3.1-SNAPSHOT.zip.sha1
last-sync.txt
wrote 25915857 bytes  read 222346 bytes  30588.89 bytes/sec
total size is 3628588779  speedup is 138.82

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (CONTINUUM-148) Allow file:// urls when adding POMs

[Trygve Laugstol (JIRA)]

 [ http://jira.codehaus.org/browse/CONTINUUM-148?page=comments#action_39746 
]
 
Trygve Laugstol commented on CONTINUUM-148:
---

Yes, I'm definitely +1 for using Wagon. Makes configuring username/passwords 
and proxies very easy for users. It also makes it possible for administrators 
to make a special "continuum" account in proxies and configure that without 
giving access to all deveopers.

> Allow file:// urls when adding POMs
> ---
>
>  Key: CONTINUUM-148
>  URL: http://jira.codehaus.org/browse/CONTINUUM-148
>  Project: Continuum
> Type: Bug
> Reporter: Jason van Zyl
>  Fix For: 1.0-alpha-3

>
>
> When turning on the URL validator I made the default schemes http/https/ftp 
> and disallowed file which is a problem.

-- 
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] Closed: (MNG-359) support project inheritence with flat project layout

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-359?page=all ]
 
Brett Porter closed MNG-359:


Fix Version: (was: 2.0-beta-1)
 2.0-alpha-3
 Resolution: Fixed

ok, based on comments it appears that allowing ".." in the modules section is 
all that is needed. Done.

> support project inheritence with flat project layout
> 
>
>  Key: MNG-359
>  URL: http://jira.codehaus.org/browse/MNG-359
>  Project: Maven 2
> Type: Wish
>   Components: maven-core
> Versions: 2.0-alpha-1
> Reporter: Ryan Sonnek
> Priority: Critical
>  Fix For: 2.0-alpha-3
>  Attachments: was5.1flatmavenstructure.zip
>
>
> the project inheritence does not currently support projects that are laid out 
> with a "flat" directory structure.
> ex:
> --/my-project-root/
> pom.xml  (base pom)
> --/my-subproject-one/
> pom.xml (child pom)
> original thread on mailing list:  
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111442037703037&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]

svn commit: r178621 - /maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultMaven.java

[brett]

Author: brett
Date: Thu May 26 01:40:05 2005
New Revision: 178621

URL: http://svn.apache.org/viewcvs?rev=178621&view=rev
Log:
PR: MNG-359
Allow .. in module names to support a flat layout for eclipse

Modified:

maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultMaven.java

Modified: 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultMaven.java
URL: 
http://svn.apache.org/viewcvs/maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultMaven.java?rev=178621&r1=178620&r2=178621&view=diff
==
--- 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultMaven.java
 (original)
+++ 
maven/components/trunk/maven-core/src/main/java/org/apache/maven/DefaultMaven.java
 Thu May 26 01:40:05 2005
@@ -214,11 +214,6 @@
 for ( Iterator i = project.getModules().iterator(); 
i.hasNext(); )
 {
 String name = (String) i.next();
-if ( name.indexOf( ".." ) >= 0 )
-{
-String message = "Illegal module name: " + name + " 
(cannot contain path characters)";
-throw new ReactorException( message );
-}
 moduleFiles.add( new File( basedir, name + "/pom.xml" ) );
 }
 



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

[jira] Commented: (MNG-359) support project inheritence with flat project layout

[J. Matthew Pryor (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-359?page=comments#action_39744 ]
 
J. Matthew Pryor commented on MNG-359:
--

The requirement is really simple. Eclipse does not allow projects to contain 
other projects and I like having my master project POM accesible from eclipse; 
so I normally create an eclipse project per maven project. This works really 
well for maven1.
How would I be able to edit all my maven2 project in Eclipse with the 'no flat 
layout' restriction?

> support project inheritence with flat project layout
> 
>
>  Key: MNG-359
>  URL: http://jira.codehaus.org/browse/MNG-359
>  Project: Maven 2
> Type: Wish
>   Components: maven-core
> Versions: 2.0-alpha-1
> Reporter: Ryan Sonnek
> Priority: Critical
>  Fix For: 2.0-beta-1
>  Attachments: was5.1flatmavenstructure.zip
>
>
> the project inheritence does not currently support projects that are laid out 
> with a "flat" directory structure.
> ex:
> --/my-project-root/
> pom.xml  (base pom)
> --/my-subproject-one/
> pom.xml (child pom)
> original thread on mailing list:  
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111442037703037&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] Updated: (MPCHANGELOG-47) CVS log issue with CVSNT & maven-changelog-plugin

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MPCHANGELOG-47?page=all ]

Brett Porter updated MPCHANGELOG-47:


Fix Version: 1.8
Environment: 
Windows XP
Maven 1.0
maven-changelog-plugin 1.7.1
scm:ssh:...
TortoiseCVS-1.8.3

  was:
Windows XP
Maven 1.0
maven-changelog-plugin 1.7.1
scm:ssh:...
TortoiseCVS-1.8.3

Description: 
Using the command displayed while useing the changelog plugin, I can not obtain 
the log.  The fix is to add quotes around the dates specified.

SCM Command Line[0]: cvs
SCM Command Line[1]: -d
SCM Command Line[2]: :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository
SCM Command Line[3]: log
SCM Command Line[4]: -d 2004-09-30<2004-10-31

so that the command line goes from 

this: cvs -d :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository log -d 
2004-09-30<2004-10-31

to this: cvs -d :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository log -d 
"2004-09-30<2004-10-31"

  was:
Using the command displayed while useing the changelog plugin, I can not obtain 
the log.  The fix is to add quotes around the dates specified.

SCM Command Line[0]: cvs
SCM Command Line[1]: -d
SCM Command Line[2]: :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository
SCM Command Line[3]: log
SCM Command Line[4]: -d 2004-09-30<2004-10-31

so that the command line goes from 

this: cvs -d :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository log -d 
2004-09-30<2004-10-31

to this: cvs -d :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository log -d 
"2004-09-30<2004-10-31"


> CVS log issue with CVSNT & maven-changelog-plugin
> -
>
>  Key: MPCHANGELOG-47
>  URL: http://jira.codehaus.org/browse/MPCHANGELOG-47
>  Project: maven-changelog-plugin
> Type: Bug
> Versions: 1.7.1
>  Environment: Windows XP
> Maven 1.0
> maven-changelog-plugin 1.7.1
> scm:ssh:...
> TortoiseCVS-1.8.3
> Reporter: Kevin Dosey
>  Fix For: 1.8

>
> Original Estimate: 1 hour
> Remaining: 1 hour
>
> Using the command displayed while useing the changelog plugin, I can not 
> obtain the log.  The fix is to add quotes around the dates specified.
> SCM Command Line[0]: cvs
> SCM Command Line[1]: -d
> SCM Command Line[2]: :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository
> SCM Command Line[3]: log
> SCM Command Line[4]: -d 2004-09-30<2004-10-31
> so that the command line goes from 
> this: cvs -d :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository log -d 
> 2004-09-30<2004-10-31
> to this: cvs -d :ssh:xxx.xxx.xxx.xxx:/usr/local/cvsrepository log -d 
> "2004-09-30<2004-10-31"

-- 
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: (MPCHANGELOG-62) Inconsistent use of repositoryConnection and repositoryDeveloperConnectio

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MPCHANGELOG-62?page=all ]

Brett Porter updated MPCHANGELOG-62:


Fix Version: 1.8
Description: 
The scm plugin uses developerConnection and the repositoryConnection but the 
report plugins like changelog, file-activity, developer-activity perform the 
test the other way round.

The report plugins should use the scm plugin test order ...


  Using connection: ${pom.repository.developerConnection}
  

  

  
  


  Using connection: ${pom.repository.connection}
  

 
Not 

  ${pom.repository.connection}

${pom.repository.developerConnection}


  was:
The scm plugin uses developerConnection and the repositoryConnection but the 
report plugins like changelog, file-activity, developer-activity perform the 
test the other way round.

The report plugins should use the scm plugin test order ...


  Using connection: ${pom.repository.developerConnection}
  

  

  
  


  Using connection: ${pom.repository.connection}
  

 
Not 

  ${pom.repository.connection}

${pom.repository.developerConnection}



> Inconsistent use of repositoryConnection and repositoryDeveloperConnectio
> -
>
>  Key: MPCHANGELOG-62
>  URL: http://jira.codehaus.org/browse/MPCHANGELOG-62
>  Project: maven-changelog-plugin
> Type: Bug
>  Environment: All
> Reporter: Martin West
>  Fix For: 1.8

>
>
> The scm plugin uses developerConnection and the repositoryConnection but the 
> report plugins like changelog, file-activity, developer-activity perform the 
> test the other way round.
> The report plugins should use the scm plugin test order ...
> 
>   Using connection: ${pom.repository.developerConnection}
>   
> 
>   
>   
> 
>   
> 
> 
>   Using connection: ${pom.repository.connection}
>   
> 
>  
> Not 
>   ${pom.repository.connection}
> 
> ${pom.repository.developerConnection}
> 

-- 
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: (MPSCM-53) NullPointerException when setting checkout dir

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MPSCM-53?page=all ]

Brett Porter updated MPSCM-53:
--

Fix Version: 1.5

> NullPointerException when setting checkout dir
> --
>
>  Key: MPSCM-53
>  URL: http://jira.codehaus.org/browse/MPSCM-53
>  Project: maven-scm-plugin
> Type: Bug
> Versions: 1.5
>  Environment: Maven 1.02 with scm plugin 1.5-beta-3 under Windows XP and 
> cygwin.  I am also using the cygwin subversion package.
> Reporter: Alex Soto
>  Fix For: 1.5

>
>
> Checking out WITHOUT setting the checkout dir property works.  Setting the 
> checkout dir property reports a NullPointerException.
> Notice that I am using svn+ssh.  I have an ssh key setup so I do not have to 
> enter a password to login.
> $ maven -e scm:checkout 
> -Dmaven.scm.url=scm:svn:svn+ssh://svn.XXX.com/var/svn/itn/trunk  
> -Dmaven.scm.checkout.dir=itn
> build:start:
> scm:find-connection:
> [echo] Using connection: scm:svn:svn+ssh://svn.XXX.com/var/svn/itn/trunk
> scm:checkout:
> [echo] Checking out scm:svn:svn+ssh://svn.XXX.com/var/svn/itn/trunk
> BUILD FAILED
> org.apache.maven.scm.ScmException: Exception while executing SCM command.
> at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
> at 
> org.apache.maven.scm.provider.AbstractScmProvider.execute(AbstractScmProvider.java:85)
> at 
> org.apache.maven.scm.manager.DefaultScmManager.execute(DefaultScmManager.java:250)
> at 
> org.apache.maven.scm.manager.DefaultScmManager.checkOut(DefaultScmManager.java:141)
> at org.apache.maven.plugins.scm.ScmBean.checkout(ScmBean.java:94)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at 
> org.apache.commons.jelly.impl.DynamicBeanTag.doTag(DynamicBeanTag.java:230)
> at 
> org.apache.commons.jelly.impl.StaticTagScript.run(StaticTagScript.java:145)
> at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:135)
> at 
> org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:79)
> at 
> org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:110)
> at com.werken.werkz.Goal.fire(Goal.java:639)
> at com.werken.werkz.Goal.attain(Goal.java:575)
> at 
> org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:671)
> at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263)
> at org.apache.maven.cli.App.doMain(App.java:488)
> at org.apache.maven.cli.App.main(App.java:1239)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at 
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at 
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:324)
> at com.werken.forehead.Forehead.run(Forehead.java:551)
> at com.werken.forehead.Forehead.main(Forehead.java:581)
> Caused by: java.lang.NullPointerException
> at 
> org.apache.maven.scm.provider.svn.command.checkout.SvnCheckOutCommand.createCommandLine(SvnCheckOutCommand.java:97)
> at 
> org.apache.maven.scm.provider.svn.command.checkout.SvnCheckOutCommand.executeCheckOutCommand(SvnCheckOutCommand.java:58)
> at 
> org.apache.maven.scm.command.checkout.AbstractCheckOutCommand.executeCommand(AbstractCheckOutCommand.java:45)
> at 
> org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:54)
> ... 25 more
> File.. C:\Documents and 
> Settings\asoto\.maven\cache\maven-scm-plugin-1.5-beta-3\plugin.jelly
> Element... scm:checkout
> Line.. 110
> Column 167
> Exception while executing SCM command.
> Total time: 4 seconds
> Finished at: Sun May 22 22:51:27 PDT 2005

-- 
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: (MPSCM-44) Skip prompt for tag

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MPSCM-44?page=all ]

Brett Porter updated MPSCM-44:
--

Fix Version: 1.5

> Skip prompt for tag
> ---
>
>  Key: MPSCM-44
>  URL: http://jira.codehaus.org/browse/MPSCM-44
>  Project: maven-scm-plugin
> Type: Improvement
> Versions: 1.5
> Reporter: Thomas Van de Velde
>  Fix For: 1.5

>
>
> For my project I want to fully automate release management.  Therefore I 
> would not like to be prompted for a tag when I execute 'prepare-release'.  
> Would it be possible to add a test that looks if a the tag for the release 
> has been defined as a variable, you are not prompted to provide one?
> CURRENT CODE:
> question="What is the new tag name?"
>   answer="tag_name"
>   default="${maven.scm.tag}"
> />
>question="What is the new version?"
>   answer="version_name"
>   default="${tag_name}"
> />
> SUGGESTED CODE:
> 
>   question="What is the new tag name?"
>   answer="tag_name"
>   default="${maven.scm.tag}"
> />
> 
> 
>question="What is the new version?"
>   answer="version_name"
>   default="${maven.scm.tag}"
> />
> 

-- 
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: (MPSCM-52) scm:bootstrap fails on SVN project requiring username/password.

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MPSCM-52?page=all ]

Brett Porter updated MPSCM-52:
--

Fix Version: 1.5

> scm:bootstrap fails on SVN project requiring username/password.
> ---
>
>  Key: MPSCM-52
>  URL: http://jira.codehaus.org/browse/MPSCM-52
>  Project: maven-scm-plugin
> Type: Bug
> Versions: 1.5
>  Environment: WinXP (SP2); 5.0 JVM
> Reporter: Jamie Bisotti
> Assignee: Brett Porter
>  Fix For: 1.5

>
>
> Trying to boostrap an SVN project, requiring a username/password does not 
> appear to be working.  Specifying the command-line below results in the 
> output listed.  Looking the plugin.jelly, I do not see where the username 
> and/or password are being taken into consideration.  Am I missing something?
> maven -Dmaven.proxy.host=proxy.host.com -Dmaven.proxy.port=80 
> -Dmaven.scm.url=scm:svn:http://svnserver/repos/myproject/trunk/ 
> -Dmaven.scm.svn.module=mymodule -Dmaven.scm.username=u1 
> -Dmaven.scm.password=p1 scm:bootstrap
>  __  __
> |  \/  |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
> |_|  |_\__,_|\_/\___|_||_|  v. 1.0.2
> build:start:
> scm:find-connection:
> [echo] Using connection: scm:svn:http://svnserver/repos/myproject/trunk/
> scm:checkout:
> [echo] Checking out scm:svn:http://svnserver/repos/myproject/trunk/
> [INFO] Working directory: C:\blah\target\checkout
> [INFO] Command line: svn checkout --non-interactive 
> http://svnserver/repos/myproject
> /trunk/ checkout
> Provider message:
> The svn command failed.
> Command output:
> svn: PROPFIND request failed on '/repos/myproject/trunk'
> svn: PROPFIND of '/repos/myproject/trunk': authorization failed 
> (http://svnserver)
> BUILD FAILED
> File.. C:\Documents and Settings\James F 
> Bisotti\.maven\cache\maven-scm-plug
> in-1.5-beta-3\plugin.jelly
> Element... scm:checkout
> Line.. 110
> Column 167
> Error!
> Total time: 4 seconds

-- 
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: (MPSCM-29) scm:cvs-update-project uses developer connection

[Brett Porter (JIRA)]

 [ http://jira.codehaus.org/browse/MPSCM-29?page=all ]

Brett Porter updated MPSCM-29:
--

Fix Version: (was: 1.6)
 1.5
Environment: 

> scm:cvs-update-project uses developer connection
> 
>
>  Key: MPSCM-29
>  URL: http://jira.codehaus.org/browse/MPSCM-29
>  Project: maven-scm-plugin
> Type: Bug
> Versions: 1.4.2, 1.4.1
> Reporter: Carlos Sanchez
>  Fix For: 1.5

>
>
> IMHO it shouldn't specify cvsRoot in the ant task, let cvs use root from CVS 
> directory.

-- 
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-359) support project inheritence with flat project layout

[bryan hunt (JIRA)]

 [ http://jira.codehaus.org/browse/MNG-359?page=all ]

bryan hunt updated MNG-359:
---

Attachment: was5.1flatmavenstructure.zip

Hi there, 
I've uploaded a sample project that shows how people working with 
websphere/WSAD and also in general might want to structure their 
maven projects for easy sharing with their team members and quick 
eclipse setup for new developers.

> support project inheritence with flat project layout
> 
>
>  Key: MNG-359
>  URL: http://jira.codehaus.org/browse/MNG-359
>  Project: Maven 2
> Type: Wish
>   Components: maven-core
> Versions: 2.0-alpha-1
> Reporter: Ryan Sonnek
> Priority: Critical
>  Fix For: 2.0-beta-1
>  Attachments: was5.1flatmavenstructure.zip
>
>
> the project inheritence does not currently support projects that are laid out 
> with a "flat" directory structure.
> ex:
> --/my-project-root/
> pom.xml  (base pom)
> --/my-subproject-one/
> pom.xml (child pom)
> original thread on mailing list:  
> http://marc.theaimsgroup.com/?l=turbine-maven-user&m=111442037703037&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: JIRA proposal for plugins

[Brett Porter]

Stephane Nicoll wrote:


If you guys can afford one projet per plugin, I would suggest to go
that way. 

I don't think we can afford to add any more, but we could probably reuse 
the m1 plugins with new version identifiers... I'd just find that very 
confusing as they are completely different, for the most part.



Maybe, we can give differents rights to different people
(e.g. one project manager per plugin).
 

This doesn't happen in practice (different leads - perhaps, but you can 
have component leads).



Have you thinked of Fix For Version? I agree with Vincent when he says
that plugins do not share the same dev/release lifecycle.
 


That was the downside I mentioned.


Maybe you can create a 'maven2 plugins' category in Jira?
 


The problems I'm seeing with the multiple plugins in JIRA are:
- version management not always done when releases are, especially when 
a batch are done together as it takes a lot of time to do. Free text 
would allow users to specify what they are actually using
- can't query across a group of plugins without querying across every 
project in JIRA (it's concept of a project group is essentially 
useless). This is a pain for developers, but even more so for users.


Because plugins are generally not getting a lot of bugs filed, and 
releases rarely fix more than 5-10 issues, I don't think we're seeing 
the benefits of having them separate.


- Brett



-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Re: M1.1 bootstrap fails

[Arnaud HERITIER]

yes, I'll do it today
 Thx
 Arnaud

 On 5/26/05, Brett Porter <[EMAIL PROTECTED]> wrote: 
> 
> ok, I can reproduce. Stupid XML parsers.
> 
> Can you file a JIRA?
> 
> - Brett
> 
> Arnaud HERITIER wrote:
> 
> >I use a JDK 1.4.2 on Windows XP :
> >
> >D:\Work\Dev\apache-maven-1.1\core\trunk\src\test\touchstone-build>java 
> -version
> >java version "1.4.2_05"
> >Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_05-b04)
> >Java HotSpot(TM) Client VM (build 1.4.2_05-b04, mixed mode)
> >
> >Arnaud
> >
> >
> 
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
>

Re: JIRA proposal for plugins

[Stephane Nicoll]

If you guys can afford one projet per plugin, I would suggest to go
that way. Maybe, we can give differents rights to different people
(e.g. one project manager per plugin).

Have you thinked of Fix For Version? I agree with Vincent when he says
that plugins do not share the same dev/release lifecycle.

Maybe you can create a 'maven2 plugins' category in Jira?

Cheers,
Stéphane

On 5/26/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> Hi,
> 
> Given the resounding mess that resulted from giving each plugin its own
> project in JIRA for m1, I'd like to propose the following for m2:
> 
> - create a maven-plugins project
> - add new plugins as components
> - add a "component version" field that is free text.
> 
> Upside:
> - more manageable
> - can still query per plugin/per version as long as the text is well formed
> 
> Downside:
> - can't use roadmap etc
> - can't bulk change version for scheduling
> 
> In general, I don't think this is a problem - I think that plugins tend
> to have very few bugs assigned to them at any given time if they are
> being looked after (xdoc is an exception as it is basically a product
> unto itself in m1).
> 
> Thoughts? Should we move towards this in m1 too, or just let them wind
> down over time?
> 
> - Brett
> 
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 


-- 
.::You're welcome ::.

-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JIRA proposal for plugins

[Vincent Massol]

> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 26 mai 2005 08:33
> To: Maven Developers List
> Subject: JIRA proposal for plugins
> 
> Hi,
> 
> Given the resounding mess that resulted from giving each plugin its own
> project in JIRA for m1

Could you explain what you consider a mess? Personally, I've not seen any
issue but I can see the downsides of having a single JIRA project (basically
not the same release cycle).

Thanks
-Vincent






_ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, 
photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

RE: JIRA proposal for plugins

[Vincent Massol]

> -Original Message-
> From: Brett Porter [mailto:[EMAIL PROTECTED]
> Sent: jeudi 26 mai 2005 08:33
> To: Maven Developers List
> Subject: JIRA proposal for plugins
> 
> Hi,
> 
> Given the resounding mess that resulted from giving each plugin its own
> project in JIRA for m1

Could you explain what you consider a mess? Personally, I've not seen any
issue but I can see the downsides of having a single JIRA project (basically
not the same release cycle).

Thanks
-Vincent






_ 
Découvrez le nouveau Yahoo! Mail : 1 Go d'espace de stockage pour vos mails, 
photos et vidéos ! 
Créez votre Yahoo! Mail sur http://fr.mail.yahoo.com


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]