date:20090318


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2374.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Bouncycastle 140 bundle for bcmail jdk16
 

 Key: MAVENUPLOAD-2374
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2374
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Thierry Carré
Assignee: Carlos Sanchez
 Attachments: bcmail-jdk16-140-bundle.jar


 One bundle to upload bouncycastle's bcmail jar files, including sources and 
 javadoc.
 Note that I am not associated with the bouncycastle project.

-- 
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: (MAVENUPLOAD-2370) Maven Config Processor 1.5 Upload Request


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2370?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2370.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Maven Config Processor 1.5 Upload Request
 -

 Key: MAVENUPLOAD-2370
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2370
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Leandro
Assignee: Carlos Sanchez
 Attachments: maven-config-processor-plugin-1.5-bundle.jar, 
 maven-config-processor-plugin-1.5-bundle.jar


 http://maven-config-processor-plugin.googlecode.com/files/maven-config-processor-plugin-1.5-bundle.jar
 http://code.google.com/p/maven-config-processor-plugin/
 http://code.google.com/u/lehphyro/
 Hi, I'm leader developer of the Maven Config Processor Plugin and would like 
 to upload my plugin to the Maven Central Repository.
 Thanks

-- 
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: (MAVENUPLOAD-2373) Sync the FindBugs repository Take 2


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2373?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2373.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Sync the FindBugs repository Take 2 
 

 Key: MAVENUPLOAD-2373
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2373
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Garvin LeClaire
Assignee: Carlos Sanchez

 This is the second take of my previous request 
 http://jira.codehaus.org/browse/MAVENUPLOAD-2364 .This one is in line 
 with the request of http://jira.codehaus.org/browse/MAVENUPLOAD-2335 and the 
 way some of the other google code hosted projects are packaging their 
 artifacts for the central repository.
 com.google.code.findbugs,,svn,Garvin 
 LeClaire,garvin.lecla...@gmail.com,,http://findbugs.googlecode.com/svn/repos/release-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

[jira] Closed: (MAVENUPLOAD-2343) jabsorb 1.3 (Java to JavaScript Object Request Broker)


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2343.
---

  Assignee: Carlos Sanchez
Resolution: Incomplete

 jabsorb 1.3 (Java to JavaScript Object Request Broker)
 --

 Key: MAVENUPLOAD-2343
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2343
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Roman Kuzmik
Assignee: Carlos Sanchez
 Attachments: jabsorb-1.3-bundle.jar, jabsorb-1.3.zip


 I am not developer. But we've got the permission form author (Arthur Blake) 
 to submit this request:
 http://groups.google.com/group/jabsorb-user/browse_thread/thread/6bd3a12b8e87b036
 @see http://jabsorb.org/JabsorbContributors
 Bundle URL: http://findnetbook.com/jabsorb/jabsorb-1.3.zip

-- 
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: (MAVENUPLOAD-2371) JWBF


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2371?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2371.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 JWBF
 

 Key: MAVENUPLOAD-2371
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2371
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Loki
Assignee: Carlos Sanchez

 net.sourceforge.jwbf,mavens...@web.sourceforge.net:/home/groups/j/jw/jwbf/m2repo-release,rsync_ssh,eldurloki,eldurl...@users.sourceforge.net,,

-- 
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: (MAVENUPLOAD-2372) sync mycila repository


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2372.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 sync mycila repository
 --

 Key: MAVENUPLOAD-2372
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2372
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Mathieu Carbou
Assignee: Carlos Sanchez

 Hi,
 Please add the Mycila repository to the list of repositories to SYNC. We are 
 currently finishing the migration of projects listed at 
 http://code.mycila.com/ to the com.mycila package and groupid.
 Thank you,
 Mathieu Carbou,
 Projects owner  Domain name owner.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MAVENUPLOAD-2375) Please upload jboss-retro artifact


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2375?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170159#action_170159
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2375:
-

is the pom in http://repository.jboss.com/maven2/org/jboss/jboss-retro/1.1.2/ 
ok?

 Please upload jboss-retro artifact
 --

 Key: MAVENUPLOAD-2375
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2375
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Davide Simonetti

 Jboss retro is a retroweaver developed by jboss. 
 It can weave java 1.5 compiled code into a jdk 1.4 compatible. I use it into 
 my projects because it works better than retrotranslator.
 Detailed information can be found here: 
 http://www.jboss.org/community/docs/DOC-10738
 It's licensed under  GNU LGPL software license.
 Thanks in advance.
 Davide.

