[jira] Closed: (MAVENUPLOAD-264) eclipse jdtcore update

2004-12-05 Thread jira
Message:

   The following issue has been closed.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-264

Here is an overview of the issue:
-
Key: MAVENUPLOAD-264
Summary: eclipse jdtcore update
   Type: Task

 Status: Closed
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Carlos Sanchez
   Reporter: Torsten Curdt

Created: Sun, 21 Nov 2004 8:25 PM
Updated: Sun, 5 Dec 2004 8:21 AM

Description:
http://eclipse.org

Please update!!


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



[jira] Closed: (MAVENUPLOAD-267) Please upload jbpm 2.0 to ibiblio

2004-12-05 Thread jira
Message:

   The following issue has been closed.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-267

Here is an overview of the issue:
-
Key: MAVENUPLOAD-267
Summary: Please upload jbpm 2.0 to ibiblio
   Type: Task

 Status: Closed
 Resolution: INCOMPLETE

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Carlos Sanchez
   Reporter: Yujin Kim

Created: Tue, 30 Nov 2004 11:15 AM
Updated: Sun, 5 Dec 2004 8:23 AM

Description:
Jbpm is a BPM framework and is now part of Jboss alliance

http://sourceforge.net/project/showfiles.php?group_id=70542package_id=117680

thanks


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



[jira] Closed: (MAVENUPLOAD-268) inetaddresslocator-2.18

2004-12-05 Thread jira
Message:

   The following issue has been closed.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-268

Here is an overview of the issue:
-
Key: MAVENUPLOAD-268
Summary: inetaddresslocator-2.18
   Type: Task

 Status: Closed
 Resolution: FIXED

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Carlos Sanchez
   Reporter: Caoilte O'Connor

Created: Fri, 3 Dec 2004 5:32 AM
Updated: Sun, 5 Dec 2004 8:25 AM

Description:
http://sourceforge.net/projects/javainetlocator
http://sourceforge.net/project/memberlist.php?group_id=72381

Java and ColdFusion libraries to lookup country code and language from IP 
address. It uses a local copy of the WHOIS database to perform fast, accurate 
lookups of country codes. Useful for log analysis, internationalization, 
geolocation, etc..


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



[jira] Closed: (MAVENUPLOAD-269) MyFaces JSF-API

2004-12-05 Thread jira
Message:

   The following issue has been closed.

   Resolver: Carlos Sanchez
   Date: Sun, 5 Dec 2004 8:34 AM

For apache projects you can deploy to 
http://www.apache.org/dist/java-repository/ whenever you want. It's mirrored to 
ibiblio.
For non public builds (not mirrored to ibilio) you can use 
http://cvs.apache.org/repository/
-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-269

Here is an overview of the issue:
-
Key: MAVENUPLOAD-269
Summary: MyFaces JSF-API
   Type: Task

 Status: Closed
 Resolution: WON'T FIX

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: Carlos Sanchez
   Reporter: Matthias Weßendorf

Created: Sat, 4 Dec 2004 4:24 AM
Updated: Sun, 5 Dec 2004 8:34 AM

Description:
incubator.apache.org/myfaces/
http://incubator.apache.org/myfaces/community/contributors.html

MyFaces is an open source Impl of JavaServer Faces Spec. (JSR #127).

Since some projects depend on JSF-API, I guess there is interesst
in hosting MyFaces' JSF-API Impl on ibiblio

Please upload! DO IT NOW! 
;-)


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



RE: [vote] release Maven 1.0.2

2004-12-05 Thread Carlos Sanchez
+0

Haven't tested yet but MAVEN-1501 was really annoying. 

 -Original Message-
 From: Brett Porter [mailto:[EMAIL PROTECTED] 
 Sent: Saturday, December 04, 2004 10:55 AM
 To: Maven Developers List
 Subject: [vote] release Maven 1.0.2
 
 Hi,
 
 Please vote for whether to release the following:
 http://www.apache.org/~brett/maven-1.0.2-SNAPSHOT/
 
 7 fixes, one of which has been quite problematic (MAVEN-1501)
 
 http://jira.codehaus.org/secure/BrowseProject.jspa
 
 Updated plugins: dashboard, java, linkcheck Not updated: ear 
 (not yet released - has outstanding issues. Can be 
 individually released).
 
 [ ] +1 - I have tested it and say go for it [ ] +0 - I 
 haven't tested it but say go for it [ ] -1 - I found a bug in 
 testing/have a reason to wait
 
 +1 from me...
 
 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]



