date:20071106


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

Vincent Siveton closed MSANDBOX-34.
---

  Assignee: Vincent Siveton
Resolution: Cannot Reproduce

Cannot reporduce it after the refactoring

 [jxr] Error for dot target in java.xml
 --

 Key: MSANDBOX-34
 URL: http://jira.codehaus.org/browse/MSANDBOX-34
 Project: Maven 2.x Sandbox
  Issue Type: Bug
  Components: jxr
Reporter: Vincent Siveton
Assignee: Vincent Siveton

 Using the rev 554901 of forrestdoc, the dot target in the src/java.xml 
 produces errors on Windows with graphviz-2.12.
 Here is an extract of the build output:
 {noformat}
 xml2dot:
 Processing 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\xml\xmldocs.xml
  to 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot\graph.dot
 Loading stylesheet 
 D:\temp\forrest\whiteboard\forrestdoc\src\resources\javadoc\xml2dot.xsl
 dot:
 Error: 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:3:
  syntax error near line 3
 context:  Converts  path and classpath information to a specific target 
 OS
 Warning: 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:190:
  string ran past end of line
 Warning: 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:249:
  string ran past end of line
 Result: 1
 uml:
 Using Project dir: D:\temp\forrest\whiteboard\forrestdoc
 Using Target dir: D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\for
 restdoc
 ant buildfine available: true
 dot:
 Error: 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:3:
  syntax error near line 3
 context:  Converts  path and classpath information to a specific target 
 OS
 Warning: 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:190:
  string ran past end of line
 Warning: 
 D:\temp\forrest\whiteboard\forrestdoc\build\forrestdoc\forrestdoc\dot/graph.dot:249:
  string ran past end of line
 Result: 1
 {noformat}
 It seems that the xml2dot target produces wrong graph.dot.
 Here is an extract from build\forrestdoc\forrestdoc\dot\graph.dot
 {noformat}
 Converts path and classpath information to a specific target OS
  format. The resulting formatted path is placed into the specified 
 property.Ant 1.4
 category=utility
 constructor
 Create a nested PATH element
 ...
 {noformat} 
 Refer to https://issues.apache.org/jira/browse/FOR-1023

-- 
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: (MSANDBOX-35) [jxr] JavaSrcTask needs to handle a custom bottom


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

Vincent Siveton closed MSANDBOX-35.
---

  Assignee: Vincent Siveton
Resolution: Fixed

Done in 588222

 [jxr] JavaSrcTask needs to handle a custom bottom
 -

 Key: MSANDBOX-35
 URL: http://jira.codehaus.org/browse/MSANDBOX-35
 Project: Maven 2.x Sandbox
  Issue Type: Improvement
  Components: jxr
Reporter: Vincent Siveton
Assignee: Vincent Siveton

 We need to handle a custom bottom instead to have static one: the following 
 code is harcoded in Pass2.java
 {noformat}
 Copyright copy; 2001-2003 Apache Software Foundation. All Rights Reserved.
 {noformat} 
 Refer to https://issues.apache.org/jira/browse/FOR-1030

-- 
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: (SUREFIRE-156) Typo in JavaDoc comment of deprecated classorg.apache.maven.test.SurefirePlugin

2007-11-06 Thread Marat Radchenko (JIRA)


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

Marat Radchenko updated SUREFIRE-156:
-

Attachment: SUREFIRE-156.patch

better patch

 Typo in JavaDoc comment of deprecated 
 classorg.apache.maven.test.SurefirePlugin
 ---

 Key: SUREFIRE-156
 URL: http://jira.codehaus.org/browse/SUREFIRE-156
 Project: Maven Surefire
  Issue Type: Bug
  Components: documentation
Reporter: Andreas Guther
Priority: Trivial
 Fix For: 2.3.1

 Attachments: patch.txt, SUREFIRE-156.patch


 The deprecated documentation for use instead of the JavaDoc has a typo: the 
 package name contains a letter s.  Patch attached.

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

[jira] Created: (CONTINUUM-1551) the builds are not ordered by date

2007-11-06 Thread Ionut S (JIRA)

the builds are not ordered by date
--

 Key: CONTINUUM-1551
 URL: http://jira.codehaus.org/browse/CONTINUUM-1551
 Project: Continuum
  Issue Type: Bug
Affects Versions: 1.1-beta-4
 Environment: RHEL AS 4.0
Reporter: Ionut S
 Attachments: builds-not-in-order.png

Sometimes the build in progress doesn't appear the last in the list, but 
somewhere below other builds who are already finished.



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

[jira] Created: (CONTINUUM-1550) Upgrade documentation commands don't work

2007-11-06 Thread fdb (JIRA)

Upgrade documentation commands don't work
-

 Key: CONTINUUM-1550
 URL: http://jira.codehaus.org/browse/CONTINUUM-1550
 Project: Continuum
  Issue Type: Bug
  Components: Data Management
Affects Versions: 1.1-beta-3
 Environment: Linux / Any
Reporter: fdb
Priority: Minor


http://maven.apache.org/continuum/documentation/1_1/installation/upgrade.html

exporting section:
the -file argument does not exist, should be -directory? x2

importing section:
the first line had the directory argument missing: -directory
the -f argument does not exist, should be -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

[jira] Commented: (CONTINUUM-1492) error when trying to run data management tool when behind a proxied firewall

2007-11-06 Thread fdb (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-1492?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112952
 ] 

fdb commented on CONTINUUM-1492:


Olivier, i got the same problems while having this ~/.m2/settings.xml
using the -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=8080 everything 
works fine

(exporting from beta3)

settings
  proxies
   proxy
  activetrue/active
  protocolhttp/protocol
  hosthttp-proxy.xxx.com/host
  port8080/port
  nonProxyHostswww.google.com|*.xxx.local/nonProxyHosts
/proxy
  /proxies
/settings


 error when trying to run data management tool when behind a proxied firewall
 

 Key: CONTINUUM-1492
 URL: http://jira.codehaus.org/browse/CONTINUUM-1492
 Project: Continuum
  Issue Type: Bug
  Components: Data Management