-- 
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: (MAVENUPLOAD-2379) Sync Spock Framework


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2379?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2379.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Sync Spock Framework
 

 Key: MAVENUPLOAD-2379
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2379
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Peter Niederwieser
Assignee: Carlos Sanchez

 I'm the founder of the Spock Framework, and owner of the spockframework.org 
 domain. Please add the Spock repository to the list of synced repositories. 
 Thank you!

-- 
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: (SCM-441) NPE when using Git SCM 1.2-SNAPSHOT


 [ 
http://jira.codehaus.org/browse/SCM-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Mark Struberg updated SCM-441:
--

Attachment: SCM-441.patch

please check this patch!

the GitUpdateCommand now detects the latest version of the branch given (or 
master if non given).

 NPE when using Git SCM 1.2-SNAPSHOT
 ---

 Key: SCM-441
 URL: http://jira.codehaus.org/browse/SCM-441
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.2
 Environment: Linux and MacOSX, probably everywhere
Reporter: Petter Måhlén
Assignee: Olivier Lamy
 Fix For: 1.2

 Attachments: SCM-441.patch


 This is the log message:
 ---
 [INFO] Storing revision in 'scm.revision' project property.
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] null
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:394)
   at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:103)
 ---
 Looking at the code:
 public void execute()
 throws MojoExecutionException
 {
 super.execute();  
 
 try
 {
 ScmRepository repository = getScmRepository();
 
 UpdateScmResult result = getScmManager().update( repository, 
 getFileSet(),
  getScmVersion( 
 scmVersionType, scmVersion ),
  runChangelog );  
 
 checkResult( result );
 
 if ( result instanceof UpdateScmResultWithRevision )
 {
 String revision = ( (UpdateScmResultWithRevision) result 
 ).getRevision(); 
 getLog().info( Storing revision in ' + revisionKey + ' 
 project property. );   
 if ( project.getProperties() != null ) // Remove the test 
 when we'll use plugin-test-harness 1.0-alpha-2
   {
 project.getProperties().put( revisionKey, revision ); 
 
 }
 getLog().info( Project at revision  + revision );   
 
 }
 }
 catch ( IOException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 catch ( ScmException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 }
 The problem must be that the 'revision' String is null. I guess that is a bug 
 in the Git SCM provider, but I would argue it is also a bug in the Update 
 mojo, which should be a little bit more resistant to null results.

-- 
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: (MAVENUPLOAD-2028) Sync Compass maven repository with the central maven repository


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2028?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2028.
---

Resolution: Fixed

remember to check the report mails or its going to be removed again if in error

 Sync Compass maven repository with the central maven repository
 ---

 Key: MAVENUPLOAD-2028
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2028
 Project: Maven Upload Requests
  Issue Type: Task
Reporter: Shay Banon
Assignee: Carlos Sanchez

 org.compass-project,rsync://repo.compass-project.org,rsync,Shay 
 Banon,kim...@gmail.com,,

-- 
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: (MAVENUPLOAD-2381) Change the repository URL for the VRaptor


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2381?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2381.
---

  Assignee: Carlos Sanchez
Resolution: Fixed

 Change the repository URL for the VRaptor
 -

 Key: MAVENUPLOAD-2381
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2381
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Rafael de F. Ferreira
Assignee: Carlos Sanchez

 We decided to upload our artifacts to SourceForge instead of our own server. 
 The new configuration line is:
 org.vraptor,mavens...@web.sourceforge.net:/home/groups/v/vr/vraptor2/htdocs/maven,rsync_ssh,Fabio
  Kung,fabio.k...@caelum.com.br,,
 (This issue supersedes MEV-593). 

-- 
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: (MEV-593) update .ssh/known_hosts for vraptor.org

[
http://jira.codehaus.org/browse/MEV-593?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Carlos Sanchez closed MEV-593.
--

Assignee: Carlos Sanchez
Resolution: Won't Fix

see linked issue

update .ssh/known_hosts for vraptor.org
---

Key: MEV-593
URL: http://jira.codehaus.org/browse/MEV-593
Project: Maven Evangelism
Issue Type: Wish
Reporter: Fabio Kung
Assignee: Carlos Sanchez

Our server has changed and we've lost the old rsa fingerprint. Could you
please update your /home/maven/.ssh/known_hosts vraptor.org entry to
0c:f9:fa:87:1d:a6:41:fe:e1:47:d2:7c:ed:a6:a6:c1 ?
I'm receiving the following rsync failure:
--- Some repositories were not synchronized ---
groupId: org.vraptor
Error:
@@@
@WARNING: REMOTE HOST IDENTIFICATION HAS CHANGED! @
@@@
IT IS POSSIBLE THAT SOMEONE IS DOING SOMETHING NASTY!
Someone could be eavesdropping on you right now (man-in-the-middle attack)!
It is also possible that the RSA host key has just been changed.
The fingerprint for the RSA key sent by the remote host is
0c:f9:fa:87:1d:a6:41:fe:e1:47:d2:7c:ed:a6:a6:c1.
Please contact your system administrator.
Add correct host key in /home/maven/.ssh/known_hosts to get rid of this
message.
Offending key in /home/maven/.ssh/known_hosts:15
RSA host key for vraptor.org has changed and you have requested strict
checking.
Host key verification failed.
rsync: connection unexpectedly closed (0 bytes received so far) [receiver]
rsync error: error in rsync protocol data stream (code 12) at io.c(453)
[receiver=2.6.9]
Error synchronizing metadata. Exit code: 12
Thanks.

--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SCM-444) Git provider does 'git push' during 'mvn release:prepare' which causes unwanted problems

[
http://jira.codehaus.org/browse/SCM-444?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170165#action_170165
]

Mark Struberg commented on SCM-444:
---

my guess: the git-push is being executed while the release plugin tags the
release.

normally only a

git-push origin tag

is being execute.

Would be awesome if you could provide a full log for me!

Git provider does 'git push' during 'mvn release:prepare' which causes
unwanted problems

Key: SCM-444
URL: http://jira.codehaus.org/browse/SCM-444
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-git
Affects Versions: 1.1
Reporter: Petter Måhlén
Assignee: Olivier Lamy
Priority: Minor
Fix For: 1.2

When doing 'mvn release:prepare' with a Git provider, a 'git push' command is
executed. This is not ideal because the push command can fail or push things
from the local repository that are not needed/wanted in the remote
repository. Some examples are:
1. The local repository has two branches: master (tracking origin/master) and
dummy (tracking origin/dummy). The release is being made on the master
branch, and the dummy and origin/dummy branches have diverged. Running
'release:prepare' causes a 'git push', which will succeed for the master
branch (assuming that the release preparation has been made correctly) and
fail for the dummy branch (the two branches have diverged and need to be
merged or rebased). The release preparation aborts and the directory is left
in a somewhat inconsistent state where manual cleaning up is needed (removing
pom.xml.next files, changing versions to new-SNAPSHOT, etc.)
2. The local repository has two branches: master (tracking origin/master) and
localtest (not in the origin repository). The localtest branch shouldn't be
published because it is just used for some temporary testing and doesn't even
work. It will be pushed during 'release:prepare'.
Suggested behaviour: use 'git push origin currentbranch:currentbranch',
or even better, query for which remote repository to push to (found in
.git/config) and which branch to push from and to. For me, it would be great
to have a 'confirm push' before doing it so as to keep things clean, but
maybe that is quite complex.

[jira] Commented: (MAVENUPLOAD-2382) Sync my repository to the central repository


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2382?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170163#action_170163
 ] 

Carlos Sanchez commented on MAVENUPLOAD-2382:
-

you need to use a qualified groupId, like net.java.dev.args4j 

 Sync my repository to the central repository
 

 Key: MAVENUPLOAD-2382
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2382
 Project: Maven Upload Requests
  Issue Type: Wish
Reporter: Alex Eagle

 args4j,rs...@jakeherringbone.com:/srv/m2repo,rsync_ssh,Alex 
 Eagle,alexea...@google.com,,
 Note, I am working on a project in the google-maven-repository that depends 
 on args4j. To upload that project, you require that I have no repository/ 
 tags, so I need to upload args4j to the central repository.
 I have communicated with Kohsuke (the author of args4j and Hudson) about this 
 and gotten his blessing to upload. The files are copied from 
 http://download.java.net/maven/2/args4j/
 with the scmurl//scm and license/ tags added, as the Maven 
 documentation requires.

-- 
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: (MAVENUPLOAD-2385) maven1 clover 2.4.3 plugin bundle upload


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2385?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2385.
---

  Assignee: Carlos Sanchez
Resolution: Won't Fix

everything in your repo under com.cenqua is automatically sync'ed 

you can check at http://repo1.maven.org/maven2/com/cenqua

 maven1 clover 2.4.3 plugin bundle upload
 

 Key: MAVENUPLOAD-2385
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2385
 Project: Maven Upload Requests
  Issue Type: Task
Reporter: Nick Pellow
Assignee: Carlos Sanchez

 Hi Carlos, 
 I'm not sure if this bundle has already been automatically synced with repo1 
 as per the suggestion here: http://jira.codehaus.org/browse/MAVENUPLOAD-2292 
 so am creating this upload bundle request anyway.
 Please let me know if there is anything we need to do to have this automated.
 Cheers,
 Nick

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SCM-441) NPE when using Git SCM 1.2-SNAPSHOT