Renaming the docbook plugin

2004-12-05 Thread Carlos Sanchez
Hi,

Is it possible to rename the maven docbook plugin to something like 
xdoc2docbook, so sourceforge sdocbook could be called docbook?
This way I think it'd be less confusing to users.

Regards

Carlos Sanchez
A Coruña, Spain
http://www.jroller.com/page/carlossg



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



Re: Invoking 1.3.1 javac from Maven running on Java 1.4.2

2004-12-05 Thread Doug Knesek
Brett,

I checked out maven-plugins.  But how do I do a
plugin:install pointing to the local directory in
which I checked out the latest plugins?

--- Brett Porter [EMAIL PROTECTED] wrote:

 try checking out maven-plugins CVS and running
 plugin:install on the
 java plugin. This has been fixed.
 
 I'll slate a release of this for 1.0.2
 
 - Brett
 
 
 On Fri, 3 Dec 2004 07:14:53 -0800 (PST), Doug Knesek
 [EMAIL PROTECTED] wrote:
  Hello,
  
  I am currently using Maven 1.0.1 running on Java
  1.4.2. I'm trying to invoke a 1.3.1 javac for my
  builds.
  
  I'm doing this because, although my project was
  written for Java 1.3, I think the Maven plug-ins I
  need were compiled with Java 1.4, as I get an
 error
  when I run Maven using Java 1.3. For instance,
  FindBugs gives the following error:
  
  java.lang.UnsupportedClassVersionError:
  edu/umd/cs/findbugs/anttask/FindBugsTask
 (Unsupported
  major.minor version 48.0)
  
  So to invoke the Java 1.3 javac using Maven
 running on
  Java 1.4.2, I set some properties as follows:
  
  maven.compile.source=
  maven.compile.fork=yes
  maven.compile.jdk=1.3
  maven.compile.jdk.home=C:/jdk1.3.1_14
  maven.compile.executable=C:/jdk1.3.1_14/bin/javac
  
  When running maven -X jar, the Java plug-in is
  trying to pass a parameter (-source) to javac that
 the
  1.3 version of javac doesn't support. The error is
 as
  follows:
  
  [javac] javac: invalid flag: -source 
  
  Here are excerpts from maven -X jar:
  
  ...
  [javac] [DEBUG] Execute:Java13CommandLauncher:
  Executing 'C:\jdk1.3.1_14\bin\javac' with
 arguments:
  '-d'
  
 'O:\wsad_lvc\GLCommon\GlMaven\Common\target\classes'
  '-classpath'
  
 
'O:\wsad_lvc\GLCommon\GlMaven\Common\target\classes;T:\Edc\Consolidation\.maven\reposi
\
tory\log4j\jars\log4j-1.2.8.jar;T
  
  
 
\Edc\Consolidation\.maven\repository\regexp\jars\regexp-1.2.jar;T:\Edc\Consolidation\.
\
maven\repository\great-lakes\jars
  
  
 
gl-framework-1.0.jar;T:\Edc\Consolidation\.maven\repository\ibm\jars\j2ee.jar;T:\Edc\C
\
onsolidation\maven-1.0.1\lib\fore
  
  ead-1.0-beta-5.jar'
  '-sourcepath'
  'O:\wsad_lvc\GLCommon\GlMaven\Common\src\java'
  '-target'
  '1.1'
  '-g'
  '-source'
  ''
  
 
'@O:\wsad_lvc\GLCommon\GlMaven\Common\files625000713'
  
  The ' characters around the executable and
 arguments
  are
  not part of the command.
  
  [javac] javac: invalid flag: -source
  ...
  
  Thanks
  
  
 


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



[jira] Commented: (MAVEN-1522) Proxy + NTLM = NullPointerException

2004-12-05 Thread jira
The following comment has been added to this issue:

 Author: Graham Leggett
Created: Sun, 5 Dec 2004 11:53 AM
   Body:
Some testing reveals that if the ntlm.host option is left off, it throws 
NullPointException.

It seems that if at least one option is set, it assumes all the options are 
set, which is not necessarily the case.

-
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1522?page=comments#action_27511

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1522