Affects Versions: 1.1-beta-3
Reporter: Tomislav Stojcevich

 Using -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 
 -Dproxy.User=myuserid -Dhttp.proxyPassword=mypassword doesn't work
 Setting -Djava.net.useSystemProxies=true doesn't work
 Setting -Dhttp.auth.ntlm.domain=mydomain doesn't work
 Nor does it pick up the proxy settings in my settings.xml file.
 0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  - 
 Processing Continuum database...
 Exception in thread main 
 org.apache.maven.artifact.resolver.MultipleArtifactsNotFoundException: 
 Missing:
 --
 1) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3
   Try downloading the file manually from the project website.
   Then, install it using the command:
   mvn install:install-file -DgroupId=org.apache.maven.continuum 
 -DartifactId=data-management-jdo \
   -Dversion=1.1-beta-3 -Dpackaging=jar -Dfile=/path/to/file
   Path to dependency:
 1) dummy:dummy:pom:1.0
 2) org.apache.maven.continuum:data-management-jdo:jar:1.1-beta-3
 --
 1 required artifact is missing.
 for artifact:
   dummy:dummy:pom:1.0
 from the specified remote repositories:
   central (http://repo1.maven.org/maven2)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:305)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:272)
 at 
 org.apache.maven.artifact.resolver.DefaultArtifactResolver.resolveTransitively(DefaultArtifactResolver.java:243)
 at 
 org.apache.maven.continuum.management.DataManagementCli.downloadArtifact(DataManagementCli.java:292)
 at 
 org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:173)
 at 
 org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:146)

-- 
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] Issue Comment Edited: (MSITE-262) site.xml not inherited if build run from parent


[ 
http://jira.codehaus.org/browse/MSITE-262?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112953
 ] 

Cameron Jones edited comment on MSITE-262 at 11/6/07 8:44 AM:
--

Here's a project which displays the behavior. If run from the parent as a 
recursive build the module's site menu doesn't contain the inherited parent 
menu.


 was:
Here's a project which displays the behavior

 site.xml not inherited if build run from parent
 ---

 Key: MSITE-262
 URL: http://jira.codehaus.org/browse/MSITE-262
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
 Attachments: MSITE-262.zip


 I've seen that the site.xml is not being inherited in a module when the build 
 is run from the parent - when run from the module itself the inheritance 
 works correctly.

-- 
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: (MSITE-262) site.xml not inherited if build run from parent


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

Cameron Jones updated MSITE-262:


Attachment: MSITE-262.zip

Here's a project which displays the behavior

 site.xml not inherited if build run from parent
 ---

 Key: MSITE-262
 URL: http://jira.codehaus.org/browse/MSITE-262
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
 Attachments: MSITE-262.zip


 I've seen that the site.xml is not being inherited in a module when the build 
 is run from the parent - when run from the module itself the inheritance 
 works correctly.

-- 
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: (MSITE-263) NullPointerException if build run from a module and no url defined in module or parent


[ 
http://jira.codehaus.org/browse/MSITE-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112951
 ] 

Cameron Jones commented on MSITE-263:
-

I can't seem to replicate this either - sorry must have been some other 
configuration option which was affecting this. I've since lost that old 
config...

 NullPointerException if build run from a module and no url defined in module 
 or parent
 --

 Key: MSITE-263
 URL: http://jira.codehaus.org/browse/MSITE-263
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
Priority: Trivial
 Attachments: MSITE-263.zip


 i've found that you get a null pointer exception if there is no url defined 
 on a module or on it's parent pom. If the build is run from the parent it 
 works but gives a warning that urls will not be decorated. Adding the url 
 back to the parent fixes the issue. Here's the stacktrace:
 java.lang.NullPointerException
 at 
 org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83)
 at 
 org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:251)
 at 
 org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:525)
 at 
 org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:464)
 at 
 org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:114)
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
 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:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

-- 
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: (MSITE-269) Urls rewritten when they contain the project urls' hostname


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

Cameron Jones updated MSITE-269:


Attachment: MSITE-269.zip

Yeah but the problem is that i don't want the urls to be relative. I have the 
following environments which i want to link to in the site:

build - http://localhost/build
staging - http://localhost/staging
prod - http://localhost/prod

And i want to deploy my site under:

http://localhost/project/test/site

I want the environment links to be static as they aren't related to the site 
itself and are there only for navigation but instead they are rewritten to:

http://localhost/project/test/site/build
http://localhost/project/test/site/staging
http://localhost/project/test/site/prod

I've included a test project which displays this.

 Urls rewritten when they contain the project urls' hostname
 ---

 Key: MSITE-269
 URL: http://jira.codehaus.org/browse/MSITE-269
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
Assignee: Dennis Lundberg
 Attachments: MSITE-269.zip, pom.xml, site.xml


 Urls in the site.xml file are being rewritten if they contain the hostname of 
 the project url. For example:
 pom.xml:
 urlhttp://208.75.85.243/url
 ...
 site
 idtest.site/id
 urlfile:///srv/www/test/site/url
 /site
 ...
 site.xml:
 item name=About href=http://208.75.85.243/index.html; /
 Results in the following link for the About page which is incorrect and 
 includes the deployment location instead of the url:
 http://208.75.85.243/test/site/index.html

-- 
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] Reopened: (MSITE-269) Urls rewritten when they contain the project urls' hostname


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

Cameron Jones reopened MSITE-269:
-


 Urls rewritten when they contain the project urls' hostname
 ---

 Key: MSITE-269
 URL: http://jira.codehaus.org/browse/MSITE-269
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
Assignee: Dennis Lundberg
 Attachments: MSITE-269.zip, pom.xml, site.xml


 Urls in the site.xml file are being rewritten if they contain the hostname of 
 the project url. For example:
 pom.xml:
 urlhttp://208.75.85.243/url
 ...
 site
 idtest.site/id
 urlfile:///srv/www/test/site/url
 /site
 ...
 site.xml:
 item name=About href=http://208.75.85.243/index.html; /
 Results in the following link for the About page which is incorrect and 
 includes the deployment location instead of the url:
 http://208.75.85.243/test/site/index.html

-- 
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: (MWAR-129) WebRessource not filtered

2007-11-06 Thread Jean-Yves LEBLEU (JIRA)

WebRessource not filtered
-

 Key: MWAR-129
 URL: http://jira.codehaus.org/browse/MWAR-129
 Project: Maven 2.x War Plugin
  Issue Type: Bug
Affects Versions: 2.1-alpha-1
 Environment: windows, maven 2.0.7
Reporter: Jean-Yves LEBLEU