[ 
http://jira.codehaus.org/browse/SCM-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170167#action_170167
 ] 

Olivier Lamy commented on SCM-441:
--

you mean please check in or check/verify ? :D.


 NPE when using Git SCM 1.2-SNAPSHOT
 ---

 Key: SCM-441
 URL: http://jira.codehaus.org/browse/SCM-441
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.2
 Environment: Linux and MacOSX, probably everywhere
Reporter: Petter Måhlén
Assignee: Olivier Lamy
 Fix For: 1.2

 Attachments: SCM-441.patch


 This is the log message:
 ---
 [INFO] Storing revision in 'scm.revision' project property.
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] null
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:394)
   at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:103)
 ---
 Looking at the code:
 public void execute()
 throws MojoExecutionException
 {
 super.execute();  
 
 try
 {
 ScmRepository repository = getScmRepository();
 
 UpdateScmResult result = getScmManager().update( repository, 
 getFileSet(),
  getScmVersion( 
 scmVersionType, scmVersion ),
  runChangelog );  
 
 checkResult( result );
 
 if ( result instanceof UpdateScmResultWithRevision )
 {
 String revision = ( (UpdateScmResultWithRevision) result 
 ).getRevision(); 
 getLog().info( Storing revision in ' + revisionKey + ' 
 project property. );   
 if ( project.getProperties() != null ) // Remove the test 
 when we'll use plugin-test-harness 1.0-alpha-2
   {
 project.getProperties().put( revisionKey, revision ); 
 
 }
 getLog().info( Project at revision  + revision );   
 
 }
 }
 catch ( IOException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 catch ( ScmException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 }
 The problem must be that the 'revision' String is null. I guess that is a bug 
 in the Git SCM provider, but I would argue it is also a bug in the Update 
 mojo, which should be a little bit more resistant to null results.

-- 
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: (MAVENUPLOAD-2389) File doesn't sync


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2389?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2389.
---

  Assignee: Carlos Sanchez
Resolution: Won't Fix

nothing is deleted from central. You'd need to make a new release 3.6.1, 
3.6.0-1 or whatever you want.

 File doesn't sync
 -

 Key: MAVENUPLOAD-2389
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2389
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Ivan Chang
Assignee: Carlos Sanchez

 I made a mistake that I upload wrong files.So I tried to re-post it to 
 overwrite with the right release , but it didn't sync to  
 http://repo1.maven.org/maven2/org/zkoss/zk/zk/3.6.0/ .
 So how should I do ? Can I delete this folder and re-upload 3.6.0?

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SCM-441) NPE when using Git SCM 1.2-SNAPSHOT


[ 
http://jira.codehaus.org/browse/SCM-441?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170170#action_170170
 ] 

Mark Struberg commented on SCM-441:
---

Same thing like in a good restaurant:
The question is now WHAT, the question is IN WHICH ORDER!

So I prefer you do both ;)