Here is an overview of the issue:
-
Key: MAVEN-1522
Summary: Proxy + NTLM = NullPointerException
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1-beta-1
   Versions:
 1.0.1

   Assignee: 
   Reporter: Graham Leggett

Created: Wed, 1 Dec 2004 8:32 AM
Updated: Sun, 5 Dec 2004 11:53 AM
Environment: MacOSX 10.3.6 / JDK v1.4.2

Description:
If build.properties is defined like this:

maven.proxy.host = 192.168.1.27
maven.proxy.port = 80
maven.proxy.username = username
maven.proxy.password = password
maven.proxy.ntlm.domain = domain

Then maven bombs out with a NullPointerException like this:

Graham-Leggetts-Computer:~/src/standard/autobahn minfrin$ maven site
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.1

Attempting to download jdepend-2.7.jar.
Error retrieving artifact from 
[http://www.ibiblio.org/maven/jdepend/jars/jdepend-2.7.jar]: 
java.lang.NullPointerException
WARNING: Failed to download jdepend-2.7.jar.

BUILD FAILED
File.. /Users/minfrin/.maven/cache/maven-xdoc-plugin-1.8/plugin.jelly
Element... attainGoal
Line.. 693
Column 57
The build cannot continue because of the following unsatisfied dependency:

jdepend-2.7.jar

Total time: 5 seconds
Finished at: Wed Dec 01 15:10:41 SAST 2004

What should happen is that a valid error message be returned to the user as to 
whatever is missing. NullPointerException says nothing to the user.



-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



Re: cvs commit: maven/src/java/org/apache/maven ArtifactListBuilder.java

2004-12-05 Thread Jason van Zyl
On Sat, 2004-12-04 at 15:03, Brett Porter wrote:
 Actually, it will, because it starts with a number :)
 
 I'm not particularly happy with the property syntax for JAR overrides 
 and its dual meaning, but something that can be rectified later.

I think it would be perfectly fine to only allow the specification of a
property that indicated a version. All artifacts then must be present in
a repository and not in some random place in the filesystem. That hack
was added for whacky jakarta commons usage and I would be more than
happy to see it go away.

 - Brett
 
 Jason van Zyl wrote:
 
 On Fri, 2004-12-03 at 23:07, [EMAIL PROTECTED] wrote:
   
 
 brett   2004/12/03 23:07:08
 
   Modified:src/java/org/apache/maven Tag: MAVEN-1_0-BRANCH
 ArtifactListBuilder.java
   Log:
   has to match exactly, as a path can contain SNAPSHOT
 
 
 
 Then determine whether the property is for a path or version because
 what you've changed won't allow 1.1-SNAPSHOT as a version which is what
 we've decided we're going to allow.
 
   
 
 
 
 
 -
 To unsubscribe, e-mail: [EMAIL PROTECTED]
 For additional commands, e-mail: [EMAIL PROTECTED]

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
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]



[jira] Commented: (MAVEN-1522) Proxy + NTLM = NullPointerException

2004-12-05 Thread jira
The following comment has been added to this issue:

 Author: Brett Porter
Created: Sun, 5 Dec 2004 1:10 PM
   Body:
Graham,
Thanks - but what I really need is for you to run it with -X so I can get the 
line number it occurs at from the stack trace. It'll save me time tracking it 
down to fix the error message.

-
View this comment:
  http://jira.codehaus.org/browse/MAVEN-1522?page=comments#action_27515

-
View the issue:
  http://jira.codehaus.org/browse/MAVEN-1522

Here is an overview of the issue:
-
Key: MAVEN-1522
Summary: Proxy + NTLM = NullPointerException
   Type: Bug

 Status: Unassigned
   Priority: Major

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven
   Fix Fors:
 1.1-beta-1
   Versions:
 1.0.1

   Assignee: 
   Reporter: Graham Leggett

Created: Wed, 1 Dec 2004 8:32 AM
Updated: Sun, 5 Dec 2004 1:10 PM
Environment: MacOSX 10.3.6 / JDK v1.4.2

Description:
If build.properties is defined like this:

maven.proxy.host = 192.168.1.27
maven.proxy.port = 80
maven.proxy.username = username
maven.proxy.password = password
maven.proxy.ntlm.domain = domain

Then maven bombs out with a NullPointerException like this:

Graham-Leggetts-Computer:~/src/standard/autobahn minfrin$ maven site
 __  __
|  \/  |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|  v. 1.0.1