Previously Webressources were correctly filtered and are not filtered any more 

See above extract from pom.xml 
  plugin
artifactIdmaven-war-plugin/artifactId
version2.0.2/version
configuration
  warSourceDirectorysrc/main/webapp/warSourceDirectory
  webResources
resource
  filteringtrue/filtering
  directorysrc/main/webapp/directory
  targetPath./targetPath
  includes
includeparam.jsp/include
  /includes
/resource
  /webResources
/configuration
  /plugin

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

[jira] Commented: (MNG-3234) org.apache.maven.lifecycle.LifecycleExecutionException

2007-11-06 Thread David Hilton (JIRA)


[ 
http://jira.codehaus.org/browse/MNG-3234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112959
 ] 

David Hilton commented on MNG-3234:
---

Hi,

Had a similar problem because I am working behind a firewall and we use a proxy 
server for internet access

Look here http://maven.apache.org/guides/mini/guide-proxies.html for 
instruction on how to set up your proxy access for mavern, the Windows 
folder\file you want tp create is;

C:\Documents and Settings\'your windows login name'\.m2\settings.xml

content is ...

settings
  .
  .
  proxies
   proxy
  activetrue/active
  protocolhttp/protocol
  hostproxy.somewhere.com/host
  port8080/port
  usernameproxyuser/username
  passwordsomepassword/password
  nonProxyHostswww.google.com|*.somewhere.com/nonProxyHosts
/proxy
  /proxies
  .
  .
/settings

with your settings inserted.

On *nix it the file will be ~\.m2\settings.xml

 org.apache.maven.lifecycle.LifecycleExecutionException
 --

 Key: MNG-3234
 URL: http://jira.codehaus.org/browse/MNG-3234
 Project: Maven 2
  Issue Type: Bug
  Components: Plugin API
Affects Versions: 2.0.7
Reporter: subin Balachandran Nair
Assignee: Brett Porter

 Hi ,
 I am new to Maven. I installed maven in my local machine and add the maven 
 path(C:\maven2.0.7.\bin) in the 
 PATH also.
 This is my mvn version 
 
 C:\maven-2.0.7\binmvn --version
 Maven version: 2.0.7
 Java version: 1.5.0_13
 OS name: windows xp version: 5.1 arch: x86
 But while running mvn -U compile, getting error
 C:\maven-2.0.7mvn -U compile
 [INFO] Scanning for projects...
 [INFO] 
 -
 ---
 [INFO] Building Maven Default Project
 [INFO]task-segment: [compile]
 [INFO] 
 -
 ---
 [INFO] artifact org.apache.maven.plugins:maven-resources-plugin: checking for 
 up
 dates from central
 [WARNING] repository metadata for: 'artifact 
 org.apache.maven.plugins:maven-reso
 urces-plugin' could not be retrieved from repository: central due to an 
 error: E
 rror transferring file
 [INFO] Repository 'central' will be blacklisted
 [INFO] 
 
 [ERROR] BUILD ERROR
 [INFO] 
 
 [INFO] The plugin 'org.apache.maven.plugins:maven-resources-plugin' does not 
 exi
 st or no valid version could be found
 [INFO] 
 
 [INFO] For more information, run Maven with the -e switch
 [INFO] 
 
 [INFO] Total time: 23 seconds
 [INFO] Finished at: Wed Oct 10 16:18:28 IST 2007
 [INFO] Final Memory: 1M/2M
 [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

[jira] Created: (CONTINUUM-1552) When trying to export the user database - FileNotFoundException: backups/users/keys.xml (No such file or directory)

2007-11-06 Thread fdb (JIRA)

When trying to export the user database - FileNotFoundException: 
backups/users/keys.xml (No such file or directory)


 Key: CONTINUUM-1552
 URL: http://jira.codehaus.org/browse/CONTINUUM-1552
 Project: Continuum
  Issue Type: Bug
  Components: Data Management
Affects Versions: 1.1-beta-3
 Environment: Linux / Http Proxy
Reporter: fdb


java -Xmx512m -jar data-management-cli-1.1-beta-3-app.jar -usersJdbcUrl 
jdbc:derby:continuum-1.1-beta-3/data/users/database -mode EXPORT -directory 
backups/users
0 [main] INFO org.apache.maven.continuum.management.DataManagementCli  - 
Processing Redback database...
2605 [main] WARN JPOX.JDO  - Property org.jpox.validateSchema unknown - will be 
ignored
2854 [main] INFO JPOX.JDO  - PersistenceManagerFactory - Vendor: JPOX  Version: 
1.1.6
2854 [main] INFO JPOX.JDO  - PersistenceManagerFactory initialised for 
datastore URL=jdbc:derby:continuum-1.1-beta-3/data/users/database 
driver=org.apache.derby.jdbc.EmbeddedDriver userName=sa
4378 [main] INFO JPOX.RDBMS  -  DatabaseAdapter 
==
4378 [main] INFO JPOX.RDBMS  - Adapter : 
org.jpox.store.rdbms.adapter.DerbyAdapter
4378 [main] INFO JPOX.RDBMS  - Datastore : name=Apache Derby 
version=10.1.3.1 (major=10, minor=1, revision=3)
4378 [main] INFO JPOX.RDBMS  - Driver : name=Apache Derby Embedded JDBC 
Driver version=10.1.3.1 (major=10, minor=1)
4378 [main] INFO JPOX.RDBMS  - 
===
4427 [main] INFO JPOX.RDBMS.Schema  - Initialising Catalog , Schema SA 
using SchemaTable auto-start option
5305 [main] INFO JPOX.JDO  - Managing Persistence of 
org.codehaus.plexus.redback.keys.jdo.JdoAuthenticationKey since it was managed 
previously
5327 [main] WARN JPOX.MetaData  - No manager for annotations was found in the 
CLASSPATH so all annotations are ignored.
3974 [main] INFO JPOX.RDBMS.Schema  - Managing Persistence of Class : 
org.codehaus.plexus.redback.keys.jdo.JdoAuthenticationKey [Table : 
JDOAUTHENTICATIONKEY, InheritanceStrategy : new-table]
5870 [main] INFO JPOX.RDBMS  - Validated 1 unique key(s) for table 
JDOAUTHENTICATIONKEY
5897 [main] INFO JPOX.RDBMS  - Validated 1 index(es) for table 
JDOAUTHENTICATIONKEY
5899 [main] INFO JPOX.RDBMS.Schema  - Catalog , Schema SA initialised - 
managing 1 classes
Exception in thread main java.io.FileNotFoundException: 
backups/users/keys.xml (No such file or directory)
at java.io.FileOutputStream.open(Native Method)
at java.io.FileOutputStream.init(FileOutputStream.java:179)
at java.io.FileOutputStream.init(FileOutputStream.java:131)
at java.io.FileWriter.init(FileWriter.java:73)
at 
org.codehaus.plexus.redback.management.JdoDataManagementTool.backupKeyDatabase(JdoDataManagementTool.java:115)
at 
org.apache.maven.continuum.management.redback.JdoDataManagementTool.backupDatabase(JdoDataManagementTool.java:66)
at 
org.apache.maven.continuum.management.DataManagementCli.processDatabase(DataManagementCli.java:238)
at 
org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:153)

