[jira] Created: (MNG-3337) Downloading plugins for an inhouse repository problem
Downloading plugins for an inhouse repository problem - Key: MNG-3337 URL: http://jira.codehaus.org/browse/MNG-3337 Project: Maven 2 Issue Type: Bug Components: Plugins and Lifecycle Reporter: sedatcorbaci Priority: Blocker For an inhouse maven repository we can't find a way to download the plugins to local repo. When we try to execute an initial archetype:create command encountered maven couldn't find the archetype plugin error. To deal with this we just copies org.apache folder to local repo and then everything fine. But again if i need any plugin that is not in copied to local repo manually maven couldn't download it from internal 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] Commented: (MNG-3336) site reporting causes release:perform to fail
[ http://jira.codehaus.org/browse/MNG-3336?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117809 ] Paul Sundling commented on MNG-3336: Forgot to mention, zip file contains code that reproduces issue with aggregate reports causing release failure. > site reporting causes release:perform to fail > - > > Key: MNG-3336 > URL: http://jira.codehaus.org/browse/MNG-3336 > Project: Maven 2 > Issue Type: Bug >Reporter: Paul Sundling > Attachments: minimal.zip > > > It seems that if mxing aggregates and non-aggregates of the same report that > it causes release:perform to fail! This definitely happens with javadoc . > Either removing the aggregate or non-aggregate version seems to not cause a > release:perform failure. > The specific command lines I am using: > mvn -B -Dresume=false -Dmaven.test.skip release:prepare > mvn -B -Dmaven.test.skip release:perform > I can also get this error when doing mvn site:site if I have not done a mvn > install since the version was updated. -- 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-3336) site reporting causes release:perform to fail
site reporting causes release:perform to fail - Key: MNG-3336 URL: http://jira.codehaus.org/browse/MNG-3336 Project: Maven 2 Issue Type: Bug Reporter: Paul Sundling Attachments: minimal.zip It seems that if mxing aggregates and non-aggregates of the same report that it causes release:perform to fail! This definitely happens with javadoc . Either removing the aggregate or non-aggregate version seems to not cause a release:perform failure. The specific command lines I am using: mvn -B -Dresume=false -Dmaven.test.skip release:prepare mvn -B -Dmaven.test.skip release:perform I can also get this error when doing mvn site:site if I have not done a mvn install since the version was updated. -- 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: (WAGON-94) ignoreFailures flag is ignored
[ http://jira.codehaus.org/browse/WAGON-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dan Tran updated WAGON-94: -- Component/s: wagon-ssh > ignoreFailures flag is ignored > -- > > Key: WAGON-94 > URL: http://jira.codehaus.org/browse/WAGON-94 > Project: wagon > Issue Type: Bug > Components: wagon-ssh >Affects Versions: 1.0-beta-2 > Environment: xp,solaris,linux >Reporter: Dan Tran > Attachments: WAGON-91-94.diff > > > The current AbstractJschWagon.java has an option ignore error found in stderr > stream, how ever this option is not checked. > For my case, I wouild like to setup that option so what wagon would not throw > exception and have me to handle error myself. -- 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: (WAGON-92) Wrong URL computation causes svn commit error
[
http://jira.codehaus.org/browse/WAGON-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117789
]
Geoff Fortytwo commented on WAGON-92:
-
Thank you for this! I just spent several hours trying to figure this out. I
kept searching for newer versions of various libraries. Eventually I found this
page, went back and made the modification, generated a new version of the
wagon-scm jar, and I was in business!
I don't know why it was inserting backslashes into the url, but forcing them to
be forward slashes made everything work.
> Wrong URL computation causes svn commit error
> -
>
> Key: WAGON-92
> URL: http://jira.codehaus.org/browse/WAGON-92
> Project: wagon
> Issue Type: Bug
> Components: wagon-scm
>Reporter: Kohsuke Kawaguchi
>
> In ScmWagon.java line 388, the following code exists:
> {noformat}
> scmRepository = getScmRepository( getRepository().getUrl() + "/"
> + target );
> CheckOutScmResult ret = scmProvider.checkOut( scmRepository,
> new ScmFileSet( new
> File( checkoutDirectory, "" ) ),
> (ScmVersion) null,
> false );
> checkScmResult( ret );
> {noformat}
> On Windows where the directory separator in 'target' is back slave, this
> creates incorrect URL, causing the check out operation to fail like this:
> {noformat}
> Caused by: org.apache.maven.wagon.TransferFailedException: Unable to commit
> file. The svn command failed. svn: URL
> 'file:///c:/kohsuke/My%20Projects/experiments/wagon-scm/repo/test%5Cstax-ex%5C1.2-SNAPSHOT'
> doesn't exist
> at
> org.apache.maven.wagon.providers.scm.ScmWagon.checkScmResult(ScmWagon.java:514)
> at
> org.apache.maven.wagon.providers.scm.ScmWagon.checkOut(ScmWagon.java:393)
> at
> org.apache.maven.wagon.providers.scm.ScmWagon.putInternal(ScmWagon.java:287)
> at
> org.apache.maven.wagon.providers.scm.ScmWagon.put(ScmWagon.java:259)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:222)
> at
> org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:151)
> at
> org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:80)
> ... 19 more
> {noformat}
> Unlike file path, a path separator in URL is always '/'. I confirmed that the
> following change makes this work.
> {noformat}
> scmRepository = getScmRepository( getRepository().getUrl() + "/"
> + target.replace('\\','/') );
> {noformat}
--
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