Would be cool if Petter could also check it on his repo - txs!

 NPE when using Git SCM 1.2-SNAPSHOT
 ---

 Key: SCM-441
 URL: http://jira.codehaus.org/browse/SCM-441
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.2
 Environment: Linux and MacOSX, probably everywhere
Reporter: Petter Måhlén
Assignee: Olivier Lamy
 Fix For: 1.2

 Attachments: SCM-441.patch


 This is the log message:
 ---
 [INFO] Storing revision in 'scm.revision' project property.
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] null
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:394)
   at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:103)
 ---
 Looking at the code:
 public void execute()
 throws MojoExecutionException
 {
 super.execute();  
 
 try
 {
 ScmRepository repository = getScmRepository();
 
 UpdateScmResult result = getScmManager().update( repository, 
 getFileSet(),
  getScmVersion( 
 scmVersionType, scmVersion ),
  runChangelog );  
 
 checkResult( result );
 
 if ( result instanceof UpdateScmResultWithRevision )
 {
 String revision = ( (UpdateScmResultWithRevision) result 
 ).getRevision(); 
 getLog().info( Storing revision in ' + revisionKey + ' 
 project property. );   
 if ( project.getProperties() != null ) // Remove the test 
 when we'll use plugin-test-harness 1.0-alpha-2
   {
 project.getProperties().put( revisionKey, revision ); 
 
 }
 getLog().info( Project at revision  + revision );   
 
 }
 }
 catch ( IOException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 catch ( ScmException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 }
 The problem must be that the 'revision' String is null. I guess that is a bug 
 in the Git SCM provider, but I would argue it is also a bug in the Update 
 mojo, which should be a little bit more resistant to null results.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (SCM-442) Incorrect SCM URL constructed when using parent POM that is not in the parent directory

[
http://jira.codehaus.org/browse/SCM-442?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170171#action_170171
]

Mark Struberg commented on SCM-442:
---

the SCM URL creation is usually not part of the scm-provider but done by the
release-plugin. So this is most probably a release bug

Incorrect SCM URL constructed when using parent POM that is not in the parent
directory
---

Key: SCM-442
URL: http://jira.codehaus.org/browse/SCM-442
Project: Maven SCM
Issue Type: Bug
Components: maven-scm-provider-git
Affects Versions: 1.1
Reporter: Petter Måhlén
Assignee: Olivier Lamy
Fix For: 1.2

We have a parent corporate POM that is not in the parent folder of each
project. When running release:perform, the correct (as specified) GIT SCM URL
is not used, but instead a URL is created by appending the Maven artifact
name to the SCM URL of the parent corporate POM project. Which doesn't make
sense at all to me:
1. There is no requirement (and in fact bad practice in a lot of cases) that
the POM hierarchy should map exactly to the folder hierarchy. So a parent POM
doesn't have to reside in a parent directory.
2. There is no requirement (but maybe good practice) to have folder names in
SCM be the same as the artifact names. In our case, we have a bad artifact
name that we want to keep so as not to have to modify a lot of POMs, but we
wanted a clearer repository name for the new Git repository.
This is the error message from the 'mvn release:perform' command.
INFO] Executing: /bin/sh -c cd
/Users/pettermahlen/git/sponsoredlinks-client/target git clone
git://git.shopzilla.com/java/common.mvn.git/slg_client
/Users/pettermahlen/git/sponsoredlinks-client/target/checkout
[INFO] Working directory: /Users/pettermahlen/git/sponsoredlinks-client/target
[ERROR] The git-clone command failed.
[INFO]

[ERROR] BUILD FAILURE
[INFO]

[INFO] Unable to checkout from SCM
Provider message:
The git-clone command failed.
Command output:
fatal: The remote end hung up unexpectedly
The SCM configuration from the 'slg_client' pom.xml is;
scm

connectionscm:git:git://git.shopzilla.com/site/client/sponsoredlinks-client/connection
/scm
The workaround that I have found is to manually edit the release.properties
file and change to using the correct SCM URL.

[jira] Closed: (MAVENUPLOAD-2387) Transitive dependencies in eclipse jdt core are broken


 [ 
http://jira.codehaus.org/browse/MAVENUPLOAD-2387?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Carlos Sanchez closed MAVENUPLOAD-2387.
---

  Assignee: Carlos Sanchez
Resolution: Won't Fix

There are many issues with version ranges and osgi, but that's more of a Maven 
issue than repository problem
Please refer to the mailing list for questions

 Transitive dependencies in eclipse jdt core are broken
 --

 Key: MAVENUPLOAD-2387
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-2387
 Project: Maven Upload Requests
  Issue Type: Bug
Reporter: Dave Syer
Assignee: Carlos Sanchez

 Transitive dependencies in eclipse jdt core are broken.  I can 
 MAVENUPLOAD-1795 that the JDT core JAR was uploaded (the version number does 
 not match the actual one in the repo, so maybe that is part of the problem - 
 the repo has 3.3.0-v_771).  This JAR has dependencies and transitive 
 dependencies that (quite sensibly) use version ranges.  But the ranges do not 
 match any deployed versions of the dependencies, so if you try to use it you 
 get, for example
 Caused by: 
 org.apache.maven.artifact.versioning.OverConstrainedVersionException: 
 Couldn't find a version in [1.0.0-v20070606] to match range [1.0.0,2.0.0)
   org.eclipse.equinox:app:jar:null
 There seems to be an issue with the form of the version in the app artifact.  
 It looks like it might match, but clearly doesn't.

-- 
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: (MASSEMBLY-399) jar-with-dependencies descriptor adding files twice

2009-03-18 Thread Soraya Sanchez (JIRA)

jar-with-dependencies descriptor adding files twice
---

 Key: MASSEMBLY-399
 URL: http://jira.codehaus.org/browse/MASSEMBLY-399
 Project: Maven 2.x Assembly Plugin
  Issue Type: Bug
Affects Versions: 2.2-beta-3
 Environment: windows xp
maven 2.0.7

Reporter: Soraya Sanchez


When generating a .jar with the project dependencies, files are being added 
twice to the jar (but in a location related to the absolute location).

When the plugin configuration is as follows:
plugin
artifactIdmaven-assembly-plugin/artifactId
version2.2-beta-3/version
configuration
  descriptorRefs
 descriptorRefjar-with-dependencies/descriptorRef   
 
  /descriptorRefs 
  archive

manifestFilesrc/main/resources/META-INF/MANIFEST.MF/manifestFile
  /archive 
/configuration
executions
execution
phasepackage/phase
goals
goalattached/goal
/goals
/execution
/executions
/plugin

The generated jar is:

+ the-jar
  + com
  + ...
  + TheClass.class
   + C:
  + workspace
 + ...
  + TheClass.class

that is, the files are being properly added from the project but, the C: folder 
should not exist (it contains, once more, the files located under com)

If using the plugin version 2.2-beta-2 the files are included twice as well 
but, the following way:

+ the-jar
  + com
  + TheClass.class
  + TheClass.class

whereas, if using version is 2.2-beta-1 the file is being generated properly 
(no duplicate files at all).





-- 
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: (MNG-4095) Release instructions unclear

2009-03-18 Thread David Jencks (JIRA)

Release instructions unclear


 Key: MNG-4095
 URL: http://jira.codehaus.org/browse/MNG-4095
 Project: Maven 2
  Issue Type: Improvement
  Components: Documentation:  General
Reporter: David Jencks


Refers to http://maven.apache.org/developers/release/releasing.html

This is AFAICT the de-facto advice on best practices for apache projects that 
want to use maven... if there's more information elsewhere it should be linked 
from here.   As such it is sorely lacking some basic info such as...

1. It applies to projects using the apache pom version 5 which implies you are 
deploying to nexus.  This needs to be stated up front and the consequences 
outlined (e.g. getting someone (who?) to move old stuff onto nexus, and what 
happens to a large collection of projects (e.g. portals or geronimo) that may 
not want to move everything at once)

2. if 
altDeploymentRepository${deploy.altRepository}/altDeploymentRepository in 
the release profile is actually recommended please document where the value 
actually comes from.

3. In the Release Process for part of Maven 1.b it says Verify that all 
pom.xml files have an SCM definition.  I think this is wrong.  IIUC only root 
poms in a multimodule project should define scm.

4. In the note on the settings.xml server definition of apache.snapshots.https 
please document that it is used from the apache 5 pom.  Also, I think that the 
password required is your apache svn password rather than a possible p.a.o 
password.  There is at least one other reference to logging on to nexus with 
apache credentials that should be more specifically apache svn username and 
password

5. If this is the de-facto advice to apache projects wishing to move from the 
file based repo to apache's nexus it needs to be findable through google. 
Linking it to INFRA-1885 would be good.  Linking from the front page of the 
maven docs would be good. More generic separate docs would be better.





-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MNGSITE-79) Release instructions unclear

2009-03-18 Thread Brett Porter (JIRA)

[
http://jira.codehaus.org/browse/MNGSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170186#action_170186
]

Brett Porter commented on MNGSITE-79:
-

2/3/4 apply to the docs here, but really an INFRA ticket should be opened to
get generic stuff made available.

Release instructions unclear

Key: MNGSITE-79
URL: http://jira.codehaus.org/browse/MNGSITE-79
Project: Maven 2 Project Web Site
Issue Type: Improvement
Reporter: David Jencks

Refers to http://maven.apache.org/developers/release/releasing.html
This is AFAICT the de-facto advice on best practices for apache projects that
want to use maven... if there's more information elsewhere it should be
linked from here. As such it is sorely lacking some basic info such as...
1. It applies to projects using the apache pom version 5 which implies you
are deploying to nexus. This needs to be stated up front and the
consequences outlined (e.g. getting someone (who?) to move old stuff onto
nexus, and what happens to a large collection of projects (e.g. portals or
geronimo) that may not want to move everything at once)
2. if
altDeploymentRepository${deploy.altRepository}/altDeploymentRepository in
the release profile is actually recommended please document where the value
actually comes from.
3. In the Release Process for part of Maven 1.b it says Verify that all
pom.xml files have an SCM definition. I think this is wrong. IIUC only
root poms in a multimodule project should define scm.
4. In the note on the settings.xml server definition of
apache.snapshots.https please document that it is used from the apache 5 pom.
Also, I think that the password required is your apache svn password rather
than a possible p.a.o password. There is at least one other reference to
logging on to nexus with apache credentials that should be more
specifically apache svn username and password
5. If this is the de-facto advice to apache projects wishing to move from the
file based repo to apache's nexus it needs to be findable through google.
Linking it to INFRA-1885 would be good. Linking from the front page of the
maven docs would be good. More generic separate docs would be better.

[jira] Moved: (MNGSITE-79) Release instructions unclear

2009-03-18 Thread Brett Porter (JIRA)

[
http://jira.codehaus.org/browse/MNGSITE-79?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Brett Porter moved MNG-4095 to MNGSITE-79:
--

Component/s: (was: Documentation: General)
Complexity: (was: Intermediate)
Key: MNGSITE-79 (was: MNG-4095)
Project: Maven 2 Project Web Site (was: Maven 2)

Release instructions unclear

Key: MNGSITE-79
URL: http://jira.codehaus.org/browse/MNGSITE-79
Project: Maven 2 Project Web Site
Issue Type: Improvement
Reporter: David Jencks

[jira] Created: (MSOURCES-41) Generate source jars supporting Eclipse Source Bundle format.

2009-03-18 Thread Don Laidlaw (JIRA)

Generate source jars supporting Eclipse Source Bundle format.
-

 Key: MSOURCES-41
 URL: http://jira.codehaus.org/browse/MSOURCES-41
 Project: Maven 2.x Source Plugin
  Issue Type: New Feature
Affects Versions: 2.0.4
 Environment: Eclipse 3.3+
Reporter: Don Laidlaw


When developing eclipse plugins, or any OSGi bundle, it is desirable to create 
the source attachments for a project as Eclipse Source Bundles. See 
http://wiki.eclipse.org/Source_Bundles

A source bundle appears in the target platform (the bundles in the runtime) and 
allows the user to step into the source in debug, view the source, and see the 
javadoc from the source. All without having to download the source project. 
Source bundles differ from source attachments in non OSGi projects in that they 
are part of the target platform, which is resolved dynamically at runtime, not 
at compile time with the classpath.

It is very easy to extend the maven source plugin to create these source 
bundles. They are identical to the currently generated jar, with the addition 
of a few entries in the META-INF/MANIFEST.MF file. So source jars usable as 
source bundles are also 100% compatible with what is currently generated.

I have already done the work and would be happy to contribute this back if 
there is any interest.

-- 
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: (MRELEASE-428) ForkedMavenExecutor must use ${maven.home}/bin/mvn and not only mvn

ForkedMavenExecutor must use ${maven.home}/bin/mvn and not only mvn
---

 Key: MRELEASE-428
 URL: http://jira.codehaus.org/browse/MRELEASE-428
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
Affects Versions: 2.0-beta-8
Reporter: Olivier Lamy


currently ForkedMavenExecutor use only mvn for forked maven execution.
With bad path, it can failed. It must use ${maven.home}/bin/mvn.

-- 
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: (MRELEASE-428) ForkedMavenExecutor must use ${maven.home}/bin/mvn and not only mvn


 [ 
http://jira.codehaus.org/browse/MRELEASE-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy closed MRELEASE-428.
-

Resolution: Fixed

fix in [rev755740|http://svn.apache.org/viewvc?rev=755740view=rev]

 ForkedMavenExecutor must use ${maven.home}/bin/mvn and not only mvn
 ---

 Key: MRELEASE-428
 URL: http://jira.codehaus.org/browse/MRELEASE-428
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
Affects Versions: 2.0-beta-8
Reporter: Olivier Lamy
Assignee: Olivier Lamy

 currently ForkedMavenExecutor use only mvn for forked maven execution.
 With bad path, it can failed. It must use ${maven.home}/bin/mvn.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

[jira] Commented: (MRELEASE-428) ForkedMavenExecutor must use ${maven.home}/bin/mvn and not only mvn


[ 
http://jira.codehaus.org/browse/MRELEASE-428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=170228#action_170228
 ] 

Olivier Lamy commented on MRELEASE-428:
---

M2_HOME env var added too in [rev 
755744|http://svn.apache.org/viewvc?rev=755744view=rev]

 ForkedMavenExecutor must use ${maven.home}/bin/mvn and not only mvn
 ---

 Key: MRELEASE-428
 URL: http://jira.codehaus.org/browse/MRELEASE-428
 Project: Maven 2.x Release Plugin
  Issue Type: Bug
Affects Versions: 2.0-beta-8
Reporter: Olivier Lamy
Assignee: Olivier Lamy

 currently ForkedMavenExecutor use only mvn for forked maven execution.
 With bad path, it can failed. It must use ${maven.home}/bin/mvn.

-- 
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: (SCM-441) NPE when using Git SCM 1.2-SNAPSHOT


 [ 
http://jira.codehaus.org/browse/SCM-441?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Olivier Lamy closed SCM-441.


Resolution: Fixed

fixed in [rev 755751|http://svn.apache.org/viewvc?rev=755751view=rev]
Thanks !

 NPE when using Git SCM 1.2-SNAPSHOT
 ---

 Key: SCM-441
 URL: http://jira.codehaus.org/browse/SCM-441
 Project: Maven SCM
  Issue Type: Bug
  Components: maven-scm-provider-git
Affects Versions: 1.2
 Environment: Linux and MacOSX, probably everywhere
Reporter: Petter Måhlén
Assignee: Olivier Lamy
 Fix For: 1.2

 Attachments: SCM-441.patch


 This is the log message:
 ---
 [INFO] Storing revision in 'scm.revision' project property.
 [INFO] 
 
 [ERROR] FATAL ERROR
 [INFO] 
 
 [INFO] null
 [INFO] 
 
 [INFO] Trace
 java.lang.NullPointerException
   at java.util.Hashtable.put(Hashtable.java:394)
   at org.apache.maven.scm.plugin.UpdateMojo.execute(UpdateMojo.java:103)
 ---
 Looking at the code:
 public void execute()
 throws MojoExecutionException
 {
 super.execute();  
 
 try
 {
 ScmRepository repository = getScmRepository();
 
 UpdateScmResult result = getScmManager().update( repository, 
 getFileSet(),
  getScmVersion( 
 scmVersionType, scmVersion ),
  runChangelog );  
 
 checkResult( result );
 
 if ( result instanceof UpdateScmResultWithRevision )
 {
 String revision = ( (UpdateScmResultWithRevision) result 
 ).getRevision(); 
 getLog().info( Storing revision in ' + revisionKey + ' 
 project property. );   
 if ( project.getProperties() != null ) // Remove the test 
 when we'll use plugin-test-harness 1.0-alpha-2
   {
 project.getProperties().put( revisionKey, revision ); 
 
 }
 getLog().info( Project at revision  + revision );   
 
 }
 }
 catch ( IOException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 catch ( ScmException e )
 {
 throw new MojoExecutionException( Cannot run update command : , 
 e );
 }
 }
 The problem must be that the 'revision' String is null. I guess that is a bug 
 in the Git SCM provider, but I would argue it is also a bug in the Update 
 mojo, which should be a little bit more resistant to null results.

-- 
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: (SCM-442) Incorrect SCM URL constructed when using parent POM that is not in the parent directory