-- 
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: (SUREFIRE-343) html escaping problems in xml reports

2007-11-06 Thread Marat Radchenko (JIRA)


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

Marat Radchenko updated SUREFIRE-343:
-

Attachment: SUREFIRE-343.patch

patch

 html escaping problems in xml reports
 -

 Key: SUREFIRE-343
 URL: http://jira.codehaus.org/browse/SUREFIRE-343
 Project: Maven Surefire
  Issue Type: Bug
  Components: xml generation
Affects Versions: 2.0 (2.2 plugin)
Reporter: Brydie McCoy
Priority: Minor
 Fix For: 2.3.1

 Attachments: SUREFIRE-343.patch


 Hi,
 I'm having some problems with the escaping of html specific characters 
 (namely the  and ) in the surefire reports.   
 The following example test:
 {code}
public void testShouldFail() throws Exception
 {
 fail(htmlbodyh2 This Failed /h2/body/html);
}
 {code}
 resulted in the following xml report 
 {code}
 testcase time=0 name=testShouldFail
 failure type=junit.framework.AssertionFailedError 
 message=amp;lt;htmlamp;gt;amp;lt;bodyamp;gt;amp;lt;h2amp;gt; This 
 Failed amp;lt;/h2amp;gt;amp;lt;/bodyamp;gt;amp;lt;/htmlamp;gt;
 junit.framework.AssertionFailedError: 
 amp;htmlamp;amp;bodyamp;amp;h2amp; This Failed 
 amp;/h2amp;amp;/bodyamp;amp;/htmlamp;
   at junit.framework.Assert.fail(Assert.java:47)
   at FailingTest.testShouldFail(FailingTest.java:7)
/failure
 /testcase
 {code}
 The text in the message' attribute has been correctly escaped but the text 
 within the failure tags seems to just have amp; for any of the html 
 characters. 

-- 
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: (MECLIPSE-340) Option to point source-path at target/artifactId-version

2007-11-06 Thread Taras Lipatov (JIRA)

Option to point source-path at target/artifactId-version


 Key: MECLIPSE-340
 URL: http://jira.codehaus.org/browse/MECLIPSE-340
 Project: Maven 2.x Eclipse Plugin
  Issue Type: New Feature
  Components: WTP support
Reporter: Taras Lipatov
Priority: Minor


Not sure if this is available and if not, why its not...

Our app requires processing of config files prior to deployment. so thre is no 
way to fire up the app from src/main/webapp
Currently we manually edit .settings/org.eclipse.wst.common.component
But  target/artifactId-version changes with every release, so we need to keep 
track.

We can then automatically regenerate the org.eclipse.wst.common.component file 
with every release.

-- 
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: (MRM-569) Browse shows results for all repositories, regardless of security.

2007-11-06 Thread Joakim Erdfelt (JIRA)


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

Joakim Erdfelt closed MRM-569.
--

Resolution: Fixed

Completed work merged from branch to trunk in revision 592513.

 Browse shows results for all repositories, regardless of security.
 --

 Key: MRM-569
 URL: http://jira.codehaus.org/browse/MRM-569
 Project: Archiva
  Issue Type: Bug
  Components: Users/Security
Affects Versions: 1.0-beta-3
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
Priority: Critical
 Fix For: 1.0-beta-4


 When browsing archiva (using the browse link on the left hand navigation 
 bar), the results are for all repositories, regardless of security.
 This needs to be filtered based on access rights of the user.

-- 
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: (MRM-516) Search results return results for all repositories, regardless of security.

2007-11-06 Thread Joakim Erdfelt (JIRA)


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

Joakim Erdfelt closed MRM-516.
--

Resolution: Fixed

Completed work merged from branch to trunk in revision 592513.

 Search results return results for all repositories, regardless of security.
 ---

 Key: MRM-516
 URL: http://jira.codehaus.org/browse/MRM-516
 Project: Archiva
  Issue Type: Bug
  Components: indexing
Affects Versions: 1.0-beta-2
Reporter: Joakim Erdfelt
Assignee: Joakim Erdfelt
Priority: Critical
 Fix For: 1.0-beta-4


 The UserAllowedToSearchRepositoryPredicate needs to be finished.
 It should take the current user, their RBAC roles, and filter based on the 
 roles available to the user.

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

[jira] Commented: (MNG-3269) Different builds for ejb-client optional with parent

2007-11-06 Thread Tim Reilly (JIRA)

[
http://jira.codehaus.org/browse/MNG-3269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112979
]

Tim Reilly commented on MNG-3269:
-

I wanted to check with the team I work with about this. They basically said
they are not against this, but they would like to know more about how this
change would be implemented before 'giving a thumbs up' at least for our team
here.

On a different but potentially related noete: I can say that we ran into a
seemly unresolvable issue a few months ago. We build (or at least tried to
build) a properties file into the ear's resource directory. In the Ant world
this worked fine for them, but when we moved to Maven we could not figure out
how to get the property file in the ear referenced in the war's manifest
class-path (and still use the add classpath feature of the mwar plugin.)

Let us know what the change might look like and I'll run it by the various team
members here to see what they think.

Thank you

Different builds for ejb-client optional with parent

Key: MNG-3269
URL: http://jira.codehaus.org/browse/MNG-3269
Project: Maven 2
Issue Type: Bug
Affects Versions: 2.0.7
Reporter: Tim Reilly
Attachments: MWAR114-maven-war-plugin-2.0.2.patch,
MWAR114-maven-war-plugin-2.0.2.patch,
MWAR114-maven-war-plugin-2.1-alpha-1.patch, mytime.zip