Attempting to download jdepend-2.7.jar.
Error retrieving artifact from 
[http://www.ibiblio.org/maven/jdepend/jars/jdepend-2.7.jar]: 
java.lang.NullPointerException
WARNING: Failed to download jdepend-2.7.jar.

BUILD FAILED
File.. /Users/minfrin/.maven/cache/maven-xdoc-plugin-1.8/plugin.jelly
Element... attainGoal
Line.. 693
Column 57
The build cannot continue because of the following unsatisfied dependency:

jdepend-2.7.jar

Total time: 5 seconds
Finished at: Wed Dec 01 15:10:41 SAST 2004

What should happen is that a valid error message be returned to the user as to 
whatever is missing. NullPointerException says nothing to the user.



-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



Re: Renaming the docbook plugin

2004-12-05 Thread Brett Porter
Perhaps they can merged into one?
Nobody is maintaining our one, so I have no problem if it is demoted to 
the sandbox and cut from releases either.

- Brett
Carlos Sanchez wrote:
Hi,
Is it possible to rename the maven docbook plugin to something like 
xdoc2docbook, so sourceforge sdocbook could be called docbook?
This way I think it'd be less confusing to users.
Regards
Carlos Sanchez
A Coruña, Spain
http://www.jroller.com/page/carlossg

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


[ANN] Maven Java Plug-in 1.5 released

2004-12-05 Thread brett
The maven team is pleased to announce the Maven Java Plug-in 1.5 release! 

http://maven.apache.org/reference/plugins/java/



Changes in this version include:

  Fixed bugs:

o Make it work by default with any version of the JDK Issue: MPJAVA-22. 

  Changes:

o Deprecate dependency handle 
o Use assert taglib for tests  

To automatically install the plugin, type the following on a single line:

maven plugin:download 
  -DgroupId=maven 
  -DartifactId=maven-java-plugin
  -Dversion=1.5

For a manual installation, you can download the plugin here:
http://www.apache.org/dyn/closer.cgi/java-repository/maven/plugins/maven-java-plugin-1.5.jar
 

Have fun!
-The maven team
  

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



Re: Invoking 1.3.1 javac from Maven running on Java 1.4.2

2004-12-05 Thread Brett Porter
cd maven-plugins/java
maven plugin:install
Actually, I released the 1.5 Java plugin, though didn't do an 
announcement. Let me send that now.

Basically, you can do:
maven plugin:download -DgroupId=maven  -DartifactId=maven-java-plugin  
-Dversion=1.5

Cheers,
Brett
Doug Knesek wrote:
Brett,
I checked out maven-plugins.  But how do I do a
plugin:install pointing to the local directory in
which I checked out the latest plugins?
 


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


RE: [vote] release Maven 1.0.2

2004-12-05 Thread Eric Pugh
I haven't had a chance to test it either, but I'd like to see it released as
well.  I think the fixes are important.  I wish I had more changes for
cruisecontrol plugin to release with it, but haven't had a chance to do
it...

ERic

 -Original Message-
 From: Brett Porter [mailto:[EMAIL PROTECTED]
 Sent: Saturday, December 04, 2004 10:55 AM
 To: Maven Developers List
 Subject: [vote] release Maven 1.0.2


 Hi,

 Please vote for whether to release the following:
 http://www.apache.org/~brett/maven-1.0.2-SNAPSHOT/

 7 fixes, one of which has been quite problematic (MAVEN-1501)

 http://jira.codehaus.org/secure/BrowseProject.jspa

 Updated plugins: dashboard, java, linkcheck
 Not updated: ear (not yet released - has outstanding issues. Can be
 individually released).

 [ ] +1 - I have tested it and say go for it
 [ ] +0 - I haven't tested it but say go for it
 [ ] -1 - I found a bug in testing/have a reason to wait

 +1 from me...

 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]



[proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Brett Porter
Hi,

I'd like to start a discussion about this to see what people think.

The reasons:
- timing is right as we wind down MAVEN-1_0-BRANCH
- HTTPS makes it more practical behind firewalls
- the tool support seems to be mostly there now (not perfect, but good enough)
- is being encouraged ASF wide

Proposed repositories to move:
maven
maven-plugins
maven-plugins-sandbox
maven-jelly-tags

Proposed layout in svn:
maven
  maven-1
core (formerly maven)
  trunk
  branches
  tags (hereafter abbreviated as t/b/t)
plugins
  t/b/t
plugins-sandbox
  t/b/t
jelly-tags
  t/b/t
(and later on...)
  wagon
t/b/t
  scm
t/b/t
  components (or maven-2?)
maven-core
  t/b/t
maven-model
  t/b/t
...

Some points:

* Why t/b/t at plugins level, not for individual plugins?
easier to maintain the current structure, and plugins are infrequently branched.
When they are branched/tagged, they would be copied to, for example,
maven-plugins/branches/java/1.5-SNAPSHOT/...
The fact that this causes a different relative path to the extended parent is
problematic, so developing on the branch would require switcing your checkout to
the branch (which is possible), much like is done with CVS. I don't see an easy
way to avoid this (except for m2 style parent POM references :)

* What about Maven's subversion support?
The only remaining plugin missing support is maven-scm-plugin. I'm going to look
at adding it quickly, then revisit that plugin later to use maven-scm once it is
released.

What do others think?

Cheers,
Brett


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



RE: [proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Vincent Massol
I would be +1 for moving to subversion.

I have been using svn on Cargo (codehaus) for 1-2 months and I'm very happy.
The only downside on codehaus I can think of is that we're using svn+ssh as
the protocol which is not very well supported by the different tools (except
TortoiseSVN which is very nice). Dunno about HTTPS support.

Thanks
-Vincent

 -Original Message-
 From: Brett Porter [mailto:[EMAIL PROTECTED]
 Sent: dimanche 5 décembre 2004 22:55
 To: [EMAIL PROTECTED]
 Subject: [proposal] Move Maven 1.x from CVS to Subversion
 
 Hi,
 
 I'd like to start a discussion about this to see what people think.
 
 The reasons:
 - timing is right as we wind down MAVEN-1_0-BRANCH
 - HTTPS makes it more practical behind firewalls
 - the tool support seems to be mostly there now (not perfect, but good
 enough)
 - is being encouraged ASF wide
 
 Proposed repositories to move:
 maven
 maven-plugins
 maven-plugins-sandbox
 maven-jelly-tags
 
 Proposed layout in svn:
 maven
   maven-1
 core (formerly maven)
   trunk
   branches
   tags (hereafter abbreviated as t/b/t)
 plugins
   t/b/t
 plugins-sandbox
   t/b/t
 jelly-tags
   t/b/t
 (and later on...)
   wagon
 t/b/t
   scm
 t/b/t
   components (or maven-2?)
 maven-core
   t/b/t
 maven-model
   t/b/t
 ...
 
 Some points:
 
 * Why t/b/t at plugins level, not for individual plugins?
 easier to maintain the current structure, and plugins are infrequently
 branched.
 When they are branched/tagged, they would be copied to, for example,
 maven-plugins/branches/java/1.5-SNAPSHOT/...
 The fact that this causes a different relative path to the extended parent
 is
 problematic, so developing on the branch would require switcing your
 checkout to
 the branch (which is possible), much like is done with CVS. I don't see an
 easy
 way to avoid this (except for m2 style parent POM references :)
 
 * What about Maven's subversion support?
 The only remaining plugin missing support is maven-scm-plugin. I'm going
 to look
 at adding it quickly, then revisit that plugin later to use maven-scm once
 it is
 released.
 
 What do others think?
 
 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]



Re: [proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Alex Karasulu
Hiya,
+1
Really the timing as U said sounds about right.  Also this helps 
progress the use and development of the SCM plugin.  BTW there was a 
pure Java SVN client in the works out there.  Down the road it might be 
useful for adding more SCM goals to beef up the plugin:

http://tmate.org/svn/
Cheers,
Alex
Brett Porter wrote:
Hi,
I'd like to start a discussion about this to see what people think.
The reasons:
- timing is right as we wind down MAVEN-1_0-BRANCH
- HTTPS makes it more practical behind firewalls
- the tool support seems to be mostly there now (not perfect, but good enough)
- is being encouraged ASF wide
Proposed repositories to move:
maven
maven-plugins
maven-plugins-sandbox
maven-jelly-tags
Proposed layout in svn:
maven
 maven-1
   core (formerly maven)
 trunk
 branches
 tags (hereafter abbreviated as t/b/t)
   plugins
 t/b/t
   plugins-sandbox
 t/b/t
   jelly-tags
 t/b/t
(and later on...)
 wagon
   t/b/t
 scm
   t/b/t
 components (or maven-2?)
   maven-core
 t/b/t
   maven-model
 t/b/t
   ...

Some points:
* Why t/b/t at plugins level, not for individual plugins?
easier to maintain the current structure, and plugins are infrequently branched.
When they are branched/tagged, they would be copied to, for example,
maven-plugins/branches/java/1.5-SNAPSHOT/...
The fact that this causes a different relative path to the extended parent is
problematic, so developing on the branch would require switcing your checkout to
the branch (which is possible), much like is done with CVS. I don't see an easy
way to avoid this (except for m2 style parent POM references :)
* What about Maven's subversion support?
The only remaining plugin missing support is maven-scm-plugin. I'm going to look
at adding it quickly, then revisit that plugin later to use maven-scm once it is
released.
What do others think?
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]


Re: [proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Jason van Zyl
On Sun, 2004-12-05 at 13:54, Brett Porter wrote:
 Hi,
 
 I'd like to start a discussion about this to see what people think.
 
 The reasons:
 - timing is right as we wind down MAVEN-1_0-BRANCH
 - HTTPS makes it more practical behind firewalls
 - the tool support seems to be mostly there now (not perfect, but good enough)
 - is being encouraged ASF wide
 
 Proposed repositories to move:
 maven
 maven-plugins
 maven-plugins-sandbox
 maven-jelly-tags

+1

The only thing to keep in mind for m2 is that the directory in which an
artifact build resides must be the same as the artifactId. It's really
only important for m2 but allows the unified source tree (USD) to
function and allows the proper creation of an artifact path which is
used in continuum to derive the correct SCM path for a child project
where the only definition for the entire group of projects is in the
top-level parent POM. 

-- 
jvz.

Jason van Zyl
[EMAIL PROTECTED]
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: [proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Felipe Leme
+ 1 (even though I haven't played enough with svn yet...)


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



Re: [proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Trygve Laugstøl
On søn, 2004-12-05 at 22:54, Brett Porter wrote:
 Hi,
 
 I'd like to start a discussion about this to see what people think.
 
 The reasons:
 - timing is right as we wind down MAVEN-1_0-BRANCH
 - HTTPS makes it more practical behind firewalls
 - the tool support seems to be mostly there now (not perfect, but good enough)
 - is being encouraged ASF wide
 
 Proposed repositories to move:
 maven
 maven-plugins
 maven-plugins-sandbox
 maven-jelly-tags
 
 Proposed layout in svn:
 maven
   maven-1
 core (formerly maven)
   trunk
   branches
   tags (hereafter abbreviated as t/b/t)
 plugins
   t/b/t
 plugins-sandbox
   t/b/t
 jelly-tags
   t/b/t
 (and later on...)
   wagon
 t/b/t
   scm
 t/b/t
   components (or maven-2?)
 maven-core
   t/b/t
 maven-model
   t/b/t
 ...
 
 Some points:
 
 * Why t/b/t at plugins level, not for individual plugins?
 easier to maintain the current structure, and plugins are infrequently 
 branched.
 When they are branched/tagged, they would be copied to, for example,
 maven-plugins/branches/java/1.5-SNAPSHOT/...
 The fact that this causes a different relative path to the extended parent is
 problematic, so developing on the branch would require switcing your checkout 
 to
 the branch (which is possible), much like is done with CVS. I don't see an 
 easy
 way to avoid this (except for m2 style parent POM references :)
 
 * What about Maven's subversion support?
 The only remaining plugin missing support is maven-scm-plugin. I'm going to 
 look
 at adding it quickly, then revisit that plugin later to use maven-scm once it 
 is
 released.
 
 What do others think?

+1

--
Trygve

 
 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]



[jira] Created: (MAVENUPLOAD-270) Upload of wicket-0.9.14-alpha.jar

2004-12-05 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-270

Here is an overview of the issue:
-
Key: MAVENUPLOAD-270
Summary: Upload of wicket-0.9.14-alpha.jar
   Type: Task

 Status: Unassigned

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: 
   Reporter: Martijn Dashorst

Created: Sun, 5 Dec 2004 8:10 PM
Updated: Sun, 5 Dec 2004 8:10 PM

Description:
http://wicket.sourceforge.net/wicket-0.9.14-alpha.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Please upload! DO IT NOW!


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



[jira] Closed: (MAVENUPLOAD-270) Upload of wicket-0.9.14-alpha.jar

2004-12-05 Thread jira
Message:

   The following issue has been closed.

   Resolver: Martijn Dashorst
   Date: Sun, 5 Dec 2004 8:12 PM

Wrong links uploaded. :(
-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-270

Here is an overview of the issue:
-
Key: MAVENUPLOAD-270
Summary: Upload of wicket-0.9.14-alpha.jar
   Type: Task

 Status: Closed
 Resolution: INCOMPLETE

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: 
   Reporter: Martijn Dashorst

Created: Sun, 5 Dec 2004 8:10 PM
Updated: Sun, 5 Dec 2004 8:12 PM

Description:
http://wicket.sourceforge.net/wicket-0.9.14-alpha.jar

http://wicket.sourceforge.net
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Please upload! DO IT NOW!


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



[jira] Created: (MAVENUPLOAD-271) Upload of wicket-0.9.14-alpha-bundle.jar

2004-12-05 Thread jira
Message:

  A new issue has been created in JIRA.

-
View the issue:
  http://jira.codehaus.org/browse/MAVENUPLOAD-271

Here is an overview of the issue:
-
Key: MAVENUPLOAD-271
Summary: Upload of wicket-0.9.14-alpha-bundle.jar
   Type: Task

 Status: Unassigned

 Original Estimate: Unknown
 Time Spent: Unknown
  Remaining: Unknown

Project: maven-upload-requests

   Assignee: 
   Reporter: Martijn Dashorst

Created: Sun, 5 Dec 2004 8:14 PM
Updated: Sun, 5 Dec 2004 8:14 PM

Description:
http://wicket.sourceforge.net/wicket-0.9.14-alpha-bundle.jar

http://wicket.sourceforge.net/
http://wicket.sourceforge.net/team-list.html

Wicket is a Java web application framework that takes simplicity, separation of 
concerns and ease of development to a whole new level. Wicket pages can be 
mocked up, previewed and later revised using standard WYSIWYG HTML design 
tools. Please upload! DO IT NOW!


-
JIRA INFORMATION:
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

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


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



RE: [proposal] Move Maven 1.x from CVS to Subversion

2004-12-05 Thread Arnaud HERITIER
+1

I tested it with cargo and I find SVN very good.

Arnaud

 -Message d'origine-
 De : Brett Porter [mailto:[EMAIL PROTECTED]
 Envoyé : dimanche 5 décembre 2004 22:55
 À : [EMAIL PROTECTED]
 Objet : [proposal] Move Maven 1.x from CVS to Subversion
 
 Hi,
 
 I'd like to start a discussion about this to see what people think.
 
 The reasons:
 - timing is right as we wind down MAVEN-1_0-BRANCH
 - HTTPS makes it more practical behind firewalls
 - the tool support seems to be mostly there now (not perfect, but good enough)
 - is being encouraged ASF wide
 
 Proposed repositories to move:
 maven
 maven-plugins
 maven-plugins-sandbox
 maven-jelly-tags
 
 Proposed layout in svn:
 maven
   maven-1
 core (formerly maven)
   trunk
   branches
   tags (hereafter abbreviated as t/b/t)
 plugins
   t/b/t
 plugins-sandbox
   t/b/t
 jelly-tags
   t/b/t
 (and later on...)
   wagon
 t/b/t
   scm
 t/b/t
   components (or maven-2?)
 maven-core
   t/b/t
 maven-model
   t/b/t
 ...
 
 Some points:
 
 * Why t/b/t at plugins level, not for individual plugins?
 easier to maintain the current structure, and plugins are infrequently 
 branched.
 When they are branched/tagged, they would be copied to, for example,
 maven-plugins/branches/java/1.5-SNAPSHOT/...
 The fact that this causes a different relative path to the extended parent is
 problematic, so developing on the branch would require switcing your checkout 
 to
 the branch (which is possible), much like is done with CVS. I don't see an 
 easy
 way to avoid this (except for m2 style parent POM references :)
 
 * What about Maven's subversion support?
 The only remaining plugin missing support is maven-scm-plugin. I'm going to 
 look
 at adding it quickly, then revisit that plugin later to use maven-scm once it 
 is
 released.
 
 What do others think?
 
 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]