When trying to package a j2ee project's ejb-client artifact in the ear /lib
directory the war plugin's optional attribute is ignored if building from the
parent app project. If you build from the parent project you get the
ejb-client packaged in the web-inf/lib directory. If you build the ejb, war,
and ear independently you get the ejb-client packaged in the ear /lib
directory. It seems when run from the parent project the dependency/artifact
doesn't have the optional attribute set.
Perhaps this is b/c the artifact is a project artifact that was attached from
the ejb plugin it is not resolved as optional when the dependency is resolved
from the war project.
Attaching Geronimo's mytime sample with modifications to reproduce the
behavior.

[jira] Commented: (CONTINUUM-1551) the builds are not ordered by date

2007-11-06 Thread Ionut S (JIRA)


[ 
http://jira.codehaus.org/browse/CONTINUUM-1551?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112983
 ] 

Ionut S commented on CONTINUUM-1551:


Now I remember I deleted a stalled build (whose state was still In progress 
after 15 hours)
So this might be an extra tip to reproduce the bug..

 the builds are not ordered by date
 --

 Key: CONTINUUM-1551
 URL: http://jira.codehaus.org/browse/CONTINUUM-1551
 Project: Continuum
  Issue Type: Bug
Affects Versions: 1.1-beta-4
 Environment: RHEL AS 4.0
Reporter: Ionut S
 Attachments: builds-not-in-order.png


 Sometimes the build in progress doesn't appear the last in the list, but 
 somewhere below other builds who are already finished.

-- 
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: (MEJB-29) ejbClient javadoc option

2007-11-06 Thread darren hartford (JIRA)

ejbClient javadoc option


 Key: MEJB-29
 URL: http://jira.codehaus.org/browse/MEJB-29
 Project: Maven 2.x Ejb Plugin
  Issue Type: New Feature
Affects Versions: 2.1
Reporter: darren hartford


usecase:  Create a client jar that already includes javadoc.

Either modify the clientIncludes to grab files from other locations, or 
modify plugin to integrate to support  for Javadoc plugin.

Note that including the javadoc output to /target/classes includes parts of 
those files within the regular artifact, which is not the intent.

clientIncludes../apidocs/**.*/clientIncludes does not work.
clientInclude${project.build.directory}/apidocs/**/*.*/clientInclude does 
not work.


-- 
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: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112994
 ] 

Daniel Kulp commented on MSOURCES-27:
-

Note:  it's only grabbing the SVN directories for SOURCE directories, not 
resource directories.   

The default excludes seem to be OK for resources.


 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
 Fix For: 2.0.3


 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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] Issue Comment Edited: (MSOURCES-26) source:jar ignoring remote-resources


[ 
http://jira.codehaus.org/browse/MSOURCES-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112993
 ] 

Daniel Kulp edited comment on MSOURCES-26 at 11/6/07 4:13 PM:
--

This is due to the change:
{code}
-if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) ) 
-{ 
-archiver.addDirectory( new File( r.getDirectory() ) ); 
-} 
{code}
to:
{code}
+if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
+{
+addDirectory( archiver, new File( r.getDirectory() ), new 
String[]{}, new String[]{} );
+}
{code}
The includesis empty so nothing is included. Changing it to:
{code}
if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
{
addDirectory( archiver, new File( r.getDirectory() ), 
DEFAULT_INCLUDES, new String[0] );
}
{code}
works fine.




 was:

This is due to the change:

-if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) ) 
-{ 
-archiver.addDirectory( new File( r.getDirectory() ) ); 
-} 

to:

+if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
+{
+addDirectory( archiver, new File( r.getDirectory() ), new 
String[]{}, new String[]{} );
+}

The includesis empty so nothing is included. Changing it to:

if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
{
addDirectory( archiver, new File( r.getDirectory() ), 
DEFAULT_INCLUDES, new String[0] );
}

works fine.



 source:jar ignoring remote-resources
 

 Key: MSOURCES-26
 URL: http://jira.codehaus.org/browse/MSOURCES-26
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
Priority: Critical

 The source jar created does not include the resources generated from the 
 remote-resources plugin.  This works fine with 2.0.2, but not with 2.0.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

[jira] Issue Comment Edited: (MSOURCES-26) source:jar ignoring remote-resources


[ 
http://jira.codehaus.org/browse/MSOURCES-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112993
 ] 

Daniel Kulp edited comment on MSOURCES-26 at 11/6/07 4:12 PM:
--


This is due to the change:

-if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) ) 
-{ 
-archiver.addDirectory( new File( r.getDirectory() ) ); 
-} 

to:

+if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
+{
+addDirectory( archiver, new File( r.getDirectory() ), new 
String[]{}, new String[]{} );
+}

The includesis empty so nothing is included. Changing it to:

if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
{
addDirectory( archiver, new File( r.getDirectory() ), 
DEFAULT_INCLUDES, new String[0] );
}

works fine.




 was:


This is due to the change:

-if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) ) 
-{ 
-archiver.addDirectory( new File( r.getDirectory() ) ); 
-} 

to:

+if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
+{
+addDirectory( archiver, new File( r.getDirectory() ), new 
String[]{}, new String[]{} );
+}

The includesis empty so nothing is included. Changing it to:

if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
{
addDirectory( archiver, new File( r.getDirectory() ), 
DEFAULT_INCLUDES, new String[0] );
}

works fine.



 source:jar ignoring remote-resources
 

 Key: MSOURCES-26
 URL: http://jira.codehaus.org/browse/MSOURCES-26
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
Priority: Critical

 The source jar created does not include the resources generated from the 
 remote-resources plugin.  This works fine with 2.0.2, but not with 2.0.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

[jira] Closed: (MSOURCES-26) source:jar ignoring remote-resources


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

Dennis Lundberg closed MSOURCES-26.
---

 Assignee: Dennis Lundberg
   Resolution: Fixed
Fix Version/s: 2.0.4

Fixed, thanks!

 source:jar ignoring remote-resources
 

 Key: MSOURCES-26
 URL: http://jira.codehaus.org/browse/MSOURCES-26
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
Assignee: Dennis Lundberg
Priority: Critical
 Fix For: 2.0.4


 The source jar created does not include the resources generated from the 
 remote-resources plugin.  This works fine with 2.0.2, but not with 2.0.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

[jira] Commented: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112996
 ] 

Dennis Lundberg commented on MSOURCES-27:
-

I have checked the source code and it used the default excludes from 
org.codehaus.plexus.util.DirectoryScanner, which excludes **/.svn and 
**/.svn/** among other things.

I also tried this on the trunk of commons-logging using maven-source-plugin 
2.0.3 and 2.0.4-SNAPSHOT and none of them include any .svn directories.

Do you have a publicly available test case that isn't working for you?

 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MSOURCES-27) source jar includes .svn directories


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

Dennis Lundberg updated MSOURCES-27:


  Description: 
source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 did 
not.



  was:

source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 did 
not.



Fix Version/s: (was: 2.0.3)

 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MSOURCES-26) source:jar ignoring remote-resources


[ 
http://jira.codehaus.org/browse/MSOURCES-26?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112993
 ] 

Daniel Kulp commented on MSOURCES-26:
-



This is due to the change:

-if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) ) 
-{ 
-archiver.addDirectory( new File( r.getDirectory() ) ); 
-} 

to:

+if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
+{
+addDirectory( archiver, new File( r.getDirectory() ), new 
String[]{}, new String[]{} );
+}

The includesis empty so nothing is included. Changing it to:

if ( r.getDirectory().endsWith( 
maven-shared-archive-resources ) )
{
addDirectory( archiver, new File( r.getDirectory() ), 
DEFAULT_INCLUDES, new String[0] );
}

works fine.



 source:jar ignoring remote-resources
 

 Key: MSOURCES-26
 URL: http://jira.codehaus.org/browse/MSOURCES-26
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
Priority: Critical

 The source jar created does not include the resources generated from the 
 remote-resources plugin.  This works fine with 2.0.2, but not with 2.0.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

[jira] Commented: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl


[ 
http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112992
 ] 

Dennis Lundberg commented on MPIR-74:
-

Are you saying that we can't release maven-pir-plugin 2.1 until this is fixed? 
Otherwise I would like to push this issue to the next release.

 Move logic inside AbstractProjectInfoReport to maven-reporting-impl
 ---

 Key: MPIR-74
 URL: http://jira.codehaus.org/browse/MPIR-74
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Vincent Siveton
Priority: Blocker
 Fix For: 2.1


 Due to doxia:1.0-alpha-9, the following methods need to be a part of 
 maven-reporting-impl:
 private File getSkinArtifactFile();
 public void execute();
 So, it should be more easy to create a new report plugin.

-- 
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: (MSOURCES-26) source:jar ignoring remote-resources

source:jar ignoring remote-resources


 Key: MSOURCES-26
 URL: http://jira.codehaus.org/browse/MSOURCES-26
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
Priority: Critical



The source jar created does not include the resources generated from the 
remote-resources plugin.  This works fine with 2.0.2, but not with 2.0.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

[jira] Closed: (MSITE-269) Urls rewritten when they contain the project urls' hostname


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

Dennis Lundberg closed MSITE-269.
-

Resolution: Duplicate

Please make any comments you might have regarding this in MSITE-159 instead.

 Urls rewritten when they contain the project urls' hostname
 ---

 Key: MSITE-269
 URL: http://jira.codehaus.org/browse/MSITE-269
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
Assignee: Dennis Lundberg
 Attachments: MSITE-269.zip, pom.xml, site.xml


 Urls in the site.xml file are being rewritten if they contain the hostname of 
 the project url. For example:
 pom.xml:
 urlhttp://208.75.85.243/url
 ...
 site
 idtest.site/id
 urlfile:///srv/www/test/site/url
 /site
 ...
 site.xml:
 item name=About href=http://208.75.85.243/index.html; /
 Results in the following link for the About page which is incorrect and 
 includes the deployment location instead of the url:
 http://208.75.85.243/test/site/index.html

-- 
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: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113000
 ] 

Daniel Kulp commented on MSOURCES-27:
-


This one is a bit more complex.For CXF, we have properties files in the 
src/main/java dir (i18n message files) that are included via resource.   Thus, 
in the pom, we have:

resources
resource
directorysrc/main/java/directory
excludes
exclude**/*.java/exclude
/excludes
/resource
/resources
to grab all the non-java files as resources.

The new source plugin uses the **/*.java as an exclude, but but DOESN'T add the 
list of default excludes.   Thus, the source plugin will get the .svn dirs.

Basically, for resources that don't have excludes, the source plugin works fine 
as it uses the default excludes.   For those that DO define an exclude, it 
doesn't quite work as expected.





 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MSOURCES-27) source jar includes .svn directories

source jar includes .svn directories


 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp
 Fix For: 2.0.3



source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 did 
not.



-- 
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: (MSITE-266) Schedule and release doxia 1.0-alpha-10


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

Dennis Lundberg closed MSITE-266.
-

Resolution: Fixed

Done.

 Schedule and release doxia 1.0-alpha-10
 ---

 Key: MSITE-266
 URL: http://jira.codehaus.org/browse/MSITE-266
 Project: Maven 2.x Site Plugin
  Issue Type: Task
  Components: doxia integration
Affects Versions: 2.0-beta-6
Reporter: Olivier Lamy
Assignee: Dennis Lundberg
Priority: Critical
 Fix For: 2.0-beta-6




-- 
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: (MSITE-263) NullPointerException if build run from a module and no url defined in module or parent


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

Dennis Lundberg closed MSITE-263.
-

  Assignee: Dennis Lundberg
Resolution: Cannot Reproduce

 NullPointerException if build run from a module and no url defined in module 
 or parent
 --

 Key: MSITE-263
 URL: http://jira.codehaus.org/browse/MSITE-263
 Project: Maven 2.x Site Plugin
  Issue Type: Bug
Reporter: Cameron Jones
Assignee: Dennis Lundberg
Priority: Trivial
 Attachments: MSITE-263.zip


 i've found that you get a null pointer exception if there is no url defined 
 on a module or on it's parent pom. If the build is run from the parent it 
 works but gives a warning that urls will not be decorated. Adding the url 
 back to the parent fixes the issue. Here's the stacktrace:
 java.lang.NullPointerException
 at 
 org.apache.maven.doxia.site.decoration.inheritance.PathUtils.getRelativePath(PathUtils.java:83)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.PathUtils.convertPath(PathUtils.java:43)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.convertPath(DefaultDecorationModelInheritanceAssembler.java:334)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.resolveLinkItemPaths(DefaultDecorationModelInheritanceAssembler.java:255)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.mergeLinkItemLists(DefaultDecorationModelInheritanceAssembler.java:277)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleBodyInheritance(DefaultDecorationModelInheritanceAssembler.java:192)
 at 
 org.apache.maven.doxia.site.decoration.inheritance.DefaultDecorationModelInheritanceAssembler.assembleModelInheritance(DefaultDecorationModelInheritanceAssembler.java:83)
 at 
 org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:251)
 at 
 org.apache.maven.plugins.site.AbstractSiteRenderingMojo.getDecorationModel(AbstractSiteRenderingMojo.java:525)
 at 
 org.apache.maven.plugins.site.AbstractSiteRenderingMojo.createSiteRenderingContext(AbstractSiteRenderingMojo.java:464)
 at 
 org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:114)
 at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:97)
 at 
 org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:443)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:459)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278)
 at 
 org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:334)
 at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:125)
 at org.apache.maven.cli.MavenCli.main(MavenCli.java:272)
 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:315)
 at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
 at 
 org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
 at org.codehaus.classworlds.Launcher.main(Launcher.java:375)

-- 
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] Issue Comment Edited: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_112996
 ] 

Dennis Lundberg edited comment on MSOURCES-27 at 11/6/07 5:15 PM:
--

I have checked the source code and it used the default excludes from 
org.codehaus.plexus.util.DirectoryScanner, which excludes \*\*/.svn and 
\*\*/.svn/\*\* among other things.

I also tried this on the trunk of commons-logging using maven-source-plugin 
2.0.3 and 2.0.4-SNAPSHOT and none of them include any .svn directories.

Do you have a publicly available test case that isn't working for you?


 was:
I have checked the source code and it used the default excludes from 
org.codehaus.plexus.util.DirectoryScanner, which excludes **/.svn and 
**/.svn/** among other things.

I also tried this on the trunk of commons-logging using maven-source-plugin 
2.0.3 and 2.0.4-SNAPSHOT and none of them include any .svn directories.

Do you have a publicly available test case that isn't working for you?

 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113005
 ] 

Dennis Lundberg commented on MSOURCES-27:
-

Do you expect the exclude to mean: use the default excludes and add this 
one? And that was the behavior in maven-sources-plugin 2.0.2?

Just out of curiosity, is there a reason for not having the properties files in 
/src/main/resources/... ?

 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl


[ 
http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113009
 ] 

Vincent Siveton commented on MPIR-74:
-

The main goal of this issue was how to create a new MavenReport (which extends 
AbstractMavenReport) with new Doxia dependency. The main pb that I found is how 
to use the correct sink.
If you release MPIRP like this, I guess that we need to copy and paste these 
methods in all reports which will be bumped to Doxia:1.0-alpha-9

 Move logic inside AbstractProjectInfoReport to maven-reporting-impl
 ---

 Key: MPIR-74
 URL: http://jira.codehaus.org/browse/MPIR-74
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Vincent Siveton
Priority: Blocker
 Fix For: 2.1


 Due to doxia:1.0-alpha-9, the following methods need to be a part of 
 maven-reporting-impl:
 private File getSkinArtifactFile();
 public void execute();
 So, it should be more easy to create a new report plugin.

-- 
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: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113010
 ] 

Dennis Lundberg commented on MSOURCES-27:
-

I can now confirm that 2.0.2 works as describe in my previous comment.

I'm considering changing from 
{code}
if ( resourceExcludes == null || resourceExcludes.size() == 0 )
{
excludes = FileUtils.getDefaultExcludes();
}
else
{
excludes = (String[]) resourceExcludes.toArray( new 
String[resourceExcludes.size()] );
}
{code}

to

{code}
if ( resourceExcludes == null || resourceExcludes.size() == 0 )
{
excludes = FileUtils.getDefaultExcludes();
}
else
{
List allExcludes = new ArrayList();
allExcludes.addAll( FileUtils.getDefaultExcludesAsList() );
allExcludes.addAll( resourceExcludes );
excludes = (String[]) allExcludes.toArray( new String[allExcludes.size()] );
}
{code}

Does that sound right to you Daniel?

 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl


[ 
http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113011
 ] 

Dennis Lundberg commented on MPIR-74:
-

Do you mean reports within the maven-pir-plugin or other reports?

This plugin builds and runs fine as it is now, with doxia 1.0-alpha-9. I don't 
see what the problem is.

 Move logic inside AbstractProjectInfoReport to maven-reporting-impl
 ---

 Key: MPIR-74
 URL: http://jira.codehaus.org/browse/MPIR-74
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Vincent Siveton
Priority: Blocker
 Fix For: 2.1


 Due to doxia:1.0-alpha-9, the following methods need to be a part of 
 maven-reporting-impl:
 private File getSkinArtifactFile();
 public void execute();
 So, it should be more easy to create a new report plugin.

-- 
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: (MPIR-74) Move logic inside AbstractProjectInfoReport to maven-reporting-impl


[ 
http://jira.codehaus.org/browse/MPIR-74?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113012
 ] 

Vincent Siveton commented on MPIR-74:
-

The main pb is not in the MPIR (works fine) but in all report pending plugins. 
We need to extract this logic somewhere to avoid copy/paste.

Just try to create a new report plugin with doxia:1.0-alpha-9 and specify the 
following content
{noformat}
getSink().head();
getSink().text( REPORT NAME );
getSink().head_();
{noformat}


 Move logic inside AbstractProjectInfoReport to maven-reporting-impl
 ---

 Key: MPIR-74
 URL: http://jira.codehaus.org/browse/MPIR-74
 Project: Maven 2.x Project Info Reports Plugin
  Issue Type: Improvement
Affects Versions: 2.1
Reporter: Vincent Siveton
Priority: Blocker
 Fix For: 2.1


 Due to doxia:1.0-alpha-9, the following methods need to be a part of 
 maven-reporting-impl:
 private File getSkinArtifactFile();
 public void execute();
 So, it should be more easy to create a new report plugin.

-- 
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: (SUREFIRE-286) ClassLoader.getSystemResource(String) returns null with valid resource

2007-11-06 Thread Clint Gilbert (JIRA)


[ 
http://jira.codehaus.org/browse/SUREFIRE-286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113015
 ] 

Clint Gilbert commented on SUREFIRE-286:


I had the same issue, but using

this.getClass().getClassLoader().getResourceAsStream(my-resource);

instead of 

this.getClass().getResourceAsStream(my-resource);

Did the trick.  Thanks for the suggestion!  It saved me lots and lots of 
frustration.

 ClassLoader.getSystemResource(String) returns null with valid resource
 --

 Key: SUREFIRE-286
 URL: http://jira.codehaus.org/browse/SUREFIRE-286
 Project: Maven Surefire
  Issue Type: Bug
  Components: classloading
Affects Versions: 2.0 Report Plugin
 Environment: Windows XP
Reporter: Jamo Smith
Priority: Minor
 Fix For: 2.4

 Attachments: mvntest.zip


 src/main/java/org/mvntest/TinyGetter.java does this:
 URL url = ClassLoader.getSystemResource(tiny.gif);
 tiny.gif is located in
 src/main/resources
 a TestCase can be found in src/test/java/org/mvntest/TinyGetterTest.java
 which fails with NPE (url is null)
 I believe this TestCase ought to be successful, since tiny.gif should be in 
 the classpath during tests (how else do you have a simulated test 
 environment?).  I tried placing tiny.gif in src/main/java, src/test/java and 
 src/test/resources with no luck anywhere.  Although I believe this should 
 work even if it is only in src/main/resources
 A full, isolated, maven2 project is attached.
 Thanks, and I hope I'm not over looking something.  If I am, I apologize in 
 advance.

-- 
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: (MSOURCES-27) source jar includes .svn directories


[ 
http://jira.codehaus.org/browse/MSOURCES-27?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113017
 ] 

Daniel Kulp commented on MSOURCES-27:
-

Yep.  That looks right to me.   That matches 2.0.2 as well as the behavior of 
the resource plugin.



 source jar includes .svn directories
 

 Key: MSOURCES-27
 URL: http://jira.codehaus.org/browse/MSOURCES-27
 Project: Maven 2.x Source Plugin
  Issue Type: Bug
Affects Versions: 2.0.3
Reporter: Daniel Kulp

 source:jar with 2.0.3 is adding the .svn directories into the jar.2.0.2 
 did not.

-- 
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: (MAVENUPLOAD-1798) Need to move rsync to different host than sourceforge

2007-11-06 Thread Mark Diggory (JIRA)

Need to move rsync to different host than sourceforge
-

 Key: MAVENUPLOAD-1798
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1798
 Project: maven-upload-requests
  Issue Type: Improvement
Reporter: Mark Diggory


Apparently our artifacts are simply too big and numerous to be supported in the 
SF group directory, instead we will be hosting our own remote repository.  I 
configured the mavensync user with the public key and it should now be 
available for login.

#!/bin/sh

CONTACTS=DSpace Developers [EMAIL PROTECTED]
MODE=rsync_ssh

[EMAIL PROTECTED]:/var/maven/release
GROUP_DIR=org/dspace/


-- 
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-1798) Need to move rsync to different host than sourceforge

2007-11-06 Thread Mark Diggory (JIRA)


[ 
http://jira.codehaus.org/browse/MAVENUPLOAD-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_113023
 ] 

Mark Diggory commented on MAVENUPLOAD-1798:
---

I've also encountered a syncronization issue the following artifacts are not 
getting added to the central repo

http://dspace.sourceforge.net/repository/release/org/dspace/xmlui/jakarta/jakarta-bcel/20040329/

should be at 

http://repo2.maven.org/maven2/org/dspace/xmlui/jakarta/jakarta-bcel/20040329/

it is also available in the new repository location at

http://maven.dspace.org/release/org/dspace/xmlui/jakarta/jakarta-bcel/20040329/

I'm concerned that because the release looks like a date its not getting 
transfered. However, this is a stable release of this dependency for our 
project.

We are encountering the same issue for

http://repo2.maven.org/maven2/org/dspace/xmlui/jcs/jcs/1.2.5-dev-20050313/
http://dspace.sourceforge.net/repository/org/dspace/xmlui/jcs/jcs/1.2.5-dev-20050313/
http://maven.dspace.org/release/org/dspace/xmlui/jcs/jcs/1.2.5-dev-20050313/

thanks for any advice,
Mark Diggory

 Need to move rsync to different host than sourceforge
 -

 Key: MAVENUPLOAD-1798
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1798
 Project: maven-upload-requests
  Issue Type: Improvement
Reporter: Mark Diggory

 Apparently our artifacts are simply too big and numerous to be supported in 
 the SF group directory, instead we will be hosting our own remote repository. 
  I configured the mavensync user with the public key and it should now be 
 available for login.
 #!/bin/sh
 CONTACTS=DSpace Developers [EMAIL PROTECTED]
 MODE=rsync_ssh
 [EMAIL PROTECTED]:/var/maven/release
 GROUP_DIR=org/dspace/

-- 
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: (MAVENUPLOAD-1803) Upload request for swingworker

Upload request for swingworker
--

 Key: MAVENUPLOAD-1803
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1803
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Wim Deblauwe




-- 
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: (MAVENUPLOAD-1802) Upload request for swinglayout

Upload request for swinglayout
--

 Key: MAVENUPLOAD-1802
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1802
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Wim Deblauwe




-- 
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: (MAVENUPLOAD-1801) Upload request for multiplegradientpaint

Upload request for multiplegradientpaint


 Key: MAVENUPLOAD-1801
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1801
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Wim Deblauwe


Needed for swingx for jdk 1.5

-- 
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: (MAVENUPLOAD-1800) Upload request for swingx 0.9 for jdk 1.6

Upload request for swingx 0.9 for jdk 1.6
-

 Key: MAVENUPLOAD-1800
 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1800
 Project: maven-upload-requests
  Issue Type: Task
Reporter: Wim Deblauwe


SwingX is all about Swing components. It focuses both on extensions to existing 
Swing components as well as brand new ones. SwingX contains a lot of great 
components that you can use in your applications today.

-- 
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: (MAVENUPLOAD-1799) Upload request for swingx 0.9 for jdk 1.5